Re: OSPFv3 Traffic Engineering TLVs and TE Node Address TLV

Rahul Aggarwal <rahul@JUNIPER.NET> Fri, 13 February 2004 23:12 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 SAA13892 for <ospf-archive@LISTS.IETF.ORG>; Fri, 13 Feb 2004 18:12:44 -0500 (EST)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <21.00CDE3D3@cherry.ease.lsoft.com>; Fri, 13 Feb 2004 18:12:45 -0500
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 2134491 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 13 Feb 2004 18:12:44 -0500
Received: from 207.17.137.64 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 13 Feb 2004 18:12:44 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id i1DNChBm046659 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 13 Feb 2004 15:12:43 -0800 (PST) (envelope-from rahul@juniper.net)
Received: from sapphire.juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i1DNCho05700 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 13 Feb 2004 15:12:43 -0800 (PST) (envelope-from rahul@juniper.net)
Received: from localhost (rahul@localhost) by sapphire.juniper.net (8.11.6/8.11.3) with ESMTP id i1DNChA74334 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 13 Feb 2004 15:12:43 -0800 (PST) (envelope-from rahul@juniper.net)
X-Authentication-Warning: sapphire.juniper.net: rahul owned process doing -bs
References: <39469E08BD83D411A3D900204840EC55FB71E7@vie-msgusr-01.dc.fore.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Message-ID: <20040213150711.V61537@sapphire.juniper.net>
Date: Fri, 13 Feb 2004 15:12:43 -0800
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Rahul Aggarwal <rahul@JUNIPER.NET>
Subject: Re: OSPFv3 Traffic Engineering TLVs and TE Node Address TLV
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <39469E08BD83D411A3D900204840EC55FB71E7@vie-msgusr-01.dc.fore.com>
Precedence: list

Hi Venkata,

On Fri, 13 Feb 2004, Naidu, Venkata wrote:

> -> The Node Address TLV is intended to carry local addresses,
> -> that are not
> -> otherwise advertised in OSPF TE (router ID, TE links, Router IPv6
> -> Address). This can be clarified further in
> -> draft-raggarwa-ospf-te-node-addr-00.txt. Will that suffice ?
>
>   If possible, can you please look at my previous question ?
>
> http://peach.ease.lsoft.com/scripts/wa.exe?A2=ind0311&L=ospf&T=0&F=&S=&P=732
>

Sorry, I missed your previous email. The question was:

>In other words, why is Router LSA stub info not *sufficient*
> to learn all local addresses (if we enable active/passive
> OSPF routing over all those interfaces) ?

It doesn't cover all the cases, in particular a P2P interface. For a P2P
interface, as per RFC 2328:
    - If subnetted P2P: Link ID: subnet, Link Data: mask, Cost: Intf Cost

This is not sufficient to add the local intf address of the advertising
router, needed by TED.

    - If not subnetted P2P and nbr, LID: nbr address, LData: 0xffffffff,
      Cost: Intf Cost

Same problem as above. Thanks for the comment. We can clarify this in the
draft.

rahul

> Venkata.
>