Link Management Protocol Behavior Negotiation and Configuration Modifications
RFC 6898
|
| Document |
Type |
|
RFC - Proposed Standard
(March 2013; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-li-ccamp-lmp-behavior-negotiation
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
|
|
Document shepherd |
|
Deborah Brungard
|
| IESG |
IESG state |
|
RFC 6898 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Adrian Farrel
|
|
IESG note |
|
Deborah Brungard (db3546@att.com) is the Document Shepherd.
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) D. Li
Request for Comments: 6898 Huawei
Updates: 4204, 4207, 4209, 5818 D. Ceccarelli
Category: Standards Track Ericsson
ISSN: 2070-1721 L. Berger
LabN
March 2013
Link Management Protocol Behavior Negotiation and
Configuration Modifications
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6898.
Li, et al. Standards Track [Page 1]
RFC 6898 LMP Behavior Negotiation March 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
1.1. Conventions Used in This Document ..........................4
2. LMP Message Modifications .......................................4
2.1. Modified Message Formats ...................................4
2.2. Processing .................................................5
3. LMP Behavior Negotiation ........................................6
3.1. BehaviorConfig C-Type Format ...............................6
3.2. Processing .................................................7
4. Backward Compatibility ..........................................7
5. Security Considerations .........................................8
6. IANA Considerations .............................................9
6.1. New LMP Class Type .........................................9
6.2. New Capabilities Registry ..................................9
7. Normative References ...........................................10
8. Acknowledgments ................................................10
9. Contributors ...................................................10
Li, et al. Standards Track [Page 2]
RFC 6898 LMP Behavior Negotiation March 2013
1. Introduction
The Link Management Protocol (LMP) [RFC4204] has been successfully
deployed in networks controlled by Generalized Multiprotocol Label
Switching (GMPLS).
New LMP behaviors and protocol extensions have been introduced in a
number of IETF documents, as set out later in this section. It is
likely that future extensions will be made to support additional
functions.
In a network, if one LMP-capable node supports a new behavior or
protocol extension but its adjacent node does not, it is beneficial
to have a protocol mechanism to discover the capabilities of peer
nodes so that the right protocol extensions can be selected and the
correct features can be enabled. There are no such procedures
defined in the base LMP specification [RFC4204]. [RFC4209] defined a
specific mechanism to identify support for the functions specified in
that document. This document defines an LMP extension to support the
Show full document text