Re: [quicwg/base-drafts] Add application parameters to QUIC handshake and use it for H3 SETTINGS (#3086)

[hardie <[e-mail]>]

On Fri, Oct 11, 2019 at 2:13 PM Nick Harper <[e-mail]>
wrote:

> Regarding the confidentiality of this mechanism:
>
> I am assuming (perhaps incorrectly) that the contents advertised in the
> client's application parameters are no more confidential than transport
> parameters. In H3, both the transport parameters and SETTINGS are
> effectively constant per implementation - any identifying bit leaked by the
> H3 SETTINGS is also leaked by the transport parameters. My assumption is
> that other future applications using this mechanism will be similar in the
> amount of (non) leakage, but that can be analyzed on a per-application
> basis.
>
> This definitely needs to be per-application and may need to be per
parameter.  If you treat the DNS client subnet as an application parameter
for DNS over QUIC, for example, the implications may be much more privacy
sensitive than for other EDNS0 parameters.

Ted


> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/3086?email_source=notifications&email_token=AAKVXZDWUYVNFQ2E5TAW7ODQODT67A5CNFSM4I7SPSU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBHJGQ#issuecomment-541226138>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAKVXZFXDQRJ32OEVYHAOCDQODT67ANCNFSM4I7SPSUQ>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3086#issuecomment-541960573