RFC 5960 on MPLS Transport Profile Data Plane Architecture

rfc-editor@rfc-editor.org Thu, 19 August 2010 23:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7127F3A6A7B; Thu, 19 Aug 2010 16:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[AWL=-0.611, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zFWMdN6V86eD; Thu, 19 Aug 2010 16:21:59 -0700 (PDT)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 9BD783A6A75; Thu, 19 Aug 2010 16:21:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BD086E06EB; Thu, 19 Aug 2010 16:22:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5960 on MPLS Transport Profile Data Plane Architecture
From: rfc-editor@rfc-editor.org
Message-Id: <20100819232234.BD086E06EB@rfc-editor.org>
Date: Thu, 19 Aug 2010 16:22:34 -0700 (PDT)
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Aug 2010 23:22:00 -0000

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

        
        RFC 5960

        Title:      MPLS Transport Profile Data Plane 
                    Architecture 
        Author:     D. Frost, Ed.,
                    S. Bryant, Ed.,
                    M. Bocci, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    danfrost@cisco.com, 
                    stbryant@cisco.com, 
                    matthew.bocci@alcatel-lucent.com
        Pages:      15
        Characters: 31764
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-data-plane-04.txt

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

The Multiprotocol Label Switching Transport Profile (MPLS-TP) is the
set of MPLS protocol functions applicable to the construction and
operation of packet-switched transport networks.  This document
specifies the subset of these functions that comprises the MPLS-TP
data plane: the architectural layer concerned with the encapsulation
and forwarding of packets within an MPLS-TP network.

This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
(PWE3) architectures to support the capabilities and functionalities
of a packet transport network.  [STANDARDS TRACK]

This document is a product of the Multiprotocol Label Switching 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC