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 Jan 25, 2020, at 10:31 AM, Salz, Rich <rsalz@xxxxxxxxxx> wrote:

  • I suggest a better way forward would be to post an updated IESG statement that requires consensus as well.
 
And what prevents a future IESG from changing its mind next year?

Nothing.  That said, the procedures in this statement have been followed since 2007, and the proposed change is really building on things that are in this statement, like the requirement for the IETF Last Call, which is not in RFC 2026.

Russ


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