Re: [v6ops] Call for adoption: draft-peng-v6ops-hbh

Vasilenko Eduard <vasilenko.eduard@huawei.com> Fri, 10 September 2021 16:43 UTC

Return-Path: <vasilenko.eduard@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 ABA383A0BFE for <v6ops@ietfa.amsl.com>; Fri, 10 Sep 2021 09:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 olebrSZgB2tk for <v6ops@ietfa.amsl.com>; Fri, 10 Sep 2021 09:43:33 -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 9E4483A0BF5 for <v6ops@ietf.org>; Fri, 10 Sep 2021 09:43:33 -0700 (PDT)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4H5hTY59zzz67NMn for <v6ops@ietf.org>; Sat, 11 Sep 2021 00:41:21 +0800 (CST)
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Fri, 10 Sep 2021 18:43:29 +0200
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml500001.china.huawei.com (7.188.26.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Fri, 10 Sep 2021 19:43:29 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2308.008; Fri, 10 Sep 2021 19:43:29 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Call for adoption: draft-peng-v6ops-hbh
Thread-Index: AQHXphTz3fGWLYNIQiK+F0VNim+BZaucsX8AgADHncA=
Date: Fri, 10 Sep 2021 16:43:28 +0000
Message-ID: <662d5323dbf8441db34ae3fcc299ae54@huawei.com>
References: <82208000-8C92-4AD8-A64F-667E73662626@chinaunicom.cn> <CO1PR11MB4881923AB3A534EFFAED7616D8D69@CO1PR11MB4881.namprd11.prod.outlook.com>
In-Reply-To: <CO1PR11MB4881923AB3A534EFFAED7616D8D69@CO1PR11MB4881.namprd11.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.205.91]
Content-Type: multipart/alternative; boundary="_000_662d5323dbf8441db34ae3fcc299ae54huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BItegni9TG1_-ts-4rJ7oHFcRAk>
Subject: Re: [v6ops] Call for adoption: draft-peng-v6ops-hbh
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: Fri, 10 Sep 2021 16:43:39 -0000

Like Pascal, I believe that if we would do nothing – then we would get nothing.
I support the adoption.
But I have a request: does it make sense to include a requirement that vendors SHOULD disclose options supported in the data plane and control plane separately?
The world should know their heroes. It would help to improve support in hardware.
Ed/
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: Friday, September 10, 2021 10:47 AM
To: 秦壮壮(联通北京市北京市分公司) <qinzhuangzhuang@chinaunicom.cn>; v6ops@ietf.org
Subject: Re: [v6ops] Call for adoption: draft-peng-v6ops-hbh

I support the adoption too; it will take years and years to reverse the trend but we must start someday.

Note that I do not read RFC 8200 as the draft does “
While [RFC8200<https://www.ietf.org/archive/id/draft-peng-v6ops-hbh-06.html#RFC8200>] required that all nodes must examine and process the Hop-by-Hop Options header
“
RFC 8200 says “
  The Hop-by-Hop Options header is not inserted or deleted, but may be
   examined or processed by any node along a packet's delivery path,
“
The text that follows in the draft (expecting routers to ignore) is also what RFC 8200 says.

Another comment is that not all networks are SP networks, maybe we could have other sections. E.g., take high speed IoT networks, Ethernet and IP are slowly replacing a dozen of semi proprietary protocols in industrial automation and pro A/V. Special processing (topology / path, replication / elimination, advanced shaping) is required. If we cannot signal that in HbH then it will have to be ULP.

Keep safe;

Pascal


From: v6ops <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org>> On Behalf Of ???(???????????)
Sent: vendredi 10 septembre 2021 9:25
To: v6ops@ietf.org<mailto:v6ops@ietf.org>
Subject: Re: [v6ops] Call for adoption: draft-peng-v6ops-hbh

As a co-author of this draft and an operator running IPv6 networks, I support the adoption of this draft.
It states very clearly the operators’ real requirements in the field.

Thanks to other co-authors and WG.

Zhuangzhuang


From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Ron Bonica
Sent: Friday, September 10, 2021 1:11 AM
To: v6ops@ietf.org<mailto:v6ops@ietf.org>
Subject: [v6ops] Call for adoption: draft-peng-v6ops-hbh

Folks,

This message initiates a call for adoption for draft-peng-v6ops-hbh (https://datatracker.ietf.org/doc/draft-peng-v6ops-hbh/).

Please post comments by September 24, 2021.

                                                                   Fred and Ron
如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除<mailto:hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除>。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn<mailto:hqs-spmc@chinaunicom.cn> ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.