IETF-88 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Common Control and Measurement Plane (ccamp) (WG)

Minutes   |   Audio Archives  |   Jabber Logs  |   Mailing List Archives

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

Chair(s):

Secretary

Routing Area Area Director(s):

Routing Area Advisor



Meeting Slides:

Blue Sheets:

Internet-Drafts:

Request for Comments:

Charter (as of 2001-01-31):


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 and extensions to protocols for link and path attribute
measurement. This includes the Link Management Protocol (LMP).

- Functional specification of extensions for GMPLS-related routing
(OSPF, ISIS) and signaling (RSVP-TE) protocols required for path
establishment and maintenance. 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
control of 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 data paths for data
planes that are already approved by a Standards Development
Organization (SDO). Note that the specification or modification of
data planes is out of scope of this working group. Example data planes
include Wavelength Switched Optical Networks (WSON), Optical Transport
Networks (OTN), Ethernet, and the MPLS data plane.

- 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 (or by other means e.g. configured) can be
distributed in existing routing protocols, such as OSPF and
IS-IS. CCAMP will work with the WGs that supervise these
protocols. The specifics of distribution within IS-IS are being
addressed in the ISIS WG. Current work activities are focused in the
areas of WSON and OTN.

- 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 signaling mechanisms for path protection, diverse
routing and fast path restoration. Ensure that multi-layer path
protection and restoration functions are achievable using the defined
signaling, routing, and measurement protocols, either separately or in
combination.

- Identify signaling and routing requirements for supporting protocol
extensions in support of data plane technologies (e.g., WSON, OTN,
MPLS-TP, and Ethernet) and network architectures (e.g. ITU-T's
Automatically Switched Optical Network (ASON)) not currently met by
protocols defined in CCAMP; based on these, define mechanisms to
address these requirements. This activity will build on documents
produced by the WG, including Informational, Standards Track and
Experimental documents.

- 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, and PCE. The WG will also
cooperate with the ITU-T and the IEEE 802.1.


Internet SocietyAMSHome - Tools Team - Datatracker - Web Site Usage Statistics - IASA - IAB - RFC Editor - IANA - IRTF - IETF Trust - ISOC - Store - Contact Us
Secretariat services provided by Association Management Solutions, LLC (AMS).
Please send problem reports to: ietf-action@ietf.org.