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

Ben Schwartz <bemasc@google.com> Wed, 19 October 2022 20:16 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 A5A8BC152596 for <ohai@ietfa.amsl.com>; Wed, 19 Oct 2022 13:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.607
X-Spam-Level:
X-Spam-Status: No, score=-22.607 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_HI=-5, 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=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-XVY2PPBei6 for <ohai@ietfa.amsl.com>; Wed, 19 Oct 2022 13:16:46 -0700 (PDT)
Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 28539C1524D7 for <ohai@ietf.org>; Wed, 19 Oct 2022 13:14:18 -0700 (PDT)
Received: by mail-il1-x12b.google.com with SMTP id o13so9788820ilc.7 for <ohai@ietf.org>; Wed, 19 Oct 2022 13:14:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=0nPpmF2p4MU2QXdOVCMRSYE/oa+6TAE8/YkpvsMzLGI=; b=VN7j4lD1S1UKNrvrMMbbAv2zdsb7NkFylzeDJJDbzd6qZ9fUxXMNXxVSGtfvAf1XhE V9oazqgc5cMgKQHjwPFm5IwcHy69VzZBpWFEGrbLXUxMei4xNqMMbIKLZDpkk2EX3PPy axb6nJMinr3B2Dx8OiPA7mL/yCBnADQayEyqBo4R8XA+6nS1V3TrUXyTbz3kyf8n59yp Mwky6CSVd03WVprTX4nJYDF1M72NwavWGasZWKrpTvN2wo6U4YwXPtsExr+/UTuxcq8Y Zb9icjeO0KC8U3X4SkDUdzTUcFdqfwousP+23alNLjjKfY8THkARnnuQJMpshLSlWPvr zPmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=0nPpmF2p4MU2QXdOVCMRSYE/oa+6TAE8/YkpvsMzLGI=; b=vz/pvpwXxSZ+GB8H6OP8P8//LJ7t+XhZoyH+/uVURzYikgGjGs8BVn7WvWwFrIBQ3m vFlWjtO+lQlPiHxNYFOwRjS94Z7B8TCs66jQJU/9Er9+7ixB7wLQFG5wotOxuNaM3TVY RtkUdj0YJZz+Z3nCczFCE5L2OdCjs5kERg5Qgr3w804drT24AuvZVZTdcG0KeSGXdZy6 S015cdHsJLpEkwqrA2n+U3xOBGcCXV9+1FdoppCF6nQQEaWAt0oCjgRPJ3JxxCh+xCdi nevf4TmigTji6LAoaTJaoHxI5cHj+gXZ5dS64Ee5xrRMxH9I0kFpGprakRgKpfFqOBE5 dDUg==
X-Gm-Message-State: ACrzQf2auzA+eNba7j6M/VEi5nU6eTpkDbI/2QRhTdaQG0Kz7UvH//5q aZWLutKiujqDGVP1/d6soFecAOpJAGmVhJSaEClAbAdE2yoU/A==
X-Google-Smtp-Source: AMsMyM5WKKuFbqt/S9UV77Pk+OUSzvnazSnttD/FKjnozVYwq5NscM5TUPPSxEiGCkOxhCkXArwdpJV95PcjVtLN4DQ=
X-Received: by 2002:a05:6e02:15c9:b0:2e1:a5b6:7e25 with SMTP id q9-20020a056e0215c900b002e1a5b67e25mr6743262ilu.185.1666210456998; Wed, 19 Oct 2022 13:14:16 -0700 (PDT)
MIME-Version: 1.0
References: <166620948548.40913.9820980135582975290@ietfa.amsl.com>
In-Reply-To: <166620948548.40913.9820980135582975290@ietfa.amsl.com>
From: Ben Schwartz <bemasc@google.com>
Date: Wed, 19 Oct 2022 16:14:03 -0400
Message-ID: <CAHbrMsDWTexrdKuzYeG7_RBXE2TLUMxT5gmA+GWT+x=cdsDmrw@mail.gmail.com>
To: ohai@ietf.org, privacy-pass@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="00000000000070695a05eb68dada"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohai/LWcb66l98qjvWwVCYhkKTu17J7w>
Subject: [Ohai] Fwd: New Version Notification for draft-schwartz-ohai-consistency-doublecheck-03.txt
X-BeenThere: ohai@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 19 Oct 2022 20:16:50 -0000

Hello OHAI and PRIVACYPASS,

This revision of the DoubleCheck draft makes extensive changes based on
feedback from the last session and subsequent discussions:

* The draft no longer has a normative dependency on
draft-schwartz-masque-access-descriptions or OHTTP.
* The draft no longer recommends CONNECT-UDP over CONNECT.
* The "MUST" requirement to provide and use a transport proxy has been
reduced to SHOULD, with explanation about the risks if one is not used.
* The introduction has been expanded to describe how this procedure might
be useful for both OHTTP and Privacy Pass.
* The example (Section 5) has been adjusted to make use of
draft-pauly-ohai-svcb-config.
* The draft introduces its own capitalized terminology for the three
parties, similar to OHTTP and Privacy Pass.

The protocol itself has not changed since the previous revision.

I would like to present this revision at IETF 115 if possible.

Good topics for feedback:

* Is this bending HTTP Cache-Control semantics too far?
* Is there any way to solve the Thundering Herd problem (Section 6.2) using
only HTTP caching directives?
* Which working group would be best to discuss this?

--Ben Schwartz

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Wed, Oct 19, 2022 at 3:58 PM
Subject: New Version Notification for
draft-schwartz-ohai-consistency-doublecheck-03.txt
To: Benjamin M. Schwartz <bemasc@google.com>



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

Name:           draft-schwartz-ohai-consistency-doublecheck
Revision:       03
Title:          Key Consistency by Double-Checking via a Semi-Trusted Proxy
Document date:  2022-10-19
Group:          Individual Submission
Pages:          15
URL:
https://www.ietf.org/archive/id/draft-schwartz-ohai-consistency-doublecheck-03.txt
Status:
https://datatracker.ietf.org/doc/draft-schwartz-ohai-consistency-doublecheck/
Html:           https://www.ietf.org/archive/id/draft-schwartzAs the draft
is more general-ohai-consistency-doublecheck-03.html
<https://www.ietf.org/archive/id/draft-schwartz-ohai-consistency-doublecheck-03.html>
Htmlized:
https://datatracker.ietf.org/doc/html/draft-schwartz-ohai-consistency-doublecheck
Diff:
https://www.ietf.org/rfcdiff?url2=draft-schwartz-ohai-consistency-doublecheck-03

Abstract:
   Several recent IETF privacy protocols require clients to acquire
   bootstrap information for a service in a way that guarantees both
   authenticity and consistency, e.g., encrypting to the same key as
   many other users.  This specification defines a procedure for
   transferring arbitrary HTTP resources in a manner that provides these
   guarantees.  The procedure relies on access to a semi-trusted HTTP
   proxy, under the same security assumptions as an Oblivious HTTP
   Relay.




The IETF Secretariat