Skip to main content

Bidirectional Forwarding Detection (BFD) Directed Return Path for MPLS Label Switched Paths (LSPs)
draft-ietf-mpls-bfd-directed-30

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Nicolai Leymann <n.leymann@telekom.de>, The IESG <iesg@ietf.org>, draft-ietf-mpls-bfd-directed@ietf.org, james.n.guichard@futurewei.com, mpls-chairs@ietf.org, mpls@ietf.org, n.leymann@telekom.de, rfc-editor@rfc-editor.org
Subject: Document Action: 'Bidirectional Forwarding Detection (BFD) Directed Return Path for MPLS Label Switched Paths (LSPs)' to Experimental RFC (draft-ietf-mpls-bfd-directed-26.txt)

The IESG has approved the following document:
- 'Bidirectional Forwarding Detection (BFD) Directed Return Path for MPLS
   Label Switched Paths (LSPs)'
  (draft-ietf-mpls-bfd-directed-26.txt) as Experimental RFC

This document is the product of the Multiprotocol Label Switching Working
Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mpls-bfd-directed/


Ballot Text

Technical Summary

   Bidirectional Forwarding Detection (BFD) is expected to be able to
   monitor a wide variety of encapsulations of paths between systems.
   When a BFD session monitors an explicitly routed unidirectional path
   there may be a need to direct egress BFD peer to use a specific path
   for the reverse direction of the BFD session.  This document
   describes an extension to the MPLS Label Switched Path (LSP) echo
   request that allows a BFD system requests that the remote BFD peer
   transmits BFD control packets over the specified LSP.

Working Group Summary

   Working group consensus reached after several iterations of earlier versions (shepherd report provides details).  

Document Quality

   One implementation reported and documented in the shepherd writeup. 

Personnel

   The Document Shepherd for this document is Nicolai Leymann. The
   Responsible Area Director is Jim Guichard.

RFC Editor Note