RE: draft-mrose-ietf-posting-03

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

OK by me

Thanks,
Bert 

> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no]
> Sent: vrijdag 19 september 2003 23:57
> To: Russ Housley; iesg@ietf.org
> Subject: Re: draft-mrose-ietf-posting-03
> 
> 
> I can forward this to the author, and suggest that we can do 
> this with an 
> RFC Editor note. That OK with y'all?
> 
> --On 18. september 2003 19:30 -0400 Russ Housley 
> <housley@vigilsec.com> 
> wrote:
> 
> > Here is my suggested rewording to avoid the term "vote."
> >
> > The 2nd paragraph of section 2...
> >
> > OLD:
> >
> >     As a part of its activities, the Internet Engineering 
> Steering Group
> >     (IESG) votes on "actions". Typically, an action refers to the
> >     publication of a document on the standards-track, the 
> chartering of a
> >     working group, and so on. This memo recommends that the 
> IESG also
> >     undertake a new type of action, termed a PR-action.
> >
> > NEW:
> >
> >     As a part of its activities, the Internet Engineering 
> Steering Group
> >     (IESG) makes decisions about "actions". Typically, an action
> >     refers to the publication of a document on the 
> standards-track, the
> >     chartering of a working group, and so on. This memo recommends
> >     that the IESG also undertake a new type of action, termed a
> >     PR-action.
> >
> > The numbered list in section 2...
> >
> > OLD:
> >
> >     1.  it is introduced by an IESG Area Director (AD), 
> who, prior to
> >         doing so, may choose to inform the interested parties;
> >
> >     2.  is is published as an IESG last call on the IETF general
> >         discussion list;
> >
> >     3.  it is discussed by the community;
> >
> >     4.  it is discussed by the IESG; and, finally,
> >
> >     5.  it is voted upon by the IESG.
> >
> > NEW:
> >
> >     1.  it is introduced by an IESG Area Director (AD), 
> who, prior to
> >         doing so, may choose to inform the interested parties;
> >
> >     2.  it is published as an IESG last call on the IETF general
> >         discussion list;
> >
> >     3.  it is discussed by the community;
> >
> >     4.  it is discussed by the IESG; and, finally,
> >
> >     5.  using the usual consensus-based process, it is decided
> >         upon by the IESG.
> >
> >
> >
> >
> 
> 
> 
> 
>