Hi all,

A couple of issues were filed on github and resolved in this update, as
summarized in section 7.2:

7.2.  Changes from draft-fenner-intarea-probe-clarification-00


   *  Changed "NULL" to "NUL" when referring to the ASCII control

      character, per RFC20.


   *  Consistently refer to interface name and index using their yang

      names, not SNMP names.


   *  Added [] around the Data following the ICMP Extension Structure in

      Figure 1 and Figure 3 to indicate that it is optional.

We feel this draft is ready to move forward in the process; any feedback is
very welcome.

Thanks,
  Bill



---------- Forwarded message ---------
From: <[email protected]>
Date: Fri, Jul 5, 2024 at 9:20 AM
Subject: New Version Notification for
draft-fenner-intarea-probe-clarification-01.txt
To: Bill Fenner <[email protected]>, Chris Lenart <[email protected]>,
Jen Linkova <[email protected]>, Mohamed Boucadair <
[email protected]>, Reji Thomas <[email protected]>, Ron
Bonica <[email protected]>


A new version of Internet-Draft
draft-fenner-intarea-probe-clarification-01.txt has been successfully
submitted by Bill Fenner and posted to the
IETF repository.

Name:     draft-fenner-intarea-probe-clarification
Revision: 01
Title:    PROBE: A Utility for Probing Interfaces
Date:     2024-07-05
Group:    Individual Submission
Pages:    21
URL:
https://www.ietf.org/archive/id/draft-fenner-intarea-probe-clarification-01.txt
Status:
https://datatracker.ietf.org/doc/draft-fenner-intarea-probe-clarification/
HTML:
https://www.ietf.org/archive/id/draft-fenner-intarea-probe-clarification-01.html
HTMLized:
https://datatracker.ietf.org/doc/html/draft-fenner-intarea-probe-clarification
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-fenner-intarea-probe-clarification-01

Abstract:

   This document describes a network diagnostic tool called PROBE.
   PROBE is similar to PING in that it can be used to query the status
   of a probed interface, but it differs from PING in that it does not
   require bidirectional connectivity between the probing and probed
   interfaces.  Instead, PROBE requires bidirectional connectivity
   between the probing interface and a proxy interface.  The proxy
   interface can reside on the same node as the probed interface, or it
   can reside on a node to which the probed interface is directly
   connected.  This document updates RFC 4884 and obsoletes RFC 8335.



The IETF Secretariat
_______________________________________________
Int-area mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to