RFC 6898 on Link Management Protocol Behavior Negotiation and Configuration Modifications

rfc-editor@rfc-editor.org Fri, 29 March 2013 21:17 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB4A21E8049; Fri, 29 Mar 2013 14:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.084
X-Spam-Level:
X-Spam-Status: No, score=-102.084 tagged_above=-999 required=5 tests=[AWL=-0.084, 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 ovQ2D3jx-9cx; Fri, 29 Mar 2013 14:17:25 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A9DA921E8048; Fri, 29 Mar 2013 14:17:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AA601B1E003; Fri, 29 Mar 2013 14:16:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6898 on Link Management Protocol Behavior Negotiation and Configuration Modifications
From: rfc-editor@rfc-editor.org
Message-Id: <20130329211648.AA601B1E003@rfc-editor.org>
Date: Fri, 29 Mar 2013 14:16:48 -0700
Cc: ccamp@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 29 Mar 2013 21:17:31 -0000

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

        
        RFC 6898

        Title:      Link Management Protocol Behavior Negotiation 
                    and Configuration Modifications 
        Author:     D. Li, D. Ceccarelli,
                    L. Berger
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2013
        Mailbox:    huawei.danli@huawei.com, 
                    daniele.ceccarelli@ericsson.com, 
                    lberger@labn.net
        Pages:      11
        Characters: 21446
        Updates:    RFC 4204, RFC 4207, RFC 4209, RFC 5818

        I-D Tag:    draft-ietf-ccamp-lmp-behavior-negotiation-11.txt

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

The Link Management Protocol (LMP) is used to coordinate the
properties, use, and faults of data links in networks controlled by
Generalized Multiprotocol Label Switching (GMPLS).  This document
defines an extension to LMP to negotiate capabilities and indicate
support for LMP extensions.  The defined extension is compatible with
non-supporting implementations.

This document updates RFC 4204, RFC 4207, RFC 4209, and RFC 5818.

This document is a product of the Common Control and Measurement Plane 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