From nobody Fri Nov 24 12:40:26 2017 Return-Path: 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 4D0F01289C3 for ; Fri, 24 Nov 2017 12:40:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es 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 Hr2MzYvwgkfH for ; Fri, 24 Nov 2017 12:40:23 -0800 (PST) Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71751129329 for ; Fri, 24 Nov 2017 12:40:23 -0800 (PST) X-MDAV-Processed: mail.consulintel.com, Fri, 24 Nov 2017 21:36:19 +0100 Received: from mail.consulintel.es by mail.consulintel.com (Cipher TLSv1:-SHA:128) (MDaemon PRO v11.0.3) with ESMTP id md50000956356.msg for ; Fri, 24 Nov 2017 21:36:18 +0100 X-Spam-Processed: mail.consulintel.com, Fri, 24 Nov 2017 21:36:18 +0100 (not processed: spam filter heuristic analysis disabled) X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0) X-Return-Path: prvs=1501f01733=jordi.palet@consulintel.es X-Envelope-From: jordi.palet@consulintel.es X-MDaemon-Deliver-To: sunset4@ietf.org DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1511555777; x=1512160577; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=N8QCJDcY/K4KfCBo3DQtLep9h Le65IuilLFIcC7yQCk=; b=t7IAN+raFOXpCrOmHbQjUCCRdPL/aLFusXdl13GMu 2mjC1xUj6Bs3xgnNGJvGsxzM3DTa9GldgIsycXXfHvOpNLs5kTvl3tZKs1vBgOut kWsxURYthM6x2PtpxpnX+1S/0Ui5VfOjDV+pkFIxcix/7Zv5SrRqE+DvqlaBT+aw eY= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=cIfZSYBiNrp9kkfWF8J+Om3/75ATUeIdDJqY+ygyDJ+FnjTrDd+rUe0hv6i/ mUxJSTz5R8YrxiZCf1aU6pj8LZe2zVJM5stomV3c8WvGhUMt2KTMMIN4e tPS1ZLzkgW51Z2Eh9MEP0OXRMbys8/SdAg+WFzWJtGS2B3d2eswKjk=; X-MDAV-Processed: mail.consulintel.es, Fri, 24 Nov 2017 21:36:17 +0100 X-Spam-Processed: mail.consulintel.es, Fri, 24 Nov 2017 21:36:16 +0100 Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005637839.msg for ; Fri, 24 Nov 2017 21:36:15 +0100 X-Authenticated-Sender: jordi.palet@consulintel.es X-HashCash: 1:20:171124:md50005637839::kHds4xwnyE6xp0mU:00001qVJ User-Agent: Microsoft-MacOutlook/f.27.0.171010 Date: Fri, 24 Nov 2017 21:36:11 +0100 From: JORDI PALET MARTINEZ To: CC: , <6man@ietf.org>, Message-ID: Thread-Topic: New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> In-Reply-To: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.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: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 20:40:25 -0000 Hi, I=E2=80=99ve posted =E2=80=9CTowards a Worldwide IPv6-Ready DNS Infrastruct= ure=E2=80=9D https://datatracker.ietf.org/doc/draft-palet-sunset4-ipv6-ready-dns/ I believe this is covered by the charter of sunset4, however, it is very re= levant as well for a recent discussion in 6man and v6ops and of course, it = is relevant as well to dnsop. I will love to get some inputs. I order to avoid unnecessary noise in sever= al mail exploders, I will suggest responding only in sunset4. Regards, Jordi =20 -----Mensaje original----- De: Responder a: Fecha: viernes, 24 de noviembre de 2017, 21:30 Para: Jordi Palet Martinez , Jordi Martinez= Asunto: New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.= txt =20 A new version of I-D, draft-palet-sunset4-ipv6-ready-dns-00.txt has been successfully submitted by Jordi Palet Martinez and posted to t= he IETF repository. =20 Name: draft-palet-sunset4-ipv6-ready-dns Revision: 00 Title: Towards a Worldwide IPv6-Ready DNS Infrastructure Document date: 2017-11-23 Group: Individual Submission Pages: 4 URL: https://www.ietf.org/internet-drafts/draft-palet-sunset= 4-ipv6-ready-dns-00.txt Status: https://datatracker.ietf.org/doc/draft-palet-sunset4-ip= v6-ready-dns/ Htmlized: https://tools.ietf.org/html/draft-palet-sunset4-ipv6-re= ady-dns-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-palet-sunse= t4-ipv6-ready-dns-00 =20 =20 Abstract: This document defines the timing for implementing an IPv6-Ready global DNS infrastructure, worldwide, in order to allow the global IPv6-only deployment. =20 = =20 =20 =20 Please note that it may take a couple of minutes from the time of submi= ssion until the htmlized version and diff are available at tools.ietf.org. =20 The IETF Secretariat =20 =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. From nobody Fri Nov 24 12:50:57 2017 Return-Path: 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 6FA56127005 for ; Fri, 24 Nov 2017 12:50:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es 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 OVeIADfoZ4xO for ; Fri, 24 Nov 2017 12:50:50 -0800 (PST) Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAF4B1293E0 for ; Fri, 24 Nov 2017 12:50:49 -0800 (PST) X-MDAV-Processed: mail.consulintel.com, Fri, 24 Nov 2017 21:47:45 +0100 Received: from mail.consulintel.es by mail.consulintel.com (Cipher TLSv1:-SHA:128) (MDaemon PRO v11.0.3) with ESMTP id md50000956358.msg for ; Fri, 24 Nov 2017 21:47:43 +0100 X-Spam-Processed: mail.consulintel.com, Fri, 24 Nov 2017 21:47:43 +0100 (not processed: spam filter heuristic analysis disabled) X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0) X-Return-Path: prvs=1501f01733=jordi.palet@consulintel.es X-Envelope-From: jordi.palet@consulintel.es X-MDaemon-Deliver-To: sunset4@ietf.org DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1511556460; x=1512161260; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=vviGiOd48ye4ysI+uuDVxaZbi wUkxB109MI4gNsNhqs=; b=Hz92WdXCC+otnzLAgNvQXlYQDs1vAImtRoejYgf0d wNmxYRt+9CznmMkgAqps7N7GTF7BO7rj0tVdqPGx8REc6tFxUD9iQoCRbhSaYE8l 9FAKcs5j54zdrlex2XRQUnHBeNMnKKVvOT073yoS2c0nf98hiEcJ/0UznKdY4FCe bI= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=IHpd/kh4jaBLyhTTAEANFbMzVstEttpq6ofKUjj4f5ZdSSzXFIULv2XP6PRe O/ITDUYqcIEqQuqoWb7Tiy3knsrU+4ths8+lokHaN2UsQlfjtwkQ1a3b8 FQXC/FtCoD1DM28nZOXrscKjFt2GTbisHIyzFVl8yDLTa/HMAcgZDY=; X-MDAV-Processed: mail.consulintel.es, Fri, 24 Nov 2017 21:47:40 +0100 X-Spam-Processed: mail.consulintel.es, Fri, 24 Nov 2017 21:47:39 +0100 Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005637852.msg for ; Fri, 24 Nov 2017 21:47:38 +0100 X-Authenticated-Sender: jordi.palet@consulintel.es X-HashCash: 1:20:171124:md50005637852::FoYb/6uusNgsM10P:00005866 User-Agent: Microsoft-MacOutlook/f.27.0.171010 Date: Fri, 24 Nov 2017 21:47:33 +0100 From: JORDI PALET MARTINEZ To: CC: , <6man@ietf.org>, Message-ID: <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> Thread-Topic: New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Reply-To: jordi.palet@consulintel.es Archived-At: Subject: Re: [sunset4] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 20:50:51 -0000 By the way, forgot to mention something else. I=E2=80=99ve started also to work in a policy proposal for ICANN in order t= o make sure that we get aligned. Regards, Jordi =20 -----Mensaje original----- De: JORDI PALET MARTINEZ Fecha: viernes, 24 de noviembre de 2017, 21:36 Para: CC: , <6man@ietf.org>, Asunto: FW: New Version Notification for draft-palet-sunset4-ipv6-ready-dns= -00.txt Hi, =20 I=E2=80=99ve posted =E2=80=9CTowards a Worldwide IPv6-Ready DNS Infrast= ructure=E2=80=9D =20 https://datatracker.ietf.org/doc/draft-palet-sunset4-ipv6-ready-dns/ =20 I believe this is covered by the charter of sunset4, however, it is ver= y relevant as well for a recent discussion in 6man and v6ops and of course,= it is relevant as well to dnsop. =20 I will love to get some inputs. I order to avoid unnecessary noise in s= everal mail exploders, I will suggest responding only in sunset4. =20 Regards, Jordi =20 =20 =20 -----Mensaje original----- De: Responder a: Fecha: viernes, 24 de noviembre de 2017, 21:30 Para: Jordi Palet Martinez , Jordi Mart= inez Asunto: New Version Notification for draft-palet-sunset4-ipv6-ready-dns= -00.txt =20 =20 A new version of I-D, draft-palet-sunset4-ipv6-ready-dns-00.txt has been successfully submitted by Jordi Palet Martinez and posted = to the IETF repository. =20 Name: draft-palet-sunset4-ipv6-ready-dns Revision: 00 Title: Towards a Worldwide IPv6-Ready DNS Infrastructure Document date: 2017-11-23 Group: Individual Submission Pages: 4 URL: https://www.ietf.org/internet-drafts/draft-palet-su= nset4-ipv6-ready-dns-00.txt Status: https://datatracker.ietf.org/doc/draft-palet-sunset= 4-ipv6-ready-dns/ Htmlized: https://tools.ietf.org/html/draft-palet-sunset4-ipv= 6-ready-dns-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-palet-s= unset4-ipv6-ready-dns-00 =20 =20 Abstract: This document defines the timing for implementing an IPv6-Ready global DNS infrastructure, worldwide, in order to allow the glob= al IPv6-only deployment. =20 = =20 =20 =20 Please note that it may take a couple of minutes from the time of s= ubmission until the htmlized version and diff are available at tools.ietf.org= . =20 The IETF Secretariat =20 =20 =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. From nobody Fri Nov 24 19:01:10 2017 Return-Path: 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 94C7A1293FF for ; Fri, 24 Nov 2017 19:00:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu 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 X7u7ifHJtFoX for ; Fri, 24 Nov 2017 19:00:58 -0800 (PST) Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A65E1129479 for ; Fri, 24 Nov 2017 19:00:55 -0800 (PST) Received: by mail-pg0-x235.google.com with SMTP id 207so16369413pgc.12 for ; Fri, 24 Nov 2017 19:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=S6OI+0sSkj+VRF/0aZv1/01O1ZBFJQD/4HzKrMP9hSQ=; b=CTp3bvf5/vvskRESUNJullTiOrucoUGin166WIcswbQiwhsBydFkeRUGcnAMipH6Ho Kelgou5BTsvEgRt7Kd30dQEhepDI0jDVOvSxVhL6D0ClyKNH/+g/pPR2Ej/zo6EuxtMA A6iXAzNV0N3p9VJNcEOI21HWRvMI2w+CbNGy3hUOLna3OBYJiRbJet31RvJPH3pTwnMF eqjdmHUqkOTNimWT3oNXDRGZ2iXDwV9Pcnl0wPdHEUXaJxUKvzDjlsFrr1O9bf+SU0bL vEnsw8AnSnqLf8xaYL7UN9McLpo6bkI4DtSmYOdFBK7jJpf7ZqWWsqFoSUgHiW5zC/Lm qiqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=S6OI+0sSkj+VRF/0aZv1/01O1ZBFJQD/4HzKrMP9hSQ=; b=OzDqB1trPzErDTIxLj64h/DXA5BveLnmlxH4D0mp3NKVEHVvaEJDwwNK45dQjvjn6V mb3J7w26Qul1zT/zdAG2UQSeVUyj4EMEAE49dy80WSwuUb/xfWJs/kE9e9wnFEyVL4Tg SbzPRzf11rhv6+WywQkTr1A1y9ker/xQ2yUSxHJxvCpvkunn6aL8sr6KusapGTRObjZG OH3ZkAFmbdLIrbkkJAIUdld840C2OFMzoo8eo674gxBDaG0QvZLN/zYPJ30V9S8RTTdN eGOJsi1Ef7sPlI+ZcGrrCl4huKLJaFE3KN0LykCHQ2rhdMKKiEOuHDBgkzW8CudIqXOE SVaA== X-Gm-Message-State: AJaThX7qg7hVSG9AABu5T1qVj5HpGkkWFDRPH7yawS9RMrDNBzNcTkAO 51Ky8UCg2PlYjCtQ0CR0FU9dG4IbMCDgBQrgT9ik6g== X-Google-Smtp-Source: AGs4zMaz8jY/YxvgWIW491duqWEOydasFY4T+rtQMlsNNIb7vN/IVMo2Pr1Q5QERt02sT5VwAK2nZc+UK/eAtGCFRb4= X-Received: by 10.101.82.76 with SMTP id q12mr29896243pgp.140.1511578854927; Fri, 24 Nov 2017 19:00:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.139.5 with HTTP; Fri, 24 Nov 2017 19:00:54 -0800 (PST) In-Reply-To: References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> From: Bob Harold Date: Fri, 24 Nov 2017 22:00:54 -0500 Message-ID: To: jordi.palet@consulintel.es Cc: sunset4@ietf.org, IETF DNSOP WG , 6man@ietf.org, v6sop@ietf.org Content-Type: multipart/alternative; boundary="f403043e6878b2bd67055ec5e0b5" Archived-At: Subject: Re: [sunset4] [DNSOP] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 03:00:59 -0000 --f403043e6878b2bd67055ec5e0b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Nov 24, 2017 at 3:36 PM, JORDI PALET MARTINEZ < jordi.palet@consulintel.es> wrote: > Hi, > > I=E2=80=99ve posted =E2=80=9CTowards a Worldwide IPv6-Ready DNS Infrastru= cture=E2=80=9D > > https://datatracker.ietf.org/doc/draft-palet-sunset4-ipv6-ready-dns/ > > I believe this is covered by the charter of sunset4, however, it is very > relevant as well for a recent discussion in 6man and v6ops and of course, > it is relevant as well to dnsop. > > I will love to get some inputs. I order to avoid unnecessary noise in > several mail exploders, I will suggest responding only in sunset4. > > Regards, > Jordi > > > > -----Mensaje original----- > De: > Responder a: > Fecha: viernes, 24 de noviembre de 2017, 21:30 > Para: Jordi Palet Martinez , Jordi > Martinez > Asunto: New Version Notification for draft-palet-sunset4-ipv6- > ready-dns-00.txt > > > A new version of I-D, draft-palet-sunset4-ipv6-ready-dns-00.txt > has been successfully submitted by Jordi Palet Martinez and posted to > the > IETF repository. > > Name: draft-palet-sunset4-ipv6-ready-dns > Revision: 00 > Title: Towards a Worldwide IPv6-Ready DNS Infrastructure > Document date: 2017-11-23 > Group: Individual Submission > Pages: 4 > URL: https://www.ietf.org/internet- > drafts/draft-palet-sunset4-ipv6-ready-dns-00.txt > Status: https://datatracker.ietf.org/ > doc/draft-palet-sunset4-ipv6-ready-dns/ > Htmlized: https://tools.ietf.org/html/draft-palet-sunset4-ipv6- > ready-dns-00 > Htmlized: https://datatracker.ietf.org/ > doc/html/draft-palet-sunset4-ipv6-ready-dns-00 > > > Abstract: > This document defines the timing for implementing an IPv6-Ready > global DNS infrastructure, worldwide, in order to allow the global > IPv6-only deployment. > > As much as I would like to see the transition happen, Realistically, IPv4 will continue to 'work', for a large number of users, for a very long time. If you multiply your times by 10 (or more) and work hard, you might be successful in phasing out most of IPv4 in DNS. But forcing users to change seems like a bad idea. I note issues like: - Cloud providers (Amazon, Google, Azure?) only provide a private IPv4 address to virtual machines. They use NAT to get an IPv6 address for incoming traffic. I don't know of any way to do IPv6 outgoing. (I could be wrong, still learning here.) - Android does not support DHCPv6. - DNS64 breaks DNSSEC. - There are probably a large number of legacy hardware devices and software programs that do not support IPv6, but will still be running 10 or 20 years from now. I expect there are many more, but those come to mind. --=20 Bob Harold --f403043e6878b2bd67055ec5e0b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

