60 likes | 71 Views
Updates and progress in 100G interface, multi-domain restoration, ASON routing, OTN enhancements, and control plane requirements discussed in ITU-T, OIF, and IETF reports.
E N D
ITU-T/OIF Report IETF 77 – Anaheim – Mar’10 L. Ong (Ciena) lyong@ciena.com Thanks to Malcolm Betts & Kam Lam for ITU-T input
OIF Status • OIF met February 2010 • Continued work on 100G interface specifications • Active networking projects: • Routing, • Multilayer architecture • End-to-end multi-domain restoration • Interest in PCE applications and new OTN extensions • 2 Liaisons to IETF CCAMP
OIF Liaisons • Revised proposal on ASON routing • Request to update RFC 5787 work with minor format changes based on testing experience • We believe this should help move ASON routing to standards track due to the presence of running code • draft-ong-gmpls-ason-routing-exper-01.txt (review Tuesday) • New draft on LSP hierarchy for ASON networks • Provides problem statement for potential GMPLS change • Need to identify client layer in flexible adaptation • Need to configure adjacency with client layer controller(s) • Need to support separation of controller ID and control plane address • draft-roch-ccamp-reqts-auto-adj-00.txt (also Tuesday)
ITU-T SG15 • Joint Q.12&14/15 Meeting – 3/10 Darmstadt • Q.14/15 • G.7713 • New revision approved • Incorporates multilayer modeling • G.7714 • Ring protection discovery – still under discussion • G.7715 • Ring topology dissemination – modeling being discussed in Q.12/15 • Using the G.800 and G.8080 multi-layer topologies for multi-layer path computation – study started • No liaisons to CCAMP
Q.12/15 Activities • G.8080 Amd 2 (ASON architecture) • Adding the concept of transitional links (client-server/server-client) • Believed to be compatible with IETF WSON work • Discussing dissemination of ring maps via routing • Representation of ring as subnetwork or RA, including constraints and termination on a single node • G.872 Amd 2 (OTN architecture) • Adding OTN enhancements and updating OTN modeling • Related Liaison to CCAMP
Q.12/15 Liaison to CCAMP • Q.12/15 is updating G.872 (OTN Architecture) as described in report to IETF 76 • Architecture change • ODU is a single layer network • Client bit rate is a parameter • Includes a number of new requirements on control plane • Support for new ODU rates ODU0, ODU4 and ODUFlex • Support for new server layer (OTU4) • Need to advertise maximum payload bandwidth on link as well as available BW • e.g., largest ODUFlex rate that can be supported this may be less than total available BW due to fragmentation across component links • Independence between service rate and link rate used for transport • Need to indicate payload bit rate for the call so that number of TS required and location of stuff opportunities can be computed per link