Re: NSSA forwarding address

"Pat Murphy - (650)329-4044" <pmurphy@omega7.wr.usgs.gov> Fri, 30 May 2003 15:31 UTC

MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Message-ID: <01KWHVJOYL4Y8X29XX@omega7.wr.usgs.gov>
Date: Fri, 30 May 2003 08:31:04 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: "Pat Murphy - (650)329-4044" <pmurphy@omega7.wr.usgs.gov>
Subject: Re: NSSA forwarding address
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

NSSA RFC3101, states

   Normally the next hop address of an installed AS external route
   learned by an NSSA ASBR from an adjacent AS points at one of the
   adjacent AS's gateway routers. If this address belongs to a network
   connected to the NSSA ASBR via one of its NSSAs' active interfaces,
   then the NSSA ASBR copies this next hop address into the forwarding
   address field of the route's Type-7 LSA that is originated into this
   NSSA, as is currently done with Type-5 LSAs....

   ...For an NSSA with no such network the forwarding address
   field may only be filled with an address from one of the its active
   interfaces or 0.0.0.0.

Note in both cases the address must be chosen from one of the NSSA's
networks. This always applies. If no such address is available, 0.0.0.0
must be used and the P-bit must be clear. When forced to chose an
address from one of "the NSSA's active interfaces", the preference is

   1) Loop back interface
   2) Stub interface
   3) Any remaining interface

In all cases the network containing the non-zero forwarding address of a
Type 7 LSA must be part of the NSSA.

By the way it looks like the IETF OSPF WG page needs its Mailing Lists
updated.

Pat

NSSA forwarding address somnath mani
Re: NSSA forwarding address Vivek Dubey
Re: NSSA forwarding address Pat Murphy - (650)329-4044