blank.gif (43 bytes)

Church Of The
Swimming Elephant

Search:
4.5 Intra-domain protocol considerations Connected: An Internet Encyclopedia
4.5 Intra-domain protocol considerations

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1519
Up: 4. Changes to inter-domain routing protocols and practices
Prev: 4.4. Responsibility for and configuration of aggregation
Next: 5. Example of new allocation and routing

4.5 Intra-domain protocol considerations

4.5 Intra-domain protocol considerations

While no changes need be made to internal routing protocols to support the advertisement of aggregated routing information between autonomous systems, it is often the case that external routing information is propagated within interior protocols for policy reasons or to aid in the propagation of information through a transit network. At the point when aggregated routing information starts to appear in the new exterior protocols, this practice of importing external information will have to be modified. A transit network which imports external information will have to do one of:

  1. use an interior protocol which supports aggregated routing

  2. find some other method of propagating external information which does not involve flooding it through the interior protocol (i.e., by the use of internal BGP, for example).

  3. stop the importation of external information and flood a "default" route through the internal protocol for discovery of paths to external destinations.

For case (a), the modifications necessary to a routing protocol to allow it to support aggregated information may not be simple. For protocols such as OSPF and IS-IS, which represent routing information as either a destination+mask (OSPF) or as a prefix+prefix-length (IS-IS) changes to support aggregated information are conceptually fairly simple; for protocols which are dependent on the class-A/B/C nature of networks or which support only fixed-sized subnets, the changes are of a more fundamental nature. Even in the "conceptually simple" cases of OSPF and IS-IS, an implementation may need to be modified to support supernets in the database or in the forwarding table.


Next: 5. Example of new allocation and routing

Connected: An Internet Encyclopedia
4.5 Intra-domain protocol considerations

Cotse.Net

Protect yourself from cyberstalkers, identity thieves, and those who would snoop on you.
Stop spam from invading your inbox without losing the mail you want. We give you more control over your e-mail than any other service.
Block popups, ads, and malicious scripts while you surf the net through our anonymous proxies.
Participate in Usenet, host your web files, easily send anonymous messages, and more, much more.
All private, all encrypted, all secure, all in an easy to use service, and all for only $5.95 a month!

Service Details

 
.
www.cotse.com
Have you gone to church today?
.
All pages ©1999, 2000, 2001, 2002, 2003 Church of the Swimming Elephant unless otherwise stated
Church of the Swimming Elephant©1999, 2000, 2001, 2002, 2003 Cotse.com.
Cotse.com is a wholly owned subsidiary of Packetderm, LLC.

Packetderm, LLC
210 Park Ave #308
Worcester, MA 01609