RSVP-TE extensions for MPLS-TP OAM Configuration

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 CCCV in
  MPLS-TP

OAM Function
Continuity Check (BFD for CC)
1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Performance Monitoring/Loss
0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Performance Monitoring/Delay
1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0
Connectivity Verification (BFD for CCCV)
0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1
To be Defined
3
BFD for CC TLV Definition
Path/Resv message
LSP Attributes
OAM Configuration TLV
BFD CC Configuration TLV
4
BFD for CCCV in G-ACh

• Unique MEP-ID of source of the BFD packet
  provides 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

5
BFD for CCCV TLV Definition
Path/Resv message
LSP Attributes
OAM Configuration TLV
BFD CCCV Configuration TLV
6
Example of GMLS setup of BFD for CCCV
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)
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