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

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Thu, 18 March 2021 08:13 UTC

Return-Path: <gengxuesong@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 D6F293A2440; Thu, 18 Mar 2021 01:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 3UNoh0SkL_e0; Thu, 18 Mar 2021 01:13:26 -0700 (PDT)
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 D06B13A243D; Thu, 18 Mar 2021 01:13:25 -0700 (PDT)
Received: from fraeml701-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F1KLp38hhz6815Y; Thu, 18 Mar 2021 16:04:50 +0800 (CST)
Received: from dggpemm100007.china.huawei.com (7.185.36.116) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Thu, 18 Mar 2021 09:13:17 +0100
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by dggpemm100007.china.huawei.com (7.185.36.116) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Thu, 18 Mar 2021 16:13:15 +0800
Received: from dggeme752-chm.china.huawei.com ([10.6.80.76]) by dggeme752-chm.china.huawei.com ([10.6.80.76]) with mapi id 15.01.2106.013; Thu, 18 Mar 2021 16:13:15 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: Tony Przygienda <tonysietf@gmail.com>, Aijun Wang <wangaijun@tsinghua.org.cn>
CC: BIER WG <bier@ietf.org>, zhang.zheng <zhang.zheng@zte.com.cn>, "BIER WG Chairs" <bier-chairs@ietf.org>
Thread-Topic: [Bier] WG adoption call for draft-chen-bier-frr-02
Thread-Index: AQHXGi9xZ6IhhWxpI0KATDBZLtTDLaqIigQAgABSuwCAAIjP0A==
Date: Thu, 18 Mar 2021 08:13:15 +0000
Message-ID: <ccc6f0ff8d564b8889a19d4c252c3214@huawei.com>
References: <202103161440487606255@zte.com.cn> <014101d71ba2$40a9ca00$c1fd5e00$@tsinghua.org.cn> <CA+wi2hNASuqW4oSPSMjjgkw7whkwin8mDdmiuDiqdEiGUKg6hA@mail.gmail.com>
In-Reply-To: <CA+wi2hNASuqW4oSPSMjjgkw7whkwin8mDdmiuDiqdEiGUKg6hA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.242.209]
Content-Type: multipart/alternative; boundary="_000_ccc6f0ff8d564b8889a19d4c252c3214huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/PRdvnhIZI1NbYii2CA2cRiPRQiI>
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: Thu, 18 Mar 2021 08:13:28 -0000

Hi Tony,

Sorry for stepping in. But I’m really confused why this document is called “implementation dependent”. Especially so many fast reroute algorithms have been standardized in history, as  RFC5286 or RFC7490.
LFA BIER FRR mechanism introduce multiple FRR BIFTs because calculating FRR BIRT makes the F-BM different for different BFR-NBR failure, if the problem is about “multiple BIFTs” . If there is any other concern, could you raise some examples from the document?

Best
Xuesong


From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Thursday, March 18, 2021 3:52 PM
To: Aijun Wang <wangaijun@tsinghua.org.cn>
Cc: BIER WG <bier@ietf.org>rg>; zhang.zheng <zhang.zheng@zte.com.cn>cn>; BIER WG Chairs <bier-chairs@ietf.org>
Subject: Re: [Bier] WG adoption call for draft-chen-bier-frr-02

As others pointed out it's not clear we need to "standardize" this for the simple reason this is _very_ implementation dependent. "Standardizing" is important if interoperability is important, in this sense if this draft talks about different schemes interoperating, gotchas etc, yes, there may be an angle there. Starting from a model aligned with Menthe, describing alternate techniques [like multiple BIFTs with compression etc] if the technical problems/discussions with those can be ironed out is a good thing since it will document possible approaches/issues etc but what track this is best published on should be discussed bit down the road especially after implementation/experience with different approaches.

-- tony

On Thu, Mar 18, 2021 at 3:56 AM Aijun Wang <wangaijun@tsinghua.org.cn<mailto:wangaijun@tsinghua.org.cn>> wrote:
Hi, All:

As co-author of this draft, I support its adoption.
I am not aware of any IPR that applies to this draft.

Some technical discussions and clear statements for the implementation are necessary, standardize them can accomplish the consistent behavior across the network wide.

Best Regards

Aijun Wang
China Telecom

From: bier-bounces@ietf.org<mailto:bier-bounces@ietf.org> <bier-bounces@ietf.org<mailto:bier-bounces@ietf.org>> On Behalf Of zhang.zheng@zte.com.cn<mailto:zhang.zheng@zte.com.cn>
Sent: Tuesday, March 16, 2021 2:41 PM
To: bier@ietf.org<mailto:bier@ietf.org>
Cc: bier-chairs@ietf.org<mailto:bier-chairs@ietf.org>
Subject: [Bier] WG adoption call for draft-chen-bier-frr-02


A 2-week WG adoption call begins for the following draft:

https://datatracker.ietf.org/doc/draft-chen-bier-frr/

Please indicate your support or objection by March 30th, 2021.

Authors, please respond to the list indicating whether you are aware of any IPR that applies to this draft.

Thanks,

Sandy (As WG secretary, on behalf of Greg/Tony)