OSPF-TE extensions for GMPLS Control of Evolving G.709 OTN draft-ceccarelli-ccamp-gmpls-ospf-g709-02/03 CCAMP WG, IETF 78 th Maastricht

Agenda Quick overview of version -02 Agreed requirements Overview of version -03

Encoding format - SubTLV Priority flags Bit set = priority supported Non supported priorities are not advertised. Tributary slot 1,25 or 2,5 Gbps Data Row Signal Type ODUk sublambda ODUk full lambda ODUflex, ODUflex resizable F bit (for ODUflex) F=1 Unres Bandwidth F=0 Max LSP Bandwidth Pi Unreserved bandwidth or Max LSP bandwidth expressed in number of TSs

Example – t0 Supported priorities 0,3,7 Tributary slot 1,25 Gbps Link component #1 Full lambda: ODU2 Sub lambda: ODU0, 1, Flex Link component #2 Full lambda: ODU3 Sub lambda: ODU1, Flex AB LC #1 – 8 TS LC #2 – 32 TS

Example – LSP setup LSP1 – 35Gbps corresponding to 28 TS on LC#2 AB LC #1 – 8 TS LC #2 – 32 TS

Example – LSP preemption LSP1 – 35Gbps corresponding to 28 TS on LC#2 LSP2 – 15 Gbps corresponding to 12 TS on LC#2 AB LC #1 – 8 TS LC #2 – 32 TS

Requirements – From OTN Framework Multiple signal types Multiple priorities Scalability Compact representation ODUFlex No precluding VCAT Number of LSPs per signal type Resource switched vs terminated, both Consistent with CCAMP charter and work Reuse existing mechanisms wherever possible Extensions permitted, but need to be Generic wherever possible

New Solution (-03) New sub-TLV Signal types are scoped within Switching capability Compress Signal Type and priority

Example (-03) Signal types ODU2 (1) ODU 3 (2) Supported priorities 1,2,5 M = 0 T = 1 (terminating capability) S = 1 (switching capability) AB

Compressing signal type and priority Advertising once the bandwidth common to different: Signal Types Priorities ODU2 ODU3 ODU2e

Next steps Collect feedbacks from the meeting Publish version -03 with new solution Collect feedback on the ML Keep alignment with OTN Framework and G.709 Info Model.

QUESTIONS ? THANK YOU