Acee - The logical extension to your position would be that there is no need to define/use flex-algo because everything we can do with flex-algo could be done with multiple topologies. This may be true - but the deployment challenges/costs associated with using multiple topologies in this way have made it far less appealing for many use cases.
I would also suggest that you consider the use case described in https://datatracker.ietf.org/doc/draft-xz-pim-flex-algo/ - where flex-algo soft dataplane is used as an adjunct to a multicast topology - not a replacement. I guess your answer to that would be to have "many multicast topologies"??? This would be, of course, possible - but much more difficult/expensive to deploy. Les > -----Original Message----- > From: Acee Lindem <[email protected]> > Sent: Friday, August 22, 2025 2:33 PM > To: Acee Lindem <[email protected]> > Cc: lsr <[email protected]>; Les Ginsberg (ginsberg) <[email protected]>; Peter > Psenak (ppsenak) <[email protected]>; <[email protected]> > <[email protected]> > Subject: Re: LSR WG Adoption Poll for "IGP Flex Soft Dataplane" - draft- > ginsberg-lsr-flex-soft-dataplane-01 > > Speaking as WG member: > > I think the requirements for this draft are "soft" given that the only example > provided is the multicast distribution which has been satisfied for decades > using a separate multicast topology. > In short, the draft suffers from "ED" which in this case is "Exemplar > Deficiency". > I'm certainly not going to support adoption until I see a more compelling use > case. > > Thanks, > Acee > > > > On Aug 22, 2025, at 5:22 PM, Acee Lindem <[email protected]> wrote: > > > > LSR WG, > > > > The begins the LSR WG adoption call for "IGP Flex Soft Dataplane" - draft- > ginsberg-lsr-flex-soft-dataplane-01. Please express your support or objection > on this list prior to Saturday September 6, 2025. > > > > Thanks, > > Acee _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
