Re: Zero as ospfIfRetransInterval

Acee Lindem <acee@REDBACK.COM> Wed, 25 June 2003 17:06 UTC

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
MIME-Version: 1.0
References: <E7E13AAF2F3ED41197C100508BD6A328DD4547@india_exch.corp.mot.com> <3EF84BA9.6090701@redback.com> <3EF9BA41.8370DC42@GraIyMage.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3EF9D5BC.4030805@redback.com>
Date: Wed, 25 Jun 2003 13:02:52 -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: ewgray@GraIyMage.com
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Eric Gray wrote:
> Acee,
>
>     Why would it be wrong to set a retransmit interval to zero?  Usually,
> setting a retransmit interval to zero would have the special meaning that
> retransmission does not occur (i.e. - the interval is infinite).  Is that not
> an intended meaning in this case?

Nope - not retransmitting would make the flooding unreliable and
would violate the base protocol specification (RFC 2328).

>
> Acee Lindem wrote:
>
>
>>Manral, Vishwas wrote:
>>
>>>Hi Acee,
>>>
>>>If we do not intend to define new variables, we may want to at least put the
>>>limitation of 0, in the object description in the MIB.
>>
>>Hi Vishwas,
>>
>>That sounds like a good idea since any implementation that allows
>>write access to set the variables to 0 is broken.
>>
>>Thanks,
>>Acee
>>
>>
>>>Thanks,
>>>Vishwas
>>>
>>>-----Original Message-----
>>>From: Acee Lindem [mailto:acee@REDBACK.COM]
>>>Sent: Tuesday, June 24, 2003 18:16
>>>To: OSPF@PEACH.EASE.LSOFT.COM
>>>Subject: Re: Zero as ospfIfRetransInterval
>>>
>>>
>>>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
>>>
>>
>>--
>>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