= On Fri, Nov 24, 2017 at 3:36 PM, JORDI PALET MARTINEZ <= ;jordi.pale= t@consulintel.es> wrote:
Hi= ,

I=E2=80=99ve posted =E2=80=9CTowards a Worldwide IPv6-Ready DNS Infrastruct= ure=E2=80=9D

https://datatracker.ietf.org/doc/draft-palet-sunset4-ipv6-ready-dns/

I believe this is covered by the charter of sunset4, however, it is very re= levant as well for a recent discussion in 6man and v6ops and of course, it = is relevant as well to dnsop.

I will love to get some inputs. I order to avoid unnecessary noise in sever= al mail exploders, I will suggest responding only in sunset4.

Regards,
Jordi



-----Mensaje original-----
De: <internet-drafts@ietf.or= g>
Responder a: <internet-draft= s@ietf.org>
Fecha: viernes, 24 de noviembre de 2017, 21:30
Para: Jordi Palet Martinez <jordi.palet@theipv6company.com>, Jordi Martinez <jordi.palet@theipv6company.com>
Asunto: New Version Notification for draft-palet-sunset4-ipv6-ready-dn= s-00.txt


=C2=A0 =C2=A0 A new version of I-D, draft-palet-sunset4-ipv6-ready-dns= -00.txt
=C2=A0 =C2=A0 has been successfully submitted by Jordi Palet Martinez and p= osted to the
=C2=A0 =C2=A0 IETF repository.

