1 / 7

OSPF-TE extensions for GMPLS Control of Evolutive G.709 OTN

draft-ceccarelli-ccamp-gmpls-ospf-g709-01 CCAMP WG, IETF 77 th Anaheim. OSPF-TE extensions for GMPLS Control of Evolutive G.709 OTN. Agenda. OTN TE info needed for ODU path computation WSON TE info out of scope

dirk
Télécharger la présentation

OSPF-TE extensions for GMPLS Control of Evolutive G.709 OTN

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ceccarelli-ccamp-gmpls-ospf-g709-01 CCAMP WG, IETF 77th Anaheim OSPF-TE extensions for GMPLS Control of Evolutive G.709 OTN

  2. Agenda OTN TE info needed for ODU path computation WSON TE info out of scope Common interest to assure OSPF-TE routing extensions fully support OTN-G.709(2009) capabilities. Requirements Detail of routing specific requirements from OTN FWK Actual solution Being refined Next Steps

  3. Requirements • Possibility of bundling links either at the same line rate or different line rates (e.g. 40G and 10G link total bandwidth) • Bundling links at the same rate makes the calculation for ODU-flex routes slightly more precise while bundling links at different rates makes the control plane more scalable. • The choice of the method is implementation dependent • Support priority for restoration. • IETF requires supporting resource allocation at up to 8 priority levels. • Support any ODUs and ODU-flex • Differently from other containers (that have a fixed size) it is needed to declare the maximum LSP bandwidth and the maximum number of LSPs that can be supported using this bandwidth. • Concurrent path computation for ODUk and ODUflex 32 TS A B 24 TS 24 TS Example: 3-odu3 – Max Band 32TS – Unres 80

  4. Requirements • Differentiate multiplexed capacity from line rate capacity • Need not to lock connection service rate to infrastructure rate. • Perform accurate route calculation for containers that use a different number of time slot depending from the server rate. • E.g. ODU2e

  5. Solution - 1 • New ISCD • Max LSP Bandwidth and Unreserved bandwidth per priority • Flags for multiplexing capability declaration • 1 ISCD per component links with same line rate and multiplexing capability • Drawbacks • Bundling of component links with same OD(T)Uk and signal flags • Concurrent path computation • Example: 3-odu3 – Max Band 32TS – Unres 80 How many service connections can be supported? 1 or 2?!?! 32 TS A B 24 TS 24 TS

  6. Next steps • Follow latest progresses on G.709 • Progress the joint work aiming at finding a solution respecting all the requirements • New draft after the meeting

  7. QUESTIONS ? THANK YOU

More Related