IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
datatracker.ietf.org
IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
1–9 of 9 posts
Re: IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
#2Re: IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
#3Interestingly, draft authors include members from Google, Fastly, Apple, Cloudflare... so this could have legs.
Re: IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
#4Re: IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
#5Interestingly, draft authors include members from Google, Fastly, Apple, Cloudflare... so this could have legs.
It could have legs without them, it just wouldn't have built-in clout that an appeal to authority affords.
Re: IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
#6This is really cool stuff. Does anyone have a good comparison between Privacy Pass and Anon-Pass ( https://eprint.iacr.org/2013/317.pdf )? Is one better for subscriptions than the other?
You could reach out and share it with them, and see what they say?
Re: IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
#7Interestingly, draft authors include members from Google, Fastly, Apple, Cloudflare... so this could have legs.
Re: IETF Draft: Privacy Pass Framework – privacy-preserving replacement for cookies
#8Interestingly, draft authors include members from Google, Fastly, Apple, Cloudflare... so this could have legs.
I question any "privacy" drafts authored by companies who's business consists of or is related to essentially violating the privacy of their users.
Not defending the mentioned companies here, but comments like these add no value. What specifically about the IETF draft advances the business of violating user privacy? Would it be better for users if Google, Fastly, Apple and Cloudflare abstained from standardization processes?