[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A slightly more detailed analysis Re: NAT64 and IPsec support
George Tsirtsis wrote :
The scenarios you describe below require a box that can receive an
IPv6 tunnel from one side and forward the encapsulated IPv4 traffic
on the other side. This could also be combined with a v4NAT for
efficient use of IPv4 addresses, but in now way this requires
protocol translation.
IPv6/IPv4 Node ======= TunnelEndPoint+v4NAT -------- IPv4 only node
A configuration with similar properties is covered in:
http://www.ietf.org/internet-drafts/draft-despres-v6ops-apbp-00.txt
The configuration, where APBP means Address-port-borrowing-protocol,
looks like:
Dual-stack node+APBP ======= APBP ===== IPv4-only node
- No NAT is needed (E2E transport connections are transparent IPv4
between applications)
- TUNNELS v4 over v6 are etablished "per connection", with a request to
an anycast address to find each APBP tunnel endpoint.
Another important configuration is:
IPv4-only node ------- v4NAT+APBP ======= APBP ------- IPv4 node
... such a function would make sense to be collocated in a NAT64 box,
but it has nothing to do with an IPv6 to IPv4 protocol translation
as such.
Right.
With APBP, the v4NAT+APBP function also can be collocated in a NAT64 box.
The need for NAT64 is however mitigated if APBP is available.
(Comments most welcome.)
Regards.
Rémi