Skip to main content

Policy Behavior for Well-Known BGP Communities
RFC 8642

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed metadata: changed keywords to '['Operations', 'Inter-Provider Communication']' from '[]'
2026-05-20
(System) Metadata update from RFC Editor
2026-05-20
(System) Changed author "S. Bayraktar": changed name from "Serpil Bayraktar" to "S. Bayraktar", cleared country (was "United States of America"), changed order from "3" to "4"
2026-05-20
(System) Changed author "R. Bonica": changed name from "Ron Bonica" to "R. Bonica", cleared country (was "US"), changed order from "2" to "3"
2026-05-20
(System) Changed author "R. Bush": changed name from "Randy Bush" to "R. Bush", cleared country (was "US"), changed order from "1" to "2"
2026-05-20
(System) Changed author "J. Borkenhagen": changed name from "Jay Borkenhagen" to "J. Borkenhagen", cleared country (was "United States of America"), changed order from "0" to "1"
2026-05-20
(System) Metadata update from RFC Editor
2019-08-26
Gunter Van de Velde Closed request for Telechat review by OPSDIR with state 'Overtaken by Events'
2019-08-26
Gunter Van de Velde Assignment of request for Telechat review by OPSDIR to Carlos Pignataro was marked no-response
2019-08-09
(System) IANA registries were updated to include RFC8642
2019-08-07
(System)
Received changes through RFC Editor sync (created alias RFC 8642, changed title to 'Policy Behavior for Well-Known BGP Communities', changed abstract to 'Well-known BGP …
Received changes through RFC Editor sync (created alias RFC 8642, changed title to 'Policy Behavior for Well-Known BGP Communities', changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-08-07, changed IESG state to RFC Published, created updates relation between draft-ietf-grow-wkc-behavior and RFC 1997)
2019-08-07
(System) RFC published