Re: [Bier] WG adoption call for draft-chen-bier-frr-02

peng.shaofu@zte.com.cn Tue, 23 March 2021 01:55 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 D8D2B3A19CA; Mon, 22 Mar 2021 18:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable 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 SQDHm8z-w_ZD; Mon, 22 Mar 2021 18:55:08 -0700 (PDT)
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 0CD453A19CD; Mon, 22 Mar 2021 18:55:07 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id B4E75BF963D9C754003D; Tue, 23 Mar 2021 09:55:02 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 12N1shD7054956; Tue, 23 Mar 2021 09:54:43 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid201; Tue, 23 Mar 2021 09:54:42 +0800 (CST)
Date: Tue, 23 Mar 2021 09:54:42 +0800
X-Zmail-TransId: 2afa60594a627e6d5342
X-Mailer: Zmail v1.0
Message-ID: <202103230954429063344@zte.com.cn>
In-Reply-To: <CA+wi2hOd+WEv=pziZcQEJvLc-0wHQkWTw6kq5gT8L-4RoNBHTg@mail.gmail.com>
References: 202103161440487606255@zte.com.cn, 014101d71ba2$40a9ca00$c1fd5e00$@tsinghua.org.cn, CA+wi2hNASuqW4oSPSMjjgkw7whkwin8mDdmiuDiqdEiGUKg6hA@mail.gmail.com, ccc6f0ff8d564b8889a19d4c252c3214@huawei.com, MN2PR05MB598131E8D851F1F6A90185D1D4699@MN2PR05MB5981.namprd05.prod.outlook.com, 58c674fdbc0a4ae0b53e370fdfc5f1ab@huawei.com, MN2PR05MB59817845050F372BF3B95785D4689@MN2PR05MB5981.namprd05.prod.outlook.com, e56369de6044456994349e729c8bc52c@huawei.com, CA+wi2hPxQwcK9GyEwapbc-TvGkw5K079G+Ghb6gnoWZgFSXG4A@mail.gmail.com, CA+wi2hOd+WEv=pziZcQEJvLc-0wHQkWTw6kq5gT8L-4RoNBHTg@mail.gmail.com
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: tonysietf@gmail.com
Cc: gengxuesong@huawei.com, zzhang=40juniper.net@dmarc.ietf.org, wangaijun@tsinghua.org.cn, bier@ietf.org, zhang.zheng@zte.com.cn, bier-chairs@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 12N1shD7054956
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/nh3U37MXxjb8Mo15S8Y9nm-Cg_4>
Subject: Re: [Bier] WG adoption call for draft-chen-bier-frr-02
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, 23 Mar 2021 01:55:16 -0000

Hi Tony,





When primary NBR has failed, the following two schemes have the same logic, both of them limit the processing socpe to the failure of specific primary NBR.

1) Within the scope of specific FRR-BIFT for the primary NBR, when packet is steered to an FRR-BIFT entry, the bitstring contained in the outgoing copy is the result of "original bitstring of the received packet" & "FBM".

2) A single BIFT entry with primary NBR and backup path, when packet is steered to backup path, the bitstring contained in the outgoing copy is the result of "original bitstring of the received packet" & "primary FBM" & "backup FBM".

For example, BIFT entry 1 has primary NBR X, BIFT entry 2 has primary NBR Y, but they have the same backup path. When NBR X has failed, BIFT entry 1 need switch to backup path, but BIFT entry 2 need not.




If the above two schemes are equivalent,  I think the simple one is the better one. There is no need to maintain so many FRR-BIFT tables as draft-chen described.




Regards,

PSF










原始邮件



发件人:TonyPrzygienda
收件人:Gengxuesong (Geng Xuesong);
抄送人:Jeffrey (Zhaohui) Zhang;Aijun Wang;BIER WG;张征00007940;BIER WG Chairs;
日 期 :2021年03月23日 04:36
主 题 :Re: [Bier] WG adoption call for draft-chen-bier-frr-02







On Fri, Mar 19, 2021 at 11:42 AM Tony Przygienda <tonysietf@gmail.com> wrote:




I would prefer a single document on bier-frr as joined Menth and Xuesong draft with the single BIFT mode & possibly multiple (again, modulo technical comments on it right now) but it's up to the authros to sit down and od the work and drink some beer together if they choose. 






I stand corrected of course, it was Huaimo's draft 


-- tony