[rfc-dist] RFC 5143 on Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation Service over MPLS (CEM) Encapsulation
rfc-editor at rfc-editor.org
Fri Feb 22 17:12:41 PST 2008
A new Request for Comments is now available in online RFC libraries.
Title: Synchronous Optical Network/Synchronous Digital
Hierarchy (SONET/SDH) Circuit Emulation Service
over MPLS (CEM) Encapsulation
Author: A. Malis, J. Brayley,
J. Shirron, L. Martini,
Date: February 2008
Mailbox: andrew.g.malis at verizon.com,
jeremy.brayley at ecitele.com,
john.shirron at ecitele.com, lmartini at cisco.com,
steve.vogelsang at alcatel-lucent.com
Obsoleted by: RFC4842
I-D Tag: draft-malis-sonet-ces-mpls-09.txt
This document describes a historical method for encapsulating
Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)
Path signals for transport across packet-switched networks (PSNs).
The PSNs explicitly supported by this document include MPLS and
IP. Note that RFC 4842 describes the standards-track protocol for
this functionality, and new implementations must use RFC 4842 rather
than this document except when interoperability with older
implementations is desired. This memo defines a Historic
Document for the Internet community.
HISTORIC: This memo defines a Historic Document for the Internet
community. It does not specify an Internet standard of any kind.
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
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
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.
The RFC Editor Team
USC/Information Sciences Institute
IETF-Announce mailing list
IETF-Announce at ietf.org
More information about the rfc-dist