[Ohai] Fwd: New Version Notification for draft-schwartz-ohai-consistency-doublecheck-00.txt

Ben Schwartz <bemasc@google.com> Thu, 07 April 2022 21:26 UTC

Return-Path: <bemasc@google.com>
X-Original-To: ohai@ietfa.amsl.com
Delivered-To: ohai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB2E3A17B0 for <ohai@ietfa.amsl.com>; Thu, 7 Apr 2022 14:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.608
X-Spam-Level:
X-Spam-Status: No, score=-17.608 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZNKKs92ZVxkO for <ohai@ietfa.amsl.com>; Thu, 7 Apr 2022 14:26:13 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF09C3A17A7 for <ohai@ietf.org>; Thu, 7 Apr 2022 14:26:12 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id e22so8405074ioe.11 for <ohai@ietf.org>; Thu, 07 Apr 2022 14:26:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ZEq3TR+l9gmabnKOQa30Fb6SsX1m6mTyjoxeaqOKmu8=; b=UcctO1xXcERJN4EcK6jmcsaQUQzuOtETFGfE0aKPARThqWBpQsAHiUXFHQjo6Bz7hA 8n8gw6eXMOCtVjMitk7pLlFul+sOXnVNRm8WilylYuHsKW/YO0lRG3lcIYiStMccYGET L3Q9fJmKZcWvs61QqWVJBaT6lRRFcfZjqzoteb80wS74frbrOEyIZcEi1D7R/ztr4jvT LA/2ZTgFhoJ9hFQl+eGkGR3GUNNmwsd3wHYMaEutlgi2/kjZPtlDBbwlFwPMfdS2jDog Uc2h8KovQD1FhVIB8dTg9PcdOVjftdoFne4X11UaM3EMTU34iQA648JUdSZTydBEcB0P eb0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ZEq3TR+l9gmabnKOQa30Fb6SsX1m6mTyjoxeaqOKmu8=; b=p/7ioOIyVUpqznPjOMhz5CRn+WcNouPo+sN91+iJDVLt7sVjfNo+Cl8bMjxi5vd1q1 uz5pM+itpUWFhdxy3Ad2+YGmcFrKOD+7R5DVWo1tTubdub02ICHJsLyp3EyJPRel6vI8 jBODFvKLADt1VZKpsyYpV8k9IQdU3piw5WLG3yIvM909iFUw3/He/SLVkSM9M3un09mi WnKw+77cd/lFNxGUbxUhNYbZFJOCqRismLO90Pfl6JZGJtRns8FA5fPJuRgIltt1Er3y zYE5ZsyilMI5vfdQQ+YUT+JpoQ7mNjzS9RdsCrq+KmmE5ja0ocgUtGyw7ccUsARwqrQD mMZA==
X-Gm-Message-State: AOAM533INQ09neUQEXIczt7bNUn4Ba79Wi1bBwFlePSbIztw2MbH6lhQ rGxUxDbO0O7SAvYl5m0RlKn71tLSVFsGXrs/5gd2VkYFsB7tFw==
X-Google-Smtp-Source: ABdhPJwBSfuviQ638HhBx05b0zNzebZA/Gpkazb+RWA+8vz/2r5CBDAH084bLQx7UNH/CCJmuUi/zDh6CpxwUsiMF44=
X-Received: by 2002:a6b:7b03:0:b0:648:40c7:309d with SMTP id l3-20020a6b7b03000000b0064840c7309dmr7177056iop.15.1649366771094; Thu, 07 Apr 2022 14:26:11 -0700 (PDT)
MIME-Version: 1.0
References: <164936617915.4445.18094554549085923675@ietfa.amsl.com>
In-Reply-To: <164936617915.4445.18094554549085923675@ietfa.amsl.com>
From: Ben Schwartz <bemasc@google.com>
Date: Thu, 07 Apr 2022 17:25:59 -0400
Message-ID: <CAHbrMsAkprChiVp9muoi=uwHuQQHHg1pm9QM3qF5HsL+cgZDxw@mail.gmail.com>
To: ohai@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="00000000000085c58205dc1720b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohai/TaqPL31A2e-6Nnegzwgf6L0WvNI>
Subject: [Ohai] Fwd: New Version Notification for draft-schwartz-ohai-consistency-doublecheck-00.txt
X-BeenThere: ohai@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Oblivious HTTP Application Intermediation <ohai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ohai>, <mailto:ohai-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ohai/>
List-Post: <mailto:ohai@ietf.org>
List-Help: <mailto:ohai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ohai>, <mailto:ohai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2022 21:26:16 -0000

Hi OHAI,

In the last session, we had some discussion about the relationship between
key consistency and key discovery.  I argued that it is natural to combine
them, and I've written a draft exploring how that could work.  In brief, it
relies on the Oblivious Proxy also being a MASQUE server, so that the
client can fetch the KeyConfig from both the proxy (providing consistency)
and the origin (providing authenticity).

This approach relies on a small JSON format for conveying KeyConfigs and
URI templates, which is shared with MASQUE and defined in
https://datatracker.ietf.org/doc/html/draft-schwartz-masque-access-descriptions-00
.

Thoughts appreciated,
Ben Schwartz

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Thu, Apr 7, 2022 at 5:16 PM
Subject: New Version Notification for
draft-schwartz-ohai-consistency-doublecheck-00.txt
To: Benjamin M. Schwartz <bemasc@google.com>



A new version of I-D, draft-schwartz-ohai-consistency-doublecheck-00.txt
has been successfully submitted by Benjamin Schwartz and posted to the
IETF repository.

Name:           draft-schwartz-ohai-consistency-doublecheck
Revision:       00
Title:          Key Consistency for Oblivious HTTP by Double-Checking
Document date:  2022-04-07
Group:          Individual Submission
Pages:          12
URL:
https://www.ietf.org/archive/id/draft-schwartz-ohai-consistency-doublecheck-00.txt
Status:
https://datatracker.ietf.org/doc/draft-schwartz-ohai-consistency-doublecheck/
Html:
https://www.ietf.org/archive/id/draft-schwartz-ohai-consistency-doublecheck-00.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-schwartz-ohai-consistency-doublecheck


Abstract:
   The assurances provided by Oblivious HTTP depend on the client's
   ability to verify that it is using the same Request Resource and
   KeyConfig as many other users.  This specification defines a protocol
   to enable this verification.




The IETF Secretariat