DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
 c=simple; q=dns; h=from:message-id;
 b=FSWoo2e2gwzp3J0Qc8IBuPgXMNNVuID2HjhfKMxSz63IJNHDU1CyvCRejhTZ
 Qk70pobu2oj0zphEhv46WBSghrF2W5qcv3c+JEmyLvw5ISDmWmuQg4HrD
 xNWi9OYb4RXEYfIBwO/UaTrzCBGT1kfEb7TFyFMpZCDsLUCgm136Dg=;
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Sun, 26 Nov 2017 10:06:36 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <sunset4@ietf.org>
CC: Daniel Karrenberg <daniel@karrenberg.net>
Message-ID: <54BE124A-EBAB-43B3-A405-0BAC35E09A4D@consulintel.es>
Thread-Topic: [sunset4] New Version Notification for
 draft-palet-sunset4-ipv6-ready-dns-00.txt
References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com>
 <B0A6AF83-099A-4D4D-83EB-BA4B45D00353@consulintel.es>
 <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es>
 <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com>
In-Reply-To: <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/HrWCTgjRzANLI0zAoOBg3YSXoFc>
Subject: Re: [sunset4] New Version Notification for
 draft-palet-sunset4-ipv6-ready-dns-00.txt
Precedence: list

(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 =E2=80=9Creinforce it=E2=80=9D, because I don=E2=80=
=99t think there is any IETF document that mandates it, so at this way we e=
nsure that IPv6 support is not =E2=80=9Cdropped=E2=80=9D in a root in the f=
uture (looks silly, but just in case). Also at this way if there is such do=
cument, we have a =E2=80=9Csingle on=E2=80=9D that include all the DNS leve=
ls.

I tried to find an ICANN document that states it before writing the draft, =
but google didn=E2=80=99t helped. Right now, doing some new searches, I fou=
nd 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 =
=E2=80=A6 However, if we make it happen in a couple of years for all but a =
few ccTLDs, that=E2=80=99s a great success. Even more, ccTLDs frequently ha=
ve copies among themselves, so for example .es, .cl, .fr, which are IPv6 en=
abled, 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 =E2=80=A6 I didn=E2=80=99t want to say SLD=
s, 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 kno=
w SLD or 3LD), but they know =E2=80=9Canything that has an A record =E2=80=
=A6=E2=80=9D so I used =E2=80=9COther A RRs, MUST be IPv6-Ready in 24 month=
s=E2=80=9D, and before that I spell out =E2=80=9CIPv6-Ready=E2=80=9D as=20

=E2=80=9CIPv6-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.=E2=80=9D

I guess that if you didn=E2=80=99t get that in my ID, I need to do some cla=
rification in the text =E2=80=A6

I=E2=80=99m an ATLAS ambassador and I=E2=80=99ve about 100 million credits,=
 so I guess it will be easy to use them for this very interesting measureme=
nt, 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, an=
d checks as I mention in the draft not just the availability and reachabili=
ty of AAAA, but also PMTUD/fragmentation, and I will say in both TCP and UD=
P. 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
=20

-----Mensaje original-----
De: sunset4 <sunset4-bounces@ietf.org> en nombre de Fred Baker <fredbaker.i=
etf@gmail.com>
Responder a: <fredbaker.ietf@gmail.com>
Fecha: s=C3=A1bado, 25 de noviembre de 2017, 20:01
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: <dnsop@ietf.org>, <6man@ietf.org>, Daniel Karrenberg <daniel@karrenberg=
.net>, "v6ops@ietf.org WG" <v6ops@ietf.org>, <sunset4@ietf.org>
Asunto: Re: [sunset4] New Version Notification for draft-palet-sunset4-ipv6=
-ready-dns-00.txt

   =20
   =20
    > On Nov 24, 2017, at 12:47 PM, JORDI PALET MARTINEZ <jordi.palet@consu=
lintel.es> wrote:
    >=20
    > I=E2=80=99ve started also to work in a policy proposal for ICANN in o=
rder to make sure that we get aligned.
   =20
    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 requ=
ired by contract with ICANN to be IPv6-capable. I think you'll find yoursel=
f holding the burden of proof that the infrastructure isn't capable of IPv6=
-only operation today.
   =20
    RSO statistics are available from http://www.root-servers.org/. ICANN T=
LDs are at https://data.iana.org/TLD/tlds-alpha-by-domain.txt.
   =20
    Reading through your draft, what I see that is probably not present tod=
ay is an IPv6 address for every SLD, which is to say names like "example.co=
m".
   =20
    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 docum=
entation on how to do one yourself) would be to set up a RIPE Atlas study t=
hat accesses the Root, ccTLD, and gTLD authoritative servers using their IP=
v6 addresses and reports on the status of that from a wide variety of locat=
ions.
    _______________________________________________
    sunset4 mailing list
    sunset4@ietf.org
    https://www.ietf.org/mailman/listinfo/sunset4
   =20



**********************************************
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 con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.