1 / 6

Zafar Ali ( zali@cisco ) Antonello Bonfanti ( abonfant@cisco )

RSVP-TE Recovery Extension Extension for Additional Signal Types in G.709 OTN draft-ali-ccamp-additional-signal-type-g709v3- 03. txt. Zafar Ali ( zali@cisco.com ) Antonello Bonfanti ( abonfant@cisco.com ) Fatai Zhang ( zhangfatai@ huawei.com ).

nico
Download Presentation

Zafar Ali ( zali@cisco ) Antonello Bonfanti ( abonfant@cisco )

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. RSVP-TE Recovery Extension Extension for Additional Signal Types in G.709 OTN draft-ali-ccamp-additional-signal-type-g709v3-03.txt Zafar Ali (zali@cisco.com) AntonelloBonfanti (abonfant@cisco.com) Fatai Zhang (zhangfatai@huawei.com) 90th IETF, CCAMP WG, Toronto, Canada (July 2014)

  2. Outline • Requirements • Solution • Next Steps

  3. Requirements • G.Sup43 defines the following additional signaling types: • ODU1e • ODU3e1 • ODU3e2 • G.Sup43 is a de facto standard with ITU-T status as "in force” [http://www.itu.int/rec/T-REC-G.Sup43/en]. • Current GMPLS specifications for G709 v3 does not cover these signaling types. • Current GMPLS OTN specifications does not support any values for vendor specific signaling type or for “Private Use”, either (e.g., for ODU1fand ODU2f).

  4. Summary of Changes (in -02) • Addressed all comments received from the WG (public or private) • Position the draft as “experimental”. • Wrote a companion draft to propose changes to “OTN Signal Type” Subregistry(draft-ali-ccamp-changing-otn-signal-type-iana-subregistry-00)

  5. Solution • Just need code points for signal types defined in G.Sup43 and vendor specific signal types.

  6. Next steps • We would like to hear WG feedback on this draft. • We would like to make this a WG document.

More Related