Re: [DNSOP] [v6ops] inputs on NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks draft-ietf-v6ops-nat64-deployment

Alejandro D'Egidio <adegidio@telecentro.net.ar> Mon, 25 February 2019 15:23 UTC

Return-Path: <adegidio@telecentro.net.ar>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70461130EF9; Mon, 25 Feb 2019 07:23:02 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telecentro.net.ar
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 ra7I5-FLwrnH; Mon, 25 Feb 2019 07:22:59 -0800 (PST)
Received: from mail.telecentro.net.ar (mail.telecentro.net.ar [190.55.63.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA28112F1AB; Mon, 25 Feb 2019 07:22:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.telecentro.net.ar (Postfix) with ESMTP id 5B84A3201FA9; Mon, 25 Feb 2019 12:22:56 -0300 (-03)
Received: from mail.telecentro.net.ar ([127.0.0.1]) by localhost (tclmail6.telecentro.local [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 0wUmPCxPDeW1; Mon, 25 Feb 2019 12:22:54 -0300 (-03)
Received: from localhost (localhost [127.0.0.1]) by mail.telecentro.net.ar (Postfix) with ESMTP id B11073201FAC; Mon, 25 Feb 2019 12:22:54 -0300 (-03)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.telecentro.net.ar B11073201FAC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telecentro.net.ar; s=25118654-7AE4-11E8-AD98-8D0B0E6845CD; t=1551108174; bh=d5wyBfK+LXFYfGVZW1SbIsvCMf/nIC4YGsQDp6Lta+g=; h=Date:From:To:Message-ID:MIME-Version; b=AoTw98JSCxPD7TTNgSA+F3UfvIElsk3PzUVgT3mj336RZ/954TWIFkSmQ8/dI6O+4 CacjSv0/jXfhRtVJJgXE6mf6WgoPM5t4pYSXBFeoyuV+RZronQfmwxOPOam6GDGway ih0hR58PDQLo7igKgWm7y7ntEigPUfa9WCxX7pq3gt37AvAENmQOaA4FukS3caietF TS7MKRsOgTjbwmS8g23tQDe7PzFw7XibyMeFcb1OB+FNIgtwsIkseoDC9uTTNIwohR Po2IpkchmGL/IN9YxWbxoQjtqF52rFPL/jbFPwBOjqqHO4g2uFxMJ0ZIvAJxvUq2Tn UrO6dWr7Pu7/w==
X-Virus-Scanned: amavisd-new at tclmail6.telecentro.local
Received: from mail.telecentro.net.ar ([127.0.0.1]) by localhost (tclmail6.telecentro.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Zfq957ybW9Gp; Mon, 25 Feb 2019 12:22:54 -0300 (-03)
Received: from tclmail6.telecentro.local (tclmail6.telecentro.local [10.210.50.96]) by mail.telecentro.net.ar (Postfix) with ESMTP id 759E13201FA9; Mon, 25 Feb 2019 12:22:54 -0300 (-03)
Date: Mon, 25 Feb 2019 12:22:54 -0300
From: Alejandro D'Egidio <adegidio@telecentro.net.ar>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
Cc: "v6ops@ietf.org list" <v6ops@ietf.org>, dnsop <dnsop@ietf.org>
Message-ID: <128899659.2649874.1551108174039.JavaMail.zimbra@telecentro.net.ar>
In-Reply-To: <40C16CF8-8EE8-468D-8248-A2873CC7EAB6@consulintel.es>
References: <40C16CF8-8EE8-468D-8248-A2873CC7EAB6@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.210.50.96]
X-Mailer: Zimbra 8.8.8_GA_3008 (ZimbraWebClient - GC72 (Win)/8.8.8_GA_1703)
Thread-Topic: inputs on NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks draft-ietf-v6ops-nat64-deployment
Thread-Index: 4g1eMoftmD8xnaYUH5EqHNFIxoK+Hg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/k3wKzECIC0gNDwIPG2VYhS9cXWM>
Subject: Re: [DNSOP] [v6ops] inputs on NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks draft-ietf-v6ops-nat64-deployment
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 25 Feb 2019 15:23:03 -0000

Hello Jordi,
I like 464XLAT and this is something I would like to implement in DOCSIS networks.
As Deployment Guidelines maybe you can include/consider the next case, if not please forget it or we can include it on another document.

Today we still have many devices that don't support IPv6 or some applications on it don't support it, this is the case of SMART TVs and set top boxes.
There is a common scenario where big public CDNs support deliver content to private IPv4 destinations (usually CGN prefixes) directly without going through a CGN.
In that scenario, CPEs (with eRouter) that have IPv4 of CGN (ie 100.64.x.x) can connect receive traffic from CDNs directly without having any CGN in the middle.

So I see three points in this case:
1- Traffic avoids a point of failure (CGN), obviously it should be redundant but the point of failure exists.
2- Traffic is more "transparent" avoiding another translation for CDN.
3- This traffic doesn't impact in CGN sizing.

As I said, I like 464XLAT and I would like to have a IPv6-Only access network but this is a real case where ISPs can consider to continue provisioning IPv4 to customers.



Regards,
Alejandro

----- Mensaje original -----
De: "JORDI PALET MARTINEZ" <jordi.palet=40consulintel.es@dmarc.ietf.org>
Para: "v6ops@ietf.org list" <v6ops@ietf.org>, "dnsop" <dnsop@ietf.org>
Enviados: Jueves, 21 de Febrero 2019 2:58:36
Asunto: [v6ops] inputs on NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks draft-ietf-v6ops-nat64-deployment

Hi all,

(dnsop copied because DNS64)

I'm working in a new version of this document.

Link to the document:

https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/

It will be great if we can get some new inputs.

Thanks!

Regards,
Jordi
 
 



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.



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