Dear BFD WG,





A new -08 version of Unaffiliated BFD Echo has just been posted. Link and Diff 
as below.


This version is intended to address Greg's comments on -07 version of this 
draft.


Many thanks to Greg for his thorough review and helpful comments.






Best Regards,


Xiao Min






Original



From: internet-dra...@ietf.org <internet-dra...@ietf.org>
To: i-d-annou...@ietf.org <i-d-annou...@ietf.org>;
Cc: rtg-bfd@ietf.org <rtg-bfd@ietf.org>;
Date: 2023年07月06日 10:20
Subject: I-D Action: draft-ietf-bfd-unaffiliated-echo-08.txt



A New Internet-Draft is available from the on-line Internet-Drafts
directories. This Internet-Draft is a work item of the Bidirectional
Forwarding Detection (BFD) WG of the IETF.
 
   Title           : Unaffiliated BFD Echo
   Authors         : Weiqiang Cheng
                     Ruixue Wang
                     Xiao Min
                     Reshad Rahman
                     Raj Chetan Boddireddy
   Filename        : draft-ietf-bfd-unaffiliated-echo-08.txt
   Pages           : 12
   Date            : 2023-07-05
 
Abstract:
   Bidirectional Forwarding Detection (BFD) is a fault detection
   protocol that can quickly determine a communication failure between
   two forwarding engines.  This document proposes a use of the BFD Echo
   where the local system supports BFD but the neighboring system does
   not support BFD.  BFD Control packet and its processing procedures
   can be executed over the BFD Echo port where the neighboring system
   only loops packets back to the local system.
 
   This document updates RFC 5880.
 
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/
 
There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo-08
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-bfd-unaffiliated-echo-08
 
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts

Reply via email to