Re: Working Group Last Call for "Traffic Engineering Extensions to OSPF version 3"

Acee Lindem <acee@CISCO.COM> Mon, 23 May 2005 13:02 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22548 for <ospf-archive@LISTS.IETF.ORG>; Mon, 23 May 2005 09:02:05 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <7.010566C4@cherry.ease.lsoft.com>; Mon, 23 May 2005 9:02:03 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 72192850 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 23 May 2005 09:02:01 -0400
Received: from 64.102.122.149 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Mon, 23 May 2005 09:02:01 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 23 May 2005 09:02:02 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j4ND1q52002262 for <OSPF@PEACH.EASE.LSOFT.COM>; Mon, 23 May 2005 09:01:59 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 23 May 2005 09:01:55 -0400
Received: from [10.82.242.200] ([10.82.242.200]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 23 May 2005 09:01:54 -0400
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <E1DaAFI-0000Cg-9V@oceanus.uk.clara.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 May 2005 13:01:55.0029 (UTC) FILETIME=[98545050:01C55F97]
Message-ID: <4291D442.4090700@cisco.com>
Date: Mon, 23 May 2005 09:01:54 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@CISCO.COM>
Subject: Re: Working Group Last Call for "Traffic Engineering Extensions to OSPF version 3"
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <E1DaAFI-0000Cg-9V@oceanus.uk.clara.net>
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Adrian,

Adrian Farrel wrote:

> Hi,
> Two comments...
> 1. Would it be possible to clarify the behavior if the scope is
>  set to some value other than 01? Is it a requirement that the
>  scope be ignored in that case, that TE information be allowed
>  to be flooded out of the area, or that the LSA is rejected?
>  Given the setting of the U-bit, this may be hard to control
>  properly and I suspect the best you can do is say MUST
>  be transmitted as 01 and SHOULD only be flooded within
>  the area.

I'll change the text to say the flooding scope MUST be set to 01. This
is enough since flooding outside the orginating area would not
be compliant with OSPFv3.

> 2. Section 4 - Router IPv6 Address TLV
>  "The Router IPv6 Address TLV has type 3, length 16, and a value
>   containing a 16 octet local IPv6 address.  It MUST appear in exactly
>   one Traffic Engineering LSA originated by an OSPFv3 router supporting
>   the TE extensions."
>  I am confused by 'MUST appear in exactly one'.
>  Can a router advertise multiple Router addresses? (Hint, please talk to
>  the CCAMP ASON Routing design team for a very good reason why the answer
>  is "yes".)

The intent is that there is at least one stable routable address for the 
OSPF TE router.
There is a proposal to advertise multiple addresses using the TE Node 
Address TLV.


>  Can a TE LSA contain "orphaned" TLVs? I.e. can we have a continuation TE
>  LSA that does not carry a Router Address TLV?

I don't understand this - each TE LSA has a unique LSID. An OSPFv3 router
can originate multiples per area.

>  Given that a router has (probably) more than one "stable IPv6 address
>  that is always reachable if there is connectivity to the OSPFv3 router"
>  must all of these be advertised in Router Address TLVs?

I think the TE node address TLV is meant to advertise additional
addresses. At one time, this TLV was to take on the function of the
Router IPv6 Address TLV. However, it was felt that have a single
preferred router address was preferable. Here is a link to the TE node
address draft:

http://www.ietf.org/internet-drafts/draft-ietf-ospf-te-node-addr-02.txt

Thanks,
Acee

>
>  The text needs to cover all of these questions.
> Cheers,
> Adrian
>