Re: Last Call: CR-LDP Extensions for ASON to Informational

Kireeti Kompella <kireeti@juniper.net> Wed, 15 January 2003 00:47 UTC

Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17580; Tue, 14 Jan 2003 19:47:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18Ybd4-00057x-00 for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 19:42:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18Ybcl-00056b-00 for ietf@ran.ietf.org; Tue, 14 Jan 2003 19:41:43 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17365; Tue, 14 Jan 2003 19:37:18 -0500 (EST)
Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h0F0edS64452; Tue, 14 Jan 2003 16:40:39 -0800 (PST) (envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost) by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h0F0ed546836; Tue, 14 Jan 2003 16:40:39 -0800 (PST) (envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Tue, 14 Jan 2003 16:40:39 -0800
From: Kireeti Kompella <kireeti@juniper.net>
To: Bob Braden <braden@ISI.EDU>
cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
In-Reply-To: <200301142300.XAA04045@gra.isi.edu>
Message-ID: <20030114163836.T46812-100000@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf@ietf.org
Precedence: bulk


On Tue, 14 Jan 2003, Bob Braden wrote:

> According to the IANA assignment rules for RSVP values, the only two
> options are IETF consensus and FCFS.

The document in question is the *CR-LDP* Extensions.  I am (sadly)
aware of the RSVP assignment status.

>   *> If code points are to be allocated from the space to be allocated by
>   *> IETF Consensus, I strongly suggest that a *Standards Track* document be
>   *> written, with more detail on the messages, especially their processing.
>
> Indeed, that is what "IETF consensus" means, isn't it?

Is it?  That's good.  Currently, the document is Informational, and
is being processed as such.  Can this be changed?

Kireeti.