Intra-Area-Prefix LSA's on P2P interface
Nitin Kakkar <nitink@HUAWEI.COM> Thu, 20 May 2004 11:02 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 HAA11254 for <ospf-archive@LISTS.IETF.ORG>; Thu, 20 May 2004 07:02:49 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <2.00DB8221@cherry.ease.lsoft.com>; Thu, 20 May 2004 7:02:49 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 17528978 for OSPF@PEACH.EASE.LSOFT.COM; Thu, 20 May 2004 07:02:48 -0400
Received: from 61.144.161.41 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Thu, 20 May 2004 07:02:47 -0400
Received: from nitin (huawei.com [172.17.1.62]) by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12 2002)) with ESMTPA id <0HY000EGFEMWDE@mta0.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Thu, 20 May 2004 19:01:45 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
Content-type: multipart/alternative; boundary="Boundary_(ID_48sHILyIeGUUDDD8K7XzgA)"
X-Priority: 3
X-MSMail-priority: Normal
X-imss-version: 2.5
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:19 M:1 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:3 R:3 (0.0000 0.0000)
Message-ID: <001401c43ed8$fb9dd720$8698fea9@HUAWEI.COM>
Date: Thu, 20 May 2004 19:11:52 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Nitin Kakkar <nitink@HUAWEI.COM>
Subject: Intra-Area-Prefix LSA's on P2P interface
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Hello,
In RFC 2740 Page 33, Paragraph 3
"Router RTX examines its list of interfaces to the area. If the interface is in state Down, its prefixes are not included. If the
interface has been reported in RTX's router-LSA as a Type 2 link description (link to transit network), its prefixes are not included (they will be included in the intra-area-prefix-LSA for the link instead). 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. Otherwise,the list of site-local and global prefixes configured in RTX for the link are copied into the intra-area-prefix-LSA by specifying the PrefixLength, PrefixOptions, and Address Prefix fields. The Metric field for each of these prefixes is set to the interface's
output cost".
In the above paragraph please refer to the lines in bold, they seem to indicate that, if a P2P interface is NOT assigned a global ipv6 address then its corresponding inter-area-prefix LSA should send the site local address for that interface.
My questions are
1) Where & how to use this site local address ?
2) Is this condition for IPV6 unnumbered interfaces ?
Regards
Nitin
- Intra-Area-Prefix LSA's on P2P interface Nitin Kakkar
- Re: Intra-Area-Prefix LSA's on P2P interface Acee Lindem