1 / 6

draft-rahman-ccamp-rsvp-restart-extensions-00

draft-rahman-ccamp-rsvp-restart-extensions-00. Reshad Rahman rrahman@cisco.com Anca Zamfir ancaz@cisco.com Junaid Israr jisrar@cisco.com. Summary. Extensions to RSVP-TE GR as specified in RFC3473. Addresses recovery of ERO after restart: At ingress nodes. At transit nodes.

agrata
Télécharger la présentation

draft-rahman-ccamp-rsvp-restart-extensions-00

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-rahman-ccamp-rsvp-restart-extensions-00 Reshad Rahman rrahman@cisco.com Anca Zamfir ancaz@cisco.com Junaid Israr jisrar@cisco.com 59th IETF Seoul March 2004

  2. Summary • Extensions to RSVP-TE GR as specified in RFC3473. • Addresses recovery of ERO after restart: • At ingress nodes. • At transit nodes. • Proposes a mechanism to detect multiple restarts. • Presented at MPLS WG at IETF 58. 59th IETF Seoul March 2004

  3. Feedback • There have been some discussions on the mailing list to see if we can use RRO instead of defining a new object. 59th IETF Seoul March 2004

  4. Next Actions • draft-aruns-ccamp-rsvp-restart-ext-00.txt proposes a mechanism to recover full signaling state. • The drafts will be merged. 59th IETF Seoul March 2004

  5. ERO Recovery R5 R1 R6 R3 R2 [R2, R6(loose)] [R6] [R3, R4, R5, R6] • After R2 restarts, it receives the Path message with ERO [R2, R6(loose)] from R1 and R2 sends a Path message to R3 with Recovery ERO [R3, R6]. • R3 finds the associated Path state and replies with a Resv message containing Recovery ERO [R3, R4, R5, R6]. • R2 uses the Resv’s Recovery ERO to update its Path ERO. Subsequent Path messages from R2 are sent with ERO [R3, R4, R5, R6]. [R2, R6(loose)] Rec ERO [R3, R6] Rec ERO [R3, R4, R5, R6] [R5, R6] [R4, R5, R6] R4 59th IETF Seoul March 2004

  6. Detecting Multiple Restarts • Each node sends a non-zero Recovery Time while in recovery mode and must set it to zero once its recovery is complete. This allows a restarting node to detect that its downstream neighbor also restarted: it sends a Recovery Label instead of a Suggested Label. 59th IETF Seoul March 2004

More Related