[v6ops] New Version Notification for draft-ietf-v6ops-ipv6-deployment-04.txt
JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 22 February 2022 11:20 UTC
Return-Path: <prvs=1052d8a3fe=jordi.palet@consulintel.es>
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 5BA053A0E06 for <v6ops@ietfa.amsl.com>; Tue, 22 Feb 2022 03:20:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 bTaOOB3L-LQq for <v6ops@ietfa.amsl.com>; Tue, 22 Feb 2022 03:20:46 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 9D3DC3A0D49 for <v6ops@ietf.org>; Tue, 22 Feb 2022 03:20:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1645528837; x=1646133637; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=Jrw3VHSa xdU06dLPw0Buw08LIbnSXYhZLvYjbHYROD8=; b=sp2Gnm+lNmsAMWAjdNurzBKl fwmfh5bMjQPuEKLbEDlWYOnvXEaYDacTk4/YCpkIAESM80X4MenfQ5i6sT02KX4z /xop8h04BrSmngFGMm2QvBqjIQRzwVnTRKSzmYWTCgrh1OzAlW7CjFnBtQW0iFxv WmbwLIXpTViLP7CQE0E=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Tue, 22 Feb 2022 12:20:37 +0100
X-Spam-Processed: mail.consulintel.es, Tue, 22 Feb 2022 12:20:37 +0100
Received: from [10.10.10.105] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000808291.msg for <v6ops@ietf.org>; Tue, 22 Feb 2022 12:20:36 +0100
X-MDRemoteIP: 2001:470:1f09:495:11f2:94a4:333d:f695
X-MDHelo: [10.10.10.105]
X-MDArrival-Date: Tue, 22 Feb 2022 12:20:36 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1052d8a3fe=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.59.22022002
Date: Tue, 22 Feb 2022 12:20:31 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Message-ID: <7E5D02CC-061C-4050-A515-C9ADD03DFF06@consulintel.es>
Thread-Topic: New Version Notification for draft-ietf-v6ops-ipv6-deployment-04.txt
References: <164433441833.15468.9198475503392258025@ietfa.amsl.com> <351c7adf1852465b92faba70c10e294d@huawei.com> <da5a74567e7f46abbcb9315b049b9142@huawei.com> <A654B77E-88E5-4799-850F-3A4FCF116AB5@consulintel.es> <58390a80966746559cc909743b2743d5@huawei.com>
In-Reply-To: <58390a80966746559cc909743b2743d5@huawei.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9QBYMX8ooyU5CveXs3TSUU9QytE>
Subject: [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: Tue, 22 Feb 2022 11:20:52 -0000
Hi all,
I've cached some minor points that we have already confirmed among the co-authors, but it will be good to see if someone else in the WG has anything else to say before a new version.
1) After "The reasons for having high or medium-to-high IPv6 deployment may be
quite different from country to country. For example, in West
European countries such as Belgium, France, Germany the outcome
depends on a mix of government and regulation activities which
incentivized the adoption of IPv6 in the recent years."
I think we should add "In some cases it has been industry self-regulation which created the traction for a bigger IPv6 adoption".
Explanation: This was for example the case for Belgium, much more than government regulation. It was an agreement among operators and to reduce the number of users behind NAT in a single IPv4 address.
2) Across all the document. There is no such thing as "migration", there are no "migration" techniques. We should replace it with "transition" or "transition and coexistence", etc., unless IPv4 is totally discarded from that network (that will be a real migration case, like when you move from Windows 7 to Windows 10, you don't keep both running at the same time). This is key, because this document will be read by people learning, not so versed in the topic, and when I do trainings, using migration is the aspect that most confuses people.
3) Usage of CPE or CE? I think to be consistent with other documents, we should use CE instead of CPE.
4) Terminology. Should we have a terminology section at the beggininig of the document? We can there define each term and abbreviation used across the document, so it clarifies the text and avoid duplication. For example my previous point will be:
CE: Customer Edge router.
5) After "the consensus to move to IPv6-only is when IPv6
traffic volume is between 50% and 60%.," I will say ", which easily happens from since the moment IPv6 is deployed in networks where residential customers traffic is higher than business traffic (because major content providers, as already explained, already use IPv6)".
6) After "For example, Sony Play
Station Network or OpenDNS imply a higher rotation of IPv4 prefixes
in CGN, until they get totally blocked.", I will say "which means extra CAPEX in new IPv4 transfers."
7) I'm included in the ack section, I guess should be removed from there.
-----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
**********************************************
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.
**********************************************
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.
- 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