Re: [v6ops] Thoughts about wider operational input

Paolo Volpato <paolo.volpato@huawei.com> Thu, 24 March 2022 09:32 UTC

Return-Path: <paolo.volpato@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 CB6EF3A0DEF for <v6ops@ietfa.amsl.com>; Thu, 24 Mar 2022 02:32:55 -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 fn81-UvVSDhW for <v6ops@ietfa.amsl.com>; Thu, 24 Mar 2022 02:32:51 -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 149D93A0DDD for <v6ops@ietf.org>; Thu, 24 Mar 2022 02:32:51 -0700 (PDT)
Received: from fraeml739-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KPKj40JLfz68735; Thu, 24 Mar 2022 17:31:04 +0800 (CST)
Received: from fraeml740-chm.china.huawei.com (10.206.15.221) by fraeml739-chm.china.huawei.com (10.206.15.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 24 Mar 2022 10:32:48 +0100
Received: from fraeml740-chm.china.huawei.com ([10.206.15.221]) by fraeml740-chm.china.huawei.com ([10.206.15.221]) with mapi id 15.01.2375.024; Thu, 24 Mar 2022 10:32:48 +0100
From: Paolo Volpato <paolo.volpato@huawei.com>
To: "Ackermann, Michael" <MAckermann=40bcbsm.com@dmarc.ietf.org>, Fred Baker <fredbaker.ietf@gmail.com>, IPv6 Ops WG <v6ops@ietf.org>
Thread-Topic: [v6ops] Thoughts about wider operational input
Thread-Index: AQHYPWL+iFqwU6qP7kW8sKC3J1h2rKzLUXgAgALoWaA=
Date: Thu, 24 Mar 2022 09:32:47 +0000
Message-ID: <29f35cbabc114386a1d00bf5c4054f6c@huawei.com>
References: <BE3310F7-692C-46E9-A75B-07C4C3C6476F@gmail.com> <DM6PR14MB3178DB5E4F9560FFE0B13521D7179@DM6PR14MB3178.namprd14.prod.outlook.com>
In-Reply-To: <DM6PR14MB3178DB5E4F9560FFE0B13521D7179@DM6PR14MB3178.namprd14.prod.outlook.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.126.171.116]
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/sAW-emp7k18-gwdnkKC1VW_dmpw>
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: Thu, 24 Mar 2022 09:32:56 -0000

I go back to the initial question posed by Fred and discussed by Michael here below (and echoed by others in the thread).

Personally, I agree with what Michael says and this is also one of the conclusions I would draw from the analysis done in draft-ietf-v6ops-ipv6-deployment. Enterprises, whatever we mean by that term and with the due exceptions, don't care about IPv6, unless it supports/enables their business goals.

But I believe that enterprises are represented in the IETF, either directly or indirectly. 
As discussed at the v6ops session on Monday, if the proposal is to listen to the people who have challenges or are even opposing to IPv6 then we can think of finding room for listening/interacting with enterprises on that. Without discussing here how and where, Fred's idea to have a meeting at the next RIPE could be a first step (and if accepted I would be happy to give support).

I am pretty sure that the contributions we may collect as a WG could be the subject of an operational draft.

BR
Paolo 


-----Original Message-----
From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Ackermann, Michael
Sent: Tuesday, March 22, 2022 2:13 PM
To: Fred Baker <fredbaker.ietf@gmail.com>; IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Thoughts about wider operational input

Good question Fred. 
As one of those enterprises "Dragging their heels" on IPv6, and knowing MANY others in the same state,   I believe the following are the core issues: 
1. Lack of technical knowledge regarding IPv6 implementation and operation.  
2. Lack of understanding of compelling reason(s) to deploy IPv6.   Both Technical and Business reasons.  

There is progress in both areas,  but definitely  not enough and results are slow (or worse).  

Another area that COULD be compelling is to highlight what issues may be faced if an Org stays on IPv4 only, for either the short or long term

Any help, guidance or info regarding either of the above would be helpful and appreciated.    

The best methods for doing this is a probably a longer discussion(s), so I will not attempt to address related details in this email.    
But I do believe this is any topic which warrants attention and would glad to contribute,  if I can.  

Thanks

Mike



-----Original Message-----
From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Fred Baker
Sent: Monday, March 21, 2022 4:33 PM
To: IPv6 Ops WG <v6ops@ietf.org>
Subject: [v6ops] Thoughts about wider operational input

[External email]


I have thought some about the discussion we had in the V6ops meeting about increasing operational input. Several suggestions were made: add a separate meeting, segregate parts of the meeting, attend the IEPG, use an interim, and so on. One thought that I had was to schedule a meeting at RIPE in May.

None of these address what seems to me to be a core problem: ISPs are deploying, but enterprise isn’t. How do we get enterprise on board?

Sent using a machine that autocorrects in interesting ways...
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops


The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.
 
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.


This message was secured by Zix(R).
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops