Re: Working Group Last Call for draft-ietf-ospf-mib-update-06.txt

Erblichs <erblichs@EARTHLINK.NET> Wed, 23 April 2003 20:52 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 QAA06590 for <ospf-archive@LISTS.IETF.ORG>; Wed, 23 Apr 2003 16:52:00 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <9.0098EC97@cherry.ease.lsoft.com>; Wed, 23 Apr 2003 16:54:44 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 670115 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 23 Apr 2003 16:54:44 -0400
Received: from 207.217.120.54 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 23 Apr 2003 16:54:43 -0400
Received: from user-38ldsni.dialup.mindspring.com ([209.86.242.242] helo=earthlink.net) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 198RGL-00038w-00 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 23 Apr 2003 13:54:42 -0700
X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <3EA6A934.1050904@redback.com> <3EA6DBA8.8000509@redback.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <3EA6FD97.F72A727B@earthlink.net>
Date: Wed, 23 Apr 2003 13:54:47 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Erblichs <erblichs@EARTHLINK.NET>
Subject: Re: Working Group Last Call for draft-ietf-ospf-mib-update-06.txt
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Acee,

        After a quick look here are a few possible changes/additions for you
        and your group...

        1) No "Wait timer" with the other timers in 1.6 Default configuration.

        1b) Don't see a ospfIfWaitinterval object..

        Yes, the value is RouterDeadInterval by default and it applies only to
BMA.

        2) Associated with ospfExternLsaChksumSum
           Why don't you support a query of the number of ChkSum failures
           within the LSDB since bootup?

        3) Query of Overflow state. Current and past. Past tells you
           whether you have ever entered the OverflowState due to
           exceeding the ospfExtLsdbLimit..

        I am only seiing OverlowInterval...

        4) Query on CongestionState. Current and past. This I know is a
stretch!

        5) Ability to Reset counters ((ospRxNewLsas, ospfSpfRuns, et)
ATOMICLY..
           These would be reset to 0. Yes, in effect it does change the state
to
           READ-WRITE from READ-ONLY.

        Mitchell Erblich
        Sr Software Engineer
        ==========================


Acee Lindem wrote:
>
> We've decided do another revision of this draft prior to WG
> last call. If you forward comments quickly (I don't have an
> exact date), they can be incorporated into the next revision.
>
> Thanks,
> Acee
>
> Acee Lindem wrote:
> > This is the start of a Working Group last call for
> > draft-ietf-ospf-mib-update-06.txt, OSPF Version 2 Management
> > Information Base. All comments must be received by Wednesday,
> > May 7th, 2003.
> >
> > This document reached the AD review phase once before but
> > we decided to add MIB support for recent OSPF extensions.
> >
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ospf-mib-update-06.txt
>
> --
> Acee