IETF Logo Mail Archive

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

Tommy Pauly <tpauly@apple.com> Mon, 26 September 2022 20:49 UTC

Return-Path: <tpauly@apple.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 DD33AC14CF03 for <privacy-pass@ietfa.amsl.com>; Mon, 26 Sep 2022 13:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.667
X-Spam-Level:
X-Spam-Status: No, score=-2.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 uFbOGJ5PARc0 for <privacy-pass@ietfa.amsl.com>; Mon, 26 Sep 2022 13:49:14 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp45.apple.com (rn-mailsvcp-ppex-lapp45.rno.apple.com [17.179.253.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CC7CC14F73E for <privacy-pass@ietf.org>; Mon, 26 Sep 2022 13:49:14 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp45.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp45.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 28QKfBng012771; Mon, 26 Sep 2022 13:49:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=5e6PXnE9T5WrqyKa8zkEDTkDLtwWWMPfXsIgZGwLps4=; b=Ea8J/5AK3RCs5OQFxp1i9z64H/nU5De0jQc0IuW88o02kDt0LC+bcjMd+z0BuP+VwlTJ dKDGE1Sa7ucWqcbP1qywm9BoZsnbKylxOIGwZ52+oGzxCrp914bCog5y1Uu29u5+B2fq 28VypLmp0Pm52HDSCAn6yNcP4/RQh6OJd2fBLR4zcIotwFy3szv2RyAhDArN1qmE0bwP iQvKNYN0CMa/krwxrtuDNBkcjSKEQ7ZRFUNb6PsJy7zR6Kj20c4mrh1zhjxcOScXWrqD a4sdpA+wYitnpRSVAaTt0vS98Cib+2YSoz0Qi+1oBU6O6CwV0RYNnZVnV43xpzi4xYbS HA==
Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by rn-mailsvcp-ppex-lapp45.rno.apple.com with ESMTP id 3jt06rufns-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 26 Sep 2022 13:49:12 -0700
Received: from rn-mailsvcp-mmp-lapp01.rno.apple.com (rn-mailsvcp-mmp-lapp01.rno.apple.com [17.179.253.14]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.19.20220711 64bit (built Jul 11 2022)) with ESMTPS id <0RIU004EW4HZ8MB0@rn-mailsvcp-mta-lapp01.rno.apple.com>; Mon, 26 Sep 2022 13:49:12 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp01.rno.apple.com by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.19.20220711 64bit (built Jul 11 2022)) id <0RIU002004FOIQ00@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Mon, 26 Sep 2022 13:49:12 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 743daa564def5b9040e57c2f274ad80f
X-Va-E-CD: b1982c4ee0c210eace443be4b2ad67b2
X-Va-R-CD: f5822bc24b9604623c1bd3303d0b9709
X-Va-CD: 0
X-Va-ID: 3c93af4b-1a85-4318-a32d-59a423c2e58d
X-V-A:
X-V-T-CD: 743daa564def5b9040e57c2f274ad80f
X-V-E-CD: b1982c4ee0c210eace443be4b2ad67b2
X-V-R-CD: f5822bc24b9604623c1bd3303d0b9709
X-V-CD: 0
X-V-ID: 87c0e36e-16d6-49dd-8335-d2f81c3b848e
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.528, 18.0.895 definitions=2022-09-26_09:2022-09-22, 2022-09-26 signatures=0
Received: from smtpclient.apple (unknown [17.234.123.19]) by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.19.20220711 64bit (built Jul 11 2022)) with ESMTPSA id <0RIU00FDN4HYA900@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Mon, 26 Sep 2022 13:49:11 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <88FDCAC8-68A4-4209-A5ED-CDC1F3ECAE0F@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_52C77FDF-F95E-4295-8F0E-0A2E6CCAA4F6"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3730.0.21\))
Date: Mon, 26 Sep 2022 13:48:59 -0700
In-reply-to: <CAOgPGoBwcokG5OEpgyxDMwoQ=eCvGCWtnu8ZBZWxdJqTCoWoeQ@mail.gmail.com>
Cc: privacy-pass@ietf.org
To: Joseph Salowey <joe@salowey.net>
References: <CAOgPGoBwcokG5OEpgyxDMwoQ=eCvGCWtnu8ZBZWxdJqTCoWoeQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3730.0.21)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.528, 18.0.895 definitions=2022-09-26_09:2022-09-22, 2022-09-26 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/privacy-pass/S7wIHvc36f1ZkICyZ_KLd49bZys>
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: Mon, 26 Sep 2022 20:49:15 -0000

I think this is useful work, and important discussion to have in this working group. To that end, I support adoption.

I have a bit of a broad question as to the specific venue for the work, since the document explicitly has relevance for PRIVACYPASS and OHAI (and could apply to other protocols). If we do this here, we would of course want cross-group discussion. Is there a rationale for one or the other? I also note that draft-schwartz-ohai-consistency-doublecheck is targeted at OHAI, and it really seems like these efforts should be in the same place. I’m also of the opinion that the double-checking technique could be merged into draft-wood-key-consistency overall.

Thanks,
Tommy

> On Sep 18, 2022, at 12:42 PM, Joseph Salowey <joe@salowey.net> wrote:
> 
> This is a call for adoption of the Key Consistency and Discovery Draft - draft-wood-key-consistency-03 [1]. Please respond to the list and indicate if you think the PrivacyPass working group should adopt this work or not.  Also please indicate if you are willing to contribute text or review the document. The call will end on October 6, 2022.
> 
> Thanks,
> 
> Ben and Joe
> 
> [1] https://datatracker.ietf.org/doc/draft-wood-key-consistency/
> -- 
> Privacy-pass mailing list
> Privacy-pass@ietf.org
> https://www.ietf.org/mailman/listinfo/privacy-pass

v2.23.0 | Report a Bug | By Email