Re: [Bier] WG adoption call for draft-chen-bier-frr-02
Michael Menth <menth@uni-tuebingen.de> Tue, 16 March 2021 22:57 UTC
Return-Path: <menth@uni-tuebingen.de>
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 E9A6B3A1236 for <bier@ietfa.amsl.com>; Tue, 16 Mar 2021 15:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 GVaPJWcZSfOt for <bier@ietfa.amsl.com>; Tue, 16 Mar 2021 15:57:22 -0700 (PDT)
Received: from mx04.uni-tuebingen.de (mx04.uni-tuebingen.de [134.2.5.214]) (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 5B59D3A123C for <bier@ietf.org>; Tue, 16 Mar 2021 15:57:21 -0700 (PDT)
Received: from [192.168.0.69] (HSI-KBW-078-043-000-193.hsi4.kabel-badenwuerttemberg.de [78.43.0.193]) by mx04.uni-tuebingen.de (Postfix) with ESMTPSA id D7658209A201; Tue, 16 Mar 2021 23:57:17 +0100 (CET)
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, Huaimo Chen <huaimo.chen@futurewei.com>, Tony Przygienda <tonysietf@gmail.com>
Cc: "bier@ietf.org" <bier@ietf.org>
References: <202103161440487606255@zte.com.cn> <CA+wi2hPLG_Og=rDerVqK7hMjkjUGxzjpQnZMSFMf965UVLCxNA@mail.gmail.com> <54b33eef-31c1-5ceb-0bcf-051149d7e876@uni-tuebingen.de> <MN2PR13MB40870D62A90DBC972AE31B48F26B9@MN2PR13MB4087.namprd13.prod.outlook.com> <CA+wi2hN5xrq758tXQ0MxWe2tgfqQtH0Mw1zhU0t5DWS7N9gCrg@mail.gmail.com> <MN2PR13MB4087993A204A1A3D9665E463F26B9@MN2PR13MB4087.namprd13.prod.outlook.com> <MN2PR05MB598161405942FBFB47099CBCD46B9@MN2PR05MB5981.namprd05.prod.outlook.com> <3910c2e1-759e-0c23-ec58-365087d94084@uni-tuebingen.de> <MN2PR05MB5981BCEC8671855961325B79D46B9@MN2PR05MB5981.namprd05.prod.outlook.com>
From: Michael Menth <menth@uni-tuebingen.de>
Message-ID: <2ade8e9e-af8b-86c4-3b11-16fd71ff6b55@uni-tuebingen.de>
Date: Tue, 16 Mar 2021 23:57:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <MN2PR05MB5981BCEC8671855961325B79D46B9@MN2PR05MB5981.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/rUYtBbTDPPmT0VuTHbiVoMP41O8>
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, 16 Mar 2021 22:57:26 -0000
Hi Jeffrey, I understand that informational is the right classification of such documents. I see two options. - A single document covering the entire topic. - Two bier-frr docs (tunnel-based and lfa-based), preferentially using similar laguage. Then one can talk about RFC 123 or RFC XYZ protection. If the mechanisms are described within a single document, there is some potential for confusion. Not sure if an overarching framework for bier-frr is then still needed. Regards, Michael Am 16.03.2021 um 23:16 schrieb Jeffrey (Zhaohui) Zhang: > Hi Michael, > > We are on the same page. Progressing an informational draft on this topic is fine and seems to be even more necessary now. In fact, when draft-chen was presented last time I had suggested for some joint work. > > Thanks. > Jeffrey > > -----Original Message----- > From: Michael Menth <menth@uni-tuebingen.de> > Sent: Tuesday, March 16, 2021 3:03 PM > To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>; Huaimo Chen <huaimo.chen@futurewei.com>; Tony Przygienda <tonysietf@gmail.com> > Cc: bier@ietf.org > Subject: Re: [Bier] WG adoption call for draft-chen-bier-frr-02 > > [External Email. Be cautious of content] > > > Hi Jeffrey, all, > > your proposal was also the conclusion two years ago when I brought up > the topic in the working group: > > "The BIER FRR mechanism - be it tunnel-based or re-implementing LFAs on > the BIER layer - is a local mechanism and does not require cooperation > from other nodes. Probably both mechanisms can be even mixed within the > same network. Therefore, there is not need for standardization." > > I think this is not documented in any IETF drafts or even meeting > minutes, it was just a conclusion from some side meetings. That was also > the reason why we did not progress the draft on tunnel-based bier-frr. > > Nevertheless, it may be helpful to at least document both existing > bier-frr approaches as an informational draft so that manufacturers can > easily point to an implemented solution. This is helpful as both > solutions have pros and cons. A lot of contents is already in that paper > in which we summarized our understanding of the discussions two years ago: > https://urldefense.com/v3/__https://atlas.informatik.uni-tuebingen.de/*menth/papers/Menth20c.pdf__;fg!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUsxoFVJv$ > Some of its content may be useful for an overview draft of bier-frr methods. > > Regards > > Michael > > Am 16.03.2021 um 19:23 schrieb Jeffrey (Zhaohui) Zhang: >> If you consider BIFT and unicast FIB, they are actually very similar >> (ignoring the SI/sub-domain and bier label aspects). The only >> differences are: >> >> >> >> 1. (bfr-id % bitstringLength) or prefix as key >> 2. F-BM associated with a BFR-nbr in BIFT >> >> >> >> Each BIFT entry is built according how to reach a corresponding BFER, >> and the F-BM is obtained by setting the bits for all the BFERs that are >> reached by the BFR nbr. >> >> >> >> So, however you do FRR for unicast (LFA or tunnel based link/node >> protection or whatever) and whether it is IGP or BGP or whatever, you >> can just build the BIER FRR forwarding state the same way, and update >> the F-BM for the backup nbr accordingly. >> >> >> >> That's why I keep saying that there is not much to standardize on BIER >> FRR. It seems that this topic keeps coming up, so perhaps I should write >> an information draft to elaborate the above principle and how it works >> with various protection mechanisms. >> >> >> >> Jeffrey >> >> >> >> *From:* BIER <bier-bounces@ietf.org> *On Behalf Of * Huaimo Chen >> *Sent:* Tuesday, March 16, 2021 1:28 PM >> *To:* Tony Przygienda <tonysietf@gmail.com> >> *Cc:* bier@ietf.org; Michael Menth <menth@uni-tuebingen.de> >> *Subject:* Re: [Bier] WG adoption call for draft-chen-bier-frr-02 >> >> >> >> *[External Email. Be cautious of content]* >> >> >> >> Hi Tony, >> >> >> >> Even though there is IGP running in the network and the underlay IP >> FRR is provided, the BIER FRR seems still needed. All the BIER packets >> are forwarded using the BIFTs. They are not forwarded using the normal >> FIBs with IP FRR support. When a failure happens in the network, the >> BIER packets will still be forwarded using the old BIFTs without >> considering the failure until the old BIFT is recomputed and updated >> based on the new network topology after the failure. During this period >> (from the time of the failure to the time at which the BIFTs are >> updated), the BIER packets may be lost. >> >> >> >> Best Regards, >> >> Huaimo >> >> ------------------------------------------------------------------------ >> >> *From:*Tony Przygienda <tonysietf@gmail.com <mailto:tonysietf@gmail.com>> >> *Sent:* Tuesday, March 16, 2021 12:58 PM >> *To:* Huaimo Chen <huaimo.chen@futurewei.com >> <mailto:huaimo.chen@futurewei.com>> >> *Cc:* Michael Menth <menth@uni-tuebingen.de >> <mailto:menth@uni-tuebingen.de>>; bier@ietf.org <mailto:bier@ietf.org> >> <bier@ietf.org <mailto:bier@ietf.org>> >> *Subject:* Re: [Bier] WG adoption call for draft-chen-bier-frr-02 >> >> >> >> we need a framework here ;-) >> >> >> >> when IGP calculates the underlying FRR it's always a better solution. >> Nothing is faster than IGP and anything calculated as "better FRR" or >> "backup FRR" will not have the topology to do a better job/faster than >> IGP can. So AFAIS the only real use case here is BIER without IGP >> signalling but correct me if I'm wrong >> >> >> >> -- tony >> >> >> >> >> >> On Tue, Mar 16, 2021 at 5:02 PM Huaimo Chen <huaimo.chen@futurewei.com >> <mailto:huaimo.chen@futurewei.com>> wrote: >> >> Hi Michael, >> >> >> >> Thanks much for your valuable comments. >> >> My responses are inline below with prefix [HC]. >> >> >> >> Best Regards, >> >> Huaimo >> >> ------------------------------------------------------------------------ >> >> *From:*BIER <bier-bounces@ietf.org <mailto:bier-bounces@ietf.org>> >> on behalf of Michael Menth <menth@uni-tuebingen.de >> <mailto:menth@uni-tuebingen.de>> >> *Sent:* Tuesday, March 16, 2021 7:11 AM >> *To:* bier@ietf.org <mailto:bier@ietf.org> <bier@ietf.org >> <mailto:bier@ietf.org>> >> *Subject:* Re: [Bier] WG adoption call for draft-chen-bier-frr-02 >> >> >> >> Hi Tony, all, >> >> Am 16.03.2021 um 11:08 schrieb Tony Przygienda: >> >> > I think it's a good addition within the architecture for the case >> IGP is >> > not used for signalling, e.g. when controller or static programming. >> >> Right. The solution may make sense if the routing underlay does not >> offer FRR capabilities. >> >> >> >> [HC]: When the routing underlay supports IP FRR, the BIER should also >> >> provide BIER FRR since the BIER packets are forwarded using the BIFTs. >> >> When failures happen in the network, the BIER packets are still >> forwarded >> >> using the old BIFTs until the old BIFTs are updated according to the >> >> updated network topology after the failures. >> >> >> > >> > The draft must however explain in what scenarios it is used and quote >> > the according IGP drafts to guarantee loop-free behavior (well, BIER >> > will tie-break loops but we'll have 1x microloop & possibly not >> deliver >> > payload if BIER FRR is not properly computed/intsalled). With that the >> > draft should also pay attention to how the function is >> deployed/updated >> > network-wide if IGP is not present >> >> I agree. in the absence of an IGP, the "native BIER-FRR on bier layer" >> must be set by a controller. >> >> >> >> [HC]: I agree too. >> >> So, below the line, an applicability statement would be helpful. What >> are those cases? >> - IGP running but without FRR on the routing underlay? >> - No IGP and no FRR on the routing underlay? >> >> >> >> [HC]: When IGP is running in the network, each BFR in the network >> calculates, >> >> installs and/or updates its BIER FRR BIFTs. The BIER FRR in the >> draft is >> >> independent of the underlay IP FRR. >> >> When no IGP is running in the network, the BIER controller for the >> network >> >> calculates, installs and/or updates the BIER FRR BIFTs into BFRs in >> the network, >> >> regardless of whether the routing underlay FRR is provided. >> >> >> >> However, if the controller takes care of BIER-FRR, what could be reasons >> for missing FRR on the routing underlay? If there is a FRR on the >> routing underlay (also provided through a controller), tunnel-based >> bier-frr solves the problem in a transparent way. >> >> >> >> [HC]: The BIER FRR in the draft is independent of the underlay IP FRR. >> >> Regardless of whether the routing underlay FRR is provided, the >> >> BIER FRR BIFTs are computed in the same way. >> >> BTW, we studied protection variants for controller-based infrastructures >> (for routing underlays, not for BIER). Challenge is to keep state low. >> LFA-based solutions help a lot and outperform others. 100% protection is >> possible with only little additions. Results are available: >> https://urldefense.com/v3/__https://nam11.safelinks.protection.outlook.com/?url=https:*2F*2Fatlas.informatik.uni-tuebingen.de*2F*menth*2Fpapers*2FMenth20-Sub-6.pdf&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C5d3cb8163c7f4a1557e608d8e86c408f*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637514898966623524*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=03cc*2BIvdV*2BCg*2F0PCFulWzuCa0h4I5sBqn8K5QPT5BR8*3D&reserved=0__;JSUlfiUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUh_8_hxk$ >> <https://urldefense.com/v3/__https:/nam11.safelinks.protection.outlook.com/?url=https:*2F*2Fatlas.informatik.uni-tuebingen.de*2F*menth*2Fpapers*2FMenth20-Sub-6.pdf&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C2b86f5e805f04cf24c1008d8e89cdcd4*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637515107733090092*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=CNKcultin43VrTAvr*2BFH7V1FrMALSvaSpfmEiHcKm*2Fg*3D&reserved=0__;JSUlfiUlJSUlJSUlJSUlJSUlJSUl!!NEt6yMaO-gk!SBpWq7LIP13dlIX5P6U98cqIp8gTMP5_gelzA7rNyBrhf7h6mMn6N6YLFKhaK3F2$> >> (under >> revision) >> >> >> >> [HC]: Thanks much for your information. >> >> >> >> Regards, >> >> Michael >> >> > >> > thanks >> > >> > -- tony >> > >> > On Tue, Mar 16, 2021 at 7:41 AM <zhang.zheng@zte.com.cn >> <mailto:zhang.zheng@zte.com.cn> >> > <mailto:zhang.zheng@zte.com.cn <mailto:zhang.zheng@zte.com.cn>>> >> wrote: >> > >> > A 2-week WG adoption call begins for the following draft: >> > >> > >> https://urldefense.com/v3/__https://nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fdatatracker.ietf.org*2Fdoc*2Fdraft-chen-bier-frr*2F&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C5d3cb8163c7f4a1557e608d8e86c408f*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637514898966623524*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=797z0ndM2IahVL2y9xPoY*2BOU5x4*2F3w1FaSWfoF*2BC6pQ*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUjt7UD4f$ >> <https://urldefense.com/v3/__https:/nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fdatatracker.ietf.org*2Fdoc*2Fdraft-chen-bier-frr*2F&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C2b86f5e805f04cf24c1008d8e89cdcd4*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637515107733090092*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=4v2q4ToPT83pQYu5Fdwpc04pIcWrlihqy5m8YjgkVMA*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!SBpWq7LIP13dlIX5P6U98cqIp8gTMP5_gelzA7rNyBrhf7h6mMn6N6YLFNWNaFXu$> >> > >> <https://urldefense.com/v3/__https://nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fdatatracker.ietf.org*2Fdoc*2Fdraft-chen-bier-frr*2F&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C5d3cb8163c7f4a1557e608d8e86c408f*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637514898966623524*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=797z0ndM2IahVL2y9xPoY*2BOU5x4*2F3w1FaSWfoF*2BC6pQ*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUjt7UD4f$ >> <https://urldefense.com/v3/__https:/nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fdatatracker.ietf.org*2Fdoc*2Fdraft-chen-bier-frr*2F&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C2b86f5e805f04cf24c1008d8e89cdcd4*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637515107733100045*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=koqOJ4RFqPhBPl81t259PjxeQ6TxmcdtMMqgC0XXDzQ*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!SBpWq7LIP13dlIX5P6U98cqIp8gTMP5_gelzA7rNyBrhf7h6mMn6N6YLFF8NiiJX$>> >> > >> > 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) >> > >> > >> > >> > _______________________________________________ >> > BIER mailing list >> > BIER@ietf.org <mailto:BIER@ietf.org> >> > >> https://urldefense.com/v3/__https://nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fbier&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C5d3cb8163c7f4a1557e608d8e86c408f*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637514898966623524*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=aZ6*2BjQBpo7k81fqf*2FnYdfer7mS45RlhB0lPT7*2B*2BVm6I*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUnaUrsWg$ >> <https://urldefense.com/v3/__https:/nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fbier&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C2b86f5e805f04cf24c1008d8e89cdcd4*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637515107733110014*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=54DHmen2Kbqxu0LRWeuGlVBQbIepvbs1MqJHtfd6Wh8*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!SBpWq7LIP13dlIX5P6U98cqIp8gTMP5_gelzA7rNyBrhf7h6mMn6N6YLFMxV4XUQ$> >> > >> >> -- >> Prof. Dr. habil. Michael Menth >> University of Tuebingen >> Faculty of Science >> Department of Computer Science >> Chair of Communication Networks >> Sand 13, 72076 Tuebingen, Germany >> phone: (+49)-7071/29-70505 >> fax: (+49)-7071/29-5220 >> mailto:menth@uni-tuebingen.de <mailto:menth@uni-tuebingen.de> >> https://urldefense.com/v3/__https://nam11.safelinks.protection.outlook.com/?url=http*3A*2F*2Fkn.inf.uni-tuebingen.de*2F&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C5d3cb8163c7f4a1557e608d8e86c408f*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637514898966623524*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=2gozTq4XIXnxQu2P62mtFSGOEID93679cjqQeAQOPbo*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUt3QWHXy$ >> <https://urldefense.com/v3/__https:/nam11.safelinks.protection.outlook.com/?url=http*3A*2F*2Fkn.inf.uni-tuebingen.de*2F&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C2b86f5e805f04cf24c1008d8e89cdcd4*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637515107733110014*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=JxeRMSG7j*2FOyGLbPa*2BzGXw6kmFMVp5QqUTHjBEi69L8*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!SBpWq7LIP13dlIX5P6U98cqIp8gTMP5_gelzA7rNyBrhf7h6mMn6N6YLFMoeJ9A-$> >> >> _______________________________________________ >> BIER mailing list >> BIER@ietf.org <mailto:BIER@ietf.org> >> https://urldefense.com/v3/__https://nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fbier&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C5d3cb8163c7f4a1557e608d8e86c408f*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637514898966623524*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=aZ6*2BjQBpo7k81fqf*2FnYdfer7mS45RlhB0lPT7*2B*2BVm6I*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUnaUrsWg$ >> <https://urldefense.com/v3/__https:/nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fbier&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C2b86f5e805f04cf24c1008d8e89cdcd4*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637515107733119960*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=t3kSFKDwKsa46DGRbO8YW1nyUrPEFKa5JsBBFmOsoBU*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!SBpWq7LIP13dlIX5P6U98cqIp8gTMP5_gelzA7rNyBrhf7h6mMn6N6YLFEmh99Af$> >> >> _______________________________________________ >> BIER mailing list >> BIER@ietf.org <mailto:BIER@ietf.org> >> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/bier__;!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUmTz4u5t$ >> <https://urldefense.com/v3/__https:/nam11.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fbier&data=04*7C01*7Chuaimo.chen*40futurewei.com*7C2b86f5e805f04cf24c1008d8e89cdcd4*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C1*7C637515107733129927*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=5GMZctOBdR6ynmvuwvZlL2O2*2FIFbQWVFmmk*2FJwKnHxE*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!NEt6yMaO-gk!SBpWq7LIP13dlIX5P6U98cqIp8gTMP5_gelzA7rNyBrhf7h6mMn6N6YLFLvTCBdE$> >> >> >> Juniper Business Use Only >> > > -- > Prof. Dr. habil. Michael Menth > University of Tuebingen > Faculty of Science > Department of Computer Science > Chair of Communication Networks > Sand 13, 72076 Tuebingen, Germany > phone: (+49)-7071/29-70505 > fax: (+49)-7071/29-5220 > mailto:menth@uni-tuebingen.de > https://urldefense.com/v3/__http://kn.inf.uni-tuebingen.de__;!!NEt6yMaO-gk!XVo5XuifwFLLaWFLD2OZmJq1fws1WhcSKnUU3bjUch1IhPPKhQgxjetcUk6GcMm1$ > > Juniper Business Use Only > -- Prof. Dr. habil. Michael Menth University of Tuebingen Faculty of Science Department of Computer Science Chair of Communication Networks Sand 13, 72076 Tuebingen, Germany phone: (+49)-7071/29-70505 fax: (+49)-7071/29-5220 mailto:menth@uni-tuebingen.de http://kn.inf.uni-tuebingen.de
- [Bier] WG adoption call for draft-chen-bier-frr-02 zhang.zheng
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gyan Mishra
- [Bier] 答复: WG adoption call for draft-chen-bier-f… qinfengwei
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gengxuesong (Geng Xuesong)
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Mirsky
- Re: [Bier] WG adoption call for draft-chen-bier-f… Aijun Wang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gengxuesong (Geng Xuesong)
- Re: [Bier] WG adoption call for draft-chen-bier-f… peng.shaofu
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gengxuesong (Geng Xuesong)
- Re: [Bier] WG adoption call for draft-chen-bier-f… peng.shaofu
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Bidgoli, Hooman (Nokia - CA/Ottawa)
- Re: [Bier] WG adoption call for draft-chen-bier-f… Linda Dunbar
- Re: [Bier] WG adoption call for draft-chen-bier-f… Yanhe Fan
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael McBride
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gengxuesong (Geng Xuesong)
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gengxuesong (Geng Xuesong)
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Donald Eastlake
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Mirsky
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeff Tantsura
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Mirsky
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Mirsky
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Mirsky
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… LEI LIU
- Re: [Bier] WG adoption call for draft-chen-bier-f… peng.shaofu
- Re: [Bier] WG adoption call for draft-chen-bier-f… duanfanghong
- Re: [Bier] WG adoption call for draft-chen-bier-f… Lizhenbin
- Re: [Bier] WG adoption call for draft-chen-bier-f… Xufeng Liu
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gyan Mishra
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… zhangzhe (M)
- Re: [Bier] WG adoption call for draft-chen-bier-f… Steffen Lindner
- Re: [Bier] WG adoption call for draft-chen-bier-f… Daniel Merling
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Mirsky
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Shepherd
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael McBride
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Shepherd
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael McBride
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Adrian Farrel
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gyan Mishra
- Re: [Bier] WG adoption call for draft-chen-bier-f… peng.shaofu
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gengxuesong (Geng Xuesong)
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Tony Przygienda
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth
- Re: [Bier] WG adoption call for draft-chen-bier-f… Gengxuesong (Geng Xuesong)
- Re: [Bier] WG adoption call for draft-chen-bier-f… peng.shaofu
- Re: [Bier] WG adoption call for draft-chen-bier-f… Jeffrey (Zhaohui) Zhang
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Shepherd
- Re: [Bier] WG adoption call for draft-chen-bier-f… Mankamana Mishra (mankamis)
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Shepherd
- Re: [Bier] WG adoption call for draft-chen-bier-f… Huaimo Chen
- Re: [Bier] WG adoption call for draft-chen-bier-f… Greg Shepherd
- Re: [Bier] WG adoption call for draft-chen-bier-f… Michael Menth