RFC 7212 on MPLS Generic Associated Channel (G-ACh) Advertisement Protocol

rfc-editor@rfc-editor.org Tue, 17 June 2014 23:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC5A31A0170; Tue, 17 Jun 2014 16:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lS_T_JxB3K4l; Tue, 17 Jun 2014 16:26:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3951A0155; Tue, 17 Jun 2014 16:26:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 058A41801C2; Tue, 17 Jun 2014 16:25:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7212 on MPLS Generic Associated Channel (G-ACh) Advertisement Protocol
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140617232534.058A41801C2@rfc-editor.org>
Date: Tue, 17 Jun 2014 16:25:34 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/9a7LmYyYUDvm2_8TQFInEgiIfXI
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 17 Jun 2014 23:26:57 -0000

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

        
        RFC 7212

        Title:      MPLS Generic Associated Channel (G-ACh) 
                    Advertisement Protocol 
        Author:     D. Frost, S. Bryant, M. Bocci
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2014
        Mailbox:    frost@mm.st, 
                    stbryant@cisco.com, 
                    matthew.bocci@alcatel-lucent.com
        Pages:      23
        Characters: 52340
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-gach-adv-08.txt

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

The MPLS Generic Associated Channel (G-ACh) provides an auxiliary
logical data channel associated with a Label Switched Path (LSP), a
pseudowire, or a section (link) over which a variety of protocols may
flow.  These protocols are commonly used to provide Operations,
Administration, and Maintenance (OAM) mechanisms associated with the
primary data channel.  This document specifies simple procedures by
which an endpoint of an LSP, pseudowire, or section may inform the
other endpoints of its capabilities and configuration parameters, or
other application-specific information.  This information may then be
used by the receiver to validate or adjust its local configuration,
and by the network operator for diagnostic purposes.

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/search
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