> On Apr 23, 2025, at 8:25 AM, Roger David > <[email protected]> wrote: > > Dear Authors, > Greetings ! > I have a question on the highlighted text of the RFC (see snip below) where > it clarifies that Router should select the LSA with larger checksum as the > most recent one. > As I know, originator router is the one that initializes the checksum of the > LSA and this shall not be modified by any intermediate routers during > flooding. > So in an ideal situation, all routers in the network would receive this LSA > with the exact same checksum. > But lets say some intermediate router (with a non-pleasant intention) > modifies the checksum to a larger value before flooding it. It could cause > entire network to believe that this instance of the LSA is the most recent > one. > Could you pls. clarify or correct my incorrect understanding.
That's correct and since LSAs with an invalid checksum are rejected (section 13, RFC 2328), it implies the contents of the two instances are different. Having the benefit of year's of experience, with OSPF networks, I would have chosen a different precedence for determining which LSA is more recent. Thanks, Acee > <image001.png> Roger David > Architect, Verification Engineering > Reliable Tech Park | Navi Mumbai, India > Mobile: +91 8308227212 > <image002.png> > > Disclaimer > This e-mail together with any attachments may contain information of Ribbon > Communications Inc. and its Affiliates that is confidential and/or > proprietary for the sole use of the intended recipient. Any review, > disclosure, reliance or distribution by others or forwarding without express > permission is strictly prohibited. If you are not the intended recipient, > please notify the sender immediately and then delete all copies, including > any attachments. > _______________________________________________ > Lsr mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
