Re: [v6ops] FW: New Version Notification for draft-vf-v6ops-ipv6-deployment-00.txt

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Thu, 15 October 2020 15:20 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 07E443A07CE; Thu, 15 Oct 2020 08:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 1QNkgXF3EcoZ; Thu, 15 Oct 2020 08:20:43 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20E863A07C4; Thu, 15 Oct 2020 08:20:43 -0700 (PDT)
Received: from lhreml734-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id AD35B36C3CDB3104819D; Thu, 15 Oct 2020 16:20:40 +0100 (IST)
Received: from fraeml709-chm.china.huawei.com (10.206.15.37) by lhreml734-chm.china.huawei.com (10.201.108.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 15 Oct 2020 16:20:40 +0100
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 15 Oct 2020 17:20:39 +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.1913.007; Thu, 15 Oct 2020 17:20:39 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: "Dale W. Carder" <dwcarder@es.net>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-vf-v6ops-ipv6-deployment@ietf.org" <draft-vf-v6ops-ipv6-deployment@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
Thread-Topic: [v6ops] FW: New Version Notification for draft-vf-v6ops-ipv6-deployment-00.txt
Thread-Index: AQHWovdnldXGZSP3DkOI6d1DuX9RaamYqeYw///zAICAACe6gA==
Date: Thu, 15 Oct 2020 15:20:39 +0000
Message-ID: <7741125e4deb4b7ba725d8a68d0fe7d5@huawei.com>
References: <160276863269.12225.15313625467391617602@ietfa.amsl.com> <19408462e0bf4f0a8776820bef8d9130@huawei.com> <20201015144801.GB78739@dwc-desktop.local>
In-Reply-To: <20201015144801.GB78739@dwc-desktop.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.208.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/IxijU1psR6uqTDYJDcMfbValUg0>
Subject: Re: [v6ops] FW: New Version Notification for draft-vf-v6ops-ipv6-deployment-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: Thu, 15 Oct 2020 15:20:45 -0000

Hi Dale,
Thanks for your quick feedback!
Yes, this gives me the opportunity to clarify. The ETSI White Paper No. 35 is a reference of the draft and we are also coauthors of it. The first part of our draft starts from the same considerations of the White Paper (If it is not considered useful to reaffirm some concepts we can simply omit them in the next revision). 
But we would like to go beyond and extend the second part of the document, in particular the "Call for Action" section, that is new. To start a call for action on specific areas (IPv6 Performance, Security,...) and encourage the community, we need to go ahead in IETF.

Regards,

Giuseppe

-----Original Message-----
From: Dale W. Carder [mailto:dwcarder@es.net] 
Sent: Thursday, October 15, 2020 4:48 PM
To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
Cc: v6ops@ietf.org; draft-vf-v6ops-ipv6-deployment@ietf.org; v6ops-chairs@ietf.org
Subject: Re: [v6ops] FW: New Version Notification for draft-vf-v6ops-ipv6-deployment-00.txt

Thus spake Giuseppe Fioccola (giuseppe.fioccola@huawei.com) on Thu, Oct 15, 2020 at 02:31:55PM +0000:
> Dear All,
> We have just posted a new informational draft on IPv6 deployment. This document aims to provide the global picture of IPv6 to show how IPv6 is growing and also an overview of IPv6 transition deployment status. Indeed, it is reported a survey of the deployed IPv6 transition technologies. The document also aims to analyze the challenges and therefore encourage actions and more investigations on some areas that are still under discussion.
> 
> For those interested to collaborate on this topic, we are open to discuss and work together to improve the document.
> 
> Your inputs and comments are welcome.

With admittedly only a very quick glance through it, to me it sort of looks like a copy+paste of ETSI White Paper No. 35 into RFC format.  

Would you mind expanding on the difference between that document and what you are hoping to do here?

Dale

 
> Name:		draft-vf-v6ops-ipv6-deployment
> Revision:	00
> Title:		IPv6 Transition Deployment Status
> Document date:	2020-10-15
> Group:		Individual Submission
> Pages:		24
> URL:            https://www.ietf.org/archive/id/draft-vf-v6ops-ipv6-deployment-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-vf-v6ops-ipv6-deployment/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-vf-v6ops-ipv6-deployment
> Htmlized:       https://tools.ietf.org/html/draft-vf-v6ops-ipv6-deployment-00