Market Leader Programs
5G Transport - A 2023 Heavy Reading Survey 2023 Open RAN Operator Survey Coherent Optics at 100G, 400G, and Beyond Open RAN Platforms and Architectures Operator Survey Cloud Native 5G Core Operator Survey Bridging the Digital Divide 5G Network Slicing Operator Survey Open, Automated & Programmable Transport The Journey to Cloud Native
"MPLS does provide a connection-oriented framework to handle this. You are raising the issue of the cost of adding this connection-oriented framework to IP, which is a very valid point. "
I am painfully familiar with MPLS. unfortunately, it does not in fact provide a UNIVERSAL connection-oriented service in today's networks. To use MPLS to avoid oversubscriptoin, we need user-to-user connections on demand. i.e. the MPLS equivalent of X.25, FR. or ATM SVCs. If you do not have user-to-user VCs, then you cannot have guaranteed user-to-user bandwidth. The fact that the RSVP protocol provides a mechanism for SVCs is irrelevant, since the Internet as a whole does not support user-to-user MPLS SVCs.
indianajones furhter said:
"I really believe that it can be done if you limit the number of different service classes to something small, say 3 to 4. The number of states that one needs to keep in the core is within limits and we can still achieve a good service model without over-provisioning. I am not arguing for a flow-based core - too much complexity with no real tangible return."
You imply that the core will not in fact be sensitive to per-flow guarantees. I can conceive of an aggregation scheme that can reduce the amount of state information in the core, but such a scheme will require new protocols that have not been specified or implemented.
indianajones said fruther:
"It is not entirely true that premium traffic cannot take up a lot of bandwidth."
I did not say that premium services would be a low percentage of total bandwidth. I was quoting another post that mad this assdertion. I said that IF premium services are a low percentage, THEN the core can (almost always) provide premium service without per-flow state. If premiun services comprise more than a small percentage of the bandwidth, then the current protocols are insufficient to guarantee premium service, even assuming that each router can perform "perfect forwarding."