Re: OSPFv3 Traffic Engineering TLVs and TE Node Address TLV
Rahul Aggarwal <rahul@JUNIPER.NET> Fri, 13 February 2004 22:33 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 RAA11796 for <ospf-archive@LISTS.IETF.ORG>; Fri, 13 Feb 2004 17:33:38 -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 <1.00CDE34F@cherry.ease.lsoft.com>; Fri, 13 Feb 2004 17:33:39 -0500
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 2131686 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 13 Feb 2004 17:33:37 -0500
Received: from 207.17.137.64 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 13 Feb 2004 17:33:37 -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 i1DMXZBm046561 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 13 Feb 2004 14:33:36 -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 i1DMXZo01054 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 13 Feb 2004 14:33:35 -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 i1DMXZq69441 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 13 Feb 2004 14:33:35 -0800 (PST) (envelope-from rahul@juniper.net)
X-Authentication-Warning: sapphire.juniper.net: rahul owned process doing -bs
References: <0b5b01c3f27e$c59233c0$0302a8c0@aceeinspiron>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Message-ID: <20040213142454.Q61537@sapphire.juniper.net>
Date: Fri, 13 Feb 2004 14:33:35 -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: <0b5b01c3f27e$c59233c0$0302a8c0@aceeinspiron>
Precedence: list
Hi Acee, On Fri, 13 Feb 2004, Acee Lindem wrote: > We have draft-ietf-ospf-ospfv3-traffic-01.txt describing > OSPFv3 traffic engineering TLVs. A new TLV, Router Address TLV, > is proposed to carry a single routable IPv6 address. > > Additionally, at the last IETF, a new draft was presented, > draft-raggarwa-ospf-te-node-addr-00.txt, which proposes the > advertisement of multiple routable addresses. There seemed to > be agreement that the draft was a logical extension of > RFC 3630 and there was no opposition. > Thanks for bringing this up. I have been meaning to poll the list for moving this draft forward. > It seems that if we accept the node address draft we should > modify the OSPFv3 traffic engineering draft to add the > requirement for a node address TLV specifying at least one > routable IPv6 address. > 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 ? Thanks, rahul > > > ------ > Acee >
- OSPFv3 Traffic Engineering TLVs and TE Node Addre… Acee Lindem
- Re: OSPFv3 Traffic Engineering TLVs and TE Node A… Kunihiro Ishiguro
- Re: OSPFv3 Traffic Engineering TLVs and TE Node A… Rahul Aggarwal
- Re: OSPFv3 Traffic Engineering TLVs and TE Node A… Naidu, Venkata
- Re: OSPFv3 Traffic Engineering TLVs and TE Node A… Rahul Aggarwal