1 / 6

Proactive Connection Verification and Continuity Check for MPLS Transport Profile

This draft outlines the updates to the methodology of performing proactive connection verification (CV) and continuity checks (CC) within the MPLS Transport Profile (MPLS-TP). The document focuses on clarifying procedures, reducing processing loads on source Maintenance End Points (MEPs), and ensuring the effective detection of mis-connectivity. Key enhancements include the interleaving of CC and CV messages, IP encapsulation for backward compatibility, and new diagnostic codes for Remote Defect Indication (RDI). Ongoing feedback will further refine the draft.

yuki
Télécharger la présentation

Proactive Connection Verification and Continuity Check for MPLS Transport Profile

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. Proactive Connection Verification, Continuity Check and Remote Defect indication for MPLS Transport Profiledraft-ietf-mpls-tp-cc-cv-rdi-02editors:Dave Allan, John Drake, George Swallow

  2. Changes Since the Last Version • Comment resolution • Primarily clarification and editorial • Major changes • Interleaving of CC and CV • Relocation of source MEP information • Clarifications on the startup procedures • Minor changes • IP encapsulation added for backwards compatibility • RDI clarified as being a diagnostic code • Poll/Final clarified as not valid operation for GAL/G-ACh encapsulated BFD

  3. CC CC CC CV CC Interleaving of CC and CV • Objective is to reduce sink MEP processing load while still offering mis-connectivity detection • A source MEP can send CV source MEP information every ‘n’ CC messages • Note CV counts as a CC for LOC defect detection • Discussion point is defect exit criteria • Either LSP “locks” in down state on detecting mis-connectivity OR there is a minimum insertion interval for CV

  4. Relocation of Source MEP Information • No longer uses ACh TLV • ACh channel type identifies if source MEP TLV trails the BFD control packet 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0 0 0 1|Version| Flags | 0xHH BFD CV Code Point | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ BFD Control Packet ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Unique MEP-ID of source of the BFD packet ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  5. Clarification on Startup • For DOWN and INIT states, tx rate is 1/sec and detection time is 3.5 seconds • On transition to UP tx rate switches to configured/negotiated rate and detection time is “detect mult x tx interval”

  6. Next Steps • Continue to gather feedback from the list • May need to progress draft without addressing uni-directional paths • Document in a “bis” version

More Related