rfc2185.txt

中、英文RFC文档大全打包下载完全版 .

   that where tunneling is needed, host to host tunneling will be
   preferred over host to router tunneling. Other combinations are
   therefore possible if other policies are used.

   Due to a specific policy choice, the default sending rules in [1] may
   not be followed.

   Note that IPv6-capable hosts which do not have any local IPv6 router
   must be given an IPv4-compatible v6 address in order to make use of
   their IPv6 capabilities. Thus, there are no entries for IPv6-capable
   hosts which have an incompatible IPv6 address and which also do not
   have any connectivity to any local IPv6 router. In fact, such hosts
   could communicate with other IPv6 hosts on the same local network
   without the use of a router.  However, since this document focuses on



Callon & Haskin              Informational                      [Page 9]

RFC 2185           Routing Aspects Of IPv6 Transition     September 1997


   routing and router implications of IPv6 transition, direct
   communication between two hosts on the same local network without any
   intervening router is outside the scope of this document.

   Also, table 1 does not consider manually configured point-to-point
   tunnels.  Such tunnels are treated as if they were normal point-to-
   point links. Thus any two IPv6-capable devices which have a manually
   configured tunnel between them may be considered to be directly
   connected.

  -----------------+------------------+--------------------------
  Host A           | Host B           | Result
  -----------------+------------------+--------------------------
  v4-compat. addr. | v4-compat. addr. | host to host tunneling
  no local v6 rtr. | no local v6 rtr. | in both directions
  -----------------+------------------+--------------------------
  v4-compat. addr. | v4-compat. addr. | A->B: host to host tunnel
  no local v6 rtr. | local v6 rtr.    | B->A: v6 forwarding plus
                   |                  |       rtr->host tunnel
  -----------------+------------------+--------------------------
  v4-compat. addr. | incompat. addr.  | A->B: host to rtr tunnel
  no local v6 rtr. | local v6 rtr.    |       plus v6 forwarding
                   |                  | B->A: v6 forwarding plus
                   |                  |       rtr to host tunnel
  -----------------+------------------+--------------------------
  v4-compat. addr. | v4-compat. addr. | end to end native v6
  local v6 rtr.    | local v6 rtr.    | in both directions
  -----------------+------------------+--------------------------
  v4-compat. addr. | incompat. addr.  | end to end native v6
  local v6 rtr.    | local v6 rtr.    | in both directions
  -----------------+------------------+--------------------------
  incompat. addr.  | incompat. addr.  | end to end native v6
  local v6 rtr.    | local v6 rtr.    | in both directions
  -----------------+------------------+--------------------------

          Table 1: Summary of Automatic Tunneling Combinations

3.3.5 Example

   Figure 2 illustrates an example network with two regions A and B.
   Region A is dual, meaning that the routers within region A are
   capable of forwarding both IPv4 and IPv6. Region B is IPv4-only,
   implying that the routers within region B are capable of routing only
   IPv4. The illustrated routers R1 through R4 are dual. The illustrated
   routers r5 through r9 are IPv4-only. Also assume that hosts H3
   through H8 are dual. Thus H7 and H8 have been upgraded to be IPv6-
   capable, even though they exist in a region in which the routers are
   not IPv6-capable. However, host h1 and h2 are IPv4-only.



Callon & Haskin              Informational                     [Page 10]

