• An AS is a collection of networks under a single technical
administration. • An IGP is run inside an AS, resulting in optimum intra-AS routing. • An EGP is run between autonomous systems to enable routing policies and improve security.
Scalability • The Internet has more than 140,000 routes and is still growing. Secure routing information exchange • Routers from another AS cannot be trusted. • Tight filters are required; authentication is desirable. Support for routing policies • Routing between autonomous systems might not always follow the optimum path.
Reliable updates • TCP used as transport protocol • No periodic updates • Periodic keepalives to verify TCP connectivity • Triggered updates batched and rate-limited – Every 5 seconds for internal peer – Every 30 seconds for external peer
• BGP was designed to perform well in the following areas: – Interdomain routing applications – Huge internetworks with large routing tables – Environments that require complex routing policies • Some design tradeoffs were made: – BGP uses TCP for reliable transport— CPU-intensive – Scalability is the top priority—slower convergence
• Customers connected to more than one service provider • Service provider networks (transit autonomous systems) • Service providers exchanging traffic at an exchange point (CIX, GIX, NAP, …) • Network cores of large-enterprise customers
provider in these situations: • Customers multihomed to the same service provider • Customers that need dynamic routing protocol with the service provider to detect failures – Hint: Use private AS number for these customers. • Smaller ISPs that need to originate their routes in the Internet Use static routes in all other cases: • Static routes always simpler than BGP
• BGP has the right set of functions to support the various
interdomain routing policies. Contrary to BGP, interior routing protocols focus only on finding the optimum (usually fastest) route between two points, without respect to routing policies. • BGP is an enhanced distance vector protocol with reliable transport provided by TCP, a rich set of metrics called BGP path attributes, and scalability features such as batched updates that make it suitable for very large networks. • Customers that plan to connect to more than one ISP, and small ISPs that plan to have multiple Internet connections in the future, usually use BGP with their service provider.
• Although there are designs where BGP could be avoided,
most multihomed customers use BGP with their service providers. • A transit AS is an AS that exchanges BGP routing information with other autonomous systems and forwards information received from one AS to another AS. • BGP is bound by IP hop-by-hop, destination-only routing. Routing policies that deviate from this model cannot be implemented with BGP.
![[Cisco Press] Deploying 2.5G and 3G Technologies and Services in GSM-UMTS and CDMA Networks](https://imgv2-2-f.scribdassets.com/img/document/37870117/149x198/18019a4f4a/1285068134?v=1)
