Re: [v6ops] Thoughts about wider operational input

Xipengxiao <xipengxiao@huawei.com> Tue, 22 March 2022 10:17 UTC

Return-Path: <xipengxiao@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 255063A0CE8 for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 03:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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 jQEX8QCsf7rp for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 03:16:58 -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 950F13A0CF1 for <v6ops@ietf.org>; Tue, 22 Mar 2022 03:16:21 -0700 (PDT)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KN6mz1sxlz67wM8; Tue, 22 Mar 2022 18:15:15 +0800 (CST)
Received: from fraeml712-chm.china.huawei.com (10.206.15.61) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 22 Mar 2022 11:16:19 +0100
Received: from fraeml712-chm.china.huawei.com ([10.206.15.61]) by fraeml712-chm.china.huawei.com ([10.206.15.61]) with mapi id 15.01.2375.024; Tue, 22 Mar 2022 11:16:19 +0100
From: Xipengxiao <xipengxiao@huawei.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, IPv6 Ops WG <v6ops@ietf.org>
CC: "intc-board@industrynetcouncil.org" <intc-board@industrynetcouncil.org>
Thread-Topic: [v6ops] Thoughts about wider operational input
Thread-Index: AQHYPWL+iivaR7toLkau7q+5KQunzazKTsQAgADVgsA=
Date: Tue, 22 Mar 2022 10:16:19 +0000
Message-ID: <8b312fdf8071416a81623436ec54bc95@huawei.com>
References: <BE3310F7-692C-46E9-A75B-07C4C3C6476F@gmail.com> <EEEAF809-8F0E-4FF8-85CE-8EF8DA8A4A69@gmail.com>
In-Reply-To: <EEEAF809-8F0E-4FF8-85CE-8EF8DA8A4A69@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.126.172.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mGdf4WXdZtaU2WwwgEHtyg7Z6oY>
Subject: Re: [v6ops] Thoughts about wider operational input
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 Mar 2022 10:17:03 -0000

>> Fred said: Following along these lines. We have had various and sundry talk about their IPv6 deployments in V6ops. Could we have an enterprise operator talk about what stops them from deploying? Looking for volunteers/suggestions.

In the NANOG discussion on "not making use of 240/4", there are a few people chanting against IPv6.  It may be good to invite some of them to talk about their technical concerns.   Then somebody from us can document all these concerns and solutions into a draft.  This solves problems.

While motivation is generally a bigger problem, even there I see momentum.  Many small and medium enterprises (SMEs) don't see the need for IPv6, as they don't need many addresses, and they may not have the IPv6 expertise to make the change.  But even for these SMEs, I see the recent support of IPv6 from Azure/AWS a potential game changer for this situation:  if the Azure/AWS makes the use of IPv6 default (current default is still IPv4), many SMEs will be moved to IPv6 with very little effort!  I see this as the biggest momentum for IPv6 in enterprise.

Lastly, let's not be too optimistic about IPv6 in network operators.  First, there are still many big operators that don't do IPv6.  If we are to spend some effort persuading somebody to do IPv6, talking with these operators (they have need for IPv6) will likely be more rewarding than with some enterprises (may not have need).  Second, many operators that have deployed IPv6 actually only deployed IPv6 in overlay (i.e. UEs & gateways like BNGs), not in underlay (routers).  When an operator tells you that they do Dual-Stack, you would think that their network can transport IPv6 packets natively.  But that is mostly NOT that case.  Only the UEs and BNGs/mobile gateways are Dual-Stack.  The routers are not.  The routers often just put IPv6 over MPLS.  The reason for doing so, is to use only an IPv4 data/control/management plane.  If they do Dual-Stack in underlay with the routers, they will have 2 data/control/management planes.  This was the biggest IPv6 surprise I found in 2021.  Many IPv6 veterans still don't realize this, or don't believe it.  If we can, I suggest we do a survey to verify what I said.   

In 16:45 today in Park Suite 9 in Vienna I will do a host techtalk on "IPv6 Adoption Worldwide: Momentum, Challenges and Next Steps".  It will touch many issues we discuss here.  I invite you to join the discussion on site or on line: https://wws.conf.meetecho.com/conference/?group=hostspeaker .  Thank you very much.

XiPeng