[mpls] RFC 6215 on MPLS Transport Profile User-to-Network and Network-to-Network Interfaces

rfc-editor@rfc-editor.org Mon, 11 April 2011 19:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 570183A6AF4; Mon, 11 Apr 2011 12:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id tpLkNAX2YGGm; Mon, 11 Apr 2011 12:20:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C34603A6B41; Mon, 11 Apr 2011 12:20:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 77B90E0784; Mon, 11 Apr 2011 12:20:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110411192059.77B90E0784@rfc-editor.org>
Date: Mon, 11 Apr 2011 12:20:59 -0700
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6215 on MPLS Transport Profile User-to-Network and Network-to-Network Interfaces
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2011 19:21:00 -0000

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

        RFC 6215

        Title:      MPLS Transport Profile User-to-Network and 
                    Network-to-Network Interfaces 
        Author:     M. Bocci, L. Levrau,
                    D. Frost
        Status:     Informational
        Stream:     IETF
        Date:       April 2011
        Mailbox:    matthew.bocci@alcatel-lucent.com, 
        Pages:      6
        Characters: 13619
        Updates:    RFC5921

        I-D Tag:    draft-ietf-mpls-tp-uni-nni-03.txt

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

The framework for MPLS in transport networks (RFC 5921) provides
reference models for the MPLS Transport Profile (MPLS-TP) Transport
Service Interfaces, which are a User-to-Network Interface (UNI), and
a Network-to-Network Interface (NNI).  This document updates those
reference models to show detailed reference points for these
interfaces, along with further clarification of the functional
architecture of MPLS-TP at a UNI and NNI.

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 as defined by the ITU-T.  This document 
is not an Internet Standards Track specification; it is published for 
informational purposes.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

INFORMATIONAL: This memo provides information 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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