1 / 4

VPWS Interworking OAM Procedures: Efficient Management Across Multiple Network Technologies

This draft specifies OAM interworking procedures for VPWS, including IP L2 interworking, FR-ATM interworking, and Ethernet interworking. Addressed issues include defect loop operation and behavior in various scenarios. The document proposes inband fault notification using BFD for enhanced fault management.

bermudezs
Télécharger la présentation

VPWS Interworking OAM Procedures: Efficient Management Across Multiple Network Technologies

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. OAM Procedures for VPWS Interworkingdraft-aissaoui-l2vpn-vpws-iw-oam-02Mustapha Aïssaoui, Matthew Bocci, David Watkinson, AlcatelHamid Ould-Brahim, Mike Loomis, David Allan, NortelThomas D. Nadeau, Monique Morrow, Cisco SystemsJohn Z. Yu, Hammerhead SystemsHimanshu Shah, CienaPaul Doolan, Mangrove SystemsPeter Busschbach, Lucent Technologies

  2. Scope • This draft specifies the procedures for OAM interworking for the following VPWS: • IP L2 interworking (ARP-mediation) • FR-ATM interworking (FRF8.2) • Ethernet interworking • It complements draft-ietf-pwe3-oam-msg-map-01.txt, which covers the homogeneous VPWS

  3. Changes from Revision 01 • Addressed three issues raised by coauthors • Issue 1: Defect loop operation • Single emulated end-to-end loop versus multiple coupled loops • settled on a modified "coupled loop" model which we believe works in all scenarios addressed in the draft • Issue 2: • Should the receipt of a defect in the reverse direction of a remote AC or a PW result in a different action at a PE? • we analyzed the defects for all scenarios in the draft and we have now updated the text to treat this as a separate defect • Issue 3: • Check the behavior in the case of L2TPv3 PSN • Updated PW defect handling procedures using StopCCN and CDN messages after discussion with Mark Townsley in San-Diego

  4. Next Steps • Add support for inband fault notification based on BFD • Authors would like to make this document a Working Group draft • Progress as the basis for OAM for IP L2 Interworking work item • Sent message to mailing list to request more feedback

More Related