RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport Network
RFC 5852
|
| Document |
Type |
|
RFC - Proposed Standard
(April 2010; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 5852 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Adrian Farrel
|
|
IESG note |
|
RC 5852
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) D. Caviglia
Request for Comments: 5852 D. Ceccarelli
Category: Standards Track D. Bramanti
ISSN: 2070-1721 Ericsson
D. Li
Huawei Technologies
S. Bardalai
Fujitsu Network
April 2010
RSVP-TE Signaling Extension for LSP Handover from the Management Plane
to the Control Plane in a GMPLS-Enabled Transport Network
Abstract
In a transport network scenario, Data Plane connections controlled by
either a Generalized Multiprotocol Label Switching (GMPLS) Control
Plane (Soft Permanent Connections - SPC) or a Management System
(Permanent Connections - PC) may independently coexist. The ability
of transforming an existing PC into an SPC and vice versa -- without
actually affecting Data Plane traffic being carried over it -- is a
requirement. The requirements for the conversion between permanent
connections and switched connections in a GMPLS Network are defined
in RFC 5493.
This memo describes an extension to GMPLS Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) signaling that enables the
transfer of connection ownership between the Management and the
Control Planes. Such a transfer is referred to as a Handover. This
document defines all Handover-related procedures. This includes the
handling of failure conditions and subsequent reversion to original
state. A basic premise of the extension is that the Handover
procedures must never impact an already established Data Plane
connection.
Caviglia, et al. Standards Track [Page 1]
RFC 5852 RSVP-TE Ext for MP2CP LSP Handover April 2010
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/rfc5852.
Copyright Notice
Copyright (c) 2010 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.
Caviglia, et al. Standards Track [Page 2]
RFC 5852 RSVP-TE Ext for MP2CP LSP Handover April 2010
Table of Contents
1. Introduction ....................................................4
1.1. Dedication .................................................4
2. Terminology .....................................................4
3. Motivation ......................................................4
4. Procedures ......................................................5
4.1. MP-to-CP Handover: LSP Ownership Transfer from
Management Plane to Control Plane ..........................6
4.2. MP-to-CP Handover Procedure Failure Handling ...............7
4.2.1. MP-to-CP Handover Failure - Path Failure ............8
4.2.1.1. MP-to-CP Handover Failure - Path
Message and Data Plane Failure .............8
4.2.1.2. MP-to-CP Handover Failure - Path
Message and Communication Failure ..........8
4.2.2. MP-to-CP Handover Failure - Resv Error ..............9
4.2.2.1. MP-to-CP Handover Failure - Resv
Error and Data Plane Failure ...............9
4.2.2.2. MP-to-CP Handover Failure - Resv
Error and Communication Failure ...........10
Show full document text