RFC 3056:Connection of IPv6 Domains via IPv4 Cloud...
RFC-Ref

domain


Click on the red underlined text to get to the source

... tunnel setup, and for them to communicate with native IPv6 domains via relay routers. Effectively it treats the wide area IPv4 network ...
... wide area network which has no native IPv6 support, to communicate with other such IPv6 domains or hosts with minimal manual configuration ...
... 6to4 exterior routing domain: a routing domain ...
... domain: a routing domain interconnecting a set of 6to4 routers and relay routers ...
... IPv6 site's interior routing domain, and distinct from all native IPv6 exterior routing ...
... IPv6 exterior routing domains. ...


... router acting as a relay between the 6to4 domain and a given native IPv6 domain. There is nothing special about it; it is simply a normal router ...
... 6to4 domain and a given native IPv6 domain. There is nothing special about it; it is simply a normal router which happens to have at least ...
... We now have three distinct classes of routing domain to consider: ...
... 1. the internal IPv6 routing domain of each 6to4 site; 2. an exterior IPv6 routing ...
... 6to4 site; 2. an exterior IPv6 routing domain interconnecting a given set of 6to4 border routers ...
... among themselves, i.e., a 6to4 exterior routing domain; 3. the exterior IPv6 routing domain ...
... domain; 3. the exterior IPv6 routing domain of each native IPv6 island. ...
... 1. The internal routing domain of a 6to4 site behaves as described in section 5.1. ...
... 6to4 exterior routing domain: 2.1 No IPv6 ...
... IPv6 exterior routing domain. It is a matter of routing policy how far this routing advertisement ...
... interface, but these are independent routing domains with separate policies, even if the same protocol, probably BGP4+, is used in both cases. ...
... Routing policy within the native IPv6 routing domain determines the scope of that advertisement, thereby limiting the visibility of the relay router in that domain ...
... domain determines the scope of that advertisement, thereby limiting the visibility of the relay router in that domain. ...
... If BGP4+ is not deployed in the 6to4 exterior routing domain (option 2.1 of Section 5.2), the relay router will be configured to accept ...
... If BGP4+ is deployed in the 6to4 exterior routing domain (option 2.2 of Section 5.2), the relay router advertises IPv6 ...
... routing prefix into the native IPv6 domain and MUST NOT advertise any native IPv6 routing prefixes ...
... IPv6 route into the 6to4 domain. Within the 6to4 domain ...
... domain. Within the 6to4 domain it will behave exactly as in the basic 6to4 scenario of Section 5.1. ...
... routing protocol is in use in the 6to4 exterior routing domain, the site's 6to4 router will be configured with a default IPv6 ...
... prefix from relay routers into the native IPv6 domain, whose scope is limited by routing policy. This is the only non-native IPv6 prefix ...
... It will be necessary for 6to4 routers to obtain routes to relay routers in order to access the native IPv6 domain. In the simplest case there will be a manually configured default IPv6 route ...
... IPv6 traffic within a 6to4 domain will follow exactly the same path as unicast IPv4 ...
... into a 6to4 exterior routing domain, since this would attract all 6to4 traffic ...
... prefix may be legitimately advertised into the native IPv6 routing domain by a relay router, and into an IPv6 site's ...
... IPv6 site's local IPv6 routing domain; hence there is a risk of misconfiguration causing it to be advertised into a 6to4 exterior routing ...
... causing it to be advertised into a 6to4 exterior routing domain. ...
... 6to4 exterior routing domain. ...


... traffic once it leaves the 6to4 domain. Therefore, implementing IPv6 security is required even if ...


... Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing", RFC 2545prop, March 1999. ...
... Carpenter, B. and C. Jung, "Transmission of IPv6 over IPv4 Domains without Explicit Tunnels", RFC 2529prop, March 1999. ...



Google
Web
RFC-Ref