Re: OSPFv3 Point-to-Point interface
Acee Lindem <acee@REDBACK.COM> Tue, 01 July 2003 19:53 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 PAA14477 for <ospf-archive@LISTS.IETF.ORG>; Tue, 1 Jul 2003 15:53:33 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <2.00A401E3@cherry.ease.lsoft.com>; Tue, 1 Jul 2003 15:53:33 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 47267070 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 1 Jul 2003 15:53:32 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 1 Jul 2003 15:53:32 -0400
Received: from redback.com (login003.redback.com [155.53.12.55]) by prattle.redback.com (Postfix) with ESMTP id B65B939F4E1 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 1 Jul 2003 12:53:30 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <20030624160304.6E7A.SASAKI@soft.net.fujitsu.co.jp>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3F01E68F.6050000@redback.com>
Date: Tue, 01 Jul 2003 15:52:47 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: OSPFv3 Point-to-Point interface
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
Taisuke Sasaki wrote: > I have a question about how to advertise its own > point-to-point interface address in its Intra-Area-Prefix-LSAs. > > Suppose that a Router A has a point-to-point link > and IPv6 address 3ffe:1::1/64 is assigned. > > point-to-point > +---+ 3ffe:1::/64 +---+ > | A +---------------+ B | > +---+ ::1 ::2 +---+ > > I saw some OSPFv3 implementations that Router A advertised > its p2p interface address in an Intra-Area-Prefix-LSA as follows: > > PrefixLength = 128 > PrefixOptions = LA-bit > Metric = 0 > Address Prefix = 3ffe:1::1 > > It's no problem from the viewpoint of Routing, > but is this implementation fully compliant with rfc2740 3.4.3.7? > > My opinion is the next: > If IPv6 address 3ffe:1::1/128 is assigned to Router A's p2p > interface, it is OK. > But in this case, IPv6 prefix(/64) is assigned to its p2p > interface, so Router A should advertise its interface prefix > as follows: > > PrefixLength = 64 > PrefixOptions = 0 > Metric = 1 ;interface output cost > Address Prefix = 3ffe:1:: Hi Taisuke Sasaki, I would agree with you the prefix should be advertised with the assigned length and cost. Actually, there is very ambiguous statement in RFC 2740: If the interface type is Point-to-MultiPoint, or the interface is in state Loopback, or the interface connects to a point-to-point link which has not been assigned a prefix, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ then the site-local and global scope IPv6 addresses associated ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ with the interface (if any) are copied into the intra-area- prefix-LSA, setting the LA-bit in the PrefixOptions field, and setting the PrefixLength to 128 and the Metric to 0. It seems to be a contraction to reference site-local and global scope IPv6 addresses associated with a P2P link that doesn't have any prefixes assigned. Any other interpretations? Thanks, Acee > > regards. > > --- > taisuke sasaki > -- Acee
- OSPFv3 Point-to-Point interface Taisuke Sasaki
- Re: OSPFv3 Point-to-Point interface Acee Lindem