1 / 10

Authors: Zafar Ali ( zali@cisco ) George Swallow (swallow@cisco )

Extensions to RSVP- TE for Error Notification in GMPLS UNI draft-ali-ccamp-gmpls-uni-error-notification-00.txt. Authors: Zafar Ali ( zali@cisco.com ) George Swallow (swallow@cisco.com ) Clarence Filsfils ( cfilsfil@cisco.com ) Matt Hartley ( mhartley@cisco.com ) - Presenter

haley-bradshaw
Download Presentation

Authors: Zafar Ali ( zali@cisco ) George Swallow (swallow@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. Extensions to RSVP-TEfor Error Notification in GMPLS UNIdraft-ali-ccamp-gmpls-uni-error-notification-00.txt Authors: Zafar Ali (zali@cisco.com) George Swallow (swallow@cisco.com) Clarence Filsfils (cfilsfil@cisco.com) Matt Hartley (mhartley@cisco.com) - Presenter Kenji Kumaki (ke-kumaki@kddi.com) 87th IETF, CCAMP WG, Berlin, Germany (July-August 2013)

  2. Outline • Problem Statement • Solution • Next Steps

  3. Reference Network EN: Edge Node CN: Core Node Core Network Egress Ingress CN2 CN1 CN3 EN1 EN2 CN5 CN4 EN4 EN3 Link failure GMPLS-UNI LSP

  4. Problems • Error notification: Edge nodes have no visibility into core topology • Failed link address is unknown to them • Core’s policy may be to hide addresses and topology • Recovery of GMPLS-UNI LSP after failure • Repair within optical network • Re-setup from ingress node • How do we coordinate the two? • These issues apply to GMPLS-UNI, and therefore fall within CCAMP’s charter.

  5. Solutions • Allow a node to change the address in a Path-Err message • New flag to indicate that this has been done • New PathErr to allow core to inform edge that LSP repair has occurred

  6. Error signaling Egress Ingress CN2 CN1 CN3 EN1 EN2 Perr: address: <CN2> Perr: address: <CN1> “Address-changed” flag set Internal core topology hidden from EN

  7. Repair mechanisms Core network repair Orginal LSP Re-signaled Egress Ingress CN2 CN1 CN3 EN1 EN2 CN5 CN4 EN4 EN3 Either mechanism may be preferable; both together may not be.

  8. Repair mechanisms Path-error allows notification of repair by core network Original LSP Core network repair Egress Ingress CN2 CN1 CN3 EN1 EN2 Path-Err: notify / LSP restored CN5 CN4 EN4 EN3 Original LSP signaled with protection requested: Protection Object, LSP flags 0x01 (full rerouting)

  9. Next Steps • This is the first presentation of this draft • We would like to move the draft towards WG adoption

  10. Thank You.

More Related