Re: [DNSOP] New Version Notification for draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt

Alain Durand <alain.durand@icann.org> Tue, 03 November 2015 10:39 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 907411B31B7; Tue, 3 Nov 2015 02:39:01 -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 0sG9tAow4DLA; Tue, 3 Nov 2015 02:39:00 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 674BF1B31B5; Tue, 3 Nov 2015 02:39:00 -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 02:38:58 -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 02:38:58 -0800
From: Alain Durand <alain.durand@icann.org>
To: Tony Finch <dot@dotat.at>
Thread-Topic: [DNSOP] New Version Notification for draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt
Thread-Index: AQHRFUd7foUpK2I9C0GX0e+YjfXiOZ6KoOwA//8lnDiAAALnEIAAYkeAgABs5ID//4SGbA==
Date: Tue, 03 Nov 2015 10:38:56 +0000
Message-ID: <6B7CD8BA-4627-4196-B65D-2043ECDF8D5E@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>, <alpine.LSU.2.00.1511030958410.25050@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1511030958410.25050@hermes-2.csi.cam.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/mUkjX1SIRkBqou7jU2z35us0ZLY>
Cc: Brian Haberman <brian@innovationslab.net>, "dnsop@ietf.org" <dnsop@ietf.org>, Joel Jaeggli <joelja@bogus.com>, "Fred Baker (fred)" <fred@cisco.com>, "sunset4@ietf.org" <sunset4@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>, "Ebersman, Paul" <Paul_Ebersman@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 10:39:01 -0000


> On Nov 3, 2015, at 7:01 PM, Tony Finch <dot@dotat.at> wrote:
> 
> 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.
> 
> But there needs to be a specification for interop between the CPE and the
> ISP's network, so the ISP knows which suppliers they can buy equipment from.

Exactly. This is specified in each of the various IPv4aas docs, as I pointed out earlier, along with the other things the CPE and the device on the ISP side must agree to do, such as packet format, address/port syntax, etc...

Alain