RFC 5654 on Requirements of an MPLS Transport Profile

rfc-editor@rfc-editor.org Thu, 24 September 2009 22:53 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 54FF13A6862; Thu, 24 Sep 2009 15:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.603
X-Spam-Status: No, score=-16.603 tagged_above=-999 required=5 tests=[AWL=0.396, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id NHIYtge-gdjD; Thu, 24 Sep 2009 15:53:18 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 7C6A83A6846; Thu, 24 Sep 2009 15:53:18 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 8D08F32CFA2; Thu, 24 Sep 2009 15:53:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5654 on Requirements of an MPLS Transport Profile
From: rfc-editor@rfc-editor.org
Message-Id: <20090924225358.8D08F32CFA2@bosco.isi.edu>
Date: Thu, 24 Sep 2009 15:53:58 -0700
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, 24 Sep 2009 22:53:19 -0000

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

        RFC 5654

        Title:      Requirements of an MPLS Transport 
        Author:     B. Niven-Jenkins, Ed.,
                    D. Brungard, Ed.,
                    M. Betts, Ed.,
                    N. Sprecher, S. Ueno
        Status:     Standards Track
        Date:       September 2009
        Mailbox:    benjamin.niven-jenkins@bt.com, 
        Pages:      31
        Characters: 69999
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-requirements-10.txt

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

This document specifies the requirements of an MPLS Transport Profile
(MPLS-TP).  This document is a product of a joint effort of the
International Telecommunications Union (ITU) and IETF to include an
MPLS Transport Profile within the IETF MPLS and PWE3 architectures to
support the capabilities and functionalities of a packet transport
network as defined by International Telecommunications Union -
Telecommunications Standardization Sector (ITU-T).

This work is based on two sources of requirements: MPLS and PWE3
architectures as defined by IETF, and packet transport networks as
defined by ITU-T.

The requirements expressed in this document are for the behavior of
the protocol mechanisms and procedures that constitute building
blocks out of which the MPLS Transport Profile is constructed.  The
requirements are not implementation requirements.  [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

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
USC/Information Sciences Institute