Rolf,
I don't believe that this is true. According to Section 3.4 of RFC 2151,
Traceroute is aways directed towards an invalid​ port on the destination node.
TCP and UDP ports 33434 are reserved for this purpose.
I don't see any such restriction in your draft. Did I miss something?
Ron
________________________________
Hi Ron,
you raise a valid point, which however is not specific to reverse
traceroute but applies to regular traceroute just as well, since we
perform the exact same operation. One way to deal with this is assign a
port for this purpose just as for regular traceroute:
https://urldefense.com/v3/__https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=131__;!!NEt6yMaO-gk!E-ykEBNpR2rNjoOUkPjIxU5n8mSBgySkexROpP52eUYXDgXVGu88eOOvzuXvb6MivXawy_Ckbv_6ea_QpuQg0GOaqLQ$
which is what we suggest in the document. For ICMP probes, this issue
does not apply.
Best,
Rolf
Am 06.06.24 um 16:32 schrieb Ron Bonica:
>
> Authors,
>
> Just a reminder regarding the one significant issue that was raised
> during our phone call....
>
> When a reverse traceroute messages reaches its destination (i.e., the
> initiating node), what prevents it from being delivered to an application?
>
>
> Ron
>
>
> Juniper Business Use Only
>
>
Juniper Business Use Only
_______________________________________________
Int-area mailing list -- [email protected]
To unsubscribe send an email to [email protected]