RFC 2185           Routing Aspects Of IPv6 Transition     September 1997


     .........................       .......................
     .                       .       .                     .
     .       h1              .       .              |-h2   .
     .       |               .       .              |      .
     .  H3---R1--------R2---------------r5----r9----+      .
     .       |         |     .       .        |     |-H7   .
     .       |         |     .       .        |            .
     .       |         |     .       .        |            .
     .  H4---R3--------R4---------------r6----r8-----H8    .
     .                       .       .                     .
     .........................       .......................
      Region A (Dual Routers)        Region B (IPv4-only Rtrs)

                Figure 2: Example of Automatic Tunneling

   Consider a packet from h1 to H8. In this case, since h1 is IPv4-only,
   it will send an IPv4 packet. This packet will traverse regions A and
   B as a normal IPv4 packet for the entire path. Routing will take
   place using normal IPv4 routing methods, with no change from the
   operation of the current IPv4 Internet (modulo normal advances in the
   operation of IPv4, of course). Similarly, consider a return packet
   from H8 to h1. Here again H8 will transmit an IPv4 packet, which will
   be forwarded as a normal IPv4 packet for the entire path.

   Consider a packet from H3 to H8. In this case, since H8 is in an
   IPv4-only routing domain, we can assume that H8 uses an IPv4-
   compatible IPv6 address. Since both source and destination are IPv6-
   capable, H3 may transmit an IPv6 packet destined to H8. The packet
   will be forwarded as far as R2 (or R4) as an IPv6 packet.

   Router R2 (or R4) will then encapsulate the full IPv6 packet in an
   IPv4 header for delivery to H8. In this case it is necessary for
   routing of IPv6 within region A to be capable of delivering this
   packet correctly to R2 (or R4). As explained in section 3.3, routers
   R2 and R4 may inject routes to IPv4-compatible IPv6 addresses into
   the IPv6 routing used within region A corresponding to the routes
   which are available via IPv4 routing within region B.

   Consider a return packet from H8 to H3. Again, since both source and
   destination are IPv6-capable, a IPv6 packet may be transmitted by H8.
   However, since H8 does not have any direct connectivity to an IPv6-
   capable router, H8 must make use of an automatic tunnel.  Which form
   of automatic tunnel will be used depends upon the type of address
   assigned to H3.







Callon & Haskin              Informational                     [Page 11]

RFC 2185           Routing Aspects Of IPv6 Transition     September 1997


   If H3 is assigned an IPv4-compatible address, then the requirements
   specified in section 3.3.1 will all be satisfied. In this case host
   H8 may encapsulate the full IPv6 packet in an IPv4 header using a
   source IPv4 address extracted from the IPv6 address of H8, and using
   a destination IPv4 address extracted from the IPv6 address of H3.

   If H3 has an IPv6-only address, then it is not possible for H8 to
   extract an IPv4 address to use as the destination tunnel address from
   the IPv6 address of H3.  In this case H8 must use host to router
   tunneling, as specified in section 3.3.2. In this case one or both of
   R2 and R4 must have been configured with a tunnel endpoint IPv4
   address (R2 and R4 may use either the same address or different
   addresses for this purpose).  R2 and/or R4 therefore advertise
   reachability to the tunnel endpoint address to r5 and r6
   (respectively), which advertise this reachability information into
   region B. Also, H8 must have been configured to know which tunnel
   endpoint address to use for host to router tunneling. This will
   result in the IPv6 packet, encapsulated in an IPv4 header, to be
   transmitted as far as the border router R2 or R4. The border router
   will then strip off the IPv4 header, and forward the remaining IPv6
   packet as a normal IPv6 packet using the normal IPv6 routing used in
   region A.

4. SECURITY CONSIDERATIONS

   Use of tunneling may violate firewalls of underlying routing
   infrastructure.

   No other security issues are discussed in this paper.

5. REFERENCES

   [1] Gilligan, B. and E. Nordmark. Transition Mechanisms for IPv6
       Hosts and Routers, Sun Microsystems, RFC 1933,  April 1996.


6. AUTHORS' ADDRESSES

   Ross Callon
   Cascade Communications Co.
   5 Carlisle Road
   Westford, MA 01886
   email: [e-mail]








Callon & Haskin              Informational                     [Page 12]

RFC 2185           Routing Aspects Of IPv6 Transition     September 1997


   Dimitry Haskin
   Bay Networks, Inc.
   2 Federal Street
   Billerica, MA 01821
   email: [e-mail]














































Callon & Haskin              Informational                     [Page 13]