RFC 4717 on Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks

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

        RFC 4717

        Title:      Encapsulation Methods for Transport of 
                    Asynchronous Transfer Mode (ATM) over MPLS 
                    Networks 
        Author:     L. Martini, J. Jayakumar,
                    M. Bocci, N. El-Aawar,
                    J. Brayley, G. Koleyni
        Status:     Standards Track
        Date:       December 2006
        Mailbox:    lmartini@cisco.com, 
                    jjayakum@cisco.com, 
                    matthew.bocci@alcatel.co.uk,  nna@level3.net, 
                    jeremy.brayley@ecitele.com,  
                    ghassem@nortelnetworks.com
        Pages:      40
        Characters: 86173
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-atm-encap-11.txt

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

An Asynchronous Transfer Mode (ATM) Pseudowire (PW) is used to carry
ATM cells over an MPLS network.  This enables service providers to
offer "emulated" ATM services over existing MPLS networks.  This
document specifies methods for the encapsulation of ATM cells within
a pseudowire.  It also specifies the procedures for using a PW to
provide an ATM service.  [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.

The RFC Editor Team
USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce