Re: Facts and draft-state information (was Re: Protocol Action: 'Case-Sensitive String Support in ABNF' to Proposed Standard (draft-kyzivat-case-sensitive-abnf-02.txt)

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

 



On Tue, Oct 7, 2014 at 2:38 AM, Abdussalam Baryun <abdussalambaryun@xxxxxxxxx> wrote:
The draft in subject is not product of IETF WG so it has no consensus needed, however, in the document Page in data tracker it should IETF-state as None and that there were consensus as Yes. We need to make this error stop. There are other state/info issues with other RFCs that we need to be careful when we input but  I will give some examples;

It's not true that no consensus is needed for a document just because it's not a WG product.  Anything that comes through the IETF stream (including AD-sponsored documents) need to reflect consensus.

-MSK

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