1 / 5

IETF -90 Toronto, ON Vengada Prasad Govindan Nobo Akiya

Extended BFD Discriminator TLV for MPLS ping (draft- vgovindan - mpls -extended- bfd -disc- tlv -00). IETF -90 Toronto, ON Vengada Prasad Govindan Nobo Akiya. Problem statement.

quasar
Download Presentation

IETF -90 Toronto, ON Vengada Prasad Govindan Nobo Akiya

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. Extended BFD Discriminator TLV for MPLS ping(draft-vgovindan-mpls-extended-bfd-disc-tlv-00) IETF-90 Toronto, ON Vengada Prasad Govindan Nobo Akiya

  2. Problem statement • Usage of <MPLSFEC, LSP> as the BFD session de-multiplex key at the LSR egress permits only one BFD session to be established. • Use cases involving more than one session per <MPLSFEC, LSP>: • Load balancing using entropy labels. • BFD over MPLSLSP session redundancy.

  3. Details • Generically extend the BFD Discriminator TLV to track more than one session for <MPLSFEC, LSP> • Introduce a new TLV that allows multiple BFD session(s) to be established for a given <MPLSFEC, LSP>. • LSR ingress allocated Path identifier added to the TLV. • LSR egress can allocate one unique discriminator for every LSP ping with a unique path-identifier received. • Migration of sessions established from the old to the new TLV.

  4. Open Items • Do we introduce a new procedure to allow the LSR egress to acknowledge the BFD session establishment? • LSR egress can respond to MPLS ping with CreateAckopcode in the proposed extended TLV. • Do we introduce an explicit mechanism for deleting BFD session(s) at the LSR egress? • Opcode based Delete/ DeleteAck signaled from the LSR ingress using MPLS ping. • Purge timer based: Remove the BFD sessions that tranisition from Up->Down after a timer expiry. • Continue with status quo? • Comments and feedback welcome!

  5. Next steps • Discuss open items and re-publish before seeking WG adoption.

More Related