
From nobody Thu Jun  3 07:07:47 2021
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 44F733A12F8 for <hrpc@ietfa.amsl.com>; Thu,  3 Jun 2021 07:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yEFuu4dG4l53 for <hrpc@ietfa.amsl.com>; Thu,  3 Jun 2021 07:07:39 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D6423A1302 for <hrpc@irtf.org>; Thu,  3 Jun 2021 07:07:34 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id u30so5991531qke.7 for <hrpc@irtf.org>; Thu, 03 Jun 2021 07:07:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language :from:to:references:in-reply-to:content-transfer-encoding; bh=CR60X/sQVOQE5Jl05Urxe6KjF57UU0K6WJ0JvfGRNSA=; b=S2HPxH2oNMJ09lBA4rVanVdLUvmf94iZBi7/4yXwt6UkvQ4A6k73CIjp9J7m9l9HBV n6GtqrDaUCC173DFEAawF0OVhFPpifBMpScXcOuW3dDxD1v/1Tvq92MjH9ZE53J53Yju 7Y4FNUlf0nosCqn6PuL9kDeK45xnHiG3f3vJc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:references:in-reply-to :content-transfer-encoding; bh=CR60X/sQVOQE5Jl05Urxe6KjF57UU0K6WJ0JvfGRNSA=; b=KsirRvOO95RsXp8NH2fvn127UHZXnbVYpwe1keIevTcDMIMAuTjHnJpuMwb/nVmT17 oXMIfovAMhkEjVr/MVKA0aGOuwH26+SZNHDcyhLWYdpnikkT6mL9749uqo4+QuLhOG5f 1v+7te8B7nMyZHyUA6mUSrN3M9dqeruo7gyF18Hb9JSQmeoMfz3ud6GLNqDM8n2DXqhv DLJON0izJfuw4E6hRw186T+3OP25YyT5yT4KCIFYETi4UBAxwHS/4epW27GaBHOY8eYV ph5k4yMj2IDe+kxBq9uHcVa+dw+JAqQqPkNwJdZgMvkcWW626NpP42OMcz/4ezaBdcPa 4apg==
X-Gm-Message-State: AOAM532b8J1E+sDGHJ/iJabxcoB48Z73wCYJZ7ePpqPjtpoD1PSUGtI8 UGSLj94XPcQYxhTsTu4LQUMpf137vMytjsdZ
X-Google-Smtp-Source: ABdhPJwQUmyv8bSbvZpOtmjNRx9JgTD/WL+PmtrYHM3J8rTBvt/x/nINuEUxYN7A+4tQX4f0q+Xeng==
X-Received: by 2002:a05:620a:13c4:: with SMTP id g4mr32244939qkl.256.1622729252291;  Thu, 03 Jun 2021 07:07:32 -0700 (PDT)
Received: from [192.168.0.130] (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with UTF8SMTPSA id o5sm1950377qkl.25.2021.06.03.07.07.31 for <hrpc@irtf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Jun 2021 07:07:31 -0700 (PDT)
Message-ID: <f7172f3c-71b3-f30c-e05c-61d8f9b8da8e@cdt.org>
Date: Thu, 3 Jun 2021 10:07:30 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:89.0) Gecko/20100101 Thunderbird/89.0
Content-Language: en-US
From: Mallory Knodel <mknodel@cdt.org>
To: Hrpc <hrpc@irtf.org>
References: <b53cf50e-855b-45d3-44af-e0d024e27775@cdt.org>
In-Reply-To: <b53cf50e-855b-45d3-44af-e0d024e27775@cdt.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/3opgyvd4ifPWAr9AoPzCMYGP1KU>
Subject: Re: [hrpc] Working group last call for draft-irtf-hrpc-guidelines
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
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, 03 Jun 2021 14:07:44 -0000

Hi all,

The LC has ended. Thanks to those who commented both on and off list. I 
checked in with the authors this week and they plan to have an updated 
version very soon, based on the feedback, as well as responses to the 
list as appropriate.

