Ramachandran Sathianandan <[email protected]> writes:
Dear Acee, Thanks for the quick response. My concern stems from implementations that *do* keep link-scoped LSAs in the area LSDB, as you mentioned. If the Helper aggregates all link-local Type-9 LSAs into the area LSDB without per-interface tracking, the collision on Opaque ID becomes an issue for deterministic flushing.
Are you're saying the implementation is storing link-scoped LSAs in it's area LSDB, and also not adding the link information to differentiate between otherwise identical LSAs? If you strip the link identity from the LSAs and put them all together, you haven't implemented link-scoped anything, and this is just an implementation bug that needs to be fixed, right? Thanks, Chris. _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
