1 / 7

Pseudo-Wire Protection

Pseudo-Wire Protection. Mustapha Aissaoui, Florin Balus, Matthew Bocci, Hamid Ould-Brahim, Ping Pan IETF 66, Montreal. What we have learned since last IETF. PW protection may mean different things to different people: End-to-end path protection Congestion relief Multi-homed AC protection

kennethf
Download Presentation

Pseudo-Wire Protection

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. Pseudo-Wire Protection Mustapha Aissaoui,Florin Balus, Matthew Bocci, Hamid Ould-Brahim, Ping Pan IETF 66, Montreal

  2. What we have learned since last IETF • PW protection may mean different things to different people: • End-to-end path protection • Congestion relief • Multi-homed AC protection • Single-segment protection • Multi-segment protection • … • So, not only do we need protocol extension specification(s), we may need a framework/user document as well.

  3. Key Changes from the previous version • Defined a Preference TLV and a Protection TLV • Preference TLV: provide the capability for PW’s to preempt each other in case of congestion • Protection TLV: provide the protection information for Path Protection • Removed 1:N protection option • This does not make sense after further discussion • Added more text on messaging processing

  4. PW Path Protection • Protection TLV contains: • Reference ID: working and protection PW’s must be uniquely identified • Protection information: CAC-desired, fate-sharing working protection Reference ID is needed to know what to process on S-PE’s

  5. PW Congestion Control • Preference TLV contains: • Preference level of the PW’s • Use setup and holding preference to control the preemption Preempt less important PW’s PW: high preference Send status back PW: low preference

  6. Other protection cases… to be worked out in details Multi-homed PW Protection Individual PW’s PW Segment Protection Backup PW

  7. Next Step • The current proposal supports • PW preemption • PW Path Protection • Like to • Iron out other issues • Work with the framework/user-case draft people • Gather more feedback from carriers • Make this into a WG Working Document THANK YOU ALL

More Related