| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
BGP Autonomous System Types, Traffic Flows and Routing Policies (Page 3 of 3) Issues With Routing Policies and Internetwork Design What would happen to a city if every street only allowed local traffic? It would be pretty hard to get around. Of course this problem never occurs in well-designed cities, because traffic planners understand the dual need for connectivity and through-traffic avoidance in residential areas. Cities are laid out in a somewhat hierarchical fashion, so local traffic funnels to thoroughfares intended specifically to carry non-local traffic. The same basic situation exists in an internetwork. It wouldn't work very well if every AS declared it was not interested in carrying transit traffic! Usually, internetworks are designed so that certain autonomous systems are intended to carry large amounts of transit traffic. This is typically the function of high-speed, high-capacity backbone connections, which serve other ASes as customers. An AS will usually only carry another AS's traffic if arrangements have been made to allow this.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. |