=C2=A0 =C2=A0 Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0d= raft-palet-sunset4-ipv6-ready-dns
=C2=A0 =C2=A0 Revision:=C2=A0 =C2=A000
=C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Toward= s a Worldwide IPv6-Ready DNS Infrastructure
=C2=A0 =C2=A0 Document date:=C2=A0 =C2=A0 =C2=A0 2017-11-23
=C2=A0 =C2=A0 Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Indivi= dual Submission
=C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 4
=C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet-dr= afts/draft-palet-sunset4-ipv6-ready-dns-00.txt
=C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/draft-palet-su= nset4-ipv6-ready-dns/
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https://tools.ietf.org/html/draft-palet-sunset4-ipv6-ready-dns-00
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/html/draft-p= alet-sunset4-ipv6-ready-dns-00


=C2=A0 =C2=A0 Abstract:
=C2=A0 =C2=A0 =C2=A0 =C2=A0This document defines the timing for implementin= g an IPv6-Ready
=C2=A0 =C2=A0 =C2=A0 =C2=A0global DNS infrastructure, worldwide, in order t= o allow the global
=C2=A0 =C2=A0 =C2=A0 =C2=A0IPv6-only deployment.


As much as I would like to see the tra= nsition happen,
Realistically, IPv4 will continue to 'wo= rk', for a large number of users, for a very long time.
If yo= u multiply your times by 10 (or more) and work hard, you might be successfu= l in phasing out most of IPv4 in DNS.
But forcing users to change= seems like a bad idea.

I note issues like:
- Cloud providers (Amazon, Google, Azure?) only provide a private I= Pv4 address to virtual machines.=C2=A0 They use NAT to get an IPv6 address = for incoming traffic.=C2=A0 I don't know of any way to do IPv6 outgoing= .=C2=A0 (I could be wrong, still learning here.)
- Android do= es not support DHCPv6.
- DNS64 breaks DNSSEC.
- There a= re probably a large number of legacy hardware devices and software programs= that do not support IPv6, but will still be running 10 or 20 years from no= w.
I expect there are many more, but those come to mind.
<= /div>

--
Bob Harold

