Re: [Last-Call] Last Call: <draft-halpern-gendispatch-consensusinformational-02.txt> (IETF Stream Documents Require IETF Rough Consensus) to Best Current Practice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have no idea what you are asking for.
The existing rules permit certain behavior which, if the community approves this document, will now be prohibited. that is all it does. There are very few if any examples of documents that were permitted but would now be prohibited.

At this point, I will leave it to the document shepherd and AD to tell me if there is something more needed.

Yours,
Joel

On 1/25/2020 1:12 AM, Rob Sayre wrote:
On Fri, Jan 24, 2020 at 9:48 PM Joel M. Halpern <jmh@xxxxxxxxxxxxxxx <mailto:jmh@xxxxxxxxxxxxxxx>> wrote:

    You seem to be looking for some categorization other than what the
    document says.  I am unclear why.


I asked for some example documents. Could you provide some?


    The document states clearly that it applies to all Informational and
Experimental documents on the IETF stream.

Yes, but not what happens next. Which leaves it incomplete.

thanks,
Rob

--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux