Re: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-lmhp-v6ops-transition-comparison

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Mon, 29 March 2021 12:04 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
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 7979A3A0DF3 for <v6ops@ietfa.amsl.com>; Mon, 29 Mar 2021 05:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 f20cIb8ISjg4 for <v6ops@ietfa.amsl.com>; Mon, 29 Mar 2021 05:04:13 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95BED3A0E0B for <v6ops@ietf.org>; Mon, 29 Mar 2021 05:04:13 -0700 (PDT)
Received: from fraeml715-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F8B2D6wfHz68528; Mon, 29 Mar 2021 19:59:16 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml715-chm.china.huawei.com (10.206.15.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 29 Mar 2021 14:04:09 +0200
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2106.013; Mon, 29 Mar 2021 14:04:09 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Gabor LENCSE <lencse@hit.bme.hu>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-lmhp-v6ops-transition-comparison
Thread-Index: AQHXIx7vL1cJ9Q33LUaTMOocytdgBqqa3GBA
Date: Mon, 29 Mar 2021 12:04:09 +0000
Message-ID: <4ae0473b73794b55adbd86f92a48f478@huawei.com>
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <59B5C1F7-48E4-4915-BAAC-41D8ADA29E8F@gmail.com> <18ea74665936408bb33f20630da95311@huawei.com> <E0757B36-8FFB-43A8-8F8B-A7F152F81156@gmail.com> <fb216b2c2d9743d9aedbd4112bb71a27@huawei.com> <c29d1459-14f9-0ece-26be-91de3bc04ec2@hit.bme.hu>
In-Reply-To: <c29d1459-14f9-0ece-26be-91de3bc04ec2@hit.bme.hu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.213.66]
Content-Type: multipart/alternative; boundary="_000_4ae0473b73794b55adbd86f92a48f478huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/eXgfDKbBb7tb2ah4E0Jvxox8YGA>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-lmhp-v6ops-transition-comparison
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, 29 Mar 2021 12:04:18 -0000

Hi Gabor,
Thanks a lot for your support and for the suggestion regarding IPv6 security.
We will have a look at your paper and revise our security part.
I think we can also highlight the main points from https://tools.ietf.org/html/draft-ietf-opsec-v6-24#section-2.7

Regards,

Giuseppe

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gabor LENCSE
Sent: Saturday, March 27, 2021 4:35 PM
To: v6ops@ietf.org
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-lmhp-v6ops-transition-comparison


Dear All,

I have read draft-vf-v6ops-ipv6-deployment-02 and I found it useful and I support its adoption.

I have found a typo at the bottom of page 18:

"Yet, this worsening effect may appeae as disturbing for a plain transition to IPv6." --> "Yet, this worsening effect may appear as disturbing for a plain transition to IPv6."

Regarding IPv6 Security in Section 11.4, I think it is also worth considering the additional security issues brought into existence by the applied IPv6 transition technologies used to implement IPv4aaS, like 464XLAT, DS-Lite, etc. You can find some basic hints in our paper:

G. Lencse and Y. Kadobayashi, "Methodology for the identification of potential security issues of different IPv6 transition technologies: Threat analysis of DNS64 and stateful NAT64", Computers & Security (Elsevier), vol. 77, no. 1, pp. 397-411, August 1, 2018, DOI: 10.1016/j.cose.2018.04.012

Available from: http://www.hit.bme.hu/~lencse/publications/ECS-2018-Methodology-revised.pdf

As for our draft, draft-lmhp-v6ops-transition-comparison-06, I am working on an RFC 8219 compliant performance measurement tool to be able to add relevant data to Section 5 about Performance Comparison. I have just prepared the very much alpha state version of a stateful NAT64 tester, by enabling siitperf for stateful tests: https://github.com/lencsegabor/siitperf/tree/stateful

It is capable of benchmarking both stateful NAT64 and stateful NAT44 (CGNAT) implementations. Its documentation is to be updated yet, but I am glad the help, if any you would like to use it.

Best regards,

Gábor

p.s.: I have corrected the subject line, as I think Fred intended to include both drafts in it.
On 3/27/2021 1:05 PM, Xipengxiao wrote:

Hi All,



I support the adoption of both drafts, as they provide (1) useful information about the current deployment status of IPv6, and (2) useful information for operators to consider while deploying IPv6.   With almost 500 IPv6-related RFCs, it's difficult for IPv6-deployers to find all the relevant information.  So these summary-and-advice types of  documents are useful for our industry at this stage.



XiPeng



-----Original Message-----

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Fred Baker

Sent: Saturday, March 27, 2021 5:58 AM

To: v6ops@ietf.org<mailto:v6ops@ietf.org>

Cc: draft-lmhp-v6ops-transition-comparison@ietf.org<mailto:draft-lmhp-v6ops-transition-comparison@ietf.org>; draft-vf-v6ops-ipv6-

deployment@ietf.org<mailto:deployment@ietf.org>

Subject: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-vf-v6ops-ipv6-

deployment







On Mar 19, 2021, at 1:39 AM, Paolo Volpato <paolo.volpato@huawei.com><mailto:paolo.volpato@huawei.com>

wrote:



For lmhp-v6ops-transition-comparison, on behalf of the authors of draft-vf-

v6ops-ipv6-deployment I can say we are in favor of the WG adoption. Not

only is it a good description of the transition technologies to IPv6, but it also

constitutes a basis for our draft.



OK, let me put this to the working group. We asked about adoption of draft-

lmhp-v6ops-transition-comparison once before (in January 2020), and got

essentially no response. It has come up on the list twice since, in July and in

November. The authors of draft-vf-v6ops-ipv6-deployment would like to see

it adopted. The two sets of authors are disjoint. I therefore have at least nine

people that would like to see us adopt and publish it. What other folks have

opinions, pro or con?



Along the same lines, are there opinions regarding the adoption of draft-vf-

v6ops-ipv6-deployment?



https://mailarchive.ietf.org/arch/search/?qdr=a&q=%22draft-lmhp-v6ops-

transition-comparison%22

https://mailarchive.ietf.org/arch/search/?qdr=a&q=%22draft-vf-v6ops-ipv6-

deployment%22



_______________________________________________

v6ops mailing list

v6ops@ietf.org<mailto:v6ops@ietf.org>

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