Connected: An Internet Encyclopedia
RFC 1772 - 8. Interaction with other exterior routing protocols

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1772
Prev: 7. Required set of supported routing policies
Next: 8.1 Exchanging information with EGP2

### 8. Interaction with other exterior routing protocols

The guidelines suggested in this section are consistent with the guidelines presented in [3].

An AS should advertise a minimal aggregate for its internal destinations with respect to the amount of address space that it is actually using. This can be used by administrators of non-BGP 4 AS's to determine how many routes to explode from a single aggregate.

A route that carries the ATOMIC_AGGREGATE path attribute shall not be exported into either BGP-3 or EGP2, unless such an exportation can be accomplished without exploding the NLRI of the route.

8.1 Exchanging information with EGP2
8.2 Exchanging information with BGP-3

Next: 8.1 Exchanging information with EGP2

Connected: An Internet Encyclopedia
RFC 1772 - 8. Interaction with other exterior routing protocols