Re: [v6ops] I-D Action: draft-ietf-v6ops-transition-comparison-00.txt

Chongfeng Xie <xiechf@chinatelecom.cn> Mon, 19 April 2021 08:43 UTC

Return-Path: <xiechf@chinatelecom.cn>
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 A200C3A28EC for <v6ops@ietfa.amsl.com>; Mon, 19 Apr 2021 01:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.012
X-Spam-Level:
X-Spam-Status: No, score=0.012 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 tE6zD5J_A-Yn for <v6ops@ietfa.amsl.com>; Mon, 19 Apr 2021 01:43:14 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.228]) by ietfa.amsl.com (Postfix) with ESMTP id 7817E3A28EB for <v6ops@ietf.org>; Mon, 19 Apr 2021 01:43:13 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:47188.651708508
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.78?logid-5d9e4e2130ce481c8d29288554be0b79 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 37F87280119; Mon, 19 Apr 2021 16:43:06 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([172.18.0.48]) by app0024 with ESMTP id 5d9e4e2130ce481c8d29288554be0b79 for jordi.palet=40consulintel.es@dmarc.ietf.org; Mon Apr 19 16:43:09 2021
X-Transaction-ID: 5d9e4e2130ce481c8d29288554be0b79
X-filter-score: filter<0>
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Mon, 19 Apr 2021 16:43:01 +0800
From: Chongfeng Xie <xiechf@chinatelecom.cn>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <161851774047.23547.18406903341297144719@ietfa.amsl.com>, <0eb0c029ca6247cc9b7274082e694ad1@huawei.com>, <48230BB0-88CF-4610-931A-9827C9C67799@consulintel.es>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.20.273[cn]
Mime-Version: 1.0
Message-ID: <2021041916430101310920@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart221251742232_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/j0AIv1E78BtZ7W6dlXLq7uWPtYg>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-transition-comparison-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 19 Apr 2021 08:43:19 -0000

I don't think CLAT is only used for tethering,  it also be responsible for synthetisingIPv4 address into IPv6 address when the DNS query is not processed by DNS64 of the carrier network, for instance, the DNS service is provided via HTTPDNS by some other organzations, which is very popular in the current Internet.

Regards
Chongfeng

From: JORDI PALET MARTINEZ
Date: 2021-04-16 20:20
To: v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-transition-comparison-00.txt
Hi Eduard,
 
I think I can provide some light on this.
 
iOS was not supporting CLAT since a few years ago, which was a problem for using 464XLAT in tethering, but this is no longer true. Thanks to the push from several operators Apple finally implemented CLAT, which is only needed for the tethering, because the "similar" solution to bump-in-the-host resolve the problem for the apps in the iOS device. Further to that, this is supported because Apple took a very good decision long time ago (2016 I believe), to only allow in the AppStore apps that work in IPv6-only, so that's why the CLAT is not need for the iOS device itself.
 
Having no need for the CLAT to be enabled means lower battery consumption, and of course, lower CPU cost and delay if the other end is also using IPv6, so not NAT at all.
 
We have indeed some mentions about PCP and EAM in the text, not sure what you will like to see in the document. Could you please elaborate a bit more? An specific section about that or?
 
Regards,
Jordi
@jordipalet
 
El 16/4/21 14:03, "v6ops en nombre de Vasilenko Eduard" <v6ops-bounces@ietf.org en nombre de vasilenko.eduard@huawei.com> escribió:
 
    Hi all,
    iOS does not support 464XLAT/CLAT.
    They do use RFC 6535 (Bump in the host) instead.
    It is probably an important fact for 4.4.2
 
    I am not sure that it is needed here. But there is the story of how to initiate a NAT connection in the opposite direction.
    PCP (RFC 7225, RFC 6887), STUN (RFC 5389), EAM (RFC 7757), public IP allocation on CGNAT.
    Different translation technologies have different compatibility and different tools for how to punch a hole in the opposite direction.
    Some FBBs have a real shortage of public IPv4 to play with this.
 
    It is a little strange that PCP (RFC 7225) has not been mentioned at all.
 
    Eduard
    -----Original Message-----
    From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
    Sent: Thursday, April 15, 2021 11:16 PM
    To: i-d-announce@ietf.org
    Cc: v6ops@ietf.org
    Subject: [v6ops] I-D Action: draft-ietf-v6ops-transition-comparison-00.txt
 
 
    A New Internet-Draft is available from the on-line Internet-Drafts directories.
    This draft is a work item of the IPv6 Operations WG of the IETF.
 
            Title           : Pros and Cons of IPv6 Transition Technologies for IPv4aaS
            Authors         : Gabor Lencse
                              Jordi Palet Martinez
                              Lee Howard
                              Richard Patterson
                              Ian Farrer
    Filename        : draft-ietf-v6ops-transition-comparison-00.txt
    Pages           : 30
    Date            : 2021-04-15
 
    Abstract:
       Several IPv6 transition technologies have been developed to provide
       customers with IPv4-as-a-Service (IPv4aaS) for ISPs with an IPv6-only
       access and/or core network.  All these technologies have their
       advantages and disadvantages, and depending on existing topology,
       skills, strategy and other preferences, one of these technologies may
       be the most appropriate solution for a network operator.
 
       This document examines the five most prominent IPv4aaS technologies
       considering a number of different aspects to provide network
       operators with an easy to use reference to assist in selecting the
       technology that best suits their needs.
 
 
    The IETF datatracker status page for this draft is:
    https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-comparison/
 
    There are also htmlized versions available at:
    https://tools.ietf.org/html/draft-ietf-v6ops-transition-comparison-00
    https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-transition-comparison-00
 
 
    Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
 
    Internet-Drafts are also available by anonymous FTP at:
    ftp://ftp.ietf.org/internet-drafts/
 
 
    _______________________________________________
    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.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