70 likes | 94 Views
This document outlines the plan for the CCAMP Working Group at the 63rd IETF Paris meeting. It includes options for progress, new work areas, and discussion topics.
E N D
CCAMP Working GroupWork Plan 63rd IETF Paris August 2005
Major Options for Progress • Leave existing charter text as is • Add new milestones to drive specific work • Update and enhance charter text • Focused and detailed descriptions of work areas • Add new milestones to drive specific work • Wind-up WG • Timing? • Complete current drafts first or allow overlap? • What to do with “out of scope” work? • Take it to another WG • Hold a BOF 63rd IETF Paris August 2005
Potential New Work • Discussion on mailing list in November • On charter but needing more focus and specific tasks • Inter-domain (complete current work; extend to diverse paths?) • Layer 2 switching • Multi-layer / multi-region networking • Proposed new work items • Important • MPLS-GMPLS migration • GMPLS interoperability issues (including addressing) • L1VPNs New working group • PCE requirements (input to PCE WG) • Marginal • Control plane work (resiliency etc.) • Deployment considerations • Less important • Waveband switching • QoS control 63rd IETF Paris August 2005
Recent New Topics • Signaling Issues • Control and use of VCAT/LCAS • Control plane saturation • Change of ownership from Mgmt to Ctrl Plane • Routing issues • TE/GMPLS MIB modules for IGPs • Advertisement of TE/GMPLS capabilities • Interpretation of CSPF constraints • Complex optical constraints • GMPLS OAM Requirements 63rd IETF Paris August 2005
What Else? 63rd IETF Paris August 2005
Discussion • Which option do we take? • Increase the scope or focus the work? • Milestones mean commitment • To work on these drafts ahead of others • To implement and deploy 63rd IETF Paris August 2005
Notes from the Meeting • Plan one to two years’ work • Flag items that might be spun-off to new/other WGs • PCE WG needs to decide whether it needs CCAMP input on GMPLS PCE requirements • Put some priority on “core” issues • What else needs to be done wrt ASON? • What steps to align GMPLS and ASON solutions? 63rd IETF Paris August 2005