Resilience in QoS
[Autenrieth-Kirstädter-2001 (doi) . ]
Achim Autenrieth, Andreas Kirstädter,
"Resilience-Differentiated QoS – Extensions to RSVP and DiffServ to Signal End-to-End IP Resilience Requirements",
Third International Workshop on the Design of Reliable Communication Networks, Budapest, Hungary, 7-10 October, 2001
ResiliNets Keywords: Resilience Service Level
Abstract: "Based on the growing commercial importance of the Internet network resilience is becoming a key design issue for future IPbased networks. Faced with multiple recovery options, an ISP or NSP must decide, which flows to protect to what degree against network failures. In this paper an extension to existing Quality of Service (QoS) architectures is presented which integrates the signaling of resilience requirements with the traditional QoS signaling. We refer to this extended QoS model as Resilience-Differentiated QoS (RD-QoS). The applications signal their resilience requirements in addition to their QoS requirements to the network edge. The network takes the resilience requirements into consideration for the resource management and traffic handling. At the border of MPLS domains, the resilience requirements can then be directly mapped to the appropriate MPLS recovery options. This approach allows an integrated end-to-end provisioning of resilience and QoS in an IP-based network employing MPLS."
[Autenrieth-Kirstädter-2002 (doi) . ]
Achim Autenrieth, Andreas Kirstädter,
"RD-QoS - the integrated provisioning of resilience and QoS in MPLS-based networks",
International Conference on Communications (ICC) 2002, New York, NY, USA, 28 April - 2 May, 2002
ResiliNets Keywords: RD-QoS, MPLS
Abstract: "Based on the growing commercial importance of the Internet network resilience is becoming a key design issue for future IPbased networks. Faced with multiple recovery options, an ISP or NSP must decide, which flows to protect to what degree against network failures. In this paper an extension to existing Quality of Service (QoS) architectures is presented which integrates the signaling of resilience requirements with the traditional QoS signaling. We refer to this extended QoS model as Resilience-Differentiated QoS (RD-QoS). The applications signal their resilience requirements in addition to their QoS requirements to the network edge. The network takes the resilience requirements into consideration for the resource management and traffic handling. At the border of MPLS domains, the resilience requirements can then be directly mapped to the appropriate MPLS recovery options. This approach allows an integrated end-to-end provisioning of resilience and QoS in an IP-based network employing MPLS."
[Iannaccone-Chuah-Mortier-Bhattacharyya-Diot-2002 (doi) . ]
Gianluca Iannaccone, Chen-nee Chuah, Richard Mortier, Supratik Bhattacharyya, Christophe Diot,
"Analysis of link failures in an IP backbone",
ACM SIGCOMM Internet Measurement Workshop, 2002, Marseille, France, 6-8 November 2002
ResiliNets Keywords: Link failures, IP backbone
Abstract: "Today's IP backbones are provisioned to provide excellent performance in terms of loss, delay and availability. However, performance degradation and service disruption are likely in the case of failure, such as fiber cuts, router crashes, etc. In this paper, we investigate the occurence of failures in Sprint's IP backbone and their potential impact on emerging services such as Voice-over-IP (VoIP). We first examine the frequency and duration of failure events derived from IS-IS routing updates collected from three different points in the Sprint IP backbone. We observe that link failures occur as part of everyday operation, and the majority of them are short-lived (less than 10 minutes). We also discuss various statistics such as the distribution of inter-failure time, distribution of link failure durations, etc. which are essential for constructing a realistic link failure model. Next, we present an analysis of routing and service reconvergence time during a controlled link failure scenario in our backbone. Our results indicate that disruption to packet forwarding after link failures depends not only on routing protocol dynamics, but also on the design of routers' architectures and control planes. Thus our results offer insights into two basic components for defining network-wide availability, which we consider a more appropriate metric for service-level agreements to support emerging applications."
