Re: draft-ietf-ospf-ospfv3-mib-09
Acee Lindem <acee@CISCO.COM> Sat, 09 July 2005 16:34 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DrII7-0004Iq-48 for ospf-archive@megatron.ietf.org; Sat, 09 Jul 2005 12:34:59 -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 MAA10556 for <ospf-archive@LISTS.IETF.ORG>; Sat, 9 Jul 2005 12:34:55 -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 <0.010A0329@cherry.ease.lsoft.com>; Sat, 9 Jul 2005 12:34:52 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 78495579 for OSPF@PEACH.EASE.LSOFT.COM; Sat, 9 Jul 2005 12:34:50 -0400
Received: from 64.102.122.148 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Sat, 9 Jul 2005 12:34:50 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 09 Jul 2005 09:34:52 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.93,276,1115017200"; d="scan'208"; a="1126657:sNHT23751924"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j69GYok6010303 for <OSPF@PEACH.EASE.LSOFT.COM>; Sat, 9 Jul 2005 12:34:50 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 9 Jul 2005 12:34:51 -0400
Received: from [10.82.241.216] ([10.82.241.216]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 9 Jul 2005 12:34:50 -0400
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <BB6D74C75CC76A419B6D6FA7C38317B28A2ACA@sinett-sbs.SiNett.LAN>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jul 2005 16:34:50.0155 (UTC) FILETIME=[205017B0:01C584A4]
Message-ID: <42CFFCA9.5040500@cisco.com>
Date: Sat, 09 Jul 2005 12:34:49 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@CISCO.COM>
Subject: Re: draft-ietf-ospf-ospfv3-mib-09
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <BB6D74C75CC76A419B6D6FA7C38317B28A2ACA@sinett-sbs.SiNett.LAN>
Precedence: list
Content-Transfer-Encoding: 7bit
Vishwas Manral wrote: >Hi Acee, > > > >Should we list the below as an exception too in the OSPFv3 update draft? > > Hi Vishwas, Yes - I will add it in the next revision. Thanks, Acee > > >Thanks, > >Vishwas > >________________________________ > >From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Vivek >Dubey >Sent: Thursday, July 07, 2005 2:19 PM >To: OSPF@PEACH.EASE.LSOFT.COM >Subject: Re: draft-ietf-ospf-ospfv3-mib-09 > > > >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 >>> >>> > > > > <http://clients.rediff.com/signature/track_sig.asp> > > > >
- 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