IETF Logo Mail Archive

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

Eric Orth <ericorth@google.com> Wed, 05 October 2022 22:51 UTC

Return-Path: <ericorth@google.com>
X-Original-To: privacy-pass@ietfa.amsl.com
Delivered-To: privacy-pass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E1AC1522A9 for <privacy-pass@ietfa.amsl.com>; Wed, 5 Oct 2022 15:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.605
X-Spam-Level:
X-Spam-Status: No, score=-17.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tfEMfEpW0L5I for <privacy-pass@ietfa.amsl.com>; Wed, 5 Oct 2022 15:51:38 -0700 (PDT)
Received: from mail-oa1-x2f.google.com (mail-oa1-x2f.google.com [IPv6:2001:4860:4864:20::2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46B29C14CF09 for <privacy-pass@ietf.org>; Wed, 5 Oct 2022 15:51:38 -0700 (PDT)
Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-1322d768ba7so344315fac.5 for <privacy-pass@ietf.org>; Wed, 05 Oct 2022 15:51:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=v+J7bcIoWcIjtwTHFO5ZM1gjSRziG7bI/G3mf9P76XM=; b=YW0gDehlNnvRsK/BMAC6TMJ3A2Sk43K0UBer/y30t5qkvSkcv9LuDyqZ51UBQtRlJf xSpB+wUaIesmyI79Vp3A4SrR7qh9CETuimgAxUXV0eY7qhuYWvuv3+nC5zakXdTPoha8 j2JvWwxWhatazC/qDHYN5lFn2Try+/16+eUsRkXJfceWw0kD6H5pGhUhwQXHYZwAFZzI e1nYwIDmpJDlhOsfixrX/t6WGlHMsLESMInW30vyw4tQMGpJ5SVyCNT1PB35UnddsXec hSXArTCu+wsIaBlD/+PtLYYrwmqiEeEC8StrngNV4iQDe6/Ky4xAffXwdB547N7aAKpv oO+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=v+J7bcIoWcIjtwTHFO5ZM1gjSRziG7bI/G3mf9P76XM=; b=deufM0NGWem0kiolE2f4dQ5wQFGck60tlPEV2E1IYOCDdGcumm9b0CNAzYHTJA43sh 9xbFtYnNSBKpwm3HYvrAJSd4YvN3yd12NiPkL2DnLSz3rNi9h0IrQ0FRE9EMfqkRByHn KjIgbTp8Verd45MG0kMxMQvIvoJO4ulpuNdEPNX8PiC5bksG5h0mNmxxVi9TwHS3iknV 4s/ADPgNzoG7+2zpBrZzJ7rtZZRFfwRsQ12/QkPh23FNoG13bDIOWRpBpYO2VFdgue6O eLsp45DE2MYdCZLNSIqVD/JWT7+Qy1sZ4PNC92CKLj190SolOTOB4miCOvNjOcL75lsR GBvg==
X-Gm-Message-State: ACrzQf2GC3C0x14dF4tB5/xXZqLubOEtutWFdXAt27JBCYQtQ1DCBURu +IYS7NnAOzbi0Ak3wG83PC9bTWz/5uCLeixKNYXDV5ozH9g=
X-Google-Smtp-Source: AMsMyM4/UvjYRp6Z6Tix2wj7cj/3FN46vXC/8Bao8khTImOFo7ZTtU+v+u3RdYk5Ncaki4WCkM6j+OIYuJdQasGdNkc=
X-Received: by 2002:a05:6870:6088:b0:12c:19b0:f878 with SMTP id t8-20020a056870608800b0012c19b0f878mr1029590oae.70.1665010297235; Wed, 05 Oct 2022 15:51:37 -0700 (PDT)
MIME-Version: 1.0
References: <CAMOjQcH6n=DzX0Mh-ufLJ9srqxP+zt6kuQgrjYs4mic6K6Wg=g@mail.gmail.com> <CAHbrMsAqfgJNOfxAy7LXztYLPzdVvKoKfuAXzOhHYVTm6=LkdA@mail.gmail.com>
In-Reply-To: <CAHbrMsAqfgJNOfxAy7LXztYLPzdVvKoKfuAXzOhHYVTm6=LkdA@mail.gmail.com>
From: Eric Orth <ericorth@google.com>
Date: Wed, 05 Oct 2022 18:51:26 -0400
Message-ID: <CAMOjQcEfLZJsONzVKJOn-aPwtg8P37ZVh+ypfirbbjRz+46yjw@mail.gmail.com>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: privacy-pass@ietf.org
Content-Type: multipart/alternative; boundary="00000000000050c96f05ea516bbb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/privacy-pass/9jBevJlNymKNUbGZuNtqrSHqWlk>
Subject: Re: [Privacy-pass] Call for Adoption of Key Consistency and Discovery Draft
X-BeenThere: privacy-pass@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Privacy Pass Protocol <privacy-pass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/privacy-pass>, <mailto:privacy-pass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/privacy-pass/>
List-Post: <mailto:privacy-pass@ietf.org>
List-Help: <mailto:privacy-pass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/privacy-pass>, <mailto:privacy-pass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2022 22:51:42 -0000

On Wed, Oct 5, 2022 at 6:32 PM Ben Schwartz <bemasc=
40google.com@dmarc.ietf.org> wrote:

> On Wed, Oct 5, 2022 at 6:17 PM Eric Orth <ericorth=
> 40google.com@dmarc.ietf.org> wrote:
>
> One specific minor concern is that I
>> recall draft-schwartz-ohai-consistency-doublecheck had a payload format
>> specific to use for OHAI. I suggested at IETF 114 that the draft be split
>> into two, one for the general protocol, and one for the OHAI-specific
>> payload and any other OHAI-specific details (which could maybe be merged
>> with other similar OHAI drafts for payload specs).
>>
>
> I think this is achievable and perhaps worthwhile.  However, DoubleCheck
> still depends on (1) use of a proxy similar to OHTTP and (2) an OHTTP-like
> threat model in which the proxy is trusted not to collude with the target
> service.  As such, it would only be applicable to Privacy Pass in contexts
> where an OHTTP-like proxy is also in use.
>

I agree, but I don't think use of OHTTP means a protocol should only be
discussed in OHAI.  OHTTP is expected to be useful for many different
contexts.  If PRIVACYPASS has need for some protocol, and that protocol is
best accomplished using OHTTP, it's still a PRIVACYPASS-appropriate draft.


> --
> Privacy-pass mailing list
> Privacy-pass@ietf.org
> https://www.ietf.org/mailman/listinfo/privacy-pass
>

v2.23.0 | Report a Bug | By Email