[OSPF] Re: [Fwd: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt]

Acee Lindem <acee@cisco.com> Thu, 30 November 2006 16:56 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GppDO-0002qT-M7; Thu, 30 Nov 2006 11:56:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GppDN-0002qE-JV; Thu, 30 Nov 2006 11:56:49 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GppDM-0007Kb-4M; Thu, 30 Nov 2006 11:56:49 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by sj-iport-4.cisco.com with ESMTP; 30 Nov 2006 08:56:47 -0800
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kAUGukgo012783; Thu, 30 Nov 2006 11:56:46 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kAUGukYJ005588; Thu, 30 Nov 2006 11:56:46 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Nov 2006 11:56:45 -0500
Received: from [10.82.224.37] ([10.82.224.37]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Nov 2006 11:56:45 -0500
Message-ID: <456F0D4C.2070209@cisco.com>
Date: Thu, 30 Nov 2006 11:56:44 -0500
From: Acee Lindem <acee@cisco.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: JP Vasseur <jvasseur@cisco.com>
References: <C12AE018.896F0%dward@cisco.com> <452C089D.5090204@cisco.com> <452C0A97.5010501@cisco.com> <ED2D9A4E-8D44-47B4-B3F9-5A6D7F6E7671@cisco.com>
In-Reply-To: <ED2D9A4E-8D44-47B4-B3F9-5A6D7F6E7671@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Nov 2006 16:56:45.0364 (UTC) FILETIME=[847FCF40:01C714A0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4384; t=1164905806; x=1165769806; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=acee@cisco.com; z=From:=20Acee=20Lindem=20<acee@cisco.com> |Subject:=20Re=3A=20[Fwd=3A=20[mpls]=20WG=20Last=20Call=20on=20draft-ietf -mpls-number-0-bw-te-lsps-02.txt] |Sender:=20 |To:=20JP=20Vasseur=20<jvasseur@cisco.com>; bh=I+70JaJfV5d2Tn3iDx8cCBGNTPlUijVXXjkXF9iT4iU=; b=QfucUAOzPCqU11THGaTNs/G3PPEBED/oQdFpTYFgoBW48kqul0kZjNkS3Wwr7jZJbIZqAm2V mwlIRQ5KHa2YKMrvIY/p4m2uGh+T3mzwzJdfmEZJl+/OkPF7sTyF8N6W;
Authentication-Results: rtp-dkim-1; header.From=acee@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: George Swallow <swallow@cisco.com>, rtg-dir@ietf.org, isis-wg@ietf.org, ospf@ietf.org, David Ward <dward@cisco.com>, Loa Andersson <loa@pi.se>
Subject: [OSPF] Re: [Fwd: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt]
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

Hi JP,
Looks good. See one question below.

JP Vasseur wrote:
> Hi Acee,
>
> Thanks for your comments -
>
> As soon as you ACK that the changes address your comments I'll post 
> the updated ID.
>
> see in line,
>
> On Oct 10, 2006, at 5:03 PM, Acee Lindem wrote:
>
>> JP,
>>
>> One more comment - Please write the document so that it can
>> apply to OSPFv3 TE as well. The existing draft can be an informative
>> reference (draft-ietf-ospf-ospfv3-traffic-07.txt)
>>
>
> OK. Text added:
>
> OLD:
>
>    The Number of 0-bandwidth TE LSP(s) sub-TLV is OPTIONAL and MUST
>    appear at most once within the Link TLV (Type 2) that is itself
>    carried within the Traffic Engineering LSA specified in [RFC3630]. If
>    a second instance of the Number of 0-bandwidth TE LSP(s) sub-TLV is
>    present, the receiving system MUST only process the first instance of
>    the sub-TLV.
>
>
> NEW:
>
>    The Number of 0-bandwidth TE LSP(s) sub-TLV is OPTIONAL and MUST
>    appear at most once within the Link TLV (Type 2) that is itself
>    carried within the OSPFv2 Traffic Engineering LSA specified in 
> [RFC3630]
>    or the OSPFv3 Intra-Area-TE LSA (function code 10) defined in 
> draft-ietf-ospf-ospfv3-traffic.
>    If a second instance of the Number of 0-bandwidth TE LSP(s) sub-TLV is
>    present, the receiving system MUST only process the first instance of
>    the sub-TLV.
>
> see below
>
>> Thanks,
>> Acee
>>
>> Acee Lindem wrote:
>>> I've reviewed the subject document and don't have any comments on it
>>> from the perspective of the OSPF WG. However, I have the following
>>> comments as a member of the routing directorate (copying JP):
>>>
>>>   1. Why the cryptic sub-TLV name? RFC 3630 doesn't define short
>>>       cryptic names for sub-TLVs so I don't really see why you've 
>>> defined
>>>       NB-0-BW-LSP? Why not just call it the Unconstrained LSP Count 
>>> sub-TLV?
>>>       Or at least come up with a better short name :^),  e.g. 
>>> BW-0-LSP-CNT.
>
> Yes, no problem. I renamed it ;-)
>
> Number of 0-bandwidth TE LSP(s) sub-TLV.
>
>>>   2. How did you arrive at 19 for the suggested value for the 
>>> sub-TLV type? I checked
>>>       IANA and 18 is the next available. I may be missing a document 
>>> though.
>
> As documented, 18 looks the next one available (when I first wrote the 
> ID I vaguely remember having seen another ID using 18 but I'm not 
> quite sure). Let's propose 18 and will see with IANA.
>
>>>   3. Do  you want to reserve a value (e.g., 0xffffffff) to indicate 
>>> no unconstrained
>>>       LSPs are to traverse a given link.
>
> Let's just use the value 0.
Since this is the current number wouldn't there be ambiguity between 
designating there
are currently no BW-0 LSPs traversing this link and no BW-0 LSPs are allowed
to traverse this linke?

Thanks,
Acee

>
>>>   4. Nit - in section 4, replace "OSPF LSA" with "OSPF LSAs" and 
>>> "ISIS LSP"
>>>       with "ISIS LSPs".
>
> Thanks.
>
> Cheers.
>
> JP.
>
>>>
>>> Thanks,
>>> Acee
>>>              David Ward wrote:
>>>> Do you want our WG to review? Co-Last Call (as we have for other WG 
>>>> that
>>>> affect our protocol)? Do you have a desired date for end of last 
>>>> call from
>>>> the IGPs?
>>>>
>>>> Thanks
>>>>
>>>> -DWard
>>>>
>>>>
>>>> On 9/4/06 5:01 AM, "Loa Andersson" <loa@pi.se> wrote:
>>>>
>>>>
>>>>> All,
>>>>>
>>>>> the MPLS working group want to notify the ospf and is-s
>>>>> working groups, as well as the routing directorate that
>>>>> we are currently doing a wg last call on
>>>>> draft-ietf-mpls-number-0-bw-te-lsps-02.txt.
>>>>>
>>>>> Loa and George
>>>>>
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: [mpls] WG Last Call on 
>>>>> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
>>>>> Date: Fri, 01 Sep 2006 10:08:10 +0200
>>>>> From: Loa Andersson <loa@pi.se>
>>>>> Organization: Acreo AB
>>>>> To: mpls@ietf.org
>>>>>
>>>>> Working Group,
>>>>>
>>>>> this initiates a two week working group last call on
>>>>> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
>>>>>
>>>>> The wg last call ends on September 17.
>>>>>
>>>>> Please send comments to the working group mailing list and/or
>>>>> the working group chairs.
>>>>>
>>>>> /Loa and George
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>

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