OSPFv3 Point-to-Point interface
Taisuke Sasaki <sasaki@SOFT.NET.FUJITSU.CO.JP> Tue, 24 June 2003 07:04 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 DAA05770 for <ospf-archive@LISTS.IETF.ORG>; Tue, 24 Jun 2003 03:04:56 -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 <19.00A2D47C@cherry.ease.lsoft.com>; Tue, 24 Jun 2003 3:03:55 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 46417552 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 24 Jun 2003 03:03:54 -0400
Received: from 192.51.44.37 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 24 Jun 2003 03:03:53 -0400
Received: from m6.gw.fujitsu.co.jp ([10.0.50.76]) by fgwmail7.fujitsu.co.jp (8.12.9/Fujitsu Gateway) id h5O73iM2022055 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 24 Jun 2003 16:03:44 +0900 (envelope-from sasaki@soft.net.fujitsu.co.jp)
Received: from s4.gw.fujitsu.co.jp by m6.gw.fujitsu.co.jp (8.12.9/Fujitsu Domain Master) id h5O73hh1032276 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 24 Jun 2003 16:03:43 +0900 (envelope-from sasaki@soft.net.fujitsu.co.jp)
Received: from incapgw1.fujitsu.co.jp (incapgw.fujitsu.co.jp [10.75.179.5]) by s4.gw.fujitsu.co.jp (8.12.9) id h5O73hOd008119 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 24 Jun 2003 16:03:43 +0900 (envelope-from sasaki@soft.net.fujitsu.co.jp)
Received: from [45.0.8.144] (mogw2.gw.fujitsu.co.jp [10.75.179.52]) by incapgw1.fujitsu.co.jp (8.11.6p2/3.7W-0305) id h5O73g113866; Tue, 24 Jun 2003 16:03:42 +0900 (JST)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.05.06
Message-ID: <20030624160304.6E7A.SASAKI@soft.net.fujitsu.co.jp>
Date: Tue, 24 Jun 2003 16:03:09 +0900
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Taisuke Sasaki <sasaki@SOFT.NET.FUJITSU.CO.JP>
Subject: OSPFv3 Point-to-Point interface
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
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::
regards.
---
taisuke sasaki
- OSPFv3 Point-to-Point interface Taisuke Sasaki
- Re: OSPFv3 Point-to-Point interface Acee Lindem