IETF Logo Mail Archive

Re: [Privacy-pass] Updated WG charter text

Benjamin Kaduk <kaduk@mit.edu> Thu, 23 April 2020 01:46 UTC

Return-Path: <kaduk@mit.edu>
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 B919A3A1077 for <privacy-pass@ietfa.amsl.com>; Wed, 22 Apr 2020 18:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 FE4sVEKSt6o9 for <privacy-pass@ietfa.amsl.com>; Wed, 22 Apr 2020 18:46:54 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 9C4A43A1073 for <privacy-pass@ietf.org>; Wed, 22 Apr 2020 18:46:54 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 03N1koca006780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 22 Apr 2020 21:46:52 -0400
Date: Wed, 22 Apr 2020 18:46:50 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Martin Thomson <mt@lowentropy.net>
Cc: privacy-pass@ietf.org
Message-ID: <20200423014650.GJ27494@kduck.mit.edu>
References: <40600024-A6F1-41D7-B7A8-4B4D7D48201B@cloudflare.com> <4239f287-9a96-4700-ac32-8583ca451115@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4239f287-9a96-4700-ac32-8583ca451115@www.fastmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/privacy-pass/eRoZufow7IceYeYiC14M9AG4ZQo>
Subject: Re: [Privacy-pass] Updated WG charter text
X-BeenThere: privacy-pass@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Thu, 23 Apr 2020 01:46:56 -0000

On Thu, Apr 23, 2020 at 10:32:18AM +1000, Martin Thomson wrote:
> 
> > 4. Describing verification mechanisms for sanctioning or trusting
> >  Issuers and their corresponding keying material.
> 
> Sanctioning implies punishment, which we can't write a protocol for.

I'm pretty sure this was intended in the "give official permission or
approval for" sense, not the "impose a santction on" sense ... but the
ambiguity is not worth keeping around; we should reword.

-Ben

v2.23.0 | Report a Bug | By Email