CCAMP Working Group Charter Update

1. CCAMP Working GroupCharter Update Chairs: Lou Berger <lberger@labn.net> Deborah Brungard <db3546@att.com> 76th IETF Hiroshima, November 2009

2. Charter Update Needed • Current scope and work description need minor updates • Milestones are out of sync with current work • 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 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 • Chairs have a baseline proposed update • Need input from AD, WG • Objective is to discuss today and on list • Goal is a final update by the end of the year 76th IETF Hiroshima, November 2009

3. Proposed changes – Scope • No major changes • Minor wording changes to clarify scope • Group focuses on GMPLS protocols • We’re data plane agnostic (which is defined outside of CCAMP/IETF) 76th IETF Hiroshima, November 2009

4. Proposed changes – Scope (cont.) • Proposed language: • red = delete, underlined = add • 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 protocols for link and path attribute measurement. This includes the Link Management Protocol (LMP) is included here. • Functional specification of extensions for GMPLS-related routing (OSPF, ISIS) and signalling (RSVP-TE) protocols 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 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 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. 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. 76th IETF Hiroshima, November 2009

5. Proposed changes – Work • Update to reflect current major work items • WSON, OTN, MPLS-TP (planned) • Allow for extensions/continuation of prior work • Such as base protocols and ASON • Driven by data plane behavior 76th IETF Hiroshima, November 2009

6. Proposed changes – Work (cont.) • Proposed language: • red= delete, underlined = add • 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 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. 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 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 requirements for supporting extensions to data plane technologies (e.g. WSON, OTN, MPLS-TP and Ethernet) and network architectures (e.g., ITU-T’s Automatically Switched Optical Network (ASON) are) 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, L1VPN and PCE. The WG will also cooperate with the ITU-T and the IEEE 802.1. 76th IETF Hiroshima, November 2009

7. Goals and Milestones • Updated to reflect • Current WG documents • Ethernet, MLN/MRN, MIB, hierarchy (Near completion) • WSON, OAM • WG document candidates • WSON related • OTN extensions related • Base protocol related (e.g., LMP) • MPLS-TP • Framework and other anticipated documents 76th IETF Hiroshima, November 2009

8. Goals and Milestones (cont.) • Proposed items: • Dec 2009 Submit Protocol solutions for MLN/MRN I-D for IESG review • Dec 2009 Submit TE MIB module IESG review • Dec 2009 Submit Ethernet related drafts for IESG review • Dec 2009 Submit hierarchy bis for IESG review • Jan 2010 First version of WSON routing related Working Group drafts • Jan 2010 First versions of impairments related solutions Working Group drafts • Jan 2010 First version of G.709 enhancements framework Working Group drafts • Feb 2010 Submit VCAT/LCAS with GMPLS for IESG review • Apr 2010 Submit Lambda labels draft for IESG review • Apr 2010 Submit WSON framework draft for IESG review • Apr 2010 Submit WSON impairment framework draft for IESG review • Apr 2010 Submit OAM configuration framework for IESG review • Apr 2010 First version of Working Group draft providing Control Plane Framework for MPLS-TP • Apr 2010 First version of LMP Negotiation Working Group draft • May 2010 First version of G.709 enhancements solutions Working Group drafts • May 2010 First version of OAM configuration solutions Working Group drafts • May 2010 First version of LMP for G.709 enhancements Working Group drafts • Sep 2010 First version of Working Group draft defining RSVP-TE extensions for MPLS-TP • Dec 2010 Submit WSON routing related for IESG review • Dec 2010 Submit impairments related solutions for IESG review • Dec 2010 Submit G.709 enhancements framework for IESG review • Dec 2010 Submit Control Plane Framework for MPLS-TP for IESG review • Mar 2011 Submit RSVP-TE extensions for MPLS-TP for IESG review • Apr 2011 Submit G.709 enhancements solutions for IESG review • Apr 2011 Submit LMP Negotiation for IESG review • Apr 2011 Submit OAM configuration solutions for IESG review • Aug 2011 Submit LMP for G.709 enhancements for IESG review • Nov 2011 Recharter or close Working Group 76th IETF Hiroshima, November 2009