[rfc-dist] RFC 4720 on Pseudowire Emulation Edge-to-Edge (PWE3) Frame Check Sequence Retention
rfc-editor@rfc-editor.org
rfc-editor at rfc-editor.org
Tue Nov 14 16:23:34 PST 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4720
Title: Pseudowire Emulation Edge-to-Edge (PWE3) Frame
Check Sequence Retention
Author: A. Malis, D. Allan,
N. Del Regno
Status: Standards Track
Date: November 2006
Mailbox: Andy.Malis at tellabs.com,
dallan at nortelnetworks.com,
nick.delregno at mci.com
Pages: 9
Characters: 18248
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pwe3-fcs-retention-04.txt
URL: http://www.rfc-editor.org/rfc/rfc4720.txt
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]
This document is a product of the Pseudo Wire Emulation Edge to Edge
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is
unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
More information about the rfc-dist
mailing list