Behavior during OSPF premature aging

[Ondrej Zajicek]

On Tue, Jun 24, 2014 at 08:46:20AM +0100, Lennard Klein wrote:
> Hi,
> 
> When premature aging an LSA, bird seems to increase the LSA sequence number to its maximum (proto/ospf/lsupd.c line 616, in 1.4.3).
> 
> While I think the main fault lies with the other vendor, my question
> at this time is: what is the reasoning behind updating the sequence
> number to its maximum, even though the RFC says to leave it as-is?

Hi

This is done mainly to compensate other problems/quirks/hacks in BIRD
OSPF implementation. One reason is that if you flush LSA using MaxSeqNo,
you could forget old LSA sequence number, and when you originate a new
one later, you could safely start from InitSeqNo.

Currently i am finishing OSPF revision that removes most of these BIRD
quirks and problems related to LSA flood and makes BIRD much better in
RFC compliance.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20140625/3f91e787/attachment-0001.asc>