Current CCAMP Activities and Future Directions in Optical Networks and Signaling
90 likes | 217 Vues
The latest updates from CCAMP cover various ongoing activities, including the successful winding down of current projects related to Protection & Restoration, ASON signaling, and routing. Key discussions include the migration from MPLS to GMPLS, the resilience of the GMPLS control plane, and addressing challenges in inter-domain signaling. Additionally, proposals for the specification of protocols for Layer 1 VPNs and interop experiences highlight future directions. Please provide input on additional work items by Nov. 19, with consensus checks by Dec. 3.
Current CCAMP Activities and Future Directions in Optical Networks and Signaling
E N D
Presentation Transcript
Rechartering CCAMP ‘61
Current CCAMP Activities • Most winding down nicely • Protection & Restoration • ASON signaling and routing • Others well under way • Inter-domain signaling and routing • Oh, yes, MIBs • Log-jam of documents broken up • Thanks, Adrian!
Work That’s Been Discussed • MPLS-GMPLS migration • Optical (Layer 1) VPNs • GMPLS control plane resilience • Addressing • Implementation/interop experience • GTTP?
MPLS-GMPLS Migration • GMPLS is a superset of MPLS • However, some objects are different • Label request, labels, upstream labels, … • BCP describing how implementations can migrate smoothly from one set of objects to the shiny new set • BCP describing how operators can migrate, issues they might face, …?
Optical (Layer 1) VPNs • Question: should the IETF take on the work of specifying protocols for L1VPNs? • If so, should this be a new WG, or just added to the CCAMP charter? • Signaling is a major component of L1VPNs • Intimately tied to UNI signaling and inter-domain signaling/routing • Liaisons to SG13 already under way
GMPLS Control Plane Resilience • Many feel this has not been adequately addressed • Control plane resilience is crucial to transport networks • Graceful restart is a first step, but other aspects need to be considered
Addressing • IP uses IP addresses everywhere :-) • Transport networks are used to having different types of addresses at different points in the network • A decoder ring that maps transport network address types to different uses of IP addresses in signaling, routing etc. would be useful
Implementation/Interop • Many interop events have taken place, and there is good feedback from them • Some in the form of BCPs • Addressing, use of router ID, … • Some tweaks to protocol specs • Seems important to do this to have good standards
Next Steps • Send out a request for additional work items • Replies due by Friday Nov 19 • Send out consensus checks for each item • Replies due by Friday Dec 3 • Trim list (if necessary), and send to ADs • Add appropriate milestones