Re: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 12 July 2018 15:56 UTC

Return-Path: <prvs=1731875ab0=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C06F130F02 for <v6ops@ietfa.amsl.com>; Thu, 12 Jul 2018 08:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 xDDjRoXhjpyO for <v6ops@ietfa.amsl.com>; Thu, 12 Jul 2018 08:56:37 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8D1B130EA7 for <v6ops@ietf.org>; Thu, 12 Jul 2018 08:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1531410994; x=1532015794; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type; bh=cBgPpb2/pFHR4OqGYNSAxv NpwLyWL53ippf4Jdt8PMM=; b=ryOZ+npmCylRaq+32LuQehpHGojft93hEpZXZj vXMrSqNCoANjSDpKvNVGAT/Fy35rMDQ4cGCiUxF9rhGpH/pZCpanWJ/mNX1IehEJ KGk+lUUAppEB6O50//Hofwq64OuSVe4C4OoimRIC1qSyGNTIrtJRj0lMmoaaAoYL boZXs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 12 Jul 2018 17:56:34 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 12 Jul 2018 17:56:34 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50005810812.msg for <v6ops@ietf.org>; Thu, 12 Jul 2018 17:56:33 +0200
X-MDRemoteIP: 2001:470:1f09:495:5132:8a59:5167:a07e
X-MDHelo: [10.10.10.99]
X-MDArrival-Date: Thu, 12 Jul 2018 17:56:33 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1731875ab0=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.f.0.180709
Date: Thu, 12 Jul 2018 17:56:29 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "Rajiv Asati (rajiva)" <rajiva=40cisco.com@dmarc.ietf.org>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Gert Doering <gert@space.net>, KOSSUT Tomasz O-PL <tomasz.kossut@orange.com>
CC: "nick.heatley@bt.com" <nick.heatley@bt.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <1E4DFE85-4B9D-4BD7-9956-4D2F66B8A94F@consulintel.es>
Thread-Topic: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments
References: <CAD6AjGQqaQumYyBPVG6qkc9cs+jSGFKgUnGHkMfJmtes5Fk47g@mail.gmail.com> <AD5D4A8E-8A02-463B-A222-3D32A6235DF4@gmail.com> <CAD6AjGQsDq1ELdZPnaAtbZPq5SZoXbD--W5JS5tkN63J1D=W9g@mail.gmail.com> <2F5CCC76-4364-4B66-B956-199969CFFCB4@isc.org> <LO1P123MB009802AF44568758A8A3ECB4EA410@LO1P123MB0098.GBRP123.PROD.OUTLOOK.COM> <3fa26b65c7c64eada0ae04caa0a94ddf@orange.com> <20180712130103.GQ11393@Space.Net> <787AE7BB302AE849A7480A190F8B93302DF599FE@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <2B33FCAF-C612-45FC-AA9F-7F087F164937@cisco.com>
In-Reply-To: <2B33FCAF-C612-45FC-AA9F-7F087F164937@cisco.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3614262989_577259618"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Me1JpGzzIG642d1SIXQ8c895bYQ>
Subject: Re: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 15:56:40 -0000

If there is a CLAT, you don’t need synthesis. The impact is that the CLAT will do always NAT46, for any IPv4 destination, so in cellular devices, there may be some extra battery impact.

 

If you want to have synthesis, the safer approach is doing it in the “end-device”, this way even if this device is a DNSSEC validator, will not create a trouble. This is the way RFC8305 (HEv2) is using for literals.


Regards,

Jordi

 

 

 

De: v6ops <v6ops-bounces@ietf.org> en nombre de "Rajiv Asati (rajiva)" <rajiva=40cisco.com@dmarc.ietf.org>
Fecha: jueves, 12 de julio de 2018, 17:50
Para: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Gert Doering <gert@space.net>, KOSSUT Tomasz O-PL <tomasz.kossut@orange.com>
CC: "nick.heatley@bt.com" <nick.heatley@bt.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Asunto: Re: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments

 

Med, 

 

A-AAAA address synthesis without DNS64 usage??   

 

-- 

Cheers,

Rajiv 

 

 

From: v6ops <v6ops-bounces@ietf.org> on behalf of "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Date: Thursday, July 12, 2018 at 9:45 AM
To: Gert Doering <gert@space.net>, KOSSUT Tomasz O-PL <tomasz.kossut@orange.com>
Cc: "nick.heatley@bt.com" <nick.heatley@bt.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments

 

Hi Gert, 

 

No surprise out there: Address synthesis on the handset (CLAT) + NAT64 at the network side.

 

Cheers,

Med

 

-----Message d'origine-----

De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de Gert Doering

Envoyé : jeudi 12 juillet 2018 15:01

À : KOSSUT Tomasz O-PL

Cc : nick.heatley@bt.com; v6ops@ietf.org

Objet : Re: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments

Hi,

On Tue, Jul 10, 2018 at 01:29:41PM +0000, Kossut Tomasz - Hurt wrote:

> So far DNS64 is mandatory for iOS.

> 

> Orange Poland is running IPv6-only mobile network without DNS64 since 2012.

So how do their customers reach all those ipv4-only websites out there,

like github.com?

(I'm all for having IPv6-only things, but as long as the rest of the world

is dragging their feet, between a rock and a hard place...)

Gert Doering

         -- NetMaster

--

have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael

Emmer

Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann

D-80807 Muenchen                 HRB: 136055 (AG Muenchen)

Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

_______________________________________________

v6ops mailing list

v6ops@ietf.org

https://www.ietf.org/mailman/listinfo/v6ops

 

_______________________________________________

v6ops mailing list

v6ops@ietf.org

https://www.ietf.org/mailman/listinfo/v6ops

 

_______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops 



**********************************************
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 confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.