ccamp working group charter and liaisons n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
CCAMP Working Group Charter and Liaisons PowerPoint Presentation
Download Presentation
CCAMP Working Group Charter and Liaisons

Loading in 2 Seconds...

play fullscreen
1 / 11
cairo-goodwin

CCAMP Working Group Charter and Liaisons - PowerPoint PPT Presentation

124 Views
Download Presentation
CCAMP Working Group Charter and Liaisons
An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. CCAMP Working GroupCharter and Liaisons 69th IETF Chicago, July 2007

  2. Things to Cover • Charter Update Discussion (cont.) • Liaisons and Communications • IEEE Related • ITU-T SG15 Related • MFA Related • OIF Related • All incoming and outgoing communications are recorded and tracked at:http://www.olddog.co.uk/ccamp.htm 69th IETF Chicago, July 2007

  3. Adding GELS to the Charter • Just housekeeping • First sentence 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, MPLS, and GRE, in cooperationwith the MPLS WG. • Final paragraph In doing this work, the WG will work closely with at least the following other WGs: MPLS, ISIS, OSPF, IDR, L1VPN and PCE. The WG will also cooperate with the ITU-T, and the IEEE 802.1. 69th IETF Chicago, July 2007

  4. New/Revised Goals and Milestones Aug 2007 First version WG I-D for Protocol solutions for MLN/MRN Aug 2007 First version WG I-D GMPLS OAM Requirements Sep 2007 Submit Informational I-D for Analysis of inter-domain issues for disjoint and protected paths for IESG review Sep 2007 Submit MPLS to GMPLS migration strategies I-D for IESG review Sep 2007 Submit MPLS-GMPLS interworking requirements and solutions I-D for IESG review Sep 2007 First version WG I-Ds for control of Ethernet networks Oct 2007 Submit Requirements for Multi-Layer and Multi-Region Networks I-D for IESG review Oct 2007 Submit Evaluation of existing protocols for MLN/MRN for IESG review Oct 2007 First version of WG I-D for additional MIB module to cover RSVP-TE signaling extensions Dec 2007 Submit OSPF-TE/GMPLS MIB module for MIB doctor and IESG review Jan 2008 Submit ASON Routing solutions I-D for IESG review 69th IETF Chicago, July 2007

  5. New/Revised Milestones (cont.) Feb 2008 Submit GMPLS OAM Requirements I-D for IESG review Mar 2008 Submit Protocol solutions for MLN/MRN I-D for IESG review Apr 2008 Submit MIB module for RSVP-TE signaling extensions for MIB doctor and IESG review May 2008 Submit protocol extensions for control of Ethernet networks for IESG review Dec 2008 Recharter or close Working Group 69th IETF Chicago, July 2007

  6. Charter Update • Anything else for consideration? 69th IETF Chicago, July 2007

  7. IEEE Liaisons • End of 2006 • Back and forth on VLAN Tag switching • June 2007 • Notification of our intent to work on a control plane for 802.1Qay (PBB-TE) • Request confirmation that this is reasonable • IEEE met last week and responds… • Although IEEE 802.1 holds no opinion on GMPLS control plane work, the IEEE 802.1 working group does not object to work that is compatible with IEEE 802.1 data planes. • Note that IEEE 802.1 reserves the right to develop its own control planes for PBB-TE. For your information, the only projects currently underway that are related to control planes is P802.1aq for Shortest Path Bridging and P802.1Qat for bandwidth reservation. • Response not posted yet 69th IETF Chicago, July 2007

  8. ITU-T Study Group 15 • Relatively high level of communication • Not always smooth and easy • Need to generate some liaisons: • RFC 4258 and RFC 4652 for reconsideration and technical input • Notification of new RFCs • Several liaisons for us to respond to: • VCAT/LCAS received end April 2007 • Asked for response by end May • Greg did a draft response • Chairs need to tidy it up and send it • Attach latest I-D • MLN received end May 2007 • Asked for response by start of September • Questions and comments to be addressed as part of last call • Response should say how we have addressed each point • Looking to document editors to draft the response 69th IETF Chicago, July 2007

  9. ITU-T Study Group 15 - continued • Several liaisons for us to respond to: • Comments on ASON OSPF received Feb 2007 • We have already responded • Should do a new response to show how we have updated the I-D • Loop Detection in ASON OSPF received June 2007 • Some minor clarifications to be addressed • Dimitri and chairs to draft a response • Call Signaling received June 2007 • Comments requested by January 2008 • Clarification of how calls are used for ASON • Call ID formats • Call end-point identifiers • Dimitri and Adrian to draft a response • OTN Work plan received June 2007 • Comments requested by December 2007 69th IETF Chicago, July 2007

  10. MFA • Liaised a draft Customer to Network interface (CNI) to us in November 2006 • Requested response by Feb 2007 • Detailed response sent Nov 2006 • No further communication received • Understand that CNI work is progressing • Not top priority for MFA • Anyone from MFA want to comment? 69th IETF Chicago, July 2007

  11. OIF • VLAN IDs and MEF services received Oct 2006 and Feb 2007 • Requested response (no deadline given) • We now have some I-Ds in this area • Suggest we send them for comment • VCAT • We learnt on Tuesday that OIF is working with VCAT and doing “something different” • The industry needs convergence of solutions (not divergence) • We also heard that hierarchy-bis is being used • What should we liaise? 69th IETF Chicago, July 2007