Subject: Re: [sunset4] New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt
From: JORDI PALET MARTINEZ <[email-masked]>
To: <[email-masked]>
Cc: Daniel Karrenberg <[email-masked]>
Date: Sun, 26 Nov 2017 10:06:36 +0100
List-Id: sunset4 working group discussion list <sunset4.ietf.org>

(keeping the discussion in sunset4, as I believe is where it belongs to)

Hi Fred,

Thanks a lot for reading and providing input!

I know the root servers are IPv6 enables since many years ago, however, in my document I want to “reinforce it”, because I don’t think there is any IETF document that mandates it, so at this way we ensure that IPv6 support is not “dropped” in a root in the future (looks silly, but just in case). Also at this way if there is such document, we have a “single on” that include all the DNS levels.

I tried to find an ICANN document that states it before writing the draft, but google didn’t helped. Right now, doing some new searches, I found this:

https://www.icann.org/resources/pages/ipv6-initiative-2017-02-28-en

So, it looks like only the ccTLDcan opt-out that rule, which is very sad … However, if we make it happen in a couple of years for all but a few ccTLDs, that’s a great success. Even more, ccTLDs frequently have copies among themselves, so for example .es, .cl, .fr, which are IPv6 enabled, may backup .sv which is not (is just an example, not saying this is the case, but lots of them do this way).

Regarding SLD, I actually say it … I didn’t want to say SLDs, 3LDs, and so on, because they may be many extra levels, and I wanted to cover all the with a more simpler terminology (I think many folks don't know SLD or 3LD), but they know “anything that has an A record …” so I used “Other A RRs, MUST be IPv6-Ready in 24 months”, and before that I spell out “IPv6-Ready” as 

“IPv6-Ready DNS Infrastructure" means that a DNS
   server (root, TLD, authoritative NS) is fully accessible and
operational if queried from a remote dual-stack and IPv6-only
   network.

   In general, that means having AAAA RRs in addition to A RRs, ensuring
   that PMTUD works correctly and fragmentation is correctly handled.

   In case DNSSEC is implemented with IPv4, it MUST support also
   IPv6-only operation according the below defined timing.”

I guess that if you didn’t get that in my ID, I need to do some clarification in the text …

I’m an ATLAS ambassador and I’ve about 100 million credits, so I guess it will be easy to use them for this very interesting measurement, we just need to restart those measurements and if needed readjust what it was done before, to make sure that works in an IPv6-only environment, and checks as I mention in the draft not just the availability and reachability of AAAA, but also PMTUD/fragmentation, and I will say in both TCP and UDP. I also think that the community and/or RIPE NCC will be happy to provide more credits/resources for something like this if needed.

Regards,
Jordi

-----Mensaje original-----
De: sunset4 <[email-masked]> en nombre de Fred Baker <[email-masked]>
Responder a: <[email-masked]>
Fecha: sábado, 25 de noviembre de 2017, 20:01
Para: JORDI PALET MARTINEZ <[email-masked]>
CC: <[email-masked]>, <[email-masked]>, Daniel Karrenberg <[email-masked]>, "[email-masked] WG" <[email-masked]>, <[email-masked]>
Asunto: Re: [sunset4] New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt

    
    > On Nov 24, 2017, at 12:47 PM, JORDI PALET MARTINEZ <[email-masked]> wrote:
    > 
    > I’ve started also to work in a policy proposal for ICANN in order to make sure that we get aligned.
    
    One thing you might want to think about: the root servers are all IPv6-capable today and serve requests using IPv6, and the 1541 TLDs are all required by contract with ICANN to be IPv6-capable. I think you'll find yourself holding the burden of proof that the infrastructure isn't capable of IPv6-only operation today.
    
    RSO statistics are available from http://www.root-servers.org/. ICANN TLDs are at https://data.iana.org/TLD/tlds-alpha-by-domain.txt.
    
    Reading through your draft, what I see that is probably not present today is an IPv6 address for every SLD, which is to say names like "example.com".
    
    What might be worth your while (I copy Daniel because he did a similar study using RIPE Atlas not too long ago and can point you to relevant documentation on how to do one yourself) would be to set up a RIPE Atlas study that accesses the Root, ccTLD, and gTLD authoritative servers using their IPv6 addresses and reports on the status of that from a wide variety of locations.
    _______________________________________________
    sunset4 mailing list
    [email-masked]
    https://www.ietf.org/mailman/listinfo/sunset4

**********************************************
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.