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: 2007-11-14

Additional information is available at tools.ietf.org/wg/ccamp

Chair(s):

Adrian Farrel <adrian@olddog.co.uk>

Deborah Brungard <dbrungard@att.com>

Routing Area Director(s):

Ross Callon <rcallon@juniper.net>

David Ward <dward@cisco.com>

Routing Area Advisor:

Ross Callon <rcallon@juniper.net>

Technical Advisor(s):

Alex Zinin <zinin@psg.com>

Mailing Lists:

General Discussion: ccamp@ops.ietf.org
To Subscribe: majordomo@ops.ietf.org
In Body: subscribe ccamp
Archive: https://ops.ietf.org/lists/ccamp

Description of Working Group:

Organizational Overview

The 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 MIB modules and other 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 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.

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 ASON are
not currently met by protocols defined in CCAMP; based on these,
define mechanisms to address these requirements.

- Document issues and strategies for the migration of MPLS-based
deployments to GMPLS. Based on the outcome, identify protocol
machinery that implementations may have to change to ease the
migration from MPLS to GMPLS.

In doing this work, the WG will work closely with at least the
following other WGs: MPLS, 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
Apr 2006		First version of WG I-D for additional MIB module to cover RSVP-TE signaling extensions
Done		Submit GMPLS routing and signaling interoperability advice I-D for IESG review
Jun 2006		Submit Informational I-D for Analysis of inter-domain issues for disjoint and protected paths for IESG review
Done		Submit MPLS to GMPLS migration strategies I-D for IESG review
Nov 2006		Submit ASON Routing solutions 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
Mar 2007		Submit OSPF-TE/GMPLS MIB module for MIB doctor and IESG review
Jun 2007		Submit GMPLS OAM Requirements I-D for IESG review
Aug 2007		Submit Protocol solutions for MLN/MRN I-D for IESG review
Dec 2007		Submit MIB module for RSVP-TE signaling extensions for MIB doctor and IESG review
Dec 2007		Recharter or close Working Group

Internet-Drafts:

Inter domain Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering - RSVP-TE extensions (55171 bytes)
Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE) (47682 bytes)
A Per-domain path computation method for establishing Inter-domain Traffic Engineering (TE) Label Switched Paths (LSPs) (51416 bytes)
IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities (26263 bytes)
Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN) (61928 bytes)
Evaluation of existing GMPLS Protocols against Multi Layer and Multi Region Networks (MLN/MRN) (36366 bytes)
Framework for MPLS-TE to GMPLS migration (44736 bytes)
MEF Ethernet Traffic Parameters (23256 bytes)
Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks (26060 bytes)
Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS) (35730 bytes)
Traffic Engineering Database Management Information Base in support of GMPLS (49569 bytes)
Requirements for the Conversion Between Permanent Connections and Switched Connections in a Generalized Multiprotocol Label Switching (GMPLS) Network (25420 bytes)
Interworking Requirements to Support operation of MPLS-TE over GMPLS Networks (31979 bytes)
Analysis of Inter-domain Label Switched Path (LSP) Recovery (57455 bytes)
OSPF Traffic Engineering (OSPF-TE) Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (28776 bytes)
Description of the RSVP-TE Graceful Restart Procedures (37157 bytes)
OAM Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Networks (26686 bytes)
Generalized Multi-Protocol Label Switching (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN) (40725 bytes)

Request For Comments:

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to working group directory.

Return to IETF home page.