Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
Jari Arkko <jari.arkko@piuha.net> Tue, 06 November 2007 10:45 UTC
Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpLvi-0002Er-L7; Tue, 06 Nov 2007 05:45:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpLvf-0002DI-Is for ietf@ietf.org; Tue, 06 Nov 2007 05:45:07 -0500
Received: from [2001:14b8:400::130] (helo=smtp.piuha.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpLve-0006pG-VO for ietf@ietf.org; Tue, 06 Nov 2007 05:45:07 -0500
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 24F1F1986C6; Tue, 6 Nov 2007 12:45:06 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 75B73198676; Tue, 6 Nov 2007 12:45:05 +0200 (EET)
Message-ID: <473045AC.9040509@piuha.net>
Date: Tue, 06 Nov 2007 12:45:00 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.14pre (X11/20071022)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
References: <E1Ip924-0002IB-7X@stiedprstage1.ietf.org> <fgo5r7$ejk$1@ger.gmane.org> <472FB07F.7030401@gmail.com>
In-Reply-To: <472FB07F.7030401@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -1.4 (-)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ietf@ietf.org
Subject: Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
Brian, Frank, Thanks for your comments. A few additional notes below: > Red herring as far as this draft is concerned: I'd be interested > to know why we are still willing to allow non-disclosure for > port numbers (see RFC 2780 sections 8 and 9.1). Port numbers > are going fast. As was mentioned already, this is something that Lars and a few other folks are currently looking at. I'm presuming that there will be a draft about this later. But the port case might be different; that's why they are pursued separately, even if both share some practical problems associated with NDAs for volunteer experts etc. I view the protocol number rule change as a bug fix. >>> From -00 to Last Call in less than three hours, is that >> a "speedy publish" procedure I haven't heard of before ? > > I-D submission tool plus the sponsoring AD's special buttons in > the I-D tracker. Seems like eating our own dogfood to me. Its part of the IESG's effort to improve the speed of our process by moving to units of hours instead of months ;-) But seriously, this was merely the combination of a very short draft, a change that appears to be the right thing, sponsoring AD (Russ) being aware of the issue from past discussions with IANA, and the AD review getting done in fifteen minutes after I requested it. But the main effort and bulk of time for this draft is in the public discussion of what rules makes sense -- and we just started that in the last call. More generally, short drafts and bug fixes tend to go through relatively quickly. Individual submissions via sponsoring AD may sometimes go quicker than WG submissions, because there are less forums and their managers to go through. However, individual submissions may get less priority from the ADs if they have many WG submissions on their queue as well. And complex proposals need some forum for the discussion to happen in any case. Finally, drafts that do not need modification at LC or IESG review stage tend to go through about four times as fast as drafts that do need modification. Jari _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Frank Ellermann
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Brian E Carpenter
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Lars Eggert
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Jari Arkko
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Bernard Aboba
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Russ Housley
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Ted Hardie
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Jari Arkko
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Michelle Cotton
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Bill Fenner
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Stephane Bortzmeyer
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Stephane Bortzmeyer
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Jari Arkko
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Bernard Aboba
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Bill Fenner
- Re: Last Call: draft-arkko-rfc2780-proto-update (… Jari Arkko