Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
RFC 8395

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2021-06-10	Jenny Bui	Posted related IPR disclosure Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 8395
2019-05-28	Jasmine Magallanes	Posted related IPR disclosure: Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 8395
2018-06-28	(System)	IANA registries were updated to include RFC8395
2018-06-26	(System)	Received changes through RFC Editor sync (created alias RFC 8395, changed title to 'Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels', changed abstract … Received changes through RFC Editor sync (created alias RFC 8395, changed title to 'Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels', changed abstract to 'This document defines protocol extensions required to synchronize flow label states among Provider Edges (PEs) when using the BGP-based signaling procedures. These protocol extensions are equally applicable to point-to-point Layer 2 Virtual Private Networks (L2VPNs). This document updates RFC 4761 by defining new flags in the Control Flags field of the Layer2 Info Extended Community.', changed pages to 9, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-06-26, changed IESG state to RFC Published, created updates relation between draft-ietf-bess-fat-pw-bgp and RFC 4761)
2018-06-26	(System)	RFC published