Liaison statement
Notification of work in the IETF CCAMP working group

State Posted
Posted Date 2006-10-23
From Group ccamp
From Contact Adrian Farrel
To Group ITU-T-SG-15
To Contacts Greg Jones
CcStephen Trowbridge
Kam Lam
Ross Callon
Bill Fenner
Scott Bradner
Deborah Brungard
CCAMP Mailing List
Response Contact Adrian Farrel
Technical Contact Adrian Farrel
Purpose For action
Deadline 2006-11-17 Action Taken
Attachments (None)
The CCAMP Working Group of the IETF is pleased to inform you of its progress
with work that we believe may be of direct interest to your participants.

A new RFC has been published. provides some small updates and
clarifications to the SNMP MIB module for the Link Management Protocol (LMP).
It obsoletes RFC 4327, the previous version of this MIB module. Section 14 of
the new RFC shows a list of the changes.

The CCAMP working group continues to make good progress in many areas. Full
details of the work of CCAMP can be found at from where all of the
latest revisions of the various RFCs and Internet-Drafts can be freely
downloaded without charge.

Four Internet-Drafts that may be of particular interest to your members are
listed below. is
a relatively new work item that examines the requirements and procedures for
using GMPLS protocols to support Virtual Concatenation Groups across TDM
networks. We believe this may be of particular interest to you in support of
Ethernet services over TDM. The Abstract of this draft reads as follows:
   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 the Optical Transport
   Network (OTN), Synchronous Optical Network (SONET), Synchronous
   Digital Hierarchy (SDH), and Plesiochronous Digital Hierarchy (PDH)
describes extensions to the OSPF routing protocol to satisfy the ASON routing
requirements as set out in in the light of
the evaluation provided in
(both of which were written with considerable help from some of your individual
members). The Abstract of this draft reads as follows:
   The Generalized MPLS (GMPLS) suite of protocols has been defined to
   control different switching technologies as well as different
   applications. These include support for requesting TDM connections
   including SONET/SDH and Optical Transport Networks (OTNs).

   This document provides the extensions of the OSPFv2 Link State
   Routing Protocol to meet the routing requirements for an
   Automatically Switched Optical Network (ASON) as defined by ITU-T.
In view of the fact that this work addresses the ASON routing requirements, we
would like to solicit your review and feedback on this draft.
presents a GMPLS Sender_TSpec (and hence a Flowspec) for Ethernet Traffic
Parameters as described in MEF.10. The Abstract of this draft reads as follows:
   This document described the Metro Ethernet Forum (MEF) - specific
   Ethernet Traffic Parameters as described in MEF.10 when using
   Generalized Multi-Protocol Label Switching (GMPLS) Resource
   ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling.
describes extensions to RSVP-TE for the establishment and management of Calls
in GMPLS networks, and for the association of LSPs (connections) with those
Calls. The Abstract if this draft reads as follows:
   In certain networking topologies, it may be advantageous to maintain
   associations between endpoints and key transit points to support an
   instance of a service. Such associations are known as Calls.

   A Call does not provide the actual connectivity for transmitting user
   traffic, but only builds a relationship by which subsequent
   Connections may be made. In Generalized MPLS (GMPLS) such Connections
   are known as Label Switched Paths (LSPs).

   This document specifies how GMPLS RSVP-TE signaling may be used and
   extended to support Calls. These mechanisms provide full and logical
   Call/Connection separation.

   The mechanisms proposed in this document are applicable to any
   environment (including multi-area), and for any type of interface:
   packet, layer-2, time-division multiplexed, lambda or fiber

The CCAMP Working Group welcomes comments on its work at any time. These can be
sent by anyone to the CCAMP mailing list. Details of how to subscribe to the
list together with information on all of the work currently being pursued by
the working group can be found at the charter page:

Adrian Farrel and Deborah Brungard
CCAMP Working Group Co-Chairs