> The choice of DHT typically has protocolar implications, such as the use of XOR metric in Kademlia, or the bootstrap algorithm.
> Furthermore, different DHTs have distinct properties, including provisions for fault tolerance, resource recovery, latency bounds, and byzantine tolerance, which here seems like a concern.
What in the RFC is dependent or contingent on those? from what I read in it none of those properties affect what is specified in the draft.
> All nodes must use the same DHT. As a result, this cannot be implemented without knowing the particular DHT in use.
Not according to the draft. Sure, if a zone uses a specific DHT and then other nodes not using the same DHT they won't be able to resolve addresses from that zones, but everything in this draft would still be valid.
> Furthermore, different DHTs have distinct properties, including provisions for fault tolerance, resource recovery, latency bounds, and byzantine tolerance, which here seems like a concern.
What in the RFC is dependent or contingent on those? from what I read in it none of those properties affect what is specified in the draft.
> All nodes must use the same DHT. As a result, this cannot be implemented without knowing the particular DHT in use.
Not according to the draft. Sure, if a zone uses a specific DHT and then other nodes not using the same DHT they won't be able to resolve addresses from that zones, but everything in this draft would still be valid.