<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.heiwin-intarea-reverse-traceroute-stateless" target="https://datatracker.ietf.org/doc/html/draft-heiwin-intarea-reverse-traceroute-stateless-01">
   <front>
      <title>Stateless Reverse Traceroute</title>
      <author initials="V." surname="Heinrich" fullname="Valentin Heinrich">
         </author>
      <author initials="R." surname="Winter" fullname="Rolf Winter">
         </author>
      <date month="June" day="3" year="2024" />
      <abstract>
	 <t>   Only very few troubleshooting tools exist, that universally work on
   the public internet.  Ping and traceroute are the ones that are most
   frequently used, when issues arise that are outside the user&#x27;s
   administrative reach.  Both perform quite basic checks.  Ping can
   only confirm basic reachability of an interface.  Traceroute can
   enumerate routers in the forward direction of a path but remains
   blind to the reverse path.  In this memo, ICMP extensions are
   defined, that allow to build a reverse traceroute tool for the public
   internet without having to store state on the host performing the
   actual reverse traceroute operation.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-heiwin-intarea-reverse-traceroute-stateless-01" />
   
</reference>
