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 25-Jan-20 15:08, Rob Sayre wrote:
> 
> 
> On Fri, Jan 24, 2020 at 6:03 PM Brian E Carpenter <brian.e.carpenter@xxxxxxxxx <mailto:brian.e.carpenter@xxxxxxxxx>> wrote:
> 
>     On 25-Jan-20 14:48, Eric Rescorla wrote:
>     ...
>     >>     However, there are a bunch of ways for the IESG to block publication of IRTF or Independent Stream documents given in RFC 5742.
>     >
>     >
>     > This seems off topic for this document, which, as noted above, only refers to the IETF stream.
> 
>     Also it's inaccurate. The IESG has no blocking power. The most the IESG can do is request the Independent Stream Editor not to publish a draft, or to request them to insert a specific IESG note, but the ISE has the final say. Similarly for IRTF drafts, where authority lies with the IRSG.
> 
> 
> Has the IESG ever been crossed in this way? I've seen some RFCs with IESG disapproval notes, but nothing more.

You'd better ask that question on the rfc-interest@xxxxxxxxxxxxxx list.

    Brian

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