Re: [Privacy-pass] Call for Adoption of Key Consistency and Discovery Draft
Eric Orth <ericorth@google.com> Wed, 05 October 2022 22:17 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 ED0F4C1522A6 for <privacy-pass@ietfa.amsl.com>; Wed, 5 Oct 2022 15:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.606
X-Spam-Level:
X-Spam-Status: No, score=-17.606 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_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=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 UJOgao4C3NQD for <privacy-pass@ietfa.amsl.com>; Wed, 5 Oct 2022 15:17:36 -0700 (PDT)
Received: from mail-oa1-x29.google.com (mail-oa1-x29.google.com [IPv6:2001:4860:4864:20::29]) (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 254ECC1522A2 for <privacy-pass@ietf.org>; Wed, 5 Oct 2022 15:17:36 -0700 (PDT)
Received: by mail-oa1-x29.google.com with SMTP id 586e51a60fabf-132fb4fd495so232016fac.12 for <privacy-pass@ietf.org>; Wed, 05 Oct 2022 15:17:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=SJYogVywPaPjhut1403k3XPbiGDpa+YvrIFqGtvcoWI=; b=LrYA7+wosauKH1ivbHq2Z2n7rgIhTHNv0kfxL4oj9RCIc1AJjlPqGaXKwvP4fwDzBI 0EwWfYyNsfB1Hshl/KtZ5sG8M16DIbtHKLoYgo9zBoxQTHocmhvU9fqLvhHkrwouTXf6 1G5TjZnF6yQohxiQAgoWMAs+Rkc4Y/WykDh3Th0iC9tZzNkgNmcMAwBgeOCZ/aphxlaQ HlfZNMmbQqLnaRPxjnZQ+gIHVfAzj0IuGRIIlnf/6R4FXBi5b2dhcqXXZ7C8mrYwRzzt rmo/HaDGr7w1pVpJPr8AHtVaQ6+A7ahKuSRCuXOCh0ARcEcKaSoZRbDQ5X8d77QB4q4R EHKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=SJYogVywPaPjhut1403k3XPbiGDpa+YvrIFqGtvcoWI=; b=yQxlSLoSVKSqlY6EJ7phUZD0QCqYc1vMERXQ4JBy3BNy9JEn+SjyqKc+FlQvKLk23k CH2H7goKcKVSrw02f8zLUUpzRReIT8jDMTzlwYse3VEkbPJE8b1Gq1IbbNL1Z6TpS1/c rP4tVh+Rv+izf/0p+08LNgdSpj27wHb/39k4uUZgCdrAiok+dIkn/L2X5FTxvYQOkN+S Tq14hLSmEei8bDCnr4OR7g2T1pATWasCSWvRge1ks5DSYBmYDNGmiUfIldF1Kgp+wVYn ZIk9QwHhysAl9s5MfnjB6aWcEeS0uTMWuonxssKB3PA86BsaLJxsPzPbX250LYYAl07w peDw==
X-Gm-Message-State: ACrzQf2TAMFvWUC0SDsnJMq7fpAwnosYXbPMjIVVrDGAxdvXcfEYlKZP x7V1+u1TPk/7Xv2j2PVoCGqk0hjFdspS3CmPrW00qlERB3MUUQ==
X-Google-Smtp-Source: AMsMyM6xahLnEhBqnEGKccdbEasIYC0vM33Xfr7b3lF4NueUSFngAMOOO6/LmzIOrJLT6n49NogCanowOFVLRWw53Rg=
X-Received: by 2002:a05:6870:d607:b0:132:7c31:1bc9 with SMTP id a7-20020a056870d60700b001327c311bc9mr936652oaq.131.1665008254970; Wed, 05 Oct 2022 15:17:34 -0700 (PDT)
MIME-Version: 1.0
From: Eric Orth <ericorth@google.com>
Date: Wed, 05 Oct 2022 18:17:24 -0400
Message-ID: <CAMOjQcH6n=DzX0Mh-ufLJ9srqxP+zt6kuQgrjYs4mic6K6Wg=g@mail.gmail.com>
To: privacy-pass@ietf.org, tpauly@apple.com
Content-Type: multipart/alternative; boundary="00000000000096331205ea50f1e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/privacy-pass/bgc3StTbLhNv1rePxQBwu8iswAg>
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:17:40 -0000
I think this is an important draft, useful for a couple different protocols, and I support adoption. On Mon, 26 September 2022 20:49 UTC, Tommy Pauly <tpauly@apple.com> wrote: > 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. Overall, I agree. We should pick one WG (PRIVACYPASS seems fine), unless somebody can think of a better, more general WG, and adopt all such consistency drafts there. 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’m also of the opinion that the double-checking technique could be merged > into draft-wood-key-consistency overall. > If you mean add a general description of techniques more similar to the double-checking technique, I agree. If you mean merge the two drafts completely, I disagree. One is an informational draft with a general overview of possible techniques. The other is a standards draft laying out a specific protocol to implement a specific technique. They should stay separate, and I believe having both drafts would be very valuable. Although there's probably good room for both drafts to do more to reference the other. > > 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 >
- [Privacy-pass] Call for Adoption of Key Consisten… Joseph Salowey
- Re: [Privacy-pass] Call for Adoption of Key Consi… Tommy Pauly
- Re: [Privacy-pass] Call for Adoption of Key Consi… Ben Schwartz
- Re: [Privacy-pass] Call for Adoption of Key Consi… Christopher Wood
- Re: [Privacy-pass] Call for Adoption of Key Consi… Eric Orth
- Re: [Privacy-pass] Call for Adoption of Key Consi… Ben Schwartz
- Re: [Privacy-pass] Call for Adoption of Key Consi… Eric Orth
- Re: [Privacy-pass] Call for Adoption of Key Consi… Tommy Pauly
- Re: [Privacy-pass] Call for Adoption of Key Consi… Martin Thomson
- Re: [Privacy-pass] Call for Adoption of Key Consi… Tommy Pauly
- Re: [Privacy-pass] Call for Adoption of Key Consi… Christopher Wood
- Re: [Privacy-pass] Call for Adoption of Key Consi… Raphael Robert
- Re: [Privacy-pass] Call for Adoption of Key Consi… Eric Orth
- Re: [Privacy-pass] Call for Adoption of Key Consi… Scott Hendrickson
- Re: [Privacy-pass] Call for Adoption of Key Consi… Ben Schwartz