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]

 





On Fri, Jan 24, 2020 at 5:54 PM Rob Sayre <sayrer@xxxxxxxxx> wrote:
On Fri, Jan 24, 2020 at 5:49 PM Eric Rescorla <ekr@xxxxxxxx> wrote:

Maybe I'm confused about this, or shouldn't have used the term "discuss criteria" (though [0] contained the term, as well as the section on "Document Classes Reviewed by the IESG").

All of these document classes apply only to the IETF stream.

Then where do "Document Actions (from RFC-Editor)" originate?

My mistake. The DISCUSS criteria only apply to Protocol actions.

"Protocol Actions are naturally subject to greater scrutiny than Document Actions; Area Directors are not even required to state a position on a Document Action (the default being "No Objection"). Accordingly, the exact criteria used to evaluate Protocol Actions would benefit from greater scrutiny. The remainder of this document focuses on the use of DISCUSS for standards-track and BCP documents."

-Ekr



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