Option #2 For reasons I have stated both on the list and in the recent WG meeting
Les > -----Original Message----- > From: Acee Lindem <acee.i...@gmail.com> > Sent: Friday, August 2, 2024 11:06 AM > To: lsr <lsr@ietf.org> > Subject: [Lsr] Consensus Call on "IS-IS Distributed Flooding Reduction" - > draft- > ietf-lsr-distoptflood-05 > > > The subject draft was adopted as a WG document containing only the flooding > reduction algorithm (section 2). > > Procedures and signaling have been added to the current version allowing > concurrent operation within an IS-IS area of IS-IS routers running different > flooding reduction algorithms or no flooding reduction at all (section 1). > > WG members are questioning if this extra requirement needs to be met and > included in this document. There was an extensive discussion during the IETF > 120 LSR meeting and a MeetEcho show-of-hands poll was taken - > https://notes.ietf.org/notes-ietf-120-lsr > > Please indicate your preference and reasoning amongst the following options > by August 17, 2024: > > 1) The document remains in its current form describing both the flooding > reduction algorithm signaling/procedures and the new flooding reduction > algorithm. > 2) The flooding reduction algorithm and procedures will be split into a > separate document with its own LSR WG adoption call. > 3) Some other resolution? > > Thanks, > Yingzhen, Chris, and Acee (LSR Chairs) > _______________________________________________ > Lsr mailing list -- lsr@ietf.org > To unsubscribe send an email to lsr-le...@ietf.org _______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
