Re: [sunset4] FW: New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 27 November 2017 09:44 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15447127B73; Mon, 27 Nov 2017 01:44:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 jR3mSPTR7SJ0; Mon, 27 Nov 2017 01:44:01 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9FAE127B5A; Mon, 27 Nov 2017 01:44:01 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 5A09E280B8D; Mon, 27 Nov 2017 10:43:59 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id 53274281DB4; Mon, 27 Nov 2017 10:43:59 +0100 (CET)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 4C216280B8D; Mon, 27 Nov 2017 10:43:59 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 48B086423520; Mon, 27 Nov 2017 10:43:59 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 3D50F40034; Mon, 27 Nov 2017 10:43:59 +0100 (CET)
Date: Mon, 27 Nov 2017 10:43:59 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: sunset4@ietf.org, dnsop@ietf.org, 6man@ietf.org, v6sop@ietf.org
Message-ID: <20171127094359.z3asfj72vvur27pr@nic.fr>
References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <FB517F47-9660-4DFF-BD4F-276F91227394@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <FB517F47-9660-4DFF-BD4F-276F91227394@consulintel.es>
X-Operating-System: Debian GNU/Linux 9.2
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000077, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.11.27.93316
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/xx8gqg5IJBeMjaU9Ng0HQb9-ZH0>
Subject: Re: [sunset4] FW: New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Nov 2017 09:44:05 -0000

On Fri, Nov 24, 2017 at 09:36:11PM +0100,
 JORDI PALET MARTINEZ <jordi.palet@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?