RFC 8642

Policy Behavior for Well-Known BGP Communities, August 2019

File formats:
icon for text file icon for PDF icon for HTML
Status:
PROPOSED STANDARD
Updates:
RFC 1997
Authors:
J. Borkenhagen
R. Bush
R. Bonica
S. Bayraktar
Stream:
IETF
Source:
grow (ops)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8642

Discuss this RFC: Send questions or comments to the mailing list grow@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8642


Abstract

Well-known BGP communities are manipulated differently across various current implementations, resulting in difficulties for operators. Network operators should deploy consistent community handling across their networks while taking the inconsistent behaviors from the various BGP implementations into consideration. This document recommends specific actions to limit future inconsistency: namely, BGP implementors must not create further inconsistencies from this point forward. These behavioral changes, though subtle, actually update RFC 1997.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search