1. IETF Differentiated Services Concerns with Intserv: r Scalability: signaling, maintaining per-flow router state difficult with large number of flows r Flexible Service Models: Intserv has only two classes. Also want “qualitative” service classes m “behaves like a wire” m relative service distinction: Platinum, Gold, Silver Diffserv approach: r simple functions in network core, relatively complex functions at edge routers (or hosts) r Don’t define define service classes, provide functional components to build service classes

2. Differentiated Services r Intended to address the following difficulties with Intserv and RSVP; r Scalability: maintaining states by routers in high speed networks is difficult sue to the very large number of flows r Flexible Service Models: Intserv has only two classes, want to provide more qualitative service classes; want to provide ‘relative’ service distinction (Platinum, Gold, Silver, …) r Simpler signaling: (than RSVP) many applications and users may only w ant to specify a more qualitative notion of service

3. Diffserv Architecture Edge router: - per-flow traffic management - marks packets as in-profile and out-profile Core router: - per class traffic management - buffering and scheduling based on marking at edge - preference given to in-profile packets - Assured Forwarding scheduling... r b marking

4. Edge Functions r At DS-capable host or first DS-capable router r Classification: edge node marks packets according to classification rules to be specified (manually by admin, or by some TBD protocol) r Traffic Conditioning: edge node may delay and then forward or may discard

5. Edge-router Packet Marking r class-based marking: packets of different classes marked differently r intra-class marking: conforming portion of flow marked differently than non-conforming one r profile: pre-negotiated rate A, bucket size B r packet marking at edge based on per-flow profile Possible usage of marking: User packets Rate A B

6. Classification and Conditioning r Packet is marked in the Type of Service (TOS) in IPv4, and Traffic Class in IPv6 r 6 bits used for Differentiated Service Code Point (DSCP) and determine PHB that the packet will receive r 2 bits are currently unused

7. Classification and Conditioning may be desirable to limit traffic injection rate of some class: r user declares traffic profile (eg, rate, burst size) r traffic metered, shaped if non-conforming

8. Forwarding (PHB) r PHB result in a different observable (measurable) forwarding performance behavior r PHB does not specify what mechanisms to use to ensure required PHB performance behavior r Examples: m Class A gets x% of outgoing link bandwidth over time intervals of a specified length m Class A packets leave first before packets from class B

9. Forwarding (PHB) PHBs being developed: r Expedited Forwarding: pkt departure rate of a class equals or exceeds specified rate m logical link with a minimum guaranteed rate r Assured Forwarding: 4 classes of traffic m each guaranteed minimum amount of bandwidth m each with three drop preference partitions

10. Diffserv and MPLS r Both are WAN QoS mechanisms. While Diffserv is used for traffic aggregation and provisioning of differentiated services, MPLS is mainly used for traffic aggregation and load balancing.

11. MPLS r Originally introduced as a WAN mechanism for forwarding packets using label switching instead of the IP address-based routing and provide differentiated QoS. r It has found its most use in Traffic Engineering (TE) m TE requires that traffic follows specific, possibly nonoptimal, routes to enable diverse routing, traffic load balancing, and other means of optimizing network resources. r MPLS forces traffic into these routes or Label Switched Paths (LSPs).

12. Routers or LSRs r In the MPLS network, routers are called label switching routers (LSR). m Edge LSRs (also called LERs) provide the interface between the external IP network and the LSP. m Core LSRs provide transit services through the MPLS cloud using the pre-established LSP. m In a SP network, on the ingress the Edge LSR accepts IP packets and appends MPLS labels. m On the egress, an edge LSR terminates the LSP by removing MPLS labels and resorting to the normal IP forwarding.

13. FEC r The forward equivalence class (FEC) is a representation of a group of packets that share the same requirements for their transport. All packets in such a group are provided the same treatment en route to the destination. r Each LSR builds a table to specify how a packet must be forwarded. The table, label information base (LIB) comprises of FEC-to-label bindings.

14. Labels and Label Bindings r A label identifies the path a packet should traverse r It is encapsulated in a layer-2 header of the packet -- special MPLS header (aka shim) includes a label, an experimental field (Exp), an indicator of additional labels(S), and Time to live (TTL). r Receiving router uses the label content to determine the next hop. r Label values are of local significance only pertaining to hops between LSRs. r Labels are bound to an FEC asa result of some event or policy

15. Label Assignment r Based on forwarding criteria such as m destination unicast routing m traffic engineering m multicast m virtual private network m QoS

16. MPLS Signaling r A signaling protocol performs a variety of functions such as: m setting up LSPs traversing specified sequences of LSRs derived from the constraint-based routing (CR) analysis; m create the path state in each LSR by performing label allocation, distribution, and binding; m reserve resources in each LSR including bandwidth, delay, and packet loss bounds; m eassign the network resources as necessary; m dynamically reroute during network congestion and failures; m monitor and maintain explicitly routed LSP state

17. CR-LDP r CR-LDP: LDP using constraint-based routing m LDP provides a common understanding between LSR peers of the meaning of labels used to forward traffic between them m Message categories: Discovery -- sent periodically by LSRs to announce their presence Session -- to establish, maintain, and terminate a session between two LDP peers Advertisement -- to create, change, and delete label mappings to FECs after a session has been established Notification -- to signal and provide advisory info. r Forward path, hard state with no state refreshes

18. RSVP-TE r Signals between LSRs r Creates a state for a collection of flows between the ingress and egress points of a traffic trunk r An LSP aggregates multiple host-to-host flows and thus reduces the amount of RSVP states in the network r Uses firm state where Path and Resv messages are periodically refreshed but their volume is significantly reduced

