On Fri, Nov 24, 2017 at 3:36 PM, JORDI PALET MARTINEZ < jordi.pa...@consulintel.es> wrote:
> Hi, > > I’ve posted “Towards a Worldwide IPv6-Ready DNS Infrastructure” > > https://datatracker.ietf.org/doc/draft-palet-sunset4-ipv6-ready-dns/ > > I believe this is covered by the charter of sunset4, however, it is very > relevant as well for a recent discussion in 6man and v6ops and of course, > it is relevant as well to dnsop. > > I will love to get some inputs. I order to avoid unnecessary noise in > several mail exploders, I will suggest responding only in sunset4. > > Regards, > Jordi > > > > -----Mensaje original----- > De: <internet-dra...@ietf.org> > Responder a: <internet-dra...@ietf.org> > Fecha: viernes, 24 de noviembre de 2017, 21:30 > Para: Jordi Palet Martinez <jordi.pa...@theipv6company.com>, Jordi > Martinez <jordi.pa...@theipv6company.com> > Asunto: New Version Notification for draft-palet-sunset4-ipv6- > ready-dns-00.txt > > > A new version of I-D, draft-palet-sunset4-ipv6-ready-dns-00.txt > has been successfully submitted by Jordi Palet Martinez and posted to > the > IETF repository. > > Name: draft-palet-sunset4-ipv6-ready-dns > Revision: 00 > Title: Towards a Worldwide IPv6-Ready DNS Infrastructure > Document date: 2017-11-23 > Group: Individual Submission > Pages: 4 > URL: https://www.ietf.org/internet- > drafts/draft-palet-sunset4-ipv6-ready-dns-00.txt > Status: https://datatracker.ietf.org/ > doc/draft-palet-sunset4-ipv6-ready-dns/ > Htmlized: https://tools.ietf.org/html/draft-palet-sunset4-ipv6- > ready-dns-00 > Htmlized: https://datatracker.ietf.org/ > doc/html/draft-palet-sunset4-ipv6-ready-dns-00 > > > Abstract: > This document defines the timing for implementing an IPv6-Ready > global DNS infrastructure, worldwide, in order to allow the global > IPv6-only deployment. > > As much as I would like to see the transition happen, Realistically, IPv4 will continue to 'work', for a large number of users, for a very long time. If you multiply your times by 10 (or more) and work hard, you might be successful in phasing out most of IPv4 in DNS. But forcing users to change seems like a bad idea. I note issues like: - Cloud providers (Amazon, Google, Azure?) only provide a private IPv4 address to virtual machines. They use NAT to get an IPv6 address for incoming traffic. I don't know of any way to do IPv6 outgoing. (I could be wrong, still learning here.) - Android does not support DHCPv6. - DNS64 breaks DNSSEC. - There are probably a large number of legacy hardware devices and software programs that do not support IPv6, but will still be running 10 or 20 years from now. I expect there are many more, but those come to mind. -- Bob Harold
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
