Inter-Domain Traffic Engineering using the Origin Preference Attribute

Inter-Domain Traffic Engineering using the Origin Preference Attribute

Rolf Winter, Iljitsch van Beijnum
Copyright: © 2014 |Pages: 21
ISBN13: 9781466643055|ISBN10: 1466643056|EISBN13: 9781466643062
DOI: 10.4018/978-1-4666-4305-5.ch002
Cite Chapter Cite Chapter

MLA

Winter, Rolf, and Iljitsch van Beijnum. "Inter-Domain Traffic Engineering using the Origin Preference Attribute." Solutions for Sustaining Scalability in Internet Growth, edited by Mohamed Boucadair and David Binet, IGI Global, 2014, pp. 18-38. https://doi.org/10.4018/978-1-4666-4305-5.ch002

APA

Winter, R. & van Beijnum, I. (2014). Inter-Domain Traffic Engineering using the Origin Preference Attribute. In M. Boucadair & D. Binet (Eds.), Solutions for Sustaining Scalability in Internet Growth (pp. 18-38). IGI Global. https://doi.org/10.4018/978-1-4666-4305-5.ch002

Chicago

Winter, Rolf, and Iljitsch van Beijnum. "Inter-Domain Traffic Engineering using the Origin Preference Attribute." In Solutions for Sustaining Scalability in Internet Growth, edited by Mohamed Boucadair and David Binet, 18-38. Hershey, PA: IGI Global, 2014. https://doi.org/10.4018/978-1-4666-4305-5.ch002

Export Reference

Mendeley
Favorite

Abstract

Inter-domain Traffic Engineering (TE) is an important aspect of network operation both technically and economically. Outbound Traffic Engineering is less problematic as routers under the control of the network operator are responsible for the way traffic leaves the network. The inbound direction is considerably harder as the way traffic enters a network is based on routing decisions in other networks. There are very few mechanisms available today that facilitate inter-domain inbound traffic engineering, such as prefix deaggregation (i.e., advertise more specific prefixes), AS path prepending and systems based on BGP communities. These mechanisms have severe drawbacks such as exacerbating the increase of the size of global routing table or providing only coarse-grained control. In this chapter, an alternative mechanism is described and evaluated. The proposed solution does not increase the size of the global routing table, is easy to configure through a simple numeric value and provides a finer-grained control compared to currently used mechanisms that also do not add additional prefixes to the global routing table.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.