router
Click on the red underlined text to get to the source
... There are roughly three scenarios:
1. (Generic) router-to-router tunnels.
...
... There are roughly three scenarios:
1. (Generic) router-to-router tunnels.
...
... Router-to-Router Tunnels ...
... Router-to-Router Tunnels ...
... | Router | <======( Internet )=====> | Router |
| A | (_ _) | B |
'--------' '----' '--------'
...
... V V
Figure 1: Router-to-Router Scenario.
IPv6/IPv4 ...
... V V
Figure 1: Router-to-Router Scenario.
IPv6/IPv4 ...
... A specific case of router-to-router tunnels, when one router resides
at an end site, is described in the next section.
...
...
This is a generalization of host-to-router and router-to-host
tunneling, because the issues when connecting a whole site (using a
router ...
...
This is a generalization of host-to-router and router-to-host
tunneling, because the issues when connecting a whole site (using a
router) and connecting a single host ...
... host-to-router and router-to-host
tunneling, because the issues when connecting a whole site (using a
router) and connecting a single host are roughly equal.
...
... Tunnel | V4/V6 |
( Internet )<--->| Router |<=======( Internet )=======>| Site B |
(_ _) | A | (_ _) '--------'
...
... IPv4 )_ | |v6-in-v4| |
| Site B |<====( Internet )==========>| Router | |
'--------' (_ _) | | A | |
'----' | '--------' |
...
... +---------------------+
Figure 3: Site-to-Router Scenario.
In the other direction, IPv6/IPv4 ...
... IPv6 packets to an
intermediary IPv6/IPv4 router that is reachable via an IPv4
infrastructure. This type of tunnel ...
... SA could be bound to the prefix
that was allocated to the router at Site B, and Router A could verify
that the source address ...
... prefix
that was allocated to the router at Site B, and Router A could verify
that the source address of the packet matches the prefix ...
... router, and
the ISP's router can verify that Site B is the only one that can
originate packets within the /48.
...
... IPv6 neighbor cache causing
disruption in communication between the two routers.
2. In router-to-router ...
... difficult to satisfy, because the traffic needing protection is not
necessarily (e.g., router-to-router tunnel) known a priori [RFC3884].
...
... difficult to satisfy, because the traffic needing protection is not
necessarily (e.g., router-to-router tunnel) known a priori [RFC3884].
...
...
The following SPD entries assume that there are two routers, Router1
and Router2, with tunnel endpoint IPv4 addresses ...
... Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms for IPv6 Hosts and Routers", RFC 4213prop, October 2005. ...
... Gilligan, R. and E. Nordmark, "Transition Mechanisms for IPv6 Hosts and Routers", RFC 2893(-> 4213prop), August 2000. ...
... The second approach can be made to work, but is only applicable in
host-to-host or site-to-router/router-to-site scenarios (i.e., when
the IPv6 prefixes ...
... host-to-host or site-to-router/router-to-site scenarios (i.e., when
the IPv6 prefixes can be known a priori), and it offers only a
...
... A.3. Specific SPD for Host-to-Router Scenario ...
... TEP1 and IPV4-TEP2, respectively. If the tunnel is between a router
and a host where the router ...
... bypass entry for host's SPD, absent in router's SPD.
While this might be an implementation matter for host-to-router ...
... router's SPD.
While this might be an implementation matter for host-to-router
tunneling, having a similar entry, "Local=IPV6 ...
...
This could be used (for example) by the host in the host-to-router
scenario to obtain an IPv6 address from the ISP ...