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

John Drake <jdrake@calient.net> Tue, 14 January 2003 15:13 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 KAA26444; Tue, 14 Jan 2003 10:13:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18YSfX-0003S9-00 for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 10:07:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18YSfD-0003Rq-00 for ietf@ran.ietf.org; Tue, 14 Jan 2003 10:07:39 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26022; Tue, 14 Jan 2003 10:03:21 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19) id <4GJZ1JM8>; Tue, 14 Jan 2003 07:06:35 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC972118@nimbus>
From: John Drake <jdrake@calient.net>
To: 'Kireeti Kompella' <kireeti@juniper.net>, iesg@ietf.org
Cc: ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Tue, 14 Jan 2003 07:06:34 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Kireeti,

Presumably your comments, which I agree with, apply to
draft-lin-ccamp-gmpls-ason-rsvpte-04.txt as well?

Thanks,

John

-----Original Message-----
From: Kireeti Kompella [mailto:kireeti@juniper.net]
Sent: Monday, January 13, 2003 5:26 PM
To: iesg@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational


Hi All,

On Tue, 31 Dec 2002, The IESG wrote:

> The IESG has received a request to consider CR-LDP Extensions for ASON
> <draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.
> This has been reviewed in the IETF but is not the product of an IETF
> Working Group.

I have two comments about this draft.

The first is that the draft calls for assignment of code points for
some new messages, TLVs and status codes.  The draft, however, fails
to say from which spaces these should come (e.g., that to be allocated
by IETF Consensus, First Come First Served, Experimental).  If this is
not specified, then I would suggest that code points from Experimental
spaces be used.

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.
Also, more detail on what the goal is here, under what circumstances
these messages need to be sent/replied to, etc.

Kireeti.