Re: [DNSOP] New Version Notification for draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt
Alain Durand <alain.durand@icann.org> Tue, 03 November 2015 09:26 UTC
Return-Path: <alain.durand@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E4B1B30D5; Tue, 3 Nov 2015 01:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level:
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aXs7YB0JMwHP; Tue, 3 Nov 2015 01:26:52 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B0131B30D1; Tue, 3 Nov 2015 01:26:52 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 3 Nov 2015 01:26:49 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1044.021; Tue, 3 Nov 2015 01:26:49 -0800
From: Alain Durand <alain.durand@icann.org>
To: "Ebersman, Paul" <Paul_Ebersman@cable.comcast.com>
Thread-Topic: [DNSOP] New Version Notification for draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt
Thread-Index: AQHRFUd7foUpK2I9C0GX0e+YjfXiOZ6KoOwA//8lnDiAAALnEIAAYkeAgABWqgCAAAyxAA==
Date: Tue, 03 Nov 2015 09:26:49 +0000
Message-ID: <06FFD2AE-04A6-466D-8D58-415A1B552C71@icann.org>
References: <20151102074846.14431.30976.idtracker@ietfa.amsl.com> <D25D44C3.1913B8%john_brzozowski@cable.comcast.com> <D25E5E26.1916A1%john_brzozowski@cable.comcast.com> <20151103052757.DAF2D3BBB299@rock.dv.isc.org> <20151103053711.A9AF43BBB46A@rock.dv.isc.org> <D25DD742.AF98%alain.durand@icann.org> <737F9831-0823-42CB-B6CE-19CD1E256532@cable.comcast.com>
In-Reply-To: <737F9831-0823-42CB-B6CE-19CD1E256532@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.236]
Content-Type: multipart/signed; boundary="Apple-Mail=_EFB9A84C-E7AA-41A5-B0C6-7710A5AFE341"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/wa9QUAwjTVZWrBHbO6bMbREJoyI>
Cc: Brian Haberman <brian@innovationslab.net>, "dnsop@ietf.org" <dnsop@ietf.org>, Joel Jaeggli <joelja@bogus.com>, Fred Baker <fred@cisco.com>, "sunset4@ietf.org" <sunset4@ietf.org>, "Brzozowski, John" <John_Brzozowski@cable.comcast.com>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [DNSOP] New Version Notification for draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 03 Nov 2015 09:26:53 -0000
> On Nov 3, 2015, at 3:41 AM, Ebersman, Paul <Paul_Ebersman@cable.comcast.com> wrote: > > > On 03Nov, 2015, at 5:31 PM, Alain Durand <alain.durand@icann.org> wrote: > >> In the particular case of the communication between the CPE and the ISP >> DNS recursive resolver, the two parties are within the same administrative >> authority. Thus, the need to make a BCP is much lower. This can be seen >> as simply an implementation issue. In other words, there are other >> solutions that could be used, for example a translation of the DNS packets >> from IPv4 to IPv6. Such a translation may or may not be optimal, but it >> would work and, more importantly, would not break the DNS resolution and >> would have no impact on the stability of the DNS system as a whole. > > Putting in a second DNS server that does nothing but forward everything just to > translate v4 to v6 does indeed have an impact on stability if you try to do it > at large scale. It impacts infrastructure costs, performance and potentlally confuses > geo-ip/cdn. It also adds complexity in debugging. I was talking about doing the translation in the CPE. But, the larger point is, this was just an example of something else that could be done, although, I agree, sub-optimally. What draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt proposes is reasonable, no objections. However, as far as I know, this is already being documented by the various IPv4aas solutions. Alain.
- Re: [DNSOP] New Version Notification for draft-jj… Brzozowski, John
- Re: [DNSOP] New Version Notification for draft-jj… Alain Durand
- Re: [DNSOP] New Version Notification for draft-jj… Mark Andrews
- Re: [DNSOP] New Version Notification for draft-jj… Mark Andrews
- Re: [DNSOP] New Version Notification for draft-jj… Brzozowski, John
- Re: [DNSOP] New Version Notification for draft-jj… Brzozowski, John
- Re: [DNSOP] New Version Notification for draft-jj… Brzozowski, John
- Re: [DNSOP] New Version Notification for draft-jj… Alain Durand
- Re: [DNSOP] New Version Notification for draft-jj… Ebersman, Paul
- Re: [DNSOP] New Version Notification for draft-jj… Alain Durand
- Re: [DNSOP] New Version Notification for draft-jj… Tony Finch
- Re: [DNSOP] New Version Notification for draft-jj… Alain Durand
- Re: [DNSOP] New Version Notification for draft-jj… Brzozowski, John