I support WG adoption of this draft. I think it is useful to capture the approach for an effective centralized algorithm (RFC 9667).
Although Section 3 of the draft already references RFC 9667 centralized mode, I think it would be good to add an IANA section which explicitly states that there is no need/intention to assign an algorithm # in the IGP Algorithm Type For Computing Flooding Topology registry created by RFC 9667 (i.e., reserved algorithm #0 is used) just to avoid any confusion on this point. Les > -----Original Message----- > From: Acee Lindem <[email protected]> > Sent: Friday, June 13, 2025 12:16 PM > To: lsr <[email protected]> > Cc: Tony Li <[email protected]>; Sarah Chen <[email protected]> > Subject: [Lsr] LSR WG Adoption Call on "An Algorithm for Computing Dynamic > Flooding Topologies" - draft-chen-lsr-dynamic-flooding-algorithm-02 > > After some disruption, we are getting back to the normal work of the LSR > working group. > > This begins the start of a 3-week WG adoption poll for "An Algorithm for > Computing Dynamic Flooding Topologies”. > This draft specifies a centralized algorithm utilizing the RFC 9667 dynamic > flooding framework. The intended status > is Experimental. > > Please express your support or objection to this draft by July 5th, 2025. The > extended (3 week) WG adoption is to > allow for several US holidays. > > Thanks, > Acee > _______________________________________________ > 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]
