IETF Logo Mail Archive

Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6

"zhangzhe (M)" <zhangzhe22@huawei.com> Tue, 02 March 2021 01:37 UTC

Return-Path: <zhangzhe22@huawei.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB193A0A34 for <bier@ietfa.amsl.com>; Mon, 1 Mar 2021 17:37:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 XxZVpcBHc2Ve for <bier@ietfa.amsl.com>; Mon, 1 Mar 2021 17:37:00 -0800 (PST)
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 5F7BC3A0A1C for <bier@ietf.org>; Mon, 1 Mar 2021 17:37:00 -0800 (PST)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DqKPp2N5Kz67v8x; Tue, 2 Mar 2021 09:32:46 +0800 (CST)
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) 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.2106.2; Tue, 2 Mar 2021 02:36:56 +0100
Received: from dggemx752-chm.china.huawei.com (10.0.44.33) by nkgeml707-chm.china.huawei.com (10.98.57.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Tue, 2 Mar 2021 09:36:54 +0800
Received: from dggemx752-chm.china.huawei.com ([10.9.82.157]) by dggemx752-chm.china.huawei.com ([10.9.82.157]) with mapi id 15.01.2106.006; Tue, 2 Mar 2021 09:36:54 +0800
From: "zhangzhe (M)" <zhangzhe22@huawei.com>
To: Michael McBride <michael.mcbride@futurewei.com>, "gjshep@gmail.com" <gjshep@gmail.com>, BIER WG <bier@ietf.org>
Thread-Topic: [Bier] Call For Adoption: draft-zhang-bier-bierin6
Thread-Index: AQHXC5SUt8NALInKcUizaE35nWOSI6ppcBqAgAaA4lA=
Date: Tue, 02 Mar 2021 01:36:54 +0000
Message-ID: <21b915579f8f413190cbe3230720801d@huawei.com>
References: <CABFReBodz5ko0wAZ_8vKgreWMLnCE_6O_qhKS_RGUbSAowEwfQ@mail.gmail.com> <BYAPR13MB2582DB22A823BBEDF071DE93F49D9@BYAPR13MB2582.namprd13.prod.outlook.com>
In-Reply-To: <BYAPR13MB2582DB22A823BBEDF071DE93F49D9@BYAPR13MB2582.namprd13.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.134.44]
Content-Type: multipart/alternative; boundary="_000_21b915579f8f413190cbe3230720801dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/YppNfLxadkpDKM2G-F1Wqogmc-U>
Subject: Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2021 01:37:03 -0000

I agree with mike and oppose the adoption of this draft.

For example, this document proposes 2 options for the fragmentation in BIERin6 in section 2.
One is using an IPv6 header before BIER header, but this will enforce every BFR to assembly and re-fragment a packet.
The other is to use a Fragment header after BIER header to avoid intermediate BFR to do the assembly and re-fragment,
however I don't think it is a mature and accepted solution to support this draft to be adopted.

Thank you.
Zhe Zhang

From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Michael McBride
Sent: Friday, February 26, 2021 2:15 PM
To: gjshep@gmail.com; BIER WG <bier@ietf.org>
Subject: Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6

Oppose.

We are unfortunately no where near consensus on this topic including this draft. We'll likely see that during this adoption call.

Adrian's suggestion for consensus remains the best I've heard: simultaneously call to adopt both solutions as experimental.

mike

From: BIER <bier-bounces@ietf.org<mailto:bier-bounces@ietf.org>> On Behalf Of Greg Shepherd
Sent: Thursday, February 25, 2021 8:37 AM
To: BIER WG <bier@ietf.org<mailto:bier@ietf.org>>
Subject: [Bier] Call For Adoption: draft-zhang-bier-bierin6

Thank you all for the active discussion that brought us to consensus. This draft now addresses all of the points of discussion for the solution.

https://datatracker.ietf.org/doc/draft-zhang-bier-bierin6/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-zhang-bier-bierin6%2F&data=04%7C01%7Cmichael.mcbride%40futurewei.com%7C7aecd20ae06a4b6a300a08d8d9aba70d%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637498678569221968%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IV22zVnPbym%2FJTZljh%2FLGNUqxFp4zZKJWcHBTx9a%2BPY%3D&reserved=0>

Please reply to this thread with your support/opposition of WG adoption of the draft.

Thanks,
Shep
(Chairs)

v2.23.0 | Report a Bug | By Email