Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP

Russ Housley <housley@vigilsec.com> Tue, 06 November 2007 17:20 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 1IpS6Y-0007iA-JL; Tue, 06 Nov 2007 12:20:46 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpS6X-0007i5-Da for ietf@ietf.org; Tue, 06 Nov 2007 12:20:45 -0500
Received: from woodstock.binhost.com ([8.8.40.152]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IpS6X-0005NS-3I for ietf@ietf.org; Tue, 06 Nov 2007 12:20:45 -0500
Received: (qmail 16251 invoked by uid 0); 6 Nov 2007 17:20:39 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.231.48.203) by woodstock.binhost.com with SMTP; 6 Nov 2007 17:20:39 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 06 Nov 2007 12:19:28 -0500
To: Bernard Aboba <aboba@internaut.com>, ietf@ietf.org
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <Pine.LNX.4.64.0711060651260.16514@internaut.com>
References: <Pine.LNX.4.64.0711060651260.16514@internaut.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc:
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
Message-Id: <E1IpS6Y-0007iA-JL@megatron.ietf.org>

Bernard:

The worst case latency comes from the expert review with 
non-disclosure agreements.

We really do believe that this will make the latency much more consistent.

Russ


At 10:02 AM 11/6/2007, Bernard Aboba wrote:
> >I also think this is an appropriate, even if significant,
> >change of policy. I really don't see why we would give away
> >a precious resource such as a protocol number for secret
> >usage.
>
>I also agree that the change is appropriate.  However, I am also aware of
>significant frustration being voiced with respect to the speed by which
>the expert review process moved -- and this change could slow it
>further.  It's worth keeping in mind that the IETF has no power to prevent
>people from using unallocated protocol numbers.


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