-Mallory

On 5/19/21 11:21 AM, Mallory Knodel wrote:
> Hi all,
>
> We are starting a two-week last call in HRPC on the 'Guidelines for 
> Human Rights Protocol and Architecture Considerations' draft as an 
> informational RFC of the IRTF. The draft is available at
>
> https://datatracker.ietf.org/doc/draft-irtf-hrpc-guidelines.
>
> All comments, suggestions and support for advancing this document 
> should be directed as a reply to this message in the HRPC mailing 
> list. Copy edits don't need discussion but would be welcomed by the 
> authors, Gurshabad and Niels, at
>
> draft-irtf-hrpc-guidelines@ietf.org.
>
> Last call concludes on 2 June 2021, COB.
>
> Thank you!
> -Mallory
> -- 
> Mallory Knodel
> CTO, Center for Democracy and Technology
> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780

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


From nobody Fri Jun 25 09:15:58 2021
Return-Path: <session-request@ietf.org>
X-Original-To: hrpc@irtf.org
Delivered-To: hrpc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7983A083D; Fri, 25 Jun 2021 09:15:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: hrpc-chairs@ietf.org, hrpc@irtf.org, irtf-chair@irtf.org, lflynn@amsl.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162463775549.22007.16817646477611173792@ietfa.amsl.com>
Date: Fri, 25 Jun 2021 09:15:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/XBL_nX6B0EzbG7UOL_hMnPbAYtU>
Subject: [hrpc] hrpc - Update to a Meeting Session Request for IETF 111
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
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: Fri, 25 Jun 2021 16:15:56 -0000

An update to a meeting session request has just been submitted by Liz Flynn, on behalf of the hrpc working group.


---------------------------------------------------------
Working Group Name: Human Rights Protocol Considerations
Area Name: IRTF
Session Requester: Liz Flynn


Number of Sessions: 2
Length of Session(s):  1 Hour, 1 Hour
Number of Attendees: 100
Conflicts to Avoid: 
 Chair Conflict: dprive gaia irtfopen pearg
 Technology Overlap: mls dnsop openpgp
 Key Participant Conflict: lamps gendispatch





People who must be present:
  Avri Doria
  Mallory Knodel

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Fri Jun 25 09:18:27 2021
Return-Path: <session-request@ietf.org>
X-Original-To: hrpc@irtf.org
Delivered-To: hrpc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CAB3A085E; Fri, 25 Jun 2021 09:18:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: hrpc-chairs@ietf.org, hrpc@irtf.org, irtf-chair@irtf.org, lflynn@amsl.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162463790553.31831.17596313452998624370@ietfa.amsl.com>
Date: Fri, 25 Jun 2021 09:18:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ybDFlQWA_LZJURPxLZglLM1vV1E>
Subject: [hrpc] hrpc - Update to a Meeting Session Request for IETF 111
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
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: Fri, 25 Jun 2021 16:18:26 -0000

An update to a meeting session request has just been submitted by Liz Flynn, on behalf of the hrpc working group.


---------------------------------------------------------
Working Group Name: Human Rights Protocol Considerations
Area Name: IRTF
Session Requester: Liz Flynn


Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 100
Conflicts to Avoid: 
 Chair Conflict: dprive gaia irtfopen pearg
 Technology Overlap: mls dnsop openpgp
 Key Participant Conflict: lamps gendispatch





People who must be present:
  Avri Doria
  Mallory Knodel

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Mon Jun 28 07:43:25 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: hrpc@irtf.org
Delivered-To: hrpc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE273A0B04; Mon, 28 Jun 2021 07:43:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: hrpc@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: hrpc@irtf.org
Message-ID: <162489140279.16984.13299770022533633593@ietfa.amsl.com>
Date: Mon, 28 Jun 2021 07:43:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/1LrhyDL6Z0xo9zSKx-6BR7LZJGQ>
Subject: [hrpc] I-D Action: draft-irtf-hrpc-guidelines-09.txt
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
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: Mon, 28 Jun 2021 14:43:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Human Rights Protocol Considerations RG of the IRTF.

        Title           : Guidelines for Human Rights Protocol and Architecture Considerations
        Authors         : Gurshabad Grover
                          Niels ten Oever
	Filename        : draft-irtf-hrpc-guidelines-09.txt
	Pages           : 31
	Date            : 2021-06-28

