Re: draft-ietf-ospf-ospfv3-mib-09
Vivek Dubey <vivek_ospf@REDIFFMAIL.COM> Thu, 07 July 2005 08:47 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqS2v-0000HO-Lw for ospf-archive@megatron.ietf.org; Thu, 07 Jul 2005 04:47:51 -0400
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 EAA12914 for <ospf-archive@LISTS.IETF.ORG>; Thu, 7 Jul 2005 04:47:46 -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 <15.0109D5F0@cherry.ease.lsoft.com>; Thu, 7 Jul 2005 4:47:44 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 78194461 for OSPF@PEACH.EASE.LSOFT.COM; Thu, 7 Jul 2005 04:47:42 -0400
Received: from 203.199.83.148 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Thu, 7 Jul 2005 04:47:41 -0400
Received: (qmail 21677 invoked by uid 510); 7 Jul 2005 08:49:09 -0000
Received: from unknown (203.126.136.220) by rediffmail.com via HTTP; 07 jul 2005 08:49:08 -0000
MIME-Version: 1.0
Content-type: multipart/alternative; boundary="Next_1120726148---0-203.199.83.148-21667"
Message-ID: <20050707084909.21675.qmail@webmail26.rediffmail.com>
Date: Thu, 07 Jul 2005 08:49:09 -0000
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Vivek Dubey <vivek_ospf@REDIFFMAIL.COM>
Subject: Re: draft-ietf-ospf-ospfv3-mib-09
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Hi Vishwas, Reason why i mentioned "ospfRFC1583Compatibility" draft-ietf-ospf-ospfv3-update-04.txt 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. Thanks Vivek 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). > >Thanks, >Vishwas >________________________________________ > From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Vivek Dubey >Sent: Wednesday, July 06, 2005 3:53 PM >To: OSPF@PEACH.EASE.LSOFT.COM >Subject: draft-ietf-ospf-ospfv3-mib-09 > >No configuration support is provided for "ospfRFC1583Compatibility " in OSPFv3? > >Thanks >Vivek > > > > >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 OSPF > >router advertises Opaque LSA (TE) with an syntatically incorrect IP > >address (ex. 0.0.0.54 etc.) in Router Address TLV ? > > > >Thanks, > >Dilip
- draft-ietf-ospf-ospfv3-mib-09 Vivek Dubey
- Re: draft-ietf-ospf-ospfv3-mib-09 Vishwas Manral
- Re: draft-ietf-ospf-ospfv3-mib-09 Vivek Dubey
- Re: draft-ietf-ospf-ospfv3-mib-09 Vishwas Manral
- Re: draft-ietf-ospf-ospfv3-mib-09 Acee Lindem