Re: Clarification in NSSA

"Pat Murphy - (650)329-4044" <pmurphy@omega7.wr.usgs.gov> Tue, 01 July 2003 18:20 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 OAA09879 for <ospf-archive@LISTS.IETF.ORG>; Tue, 1 Jul 2003 14:20:37 -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 <5.00A3FB32@cherry.ease.lsoft.com>; Tue, 1 Jul 2003 14:20:16 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 47251620 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 1 Jul 2003 14:20:14 -0400
Received: from 130.118.4.3 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 1 Jul 2003 14:20:14 -0400
Received: from omega7.wr.usgs.gov by omega7.wr.usgs.gov (PMDF V6.0-24 #41392) id <01KXQQSCGORQ8X32YF@omega7.wr.usgs.gov> for OSPF@PEACH.EASE.LSOFT.COM; Tue, 01 Jul 2003 11:20:08 -0700 (PDT)
X-VMS-To: OSPF@PEACH.EASE.LSOFT.COM
X-VMS-Cc: PMURPHY
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Message-ID: <01KXQQSCGPQ08X32YF@omega7.wr.usgs.gov>
Date: Tue, 01 Jul 2003 11:20:08 -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: Clarification in NSSA
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

Thank you Vivek for quoting the magic words. Sorry to be so
tardy, I have been out of the office.

>"If the Type-7 LSA is not contained in any explicitly
>configured Type-7 address range and the calculating router has
>the highest router ID amongst NSSA translators that have
>originated a functionally equivalent Type-5 LSA (i.e. same
>destination, cost and non-zero forwarding address) and that
>are reachable over area 0 and the NSSA, then a Type-5 LSA
>should be generated"

This change was a late entry in RFC 3101 that was added shortly
before its last call. It was not in RFC 1587. For any folk who
are/have upgraded RFC 1587 implementations make sure this is
added. RFC 3101 is much more than new feature. It has closed a
number of bugs.

Pat