Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6 Tue, 02 March 2021 02:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 959723A0C7C for <>; Mon, 1 Mar 2021 18:18:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Hl0aMTq3guqA for <>; Mon, 1 Mar 2021 18:18:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BC7FC3A0C66 for <>; Mon, 1 Mar 2021 18:18:22 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTPS id 268427B0172E401D1AE0; Tue, 2 Mar 2021 10:18:21 +0800 (CST)
Received: from ([]) by with SMTP id 1222IAru099940; Tue, 2 Mar 2021 10:18:10 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid203; Tue, 2 Mar 2021 10:18:10 +0800 (CST)
Date: Tue, 2 Mar 2021 10:18:10 +0800 (CST)
X-Zmail-TransId: 2afa603da06222854e4f
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
From: <>
To: <>
Cc: <>, <>, <>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: 1222IAru099940
Archived-At: <>
Subject: Re: [Bier] =?utf-8?q?Call_For_Adoption=3A_draft-zhang-bier-bierin6?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Mar 2021 02:18:43 -0000

Hi Zhe, 

Just response to your comments about fragmentation. 

If you read the BIERin6 draft more carefully, you may find that the fragmentation description is in section 1.2 and not in section 2. 

The first option is treat the IPv6 fragmentation packet as BIER payload, the BFR needs not to do the assembling work. 

Only BFIR and BFER needs to do the fragmentation and assembling work. This function is mature and practicable. 

The second option provides a novel way for fragmentation, not only for BIER. 

The working group draft takes time to be mature, the GTF function as well. 




收件人:Michael McBride;;BIER WG;
日 期 :2021年03月02日 09:37
主 题 :Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6

BIER mailing list


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 [] On Behalf Of Michael McBride
 Sent: Friday, February 26, 2021 2:15 PM
 To:; BIER WG <>
 Subject: Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6




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.




From: BIER <> On Behalf Of Greg Shepherd
 Sent: Thursday, February 25, 2021 8:37 AM
 To: BIER WG <>
 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.


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