Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
RFC 5212
| Document | Type | RFC - Informational (July 2008; No errata) | |
|---|---|---|---|
| Authors | Jean-Louis Le Roux , Kohei Shiomoto , Martin Vigoureux , Dimitri Papadimitriou , Deborah Brungard | ||
| Last updated | 2018-12-20 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5212 (Informational) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ross Callon | ||
| Send notices to | (None) | ||
Network Working Group K. Shiomoto
Request for Comments: 5212 NTT
Category: Informational D. Papadimitriou
Alcatel-Lucent
JL. Le Roux
France Telecom
M. Vigoureux
Alcatel-Lucent
D. Brungard
AT&T
July 2008
Requirements for GMPLS-Based
Multi-Region and Multi-Layer Networks (MRN/MLN)
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Abstract
Most of the initial efforts to utilize Generalized MPLS (GMPLS) have
been related to environments hosting devices with a single switching
capability. The complexity raised by the control of such data planes
is similar to that seen in classical IP/MPLS networks. By extending
MPLS to support multiple switching technologies, GMPLS provides a
comprehensive framework for the control of a multi-layered network of
either a single switching technology or multiple switching
technologies.
In GMPLS, a switching technology domain defines a region, and a
network of multiple switching types is referred to in this document
as a multi-region network (MRN). When referring in general to a
layered network, which may consist of either single or multiple
regions, this document uses the term multi-layer network (MLN). This
document defines a framework for GMPLS based multi-region / multi-
layer networks and lists a set of functional requirements.
Shiomoto, et al. Informational [Page 1]
RFC 5212 MRN/MLN Requirements July 2008
Table of Contents
1. Introduction ....................................................3
1.1. Scope ......................................................4
2. Conventions Used in This Document ...............................5
2.1. List of Acronyms ...........................................6
3. Positioning .....................................................6
3.1. Data Plane Layers and Control Plane Regions ................6
3.2. Service Layer Networks .....................................7
3.3. Vertical and Horizontal Interaction and Integration ........8
3.4. Motivation .................................................9
4. Key Concepts of GMPLS-Based MLNs and MRNs ......................10
4.1. Interface Switching Capability ............................10
4.2. Multiple Interface Switching Capabilities .................11
4.2.1. Networks with Multi-Switching-Type-Capable
Hybrid Nodes .......................................12
4.3. Integrated Traffic Engineering (TE) and Resource Control ..12
4.3.1. Triggered Signaling ................................13
4.3.2. FA-LSPs ............................................13
4.3.3. Virtual Network Topology (VNT) .....................14
5. Requirements ...................................................15
5.1. Handling Single-Switching and
Multi-Switching-Type-Capable Nodes ........................15
5.2. Advertisement of the Available Adjustment Resources .......15
5.3. Scalability ...............................................16
5.4. Stability .................................................17
5.5. Disruption Minimization ...................................17
5.6. LSP Attribute Inheritance .................................17
5.7. Computing Paths with and without Nested Signaling .........18
5.8. LSP Resource Utilization ..................................19
5.8.1. FA-LSP Release and Setup ...........................19
5.8.2. Virtual TE Links ...................................20
5.9. Verification of the LSPs ..................................21
5.10. Management ...............................................22
6. Security Considerations ........................................24
7. Acknowledgements ...............................................24
8. References .....................................................25
8.1. Normative References ......................................25
8.2. Informative References ....................................25
9. Contributors' Addresses ........................................26
Show full document text