[mpls-tp] New RFC: RFC 5718 on An In-Band Data Communication Network For the MPLS Transport Profile]

Loa Andersson <loa@pi.nu> Fri, 08 January 2010 02:41 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A70DD28C0EA for <mpls-tp@core3.amsl.com>; Thu, 7 Jan 2010 18:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6]
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 pfCdVkDJ2O6l for <mpls-tp@core3.amsl.com>; Thu, 7 Jan 2010 18:41:34 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 6F2CA28C0EE for <mpls-tp@ietf.org>; Thu, 7 Jan 2010 18:41:34 -0800 (PST)
Received: from [95.209.177.6] (95.209.177.6.bredband.tre.se [95.209.177.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 282A9D403E; Fri, 8 Jan 2010 03:41:20 +0100 (CET)
Message-ID: <4B469B44.1070303@pi.nu>
Date: Fri, 08 Jan 2010 03:41:08 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: mpls-tp@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [mpls-tp] New RFC: RFC 5718 on An In-Band Data Communication Network For the MPLS Transport Profile]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2010 02:41:35 -0000

All,

we have a new RFC - please join me in congratulating the Dieter
and Adrian.

/Loa

-------- Original Message --------
Subject: [mpls] RFC 5718 on An In-Band Data Communication Network For 
the	MPLS Transport Profile
Date: Thu,  7 Jan 2010 16:50:25 -0800 (PST)
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: mpls@ietf.org, rfc-editor@rfc-editor.org


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


         RFC 5718

         Title:      An In-Band Data Communication Network
                     For the MPLS Transport Profile
         Author:     D. Beller, A. Farrel
         Status:     Standards Track
         Date:       January 2010
         Mailbox:    dieter.beller@alcatel-lucent.com,
                     adrian@olddog.co.uk
         Pages:      8
         Characters: 18997
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-ietf-mpls-tp-gach-dcn-06.txt

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

The Generic Associated Channel (G-ACh) has been defined as a
generalization of the pseudowire (PW) associated control channel to
enable the realization of a control/communication channel that is
associated with Multiprotocol Label Switching (MPLS) Label Switched Paths
(LSPs), MPLS PWs, MPLS LSP segments, and MPLS sections between
adjacent MPLS-capable devices.

The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS
architecture that identifies elements of the MPLS toolkit that may be
combined to build a carrier-grade packet transport network based on
MPLS packet switching technology.

This document describes how the G-ACh may be used to provide the
infrastructure that forms part of the Management Communication
Network (MCN) and a Signaling Communication Network (SCN).
Collectively, the MCN and SCN may be referred to as the Data
Communication Network (DCN).  This document explains how MCN and SCN
messages are encapsulated, carried on the G-ACh, and demultiplexed
for delivery to the management or signaling/routing control plane
components on an MPLS-TP node.  [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


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13