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 11:08 AM, Spencer Dawkins at IETF <spencerdawkins.ietf@xxxxxxxxx> wrote:
Just piling in after Barry here ... and speaking as the AD who had the most recent ¨draft on a telechat agenda with consensus = unknown¨, but I'm hardly the only one.

The field in the tracker is labeled ¨consensus¨, which is ambiguous but actually means ¨IETF consensus¨. So, it should be set after IETF Last Call.

A fair number of the documents I've processed already had it set to ¨yes¨ when they were publication-requested, so that means the shepherd/working group chairs thought it meant ¨working group consensus¨.

I believe - but Barry would know - that we've requested that the field label be changed to ¨IETF Consensus¨ in the datatracker. 

(I know we talked about that, but I don't know whether we've made the request yet)


I've set that field as a WG chair to indicate the document came from a consensus process, which I guess is the same thing, and would always be "Yes" for the product of a working group anyway.  I've noticed though that I don't always have control over that field's contents anymore.

-MSK


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