Hi,I would like to use the energy from the meeting to get closure on the two issues I presented at the meeting. I will use two separate Email threads, one for each issue. Here, I'd like to come back to the encoding question - or going with ICMP Echo or Extended Echo.
As I said, the authors would be in favour of using Echo with new ICMP codes and then either using RFC 4884 extensions or hand-roll TLVs. The primary reason would be that it has a good likelyhood to go through NAT routers and the reality of today's internet is, that most internet users are behind a NAT, whether we like it or not.
There was a question how legacy hosts react to Echo with new codes. We already presented this at IETF 118. You can find the results here:
https://youtu.be/w7K_BT1UB1Q?t=3164In short, it works and we can easily distinguish a reverse traceroute answer from a legacy host just responing with an Echo reply.
Comments? Best, Rolf
smime.p7s
Description: Kryptografische S/MIME-Signatur
_______________________________________________ Int-area mailing list -- int-area@ietf.org To unsubscribe send an email to int-area-le...@ietf.org
