[mpls] RFC 6923 on MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T Conventions

rfc-editor@rfc-editor.org Thu, 09 May 2013 20:43 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 327E021F8EBC; Thu, 9 May 2013 13:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.825
X-Spam-Level:
X-Spam-Status: No, score=-101.825 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBS4FpEAjHCq; Thu, 9 May 2013 13:43:48 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8D51F21F8E4C; Thu, 9 May 2013 13:43:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8C166B1E003; Thu, 9 May 2013 13:43:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130509204335.8C166B1E003@rfc-editor.org>
Date: Thu, 09 May 2013 13:43:35 -0700
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6923 on MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T Conventions
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 09 May 2013 20:43:49 -0000

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

        
        RFC 6923

        Title:      MPLS Transport Profile (MPLS-TP) Identifiers 
                    Following ITU-T Conventions 
        Author:     R. Winter, E. Gray,
                    H. van Helvoort, M. Betts
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2013
        Mailbox:    rolf.winter@neclab.eu, 
                    eric.gray@ericsson.com, 
                    huub.van.helvoort@huawei.com,
                    malcolm.betts@zte.com.cn
        Pages:      12
        Characters: 23811
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-itu-t-identifiers-08.txt

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

This document specifies an extension to the identifiers to be used in
the Transport Profile of Multiprotocol Label Switching (MPLS-TP).
Identifiers that follow IP/MPLS conventions have already been
defined.  This memo augments that set of identifiers for MPLS-TP
management and Operations, Administration, and Maintenance (OAM)
functions to include identifier information in a format typically
used by the International Telecommunication Union Telecommunication
Standardization Sector (ITU-T).

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

This is now a Proposed Standard.

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