RFC 8469: Recommendation to Use the Ethernet Control Word
In plain English — editorial summary, not part of the RFC
The pseudowire (PW) encapsulation of Ethernet, as defined in RFC 4448, specifies that the use of the control word (CW) is optional. In the absence of the CW, an Ethernet PW packet can be misidentified as an IP packet by a label switching router (LSR). This may lead to the selection of the wrong equal-cost multipath (ECMP) path for the packet, leading in turn to the misordering of packets. This problem has become more serious due to the deployment of equipment with Ethernet Media Access Control (MAC) addresses that start with 0x4 or 0x6. The use of the Ethernet PW CW addresses this problem. This document RECOMMENDS the use of the Ethernet PW CW in all but exceptional circumstances. This document updates RFC 4448.
Document record
- Document ID
- RFC8469
- Published
- November 2018
- Authors
- S. Bryant; A. Malis; I. Bagdonas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 4448
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
- RFC 4618Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS NetworksCurrent
September 2006
- RFC 8159Keyed IPv6 TunnelCurrent
May 2017
- RFC 7938Use of BGP for Routing in Large-Scale Data CentersCurrent
August 2016
- RFC 7893Pseudowire Congestion ConsiderationsCurrent
June 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?