Re: draft-housley-two-maturity-levels
John Leslie <john@jlc.net> Tue, 26 October 2010 14:45 UTC
Return-Path: <john@jlc.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C4933A697D for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 07:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.102
X-Spam-Level:
X-Spam-Status: No, score=-106.102 tagged_above=-999 required=5 tests=[AWL=0.497, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DhaK-XctE+7f for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 07:45:14 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by core3.amsl.com (Postfix) with ESMTP id B25023A6972 for <ietf@ietf.org>; Tue, 26 Oct 2010 07:45:13 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id E573333C48; Tue, 26 Oct 2010 10:46:58 -0400 (EDT)
Date: Tue, 26 Oct 2010 10:46:58 -0400
From: John Leslie <john@jlc.net>
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <20101026144658.GO82074@verdi>
References: <20101026024811.BD2AD5AC74F@newdev.eecs.harvard.edu> <665140E6-F4EF-4F7E-8973-984CF3096694@standardstrack.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <665140E6-F4EF-4F7E-8973-984CF3096694@standardstrack.com>
User-Agent: Mutt/1.4.1i
Cc: "Scott O. Bradner" <sob@harvard.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2010 14:45:15 -0000
Eric Burger <eburger@standardstrack.com> wrote: > > The known problem is it takes well over four years to get anything > published. We've actually been making progress on that, at least for the part where the IESG is involved. Russ's draft _would_ reduce one issue: where a reference should be Normative but hasn't been called out, the LastCall must be repeated. This is an irritant, and never seems to actually change anything. I frankly cannot see how Russ's draft would speed the process any other way. And I worry that changing to two levels would make folks even more hesitant to approve Proposed Standard status. (This is more a worry than an actual issue with what Russ's draft _says_...) > I am experiencing in one never-ending saga the logical conclusion > of the logic: since Proposed Standard is the new Draft Standard, > and since the IESG has to make sure any proposal is beyond bullet- > proof, the industry has long since implemented draft-mumble-21, > which has not changed for over a year, and few in industry cares > if the document publishes as an RFC, because from their point of > view, if something has been working in the field for three years, > has 18 independent implementations, and has not yet crashed the > Internet, it is probably ready, whether the IETF formally says so > or not. That is the fast track to making the IETF irrelevant. This is a function of WGCs worrying too much before asking the IESG to act on Working-Group submissions. I can't see Russ's proposal reducing that problem. :^( BTW, the Individual Submission route bypasses that problem, and is being used fairly liberally. Individual Submissions _never_ take four years (unless the submitter lost interest along the way). > The very real danger here is while that attitude may be OK for a > small media application, that attitude could be a disaster in, > for example, the routing area. Something really has to be done. Indeed, we _have_ seen a disaster in the routing area... :^( > Now, I do agree with Scott here there is absolutely no incentive > for anyone to bring a protocol to Draft/Internet Standard level. Scott exaggerates a bit, but the incentive _is_ usually lacking. It's the lack of incentive, combined with a belief that so-and-so "should" shepherd the advancement, that has led to IESG desires to remove known problems from PS drafts. (Thus, IMHO, the fix for this problem is either better incentives or assigning responsibility for advancement to someone who _has_ an incentive to complete it.) > What I *am* hoping is that with two, clearly defined maturity > levels, we can go back to publishing Proposed Standards in about > a year, and have Internet Standard mean something. "Hope springs eternal..." Alas, I can imagine no rational basis for that hope. :^( > Otherwise, we will be perpetually running the Internet on Internet > Drafts, which is something I do not think anyone really can say > is a good thing. We _cannot_ stop folks from "running" the Internet on I-Ds. And, to be honest, the Internet is based on RFCs that were _easier_ to publish than I-Ds are today. Although Russ's draft _would_ fix the downref irritant, I can't see it doing anything to reduce the PS logjams -- indeed, human nature ensures we'll invent _more_ logjams once PS is "only one step" from final Standard. Lots of us would like to reduce the PS logjams, but we need to look outside the part of 2026 that deals with number of levels. We might, for example, specifically _allow_ Individual Submissions to bypass a congested WG if no specific objections could be listed. We might reduce the level of "considerations" (such as Security Considerations) expected for Proposed Standard (though, IMHO, that's an increasingly dangerous place to go), or assign responsibility for adding such Considerations to something like a Security Area Directorate. We might forbid WGCs from putting things off until the next IETF week... We might formalize issue-tracking for WGs considering something for PS... We might formalize the Document Editor role to prevent "Document Editors" from pushing their own viewpoint... We might formalize a WG Secretary role to clarify specific issues raised during in-person and virtual meetings... We might _require_ virtual meetings whenever a milestone is in danger of slipping... And, frankly, I could go on, and many others could go on listing things which _would_ reduce some of the logjams that have led us to such long leadtimes to reach PS status. We may be nearing the point, universally found in legislatures, where we'll "vote for anything so we can adjourn". If so, we could do worse than Russ's proposal. But "vote for anything" _very_ often leads to bad law. I fully agree with Scott Bradner that changing the number of levels isn't something we should do lightly. -- John Leslie <john@jlc.net>
- draft-housley-two-maturity-levels John C Klensin
- Re: draft-housley-two-maturity-levels SM
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: draft-housley-two-maturity-levels John C Klensin
- Re: draft-housley-two-maturity-levels Eric Rosen
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: draft-housley-two-maturity-levels Julian Reschke
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: draft-housley-two-maturity-levels Russ Housley
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels James M. Polk
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels James M. Polk
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels Russ Housley
- Re: draft-housley-two-maturity-levels Barry Leiba
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels Eric Burger
- Re: draft-housley-two-maturity-levels Keith Moore
- Re: draft-housley-two-maturity-levels John Levine
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- RE: draft-housley-two-maturity-levels Ross Callon
- Re: draft-housley-two-maturity-levels Bert (IETF) Wijnen
- Re: draft-housley-two-maturity-levels Eric Burger
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- Re: draft-housley-two-maturity-levels Russ Housley
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: draft-housley-two-maturity-levels Julian Reschke
- Re: draft-housley-two-maturity-levels John Leslie
- Re: draft-housley-two-maturity-levels Michael Richardson
- Re: draft-housley-two-maturity-levels Michael Richardson
- Re: draft-housley-two-maturity-levels Andrew Sullivan
- Re: draft-housley-two-maturity-levels RJ Atkinson
- Re: draft-housley-two-maturity-levels Barry Leiba
- Re: draft-housley-two-maturity-levels Martin Rex
- Re: draft-housley-two-maturity-levels Keith Moore
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- Re: draft-housley-two-maturity-levels Ted Hardie
- RE: draft-housley-two-maturity-levels Tony Hain
- Re: draft-housley-two-maturity-levels Michael Richardson
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels John Leslie
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- RE: draft-housley-two-maturity-levels Tony Hain
- RE: draft-housley-two-maturity-levels Tony Hain
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels Michael Richardson
- two independent implementations (Re: draft-housle… Lars Eggert
- Re: draft-housley-two-maturity-levels Lars Eggert
- Re: draft-housley-two-maturity-levels Lars Eggert
- Re: draft-housley-two-maturity-levels ned+ietf
- Re: two independent implementations (Re: draft-ho… James M. Polk
- RE: draft-housley-two-maturity-levels Tony Hain
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: two independent implementations (Re: draft-ho… James M. Polk
- Re: draft-housley-two-maturity-levels David Kessens
- Re: two independent implementations John Leslie
- Re: draft-housley-two-maturity-levels SM
- RE: two independent implementations Tony Hain
- Re: draft-housley-two-maturity-levels Bob Braden
- Re: draft-housley-two-maturity-levels Yoav Nir
- RE: draft-housley-two-maturity-levels Tony Hain
- Re: draft-housley-two-maturity-levels Bob Braden
- Re: draft-housley-two-maturity-levels Peter Saint-Andre
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels Eric Burger
- Re: draft-housley-two-maturity-levels Ralph Droms
- Re: draft-housley-two-maturity-levels Ralph Droms
- Re: draft-housley-two-maturity-levels ned+ietf
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels Joel Jaeggli
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels Russ Housley
- Re: draft-housley-two-maturity-levels Peter Saint-Andre
- Re: draft-housley-two-maturity-levels Joel M. Halpern
- Re: draft-housley-two-maturity-levels Peter Saint-Andre
- Re: draft-housley-two-maturity-levels Phillip Hallam-Baker
- Re: draft-housley-two-maturity-levels RJ Atkinson
- Re: draft-housley-two-maturity-levels Tony Hansen
- Re: draft-housley-two-maturity-levels Mykyta Yevstifeyev
- Re: draft-housley-two-maturity-levels John Leslie
- Re: draft-housley-two-maturity-levels ned+ietf
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- Re: draft-housley-two-maturity-levels John C Klensin
- Re: draft-housley-two-maturity-levels Gonzalo Camarillo
- Re: draft-housley-two-maturity-levels John C Klensin
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: draft-housley-two-maturity-levels Doug Barton
- Re: draft-housley-two-maturity-levels SM
- Re: draft-housley-two-maturity-levels Martin Rex
- Re: draft-housley-two-maturity-levels Mark Atwood
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels Russ Housley
- New version of NroffEdit released for IETF80 Stefan Santesson
- Re: draft-housley-two-maturity-levels Joel M. Halpern
- Re: New version of NroffEdit released for IETF80 Stefan Santesson
- Re: draft-housley-two-maturity-levels Mykyta Yevstifeyev
- Re: draft-housley-two-maturity-levels Joel M. Halpern
- Re: draft-housley-two-maturity-levels Mykyta Yevstifeyev
- Re: draft-housley-two-maturity-levels Dave CROCKER
- Re: draft-housley-two-maturity-levels Bob Hinden
- Re: draft-housley-two-maturity-levels Eric Burger
- draft-housley-two-maturity-levels Jari Arkko
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels Scott O. Bradner
- Re: draft-housley-two-maturity-levels Robert Sparks
- Re: draft-housley-two-maturity-levels Eric Burger
- Re: draft-housley-two-maturity-levels Peter Saint-Andre
- Re: draft-housley-two-maturity-levels Keith Moore
- Re: draft-housley-two-maturity-levels Peter Saint-Andre
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels Chris Newman
- Re: draft-housley-two-maturity-levels Pete Resnick
- Re: draft-housley-two-maturity-levels Joel M. Halpern
- Re: draft-housley-two-maturity-levels John Leslie
- Re: draft-housley-two-maturity-levels Brian E Carpenter
- Re: draft-housley-two-maturity-levels RJ Atkinson
- Re: draft-housley-two-maturity-levels Eric Burger
- Re: draft-housley-two-maturity-levels Scott O Bradner
- Re: draft-housley-two-maturity-levels Peter Saint-Andre
- Re: draft-housley-two-maturity-levels John C Klensin
- Re: draft-housley-two-maturity-levels Joel M. Halpern
- Re: draft-housley-two-maturity-levels John C Klensin
- Conclusion of the last call on draft-housley-two-… Jari Arkko
- Re: Conclusion of the last call on draft-housley-… SM
- Re: Conclusion of the last call on draft-housley-… John C Klensin
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… Frank Ellermann
- RE: Conclusion of the last call on draft-housley-… Ross Callon
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- RE: Conclusion of the last call on draft-housley-… ned+ietf
- RE: Conclusion of the last call on draft-housley-… James M. Polk
- Other proposals (Was: :Re: Conclusion of the last… Jari Arkko
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… Jari Arkko
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… Barry Leiba
- RE: Conclusion of the last call on draft-housley-… John C Klensin
- Re: Conclusion of the last call on draft-housley-… ned+ietf
- Re: Conclusion of the last call on draft-housley-… ned+ietf
- Re: Conclusion of the last call on draft-housley-… Brian E Carpenter
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… ned+ietf
- Re: Other proposals (Was: :Re: Conclusion of the … SM
- Re: Conclusion of the last call on draft-housley-… Russ Housley
- Re: Conclusion of the last call on draft-housley-… Hector Santos
- RE: Conclusion of the last call on draft-housley-… Ross Callon
- Re: Conclusion of the last call on draft-housley-… Andrew Sullivan
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… ned+ietf
- Re: Conclusion of the last call on draft-housley-… Ted Hardie
- Re: Conclusion of the last call on draft-housley-… John C Klensin
- Who raised the bar? [Conclusion of the last call … Brian E Carpenter
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Who raised the bar? [Conclusion of the last c… Julian Reschke
- Re: Who raised the bar? [Conclusion of the last c… Keith Moore
- Re: Who raised the bar? [Conclusion of the last c… Dave Cridland
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Who raised the bar? Brian E Carpenter
- Re: Who raised the bar? [Conclusion of the last c… Cullen Jennings
- Re: Conclusion of the last call on draft-housley-… Ted Hardie
- Re: Who raised the bar? [Conclusion of the last c… Ted Hardie
- Re: Conclusion of the last call on draft-housley-… Fred Baker
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… John Leslie
- Re: Conclusion of the last call on draft-housley-… t.petch
- Re: Conclusion of the last call on draft-housley-… ned+ietf
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Who raised the bar? [Conclusion of the last c… Hector Santos
- Re: Who raised the bar? [Conclusion of the last c… JP Vasseur
- Re: Who raised the bar? [Conclusion of the last c… JP Vasseur
- Re: Who raised the bar? [Conclusion of the last c… SM
- Re: Conclusion of the last call on draft-housley-… Thomas Narten
- Re: Conclusion of the last call on draft-housley-… Mykyta Yevstifeyev
- Re: Conclusion of the last call on draft-housley-… Barry Leiba
- Re: Conclusion of the last call on draft-housley-… Russ Housley
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… Mykyta Yevstifeyev
- Re: Conclusion of the last call on draft-housley-… Mykyta Yevstifeyev
- Re: Conclusion of the last call on draft-housley-… Sam Hartman
- Re: Conclusion of the last call on draft-housley-… Hector
- Re: Conclusion of the last call on draft-housley-… hector
- Re: Conclusion of the last call on draft-housley-… Brian E Carpenter
- Re: Conclusion of the last call on draft-housley-… Scott O. Bradner
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… Hector
- Re: Conclusion of the last call on draft-housley-… John C Klensin
- Re: Conclusion of the last call on draft-housley-… Eric Burger
- RFC3844 and IETF Core Values Hector
- Re: Conclusion of the last call on draft-housley-… John C Klensin
- Re: Conclusion of the last call on draft-housley-… Brian E Carpenter
- Re: Conclusion of the last call on draft-housley-… John C Klensin
- Re: Conclusion of the last call on draft-housley-… hector
- Re: Conclusion of the last call on draft-housley-… Mykyta Yevstifeyev
- Re: Conclusion of the last call on draft-housley-… Jari Arkko
- Re: Conclusion of the last call on draft-housley-… Russ Housley
- Re: Conclusion of the last call on draft-housley-… John C Klensin
- Re: Conclusion of the last call on draft-housley-… Hector
- Re: Conclusion of the last call on draft-housley-… John C Klensin
- Re: Conclusion of the last call on draft-housley-… Hector
- Re: Conclusion of the last call on draft-housley-… Sam Hartman
- Re: Conclusion of the last call on draft-housley-… Keith Moore
- Re: Conclusion of the last call on draft-housley-… Martin Rex
- Re: Conclusion of the last call on draft-housley-… Douglas Otis
- Re: Conclusion of the last call on draft-housley-… Hadriel Kaplan
- Re: Conclusion of the last call on draft-housley-… Brian E Carpenter