Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-communities-06.txt (2/4/2022 to 2/18/2022)

[Gyan Mishra <[e-mail]>]

+1

I agree with Robert as well that the atom mechanism has been proven by the
implementation and that all atoms defined in the specification should
remain for future extensibility by operators as well as developers seeking
new innovations such as RPD that could reap the benefit of this
extensibility.

The key point here is that the wide community draft can be implemented by
operators as well as can be utilized to design new solutions like the RPD
 that can be still developed in the future that may need to take advantage
of the other atoms or features not implemented by RPD.

So I think in this case it’s is different then the norm that every feature
must be implemented for interoperability.

This document is ready for publication.

Kind Regards

Gyan
On Tue, Feb 8, 2022 at 11:31 AM Lange, Andrew (Nokia - US) <
[e-mail]> wrote:

> I agree with Robert, the atom mechanism is proven by implementation, and
> keeping the existing atoms documented reflects community consensus.
>
> I also agree with Linda that the document is ready for publication.
>
> Andrew
> ------------------------------
> *From:* Idr <[e-mail]> on behalf of Linda Dunbar <
> [e-mail]>
> *Sent:* Monday, February 7, 2022 3:57 PM
> *To:* [e-mail] <[e-mail]>
> *Cc:* Keyur Patel <[e-mail]>
> *Subject:* Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-communities-06.txt
> (2/4/2022 to 2/18/2022)
>
>
> I think the draft-ietf-idr-wide-bgp-communities-06 is ready for
> publication. I support the WGLC.
>
> Linda Dunbar
>
>
>
> *From: *Keyur Patel <[e-mail]>
> *Sent: *Friday, February 4, 2022 8:28 AM
> *To: *[e-mail]
> *Subject: *[Idr] WG LC on draft-ietf-idr-wide-bgp-communities-06.txt
> (2/4/2022 to 2/18/2022)
>
>
>
> Hi Folks:
>
>
>
> The working group last call has been issued for draft-ietf-idr-wide-bgp-communities-06.txt, “BGP Community Container Attribute”.  Please reply to the list with your comments. This adoption call will conclude on February 18th, 2022.
>
>
>
> The draft can be found at: https://datatracker.ietf.org/doc/draft-ietf-idr-wide-bgp-communities/ <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-idr-wide-bgp-communities%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C643de43c0ba04a002b7d08d9e8249406%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637796066078367604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4B4iqtEQX14eaGgiFMZjCC%2F9Pe5E50ABt2dj9tYqW9U%3D&reserved=0>. The implementation report for the draft can be found at: https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-wide-bgp-communities <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.ietf.org%2Ftrac%2Fidr%2Fwiki%2Fdraft-ietf-idr-wide-bgp-communities&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C643de43c0ba04a002b7d08d9e8249406%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637796066078367604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VSV07uT5gxoU7V76CVjsL7ID0mGF7oMSEtOzLsyJa4I%3D&reserved=0>.  Authors, please reply indicating whether you're aware of any relevant IPR that hasn't been disclosed.
>
>
>
> Best Regards,
>
> Keyur
>
>
>
>
>
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C643de43c0ba04a002b7d08d9e8249406%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637796066078367604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Eqe8KBV19SGW5LBx4gBUCRhHSc%2FcoYlSjwpJM1stSF8%3D&reserved=0>
>
> --
>
>
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email [e-mail] <[e-mail]>*



*M 301 502-1347*