1 / 5

Full Reroute Reversion Combined Recovery

Full Reroute Reversion Combined Recovery. Draft-roch-ccamp-full-reroute-reversion-01.txt Draft-roch-ccamp-combined-recovery-reqts-01.txt Co-authors: E. Roch, L. Ong, A. Malis March 26, 2012. Reversion. Reversion – return to original path

lamond
Download Presentation

Full Reroute Reversion Combined Recovery

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. Full Reroute ReversionCombined Recovery Draft-roch-ccamp-full-reroute-reversion-01.txt Draft-roch-ccamp-combined-recovery-reqts-01.txt Co-authors: E. Roch, L. Ong, A. Malis March 26, 2012

  2. Reversion • Reversion – return to original path • 4873 provides explicit text on how this is supported for 1+1 and 1:n protection and rerouting with extra traffic • These generally involve preplanning or prereservation of a disjoint backup path • Carriers are interested in reversion with full reroute as well, where • No preplanning or prereservation is done • The backup path may share resources with the original path

  3. Proposal • Review requirements for supporting this service • Subset of existing recovery services • See if any extensions are needed • Hopefully not, ideally supported with existing specs • Document in BCP if no extensions needed

  4. Combined Recovery • Preservation of high availability at all times is highly valued functionality • Combinations of restoration and protection may be involved in • Preserving 1+1 protection under planned events such as maintenance • Temporary reroute (with reversion) of affected path • Supporting higher availability beyond 1+1 • Restoration of one or both paths in case of failure

  5. Proposed Actions • Review requirements • combinations of existing recovery capabilities • Evaluate if any additional extensions are necessary • Document as needed

More Related