A Study of Path Protection in Self-Healing Routing
Recent routing failure accidents show that routing systems are not so stable as we estimated because most of accidents caused packet delivery failure in Internet. In order to resolve this problem, many fast reroute solutions are proposed to guarantee reroute path provision after network failures without high packet loss. However, most of these solutions are not deployed in practice, and some key issues still need further consideration, such as the route loop issue and the deployment cost issue. In this paper, we present state machine models to analyze how path protection works in self-healing routing solutions and identify the drawbacks in traditional path protection approaches. We identify several requirements of path protection approaches, and present principles of our path protection approach to protect Internet routing based on our analysis result. Furthermore, we conduct a detailed study to measure our proposed path protection approach in production networks and the study shows that availability and stability of routing systems is improved in real production networks.
KeywordsPacket Loss Production Network Path Protection Network Failure Internet Draft
- 2.Atlas, A., Zinin, A., Torvi, R., Choudhury, G., Martin, C., Imhoff, B., Fedyk, D.: Basic specification for ip fast-reroute: Loop-free alternates, Internet draft, draft-ietf-rtgwg-ipfrrspec- base-10.txt (November 2007)Google Scholar
- 4.Katz, D., Ward, D.: Bidirectional forwarding detection, March 2007. Internet draft, draft-ietf-bfd-base- 06.txt (2007)Google Scholar
- 5.Markopoulou, A., Iannaccone, G., Bhattacharyya, S., Chuah, C., Diot, C.: Characterization of failures in an ip backbone. In: Proceeding of the IEEE INFOCOM, pp. 2307–2317 (2004)Google Scholar
- 7.Shand, M., Bryant, S.: Ip fast reroute framework, June 2007. Internet draft, draft-ietf-rtgwg-ipfrrframework- 07.txt (2007)Google Scholar
- 8.Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, G., Palter, B.: Layer two tunneling protocol L2TP. RFC2661 (August 1999)Google Scholar