Connected: An Internet Encyclopedia
RFC 1771 - 9.3 Route Selection Criteria

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1771
Up: 9. UPDATE Message Handling
Prev: 9.2.4.2 Aggregating Routing Information
Next: 9.4 Originating BGP routes

### 9.3 Route Selection Criteria

Generally speaking, additional rules for comparing routes among several alternatives are outside the scope of this document. There are two exceptions:

- If the local AS appears in the AS path of the new route being considered, then that new route cannot be viewed as better than any other route. If such a route were ever used, a routing loop would result.

- In order to achieve successful distributed operation, only routes with a likelihood of stability can be chosen. Thus, an AS must avoid using unstable routes, and it must not make rapid spontaneous changes to its choice of route. Quantifying the terms "unstable" and "rapid" in the previous sentence will require experience, but the principle is clear.

Next: 9.4 Originating BGP routes

Connected: An Internet Encyclopedia
RFC 1771 - 9.3 Route Selection Criteria