Deploying IPv6 XLAT64

Wed Sep 26 18:24:51 UTC 2018

This document, which is already in the IESG review, may answer your question:

https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/

Also take a look into this one:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/

Remember that if your enterprise network has apps that use literals, or they don't support IPv6, you still need dual-stack in the LANs, but access IPv6-only is just fine.

Regards,
Jordi

-----Mensaje original-----
De: Matt Hoppes <mattlists at rivervalleyinternet.net>
Fecha: miércoles, 26 de septiembre de 2018, 15:22
Para: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>, North American Network Operators' Group <nanog at nanog.org>
Asunto: Re: Deploying IPv6 XLAT64

    Thanks... that is what I don't understand:  Why is NAT64 such a 
    difficult concept to put into routers and firewalls?  We already do NAT 
    with IPv4 just fine.

    I feel like IPv6 adoption would be much faster if there was a transition 
    mechanism other than dual stacking.

    Think: Corporate offices.  Rather than renumbering everything inside, 
    they just turn on NAT64 and now they can begin a slow and controlled 
    transition.

    On 9/26/18 2:19 PM, JORDI PALET MARTINEZ wrote:
    > You can use Jool for both 464XLAT and just NAT64.
    > 
    > I've done a workshop on this at the LACNIC meeting this week. See slides 43 and next ones:
    > 
    > http://www.lacnic.net/innovaportal/file/3139/1/ipv6-only_v11_16-9.pdf
    > 
    > Saludos,
    > Jordi
    >   
    >   
    > 
    > -----Mensaje original-----
    > De: NANOG <nanog-bounces at nanog.org> en nombre de Matt Hoppes <mattlists at rivervalleyinternet.net>
    > Fecha: miércoles, 26 de septiembre de 2018, 15:03
    > Para: North American Network Operators' Group <nanog at nanog.org>
    > Asunto: Deploying IPv6 XLAT64
    > 
    >      Looking at getting into IPv6 here ourselves... one of the big hold ups
    >      has been the dual stacking.
    >      
    >      Can anyone recommend a quality, not ridiculously convoluted to setup,
    >      XLAT64 translator that we could run in our network to take the IPv6 to
    >      an IPv4 address when the remote server doesn't have 6 capability?
    >      
    > 
    > 
    > 
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    > 
    > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
    > 
    > 
    > 

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.