On Fri, Nov 24, 2017 at 09:36:11PM +0100, JORDI PALET MARTINEZ <jordi.pa...@consulintel.es> wrote a message of 54 lines which said:
> I’ve posted “Towards a Worldwide IPv6-Ready DNS Infrastructure” > > https://datatracker.ietf.org/doc/draft-palet-sunset4-ipv6-ready-dns/ Besides the good remarks on ccTLDs that you already had (management of ccTLDs is not ICANN's business), a few remarks: > In general, that means having AAAA RRs in addition to A RRs, > ensuring that PMTUD works correctly and fragmentation is correctly > handled. The problem is that it is not entirely in the hands of the manager of the DNS authoritative server: the problem may be on the client side. And it is hard for the sysadmin of an authoritative DNS server to know if his clients received the fragments. > 1. Root and TLDs MUST be IPv6-Ready in 6 months. The ICANN root is IPv6-ready for a long time. Otherwise, the experience of Yeti draft-song-yeti-testbed-experience might be useful. > 2. Authoritative NS MUST be IPv6-Ready in 12 months. At every level in the DNS tree? Noble goal but which seems completely unrealistic. How will you convince Joe User, who manages the NS for foo.bar.example.com to act? _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
