rfc2430 Architecture for Differentiated Services and TE

  1. using MPLS and RSVP to create a scalable traffic management architecture that supports differentiated services.
  2. three different traffic classes: Best Effort, Priority, and Network Control
  3. Network Control: routing protocols and network management traffic.
  4. The traffic class of MPLS packets can be encoded in the three bits reserved for CoS.
  5. traffic classes for IPv4 packets can be classified via the IPv4 ToS byte.
  6. As the traffic scales up, the amount of traffic in the trunks increases; not the number of trunks.
  7. RSVP mechanisms: a. provide a general facility for creating and maintaining distributed reservation state across a mesh of multicast or unicast delivery paths; b. provides a straightforward extensibility mechanism by allowing for creation of new RSVP objects.
  8. TE is necessary because standard IGPs compute the shortest path across the ISP’s network based solely on the metric that has been administratively assigned to each link. This computation does not take into account the loading of each link.