Jeff, > What architecture? > PBR is a form of: > match DSCP X > set next-hop Y > needs no interoperability...
That's pretty narrow view. I could say the worst possible example :) You would have to either encapsulate or apply your sample config consistently on every hop. Brrrrr. To me DSCP can be used to map packets to different routing context, different plane or can be used as a parameter in flex-algorithm. Thx, R. On Fri, Nov 16, 2018 at 8:19 AM Jeff Tantsura <[email protected]> wrote: > Tony, > > What architecture? > PBR is a form of: > match DSCP X > set next-hop Y > needs no interoperability... > If someone wants to describe how they use a particular vendor feature to > solve a particular problem in a BCP, sure, the more BCPs - the better. > > Wrt using DSCP in routing decision process - it was a bad idea back then, > hasn’t got any better now... besides - now we have got a toolbox that > wasn’t available then. > > Cheers, > Jeff > On Thu, Nov 15, 2018 at 22:56 Tony Li <[email protected]> wrote: > >> >> >> On Nov 15, 2018, at 8:47 PM, Jeff Tantsura <[email protected]> >> wrote: >> >> The question is really - what is here to standardize? >> >> >> >> There’s a fine architectural BCP here: this is how we are solving problem >> XYZ. Please don’t break this. >> >> Tony >> >>
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
