Re: Another IESG Charter revision

[Bill Fenner <fenner@research.att.com>]

>> 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.

  Bill