Re: draft-ishiguro-ospf-ospfv3-traffic-01.txt
Kunihiro Ishiguro <kunihiro@IPINFUSION.COM> Sat, 19 October 2002 23:22 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 TAA08866 for <ospf-archive@LISTS.IETF.ORG>; Sat, 19 Oct 2002 19:22:24 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <9.00781668@cherry.ease.lsoft.com>; Sat, 19 Oct 2002 19:24:37 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 317190 for OSPF@DISCUSS.MICROSOFT.COM; Sat, 19 Oct 2002 19:24:37 -0400
Received: from 64.139.11.202 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Sat, 19 Oct 2002 19:24:37 -0400
Received: from titanium.zebra.org (IDENT:kunihiro@titanium [127.0.0.1]) by titanium.zebra.org (8.9.3/8.9.3) with ESMTP id TAA05765; Sat, 19 Oct 2002 19:28:10 -0400
References: <E7E13AAF2F3ED41197C100508BD6A328791869@india_exch.hyderabad.mindspeed.com>
User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.3 Emacs/21.2.91 (powerpc-unknown-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset="US-ASCII"
Message-ID: <m2vg3y9fg5.wl@titanium.zebra.org>
Date: Sat, 19 Oct 2002 16:28:10 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Kunihiro Ishiguro <kunihiro@IPINFUSION.COM>
Subject: Re: draft-ishiguro-ospf-ospfv3-traffic-01.txt
Comments: cc: "Manral, Vishwas" <VishwasM@NETPLANE.COM>
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: <E7E13AAF2F3ED41197C100508BD6A328791869@india_exch.hyderabad.mindspeed.com>
Precedence: list
>1. Section 4. states that "Link State ID of Intra-Area-TE-LSA should be the >interface ID of the link". > >If we are assuming that we have only one top level TLV in each LSA(as in >Katz-yeung) we should state the exception in case of such an LSA. draft-katz-yeung-ospf-traffic-08.txt ==================================== 2.4.2. Link TLV The Link TLV describes a single link. It is constructed of a set of sub-TLVs. There are no ordering requirements for the sub-TLVs. Only one Link TLV shall be carried in each LSA, allowing for fine granularity changes in topology. I'm following 'Only one Link TLV shall be carried in each LSA'. Well, I prefer to say it must in OSPFv3 TE... >2. If we are using "neighbor-ID TLV" for point-to-point links also, we >should not need a Remote-Interface-IPv6 Address TLV, becuase we can easily >identify the other end of the link using the Interface ID. Neighbor-ID TLV is used for any type of link. We can map each TE information to each link using Neighbor-ID TLV. CSPF runs on the constraint topology information then generates ERO. Of course to generate ERO, IPv4/IPv6 address information is needed. Interface IPv6 Address information is for that. -- Kunihiro Ishiguro
- draft-ishiguro-ospf-ospfv3-traffic-01.txt Manral, Vishwas
- Re: draft-ishiguro-ospf-ospfv3-traffic-01.txt Kunihiro Ishiguro