[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-ospf
Subject:    Re: FW: NSSA RFC for OSPFv3
From:       Acee Lindem <acee () REDBACK ! COM>
Date:       2004-05-20 21:26:27
Message-ID: 01c401c43eb1$1d594660$0302a8c0 () aceeinspiron
[Download RAW message or body]

Hi Harold,

 Issues: #1. Yes - this bit should be defined since the router
             LSA is fully defined. The position should remain
             the same as defined in RFC 3101.
         #2. This would be clearer with an explicit statement.
             However, it really isn't ambiguous without it since
             the relationship between AS external LSAs and NSSA
             LSA remains the same.
         #3. Same as #2. It would be better with the statement but
             is unambiguous without it.

It looks like maybe I should gather all the OSPFv3 errata and
come out with a respin of RFC 2740.

Thanks,
Acee


----- Original Message ----- 
From: "Harold Rabbie" <harold@ipinfusion.com>
To: <OSPF@PEACH.EASE.LSOFT.COM>; <acee@redback.com>
Cc: "Toshiaki Takada" <toshiaki@ipinfusion.com>; "Kunihiro Ishiguro" \
                <kunihiro@ipinfusion.com>; <zhangjp@huawei.com>
Sent: Thursday, May 20, 2004 4:56 PM
Subject: FW: FW: NSSA RFC for OSPFv3


> Hello Acee,
> 
> We were very interested to see your response (below) to Huawei regarding
> implementing NSSA for OSPFv3.
> IP Infusion would like to implement this option, but we're running into a
> couple of undefined issues.
> Perhaps you could let us know your thoughts on these topics:
> 
> Issue #1:
> ========
> 
> RFC 3101 defines the "Nt" bit in the Router-LSA.  But RFC 2740 does not
> describe that bit.
> 
> RFC 3101 Router LSA
> 0                   1                   2                   3
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > 0  Nt|W|V|E|B|        0      |            # links            |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> RFC 2740 Router LSA
> 0                   1                   2                   3
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > 0  |W|V|E|B|            Options                            |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> In order to implement NSSA for OSPFv3, this bit needs to be defined
> somewhere.
> It could presumably be in the analogous location next to the W bit.
> 
> Issue #2:
> ========
> 
> Although LSA type ID 7 is reserved for NSSA, RFC 2740 does not define the
> format of a type 7 LSA.
> The RFC could be updated with a statement, for example:
> 
> A.4.?  NSSA-LSAs
> 
> NSSA-LSAs have LS type equal to 0x2007.  These LSAs are originated
> by NSSA internal router or NSSA-ABR, and describe destinations
> external to AS but only through NSSA. The NSSA-LSA format is exactly
> the same as AS-external-LSAs.
> 
> Issue #3:
> ========
> 
> RFC 2740 section 3.8.4 describes how to calculate AS external routes as
> follows:
> 
> The IPv6 AS external route calculation proceeds along the same lines
> as the IPv4 calculation in Section 16.4 of [Ref1], with the following
> exceptions:
> 
> [Ref1] is Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998
> which doesn't contain any reference to NSSA.
> 
> This section could be updated to refer to RFC 3101 as well.
> 
> Summary
> =======
> 
> 1) Nt bit in Router-LSA is not defined.
> 2) The format for NSSA-LSA is not defined.
> 3) Calculating NSSA external route is not defined.
> 
> Many thanks,
> 
> Harold Rabbie
> Director of Applications Engineering
> IP Infusion Inc.
> 111 W. St. John St #910, San Jose, CA 95113
> ofc (408)794-1526 cell (408)506-4224 fax (408)278-0521
> Web http://www.ipinfusion.com
> E-mail harold@ipinfusion.com
> 
> 
> > 
> > -----Original Message-----
> > From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of Acee
> > Lindem
> > Sent: Wednesday, May 19, 2004 11:14 AM
> > To: OSPF@PEACH.EASE.LSOFT.COM
> > Subject: Re: NSSA RFC
> > 
> > 
> > Hi 张 江平 ,
> > 
> > I don't think we need a new NSSA for OSPFv3 other than RFC 3101.
> > 
> > One obvious omission from RFC 2740 is that a forwarding address for
> > an NSSA or AS external LSA must not be a link local address. We'll add
> > this if we ever re-spin RFC 2740.
> > 
> > Thanks,
> > Acee
> > ----- Original Message -----
> > From: 张 江平
> > To: OSPF@PEACH.EASE.LSOFT.COM
> > Sent: Tuesday, May 18, 2004 8:22 AM
> > Subject: NSSA RFC
> > 
> > 
> > Hi all,
> > 
> > Does OSPFv3 support NSSA now, RFC2740 has defined the type for NSSA, do
> we
> > need another NSSA rfc the same as RFC3101 for OSPFv3?
> > 
> > thanks!
> 
> Hi harold,
> 
> Ipinfusion don't support NSSA feature, the reason is that no NSSA Draft/RFC
> for OSPFv3,
> I don't think we need another NSSA RFC for OSPFv3, and I confirm with Mr.
> Acee,
> the chairman of IETF OSPF work group. Pls find attached mail for Mr. Acee's
> answer.
> 
> Regards,
> Zhang Jiangping
> Huawei Technologies R&D Beijing Branch
> Phone: +86-10-82882249
> Mobile: +86-13301132983
> 


[prev in list] [next in list] [prev in thread] [next in thread]