[robjs]

I don't understand what this means. This was not a defence of MPLS, but rather an observation that says that the fundamental domains and business logic around externally-selected TE paths do not change because we change what header instructs the network to steer packets. It's still not going to make sense to have external users try and use the "premium" paths in the network without some recompense to keep scaling them, equally, there needs to be some incentive for users to choose a "less than best" path.

Quite honestly -- this kind of marketing hype and hyperbole is what is wrong with the whole area of SR today (and I say this as someone that was _very_ involved). We've completely lost the ability to say what it is we're solving, and why we're doing it. We're driving disparate architectures into silicon where there's opportunity cost for the functionality. We're having political disagreements within the IETF based on folks trying to keep political control of technologies, not worrying about the efficacy for the industry. It's all pretty broken. YMMV.

[teleforce]

Let's us step back and look into the current mess of the existing IP networks with all the duct tapes involved (looking at you NAT). Any QoS that the end users probably want is only make dollar sense for the big companies that's why we have the fine print of best-effort services written in almost all the Telcos' EULA. What IPv6 based technology for example SRv6 is doing is trying to democratize QoS so that it's hopefully affordable to the average Joe. Perhaps it's still a pipe dream at the moment but given the current situations I will take SRv6 over MPLS, or any expensive TE any day. My networking utopia will be a local-first software with cloud vendors and Telcos independence that can utilize the networks based on their required and necessary QoS. I foresee that the best way of going forward is based on this new promising and more affordable technology that the incumbent technology cannot provide.

[fach]

Can we not step back and instead address the practical implementation challenges robjs raised?