1 / 7

RSVP-TE extensions for MPLS-TP OAM Configuration

RSVP-TE extensions for MPLS-TP OAM Configuration. draft-bellagamba-ccamp-rsvp-te-mpls-tp-oam-ext-03. Elisa Bellagamba Ericsson Loa Andersson Ericsson Pontus Sköldström Acreo. OAM Function field. draft-ietf-ccamp-oam-configuration-fwk. In case of MPLS-TP OAM:

robert-harrell
Download Presentation

RSVP-TE extensions for MPLS-TP OAM Configuration

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. RSVP-TE extensions for MPLS-TP OAM Configuration draft-bellagamba-ccamp-rsvp-te-mpls-tp-oam-ext-03 Elisa Bellagamba Ericsson Loa Andersson Ericsson Pontus Sköldström Acreo

  2. OAM Function field draft-ietf-ccamp-oam-configuration-fwk In case of MPLS-TP OAM: • OAM Type = 2 • BFD is the Choosen tools for MPLS-TP CC&CV in MPLS-TP OAM Function Continuity Check (BFD for CC) Performance Monitoring/Loss Performance Monitoring/Delay Connectivity Verification (BFD for CC&CV) To be Defined IETF 76, Hiroshima

  3. BFD for CC: TLV Definition Path/Resv message LSP Attributes OAM Configuration TLV BFD CC Configuration TLV IETF 76, Hiroshima

  4. …from draft-swallow-mpls-tp-identifiers Unique MEP-ID ME ID Unique MEP-ID of source of BFD packet Node ID Logical Interface Handle BFD Control Packet BFD for CC&CV in G-ACh • Unique MEP-ID of source of the BFD packetprovides a global context for the BFD session so if packet is mis-delivered, lost context can not be confused • Based on draft-asm-mpls-tp-bfd-cc-cv • The new tool is obtained introducing Unique MEP-ID, between the ACH (Associated Channel Header) and the current BFD • The benefit of this solution is to maintain the base behavior and protocol version of BFD IETF 76, Hiroshima

  5. BFD for CC&CV: TLV Definition Path/Resv message LSP Attributes OAM Configuration TLV BFD CC&CV Configuration TLV IETF 76, Hiroshima

  6. PE PE P P BFD CC&CV OAM Configuration TLV BFD CC&CV OAM Configuration TLV BFD control packet encapsulated in the ACH BFD control packet encapsulated in the ACH Unique MEP-ID of source Unique MEP-ID of source BFD control pkt BFD control pkt BFD session Section Section Section Example of GMLS setup of BFD for CC&CV draft-bellagamba-ccamp-rsvp-te-mpls-tp-oam-ext Unique MEP-ID of source Unique MEP-ID of source LSP (RSVP-TE) LSP (RSVP-TE) IETF 76, Hiroshima

  7. Next Steps • Work in collaboration with the authors of: • draft-ietf-ccamp-oam-configuration-fwk • draft-ietf-ccamp-rsvp-te-eth-oam-ext • draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext-01 • Integrate the remaining MPLS-TP OAM tools • Adopt it as CCAMP WG document IETF 76, Hiroshima

More Related