19. QoS Routing r As defined in RFC 2386, QoS “is a set of service requirements to be met by the network while transporting a flow.” A flow is “a packet stream from source to a destination with an associated QoS.” r Measurable level of service delivered to network users which can be characterized by packet loss probability, available bandwidth, end-to-end delay, etc. Expressed as a Service Level Agreement(SLA) between network users and service providers. r QoS-based routing is defined as “a routing mechanism under which paths for flows are determined based on some knowledge of resource availability in the network as well as the QoS requirement of the flows.” A dynamic routing scheme with QoS considerations.

20. QoS Metrics r Bandwidth, delay, jitter, cost, loss probability r three types of metrics: additive, multiplicative, concave r Let m(n1,n2) be a metric for link(n1, n2). For any path P = (n1, n2,.., ni, nj), metrci m is: m additive, if m(P) = m(n1,n2) + m(n2,n3) +…..+ m(ni,nj) (examples are dealy, jitter, cost, hop-count) m multiplicative, if m(P) = m(n1,n2) * m(n2,n3) *…* m(ni,nj) (example is reliability, in which case 0<=m(ni,nj)<=1) m concave, if m(P) = min{m(n1,n2), m(n2,n3), …, m(ni,nj)} (example is bandwidth meaning that the bandwidth of the path as a whole is determined by the link with the minimum available bandwidth)

21. Objectives r To meet QoS requirements of end users. r To optimize network resource usage r to gracefully degrade network performance under heavy load

22. Design Issues(1) r IP routing protocols such as OSPF, RIP, and BGP are called “best-effort” routing protocols. They use only the shortest path to the destination -- single objective optimization algorithms which consider only one metric (like hop-count). r Much more difficult to design and implement than Best-effort routing. Many tradeoffs have to be made. In most cases the goal is not to find the best solution but to find a viable solution with acceptable cost.

23. Design Issues(2) r Metrics and path computation m how do we measure and collect network state information? m how do we compute routes based on the information collected? r Mapping of QoS requirements to well defined QoS Metrics r Computation complexity associated with path computation (much of QoS routing based on multiple constraint optimization is NP-complete). Many heuristic algorithms exist.

24. Design Issues (3) r Path computation is followed by resource reservation which means that when the path is chosen the network state in terms of available resources is changed and such information needs to propagated throughout the network. r Knowledge propagation and Maintenance m how often the routing information is exchanged between the routers? m The tradeoff here is between information accuracy and efficiency. m For instance, what is available bandwidth? Is it what is left after reservation or the actual physically available? m How do we maintain the info collected?(on demand path computation, aggregation, routing tables?)

25. Design Issues (4) r Scaling by hierarchical aggregation r Imprecise state information model. Sources of inaccuracy: m network dynamics m aggregation of routing information m hidden information m approximate calculation r Administrative control -- flow priorities and preemption, resource control and fairness r Integrate QoS-based routing and Best-effort routing

26. Intra-domain Vs. Inter-domain r Dynamic path computation to statically provisioned paths for a few service classes for intra-domain r Some common features for intra-domain: m admission control, optimal resource usage, failure notices, support for best-effort flows, support for multicast routing with receiver heterogeneity and shared reservation styles r Inter-domain routing scheme have to be scalable and therefore, simple. m Cannot be based on highly dynamic network state info m info exchange between domains should be relatively static

27. Routing Strategies r Source routing r distributed routing r hierarchical routing r they are classified based on the way the state information is maintained and the search foe feasible path is carried out

28. Source Routing r Each node maintains the complete global state, including the network topology and the state information of every link r Based on the global state, a feasible path is locally computed at the source node r A control message is sent out along the selected path to inform the intermediate nodes of their precedent and successive nodes r A link state protocol is used to update the global state at every node

29. Source Routing (2) r Strengths: simplicity through centralization; avoids many of the distributed computing problems; guarantees loop-free routes; conceptually simple, easy to implement, evaluate, debug and upgrade; centralized heuristics are much easier to design for some NP-complete routing problems. r Weaknesses: communication overhead to maintain global state; imprecision global state info; high computation overhead at the source; In short, source routing has scalability problem.

30. Distributed Routing r Path is computed by a distributed computation r Control messages are exchanged among nodes and state information kept at each node is collectively used for path search r Requires a distance-vector protocol or link-state protocol to maintain a global state in the form of distance vectors at every node. Based on the distance vectors, the routing is done on a hop-by- hop basis.

31. Distributed Routing (2) r Strengths: path computation is distributed and result in shorter routing response time; scalable; searching multiple paths in parallel for a feasible path; routing decision and optimization is done entirely based on local states; r Weaknesses: dependence on global state; flooding based algorithms which do not maintain global state have higher communication overheads; difficult to design efficient heuristics in the absence of detailed topology or link-state info; presence of loops due to inaccurate global state info at individual nodes (easily detected but alternate paths are difficult to find)

32. Hierarchical Routing r Nodes are clustered into groups which may be clustered into higher level groups recursively creating a multi-level hierarchy. r Each physical node maintains an aggregated global state -- contains the detailed state info about the nodes in the same group and aggregated state info about other groups. r Source routing is used to find a feasible path. r A control message is sent along this path to establish the connection. A border node in a group represented by a logical node receives the message and uses source routing to extend the path through the group.

33. Hierarchical Routing (2) r Strengths: Scales well; retains many advantages of source routing as well as distributed routing. r Weaknesses: aggregated network state introduces additional imprecision; gets more complicated when multiple QoS constraints are involved.