Re: [hrpc] HRPC recharter

Mallory Knodel <mknodel@cdt.org> Thu, 05 January 2023 14:59 UTC

Return-Path: <mknodel@cdt.org>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C15C1516E1 for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 06:59:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 UmylWRlbu48I for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 06:59:52 -0800 (PST)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 75486C1526FA for <hrpc@irtf.org>; Thu, 5 Jan 2023 06:59:29 -0800 (PST)
Received: by mail-vs1-xe31.google.com with SMTP id i10so16663220vsr.12 for <hrpc@irtf.org>; Thu, 05 Jan 2023 06:59:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=HSwAs5Ml0xXVfSAJe8547btiawkcmGiuPlrosm9Clg8=; b=YEGTL9VgSmXSLAHv8ekXQKzJBaMIYAjfPZiYAn8mQipO8OkMxqC/Z25I0XbpX93Ilw uDfATfNbP3PLX5z4xhl9QNj5vySRIv9yLYpaWsNw5STjx2RweGVZf7vWSKHZvP0iadGk zi4ajU57wgX7Y2Somcf5W/r5i9wi9PFWykhuk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=HSwAs5Ml0xXVfSAJe8547btiawkcmGiuPlrosm9Clg8=; b=2f9d5xBWP5AFSguk9CI9VDECpEnPTx/oDEQ3DY1XLzxlZo/HEP6VB4UO8fxbmNAIM/ uMazCT11ZoTXY45rk8H+NFOa9d4P2y8lp9Socvn9jgfpWVQNkX8CkdxhdIJ67i9pvRpG 7RCGEUZuli0M8ppm4NNxIau2yXuEd5vONoSOM+YlHLklWX6CCwRqf9lRL+CoSH05YztL tjX8qTYy4j98kOirhkmp7Mpkl3nrOqqDb4Cv7UZAoSkSLNmmlrqsL7WBAb+aJs7YSp8S /47EdFIH3STztAP6gP6GF40ZX8cE5Gkyv86vW5nMDXwGu5vnBCj6zeYVA4rrQcZLYzO7 VK+w==
X-Gm-Message-State: AFqh2kol+Ez5zZQV3pwRRAS+BQkpUAd2paT7dfNpWHfS7SBA8F9Reo1Y Volk/2xqFIhvvMox/G8sv6YczxuIBjahFA9X
X-Google-Smtp-Source: AMrXdXtzay5xgvER6V5/RVL29G+qdW5GNLeIkpCAshhsG/I/RlxzPKei16Gv5sAIZD+2odU15mzYxA==
X-Received: by 2002:a05:6102:e83:b0:3cc:4469:1106 with SMTP id l3-20020a0561020e8300b003cc44691106mr15666780vst.21.1672930768099; Thu, 05 Jan 2023 06:59:28 -0800 (PST)
Received: from ?IPV6:2603:3003:360f:f700:8881:64c2:d858:9e61? ([2603:3003:360f:f700:8881:64c2:d858:9e61]) by smtp.gmail.com with ESMTPSA id h17-20020a05620a401100b006fa9d101775sm26526085qko.33.2023.01.05.06.59.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 05 Jan 2023 06:59:27 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------a10XKn8ENXbqhuuKF1wpd9WJ"
Message-ID: <ff338456-b2b5-0eec-f18f-be81ef1afe99@cdt.org>
Date: Thu, 05 Jan 2023 09:59:24 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:106.0) Gecko/20100101 Thunderbird/106.0
Content-Language: en-US
To: Eric Rescorla <ekr@rtfm.com>
Cc: Hrpc <hrpc@irtf.org>
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <CABcZeBO-kN+KmNcGuiAxv5ZidvuZW5A5yjB2mP_ZJCiF1qNLyg@mail.gmail.com> <f727a6c8-7f1e-0db8-46d0-36248b921b79@cdt.org> <CABcZeBPuGUXcAo6z+uSCn=99ct7ALxOP8aQHYX+ncViLitMciw@mail.gmail.com>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <CABcZeBPuGUXcAo6z+uSCn=99ct7ALxOP8aQHYX+ncViLitMciw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/itYJQ2_jppKBA5p3nQfx97FKqGE>
Subject: Re: [hrpc] HRPC recharter
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: hrpc discussion list <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jan 2023 14:59:56 -0000

Hi,

On 1/4/23 4:17 PM, Eric Rescorla wrote:
>
>     I see that the proposed charter revises this bullet somewhat to remove
>     the comparison to 6973, but I think it would be good to be clearer in
>     the charter that the intent for the HRPC is not to be some
>     human-rights flavored version of secdir or opsdir. In particular, if
>     guidelines for how to design protocols so that they protect human
>     rights are to have any normative force, they need to come out of the
>     IETF, not the IRTF. And if the intent is to provide something
>     informative, then I think what's needed is something much more like an
>     analysis of problems and a catalog of techniques than guidelines. This
>     is, for instance, what PEARG does.
>
...
>
>     And alternatively if you can point to a place in the charter where
>     this sort of thing appears and is described better than what we have?
>
> I'm sorry,  I don't think I understand that question.

In an effort to keep this conversation specific to the charter text, I 
am wondering if you feel that PEARG's success in analysis of problems 
and a catalog of techniques lies in the way it's charter is written on 
these points? Because this is what I'm seeing in their charter:

> Provide a forum for discussion and analysis of the cryptographic and 
> practical aspects of privacy protocols e.g.
> Analyse dependencies between protocols in the larger Internet 
> ecosystem and understand the privacy implications in a wider context
> Understand why some protocol design efforts have succeeded and other 
> have not
> Formulate better models for analyzing and quantifying privacy risks
> Offer guidance on the use of emerging techniques and new uses of 
> existing ones. 
It does not in fact look that different than ours. I think that 
execution and interest in bringing research to HRPC is what we need to 
focus on to fix much of what is being raised in the conversation, not 
necessarily charter text.

-Mallory

-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780