Ondrej - Reading 10.9 of RFC2328 leads me to two interpretations of it:
(A) Your interpretation, as stated below. (B) When the originating router receives a LSUPD, it should truncate it's list and immediately send a new LSREQ packet for the remaining items. Having said that, 0.99.22 of Quagga is just over 2 years old now and from a quick glance at the logs I see ~70 commits into OSPF alone in that time frame. Is there an easy way to upgrade to a newer version of Quagga? I'll spend some time this evening looking at the OSPF code in Quagga to get a real understanding of what it does when it receives a LSREQ packet. thanks! donald On Thu, Jun 18, 2015 at 6:14 AM, Ondrej Zajicek <[email protected]> wrote: > Hello > > We noticed an incompatibility between Quagga and BIRD in > OSPF loading phase: > > In short: > > 1) BIRD sends LSREQ packet with ~60 LSR. > > 2) Quagga answers with one LSUPD packet with ~20 LSA. > > 3) BIRD waits for remaining LSUPD packets (to cover all requested LSAs) > before sending new LSREQ. > > 4) Usually no more LSUPD is sent by Quagga, therefore BIRD timeouts > (RxmtInterval) before sending next LSREQ packet. This leads to > significantly longer loading phase. > > > We noticed this problem with Quagga 0.99.22 and BIRD 1.5.0 > > My interpretation of RFC 2328 10.9 is that when LSREQ is received, it > should be immediately answered by multiple LSUPD packets to cover all > LSRs from LSREQ. And when LSREQ is sent, it should be completely answered > before sending the next one. But i would say that this aspect of RFC 2328 > is especially vague and i see other alternative interpretations. > What is the opinion of Quagga developers w.r.t. this issue? > > -- > Elen sila lumenn' omentielvo > > Ondrej 'Santiago' Zajicek (email: [email protected]) > OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) > "To err is human -- to blame it on a computer is even more so." > > _______________________________________________ > Quagga-dev mailing list > [email protected] > https://lists.quagga.net/mailman/listinfo/quagga-dev >
_______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
