Re: I-D Action:draft-housley-two-maturity-levels-04.txt

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

 



At 04:05 PM 3/14/2011, Brian E Carpenter wrote:
There are numerous improvements in this version and I hope we
can get consensus soon.

Just a couple of remarks on
 5. Transition to a Standards Track with Two Maturity Levels

1) Probably there should be a statement that all existing
   Internet Standard documents are still classified as Internet Standard.
   That may seem blindingly obvious, but if we don't write it down,
   somebody will ask.

2) More substantively,

   "Any protocol or service that is currently at the Draft Standard
maturity level may be reclassified as an Internet Standard as soon as
    the criteria in Section 2.2 are satisfied. This reclassification is
    accomplished by submitting a request to the IESG along with a
    description of the implementation and operational experience. "

I'm a bit concerned that this doesn't scale, and we will be left
with a long tail of DS documents that end up in limbo. One way to avoid
this is to encourage bulk reclassifications (rather like we did a bulk
declassification in RFC 4450). Another way is to define a sunset date,
e.g.

   Any documents that are still classified as Draft Standard two years
   after the publication of this RFC will be automatically downgraded
   to Proposed Standard.

Brian

playing devil's advocate here...

Say someone submits a request for an existing DS to the IESG and it takes 6 months (or 3 months) to get through the process, but only 2 months remain before the 2 year window is up (since this RFC was published). Does that grandfather the DS into "the process" - meaning that document is no longer subject to this 'within 2 year notice' rule?

I'm just saying that this appears to beg all DS editors to get their DS notifications into the IESG sooner rather than later, which is fine, but that also creates a heck of a workload on the IESG that they currently do not have, does it not?

Something is going to be impacted.

James



     Brian
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


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