Charter for Working Group

The CCAMP working group is responsible for standardizing a commoncontrol plane and a separate common measurement plane for non-packettechnologies found in the Internet and in the networks of telecomservice providers (ISPs and SPs). Examples of the devices in suchnetworks include photonic cross-connects, OEO switches, ROADMs, TDMswitches, microwave links, and Ethernet switches.

In this context, measurement refers to the acquisition and distribution of attributes relevant to the setting up of tunnelsand paths.

The working group develops extensions to core Traffic Engineering protocols that are under the care of other working groups. The CCAMPworking group will coordinate with the TEAS working group to ensurethat extensions that can be generalized for use with more than onetechnology are made appropriately, and with the working groups thathave responsibility for the specific protocols.

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 in technology-specific networks. These will be developed in conjunction with requests and requirements from other WGs to ensure overall usefulness.

- Maintenance and extension of 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 in non-packet, technology-specific networks. Protocol formats and procedures that embody these extensions will be done jointly with the WGs supervising those protocols and the TEAS working group has the responsibility to determine whether such protocol extensions should be generalized for Traffic Engineering in any network.

This may include protocol work to support data planes that have already been approved by another Standards Development Organization. Note that the specification or modification of data planes is out of scope of this working group

- Definition of management objects (e.g., as part of MIB modules or YANG models) and control of OAM techniques relevant to the protocols and extensions specified within the WG. The OAM work will be synchronized with the LIME WG

- Describe non-packet-specific aspects of traffic engineering including for multi-areas/multi-AS/multi-layer scenarios and define protocol extensions in cooperation with the TEAS and PCE working groups.

- Define how the properties of network resources gathered by a measurement protocol (or by other means such as configuration) can be distributed in existing routing protocols, such as OSPF, IS-IS, and BGP-LS. CCAMP will work with the WGs that supervise these