[BEHAVE] New I-D: IPv4/IPv6 Translator for IPv4-Only Networks

Folks,

at the IPv4/IPv6 co-existence interim, Alain and I had sketched a
translation-based IPv4/IPv6 interworking method that, unlike other
translation-based solution proposals, is for deployment in IPv4
networks.  Here is now a more detailed specification of this method,
which we call "Virtual IPv6 Connectivity for IPv4-only networks":

http://tools.ietf.org/html/draft-vogt-durand-virtual-ip6-connectivity

Recall from the interim:  The main advantage of Virtual IPv6
Connectivity is that it does not require extra global IPv4 addresses.
We hence believe that the method will be of advantage when (a) the pool
of unallocated IPv4 addresses is exhausted, and (b) there is sufficient
IPv6 deployment to make it worthwhile for IPv4 networks to invest into
IPv4/IPv6 interworking.  Consequently, Virtual IPv6 Connectivity is not
intended to replace any other solution proposal.  It is instead intended
to complement other solution proposals in a future where the impetus to
invest into IPv4/IPv6 interworking has shifted from the IPv6 side to the
IPv4 side.

Furthermore, Virtual IPv6 Connectivity can already today solve some of
the key problem scenarios, namely those involving IPv6 clients and IPv4
servers in the absence of a unique global IPv4 addresses for each
server.  An example is scenario (4) in Mark's and Jari's analysis [1].

Finally, we would like to request a presentation slot for Virtual IPv6
Connectivity at IETF 73.  Dan and Dave, I am assuming this would be in
the BEHAVE session, right?

Thanks everybody.

- Christian, for Alain and Christian

[1] http://tools.ietf.org/html/draft-arkko-townsley-coexistence

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave