%% You should probably cite draft-ietf-mpls-bfd-directed-30 instead of this revision.
@techreport{ietf-mpls-bfd-directed-21,
    number =    {draft-ietf-mpls-bfd-directed-21},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-mpls-bfd-directed/21/},
    author =    {Greg Mirsky and Jeff Tantsura and Ilya Varlashkin and Mach Chen},
    title =     {{Bidirectional Forwarding Detection (BFD) Directed Return Path for MPLS Label Switched Paths (LSPs)}},
    pagetotal = 9,
    year =      2022,
    month =     nov,
    day =       7,
    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. This document describes an extension to MPLS LSP echo request that allows a BFD system request that the remote BFD peer transmits BFD control packets over the specified LSP.},
}