The way BitTorrent works, it’s basically a Merkle tree over the chunks. So, you need to compute the main hash over the zone data.
Maybe there’s a smart way to compute hash over the data that includes that hash, but my poor brain thinks it would break the Matrix (or at least the hashing function). Therefore either you need to exclude the data that changes (hash and its RRSIG) when computing the hash for the BitTorrent and the receiving side would have to reassemble this. Or you would need OOB mechanism to distribute the hash (different part of the tree, CDN, ...). Ondřej -- Ondřej Surý — ISC > On 28 Jul 2018, at 23:58, John Levine <jo...@taugh.com> wrote: > > In article <208f049b-b35a-4755-9a20-fa0c7f685...@isc.org> you write: >> a) the hash has to be independent to zone, so either the hash has to reside >> outside of the root zone, or the root zone file would >> have to be reconstructed with “the torrent hash” and “the torrent data”; >> generally you would want the hash to be signed, >> so the TORRENT RR + RRSIG would have to be distributed outside of the data >> received via BitTorrent > > I'm confused again. Why couldn't the hash RR and sig be in the zone > just like any other record in the zone? > > R's, > John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
