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

2011-03-15 Thread Brian Carpenter
On Wed, Mar 16, 2011 at 6:13 AM, Dave CROCKER wrote: > > On 3/14/2011 2:05 PM, Brian E Carpenter wrote: >> >> 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

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

2011-03-15 Thread Brian Carpenter
On Wed, Mar 16, 2011 at 12:03 AM, Mykyta Yevstifeyev wrote: > Hello, > > 2011/3/14, Brian E Carpenter : >> 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 >> >

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

2011-03-15 Thread Brian Carpenter
On Wed, Mar 16, 2011 at 1:11 AM, Phillip Hallam-Baker wrote: > On Tue, Mar 15, 2011 at 3:33 AM, James M. Polk wrote: >> >> 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 proc

ion-procdocs open for public comment

2007-01-31 Thread Brian Carpenter
An ION (IETF Operational Note, see RFC 4693) is open for public comment on the ietf@ietf.org list. Comments should be sent by 2007-02-12. Please see http://www.ietf.org/IESG/content/ions/drafts/ion-procdocs.html ___ Ietf mailing list Ietf@ietf.org https

ion-agenda-and-minutes open for public comment

2007-01-31 Thread Brian Carpenter
An ION (IETF Operational Note, see RFC 4693) is open for public comment on the ietf@ietf.org list. Comments should be sent by 2007-02-12. Note that some early reviewers have suggested that this document is not really needed, since IETF minutes are already of a good enough standard. Opinions on thi

IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)

2006-09-05 Thread Brian Carpenter
[Discussion invited on [EMAIL PROTECTED] The IESG received a request under RFC 3933 to run draft-klensin-norm-ref-01.txt as an experiment in loosening the IETF's requirements for normative references in RFCs. The experiment is composed of two parts. The first part allows approved Internet Drafts