Re: [Privacy-pass] The PRIVACYPASS WG has placed draft-group-privacypass-consistency-mirror in state "Candidate for WG Adoption"
Watson Ladd <watsonbladd@gmail.com> Tue, 09 January 2024 01:16 UTC
Return-Path: <watsonbladd@gmail.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 847ECC06F691; Mon, 8 Jan 2024 17:16:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, 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] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 L_2y8uA3j_0f; Mon, 8 Jan 2024 17:16:35 -0800 (PST)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 A3073C06F6B5; Mon, 8 Jan 2024 17:16:35 -0800 (PST)
Received: by mail-wr1-x434.google.com with SMTP id ffacd0b85a97d-336dcebcdb9so2597687f8f.1; Mon, 08 Jan 2024 17:16:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704762993; x=1705367793; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=q36QFgzV6OlqPjdV9YUl9VlPA6JXP1w21F1JvWnJjfQ=; b=hAZdVlzcg2wq+Ffd0gz/UfEbgcGUPJ+ffgV1PMMtzGykJtZDDOlCG0MkpzD14o8COR 8cuveasIsPej+pyNS0MUp7E9TLSqMl6oxQlaK7QUtr25h3PwZqvE9ZITv9Mah3KKi1nM /lyMtBo5j0XHXt7Pqyia+Yq6nCYgZR3Bt8ikE63oVzN8eQ41gid2Fl7yXHiRCHt74tc3 +teFz2JXYpbNm1hYtTIquZfstGaupIX+i6ovOFOS6/E+A6Rv39Yaz0MLFkELzLZ2UaS3 2XSSDtvE+EHMpPFB+4Ja78+F13Fqe1v/blfEM7HBvDNUfwKL1nrxfRsXFjlspB8+ooV/ wXdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704762993; x=1705367793; h=content-transfer-encoding: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=q36QFgzV6OlqPjdV9YUl9VlPA6JXP1w21F1JvWnJjfQ=; b=JoA/rQK/xf34liTznt95evMf4CT/4RuqRs2ZX7XnH+SAqmJQzv+suNXgdDtvhQv+0t WzCPey3sMZRrHqAX7eWVdQxxMqKHHTFyy7uQJeM8G4lZcbZsgYlLrKDeR7d2z0e+zqVY mNkQdbr8lTP4W3NBp9b1t2zmEnPmW+ayRct6iq3gLqHOSipyL4l6dnorArqIc8gXWZ+w dBpleaJZF8An6R2CzSAyEnxEEeCdicLMx4MDyLLNqq8+vLAcrzmKV3vVc/glBVRt2sT6 V4/BX8w37AspVTEE3HOsYt6KfL0aiG8x8xSWiumxQlB0UU2oXtmSVizVZooYorKZts75 aSKA==
X-Gm-Message-State: AOJu0Yx09oIhCsdi8hqYA7xDUwd9CaneOC6wGXHJ5hIhcI+aYGzKFjDc OpD2hdjPlTHKZeEuEveQdzuJ8V7n+ep5sw34l23NPpTojNY=
X-Google-Smtp-Source: AGHT+IErCiDmwGa0kBPpB+6ENHLIMuY71C8hNrqqaCd+fz+2p0AiC8G1GqQSN2m78cqO+aP/GceS/2g9gVE/S/6POUo=
X-Received: by 2002:adf:eb04:0:b0:336:8080:1d61 with SMTP id s4-20020adfeb04000000b0033680801d61mr81189wrn.58.1704762992712; Mon, 08 Jan 2024 17:16:32 -0800 (PST)
MIME-Version: 1.0
References: <170137846545.34849.17139555973021303518@ietfa.amsl.com> <BN8PR15MB32811657C0AEC39E213E8798B382A@BN8PR15MB3281.namprd15.prod.outlook.com>
In-Reply-To: <BN8PR15MB32811657C0AEC39E213E8798B382A@BN8PR15MB3281.namprd15.prod.outlook.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Mon, 08 Jan 2024 17:16:21 -0800
Message-ID: <CACsn0cmsKAS-UZa2_oBkF+SeSVEkmQDQAWN2+-F4AsaX0HJOzg@mail.gmail.com>
To: Ben Schwartz <bemasc=40meta.com@dmarc.ietf.org>
Cc: IETF Secretariat <ietf-secretariat-reply@ietf.org>, "draft-group-privacypass-consistency-mirror@ietf.org" <draft-group-privacypass-consistency-mirror@ietf.org>, "privacy-pass@ietf.org" <privacy-pass@ietf.org>, "privacypass-chairs@ietf.org" <privacypass-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/privacy-pass/T6ut-dS5CMp5qwq0O1wtzbNgIiU>
Subject: Re: [Privacy-pass] The PRIVACYPASS WG has placed draft-group-privacypass-consistency-mirror in state "Candidate for WG Adoption"
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: Tue, 09 Jan 2024 01:16:39 -0000
Apologies for the late reply. It seems that this is a fine instantiation of a pull based model, and that's what the underlying draft-ietf-privacypass-key-consistency discusses in its architecture. I do wonder if a push or polling based model akin to e.g. Usenet might be a better fit for a consistent broadcast medium. If we do think the pull based model is what's needed, then we should adopt. On Thu, Nov 30, 2023 at 1:39 PM Ben Schwartz <bemasc=40meta.com@dmarc.ietf.org> wrote: > > We are opening a two-week Call for Adoption (ending Friday, December 15th) for "Checking Resource Consistency with HTTP Mirrors". > > Please comment in this thread with your view as to whether this document should be adopted by the PRIVACYPASS working group. > > --Ben Schwartz, for the chairs. > ________________________________ > From: Privacy-pass <privacy-pass-bounces@ietf.org> on behalf of IETF Secretariat <ietf-secretariat-reply@ietf.org> > Sent: Thursday, November 30, 2023 4:07 PM > To: draft-group-privacypass-consistency-mirror@ietf.org <draft-group-privacypass-consistency-mirror@ietf.org>; privacy-pass@ietf.org <privacy-pass@ietf.org>; privacypass-chairs@ietf.org <privacypass-chairs@ietf.org> > Subject: [Privacy-pass] The PRIVACYPASS WG has placed draft-group-privacypass-consistency-mirror in state "Candidate for WG Adoption" > > !-------------------------------------------------------------------| > This Message Is From an External Sender > > |-------------------------------------------------------------------! > > > The PRIVACYPASS WG has placed draft-group-privacypass-consistency-mirror in > state Candidate for WG Adoption (entered by Benjamin Schwartz) > > The document is available at > https://datatracker.ietf.org/doc/draft-group-privacypass-consistency-mirror/ > > > -- > Privacy-pass mailing list > Privacy-pass@ietf.org > https://www.ietf.org/mailman/listinfo/privacy-pass > -- > Privacy-pass mailing list > Privacy-pass@ietf.org > https://www.ietf.org/mailman/listinfo/privacy-pass -- Astra mortemque praestare gradatim
- [Privacy-pass] The PRIVACYPASS WG has placed draf… IETF Secretariat
- Re: [Privacy-pass] The PRIVACYPASS WG has placed … Ben Schwartz
- Re: [Privacy-pass] The PRIVACYPASS WG has placed … Thibault Meunier
- Re: [Privacy-pass] The PRIVACYPASS WG has placed … Eric Rosenberg
- Re: [Privacy-pass] The PRIVACYPASS WG has placed … Christopher Wood
- Re: [Privacy-pass] The PRIVACYPASS WG has placed … Watson Ladd
- Re: [Privacy-pass] The PRIVACYPASS WG has placed … Martin Thomson