[rfc-dist] RFC 4816 on Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Feb 16 09:44:11 PST 2007


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4816

        Title:      Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous 
                    Transfer Mode (ATM) Transparent Cell Transport 
                    Service 
        Author:     A. Malis, L. Martini,
                    J. Brayley, T. Walsh
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    andrew.g.malis at verizon.com, 
                    lmartini at cisco.com, 
                    jeremy.brayley at ecitele.com, twalsh at juniper.net
        Pages:      5
        Characters: 10269
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-cell-transport-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4816.txt

The document describes a transparent cell transport service that
makes use of the "N-to-one" cell relay mode for Pseudowire Emulation
Edge-to-Edge (PWE3) Asynchronous Transfer-Mode (ATM) cell
encapsulation.  [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.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list