Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
Re: Opaque LSA Timers...
From: Vivek Dubey (vivek_ospfREDIFFMAIL.COM)
Date: Sat Apr 19 2003 - 02:45:26 CDT
Your reasons for not supporting such variations
are agreeable but:
"If Ospf is providing a service to application (by
mean of Opaque LSA), there is every reason for
an application to except some priority service
in case of requirements."
Because flooding of application specific information
shouldn't be entirely retricted by base protocol
Possibly there is scope to explore ways to handle
such requirments in a generalized way.
On Fri, 18 Apr 2003 Acee Lindem wrote :
>>i excuse me for this and previous observation, but
>>i considered the administrative group information very
>>because i think they can come from network administrator or
>>any administrative tool and perhaps the administrator doesn' t
>>to wait MinLSInterval seconds to send his update;
>>so i thought was reasonable to do a separate timer for this
>>particular and important opaque field. Do you agree?
>I don't agree for (at least) the following reasons:
> 1. This is just one variation of the "re-originate the LSA
> requirement. We can't afford to have a separate solution
> each variation.
> 2. Multiple timers LSA Interval timers (which I assume you
> to advertise if any interval is satisfied) would add
> complexity and overhead.
> 3. While we have Not-So-Stubby Areas I don't think we want
> Not-So-Opaque LSAs. If the contents of the LSAs are truly
> opaque they should not have ramifications on the base
> flooding algorithm.
>>I read there was proposals in the past to reduce or ignore
>>MinLSInterval, but i agree with the important presence of
>>i only think to a separate management.
>>Was this proposals (or drafts ) specific to my consideration and
>>did they refer
>>to the only Opaque administrative field?
>>Thanks in advance for your answers and kindness.
>>Coritel - Rome