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

[Huaimo Chen <[e-mail]>]

Hi Tony,

    Thank you very much for your valuable suggestions, which will help us to make the document better.

Best Regards,
Huaimo
________________________________
From: Tony Przygienda <[e-mail]>
Sent: Friday, March 26, 2021 5:16 AM
To: Huaimo Chen <[e-mail]>
Cc: zhang.zheng <[e-mail]>; BIER WG <[e-mail]>; BIER WG Chairs <[e-mail]>
Subject: Re: [Bier] WG adoption call for draft-chen-bier-frr-02

Excellent, having authors of multiple drafts in this area co-allesce and colaborate on a single framework document would be a very positive and productive development in my eyes. If it explains the IGP model e'one uses today so far and the architecture kind of implies as default with IGP signalling, the better.

Discussions around informational/experimental can happen later of course but generally experimental will introduce the burden of two implementations most likely (and with that many models that may not be trivial) and of course experimental is needed in case we end up allocating codepoints or need to agree on some on-the-wire formats (algorithms are not that clear). We play it by the ear depending on the scope of the document as it evolves and content would be my take for now.

thanks

-- tony



On Thu, Mar 25, 2021 at 10:05 PM Huaimo Chen <[e-mail]<mailto:[e-mail]>> wrote:
Hi Everyone,

    Michael, Steffan, Huaimo and Mike met to discuss the merge and we are in agreement that if draft-chen-bier-frr is adopted we will expand it to include a framework along with the tunnel and LFA based solutions.

Best Regards,
Huaimo
________________________________
From: BIER <[e-mail]<mailto:[e-mail]>> on behalf of Tony Przygienda <[e-mail]<mailto:[e-mail]>>
Sent: Tuesday, March 16, 2021 6:08 AM
To: zhang.zheng <[e-mail]<mailto:[e-mail]>>
Cc: BIER WG <[e-mail]<mailto:[e-mail]>>; BIER WG Chairs <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Bier] WG adoption call for draft-chen-bier-frr-02

+1

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.

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

thanks

-- tony

On Tue, Mar 16, 2021 at 7:41 AM <[e-mail]<mailto:[e-mail]>> wrote:

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

https://datatracker.ietf.org/doc/draft-chen-bier-frr/<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%7C1e0e547abd8d47f7e26b08d8f037fa5a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637523470508327528%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=t8qPHEul9oXIfEyUj907PJCQ%2BHPEHqwARO8choKcmAU%3D&reserved=0>

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)