IETF Logo Mail Archive

Re: [v6ops] Thoughts about wider operational input

Xipengxiao <xipengxiao@huawei.com> Tue, 29 March 2022 22:38 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 186CE3A11A0 for <v6ops@ietfa.amsl.com>; Tue, 29 Mar 2022 15:38:32 -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 dzQOmKDXWCuy for <v6ops@ietfa.amsl.com>; Tue, 29 Mar 2022 15:38:27 -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 B2B643A119D for <v6ops@ietf.org>; Tue, 29 Mar 2022 15:38:27 -0700 (PDT)
Received: from fraeml712-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KSktF6BW3z67Zx5; Wed, 30 Mar 2022 06:35:49 +0800 (CST)
Received: from fraeml712-chm.china.huawei.com (10.206.15.61) by fraeml712-chm.china.huawei.com (10.206.15.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 30 Mar 2022 00:38:23 +0200
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; Wed, 30 Mar 2022 00:38:23 +0200
From: Xipengxiao <xipengxiao@huawei.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, Paolo Volpato <paolo.volpato=40huawei.com@dmarc.ietf.org>, "buraglio@es.net" <buraglio@es.net>
CC: "Philipp S. Tiesel" <phils@in-panik.de>, IPv6 Ops WG <v6ops@ietf.org>
Thread-Topic: [v6ops] Thoughts about wider operational input
Thread-Index: AQHYPWL+iivaR7toLkau7q+5KQunzazLUXgAgALnPICAAAlRgIAAJp+AgAFv3YCAAPRUAIAEGh6AgAF1zQCAAE/IgIAAUVaQ
Date: Tue, 29 Mar 2022 22:38:23 +0000
Message-ID: <82aa58bd0dd648ee9eda2d9307a69a47@huawei.com>
References: <BE3310F7-692C-46E9-A75B-07C4C3C6476F@gmail.com> <DM6PR14MB3178DB5E4F9560FFE0B13521D7179@DM6PR14MB3178.namprd14.prod.outlook.com> <29f35cbabc114386a1d00bf5c4054f6c@huawei.com> <DM6PR14MB3178A04B566F1D24571924F8D7199@DM6PR14MB3178.namprd14.prod.outlook.com> <1DA8D34D-3B77-4B6B-B49F-C4C200492624@in-panik.de> <36b1c1aa244f40afa05eb5e58cc62cdb@huawei.com> <DM6PR14MB3178AAF2A80CE63ED8A11C1DD71B9@DM6PR14MB3178.namprd14.prod.outlook.com> <CAM5+tA-zjL4hiL6uSTj3mUJYBAY==kuDUMynA=rCQTtmoSAmGA@mail.gmail.com> <bdd02e1bc8f5468ea4501f071a9e95a7@huawei.com> <78A86A99-38C3-4494-B085-FFC224AFE1C4@gmail.com>
In-Reply-To: <78A86A99-38C3-4494-B085-FFC224AFE1C4@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.196.181]
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/WDhzdhl5iGlswZAqDu3cofILug8>
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, 29 Mar 2022 22:38:32 -0000

Hi Fred,

I volunteer to work with Michael, Nick, Nalini, Paolo, Eduard and Philipp et al to find a few candidates, so that you and Ron can select 1-2 to talk in v6ops in Philadelphia IETF. I suggest we select those who are hands-on and can talk about the challenges and lessons in depth.

XiPeng 

-----Original Message-----
From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Fred Baker
Sent: Tuesday, March 29, 2022 9:37 PM
To: Paolo Volpato <paolo.volpato=40huawei.com@dmarc.ietf.org>; buraglio@es.net
Cc: Philipp S. Tiesel <phils@in-panik.de>; IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Thoughts about wider operational input



> On Mar 29, 2022, at 7:51 AM, Paolo Volpato <paolo.volpato=40huawei.com@dmarc.ietf.org> wrote:
> 
> As Nick suggested, I also see a role for them to contribute in defining an evolution path to IPv6. I see this something that can be addressed in the IETF. 

I don't disagree with you in the least. That brings me back to my original question, however:

Can we get someone-that's-not-a-vendor-academic-or-ISP (using the word "enterprise" seems to be confusing) give a talk in v6ops in Philadelphia about what their proposed evolutionary target for IPv6 might be?
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email