Hi, Route logging was removed entirely from the 03 base draft, due to the problems it causes with fragmentation and message length. There was a discussion on the mailing list to use it for the diagnostics.
Currently the diagnostic draft suggests using the Path Track method to retrieve diagnostic information. In order to collect diagnostic information from all peers in a route the requesting peer must send a separate request to each peer in the route. In past versions there was an option for the requesting peer to send one request and each peer in the route would respond with his diagnostic information, this option was removed due to security considerations (message explosions attack) and we were looking for another method to optimize the diagnostic information reporting. I suggest adding a route log option to the Inspect method. This will enable a requesting peer to send one request and collect diagnostic information from the peers in the route. In order to limit the message length and prevent fragmentation we can specify a fixed subset of diagnostic information that will be reported when route log is requested. The full diagnostics will still be collected using the Path Track method. Does this looks like a reasonable optimization for collecting the diagnostic information Thanks Roni Even
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
