Re: [DNSOP] New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt
Shane Kerr <shane@time-travellers.org> Mon, 27 November 2017 10:31 UTC
Return-Path: <shane@time-travellers.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B13D312714F for <dnsop@ietfa.amsl.com>; Mon, 27 Nov 2017 02:31:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id coPVWyTcS7E0 for <dnsop@ietfa.amsl.com>; Mon, 27 Nov 2017 02:31:34 -0800 (PST)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8AFC1250B8 for <dnsop@ietf.org>; Mon, 27 Nov 2017 02:31:34 -0800 (PST)
Received: from exit-01a.noisetor.net ([173.254.216.66] helo=[127.0.0.1]) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1eJGjk-0001xm-6W; Mon, 27 Nov 2017 10:34:04 +0000
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: dnsop@ietf.org
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> <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> <57628d3a-93ef-567d-09ca-a2b37112a544@time-travellers.org> <20171127095212.dkdgl5dkqn56arvh@nic.fr>
From: Shane Kerr <shane@time-travellers.org>
Message-ID: <5abc6b0f-face-a777-22c7-fe3d3afeea96@time-travellers.org>
Date: Mon, 27 Nov 2017 10:31:00 +0000
MIME-Version: 1.0
In-Reply-To: <20171127095212.dkdgl5dkqn56arvh@nic.fr>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/x3Gq_aFLwie2_C_3fIKqc6Bab-E>
Subject: Re: [DNSOP] New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Nov 2017 10:31:37 -0000
Stephane, Stephane Bortzmeyer: > On Mon, Nov 27, 2017 at 09:32:00AM +0000, > Shane Kerr <shane@time-travellers.org> wrote > a message of 45 lines which said: > >> I just ran a check, and there are 23 TLD without any name servers >> that support IPv6. > > Can you detail the methodology? For instance, did you measure what the > root announces (the glue records), what the TLD announces (the > authoritative AAAA records) or the reality (actual answers to DNS > requets over IPv6). I cleaned it up a bit and put it on GitHub: https://github.com/shane-kerr/tldIPv6 In the README.md: "Next it goes through each TLD and does an NS lookup to get the authoritative list of name servers. It then tries each name server returned until it finds one with an AAAA record. If none of the name servers for a TLD have an AAAA record, then it is reported as not supporting IPv6." It wouldn't be too difficult to add checks to see that IPv6 works for at least one of the AAAA returned, but I was mostly just looking to see if each TLD is trying to provide IPv6, not how good of a job they are doing at it (although the results file does log TLD that fail to resolve at all, but that's a side effect of the process). :) Cheers, -- Shane
- [DNSOP] FW: New Version Notification for draft-pa… JORDI PALET MARTINEZ
- Re: [DNSOP] New Version Notification for draft-pa… JORDI PALET MARTINEZ
- Re: [DNSOP] FW: New Version Notification for draf… Bob Harold
- Re: [DNSOP] New Version Notification for draft-pa… Fred Baker
- Re: [DNSOP] New Version Notification for draft-pa… Joe Abley
- Re: [DNSOP] New Version Notification for draft-pa… Shane Kerr
- Re: [DNSOP] FW: New Version Notification for draf… Stephane Bortzmeyer
- Re: [DNSOP] FW: New Version Notification for draf… Stephane Bortzmeyer
- Re: [DNSOP] New Version Notification for draft-pa… Stephane Bortzmeyer
- Re: [DNSOP] New Version Notification for draft-pa… Stephane Bortzmeyer
- Re: [DNSOP] New Version Notification for draft-pa… Shane Kerr
- Re: [DNSOP] [v6ops] New Version Notification for … Tony Finch
- Re: [DNSOP] [v6ops] New Version Notification for … Shane Kerr
- Re: [DNSOP] [v6ops] New Version Notification for … Tony Finch
- Re: [DNSOP] [v6ops] New Version Notification for … Stephane Bortzmeyer
- Re: [DNSOP] [v6ops] New Version Notification for … Gert Doering
- Re: [DNSOP] New Version Notification for draft-pa… Mark Andrews
- Re: [DNSOP] New Version Notification for draft-pa… Mark Andrews