[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Notify Invalid Spi/Cookie (was RE: Phase 1 KB lifetime)
>>>>> "Henry" == Henry Spencer <henry@spsystems.net> writes:
Henry> On Thu, 20 Jan 2000, Sankar Ramamoorthi wrote:
>> With the present rule, one end of the communication could endup
>> sending packets into a blackhole and there is no way to notice it
>> till the sender's SA expires...
Henry> Given properly-functioning ends, how could such a situation
Henry> arise? How would one end forget an SA that the other end was
Henry> still using? ...
If you want the protocol to be self-stabilizing, you should *not*
approach the question that way! "Self-stabilizing" means: the
protocol recovers in a reasonable amount of time from faults,
including from getting into states it wasn't supposed to have gotten
into. Robust protocols have this property; protocols that don't are
fragile. (For example, you may find yourself having to reboot an
entire network to recover from an implementation bug.)
Than again "reasonable amount of time" may be minutes or hours in the
case of states that can be reached only through faults.
paul
References: