diff --git a/Web/details.wml b/Web/details.wml
index fb65b57..93a79f9 100644
--- a/Web/details.wml
+++ b/Web/details.wml
@@ -5,12 +5,15 @@
 
 <H2>echo service</H2>
 
-<P>echoping assumes the remote host accepts such connections. Experience show that 
-most Internet routers do and many hosts also. However, some Unices are not 
-shipped with this service enabled and, anyway, the administrator is always 
-free to close it (I think they shouldn't). echoping has therefore less chance 
-to succeed than ping or bing. (On a typical Unix box, "echo" service is 
-configured in /etc/inetd.conf but see the <A HREF="http://www.cert.org/advisories/CA-96.01.UDP_service_denial.html">CERT advisory</A>.)
+<P>echoping, with its default setting, assumes the remote host accepts
+such connections. Experience show that most Internet routers or hosts
+do not. Some Unices are not shipped with this service enabled and,
+anyway, the administrator is always free to close it (I think they
+shouldn't). echoping has therefore less chance to succeed than ping or
+bing. (On a typical Unix box, "echo" service is configured in
+/etc/inetd.conf but see the <A
+HREF="http://www.cert.org/advisories/CA-96.01.UDP_service_denial.html">CERT
+advisory</A>.)
 
 <H2>What does it measure?</H2>
 
@@ -41,12 +44,17 @@ SunOS need time to recover :-)
 <H3>Unix</H3>
 
 <UL>
-<LI><A HREF="ftp://ftp.lip6.fr/pub/networking">bing</A>, a bandwidth measurement tool
+<LI><A
+  HREF="http://www.freenix.fr/freenix/logiciels/bing.html">bing</A>, a
+  bandwidth measurement tool
+<LI>pathchar or <A
+  HREF="http://www.employees.org/~bmah/Software/pchar/">pchar, a bandwidth measurement tool
 <LI>ping, probably available with your system
 <LI>traceroute, idem (otherwise, see <A HREF="ftp://ftp.ee.lbl.gov/">LBL</A>)
 <LI><A HREF="ftp://ftp.arl.mil/pub/ttcp/">ttcp</A>, the best measurement tool but it needs some control over the 
   two machines (nothing to do with
   the T/TCP protocol)
+<LI><A HREF="ftp://ftp.scl.ameslab.gov/pub/netpipe/">Netpipe</A>, it needs some control over the two machines 
 <LI><A HREF="http://www.psc.edu/~pscnoc/treno_info.html">treno</A> (evaluates available bandwidth for TCP) 
 <LI>spray is a tool which I dont't know very well. It is available on some 
   machines (Sun, OSF/1).
@@ -65,7 +73,7 @@ SunOS need time to recover :-)
 <UL>
 <LI>TCP Watcher, a very nice "swiss-army knife" tool, to test ping, DNS, echo. 
   It includes an echo server. Available on <A
-  HREF="http://www.info-mac.org/">Info-Mac</A> in "comm/tcp".
+  HREF="http://www.info-mac.org/">Info-Mac</A> in "comm/inet".
 </UL>
 
 <H3>MS-Windows</H3>
@@ -93,16 +101,18 @@ can be enabled through the Network Control Panel
 
 <H3>Web clients</H3>
 
-You can ping or traceroute on the Web. See 
-  <A
-  HREF="http://www.freenix.org/cgi-bin/traceroute.iphtml">Freenix</A>,
-  <A HREF="http://www.fr.net/internet/trace.html">fr.net</A> (with
-  Autonomous Systems handling) or
-  <A HREF="http://www.tracert.com/">Multiple Traceroute Gateway</A>.
-
+You can ping or traceroute on the Web. See <A
+HREF="http://www.traceroute.org/">traceroute.org</A>.
 
 <P>Use all of them with care, the result is not obvious to interpret.
 
+<P>If you are interested in Internet measurements, there is an <A
+HREF="http://www.ietf.org/">Internet Engineering Task Force</A>
+Working Group, <A
+HREF="http://www.ietf.org/html.charters/ippm-charter.html">IPPM (IP
+Performance Metrics)</A> which produces many fine RFC that are really
+good to read. I appreciate RFC 2330 and 3148.
+
 <P>And don't forget to read RFC 1470 ("Tools for Monitoring and Debugging 
 TCP/IP Internets and Interconnected Devices"), specially its "Benchmark"
 section and the Richard Stevens' books (all of them), published by