RFC 2772 (rfc2772) - Page 3 of 14
6Bone Backbone Routing Guidelines
Alternative Format: Original Text Document
RFC 2772 6Bone Backbone Routing Guidelines February 2000
2. Scope of this document
This document is a best-practices Informational document aimed at
IPv6 entities which operate under the 6Bone IPv6 testbed TLA
allocation.
3. Common Rules for the 6bone
This section details common rules governing the routing of the 6Bone.
They are derived from the issues encountered on the 6Bone, with
respect to the routes advertised, handling of special addresses, and
aggregation:
1) link local prefixes
2) site local prefixes
3) loopback and unspecified prefixes
4) multicast prefixes
5) IPv4-compatible prefixes
6) IPv4-mapped prefixes
7) default routes
8) yet undefined unicast prefixes (from a different /3 prefix)
9) inter-site links issues
10) 6to4 prefixes
11) aggregation & advertisement issues
3.1 Link-local prefixes
This link-local prefix (FE80::/10) MUST NOT be advertised through
either an IGP or an EGP. Under no circumstance should this prefix be
seen in the 6Bone backbone routing table.
By definition, the link-local prefix has a scope limited to a
specific link. Since the prefix is the same on all IPv6 links,
advertising it in any routing protocol does not make sense and,
worse, may introduce nasty error conditions.
Well known cases where link-local prefixes could be advertised by
mistake include, but are not limited to:
Rockell & Fink Informational