Abstract:
   This document sets guidelines for human rights considerations for
   developers working on network protocols and architectures, similar to
   the work done on the guidelines for privacy considerations [RFC6973].
   This is an updated version of the guidelines for human rights
   considerations in [RFC8280].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-hrpc-guidelines/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-irtf-hrpc-guidelines-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-irtf-hrpc-guidelines-09


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Jun 28 07:45:39 2021
Return-Path: <gurshabad@cis-india.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 81F963A0B20 for <hrpc@ietfa.amsl.com>; Mon, 28 Jun 2021 07:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 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, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cis-india.org
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 P1MUHLksXqqv for <hrpc@ietfa.amsl.com>; Mon, 28 Jun 2021 07:45:34 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (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 008E23A0B1A for <hrpc@irtf.org>; Mon, 28 Jun 2021 07:45:33 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org 9AFBB580B0016
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1624891522; bh=yeqJIsYh9joJGrgg0phk2Okvxc6w+YyCCaF9w5QT5PY=; h=From:To:Message-ID:Date:MIME-Version; b=u90L8Gz7vxLSElRPMDD0kInzOYQFcv7AiFLqKKJ9nrpy8kpd8Gyh+27QGumEc/zPW abmY/9IRq0H9wRLv7teBRoo6iNPrre6B0x0HDw4MoqDwV6ATA1djduqwAwR2oPP2Pq 5UIDRWMcgd0UF+DCTfmS7kMMZXM0ldTiGS5dhRaGdo336V/g7+/BfD9hGGvGI8rH0H huRRUsHdrzRuzUgM7ObUQqIiEREbGY9uXMTAtiPl+lJLzcYoPnRj4YiMsS7BZaHEd7 Ozmdme0p2ZNaiOFYIyl182oPwMz8T1D4ti85QH+Z9VGk+KCYzHmcWfMzSVn323NPQf Rc+rtf5wwaYAQ==
From: Gurshabad Grover <gurshabad@cis-india.org>
To: Eliot Lear <lear@lear.ch>, Mallory Knodel <mallory@cdt.org>
Cc: "hrpc@irtf.org" <hrpc@irtf.org>
References: <447c4444-800b-dfb9-de3e-bbbe3bb4ac64@lear.ch>
Message-ID: <6b540117-38a6-fbfa-3749-048d14b34f38@cis-india.org>
Date: Mon, 28 Jun 2021 20:15:19 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <447c4444-800b-dfb9-de3e-bbbe3bb4ac64@lear.ch>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Authenticated-As-Hash: 3c8a76879922505f22521320ab57e3bbe25ea7cc
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 8e5288e5c3cb7c234bd65e385d1f5366
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/8foo-CslXnUx4QTfGYJZLPnrsoA>
Subject: Re: [hrpc] Working group last call for draft-irtf-hrpc-guidelines
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
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: Mon, 28 Jun 2021 14:45:39 -0000

Eliot, thanks very much for your review! Replies in-line.

On 5/20/21 5:38 PM, Eliot Lear wrote:
>=20
> For "Impacts"-
>=20
> These impacts are claimed, both here and in 8280, but the linkage isn't
> explicitly made in each case.=C2=A0 Are these linkages made clear somew=
here
> else?=C2=A0 I may have entirely missed it, in which case this issue isn=
't an
> issue at all.=C2=A0 Otherwise, one wonders if we are putting the cart b=
efore
> the horse.
>=20

I think the explanation and examples under each each sub-section of 2.3
are intended to make these links explicit. Are you referring to some
other sort of links between rights and properties of protocols/specs?

> *Somewhere between Minor and Major*
>=20
> Section 2 & 2.2
>=20
> I think there is a slight organizational issue, from a readability
> perspective.
>=20
> It feels to me like 2.1 is really still introductory, and then 2.2 gets
> into what to do, starting with interviews.=C2=A0 It may make sense to m=
ove
> 2.1 up into Section 1,

Good point. Made it into a new section in the recent update.

> and then create a new chapeau in Section 2 that
> shows your preferred work flow.
>=20
> For example:
>=20
> [concept formation] -> [WG discussion] -> [HR expert consultation] ->
> [impacted community consultation]
>=20
> -> [modifications] -> ... -> [implementations] -> [tracing impacts] ->
> [revisions]
>=20
> And there can be while/if loops etc.=C2=A0 A little UML might go a long=
 way here.
>=20
> Section 2.3 should be consulted throughout, under such a model.=C2=A0 Y=
ou
> could even move that into a new H1 section 3.
>=20

As I understand it, we are not proposing an ideal workflow as such. We
are just listing out some assessment frameworks (which may be used
independently or in conjunction with each other).

> A few of the examples seem to me a bit disjoint from the IETF.=C2=A0 I =
think
> we talked about Accessibility at some point, but an example more
> relevant to the IETF might help people grasp the more direct relevance
> to the organization.=C2=A0 I don't have a particularly good example of =
this,
> but there should at least be an existence proof of the relevance to
> us... unless...
>=20
> ... you want the guidance to be broader than just the IETF.=C2=A0 I see
> absolutely nothing wrong with that, but you should scrub the doc then t=
o
> make sure that IETF-specific stuff is generalized.=C2=A0 An example mig=
ht be
> to replace "protocol" with "specification".
>=20

I don't think we're saying this explicitly anywhere, but that's
deliberate. Since IETF is not the only place where protocols are made, I
think that this vagueness is acceptable. Of course, one of the primary
goals for the document remains that it is usable by people at IETF.

That said, I think we were at consensus that the guidelines are not just
relevant to protocols, but specifications (an example at IETF would be
specifications that lay out an architecture but not a protocol) in the
broad area of networking. For instance, I think the group has used the
guidelines to review the MLS architecture and SUIT architecture. Made
some changes to say 'specification' instead of protocol where relevant.

>=20
> Section 2.3.13
>=20
> I don't know that we have *any* real success stories for
> decentralization.=C2=A0 HTTP certainly isn't one.=C2=A0 Certainly desig=
ning
> *toward* centralization might be best, but I don't think we have very
> many examples of that *either.*=C2=A0 Moreover, I have argued, and cont=
inue
> to argue, that some centralization may *facilitate* human rights.=C2=A0=
 If
> you take into account the combination of DOH + cloud, an observer must
> go to far greater lengths to discern even so much as the nature of the
> traffic, much less content and actual endpoint.
>=20
> And this raises another issue: the point of much of cloud services is t=
o
> improve individual service reliability.=C2=A0 And yet those same cloud
> services are a form of centralization.=C2=A0 If you consider that perha=
ps a
> handful of players might force DNS traffic to a limited number of
> resolver services, we might also say that DoH itself presents
> centralization risks.
>=20
> These sorts of conflicts are of course to be expected.=C2=A0 The questi=
on is
> whether it is worth providing guidance relating to centralization.=C2=A0=
 I
> will claim that nobody yet has a real handle in this area, and so bette=
r
> to say nothing in the form of guidance.=C2=A0 Instead, it seems to me t=
o be
> good fodder for future work.
>=20

I don't think I have a strong opinion about this. Before making any
changes in this section, however, I'd love to hear what others think.

> 2.3.17 Authenticity
>=20
> The authors write:
>=20
>>    At the same time, authentication should not be used as a way to
>>    prevent heterogeneity support, as is often done for vendor lock-in =
or
>>    digital rights management.
>=20
> As if that should be the #1 concern.=C2=A0 Perhaps a bigger concern is =
that
> authenticity directly conflicts with anonymity or pseudo-anonymity.=C2=A0=
 If
> someone is forcing you to authenticate, the authentication identity can
> and will be associated with whatever access takes place, and that
> information can be demanded.
>=20
> Furthermore,=C2=A0 I'm not at all sure that the example holds up, and i=
t
> should be at least supported by a current reference.=C2=A0 Finally, the=
re are
> conflicts here as well: the technology that one might use for vendor
> lock-in is=C2=A0 the same as that used to validate the authenticity of
> software, for purposes of preventing malware spread.
>=20
> Also, the question itself is a bit shallow.=C2=A0 Authenticity of what?=
=C2=A0 If
> we are talking about the underlying data, a mere transport connection
> may not in and of itself provide sufficient protection.=C2=A0 We have p=
lenty
> of mail traversing encrypted tunnels and lots of spam to go with.
>=20

I agree that identity authentication can be at odds with
anonymity/pseudonymity, but this section is not about that. I re-read
the text and example in this section, and to me it's clear that it's
more to do with transport/data authenticity than identity
authentication. Would love to hear your thoughts on how we can make this
even clearer if it's cause for confusion.

> *Minor issues:*
>=20
> Beginning with Section 1:
>=20
>>   This is by no means an attempt to exclude specific rights or
>>    prioritize some rights over others.  If other rights seem relevant,
>>    please contact the authors.
>=20
> Are we are sufficiently taking into account how linkages to other right=
s
> might prevail?=C2=A0 Let me give an example:
>=20
> If we are talking about a new version of "whois" that retrieves
> information necessary for law enforcement, the whole point of the
> protocol is to expose information that some would say is private.=C2=A0=
 And
> so the question revolves around whether appropriate protections are in
> place to limit access to that information to authorized parties.=C2=A0
> However, even doing that may not be enough, if "authorized parties" are
> the source of abuse.=C2=A0 I don't know if such an example is an outlie=
r, but
> there it is.
>=20
> Nit: the 2nd sentence will need to be changed or removed.

Removed the second sentence.

Could you please elaborate on what you mean to demonstrate through the
example here (with respect to linkages of rights)?

>=20
> 2.3.12 "Localization"
>=20
> Be advised that this term has distinctly different meanings.=C2=A0 In t=
rade
> parlance it is a barrier to trade through local requirements.[1]=C2=A0 =
A TBT
> can also be viewed as a means to restrict content that isn't translated
> (ie, stuff that censors can read).=C2=A0 I think this might be worth a
> mention, just because they're related and yet potentially conflicting.
>=20

Clarified the definition; it now says exactly what meaning we're using no=
w.

Thanks again for your review, Eliot. Much appreciated.

-Gurshabad



From nobody Mon Jun 28 12:14:11 2021
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 B0FA93A098D for <hrpc@ietfa.amsl.com>; Mon, 28 Jun 2021 12:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nuw-wzXu33UR for <hrpc@ietfa.amsl.com>; Mon, 28 Jun 2021 12:14:06 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 041F63A098E for <hrpc@irtf.org>; Mon, 28 Jun 2021 12:14:05 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id m9so20243185ybo.5 for <hrpc@irtf.org>; Mon, 28 Jun 2021 12:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=diXwfUNHCTHY/+3+4dt2SYLxXIxgroLXzt6U40uC7fQ=; b=Yfav5EGZG6SLGI6SSSeKaIaoE9dAJKnZnoSK8OUvRPrpJccLMNLsoMShI1psk3CtVo krRPDoh9Yy965gxVV9+YkjpQPj5TSFqWDHxiOjn6i4IHSl0LxgJV7CdJ9VgSIIdy5NIE KmvtnMK+2YRIHo8UmsEd3kg1QRZY77+/pgmgs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=diXwfUNHCTHY/+3+4dt2SYLxXIxgroLXzt6U40uC7fQ=; b=WmEzAIH+A6tQ3vXsd3XFN/LZNwllSSwSqIHLd3z4APAyZk81ej2ncY7QXifQANZwmp mCe0BMwDNFJU92m6/MYTDmZJmIUeIMU+rXCFUFrqMax7hLBxhjBoSPPqP/LFqae2w45g O7q1+JRSrw/TDs0fCjJGZ9hKXrO8IpHNrjJdaLCyX5bLuSwsNggum/cuAAa00KMIY/xt c92eebmAVg090p+fw3MQQ3z7Ku9itzcx5U1WLLu4uu9lHgGnpxiTanaDckShj+gzsCqs CFJ9HGARfrolpXlkrHFNY+7W7l0Q0RyEkot0y9sRV3nXZvkmr//leaV4SbP40Yrn1zDh I9gg==
X-Gm-Message-State: AOAM533lPjfATPUbpQZeq99UljpFoiYRNVgM9i4hqNNvEglwDCwNmRBI P12ImGDlM2Fmw2/IzL4bpttR3BM3UnVruMerCKQK2A==
X-Google-Smtp-Source: ABdhPJzCisuUD6Ol63WTWm2vRwECst+nbSZBF9T6JA9be5KraArTa8rCpTT1VHibdkqm60cdHjKnFOyM1PWEwkq09dU=
X-Received: by 2002:a25:ad65:: with SMTP id l37mr3032939ybe.298.1624907644734;  Mon, 28 Jun 2021 12:14:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a05:6918:7127:b029:2d:b780:99cd with HTTP; Mon, 28 Jun 2021 12:14:04 -0700 (PDT)
In-Reply-To: <6b540117-38a6-fbfa-3749-048d14b34f38@cis-india.org>
References: <447c4444-800b-dfb9-de3e-bbbe3bb4ac64@lear.ch> <6b540117-38a6-fbfa-3749-048d14b34f38@cis-india.org>
From: Mallory Knodel <mknodel@cdt.org>
Date: Mon, 28 Jun 2021 15:14:04 -0400
Message-ID: <CAGVFjMK5K_VQWiQCre7r21c+ofasyUshP5wFYSxmjtX5147Q6Q@mail.gmail.com>
To: Gurshabad Grover <gurshabad@cis-india.org>
Cc: Eliot Lear <lear@lear.ch>, Mallory Knodel <mallory@cdt.org>, "hrpc@irtf.org" <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000f5229e05c5d84a68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/tmOMm37J4coLSmA65uU0JqOGCB8>
Subject: Re: [hrpc] Working group last call for draft-irtf-hrpc-guidelines
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
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: Mon, 28 Jun 2021 19:14:11 -0000

--000000000000f5229e05c5d84a68
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Monday, June 28, 2021, Gurshabad Grover <gurshabad@cis-india.org> wrote:

>
> > Section 2.3.13
> >
> > I don't know that we have *any* real success stories for
> > decentralization.  HTTP certainly isn't one.  Certainly designing
> > *toward* centralization might be best, but I don't think we have very
> > many examples of that *either.*  Moreover, I have argued, and continue
> > to argue, that some centralization may *facilitate* human rights.  If
> > you take into account the combination of DOH + cloud, an observer must
> > go to far greater lengths to discern even so much as the nature of the
> > traffic, much less content and actual endpoint.
> >
> > And this raises another issue: the point of much of cloud services is t=
o
> > improve individual service reliability.  And yet those same cloud
> > services are a form of centralization.  If you consider that perhaps a
> > handful of players might force DNS traffic to a limited number of
> > resolver services, we might also say that DoH itself presents
> > centralization risks.
> >
> > These sorts of conflicts are of course to be expected.  The question is
> > whether it is worth providing guidance relating to centralization.  I
> > will claim that nobody yet has a real handle in this area, and so bette=
r
> > to say nothing in the form of guidance.  Instead, it seems to me to be
> > good fodder for future work.
> >
>
> I don't think I have a strong opinion about this. Before making any
> changes in this section, however, I'd love to hear what others think.
>

I do think that while centralisation can be leveraged for good that it=E2=
=80=99s
well established that an interoperable, resilient decentralised internet
architecture is ideal for the public interest. So there may be trade offs.
I would point to the section on consolidation in the paper Shivan and I
wrote on DNS Privacy Vs (the public interest).

It=E2=80=99s important to keep in mind the tensions so that we aren=E2=80=
=99t dogmatically
accepting either scenario.

Here=E2=80=99s that text: https://github.com/mallory/DNS-Privacy.

Great work getting this new version out!

-M



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

--000000000000f5229e05c5d84a68
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<br><br>On Monday, June 28, 2021, Gurshabad Grover &lt;<a href=3D"mailto:gu=
rshabad@cis-india.org">gurshabad@cis-india.org</a>&gt; wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><br>
&gt; Section 2.3.13<br>
&gt; <br>
&gt; I don&#39;t know that we have *any* real success stories for<br>
&gt; decentralization.=C2=A0 HTTP certainly isn&#39;t one.=C2=A0 Certainly =
designing<br>
&gt; *toward* centralization might be best, but I don&#39;t think we have v=
ery<br>
&gt; many examples of that *either.*=C2=A0 Moreover, I have argued, and con=
tinue<br>
&gt; to argue, that some centralization may *facilitate* human rights.=C2=
=A0 If<br>
&gt; you take into account the combination of DOH + cloud, an observer must=
<br>
&gt; go to far greater lengths to discern even so much as the nature of the=
<br>
&gt; traffic, much less content and actual endpoint.<br>
&gt; <br>
&gt; And this raises another issue: the point of much of cloud services is =
to<br>
&gt; improve individual service reliability.=C2=A0 And yet those same cloud=
<br>
&gt; services are a form of centralization.=C2=A0 If you consider that perh=
aps a<br>
&gt; handful of players might force DNS traffic to a limited number of<br>
&gt; resolver services, we might also say that DoH itself presents<br>
&gt; centralization risks.<br>
&gt; <br>
&gt; These sorts of conflicts are of course to be expected.=C2=A0 The quest=
ion is<br>
&gt; whether it is worth providing guidance relating to centralization.=C2=
=A0 I<br>
&gt; will claim that nobody yet has a real handle in this area, and so bett=
er<br>
&gt; to say nothing in the form of guidance.=C2=A0 Instead, it seems to me =
to be<br>
&gt; good fodder for future work.<br>
&gt; <br>
<br>
I don&#39;t think I have a strong opinion about this. Before making any<br>
changes in this section, however, I&#39;d love to hear what others think.<b=
r>
</blockquote><div><br></div><div>I do think that while centralisation can b=
e leveraged for good that it=E2=80=99s well established that an interoperab=
le, resilient decentralised internet architecture is ideal for the public i=
nterest. So there may be trade offs. I would point to the section on consol=
idation in the paper Shivan and I wrote on DNS Privacy Vs (the public inter=
est).</div><div><br></div><div>It=E2=80=99s important to keep in mind the t=
ensions so that we aren=E2=80=99t dogmatically accepting either scenario.</=
div><div><br></div><div>Here=E2=80=99s that text:=C2=A0<a href=3D"https://g=
ithub.com/mallory/DNS-Privacy">https://github.com/mallory/DNS-Privacy</a>.<=
/div><div><br></div><div>Great work getting this new version out!</div><div=
><br></div><div>-M</div><div><br></div><br><br>-- <br><div dir=3D"ltr"><div=
><div dir=3D"ltr"><div>Mallory Knodel</div><div>CTO, Center for Democracy a=
nd Technology<br>gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9  B071 0C32 A27=
1 BD3C C780<br></div>
<br></div></div></div><br>

--000000000000f5229e05c5d84a68--

