Dear authors, Without any hat (i.e., feel free to ignore), in preparation for the IETF-120 I have read your I-D and here are some comments. As always, reviews note the things to be improved and are not criticisms.
# Generic This I-D/idea is really interesting and useful, unsure whether it is really stateless if some routers have to transmit several probes. English is also not my native language, but please use a spelling/grammar check or have it reviewed ;-) Sorry to write this but the text does not always help to convey the good message. # Section 1 IPv6 is now RFC 8200 and not RFC 2460 ;-) and does not have a TTL field but a hop-limit field. If ` The mechanism defined in this memo does not require router changes` is correct, then the intended status should rather be informational as it does not change a protocol. # Section 1.2 Please use the correct BCP14 template # Section 2 Mixing “host” and “node” (i.e., a “router” could also initiate such a traceroute) # Section 3.1 Not all traceroute “probes” are actually ICMP packets so ` The traceroute request MAY be followed by an ICMP extension `does not always apply. Add “and ignored by the receiver” after ` MUST be set to 0.` ` TTL: The Time-To-Live` what about IPv6 hop limit ? ;-) (it further occurs several times) ` Supported SHOULD be ICMP, TCP and UDP.` how can a single field have 3 values ? ;-) # Section 3.2 “server” or “router” in ` A traceroute response is sent by a server` ? # Sections 4 & 5 To be honest, they are not obvious to understand (and to add a 2nd “to be honest”, I have reviewed this in my flight from Brussels to Vancouver, so not with a sharp mind). # Section 6.1 ` It does so by setting the TTL inside the traceroute request message to 0` ? Is it in the IP header ? Then it cannot be transmitted. # Section 9 *I may have misunderstood* the proposed mechanism, but it seems that it could open the door for an amplification attack if all intermediate routers start their own traceroute. Sincerely hoping that it helps, looking forward to the intarea WG discussion -éric
_______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
