Re: draft-ietf-ospf-ospfv3-mib-09

Vishwas Manral <Vishwas@SINETT.COM> Fri, 08 July 2005 13:07 UTC

Received: from ([] by with esmtp (Exim 4.32) id 1DqsZT-0001GD-Hd for; Fri, 08 Jul 2005 09:07:15 -0400
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id JAA29820 for <ospf-archive@LISTS.IETF.ORG>; Fri, 8 Jul 2005 09:07:10 -0400 (EDT)
Received: from ( by (LSMTP for Digital Unix v1.1b) with SMTP id <>; Fri, 8 Jul 2005 9:07:08 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 78376602 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 8 Jul 2005 09:07:07 -0400
Received: from by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Fri, 8 Jul 2005 09:07:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C583BD.F0D5616A"
Thread-Topic: draft-ietf-ospf-ospfv3-mib-09
Thread-Index: AcWC0IxxM5suhTGVTqy5QJCRTKSf3QA7UDyw
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B28A2ACA@sinett-sbs.SiNett.LAN>
Date: Fri, 08 Jul 2005 06:07:24 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Vishwas Manral <Vishwas@SINETT.COM>
Subject: Re: draft-ietf-ospf-ospfv3-mib-09
Precedence: list

Hi Acee,


Should we list the below as an exception too in the OSPFv3 update draft?





From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Vivek
Sent: Thursday, July 07, 2005 2:19 PM
Subject: Re: draft-ietf-ospf-ospfv3-mib-09


Hi Vishwas,
Reason why i mentioned "ospfRFC1583Compatibility"

3.8.5  Calculating AS external routes
The IPv6 AS external route calculation proceeds along the same lines
as the IPv4 calculation in Section 16.4 of [OSPFV2] and Section 2.5
of [NSSA], with the following exceptions:

<vivek> It is not listed in exceptions and RFC2328 Section 16.4 has
the description. 


On Wed, 06 Jul 2005 Vishwas Manral wrote :
>Hi Vivek,
>Is there a reason we need to support compatibility with an older
version of OSPFv2 (RFC1583) in OSPFv3?
>Regarding a previous mail of yours
>"ospfv3AreaSummary: The variable should also effect NSSA areas.
Description should be updated"
>We will update the description to also state NSSA (to be consistent
with OSPFv2 MIB).
> From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of
Vivek Dubey
>Sent: Wednesday, July 06, 2005 3:53 PM
>Subject: draft-ietf-ospf-ospfv3-mib-09
>No configuration support is provided for "ospfRFC1583Compatibility " in
>On Wed, 06 Jul 2005 Dilip Kumar wrote :
> >Hi,
> >    I would like to know if Router Address TLV's value field MUST
> >contain a syntatically correct IP Address. I mean, is it OK if an
> >router advertises Opaque LSA (TE) with an syntatically incorrect IP
> >address (ex. etc.) in Router Address TLV ?
> >
> >Thanks,
> >Dilip