A new Request for Comments is now available in online RFC libraries.
RFC 4385
Title: Pseudowire Emulation Edge-to-Edge (PWE3) Control
Word for Use over an MPLS PSN
Author: S. Bryant, G. Swallow,
L. Martini, D. McPherson
Status: Standards Track
Date: February 2006
Mailbox: stbryant@cisco.com,
swallow@cisco.com,
lmartini@cisco.com, danny@arbor.net
Pages: 12
Characters: 22440
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pwe3-cw-06.txt
URL: http://www.rfc-editor.org/rfc/rfc4385.txt
This document describes the preferred design of a Pseudowire
Emulation Edge-to-Edge (PWE3) Control Word to be used over an MPLS
packet switched network, and the Pseudowire Associated Channel
Header. The design of these fields is chosen so that an MPLS Label
Switching Router performing MPLS payload inspection will not confuse
a PWE3 payload with an IP payload. [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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@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@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@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
--6e066bcaaffe83944d34e3491cde686c
A new Request for Comments is now available in online RFC libraries.
RFC 4385
Title: Pseudowire Emulation Edge-to-Edge (PWE3) Control
Word for Use over an MPLS PSN
Author: S. Bryant, G. Swallow,
L. Martini, D. McPherson
Status: Standards Track
Date: February 2006
Mailbox: stbryant@cisco.com,
swallow@cisco.com,
lmartini@cisco.com, danny@arbor.net
Pages: 12
Characters: 22440
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pwe3-cw-06.txt
URL: http://www.rfc-editor.org/rfc/rfc4385.txt
This document describes the preferred design of a Pseudowire
Emulation Edge-to-Edge (PWE3) Control Word to be used over an MPLS
packet switched network, and the Pseudowire Associated Channel
Header. The design of these fields is chosen so that an MPLS Label
Switching Router performing MPLS payload inspection will not confuse
a PWE3 payload with an IP payload. [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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@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@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@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
