Re: [Privacy-pass] Call for Adoption of Key Consistency and Discovery Draft

[Christopher Wood <[e-mail]>]

On Thu, Oct 6, 2022, at 12:02 PM, Tommy Pauly wrote:
>> On Oct 5, 2022, at 8:09 PM, Martin Thomson <[e-mail]> wrote:
>> 
>> On Thu, Oct 6, 2022, at 13:14, Tommy Pauly wrote:
>>> My suggestion is that the general technique of double checking like 
>>> draft-schwartz-ohai-consistency-doublecheck does — in that case once 
>>> with a GET request to a reverse proxy and once with a CONNECT request 
>>> to a forward proxy, followed by a GET — could be described in the main 
>>> key consistency document. I think really it boils down to “do a lookup 
>>> with two different proxies, or do one lookup directly and another 
>>> lookup with a proxy”.
>> 
>> Don't we already do that?
>> 
>> https://chris-wood.github.io/key-consistency/draft-wood-key-consistency.html#name-shared-proxy-with-key-confi
>
> Yes, it does. I think it could reasonably give some non-normative 
> examples of specifics (mentioning that you could do a GET and a 
> CONNECT/CONNECT-UDP/etc) for HTTP-style proxies, and not require a 
> separate document to spell out the protocol details, or mandate the use 
> of specific methods and versions.
>
> I wonder if it also would be worth mentioning mixing Direct Discovery 
> and Proxy Discovery — if you are OK to reveal your IP to the server, 
> then you could have one check through the proxy and one check without, 
> and it might have similar properties (if I’m not missing anything).

Agreed -- This seems like a fine variant to add (and describe):

   https://github.com/chris-wood/key-consistency/issues/24

Best,
Chris