RE: Another IESG Charter revision

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

> -----Original Message-----
> From: Bill Fenner [mailto:fenner@research.att.com]
> Sent: dinsdag 8 april 2003 1:01
> To: randy@psg.com
> Cc: harald@alvestrand.no; iesg@ietf.org
> Subject: Re: Another IESG Charter revision
> 
> >> 5.2.2 Informational and Experimental
> >> 
> >>    These documents are submitted to the RFC Editor in 
> accordance with
> >>    the procedures of BCP 9 [1] section 4.2.3 and BCP 25 
> [2] section 8.
> >>    The IESG is asked to review all documents submitted in 
> this fashion
> >>    for conflicts with the IETF standards process or work 
> done in the
> >>    IETF community; this is a modification of the BCP 9 [1] 
> procedure,
> >>    and documented in BCP 25 [2] section 8.
> >
> >info and experimental can also come from anyomne through an AD,
> >yes?
> 
> Scott told me in San Francisco that the process did not permit an
> AD to introduce an individual document, that the RFC-Editor had to
> be the gate for all non-WG documents.  He said that something had
> been successfully appealed due to using this process.
> 
I believe I have done several of them. Specifically those that go
for stds track. In fact I thought they MUST find a sponsoring or
shepherding AD to go through the process.

Mmm... I am working on an individual ID of my own that wants to go 
stds track. I was planning to put it on IESG agenda (after 4 week
last call, whihc is running now) and then ask Randy my co-AD to
take the yes-vote. So you tell me we cannot do that?

Bert
>   Bill
>