Re: Zero as ospfIfRetransInterval
Acee Lindem <acee@REDBACK.COM> Tue, 24 June 2003 12:51 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 IAA14051 for <ospf-archive@LISTS.IETF.ORG>; Tue, 24 Jun 2003 08:51:47 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <7.00A2DD88@cherry.ease.lsoft.com>; Tue, 24 Jun 2003 8:48:36 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 46453595 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 24 Jun 2003 08:48:35 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 24 Jun 2003 08:48:35 -0400
Received: from redback.com (login004.redback.com [155.53.12.57]) by prattle.redback.com (Postfix) with ESMTP id F1C647D6CA7; Tue, 24 Jun 2003 05:48:33 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <6204FDDE129D364D8040A98BCCB290EF05DD8EF8@zbl6c004.corpeast.baynetworks.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3EF847F2.1030907@redback.com>
Date: Tue, 24 Jun 2003 08:45:38 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Zero as ospfIfRetransInterval
Comments: To: Daniel Joyal <djoyal@nortelnetworks.com>
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
Hi Dan, Daniel Joyal wrote: > You're not allowed to change the syntax unless > it's equivalent to the old syntax. Even if the old syntax doesn't match the protocol specification? > So in this > case, we would need to deprecate/obsolete. Then I don't think it is worth defining new MIB variables given that ospfIfTransitDelay, ospfIfRetransInterval, ospfVirtIfTransitDelay, and ospfVirtIfRetransInterval have served us thus far. Other opinions are welcome. Thanks, Acee > > -Dan > > > -----Original Message----- > > From: Acee Lindem [mailto:acee@redback.com] > > Sent: Monday, June 23, 2003 11:35 PM > > To: Mailing List; Joyal, Daniel [BL60:NP30:EXCH] > > Subject: Re: Zero as ospfIfRetransInterval > > > > > > > > > > Igor Miroshnik wrote: > > > All, > > > > > > Can anybody clarify the physical sense of assigning > > > ospfIfRetransInterval to zero? RFC1850 allows such an assignment. > > > > I believe UpToMaxAge should range from 1..3600 rather than 0..3600. > > > > Dan - can we change this in the MIB update without > > deprecating variables? > > > > > > > > Thanks > > > > > > > > > -- > > Acee > > > > > -- Acee
- Zero as ospfIfRetransInterval Igor Miroshnik
- Re: Zero as ospfIfRetransInterval Acee Lindem
- Re: Zero as ospfIfRetransInterval Daniel Joyal
- Re: Zero as ospfIfRetransInterval Acee Lindem
- Re: Zero as ospfIfRetransInterval Manral, Vishwas
- Re: Zero as ospfIfRetransInterval Acee Lindem
- Re: Zero as ospfIfRetransInterval Jeff Parker
- Re: Zero as ospfIfRetransInterval Greg Mirsky
- Re: Zero as ospfIfRetransInterval Eric Gray
- Re: Zero as ospfIfRetransInterval Acee Lindem
- Re: Zero as ospfIfRetransInterval Manral, Vishwas
- Re: Zero as ospfIfRetransInterval Acee Lindem