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

zhang.zheng@zte.com.cn Tue, 02 March 2021 01:49 UTC

Return-Path: <zhang.zheng@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 250613A0AD6 for <bier@ietfa.amsl.com>; Mon, 1 Mar 2021 17:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 ppicjbZqLnTq for <bier@ietfa.amsl.com>; Mon, 1 Mar 2021 17:49:53 -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 AD9CE3A0AD5 for <bier@ietf.org>; Mon, 1 Mar 2021 17:49:52 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 16D4DDF0B9B0BA933E0F; Tue, 2 Mar 2021 09:49:50 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id E6ED68F590533C45510C; Tue, 2 Mar 2021 09:49:49 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse-fl1.zte.com.cn with SMTP id 1221nZtj057085; Tue, 2 Mar 2021 09:49:35 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid203; Tue, 2 Mar 2021 09:49:35 +0800 (CST)
Date: Tue, 2 Mar 2021 09:49:35 +0800 (CST)
X-Zmail-TransId: 2afa603d99afa9711702
X-Mailer: Zmail v1.0
Message-ID: <202103020949355964363@zte.com.cn>
In-Reply-To: <81971eb65f8848a693d9863d7e8cd6f0@huawei.com>
References: CABFReBodz5ko0wAZ_8vKgreWMLnCE_6O_qhKS_RGUbSAowEwfQ@mail.gmail.com, 81971eb65f8848a693d9863d7e8cd6f0@huawei.com
Mime-Version: 1.0
From: <zhang.zheng@zte.com.cn>
To: <duanfanghong@huawei.com>
Cc: <gjshep@gmail.com>, <bier@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 1221nZtj057085
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/attZkZxOkcqSgiC53rTO2cduK0k>
Subject: Re: [Bier] =?utf-8?q?Call_For_Adoption=3A_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:49:55 -0000

Hi Fanghong, 


You misunderstand the update of BIERin6, please find my comments with Sandy> below.


Thanks,


Sandy





原始邮件



发件人:duanfanghong
收件人:gjshep@gmail.com;BIER WG;
日 期 :2021年03月02日 09:23
主 题 :Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6




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

 

Hi,


 


I see this document proposes 2 options for MVPN/EVPN.


One is using the destination address to carry the ID of an MVPN/EVPN, but this means that every BFR have to be aware of the MVPN/EVPN instance, introducing state of MVPN/EVPN service and forwarding overhead in transit BFR nodes.


Sandy> No. BFR needs not to know MVPN/EVPN instance. Only BFIR and BFER need to know it. 






The other is to use an IPv6 address after a BIER header and before the customer IP packet, however it proposes a new Proto value and new process in forwarding plane. 


I think both of the options have obvious defects, and thus I do not support the adoption.


Sandy> As I said, only BFIR and BFER need to process the new proto value, it doesn't make affection on the intermediate forwarding plane.


 


Thanks !


Fanghong Duan


 


 


From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Greg Shepherd
 Sent: Friday, February 26, 2021 12:37 AM
 To: BIER WG <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/



 



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



 



Thanks,



Shep



(Chairs)