It is necessary to clarify the scope of the problems that are being
addressed and to precisly define what 'diagnostics' mean. Currently, it is
very open ended and includes:
-routing diagnostics
-detecting malfunctioning or badly behaving peers
-checking the health of overlay
Overlay maintenance is central to any p2p system. How is that different
from diagnostics?
The suggested solution incorporates two new methods. I think we need a
bit more clarity on what is that existing methods cannot achieve, for
which new methods are required. As an example, one can easily implement
Path_Track using RouteQuery and [Node]Fetch.
What is indeed required is a mechanism to obtain the state
[routing/storage] of a node. This can be done using NodeFetch and may also
be accomplished using Fetch.
-salman
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
