Re: [v6ops] New Version Notification for draft-ietf-v6ops-ipv6-deployment-04.txt
Li Cong <licong@chinatelecom.cn> Mon, 28 February 2022 08:48 UTC
Return-Path: <licong@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 826163A0D1C for <v6ops@ietfa.amsl.com>; Mon, 28 Feb 2022 00:48:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 ypNjI0kuTqrf for <v6ops@ietfa.amsl.com>; Mon, 28 Feb 2022 00:48:29 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.227]) by ietfa.amsl.com (Postfix) with ESMTP id DFA7F3A02BC for <v6ops@ietf.org>; Mon, 28 Feb 2022 00:48:28 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.48:41054.1939205565
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.77 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id F0C6C28009D; Mon, 28 Feb 2022 16:48:23 +0800 (CST)
X-189-SAVE-TO-SEND: 71080549@chinatelecom.cn
Received: from ([172.18.0.48]) by app0024 with ESMTP id 4efdf36e9fe741a7b163d23494c01b16 for paolo.volpato@huawei.com; Mon, 28 Feb 2022 16:48:24 CST
X-Transaction-ID: 4efdf36e9fe741a7b163d23494c01b16
X-Real-From: licong@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: licong@chinatelecom.cn
User-Agent: Microsoft-MacOutlook/16.57.22011101
Date: Mon, 28 Feb 2022 16:48:16 +0800
From: Li Cong <licong@chinatelecom.cn>
To: paolo.volpato@huawei.com
CC: v6ops@ietf.org
Message-ID: <F5F0736B-8518-4345-9B5F-24E647A55A19@chinatelecom.cn>
Thread-Topic: New Version Notification for draft-ietf-v6ops-ipv6-deployment-04.txt
References: <c998f0e502f94b69a706b08e836a4fbe@huawei.com> <3443084F-E56E-441B-964D-BED6D6A06059@chinatelecom.cn>
In-Reply-To: <3443084F-E56E-441B-964D-BED6D6A06059@chinatelecom.cn>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3728911702_1162766876"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ysLaxha6RWKMrAVL0kyM-tbmEYw>
Subject: Re: [v6ops] New Version Notification for draft-ietf-v6ops-ipv6-deployment-04.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, 28 Feb 2022 08:48:35 -0000
Hi, Paolo, This draft gives a comprehensive picture of global IPv6 development and extracts some basic challenges that need to be solved by the industry. I think this draft is useful. In addition, I also have some comments prefixed [Cong] below, [Cong]: In this draft, you use the terms of “IPv6 introduction” and “IPv6-only to illustrate the first stage and second stage of IPv6 development respectively. However, I think they may overlap in some scenarios, for instance, some operators may use IPv6-only directly and stride over the IPv6-introduction stage with dual-stack. What I mean here is that dual-stack and IPv6-only are different approaches of transition, they do not correspond to the stages absolutely. In section 3.6, “The preliminary step to take full benefit of the IPv6 capabilities is to write or adapt the application software for use in IPv6 networks” [Cong]: As far as I know, the software code of most modern applications is agnostic to the type of IP address, whether the application uses IPv6 lies in the difference of address configuration of the host. In Section 4.1, “Although the Dual-Stack IPv6 transition is a good solution to be followed in the IPv6 introductory stage,” [Cong]: From the perspective of network operation, I don’t think dual-stack is a GOOD solution, for it increase the cost of O&M. In addition, dual-stack provide exposure-face, it increases the risk of being attack. I think it should be replaced by other term. In section 4.. “IPv6-only transition technologies with IPv4aaS have a much lower need for IPv4 public addresses, because they make a more efficient usage without restricting the number of ports per subscriber.” [Cong]: I think the restriction of number of ports per-subscriber is related to the policy of address/port usage, IMO it should be independent to the approach of IPv4aaS. I hope my comments will be helpful to your document. Best regards, Cong Li -----Original Message----- From: Paolo Volpato Sent: Tuesday, February 8, 2022 4:54 PM To: v6ops@ietf.org Cc: Chongfeng Xie <xiechf@chinatelecom.cn>; Giuseppe Fioccola <giuseppe.fioccola@huawei.com>; Gyan Mishra <gyan.s.mishra@verizon.com>; Jordi Palet Martinez <jordi.palet@theipv6company.com>; Nalini Elkins <nalini.elkins@insidethestack.com> Subject: RE: New Version Notification for draft-ietf-v6ops-ipv6-deployment-04.txt Dear WG, We have published version 04 of draft-ietf-v6ops-ipv6-deployment (https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-deployment/) We have reviewed most of the draft, to update the status of IPv6 deployment and to refresh some of its parts. Here is the summary of the main changes: - Section 2: introduced the new numbers on the adoption IPv6 (as of January 2022). - Section 3: updated the adoption of IPv6 in the enterprise, government and education domains. We have also added references to more countries (e.g. India, the European Union). - Section 4: we have reviewed this section to address some offline comments and discussions on the concept of "overlay" (i.e. how IPv6 may support the service layer and its role to enable the transition to IPv6-only). - Section 5: reviewed the description of IPv6 in the "underlay" (the network). Please feel free to comment. On behalf of the authors Paolo -----Original Message----- From: internet-drafts@ietf.org <internet-drafts@ietf.org> Sent: Tuesday, February 8, 2022 4:34 PM To: Gyan S. Mishra <gyan.s.mishra@verizon.com>; Chongfeng Xie <xiechf@chinatelecom.cn>; Giuseppe Fioccola <giuseppe.fioccola@huawei.com>; Gyan Mishra <gyan.s.mishra@verizon.com>; Jordi Martinez <jordi.palet@theipv6company.com>; Jordi Palet Martinez <jordi.palet@theipv6company.com>; Nalini Elkins <nalini.elkins@insidethestack.com>; Paolo Volpato <paolo.volpato@huawei.com> Subject: New Version Notification for draft-ietf-v6ops-ipv6-deployment-04.txt A new version of I-D, draft-ietf-v6ops-ipv6-deployment-04.txt has been successfully submitted by Giuseppe Fioccola and posted to the IETF repository. Name: draft-ietf-v6ops-ipv6-deployment Revision: 04 Title: IPv6 Deployment Status Document date: 2022-02-08 Group: v6ops Pages: 45 URL: https://www.ietf.org/archive/id/draft-ietf-v6ops-ipv6-deployment-04.txt Status: https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-deployment/ Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-ipv6-deployment Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-ipv6-deployment-04 Abstract: This document provides an overview of IPv6 deployment status and a view on how the transition to IPv6 is progressing among network operators and enterprises. It also aims to analyze the related challenges and therefore encourage actions and more investigations in those areas where the industry has not taken a clear and unified approach. The IETF Secretariat
- Re: [v6ops] New Version Notification for draft-ie… Paolo Volpato
- [v6ops] New Version Notification for draft-ietf-v… JORDI PALET MARTINEZ
- Re: [v6ops] New Version Notification for draft-ie… Li Cong
- Re: [v6ops] New Version Notification for draft-ie… JORDI PALET MARTINEZ
- Re: [v6ops] New Version Notification for draft-ie… Paolo Volpato
- Re: [v6ops] New Version Notification for draft-ie… Gyan Mishra
- Re: [v6ops] New Version Notification for draft-ie… Paolo Volpato
- Re: [v6ops] New Version Notification for draft-ie… Gyan Mishra
- Re: [v6ops] New Version Notification for draft-ie… JORDI PALET MARTINEZ