Hi, Ron, Authors,

As I was reading over draft-ietf-intarea-probe-00, and wanted to share a couple 
of observations for your consideration.


  *   Have you considered the tradeoff of defining new ICMP Types versus 
extending existing ICMP Types? If using existing ICMPv6 Echo Request/Reply and 
extending them instead of defining brand new types, the backwards 
interoperability achieved is higher
  *   Have you considered using other protocols as well in addition to ICMP for 
the PROBE message, which can elicit ICMP errors or responses with appropriate 
extensions? In particular UDP is a protocol much used and desired for probes.

These two points actually reminded me of 
https://tools.ietf.org/html/draft-shen-traceroute-ping-ext-04 (and the 
ICMP-only predecessor draft-shen-udp-traceroute-ext-01) that defines a probe 
extension applied to ICMP Echo Request and UDP, and RFC 4884 extensions to 
responses. That approach seems somewhat more generic.

Additionally, I was also reminded of the ICMP AUP at RFC 7279, it would be 
useful to map against that doc to show how this is (as it is the case) a really 
good use of ICMP.

Thanks!

— Carlos.


On Jun 23, 2017, at 3:55 PM, 
[email protected]<mailto:[email protected]> wrote:


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Area Working Group of the IETF.

       Title           : PROBE: A Utility For Probing Interfaces
       Authors         : Ron Bonica
                         Reji Thomas
                         Jen Linkova
                         Chris Lenart
                         Mohamed Boucadair
Filename        : draft-ietf-intarea-probe-00.txt
Pages           : 17
Date            : 2017-06-23

Abstract:
  This document describes a network diagnostic tool called PROBE.
  PROBE is similar to PING, in that it can be used to test the status
  of a probed interface.  It differs from PING in that it does not
  require bidirectional connectivity between the probing and probed
  interfaces.  Alternatively, 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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-intarea-probe/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-intarea-probe-00
https://datatracker.ietf.org/doc/html/draft-ietf-intarea-probe-00


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area

—
Carlos Pignataro, [email protected]<mailto:[email protected]>

“Sometimes I use big words that I do not fully understand, to make myself sound 
more photosynthesis."

_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to