Post

Richard Barnes
@ipv.sx

OK, I wrote up a whole blog post with some more detailed thoughts on this. Curious if anything here resonates with other folks. Thanks to @iame.li, @dholms.at, and @bnewbold.net for helpful pointers and discussions! pckt.blog/b/bits-of-en...

pckt.blogAll data should be permissioned data - Bits of EntropyMy post with vague complaints about the proposal that made for permissioned data got a bit of attention. Daniel was kind enough to take the time to chat with me...
Richard Barnes@ipv.sx

@dholms.at - What is the right venue for discussion on this Permissioned Data proposal you wrote up. atp@ietf.org or something else? I think it is wrong in some pretty fundamental ways. Or at least the motivations are poorly articulated.

github.comgithub.com
Boris
@bmann.ca

Thanks for the write up - I copied it into the forum and asked you a question about patterns of dev inside / outside the IETF over time discourse.atprotocol.community/t/all-data-s...

discourse.atprotocol.communityAll data should be permissioned data - Bits of Entropy@ipv.sx, just pulling this stuff out: On the one hand, it’s generally not good form to both have an IETF working group and do new work elsewhere. On the other hand, it is good to keep the IETF group...

0 reposts0 likes

No replies yet.