<= div>=C2=A0
--f403043e6878b2bd67055ec5e0b5-- From nobody Sat Nov 25 00:23:07 2017 Return-Path: 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 A2F1A120721 for ; Sat, 25 Nov 2017 00:23:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es 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 hpTT2cN45Ha7 for ; Sat, 25 Nov 2017 00:23:03 -0800 (PST) Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FA1F1204DA for ; Sat, 25 Nov 2017 00:23:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1511598181; x=1512202981; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=z0WOSEN23JpryePLUCScrtAuf Hqe1uDiPW6g50sud4c=; b=kwHdn5nqZbDP7DXgsG5xPH184cAbl2IJ87DRqEibX P6DO3ctYZhd1G4wiK005TFSRjQ3VVCAYZY/IHDUnLUgjsghGw5t3dNIR9QWRFWlI ij/rkqyd6CP4C6kra2lQ0YInVmV5yf6sBSX6QAyxE0B8R6P5q3IlgvfNwjcxUA00 f0= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=hL5YHw2hKBrKuFCCbIIu8s2OmxCjf9AyAcwTQbsTihoTbukaZD7Dc8I8JIRW 5b8YCp2ji5EavbnljoukcUJly5A32cQ2/ysIDNUPClt3ASSw8NmJJdIer QV2tTGDQCIHwwRJ+0lMHhR4rSIXJR2JuypuaPGX8nIaF6kJj5chKVA=; X-MDAV-Processed: mail.consulintel.es, Sat, 25 Nov 2017 09:23:01 +0100 X-Spam-Processed: mail.consulintel.es, Sat, 25 Nov 2017 09:23:01 +0100 Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005638106.msg for ; Sat, 25 Nov 2017 09:23:00 +0100 X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0) X-Authenticated-Sender: jordi.palet@consulintel.es X-HashCash: 1:20:171125:md50005638106::Lg5unZTnv8HVz/5p:00006Vg7 X-Return-Path: prvs=1502d71778=jordi.palet@consulintel.es X-Envelope-From: jordi.palet@consulintel.es X-MDaemon-Deliver-To: sunset4@ietf.org User-Agent: Microsoft-MacOutlook/f.27.0.171010 Date: Sat, 25 Nov 2017 09:22:56 +0100 From: JORDI PALET MARTINEZ To: Message-ID: <9C93DF10-7059-45AF-930F-EC2684ED5EF5@consulintel.es> Thread-Topic: [sunset4] [DNSOP] FW: New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Reply-To: jordi.palet@consulintel.es Archived-At: Subject: Re: [sunset4] [DNSOP] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 08:23:05 -0000 Hi Bob, The lack of DHCPv6 doesn=E2=80=99t present a problem for the transition or = IPv6 support, in fact is in cellular networks where IPv6 is more predominan= t. For DNS64, you will see in my document this is one of the reasons for calli= ng to this action. In the =E2=80=9CDNS world=E2=80=9D I doubt there are legacy =E2=80=9Cserver= s=E2=80=9D or =E2=80=9Cdevices=E2=80=9D that don=E2=80=99t support IPv6. If= a =E2=80=9CDNS=E2=80=9D provider or a =E2=80=9Chosting provider=E2=80=9D o= r =E2=80=9Ccloud provider=E2=80=9D is unable to do IPv6 in two years from n= ow, do all the rest of the citizens need to pay the cost of upgrading his n= etwork or only their own customers? Do we want that those services stay as IPv4 for 10 years? Or Maybe 20 or 40= if we don=E2=80=99t take an action to let them know that the Internet serv= ices need to be IPv6-Ready ? Please note that I fully agree that at every office, every home, there are = IPv4 devices or apps that will never work with IPv4, and actually I don=E2= =80=99t care about that (even I wish is not the case). If the servers where= those devices need to access are IPv6-Ready, then 464XLAT/NAT64 will work = without breaking DNSSEC, so we bypass that problem. Regards, Jordi =20 =20 As much as I would like to see the transition happen,=20 =20 Realistically, IPv4 will continue to 'work', for a large number of user= s, for a very long time. If you multiply your times by 10 (or more) and work hard, you might be = successful in phasing out most of IPv4 in DNS. But forcing users to change seems like a bad idea. =20 =20 I note issues like: - Cloud providers (Amazon, Google, Azure?) only provide a private IPv4 = address to virtual machines. They use NAT to get an IPv6 address for incom= ing traffic. I don't know of any way to do IPv6 outgoing. (I could be wro= ng, still learning here.) =20 - Android does not support DHCPv6. - DNS64 breaks DNSSEC. - There are probably a large number of legacy hardware devices and soft= ware programs that do not support IPv6, but will still be running 10 or 20 = years from now. =20 I expect there are many more, but those come to mind. =20 =20 --=20 =20 Bob Harold =20 =20 =20 =20 =20 =20 _______________________________________________ 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. From nobody Sat Nov 25 11:00:34 2017 Return-Path: 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 25C73128891; Sat, 25 Nov 2017 11:00:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 9paqs2D-qo6W; Sat, 25 Nov 2017 11:00:26 -0800 (PST) Received: from mail-ot0-x244.google.com (mail-ot0-x244.google.com [IPv6:2607:f8b0:4003:c0f::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B94E1288B8; Sat, 25 Nov 2017 11:00:24 -0800 (PST) Received: by mail-ot0-x244.google.com with SMTP id s12so21163295otc.0; Sat, 25 Nov 2017 11:00:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=7FXK9Hbsy2NvXHbs21RXBKze0r25JhyaY220NVjBj5I=; b=H08aUilHx4bXp2Hh0gIcaZoj7DH4LEzaYRSrkUkaaJqq+8g9i9Eja7uui7aAOZcBPU zEqRo+Q0xKXVh0AYWwCaZWxB31HxQzhSxlkzbi6Ml1iM2hacw37UrqM1qZglp2PAd4Gg SN7HoXpsQ4XDQeJBJts3EjpcfjqrLdmz0biq8RtuB1mjeujp8XlN7x5DjVT5m8j7BbOx 6ThPnVJZ/f6hAixHRwZO4/aTJdOl/lS6aoO6M1r239okM123vyHUD01Jm+KmLiVWpjS7 UMGGw86fCqhfYTEic0BpUN0rPVpVKzbq5K50+VBi7dCt+CTL/w8Nl4ZuLYAUhWFj+pxn ht+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=7FXK9Hbsy2NvXHbs21RXBKze0r25JhyaY220NVjBj5I=; b=JNVBpkRZMeM7+lSj1Z1UEtvPAMo9vMxrwqLSEArQx35wqS9WiTEBOXDMxJXlpnGWd9 F00NCzerxoMNdKSv3TLl9BSmnmyGO76xpAcEAlI/9+RcssLWWkcU+Cgm42XuPV44Uf2P ho7S6DYkjH3m13s/6OM45SYecJ6YQ8197q+aAjLTrp3+vZa5ThPCqbkE+4EvPcrvw/fP 5iHmsV5plG33yF1vTh30vfWP7ePaGgWJSE33lcTVY5y6UdDTa7K6D53vL3afix1CxN6T 5VFbKbu0An0XCTX5TeaA06x1LEdUW6qnedPYbbEbIh30+oMo8L5uaGP3F1RLnhqVBsHh XBDQ== X-Gm-Message-State: AJaThX6dd9F9DXJ96l0wOUIQXmFzDBzNupct/chou/PqSvChS+F0Veri HWzAxEXybOkRulE6jTYYWZ6aTkU/ X-Google-Smtp-Source: AGs4zMap2WjSCeEO/jMKuSU/gFUaQSpFW6ZlyMVAM2Twr+rhUsBEcgT83oV89mem4er0KDiZWw7j+A== X-Received: by 10.157.25.42 with SMTP id j42mr6903047ota.348.1511636423695; Sat, 25 Nov 2017 11:00:23 -0800 (PST) Received: from ?IPv6:2600:8802:5600:f7a::1019? ([2600:8802:5600:f7a::1019]) by smtp.gmail.com with ESMTPSA id j9sm6648182oth.31.2017.11.25.11.00.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Nov 2017 11:00:22 -0800 (PST) From: Fred Baker Message-Id: <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com> Content-Type: multipart/signed; boundary="Apple-Mail=_560B97F8-4746-470D-A2C3-5112656EC11E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Date: Sat, 25 Nov 2017 11:00:19 -0800 In-Reply-To: <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> Cc: sunset4@ietf.org, dnsop@ietf.org, 6man@ietf.org, "v6ops@ietf.org WG" , Daniel Karrenberg To: JORDI PALET MARTINEZ References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [sunset4] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 19:00:28 -0000 --Apple-Mail=_560B97F8-4746-470D-A2C3-5112656EC11E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Nov 24, 2017, at 12:47 PM, JORDI PALET MARTINEZ = wrote: >=20 > I=E2=80=99ve 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. --Apple-Mail=_560B97F8-4746-470D-A2C3-5112656EC11E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAloZvcQACgkQEhdRnd2G P+B0HhAAjOpoPOzOOJXgAKPM0i+bCxze23Cgl90TFT2eAgiMRXCgEgKd+70ExW1J CPfwnQd2TL7iB9erucbaD9EnPyZMLatSUjxydKoGiX4E0Niq7teXlhFREG2a+VZS 3gCoTvQremntqZ9pO8yckaxPjh3BXKE5GCwTdqa4S+X0oPe8oafBnVkqBFy/xJso QGIsPad25z8tQW/sYSh3j4lE52Hwwts6+YzNtw/J7c9Qytm3gCI+YBJ6/wv1Zp7R esUN0kSja2Le21JxARNNkDygFx8tyxUq/FIjU/Gtca+AsFHHOdXxq/zR6RMcfAnM a3xIHTocm0QzjsbiTJBs6HalyY7Xb3EnllBW+L/nEe1UDeqkDP77rmkAhP5hBsVl wSyaA6reEkpURDNCHDbseRlL7Mt/erIrJe1TfJQCw3B0r3ooD843LqLHiFOPcxbB gG0eDipbG72SfitohFsgD7N5PGae0j7b3yazvy+meaQJoD4RFcZQoOUmwV+xq4be iYHGLtBvuuUVOA0Te0tqxAj/hUeuAb2jIdYZcCsyYFr/u33A6K9SM6rnAOeyujrh oxznyI022Jrs7MspncO9DqwDk3w9m2Bi89RfKSp/FrpPT5FVl8+CsitZDsW0cQl3 F5QMvWuPKB0N8GY5vt1fycTbRpCmtZzVQojBkaKOg8mG0G2J4s8= =REKM -----END PGP SIGNATURE----- --Apple-Mail=_560B97F8-4746-470D-A2C3-5112656EC11E-- From nobody Sat Nov 25 15:46:18 2017 Return-Path: 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 82903127B60 for ; Sat, 25 Nov 2017 15:45:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca 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 qvzwQkTFZAUo for ; Sat, 25 Nov 2017 15:45:58 -0800 (PST) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EF73127F0E for ; Sat, 25 Nov 2017 15:45:56 -0800 (PST) Received: by mail-io0-x22d.google.com with SMTP id 79so25188833ioi.3 for ; Sat, 25 Nov 2017 15:45:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=G68r27NadI28O8vYjtH//gET3CZW+SX2XoXu1ua3LRE=; b=CEtOEOTGignHqylyzb5I3+sdWFyLric1tR/xzVhR/XLCofdhRmjla3pb33GOtreXYt RL8bLkRskJFrnhY9hAHHm67ZYPvI5vxNoYZxWp2u0T0c2zYo1P6SfQtObk3BkkYANAJv MM8UzCvyHugcEiKaG6fAsisX4zsN4C8TiR20M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=G68r27NadI28O8vYjtH//gET3CZW+SX2XoXu1ua3LRE=; b=KSQS2SZYm7by1FQBuowgHA1jVQG54RZEfL6f/iOqBBJ2IMBpgnpL7XH6K2MliM20Ct RmM29jCberWWegyT6Dm5WpYUpO1pqLj4FJD38wBLZZg4Kr8JCha1EEid8N5iiwIVDorr ShWrOqZveyiptbGBq7UHMpxpeMYaRWpBENjr1RsSkZ5XGljK3raExzqcf3IqW0iWosy7 GB/xCoVqrimNrWFZ7dAHJgmZb9w8mdBw5b6Usb6CV2hdH9VZGqM8LrpJsQiAzBVuju47 zre6b7KjNye0Ss8spYum3wK4EGgqe1VE1Z4khE5wgH3A0bOEj1D/1LJYuKeWSNpGMEtM WMBQ== X-Gm-Message-State: AJaThX4NPYld7Tmu+B+bjv/rmYZEalsMUT/eC+uYzKsMTq5UpDevTVe4 DBzUChMmoSreBiNaEdsC4JaSxMDQumw= X-Google-Smtp-Source: AGs4zMbuRuIyKP/D80dRHyhwqCglS6QhrQo/TjEnWpoLtqQlKH9iFxgSB1ppUYbpr6Ed2iGhafyx9Q== X-Received: by 10.107.198.84 with SMTP id w81mr37726401iof.151.1511653555568; Sat, 25 Nov 2017 15:45:55 -0800 (PST) Received: from ?IPv6:2607:f2c0:101:3:b07e:ddeb:fe18:44cf? (node-131dv5j4grjd2zso9b.ipv6.teksavvy.com. [2607:f2c0:101:3:b07e:ddeb:fe18:44cf]) by smtp.gmail.com with ESMTPSA id q6sm4972037ita.38.2017.11.25.15.45.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Nov 2017 15:45:53 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) From: Joe Abley X-Mailer: iPad Mail (15B202) In-Reply-To: <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com> Date: Sat, 25 Nov 2017 18:45:52 -0500 Cc: JORDI PALET MARTINEZ , dnsop@ietf.org, 6man@ietf.org, Daniel Karrenberg , "v6ops@ietf.org WG" , sunset4@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com> To: Fred Baker Archived-At: Subject: Re: [sunset4] [DNSOP] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 23:45:59 -0000 Hi Fred, [I haven't read Jordi's draft; I'm just responding to what I've read in this= thread.] On Nov 25, 2017, at 14:00, Fred Baker wrote: > One thing you might want to think about: the root servers are all IPv6-cap= able 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 hol= ding the burden of proof that the infrastructure isn't capable of IPv6-only o= peration today. monster:~]% egrep -c '^[A-Z]' /usr/share/misc/iso3166=20 249 [monster:~]%=20 There are potentially 249 TLDs that are not operated under any such contract= with ICANN, although I agree that the majority of ccTLDs have at least one n= ameserver that is v6-capable (maybe all, but I haven't checked and I wouldn'= t want to assume). The important clients for all of these authoritative servers from the perspe= ctive of end-users are resolvers. I think it's uncontroversial to suggest wi= thout citation that not all resolvers used by end-users today are v6-capable= , or downstream from a resolver that is v6-capable. So we are not ready to t= urn off v4 today unless significant collateral damage is considered acceptab= le (and surely it's not). This is a relatively small problem to solve, though (note use of "relatively= "). I think it would actually be practical to announce a sunset for v4 on gT= LD and root servers at some suitable target date in the not too distant futu= re, the implementation of which could be mainly handled within the root zone= itself. Aside from the techno-political v6-deployment motivations, I think there wou= ld be good engineering reasons to sunset v4 in root and TLD servers. Such a move would open the door to the complete removal of v4 transport from= all of those servers which would eliminate them as viable amplifiers in att= acks against v4 targets. It would also provide greater motivation to deal wi= th any unreliability in v6 operations in the DNS or connecting networks, fra= gmentation-related transport issues, etc which will surely otherwise see min= imal attention so long as working v4 transport masks v6 problems. Joe= From nobody Sun Nov 26 01:06:51 2017 Return-Path: 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 2252A1293DB for ; Sun, 26 Nov 2017 01:06:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es 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 PeCNMViLH9aj for ; Sun, 26 Nov 2017 01:06:48 -0800 (PST) Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE841120725 for ; Sun, 26 Nov 2017 01:06:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1511687203; x=1512292003; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=KQXBvs8rFV/nOKz66ZT0X1N8F GQOjj92OKdgL7rPuMM=; b=aJ2aB/Ksmx/mhI03siETS/XZLaHtd91mnhxvvf0Ss zDB/pRJWZWerCZYAKgaC9GfaRR9qtVgXGe7+ZdMABG4fpN+aXLAna8pG2VNQVsHw p2MmDbFkS4GLCiPLMCu+E2j9qclrUJHX4pbauSRZ8JLhGDvRrCglqj5x85wTPDmp v8= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=FSWoo2e2gwzp3J0Qc8IBuPgXMNNVuID2HjhfKMxSz63IJNHDU1CyvCRejhTZ Qk70pobu2oj0zphEhv46WBSghrF2W5qcv3c+JEmyLvw5ISDmWmuQg4HrD xNWi9OYb4RXEYfIBwO/UaTrzCBGT1kfEb7TFyFMpZCDsLUCgm136Dg=; X-MDAV-Processed: mail.consulintel.es, Sun, 26 Nov 2017 10:06:43 +0100 X-Spam-Processed: mail.consulintel.es, Sun, 26 Nov 2017 10:06:42 +0100 Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005638797.msg for ; Sun, 26 Nov 2017 10:06:40 +0100 X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0) X-Authenticated-Sender: jordi.palet@consulintel.es X-HashCash: 1:20:171126:md50005638797::DqQmhl6KF7zPHgXs:000022/t X-Return-Path: prvs=1503e18523=jordi.palet@consulintel.es X-Envelope-From: jordi.palet@consulintel.es X-MDaemon-Deliver-To: sunset4@ietf.org User-Agent: Microsoft-MacOutlook/f.27.0.171010 Date: Sun, 26 Nov 2017 10:06:36 +0100 From: JORDI PALET MARTINEZ To: CC: Daniel Karrenberg 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> <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: Subject: Re: [sunset4] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 09:06:50 -0000 (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 en nombre de Fred Baker Responder a: Fecha: s=C3=A1bado, 25 de noviembre de 2017, 20:01 Para: JORDI PALET MARTINEZ CC: , <6man@ietf.org>, Daniel Karrenberg , "v6ops@ietf.org WG" , 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 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. From nobody Sun Nov 26 01:21:14 2017 Return-Path: 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 8A0BD1293D9 for ; Sun, 26 Nov 2017 01:21:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es 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 wnU6NKo_QQiE for ; Sun, 26 Nov 2017 01:21:11 -0800 (PST) Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E94B4120721 for ; Sun, 26 Nov 2017 01:21:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1511688064; x=1512292864; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=5zm0amV/EbtSaM/xWFPtEQxAl 3fWlllZ+2OAbwn9ojc=; b=O1G1MOJhkGfgbOHFM1z/XHaZvwdMZMjgNlwBZEn3Y JfheQcFJfqygwY368CWmI1cmTlOtNSyF3gXnN+1cm8T6WVJ2DvEJZ09Tot6357W2 hKH2vI0a+d0fIvFl82u5fSMrfO05CiVNAUqOrluqbfPYUX0u6Oa8d2A6qeBgi4kK ak= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=R5GMOVdzOSPZwt9O+4zl0MagquAZATorUwBA+Hnzf6GJNTEcoKgPqkhrx4yp AEKU9nLs+GM4qc84Es5j8jMWEOPVKe6NPt0ShbENYkuEb0m3nUajYVEfH VUb5VL9j3hWuT9sVCnTxq7ukruMXgXznbtQd3nuayX2LyKspzkAOLI=; X-MDAV-Processed: mail.consulintel.es, Sun, 26 Nov 2017 10:20:59 +0100 X-Spam-Processed: mail.consulintel.es, Sun, 26 Nov 2017 10:20:57 +0100 Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005638812.msg for ; Sun, 26 Nov 2017 10:20:48 +0100 X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0) X-Authenticated-Sender: jordi.palet@consulintel.es X-HashCash: 1:20:171126:md50005638812::Jqhau2aUC5bQD02e:00005a46 X-Return-Path: prvs=1503e18523=jordi.palet@consulintel.es X-Envelope-From: jordi.palet@consulintel.es X-MDaemon-Deliver-To: sunset4@ietf.org User-Agent: Microsoft-MacOutlook/f.27.0.171010 Date: Sun, 26 Nov 2017 10:20:40 +0100 From: JORDI PALET MARTINEZ To: CC: Daniel Karrenberg Message-ID: <42D899A2-9220-4689-971B-9C064F98C05B@consulintel.es> Thread-Topic: [sunset4] [DNSOP] New Version Notification for draft-palet-sunset4-ipv6-ready-dns-00.txt References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com> <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> In-Reply-To: <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Reply-To: jordi.palet@consulintel.es Archived-At: Subject: Re: [sunset4] [DNSOP] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 09:21:12 -0000 Hi Joe, As I just mention, it is pity that the ccTLDs can opt-out that policy. What I don=E2=80=99t think is that, if the gTLDs have such requirement in t= he contract, they are actually enforcing it? Do you have pointers to relevant documents to understand what are the exact= requirements and why is not being enforced? My perspective is that end-users, in their LANs, will have IPv4 for a while= , but the access may turn into IPv6-only sooner. End-users have devices suc= h as IP cameras and many others, that cost money, and they will not be sent= to the trash can in several years (5-10 years?). So even if the resolvers = aren=E2=80=99t IPv6-capable, is not an issue, but want we need to avoid is = the situation of having a service in Internet which is NOT-IPv6 enabled and= breaks (example breaks DNSSEC) using the transition mechanism required for= having an IPv6-only access but IPv4 support in the LAN (for example 464XLA= T with NAT64). The same solution I=E2=80=99m proposing, actually helps to h= ave IPv6-only LANs, of course, so in the way to a complete IPv6-only Intern= et. I think including in my ID a sunset for IPv4 in root and TLDs (again even i= f ccTLDs can opt-out), is interesting and definitively will be an extra =E2= =80=9Cpush=E2=80=9D in the right direction. I will include that in a new ve= rsion. I think we can have something like this: 1. Root and TLDs MUST be IPv6-Ready in 6 months. 2. Authoritative NS MUST be IPv6-Ready in 12 months. 3. Root and TLDs MUST drop IPv4 support in 15 months. 4. DNSSEC authoritative MUST be IPv6-Ready in 18 months. 5. Other A RRs, MUST be IPv6-Ready in 24 months. 6. Other RRs, MUST be IPv6-Ready in 30 months. If you don=E2=80=99t mind, I will steal your technical motivations in my te= xt, I didn=E2=80=99t considered initially in my document extending too much= in the =E2=80=9Ctechnical=E2=80=9D reasons, but it looks like a better way= to justify the need for this additional step. Regards, Jordi =20 -----Mensaje original----- De: sunset4 en nombre de Joe Abley Responder a: Fecha: domingo, 26 de noviembre de 2017, 0:47 Para: Fred Baker CC: "v6ops@ietf.org WG" , <6man@ietf.org>, Daniel Karrenber= g , , , JORDI PALE= T MARTINEZ Asunto: Re: [sunset4] [DNSOP] New Version Notification for draft-palet-suns= et4-ipv6-ready-dns-00.txt Hi Fred, =20 [I haven't read Jordi's draft; I'm just responding to what I've read in= this thread.] =20 On Nov 25, 2017, at 14:00, Fred Baker wrote: =20 > One thing you might want to think about: the root servers are all IPv= 6-capable today and serve requests using IPv6, and the 1541 TLDs are all re= quired by contract with ICANN to be IPv6-capable. I think you'll find yours= elf holding the burden of proof that the infrastructure isn't capable of IP= v6-only operation today. =20 monster:~]% egrep -c '^[A-Z]' /usr/share/misc/iso3166=20 249 [monster:~]%=20 =20 There are potentially 249 TLDs that are not operated under any such con= tract with ICANN, although I agree that the majority of ccTLDs have at leas= t one nameserver that is v6-capable (maybe all, but I haven't checked and I= wouldn't want to assume). =20 The important clients for all of these authoritative servers from the p= erspective of end-users are resolvers. I think it's uncontroversial to sugg= est without citation that not all resolvers used by end-users today are v6-= capable, or downstream from a resolver that is v6-capable. So we are not re= ady to turn off v4 today unless significant collateral damage is considered= acceptable (and surely it's not). =20 This is a relatively small problem to solve, though (note use of "relat= ively"). I think it would actually be practical to announce a sunset for v4= on gTLD and root servers at some suitable target date in the not too dista= nt future, the implementation of which could be mainly handled within the r= oot zone itself. =20 Aside from the techno-political v6-deployment motivations, I think ther= e would be good engineering reasons to sunset v4 in root and TLD servers. =20 Such a move would open the door to the complete removal of v4 transport= from all of those servers which would eliminate them as viable amplifiers = in attacks against v4 targets. It would also provide greater motivation to = deal with any unreliability in v6 operations in the DNS or connecting netwo= rks, fragmentation-related transport issues, etc which will surely otherwis= e see minimal attention so long as working v4 transport masks v6 problems. =20 =20 Joe _______________________________________________ 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. From nobody Mon Nov 27 01:44:12 2017 Return-Path: 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 To: JORDI PALET MARTINEZ 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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? From nobody Mon Nov 27 01:46:18 2017 Return-Path: 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 3B114127B5A; Mon, 27 Nov 2017 01:46:11 -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 NKTG00pevSS8; Mon, 27 Nov 2017 01:46:10 -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 41D24127B31; Mon, 27 Nov 2017 01:46:10 -0800 (PST) Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D3ADF280B8D; Mon, 27 Nov 2017 10:46:08 +0100 (CET) Received: by mx4.nic.fr (Postfix, from userid 500) id CC459281DB4; Mon, 27 Nov 2017 10:46:08 +0100 (CET) Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id C566D280B8D; Mon, 27 Nov 2017 10:46:08 +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 C1FB76423520; Mon, 27 Nov 2017 10:46:08 +0100 (CET) Received: by b12.nic.fr (Postfix, from userid 1000) id BBB9540034; Mon, 27 Nov 2017 10:46:08 +0100 (CET) Date: Mon, 27 Nov 2017 10:46:08 +0100 From: Stephane Bortzmeyer To: Bob Harold Cc: jordi.palet@consulintel.es, IETF DNSOP WG , 6man@ietf.org, v6sop@ietf.org, sunset4@ietf.org Message-ID: <20171127094608.2usyoujtzv2k5unx@nic.fr> References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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.000003, version=1.2.2 X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.11.27.93916 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 09:46:11 -0000 On Fri, Nov 24, 2017 at 10:00:54PM -0500, Bob Harold wrote a message of 203 lines which said: > - DNS64 breaks DNSSEC. That's not a fair summary. People should read RFC 6147 and 7050 before repeating this. From nobody Mon Nov 27 01:50:38 2017 Return-Path: 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 6AB1B127B31; Mon, 27 Nov 2017 01:50:26 -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 W3Z5t_x6om7d; Mon, 27 Nov 2017 01:50:25 -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 EBCF6127419; Mon, 27 Nov 2017 01:50:24 -0800 (PST) Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 87349281E21; Mon, 27 Nov 2017 10:50:23 +0100 (CET) Received: by mx4.nic.fr (Postfix, from userid 500) id 7ED78281E66; Mon, 27 Nov 2017 10:50:23 +0100 (CET) Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 77DA9281E21; Mon, 27 Nov 2017 10:50:23 +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 74B9D6423520; Mon, 27 Nov 2017 10:50:23 +0100 (CET) Received: by b12.nic.fr (Postfix, from userid 1000) id 6E6BC40034; Mon, 27 Nov 2017 10:50:23 +0100 (CET) Date: Mon, 27 Nov 2017 10:50:23 +0100 From: Stephane Bortzmeyer To: Joe Abley Cc: Fred Baker , "v6ops@ietf.org WG" , 6man@ietf.org, Daniel Karrenberg , dnsop@ietf.org, sunset4@ietf.org Message-ID: <20171127095023.tv7bu2mmemj6su4d@nic.fr> References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com> <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> 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.000000, version=1.2.2 X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.11.27.93916 Archived-At: Subject: Re: [sunset4] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 09:50:26 -0000 On Sat, Nov 25, 2017 at 06:45:52PM -0500, Joe Abley wrote a message of 28 lines which said: > I think it's uncontroversial to suggest without citation that not > all resolvers used by end-users today are v6-capable, See this experience . It was three years ago, we can re-run it but I'm afraid it will show that it is still the case. Quote: "As expected, the success rate with IPv6-only domain names (around two thirds) is much lower than with "mixed" domain names. We are not yet ready to switch off IPv4 . If you serve a domain name only on IPv6 name servers, you will get less traffic (and probably less spam, too)." From nobody Mon Nov 27 04:28:36 2017 Return-Path: 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 6366A128961; Mon, 27 Nov 2017 04:28:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 PTWoYauQKwH6; Mon, 27 Nov 2017 04:28:20 -0800 (PST) Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (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 6C330124D37; Mon, 27 Nov 2017 04:28:20 -0800 (PST) X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus Received: from grey.csi.cam.ac.uk ([131.111.57.57]:40409) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1eJIWG-000LA0-1X (Exim 4.89) (return-path ); Mon, 27 Nov 2017 12:28:16 +0000 Date: Mon, 27 Nov 2017 12:28:16 +0000 From: Tony Finch To: Joe Abley cc: Fred Baker , "v6ops@ietf.org WG" , 6man@ietf.org, Daniel Karrenberg , dnsop@ietf.org, sunset4@ietf.org In-Reply-To: <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> Message-ID: References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com> <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Archived-At: Subject: Re: [sunset4] [v6ops] [DNSOP] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 12:28:22 -0000 Joe Abley wrote: > > There are potentially 249 TLDs that are not operated under any such > contract with ICANN, although I agree that the majority of ccTLDs have > at least one nameserver that is v6-capable (maybe all, but I haven't > checked and I wouldn't want to assume). Quick root zone stats: zones 1542 servers 4216 Most servers are dual-stacked; 539 are v4-only, and 2 are v6-only (j.zdnscloud.com and i.zdnscloud.com). The 31 TLDs with no v6 nameservers: ai. bb. bh. ck. dj. fk. gf. hm. kp. mh. mil. mp. mq. mv. ni. pf. pk. sl. sr. st. to. uz. ws. xn--l1acc. xn--lgbbat1ad8j. xn--mgba3a4f16a. xn--mgbai9azgqp6j. xn--wgbh1c. xn--ygbi2ammx. ye. zw. Tony. -- f.anthony.n.finch http://dotat.at/ - I xn--zr8h punycode Biscay, Fitzroy: Variable 3 or 4 until later in south, otherwise westerly 5 or 6, veering northwesterly 4 or 5, except in south Fitzroy, becoming northeasterly 5 or 6 in southeast Fitzroy. Slight at first in south, ohterwise moderate or rough. Rain or squally showers. Moderate or good. From nobody Mon Nov 27 09:59:02 2017 Return-Path: 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 CF9DD128D69 for ; Mon, 27 Nov 2017 09:58:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable 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 2ggjXfOdR9PR for ; Mon, 27 Nov 2017 09:58:49 -0800 (PST) Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54BFE1292C5 for ; Mon, 27 Nov 2017 09:58:49 -0800 (PST) X-Original-To: sunset4@ietf.org Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 3235542A0B for ; Mon, 27 Nov 2017 18:58:47 +0100 (CET) X-SpaceNet-Relay: true X-SpaceNet-Relay: true X-SpaceNet-Relay: true X-SpaceNet-Relay: true X-SpaceNet-Relay: true X-SpaceNet-Relay: true X-SpaceNet-Relay: true Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 1F86341B96; Mon, 27 Nov 2017 18:58:47 +0100 (CET) Received: by moebius4.space.net (Postfix, from userid 1007) id 10D791BFA7; Mon, 27 Nov 2017 18:58:47 +0100 (CET) Date: Mon, 27 Nov 2017 18:58:46 +0100 From: Gert Doering To: Tony Finch Cc: Joe Abley , "v6ops@ietf.org WG" , 6man@ietf.org, Daniel Karrenberg , dnsop@ietf.org, sunset4@ietf.org Message-ID: <20171127175846.GH45648@Space.Net> References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <2E863078-8E32-4657-B1F4-0417A0C95A05@consulintel.es> <18C3DFC8-45B9-4C41-8151-ACA840F00518@gmail.com> <9B47C38D-B446-466F-BE88-DD09E40814B3@hopcount.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-NCC-RegID: de.space User-Agent: Mutt/1.8.2 (2017-04-18) Archived-At: Subject: Re: [sunset4] [v6ops] [DNSOP] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 17:58:52 -0000 Hi, On Mon, Nov 27, 2017 at 12:28:16PM +0000, Tony Finch wrote: > The 31 TLDs with no v6 nameservers: [..] > mil. Yay. Like, IPv6 mandate, and all that. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 From nobody Mon Nov 27 14:30:02 2017 Return-Path: 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 9D380127077; Mon, 27 Nov 2017 14:30:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.901 X-Spam-Level: X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 KH2S5UzUOr9Z; Mon, 27 Nov 2017 14:29:59 -0800 (PST) Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 25D081200C5; Mon, 27 Nov 2017 14:29:59 -0800 (PST) Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id E7B8C3B9A22; Mon, 27 Nov 2017 22:29:56 +0000 (UTC) Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id A758E160048; Mon, 27 Nov 2017 22:29:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8FC53160070; Mon, 27 Nov 2017 22:29:56 +0000 (UTC) Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8uek7jRJZ179; Mon, 27 Nov 2017 22:29:56 +0000 (UTC) Received: from [172.30.42.89] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 9A94C160048; Mon, 27 Nov 2017 22:29:54 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Mark Andrews In-Reply-To: <20171127094608.2usyoujtzv2k5unx@nic.fr> Date: Tue, 28 Nov 2017 09:29:51 +1100 Cc: Bob Harold , IETF DNSOP WG , 6man@ietf.org, v6sop@ietf.org, sunset4@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <04ECB158-1EF1-4CEF-937F-65048B10F2F5@isc.org> References: <151155545267.9162.17152586924934799206.idtracker@ietfa.amsl.com> <20171127094608.2usyoujtzv2k5unx@nic.fr> To: Stephane Bortzmeyer X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [sunset4] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 22:30:01 -0000 DNS64 requires EVERY validating client to support DNS64 prefix discover = and implement DNS64. If that isn=E2=80=99t breaks DNSSEC I don=E2=80=99t = know what is. > On 27 Nov 2017, at 8:46 pm, Stephane Bortzmeyer = wrote: >=20 > On Fri, Nov 24, 2017 at 10:00:54PM -0500, > Bob Harold wrote=20 > a message of 203 lines which said: >=20 >> - DNS64 breaks DNSSEC. >=20 > That's not a fair summary. People should read RFC 6147 and 7050 > before repeating this. >=20 > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- --=20 Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org