Common Control and Measurement Plane (ccamp) Internet Drafts
| Ethernet Traffic Parameters | |||||||||||||||||
|
This document describes the Metro Ethernet Forum (MEF) - specific Ethernet Traffic Parameters as described in MEF10.1 when using Generalized Multi-Protocol Label Switching (GMPLS) Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling. | ||||||||||||||||
| Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks | |||||||||||||||||
|
MPLS-TE Graceful Shutdown is a method for explicitly notifying the nodes in a Traffic Engineering (TE) enabled network that the TE capability on a link or on an entire Label Switching Router (LSR) is going to be disabled. MPLS-TE graceful shutdown mechanisms are tailored toward addressing planned outage in the network. This document provides requirements and protocol mechanisms to reduce/eliminate traffic disruption in the event of a planned shutdown of a network resource. These operations are equally applicable to both MPLS and its Generalized MPLS (GMPLS) extensions. | ||||||||||||||||
| Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS) | |||||||||||||||||
|
This document describes requirements for, and use of, the Generalized Multi-Protocol Label Switching (GMPLS) control plane in conjunction with the Virtual Concatenation (VCAT) layer 1 inverse multiplexing mechanism and its companion Link Capacity Adjustment Scheme (LCAS) which can be used for hitless dynamic resizing of the inverse multiplex group. These techniques apply to Optical Transport Network (OTN), Synchronous Optical Network (SONET), Synchronous Digital Hierarchy (SDH), and Plesiochronous Digital Hierarchy (PDH) signals. | ||||||||||||||||
| Traffic Engineering Database Management Information Base in support of MPLS-TE/GMPLS | |||||||||||||||||
|
This memo defines the Management Information Base (MIB) objects in order to manage traffic engineering database (TED) information with extension in support of Multi-Protocol Label Switching (MPLS) with traffic engineering (TE) as well as Generalized MPLS (GMPLS) for use with network management protocols. | ||||||||||||||||
| draft-ietf-ccamp-pc-and-sc-reqs-06.txt | |||||||||||||||||
|
From a Carrier perspective, the possibility of turning a Permanent Connection (PC) into a Soft Permanent Connection (SPC) and vice versa, without actually affecting Data Plane traffic being carried over it, is a valuable option. In other terms, such operation can be seen as a way of transferring the ownership and control of an existing and in-use Data Plane connection between the Management Plane and the Control Plane, leaving its Data Plane state untouched. This memo sets out the requirements for such procedures within a Generalized Multiprotocol Label Switching (GMPLS) network. | ||||||||||||||||
| OSPF Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering | |||||||||||||||||
|
This document describes extensions to the OSPF version 2 and 3 protocols to support Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems (ASes). OSPF-TE v2 and v3 extensions are defined for the flooding of TE information about inter-AS links which can be used to perform inter-AS TE path computation. No support for flooding information from within one AS to another AS is proposed or defined in this document. | ||||||||||||||||
| Description of the RSVP-TE Graceful Restart Procedures | |||||||||||||||||
|
The Hello message for the Resource Reservation Protocol (RSVP) has been defined to establish and maintain basic signaling node adjacencies for Label Switching Routers (LSRs) participating in a Multiprotocol Label Switching (MPLS) traffic engineered (TE) network. The Hello message has been extended for use in Generalized MPLS (GMPLS) network for state recovery of control channel or nodal faults. | ||||||||||||||||
| Generalized Multi-Protocol Label Switching (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN) | |||||||||||||||||
|
There are requirements for the support of networks ccomprising LSRs with different data plane switching layers controlled by a single Generalized Multi Protocol Label Switching (GMPLS) control plane instance, referred to as GMPLS Multi-Layer Networks/Multi-Region Networks (MLN/MRN). This document defines extensions to GMPLS routing and signaling protocols so as to support the operation of GMPLS Multi-Layer/Multi-Region Networks. | ||||||||||||||||
| ISIS Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering | |||||||||||||||||
|
This document describes extensions to the ISIS (ISIS) protocol to support Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems (ASes). It defines ISIS-TE extensions for the flooding of TE information about inter-AS links which can be used to perform inter- AS TE path computation. No support for flooding information from within one AS to another AS is proposed or defined in this document. | ||||||||||||||||
| GMPLS Ethernet Label Switching Architecture and Framework | |||||||||||||||||
|
There has been significant recent work in increasing the capabilities of Ethernet switches and Ethernet forwarding models. As a consequence, the role of Ethernet is rapidly expanding into "transport networks" that previously were the domain of other technologies such as SONET/SDH TDM and ATM. This document defines an architecture and framework for a GMPLS based control plane for Ethernet in this "transport network" capacity. GMPLS has already been specified for similar technologies. Some additional extensions to the GMPLS control plane are needed and this document provides a framework for these extensions.Contents | ||||||||||||||||
| Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using RSVP-TE | |||||||||||||||||
|
Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may be established using the Resource Reservation Protocol Traffic Engineering (RSVP-TE) extensions. This protocol includes an object (the SESSION_ATTRIBUTE object) that carries a Flags field used to indicate options and attributes of the LSP. That Flags field has eight bits allowing for eight options to be set. Recent proposals in many documents that extend RSVP-TE have suggested uses for each of the previously unused bits. This document defines a new object for RSVP-TE messages that allows the signaling of further attribute bits and also the carriage of arbitrary attribute parameters to make RSVP-TE easily extensible to support new requirements. Additionally, this document defines a way to record the attributes applied to the LSP on a hop-by-hop basis. | ||||||||||||||||
| GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs) | |||||||||||||||||
|
This document defines a method for the support of GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs). The presented approach is applicable to any switching technology and builds on the original RSVP model for the transport of traffic related parameters. The procedures described in this document are experimental. | ||||||||||||||||
| Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS Networks | |||||||||||||||||
|
Generalized Multi-Protocol Label Switching (GMPLS) is one of the most promising candidate technologies for future data transmission network. GMPLS has been developed to control and operate different kinds of network elements, such as conventional routers, switches, Dense Wavelength Division Multiplexing (DWDM) systems, Add- Drop Multiplexors (ADMs), photonic cross-connects (PXCs), optical cross- connects (OXCs), etc. Dynamic provisioning ability of these physically diverse devices differs from each other drastically. At the same time, the need for Dynamicly provisioned connections is increasing because optical networks are being deployed in metro areas. As different applications have varied requirements in the provisioning performance of optical networks, it is imperative to define standardized metrics and procedures such that the performance of networks and application needs can be mapped to each other. This document provides a series of performance metrics to evaluate the dynamic LSP provisioning performance in GMPLS networks, specifically the Dynamic LSP setup/release performance. These metrics can depict the features of GMPLS networks in LSP dynamic provisioning. They can also be used in operational networks for carriers to monitor the control plane performance in realtime. | ||||||||||||||||
| RSVP Extensions for Path Key Support | |||||||||||||||||
|
Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Paths (LSPs) may be computed by Path Computation Elements (PCEs). Where the TE LSP crosses multiple domains, such as Autonomous Systems (ASes), the path may be computed by multiple PCEs that cooperate, with each responsible for computing a segment of the path. To preserve confidentiality of topology within each AS, the PCE supports a mechanism to hide the contents of a segment of a path, called the Confidential Path Segment (CPS), by encoding the contents as a Path Key Subobject (PKS). This document describes how to carry Path Key Subobjects in the Resource Reservation Protocol (RSVP) Explicit Route Objects (EROs) and Record Route Object (RROs) so facilitate confiedntiality in the signaling of inter-domain TE LSPs. | ||||||||||||||||
| RSVP-TE Signaling Extension For The Conversion Between Permanent Connections And Soft Permanent Connections In A GMPLS Enabled Transport Network. | |||||||||||||||||
|
We would like to dedicate this work to our friend and colleague Dino Bramanti, who passed away at the early age of 38. Dino has been involved in this work since its beginning. In a transport network scenario, where Data Plane connections controlled either by GMPLS Control Plane (Soft Permanent Connections - SPC) or by Management System (Permanent Connections - PC) may independently coexist, the ability of transforming an existing PC into a SPC and vice versa - without actually affecting Data Plane traffic being carried over it - is a requirement. See draft "draft-ietf-ccamp-pc-and-reqs-04.txt [1]. This memo provides a minor extension to RSVP-TE [RFC2205],[RFC3471],[RFC3473],[RFC4872] signaling protocol, within GMPLS architecture, to enable such connection ownership transfer and describes the proposed procedures. Failure conductions and subsequent roll back are also illustrated taking into account that an handover failure must not impact the already established data plane connections. | ||||||||||||||||
| GMPLS control of Ethernet PBB-TE | |||||||||||||||||
|
This specification is complementary to the GMPLS controlled Ethernet architecture document [ARCH] and describes the technology specific aspects of GMPLS control for Provider Backbone Bridging Traffic Engineering (PBB-TE) [IEEE 802.1Qay]. The necessary GMPLS extensions and mechanisms are described to establish Ethernet PBB-TE point to point (P2P) and point to multipoint (P2MP) connections. This document supports, but does not modify, the standard IEEE data plane. | ||||||||||||||||
| Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 Ethernet Service Switching | |||||||||||||||||
|
This document describes a method for controlling two specific types of Ethernet switching via Generalized Multi-Protocol Label Switching (GMPLS). This document supports the types of switching implied by the Ethernet services that have been defined in the context of the Metro Ethernet Forum (MEF) and International Telecommunication Union (ITU) G.8011. Specifically, switching in support of Ethernet private line service and Ethernet virtual private line service. Support for MEF and ITU defined parameters are also covered. Some of the extensions defined in this document are generic in nature and not specific to Ethernet. | ||||||||||||||||
| Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 User-Network Interface (UNI) | |||||||||||||||||
|
This document describes a method for controlling two specific types of Ethernet switching via a Generalized Multi-Protocol Label Switching (GMPLS) based User-Network Interface (UNI). This document supports the types of switching required to implied by the Ethernet services that have been defined in the context of the Metro Ethernet Forum (MEF) and International Telecommunication Union (ITU) G.8011. This document is the UNI companion to "Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 Ethernet Service Switching". This document does not define or limit the underlying intra-domain or Internal NNI (I-NNI) technology used to support the UNI. | ||||||||||||||||
| Framework for GMPLS and PCE Control of Wavelength Switched Optical Networks (WSON) | |||||||||||||||||
|
This memo provides a framework for applying Generalized Multi- Protocol Label Switching (GMPLS) and the Path Computation Element (PCE) architecture to the control of wavelength switched optical networks (WSON). In particular we provide control plane models for key wavelength switched optical network subsystems and processes. The subsystems include wavelength division multiplexed links, tunable laser transmitters, reconfigurable optical add/drop multiplexers (ROADM) and wavelength converters. Lightpath provisioning, in general, requires the routing and wavelength assignment (RWA) process. This process is reviewed and the information requirements, both static and dynamic for this process are presented, along with alternative implementation scenarios that could be realized via GMPLS/PCE and/or extended GMPLS/PCE protocols. This memo does NOT address optical impairments in any depth and focuses on topological elements and path selection constraints that are common across different WSON environments. It is expected that a variety of different techniques will be applied to optical impairments depending on the type of WSON, such as access, metro or long haul. | ||||||||||||||||
| Generalized Labels for G.694 Lambda-Switching Capable Label Switching Routers | |||||||||||||||||
|
Technology in the optical domain is constantly evolving and as a consequence new equipment providing lambda switching capability has been developed and is currently being deployed. However, RFC 3471 has defined that a wavelength label (section 3.2.1.1) "only has significance between two neighbors" and global wavelength continuity is not considered. In order to achieve interoperability in a network composed of next generation lambda switch-capable equipment, this document defines a standard lambda label format, being compliant with ITU-T G.694. Moreover some consideration on how to ensure lambda continuity with RSVP-TE is provided. This document is a companion to the Generalized Multi-Protocol Label Switching (GMPLS) signaling. It defines the label format when Lambda Switching is requested in an all optical network. | ||||||||||||||||
| Service Provider Requirements for Ethernet control with GMPLS | |||||||||||||||||
|
Generalized Multi-Protocol Label Switching (GMPLS) is applicable to Ethernet switches supporting Provider Backbone Bridge Traffic Engineering (PBB-TE) networks. The GMPLS controlled Ethernet label switch network not only automates creation of Ethernet Label Switched Paths(Eth-LSPs), it also provides sophisticated Eth-LSP recovery Mechanisms such as protection and restoration of an Eth-LSP. This document describes the requirements for the set of solutions of GMPLS controlled Ethernet label switch networks. | ||||||||||||||||
| Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Channel Set Label Extensions | |||||||||||||||||
|
This document describes two technology independent extensions to Generalized Multi-Protocol Label Switching. The first extension defines the new switching type Data Channel Switching Capable. Data Channel Switching Capable interfaces are able to support switching of the whole digital channel presented on single channel interfaces. The second extension defines a new type of generalized label and updates related objects. The new label is called the Generalized Channel_Set Label and allows more than one data plane label to be controlled as part of an LSP. | ||||||||||||||||
| Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks | |||||||||||||||||
|
This document provides an information model of information needed by the routing and wavelength assignment (RWA) process in wavelength switched optical networks (WSONs). The purpose of information described in this model is to facilitate constrained lightpath computation in WSONs. In particular in cases where there are no or a limited number of wavelength converters available in the WSON. This model currently does not include optical impairments. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Common Control and Measurement Plane (ccamp)
In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:
Additional CCAMP Web Page
Last Modified: 2008-09-19
Additional information is available at tools.ietf.org/wg/ccamp
Chair(s):
Routing Area Director(s):
Routing Area Advisor:
Technical Advisor(s):
Mailing Lists:
General Discussion: ccamp@ops.ietf.orgTo Subscribe: majordomo@ops.ietf.org
In Body: subscribe ccamp
Archive: https://ops.ietf.org/lists/ccamp
Description of Working Group:
Organizational OverviewThe CCAMP working group coordinates the work within the IETF
defining a common control plane and a separate common measurement
plane for physical path and core tunneling technologies of Internet
and telecom service providers (ISPs and SPs), e.g. O-O and O-E-O
optical switches, TDM Switches, Ethernet Switches, ATM and Frame
Relay switches, IP encapsulation tunneling technologies, and MPLS
in cooperation with the MPLS WG.
In this context, measurement refers to the acquisition and
distribution of attributes relevant to the setting up of tunnels
and paths.
CCAMP WG work scope includes:
- Definition of protocol-independent metrics and parameters
(measurement attributes) for describing links and paths that are
required for routing and signaling. These will be developed in
conjunction with requests and requirements from other WGs to
ensure overall usefulness.
- Definition of protocol(s) and extensions to them required for
link and path attribute measurement. Link Management Protocol
(LMP) is included here.
- Functional specification of extensions for routing (OSPF, ISIS)
and signalling (RSVP-TE) required for path establishment.
Protocol formats and procedures that embody these extensions will
be done jointly with the WGs supervising those protocols.
- Definition of the mechanisms required to determine the route and
properties of an established path (tunnel tracing).
- Definition of management objects (e.g. as part of MIB modules) and
OAM techniques relevant to the protocols and extensions specified
within the WG.
- Work on traffic-engineering GMPLS mechanisms and protocol
extensions to support source-controlled and explicitly-routed
Ethernet data paths for Ethernet data planes that are already
approved by an Standards Development Organization (SDO) with
responsibility for the Ethernet data plane. It is expected that the
primary SDO in this case is the IEEE. Note that the specification or
modification of Ethernet data planes is out of scope.
- Work on GMPLS mechanisms and protocol extensions to support the
transport profile of MPLS (MPLS-TP) in cooperation with the MPLS,
L2VPN, and PWE3 Working Group and in coordination with the
requirements expressed jointly by the IETF and ITU-T.
CCAMP WG currently works on the following tasks:
- Define how the properties of network resources gathered by a
measurement protocol can be distributed in existing routing
protocols, such as OSPF and IS-IS. CCAMP defines the generic
description of the properties and how they are distributed in
OSPF. The specifics of distribution within IS-IS are being
addressed in the ISIS WG.
- Define signaling and routing mechanisms and extensions to allow
path and tunnel setup and maintenance across multiple domains,
where a domain may be an IGP area, an Autonomous System, or any
other region of topological visibility. To this end, work
cooperatively with the PCE and MPLS WGs.
- Define abstract link and path properties needed for link and
path protection. Specify signalling mechanisms for path
protection, diverse routing and fast path restoration. Ensure
that multi-layer path protection and restoration functions are
achievable using the defined signalling, routing, and measurement
protocols, either separately or in combination.
- Identify which requirements for signaling and routing for
Automatically Switched Optical Network (ASON) are not currently met
by protocols defined in CCAMP; based on these, define mechanisms to
address these requirements.
- Produce extensions to the CCAMP WG protocols and RFCs necessary
to create an MPLS Transport Profile (MPLS TP). The work on the
MPLS TP will be coordinated between the MPLS, L2VPN, PWE3, and CCAMP
working groups that are jointly chartered to do MPLS TP work.
In doing this work, the WG will work closely with at least the
following other WGs: MPLS, L2VPN, PWE3, ISIS, OSPF, IDR, L1VPN and PCE.
The WG will also cooperate with the ITU-T and the IEEE 802.1.
Goals and Milestones:
| Done | Post strawman WG goals and charter | |
| Done | Identify and document a limited set of candidate solutions for signalling and for measurement. Among candidate control solutions to be considered are the existing GMPLS drafts. | |
| Done | Build appropriate design teams | |
| Done | Submit WG document defining path setup portions of common control plane protocol | |
| Done | Submit WG document defining common measurement plane protocol | |
| Done | Submit LMP MIB to IESG | |
| Done | Submit protection & restoration documents to IESG | |
| Done | Submit ASON signaling requirements doc to IESG | |
| Done | Submit GMPLS MIBs to IESG | |
| Done | Produce CCAMP WG document for generic tunnel tracing protocol | |
| Done | Produce CCAMP WG document for multi-area/AS signaling and routing | |
| Done | Submit ASON routing requirements doc to IESG | |
| Done | Submit revised charter and milestones to IESG for IESG consideration of more detailed deliverables and determination of usefulness of continuation of WG | |
| Done | First version WG I-D for Advertising TE Node Capabilities in ISIS and OSPF | |
| Done | First version WG I-D for Automatic discovery of MPLS-TE mesh membership | |
| Done | Submit ASON Routing evaluation I-D for IESG review | |
| Done | Cross-WG review of I-D for Advertising TE Node Capabilities in ISIS and OSPF | |
| Done | First version WG I-D MPLS to GMPLS migration strategies | |
| Done | First version WG I-D Requirements for Multi-Layer and Multi-Region Networks | |
| Done | First version WG I-D for Evaluation of existing protocols for MLN/MRN | |
| Done | First version of WG I-D for ASON Routing solutions | |
| Done | Submit RSVP-TE extensions for inter-domain signaling I-D for IESG review | |
| Done | Submit Per-domain path computation signaling I-D for IESG review | |
| Done | First version of WG I-D for OSPF-TE/GMPLS MIB module | |
| Done | Submit GMPLS signaling in support of Call Management I-D for IESG review | |
| Done | First version WG Informational I-D for Analysis of inter-domain issues for disjoint and protected paths | |
| Done | Submit I-D for Advertising TE Node Capabilities in ISIS and OSPF for IESG review | |
| Done | First version WG I-D for Protocol solutions for MLN/MRN | |
| Done | Submit GMPLS/ASON lexicography I-D for IESG review | |
| Done | First version WG I-D MPLS-GMPLS interworking requirements and solutions | |
| Done | Submit LSP Stitching I-D for IESG review | |
| Done | Submit I-D for Automatic discovery of MPLS-TE mesh membership for IESG review | |
| Done | First version WG I-D GMPLS OAM Requirements | |
| Done | Submit GMPLS routing and signaling interoperability advice I-D for IESG review | |
| Done | Submit MPLS to GMPLS migration strategies I-D for IESG review | |
| Done | Submit Requirements for Multi-Layer and Multi-Region Networks I-D for IESG review | |
| Done | Submit MPLS-GMPLS interworking requirements and solutions I-D for IESG review | |
| Done | Submit Evaluation of existing protocols for MLN/MRN for IESG review | |
| Done | First version WG I-Ds for GMPLS source-controlled and explicitly-routed Ethernet networks | |
| Done | Submit Informational I-D for Analysis of inter-domain issues for disjoint and protected paths for IESG review | |
| Aug 2008 | First version of Working Group draft providing Control Plane Framework for MPLS-TP | |
| Sep 2008 | Submit OSPF-TE/GMPLS MIB module for MIB doctor and IESG review | |
| Oct 2008 | First version of Working Group draft defining RSVP-TE extensions for MPLS-TP | |
| Dec 2008 | Submit ASON Routing solutions I-D for IESG review | |
| Dec 2008 | Submit GMPLS OAM Requirements I-D for IESG review | |
| Jan 2009 | Submit protocol extensions for GMPLS source-controlled and explicitly-routed Ethernet networks for IESG review | |
| Feb 2009 | Submit Protocol solutions for MLN/MRN I-D for IESG review | |
| Mar 2009 | Submit Control Plane Framework for MPLS-TP for IESG review | |
| Jun 2009 | Submit RSVP-TE extensions for MPLS-TP for IESG review | |
| Jun 2009 | Recharter or close Working Group |
Internet-Drafts:
Ethernet Traffic Parameters (27238 bytes)Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks (27291 bytes)
Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS) (44413 bytes)
Traffic Engineering Database Management Information Base in support of MPLS-TE/GMPLS (55849 bytes)
draft-ietf-ccamp-pc-and-sc-reqs-06.txt (23682 bytes)
OSPF Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (42906 bytes)
Description of the RSVP-TE Graceful Restart Procedures (43190 bytes)
Generalized Multi-Protocol Label Switching (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN) (43798 bytes)
ISIS Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (47117 bytes)
GMPLS Ethernet Label Switching Architecture and Framework (43927 bytes)
Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using RSVP-TE (50848 bytes)
GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs) (30583 bytes)
Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS Networks (85166 bytes)
RSVP Extensions for Path Key Support (18406 bytes)
RSVP-TE Signaling Extension For The Conversion Between Permanent Connections And Soft Permanent Connections In A GMPLS Enabled Transport Network. (55924 bytes)
Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 User-Network Interface (UNI) (23033 bytes)
Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 Ethernet Service Switching (35193 bytes)
GMPLS control of Ethernet PBB-TE (70854 bytes)
Framework for GMPLS and PCE Control of Wavelength Switched Optical Networks (WSON) (79292 bytes)
Generalized Labels for G.694 Lambda-Switching Capable Label Switching Routers (23325 bytes)
Service Provider Requirements for Ethernet control with GMPLS (24050 bytes)
Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Channel Set Label Extensions (21540 bytes)
Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks (30157 bytes)
Request For Comments:
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description (RFC 3471) (72105 bytes) updated by RFC 4201,RFC 4328,RFC 4872Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions (RFC 3472) (49006 bytes) updated by RFC 3468,RFC 4201
Generalized Multi-Protocol Label Switching (GMPLS)Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions (RFC 3473) (91808 bytes) updated by RFC 4003,RFC 4201,RFC 4420,RFC 4783,RFC 4873,RFC 4874,RFC 4974,RFC 5063,RFC 5151
Tracing Requirements for Generic Tunnels (RFC 3609) (17859 bytes)
Generalized Multiprotocol Label Switching Extensions for SONET and SDH Control (RFC 3946) (52205 bytes) obsoleted by RFC 4606
Generalized Multi-Protocol Label Switching Architecture (RFC 3945) (166700 bytes)
GMPLS Signaling Procedure For Egress Control (RFC 4003) (10306 bytes) updates RFC 3473
Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON) (RFC 4139) (36660 bytes)
Generalize Multiprotocol Label Switching(GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model (RFC 4208) (28693 bytes)
Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages (RFC 4207) (29390 bytes)
Link Management Protocol (LMP) (RFC 4204) (186515 bytes)
OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (RFC 4203) (23130 bytes) updates RFC 3630
Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) (RFC 4202) (57333 bytes)
Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems (RFC 4209) (33906 bytes)
Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON) (RFC 4258) (48558 bytes)
Framework for Generalized Multi-Protocol Label Switching (GMPLS)-based Control of Synchronous Digital Hierarchy/Synchronous Optical Networking (SDH/SONET) Networks (RFC 4257) (86974 bytes)
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control (RFC 4328) (52145 bytes) updates RFC 3471
Link Management Protocol (LMP) Management Information Base (MIB) (RFC 4327) (150509 bytes) obsoleted by RFC 4631
A Lexicography for the Interpretation of Generalized Multiprotocol Label Switching (GMPLS) Terminology within The Context of the ITU-T's Automatically Switched Optical Network (ASON) Architecture (RFC 4397) (40331 bytes)
A Transport Network View of the Link Management Protocol (LMP) (RFC 4394) (40811 bytes)
Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional Specification (RFC 4426) (55820 bytes)
Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS) (RFC 4427) (43842 bytes)
Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based Recovery Mechanisms (including Protection and Restoration) (RFC 4428) (118749 bytes)
Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement (RFC 4558) (14185 bytes)
Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control (RFC 4606) (53492 bytes) obsoletes RFC 3946
Link Management Protocol (LMP) Management Information Base (MIB) (RFC 4631) (152560 bytes) obsoletes RFC 4327
Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing Requirements (RFC 4652) (47179 bytes)
Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switch Path (LSP) (RFC 4736) (28850 bytes)
A Framework for Inter-Domain Multiprotocol Label Switching Traffic Engineering (RFC 4726) (53076 bytes)
GMPLS - Communication of Alarm Information (RFC 4783) (42068 bytes) updates RFC 3473
Generalized Multiprotocol Label Switching (GMPLS)Label Switching Router (LSR) Management Information Base (RFC 4803) (79925 bytes)
Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base (RFC 4802) (118164 bytes)
Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management (RFC 4801) (16347 bytes)
Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) (RFC 4874) (59569 bytes) updates RFC 3473,RFC 3209
RSVP-TE Extensions in support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery (RFC 4872) (111882 bytes) updates RFC 3471/ updated by RFC 4873
GMPLS Segment Recovery (RFC 4873) (56859 bytes) updates RFC 4872,RFC 3473
Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE (RFC 4920) (88679 bytes)
Routing extensions for discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) mesh membership (RFC 4972) (32044 bytes)
Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in support of Calls (RFC 4974) (72000 bytes) updates RFC 3473
Use of Addresses in Generalized Multi-Protocol Label Switching (GMPLS) Networks (RFC 4990) (50908 bytes)
Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart (RFC 5063) (58542 bytes) updates RFC 2961,RFC 3473
IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities (RFC 5073) (27004 bytes)
Inter domain Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering - RSVP-TE extensions (RFC 5151) (56663 bytes) updates RFC 3209,RFC 3473
Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE) (RFC 5150) (47099 bytes)
A Per-domain path computation method for establishing Inter-domain Traffic Engineering (TE) Label Switched Paths (LSPs) (RFC 5152) (50563 bytes)
Framework for MPLS-TE to GMPLS migration (RFC 5145) (44646 bytes)
Interworking Requirements to Support operation of MPLS-TE over GMPLS Networks (RFC 5146) (31624 bytes)
Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN) (RFC 5212) (70286 bytes)
Analysis of Inter-domain Label Switched Path (LSP) Recovery (RFC 5298) (59894 bytes)
Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks (MLN/MRN) (RFC 5339) (53998 bytes)
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
