Subject: [mpls] Fwd: New Version Notification for draft-ietf-mpls-bfd-directed-13.txt

From: Greg Mirsky <[email-masked]>
Date: Thu, 19 Dec 2019 19:35:30 -0800

Dear All,
a new Implementation Status section has been added.
Your comments, questions are always welcome and greatly appreciated.

Regards,
Greg

---------- Forwarded message ---------
From: <[email-masked]>
Date: Thu, Dec 19, 2019 at 7:33 PM
Subject: New Version Notification for draft-ietf-mpls-bfd-directed-13.txt
To: Ilya Varlashkin <[email-masked]>, Gregory Mirsky <
[email-masked]>, <[email-masked]>, Ilya Varlashkin <
[email-masked]>, Jeff Tantsura <[email-masked]>, Mach Chen
(Guoyi) <[email-masked]>

A new version of I-D, draft-ietf-mpls-bfd-directed-13.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-ietf-mpls-bfd-directed
Revision:       13
Title:          Bidirectional Forwarding Detection (BFD) Directed Return
Path
Document date:  2019-12-19
Group:          mpls
Pages:          9
URL:
https://www.ietf.org/internet-drafts/draft-ietf-mpls-bfd-directed-13.txt
Status:
https://datatracker.ietf.org/doc/draft-ietf-mpls-bfd-directed/
Htmlized:       https://tools.ietf.org/html/draft-ietf-mpls-bfd-directed-13
Htmlized:
https://datatracker.ietf.org/doc/html/draft-ietf-mpls-bfd-directed
Diff:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-bfd-directed-13

Abstract:
   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.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat