RFC 4720: Pseudowire Emulation Edge-to-Edge (PWE3) Frame Check Sequence Retention
In plain English — editorial summary, not part of the RFC
This document defines a mechanism for preserving Frame Check Sequence (FCS) through Ethernet, Frame Relay, High-Level Data Link Control (HDLC), and PPP pseudowires. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4720
- Published
- November 2006
- Authors
- A. Malis; D. Allan; N. Del Regno
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4719Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3)Updated
November 2006
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
- RFC 4726A Framework for Inter-Domain Multiprotocol Label Switching Traffic EngineeringCurrent
November 2006
- RFC 4728The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4Current
February 2007
- RFC 4736Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP)Current
November 2006
- RFC 4750OSPF Version 2 Management Information BaseCurrent
December 2006
- RFC 4687Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS NetworksCurrent
September 2006
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?