IETF Logo Mail Archive

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

peng.shaofu@zte.com.cn Fri, 05 March 2021 05:41 UTC

Return-Path: <peng.shaofu@zte.com.cn>
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 E5D6C3A1EA8 for <bier@ietfa.amsl.com>; Thu, 4 Mar 2021 21:41:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVCdfXxlC18M for <bier@ietfa.amsl.com>; Thu, 4 Mar 2021 21:41:13 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B7853A1C6C for <bier@ietf.org>; Thu, 4 Mar 2021 21:41:12 -0800 (PST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 03482FCA977C6DB0AD9E; Fri, 5 Mar 2021 13:41:08 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse-fl2.zte.com.cn with SMTP id 1255f2HI020644; Fri, 5 Mar 2021 13:41:02 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid201; Fri, 5 Mar 2021 13:41:02 +0800 (CST)
Date: Fri, 05 Mar 2021 13:41:02 +0800
X-Zmail-TransId: 2af96041c46e1ba4f2a6
X-Mailer: Zmail v1.0
Message-ID: <202103051341024264286@zte.com.cn>
In-Reply-To: <CABFReBodz5ko0wAZ_8vKgreWMLnCE_6O_qhKS_RGUbSAowEwfQ@mail.gmail.com>
References: CABFReBodz5ko0wAZ_8vKgreWMLnCE_6O_qhKS_RGUbSAowEwfQ@mail.gmail.com
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: gjshep@gmail.com
Cc: bier@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 1255f2HI020644
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/1uGdj4ffbhIUSsjN4lJsqoyeTRM>
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: Fri, 05 Mar 2021 05:41:16 -0000

Dear chair and WG,




I support adoption.

The scheme described in this document looks simple and beautiful, and can be well used in the interworking of various networks, and simplify the forwarding process of BIER multicast packets. It is benefit when multiple BFR NBRs have different capabilities, suggested by this document, only a single BIER payload format itself is needed and embedded in different outer encodings, instead of defining different BIER payload format for each BFR NBR with different capabilities (otherwise it would be a disaster for the forwarding chip). So that this document well inherits the layering idea of BIER architecture.




Regards,

PSF






原始邮件



发件人：GregShepherd
收件人：BIER WG;
日 期 ：2021年02月26日 00:37
主 题 ：[Bier] Call For Adoption: draft-zhang-bier-bierin6


_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier



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/


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