RELOAD-1 was a solid protocol with strengths like the flexibility of TLV, 32-bit alignment, full 160-bit IDs, well defined symbolic values, etc. By comparison, the ASP draft was pretty rough. When these two merged into RELOAD-2, most of the RELOAD-1 pros were lost. Is RELOAD-3 on its way?
Many fields in RELOAD-2 are variable size values or arrays, so why not use Type-Length-Value to make the protocol more "binary readable" and extensible? RELOAD-1 defines a single fixed header and everything else in TLV. That is too good to abandon, not to mention being a perfect construct for supporting multiple DHTs.
By the way, I have seen several drafts use 128-bit ID in fixed structures, which means truncating the low 32-bit of a SHA-1 hash. Is there a potential risk? Any formal paper about this?
Thanks
--Michael
_______________________________________________ P2PSIP mailing list [email protected] https://www1.ietf.org/mailman/listinfo/p2psip
