
From nobody Mon Feb  1 02:03:57 2021
Return-Path: <vittorio.bertola@open-xchange.com>
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 C59073A0CE2 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 02:03:55 -0800 (PST)
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, 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 (2048-bit key) header.d=open-xchange.com
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 FQSmCHR_Gd2P for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 02:03:53 -0800 (PST)
Received: from mx3.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 9F3993A0CE5 for <hrpc@irtf.org>; Mon,  1 Feb 2021 02:03:52 -0800 (PST)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.30.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id 75EE46A284; Mon,  1 Feb 2021 11:03:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1612173828; bh=NKx/OEh1Pg6iIeWSheqUbF6Q4DobwwvWLnNhdW9qQOk=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=BiSviYyd+g+f5000ECNwz7Hn4P4R/bChK+SRmhyC5yq6x4NNCfP8fELByCqaOdcx0 zQhcS24CyJAas/5ffD66FQctPhBE+oj4b7wN/XhUUvmKQIIdgpfeP7tq5Dko9lK4Ov V+uo4K9aqTP7ANBdiK1J1n8Z/vxjJdPX789jgWFpNKPdqqQAG5rXgK99YtORfDoLe5 DdiTONg8mND7cnQpzLzJYNbSUcWUfvzuffOoJa9TN5GlWiv1VJeDglBsVN5aq/fmzN g8Tptn0Fk7Z3xeyipVg4jnPmmIzdld5xpRmZMuZgZafYuxrARsTbibLkmWyHCu6b1K i6D6RUbzCR2Gg==
Received: from appsuite-dev-gw1.open-xchange.com ([10.20.30.221]) by imap.open-xchange.com with ESMTPSA id cqi1HATSF2C5RwAA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>); Mon, 01 Feb 2021 11:03:48 +0100
Date: Mon, 1 Feb 2021 11:03:48 +0100 (CET)
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: farzaneh badii <farzaneh.badii@gmail.com>
Cc: Hrpc <hrpc@irtf.org>
Message-ID: <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com>
In-Reply-To: <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_5106_1330655696.1612173828284"
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.5-Rev3
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Et-UJiXFOgusvgkfp43E5L0-zic>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 10:03:56 -0000

------=_Part_5106_1330655696.1612173828284
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


>     Il 30/01/2021 23:00 farzaneh badii <farzaneh.badii@gmail.com> ha scritto:
> 
>     4. Nice to see that you mention DoH. It's a great privacy preserving protocol. 
> 
I was only skimming through this list but my skimmer parsed the sequence "DoH", so here I am.

Indeed, DoH is a great example of a protocol that can advance or stifle human rights depending on how it is used - even more, it can advance some people's rights while stifling other people's. I wouldn't go into DoH specifically in this draft (the current reference however is ok, no problem with it) but it led me to think that the section on "censorship resistance" seems to miss the nuances completely.

For example, Article 20 of the ICCPR mandates censorship of war propaganda and hate speech, so a protocol exhibiting "censorship resistance" may negatively impact human rights if used to bypass that censorship. This should at least be recognized in the document; protocol designers that work on features that bypass censorship should consider both the good and the bad things that can then happen. (Same for the middlebox discussion in the "connectivity" section.) Indeed, much of the ex-post heat in the DoH discussion derived from the fact that the designers had thought of the good things, but had not realized or acknowledged the bad ones.

Another rights-sensitive topic that the DoH discussions brought up is child protection. There have been concerns about the disruption both of child sexual abuse filters and of parental controls (Article 18.4 of the ICCPR recognizes the right of families to educate their children "in conformity with their own convictions"). Possibly a section on this topic would make sense.

There also are other rights that have been often mentioned in connection with architectural Internet issues but do not appear here. For example, the right to free elections, with all the discussions about decentralized electoral propaganda via social media; or the broad right to safety and life. Even in the U.S., the last few years (weeks?) seem to have turned the tide a little, with people realizing that a bit of caution in the design of Internet communication protocols and applications is necessary to preserve democracy and public order. I know it's a hard discussion to have, and also that this is possibly more about the use of the protocols than of protocol design itself (but this can be said of many things that are already in the document). But it will be the Internet policy discussion of the decade.

So I think that a document encouraging engineers to consider the societal impacts of their new technologies more deeply, from more viewpoints, and with more nuances would be quite more useful than a document just promoting the traditional view that everything on the Internet should be free, decentralized and uncontrolled to the maximum.

--

Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com mailto:vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy

------=_Part_5106_1330655696.1612173828284
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!doctype html>
<html>
 <head> 
  <meta charset="UTF-8"> 
 </head>
 <body>
  <div class="default-style">
   <br>
  </div>
  <blockquote type="cite">
   <div>
    Il 30/01/2021 23:00 farzaneh badii &lt;farzaneh.badii@gmail.com&gt; ha scritto:
   </div>
   <div dir="ltr">
    <div style="font-family: verdana,sans-serif;" class="gmail_default">
     <br>
    </div>
    <div style="font-family: verdana,sans-serif;" class="gmail_default">
     4. Nice to see that you mention DoH. It's a great privacy preserving protocol.&nbsp;
    </div>
   </div>
  </blockquote>
  <div>
   I was only skimming through this list but my skimmer parsed the sequence "DoH", so here I am.
   <br>
  </div>
  <div class="default-style">
   <br>
  </div>
  <div class="default-style">
   Indeed, DoH is a great example of a protocol that can advance or stifle human rights depending on how it is used - even more, it can advance some people's rights while stifling other people's. I wouldn't go into DoH specifically in this draft (the current reference however is ok, no problem with it) but it led me to think that the section on "censorship resistance" seems to miss the nuances completely.
   <br>
  </div>
  <div class="default-style">
   <br>
  </div>
  <div class="default-style">
   For example, Article 20 of the ICCPR mandates censorship of war propaganda and hate speech, so a protocol exhibiting "censorship resistance" may negatively impact human rights if used to bypass that censorship. This should at least be recognized in the document; protocol designers that work on features that bypass censorship should consider both the good and the bad things that can then happen. (Same for the middlebox discussion in the "connectivity" section.) Indeed, much of the ex-post heat in the DoH discussion derived from the fact that the designers had thought of the good things, but had not realized or acknowledged the bad ones. 
   <br>
  </div>
  <div class="default-style">
   <br>
  </div>
  <div class="default-style">
   Another rights-sensitive topic that the DoH discussions brought up is child protection. There have been concerns about the disruption both of child sexual abuse filters and of parental controls (Article 18.4 of the ICCPR recognizes the right of families to educate their children "in conformity with their own convictions"). Possibly a section on this topic would make sense.
   <br>
  </div>
  <div class="default-style">
   <br>
  </div>
  <div class="default-style">
   There also are other rights that have been often mentioned in connection with architectural Internet issues but do not appear here. For example, the right to free elections, with all the discussions about decentralized electoral propaganda via social media; or the broad right to safety and life. Even in the U.S., the last few years (weeks?) seem to have turned the tide a little, with people realizing that a bit of caution in the design of Internet communication protocols and applications is necessary to preserve democracy and public order. I know it's a hard discussion to have, and also that this is possibly more about the use of the protocols than of protocol design itself (but this can be said of many things that are already in the document). But it will be the Internet policy discussion of the decade.
   <br>
  </div>
  <div class="default-style">
   <br>
  </div>
  <div class="default-style">
   So I think that a document encouraging engineers to consider the societal impacts of their new technologies more deeply, from more viewpoints, and with more nuances would be quite more useful than a document just promoting the traditional view that everything on the Internet should be free, decentralized and uncontrolled to the maximum.
   <br>
  </div>
  <div class="io-ox-signature">
   <p>-- <br class=""></p>
   <pre class="">Vittorio Bertola | Head of Policy &amp; Innovation, Open-Xchange<br><a href="mailto:vittorio.bertola@open-xchange.com">vittorio.bertola@open-xchange.com</a> <br>Office @ Via Treviso 12, 10144 Torino, Italy</pre>
  </div>
 </body>
</html>
------=_Part_5106_1330655696.1612173828284--


From nobody Mon Feb  1 05:24:41 2021
Return-Path: <farzaneh.badii@gmail.com>
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 328F43A1162 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 05:24:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=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 (2048-bit key) header.d=gmail.com
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 5x5E7XZ_BS9N for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 05:24:38 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 DC1D03A1161 for <hrpc@irtf.org>; Mon,  1 Feb 2021 05:24:37 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id t8so19508584ljk.10 for <hrpc@irtf.org>; Mon, 01 Feb 2021 05:24:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oR7Q+WTZPna00YXHB0q+N6pFqcbjqqRD6Hyqvaf7YcM=; b=vJr1joxQgOv+f9OzrVNvshBaC8hkbb7QcBjBdn++bZoQe4wuRSPWvXfm/ESrNG4Qsw BYNtOsKc4F2FERKYk55q/sqKlQqWPd1lDJ6kjgmBHZiC93NMXZY5ierGsYmcJczKuzaR 2a6JB9x+3szXSrqQZTI8SGP7AqgMnMPF30haBEXS83f8bfwKzxaiiNu6tcUSwJbvqz3V bWg9ByMlYFSSwR2qdJVkQL47vaw1u82Xgen9197LagMu3gEgwI+NkRd49DqNOkizerTQ mlLH6oOU6Pfj/s3LgAIxrwW1A4Ck3YsSGXO5AHlMl8GCz5DNIY+4wMeT8PyucPSPbPm+ MsZw==
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=oR7Q+WTZPna00YXHB0q+N6pFqcbjqqRD6Hyqvaf7YcM=; b=szR76Be8IpNuZ9uvWg22UOLQEA02JRx1kvMwb5mGNkG/fYSG/IKweNdb6JCyxOFPj/ B2FUBxsYr0EysSvgX7dqLRISu2Rf2hOJmpbDH5uPlAB/aKkGPBpLJl1nJcAV7TPoOTDg UrPUfgH3tiX9U/z0NpNQis2hBGICOColNkQecP4mT8XaPULBUx4RSKG5mfti8rFX3eT5 r7aAfc0YB8ss/9qQyvYQlc7QU81ZYRhFk9opmlw20HSNEA8m78cVyGjuv4rHHWwYkIW9 vsKq4u26bb60BgbSNAOvzKhvwMyTg2Wyf4WfQuTGGwai6iBCKGKTMjrZd2XybptR4wrU 5uRw==
X-Gm-Message-State: AOAM530y6GRSOLCP7DuGNHQe2fUpb79YWz6v4llLX87eTxYXnrqJwilW NpuDbkbwA89BFnqN5p0QKEWx0naqzB4vygXXzBA=
X-Google-Smtp-Source: ABdhPJw2z5vmGzKK5oiisdc/gdeMm8JesO5GRRWqfqkXq6pQzBAOnOpH1T5/rBmuZHZJlvM+6VfkBLqAT2abcvOm2b0=
X-Received: by 2002:a2e:531d:: with SMTP id h29mr10224297ljb.115.1612185875804;  Mon, 01 Feb 2021 05:24:35 -0800 (PST)
MIME-Version: 1.0
Received: by 2002:ac2:4570:0:0:0:0:0 with HTTP; Mon, 1 Feb 2021 05:24:35 -0800 (PST)
In-Reply-To: <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Mon, 1 Feb 2021 08:24:35 -0500
Message-ID: <CAN1qJvDewtE4bCbqsXpRGRt1z0=DCxhS2QmdXrpmUSuR0o_B+w@mail.gmail.com>
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Cc: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000070779d05ba464686"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/zKaKclmHetd26xqI-TLY3MPc0Ak>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 13:24:40 -0000

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

On Monday, February 1, 2021, Vittorio Bertola <
vittorio.bertola@open-xchange.com> wrote:

>
> Il 30/01/2021 23:00 farzaneh badii <farzaneh.badii@gmail.com> ha scritto:
>
> 4. Nice to see that you mention DoH. It's a great privacy preserving
> protocol.
>
> I was only skimming through this list but my skimmer parsed the sequence
> "DoH", so here I am.
>
>
Of course.

>
> Indeed, DoH is a great example of a protocol that can advance or stifle
> human rights depending on how it is used - even more, it can advance some
> people's rights while stifling other people's. I wouldn't go into DoH
> specifically in this draft (the current reference however is ok, no probl=
em
> with it) but it led me to think that the section on "censorship resistanc=
e"
> seems to miss the nuances completely.
>
> For example, Article 20 of the ICCPR mandates censorship of war propagand=
a
> and hate speech, so a protocol exhibiting "censorship resistance" may
> negatively impact human rights if used to bypass that censorship. This
> should at least be recognized in the document; protocol designers that wo=
rk
> on features that bypass censorship should consider both the good and the
> bad things that can then happen. (Same for the middlebox discussion in th=
e
> "connectivity" section.) Indeed, much of the ex-post heat in the DoH
> discussion derived from the fact that the designers had thought of the go=
od
> things, but had not realized or acknowledged the bad ones.
>

There is nothing good about censorship.

>
> Another rights-sensitive topic that the DoH discussions brought up is
> child protection. There have been concerns about the disruption both of
> child sexual abuse filters and of parental controls (Article 18.4 of the
> ICCPR recognizes the right of families to educate their children "in
> conformity with their own convictions"). Possibly a section on this topic
> would make sense.
>

Sexual abuse filter and parental =E2=80=9Csurveillance=E2=80=9D have the po=
tential for
censorship and in my opinion raising kids that think surveillance is a
necessary part of life is a terrible for the future of the society.
We can have encryption and fight with child sexual abuse (both in our
society and online, and not just take sexual abuse pictures down and think
we and the kids are all ok!). Encryption and child online protection are
not mutually exclusive.

I hope for kids not to be indoctrinated by their parents.



>
> There also are other rights that have been often mentioned in connection
> with architectural Internet issues but do not appear here. For example, t=
he
> right to free elections, with all the discussions about decentralized
> electoral propaganda via social media; or the broad right to safety and
> life. Even in the U.S., the last few years (weeks?) seem to have turned t=
he
> tide a little, with people realizing that a bit of caution in the design =
of
> Internet communication protocols and applications is necessary to preserv=
e
> democracy and public order. I know it's a hard discussion to have, and al=
so
> that this is possibly more about the use of the protocols than of protoco=
l
> design itself (but this can be said of many things that are already in th=
e
> document). But it will be the Internet policy discussion of the decade.
>

This has been the Internet policy discussion for a decade already. Again,
elections is a matter of sovereignty and the States.

And I totally agree that this is a matter of the implementation of the
protocol and not its design, something we have brought up before.

Where is the evidence that =E2=80=9Cdecentralized=E2=80=9D electoral propag=
anda was
effective? Studies that I have seen discuss the fact that centralization
and =E2=80=9Cecho chambers=E2=80=9D can be far more effective.

>
> So I think that a document encouraging engineers to consider the societal
> impacts of their new technologies more deeply, from more viewpoints, and
> with more nuances would be quite more useful than a document just promoti=
ng
> the traditional view that everything on the Internet should be free,
> decentralized and uncontrolled to the maximum.
>

Free and decentralized does not mean uncontrolled.

This back and forth arguments about rights is a good cautionary sign that
we need to refrain from putting engineers in charge of balancing rights and
deciding what is better for people. They are not elected officials, they
are not here to control speech, and it is not their fault that the protocol
can potentially get abused during the implementation for reasons they could
not predict or control for! What we need is to understand if, where, how
and in what context protocols have affected people and if it is the
protocol or other factors involved as well.

I think this document could have mentioned that more elaborately with
concrete examples. I think our research group should have done that. But I
guess it=E2=80=99s too late now.


> --
>
> Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
> vittorio.bertola@open-xchange.com
> Office @ Via Treviso 12, 10144 Torino, Italy <https://www.google.com/maps=
/search/Via+Treviso+12,+10144+Torino,+Italy?entry=3Dgmail&source=3Dg>
>
>

--=20
Farzaneh

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

<br><br>On Monday, February 1, 2021, Vittorio Bertola &lt;<a href=3D"mailto=
:vittorio.bertola@open-xchange.com">vittorio.bertola@open-xchange.com</a>&g=
t; wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><u></u>

 =20
  =20
=20
 <div>
  <div>
   <br>
  </div>
  <blockquote type=3D"cite">
   <div>
    Il 30/01/2021 23:00 farzaneh badii &lt;<a href=3D"mailto:farzaneh.badii=
@gmail.com" target=3D"_blank">farzaneh.badii@gmail.com</a>&gt; ha scritto:
   </div>
   <div dir=3D"ltr">
    <div style=3D"font-family:verdana,sans-serif" class=3D"gmail_default">
     <br>
    </div>
    <div style=3D"font-family:verdana,sans-serif" class=3D"gmail_default">
     4. Nice to see that you mention DoH. It&#39;s a great privacy preservi=
ng protocol.=C2=A0
    </div>
   </div>
  </blockquote>
  <div>
   I was only skimming through this list but my skimmer parsed the sequence=
 &quot;DoH&quot;, so here I am.</div><div>=C2=A0
   <br>
  </div></div></blockquote><div>Of course. =C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div>
  <div>
   <br>
  </div>
  <div>
   Indeed, DoH is a great example of a protocol that can advance or stifle =
human rights depending on how it is used - even more, it can advance some p=
eople&#39;s rights while stifling other people&#39;s. I wouldn&#39;t go int=
o DoH specifically in this draft (the current reference however is ok, no p=
roblem with it) but it led me to think that the section on &quot;censorship=
 resistance&quot; seems to miss the nuances completely.
   <br>
  </div>
  <div>
   <br>
  </div>
  <div>
   For example, Article 20 of the ICCPR mandates censorship of war propagan=
da and hate speech, so a protocol exhibiting &quot;censorship resistance&qu=
ot; may negatively impact human rights if used to bypass that censorship. T=
his should at least be recognized in the document; protocol designers that =
work on features that bypass censorship should consider both the good and t=
he bad things that can then happen. (Same for the middlebox discussion in t=
he &quot;connectivity&quot; section.) Indeed, much of the ex-post heat in t=
he DoH discussion derived from the fact that the designers had thought of t=
he good things, but had not realized or acknowledged the bad ones.=20
   <br>
  </div></div></blockquote><div>=C2=A0</div><div>There is nothing good abou=
t censorship.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
  <div>
   <br>
  </div>
  <div>
   Another rights-sensitive topic that the DoH discussions brought up is ch=
ild protection. There have been concerns about the disruption both of child=
 sexual abuse filters and of parental controls (Article 18.4 of the ICCPR r=
ecognizes the right of families to educate their children &quot;in conformi=
ty with their own convictions&quot;). Possibly a section on this topic woul=
d make sense.
   <br>
  </div></div></blockquote><div><br></div><div>Sexual abuse filter and pare=
ntal =E2=80=9Csurveillance=E2=80=9D have the potential for censorship and i=
n my opinion raising kids that think surveillance is a necessary part of li=
fe is a terrible for the future of the society.</div><div>We can have encry=
ption and fight with child sexual abuse (both in our society and online, an=
d not just take sexual abuse pictures down and think we and the kids are al=
l ok!). Encryption and child online protection are not mutually exclusive.=
=C2=A0</div><div><br></div><div>I hope for kids not to be indoctrinated by =
their parents.</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div>
  <div>
   <br>
  </div>
  <div>
   There also are other rights that have been often mentioned in connection=
 with architectural Internet issues but do not appear here. For example, th=
e right to free elections, with all the discussions about decentralized ele=
ctoral propaganda via social media; or the broad right to safety and life. =
Even in the U.S., the last few years (weeks?) seem to have turned the tide =
a little, with people realizing that a bit of caution in the design of Inte=
rnet communication protocols and applications is necessary to preserve demo=
cracy and public order. I know it&#39;s a hard discussion to have, and also=
 that this is possibly more about the use of the protocols than of protocol=
 design itself (but this can be said of many things that are already in the=
 document). But it will be the Internet policy discussion of the decade.
   <br>
  </div></div></blockquote><div>=C2=A0</div><div>This has been the Internet=
 policy discussion for a decade already. Again, elections is a matter of so=
vereignty and the States.</div><div><br></div><div>And I totally agree that=
 this is a matter of the implementation of the protocol and not its design,=
 something we have brought up before.</div><div><br></div><div>Where is the=
 evidence that =E2=80=9Cdecentralized=E2=80=9D electoral propaganda was eff=
ective? Studies that I have seen discuss the fact that centralization and =
=E2=80=9Cecho chambers=E2=80=9D can be far more effective. =C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div>
  <div>
   <br>
  </div>
  <div>
   So I think that a document encouraging engineers to consider the societa=
l impacts of their new technologies more deeply, from more viewpoints, and =
with more nuances would be quite more useful than a document just promoting=
 the traditional view that everything on the Internet should be free, decen=
tralized and uncontrolled to the maximum.
   <br>
  </div></div></blockquote><div><br></div><div>Free and decentralized does =
not mean uncontrolled.=C2=A0</div><div><br></div><div>This back and forth a=
rguments about rights is a good cautionary sign that we need to refrain fro=
m putting engineers in charge of balancing rights and deciding what is bett=
er for people. They are not elected officials, they are not here to control=
 speech, and it is not their fault that the protocol can potentially get ab=
used during the implementation for reasons they could not predict or contro=
l for! What we need is to understand if, where, how and in what context pro=
tocols have affected people and if it is the protocol or other factors invo=
lved as well.=C2=A0</div><div><br></div><div>I think this document could ha=
ve mentioned that more elaborately with concrete examples. I think our rese=
arch group should have done that. But I guess it=E2=80=99s too late now.=C2=
=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
  <div>
   <p>-- <br></p>
   <pre>Vittorio Bertola | Head of Policy &amp; Innovation, Open-Xchange<br=
><a href=3D"mailto:vittorio.bertola@open-xchange.com" target=3D"_blank">vit=
torio.bertola@open-xchange.<wbr>com</a> <br>Office @ <a href=3D"https://www=
.google.com/maps/search/Via+Treviso+12,+10144+Torino,+Italy?entry=3Dgmail&a=
mp;source=3Dg">Via Treviso 12, 10144 Torino, Italy</a></pre>
  </div>
 </div>
</blockquote><br><br>-- <br><div dir=3D"ltr"><div><font face=3D"verdana, sa=
ns-serif">Farzaneh </font></div></div><br>

--00000000000070779d05ba464686--


From nobody Mon Feb  1 09:28:14 2021
Return-Path: <stephane@sources.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 554AD3A1332 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:28:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 wj_X-3meJ2lw for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:28:10 -0800 (PST)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [92.243.4.211]) (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 670563A1330 for <hrpc@irtf.org>; Mon,  1 Feb 2021 09:28:09 -0800 (PST)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id D5F7CA042B; Mon,  1 Feb 2021 18:28:06 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id E3082190AB1; Mon,  1 Feb 2021 18:23:46 +0100 (CET)
Date: Mon, 1 Feb 2021 18:23:46 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
Cc: farzaneh badii <farzaneh.badii@gmail.com>, Hrpc <hrpc@irtf.org>
Message-ID: <20210201172346.GA24309@sources.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 10.7
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/2qg0ciBjQayHxCseNGpYpMGKaCg>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 17:28:12 -0000

On Mon, Feb 01, 2021 at 11:03:48AM +0100,
 Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote 
 a message of 119 lines which said:

> protocol designers that work on features that bypass censorship
> should consider both the good and the bad things that can then
> happen.

> So I think that a document encouraging engineers to consider the
> societal impacts of their new technologies more deeply, from more
> viewpoints, and with more nuances would be quite more useful than a
> document just promoting the traditional view that everything on the
> Internet should be free, decentralized and uncontrolled to the
> maximum.

[I think I agree with Farzaneh Badii here but I would like to make
another point.]

The problem is that the protocols are not deployed in an ideal
world. We know that, out there, there are strong, very strong forces,
both political and economical, working to use the Internet as a
surveillance tool, and to censor free speech. Whatever the IETF (and
the developers of programs like Tor, which is not an IETF outcome)
produces, whatever the protocols are, these forces will try to use the
Internet to increase surveillance, censorship and other bad things. As
in the well-known XKCD picture <https://xkcd.com/538/>, using Tor,
Signal and other technologies will limit the surveillance but
certainly not stop it, as more than one human rights activist
discovered :-(

So, the issue is not really about the proper balance between, say,
freedom of speech and censorship of nazi/racist/sectarian speech. It
is that we are a small force, developing techniques that fight against
the interests of giants. We should not refrain ourselves to develop
anti-censorship techniques because we (and the ordinary users) are
already at a disadvantage.

> people realizing that a bit of caution in the design of Internet
> communication protocols and applications is necessary to preserve
> democracy and public order.

I don't think this is a consensual opinion. I don't know about the USA
but in many countries, the call "we must tame the Internet since it
allows ordinary people to communicate and this can be dangerous" is
often heard from governemnts and traditional medias but does not
represent the viewpoint of the majority of "people".

But it seems close from the traditional discussion about
encryption. How could you change Internet protocols to resist
censorship when speech is used for good and to yield to censorship
when speech is used for bad? (Spoiler: you cannot.)

> Indeed, much of the ex-post heat in the DoH discussion derived from
> the fact that the designers had thought of the good things, but had
> not realized or acknowledged the bad ones.

I strongly disagree with this assessment. The people who worked in the
doh working group were well aware of the (very ancient and
traditional) discussions about good and bad sides of censorship, about
conflicts between different human rights, about balance, etc. 


From nobody Mon Feb  1 09:53:15 2021
Return-Path: <stephane@sources.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 292BA3A1362 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level: 
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 8N2n6q1_fKsT for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:53:08 -0800 (PST)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [92.243.4.211]) (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 834A13A135F for <hrpc@irtf.org>; Mon,  1 Feb 2021 09:53:08 -0800 (PST)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 72E99A042B; Mon,  1 Feb 2021 18:53:06 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id 26ED8190AB1; Mon,  1 Feb 2021 18:50:27 +0100 (CET)
Date: Mon, 1 Feb 2021 18:50:27 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: farzaneh badii <farzaneh.badii@gmail.com>
Cc: Corinne Cath <corinnecath@gmail.com>, Hrpc <hrpc@irtf.org>
Message-ID: <20210201175026.GA25564@sources.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 10.7
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/WCgOwSYrsRir4vzDDb7Or2NwcQA>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 17:53:15 -0000

On Sat, Jan 30, 2021 at 05:00:00PM -0500,
 farzaneh badii <farzaneh.badii@gmail.com> wrote 
 a message of 380 lines which said:

> 1. One major issue that I see here and you might be able to easily
> solve it is that there is no distinction between user facing
> protocols and other protocols. For example, you ask for
> accessibility and consideration of culture etc.

Unlike the old telephone network, the Internet does not have a
clear-cut distinction between users and operators. Many protocols are
deployed by people who are not professional network operators. I tend
to think that there are no pure "developpers-only protocols". Error
messages, for instance, tend to leak and therefore their
internationalization is an issue.

Two examples:

* the tussle about IDN was fueled by the fact that some people claimed
that domain names were "purely technical identifiers" (not needing
internationalization) while others regarded them as a communication
tool between humans ("side of the bus").

* RFC 8203 was replaced by RFC 9003 just because of
internationalization issues in the messages. And this is for BGP,
hardly a "end user" protocol.

> Are you asking all the protocols to be provided in multiple
> languages, even those that only developers and implementers use and
> not the actual users? You might want to clarify that.

I'm confused here. I don't think that draft-irtf-hrpc-guidelines-05
asks for internationalization of the specifications themselves (for
instance by translating the RFC). Clarification is needed (and Niels
ten Oever's reply about Ramsey Nasr and Qalb confuses me even more;
are we talking about internationalization of protocols or
internationalization of specifications?)


From nobody Mon Feb  1 11:38:18 2021
Return-Path: <mail@nielstenoever.net>
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 A93053A140D for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 11:38:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 9QCP-2T9Pmtc for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 11:38:13 -0800 (PST)
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 A60053A1405 for <hrpc@irtf.org>; Mon,  1 Feb 2021 11:38:12 -0800 (PST)
To: farzaneh badii <farzaneh.badii@gmail.com>
Cc: Hrpc <hrpc@irtf.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <08b61ab2-7840-d993-9946-c085861f4172@nielstenoever.net> <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com>
From: Niels ten Oever <mail@nielstenoever.net>
Message-ID: <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net>
Date: Mon, 1 Feb 2021 20:38:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: base64
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: a58a25a01555903a1b5563337bfce519
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/QuKedMbcoVkswBgB_6Owckr08YA>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 19:38:17 -0000

SGkgRmFyemFuZWgsDQoNCk9uIDMxLTAxLTIwMjEgMTk6MTYsIGZhcnphbmVoIGJhZGlpIHdy
b3RlOg0KPiBIZWxsbyBOaWVscy4NCj4gDQo+IA0KPiBJIGRvbid0IGtub3cgaG93IHdlIG1l
YXN1cmUgY29uc2Vuc3VzIGhlcmUuIEJ1dCBJIHJlbWVtYmVyIHdlaWdoaW5nIGluIGJhY2sg
dGhlbiBhcyB3ZWxsKFdoZW4gTXIuIEN1cnJhbiB3ZWlnaGVkIGluIGJhY2sgaW4gMjAxOSku
IEhlcmUgaXMgdGhlIHRocmVhZDrCoGh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJj
aC9icm93c2UvaHJwYy8/cT1hdHRyaWJ1dGlvbiA8aHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRm
Lm9yZy9hcmNoL2Jyb3dzZS9ocnBjLz9xPWF0dHJpYnV0aW9uPg0KPiANCj4gSSBjYW4gc2Vl
IHRoYXQgdW5mb3J0dW5hdGVseSBJIG1pc3NlZCB0aGXCoGRpc2N1c3Npb24gb24gdGhpcyB0
b3BpYyBkdXJpbmcgdGhlIHBhc3QgeWVhciwgYW5kIHRoYXQncyBteSBmYXVsdCwgYnV0IEkg
Y2FuIGJyaW5nIHJlYXNvbnMgbm90IHRvIGFkZCAiYXR0cmlidXRpb24gYW5kIGxlZ2FsIHJl
bWVkeSIgdG8gdGhpcyBkb2N1bWVudCBhdCBhbGwuwqANCj4gDQo+IDEuIEFjY2VzcyB0byBs
ZWdhbCByZW1lZHkgaXMgc29tZXRoaW5nIHRoYXQgdGhlIFN0YXRlcyBhcmUgc3VwcG9zZWRs
eSBpbiBjaGFyZ2Ugb2YgYnJpbmdpbmcgdG8gdGhlaXIgY2l0aXplbnMuV2hpY2ggc2hvdWxk
IChpbiB0aGVvcnkpIGVuc3VyZSB0aGF0IGh1bWFuIHJpZ2h0cyBhcmUgZW5mb3JjZWQuIEkg
ZG9uJ3QgdGhpbmsgdGhlcmXCoHdhcyBhbiBpbnRlbnRpb24gdG/CoCBwcm92aWRlwqAgbWVj
aGFuaXNtcyBmb3IgImVuZm9yY2VtZW50IiBvZiBodW1hbiByaWdodHMgaW4gdmFyaW91cyBs
ZWdhbCBzeXN0ZW1zIHRocm91Z2ggSW50ZXJuZXQgcHJvdG9jb2xzLiBBcyBtZW50aW9uZWTC
oGluIHRoZSBiZWdpbm5pbmcgb2YgeW91ciBkb2N1bWVudDrCoA0KPiAiSHVtYW4gcmlnaHRz
IHRocmVhdHMgb24gdGhlIEludGVybmV0IGNvbWUgaW4gYSBteXJpYWQgb2YgZm9ybXMuKsKg
KipQKipyb3RvY29scyBhbmQgc3RhbmRhcmRzIGNhbiBoYXJtIG9yIGVuYWJsZSogdGhlIHJp
Z2h0IHRvIGZyZWVkb20gb2bCoGV4cHJlc3Npb24sIHJpZ2h0IHRvIG5vbi1kaXNjcmltaW5h
dGlvbiwgcmlnaHQgdG8gZXF1YWwgcHJvdGVjdGlvbizCoHJpZ2h0IHRvIHBhcnRpY2lwYXRl
IGluIGN1bHR1cmFsIGxpZmUsIGFydHMgYW5kIHNjaWVuY2UsIHJpZ2h0IHRvwqBmcmVlZG9t
IG9mIGFzc2VtYmx5IGFuZCBhc3NvY2lhdGlvbiwgYW5kIHRoZSByaWdodCB0byBzZWN1cml0
eS4iwqANCj4gDQo+IFNvIHdlIGFyZSBub3QgaW4gdGhlIGJ1c2luZXNzIG9mIGVuZm9yY2lu
ZyBidXQgcHJvdmlkaW5nwqBhbiBlbmFibGluZyBlbnZpcm9ubWVudC4gQmVjYXVzZcKgaWYg
d2Ugd2FudCB0byBoZWxwIGxhdyBlbmZvcmNlbWVudCBhbmQgdGhlIGp1ZGljaWFsIGF1dGhv
cml0aWVzIGVuZm9yY2UgaHVtYW4gcmlnaHRzIHRocm91Z2jCoEludGVybmV0wqBwcm90b2Nv
bHMgd2Ugc2hvdWxkIGJlYXIgaW4gbWluZCB0aGF0IHRoYXQgdGhleSBhcmUgbm90IGFsd2F5
cyBzdGF1bmNoIGFkdm9jYXRlcyBvZiBodW1hbiByaWdodHMuIFNvIHdoYXQgSSBhc3N1bWUg
d2UgYXJlIHRyeWluZyB0byBkbyBoZXJlIGlzIHRvIGhlbHAgSW50ZXJuZXQgcHJvdG9jb2wg
bm90IHRvIGZhY2lsaXRhdGUgaGFybSBhbmQgImVuYWJsZSIgaHVtYW4gcmlnaHRzLsKgDQo+
IA0KDQpUaGUgdGV4dCBpbiB0aGUgZHJhZnQgc2Vla3MgdG8gYWRkcmVzcyB0aGlzIHJpc2su
IEkgaGF2ZSBzb3VnaHQgdG8gYWRkcmVzcyBhbGwgcG9pbnRzIG1hZGUgaW4gdGhhdCBkaXNj
dXNzaW9uLCBhbmQgSSB3b3VsZCBub3QgbGlrZSB0byByZS1vcGVuIHRoYXQgZGViYXRlLiBJ
ZiB5b3UgZmVlbCB0aGUgdGV4dCBpcyB1bmJhbGFuY2VkLCBjb3VsZCB5b3UgcGVyaGFwcyBw
cm92aWRlIHRleHQgc3VnZ2VzdGlvbnM/IA0KDQo+IDIuIEF0dHJpYnV0aW9uLCBzZWN0aW9u
IDMuMy4yMMKgIG9mIHRoZSBHdWlkZWxpbmUsIHRoZSBhdXRob3JzIGFzc2VydCB0aGF0OiAi
SG93ZXZlciwgYXR0cmlidXRpb24gdG8gY29ycG9yYXRlIGVudGl0aWVzLMKgYXNzb2NpYXRp
b25zLCBhbmQvb3IgY291bnRyaWVzIG1heSBub3QgZGlyZWN0bHkgbmVnYXRpdmVseSBpbXBh
Y3TCoGh1bWFuIHJpZ2h0cy4iIEkgdGhpbmsgdGhpcyBpcyBub3QgYSB2ZXJ5wqB3ZWxsIGJh
Y2tlZCB1cCBjbGFpbS4gQmVjYXVzZSBpbiBzb21lIGNhc2VzIHNvbWUgYXNzb2NpYXRpb25z
IG1pZ2h0IGJlIHBvbGl0aWNhbCBvciB0aGV5IG1pZ2h0IGJlIGh1bWFuIHJpZ2h0cyBhc3Nv
Y2lhdGlvbnMgZGVhbGluZyB3aXRoIGEgZGljdGF0b3JzaGlwLiBBdHRyaWJ1dGlvbiB0byB0
aG9zZSBhc3NvY2lhdGlvbnMgY2VydGFpbmx5IGNhbiBpbXBhY3QgdGhlaXIgaHVtYW4gcmln
aHRzIG5lZ2F0aXZlbHkuIEV2ZW4gd2hlbiBpdCBjb21lcyB0byBjb3Jwb3JhdGlvbnMsIHNv
bWUgQ0VPcyBvZiBkaWdpdGFsIGNvbXBhbmllcyBhcmUgcHV0IGluIGphaWwgYmVjYXVzZSBv
ZiB0aGUgbWF0ZXJpYWxzIHBvc3RlZCBvbiB0aGVpciB3ZWJzaXRlcy4gSSBkb24ndCB0aGlu
ayB3ZSBjYW4gYXJndWUgdGhhdCBhdHRyaWJ1dGlvbiB0byBjb3Jwb3JhdGUgZW50aXRpZXMg
bWlnaHQgbm90IGFkdmVyc2VseSBpbXBhY3QgaHVtYW4gcmlnaHRzLg0KPiANCg0KQWdhaW4s
IHRoZSBrZXl3b3JkIGluIHRoYXQgc2VudGVuY2UgaXMgJ21heScsIHNvIHRoZXJlIGlzIG5v
IHN0cm9uZyBjbGFpbSBtYWRlLiANCg0KPiBBbGwgaW4gYWxsIEkgdGhpbmsgc2VjdGlvbiAz
LjMuMjAgZG9lcyBub3QgaGVscCBJbnRlcm5ldCBQcm90b2NvbHMgZW5hYmxlIGh1bWFuIHJp
Z2h0cyBhbmQgaXQgY2FuIGJlIG1pc2ludGVycHJldGVkLiANCg0KSSB0aGluayB0aGUgdGV4
dCBpbiB0aGVyZSBpcyBub3Qgc3Ryb25nIGFuZCBzaG93cyBkaWZmZXJlbnQgcGVyc3BlY3Rp
dmVzIGFuZCBwb3RlbnRpYWwgY29uc2VxdWVuY2VzLiBCdXQgYWdhaW4sIGhhcHB5IHRvIHJl
Y2VpdmUgdGV4dCBzdWdnZXN0aW9ucy4gDQoNCj4gDQo+IEFuZCBpbiBteSBwcmV2aW91cyBl
bWFpbCBJIHRhbGtlZCBhYm91dCB0aGUgcHJvYmxlbXMgd2l0aCB0aHJlYXQgaW50ZWxsaWdl
bmNlIGFnZW5jaWVzIGFuZCBzb21lIG9mIHRoZWlyIGNvbmR1Y3RzIGFuZCB0aGUgdXNlIG9m
IFdIT0lTIGZvciBhdHRyaWJ1dGlvbiAod2hpY2ggd2FzIGFjdHVhbGx5IG5vdCBkZXNpZ25l
ZCB0byAiaWRlbnRpZnkiIGFjdG9ycyBidXQgdW5mb3J0dW5hdGVseSB3YXMgdXNlZCBmb3Ig
dGhhdCkgc28gSSB3aWxsIG5vdCByZWl0ZXJhdGUgaGVyZS4gDQoNCkZyb20gZXhhY3RseSB0
aGF0IGRpc2N1c3Npb24gd2UgZ290IHRoZSBpZGVhIHRvIHJlbW92ZSBpbmRpdmlkdWFscywg
YW5kIGxlYXZlIG5vbi1uYXR1cmFsIHBlcnNvbnMgaW4uIA0KDQpCZXN0LA0KDQpOaWVscw0K
DQo+IA0KPiANCj4gDQo+IA0KPiANCj4gDQo+IA0KPiBPbiBTdW4sIEphbiAzMSwgMjAyMSBh
dCA1OjUyIEFNIE5pZWxzIHRlbiBPZXZlciA8bWFpbEBuaWVsc3Rlbm9ldmVyLm5ldCA8bWFp
bHRvOm1haWxAbmllbHN0ZW5vZXZlci5uZXQ+PiB3cm90ZToNCj4gDQo+ICAgICBIaSBGYXJ6
YW5laCwNCj4gDQo+ICAgICBUaGFua3MgYSBsb3QgZm9yIHRoZSByZXZpZXchDQo+IA0KPiAg
ICAgT24gMzAtMDEtMjAyMSAyMzowMCwgZmFyemFuZWggYmFkaWkgd3JvdGU6DQo+ICAgICA+
IEhlbGxvDQo+ICAgICA+DQo+ICAgICA+IEFkZGluZyBteSBjb21tZW50cyBvbiB0aGlzIGRv
Y3VtZW50OsKgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlydGYtaHJwYy1n
dWlkZWxpbmVzLTA1IDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaXJ0Zi1o
cnBjLWd1aWRlbGluZXMtMDU+IDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
aXJ0Zi1ocnBjLWd1aWRlbGluZXMtMDUgPGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1pcnRmLWhycGMtZ3VpZGVsaW5lcy0wNT4+DQo+ICAgICA+DQo+ICAgICA+IDEuIE9u
ZSBtYWpvciBpc3N1ZSB0aGF0IEkgc2VlIGhlcmUgYW5kIHlvdSBtaWdodCBiZSBhYmxlIHRv
IGVhc2lseSBzb2x2ZSBpdCBpcyB0aGF0IHRoZXJlIGlzIG5vIGRpc3RpbmN0aW9uIGJldHdl
ZW4gdXNlciBmYWNpbmcgcHJvdG9jb2xzIGFuZCBvdGhlciBwcm90b2NvbHMuIEZvciBleGFt
cGxlLCB5b3UgYXNrIGZvciBhY2Nlc3NpYmlsaXR5IGFuZCBjb25zaWRlcmF0aW9uIG9mIGN1
bHR1cmUgZXRjLiBBcmUgeW91IGFza2luZyBhbGwgdGhlIHByb3RvY29scyB0byBiZSBwcm92
aWRlZCBpbiBtdWx0aXBsZSBsYW5ndWFnZXMsIGV2ZW4gdGhvc2UgdGhhdCBvbmx5wqBkZXZl
bG9wZXJzwqBhbmQgaW1wbGVtZW50ZXJzIHVzZSBhbmQgbm90IHRoZSBhY3R1YWwgdXNlcnM/
IFlvdSBtaWdodCB3YW50IHRvIGNsYXJpZnkgdGhhdC7CoA0KPiAgICAgPg0KPiANCj4gICAg
IFdlIGhhZCBhIHF1aXRlIGV4dGVuc2l2ZSBkaXNjdXNzaW9uIGFib3V0IHRoaXMgaW4gcmVs
YXRpb24gdG8gdGhlIHByZXNlbnRhdGlvbiBieSBSYW1zZXkgTmFzciB3aG8gY3JlYXRlIFFh
bGIsIGFuIEFyYWJpYyBwcm9ncmFtbWluZyBsYW5ndWFnZS4gUHJvZ3JhbW1lcnMgYXJlIHRo
ZSBtb3N0IGZyZXF1ZW50ICd1c2Vycycgb2YgcHJvdG9jb2xzIC0gaWYgd2UgY29udGludWUg
dXNpbmcgb25seSBsYXRpbiBjaGFyYWN0ZXJzIGFuZCBFbmdsaXNoIGRvY3VtZW50YXRpb24g
aW4gcHJvdG9jb2xzIHdlIGFyZSBsaWtlbHkgdG8gcmVwcm9kdWNlIHRoZSBleGlzdGluZyBs
YWNrIG9mIGRpdmVyc2l0eSBpbiBwcm90b2NvbCBkZXZlbG9wZXJzIGNvbW11bml0aWVzLiBC
dXQgd2UgY2FuIG1ha2UgdGhlIHRleHQgb24gdGhpcyBjbGVhcmVyIGFzIHdlbGwhDQo+IA0K
PiAgICAgPiAyLnNlY3Rpb24gMy4zLjEgb24gY29ubmVjdGl2aXR5LCB5b3UgbWVudGlvbiB0
aGF0ICJjb25zaWRlcmluZyB0aGUgZmFjdCB0aGF0IG5ldHdvcmsgcXVhbGl0eSBhbmQgY29u
ZGl0aW9ucyB2YXJ5IGFjcm9zcyBnZW9ncmFwaHkgYW5kIHRpbWUgaXQgaXMgYWxzbyBpbXBv
cnRhbnQgdG8gZGVzaWduIHByb3RvY29scyBzdWNoIHRoYXQgdGhleSBhcmUgcmVsaWFibGUg
ZXZlbiBvbiBsb3cgYmFuZHdpZHRoIC4uLiIuIFRoZW4gaW4geW91ciBleGFtcGxlIHlvdSBz
YXk6IE1pZGRsZWJveGVzIChpbmNsdWRpbmcgTkFUKS4uLi4gY2FuIGNyZWF0ZSBwb3RlbnRp
YWwgZm9yIGFidXNlLiBOQVQgaXMgYSBOZXR3b3JrIEFkZHJlc3MgVHJhbnNsYXRpb24gcHJv
dG9jb2wuIEkgZG9uJ3QgdGhpbmsgaXQgaGFzIGFueXRoaW5nIHRvIGRvIHdpdGggYmFuZHdp
ZHRoLiBJbiB0aGlzIGV4YW1wbGUgeW91IGFsc28gbWVudGlvbiBDRE5zLiBBcmUgeW91IHN1
Z2dlc3RpbmcgdGhhdCB0aGUgZGV2ZWxvcGVyIHNob3VsZCBub3QgY29uc2lkZXIgIk1pZGRs
ZWJveGVzIiBwcm90b2NvbHM/IEkgdGhpbmsgeW91IG5lZWQgdG8gd29yayBvbiB0aGUgZXhh
bXBsZSBvZiBzZWN0aW9uIDMuMy4xIHNvbWUgbW9yZSB0byBtYWtlIGl0IGNsZWFyZXIuwqAN
Cj4gICAgID4NCj4gDQo+ICAgICBFeGNlbGxlbnQgcG9pbnQgLSB3ZSdsbCBhZGRyZXNzIHRo
aXMgaW4gYSBmdXR1cmUgdmVyc2lvbi4NCj4gDQo+ICAgICA+IDMuIHNlY3Rpb24gMy4zLjIw
IHJlbWVkeSBhbmQgYXR0cmlidXRpb27CoA0KPiAgICAgPiBUaGlzIHNlY3Rpb24gd29ycmll
cyBtZS4gQXMgYcKgIHNjaG9sYXIgSSBoYXZlIHdvcmtlZCBvbiBjeWJlciBhdHRyaWJ1dGlv
biB0byBzb21lIGV4dGVudCBhbmQgYmVsaWV2ZcKgaW4gZ2VuZXJhbCB3aGVuIHdlIGhhdmUg
dGhlIHJpZ2h0IHByb2Nlc3NlcyBpbiBwbGFjZSzCoGF0dHJpYnV0aW9uIGlzIHZlcnkgaW1w
b3J0YW50IGFuZCBjYW4gaG9sZCBjeWJlci1hdHRhY2tlcnMgYWNjb3VudGFibGUuIEkgYW0g
YXdhcmUgb2Ygc29tZSBvZiB0aGUgYXR0cmlidXRpb24gcHJvY2Vzc2VzIGFuZCB1bmZvcnR1
bmF0ZWx5IHNvbWUgdGhyZWF0IGludGVsbGlnZW5jZSBmaXJtcyBhbmQgb3BlbiBzb3VyY2Ug
aW50ZWxsaWdlbmNlIG9yZ2FuaXphdGlvbnMgY2FuIHZpb2xhdGUgdGhlIHByaXZhY3kgb2Yg
aW5kaXZpZHVhbHMgYnkgcHJvZmlsaW5nIHRoZW0uIEFsc28sIHVuY29udHJvbGxlZCBhdHRy
aWJ1dGlvbiBtZWNoYW5pc21zIGNhbiBsZWFkIHRvIGZyaXZvbG91c8KgaW50ZWxsZWN0dWFs
IHByb3BlcnR5IGNsYWltcy4gQm90aCBzb21lIHRocmVhdCBpbnRlbGxpZ2VuY2UgZmlybXMg
YW5kIElQIGZpcm1zIGhhdmUgdXNlZCBXSE9JUyBleHRlbnNpdmVseSBpbiB0aGVpciBmYXZv
ciB0byBhdHRyaWJ1dGUgY3liZXJzZWN1cml0eSBhdHRhY2tzIGFuZCBicmluZyBmb3J3YXJk
IElQIGNsYWltcy4gV0hPSVMgcHJvdG9jb2wgZGlkIG5vdCBoYXZlIHRoZSBpbnRlbnRpb24g
dG8gYWN0dWFsbHkgaWRlbnRpZnkgb3JnYW5pemF0aW9ucyBhbmQgaW5kaXZpZHVhbHMsIGJ1
dCB0byBtYWtlIHRoZW0gImNvbnRhY3RhYmxlIi5hbmQgaXQgd2FzIHN0aWxsIHVzZWQgYW5k
IG1pbmVkIGZvciBzbyBtYW55IHllYXJzIGFuZCB0aG9zZSB3aG8gaGF2ZSBhYnVzZWQgV0hP
SVMgaGF2ZSBub3QgYmVlbiBoZWxkIGFjY291bnRhYmxlLldoZW4geW91IHN1Z2dlc3QgdGhl
eSBjb25zaWRlciAiYXR0cmlidXRpb24iIHdoZW4gZGV2ZWxvcGluZyBwcm90b2NvbHMgaXQN
Cj4gICAgID4gY29uY2VybnMgbWUgYmVjYXVzZSBpdCBpcyBub3QgZW5vdWdoIHRoYXQgeW91
IGxpbWl0IGF0dHJpYnV0aW9uIHRvIG9yZ2FuaXphdGlvbnMgYW5kIHN0YXRlcy4gVGhlc2Ug
a2luZHMgb2YgYXR0cmlidXRpb25zIGNhbiBiZSB1c2VkIGFnYWluc3QgaW5kaXZpZHVhbHMg
YW5kIHVudGlsIHdlIGRvIG5vdCBoYXZlIHRoZSByaWdodCBwcmVzZXJ2aW5nIHByb2Nlc3Nl
cyB0byBwdXQgaW4gcGxhY2UgZm9yIHRob3NlIHdobyB3YW50IHRvIGJlIGluIHRoZSBhdHRy
aWJ1dGlvbiBidXNpbmVzcywgcmlnaHRzIG9mIHRoZSBpbmRpdmlkdWFsIGNhbiBiZSBhdCBy
aXNrLiB0aGVyZSBhcmUgdmVyeSBwcml2YWN5IGNvbnNjaW91c8KgY3liZXJzZWN1cml0eSBy
ZXNlYXJjaGVycyBvdXQgdGhlcmUgYnV0IHVuZm9ydHVuYXRlbHkgdGhhdCBkb2VzIG5vdCBl
bnN1cmUgYSBzeXN0ZW1hdGljwqBwcmFjdGljZSBvZiBhdHRyaWJ1dGlvbiBpbiBhIGZhaXIg
bWFubmVyLiBBbmQgeW91IG1lbnRpb24gYXR0cmlidXRpb24gdG8gYXNzb2NpYXRpb25zIGlz
IGZpbmUgYW5kIG1heSBub3QgZGlyZWN0bHkgbmVnYXRpdmVseSBpbXBhY3QgaHVtYW4gcmln
aHRzLiBBc3NvY2lhdGlvbnMgY2FuIHRoZW1zZWx2ZXMgYmUgYXQgcmlzayBvZiBmcml2b2xv
dXPCoGF0dGFja3MgYW5kIGZyaXZvbG91c8KgYXR0cmlidXRpb24uIEkgYW0gY29uY2VybmVk
IGFib3V0IHRoaXMgcGFyYWdyYXBoLiBJIHRoaW5rIHdlIHNob3VsZCBoYXZlIGEgY29udmVy
c2F0aW9uIGFib3V0IGl0Lg0KPiAgICAgPg0KPiANCj4gICAgIEluIHRoZSBwcm9wb3NlZCB0
ZXh0IEkgdHJpZWQgdG8gY2FwdHVyZSB0aGUgY29uc2Vuc3VzIHRoYXQgZW1lcmdlZCBmcm9t
IHRoZSBleHRlbnNpdmUgZGlzY3Vzc2lvbiB0aGF0IHdhcyBoYWQgb24gdGhpcyBsaXN0LiBE
byB5b3UgaGF2ZSBjb25jcmV0ZSBzdWdnZXN0aW9ucyBvbiBob3cgdG8gYmV0dGVyIGNhcHR1
cmUgdGhhdCBjb25lbnNlbnN1cz8gSSBhbSBhZnJhaWQgd2Ugd291bGQgZ28gYmFjayBhbmQg
cmVwZWF0IHRoZSBzYW1lIGRpc2N1c3Npb24uDQo+IA0KPiAgICAgPiA0LiBOaWNlIHRvIHNl
ZSB0aGF0IHlvdSBtZW50aW9uIERvSC4gSXQncyBhIGdyZWF0IHByaXZhY3kgcHJlc2Vydmlu
ZyBwcm90b2NvbC7CoA0KPiAgICAgPg0KPiAgICAgPg0KPiANCj4gICAgIFRoYW5rcyENCj4g
DQo+ICAgICBOaWVscw0KPiANCj4gICAgID4NCj4gICAgID4NCj4gICAgID4NCj4gICAgID4N
Cj4gICAgID4NCj4gICAgID4NCj4gICAgID4NCj4gICAgID4NCj4gICAgID4gRmFyemFuZWgN
Cj4gICAgID4NCj4gICAgID4NCj4gICAgID4gT24gU2F0LCBKYW4gMzAsIDIwMjEgYXQgMTA6
MzUgQU0gQ29yaW5uZSBDYXRoIDxjb3Jpbm5lY2F0aEBnbWFpbC5jb20gPG1haWx0bzpjb3Jp
bm5lY2F0aEBnbWFpbC5jb20+IDxtYWlsdG86Y29yaW5uZWNhdGhAZ21haWwuY29tIDxtYWls
dG86Y29yaW5uZWNhdGhAZ21haWwuY29tPj4+IHdyb3RlOg0KPiAgICAgPg0KPiAgICAgPsKg
IMKgIMKgSGkgYWxsLA0KPiAgICAgPg0KPiAgICAgPsKgIMKgIMKgSSB0cnVzdCB0aGlzIGVt
YWlsIGZpbmRzIHlvdSB3ZWxsLiBJIGRpZCBhIHJldmlldyBvZiB0aGUgZHJhZnQsIGZyb20g
bXkgcGVyc3BlY3RpdmUgYXMgYW4gYWNhZGVtaWMuIFRha2UgaXQgYXMgeW91IHBsZWFzZS4g
TXkgbWFpbiBjb25jZXJuIGlzIHRoYXQgc29tZSBvZiB0aGUgbGFuZ3VhZ2UgcmVhZHMgYSBi
aXQgZGV0ZXJtaW5pc3RpYyAoYXMsIEkga25vdyBzbyBkb2VzIFJGQyA4MjgwKS4gSXQgbWVh
bnMgdGhhdCBhIGxvdCBvZiBvbnVzIGlzIHB1dCBvbiB0aGUgaW1wYWN0IG9mIGEgcHJvdG9j
b2wsIGFzIG9wcG9zZWQgdGhlIHJvbGUgb2YgdGhlIGluZGl2aWR1YWxzIHRoYXQgd3JpdGUg
dGhlbS7CoA0KPiAgICAgPg0KPiAgICAgPsKgIMKgIMKgSSB0aGluayB0aHJvdWdoIG91dCB0
aGUgZG9jdW1lbnQsIGl0IHdvdWxkIGJlIGludGVyZXN0aW5nIChlc3BlY2lhbGx5IGluIHNl
Y3Rpb24gMSB0aHJvdWdoIDMuMi41KSB0byBzZWUgaWYgeW91IGNhbiByZXdyaXRlIHN1Y2gg
dGhhdCB5b3Ugc3BlYWsgbW9yZSBkaXJlY3RseSB0byB0aGUgcHJvdG9jb2wgZGV2ZWxvcGVy
cy4gSSB0aGluayB0aGF0IHNlY3Rpb24gMy4zIGRvZXMgdGhhdCB3ZWxsLCBpbiB0ZXJtcyBv
ZiB0aGUgdG9uZSBpdCB0YWtlcy4gQXMgaXQgY2xlYXJseSBjb25uZWN0cyB0aGUgYWN0aW9u
cyBvZiBwcm90b2NvbCBkZXZlbG9wZXJzIHRvIHRoZWlyIHBvdGVudGlhbCBvdXRjb21lcy7C
oA0KPiAgICAgPg0KPiAgICAgPsKgIMKgIMKgSG9wZSB0aGlzIGlzIGhlbHBmdWwhwqANCj4g
ICAgID4NCj4gICAgID7CoCDCoCDCoEtpbmQgcmVnYXJkcyzCoA0KPiAgICAgPg0KPiAgICAg
PsKgIMKgIMKgQ29yaW5uZQ0KPiAgICAgPg0KPiAgICAgPsKgIMKgIMKgLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ICAgICA+DQo+ICAgICA+wqAgwqAgwqAqMS4gSW50
cm9kdWN0aW9uKg0KPiAgICAgPg0KPiAgICAgPsKgIMKgIMKgIkl0IHByb3ZpZGVzIHF1ZXN0
aW9ucyBlbmdpbmVlcnMgc2hvdWxkIGFzaw0KPiAgICAgPg0KPiAgICAgPsKgIMKgIMKgIMKg
IHRoZW1zZWx2ZXMgd2hlbiBkZXZlbG9waW5nIG9yIGltcHJvdmluZyBwcm90b2NvbHMgaWYg
dGhleSB3YW50IHRvDQo+ICAgICA+wqAgwqAgwqAgwqAgdW5kZXJzdGFuZCB0aGVpciBwb3Rl
bnRpYWwgaHVtYW4gcmlnaHRzIGltcGFjdC4iDQo+ICAgICA+DQo+ICAgICA+DQo+ICAgICA+
wqAgwqAgwqA+PiBtYXliZSBpZiB0aGV5IHdhbnQgdG8gdW5kZXJzdGFuZCBwb3RlbnRpYWwg
aHVtYW4gcmlnaHRzIGNvbmNlcm5zPyBJbXBhY3Qgc2VlbXMgYSBsaXR0bGUgZGV0ZXJtaW5p
c3RpYywgYXMgeW91IGFsc28gbWVudGlvbiBpbiB0aGUgbmV4dCBzZW50ZW5jZSwgSSB3b25k
ZXIgaWYgeW91IGNhbiBwcm92ZSBzdWNoIGRpcmVjdCBpbXBhY3QgYmV0d2VlbiBwcm90b2Nv
bCBkZXZlbG9wbWVudCBpbiB0aGUgSUVURiBhbmQgaW1wYWN0IG9uIGh1bWFuIHJpZ2h0cy4N
Cj4gICAgID4NCj4gICAgID7CoCDCoCDCoCJUaGUgcmVzZWFyY2ggZXN0YWJsaXNoZXMNCj4g
ICAgID4NCj4gICAgID7CoCDCoCDCoCDCoCB0aGF0IGh1bWFuIHJpZ2h0cyByZWxhdGUgdG8g
c3RhbmRhcmRzIGFuZCBwcm90b2NvbHMsIGFuZCBvZmZlcnMgYQ0KPiAgICAgPsKgIMKgIMKg
IMKgIGNvbW1vbiB2b2NhYnVsYXJ5IG9mIHRlY2huaWNhbCBjb25jZXB0cyB0aGF0IGltcGFj
dCBodW1hbiByaWdodHMgYW5kDQo+ICAgICA+wqAgwqAgwqAgwqAgaG93IHRoZXNlIHRlY2hu
aWNhbCBjb25jZXB0cyBjYW4gYmUgY29tYmluZWQgdG8gZW5zdXJlIHRoYXQgdGhlDQo+ICAg
ICA+wqAgwqAgwqAgwqAgSW50ZXJuZXQgcmVtYWlucyBhbiBlbmFibGluZyBlbnZpcm9ubWVu
dCBmb3IgaHVtYW4gcmlnaHRzLiINCj4gICAgID4NCj4gICAgID4NCj4gICAgID7CoCDCoCDC
oD4+IHNhbWUgY29tbWVudCBmb3IgdGhlIHdvcmQgaW1wYWN0LCBwZXJoYXBzIHNoYXBlPyBp
bmZsdWVuY2U/IGV0Yy4NCj4gICAgID4NCj4gICAgID4NCj4gICAgID7CoCDCoCDCoCDCoCDC
oCDCoDMuMSA8aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlydGYtaHJwYy1n
dWlkZWxpbmVzLTA1I3NlY3Rpb24tMy4xIDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaXJ0Zi1ocnBjLWd1aWRlbGluZXMtMDUjc2VjdGlvbi0zLjE+Pi4gSHVtYW4gcmln
aHRzIHRocmVhdHMNCj4gICAgID4NCj4gICAgID4NCj4gICAgID4NCj4gICAgID7CoCDCoCDC
oCAiUHJvdG9jb2xzIGFuZCBzdGFuZGFyZHMgY2FuIGhhcm0gb3IgZW5hYmxlIHRoZSByaWdo
dCB0byBmcmVlZG9tIG9mDQo+ICAgICA+wqAgwqAgwqAgwqAgZXhwcmVzc2lvbiwgcmlnaHQg
dG8gbm9uLWRpc2NyaW1pbmF0aW9uLCByaWdodCB0byBlcXVhbCBwcm90ZWN0aW9uLA0KPiAg
ICAgPsKgIMKgIMKgIMKgIHJpZ2h0IHRvIHBhcnRpY2lwYXRlIGluIGN1bHR1cmFsIGxpZmUs
IGFydHMgYW5kIHNjaWVuY2UsIHJpZ2h0IHRvDQo+ICAgICA+DQo+ICAgICA+wqAgwqAgwqBm
cmVlZG9tIG9mIGFzc2VtYmx5IGFuZCBhc3NvY2lhdGlvbiwgYW5kIHRoZSByaWdodCB0byBz
ZWN1cml0eS4gIg0KPiAgICAgPg0KPiAgICAgPg0KPiAgICAgPsKgIMKgIMKgPj4gYWdhaW4s
IGRldGVybWluaXN0aWMgbGFuZ3VhZ2UuIFBlcmhhcHMgc29mdGVuIG9yIGFkZCBtb3JlIGNv
bmNyZXRlIGV4YW1wbGVzIGZvciBjb250ZXh0LCB0aGF0IGRyYXcgZnJvbSBjdXJyZW50IElF
VEYgZGlzY3Vzc2lvbnMvc3RhbmRhcmRzLg0KPiAgICAgPg0KPiAgICAgPg0KPiAgICAgPg0K
PiAgICAgPsKgIMKgIMKgIMKgIMKgIMKgMy4zIDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtaXJ0Zi1ocnBjLWd1aWRlbGluZXMtMDUjc2VjdGlvbi0zLjMgPGh0dHBzOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pcnRmLWhycGMtZ3VpZGVsaW5lcy0wNSNzZWN0
aW9uLTMuMz4+LiBHdWlkZWxpbmVzIGZvciBodW1hbiByaWdodHMgY29uc2lkZXJhdGlvbnMN
Cj4gICAgID4NCj4gICAgID4NCj4gICAgID4NCj4gICAgID7CoCDCoCDCoGFnYWluLCB1c2Ug
b2YgdGhlIHdvcmQgaW1wYWN0IGluIHRoZSBpbnRyb2R1Y3Rpb24uDQo+ICAgICA+DQo+ICAg
ICA+DQo+ICAgICA+DQo+ICAgICA+DQo+ICAgICA+wqAgwqAgwqAtLQ0KPiAgICAgPsKgIMKg
IMKgQ29yaW5uZSBDYXRoIC0gU3BldGgNCj4gICAgID7CoCDCoCDCoFBoLkQuIENhbmRpZGF0
ZSwgT3hmb3JkIEludGVybmV0IEluc3RpdHV0ZSAmIEFsYW4gVHVyaW5nIEluc3RpdHV0ZQ0K
PiAgICAgPg0KPiAgICAgPsKgIMKgIMKgV2ViOiB3d3cub2lpLm94LmFjLnVrL3Blb3BsZS9j
b3Jpbm5lLWNhdGggPGh0dHA6Ly93d3cub2lpLm94LmFjLnVrL3Blb3BsZS9jb3Jpbm5lLWNh
dGg+IDxodHRwOi8vd3d3Lm9paS5veC5hYy51ay9wZW9wbGUvY29yaW5uZS1jYXRoIDxodHRw
Oi8vd3d3Lm9paS5veC5hYy51ay9wZW9wbGUvY29yaW5uZS1jYXRoPj4NCj4gICAgID7CoCDC
oCDCoEVtYWlsOiBjY2F0aEB0dXJpbmcuYWMudWsgPG1haWx0bzpjY2F0aEB0dXJpbmcuYWMu
dWs+IDxtYWlsdG86Y2NhdGhAdHVyaW5nLmFjLnVrIDxtYWlsdG86Y2NhdGhAdHVyaW5nLmFj
LnVrPj4gJiBjb3Jpbm5lY2F0aEBnbWFpbC5jb20gPG1haWx0bzpjb3Jpbm5lY2F0aEBnbWFp
bC5jb20+IDxtYWlsdG86Y29yaW5uZWNhdGhAZ21haWwuY29tIDxtYWlsdG86Y29yaW5uZWNh
dGhAZ21haWwuY29tPj4NCj4gICAgID7CoCDCoCDCoFR3aXR0ZXI6IEBDX0NTDQo+ICAgICA+
wqAgwqAgwqBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiAgICAgPsKgIMKgIMKgaHJwYyBtYWlsaW5nIGxpc3QNCj4gICAgID7CoCDCoCDCoGhy
cGNAaXJ0Zi5vcmcgPG1haWx0bzpocnBjQGlydGYub3JnPiA8bWFpbHRvOmhycGNAaXJ0Zi5v
cmcgPG1haWx0bzpocnBjQGlydGYub3JnPj4NCj4gICAgID7CoCDCoCDCoGh0dHBzOi8vd3d3
LmlydGYub3JnL21haWxtYW4vbGlzdGluZm8vaHJwYyA8aHR0cHM6Ly93d3cuaXJ0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9ocnBjPiA8aHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9ocnBjIDxodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2hy
cGM+Pg0KPiAgICAgPg0KPiAgICAgPg0KPiAgICAgPiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KPiAgICAgPiBocnBjIG1haWxpbmcgbGlzdA0K
PiAgICAgPiBocnBjQGlydGYub3JnIDxtYWlsdG86aHJwY0BpcnRmLm9yZz4NCj4gICAgID4g
aHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ocnBjIDxodHRwczovL3d3
dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2hycGM+DQo+ICAgICA+DQo+IA0KPiAgICAg
LS0gDQo+ICAgICBOaWVscyB0ZW4gT2V2ZXIsIFBoRA0KPiAgICAgUG9zdGRvY3RvcmFsIFJl
c2VhcmNoZXIgLSBNZWRpYSBTdHVkaWVzIERlcGFydG1lbnQgLSBVbml2ZXJzaXR5IG9mIEFt
c3RlcmRhbQ0KPiAgICAgUG9zdGRvY3RvcmFsIFJlc2VhcmNoIEZlbGxvdyAtIENvbW11bmlj
YXRpb25zIERlcGFydG1lbnQgLSBUZXhhcyBBJk0gVW5pdmVyc2l0eQ0KPiAgICAgUmVzZWFy
Y2ggRmVsbG93IC0gQ2VudHJlIGZvciBJbnRlcm5ldCBhbmQgSHVtYW4gUmlnaHRzIC0gRXVy
b3BlYW4gVW5pdmVyc2l0eSBWaWFkcmluYQ0KPiAgICAgQXNzb2NpYXRlZCBTY2hvbGFyIC0g
Q2VudHJvIGRlIFRlY25vbG9naWEgZSBTb2NpZWRhZGUgLSBGdW5kYcOnw6NvIEdldMO6bGlv
IFZhcmdhcw0KPiANCj4gICAgIFc6IGh0dHBzOi8vbmllbHN0ZW5vZXZlci5uZXQgPGh0dHBz
Oi8vbmllbHN0ZW5vZXZlci5uZXQ+DQo+ICAgICBFOiBtYWlsQG5pZWxzdGVub2V2ZXIubmV0
IDxtYWlsdG86bWFpbEBuaWVsc3Rlbm9ldmVyLm5ldD4NCj4gICAgIFQ6IEBuaWVsc3Rlbm9l
dmVyDQo+ICAgICBQL1MvV0E6ICszMTYyOTA1MTg1Mw0KPiAgICAgUEdQOiAyNDU4IDBCNzAg
NUM0QSBGRDhBIDk0ODggNjQzQSAwRUQ4IDNGM0EgNDY4QSBDOEIzDQo+IA0KPiAgICAgUmVh
ZCBteSBkaXNzZXJ0YXRpb24gJ1dpcmVkIE5vcm1zJyBoZXJlOiBodHRwczovL3B1cmUudXZh
Lm5sL3dzL2ZpbGVzLzUwNzgxOTYxL1RoZXNpcy5wZGYgPGh0dHBzOi8vcHVyZS51dmEubmwv
d3MvZmlsZXMvNTA3ODE5NjEvVGhlc2lzLnBkZj4NCj4gICAgIF9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ICAgICBocnBjIG1haWxpbmcgbGlz
dA0KPiAgICAgaHJwY0BpcnRmLm9yZyA8bWFpbHRvOmhycGNAaXJ0Zi5vcmc+DQo+ICAgICBo
dHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2hycGMgPGh0dHBzOi8vd3d3
LmlydGYub3JnL21haWxtYW4vbGlzdGluZm8vaHJwYz4NCj4gDQoNCi0tIA0KTmllbHMgdGVu
IE9ldmVyLCBQaEQNClBvc3Rkb2N0b3JhbCBSZXNlYXJjaGVyIC0gTWVkaWEgU3R1ZGllcyBE
ZXBhcnRtZW50IC0gVW5pdmVyc2l0eSBvZiBBbXN0ZXJkYW0NClBvc3Rkb2N0b3JhbCBSZXNl
YXJjaCBGZWxsb3cgLSBDb21tdW5pY2F0aW9ucyBEZXBhcnRtZW50IC0gVGV4YXMgQSZNIFVu
aXZlcnNpdHkNClJlc2VhcmNoIEZlbGxvdyAtIENlbnRyZSBmb3IgSW50ZXJuZXQgYW5kIEh1
bWFuIFJpZ2h0cyAtIEV1cm9wZWFuIFVuaXZlcnNpdHkgVmlhZHJpbmENCkFzc29jaWF0ZWQg
U2Nob2xhciAtIENlbnRybyBkZSBUZWNub2xvZ2lhIGUgU29jaWVkYWRlIC0gRnVuZGHDp8Oj
byBHZXTDumxpbyBWYXJnYXMNCg0KVzogaHR0cHM6Ly9uaWVsc3Rlbm9ldmVyLm5ldA0KRTog
bWFpbEBuaWVsc3Rlbm9ldmVyLm5ldA0KVDogQG5pZWxzdGVub2V2ZXINClAvUy9XQTogKzMx
NjI5MDUxODUzDQpQR1A6IDI0NTggMEI3MCA1QzRBIEZEOEEgOTQ4OCA2NDNBIDBFRDggM0Yz
QSA0NjhBIEM4QjMNCg0KUmVhZCBteSBkaXNzZXJ0YXRpb24gJ1dpcmVkIE5vcm1zJyBoZXJl
OiBodHRwczovL3B1cmUudXZhLm5sL3dzL2ZpbGVzLzUwNzgxOTYxL1RoZXNpcy5wZGYNCg==


From nobody Mon Feb  1 13:22:51 2021
Return-Path: <farzaneh.badii@gmail.com>
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 1A8713A14C2 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 13:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level: 
X-Spam-Status: No, score=-1.097 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, FREEMAIL_REPLY=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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zWJRkkRJTV7T for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 13:22:47 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 668D03A14C1 for <hrpc@irtf.org>; Mon,  1 Feb 2021 13:22:46 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id s18so21470672ljg.7 for <hrpc@irtf.org>; Mon, 01 Feb 2021 13:22:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SIYLiVz0s7vCqoOT2uRwUTblzCId846Chfm6+mhTDpE=; b=YKtcimzKsCBGsCPSgGZMMgWGMibyfL+nRXPZsf9qrrW0O3LNKEHkoKlIYIPdvAVsoE 5bXJ4c9LW+U5t70KSMYTY17S3fIJT6D7UiLuOkyEshqYZd/Yht9ZV83myXuM9IvD5vsk trZB0AW1yeFDIXaiCGdmSFdGKQq46IaHpFh332uRGK3Puxk9aNQqGkjqIAtYJvUS8L94 xbGfongjd4IlAoRsXor7Iv4aYolyrX4DYrSTLb/QgrXQd/LNQyrf5m8HdpALdoXtk8bG d0umIoujNJnB2tHLe+8G5BXYqYo0zM+htrhTmzpPtWc6xDLnOhDDrIroib2wwhisGBTr mVpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SIYLiVz0s7vCqoOT2uRwUTblzCId846Chfm6+mhTDpE=; b=Ij7K68w8BAcHt+QLCqiHiwr1B1H2kGbynB37wGnA4KH7Rab5YMdsXQF23piPVwRw1d A1uy7x7bCBXvRDIghQJEYD7ZW3fs4jLhc5mJB8Pf2c+z6t7c7Fdh74/mMxv5sDItw3Cw nUmLxsx+PR/cdCOB6qpXjMYp3v0zInMGrYSTU+NhlgUGJU87kTSQJst2wuWMQEY+gvIY eowMDaddAu6Tr5QRU0m/wPKODoHoU6YneScZYH7RKep9FoedI1kUK5whV7Pe4Gd0VqTh QCYB3O71DPmLsfMADydem6XAZmcFa/Xr+S/OBXGa5gAr6Z2GgYg5JALck5a/JEPtSCup jgGg==
X-Gm-Message-State: AOAM532muRcRjHxQm2xLJPvMR9ncx0UpPkVE4BPNakC3IyZz2EWhrj56 DK0VCea4ct/EYuoykoMh3mEADvnrtnQm7bCksZI=
X-Google-Smtp-Source: ABdhPJyfM8U1UDhER42XBrIxjrTFpxOgPtqRkeOAV0CNoUWlX90WBjZ/0dgVRyfZsqrT0ATW02S7G+wGN5ONcUS8S/s=
X-Received: by 2002:a2e:804a:: with SMTP id p10mr2835035ljg.226.1612214564337;  Mon, 01 Feb 2021 13:22:44 -0800 (PST)
MIME-Version: 1.0
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <08b61ab2-7840-d993-9946-c085861f4172@nielstenoever.net> <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com> <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net>
In-Reply-To: <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Mon, 1 Feb 2021 16:22:17 -0500
Message-ID: <CAN1qJvCsbfnVePRFYAsySrgtaumUARc8PpnAX-cANu5Pgc7TMA@mail.gmail.com>
To: Niels ten Oever <mail@nielstenoever.net>
Cc: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000068ba8605ba4cf4d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Ujpd-39xZM64755E0W7GqxY50Ho>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 21:22:50 -0000

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

Here we go:


Question(s): Can your protocol facilitate a negatively impacted

   party's right to the appropriate  legal remedy without
disproportionately impacting

   other parties' human rights, especially their right to privacy?


   Explanation: Access to legal remedy is a human right that ensures

   that individuals whose rights have been violated can seek remedies




   through a judicial authority.  Attribution (i.e. mechanisms in

   protocols or architectures that are designed to make communications

   or artifacts attributable might help with seeking the appropriate remedy
.) to a certain computer or individual) can be

   a part of this, since it may allow law enforcement agencies to

   identify a possible violator.  However, attribution mechanisms may

   impede the exercise of the right to privacy.  The Special Rapporteur

   for Freedom of Expression has also argued that anonymity is an

   inherent part of freedom of expression.  [Kaye] Considering the

   adverse impact of attribution on the right to privacy and freedom of

   expression, attribution on an individual level may is not be consistent

   with human rights.  However, attribution to corporate entities,

   associations, and/or countries may not directly negatively impact

   human rights.


   Impacts:


   -  Right to legal remedy


   -  Right to security
Farzaneh


On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever <mail@nielstenoever.net>
wrote:

> Hi Farzaneh,
>
> On 31-01-2021 19:16, farzaneh badii wrote:
> > Hello Niels.
> >
> >
> > I don't know how we measure consensus here. But I remember weighing in
> back then as well(When Mr. Curran weighed in back in 2019). Here is the
> thread: https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution <
> https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution>
> >
> > I can see that unfortunately I missed the discussion on this topic
> during the past year, and that's my fault, but I can bring reasons not to
> add "attribution and legal remedy" to this document at all.
> >
> > 1. Access to legal remedy is something that the States are supposedly i=
n
> charge of bringing to their citizens.Which should (in theory) ensure that
> human rights are enforced. I don't think there was an intention to
> provide  mechanisms for "enforcement" of human rights in various legal
> systems through Internet protocols. As mentioned in the beginning of your
> document:
> > "Human rights threats on the Internet come in a myriad of
> forms.* **P**rotocols and standards can harm or enable* the right to
> freedom of expression, right to non-discrimination, right to equal
> protection, right to participate in cultural life, arts and science, righ=
t
> to freedom of assembly and association, and the right to security."
> >
> > So we are not in the business of enforcing but providing an enabling
> environment. Because if we want to help law enforcement and the judicial
> authorities enforce human rights through Internet protocols we should bea=
r
> in mind that that they are not always staunch advocates of human rights. =
So
> what I assume we are trying to do here is to help Internet protocol not t=
o
> facilitate harm and "enable" human rights.
> >
>
> The text in the draft seeks to address this risk. I have sought to addres=
s
> all points made in that discussion, and I would not like to re-open that
> debate. If you feel the text is unbalanced, could you perhaps provide tex=
t
> suggestions?
>
> > 2. Attribution, section 3.3.20  of the Guideline, the authors assert
> that: "However, attribution to corporate entities, associations, and/or
> countries may not directly negatively impact human rights." I think this =
is
> not a very well backed up claim. Because in some cases some associations
> might be political or they might be human rights associations dealing wit=
h
> a dictatorship. Attribution to those associations certainly can impact
> their human rights negatively. Even when it comes to corporations, some
> CEOs of digital companies are put in jail because of the materials posted
> on their websites. I don't think we can argue that attribution to corpora=
te
> entities might not adversely impact human rights.
> >
>
> Again, the keyword in that sentence is 'may', so there is no strong claim
> made.
>
> > All in all I think section 3.3.20 does not help Internet Protocols
> enable human rights and it can be misinterpreted.
>
> I think the text in there is not strong and shows different perspectives
> and potential consequences. But again, happy to receive text suggestions.
>
> >
> > And in my previous email I talked about the problems with threat
> intelligence agencies and some of their conducts and the use of WHOIS for
> attribution (which was actually not designed to "identify" actors but
> unfortunately was used for that) so I will not reiterate here.
>
> From exactly that discussion we got the idea to remove individuals, and
> leave non-natural persons in.
>
> Best,
>
> Niels
>
> >
> >
> >
> >
> >
> >
> >
> > On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever <mail@nielstenoever.net
> <mailto:mail@nielstenoever.net>> wrote:
> >
> >     Hi Farzaneh,
> >
> >     Thanks a lot for the review!
> >
> >     On 30-01-2021 23:00, farzaneh badii wrote:
> >     > Hello
> >     >
> >     > Adding my comments on this document:
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05 <
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05> <
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05 <
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>>
> >     >
> >     > 1. One major issue that I see here and you might be able to easil=
y
> solve it is that there is no distinction between user facing protocols an=
d
> other protocols. For example, you ask for accessibility and consideration
> of culture etc. Are you asking all the protocols to be provided in multip=
le
> languages, even those that only developers and implementers use and not t=
he
> actual users? You might want to clarify that.
> >     >
> >
> >     We had a quite extensive discussion about this in relation to the
> presentation by Ramsey Nasr who create Qalb, an Arabic programming
> language. Programmers are the most frequent 'users' of protocols - if we
> continue using only latin characters and English documentation in protoco=
ls
> we are likely to reproduce the existing lack of diversity in protocol
> developers communities. But we can make the text on this clearer as well!
> >
> >     > 2.section 3.3.1 on connectivity, you mention that "considering th=
e
> fact that network quality and conditions vary across geography and time i=
t
> is also important to design protocols such that they are reliable even on
> low bandwidth ...". Then in your example you say: Middleboxes (including
> NAT).... can create potential for abuse. NAT is a Network Address
> Translation protocol. I don't think it has anything to do with bandwidth.
> In this example you also mention CDNs. Are you suggesting that the
> developer should not consider "Middleboxes" protocols? I think you need t=
o
> work on the example of section 3.3.1 some more to make it clearer.
> >     >
> >
> >     Excellent point - we'll address this in a future version.
> >
> >     > 3. section 3.3.20 remedy and attribution
> >     > This section worries me. As a  scholar I have worked on cyber
> attribution to some extent and believe in general when we have the right
> processes in place, attribution is very important and can hold
> cyber-attackers accountable. I am aware of some of the attribution
> processes and unfortunately some threat intelligence firms and open sourc=
e
> intelligence organizations can violate the privacy of individuals by
> profiling them. Also, uncontrolled attribution mechanisms can lead to
> frivolous intellectual property claims. Both some threat intelligence fir=
ms
> and IP firms have used WHOIS extensively in their favor to attribute
> cybersecurity attacks and bring forward IP claims. WHOIS protocol did not
> have the intention to actually identify organizations and individuals, bu=
t
> to make them "contactable".and it was still used and mined for so many
> years and those who have abused WHOIS have not been held accountable.When
> you suggest they consider "attribution" when developing protocols it
> >     > concerns me because it is not enough that you limit attribution t=
o
> organizations and states. These kinds of attributions can be used against
> individuals and until we do not have the right preserving processes to pu=
t
> in place for those who want to be in the attribution business, rights of
> the individual can be at risk. there are very privacy
> conscious cybersecurity researchers out there but unfortunately that does
> not ensure a systematic practice of attribution in a fair manner. And you
> mention attribution to associations is fine and may not directly negative=
ly
> impact human rights. Associations can themselves be at risk of
> frivolous attacks and frivolous attribution. I am concerned about this
> paragraph. I think we should have a conversation about it.
> >     >
> >
> >     In the proposed text I tried to capture the consensus that emerged
> from the extensive discussion that was had on this list. Do you have
> concrete suggestions on how to better capture that conensensus? I am afra=
id
> we would go back and repeat the same discussion.
> >
> >     > 4. Nice to see that you mention DoH. It's a great privacy
> preserving protocol.
> >     >
> >     >
> >
> >     Thanks!
> >
> >     Niels
> >
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >     > Farzaneh
> >     >
> >     >
> >     > On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath <
> corinnecath@gmail.com <mailto:corinnecath@gmail.com> <mailto:
> corinnecath@gmail.com <mailto:corinnecath@gmail.com>>> wrote:
> >     >
> >     >     Hi all,
> >     >
> >     >     I trust this email finds you well. I did a review of the
> draft, from my perspective as an academic. Take it as you please. My main
> concern is that some of the language reads a bit deterministic (as, I kno=
w
> so does RFC 8280). It means that a lot of onus is put on the impact of a
> protocol, as opposed the role of the individuals that write them.
> >     >
> >     >     I think through out the document, it would be interesting
> (especially in section 1 through 3.2.5) to see if you can rewrite such th=
at
> you speak more directly to the protocol developers. I think that section
> 3.3 does that well, in terms of the tone it takes. As it clearly connects
> the actions of protocol developers to their potential outcomes.
> >     >
> >     >     Hope this is helpful!
> >     >
> >     >     Kind regards,
> >     >
> >     >     Corinne
> >     >
> >     >     ---------------------------------
> >     >
> >     >     *1. Introduction*
> >     >
> >     >     "It provides questions engineers should ask
> >     >
> >     >        themselves when developing or improving protocols if they
> want to
> >     >        understand their potential human rights impact."
> >     >
> >     >
> >     >     >> maybe if they want to understand potential human rights
> concerns? Impact seems a little deterministic, as you also mention in the
> next sentence, I wonder if you can prove such direct impact between
> protocol development in the IETF and impact on human rights.
> >     >
> >     >     "The research establishes
> >     >
> >     >        that human rights relate to standards and protocols, and
> offers a
> >     >        common vocabulary of technical concepts that impact human
> rights and
> >     >        how these technical concepts can be combined to ensure tha=
t
> the
> >     >        Internet remains an enabling environment for human rights.=
"
> >     >
> >     >
> >     >     >> same comment for the word impact, perhaps shape? influence=
?
> etc.
> >     >
> >     >
> >     >           3.1 <
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1 <
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1>>.
> Human rights threats
> >     >
> >     >
> >     >
> >     >      "Protocols and standards can harm or enable the right to
> freedom of
> >     >        expression, right to non-discrimination, right to equal
> protection,
> >     >        right to participate in cultural life, arts and science,
> right to
> >     >
> >     >     freedom of assembly and association, and the right to
> security. "
> >     >
> >     >
> >     >     >> again, deterministic language. Perhaps soften or add more
> concrete examples for context, that draw from current IETF
> discussions/standards.
> >     >
> >     >
> >     >
> >     >           3.3 <
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3 <
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3>>.
> Guidelines for human rights considerations
> >     >
> >     >
> >     >
> >     >     again, use of the word impact in the introduction.
> >     >
> >     >
> >     >
> >     >
> >     >     --
> >     >     Corinne Cath - Speth
> >     >     Ph.D. Candidate, Oxford Internet Institute & Alan Turing
> Institute
> >     >
> >     >     Web: www.oii.ox.ac.uk/people/corinne-cath <
> http://www.oii.ox.ac.uk/people/corinne-cath> <
> http://www.oii.ox.ac.uk/people/corinne-cath <
> http://www.oii.ox.ac.uk/people/corinne-cath>>
> >     >     Email: ccath@turing.ac.uk <mailto:ccath@turing.ac.uk> <mailto=
:
> ccath@turing.ac.uk <mailto:ccath@turing.ac.uk>> & corinnecath@gmail.com
> <mailto:corinnecath@gmail.com> <mailto:corinnecath@gmail.com <mailto:
> corinnecath@gmail.com>>
> >     >     Twitter: @C_CS
> >     >     _______________________________________________
> >     >     hrpc mailing list
> >     >     hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:hrpc@irtf.org
> <mailto:hrpc@irtf.org>>
> >     >     https://www.irtf.org/mailman/listinfo/hrpc <
> https://www.irtf.org/mailman/listinfo/hrpc> <
> https://www.irtf.org/mailman/listinfo/hrpc <
> https://www.irtf.org/mailman/listinfo/hrpc>>
> >     >
> >     >
> >     > _______________________________________________
> >     > hrpc mailing list
> >     > hrpc@irtf.org <mailto:hrpc@irtf.org>
> >     > https://www.irtf.org/mailman/listinfo/hrpc <
> https://www.irtf.org/mailman/listinfo/hrpc>
> >     >
> >
> >     --
> >     Niels ten Oever, PhD
> >     Postdoctoral Researcher - Media Studies Department - University of
> Amsterdam
> >     Postdoctoral Research Fellow - Communications Department - Texas A&=
M
> University
> >     Research Fellow - Centre for Internet and Human Rights - European
> University Viadrina
> >     Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=
=C3=A3o
> Get=C3=BAlio Vargas
> >
> >     W: https://nielstenoever.net <https://nielstenoever.net>
> >     E: mail@nielstenoever.net <mailto:mail@nielstenoever.net>
> >     T: @nielstenoever
> >     P/S/WA: +31629051853
> >     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
> >
> >     Read my dissertation 'Wired Norms' here:
> https://pure.uva.nl/ws/files/50781961/Thesis.pdf <
> https://pure.uva.nl/ws/files/50781961/Thesis.pdf>
> >     _______________________________________________
> >     hrpc mailing list
> >     hrpc@irtf.org <mailto:hrpc@irtf.org>
> >     https://www.irtf.org/mailman/listinfo/hrpc <
> https://www.irtf.org/mailman/listinfo/hrpc>
> >
>
> --
> Niels ten Oever, PhD
> Postdoctoral Researcher - Media Studies Department - University of
> Amsterdam
> Postdoctoral Research Fellow - Communications Department - Texas A&M
> University
> Research Fellow - Centre for Internet and Human Rights - European
> University Viadrina
> Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=A3=
o Get=C3=BAlio
> Vargas
>
> W: https://nielstenoever.net
> E: mail@nielstenoever.net
> T: @nielstenoever
> P/S/WA: +31629051853
> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>
> Read my dissertation 'Wired Norms' here:
> https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">Here we go:</div><div class=3D"gmail_default" style=3D"font-fam=
ily:verdana,sans-serif"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:verdana,sans-serif"></div><div class=3D"gmail_default" style=3D"fo=
nt-family:verdana,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:verdana,sans-serif">





<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica">Question(s): Can your protocol facilitate a neg=
atively impacted</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>party&#39;s right to<font color=3D"#ff0000">=C2=A0the appr=
opriate </font><strike>=C2=A0legal </strike>remedy without disproportionate=
ly impacting</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>other parties&#39; human rights, especially their right to=
 privacy?</p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>Explanation: Access to legal remedy is a human rig=
ht that ensures</strike></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>that individuals whose rights have been violated c=
an seek remedies</strike></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>through a judicial authority.</strike><span class=
=3D"gmail-Apple-converted-space">=C2=A0 </span>Attribution (i.e. mechanisms=
 in</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>protocols or architectures that are designed to make commu=
nications</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>or artifacts attributable <font color=3D"#ff0000">might he=
lp with seeking the appropriate remedy</font>.)=C2=A0<strike>to a certain c=
omputer or individual)</strike> <strike>can be</strike></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>a part of this, since it may allow law enforcement=
 agencies to</strike></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>identify a possible violator</strike>.<span class=
=3D"gmail-Apple-converted-space">=C2=A0 </span>However, attribution mechani=
sms may</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>impede the exercise of the right to privacy.<span class=3D=
"gmail-Apple-converted-space">=C2=A0 </span>The Special Rapporteur</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>for Freedom of Expression has also argued that anonymity i=
s an</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>inherent part of freedom of expression.<span class=3D"gmai=
l-Apple-converted-space">=C2=A0 </span>[Kaye] Considering the</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>adverse impact of attribution on the right to privacy and =
freedom of</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>expression, attribution on an individual level<strike> may=
</strike>=C2=A0<font color=3D"#ff0000">is=C2=A0</font>not <strike>be</strik=
e> consistent</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>with human rights.<span class=3D"gmail-Apple-converted-spa=
ce">=C2=A0<strike> </strike></span><strike>However, attribution to corporat=
e entities,</strike></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>associations, and/or countries may not directly ne=
gatively impact</strike></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>human rights.</strike></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>Impacts:</p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica;min-height:14px"><strike><br></strike></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><strike><span class=3D"gmail-Apple-converted-sp=
ace">=C2=A0=C2=A0 </span>-<span class=3D"gmail-Apple-converted-space">=C2=
=A0 </span>Right to legal remedy</strike></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">=C2=
=A0=C2=A0 </span>-<span class=3D"gmail-Apple-converted-space">=C2=A0 </span=
>Right to security</p></div><div><div dir=3D"ltr" class=3D"gmail_signature"=
 data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><font face=3D"ver=
dana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 1=
, 2021 at 2:38 PM Niels ten Oever &lt;<a href=3D"mailto:mail@nielstenoever.=
net">mail@nielstenoever.net</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">Hi Farzaneh,<br>
<br>
On 31-01-2021 19:16, farzaneh badii wrote:<br>
&gt; Hello Niels.<br>
&gt; <br>
&gt; <br>
&gt; I don&#39;t know how we measure consensus here. But I remember weighin=
g in back then as well(When Mr. Curran weighed in back in 2019). Here is th=
e thread:=C2=A0<a href=3D"https://mailarchive.ietf.org/arch/browse/hrpc/?q=
=3Dattribution" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ie=
tf.org/arch/browse/hrpc/?q=3Dattribution</a> &lt;<a href=3D"https://mailarc=
hive.ietf.org/arch/browse/hrpc/?q=3Dattribution" rel=3D"noreferrer" target=
=3D"_blank">https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution<=
/a>&gt;<br>
&gt; <br>
&gt; I can see that unfortunately I missed the=C2=A0discussion on this topi=
c during the past year, and that&#39;s my fault, but I can bring reasons no=
t to add &quot;attribution and legal remedy&quot; to this document at all.=
=C2=A0<br>
&gt; <br>
&gt; 1. Access to legal remedy is something that the States are supposedly =
in charge of bringing to their citizens.Which should (in theory) ensure tha=
t human rights are enforced. I don&#39;t think there=C2=A0was an intention =
to=C2=A0 provide=C2=A0 mechanisms for &quot;enforcement&quot; of human righ=
ts in various legal systems through Internet protocols. As mentioned=C2=A0i=
n the beginning of your document:=C2=A0<br>
&gt; &quot;Human rights threats on the Internet come in a myriad of forms.*=
=C2=A0**P**rotocols and standards can harm or enable* the right to freedom =
of=C2=A0expression, right to non-discrimination, right to equal protection,=
=C2=A0right to participate in cultural life, arts and science, right to=C2=
=A0freedom of assembly and association, and the right to security.&quot;=C2=
=A0<br>
&gt; <br>
&gt; So we are not in the business of enforcing but providing=C2=A0an enabl=
ing environment. Because=C2=A0if we want to help law enforcement and the ju=
dicial authorities enforce human rights through=C2=A0Internet=C2=A0protocol=
s we should bear in mind that that they are not always staunch advocates of=
 human rights. So what I assume we are trying to do here is to help Interne=
t protocol not to facilitate harm and &quot;enable&quot; human rights.=C2=
=A0<br>
&gt; <br>
<br>
The text in the draft seeks to address this risk. I have sought to address =
all points made in that discussion, and I would not like to re-open that de=
bate. If you feel the text is unbalanced, could you perhaps provide text su=
ggestions? <br>
<br>
&gt; 2. Attribution, section 3.3.20=C2=A0 of the Guideline, the authors ass=
ert that: &quot;However, attribution to corporate entities,=C2=A0associatio=
ns, and/or countries may not directly negatively impact=C2=A0human rights.&=
quot; I think this is not a very=C2=A0well backed up claim. Because in some=
 cases some associations might be political or they might be human rights a=
ssociations dealing with a dictatorship. Attribution to those associations =
certainly can impact their human rights negatively. Even when it comes to c=
orporations, some CEOs of digital companies are put in jail because of the =
materials posted on their websites. I don&#39;t think we can argue that att=
ribution to corporate entities might not adversely impact human rights.<br>
&gt; <br>
<br>
Again, the keyword in that sentence is &#39;may&#39;, so there is no strong=
 claim made. <br>
<br>
&gt; All in all I think section 3.3.20 does not help Internet Protocols ena=
ble human rights and it can be misinterpreted. <br>
<br>
I think the text in there is not strong and shows different perspectives an=
d potential consequences. But again, happy to receive text suggestions. <br=
>
<br>
&gt; <br>
&gt; And in my previous email I talked about the problems with threat intel=
ligence agencies and some of their conducts and the use of WHOIS for attrib=
ution (which was actually not designed to &quot;identify&quot; actors but u=
nfortunately was used for that) so I will not reiterate here. <br>
<br>
>From exactly that discussion we got the idea to remove individuals, and lea=
ve non-natural persons in. <br>
<br>
Best,<br>
<br>
Niels<br>
<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever &lt;<a href=3D"mailto:=
mail@nielstenoever.net" target=3D"_blank">mail@nielstenoever.net</a> &lt;ma=
ilto:<a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@niels=
tenoever.net</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Hi Farzaneh,<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Thanks a lot for the review!<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0On 30-01-2021 23:00, farzaneh badii wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Hello<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Adding my comments on this document:=C2=A0<a h=
ref=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05" rel=3D"no=
referrer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hrpc-gui=
delines-05</a> &lt;<a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-g=
uidelines-05" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/h=
tml/draft-irtf-hrpc-guidelines-05</a>&gt; &lt;<a href=3D"https://tools.ietf=
.org/html/draft-irtf-hrpc-guidelines-05" rel=3D"noreferrer" target=3D"_blan=
k">https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05</a> &lt;<a hre=
f=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05" rel=3D"nore=
ferrer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hrpc-guide=
lines-05</a>&gt;&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; 1. One major issue that I see here and you mig=
ht be able to easily solve it is that there is no distinction between user =
facing protocols and other protocols. For example, you ask for accessibilit=
y and consideration of culture etc. Are you asking all the protocols to be =
provided in multiple languages, even those that only=C2=A0developers=C2=A0a=
nd implementers use and not the actual users? You might want to clarify tha=
t.=C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0We had a quite extensive discussion about this in r=
elation to the presentation by Ramsey Nasr who create Qalb, an Arabic progr=
amming language. Programmers are the most frequent &#39;users&#39; of proto=
cols - if we continue using only latin characters and English documentation=
 in protocols we are likely to reproduce the existing lack of diversity in =
protocol developers communities. But we can make the text on this clearer a=
s well!<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; 2.section 3.3.1 on connectivity, you mention t=
hat &quot;considering the fact that network quality and conditions vary acr=
oss geography and time it is also important to design protocols such that t=
hey are reliable even on low bandwidth ...&quot;. Then in your example you =
say: Middleboxes (including NAT).... can create potential for abuse. NAT is=
 a Network Address Translation protocol. I don&#39;t think it has anything =
to do with bandwidth. In this example you also mention CDNs. Are you sugges=
ting that the developer should not consider &quot;Middleboxes&quot; protoco=
ls? I think you need to work on the example of section 3.3.1 some more to m=
ake it clearer.=C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Excellent point - we&#39;ll address this in a futur=
e version.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; 3. section 3.3.20 remedy and attribution=C2=A0=
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; This section worries me. As a=C2=A0 scholar I =
have worked on cyber attribution to some extent and believe=C2=A0in general=
 when we have the right processes in place,=C2=A0attribution is very import=
ant and can hold cyber-attackers accountable. I am aware of some of the att=
ribution processes and unfortunately some threat intelligence firms and ope=
n source intelligence organizations can violate the privacy of individuals =
by profiling them. Also, uncontrolled attribution mechanisms can lead to fr=
ivolous=C2=A0intellectual property claims. Both some threat intelligence fi=
rms and IP firms have used WHOIS extensively in their favor to attribute cy=
bersecurity attacks and bring forward IP claims. WHOIS protocol did not hav=
e the intention to actually identify organizations and individuals, but to =
make them &quot;contactable&quot;.and it was still used and mined for so ma=
ny years and those who have abused WHOIS have not been held accountable.Whe=
n you suggest they consider &quot;attribution&quot; when developing protoco=
ls it<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; concerns me because it is not enough that you =
limit attribution to organizations and states. These kinds of attributions =
can be used against individuals and until we do not have the right preservi=
ng processes to put in place for those who want to be in the attribution bu=
siness, rights of the individual can be at risk. there are very privacy con=
scious=C2=A0cybersecurity researchers out there but unfortunately that does=
 not ensure a systematic=C2=A0practice of attribution in a fair manner. And=
 you mention attribution to associations is fine and may not directly negat=
ively impact human rights. Associations can themselves be at risk of frivol=
ous=C2=A0attacks and frivolous=C2=A0attribution. I am concerned about this =
paragraph. I think we should have a conversation about it.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0In the proposed text I tried to capture the consens=
us that emerged from the extensive discussion that was had on this list. Do=
 you have concrete suggestions on how to better capture that conensensus? I=
 am afraid we would go back and repeat the same discussion.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; 4. Nice to see that you mention DoH. It&#39;s =
a great privacy preserving protocol.=C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Thanks!<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Niels<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Farzaneh<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath =
&lt;<a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@=
gmail.com</a> &lt;mailto:<a href=3D"mailto:corinnecath@gmail.com" target=3D=
"_blank">corinnecath@gmail.com</a>&gt; &lt;mailto:<a href=3D"mailto:corinne=
cath@gmail.com" target=3D"_blank">corinnecath@gmail.com</a> &lt;mailto:<a h=
ref=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gmail.co=
m</a>&gt;&gt;&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Hi all,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0I trust this email finds yo=
u well. I did a review of the draft, from my perspective as an academic. Ta=
ke it as you please. My main concern is that some of the language reads a b=
it deterministic (as, I know so does RFC 8280). It means that a lot of onus=
 is put on the impact of a protocol, as opposed the role of the individuals=
 that write them.=C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0I think through out the doc=
ument, it would be interesting (especially in section 1 through 3.2.5) to s=
ee if you can rewrite such that you speak more directly to the protocol dev=
elopers. I think that section 3.3 does that well, in terms of the tone it t=
akes. As it clearly connects the actions of protocol developers to their po=
tential outcomes.=C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Hope this is helpful!=C2=A0=
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Kind regards,=C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Corinne<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0---------------------------=
------<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0*1. Introduction*<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&quot;It provides questions=
 engineers should ask<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 themselves when dev=
eloping or improving protocols if they want to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 understand their po=
tential human rights impact.&quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;&gt; maybe if they want=
 to understand potential human rights concerns? Impact seems a little deter=
ministic, as you also mention in the next sentence, I wonder if you can pro=
ve such direct impact between protocol development in the IETF and impact o=
n human rights.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&quot;The research establis=
hes<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 that human rights r=
elate to standards and protocols, and offers a<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 common vocabulary o=
f technical concepts that impact human rights and<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 how these technical=
 concepts can be combined to ensure that the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Internet remains an=
 enabling environment for human rights.&quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;&gt; same comment for t=
he word impact, perhaps shape? influence? etc.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03.1 &l=
t;<a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sect=
ion-3.1" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/d=
raft-irtf-hrpc-guidelines-05#section-3.1</a> &lt;<a href=3D"https://tools.i=
etf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1" rel=3D"noreferrer" =
target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05=
#section-3.1</a>&gt;&gt;. Human rights threats<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 &quot;Protocols and standa=
rds can harm or enable the right to freedom of<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 expression, right t=
o non-discrimination, right to equal protection,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 right to participat=
e in cultural life, arts and science, right to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0freedom of assembly and ass=
ociation, and the right to security. &quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;&gt; again, determinist=
ic language. Perhaps soften or add more concrete examples for context, that=
 draw from current IETF discussions/standards.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03.3 &l=
t;<a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sect=
ion-3.3" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/d=
raft-irtf-hrpc-guidelines-05#section-3.3</a> &lt;<a href=3D"https://tools.i=
etf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3" rel=3D"noreferrer" =
target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05=
#section-3.3</a>&gt;&gt;. Guidelines for human rights considerations<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0again, use of the word impa=
ct in the introduction.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0--<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Corinne Cath - Speth<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Ph.D. Candidate, Oxford Int=
ernet Institute &amp; Alan Turing Institute<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Web: <a href=3D"http://www.=
oii.ox.ac.uk/people/corinne-cath" rel=3D"noreferrer" target=3D"_blank">www.=
oii.ox.ac.uk/people/corinne-cath</a> &lt;<a href=3D"http://www.oii.ox.ac.uk=
/people/corinne-cath" rel=3D"noreferrer" target=3D"_blank">http://www.oii.o=
x.ac.uk/people/corinne-cath</a>&gt; &lt;<a href=3D"http://www.oii.ox.ac.uk/=
people/corinne-cath" rel=3D"noreferrer" target=3D"_blank">http://www.oii.ox=
.ac.uk/people/corinne-cath</a> &lt;<a href=3D"http://www.oii.ox.ac.uk/peopl=
e/corinne-cath" rel=3D"noreferrer" target=3D"_blank">http://www.oii.ox.ac.u=
k/people/corinne-cath</a>&gt;&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Email: <a href=3D"mailto:cc=
ath@turing.ac.uk" target=3D"_blank">ccath@turing.ac.uk</a> &lt;mailto:<a hr=
ef=3D"mailto:ccath@turing.ac.uk" target=3D"_blank">ccath@turing.ac.uk</a>&g=
t; &lt;mailto:<a href=3D"mailto:ccath@turing.ac.uk" target=3D"_blank">ccath=
@turing.ac.uk</a> &lt;mailto:<a href=3D"mailto:ccath@turing.ac.uk" target=
=3D"_blank">ccath@turing.ac.uk</a>&gt;&gt; &amp; <a href=3D"mailto:corinnec=
ath@gmail.com" target=3D"_blank">corinnecath@gmail.com</a> &lt;mailto:<a hr=
ef=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gmail.com=
</a>&gt; &lt;mailto:<a href=3D"mailto:corinnecath@gmail.com" target=3D"_bla=
nk">corinnecath@gmail.com</a> &lt;mailto:<a href=3D"mailto:corinnecath@gmai=
l.com" target=3D"_blank">corinnecath@gmail.com</a>&gt;&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Twitter: @C_CS<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0___________________________=
____________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0hrpc mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:hrpc@irtf=
.org" target=3D"_blank">hrpc@irtf.org</a> &lt;mailto:<a href=3D"mailto:hrpc=
@irtf.org" target=3D"_blank">hrpc@irtf.org</a>&gt; &lt;mailto:<a href=3D"ma=
ilto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a> &lt;mailto:<a href=
=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>&gt;&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.irtf=
.org/mailman/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://ww=
w.irtf.org/mailman/listinfo/hrpc</a> &lt;<a href=3D"https://www.irtf.org/ma=
ilman/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.=
org/mailman/listinfo/hrpc</a>&gt; &lt;<a href=3D"https://www.irtf.org/mailm=
an/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.org=
/mailman/listinfo/hrpc</a> &lt;<a href=3D"https://www.irtf.org/mailman/list=
info/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.org/mailma=
n/listinfo/hrpc</a>&gt;&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; ______________________________________________=
_<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; hrpc mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <a href=3D"mailto:hrpc@irtf.org" target=3D"_bl=
ank">hrpc@irtf.org</a> &lt;mailto:<a href=3D"mailto:hrpc@irtf.org" target=
=3D"_blank">hrpc@irtf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <a href=3D"https://www.irtf.org/mailman/listin=
fo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.org/mailman/=
listinfo/hrpc</a> &lt;<a href=3D"https://www.irtf.org/mailman/listinfo/hrpc=
" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.org/mailman/listinf=
o/hrpc</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0-- <br>
&gt;=C2=A0 =C2=A0 =C2=A0Niels ten Oever, PhD<br>
&gt;=C2=A0 =C2=A0 =C2=A0Postdoctoral Researcher - Media Studies Department =
- University of Amsterdam<br>
&gt;=C2=A0 =C2=A0 =C2=A0Postdoctoral Research Fellow - Communications Depar=
tment - Texas A&amp;M University<br>
&gt;=C2=A0 =C2=A0 =C2=A0Research Fellow - Centre for Internet and Human Rig=
hts - European University Viadrina<br>
&gt;=C2=A0 =C2=A0 =C2=A0Associated Scholar - Centro de Tecnologia e Socieda=
de - Funda=C3=A7=C3=A3o Get=C3=BAlio Vargas<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0W: <a href=3D"https://nielstenoever.net" rel=3D"nor=
eferrer" target=3D"_blank">https://nielstenoever.net</a> &lt;<a href=3D"htt=
ps://nielstenoever.net" rel=3D"noreferrer" target=3D"_blank">https://nielst=
enoever.net</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0E: <a href=3D"mailto:mail@nielstenoever.net" target=
=3D"_blank">mail@nielstenoever.net</a> &lt;mailto:<a href=3D"mailto:mail@ni=
elstenoever.net" target=3D"_blank">mail@nielstenoever.net</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0T: @nielstenoever<br>
&gt;=C2=A0 =C2=A0 =C2=A0P/S/WA: +31629051853<br>
&gt;=C2=A0 =C2=A0 =C2=A0PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C=
8B3<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Read my dissertation &#39;Wired Norms&#39; here: <a=
 href=3D"https://pure.uva.nl/ws/files/50781961/Thesis.pdf" rel=3D"noreferre=
r" target=3D"_blank">https://pure.uva.nl/ws/files/50781961/Thesis.pdf</a> &=
lt;<a href=3D"https://pure.uva.nl/ws/files/50781961/Thesis.pdf" rel=3D"nore=
ferrer" target=3D"_blank">https://pure.uva.nl/ws/files/50781961/Thesis.pdf<=
/a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0_______________________________________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0hrpc mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">=
hrpc@irtf.org</a> &lt;mailto:<a href=3D"mailto:hrpc@irtf.org" target=3D"_bl=
ank">hrpc@irtf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.irtf.org/mailman/listinfo/hr=
pc" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.org/mailman/listi=
nfo/hrpc</a> &lt;<a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=
=3D"noreferrer" target=3D"_blank">https://www.irtf.org/mailman/listinfo/hrp=
c</a>&gt;<br>
&gt; <br>
<br>
-- <br>
Niels ten Oever, PhD<br>
Postdoctoral Researcher - Media Studies Department - University of Amsterda=
m<br>
Postdoctoral Research Fellow - Communications Department - Texas A&amp;M Un=
iversity<br>
Research Fellow - Centre for Internet and Human Rights - European Universit=
y Viadrina<br>
Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=A3o =
Get=C3=BAlio Vargas<br>
<br>
W: <a href=3D"https://nielstenoever.net" rel=3D"noreferrer" target=3D"_blan=
k">https://nielstenoever.net</a><br>
E: <a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielste=
noever.net</a><br>
T: @nielstenoever<br>
P/S/WA: +31629051853<br>
PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3<br>
<br>
Read my dissertation &#39;Wired Norms&#39; here: <a href=3D"https://pure.uv=
a.nl/ws/files/50781961/Thesis.pdf" rel=3D"noreferrer" target=3D"_blank">htt=
ps://pure.uva.nl/ws/files/50781961/Thesis.pdf</a><br>
</blockquote></div>

--00000000000068ba8605ba4cf4d4--


From nobody Mon Feb  1 14:19:43 2021
Return-Path: <mail@nielstenoever.net>
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 56D8B3A152F for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 14:19:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 7RvGShRq2DPU for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 14:19:37 -0800 (PST)
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 BBE1C3A152E for <hrpc@irtf.org>; Mon,  1 Feb 2021 14:19:36 -0800 (PST)
In-Reply-To: <CAN1qJvCsbfnVePRFYAsySrgtaumUARc8PpnAX-cANu5Pgc7TMA@mail.gmail.com>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <08b61ab2-7840-d993-9946-c085861f4172@nielstenoever.net> <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com> <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net> <CAN1qJvCsbfnVePRFYAsySrgtaumUARc8PpnAX-cANu5Pgc7TMA@mail.gmail.com>
X-Referenced-Uid: 28711
Thread-Topic: Re: [hrpc] Comment on draft-guidelines for RG Last Call
User-Agent: Android
X-Is-Generated-Message-Id: true
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----9IMB0PRWVN7XOSA790BF4UG7T4P2YG"
Content-Transfer-Encoding: 7bit
From: Niels ten Oever <mail@nielstenoever.net>
Date: Mon, 01 Feb 2021 23:19:30 +0100
To: farzaneh badii <farzaneh.badii@gmail.com>
CC: Hrpc <hrpc@irtf.org>
Message-ID: <34ab9666-4521-49f7-831e-c22841743448@nielstenoever.net>
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 056b3294c5db0d3e1c04e2a4b438e04d
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/DdArtwzOKlCnLF_md8O1jVTzcAU>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 22:19:41 -0000

------9IMB0PRWVN7XOSA790BF4UG7T4P2YG
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
 charset=UTF-8

Dear Farzaneh,

Do your alterations reflect the content of the discussion, =
or mere your opinion?

I hope we're seeking to reach a consensus during las=
t call, not reopening the discussion=2E

Best,

Niels



On Feb 1, 2021, 22=
:22, at 22:22, farzaneh badii <farzaneh=2Ebadii@gmail=2Ecom> wrote:
>Here w=
e go:
>
>
>Question(s): Can your protocol facilitate a negatively impacted
=
>
>   party's right to the appropriate  legal remedy without
>disproportion=
ately impacting
>
>   other parties' human rights, especially their right t=
o privacy?
>
>
>   Explanation: Access to legal remedy is a human right tha=
t ensures
>
>   that individuals whose rights have been violated can seek r=
emedies
>
>
>
>
>   through a judicial authority=2E  Attribution (i=2Ee=2E =
mechanisms in
>
>   protocols or architectures that are designed to make co=
mmunications
>
>or artifacts attributable might help with seeking the appro=
priate
>remedy
>=2E) to a certain computer or individual) can be
>
>   a pa=
rt of this, since it may allow law enforcement agencies to
>
>   identify a=
 possible violator=2E  However, attribution mechanisms may
>
>   impede the=
 exercise of the right to privacy=2E  The Special Rapporteur
>
>   for Free=
dom of Expression has also argued that anonymity is an
>
>   inherent part =
of freedom of expression=2E  [Kaye] Considering the
>
>   adverse impact of=
 attribution on the right to privacy and freedom of
>
>expression, attribut=
ion on an individual level may is not be consistent
>
>   with human rights=
=2E  However, attribution to corporate entities,
>
>   associations, and/or=
 countries may not directly negatively impact
>
>   human rights=2E
>
>
>  =
 Impacts:
>
>
>   -  Right to legal remedy
>
>
>   -  Right to security
>Fa=
rzaneh
>
>
>On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever <mail@nielstenoe=
ver=2Enet>
>wrote:
>
>> Hi Farzaneh,
>>
>> On 31-01-2021 19:16, farzaneh ba=
dii wrote:
>> > Hello Niels=2E
>> >
>> >
>> > I don't know how we measure c=
onsensus here=2E But I remember weighing
>in
>> back then as well(When Mr=
=2E Curran weighed in back in 2019)=2E Here is
>the
>> thread: https://mail=
archive=2Eietf=2Eorg/arch/browse/hrpc/?q=3Dattribution
><
>> https://mailar=
chive=2Eietf=2Eorg/arch/browse/hrpc/?q=3Dattribution>
>> >
>> > I can see t=
hat unfortunately I missed the discussion on this topic
>> during the past =
year, and that's my fault, but I can bring reasons
>not to
>> add "attribut=
ion and legal remedy" to this document at all=2E
>> >
>> > 1=2E Access to l=
egal remedy is something that the States are
>supposedly in
>> charge of br=
inging to their citizens=2EWhich should (in theory) ensure
>that
>> human r=
ights are enforced=2E I don't think there was an intention to
>> provide  m=
echanisms for "enforcement" of human rights in various
>legal
>> systems th=
rough Internet protocols=2E As mentioned in the beginning of
>your
>> docum=
ent:
>> > "Human rights threats on the Internet come in a myriad of
>> form=
s=2E* **P**rotocols and standards can harm or enable* the right to
>> freed=
om of expression, right to non-discrimination, right to equal
>> protection=
, right to participate in cultural life, arts and science,
>right
>> to fre=
edom of assembly and association, and the right to security=2E"
>> >
>> > S=
o we are not in the business of enforcing but providing an
>enabling
>> env=
ironment=2E Because if we want to help law enforcement and the
>judicial
>>=
 authorities enforce human rights through Internet protocols we should
>bea=
r
>> in mind that that they are not always staunch advocates of human
>righ=
ts=2E So
>> what I assume we are trying to do here is to help Internet prot=
ocol
>not to
>> facilitate harm and "enable" human rights=2E
>> >
>>
>> The=
 text in the draft seeks to address this risk=2E I have sought to
>address
=
>> all points made in that discussion, and I would not like to re-open
>tha=
t
>> debate=2E If you feel the text is unbalanced, could you perhaps provid=
e
>text
>> suggestions?
>>
>> > 2=2E Attribution, section 3=2E3=2E20  of th=
e Guideline, the authors
>assert
>> that: "However, attribution to corporat=
e entities, associations,
>and/or
>> countries may not directly negatively =
impact human rights=2E" I think
>this is
>> not a very well backed up claim=
=2E Because in some cases some
>associations
>> might be political or they =
might be human rights associations dealing
>with
>> a dictatorship=2E Attri=
bution to those associations certainly can
>impact
>> their human rights ne=
gatively=2E Even when it comes to corporations,
>some
>> CEOs of digital co=
mpanies are put in jail because of the materials
>posted
>> on their websit=
es=2E I don't think we can argue that attribution to
>corporate
>> entities=
 might not adversely impact human rights=2E
>> >
>>
>> Again, the keyword i=
n that sentence is 'may', so there is no strong
>claim
>> made=2E
>>
>> > A=
ll in all I think section 3=2E3=2E20 does not help Internet Protocols
>> en=
able human rights and it can be misinterpreted=2E
>>
>> I think the text in=
 there is not strong and shows different
>perspectives
>> and potential con=
sequences=2E But again, happy to receive text
>suggestions=2E
>>
>> >
>> > =
And in my previous email I talked about the problems with threat
>> intelli=
gence agencies and some of their conducts and the use of WHOIS
>for
>> attr=
ibution (which was actually not designed to "identify" actors but
>> unfort=
unately was used for that) so I will not reiterate here=2E
>>
>> From exact=
ly that discussion we got the idea to remove individuals,
>and
>> leave non=
-natural persons in=2E
>>
>> Best,
>>
>> Niels
>>
>> >
>> >
>> >
>> >
>> >
=
>> >
>> >
>> > On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever
><mail@niels=
tenoever=2Enet
>> <mailto:mail@nielstenoever=2Enet>> wrote:
>> >
>> >     H=
i Farzaneh,
>> >
>> >     Thanks a lot for the review!
>> >
>> >     On 30-=
01-2021 23:00, farzaneh badii wrote:
>> >     > Hello
>> >     >
>> >     >=
 Adding my comments on this document:
>> https://tools=2Eietf=2Eorg/html/dr=
aft-irtf-hrpc-guidelines-05 <
>> https://tools=2Eietf=2Eorg/html/draft-irtf=
-hrpc-guidelines-05> <
>> https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-g=
uidelines-05 <
>> https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guideline=
s-05>>
>> >     >
>> >     > 1=2E One major issue that I see here and you m=
ight be able to
>easily
>> solve it is that there is no distinction between=
 user facing
>protocols and
>> other protocols=2E For example, you ask for =
accessibility and
>consideration
>> of culture etc=2E Are you asking all th=
e protocols to be provided in
>multiple
>> languages, even those that only =
developers and implementers use and
>not the
>> actual users? You might wan=
t to clarify that=2E
>> >     >
>> >
>> >     We had a quite extensive disc=
ussion about this in relation to
>the
>> presentation by Ramsey Nasr who cr=
eate Qalb, an Arabic programming
>> language=2E Programmers are the most fr=
equent 'users' of protocols - if
>we
>> continue using only latin character=
s and English documentation in
>protocols
>> we are likely to reproduce the=
 existing lack of diversity in protocol
>> developers communities=2E But we=
 can make the text on this clearer as
>well!
>> >
>> >     > 2=2Esection 3=
=2E3=2E1 on connectivity, you mention that
>"considering the
>> fact that n=
etwork quality and conditions vary across geography and
>time it
>> is also=
 important to design protocols such that they are reliable
>even on
>> low =
bandwidth =2E=2E=2E"=2E Then in your example you say: Middleboxes
>(includi=
ng
>> NAT)=2E=2E=2E=2E can create potential for abuse=2E NAT is a Network A=
ddress
>> Translation protocol=2E I don't think it has anything to do with
=
>bandwidth=2E
>> In this example you also mention CDNs=2E Are you suggestin=
g that the
>> developer should not consider "Middleboxes" protocols? I thin=
k you
>need to
>> work on the example of section 3=2E3=2E1 some more to mak=
e it clearer=2E
>> >     >
>> >
>> >     Excellent point - we'll address th=
is in a future version=2E
>> >
>> >     > 3=2E section 3=2E3=2E20 remedy an=
d attribution
>> >     > This section worries me=2E As a  scholar I have wo=
rked on cyber
>> attribution to some extent and believe in general when we =
have the
>right
>> processes in place, attribution is very important and ca=
n hold
>> cyber-attackers accountable=2E I am aware of some of the attribut=
ion
>> processes and unfortunately some threat intelligence firms and open
=
>source
>> intelligence organizations can violate the privacy of individual=
s by
>> profiling them=2E Also, uncontrolled attribution mechanisms can lea=
d to
>> frivolous intellectual property claims=2E Both some threat intellig=
ence
>firms
>> and IP firms have used WHOIS extensively in their favor to a=
ttribute
>> cybersecurity attacks and bring forward IP claims=2E WHOIS prot=
ocol did
>not
>> have the intention to actually identify organizations and
=
>individuals, but
>> to make them "contactable"=2Eand it was still used and=
 mined for so
>many
>> years and those who have abused WHOIS have not been =
held
>accountable=2EWhen
>> you suggest they consider "attribution" when de=
veloping protocols it
>> >     > concerns me because it is not enough that =
you limit
>attribution to
>> organizations and states=2E These kinds of att=
ributions can be used
>against
>> individuals and until we do not have the =
right preserving processes
>to put
>> in place for those who want to be in =
the attribution business, rights
>of
>> the individual can be at risk=2E th=
ere are very privacy
>> conscious cybersecurity researchers out there but u=
nfortunately that
>does
>> not ensure a systematic practice of attribution =
in a fair manner=2E And
>you
>> mention attribution to associations is fine=
 and may not directly
>negatively
>> impact human rights=2E Associations ca=
n themselves be at risk of
>> frivolous attacks and frivolous attribution=
=2E I am concerned about
>this
>> paragraph=2E I think we should have a con=
versation about it=2E
>> >     >
>> >
>> >     In the proposed text I tried=
 to capture the consensus that
>emerged
>> from the extensive discussion th=
at was had on this list=2E Do you have
>> concrete suggestions on how to be=
tter capture that conensensus? I am
>afraid
>> we would go back and repeat =
the same discussion=2E
>> >
>> >     > 4=2E Nice to see that you mention Do=
H=2E It's a great privacy
>> preserving protocol=2E
>> >     >
>> >     >
>=
> >
>> >     Thanks!
>> >
>> >     Niels
>> >
>> >     >
>> >     >
>> >   =
  >
>> >     >
>> >     >
>> >     >
>> >     >
>> >     >
>> >     > Farza=
neh
>> >     >
>> >     >
>> >     > On Sat, Jan 30, 2021 at 10:35 AM Corin=
ne Cath <
>> corinnecath@gmail=2Ecom <mailto:corinnecath@gmail=2Ecom> <mail=
to:
>> corinnecath@gmail=2Ecom <mailto:corinnecath@gmail=2Ecom>>> wrote:
>>=
 >     >
>> >     >     Hi all,
>> >     >
>> >     >     I trust this emai=
l finds you well=2E I did a review of the
>> draft, from my perspective as =
an academic=2E Take it as you please=2E My
>main
>> concern is that some of=
 the language reads a bit deterministic (as, I
>know
>> so does RFC 8280)=
=2E It means that a lot of onus is put on the impact
>of a
>> protocol, as =
opposed the role of the individuals that write them=2E
>> >     >
>> >     =
>     I think through out the document, it would be interesting
>> (especia=
lly in section 1 through 3=2E2=2E5) to see if you can rewrite
>such that
>>=
 you speak more directly to the protocol developers=2E I think that
>sectio=
n
>> 3=2E3 does that well, in terms of the tone it takes=2E As it clearly
>=
connects
>> the actions of protocol developers to their potential outcomes=
=2E
>> >     >
>> >     >     Hope this is helpful!
>> >     >
>> >     >  =
   Kind regards,
>> >     >
>> >     >     Corinne
>> >     >
>> >     >   =
  ---------------------------------
>> >     >
>> >     >     *1=2E Introdu=
ction*
>> >     >
>> >     >     "It provides questions engineers should as=
k
>> >     >
>> >     >        themselves when developing or improving prot=
ocols if
>they
>> want to
>> >     >        understand their potential huma=
n rights impact=2E"
>> >     >
>> >     >
>> >     >     >> maybe if they w=
ant to understand potential human
>rights
>> concerns? Impact seems a littl=
e deterministic, as you also mention in
>the
>> next sentence, I wonder if =
you can prove such direct impact between
>> protocol development in the IET=
F and impact on human rights=2E
>> >     >
>> >     >     "The research est=
ablishes
>> >     >
>> >     >        that human rights relate to standards=
 and protocols,
>and
>> offers a
>> >     >        common vocabulary of tec=
hnical concepts that impact
>human
>> rights and
>> >     >        how thes=
e technical concepts can be combined to ensure
>that
>> the
>> >     >     =
   Internet remains an enabling environment for human
>rights=2E"
>> >     =
>
>> >     >
>> >     >     >> same comment for the word impact, perhaps sh=
ape?
>influence?
>> etc=2E
>> >     >
>> >     >
>> >     >           3=2E1=
 <
>> https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05#section=
-3=2E1
><
>>
>https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05=
#section-3=2E1>>=2E
>> Human rights threats
>> >     >
>> >     >
>> >     =
>
>> >     >      "Protocols and standards can harm or enable the right to
=
>> freedom of
>> >     >        expression, right to non-discrimination, ri=
ght to
>equal
>> protection,
>> >     >        right to participate in cult=
ural life, arts and
>science,
>> right to
>> >     >
>> >     >     freedom=
 of assembly and association, and the right to
>> security=2E "
>> >     >
=
>> >     >
>> >     >     >> again, deterministic language=2E Perhaps softe=
n or add
>more
>> concrete examples for context, that draw from current IET=
F
>> discussions/standards=2E
>> >     >
>> >     >
>> >     >
>> >     >  =
         3=2E3 <
>> https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guideli=
nes-05#section-3=2E3
><
>>
>https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc=
-guidelines-05#section-3=2E3>>=2E
>> Guidelines for human rights considerat=
ions
>> >     >
>> >     >
>> >     >
>> >     >     again, use of the word=
 impact in the introduction=2E
>> >     >
>> >     >
>> >     >
>> >     >
=
>> >     >     --
>> >     >     Corinne Cath - Speth
>> >     >     Ph=2ED=
=2E Candidate, Oxford Internet Institute & Alan Turing
>> Institute
>> >   =
  >
>> >     >     Web: www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath <
>> h=
ttp://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath> <
>> http://www=2Eoii=
=2Eox=2Eac=2Euk/people/corinne-cath <
>> http://www=2Eoii=2Eox=2Eac=2Euk/pe=
ople/corinne-cath>>
>> >     >     Email: ccath@turing=2Eac=2Euk <mailto:cc=
ath@turing=2Eac=2Euk>
><mailto:
>> ccath@turing=2Eac=2Euk <mailto:ccath@tur=
ing=2Eac=2Euk>> &
>corinnecath@gmail=2Ecom
>> <mailto:corinnecath@gmail=2Ec=
om> <mailto:corinnecath@gmail=2Ecom <mailto:
>> corinnecath@gmail=2Ecom>>
>=
> >     >     Twitter: @C_CS
>> >     >     _______________________________=
________________
>> >     >     hrpc mailing list
>> >     >     hrpc@irtf=
=2Eorg <mailto:hrpc@irtf=2Eorg>
><mailto:hrpc@irtf=2Eorg
>> <mailto:hrpc@ir=
tf=2Eorg>>
>> >     >     https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc <
=
>> https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc> <
>> https://www=2Eirtf=
=2Eorg/mailman/listinfo/hrpc <
>> https://www=2Eirtf=2Eorg/mailman/listinfo=
/hrpc>>
>> >     >
>> >     >
>> >     > __________________________________=
_____________
>> >     > hrpc mailing list
>> >     > hrpc@irtf=2Eorg <mail=
to:hrpc@irtf=2Eorg>
>> >     > https://www=2Eirtf=2Eorg/mailman/listinfo/hr=
pc <
>> https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc>
>> >     >
>> >
>> =
>     --
>> >     Niels ten Oever, PhD
>> >     Postdoctoral Researcher - M=
edia Studies Department - University
>of
>> Amsterdam
>> >     Postdoctoral=
 Research Fellow - Communications Department -
>Texas A&M
>> University
>> =
>     Research Fellow - Centre for Internet and Human Rights -
>European
>>=
 University Viadrina
>> >     Associated Scholar - Centro de Tecnologia e S=
ociedade -
>Funda=C3=A7=C3=A3o
>> Get=C3=BAlio Vargas
>> >
>> >     W: http=
s://nielstenoever=2Enet <https://nielstenoever=2Enet>
>> >     E: mail@niel=
stenoever=2Enet <mailto:mail@nielstenoever=2Enet>
>> >     T: @nielstenoeve=
r
>> >     P/S/WA: +31629051853
>> >     PGP: 2458 0B70 5C4A FD8A 9488 643A=
 0ED8 3F3A 468A C8B3
>> >
>> >     Read my dissertation 'Wired Norms' here:=

>> https://pure=2Euva=2Enl/ws/files/50781961/Thesis=2Epdf <
>> https://pur=
e=2Euva=2Enl/ws/files/50781961/Thesis=2Epdf>
>> >     _____________________=
__________________________
>> >     hrpc mailing list
>> >     hrpc@irtf=2E=
org <mailto:hrpc@irtf=2Eorg>
>> >     https://www=2Eirtf=2Eorg/mailman/list=
info/hrpc <
>> https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc>
>> >
>>
>> -=
-
>> Niels ten Oever, PhD
>> Postdoctoral Researcher - Media Studies Depart=
ment - University of
>> Amsterdam
>> Postdoctoral Research Fellow - Communi=
cations Department - Texas A&M
>> University
>> Research Fellow - Centre fo=
r Internet and Human Rights - European
>> University Viadrina
>> Associated=
 Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=A3o
>Get=C3=BA=
lio
>> Vargas
>>
>> W: https://nielstenoever=2Enet
>> E: mail@nielstenoever=
=2Enet
>> T: @nielstenoever
>> P/S/WA: +31629051853
>> PGP: 2458 0B70 5C4A =
FD8A 9488 643A 0ED8 3F3A 468A C8B3
>>
>> Read my dissertation 'Wired Norms'=
 here:
>> https://pure=2Euva=2Enl/ws/files/50781961/Thesis=2Epdf
>>

------9IMB0PRWVN7XOSA790BF4UG7T4P2YG
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"zoom: 0%;"><div dir=3D"auto">Dear Farzane=
h,<br><br></div>
<div dir=3D"auto">Do your alterations reflect the content =
of the discussion, or mere your opinion?<br><br></div>
<div dir=3D"auto">I =
hope we're seeking to reach a consensus during last call, not reopening the=
 discussion=2E<br><br></div>
<div dir=3D"auto">Best,<br><br></div>
<div dir=
=3D"auto">Niels<br><br></div>
<div class=3D"gmail_quote" >On Feb 1, 2021, a=
t 22:22, farzaneh badii &lt;<a href=3D"mailto:farzaneh=2Ebadii@gmail=2Ecom"=
 target=3D"_blank">farzaneh=2Ebadii@gmail=2Ecom</a>&gt; wrote:<blockquote c=
lass=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0=2E8ex; border-left: 1px=
 solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir=3D"ltr">
 <div cla=
ss=3D"gmail_default" style=3D"font-family:verdana,sans-serif">
  Here we go=
:
 </div>
 <div class=3D"gmail_default" style=3D"font-family:verdana,sans-s=
erif">
  <br>
 </div>
 <div class=3D"gmail_default" style=3D"font-family:ve=
rdana,sans-serif"></div>
 <div class=3D"gmail_default" style=3D"font-family=
:verdana,sans-serif">
  <br>
 </div>
 <div class=3D"gmail_default" style=3D=
"font-family:verdana,sans-serif"> 
  <p class=3D"gmail-p1" style=3D"margin:=
0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch=
:normal;font-size:12px;line-height:normal;font-family:Helvetica">Question(s=
): Can your protocol facilitate a negatively impacted</p> 
  <p class=3D"gm=
ail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-a=
sian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-fami=
ly:Helvetica"><span class=3D"gmail-Apple-converted-space">&nbsp;&nbsp; </sp=
an>party's right to<font color=3D"#ff0000">&nbsp;the appropriate </font>
  =
 <strike>
    &nbsp;legal 
   </strike>remedy without disproportionately im=
pacting</p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numer=
ic:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px=
;line-height:normal;font-family:Helvetica"><span class=3D"gmail-Apple-conve=
rted-space">&nbsp;&nbsp; </span>other parties' human rights, especially the=
ir right to privacy?</p> 
  <p class=3D"gmail-p2" style=3D"margin:0px;font-=
variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;f=
ont-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br=
></p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:nor=
mal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-=
height:normal;font-family:Helvetica">
   <strike>
    <span class=3D"gmail-=
Apple-converted-space">&nbsp;&nbsp; </span>Explanation: Access to legal rem=
edy is a human right that ensures
   </strike></p> 
  <p class=3D"gmail-p1"=
 style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:no=
rmal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helv=
etica">
   <strike>
    <span class=3D"gmail-Apple-converted-space">&nbsp;&=
nbsp; </span>that individuals whose rights have been violated can seek reme=
dies
   </strike></p> 
  <p class=3D"gmail-p2" style=3D"margin:0px;font-var=
iant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font=
-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br></=
p> 
  <p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal=
;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-hei=
ght:normal;font-family:Helvetica;min-height:14px"><br></p> 
  <p class=3D"g=
mail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-=
asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-fam=
ily:Helvetica;min-height:14px"><br></p> 
  <p class=3D"gmail-p1" style=3D"m=
argin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-s=
tretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
   =
<strike>
    <span class=3D"gmail-Apple-converted-space">&nbsp;&nbsp; </spa=
n>through a judicial authority=2E
   </strike><span class=3D"gmail-Apple-co=
nverted-space">&nbsp; </span>Attribution (i=2Ee=2E mechanisms in</p> 
  <p =
class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-var=
iant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:norma=
l;font-family:Helvetica"><span class=3D"gmail-Apple-converted-space">&nbsp;=
&nbsp; </span>protocols or architectures that are designed to make communic=
ations</p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeri=
c:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;=
line-height:normal;font-family:Helvetica"><span class=3D"gmail-Apple-conver=
ted-space">&nbsp;&nbsp; </span>or artifacts attributable <font color=3D"#ff=
0000">might help with seeking the appropriate remedy</font>=2E)&nbsp;
   <s=
trike>
    to a certain computer or individual)
   </strike> 
   <strike>
 =
   can be
   </strike></p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;fon=
t-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal=
;font-size:12px;line-height:normal;font-family:Helvetica">
   <strike>
    =
<span class=3D"gmail-Apple-converted-space">&nbsp;&nbsp; </span>a part of t=
his, since it may allow law enforcement agencies to
   </strike></p> 
  <p =
class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-var=
iant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:norma=
l;font-family:Helvetica">
   <strike>
    <span class=3D"gmail-Apple-conver=
ted-space">&nbsp;&nbsp; </span>identify a possible violator
   </strike>=2E=
<span class=3D"gmail-Apple-converted-space">&nbsp; </span>However, attribut=
ion mechanisms may</p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-va=
riant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fon=
t-size:12px;line-height:normal;font-family:Helvetica"><span class=3D"gmail-=
Apple-converted-space">&nbsp;&nbsp; </span>impede the exercise of the right=
 to privacy=2E<span class=3D"gmail-Apple-converted-space">&nbsp; </span>The=
 Special Rapporteur</p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-v=
ariant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fo=
nt-size:12px;line-height:normal;font-family:Helvetica"><span class=3D"gmail=
-Apple-converted-space">&nbsp;&nbsp; </span>for Freedom of Expression has a=
lso argued that anonymity is an</p> 
  <p class=3D"gmail-p1" style=3D"margi=
n:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stret=
ch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span cl=
ass=3D"gmail-Apple-converted-space">&nbsp;&nbsp; </span>inherent part of fr=
eedom of expression=2E<span class=3D"gmail-Apple-converted-space">&nbsp; </=
span>[Kaye] Considering the</p> 
  <p class=3D"gmail-p1" style=3D"margin:0p=
x;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:n=
ormal;font-size:12px;line-height:normal;font-family:Helvetica"><span class=
=3D"gmail-Apple-converted-space">&nbsp;&nbsp; </span>adverse impact of attr=
ibution on the right to privacy and freedom of</p> 
  <p class=3D"gmail-p1"=
 style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:no=
rmal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helv=
etica"><span class=3D"gmail-Apple-converted-space">&nbsp;&nbsp; </span>expr=
ession, attribution on an individual level
   <strike>
     may
   </strike=
>&nbsp;<font color=3D"#ff0000">is&nbsp;</font>not 
   <strike>
    be
   </=
strike> consistent</p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-va=
riant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fon=
t-size:12px;line-height:normal;font-family:Helvetica"><span class=3D"gmail-=
Apple-converted-space">&nbsp;&nbsp; </span>with human rights=2E<span class=
=3D"gmail-Apple-converted-space">&nbsp;
    <strike> 
    </strike></span>
=
   <strike>
    However, attribution to corporate entities,
   </strike></p=
> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;=
font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-heig=
ht:normal;font-family:Helvetica">
   <strike>
    <span class=3D"gmail-Appl=
e-converted-space">&nbsp;&nbsp; </span>associations, and/or countries may n=
ot directly negatively impact
   </strike></p> 
  <p class=3D"gmail-p1" sty=
le=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal=
;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetic=
a">
   <strike>
    <span class=3D"gmail-Apple-converted-space">&nbsp;&nbsp=
; </span>human rights=2E
   </strike></p> 
  <p class=3D"gmail-p2" style=3D=
"margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font=
-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min=
-height:14px"><br></p> 
  <p class=3D"gmail-p1" style=3D"margin:0px;font-va=
riant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fon=
t-size:12px;line-height:normal;font-family:Helvetica"><span class=3D"gmail-=
Apple-converted-space">&nbsp;&nbsp; </span>Impacts:</p> 
  <p class=3D"gmai=
l-p2" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asi=
an:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family=
:Helvetica;min-height:14px">
   <strike>
    <br>
   </strike></p> 
  <p cl=
ass=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-varia=
nt-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;=
font-family:Helvetica">
   <strike>
    <span class=3D"gmail-Apple-converte=
d-space">&nbsp;&nbsp; </span>-
    <span class=3D"gmail-Apple-converted-spa=
ce">&nbsp; </span>Right to legal remedy
   </strike></p> 
  <p class=3D"gma=
il-p2" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-as=
ian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-famil=
y:Helvetica;min-height:14px"><br></p> 
  <p class=3D"gmail-p1" style=3D"mar=
gin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-str=
etch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span =
class=3D"gmail-Apple-converted-space">&nbsp;&nbsp; </span>-<span class=3D"g=
mail-Apple-converted-space">&nbsp; </span>Right to security</p>
 </div>
 <d=
iv>
  <div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_si=
gnature">
   <div dir=3D"ltr">
    <div>
     <font face=3D"verdana, sans-s=
erif">Farzaneh </font>
    </div>
   </div>
  </div>
 </div>
 <br>
</div>
<=
br>
<div class=3D"gmail_quote">
 <div dir=3D"ltr" class=3D"gmail_attr">
  O=
n Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever &lt;
  <a href=3D"mailto:mail=
@nielstenoever=2Enet">mail@nielstenoever=2Enet</a>&gt; wrote:
  <br>
 </div=
>
 <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=2E8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">
  Hi Farzaneh,
  <b=
r> 
  <br> On 31-01-2021 19:16, farzaneh badii wrote:
  <br> &gt; Hello Nie=
ls=2E
  <br> &gt; 
  <br> &gt; 
  <br> &gt; I don't know how we measure con=
sensus here=2E But I remember weighing in back then as well(When Mr=2E Curr=
an weighed in back in 2019)=2E Here is the thread:&nbsp;
  <a href=3D"https=
://mailarchive=2Eietf=2Eorg/arch/browse/hrpc/?q=3Dattribution" rel=3D"noref=
errer" target=3D"_blank">https://mailarchive=2Eietf=2Eorg/arch/browse/hrpc/=
?q=3Dattribution</a> &lt;
  <a href=3D"https://mailarchive=2Eietf=2Eorg/arc=
h/browse/hrpc/?q=3Dattribution" rel=3D"noreferrer" target=3D"_blank">https:=
//mailarchive=2Eietf=2Eorg/arch/browse/hrpc/?q=3Dattribution</a>&gt;
  <br>=
 &gt; 
  <br> &gt; I can see that unfortunately I missed the&nbsp;discussio=
n on this topic during the past year, and that's my fault, but I can bring =
reasons not to add "attribution and legal remedy" to this document at all=
=2E&nbsp;
  <br> &gt; 
  <br> &gt; 1=2E Access to legal remedy is something=
 that the States are supposedly in charge of bringing to their citizens=2EW=
hich should (in theory) ensure that human rights are enforced=2E I don't th=
ink there&nbsp;was an intention to&nbsp; provide&nbsp; mechanisms for "enfo=
rcement" of human rights in various legal systems through Internet protocol=
s=2E As mentioned&nbsp;in the beginning of your document:&nbsp;
  <br> &gt;=
 "Human rights threats on the Internet come in a myriad of forms=2E*&nbsp;*=
*P**rotocols and standards can harm or enable* the right to freedom of&nbsp=
;expression, right to non-discrimination, right to equal protection,&nbsp;r=
ight to participate in cultural life, arts and science, right to&nbsp;freed=
om of assembly and association, and the right to security=2E"&nbsp;
  <br> =
&gt; 
  <br> &gt; So we are not in the business of enforcing but providing&=
nbsp;an enabling environment=2E Because&nbsp;if we want to help law enforce=
ment and the judicial authorities enforce human rights through&nbsp;Interne=
t&nbsp;protocols we should bear in mind that that they are not always staun=
ch advocates of human rights=2E So what I assume we are trying to do here i=
s to help Internet protocol not to facilitate harm and "enable" human right=
s=2E&nbsp;
  <br> &gt; 
  <br> 
  <br> The text in the draft seeks to addre=
ss this risk=2E I have sought to address all points made in that discussion=
, and I would not like to re-open that debate=2E If you feel the text is un=
balanced, could you perhaps provide text suggestions? 
  <br> 
  <br> &gt; =
2=2E Attribution, section 3=2E3=2E20&nbsp; of the Guideline, the authors as=
sert that: "However, attribution to corporate entities,&nbsp;associations, =
and/or countries may not directly negatively impact&nbsp;human rights=2E" I=
 think this is not a very&nbsp;well backed up claim=2E Because in some case=
s some associations might be political or they might be human rights associ=
ations dealing with a dictatorship=2E Attribution to those associations cer=
tainly can impact their human rights negatively=2E Even when it comes to co=
rporations, some CEOs of digital companies are put in jail because of the m=
aterials posted on their websites=2E I don't think we can argue that attrib=
ution to corporate entities might not adversely impact human rights=2E
  <b=
r> &gt; 
  <br> 
  <br> Again, the keyword in that sentence is 'may', so th=
ere is no strong claim made=2E 
  <br> 
  <br> &gt; All in all I think sect=
ion 3=2E3=2E20 does not help Internet Protocols enable human rights and it =
can be misinterpreted=2E 
  <br> 
  <br> I think the text in there is not s=
trong and shows different perspectives and potential consequences=2E But ag=
ain, happy to receive text suggestions=2E 
  <br> 
  <br> &gt; 
  <br> &gt;=
 And in my previous email I talked about the problems with threat intellige=
nce agencies and some of their conducts and the use of WHOIS for attributio=
n (which was actually not designed to "identify" actors but unfortunately w=
as used for that) so I will not reiterate here=2E 
  <br> 
  <br> From exac=
tly that discussion we got the idea to remove individuals, and leave non-na=
tural persons in=2E 
  <br> 
  <br> Best,
  <br> 
  <br> Niels
  <br> 
  <b=
r> &gt; 
  <br> &gt; 
  <br> &gt; 
  <br> &gt; 
  <br> &gt; 
  <br> &gt; 
 =
 <br> &gt; 
  <br> &gt; On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever &lt=
;
  <a href=3D"mailto:mail@nielstenoever=2Enet" target=3D"_blank">mail@niel=
stenoever=2Enet</a> &lt;mailto:
  <a href=3D"mailto:mail@nielstenoever=2Ene=
t" target=3D"_blank">mail@nielstenoever=2Enet</a>&gt;&gt; wrote:
  <br> &gt=
; 
  <br> &gt;&nbsp; &nbsp; &nbsp;Hi Farzaneh,
  <br> &gt; 
  <br> &gt;&nbs=
p; &nbsp; &nbsp;Thanks a lot for the review!
  <br> &gt; 
  <br> &gt;&nbsp;=
 &nbsp; &nbsp;On 30-01-2021 23:00, farzaneh badii wrote:
  <br> &gt;&nbsp; =
&nbsp; &nbsp;&gt; Hello
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbs=
p; &nbsp; &nbsp;&gt; Adding my comments on this document:&nbsp;
  <a href=
=3D"https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05" rel=3D"n=
oreferrer" target=3D"_blank">https://tools=2Eietf=2Eorg/html/draft-irtf-hrp=
c-guidelines-05</a> &lt;
  <a href=3D"https://tools=2Eietf=2Eorg/html/draft=
-irtf-hrpc-guidelines-05" rel=3D"noreferrer" target=3D"_blank">https://tool=
s=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05</a>&gt; &lt;
  <a href=3D=
"https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05" rel=3D"nore=
ferrer" target=3D"_blank">https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-g=
uidelines-05</a> &lt;
  <a href=3D"https://tools=2Eietf=2Eorg/html/draft-ir=
tf-hrpc-guidelines-05" rel=3D"noreferrer" target=3D"_blank">https://tools=
=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05</a>&gt;&gt;
  <br> &gt;&nb=
sp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 1=2E One major is=
sue that I see here and you might be able to easily solve it is that there =
is no distinction between user facing protocols and other protocols=2E For =
example, you ask for accessibility and consideration of culture etc=2E Are =
you asking all the protocols to be provided in multiple languages, even tho=
se that only&nbsp;developers&nbsp;and implementers use and not the actual u=
sers? You might want to clarify that=2E&nbsp;
  <br> &gt;&nbsp; &nbsp; &nbs=
p;&gt;
  <br> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;We had a quite extensive=
 discussion about this in relation to the presentation by Ramsey Nasr who c=
reate Qalb, an Arabic programming language=2E Programmers are the most freq=
uent 'users' of protocols - if we continue using only latin characters and =
English documentation in protocols we are likely to reproduce the existing =
lack of diversity in protocol developers communities=2E But we can make the=
 text on this clearer as well!
  <br> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;=
&gt; 2=2Esection 3=2E3=2E1 on connectivity, you mention that "considering t=
he fact that network quality and conditions vary across geography and time =
it is also important to design protocols such that they are reliable even o=
n low bandwidth =2E=2E=2E"=2E Then in your example you say: Middleboxes (in=
cluding NAT)=2E=2E=2E=2E can create potential for abuse=2E NAT is a Network=
 Address Translation protocol=2E I don't think it has anything to do with b=
andwidth=2E In this example you also mention CDNs=2E Are you suggesting tha=
t the developer should not consider "Middleboxes" protocols? I think you ne=
ed to work on the example of section 3=2E3=2E1 some more to make it clearer=
=2E&nbsp;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt; 
  <br> &gt;&nbsp=
; &nbsp; &nbsp;Excellent point - we'll address this in a future version=2E
=
  <br> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 3=2E section 3=2E3=2E20 re=
medy and attribution&nbsp;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; This section=
 worries me=2E As a&nbsp; scholar I have worked on cyber attribution to som=
e extent and believe&nbsp;in general when we have the right processes in pl=
ace,&nbsp;attribution is very important and can hold cyber-attackers accoun=
table=2E I am aware of some of the attribution processes and unfortunately =
some threat intelligence firms and open source intelligence organizations c=
an violate the privacy of individuals by profiling them=2E Also, uncontroll=
ed attribution mechanisms can lead to frivolous&nbsp;intellectual property =
claims=2E Both some threat intelligence firms and IP firms have used WHOIS =
extensively in their favor to attribute cybersecurity attacks and bring for=
ward IP claims=2E WHOIS protocol did not have the intention to actually ide=
ntify organizations and individuals, but to make them "contactable"=2Eand i=
t was still used and mined for so many years and those who have abused WHOI=
S have not been held accountable=2EWhen you suggest they consider "attribut=
ion" when developing protocols it
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; conce=
rns me because it is not enough that you limit attribution to organizations=
 and states=2E These kinds of attributions can be used against individuals =
and until we do not have the right preserving processes to put in place for=
 those who want to be in the attribution business, rights of the individual=
 can be at risk=2E there are very privacy conscious&nbsp;cybersecurity rese=
archers out there but unfortunately that does not ensure a systematic&nbsp;=
practice of attribution in a fair manner=2E And you mention attribution to =
associations is fine and may not directly negatively impact human rights=2E=
 Associations can themselves be at risk of frivolous&nbsp;attacks and frivo=
lous&nbsp;attribution=2E I am concerned about this paragraph=2E I think we =
should have a conversation about it=2E
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
=
  <br> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;In the proposed text I tried to=
 capture the consensus that emerged from the extensive discussion that was =
had on this list=2E Do you have concrete suggestions on how to better captu=
re that conensensus? I am afraid we would go back and repeat the same discu=
ssion=2E
  <br> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 4=2E Nice to see =
that you mention DoH=2E It's a great privacy preserving protocol=2E&nbsp;
 =
 <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <b=
r> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;Thanks!
  <br> &gt; 
  <br> &gt;&nb=
sp; &nbsp; &nbsp;Niels
  <br> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <=
br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br>=
 &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &g=
t;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&=
nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; Farzaneh
  <br>=
 &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &g=
t;&nbsp; &nbsp; &nbsp;&gt; On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath &l=
t;
  <a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_blank">corinneca=
th@gmail=2Ecom</a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail=2Ecom"=
 target=3D"_blank">corinnecath@gmail=2Ecom</a>&gt; &lt;mailto:
  <a href=3D=
"mailto:corinnecath@gmail=2Ecom" target=3D"_blank">corinnecath@gmail=2Ecom<=
/a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_bla=
nk">corinnecath@gmail=2Ecom</a>&gt;&gt;&gt; wrote:
  <br> &gt;&nbsp; &nbsp;=
 &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Hi all,
=
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbs=
p; &nbsp; &nbsp;I trust this email finds you well=2E I did a review of the =
draft, from my perspective as an academic=2E Take it as you please=2E My ma=
in concern is that some of the language reads a bit deterministic (as, I kn=
ow so does RFC 8280)=2E It means that a lot of onus is put on the impact of=
 a protocol, as opposed the role of the individuals that write them=2E&nbsp=
;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&n=
bsp; &nbsp; &nbsp;I think through out the document, it would be interesting=
 (especially in section 1 through 3=2E2=2E5) to see if you can rewrite such=
 that you speak more directly to the protocol developers=2E I think that se=
ction 3=2E3 does that well, in terms of the tone it takes=2E As it clearly =
connects the actions of protocol developers to their potential outcomes=2E&=
nbsp;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&g=
t;&nbsp; &nbsp; &nbsp;Hope this is helpful!&nbsp;
  <br> &gt;&nbsp; &nbsp; =
&nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Kind rega=
rds,&nbsp;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nb=
sp;&gt;&nbsp; &nbsp; &nbsp;Corinne
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <b=
r> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;------------------------=
---------
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbs=
p;&gt;&nbsp; &nbsp; &nbsp;*1=2E Introduction*
  <br> &gt;&nbsp; &nbsp; &nbs=
p;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;"It provides =
questions engineers should ask
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &=
gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; themselves when deve=
loping or improving protocols if they want to
  <br> &gt;&nbsp; &nbsp; &nbs=
p;&gt;&nbsp; &nbsp; &nbsp; &nbsp; understand their potential human rights i=
mpact=2E"
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbs=
p;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;&gt;&gt; mayb=
e if they want to understand potential human rights concerns? Impact seems =
a little deterministic, as you also mention in the next sentence, I wonder =
if you can prove such direct impact between protocol development in the IET=
F and impact on human rights=2E
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> =
&gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;"The research establishes
 =
 <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp=
; &nbsp; &nbsp; &nbsp; that human rights relate to standards and protocols,=
 and offers a
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp=
; common vocabulary of technical concepts that impact human rights and
  <b=
r> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; how these techni=
cal concepts can be combined to ensure that the
  <br> &gt;&nbsp; &nbsp; &n=
bsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; Internet remains an enabling environmen=
t for human rights=2E"
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp=
; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;=
&gt;&gt; same comment for the word impact, perhaps shape? influence? etc=2E=

  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  =
<br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3=
=2E1 &lt;
  <a href=3D"https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guid=
elines-05#section-3=2E1" rel=3D"noreferrer" target=3D"_blank">https://tools=
=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05#section-3=2E1</a> &lt;
  <=
a href=3D"https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05#sec=
tion-3=2E1" rel=3D"noreferrer" target=3D"_blank">https://tools=2Eietf=2Eorg=
/html/draft-irtf-hrpc-guidelines-05#section-3=2E1</a>&gt;&gt;=2E Human righ=
ts threats
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nb=
sp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;=
&gt;&nbsp; &nbsp; &nbsp; "Protocols and standards can harm or enable the ri=
ght to freedom of
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &=
nbsp; expression, right to non-discrimination, right to equal protection,
 =
 <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; right to part=
icipate in cultural life, arts and science, right to
  <br> &gt;&nbsp; &nbs=
p; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;freedo=
m of assembly and association, and the right to security=2E "
  <br> &gt;&n=
bsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp=
; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;&gt;&gt; again, deterministic langua=
ge=2E Perhaps soften or add more concrete examples for context, that draw f=
rom current IETF discussions/standards=2E
  <br> &gt;&nbsp; &nbsp; &nbsp;&g=
t;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
=
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;3=2E3 &lt;
  <a href=3D"https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-gu=
idelines-05#section-3=2E3" rel=3D"noreferrer" target=3D"_blank">https://too=
ls=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05#section-3=2E3</a> &lt;
 =
 <a href=3D"https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05#s=
ection-3=2E3" rel=3D"noreferrer" target=3D"_blank">https://tools=2Eietf=2Eo=
rg/html/draft-irtf-hrpc-guidelines-05#section-3=2E3</a>&gt;&gt;=2E Guidelin=
es for human rights considerations
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <b=
r> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> =
&gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;again, use of the word impa=
ct in the introduction=2E
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&n=
bsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp=
; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;=
--
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Corinne Cath - Sp=
eth
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Ph=2ED=2E Candid=
ate, Oxford Internet Institute &amp; Alan Turing Institute
  <br> &gt;&nbsp=
; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;=
Web: 
  <a href=3D"http://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath" rel=
=3D"noreferrer" target=3D"_blank">www=2Eoii=2Eox=2Eac=2Euk/people/corinne-c=
ath</a> &lt;
  <a href=3D"http://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-ca=
th" rel=3D"noreferrer" target=3D"_blank">http://www=2Eoii=2Eox=2Eac=2Euk/pe=
ople/corinne-cath</a>&gt; &lt;
  <a href=3D"http://www=2Eoii=2Eox=2Eac=2Euk=
/people/corinne-cath" rel=3D"noreferrer" target=3D"_blank">http://www=2Eoii=
=2Eox=2Eac=2Euk/people/corinne-cath</a> &lt;
  <a href=3D"http://www=2Eoii=
=2Eox=2Eac=2Euk/people/corinne-cath" rel=3D"noreferrer" target=3D"_blank">h=
ttp://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath</a>&gt;&gt;
  <br> &gt;&=
nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Email: 
  <a href=3D"mailto:ccat=
h@turing=2Eac=2Euk" target=3D"_blank">ccath@turing=2Eac=2Euk</a> &lt;mailto=
:
  <a href=3D"mailto:ccath@turing=2Eac=2Euk" target=3D"_blank">ccath@turin=
g=2Eac=2Euk</a>&gt; &lt;mailto:
  <a href=3D"mailto:ccath@turing=2Eac=2Euk"=
 target=3D"_blank">ccath@turing=2Eac=2Euk</a> &lt;mailto:
  <a href=3D"mail=
to:ccath@turing=2Eac=2Euk" target=3D"_blank">ccath@turing=2Eac=2Euk</a>&gt;=
&gt; &amp; 
  <a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_blank">=
corinnecath@gmail=2Ecom</a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gma=
il=2Ecom" target=3D"_blank">corinnecath@gmail=2Ecom</a>&gt; &lt;mailto:
  <=
a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_blank">corinnecath@gma=
il=2Ecom</a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail=2Ecom" targe=
t=3D"_blank">corinnecath@gmail=2Ecom</a>&gt;&gt;
  <br> &gt;&nbsp; &nbsp; &=
nbsp;&gt;&nbsp; &nbsp; &nbsp;Twitter: @C_CS
  <br> &gt;&nbsp; &nbsp; &nbsp;=
&gt;&nbsp; &nbsp; &nbsp;_______________________________________________
  <=
br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;hrpc mailing list
  <br=
> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;
  <a href=3D"mailto:hrpc=
@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a> &lt;mailto:
  <a href=3D=
"mailto:hrpc@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a>&gt; &lt;mail=
to:
  <a href=3D"mailto:hrpc@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg<=
/a> &lt;mailto:
  <a href=3D"mailto:hrpc@irtf=2Eorg" target=3D"_blank">hrpc=
@irtf=2Eorg</a>&gt;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &n=
bsp;
  <a href=3D"https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc" rel=3D"no=
referrer" target=3D"_blank">https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc<=
/a> &lt;
  <a href=3D"https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc" rel=
=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eorg/mailman/listinfo=
/hrpc</a>&gt; &lt;
  <a href=3D"https://www=2Eirtf=2Eorg/mailman/listinfo/h=
rpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eorg/mailman/=
listinfo/hrpc</a> &lt;
  <a href=3D"https://www=2Eirtf=2Eorg/mailman/listin=
fo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eorg/mail=
man/listinfo/hrpc</a>&gt;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt;
  <br> &g=
t;&nbsp; &nbsp; &nbsp;&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; ____________=
___________________________________
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; hrp=
c mailing list
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
  <a href=3D"mailto:hrp=
c@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a> &lt;mailto:
  <a href=
=3D"mailto:hrpc@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a>&gt;
  <br=
> &gt;&nbsp; &nbsp; &nbsp;&gt; 
  <a href=3D"https://www=2Eirtf=2Eorg/mailm=
an/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=
=2Eorg/mailman/listinfo/hrpc</a> &lt;
  <a href=3D"https://www=2Eirtf=2Eorg=
/mailman/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2E=
irtf=2Eorg/mailman/listinfo/hrpc</a>&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt=
;
  <br> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;-- 
  <br> &gt;&nbsp; &nbsp; =
&nbsp;Niels ten Oever, PhD
  <br> &gt;&nbsp; &nbsp; &nbsp;Postdoctoral Rese=
archer - Media Studies Department - University of Amsterdam
  <br> &gt;&nbs=
p; &nbsp; &nbsp;Postdoctoral Research Fellow - Communications Department - =
Texas A&amp;M University
  <br> &gt;&nbsp; &nbsp; &nbsp;Research Fellow - C=
entre for Internet and Human Rights - European University Viadrina
  <br> &=
gt;&nbsp; &nbsp; &nbsp;Associated Scholar - Centro de Tecnologia e Sociedad=
e - Funda=C3=A7=C3=A3o Get=C3=BAlio Vargas
  <br> &gt; 
  <br> &gt;&nbsp; &=
nbsp; &nbsp;W: 
  <a href=3D"https://nielstenoever=2Enet" rel=3D"noreferrer=
" target=3D"_blank">https://nielstenoever=2Enet</a> &lt;
  <a href=3D"https=
://nielstenoever=2Enet" rel=3D"noreferrer" target=3D"_blank">https://nielst=
enoever=2Enet</a>&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;E: 
  <a href=3D"mailt=
o:mail@nielstenoever=2Enet" target=3D"_blank">mail@nielstenoever=2Enet</a> =
&lt;mailto:
  <a href=3D"mailto:mail@nielstenoever=2Enet" target=3D"_blank"=
>mail@nielstenoever=2Enet</a>&gt;
  <br> &gt;&nbsp; &nbsp; &nbsp;T: @nielst=
enoever
  <br> &gt;&nbsp; &nbsp; &nbsp;P/S/WA: +31629051853
  <br> &gt;&nbs=
p; &nbsp; &nbsp;PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
  <b=
r> &gt; 
  <br> &gt;&nbsp; &nbsp; &nbsp;Read my dissertation 'Wired Norms' =
here: 
  <a href=3D"https://pure=2Euva=2Enl/ws/files/50781961/Thesis=2Epdf"=
 rel=3D"noreferrer" target=3D"_blank">https://pure=2Euva=2Enl/ws/files/5078=
1961/Thesis=2Epdf</a> &lt;
  <a href=3D"https://pure=2Euva=2Enl/ws/files/50=
781961/Thesis=2Epdf" rel=3D"noreferrer" target=3D"_blank">https://pure=2Euv=
a=2Enl/ws/files/50781961/Thesis=2Epdf</a>&gt;
  <br> &gt;&nbsp; &nbsp; &nbs=
p;_______________________________________________
  <br> &gt;&nbsp; &nbsp; =
&nbsp;hrpc mailing list
  <br> &gt;&nbsp; &nbsp; &nbsp;
  <a href=3D"mailto=
:hrpc@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a> &lt;mailto:
  <a hr=
ef=3D"mailto:hrpc@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a>&gt;
  <=
br> &gt;&nbsp; &nbsp; &nbsp;
  <a href=3D"https://www=2Eirtf=2Eorg/mailman/=
listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eor=
g/mailman/listinfo/hrpc</a> &lt;
  <a href=3D"https://www=2Eirtf=2Eorg/mail=
man/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=
=2Eorg/mailman/listinfo/hrpc</a>&gt;
  <br> &gt; 
  <br> 
  <br> -- 
  <br>=
 Niels ten Oever, PhD
  <br> Postdoctoral Researcher - Media Studies Depart=
ment - University of Amsterdam
  <br> Postdoctoral Research Fellow - Commun=
ications Department - Texas A&amp;M University
  <br> Research Fellow - Cen=
tre for Internet and Human Rights - European University Viadrina
  <br> Ass=
ociated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=A3o Get=
=C3=BAlio Vargas
  <br> 
  <br> W: 
  <a href=3D"https://nielstenoever=2Ene=
t" rel=3D"noreferrer" target=3D"_blank">https://nielstenoever=2Enet</a>
  <=
br> E: 
  <a href=3D"mailto:mail@nielstenoever=2Enet" target=3D"_blank">mai=
l@nielstenoever=2Enet</a>
  <br> T: @nielstenoever
  <br> P/S/WA: +31629051=
853
  <br> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
  <br> 
 =
 <br> Read my dissertation 'Wired Norms' here: 
  <a href=3D"https://pure=
=2Euva=2Enl/ws/files/50781961/Thesis=2Epdf" rel=3D"noreferrer" target=3D"_b=
lank">https://pure=2Euva=2Enl/ws/files/50781961/Thesis=2Epdf</a>
  <br> 
 <=
/blockquote>
</div></blockquote></div></body></html>
------9IMB0PRWVN7XOSA790BF4UG7T4P2YG--


From nobody Mon Feb  1 15:42:59 2021
Return-Path: <woody@pch.net>
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 2757B3A15A7 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:42:57 -0800 (PST)
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_PASS=-0.001, URIBL_BLOCKED=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 R9HaZg4462SQ for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:42:55 -0800 (PST)
Received: from mail.pch.net (keriomail.pch.net [206.220.231.84]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E70BE3A15A4 for <hrpc@irtf.org>; Mon,  1 Feb 2021 15:42:55 -0800 (PST)
X-Footer: cGNoLm5ldA==
Received: from [10.19.48.6] ([69.166.14.2]) by mail.pch.net (Kerio Connect 9.2.7 patch 3) with ESMTPS (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)) for hrpc@irtf.org; Mon, 1 Feb 2021 15:42:52 -0800
From: Bill Woodcock <woody@pch.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_93FCF144-A4B5-4AB0-9F56-4E790A36EB40"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Tue, 2 Feb 2021 00:42:50 +0100
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <20210201175026.GA25564@sources.org>
To: Hrpc <hrpc@irtf.org>
In-Reply-To: <20210201175026.GA25564@sources.org>
Message-Id: <3A402029-1B79-4617-88C8-FB48FD233566@pch.net>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/LI1WAuagSw027UHyRyHkxDg0TIw>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 01 Feb 2021 23:42:57 -0000

--Apple-Mail=_93FCF144-A4B5-4AB0-9F56-4E790A36EB40
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Feb 1, 2021, at 6:50 PM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:
>=20
> I'm confused here. I don't think that draft-irtf-hrpc-guidelines-05
> asks for internationalization of the specifications themselves (for
> instance by translating the RFC). Clarification is needed (and Niels
> ten Oever's reply about Ramsey Nasr and Qalb confuses me even more;
> are we talking about internationalization of protocols or
> internationalization of specifications?)

I am likewise confused.

I strongly believe that all protocols should be agnostic as to the =
character-sets carried as payload.

I also strongly believe that protocols themselves should not feature =
embedded text strings, in any language.  Any flags in the protocol =
itself should be binary labels, with meanings which can be documented in =
any language spoken by people developing things that use the protocol.

Is someone suggesting something other than those two cases?

                                -Bill


--Apple-Mail=_93FCF144-A4B5-4AB0-9F56-4E790A36EB40
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEm6XJ0FdpKWJHso4lb6RwSyiLf4cFAmAYkfoACgkQb6RwSyiL
f4eQXRAArLEDowxoj2Dh6WhlYjYGIdKjrBYDGv2pejO6gY+8qFolqRaqZ0m8pBXe
uvjIer8A7eHDm50v6nuKhSQ/ZeJed8JWDl2azG98YuoJwEdpuZcdJO/6fz7HQyMv
Vp7ocyqMhXSj6K6yCl7AspsgZuRHrcu9yq8vXu96U9cCC/thptOHiMHQ8uOOtCYU
/qnmwRxacIYraRUN1Ebk41HGqGNGrczNMMu0lvD/tM+Kyyi85A/yPZ9rKWFbKMen
a1AFJSSoPdIJS9dEqY7ItD5C51sle6TaLb4a4EYZtOXVNtsDNTefuhXCG/GqJuAy
U8FJHgVLCJidf1k2d8ayJOdMK2vVMkfUk9eNsntZoIGrr1Enx1XZL+CXTlAGMEce
dKHxtSH9U7blFPXP7qb1gOrovX66lfZ4PRaozho2v2X4RjrxWE0vwyfBuYXEXHa8
DgnhW3namoZZ0bByEIVBV2gQRbbEcrnvB5J2HQvHvDn7IrAWHn0ZSwdYjuouNjyd
ihy4tinpXygxiASsapAakGC8zDH/j7HMD7Qb9PdUhfqXYMooh20qDQ9FZ/KNoMnE
gcgWNmzOi7zBLmlBMwFQqApQmqx6/0AZT2bwnS0tGZPy6P/uNB5xF5+UsCec8eb1
CZRroD+j7n75Qd9+IgVE/06Yz4M+EJAXSM/eWDDRirkN7Mqh0bM=
=kOQV
-----END PGP SIGNATURE-----

--Apple-Mail=_93FCF144-A4B5-4AB0-9F56-4E790A36EB40--


From nobody Mon Feb  1 16:51:10 2021
Return-Path: <ajs@anvilwalrusden.com>
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 9C7F83A1616 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:51:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=yitter.info header.b=PbamdVC7; dkim=pass (1024-bit key) header.d=yitter.info header.b=hhbkTE0W
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 Ubt-cOi-oGjs for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:51:07 -0800 (PST)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2717C3A1615 for <hrpc@irtf.org>; Mon,  1 Feb 2021 16:51:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id B4B11BD5C6 for <hrpc@irtf.org>; Tue,  2 Feb 2021 00:51:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1612227065; bh=UgFO9HyrVdWjlopx0PQSFBe2RLS6+mJsmFxeFV1fRFw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=PbamdVC78ZPVQ8lSVZFKBaIrOSl5cD+K6sbcQMZnIOKP+gBkmdTQ+EtwtCl2ITYqQ nthXM9Ekhu80I2q8sEM65RTX3ZwtsnrMbe3ksEGRiJnIHEYm925AYx4V1kjd0n9Sjr L8PlJR4r0QZtBvSDedjHqOOTDqXZKRV63wMRBpqU=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0st8XrDRH5-e for <hrpc@irtf.org>; Tue,  2 Feb 2021 00:51:01 +0000 (UTC)
Date: Mon, 1 Feb 2021 19:51:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1612227061; bh=UgFO9HyrVdWjlopx0PQSFBe2RLS6+mJsmFxeFV1fRFw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hhbkTE0W747wL0YJ4FIY7uZ5ZCbx5b0Y/X5wZFeenTLiGK0GSooFh2v2MtBK4PQ7z 3Nj5j36pQfA/Va+yunDCFta5YRZLXHIQtypI4Oxm/4ljM27CzGYU0LvCDCDBWHA2z3 fRWB8SRXNTWKQVhcIRoMFjhjw5Ro2Hc5tPGAFxtU=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: hrpc@irtf.org
Message-ID: <20210202005101.kbz6azremoxgkzno@crankycanuck.ca>
Mail-Followup-To: hrpc@irtf.org
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <20210201175026.GA25564@sources.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20210201175026.GA25564@sources.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/z9dm7vKDEDJw-mAR5cM-jTdjdfI>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 00:51:10 -0000

Dear colleagues,

(ObDisclaimer: I work for the Internet Society, but this is only my
personal opinion and is no statement of ISOC's views.)

On Mon, Feb 01, 2021 at 06:50:27PM +0100, Stephane Bortzmeyer wrote:

>to think that there are no pure "developpers-only protocols". Error
>messages, for instance, tend to leak and therefore their
>internationalization is an issue.

I think this is true, but the entire discussion that arose as a result
of Ramsey Nasr's presentation was, in my opinion, rather unsatisfying
because in my opinion it conflated four different issues:

1.  The specification of protocols.  The IETF works in English and
always has.  IETF standards-track RFCs (and indeed, the entire series
AFAIK) have very generous republication terms in part to encourage
translation, but the official version of any standard published in the
RFC series is in English.  It is not hard to understand the arguments
about what problems that causes, but the experience with SDOs that try
to publish simultaneously in (for example) all the UN languages
suggests that too can create problems.  Technical translation is not a
trivial matter.  It doesn't seem to me that this piece of the puzzle
is considered in the current draft-irtf-hrpc-guidelines, and given the
contents of the I-D it probably shouldn't be in there.  But it seems
to be emerging in this discussion so I mention it for completeness.

2.  The protocols themselves.  I think Farzaneh's point upthread was
that this issue is more or less severe depending on the purpose of the
protocol.  What are the chances that a protocol element makes it into
a user context?  As Stephane notes, too, the definition of "user" on
the Internet is a little slippery, though it still seems to me that
(for example) identifiers from protocols that are clearly exposed in
an ordinary user's context (such as room names in XMPP or domain names
in URIs and URLs or email addresses) have more wide-ranging effects if
they are not internationalized than (say) possibly opaque strings that
are used in error codes or whatever.  The latter are rather more
easily dealt with via lookups and so on.  The draft as it stands seems
to treat this distinction without too much care, because it seems
pretty hard to imagine (for instance) tagging every error message in
every protocol with an RFC 5646 language-tag (even if that always
worked reliably, which it does not.  Domain names, for instance, are
often not words in any language).  There was a lot of work done by
the PRECIS working group on some of these matters:
https://tools.ietf.org/wg/precis/.

3.  The implementation of the protocols.  Many of the issues hinted at
in section 3.3.11 of the draft have as much to do with implementation
as they have to do with the protocols themselves.  (This actually
seems to me to be an overarching issue with the draft, which was a
concern I recall raising some time ago but that didn't seem to get any
traction, so I gave up.)  This is clearest in the bit, "The Internet
is a global medium, but many of its protocols and products are
developed with a certain audience in mind …."  There is rather a gap
between the protocols that undergird communications on the Internet
and the products that implement those protocols, and it is hard for me
to see how it helps protocol designers make the right trade-offs if we
can't be clear about which problem we're talking about.

4.  The tools used to work on all of the above.  One of the things I
found most vexing about the presentation the WG received was its
emphasis on the tools used to develop things (like, for instance, the
programming languages).  It is true that many programming languages
depend on ASCII and it is also true that there is a large quantity of
code that uses those programming languages.  I think that issue is
completely irrelevant to the matters above (if there were a Turing-complete
programming language that used Linear B for its writing system, I
presume such a system would still be able to implement protocols that
were specified in English), but the above-mentioned conflation of
protocols and products suggests that the issue of tools remains
somehow implicated in this passage.

The section in the draft is in any case actually about both localization and
internationalization, so the text is confusing in light of its heading
and the seeming cross-reference to internationalization (which I think
is actually a pointer to text in the referred-to W3C document).

I don't know how to fix any of this because I don't really know what
the text is trying to say, in part due to the conflation that I think
is there.  As I said, the last time I really engaged with this I
didn't feel like I made any headway.  But this is my feedback on
section 3.3.11, for whatever it's worth.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Feb  1 17:07:01 2021
Return-Path: <farzaneh.badii@gmail.com>
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 0F5B53A1628 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level: 
X-Spam-Status: No, score=-1.097 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 wVsYttvtLDUr for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:06:55 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 7BFCF3A1629 for <hrpc@irtf.org>; Mon,  1 Feb 2021 17:06:54 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id i187so25528375lfd.4 for <hrpc@irtf.org>; Mon, 01 Feb 2021 17:06:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cH0j+0uwJ/DFovoLVqo0GheNBT5P1fcEEBRtLhltVdA=; b=YYiwKRd50Cf1NzV8fOG2DEwvXIhAeRlua6iEaD1k1/2u+atry1xE5tMmpLIPNRN4T0 PQCHSEBjGuOMGC5CuMxm+CU65KfdOXvxS4qr5TaoCxeoSOD0qhwhajI21pbPExo+yJJ0 cjM0a6kKubFY53ANjz1c1BC1RDg+hVktnnO2ifOcamF94Vf1kEpu1bfh3gZMPf8zZO4v 8naZqWBvnFFUhMmlQgu4KFN1TXbQFMWyxGcShFf1Z7kCUmwBiIUdDK6WaZFSkcH9SZX8 3zuu07CaSFE9zr2+aF2E1rNsNlkI8DeU60RFOsbCpwTXQm8Dk3GkpRL5qZX9cjHhIsoX 9Jog==
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=cH0j+0uwJ/DFovoLVqo0GheNBT5P1fcEEBRtLhltVdA=; b=sViIFlbA9a1oL0XzOtQJrzgFH9+TtNSYMGowQG/jHkhfIFlwnmULQMsNVjMcqaB9kF q8l2Xh1/stL/y4YH9gLLkL5SWEXiV7Mz8v3Kh0XblRRwVaukYfVcxQfwwAAl0NZGNWwb 4n4JRmtVb7MV32DsEtXScRwg0GEYQVnvKFOEdDvZn6eiU5nxVG+Ak10vzYHWLglYFdNO aP3ti5W3SgUBlDHfW3cJCosy86op1zB4n4XA+TGYlpJik6+B3M/1NyPS8gdcGiRpd2AE VkH/1Uq/llrRO2r/Xoel2fSS8U9B2efjOPMiR4INqblVn3remRsQBHrBixXNaIH6Kxr3 BnWw==
X-Gm-Message-State: AOAM532EycErmne5tm0D1uLGhkT+8P4tgjoj/BeUSAJsRTos+UGvXqzi Jn4e7M7jocq7YQuPiQQ4rVAjQtIKRnr0S9ntOmI=
X-Google-Smtp-Source: ABdhPJxOkClYNRJq+0JTm5KNAkbBMQFgWU6Px79NRMzJumbPUOAL2z8zU6AVNaq0396HPeJu8WTSeMAWKtsCk7rrxXU=
X-Received: by 2002:a19:791c:: with SMTP id u28mr5116300lfc.168.1612228012080;  Mon, 01 Feb 2021 17:06:52 -0800 (PST)
MIME-Version: 1.0
Received: by 2002:ac2:4570:0:0:0:0:0 with HTTP; Mon, 1 Feb 2021 17:06:51 -0800 (PST)
In-Reply-To: <34ab9666-4521-49f7-831e-c22841743448@nielstenoever.net>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <08b61ab2-7840-d993-9946-c085861f4172@nielstenoever.net> <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com> <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net> <CAN1qJvCsbfnVePRFYAsySrgtaumUARc8PpnAX-cANu5Pgc7TMA@mail.gmail.com> <34ab9666-4521-49f7-831e-c22841743448@nielstenoever.net>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Mon, 1 Feb 2021 20:06:51 -0500
Message-ID: <CAN1qJvB++T1u+vRWLDcb9YoO5J8mJ_-bwf1c3jSPVrmzk=GDJw@mail.gmail.com>
To: Niels ten Oever <mail@nielstenoever.net>
Cc: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000f502c905ba501593"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/FRvVcgjQh2EX228D7vFZHnNCTEM>
Subject: [hrpc] Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 01:06:59 -0000

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

Niels,

I don't know how you come to consensus. I thought you as one of the
drafters need to make changes that capture the consensus. Seems like you
have had =E2=80=9Cmany discussions=E2=80=9D and all the points I have raise=
d been resolved
satisfactorily in this group in my absence. Then the only thing I can do is
to record my objection to paragraph 3.3.20: Attribution.

I don't think the paragraph as is in that document is human rights enabling
and frankly it has the potential to do the opposite. It is a mistake to
bring court and law enforcement to the discussion when the scope of this
group is "enabling human rights". It is a mistake to make a distinction
between natural and legal persons in this case and assume that natural
persons may not be harmed in the process because the distinction =E2=80=9Cm=
ay=E2=80=9D
protect them.

I brought reasons and they don't seem to be convincing to you or something
you want to work with and it seems to me it is too late now. So I get out
of your way and just record my objection to the paragraph.

Just to disclose: I have worked on cyber attack attribution processes
academically, and believe that attribution is one way to hold cyber
attackers accountable. I just don=E2=80=99t think we need the protocol deve=
loper
think about ways of attribution to make it easier to attribute cyber
attacks in court for legal remedy and include this in the guidelines for
human rights protection document as a =E2=80=9Caccess to legal remedy=E2=80=
=9D. Anonymity
makes attribution harder but still not impossible. Many John Doe=E2=80=99s =
have had
cases against them which provided the plaintiffs with the appropriate
remedies.





On Mon, Feb 1, 2021 at 5:19 PM Niels ten Oever <mail@nielstenoever.net>
wrote:

> Dear Farzaneh,
>
> Do your alterations reflect the content of the discussion, or mere your
> opinion?
>
> I hope we're seeking to reach a consensus during last call, not reopening
> the discussion.
>
> Best,
>
> Niels
>
> On Feb 1, 2021, at 22:22, farzaneh badii <farzaneh.badii@gmail.com> wrote=
:
>>
>> Here we go:
>>
>>
>> Question(s): Can your protocol facilitate a negatively impacted
>>
>>    party's right to the appropriate  legal remedy without
>> disproportionately impacting
>>
>>    other parties' human rights, especially their right to privacy?
>>
>>
>>    Explanation: Access to legal remedy is a human right that ensures
>>
>>    that individuals whose rights have been violated can seek remedies
>>
>>
>>
>>
>>    through a judicial authority.   Attribution (i.e. mechanisms in
>>
>>    protocols or architectures that are designed to make communications
>>
>>    or artifacts attributable might help with seeking the appropriate
>> remedy.)  to a certain computer or individual) can be
>>
>>    a part of this, since it may allow law enforcement agencies to
>>
>>    identify a possible violator .  However, attribution mechanisms may
>>
>    impede the exercise of the right to privacy.  The Special Rapporteur
>>
>>    for Freedom of Expression has also argued that anonymity is an
>>
>>    inherent part of freedom of expression.  [Kaye] Considering the
>>
>>    adverse impact of attribution on the right to privacy and freedom of
>>
>>    expression, attribution on an individual level may  is not be
>> consistent
>>
>>    with human rights.  However, attribution to corporate entities,
>>
>>    associations, and/or countries may not directly negatively impact
>>
>>    human rights.
>>
>>
>>    Impacts:
>>
>>
>>    -   Right to legal remedy
>>
>>
>>    -  Right to security
>>
> Farzaneh
>>
>>
>> On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever < mail@nielstenoever.net>
>> wrote:
>>
>>> Hi Farzaneh,
>>>
>>> On 31-01-2021 19:16, farzaneh badii wrote:
>>> > Hello Niels.
>>> >
>>> >
>>> > I don't know how we measure consensus here. But I remember weighing i=
n
>>> back then as well(When Mr. Curran weighed in back in 2019). Here is the
>>> thread:  https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution=
 <
>>> https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution>
>>> >
>>> > I can see that unfortunately I missed the discussion on this topic
>>> during the past year, and that's my fault, but I can bring reasons not =
to
>>> add "attribution and legal remedy" to this document at all.
>>> >
>>> > 1. Access to legal remedy is something that the States are supposedly
>>> in charge of bringing to their citizens.Which should (in theory) ensure
>>> that human rights are enforced. I don't think there was an intention to
>>> provide  mechanisms for "enforcement" of human rights in various legal
>>> systems through Internet protocols. As mentioned in the beginning of yo=
ur
>>> document:
>>> > "Human rights threats on the Internet come in a myriad of
>>> forms.* **P**rotocols and standards can harm or enable* the right to
>>> freedom of expression, right to non-discrimination, right to equal
>>> protection, right to participate in cultural life, arts and science, ri=
ght
>>> to freedom of assembly and association, and the right to security."
>>> >
>>> > So we are not in the business of enforcing but providing an enabling
>>> environment. Because if we want to help law enforcement and the judicia=
l
>>> authorities enforce human rights through Internet protocols we should b=
ear
>>> in mind that that they are not always staunch advocates of human rights=
. So
>>> what I assume we are trying to do here is to help Internet protocol not=
 to
>>> facilitate harm and "enable" human rights.
>>> >
>>>
>>> The text in the draft seeks to address this risk. I have sought to
>>> address all points made in that discussion, and I would not like to re-=
open
>>> that debate. If you feel the text is unbalanced, could you perhaps prov=
ide
>>> text suggestions?
>>>
>>> > 2. Attribution, section 3.3.20  of the Guideline, the authors assert
>>> that: "However, attribution to corporate entities, associations, and/or
>>> countries may not directly negatively impact human rights." I think thi=
s is
>>> not a very well backed up claim. Because in some cases some association=
s
>>> might be political or they might be human rights associations dealing w=
ith
>>> a dictatorship. Attribution to those associations certainly can impact
>>> their human rights negatively. Even when it comes to corporations, some
>>> CEOs of digital companies are put in jail because of the materials post=
ed
>>> on their websites. I don't think we can argue that attribution to corpo=
rate
>>> entities might not adversely impact human rights.
>>> >
>>>
>>> Again, the keyword in that sentence is 'may', so there is no strong
>>> claim made.
>>>
>>> > All in all I think section 3.3.20 does not help Internet Protocols
>>> enable human rights and it can be misinterpreted.
>>>
>>> I think the text in there is not strong and shows different perspective=
s
>>> and potential consequences. But again, happy to receive text suggestion=
s.
>>>
>>> >
>>> > And in my previous email I talked about the problems with threat
>>> intelligence agencies and some of their conducts and the use of WHOIS f=
or
>>> attribution (which was actually not designed to "identify" actors but
>>> unfortunately was used for that) so I will not reiterate here.
>>>
>>> From exactly that discussion we got the idea to remove individuals, and
>>> leave non-natural persons in.
>>>
>>> Best,
>>>
>>> Niels
>>>
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever <
>>> mail@nielstenoever.net <mailto: mail@nielstenoever.net>> wrote:
>>> >
>>> >     Hi Farzaneh,
>>> >
>>> >     Thanks a lot for the review!
>>> >
>>> >     On 30-01-2021 23:00, farzaneh badii wrote:
>>> >     > Hello
>>> >     >
>>> >     > Adding my comments on this document:
>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05 <
>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05> <
>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05 <
>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>>
>>> >     >
>>> >     > 1. One major issue that I see here and you might be able to
>>> easily solve it is that there is no distinction between user facing
>>> protocols and other protocols. For example, you ask for accessibility a=
nd
>>> consideration of culture etc. Are you asking all the protocols to be
>>> provided in multiple languages, even those that only developers and
>>> implementers use and not the actual users? You might want to clarify th=
at.
>>> >     >
>>> >
>>> >     We had a quite extensive discussion about this in relation to the
>>> presentation by Ramsey Nasr who create Qalb, an Arabic programming
>>> language. Programmers are the most frequent 'users' of protocols - if w=
e
>>> continue using only latin characters and English documentation in proto=
cols
>>> we are likely to reproduce the existing lack of diversity in protocol
>>> developers communities. But we can make the text on this clearer as wel=
l!
>>> >
>>> >     > 2.section 3.3.1 on connectivity, you mention that "considering
>>> the fact that network quality and conditions vary across geography and =
time
>>> it is also important to design protocols such that they are reliable ev=
en
>>> on low bandwidth ...". Then in your example you say: Middleboxes (inclu=
ding
>>> NAT).... can create potential for abuse. NAT is a Network Address
>>> Translation protocol. I don't think it has anything to do with bandwidt=
h.
>>> In this example you also mention CDNs. Are you suggesting that the
>>> developer should not consider "Middleboxes" protocols? I think you need=
 to
>>> work on the example of section 3.3.1 some more to make it clearer.
>>> >     >
>>> >
>>> >     Excellent point - we'll address this in a future version.
>>> >
>>> >     > 3. section 3.3.20 remedy and attribution
>>> >     > This section worries me. As a  scholar I have worked on cyber
>>> attribution to some extent and believe in general when we have the righ=
t
>>> processes in place, attribution is very important and can hold
>>> cyber-attackers accountable. I am aware of some of the attribution
>>> processes and unfortunately some threat intelligence firms and open sou=
rce
>>> intelligence organizations can violate the privacy of individuals by
>>> profiling them. Also, uncontrolled attribution mechanisms can lead to
>>> frivolous intellectual property claims. Both some threat intelligence f=
irms
>>> and IP firms have used WHOIS extensively in their favor to attribute
>>> cybersecurity attacks and bring forward IP claims. WHOIS protocol did n=
ot
>>> have the intention to actually identify organizations and individuals, =
but
>>> to make them "contactable".and it was still used and mined for so many
>>> years and those who have abused WHOIS have not been held accountable.Wh=
en
>>> you suggest they consider "attribution" when developing protocols it
>>> >     > concerns me because it is not enough that you limit attribution
>>> to organizations and states. These kinds of attributions can be used
>>> against individuals and until we do not have the right preserving proce=
sses
>>> to put in place for those who want to be in the attribution business,
>>> rights of the individual can be at risk. there are very privacy
>>> conscious cybersecurity researchers out there but unfortunately that do=
es
>>> not ensure a systematic practice of attribution in a fair manner. And y=
ou
>>> mention attribution to associations is fine and may not directly negati=
vely
>>> impact human rights. Associations can themselves be at risk of
>>> frivolous attacks and frivolous attribution. I am concerned about this
>>> paragraph. I think we should have a conversation about it.
>>> >     >
>>> >
>>> >     In the proposed text I tried to capture the consensus that emerge=
d
>>> from the extensive discussion that was had on this list. Do you have
>>> concrete suggestions on how to better capture that conensensus? I am af=
raid
>>> we would go back and repeat the same discussion.
>>> >
>>> >     > 4. Nice to see that you mention DoH. It's a great privacy
>>> preserving protocol.
>>> >     >
>>> >     >
>>> >
>>> >     Thanks!
>>> >
>>> >     Niels
>>> >
>>> >     >
>>> >     >
>>> >     >
>>> >     >
>>> >     >
>>> >     >
>>> >     >
>>> >     >
>>> >     > Farzaneh
>>> >     >
>>> >     >
>>> >     > On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath <
>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com> <mailto:
>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com>>> wrote:
>>> >     >
>>> >     >     Hi all,
>>> >     >
>>> >     >     I trust this email finds you well. I did a review of the
>>> draft, from my perspective as an academic. Take it as you please. My ma=
in
>>> concern is that some of the language reads a bit deterministic (as, I k=
now
>>> so does RFC 8280). It means that a lot of onus is put on the impact of =
a
>>> protocol, as opposed the role of the individuals that write them.
>>> >     >
>>> >     >     I think through out the document, it would be interesting
>>> (especially in section 1 through 3.2.5) to see if you can rewrite such =
that
>>> you speak more directly to the protocol developers. I think that sectio=
n
>>> 3.3 does that well, in terms of the tone it takes. As it clearly connec=
ts
>>> the actions of protocol developers to their potential outcomes.
>>> >     >
>>> >     >     Hope this is helpful!
>>> >     >
>>> >     >     Kind regards,
>>> >     >
>>> >     >     Corinne
>>> >     >
>>> >     >     ---------------------------------
>>> >     >
>>> >     >     *1. Introduction*
>>> >     >
>>> >     >     "It provides questions engineers should ask
>>> >     >
>>> >     >        themselves when developing or improving protocols if the=
y
>>> want to
>>> >     >        understand their potential human rights impact."
>>> >     >
>>> >     >
>>> >     >     >> maybe if they want to understand potential human rights
>>> concerns? Impact seems a little deterministic, as you also mention in t=
he
>>> next sentence, I wonder if you can prove such direct impact between
>>> protocol development in the IETF and impact on human rights.
>>> >     >
>>> >     >     "The research establishes
>>> >     >
>>> >     >        that human rights relate to standards and protocols, and
>>> offers a
>>> >     >        common vocabulary of technical concepts that impact huma=
n
>>> rights and
>>> >     >        how these technical concepts can be combined to ensure
>>> that the
>>> >     >        Internet remains an enabling environment for human
>>> rights."
>>> >     >
>>> >     >
>>> >     >     >> same comment for the word impact, perhaps shape?
>>> influence? etc.
>>> >     >
>>> >     >
>>> >     >           3.1 < https://tools.ietf.org/html/
>>> draft-irtf-hrpc-guidelines-05#section-3.1 < https://tools.ietf.org/html=
/
>>> draft-irtf-hrpc-guidelines-05#section-3.1>>. Human rights threats
>>> >     >
>>> >     >
>>> >     >
>>> >     >      "Protocols and standards can harm or enable the right to
>>> freedom of
>>> >     >        expression, right to non-discrimination, right to equal
>>> protection,
>>> >     >        right to participate in cultural life, arts and science,
>>> right to
>>> >     >
>>> >     >     freedom of assembly and association, and the right to
>>> security. "
>>> >     >
>>> >     >
>>> >     >     >> again, deterministic language. Perhaps soften or add mor=
e
>>> concrete examples for context, that draw from current IETF
>>> discussions/standards.
>>> >     >
>>> >     >
>>> >     >
>>> >     >           3.3 < https://tools.ietf.org/html/
>>> draft-irtf-hrpc-guidelines-05#section-3.3 < https://tools.ietf.org/html=
/
>>> draft-irtf-hrpc-guidelines-05#section-3.3>>. Guidelines for human
>>> rights considerations
>>> >     >
>>> >     >
>>> >     >
>>> >     >     again, use of the word impact in the introduction.
>>> >     >
>>> >     >
>>> >     >
>>> >     >
>>> >     >     --
>>> >     >     Corinne Cath - Speth
>>> >     >     Ph.D. Candidate, Oxford Internet Institute & Alan Turing
>>> Institute
>>> >     >
>>> >     >     Web: www.oii.ox.ac.uk/people/corinne-cath <
>>> http://www.oii.ox.ac.uk/people/corinne-cath> < http://www.oii.ox.ac.uk/
>>> people/corinne-cath < http://www.oii.ox.ac.uk/people/corinne-cath>>
>>> >     >     Email: ccath@turing.ac.uk <mailto: ccath@turing.ac.uk>
>>> <mailto: ccath@turing.ac.uk <mailto: ccath@turing.ac.uk>> &
>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com> <mailto:
>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com>>
>>> >     >     Twitter: @C_CS
>>> >     >     _______________________________________________
>>> >     >     hrpc mailing list
>>> >     >      hrpc@irtf.org <mailto: hrpc@irtf.org> <mailto:
>>> hrpc@irtf.org <mailto: hrpc@irtf.org>>
>>> >     >      https://www.irtf.org/mailman/listinfo/hrpc <
>>> https://www.irtf.org/mailman/listinfo/hrpc> <
>>> https://www.irtf.org/mailman/listinfo/hrpc <
>>> https://www.irtf.org/mailman/listinfo/hrpc>>
>>> >     >
>>> >     >
>>> >     > _______________________________________________
>>> >     > hrpc mailing list
>>> >     > hrpc@irtf.org <mailto: hrpc@irtf.org>
>>> >     > https://www.irtf.org/mailman/listinfo/hrpc <
>>> https://www.irtf.org/mailman/listinfo/hrpc>
>>> >     >
>>> >
>>> >     --
>>> >     Niels ten Oever, PhD
>>> >     Postdoctoral Researcher - Media Studies Department - University o=
f
>>> Amsterdam
>>> >     Postdoctoral Research Fellow - Communications Department - Texas
>>> A&M University
>>> >     Research Fellow - Centre for Internet and Human Rights - European
>>> University Viadrina
>>> >     Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=
=A7=C3=A3o
>>> Get=C3=BAlio Vargas
>>> >
>>> >     W: https://nielstenoever.net < https://nielstenoever.net>
>>> >     E: mail@nielstenoever.net <mailto: mail@nielstenoever.net>
>>> >     T: @nielstenoever
>>> >     P/S/WA: +31629051853
>>> >     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>>> >
>>> >     Read my dissertation 'Wired Norms' here:
>>> https://pure.uva.nl/ws/files/50781961/Thesis.pdf <
>>> https://pure.uva.nl/ws/files/50781961/Thesis.pdf>
>>> >     _______________________________________________
>>> >     hrpc mailing list
>>> >      hrpc@irtf.org <mailto: hrpc@irtf.org>
>>> >      https://www.irtf.org/mailman/listinfo/hrpc <
>>> https://www.irtf.org/mailman/listinfo/hrpc>
>>> >
>>>
>>> --
>>> Niels ten Oever, PhD
>>> Postdoctoral Researcher - Media Studies Department - University of
>>> Amsterdam
>>> Postdoctoral Research Fellow - Communications Department - Texas A&M
>>> University
>>> Research Fellow - Centre for Internet and Human Rights - European
>>> University Viadrina
>>> Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=
=A3o Get=C3=BAlio
>>> Vargas
>>>
>>> W: https://nielstenoever.net
>>> E: mail@nielstenoever.net
>>> T: @nielstenoever
>>> P/S/WA: +31629051853
>>> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>>>
>>> Read my dissertation 'Wired Norms' here: https://pure.uva.nl/ws/files/
>>> 50781961/Thesis.pdf
>>>
>>

--=20
Farzaneh

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

<div>Niels,=C2=A0<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">I =
don&#39;t know how you come to consensus. I thought you as one of the draft=
ers need to make changes that capture the consensus. Seems like you have ha=
d =E2=80=9Cmany discussions=E2=80=9D and all the points I have raised been =
resolved satisfactorily in this group in my absence. Then the only thing I =
can do is to record my objection to paragraph 3.3.20: Attribution.=C2=A0</d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">I don&#39;t think the para=
graph as is in that document is human rights enabling and frankly it has th=
e potential to do the opposite. It is a mistake to bring court and law enfo=
rcement to the discussion when the scope of this group is &quot;enabling hu=
man rights&quot;. It is a mistake to make a distinction between natural and=
 legal persons in this case and assume that natural persons may not be harm=
ed in the process because the distinction =E2=80=9Cmay=E2=80=9D protect the=
m.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">I brought reaso=
ns and they don&#39;t seem to be convincing to you or something you want to=
 work with and it seems to me it is too late now. So I get out of your way =
and just record my objection to the paragraph.=C2=A0</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Just to disclose: I have worked on cyber attac=
k attribution processes academically, and believe that attribution is one w=
ay to hold cyber attackers accountable. I just don=E2=80=99t think we need =
the protocol developer think about ways of attribution to make it easier to=
 attribute cyber attacks in court for legal remedy and include this in the =
guidelines for human rights protection document as a =E2=80=9Caccess to leg=
al remedy=E2=80=9D. Anonymity makes attribution harder but still not imposs=
ible. Many John Doe=E2=80=99s have had cases against them which provided th=
e plaintiffs with the appropriate remedies.=C2=A0</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D=
"auto"><br></div><div dir=3D"auto"><br><div class=3D"gmail_quote" dir=3D"au=
to"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 1, 2021 at 5:19 PM Ni=
els ten Oever &lt;<a href=3D"mailto:mail@nielstenoever.net" target=3D"_blan=
k">mail@nielstenoever.net</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div style=3D"zoom:0%"><div dir=3D"auto">Dear Farzaneh,<br><br></div>
<div dir=3D"auto">Do your alterations reflect the content of the discussion=
, or mere your opinion?<br><br></div>
<div dir=3D"auto">I hope we&#39;re seeking to reach a consensus during last=
 call, not reopening the discussion.<br><br></div>
<div dir=3D"auto">Best,<br><br></div>
<div dir=3D"auto">Niels<br><br></div>
<div class=3D"gmail_quote">On Feb 1, 2021, at 22:22, farzaneh badii &lt;<a =
href=3D"mailto:farzaneh.badii@gmail.com" target=3D"_blank">farzaneh.badii@g=
mail.com</a>&gt; wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0p=
t 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir=3D"ltr">
 <div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">
  Here we go:
 </div>
 <div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">
  <br>
 </div>
 <div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"></di=
v>
 <div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">
  <br>
 </div>
 <div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">Question(s): Can your protocol facilitate a nega=
tively impacted</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>party&#39;s right to<f=
ont color=3D"#ff0000">=C2=A0the appropriate </font>
   <strike>
    =C2=A0legal=20
   </strike>remedy without disproportionately impacting</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>other parties&#39; hum=
an rights, especially their right to privacy?</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica;min-height:14px"><br></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>Explanation: Access to legal remedy is a huma=
n right that ensures
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>that individuals whose rights have been viola=
ted can seek remedies
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica;min-height:14px"><br></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica;min-height:14px"><br></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica;min-height:14px"><br></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>through a judicial authority.
   </strike><span>=C2=A0 </span>Attribution (i.e. mechanisms in</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>protocols or architect=
ures that are designed to make communications</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>or artifacts attributa=
ble <font color=3D"#ff0000">might help with seeking the appropriate remedy<=
/font>.)=C2=A0
   <strike>
    to a certain computer or individual)
   </strike>=20
   <strike>
    can be
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>a part of this, since it may allow law enforc=
ement agencies to
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>identify a possible violator
   </strike>.<span>=C2=A0 </span>However, attribution mechanisms may</p></d=
iv></div></blockquote></div></div><div style=3D"zoom:0%"><div class=3D"gmai=
l_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"=
><div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>impede the exercise of=
 the right to privacy.<span>=C2=A0 </span>The Special Rapporteur</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>for Freedom of Express=
ion has also argued that anonymity is an</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>inherent part of freed=
om of expression.<span>=C2=A0 </span>[Kaye] Considering the</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>adverse impact of attr=
ibution on the right to privacy and freedom of</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>expression, attributio=
n on an individual level
   <strike>
     may
   </strike>=C2=A0<font color=3D"#ff0000">is=C2=A0</font>not=20
   <strike>
    be
   </strike> consistent</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>with human rights.<spa=
n>=C2=A0
    <strike>=20
    </strike></span>
   <strike>
    However, attribution to corporate entities,
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>associations, and/or countries may not direct=
ly negatively impact
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>human rights.
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica;min-height:14px"><br></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>Impacts:</p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica;min-height:14px">
   <strike>
    <br>
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica">
   <strike>
    <span>=C2=A0=C2=A0 </span>-
    <span>=C2=A0 </span>Right to legal remedy
   </strike></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica;min-height:14px"><br></p>=20
  <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:nor=
mal;font-family:Helvetica"><span>=C2=A0=C2=A0 </span>-<span>=C2=A0 </span>R=
ight to security</p>
 </div></div></blockquote></div></div><div style=3D"zoom:0%"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"=
ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">=
</div>
 <div>
  <div dir=3D"ltr" data-smartmail=3D"gmail_signature">
   <div dir=3D"ltr">
    <div>
     <font face=3D"verdana, sans-serif">Farzaneh </font>
    </div>
   </div>
  </div>
 </div>
 <br>
</div></blockquote></div></div><div style=3D"zoom:0%"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<div class=3D"gmail_quote">
 <div dir=3D"ltr" class=3D"gmail_attr">
  On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever &lt;
  <a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielsten=
oever.net</a>&gt; wrote:
  <br>
 </div>
 <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">
  Hi Farzaneh,
  <br>=20
  <br> On 31-01-2021 19:16, farzaneh badii wrote:
  <br> &gt; Hello Niels.
  <br> &gt;=20
  <br> &gt;=20
  <br> &gt; I don&#39;t know how we measure consensus here. But I remember =
weighing in back then as well(When Mr. Curran weighed in back in 2019). Her=
e is the thread:=C2=A0
  <a href=3D"https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution=
" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.org/<wbr>ar=
ch/browse/hrpc/?q=3D<wbr>attribution</a> &lt;
  <a href=3D"https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution=
" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.org/<wbr>ar=
ch/browse/hrpc/?q=3D<wbr>attribution</a>&gt;
  <br> &gt;=20
  <br> &gt; I can see that unfortunately I missed the=C2=A0discussion on th=
is topic during the past year, and that&#39;s my fault, but I can bring rea=
sons not to add &quot;attribution and legal remedy&quot; to this document a=
t all.=C2=A0
  <br> &gt;=20
  <br> &gt; 1. Access to legal remedy is something that the States are supp=
osedly in charge of bringing to their citizens.Which should (in theory) ens=
ure that human rights are enforced. I don&#39;t think there=C2=A0was an int=
ention to=C2=A0 provide=C2=A0 mechanisms for &quot;enforcement&quot; of hum=
an rights in various legal systems through Internet protocols. As mentioned=
=C2=A0in the beginning of your document:=C2=A0
  <br> &gt; &quot;Human rights threats on the Internet come in a myriad of =
forms.*=C2=A0**P**rotocols and standards can harm or enable* the right to f=
reedom of=C2=A0expression, right to non-discrimination, right to equal prot=
ection,=C2=A0right to participate in cultural life, arts and science, right=
 to=C2=A0freedom of assembly and association, and the right to security.&qu=
ot;=C2=A0
  <br> &gt;=20
  <br> &gt; So we are not in the business of enforcing but providing=C2=A0a=
n enabling environment. Because=C2=A0if we want to help law enforcement and=
 the judicial authorities enforce human rights through=C2=A0Internet=C2=A0p=
rotocols we should bear in mind that that they are not always staunch advoc=
ates of human rights. So what I assume we are trying to do here is to help =
Internet protocol not to facilitate harm and &quot;enable&quot; human right=
s.=C2=A0
  <br> &gt;=20
  <br>=20
  <br> The text in the draft seeks to address this risk. I have sought to a=
ddress all points made in that discussion, and I would not like to re-open =
that debate. If you feel the text is unbalanced, could you perhaps provide =
text suggestions?=20
  <br>=20
  <br> &gt; 2. Attribution, section 3.3.20=C2=A0 of the Guideline, the auth=
ors assert that: &quot;However, attribution to corporate entities,=C2=A0ass=
ociations, and/or countries may not directly negatively impact=C2=A0human r=
ights.&quot; I think this is not a very=C2=A0well backed up claim. Because =
in some cases some associations might be political or they might be human r=
ights associations dealing with a dictatorship. Attribution to those associ=
ations certainly can impact their human rights negatively. Even when it com=
es to corporations, some CEOs of digital companies are put in jail because =
of the materials posted on their websites. I don&#39;t think we can argue t=
hat attribution to corporate entities might not adversely impact human righ=
ts.
  <br> &gt;=20
  <br>=20
  <br> Again, the keyword in that sentence is &#39;may&#39;, so there is no=
 strong claim made.=20
  <br>=20
  <br> &gt; All in all I think section 3.3.20 does not help Internet Protoc=
ols enable human rights and it can be misinterpreted.=20
  <br>=20
  <br> I think the text in there is not strong and shows different perspect=
ives and potential consequences. But again, happy to receive text suggestio=
ns.=20
  <br>=20
  <br> &gt;=20
  <br> &gt; And in my previous email I talked about the problems with threa=
t intelligence agencies and some of their conducts and the use of WHOIS for=
 attribution (which was actually not designed to &quot;identify&quot; actor=
s but unfortunately was used for that) so I will not reiterate here.=20
  <br>=20
  <br> From exactly that discussion we got the idea to remove individuals, =
and leave non-natural persons in.=20
  <br>=20
  <br> Best,
  <br>=20
  <br> Niels
  <br>=20
  <br> &gt;=20
  <br> &gt;=20
  <br> &gt;=20
  <br> &gt;=20
  <br> &gt;=20
  <br> &gt;=20
  <br> &gt;=20
  <br> &gt; On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever &lt;
  <a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielsten=
oever.net</a> &lt;mailto:
  <a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielsten=
oever.net</a>&gt;&gt; wrote:
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Hi Farzaneh,
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Thanks a lot for the review!
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0On 30-01-2021 23:00, farzaneh badii wrote:
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; Hello
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; Adding my comments on this document:=C2=
=A0
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-ir=
tf-hrpc-guidelines-05</a> &lt;
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-ir=
tf-hrpc-guidelines-05</a>&gt; &lt;
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-ir=
tf-hrpc-guidelines-05</a> &lt;
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-ir=
tf-hrpc-guidelines-05</a>&gt;<wbr>&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; 1. One major issue that I see here and =
you might be able to easily solve it is that there is no distinction betwee=
n user facing protocols and other protocols. For example, you ask for acces=
sibility and consideration of culture etc. Are you asking all the protocols=
 to be provided in multiple languages, even those that only=C2=A0developers=
=C2=A0and implementers use and not the actual users? You might want to clar=
ify that.=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0We had a quite extensive discussion about th=
is in relation to the presentation by Ramsey Nasr who create Qalb, an Arabi=
c programming language. Programmers are the most frequent &#39;users&#39; o=
f protocols - if we continue using only latin characters and English docume=
ntation in protocols we are likely to reproduce the existing lack of divers=
ity in protocol developers communities. But we can make the text on this cl=
earer as well!
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; 2.section 3.3.1 on connectivity, you me=
ntion that &quot;considering the fact that network quality and conditions v=
ary across geography and time it is also important to design protocols such=
 that they are reliable even on low bandwidth ...&quot;. Then in your examp=
le you say: Middleboxes (including NAT).... can create potential for abuse.=
 NAT is a Network Address Translation protocol. I don&#39;t think it has an=
ything to do with bandwidth. In this example you also mention CDNs. Are you=
 suggesting that the developer should not consider &quot;Middleboxes&quot; =
protocols? I think you need to work on the example of section 3.3.1 some mo=
re to make it clearer.=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Excellent point - we&#39;ll address this in =
a future version.
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; 3. section 3.3.20 remedy and attributio=
n=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; This section worries me. As a=C2=A0 sch=
olar I have worked on cyber attribution to some extent and believe=C2=A0in =
general when we have the right processes in place,=C2=A0attribution is very=
 important and can hold cyber-attackers accountable. I am aware of some of =
the attribution processes and unfortunately some threat intelligence firms =
and open source intelligence organizations can violate the privacy of indiv=
iduals by profiling them. Also, uncontrolled attribution mechanisms can lea=
d to frivolous=C2=A0intellectual property claims. Both some threat intellig=
ence firms and IP firms have used WHOIS extensively in their favor to attri=
bute cybersecurity attacks and bring forward IP claims. WHOIS protocol did =
not have the intention to actually identify organizations and individuals, =
but to make them &quot;contactable&quot;.and it was still used and mined fo=
r so many years and those who have abused WHOIS have not been held accounta=
ble.When you suggest they consider &quot;attribution&quot; when developing =
protocols it
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; concerns me because it is not enough th=
at you limit attribution to organizations and states. These kinds of attrib=
utions can be used against individuals and until we do not have the right p=
reserving processes to put in place for those who want to be in the attribu=
tion business, rights of the individual can be at risk. there are very priv=
acy conscious=C2=A0cybersecurity researchers out there but unfortunately th=
at does not ensure a systematic=C2=A0practice of attribution in a fair mann=
er. And you mention attribution to associations is fine and may not directl=
y negatively impact human rights. Associations can themselves be at risk of=
 frivolous=C2=A0attacks and frivolous=C2=A0attribution. I am concerned abou=
t this paragraph. I think we should have a conversation about it.
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0In the proposed text I tried to capture the =
consensus that emerged from the extensive discussion that was had on this l=
ist. Do you have concrete suggestions on how to better capture that conense=
nsus? I am afraid we would go back and repeat the same discussion.
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; 4. Nice to see that you mention DoH. It=
&#39;s a great privacy preserving protocol.=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Thanks!
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Niels
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; Farzaneh
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; On Sat, Jan 30, 2021 at 10:35 AM Corinn=
e Cath &lt;
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a>&gt; &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a>&gt;&gt;&gt; wrote:
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Hi all,
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0I trust this email f=
inds you well. I did a review of the draft, from my perspective as an acade=
mic. Take it as you please. My main concern is that some of the language re=
ads a bit deterministic (as, I know so does RFC 8280). It means that a lot =
of onus is put on the impact of a protocol, as opposed the role of the indi=
viduals that write them.=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0I think through out =
the document, it would be interesting (especially in section 1 through 3.2.=
5) to see if you can rewrite such that you speak more directly to the proto=
col developers. I think that section 3.3 does that well, in terms of the to=
ne it takes. As it clearly connects the actions of protocol developers to t=
heir potential outcomes.=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Hope this is helpful=
!=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Kind regards,=C2=A0
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Corinne
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0--------------------=
---------<wbr>----
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0*1. Introduction*
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&quot;It provides qu=
estions engineers should ask
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 themselves w=
hen developing or improving protocols if they want to
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 understand t=
heir potential human rights impact.&quot;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;&gt; maybe if th=
ey want to understand potential human rights concerns? Impact seems a littl=
e deterministic, as you also mention in the next sentence, I wonder if you =
can prove such direct impact between protocol development in the IETF and i=
mpact on human rights.
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&quot;The research e=
stablishes
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 that human r=
ights relate to standards and protocols, and offers a
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 common vocab=
ulary of technical concepts that impact human rights and
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 how these te=
chnical concepts can be combined to ensure that the
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Internet rem=
ains an enabling environment for human rights.&quot;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;&gt; same commen=
t for the word impact, perhaps shape? influence? etc.
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A03.1 &lt;
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sect=
ion-3.1" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<=
wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.1</a> &lt;
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sect=
ion-3.1" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<=
wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.1</a>&gt;&gt;. Human right=
s threats
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 &quot;Protocols and=
 standards can harm or enable the right to freedom of
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 expression, =
right to non-discrimination, right to equal protection,
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 right to par=
ticipate in cultural life, arts and science, right to
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0freedom of assembly =
and association, and the right to security. &quot;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;&gt; again, dete=
rministic language. Perhaps soften or add more concrete examples for contex=
t, that draw from current IETF discussions/standards.
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A03.3 &lt;
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sect=
ion-3.3" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<=
wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.3</a> &lt;
  <a href=3D"https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sect=
ion-3.3" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<=
wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.3</a>&gt;&gt;. Guidelines =
for human rights considerations
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0again, use of the wo=
rd impact in the introduction.
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0--
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Corinne Cath - Speth
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Ph.D. Candidate, Oxf=
ord Internet Institute &amp; Alan Turing Institute
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Web:=20
  <a href=3D"http://www.oii.ox.ac.uk/people/corinne-cath" rel=3D"noreferrer=
" target=3D"_blank">www.oii.ox.ac.uk/people/<wbr>corinne-cath</a> &lt;
  <a href=3D"http://www.oii.ox.ac.uk/people/corinne-cath" rel=3D"noreferrer=
" target=3D"_blank">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>&gt=
; &lt;
  <a href=3D"http://www.oii.ox.ac.uk/people/corinne-cath" rel=3D"noreferrer=
" target=3D"_blank">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a> &l=
t;
  <a href=3D"http://www.oii.ox.ac.uk/people/corinne-cath" rel=3D"noreferrer=
" target=3D"_blank">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>&gt=
;&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Email:=20
  <a href=3D"mailto:ccath@turing.ac.uk" target=3D"_blank">ccath@turing.ac.u=
k</a> &lt;mailto:
  <a href=3D"mailto:ccath@turing.ac.uk" target=3D"_blank">ccath@turing.ac.u=
k</a>&gt; &lt;mailto:
  <a href=3D"mailto:ccath@turing.ac.uk" target=3D"_blank">ccath@turing.ac.u=
k</a> &lt;mailto:
  <a href=3D"mailto:ccath@turing.ac.uk" target=3D"_blank">ccath@turing.ac.u=
k</a>&gt;&gt; &amp;=20
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a>&gt; &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a> &lt;mailto:
  <a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gm=
ail.com</a>&gt;&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Twitter: @C_CS
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0____________________=
_________<wbr>__________________
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0hrpc mailing list
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a> &lt;=
mailto:
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>&gt; =
&lt;mailto:
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a> &lt;=
mailto:
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>&gt;&=
gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a> &lt;
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt; =
&lt;
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a> &lt;
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;&=
gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; ______________________________<wbr>____=
_____________
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt; hrpc mailing list
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=20
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a> &lt;=
mailto:
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;=20
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a> &lt;
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0&gt;
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0--=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Niels ten Oever, PhD
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Postdoctoral Researcher - Media Studies Depa=
rtment - University of Amsterdam
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Postdoctoral Research Fellow - Communication=
s Department - Texas A&amp;M University
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Research Fellow - Centre for Internet and Hu=
man Rights - European University Viadrina
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Associated Scholar - Centro de Tecnologia e =
Sociedade - Funda=C3=A7=C3=A3o Get=C3=BAlio Vargas
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0W:=20
  <a href=3D"https://nielstenoever.net" rel=3D"noreferrer" target=3D"_blank=
">https://nielstenoever.net</a> &lt;
  <a href=3D"https://nielstenoever.net" rel=3D"noreferrer" target=3D"_blank=
">https://nielstenoever.net</a>&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0E:=20
  <a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielsten=
oever.net</a> &lt;mailto:
  <a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielsten=
oever.net</a>&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0T: @nielstenoever
  <br> &gt;=C2=A0 =C2=A0 =C2=A0P/S/WA: +31629051853
  <br> &gt;=C2=A0 =C2=A0 =C2=A0PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A=
 468A C8B3
  <br> &gt;=20
  <br> &gt;=C2=A0 =C2=A0 =C2=A0Read my dissertation &#39;Wired Norms&#39; h=
ere:=20
  <a href=3D"https://pure.uva.nl/ws/files/50781961/Thesis.pdf" rel=3D"noref=
errer" target=3D"_blank">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.=
pdf</a> &lt;
  <a href=3D"https://pure.uva.nl/ws/files/50781961/Thesis.pdf" rel=3D"noref=
errer" target=3D"_blank">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.=
pdf</a>&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0_____________________________<wbr>__________=
________
  <br> &gt;=C2=A0 =C2=A0 =C2=A0hrpc mailing list
  <br> &gt;=C2=A0 =C2=A0 =C2=A0
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a> &lt;=
mailto:
  <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>&gt;
  <br> &gt;=C2=A0 =C2=A0 =C2=A0
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a> &lt;
  <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferrer"=
 target=3D"_blank">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
  <br> &gt;=20
  <br>=20
  <br> --=20
  <br> Niels ten Oever, PhD
  <br> Postdoctoral Researcher - Media Studies Department - University of A=
msterdam
  <br> Postdoctoral Research Fellow - Communications Department - Texas A&a=
mp;M University
  <br> Research Fellow - Centre for Internet and Human Rights - European Un=
iversity Viadrina
  <br> Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=
=C3=A3o Get=C3=BAlio Vargas
  <br>=20
  <br> W:=20
  <a href=3D"https://nielstenoever.net" rel=3D"noreferrer" target=3D"_blank=
">https://nielstenoever.net</a>
  <br> E:=20
  <a href=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielsten=
oever.net</a>
  <br> T: @nielstenoever
  <br> P/S/WA: +31629051853
  <br> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
  <br>=20
  <br> Read my dissertation &#39;Wired Norms&#39; here:=20
  <a href=3D"https://pure.uva.nl/ws/files/50781961/Thesis.pdf" rel=3D"noref=
errer" target=3D"_blank">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.=
pdf</a>
  <br>=20
 </blockquote>
</div></blockquote></div></div></blockquote></div></div>
<br><br>-- <br><div dir=3D"ltr"><div><font face=3D"verdana, sans-serif">Far=
zaneh </font></div></div><br>

--000000000000f502c905ba501593--


From nobody Mon Feb  1 23:58:02 2021
Return-Path: <mail@nielstenoever.net>
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 EB6B13A1826 for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 23:58:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 erBgm7KFOYnY for <hrpc@ietfa.amsl.com>; Mon,  1 Feb 2021 23:57:57 -0800 (PST)
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 BE37F3A1824 for <hrpc@irtf.org>; Mon,  1 Feb 2021 23:57:56 -0800 (PST)
In-Reply-To: <CAN1qJvB++T1u+vRWLDcb9YoO5J8mJ_-bwf1c3jSPVrmzk=GDJw@mail.gmail.com>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <08b61ab2-7840-d993-9946-c085861f4172@nielstenoever.net> <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com> <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net> <CAN1qJvCsbfnVePRFYAsySrgtaumUARc8PpnAX-cANu5Pgc7TMA@mail.gmail.com> <34ab9666-4521-49f7-831e-c22841743448@nielstenoever.net> <CAN1qJvB++T1u+vRWLDcb9YoO5J8mJ_-bwf1c3jSPVrmzk=GDJw@mail.gmail.com>
X-Referenced-Uid: 28718
Thread-Topic: [hrpc] Comment on draft-guidelines for RG Last Call
User-Agent: Android
X-Is-Generated-Message-Id: true
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----OQIFQ1OJ1RUXT9OK0OOL5Z3OXH2T77"
Content-Transfer-Encoding: 7bit
From: Niels ten Oever <mail@nielstenoever.net>
Date: Tue, 02 Feb 2021 08:57:40 +0100
To: farzaneh badii <farzaneh.badii@gmail.com>
CC: Hrpc <hrpc@irtf.org>
Message-ID: <46063596-f537-417f-89c1-d09e9c934b63@nielstenoever.net>
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 6b46cf40bbb127d11a761a87fa91a122
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/cCPjHXpm1Bf-_rXa_Q64m2pQdiw>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 07:58:01 -0000

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

Dear Farzaneh,

In the extensive discussion between you, John, Amelia, Pran=
esh and others you were the only one who said attribution has no role in th=
is document whatsoever=2E You reiterate this position=2E=C2=A0 But that mig=
ht mean that you are in the rough=2E 

Best,

Niels

On Feb 2, 2021, 02:06,=
 at 02:06, farzaneh badii <farzaneh=2Ebadii@gmail=2Ecom> wrote:
>Niels,
>
>=
I don't know how you come to consensus=2E I thought you as one of the
>draf=
ters need to make changes that capture the consensus=2E Seems like
>you
>ha=
ve had =E2=80=9Cmany discussions=E2=80=9D and all the points I have raised =
been
>resolved
>satisfactorily in this group in my absence=2E Then the only=
 thing I can
>do is
>to record my objection to paragraph 3=2E3=2E20: Attrib=
ution=2E
>
>I don't think the paragraph as is in that document is human rig=
hts
>enabling
>and frankly it has the potential to do the opposite=2E It is=
 a mistake to
>bring court and law enforcement to the discussion when the s=
cope of
>this
>group is "enabling human rights"=2E It is a mistake to make =
a distinction
>between natural and legal persons in this case and assume th=
at natural
>persons may not be harmed in the process because the distinctio=
n =E2=80=9Cmay=E2=80=9D
>protect them=2E
>
>I brought reasons and they don'=
t seem to be convincing to you or
>something
>you want to work with and it =
seems to me it is too late now=2E So I get
>out
>of your way and just recor=
d my objection to the paragraph=2E
>
>Just to disclose: I have worked on cy=
ber attack attribution processes
>academically, and believe that attributio=
n is one way to hold cyber
>attackers accountable=2E I just don=E2=80=99t t=
hink we need the protocol
>developer
>think about ways of attribution to ma=
ke it easier to attribute cyber
>attacks in court for legal remedy and incl=
ude this in the guidelines
>for
>human rights protection document as a =E2=
=80=9Caccess to legal remedy=E2=80=9D=2E
>Anonymity
>makes attribution hard=
er but still not impossible=2E Many John Doe=E2=80=99s have
>had
>cases aga=
inst them which provided the plaintiffs with the appropriate
>remedies=2E
>=

>
>
>
>
>On Mon, Feb 1, 2021 at 5:19 PM Niels ten Oever <mail@nielstenoeve=
r=2Enet>
>wrote:
>
>> Dear Farzaneh,
>>
>> Do your alterations reflect the =
content of the discussion, or mere
>your
>> opinion?
>>
>> I hope we're see=
king to reach a consensus during last call, not
>reopening
>> the discussio=
n=2E
>>
>> Best,
>>
>> Niels
>>
>> On Feb 1, 2021, at 22:22, farzaneh badii=
 <farzaneh=2Ebadii@gmail=2Ecom>
>wrote:
>>>
>>> Here we go:
>>>
>>>
>>> Que=
stion(s): Can your protocol facilitate a negatively impacted
>>>
>>>    par=
ty's right to the appropriate  legal remedy without
>>> disproportionately =
impacting
>>>
>>>    other parties' human rights, especially their right to=
 privacy?
>>>
>>>
>>>    Explanation: Access to legal remedy is a human rig=
ht that ensures
>>>
>>>    that individuals whose rights have been violated=
 can seek
>remedies
>>>
>>>
>>>
>>>
>>>    through a judicial authority=2E =
  Attribution (i=2Ee=2E mechanisms in
>>>
>>>    protocols or architectures=
 that are designed to make
>communications
>>>
>>>    or artifacts attribut=
able might help with seeking the appropriate
>>> remedy=2E)  to a certain c=
omputer or individual) can be
>>>
>>>    a part of this, since it may allow=
 law enforcement agencies to
>>>
>>>    identify a possible violator =2E  H=
owever, attribution mechanisms
>may
>>>
>>    impede the exercise of the ri=
ght to privacy=2E  The Special
>Rapporteur
>>>
>>>    for Freedom of Expres=
sion has also argued that anonymity is an
>>>
>>>    inherent part of freed=
om of expression=2E  [Kaye] Considering the
>>>
>>>    adverse impact of at=
tribution on the right to privacy and freedom
>of
>>>
>>>    expression, at=
tribution on an individual level may  is not be
>>> consistent
>>>
>>>    w=
ith human rights=2E  However, attribution to corporate entities,
>>>
>>>   =
 associations, and/or countries may not directly negatively impact
>>>
>>> =
   human rights=2E
>>>
>>>
>>>    Impacts:
>>>
>>>
>>>    -   Right to lega=
l remedy
>>>
>>>
>>>    -  Right to security
>>>
>> Farzaneh
>>>
>>>
>>> On=
 Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever <
>mail@nielstenoever=2Enet>
>=
>> wrote:
>>>
>>>> Hi Farzaneh,
>>>>
>>>> On 31-01-2021 19:16, farzaneh bad=
ii wrote:
>>>> > Hello Niels=2E
>>>> >
>>>> >
>>>> > I don't know how we me=
asure consensus here=2E But I remember
>weighing in
>>>> back then as well(=
When Mr=2E Curran weighed in back in 2019)=2E Here is
>the
>>>> thread: 
>h=
ttps://mailarchive=2Eietf=2Eorg/arch/browse/hrpc/?q=3Dattribution <
>>>> ht=
tps://mailarchive=2Eietf=2Eorg/arch/browse/hrpc/?q=3Dattribution>
>>>> >
>>=
>> > I can see that unfortunately I missed the discussion on this
>topic
>>=
>> during the past year, and that's my fault, but I can bring reasons
>not =
to
>>>> add "attribution and legal remedy" to this document at all=2E
>>>> =
>
>>>> > 1=2E Access to legal remedy is something that the States are
>supp=
osedly
>>>> in charge of bringing to their citizens=2EWhich should (in theo=
ry)
>ensure
>>>> that human rights are enforced=2E I don't think there was =
an
>intention to
>>>> provide  mechanisms for "enforcement" of human rights=
 in various
>legal
>>>> systems through Internet protocols=2E As mentioned =
in the beginning
>of your
>>>> document:
>>>> > "Human rights threats on th=
e Internet come in a myriad of
>>>> forms=2E* **P**rotocols and standards c=
an harm or enable* the right
>to
>>>> freedom of expression, right to non-d=
iscrimination, right to equal
>>>> protection, right to participate in cult=
ural life, arts and
>science, right
>>>> to freedom of assembly and associa=
tion, and the right to security=2E"
>>>> >
>>>> > So we are not in the busi=
ness of enforcing but providing an
>enabling
>>>> environment=2E Because if=
 we want to help law enforcement and the
>judicial
>>>> authorities enforce=
 human rights through Internet protocols we
>should bear
>>>> in mind that =
that they are not always staunch advocates of human
>rights=2E So
>>>> what=
 I assume we are trying to do here is to help Internet protocol
>not to
>>>=
> facilitate harm and "enable" human rights=2E
>>>> >
>>>>
>>>> The text in=
 the draft seeks to address this risk=2E I have sought to
>>>> address all =
points made in that discussion, and I would not like to
>re-open
>>>> that =
debate=2E If you feel the text is unbalanced, could you perhaps
>provide
>>=
>> text suggestions?
>>>>
>>>> > 2=2E Attribution, section 3=2E3=2E20  of t=
he Guideline, the authors
>assert
>>>> that: "However, attribution to corpo=
rate entities, associations,
>and/or
>>>> countries may not directly negati=
vely impact human rights=2E" I think
>this is
>>>> not a very well backed u=
p claim=2E Because in some cases some
>associations
>>>> might be political=
 or they might be human rights associations
>dealing with
>>>> a dictatorsh=
ip=2E Attribution to those associations certainly can
>impact
>>>> their hu=
man rights negatively=2E Even when it comes to corporations,
>some
>>>> CEO=
s of digital companies are put in jail because of the materials
>posted
>>>=
> on their websites=2E I don't think we can argue that attribution to
>corp=
orate
>>>> entities might not adversely impact human rights=2E
>>>> >
>>>>
=
>>>> Again, the keyword in that sentence is 'may', so there is no strong
>>=
>> claim made=2E
>>>>
>>>> > All in all I think section 3=2E3=2E20 does not=
 help Internet
>Protocols
>>>> enable human rights and it can be misinterpr=
eted=2E
>>>>
>>>> I think the text in there is not strong and shows differe=
nt
>perspectives
>>>> and potential consequences=2E But again, happy to rec=
eive text
>suggestions=2E
>>>>
>>>> >
>>>> > And in my previous email I tal=
ked about the problems with threat
>>>> intelligence agencies and some of t=
heir conducts and the use of
>WHOIS for
>>>> attribution (which was actuall=
y not designed to "identify" actors
>but
>>>> unfortunately was used for th=
at) so I will not reiterate here=2E
>>>>
>>>> From exactly that discussion =
we got the idea to remove individuals,
>and
>>>> leave non-natural persons =
in=2E
>>>>
>>>> Best,
>>>>
>>>> Niels
>>>>
>>>> >
>>>> >
>>>> >
>>>> >
>>>>=
 >
>>>> >
>>>> >
>>>> > On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever <
>=
>>> mail@nielstenoever=2Enet <mailto: mail@nielstenoever=2Enet>> wrote:
>>>=
> >
>>>> >     Hi Farzaneh,
>>>> >
>>>> >     Thanks a lot for the review!
=
>>>> >
>>>> >     On 30-01-2021 23:00, farzaneh badii wrote:
>>>> >     > H=
ello
>>>> >     >
>>>> >     > Adding my comments on this document:
>>>> ht=
tps://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05 <
>>>> https://=
tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05> <
>>>> https://tools=
=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05 <
>>>> https://tools=2Eiet=
f=2Eorg/html/draft-irtf-hrpc-guidelines-05>>
>>>> >     >
>>>> >     > 1=2E=
 One major issue that I see here and you might be able to
>>>> easily solve=
 it is that there is no distinction between user facing
>>>> protocols and =
other protocols=2E For example, you ask for
>accessibility and
>>>> conside=
ration of culture etc=2E Are you asking all the protocols to
>be
>>>> provi=
ded in multiple languages, even those that only developers and
>>>> impleme=
nters use and not the actual users? You might want to
>clarify that=2E
>>>>=
 >     >
>>>> >
>>>> >     We had a quite extensive discussion about this i=
n relation to
>the
>>>> presentation by Ramsey Nasr who create Qalb, an Ara=
bic programming
>>>> language=2E Programmers are the most frequent 'users' =
of protocols -
>if we
>>>> continue using only latin characters and English=
 documentation in
>protocols
>>>> we are likely to reproduce the existing l=
ack of diversity in
>protocol
>>>> developers communities=2E But we can mak=
e the text on this clearer as
>well!
>>>> >
>>>> >     > 2=2Esection 3=2E3=
=2E1 on connectivity, you mention that
>"considering
>>>> the fact that net=
work quality and conditions vary across geography
>and time
>>>> it is also=
 important to design protocols such that they are
>reliable even
>>>> on lo=
w bandwidth =2E=2E=2E"=2E Then in your example you say: Middleboxes
>(inclu=
ding
>>>> NAT)=2E=2E=2E=2E can create potential for abuse=2E NAT is a Netwo=
rk Address
>>>> Translation protocol=2E I don't think it has anything to do=
 with
>bandwidth=2E
>>>> In this example you also mention CDNs=2E Are you s=
uggesting that the
>>>> developer should not consider "Middleboxes" protoco=
ls? I think you
>need to
>>>> work on the example of section 3=2E3=2E1 some=
 more to make it clearer=2E
>>>> >     >
>>>> >
>>>> >     Excellent point =
- we'll address this in a future version=2E
>>>> >
>>>> >     > 3=2E sectio=
n 3=2E3=2E20 remedy and attribution
>>>> >     > This section worries me=2E=
 As a  scholar I have worked on
>cyber
>>>> attribution to some extent and =
believe in general when we have the
>right
>>>> processes in place, attribu=
tion is very important and can hold
>>>> cyber-attackers accountable=2E I a=
m aware of some of the attribution
>>>> processes and unfortunately some th=
reat intelligence firms and open
>source
>>>> intelligence organizations ca=
n violate the privacy of individuals
>by
>>>> profiling them=2E Also, uncon=
trolled attribution mechanisms can lead
>to
>>>> frivolous intellectual pro=
perty claims=2E Both some threat
>intelligence firms
>>>> and IP firms have=
 used WHOIS extensively in their favor to
>attribute
>>>> cybersecurity att=
acks and bring forward IP claims=2E WHOIS protocol
>did not
>>>> have the i=
ntention to actually identify organizations and
>individuals, but
>>>> to m=
ake them "contactable"=2Eand it was still used and mined for so
>many
>>>> =
years and those who have abused WHOIS have not been held
>accountable=2EWhe=
n
>>>> you suggest they consider "attribution" when developing protocols
>i=
t
>>>> >     > concerns me because it is not enough that you limit
>attribu=
tion
>>>> to organizations and states=2E These kinds of attributions can be=

>used
>>>> against individuals and until we do not have the right preservi=
ng
>processes
>>>> to put in place for those who want to be in the attribut=
ion
>business,
>>>> rights of the individual can be at risk=2E there are ve=
ry privacy
>>>> conscious cybersecurity researchers out there but unfortuna=
tely
>that does
>>>> not ensure a systematic practice of attribution in a f=
air manner=2E
>And you
>>>> mention attribution to associations is fine and=
 may not directly
>negatively
>>>> impact human rights=2E Associations can =
themselves be at risk of
>>>> frivolous attacks and frivolous attribution=
=2E I am concerned about
>this
>>>> paragraph=2E I think we should have a c=
onversation about it=2E
>>>> >     >
>>>> >
>>>> >     In the proposed text=
 I tried to capture the consensus that
>emerged
>>>> from the extensive dis=
cussion that was had on this list=2E Do you
>have
>>>> concrete suggestions=
 on how to better capture that conensensus? I
>am afraid
>>>> we would go b=
ack and repeat the same discussion=2E
>>>> >
>>>> >     > 4=2E Nice to see =
that you mention DoH=2E It's a great privacy
>>>> preserving protocol=2E
>>=
>> >     >
>>>> >     >
>>>> >
>>>> >     Thanks!
>>>> >
>>>> >     Niels
>=
>>> >
>>>> >     >
>>>> >     >
>>>> >     >
>>>> >     >
>>>> >     >
>>>>=
 >     >
>>>> >     >
>>>> >     >
>>>> >     > Farzaneh
>>>> >     >
>>>> =
>     >
>>>> >     > On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath <
>>>> c=
orinnecath@gmail=2Ecom <mailto: corinnecath@gmail=2Ecom> <mailto:
>>>> cori=
nnecath@gmail=2Ecom <mailto: corinnecath@gmail=2Ecom>>> wrote:
>>>> >     >=

>>>> >     >     Hi all,
>>>> >     >
>>>> >     >     I trust this email =
finds you well=2E I did a review of
>the
>>>> draft, from my perspective as=
 an academic=2E Take it as you please=2E
>My main
>>>> concern is that some=
 of the language reads a bit deterministic (as,
>I know
>>>> so does RFC 82=
80)=2E It means that a lot of onus is put on the impact
>of a
>>>> protocol=
, as opposed the role of the individuals that write them=2E
>>>> >     >
>>=
>> >     >     I think through out the document, it would be
>interesting
>=
>>> (especially in section 1 through 3=2E2=2E5) to see if you can rewrite
>=
such that
>>>> you speak more directly to the protocol developers=2E I thin=
k that
>section
>>>> 3=2E3 does that well, in terms of the tone it takes=2E=
 As it clearly
>connects
>>>> the actions of protocol developers to their p=
otential outcomes=2E
>>>> >     >
>>>> >     >     Hope this is helpful!
>>=
>> >     >
>>>> >     >     Kind regards,
>>>> >     >
>>>> >     >     Cor=
inne
>>>> >     >
>>>> >     >     ---------------------------------
>>>> >=
     >
>>>> >     >     *1=2E Introduction*
>>>> >     >
>>>> >     >     "=
It provides questions engineers should ask
>>>> >     >
>>>> >     >       =
 themselves when developing or improving protocols if
>they
>>>> want to
>>=
>> >     >        understand their potential human rights impact=2E"
>>>> >=
     >
>>>> >     >
>>>> >     >     >> maybe if they want to understand po=
tential human
>rights
>>>> concerns? Impact seems a little deterministic, a=
s you also mention
>in the
>>>> next sentence, I wonder if you can prove su=
ch direct impact between
>>>> protocol development in the IETF and impact o=
n human rights=2E
>>>> >     >
>>>> >     >     "The research establishes
>=
>>> >     >
>>>> >     >        that human rights relate to standards and p=
rotocols,
>and
>>>> offers a
>>>> >     >        common vocabulary of techn=
ical concepts that impact
>human
>>>> rights and
>>>> >     >        how th=
ese technical concepts can be combined to
>ensure
>>>> that the
>>>> >     =
>        Internet remains an enabling environment for human
>>>> rights=2E"=

>>>> >     >
>>>> >     >
>>>> >     >     >> same comment for the word im=
pact, perhaps shape?
>>>> influence? etc=2E
>>>> >     >
>>>> >     >
>>>> =
>     >           3=2E1 < https://tools=2Eietf=2Eorg/html/
>>>> draft-irtf-=
hrpc-guidelines-05#section-3=2E1 <
>https://tools=2Eietf=2Eorg/html/
>>>> d=
raft-irtf-hrpc-guidelines-05#section-3=2E1>>=2E Human rights threats
>>>> >=
     >
>>>> >     >
>>>> >     >
>>>> >     >      "Protocols and standards=
 can harm or enable the right
>to
>>>> freedom of
>>>> >     >        expre=
ssion, right to non-discrimination, right to
>equal
>>>> protection,
>>>> >=
     >        right to participate in cultural life, arts and
>science,
>>>=
> right to
>>>> >     >
>>>> >     >     freedom of assembly and associatio=
n, and the right to
>>>> security=2E "
>>>> >     >
>>>> >     >
>>>> >    =
 >     >> again, deterministic language=2E Perhaps soften or add
>more
>>>>=
 concrete examples for context, that draw from current IETF
>>>> discussion=
s/standards=2E
>>>> >     >
>>>> >     >
>>>> >     >
>>>> >     >         =
  3=2E3 < https://tools=2Eietf=2Eorg/html/
>>>> draft-irtf-hrpc-guidelines-=
05#section-3=2E3 <
>https://tools=2Eietf=2Eorg/html/
>>>> draft-irtf-hrpc-g=
uidelines-05#section-3=2E3>>=2E Guidelines for human
>>>> rights considerat=
ions
>>>> >     >
>>>> >     >
>>>> >     >
>>>> >     >     again, use of =
the word impact in the introduction=2E
>>>> >     >
>>>> >     >
>>>> >    =
 >
>>>> >     >
>>>> >     >     --
>>>> >     >     Corinne Cath - Speth
>=
>>> >     >     Ph=2ED=2E Candidate, Oxford Internet Institute & Alan
>Turi=
ng
>>>> Institute
>>>> >     >
>>>> >     >     Web: www=2Eoii=2Eox=2Eac=2E=
uk/people/corinne-cath <
>>>> http://www=2Eoii=2Eox=2Eac=2Euk/people/corinn=
e-cath> <
>http://www=2Eoii=2Eox=2Eac=2Euk/
>>>> people/corinne-cath < http=
://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath>>
>>>> >     >     Email: c=
cath@turing=2Eac=2Euk <mailto: ccath@turing=2Eac=2Euk>
>>>> <mailto: ccath@=
turing=2Eac=2Euk <mailto: ccath@turing=2Eac=2Euk>> &
>>>> corinnecath@gmail=
=2Ecom <mailto: corinnecath@gmail=2Ecom> <mailto:
>>>> corinnecath@gmail=2E=
com <mailto: corinnecath@gmail=2Ecom>>
>>>> >     >     Twitter: @C_CS
>>>>=
 >     >     _______________________________________________
>>>> >     >  =
   hrpc mailing list
>>>> >     >      hrpc@irtf=2Eorg <mailto: hrpc@irtf=
=2Eorg> <mailto:
>>>> hrpc@irtf=2Eorg <mailto: hrpc@irtf=2Eorg>>
>>>> >    =
 >      https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc <
>>>> https://www=
=2Eirtf=2Eorg/mailman/listinfo/hrpc> <
>>>> https://www=2Eirtf=2Eorg/mailma=
n/listinfo/hrpc <
>>>> https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc>>
>>>=
> >     >
>>>> >     >
>>>> >     > _______________________________________=
________
>>>> >     > hrpc mailing list
>>>> >     > hrpc@irtf=2Eorg <mailt=
o: hrpc@irtf=2Eorg>
>>>> >     > https://www=2Eirtf=2Eorg/mailman/listinfo/=
hrpc <
>>>> https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc>
>>>> >     >
>>=
>> >
>>>> >     --
>>>> >     Niels ten Oever, PhD
>>>> >     Postdoctoral =
Researcher - Media Studies Department -
>University of
>>>> Amsterdam
>>>> =
>     Postdoctoral Research Fellow - Communications Department -
>Texas
>>>=
> A&M University
>>>> >     Research Fellow - Centre for Internet and Human=
 Rights -
>European
>>>> University Viadrina
>>>> >     Associated Scholar =
- Centro de Tecnologia e Sociedade -
>Funda=C3=A7=C3=A3o
>>>> Get=C3=BAlio =
Vargas
>>>> >
>>>> >     W: https://nielstenoever=2Enet < https://nielsteno=
ever=2Enet>
>>>> >     E: mail@nielstenoever=2Enet <mailto: mail@nielstenoe=
ver=2Enet>
>>>> >     T: @nielstenoever
>>>> >     P/S/WA: +31629051853
>>>=
> >     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>>>> >
>>>> =
>     Read my dissertation 'Wired Norms' here:
>>>> https://pure=2Euva=2Enl=
/ws/files/50781961/Thesis=2Epdf <
>>>> https://pure=2Euva=2Enl/ws/files/507=
81961/Thesis=2Epdf>
>>>> >     ____________________________________________=
___
>>>> >     hrpc mailing list
>>>> >      hrpc@irtf=2Eorg <mailto: hrpc@=
irtf=2Eorg>
>>>> >      https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc <
>>=
>> https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc>
>>>> >
>>>>
>>>> --
>>>>=
 Niels ten Oever, PhD
>>>> Postdoctoral Researcher - Media Studies Departme=
nt - University of
>>>> Amsterdam
>>>> Postdoctoral Research Fellow - Commu=
nications Department - Texas
>A&M
>>>> University
>>>> Research Fellow - Ce=
ntre for Internet and Human Rights - European
>>>> University Viadrina
>>>>=
 Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=A3o=

>Get=C3=BAlio
>>>> Vargas
>>>>
>>>> W: https://nielstenoever=2Enet
>>>> E:=
 mail@nielstenoever=2Enet
>>>> T: @nielstenoever
>>>> P/S/WA: +31629051853
=
>>>> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>>>>
>>>> Read =
my dissertation 'Wired Norms' here:
>https://pure=2Euva=2Enl/ws/files/
>>>>=
 50781961/Thesis=2Epdf
>>>>
>>>
>
>-- 
>Farzaneh

------OQIFQ1OJ1RUXT9OK0OOL5Z3OXH2T77
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"zoom: 0%;"><div dir=3D"auto">Dear Farzane=
h,<br><br></div>
<div dir=3D"auto">In the extensive discussion between you,=
 John, Amelia, Pranesh and others you were the only one who said attributio=
n has no role in this document whatsoever=2E You reiterate this position=2E=
=C2=A0 But that might mean that you are in the rough=2E <br><br></div>
<div=
 dir=3D"auto">Best,<br><br></div>
<div dir=3D"auto">Niels</div>
<div class=
=3D"gmail_quote" >On Feb 2, 2021, at 02:06, farzaneh badii &lt;<a href=3D"m=
ailto:farzaneh=2Ebadii@gmail=2Ecom" target=3D"_blank">farzaneh=2Ebadii@gmai=
l=2Ecom</a>&gt; wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0p=
t 0pt 0pt 0=2E8ex; border-left: 1px solid rgb(204, 204, 204); padding-left:=
 1ex;">
<div>
 Niels,&nbsp;
 <br>
</div>
<div dir=3D"auto">
 <br>
</div>
<d=
iv dir=3D"auto">
 I don't know how you come to consensus=2E I thought you a=
s one of the drafters need to make changes that capture the consensus=2E Se=
ems like you have had =E2=80=9Cmany discussions=E2=80=9D and all the points=
 I have raised been resolved satisfactorily in this group in my absence=2E =
Then the only thing I can do is to record my objection to paragraph 3=2E3=
=2E20: Attribution=2E&nbsp;
</div>
<div dir=3D"auto">
 <br>
</div>
<div dir=
=3D"auto">
 I don't think the paragraph as is in that document is human rig=
hts enabling and frankly it has the potential to do the opposite=2E It is a=
 mistake to bring court and law enforcement to the discussion when the scop=
e of this group is "enabling human rights"=2E It is a mistake to make a dis=
tinction between natural and legal persons in this case and assume that nat=
ural persons may not be harmed in the process because the distinction =E2=
=80=9Cmay=E2=80=9D protect them=2E&nbsp;
</div>
<div dir=3D"auto">
 <br>
</=
div>
<div dir=3D"auto">
 I brought reasons and they don't seem to be convin=
cing to you or something you want to work with and it seems to me it is too=
 late now=2E So I get out of your way and just record my objection to the p=
aragraph=2E&nbsp;
</div>
<div dir=3D"auto">
 <br>
</div>
<div dir=3D"auto">=

 Just to disclose: I have worked on cyber attack attribution processes aca=
demically, and believe that attribution is one way to hold cyber attackers =
accountable=2E I just don=E2=80=99t think we need the protocol developer th=
ink about ways of attribution to make it easier to attribute cyber attacks =
in court for legal remedy and include this in the guidelines for human righ=
ts protection document as a =E2=80=9Caccess to legal remedy=E2=80=9D=2E Ano=
nymity makes attribution harder but still not impossible=2E Many John Doe=
=E2=80=99s have had cases against them which provided the plaintiffs with t=
he appropriate remedies=2E&nbsp;
</div>
<div dir=3D"auto">
 <br>
</div>
<di=
v dir=3D"auto">
 <br>
</div>
<div dir=3D"auto">
 <br>
</div>
<div dir=3D"au=
to">
 <br>
</div>
<div dir=3D"auto">
 <br>
 <div class=3D"gmail_quote" dir=
=3D"auto">
  <div dir=3D"ltr" class=3D"gmail_attr">
   On Mon, Feb 1, 2021 =
at 5:19 PM Niels ten Oever &lt;
   <a href=3D"mailto:mail@nielstenoever=2En=
et" target=3D"_blank">mail@nielstenoever=2Enet</a>&gt; wrote:
   <br>
  </d=
iv>
  <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =2E8ex;border=
-left:1px #ccc solid;padding-left:1ex">
   <div style=3D"zoom:0%">
    <div=
 dir=3D"auto">
     Dear Farzaneh,
     <br>
     <br>
    </div> 
    <div=
 dir=3D"auto">
     Do your alterations reflect the content of the discussi=
on, or mere your opinion?
     <br>
     <br>
    </div> 
    <div dir=3D"a=
uto">
     I hope we're seeking to reach a consensus during last call, not =
reopening the discussion=2E
     <br>
     <br>
    </div> 
    <div dir=3D=
"auto">
     Best,
     <br>
     <br>
    </div> 
    <div dir=3D"auto">
 =
    Niels
     <br>
     <br>
    </div> 
    <div class=3D"gmail_quote">
 =
    On Feb 1, 2021, at 22:22, farzaneh badii &lt;
     <a href=3D"mailto:fa=
rzaneh=2Ebadii@gmail=2Ecom" target=3D"_blank">farzaneh=2Ebadii@gmail=2Ecom<=
/a>&gt; wrote:
     <blockquote class=3D"gmail_quote" style=3D"margin:0pt 0=
pt 0pt 0=2E8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> 
 =
     <div dir=3D"ltr"> 
       <div class=3D"gmail_default" style=3D"font-f=
amily:verdana,sans-serif">
         Here we go: 
       </div> 
       <div=
 class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"> 
       =
 <br> 
       </div> 
       <div class=3D"gmail_default" style=3D"font-fam=
ily:verdana,sans-serif"></div> 
       <div class=3D"gmail_default" style=
=3D"font-family:verdana,sans-serif"> 
        <br> 
       </div> 
       <=
div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"> 
    =
    <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:n=
ormal;font-family:Helvetica">Question(s): Can your protocol facilitate a ne=
gatively impacted</p> 
        <p style=3D"margin:0px;font-stretch:normal;f=
ont-size:12px;line-height:normal;font-family:Helvetica"><span>&nbsp;&nbsp; =
</span>party's right to<font color=3D"#ff0000">&nbsp;the appropriate </font=
> 
         <strike>
           &nbsp;legal 
         </strike>remedy witho=
ut disproportionately impacting</p> 
        <p style=3D"margin:0px;font-st=
retch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span=
>&nbsp;&nbsp; </span>other parties' human rights, especially their right to=
 privacy?</p> 
        <p style=3D"margin:0px;font-stretch:normal;font-size=
:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br></p> 
 =
       <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-heigh=
t:normal;font-family:Helvetica"> 
         <strike> 
          <span>&nbsp;=
&nbsp; </span>Explanation: Access to legal remedy is a human right that ens=
ures 
         </strike></p> 
        <p style=3D"margin:0px;font-stretch:n=
ormal;font-size:12px;line-height:normal;font-family:Helvetica"> 
         <=
strike> 
          <span>&nbsp;&nbsp; </span>that individuals whose rights =
have been violated can seek remedies 
         </strike></p> 
        <p st=
yle=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:normal;fon=
t-family:Helvetica;min-height:14px"><br></p> 
        <p style=3D"margin:0p=
x;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helveti=
ca;min-height:14px"><br></p> 
        <p style=3D"margin:0px;font-stretch:n=
ormal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14=
px"><br></p> 
        <p style=3D"margin:0px;font-stretch:normal;font-size:=
12px;line-height:normal;font-family:Helvetica"> 
         <strike> 
       =
   <span>&nbsp;&nbsp; </span>through a judicial authority=2E 
         </st=
rike><span>&nbsp; </span>Attribution (i=2Ee=2E mechanisms in</p> 
        <=
p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:normal=
;font-family:Helvetica"><span>&nbsp;&nbsp; </span>protocols or architecture=
s that are designed to make communications</p> 
        <p style=3D"margin:=
0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helve=
tica"><span>&nbsp;&nbsp; </span>or artifacts attributable <font color=3D"#f=
f0000">might help with seeking the appropriate remedy</font>=2E)&nbsp; 
   =
      <strike>
           to a certain computer or individual) 
         </=
strike> 
         <strike>
           can be 
         </strike></p> 
     =
   <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:Helvetica"> 
         <strike> 
          <span>&nbsp;&nbs=
p; </span>a part of this, since it may allow law enforcement agencies to 
 =
        </strike></p> 
        <p style=3D"margin:0px;font-stretch:normal;f=
ont-size:12px;line-height:normal;font-family:Helvetica"> 
         <strike>=
 
          <span>&nbsp;&nbsp; </span>identify a possible violator 
       =
  </strike>=2E<span>&nbsp; </span>However, attribution mechanisms may</p>
 =
      </div>
      </div>
     </blockquote>
    </div>
   </div>
   <div s=
tyle=3D"zoom:0%">
    <div class=3D"gmail_quote">
     <blockquote class=3D=
"gmail_quote" style=3D"margin:0pt 0pt 0pt 0=2E8ex;border-left:1px solid rgb=
(204,204,204);padding-left:1ex">
      <div dir=3D"ltr">
       <div class=
=3D"gmail_default" style=3D"font-family:verdana,sans-serif"> 
        <p st=
yle=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:normal;fon=
t-family:Helvetica"><span>&nbsp;&nbsp; </span>impede the exercise of the ri=
ght to privacy=2E<span>&nbsp; </span>The Special Rapporteur</p> 
        <p=
 style=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:normal;=
font-family:Helvetica"><span>&nbsp;&nbsp; </span>for Freedom of Expression =
has also argued that anonymity is an</p> 
        <p style=3D"margin:0px;fo=
nt-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">=
<span>&nbsp;&nbsp; </span>inherent part of freedom of expression=2E<span>&n=
bsp; </span>[Kaye] Considering the</p> 
        <p style=3D"margin:0px;font=
-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><s=
pan>&nbsp;&nbsp; </span>adverse impact of attribution on the right to priva=
cy and freedom of</p> 
        <p style=3D"margin:0px;font-stretch:normal;f=
ont-size:12px;line-height:normal;font-family:Helvetica"><span>&nbsp;&nbsp; =
</span>expression, attribution on an individual level 
         <strike>
  =
         may 
         </strike>&nbsp;<font color=3D"#ff0000">is&nbsp;</fon=
t>not 
         <strike>
           be 
         </strike> consistent</p> 
=
        <p style=3D"margin:0px;font-stretch:normal;font-size:12px;line-heig=
ht:normal;font-family:Helvetica"><span>&nbsp;&nbsp; </span>with human right=
s=2E<span>&nbsp; 
          <strike> 
          </strike></span> 
         =
<strike>
           However, attribution to corporate entities, 
         <=
/strike></p> 
        <p style=3D"margin:0px;font-stretch:normal;font-size:=
12px;line-height:normal;font-family:Helvetica"> 
         <strike> 
       =
   <span>&nbsp;&nbsp; </span>associations, and/or countries may not directl=
y negatively impact 
         </strike></p> 
        <p style=3D"margin:0px=
;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetic=
a"> 
         <strike> 
          <span>&nbsp;&nbsp; </span>human rights=2E=
 
         </strike></p> 
        <p style=3D"margin:0px;font-stretch:norma=
l;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px">=
<br></p> 
        <p style=3D"margin:0px;font-stretch:normal;font-size:12px=
;line-height:normal;font-family:Helvetica"><span>&nbsp;&nbsp; </span>Impact=
s:</p> 
        <p style=3D"margin:0px;font-stretch:normal;font-size:12px;l=
ine-height:normal;font-family:Helvetica;min-height:14px"> 
         <strike=
> 
          <br> 
         </strike></p> 
        <p style=3D"margin:0px;f=
ont-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"=
> 
         <strike> 
          <span>&nbsp;&nbsp; </span>- 
          <spa=
n>&nbsp; </span>Right to legal remedy 
         </strike></p> 
        <p s=
tyle=3D"margin:0px;font-stretch:normal;font-size:12px;line-height:normal;fo=
nt-family:Helvetica;min-height:14px"><br></p> 
        <p style=3D"margin:0=
px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvet=
ica"><span>&nbsp;&nbsp; </span>-<span>&nbsp; </span>Right to security</p> 
=
       </div>
      </div>
     </blockquote>
    </div>
   </div>
   <div =
style=3D"zoom:0%">
    <div class=3D"gmail_quote">
     <blockquote class=
=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0=2E8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
      <div dir=3D"ltr">
       <div cla=
ss=3D"gmail_default" style=3D"font-family:verdana,sans-serif"></div> 
     =
  <div> 
        <div dir=3D"ltr" data-smartmail=3D"gmail_signature"> 
    =
     <div dir=3D"ltr"> 
          <div> 
           <font face=3D"verdana, =
sans-serif">Farzaneh </font> 
          </div> 
         </div> 
        </=
div> 
       </div> 
       <br> 
      </div>
     </blockquote>
    </div=
>
   </div>
   <div style=3D"zoom:0%">
    <div class=3D"gmail_quote">
    =
 <blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0=2E8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"> 
      <br> 
      <d=
iv class=3D"gmail_quote"> 
       <div dir=3D"ltr" class=3D"gmail_attr">
  =
       On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever &lt; 
        <a href=
=3D"mailto:mail@nielstenoever=2Enet" target=3D"_blank">mail@nielstenoever=
=2Enet</a>&gt; wrote: 
        <br> 
       </div> 
       <blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=2E8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">
         Hi Farzaneh, 
        <br> 
 =
       <br> On 31-01-2021 19:16, farzaneh badii wrote: 
        <br> &gt; H=
ello Niels=2E 
        <br> &gt; 
        <br> &gt; 
        <br> &gt; I do=
n't know how we measure consensus here=2E But I remember weighing in back t=
hen as well(When Mr=2E Curran weighed in back in 2019)=2E Here is the threa=
d:&nbsp; 
        <a href=3D"https://mailarchive=2Eietf=2Eorg/arch/browse/h=
rpc/?q=3Dattribution" rel=3D"noreferrer" target=3D"_blank">https://mailarch=
ive=2Eietf=2Eorg/<wbr>arch/browse/hrpc/?q=3D<wbr>attribution</a> &lt; 
    =
    <a href=3D"https://mailarchive=2Eietf=2Eorg/arch/browse/hrpc/?q=3Dattri=
bution" rel=3D"noreferrer" target=3D"_blank">https://mailarchive=2Eietf=2Eo=
rg/<wbr>arch/browse/hrpc/?q=3D<wbr>attribution</a>&gt; 
        <br> &gt; 
=
        <br> &gt; I can see that unfortunately I missed the&nbsp;discussion=
 on this topic during the past year, and that's my fault, but I can bring r=
easons not to add "attribution and legal remedy" to this document at all=2E=
&nbsp; 
        <br> &gt; 
        <br> &gt; 1=2E Access to legal remedy is=
 something that the States are supposedly in charge of bringing to their ci=
tizens=2EWhich should (in theory) ensure that human rights are enforced=2E =
I don't think there&nbsp;was an intention to&nbsp; provide&nbsp; mechanisms=
 for "enforcement" of human rights in various legal systems through Interne=
t protocols=2E As mentioned&nbsp;in the beginning of your document:&nbsp; 
=
        <br> &gt; "Human rights threats on the Internet come in a myriad of=
 forms=2E*&nbsp;**P**rotocols and standards can harm or enable* the right t=
o freedom of&nbsp;expression, right to non-discrimination, right to equal p=
rotection,&nbsp;right to participate in cultural life, arts and science, ri=
ght to&nbsp;freedom of assembly and association, and the right to security=
=2E"&nbsp; 
        <br> &gt; 
        <br> &gt; So we are not in the busin=
ess of enforcing but providing&nbsp;an enabling environment=2E Because&nbsp=
;if we want to help law enforcement and the judicial authorities enforce hu=
man rights through&nbsp;Internet&nbsp;protocols we should bear in mind that=
 that they are not always staunch advocates of human rights=2E So what I as=
sume we are trying to do here is to help Internet protocol not to facilitat=
e harm and "enable" human rights=2E&nbsp; 
        <br> &gt; 
        <br> =

        <br> The text in the draft seeks to address this risk=2E I have so=
ught to address all points made in that discussion, and I would not like to=
 re-open that debate=2E If you feel the text is unbalanced, could you perha=
ps provide text suggestions? 
        <br> 
        <br> &gt; 2=2E Attribut=
ion, section 3=2E3=2E20&nbsp; of the Guideline, the authors assert that: "H=
owever, attribution to corporate entities,&nbsp;associations, and/or countr=
ies may not directly negatively impact&nbsp;human rights=2E" I think this i=
s not a very&nbsp;well backed up claim=2E Because in some cases some associ=
ations might be political or they might be human rights associations dealin=
g with a dictatorship=2E Attribution to those associations certainly can im=
pact their human rights negatively=2E Even when it comes to corporations, s=
ome CEOs of digital companies are put in jail because of the materials post=
ed on their websites=2E I don't think we can argue that attribution to corp=
orate entities might not adversely impact human rights=2E 
        <br> &gt=
; 
        <br> 
        <br> Again, the keyword in that sentence is 'may',=
 so there is no strong claim made=2E 
        <br> 
        <br> &gt; All i=
n all I think section 3=2E3=2E20 does not help Internet Protocols enable hu=
man rights and it can be misinterpreted=2E 
        <br> 
        <br> I th=
ink the text in there is not strong and shows different perspectives and po=
tential consequences=2E But again, happy to receive text suggestions=2E 
  =
      <br> 
        <br> &gt; 
        <br> &gt; And in my previous email I=
 talked about the problems with threat intelligence agencies and some of th=
eir conducts and the use of WHOIS for attribution (which was actually not d=
esigned to "identify" actors but unfortunately was used for that) so I will=
 not reiterate here=2E 
        <br> 
        <br> From exactly that discus=
sion we got the idea to remove individuals, and leave non-natural persons i=
n=2E 
        <br> 
        <br> Best, 
        <br> 
        <br> Niels 
 =
       <br> 
        <br> &gt; 
        <br> &gt; 
        <br> &gt; 
     =
   <br> &gt; 
        <br> &gt; 
        <br> &gt; 
        <br> &gt; 
    =
    <br> &gt; On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever &lt; 
       =
 <a href=3D"mailto:mail@nielstenoever=2Enet" target=3D"_blank">mail@nielste=
noever=2Enet</a> &lt;mailto: 
        <a href=3D"mailto:mail@nielstenoever=
=2Enet" target=3D"_blank">mail@nielstenoever=2Enet</a>&gt;&gt; wrote: 
    =
    <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;Hi Farzaneh, 
        <=
br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;Thanks a lot for the review!=
 
        <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;On 30-01-2021 23:=
00, farzaneh badii wrote: 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; Hello =

        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; =
&nbsp;&gt; Adding my comments on this document:&nbsp; 
        <a href=3D"h=
ttps://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05" rel=3D"norefe=
rrer" target=3D"_blank">https://tools=2Eietf=2Eorg/html/<wbr>draft-irtf-hrp=
c-guidelines-05</a> &lt; 
        <a href=3D"https://tools=2Eietf=2Eorg/htm=
l/draft-irtf-hrpc-guidelines-05" rel=3D"noreferrer" target=3D"_blank">https=
://tools=2Eietf=2Eorg/html/<wbr>draft-irtf-hrpc-guidelines-05</a>&gt; &lt; =

        <a href=3D"https://tools=2Eietf=2Eorg/html/draft-irtf-hrpc-guideli=
nes-05" rel=3D"noreferrer" target=3D"_blank">https://tools=2Eietf=2Eorg/htm=
l/<wbr>draft-irtf-hrpc-guidelines-05</a> &lt; 
        <a href=3D"https://t=
ools=2Eietf=2Eorg/html/draft-irtf-hrpc-guidelines-05" rel=3D"noreferrer" ta=
rget=3D"_blank">https://tools=2Eietf=2Eorg/html/<wbr>draft-irtf-hrpc-guidel=
ines-05</a>&gt;
        <wbr>&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt=
; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 1=2E One major issue that I se=
e here and you might be able to easily solve it is that there is no distinc=
tion between user facing protocols and other protocols=2E For example, you =
ask for accessibility and consideration of culture etc=2E Are you asking al=
l the protocols to be provided in multiple languages, even those that only&=
nbsp;developers&nbsp;and implementers use and not the actual users? You mig=
ht want to clarify that=2E&nbsp; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;=
 
        <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;We had a quite ex=
tensive discussion about this in relation to the presentation by Ramsey Nas=
r who create Qalb, an Arabic programming language=2E Programmers are the mo=
st frequent 'users' of protocols - if we continue using only latin characte=
rs and English documentation in protocols we are likely to reproduce the ex=
isting lack of diversity in protocol developers communities=2E But we can m=
ake the text on this clearer as well! 
        <br> &gt; 
        <br> &gt;=
&nbsp; &nbsp; &nbsp;&gt; 2=2Esection 3=2E3=2E1 on connectivity, you mention=
 that "considering the fact that network quality and conditions vary across=
 geography and time it is also important to design protocols such that they=
 are reliable even on low bandwidth =2E=2E=2E"=2E Then in your example you =
say: Middleboxes (including NAT)=2E=2E=2E=2E can create potential for abuse=
=2E NAT is a Network Address Translation protocol=2E I don't think it has a=
nything to do with bandwidth=2E In this example you also mention CDNs=2E Ar=
e you suggesting that the developer should not consider "Middleboxes" proto=
cols? I think you need to work on the example of section 3=2E3=2E1 some mor=
e to make it clearer=2E&nbsp; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
 =
       <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;Excellent point - we=
'll address this in a future version=2E 
        <br> &gt; 
        <br> &g=
t;&nbsp; &nbsp; &nbsp;&gt; 3=2E section 3=2E3=2E20 remedy and attribution&n=
bsp; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; This section worries me=2E =
As a&nbsp; scholar I have worked on cyber attribution to some extent and be=
lieve&nbsp;in general when we have the right processes in place,&nbsp;attri=
bution is very important and can hold cyber-attackers accountable=2E I am a=
ware of some of the attribution processes and unfortunately some threat int=
elligence firms and open source intelligence organizations can violate the =
privacy of individuals by profiling them=2E Also, uncontrolled attribution =
mechanisms can lead to frivolous&nbsp;intellectual property claims=2E Both =
some threat intelligence firms and IP firms have used WHOIS extensively in =
their favor to attribute cybersecurity attacks and bring forward IP claims=
=2E WHOIS protocol did not have the intention to actually identify organiza=
tions and individuals, but to make them "contactable"=2Eand it was still us=
ed and mined for so many years and those who have abused WHOIS have not bee=
n held accountable=2EWhen you suggest they consider "attribution" when deve=
loping protocols it 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; concerns me =
because it is not enough that you limit attribution to organizations and st=
ates=2E These kinds of attributions can be used against individuals and unt=
il we do not have the right preserving processes to put in place for those =
who want to be in the attribution business, rights of the individual can be=
 at risk=2E there are very privacy conscious&nbsp;cybersecurity researchers=
 out there but unfortunately that does not ensure a systematic&nbsp;practic=
e of attribution in a fair manner=2E And you mention attribution to associa=
tions is fine and may not directly negatively impact human rights=2E Associ=
ations can themselves be at risk of frivolous&nbsp;attacks and frivolous&nb=
sp;attribution=2E I am concerned about this paragraph=2E I think we should =
have a conversation about it=2E 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; =

        <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;In the proposed te=
xt I tried to capture the consensus that emerged from the extensive discuss=
ion that was had on this list=2E Do you have concrete suggestions on how to=
 better capture that conensensus? I am afraid we would go back and repeat t=
he same discussion=2E 
        <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &n=
bsp;&gt; 4=2E Nice to see that you mention DoH=2E It's a great privacy pres=
erving protocol=2E&nbsp; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
      =
  <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt; 
        <br> &gt;&n=
bsp; &nbsp; &nbsp;Thanks! 
        <br> &gt; 
        <br> &gt;&nbsp; &nbsp=
; &nbsp;Niels 
        <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;=
 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp;=
 &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&n=
bsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        =
<br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt=
; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; Farzaneh 
        <br> &gt;&nb=
sp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <=
br> &gt;&nbsp; &nbsp; &nbsp;&gt; On Sat, Jan 30, 2021 at 10:35 AM Corinne C=
ath &lt; 
        <a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_bla=
nk">corinnecath@gmail=2Ecom</a> &lt;mailto: 
        <a href=3D"mailto:cori=
nnecath@gmail=2Ecom" target=3D"_blank">corinnecath@gmail=2Ecom</a>&gt; &lt;=
mailto: 
        <a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_blan=
k">corinnecath@gmail=2Ecom</a> &lt;mailto: 
        <a href=3D"mailto:corin=
necath@gmail=2Ecom" target=3D"_blank">corinnecath@gmail=2Ecom</a>&gt;&gt;&g=
t; wrote: 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbs=
p; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Hi all, 
        <br> &gt;&nbsp; &n=
bsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nb=
sp;I trust this email finds you well=2E I did a review of the draft, from m=
y perspective as an academic=2E Take it as you please=2E My main concern is=
 that some of the language reads a bit deterministic (as, I know so does RF=
C 8280)=2E It means that a lot of onus is put on the impact of a protocol, =
as opposed the role of the individuals that write them=2E&nbsp; 
        <b=
r> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&=
nbsp; &nbsp; &nbsp;I think through out the document, it would be interestin=
g (especially in section 1 through 3=2E2=2E5) to see if you can rewrite suc=
h that you speak more directly to the protocol developers=2E I think that s=
ection 3=2E3 does that well, in terms of the tone it takes=2E As it clearly=
 connects the actions of protocol developers to their potential outcomes=2E=
&nbsp; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; =
&nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Hope this is helpful!&nbsp; 
        <=
br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;=
&nbsp; &nbsp; &nbsp;Kind regards,&nbsp; 
        <br> &gt;&nbsp; &nbsp; &nb=
sp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Corin=
ne 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbs=
p; &nbsp;&gt;&nbsp; &nbsp; &nbsp;-----------------------------
        <wbr=
>---- 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &=
nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;*1=2E Introduction* 
        <br> &gt;&=
nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &n=
bsp; &nbsp;"It provides questions engineers should ask 
        <br> &gt;&n=
bsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nb=
sp; &nbsp; &nbsp; themselves when developing or improving protocols if they=
 want to 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nb=
sp; understand their potential human rights impact=2E" 
        <br> &gt;&n=
bsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        =
<br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;&gt;&gt; maybe if they=
 want to understand potential human rights concerns? Impact seems a little =
deterministic, as you also mention in the next sentence, I wonder if you ca=
n prove such direct impact between protocol development in the IETF and imp=
act on human rights=2E 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        =
<br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;"The research establis=
hes 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nb=
sp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; that human rights relate to stand=
ards and protocols, and offers a 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;=
&nbsp; &nbsp; &nbsp; &nbsp; common vocabulary of technical concepts that im=
pact human rights and 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbs=
p; &nbsp; &nbsp; how these technical concepts can be combined to ensure tha=
t the 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp;=
 Internet remains an enabling environment for human rights=2E" 
        <br=
> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
=
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;&gt;&gt; same =
comment for the word impact, perhaps shape? influence? etc=2E 
        <br>=
 &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
 =
       <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;3=2E1 &lt; 
        <a href=3D"https://tools=2Eietf=2Eorg/html/draft-=
irtf-hrpc-guidelines-05#section-3=2E1" rel=3D"noreferrer" target=3D"_blank"=
>https://tools=2Eietf=2Eorg/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>se=
ction-3=2E1</a> &lt; 
        <a href=3D"https://tools=2Eietf=2Eorg/html/dr=
aft-irtf-hrpc-guidelines-05#section-3=2E1" rel=3D"noreferrer" target=3D"_bl=
ank">https://tools=2Eietf=2Eorg/html/<wbr>draft-irtf-hrpc-guidelines-05#<wb=
r>section-3=2E1</a>&gt;&gt;=2E Human rights threats 
        <br> &gt;&nbsp=
; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br=
> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&n=
bsp; &nbsp; &nbsp; "Protocols and standards can harm or enable the right to=
 freedom of 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; =
&nbsp; expression, right to non-discrimination, right to equal protection, =

        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; right=
 to participate in cultural life, arts and science, right to 
        <br> =
&gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbs=
p; &nbsp; &nbsp;freedom of assembly and association, and the right to secur=
ity=2E " 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp=
; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp;=
 &nbsp;&gt;&gt; again, deterministic language=2E Perhaps soften or add more=
 concrete examples for context, that draw from current IETF discussions/sta=
ndards=2E 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbs=
p; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <b=
r> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3=
=2E3 &lt; 
        <a href=3D"https://tools=2Eietf=2Eorg/html/draft-irtf-hr=
pc-guidelines-05#section-3=2E3" rel=3D"noreferrer" target=3D"_blank">https:=
//tools=2Eietf=2Eorg/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3=
=2E3</a> &lt; 
        <a href=3D"https://tools=2Eietf=2Eorg/html/draft-irt=
f-hrpc-guidelines-05#section-3=2E3" rel=3D"noreferrer" target=3D"_blank">ht=
tps://tools=2Eietf=2Eorg/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>secti=
on-3=2E3</a>&gt;&gt;=2E Guidelines for human rights considerations 
       =
 <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&g=
t; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbs=
p; &nbsp;&gt;&nbsp; &nbsp; &nbsp;again, use of the word impact in the intro=
duction=2E 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nb=
sp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <=
br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;=
&nbsp; &nbsp; &nbsp;-- 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nb=
sp; &nbsp;Corinne Cath - Speth 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&n=
bsp; &nbsp; &nbsp;Ph=2ED=2E Candidate, Oxford Internet Institute &amp; Alan=
 Turing Institute 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> =
&gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Web: 
        <a href=3D"ht=
tp://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath" rel=3D"noreferrer" targe=
t=3D"_blank">www=2Eoii=2Eox=2Eac=2Euk/people/<wbr>corinne-cath</a> &lt; 
  =
      <a href=3D"http://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath" rel=
=3D"noreferrer" target=3D"_blank">http://www=2Eoii=2Eox=2Eac=2Euk/<wbr>peop=
le/corinne-cath</a>&gt; &lt; 
        <a href=3D"http://www=2Eoii=2Eox=2Eac=
=2Euk/people/corinne-cath" rel=3D"noreferrer" target=3D"_blank">http://www=
=2Eoii=2Eox=2Eac=2Euk/<wbr>people/corinne-cath</a> &lt; 
        <a href=3D=
"http://www=2Eoii=2Eox=2Eac=2Euk/people/corinne-cath" rel=3D"noreferrer" ta=
rget=3D"_blank">http://www=2Eoii=2Eox=2Eac=2Euk/<wbr>people/corinne-cath</a=
>&gt;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Ema=
il: 
        <a href=3D"mailto:ccath@turing=2Eac=2Euk" target=3D"_blank">cc=
ath@turing=2Eac=2Euk</a> &lt;mailto: 
        <a href=3D"mailto:ccath@turin=
g=2Eac=2Euk" target=3D"_blank">ccath@turing=2Eac=2Euk</a>&gt; &lt;mailto: 
=
        <a href=3D"mailto:ccath@turing=2Eac=2Euk" target=3D"_blank">ccath@t=
uring=2Eac=2Euk</a> &lt;mailto: 
        <a href=3D"mailto:ccath@turing=2Ea=
c=2Euk" target=3D"_blank">ccath@turing=2Eac=2Euk</a>&gt;&gt; &amp; 
       =
 <a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_blank">corinnecath@g=
mail=2Ecom</a> &lt;mailto: 
        <a href=3D"mailto:corinnecath@gmail=2Ec=
om" target=3D"_blank">corinnecath@gmail=2Ecom</a>&gt; &lt;mailto: 
        =
<a href=3D"mailto:corinnecath@gmail=2Ecom" target=3D"_blank">corinnecath@gm=
ail=2Ecom</a> &lt;mailto: 
        <a href=3D"mailto:corinnecath@gmail=2Eco=
m" target=3D"_blank">corinnecath@gmail=2Ecom</a>&gt;&gt; 
        <br> &gt;=
&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;Twitter: @C_CS 
        <br> &g=
t;&nbsp; &nbsp; &nbsp;&gt;&nbsp; &nbsp; &nbsp;_____________________________=

        <wbr>__________________ 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;=
&nbsp; &nbsp; &nbsp;hrpc mailing list 
        <br> &gt;&nbsp; &nbsp; &nbsp=
;&gt;&nbsp; &nbsp; &nbsp; 
        <a href=3D"mailto:hrpc@irtf=2Eorg" targe=
t=3D"_blank">hrpc@irtf=2Eorg</a> &lt;mailto: 
        <a href=3D"mailto:hrp=
c@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a>&gt; &lt;mailto: 
      =
  <a href=3D"mailto:hrpc@irtf=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a> =
&lt;mailto: 
        <a href=3D"mailto:hrpc@irtf=2Eorg" target=3D"_blank">h=
rpc@irtf=2Eorg</a>&gt;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt;&nbsp;=
 &nbsp; &nbsp; 
        <a href=3D"https://www=2Eirtf=2Eorg/mailman/listinf=
o/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eorg/mailm=
an/<wbr>listinfo/hrpc</a> &lt; 
        <a href=3D"https://www=2Eirtf=2Eorg=
/mailman/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2E=
irtf=2Eorg/mailman/<wbr>listinfo/hrpc</a>&gt; &lt; 
        <a href=3D"http=
s://www=2Eirtf=2Eorg/mailman/listinfo/hrpc" rel=3D"noreferrer" target=3D"_b=
lank">https://www=2Eirtf=2Eorg/mailman/<wbr>listinfo/hrpc</a> &lt; 
       =
 <a href=3D"https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc" rel=3D"noreferr=
er" target=3D"_blank">https://www=2Eirtf=2Eorg/mailman/<wbr>listinfo/hrpc</=
a>&gt;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nb=
sp; &nbsp; &nbsp;&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&gt; __________=
____________________
        <wbr>_________________ 
        <br> &gt;&nbsp=
; &nbsp; &nbsp;&gt; hrpc mailing list 
        <br> &gt;&nbsp; &nbsp; &nbsp=
;&gt; 
        <a href=3D"mailto:hrpc@irtf=2Eorg" target=3D"_blank">hrpc@ir=
tf=2Eorg</a> &lt;mailto: 
        <a href=3D"mailto:hrpc@irtf=2Eorg" target=
=3D"_blank">hrpc@irtf=2Eorg</a>&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&=
gt; 
        <a href=3D"https://www=2Eirtf=2Eorg/mailman/listinfo/hrpc" rel=
=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eorg/mailman/<wbr>lis=
tinfo/hrpc</a> &lt; 
        <a href=3D"https://www=2Eirtf=2Eorg/mailman/li=
stinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eorg/=
mailman/<wbr>listinfo/hrpc</a>&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;&g=
t; 
        <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;-- 
        <br=
> &gt;&nbsp; &nbsp; &nbsp;Niels ten Oever, PhD 
        <br> &gt;&nbsp; &nb=
sp; &nbsp;Postdoctoral Researcher - Media Studies Department - University o=
f Amsterdam 
        <br> &gt;&nbsp; &nbsp; &nbsp;Postdoctoral Research Fel=
low - Communications Department - Texas A&amp;M University 
        <br> &g=
t;&nbsp; &nbsp; &nbsp;Research Fellow - Centre for Internet and Human Right=
s - European University Viadrina 
        <br> &gt;&nbsp; &nbsp; &nbsp;Asso=
ciated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=A3o Get=
=C3=BAlio Vargas 
        <br> &gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;W=
: 
        <a href=3D"https://nielstenoever=2Enet" rel=3D"noreferrer" targe=
t=3D"_blank">https://nielstenoever=2Enet</a> &lt; 
        <a href=3D"https=
://nielstenoever=2Enet" rel=3D"noreferrer" target=3D"_blank">https://nielst=
enoever=2Enet</a>&gt; 
        <br> &gt;&nbsp; &nbsp; &nbsp;E: 
        <a =
href=3D"mailto:mail@nielstenoever=2Enet" target=3D"_blank">mail@nielstenoev=
er=2Enet</a> &lt;mailto: 
        <a href=3D"mailto:mail@nielstenoever=2Ene=
t" target=3D"_blank">mail@nielstenoever=2Enet</a>&gt; 
        <br> &gt;&nb=
sp; &nbsp; &nbsp;T: @nielstenoever 
        <br> &gt;&nbsp; &nbsp; &nbsp;P/=
S/WA: +31629051853 
        <br> &gt;&nbsp; &nbsp; &nbsp;PGP: 2458 0B70 5C4=
A FD8A 9488 643A 0ED8 3F3A 468A C8B3 
        <br> &gt; 
        <br> &gt;&=
nbsp; &nbsp; &nbsp;Read my dissertation 'Wired Norms' here: 
        <a hre=
f=3D"https://pure=2Euva=2Enl/ws/files/50781961/Thesis=2Epdf" rel=3D"norefer=
rer" target=3D"_blank">https://pure=2Euva=2Enl/ws/files/<wbr>50781961/Thesi=
s=2Epdf</a> &lt; 
        <a href=3D"https://pure=2Euva=2Enl/ws/files/50781=
961/Thesis=2Epdf" rel=3D"noreferrer" target=3D"_blank">https://pure=2Euva=
=2Enl/ws/files/<wbr>50781961/Thesis=2Epdf</a>&gt; 
        <br> &gt;&nbsp; =
&nbsp; &nbsp;_____________________________
        <wbr>__________________ =

        <br> &gt;&nbsp; &nbsp; &nbsp;hrpc mailing list 
        <br> &gt;&=
nbsp; &nbsp; &nbsp; 
        <a href=3D"mailto:hrpc@irtf=2Eorg" target=3D"_=
blank">hrpc@irtf=2Eorg</a> &lt;mailto: 
        <a href=3D"mailto:hrpc@irtf=
=2Eorg" target=3D"_blank">hrpc@irtf=2Eorg</a>&gt; 
        <br> &gt;&nbsp; =
&nbsp; &nbsp; 
        <a href=3D"https://www=2Eirtf=2Eorg/mailman/listinfo=
/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Eirtf=2Eorg/mailma=
n/<wbr>listinfo/hrpc</a> &lt; 
        <a href=3D"https://www=2Eirtf=2Eorg/=
mailman/listinfo/hrpc" rel=3D"noreferrer" target=3D"_blank">https://www=2Ei=
rtf=2Eorg/mailman/<wbr>listinfo/hrpc</a>&gt; 
        <br> &gt; 
        <b=
r> 
        <br> -- 
        <br> Niels ten Oever, PhD 
        <br> Postdo=
ctoral Researcher - Media Studies Department - University of Amsterdam 
   =
     <br> Postdoctoral Research Fellow - Communications Department - Texas =
A&amp;M University 
        <br> Research Fellow - Centre for Internet and =
Human Rights - European University Viadrina 
        <br> Associated Schola=
r - Centro de Tecnologia e Sociedade - Funda=C3=A7=C3=A3o Get=C3=BAlio Varg=
as 
        <br> 
        <br> W: 
        <a href=3D"https://nielstenoever=
=2Enet" rel=3D"noreferrer" target=3D"_blank">https://nielstenoever=2Enet</a=
> 
        <br> E: 
        <a href=3D"mailto:mail@nielstenoever=2Enet" tar=
get=3D"_blank">mail@nielstenoever=2Enet</a> 
        <br> T: @nielstenoever=
 
        <br> P/S/WA: +31629051853 
        <br> PGP: 2458 0B70 5C4A FD8A =
9488 643A 0ED8 3F3A 468A C8B3 
        <br> 
        <br> Read my dissertat=
ion 'Wired Norms' here: 
        <a href=3D"https://pure=2Euva=2Enl/ws/file=
s/50781961/Thesis=2Epdf" rel=3D"noreferrer" target=3D"_blank">https://pure=
=2Euva=2Enl/ws/files/<wbr>50781961/Thesis=2Epdf</a> 
        <br> 
       <=
/blockquote> 
      </div>
     </blockquote>
    </div>
   </div>
  </bloc=
kquote>
 </div>
</div> 
<br>
<br>-- 
<br>
<div dir=3D"ltr">
 <div>
  <font =
face=3D"verdana, sans-serif">Farzaneh </font>
 </div>
</div>
<br></blockquo=
te></div></body></html>
------OQIFQ1OJ1RUXT9OK0OOL5Z3OXH2T77--


From nobody Tue Feb  2 02:06:56 2021
Return-Path: <marknoumea@yahoo.com>
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 1D4F63A18FC for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 02:06:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level: 
X-Spam-Status: No, score=-2.089 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 dyzzsj6nFjwb for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 02:06:51 -0800 (PST)
Received: from sonic315-15.consmr.mail.bf2.yahoo.com (sonic315-15.consmr.mail.bf2.yahoo.com [74.6.134.125]) (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 D6E8E3A18FB for <hrpc@irtf.org>; Tue,  2 Feb 2021 02:06:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1612260409; bh=Wq4/tZC0xJZP9VoApD/rzQmvIyNFIlG1acLM96M23jY=; h=Subject:To:References:From:Date:In-Reply-To:From:Subject:Reply-To; b=i6kIsm7pzIvree1TBuV3JsqRtniEs7iXoeF8oeiF5QNKxJdHF72srHANH66732RkuYe/bwXgc5vXfMrMEC+o+tE+0HUR5S2dqUnTGAmHeT7twcsGcsQdBdzgBB3i2khJbGgQTSpfn/APkEugn/IsGSc78E0RYQligSIh4C3LyMttl6QRRyUg7lVHzRsXaNoxvI1cYeUs0+kTNSRyj0f4hnLVHyYg9ynz3ZdptsDQLvkcDzLnCEqLWCeQ2GZ+avkv4G1FUL8DRu9xO+tr3kw4R4k054Q6ocLaKfuc6H+CrQIexvUeZ35L0HtfdsfjTsOliZE/6L+f8SFNfugtMlsVUA==
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;  t=1612260409; bh=7sutEbsAF3+COU0XzIbw0pIbfAwU3UdQeafZi0o8gFs=;  h=Subject:To:From:Date:From:Subject:Reply-To; b=GzxfmTUWRO/OZ7WYaswfnGyBanUkHEw7wpzMy8j+eNwJ3zOc1sCA12ZZ9SGvEUOU+E7hbYELL7LF4Zk1fINoPHLNtyCBjfKE65QMLyr+TsG12f9fzvCuzoVwjn7kwJXd44nsoP31hxi07N9klL1QXfz3IZepOVHxge4cjG4pEWOp7S1j9Hcum7OeVLa8eZ6dfmMvZkIKfuBZIupCBbMnlH7Hl79SL0SUNl8ghN2m4fYBuhVNZkeb4dxEkgpzsiYidtP6UDSHsLS2jXk2VM6RPRs/ou/vxgSi4mp93xh1wUSv/Qna2PA0xWXczmFwrGCOXra/qi788Nf2aIIj+U/uLg==
X-YMail-OSG: Br3w8Y8VM1kjOJYQOgFeuSoH3UATeU7C5Q5JrYcm7cdChWibscnGb7yXubMPhiY C8yi2ZRq.LpzsK2_Myx4ZotSmqXKImndD9MjcBMXidvSZpaxg1El.vW54rVZr1tWyja7wEBm.tM5 3iL7VFQJRy9nmhJA3x_ELzoph2zKHTsI06SQF7K_B0vhUR27VgvLfn8koT.P.QqBaG0cJnx.Rz7P tTUVtIBHe_FabTv_FmW5McZI69yIN.LqC1PC5Aob3OxxsbEvZ9rmOAoA_voWh3OWEwcRPQva6EJM GcDVbQNmiHf0eO45Io1KclNhwaYHk6FMcSYOMPMZ1wacSZ97Fl0z1wEkWpmHeZw832EPPLBbWSpu rrta.svxdKXHp6zVAW8SJxhS_pn9xaUqQb6TgEE_2AwyxHf2OaY3iMPIs2R1MgP.XgtKxf.9s5kk xzkpze5UUCxqOsDir_hpbO4s87Ts1yGENmef7JrfRB0CXFg3dtnUretGgGaGffGI99jGAu8v1KQf H.pXMcY0t_76tl4CauqD6ib_2FyGqlXfM3k9J5cRQRELoWYvslDz8OQ3u_8jPsCfOx4lFvbhnNk. NC0_idZaUgdVv4jmqK7zAdIgT1Ibxne6e.Yacl5eSZoE18n_VX6hcL5A4qIv8v7EEmjlBKjeV8ax im0Tb5D6gvy_Gy22cJ8c4UhGDSXFfwTu7Mz4vUd8Gy_8_L7h8X4B.53SxhZ5HhUCT.eZxLianzfr um71VkdDRWXsRdS6RJ9BFKM2nMSWiYg3GKukoMfKGu_Yq1Uo_ZX9mCmHCjQ4zyH9uVqiXaAmQ5RS t6VtWJMWImMI0HkGnsk4Z52jBoIWaEkiIR6Z6W6Gjt1b91PTjczBLBK4rDBbYqYapLMvLhW6DP2X uzWKhAx_jGVby8ILC_UHjSQyL7Vpji4FDgPJlEDHo7bImIeTGA.udcyA3OIdTXWT5Aog2DixZlhi fQfET.KJxryz38aJtLGCh.F9PDkZ6apTDX4DpIpRKvY3JhGq1eVXdH9QvD1ATPpgZDQd_ff_nntE qQl4Gbf5uNXD1dUdwC.24Zn844TXcexGikNzlveVZ1c3XX5OfFx2_R3SCkWqA4lcFmF.xCxFdo08 7GDisc18VDzUeEfQVxH..wjDED7phIxa.51o5Efo2dX7P7Zs9eLJvqv59sfgIkxRTwDc9EpsrssT 1rNeCPM52hdkG_ZmvZlHKrZ7Pr5fvLZMjcB.H339wP_PqIu0e57dfgnUlyM1Xz6e3J10_NUwUS72 4_.kxT9eo28qU6enzUxdshcUWYUYgh_xgzsdMQqRU3GBFfKyXbePjUJ2phbdaTkiCq0p3DBYoB5m sMgeq8AF945nopJS7pe.xlqB0ucq8rKqqu_wIZ6IylIB60_PWKzyX3_yDfwf5he91DNnmaJcFMfQ UBLD7bHURgAO5lHBej7mPj58aIfbLpS1JD6BDJM_G2vbjIAkwUF42rHoConics19qJI65p4TIvgS 4uScb9ENHPo5pKExd0caop_U2FKJfTuph_7vy0QmEFRJ1d3erhweEp8m0VkPsBakl9r1TFBqz8Fz fhJkzKO95a0B3M1POcd0YVtz6IQU61k1RREF35KFB0tBM9dTGFiXbMmqS_YBmWBJAXm6WRox6Wov MrQJVRPgK2Dmpp.eJq4gRBXVzgKyKvOWH8FS9HH4p_usN1HzVawwkqsluI64qUX.upMIkf7ZPKM6 qRsWR_KdmpOplc2NrQiuOTVaTov5kMOAGBTYlypwWnf1P11pRCNesZrKbUBETnNbQPQkfKKXP7At MNZjANN0.GLqojy0lqVsTj9KuXbr8ZeUC1JM.NI15FrK30nSyxOFCWUgpuT6IlPlE4QVx79Px7oR Zg4liCVqnQVkLxyUNTwwLgCjOPNBic1xlGe_3CVP1X7PILXK5nZfWB4FZY8Nu_TcFymQvYNXYfsR KA_BW6K8j8inBvdVxhCyvKyv9YWlaRUEx3dIeY7HeTt2oII.VmNBpOcRycngFgRylNlNNrh8MXr_ rjl_VoLs36zencXxmYk7usNBPBXVjYKxFAE8oY2ap6v7mFgsJZ3pURs1UiFhMZtRduCYEuZhxMaZ r6RJOjYo1pT1RhYs7hsPvIsF7R1Ok7PhRYKFB4IHKyeIpFarBNRO9zV6VhNECq.fZzNBVOktzRN7 A0rmDLhsr7Qk8OkY6K3x19YNyCI0i1ErbYjF7UTOdAB.IIAxSx3oZ2EeUeZeTZQ1nafdKP1sWnYt BeWXbDVLYpEgJ12EIL2LIEeiknBS_4PI2rBvFKXAycNSnEZoWuHSs_a9L3s.sAIzsEVUipnS3LB5 Vj9LPApaVDBPWtds7eEOFaaNq0s5SW3xWD4g8CGDOaqODM.5dPU1GR5QxgBiHKQbcNOZq5CpvCHM wfktXHrIIWbQ.ogYbo.3fNhE-
Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Tue, 2 Feb 2021 10:06:49 +0000
Received: by smtp414.mail.bf1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID ad43ecba9fb3945c305eeddf05a50a24;  Tue, 02 Feb 2021 10:06:43 +0000 (UTC)
To: hrpc@irtf.org
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <08b61ab2-7840-d993-9946-c085861f4172@nielstenoever.net> <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com> <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net> <CAN1qJvCsbfnVePRFYAsySrgtaumUARc8PpnAX-cANu5Pgc7TMA@mail.gmail.com> <34ab9666-4521-49f7-831e-c22841743448@nielstenoever.net> <CAN1qJvB++T1u+vRWLDcb9YoO5J8mJ_-bwf1c3jSPVrmzk=GDJw@mail.gmail.com> <46063596-f537-417f-89c1-d09e9c934b63@nielstenoever.net>
From: Mark Perkins <marknoumea@yahoo.com>
Message-ID: <ff2984ea-d8a7-4269-1301-bfc2057579bb@yahoo.com>
Date: Tue, 2 Feb 2021 21:06:27 +1100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <46063596-f537-417f-89c1-d09e9c934b63@nielstenoever.net>
Content-Type: multipart/alternative; boundary="------------202E1F996C76D771E9A705D7"
Content-Language: fr
X-Antivirus: Avast (VPS 210201-18, 02/02/2021), Outbound message
X-Antivirus-Status: Clean
X-Mailer: WebService/1.1.17648 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo Apache-HttpAsyncClient/4.1.4 (Java/11.0.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/dyAPmSIHLUJuvHNkUxX4dls-G3Q>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 10:06:55 -0000

This is a multi-part message in MIME format.
--------------202E1F996C76D771E9A705D7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Not sure that Farzaneh is in the rough, I came out clearly against 
attribution a while ago (start of the discussion?).  Not sure how many 
others are also opposed, as not many have spoken - perhaps a straw poll 
is needed? My impression is that there is no consensus on this issue, 
more like a clear division.

Mark P.

Le 02/02/2021 à 18:57, Niels ten Oever a écrit :
> Dear Farzaneh,
>
> In the extensive discussion between you, John, Amelia, Pranesh and 
> others you were the only one who said attribution has no role in this 
> document whatsoever. You reiterate this position.  But that might mean 
> that you are in the rough.
>
> Best,
>
> Niels
> On Feb 2, 2021, at 02:06, farzaneh badii <farzaneh.badii@gmail.com 
> <mailto:farzaneh.badii@gmail.com>> wrote:
>
>     Niels,
>
>     I don't know how you come to consensus. I thought you as one of
>     the drafters need to make changes that capture the consensus.
>     Seems like you have had “many discussions” and all the points I
>     have raised been resolved satisfactorily in this group in my
>     absence. Then the only thing I can do is to record my objection to
>     paragraph 3.3.20: Attribution.
>
>     I don't think the paragraph as is in that document is human rights
>     enabling and frankly it has the potential to do the opposite. It
>     is a mistake to bring court and law enforcement to the discussion
>     when the scope of this group is "enabling human rights". It is a
>     mistake to make a distinction between natural and legal persons in
>     this case and assume that natural persons may not be harmed in the
>     process because the distinction “may” protect them.
>
>     I brought reasons and they don't seem to be convincing to you or
>     something you want to work with and it seems to me it is too late
>     now. So I get out of your way and just record my objection to the
>     paragraph.
>
>     Just to disclose: I have worked on cyber attack attribution
>     processes academically, and believe that attribution is one way to
>     hold cyber attackers accountable. I just don’t think we need the
>     protocol developer think about ways of attribution to make it
>     easier to attribute cyber attacks in court for legal remedy and
>     include this in the guidelines for human rights protection
>     document as a “access to legal remedy”. Anonymity makes
>     attribution harder but still not impossible. Many John Doe’s have
>     had cases against them which provided the plaintiffs with the
>     appropriate remedies.
>
>
>
>
>
>     On Mon, Feb 1, 2021 at 5:19 PM Niels ten Oever <
>     mail@nielstenoever.net <mailto:mail@nielstenoever.net>> wrote:
>
>         Dear Farzaneh,
>
>         Do your alterations reflect the content of the discussion, or
>         mere your opinion?
>
>         I hope we're seeking to reach a consensus during last call,
>         not reopening the discussion.
>
>         Best,
>
>         Niels
>
>         On Feb 1, 2021, at 22:22, farzaneh badii <
>         farzaneh.badii@gmail.com <mailto:farzaneh.badii@gmail.com>>
>         wrote:
>
>             Here we go:
>
>
>             Question(s): Can your protocol facilitate a negatively
>             impacted
>
>             party's right to the appropriate  legal remedy without
>             disproportionately impacting
>
>             other parties' human rights, especially their right to
>             privacy?
>
>
>             Explanation: Access to legal remedy is a human right that
>             ensures
>
>             that individuals whose rights have been violated can seek
>             remedies
>
>
>
>
>             through a judicial authority. Attribution (i.e. mechanisms in
>
>             protocols or architectures that are designed to make
>             communications
>
>             or artifacts attributable might help with seeking the
>             appropriate remedy.) to a certain computer or individual)
>             can be
>
>             a part of this, since it may allow law enforcement
>             agencies to
>
>             identify a possible violator .However, attribution
>             mechanisms may
>
>             impede the exercise of the right to privacy.The Special
>             Rapporteur
>
>             for Freedom of Expression has also argued that anonymity is an
>
>             inherent part of freedom of expression.[Kaye] Considering the
>
>             adverse impact of attribution on the right to privacy and
>             freedom of
>
>             expression, attribution on an individual level may is not
>             be consistent
>
>             with human rights.However, attribution to corporate entities,
>
>             associations, and/or countries may not directly negatively
>             impact
>
>             human rights.
>
>
>             Impacts:
>
>
>             - Right to legal remedy
>
>
>             -Right to security
>
>             Farzaneh
>
>
>             On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever <
>             mail@nielstenoever.net <mailto:mail@nielstenoever.net>>
>             wrote:
>
>                 Hi Farzaneh,
>
>                 On 31-01-2021 19:16, farzaneh badii wrote:
>                 > Hello Niels.
>                 >
>                 >
>                 > I don't know how we measure consensus here. But I
>                 remember weighing in back then as well(When Mr. Curran
>                 weighed in back in 2019). Here is the thread:
>                 https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution
>                 <https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution>
>                 <
>                 https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution
>                 <https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution>>
>
>                 >
>                 > I can see that unfortunately I missed the discussion
>                 on this topic during the past year, and that's my
>                 fault, but I can bring reasons not to add "attribution
>                 and legal remedy" to this document at all.
>                 >
>                 > 1. Access to legal remedy is something that the
>                 States are supposedly in charge of bringing to their
>                 citizens.Which should (in theory) ensure that human
>                 rights are enforced. I don't think there was an
>                 intention to provide  mechanisms for "enforcement" of
>                 human rights in various legal systems through Internet
>                 protocols. As mentioned in the beginning of your
>                 document:
>                 > "Human rights threats on the Internet come in a
>                 myriad of forms.* **P**rotocols and standards can harm
>                 or enable* the right to freedom of expression, right
>                 to non-discrimination, right to equal
>                 protection, right to participate in cultural life,
>                 arts and science, right to freedom of assembly and
>                 association, and the right to security."
>                 >
>                 > So we are not in the business of enforcing but
>                 providing an enabling environment. Because if we want
>                 to help law enforcement and the judicial authorities
>                 enforce human rights through Internet protocols we
>                 should bear in mind that that they are not always
>                 staunch advocates of human rights. So what I assume we
>                 are trying to do here is to help Internet protocol not
>                 to facilitate harm and "enable" human rights.
>                 >
>
>                 The text in the draft seeks to address this risk. I
>                 have sought to address all points made in that
>                 discussion, and I would not like to re-open that
>                 debate. If you feel the text is unbalanced, could you
>                 perhaps provide text suggestions?
>
>                 > 2. Attribution, section 3.3.20  of the Guideline,
>                 the authors assert that: "However, attribution to
>                 corporate entities, associations, and/or countries may
>                 not directly negatively impact human rights." I think
>                 this is not a very well backed up claim. Because in
>                 some cases some associations might be political or
>                 they might be human rights associations dealing with a
>                 dictatorship. Attribution to those associations
>                 certainly can impact their human rights negatively.
>                 Even when it comes to corporations, some CEOs of
>                 digital companies are put in jail because of the
>                 materials posted on their websites. I don't think we
>                 can argue that attribution to corporate entities might
>                 not adversely impact human rights.
>                 >
>
>                 Again, the keyword in that sentence is 'may', so there
>                 is no strong claim made.
>
>                 > All in all I think section 3.3.20 does not help
>                 Internet Protocols enable human rights and it can be
>                 misinterpreted.
>
>                 I think the text in there is not strong and shows
>                 different perspectives and potential consequences. But
>                 again, happy to receive text suggestions.
>
>                 >
>                 > And in my previous email I talked about the problems
>                 with threat intelligence agencies and some of their
>                 conducts and the use of WHOIS for attribution (which
>                 was actually not designed to "identify" actors but
>                 unfortunately was used for that) so I will not
>                 reiterate here.
>
>                 From exactly that discussion we got the idea to remove
>                 individuals, and leave non-natural persons in.
>
>                 Best,
>
>                 Niels
>
>                 >
>                 >
>                 >
>                 >
>                 >
>                 >
>                 >
>                 > On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever <
>                 mail@nielstenoever.net <mailto:mail@nielstenoever.net>
>                 <mailto: mail@nielstenoever.net
>                 <mailto:mail@nielstenoever.net>>> wrote:
>                 >
>                 >     Hi Farzaneh,
>                 >
>                 >     Thanks a lot for the review!
>                 >
>                 >     On 30-01-2021 23:00, farzaneh badii wrote:
>                 >     > Hello
>                 >     >
>                 >     > Adding my comments on this document:
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>
>                 <
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>>
>                 <
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>
>                 <
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>>
>                 >
>                 >     >
>                 >     > 1. One major issue that I see here and you
>                 might be able to easily solve it is that there is no
>                 distinction between user facing protocols and other
>                 protocols. For example, you ask for accessibility and
>                 consideration of culture etc. Are you asking all the
>                 protocols to be provided in multiple languages, even
>                 those that only developers and implementers use and
>                 not the actual users? You might want to clarify that.
>                 >     >
>                 >
>                 >     We had a quite extensive discussion about this
>                 in relation to the presentation by Ramsey Nasr who
>                 create Qalb, an Arabic programming language.
>                 Programmers are the most frequent 'users' of protocols
>                 - if we continue using only latin characters and
>                 English documentation in protocols we are likely to
>                 reproduce the existing lack of diversity in protocol
>                 developers communities. But we can make the text on
>                 this clearer as well!
>                 >
>                 >     > 2.section 3.3.1 on connectivity, you mention
>                 that "considering the fact that network quality and
>                 conditions vary across geography and time it is also
>                 important to design protocols such that they are
>                 reliable even on low bandwidth ...". Then in your
>                 example you say: Middleboxes (including NAT).... can
>                 create potential for abuse. NAT is a Network Address
>                 Translation protocol. I don't think it has anything to
>                 do with bandwidth. In this example you also mention
>                 CDNs. Are you suggesting that the developer should not
>                 consider "Middleboxes" protocols? I think you need to
>                 work on the example of section 3.3.1 some more to make
>                 it clearer.
>                 >     >
>                 >
>                 >     Excellent point - we'll address this in a future
>                 version.
>                 >
>                 >     > 3. section 3.3.20 remedy and attribution
>                 >     > This section worries me. As a scholar I have
>                 worked on cyber attribution to some extent and
>                 believe in general when we have the right processes in
>                 place, attribution is very important and can hold
>                 cyber-attackers accountable. I am aware of some of the
>                 attribution processes and unfortunately some threat
>                 intelligence firms and open source intelligence
>                 organizations can violate the privacy of individuals
>                 by profiling them. Also, uncontrolled attribution
>                 mechanisms can lead to frivolous intellectual property
>                 claims. Both some threat intelligence firms and IP
>                 firms have used WHOIS extensively in their favor to
>                 attribute cybersecurity attacks and bring forward IP
>                 claims. WHOIS protocol did not have the intention to
>                 actually identify organizations and individuals, but
>                 to make them "contactable".and it was still used and
>                 mined for so many years and those who have abused
>                 WHOIS have not been held accountable.When you suggest
>                 they consider "attribution" when developing protocols it
>                 >     > concerns me because it is not enough that you
>                 limit attribution to organizations and states. These
>                 kinds of attributions can be used against individuals
>                 and until we do not have the right preserving
>                 processes to put in place for those who want to be in
>                 the attribution business, rights of the individual can
>                 be at risk. there are very privacy
>                 conscious cybersecurity researchers out there but
>                 unfortunately that does not ensure a
>                 systematic practice of attribution in a fair manner.
>                 And you mention attribution to associations is fine
>                 and may not directly negatively impact human rights.
>                 Associations can themselves be at risk of
>                 frivolous attacks and frivolous attribution. I am
>                 concerned about this paragraph. I think we should have
>                 a conversation about it.
>                 >     >
>                 >
>                 >     In the proposed text I tried to capture the
>                 consensus that emerged from the extensive discussion
>                 that was had on this list. Do you have concrete
>                 suggestions on how to better capture that conensensus?
>                 I am afraid we would go back and repeat the same
>                 discussion.
>                 >
>                 >     > 4. Nice to see that you mention DoH. It's a
>                 great privacy preserving protocol.
>                 >     >
>                 >     >
>                 >
>                 >     Thanks!
>                 >
>                 >     Niels
>                 >
>                 >     >
>                 >     >
>                 >     >
>                 >     >
>                 >     >
>                 >     >
>                 >     >
>                 >     >
>                 >     > Farzaneh
>                 >     >
>                 >     >
>                 >     > On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath
>                 < corinnecath@gmail.com <mailto:corinnecath@gmail.com>
>                 <mailto: corinnecath@gmail.com
>                 <mailto:corinnecath@gmail.com>> <mailto:
>                 corinnecath@gmail.com <mailto:corinnecath@gmail.com>
>                 <mailto: corinnecath@gmail.com
>                 <mailto:corinnecath@gmail.com>>>> wrote:
>                 >     >
>                 >     >     Hi all,
>                 >     >
>                 >     >     I trust this email finds you well. I did a
>                 review of the draft, from my perspective as an
>                 academic. Take it as you please. My main concern is
>                 that some of the language reads a bit deterministic
>                 (as, I know so does RFC 8280). It means that a lot of
>                 onus is put on the impact of a protocol, as opposed
>                 the role of the individuals that write them.
>                 >     >
>                 >     >     I think through out the document, it would
>                 be interesting (especially in section 1 through 3.2.5)
>                 to see if you can rewrite such that you speak more
>                 directly to the protocol developers. I think that
>                 section 3.3 does that well, in terms of the tone it
>                 takes. As it clearly connects the actions of protocol
>                 developers to their potential outcomes.
>                 >     >
>                 >     >     Hope this is helpful!
>                 >     >
>                 >     >     Kind regards,
>                 >     >
>                 >     >     Corinne
>                 >     >
>                 >     >  ----------------------------- ----
>                 >     >
>                 >     >     *1. Introduction*
>                 >     >
>                 >     >     "It provides questions engineers should ask
>                 >     >
>                 >     >        themselves when developing or improving
>                 protocols if they want to
>                 >     >        understand their potential human rights
>                 impact."
>                 >     >
>                 >     >
>                 >     >     >> maybe if they want to understand
>                 potential human rights concerns? Impact seems a little
>                 deterministic, as you also mention in the next
>                 sentence, I wonder if you can prove such direct impact
>                 between protocol development in the IETF and impact on
>                 human rights.
>                 >     >
>                 >     >     "The research establishes
>                 >     >
>                 >     >        that human rights relate to standards
>                 and protocols, and offers a
>                 >     >        common vocabulary of technical concepts
>                 that impact human rights and
>                 >     >        how these technical concepts can be
>                 combined to ensure that the
>                 >     >        Internet remains an enabling
>                 environment for human rights."
>                 >     >
>                 >     >
>                 >     >     >> same comment for the word impact,
>                 perhaps shape? influence? etc.
>                 >     >
>                 >     >
>                 >     >           3.1 <
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1>
>                 <
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1>>>.
>                 Human rights threats
>                 >     >
>                 >     >
>                 >     >
>                 >     >      "Protocols and standards can harm or
>                 enable the right to freedom of
>                 >     >        expression, right to
>                 non-discrimination, right to equal protection,
>                 >     >        right to participate in cultural life,
>                 arts and science, right to
>                 >     >
>                 >     >     freedom of assembly and association, and
>                 the right to security. "
>                 >     >
>                 >     >
>                 >     >     >> again, deterministic language. Perhaps
>                 soften or add more concrete examples for context, that
>                 draw from current IETF discussions/standards.
>                 >     >
>                 >     >
>                 >     >
>                 >     >           3.3 <
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3>
>                 <
>                 https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3
>                 <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3>>>.
>                 Guidelines for human rights considerations
>                 >     >
>                 >     >
>                 >     >
>                 >     >     again, use of the word impact in the
>                 introduction.
>                 >     >
>                 >     >
>                 >     >
>                 >     >
>                 >     >     --
>                 >     >     Corinne Cath - Speth
>                 >     >     Ph.D. Candidate, Oxford Internet Institute
>                 & Alan Turing Institute
>                 >     >
>                 >     >     Web: www.oii.ox.ac.uk/people/corinne-cath
>                 <http://www.oii.ox.ac.uk/people/corinne-cath> <
>                 http://www.oii.ox.ac.uk/people/corinne-cath
>                 <http://www.oii.ox.ac.uk/people/corinne-cath>> <
>                 http://www.oii.ox.ac.uk/people/corinne-cath
>                 <http://www.oii.ox.ac.uk/people/corinne-cath> <
>                 http://www.oii.ox.ac.uk/people/corinne-cath
>                 <http://www.oii.ox.ac.uk/people/corinne-cath>>>
>                 >     >     Email: ccath@turing.ac.uk
>                 <mailto:ccath@turing.ac.uk> <mailto:
>                 ccath@turing.ac.uk <mailto:ccath@turing.ac.uk>>
>                 <mailto: ccath@turing.ac.uk
>                 <mailto:ccath@turing.ac.uk> <mailto:
>                 ccath@turing.ac.uk <mailto:ccath@turing.ac.uk>>> &
>                 corinnecath@gmail.com <mailto:corinnecath@gmail.com>
>                 <mailto: corinnecath@gmail.com
>                 <mailto:corinnecath@gmail.com>> <mailto:
>                 corinnecath@gmail.com <mailto:corinnecath@gmail.com>
>                 <mailto: corinnecath@gmail.com
>                 <mailto:corinnecath@gmail.com>>>
>                 >     >     Twitter: @C_CS
>                 >     >  _____________________________ __________________
>                 >     >     hrpc mailing list
>                 >     > hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:
>                 hrpc@irtf.org <mailto:hrpc@irtf.org>> <mailto:
>                 hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:
>                 hrpc@irtf.org <mailto:hrpc@irtf.org>>>
>                 >     > https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc> <
>                 https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc>> <
>                 https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc> <
>                 https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc>>>
>                 >     >
>                 >     >
>                 >     > ______________________________ _________________
>                 >     > hrpc mailing list
>                 >     > hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:
>                 hrpc@irtf.org <mailto:hrpc@irtf.org>>
>                 >     > https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc> <
>                 https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc>>
>                 >     >
>                 >
>                 >     --
>                 >     Niels ten Oever, PhD
>                 >     Postdoctoral Researcher - Media Studies
>                 Department - University of Amsterdam
>                 >     Postdoctoral Research Fellow - Communications
>                 Department - Texas A&M University
>                 >     Research Fellow - Centre for Internet and Human
>                 Rights - European University Viadrina
>                 >     Associated Scholar - Centro de Tecnologia e
>                 Sociedade - Fundação Getúlio Vargas
>                 >
>                 >     W: https://nielstenoever.net
>                 <https://nielstenoever.net> <
>                 https://nielstenoever.net <https://nielstenoever.net>>
>                 >     E: mail@nielstenoever.net
>                 <mailto:mail@nielstenoever.net> <mailto:
>                 mail@nielstenoever.net <mailto:mail@nielstenoever.net>>
>                 >     T: @nielstenoever
>                 >     P/S/WA: +31629051853
>                 >     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A
>                 468A C8B3
>                 >
>                 >     Read my dissertation 'Wired Norms' here:
>                 https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>                 <https://pure.uva.nl/ws/files/50781961/Thesis.pdf> <
>                 https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>                 <https://pure.uva.nl/ws/files/50781961/Thesis.pdf>>
>                 >     _____________________________ __________________
>                 >     hrpc mailing list
>                 > hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:
>                 hrpc@irtf.org <mailto:hrpc@irtf.org>>
>                 > https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc> <
>                 https://www.irtf.org/mailman/listinfo/hrpc
>                 <https://www.irtf.org/mailman/listinfo/hrpc>>
>                 >
>
>                 -- 
>                 Niels ten Oever, PhD
>                 Postdoctoral Researcher - Media Studies Department -
>                 University of Amsterdam
>                 Postdoctoral Research Fellow - Communications
>                 Department - Texas A&M University
>                 Research Fellow - Centre for Internet and Human Rights
>                 - European University Viadrina
>                 Associated Scholar - Centro de Tecnologia e Sociedade
>                 - Fundação Getúlio Vargas
>
>                 W: https://nielstenoever.net <https://nielstenoever.net>
>                 E: mail@nielstenoever.net <mailto:mail@nielstenoever.net>
>                 T: @nielstenoever
>                 P/S/WA: +31629051853
>                 PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>
>                 Read my dissertation 'Wired Norms' here:
>                 https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>                 <https://pure.uva.nl/ws/files/50781961/Thesis.pdf>
>
>
>
>     -- 
>     Farzaneh
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc


-- 
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

--------------202E1F996C76D771E9A705D7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Not sure that Farzaneh is in the rough, I came out clearly
      against attribution a while ago (start of the discussion?).  Not
      sure how many others are also opposed, as not many have spoken -
      perhaps a straw poll is needed? My impression is that there is no
      consensus on this issue, more like a clear division.</p>
    <p>Mark P.<br>
    </p>
    <div class="moz-cite-prefix">Le 02/02/2021 à 18:57, Niels ten Oever
      a écrit :<br>
    </div>
    <blockquote type="cite"
      cite="mid:46063596-f537-417f-89c1-d09e9c934b63@nielstenoever.net">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">Dear Farzaneh,<br>
        <br>
      </div>
      <div dir="auto">In the extensive discussion between you, John,
        Amelia, Pranesh and others you were the only one who said
        attribution has no role in this document whatsoever. You
        reiterate this position.  But that might mean that you are in
        the rough. <br>
        <br>
      </div>
      <div dir="auto">Best,<br>
        <br>
      </div>
      <div dir="auto">Niels</div>
      <div class="gmail_quote">On Feb 2, 2021, at 02:06, farzaneh badii
        &lt;<a href="mailto:farzaneh.badii@gmail.com" target="_blank"
          moz-do-not-send="true">farzaneh.badii@gmail.com</a>&gt; wrote:
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          <div> Niels,  <br>
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> I don't know how you come to consensus. I
            thought you as one of the drafters need to make changes that
            capture the consensus. Seems like you have had “many
            discussions” and all the points I have raised been resolved
            satisfactorily in this group in my absence. Then the only
            thing I can do is to record my objection to paragraph
            3.3.20: Attribution. 
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> I don't think the paragraph as is in that
            document is human rights enabling and frankly it has the
            potential to do the opposite. It is a mistake to bring court
            and law enforcement to the discussion when the scope of this
            group is "enabling human rights". It is a mistake to make a
            distinction between natural and legal persons in this case
            and assume that natural persons may not be harmed in the
            process because the distinction “may” protect them. 
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> I brought reasons and they don't seem to be
            convincing to you or something you want to work with and it
            seems to me it is too late now. So I get out of your way and
            just record my objection to the paragraph. 
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> Just to disclose: I have worked on cyber
            attack attribution processes academically, and believe that
            attribution is one way to hold cyber attackers accountable.
            I just don’t think we need the protocol developer think
            about ways of attribution to make it easier to attribute
            cyber attacks in court for legal remedy and include this in
            the guidelines for human rights protection document as a
            “access to legal remedy”. Anonymity makes attribution harder
            but still not impossible. Many John Doe’s have had cases
            against them which provided the plaintiffs with the
            appropriate remedies. 
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> <br>
          </div>
          <div dir="auto"> <br>
            <div class="gmail_quote" dir="auto">
              <div dir="ltr" class="gmail_attr"> On Mon, Feb 1, 2021 at
                5:19 PM Niels ten Oever &lt; <a
                  href="mailto:mail@nielstenoever.net" target="_blank"
                  moz-do-not-send="true">mail@nielstenoever.net</a>&gt;
                wrote: <br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div style="zoom:0%">
                  <div dir="auto"> Dear Farzaneh, <br>
                    <br>
                  </div>
                  <div dir="auto"> Do your alterations reflect the
                    content of the discussion, or mere your opinion? <br>
                    <br>
                  </div>
                  <div dir="auto"> I hope we're seeking to reach a
                    consensus during last call, not reopening the
                    discussion. <br>
                    <br>
                  </div>
                  <div dir="auto"> Best, <br>
                    <br>
                  </div>
                  <div dir="auto"> Niels <br>
                    <br>
                  </div>
                  <div class="gmail_quote"> On Feb 1, 2021, at 22:22,
                    farzaneh badii &lt; <a
                      href="mailto:farzaneh.badii@gmail.com"
                      target="_blank" moz-do-not-send="true">farzaneh.badii@gmail.com</a>&gt;
                    wrote:
                    <blockquote class="gmail_quote" style="margin:0pt
                      0pt 0pt 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex">
                      <div dir="ltr">
                        <div class="gmail_default"
                          style="font-family:verdana,sans-serif"> Here
                          we go: </div>
                        <div class="gmail_default"
                          style="font-family:verdana,sans-serif"> <br>
                        </div>
                        <div class="gmail_default"
                          style="font-family:verdana,sans-serif"> <br>
                        </div>
                        <div class="gmail_default"
                          style="font-family:verdana,sans-serif">
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">Question(s):
                            Can your protocol facilitate a negatively
                            impacted</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>party's right to<font color="#ff0000"> the
                              appropriate </font> <strike>  legal </strike>remedy
                            without disproportionately impacting</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>other parties' human rights,
                            especially their right to privacy?</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>Explanation:
                              Access to legal remedy is a human right
                              that ensures </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>that individuals
                              whose rights have been violated can seek
                              remedies </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>through a
                              judicial authority. </strike><span>  </span>Attribution
                            (i.e. mechanisms in</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>protocols or architectures that are
                            designed to make communications</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>or artifacts attributable <font
                              color="#ff0000">might help with seeking
                              the appropriate remedy</font>.)  <strike>
                              to a certain computer or individual) </strike>
                            <strike> can be </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>a part of this,
                              since it may allow law enforcement
                              agencies to </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>identify a
                              possible violator </strike>.<span>  </span>However,
                            attribution mechanisms may</p>
                        </div>
                      </div>
                    </blockquote>
                  </div>
                </div>
                <div style="zoom:0%">
                  <div class="gmail_quote">
                    <blockquote class="gmail_quote" style="margin:0pt
                      0pt 0pt 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex">
                      <div dir="ltr">
                        <div class="gmail_default"
                          style="font-family:verdana,sans-serif">
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>impede the exercise of the right to
                            privacy.<span>  </span>The Special
                            Rapporteur</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>for Freedom of Expression has also
                            argued that anonymity is an</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>inherent part of freedom of
                            expression.<span>  </span>[Kaye]
                            Considering the</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>adverse impact of attribution on the
                            right to privacy and freedom of</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>expression, attribution on an
                            individual level <strike> may </strike> <font
                              color="#ff0000">is </font>not <strike> be
                            </strike> consistent</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>with human rights.<span>  <strike> </strike></span>
                            <strike> However, attribution to corporate
                              entities, </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>associations,
                              and/or countries may not directly
                              negatively impact </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>human rights. </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>Impacts:</p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px">
                            <strike> <br>
                            </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>   </span>- <span>  </span>Right
                              to legal remedy </strike></p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                            </span>-<span>  </span>Right to security</p>
                        </div>
                      </div>
                    </blockquote>
                  </div>
                </div>
                <div style="zoom:0%">
                  <div class="gmail_quote">
                    <blockquote class="gmail_quote" style="margin:0pt
                      0pt 0pt 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex">
                      <div dir="ltr">
                        <div>
                          <div dir="ltr"
                            data-smartmail="gmail_signature">
                            <div dir="ltr">
                              <div> <font face="verdana, sans-serif">Farzaneh
                                </font> </div>
                            </div>
                          </div>
                        </div>
                        <br>
                      </div>
                    </blockquote>
                  </div>
                </div>
                <div style="zoom:0%">
                  <div class="gmail_quote">
                    <blockquote class="gmail_quote" style="margin:0pt
                      0pt 0pt 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex"> <br>
                      <div class="gmail_quote">
                        <div dir="ltr" class="gmail_attr"> On Mon, Feb
                          1, 2021 at 2:38 PM Niels ten Oever &lt; <a
                            href="mailto:mail@nielstenoever.net"
                            target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>&gt;
                          wrote: <br>
                        </div>
                        <blockquote class="gmail_quote"
                          style="margin:0px 0px 0px
                          0.8ex;border-left:1px solid
                          rgb(204,204,204);padding-left:1ex"> Hi
                          Farzaneh, <br>
                          <br>
                          On 31-01-2021 19:16, farzaneh badii wrote: <br>
                          &gt; Hello Niels. <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; I don't know how we measure consensus
                          here. But I remember weighing in back then as
                          well(When Mr. Curran weighed in back in 2019).
                          Here is the thread:  <a
                            href="https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://mailarchive.ietf.org/<wbr>arch/browse/hrpc/?q=<wbr>attribution</a>
                          &lt; <a
                            href="https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://mailarchive.ietf.org/<wbr>arch/browse/hrpc/?q=<wbr>attribution</a>&gt;
                          <br>
                          &gt; <br>
                          &gt; I can see that unfortunately I missed
                          the discussion on this topic during the past
                          year, and that's my fault, but I can bring
                          reasons not to add "attribution and legal
                          remedy" to this document at all.  <br>
                          &gt; <br>
                          &gt; 1. Access to legal remedy is something
                          that the States are supposedly in charge of
                          bringing to their citizens.Which should (in
                          theory) ensure that human rights are enforced.
                          I don't think there was an intention to 
                          provide  mechanisms for "enforcement" of human
                          rights in various legal systems through
                          Internet protocols. As mentioned in the
                          beginning of your document:  <br>
                          &gt; "Human rights threats on the Internet
                          come in a myriad of forms.* **P**rotocols and
                          standards can harm or enable* the right to
                          freedom of expression, right to
                          non-discrimination, right to equal
                          protection, right to participate in cultural
                          life, arts and science, right to freedom of
                          assembly and association, and the right to
                          security."  <br>
                          &gt; <br>
                          &gt; So we are not in the business of
                          enforcing but providing an enabling
                          environment. Because if we want to help law
                          enforcement and the judicial authorities
                          enforce human rights
                          through Internet protocols we should bear in
                          mind that that they are not always staunch
                          advocates of human rights. So what I assume we
                          are trying to do here is to help Internet
                          protocol not to facilitate harm and "enable"
                          human rights.  <br>
                          &gt; <br>
                          <br>
                          The text in the draft seeks to address this
                          risk. I have sought to address all points made
                          in that discussion, and I would not like to
                          re-open that debate. If you feel the text is
                          unbalanced, could you perhaps provide text
                          suggestions? <br>
                          <br>
                          &gt; 2. Attribution, section 3.3.20  of the
                          Guideline, the authors assert that: "However,
                          attribution to corporate
                          entities, associations, and/or countries may
                          not directly negatively impact human rights."
                          I think this is not a very well backed up
                          claim. Because in some cases some associations
                          might be political or they might be human
                          rights associations dealing with a
                          dictatorship. Attribution to those
                          associations certainly can impact their human
                          rights negatively. Even when it comes to
                          corporations, some CEOs of digital companies
                          are put in jail because of the materials
                          posted on their websites. I don't think we can
                          argue that attribution to corporate entities
                          might not adversely impact human rights. <br>
                          &gt; <br>
                          <br>
                          Again, the keyword in that sentence is 'may',
                          so there is no strong claim made. <br>
                          <br>
                          &gt; All in all I think section 3.3.20 does
                          not help Internet Protocols enable human
                          rights and it can be misinterpreted. <br>
                          <br>
                          I think the text in there is not strong and
                          shows different perspectives and potential
                          consequences. But again, happy to receive text
                          suggestions. <br>
                          <br>
                          &gt; <br>
                          &gt; And in my previous email I talked about
                          the problems with threat intelligence agencies
                          and some of their conducts and the use of
                          WHOIS for attribution (which was actually not
                          designed to "identify" actors but
                          unfortunately was used for that) so I will not
                          reiterate here. <br>
                          <br>
                          From exactly that discussion we got the idea
                          to remove individuals, and leave non-natural
                          persons in. <br>
                          <br>
                          Best, <br>
                          <br>
                          Niels <br>
                          <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; On Sun, Jan 31, 2021 at 5:52 AM Niels ten
                          Oever &lt; <a
                            href="mailto:mail@nielstenoever.net"
                            target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>
                          &lt;mailto: <a
                            href="mailto:mail@nielstenoever.net"
                            target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>&gt;&gt;
                          wrote: <br>
                          &gt; <br>
                          &gt;     Hi Farzaneh, <br>
                          &gt; <br>
                          &gt;     Thanks a lot for the review! <br>
                          &gt; <br>
                          &gt;     On 30-01-2021 23:00, farzaneh badii
                          wrote: <br>
                          &gt;     &gt; Hello <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; Adding my comments on this
                          document:  <a
                            href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>
                          &lt; <a
                            href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>&gt;
                          &lt; <a
                            href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>
                          &lt; <a
                            href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>&gt;
                          <wbr>&gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; 1. One major issue that I see
                          here and you might be able to easily solve it
                          is that there is no distinction between user
                          facing protocols and other protocols. For
                          example, you ask for accessibility and
                          consideration of culture etc. Are you asking
                          all the protocols to be provided in multiple
                          languages, even those that only developers and
                          implementers use and not the actual users? You
                          might want to clarify that.  <br>
                          &gt;     &gt; <br>
                          &gt; <br>
                          &gt;     We had a quite extensive discussion
                          about this in relation to the presentation by
                          Ramsey Nasr who create Qalb, an Arabic
                          programming language. Programmers are the most
                          frequent 'users' of protocols - if we continue
                          using only latin characters and English
                          documentation in protocols we are likely to
                          reproduce the existing lack of diversity in
                          protocol developers communities. But we can
                          make the text on this clearer as well! <br>
                          &gt; <br>
                          &gt;     &gt; 2.section 3.3.1 on connectivity,
                          you mention that "considering the fact that
                          network quality and conditions vary across
                          geography and time it is also important to
                          design protocols such that they are reliable
                          even on low bandwidth ...". Then in your
                          example you say: Middleboxes (including
                          NAT).... can create potential for abuse. NAT
                          is a Network Address Translation protocol. I
                          don't think it has anything to do with
                          bandwidth. In this example you also mention
                          CDNs. Are you suggesting that the developer
                          should not consider "Middleboxes" protocols? I
                          think you need to work on the example of
                          section 3.3.1 some more to make it clearer.  <br>
                          &gt;     &gt; <br>
                          &gt; <br>
                          &gt;     Excellent point - we'll address this
                          in a future version. <br>
                          &gt; <br>
                          &gt;     &gt; 3. section 3.3.20 remedy and
                          attribution  <br>
                          &gt;     &gt; This section worries me. As a 
                          scholar I have worked on cyber attribution to
                          some extent and believe in general when we
                          have the right processes in place, attribution
                          is very important and can hold cyber-attackers
                          accountable. I am aware of some of the
                          attribution processes and unfortunately some
                          threat intelligence firms and open source
                          intelligence organizations can violate the
                          privacy of individuals by profiling them.
                          Also, uncontrolled attribution mechanisms can
                          lead to frivolous intellectual property
                          claims. Both some threat intelligence firms
                          and IP firms have used WHOIS extensively in
                          their favor to attribute cybersecurity attacks
                          and bring forward IP claims. WHOIS protocol
                          did not have the intention to actually
                          identify organizations and individuals, but to
                          make them "contactable".and it was still used
                          and mined for so many years and those who have
                          abused WHOIS have not been held
                          accountable.When you suggest they consider
                          "attribution" when developing protocols it <br>
                          &gt;     &gt; concerns me because it is not
                          enough that you limit attribution to
                          organizations and states. These kinds of
                          attributions can be used against individuals
                          and until we do not have the right preserving
                          processes to put in place for those who want
                          to be in the attribution business, rights of
                          the individual can be at risk. there are very
                          privacy conscious cybersecurity researchers
                          out there but unfortunately that does not
                          ensure a systematic practice of attribution in
                          a fair manner. And you mention attribution to
                          associations is fine and may not directly
                          negatively impact human rights. Associations
                          can themselves be at risk of frivolous attacks
                          and frivolous attribution. I am concerned
                          about this paragraph. I think we should have a
                          conversation about it. <br>
                          &gt;     &gt; <br>
                          &gt; <br>
                          &gt;     In the proposed text I tried to
                          capture the consensus that emerged from the
                          extensive discussion that was had on this
                          list. Do you have concrete suggestions on how
                          to better capture that conensensus? I am
                          afraid we would go back and repeat the same
                          discussion. <br>
                          &gt; <br>
                          &gt;     &gt; 4. Nice to see that you mention
                          DoH. It's a great privacy preserving
                          protocol.  <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt; <br>
                          &gt;     Thanks! <br>
                          &gt; <br>
                          &gt;     Niels <br>
                          &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; Farzaneh <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; On Sat, Jan 30, 2021 at 10:35 AM
                          Corinne Cath &lt; <a
                            href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                          &lt;mailto: <a
                            href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;
                          &lt;mailto: <a
                            href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                          &lt;mailto: <a
                            href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;&gt;&gt;
                          wrote: <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     Hi all, <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     I trust this email finds you
                          well. I did a review of the draft, from my
                          perspective as an academic. Take it as you
                          please. My main concern is that some of the
                          language reads a bit deterministic (as, I know
                          so does RFC 8280). It means that a lot of onus
                          is put on the impact of a protocol, as opposed
                          the role of the individuals that write them. 
                          <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     I think through out the
                          document, it would be interesting (especially
                          in section 1 through 3.2.5) to see if you can
                          rewrite such that you speak more directly to
                          the protocol developers. I think that section
                          3.3 does that well, in terms of the tone it
                          takes. As it clearly connects the actions of
                          protocol developers to their potential
                          outcomes.  <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     Hope this is helpful!  <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     Kind regards,  <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     Corinne <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;   
                           ----------------------------- <wbr>---- <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     *1. Introduction* <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     "It provides questions
                          engineers should ask <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;        themselves when
                          developing or improving protocols if they want
                          to <br>
                          &gt;     &gt;        understand their
                          potential human rights impact." <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     &gt;&gt; maybe if they want
                          to understand potential human rights concerns?
                          Impact seems a little deterministic, as you
                          also mention in the next sentence, I wonder if
                          you can prove such direct impact between
                          protocol development in the IETF and impact on
                          human rights. <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     "The research establishes <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;        that human rights relate
                          to standards and protocols, and offers a <br>
                          &gt;     &gt;        common vocabulary of
                          technical concepts that impact human rights
                          and <br>
                          &gt;     &gt;        how these technical
                          concepts can be combined to ensure that the <br>
                          &gt;     &gt;        Internet remains an
                          enabling environment for human rights." <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     &gt;&gt; same comment for
                          the word impact, perhaps shape? influence?
                          etc. <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;           3.1 &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.1</a>
                          &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.1</a>&gt;&gt;.
                          Human rights threats <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;      "Protocols and standards
                          can harm or enable the right to freedom of <br>
                          &gt;     &gt;        expression, right to
                          non-discrimination, right to equal protection,
                          <br>
                          &gt;     &gt;        right to participate in
                          cultural life, arts and science, right to <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     freedom of assembly and
                          association, and the right to security. " <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     &gt;&gt; again,
                          deterministic language. Perhaps soften or add
                          more concrete examples for context, that draw
                          from current IETF discussions/standards. <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;           3.3 &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.3</a>
                          &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.3</a>&gt;&gt;.
                          Guidelines for human rights considerations <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     again, use of the word
                          impact in the introduction. <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     -- <br>
                          &gt;     &gt;     Corinne Cath - Speth <br>
                          &gt;     &gt;     Ph.D. Candidate, Oxford
                          Internet Institute &amp; Alan Turing Institute
                          <br>
                          &gt;     &gt; <br>
                          &gt;     &gt;     Web: <a
                            href="http://www.oii.ox.ac.uk/people/corinne-cath"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">www.oii.ox.ac.uk/people/<wbr>corinne-cath</a>
                          &lt; <a
                            href="http://www.oii.ox.ac.uk/people/corinne-cath"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>&gt;
                          &lt; <a
                            href="http://www.oii.ox.ac.uk/people/corinne-cath"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>
                          &lt; <a
                            href="http://www.oii.ox.ac.uk/people/corinne-cath"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>&gt;&gt;
                          <br>
                          &gt;     &gt;     Email: <a
                            href="mailto:ccath@turing.ac.uk"
                            target="_blank" moz-do-not-send="true">ccath@turing.ac.uk</a>
                          &lt;mailto: <a
                            href="mailto:ccath@turing.ac.uk"
                            target="_blank" moz-do-not-send="true">ccath@turing.ac.uk</a>&gt;
                          &lt;mailto: <a
                            href="mailto:ccath@turing.ac.uk"
                            target="_blank" moz-do-not-send="true">ccath@turing.ac.uk</a>
                          &lt;mailto: <a
                            href="mailto:ccath@turing.ac.uk"
                            target="_blank" moz-do-not-send="true">ccath@turing.ac.uk</a>&gt;&gt;
                          &amp; <a href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                          &lt;mailto: <a
                            href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;
                          &lt;mailto: <a
                            href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                          &lt;mailto: <a
                            href="mailto:corinnecath@gmail.com"
                            target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;&gt;
                          <br>
                          &gt;     &gt;     Twitter: @C_CS <br>
                          &gt;     &gt;   
                           _____________________________ <wbr>__________________
                          <br>
                          &gt;     &gt;     hrpc mailing list <br>
                          &gt;     &gt;      <a
                            href="mailto:hrpc@irtf.org" target="_blank"
                            moz-do-not-send="true">hrpc@irtf.org</a>
                          &lt;mailto: <a href="mailto:hrpc@irtf.org"
                            target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;
                          &lt;mailto: <a href="mailto:hrpc@irtf.org"
                            target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>
                          &lt;mailto: <a href="mailto:hrpc@irtf.org"
                            target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;&gt;
                          <br>
                          &gt;     &gt;      <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                          &lt; <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
                          &lt; <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                          &lt; <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;&gt;
                          <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; <br>
                          &gt;     &gt; ______________________________ <wbr>_________________
                          <br>
                          &gt;     &gt; hrpc mailing list <br>
                          &gt;     &gt; <a href="mailto:hrpc@irtf.org"
                            target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>
                          &lt;mailto: <a href="mailto:hrpc@irtf.org"
                            target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;
                          <br>
                          &gt;     &gt; <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                          &lt; <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
                          <br>
                          &gt;     &gt; <br>
                          &gt; <br>
                          &gt;     -- <br>
                          &gt;     Niels ten Oever, PhD <br>
                          &gt;     Postdoctoral Researcher - Media
                          Studies Department - University of Amsterdam <br>
                          &gt;     Postdoctoral Research Fellow -
                          Communications Department - Texas A&amp;M
                          University <br>
                          &gt;     Research Fellow - Centre for Internet
                          and Human Rights - European University
                          Viadrina <br>
                          &gt;     Associated Scholar - Centro de
                          Tecnologia e Sociedade - Fundação Getúlio
                          Vargas <br>
                          &gt; <br>
                          &gt;     W: <a
                            href="https://nielstenoever.net"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://nielstenoever.net</a>
                          &lt; <a href="https://nielstenoever.net"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://nielstenoever.net</a>&gt;
                          <br>
                          &gt;     E: <a
                            href="mailto:mail@nielstenoever.net"
                            target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>
                          &lt;mailto: <a
                            href="mailto:mail@nielstenoever.net"
                            target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>&gt;
                          <br>
                          &gt;     T: @nielstenoever <br>
                          &gt;     P/S/WA: +31629051853 <br>
                          &gt;     PGP: 2458 0B70 5C4A FD8A 9488 643A
                          0ED8 3F3A 468A C8B3 <br>
                          &gt; <br>
                          &gt;     Read my dissertation 'Wired Norms'
                          here: <a
                            href="https://pure.uva.nl/ws/files/50781961/Thesis.pdf"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.pdf</a>
                          &lt; <a
                            href="https://pure.uva.nl/ws/files/50781961/Thesis.pdf"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.pdf</a>&gt;
                          <br>
                          &gt;     _____________________________ <wbr>__________________
                          <br>
                          &gt;     hrpc mailing list <br>
                          &gt;      <a href="mailto:hrpc@irtf.org"
                            target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>
                          &lt;mailto: <a href="mailto:hrpc@irtf.org"
                            target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;
                          <br>
                          &gt;      <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                          &lt; <a
                            href="https://www.irtf.org/mailman/listinfo/hrpc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
                          <br>
                          &gt; <br>
                          <br>
                          -- <br>
                          Niels ten Oever, PhD <br>
                          Postdoctoral Researcher - Media Studies
                          Department - University of Amsterdam <br>
                          Postdoctoral Research Fellow - Communications
                          Department - Texas A&amp;M University <br>
                          Research Fellow - Centre for Internet and
                          Human Rights - European University Viadrina <br>
                          Associated Scholar - Centro de Tecnologia e
                          Sociedade - Fundação Getúlio Vargas <br>
                          <br>
                          W: <a href="https://nielstenoever.net"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://nielstenoever.net</a>
                          <br>
                          E: <a href="mailto:mail@nielstenoever.net"
                            target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>
                          <br>
                          T: @nielstenoever <br>
                          P/S/WA: +31629051853 <br>
                          PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A
                          468A C8B3 <br>
                          <br>
                          Read my dissertation 'Wired Norms' here: <a
                            href="https://pure.uva.nl/ws/files/50781961/Thesis.pdf"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.pdf</a>
                          <br>
                        </blockquote>
                      </div>
                    </blockquote>
                  </div>
                </div>
              </blockquote>
            </div>
          </div>
          <br>
          <br>
          -- <br>
          <div dir="ltr">
            <div> <font face="verdana, sans-serif">Farzaneh </font> </div>
          </div>
          <br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
hrpc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hrpc@irtf.org">hrpc@irtf.org</a>
<a class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/hrpc">https://www.irtf.org/mailman/listinfo/hrpc</a>
</pre>
    </blockquote>
  <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table style="border-top: 1px solid #D3D4DE;">
	<tr>
      <td style="width: 55px; padding-top: 18px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
		<td style="width: 470px; padding-top: 17px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Garanti sans virus. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a> 		</td>
	</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>

--------------202E1F996C76D771E9A705D7--


From nobody Tue Feb  2 02:37:22 2021
Return-Path: <braman@tamu.edu>
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 325593A0D03 for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 02:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_NOVOWEL=0.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 SHF3I-7b37_o for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 02:37:14 -0800 (PST)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 0591E3A0CD2 for <hrpc@irtf.org>; Tue,  2 Feb 2021 02:37:13 -0800 (PST)
Received: by mail-il1-x134.google.com with SMTP id y17so18567098ili.12 for <hrpc@irtf.org>; Tue, 02 Feb 2021 02:37:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Oo9TN7p8Sx/bMxgZn36z8PsCyTpSjt2P45mjoBnQQKE=; b=RfM/vUyxRox+NyB6H2ohv/VBpAUDMq8X4Yr5KOZHQ8P7uvEeuW2qgvYYLbIYTMHVxv 4qtPXgVsldmnz6JCtyjY2l0MKgbZKddKjmLcX02taUwWUeXLq9zf05Ke/lG631mpP7Yr V/t8Fi2WyIC7BdyhsjcMinC8oTDORGjvJfZD7K7SRNcXru01OY+HwNFEcibyTNm2Hd/V u83Rnej5kNLVKuqxznFmqkNHpnuWrM6oriN0ryQQXlSVO9v9bp+vMC7y8SS4dAVxb/lA pkw89hCFtb4tEuHsqsUCHGwhC/VY+okXzy5Z2U5bhdYuZwgM0Pytq3/j21LD7Sa4MowO WEcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Oo9TN7p8Sx/bMxgZn36z8PsCyTpSjt2P45mjoBnQQKE=; b=hW1yTp+DK/KnKeC+PwHBgErZER9SzazXvz0TehCahRBo++Z5FbAuGztZ8YfVmYFth4 7U20kLw1Vqwsa+cA5UY3Lam0800cwyyzlbv9CkxTirtZ3Prxni9WLDmeOcYvkbtiZ14I DO9lmKms18M+d13ZhRSNJIBJ071ruH364gjVxlJsgsXv+ZHXHKvBcinuPGNH2Ows6rh+ rb8YmNdka10v6uSsjznYu5UqGNdPzIcp7HCbipbpJKaUFzxGT20vfK1bjPhMoHLJceHN YnqGkrRaIgk9niel8UH+LG+Z/TZdrdKOnOsnWkOdKvV6uqAdmISFPNAFC6dxJaEQOJpY sHyg==
X-Gm-Message-State: AOAM532mejEzf0EEB+FZnnARVut9j77uucEslrdfo6j/f1qpSiY+IkbX YvJo46kj3UQSOxKq+U1QOx6mRxjGQ1eLHfhBDTD45csuHRrlqQ==
X-Google-Smtp-Source: ABdhPJxm4X5o0JcALq9QTeceagME3ZXTKhTlVlEjb0sbt7zru4FXcR2rQ2CmN6OouigbDN/2ghTKGEBs/YBUtCaOFsU=
X-Received: by 2002:a05:6e02:138f:: with SMTP id d15mr16395206ilo.303.1612262232566;  Tue, 02 Feb 2021 02:37:12 -0800 (PST)
MIME-Version: 1.0
References: <mailman.1401.1612260415.7093.hrpc@irtf.org>
In-Reply-To: <mailman.1401.1612260415.7093.hrpc@irtf.org>
From: Sandra Braman <braman@tamu.edu>
Date: Tue, 2 Feb 2021 04:38:50 -0600
Message-ID: <CAB2unbMpgo4nDSDYW=gx8Xsts8gKiBEs0NyzC2JBd+19Npd0Ew@mail.gmail.com>
To: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="000000000000a86c8b05ba580df9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/EzzPbituW2ALwVkeB_FuwB_PFxs>
Subject: Re: [hrpc] hrpc Digest, Vol 71, Issue 7
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: Tue, 02 Feb 2021 10:37:19 -0000

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

I don't know what makes something officially a "last call," but it sounds
as if the discussion needs to be reopened.  There is a range of reasons why
individuals may have been silent -- I mentioned one that affected me a few
days ago -- but reopening it with active encouragement for those who have
been silent to engage might bring additional others into the conversation
in order to determine whether or not there is an actual consensus and, if
not, where this should go.

One of the problems with determining a "consensus," of course, is the
question of who decides whether or not one has been achieved.  Humming is a
lovely cultural tradition but not necessarily reflective of genuine
consensus among all those involved, for all of the reasons affecting who
even gets into that room in the first place and differences in how loudly
people hum.  Beyond that problem, there is the question of control over the
consensus frame itself for a particular conversation.  The question of
whether or not there is actually a consensus here is clearly significantly
contested.





On Tue, Feb 2, 2021 at 4:07 AM <hrpc-request@irtf.org> wrote:

> Send hrpc mailing list submissions to
>         hrpc@irtf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;=
!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9=
cSg$
> or, via email, send a message with subject or body 'help' to
>         hrpc-request@irtf.org
>
> You can reach the person managing the list at
>         hrpc-owner@irtf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of hrpc digest..."
> Today's Topics:
>
>    1. Re: Comment on draft-guidelines for RG Last Call (Mark Perkins)
>
>
>
> ---------- Forwarded message ----------
> From: Mark Perkins <marknoumea@yahoo.com>
> To: hrpc@irtf.org
> Cc:
> Bcc:
> Date: Tue, 2 Feb 2021 21:06:27 +1100
> Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
>
> Not sure that Farzaneh is in the rough, I came out clearly against
> attribution a while ago (start of the discussion?).  Not sure how many
> others are also opposed, as not many have spoken - perhaps a straw poll i=
s
> needed? My impression is that there is no consensus on this issue, more
> like a clear division.
>
> Mark P.
> Le 02/02/2021 =C3=A0 18:57, Niels ten Oever a =C3=A9crit :
>
> Dear Farzaneh,
>
> In the extensive discussion between you, John, Amelia, Pranesh and others
> you were the only one who said attribution has no role in this document
> whatsoever. You reiterate this position.  But that might mean that you ar=
e
> in the rough.
>
> Best,
>
> Niels
> On Feb 2, 2021, at 02:06, farzaneh badii <farzaneh.badii@gmail.com>
> wrote:
>>
>> Niels,
>>
>> I don't know how you come to consensus. I thought you as one of the
>> drafters need to make changes that capture the consensus. Seems like you
>> have had =E2=80=9Cmany discussions=E2=80=9D and all the points I have ra=
ised been resolved
>> satisfactorily in this group in my absence. Then the only thing I can do=
 is
>> to record my objection to paragraph 3.3.20: Attribution.
>>
>> I don't think the paragraph as is in that document is human rights
>> enabling and frankly it has the potential to do the opposite. It is a
>> mistake to bring court and law enforcement to the discussion when the sc=
ope
>> of this group is "enabling human rights". It is a mistake to make a
>> distinction between natural and legal persons in this case and assume th=
at
>> natural persons may not be harmed in the process because the distinction
>> =E2=80=9Cmay=E2=80=9D protect them.
>>
>> I brought reasons and they don't seem to be convincing to you or
>> something you want to work with and it seems to me it is too late now. S=
o I
>> get out of your way and just record my objection to the paragraph.
>>
>> Just to disclose: I have worked on cyber attack attribution processes
>> academically, and believe that attribution is one way to hold cyber
>> attackers accountable. I just don=E2=80=99t think we need the protocol d=
eveloper
>> think about ways of attribution to make it easier to attribute cyber
>> attacks in court for legal remedy and include this in the guidelines for
>> human rights protection document as a =E2=80=9Caccess to legal remedy=E2=
=80=9D. Anonymity
>> makes attribution harder but still not impossible. Many John Doe=E2=80=
=99s have had
>> cases against them which provided the plaintiffs with the appropriate
>> remedies.
>>
>>
>>
>>
>>
>> On Mon, Feb 1, 2021 at 5:19 PM Niels ten Oever < mail@nielstenoever.net>
>> wrote:
>>
>>> Dear Farzaneh,
>>>
>>> Do your alterations reflect the content of the discussion, or mere your
>>> opinion?
>>>
>>> I hope we're seeking to reach a consensus during last call, not
>>> reopening the discussion.
>>>
>>> Best,
>>>
>>> Niels
>>>
>>> On Feb 1, 2021, at 22:22, farzaneh badii < farzaneh.badii@gmail.com>
>>> wrote:
>>>>
>>>> Here we go:
>>>>
>>>>
>>>> Question(s): Can your protocol facilitate a negatively impacted
>>>>
>>>>    party's right to the appropriate  legal remedy without
>>>> disproportionately impacting
>>>>
>>>>    other parties' human rights, especially their right to privacy?
>>>>
>>>>
>>>>    Explanation: Access to legal remedy is a human right that ensures
>>>>
>>>>    that individuals whose rights have been violated can seek remedies
>>>>
>>>>
>>>>
>>>>
>>>>    through a judicial authority.   Attribution (i.e. mechanisms in
>>>>
>>>>    protocols or architectures that are designed to make communications
>>>>
>>>>    or artifacts attributable might help with seeking the appropriate
>>>> remedy.)  to a certain computer or individual) can be
>>>>
>>>>    a part of this, since it may allow law enforcement agencies to
>>>>
>>>>    identify a possible violator .  However, attribution mechanisms may
>>>>
>>>    impede the exercise of the right to privacy.  The Special Rapporteur
>>>>
>>>>    for Freedom of Expression has also argued that anonymity is an
>>>>
>>>>    inherent part of freedom of expression.  [Kaye] Considering the
>>>>
>>>>    adverse impact of attribution on the right to privacy and freedom o=
f
>>>>
>>>>    expression, attribution on an individual level may  is not be
>>>> consistent
>>>>
>>>>    with human rights.  However, attribution to corporate entities,
>>>>
>>>>    associations, and/or countries may not directly negatively impact
>>>>
>>>>    human rights.
>>>>
>>>>
>>>>    Impacts:
>>>>
>>>>
>>>>    -   Right to legal remedy
>>>>
>>>>
>>>>    -  Right to security
>>>>
>>> Farzaneh
>>>>
>>>>
>>>> On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever < mail@nielstenoever.ne=
t>
>>>> wrote:
>>>>
>>>>> Hi Farzaneh,
>>>>>
>>>>> On 31-01-2021 19:16, farzaneh badii wrote:
>>>>> > Hello Niels.
>>>>> >
>>>>> >
>>>>> > I don't know how we measure consensus here. But I remember weighing
>>>>> in back then as well(When Mr. Curran weighed in back in 2019). Here i=
s the
>>>>> thread:  https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattributi=
on
>>>>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse=
/hrpc/?q=3Dattribution__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZ=
XjmpA9gGCELNgpD3MPnzmlLt_T_4$>
>>>>> < https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution
>>>>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse=
/hrpc/?q=3Dattribution__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZ=
XjmpA9gGCELNgpD3MPnzmlLt_T_4$>>
>>>>>
>>>>> >
>>>>> > I can see that unfortunately I missed the discussion on this topic
>>>>> during the past year, and that's my fault, but I can bring reasons no=
t to
>>>>> add "attribution and legal remedy" to this document at all.
>>>>> >
>>>>> > 1. Access to legal remedy is something that the States are
>>>>> supposedly in charge of bringing to their citizens.Which should (in t=
heory)
>>>>> ensure that human rights are enforced. I don't think there was an int=
ention
>>>>> to  provide  mechanisms for "enforcement" of human rights in various =
legal
>>>>> systems through Internet protocols. As mentioned in the beginning of =
your
>>>>> document:
>>>>> > "Human rights threats on the Internet come in a myriad of
>>>>> forms.* **P**rotocols and standards can harm or enable* the right to
>>>>> freedom of expression, right to non-discrimination, right to equal
>>>>> protection, right to participate in cultural life, arts and science, =
right
>>>>> to freedom of assembly and association, and the right to security."
>>>>> >
>>>>> > So we are not in the business of enforcing but providing an enablin=
g
>>>>> environment. Because if we want to help law enforcement and the judic=
ial
>>>>> authorities enforce human rights through Internet protocols we should=
 bear
>>>>> in mind that that they are not always staunch advocates of human righ=
ts. So
>>>>> what I assume we are trying to do here is to help Internet protocol n=
ot to
>>>>> facilitate harm and "enable" human rights.
>>>>> >
>>>>>
>>>>> The text in the draft seeks to address this risk. I have sought to
>>>>> address all points made in that discussion, and I would not like to r=
e-open
>>>>> that debate. If you feel the text is unbalanced, could you perhaps pr=
ovide
>>>>> text suggestions?
>>>>>
>>>>> > 2. Attribution, section 3.3.20  of the Guideline, the authors asser=
t
>>>>> that: "However, attribution to corporate entities, associations, and/=
or
>>>>> countries may not directly negatively impact human rights." I think t=
his is
>>>>> not a very well backed up claim. Because in some cases some associati=
ons
>>>>> might be political or they might be human rights associations dealing=
 with
>>>>> a dictatorship. Attribution to those associations certainly can impac=
t
>>>>> their human rights negatively. Even when it comes to corporations, so=
me
>>>>> CEOs of digital companies are put in jail because of the materials po=
sted
>>>>> on their websites. I don't think we can argue that attribution to cor=
porate
>>>>> entities might not adversely impact human rights.
>>>>> >
>>>>>
>>>>> Again, the keyword in that sentence is 'may', so there is no strong
>>>>> claim made.
>>>>>
>>>>> > All in all I think section 3.3.20 does not help Internet Protocols
>>>>> enable human rights and it can be misinterpreted.
>>>>>
>>>>> I think the text in there is not strong and shows different
>>>>> perspectives and potential consequences. But again, happy to receive =
text
>>>>> suggestions.
>>>>>
>>>>> >
>>>>> > And in my previous email I talked about the problems with threat
>>>>> intelligence agencies and some of their conducts and the use of WHOIS=
 for
>>>>> attribution (which was actually not designed to "identify" actors but
>>>>> unfortunately was used for that) so I will not reiterate here.
>>>>>
>>>>> From exactly that discussion we got the idea to remove individuals,
>>>>> and leave non-natural persons in.
>>>>>
>>>>> Best,
>>>>>
>>>>> Niels
>>>>>
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever <
>>>>> mail@nielstenoever.net <mailto: mail@nielstenoever.net>> wrote:
>>>>> >
>>>>> >     Hi Farzaneh,
>>>>> >
>>>>> >     Thanks a lot for the review!
>>>>> >
>>>>> >     On 30-01-2021 23:00, farzaneh badii wrote:
>>>>> >     > Hello
>>>>> >     >
>>>>> >     > Adding my comments on this document:
>>>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA=
9gGCELNgpD3MPnzmcgv0BsM$>
>>>>> < https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA=
9gGCELNgpD3MPnzmcgv0BsM$>>
>>>>> < https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA=
9gGCELNgpD3MPnzmcgv0BsM$>
>>>>> < https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA=
9gGCELNgpD3MPnzmcgv0BsM$>>
>>>>> >
>>>>> >     >
>>>>> >     > 1. One major issue that I see here and you might be able to
>>>>> easily solve it is that there is no distinction between user facing
>>>>> protocols and other protocols. For example, you ask for accessibility=
 and
>>>>> consideration of culture etc. Are you asking all the protocols to be
>>>>> provided in multiple languages, even those that only developers and
>>>>> implementers use and not the actual users? You might want to clarify =
that.
>>>>> >     >
>>>>> >
>>>>> >     We had a quite extensive discussion about this in relation to
>>>>> the presentation by Ramsey Nasr who create Qalb, an Arabic programmin=
g
>>>>> language. Programmers are the most frequent 'users' of protocols - if=
 we
>>>>> continue using only latin characters and English documentation in pro=
tocols
>>>>> we are likely to reproduce the existing lack of diversity in protocol
>>>>> developers communities. But we can make the text on this clearer as w=
ell!
>>>>> >
>>>>> >     > 2.section 3.3.1 on connectivity, you mention that "considerin=
g
>>>>> the fact that network quality and conditions vary across geography an=
d time
>>>>> it is also important to design protocols such that they are reliable =
even
>>>>> on low bandwidth ...". Then in your example you say: Middleboxes (inc=
luding
>>>>> NAT).... can create potential for abuse. NAT is a Network Address
>>>>> Translation protocol. I don't think it has anything to do with bandwi=
dth.
>>>>> In this example you also mention CDNs. Are you suggesting that the
>>>>> developer should not consider "Middleboxes" protocols? I think you ne=
ed to
>>>>> work on the example of section 3.3.1 some more to make it clearer.
>>>>> >     >
>>>>> >
>>>>> >     Excellent point - we'll address this in a future version.
>>>>> >
>>>>> >     > 3. section 3.3.20 remedy and attribution
>>>>> >     > This section worries me. As a  scholar I have worked on cyber
>>>>> attribution to some extent and believe in general when we have the ri=
ght
>>>>> processes in place, attribution is very important and can hold
>>>>> cyber-attackers accountable. I am aware of some of the attribution
>>>>> processes and unfortunately some threat intelligence firms and open s=
ource
>>>>> intelligence organizations can violate the privacy of individuals by
>>>>> profiling them. Also, uncontrolled attribution mechanisms can lead to
>>>>> frivolous intellectual property claims. Both some threat intelligence=
 firms
>>>>> and IP firms have used WHOIS extensively in their favor to attribute
>>>>> cybersecurity attacks and bring forward IP claims. WHOIS protocol did=
 not
>>>>> have the intention to actually identify organizations and individuals=
, but
>>>>> to make them "contactable".and it was still used and mined for so man=
y
>>>>> years and those who have abused WHOIS have not been held accountable.=
When
>>>>> you suggest they consider "attribution" when developing protocols it
>>>>> >     > concerns me because it is not enough that you limit
>>>>> attribution to organizations and states. These kinds of attributions =
can be
>>>>> used against individuals and until we do not have the right preservin=
g
>>>>> processes to put in place for those who want to be in the attribution
>>>>> business, rights of the individual can be at risk. there are very pri=
vacy
>>>>> conscious cybersecurity researchers out there but unfortunately that =
does
>>>>> not ensure a systematic practice of attribution in a fair manner. And=
 you
>>>>> mention attribution to associations is fine and may not directly nega=
tively
>>>>> impact human rights. Associations can themselves be at risk of
>>>>> frivolous attacks and frivolous attribution. I am concerned about thi=
s
>>>>> paragraph. I think we should have a conversation about it.
>>>>> >     >
>>>>> >
>>>>> >     In the proposed text I tried to capture the consensus that
>>>>> emerged from the extensive discussion that was had on this list. Do y=
ou
>>>>> have concrete suggestions on how to better capture that conensensus? =
I am
>>>>> afraid we would go back and repeat the same discussion.
>>>>> >
>>>>> >     > 4. Nice to see that you mention DoH. It's a great privacy
>>>>> preserving protocol.
>>>>> >     >
>>>>> >     >
>>>>> >
>>>>> >     Thanks!
>>>>> >
>>>>> >     Niels
>>>>> >
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     > Farzaneh
>>>>> >     >
>>>>> >     >
>>>>> >     > On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath <
>>>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com> <mailto:
>>>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com>>> wrote:
>>>>> >     >
>>>>> >     >     Hi all,
>>>>> >     >
>>>>> >     >     I trust this email finds you well. I did a review of the
>>>>> draft, from my perspective as an academic. Take it as you please. My =
main
>>>>> concern is that some of the language reads a bit deterministic (as, I=
 know
>>>>> so does RFC 8280). It means that a lot of onus is put on the impact o=
f a
>>>>> protocol, as opposed the role of the individuals that write them.
>>>>> >     >
>>>>> >     >     I think through out the document, it would be interesting
>>>>> (especially in section 1 through 3.2.5) to see if you can rewrite suc=
h that
>>>>> you speak more directly to the protocol developers. I think that sect=
ion
>>>>> 3.3 does that well, in terms of the tone it takes. As it clearly conn=
ects
>>>>> the actions of protocol developers to their potential outcomes.
>>>>> >     >
>>>>> >     >     Hope this is helpful!
>>>>> >     >
>>>>> >     >     Kind regards,
>>>>> >     >
>>>>> >     >     Corinne
>>>>> >     >
>>>>> >     >     ----------------------------- ----
>>>>> >     >
>>>>> >     >     *1. Introduction*
>>>>> >     >
>>>>> >     >     "It provides questions engineers should ask
>>>>> >     >
>>>>> >     >        themselves when developing or improving protocols if
>>>>> they want to
>>>>> >     >        understand their potential human rights impact."
>>>>> >     >
>>>>> >     >
>>>>> >     >     >> maybe if they want to understand potential human right=
s
>>>>> concerns? Impact seems a little deterministic, as you also mention in=
 the
>>>>> next sentence, I wonder if you can prove such direct impact between
>>>>> protocol development in the IETF and impact on human rights.
>>>>> >     >
>>>>> >     >     "The research establishes
>>>>> >     >
>>>>> >     >        that human rights relate to standards and protocols,
>>>>> and offers a
>>>>> >     >        common vocabulary of technical concepts that impact
>>>>> human rights and
>>>>> >     >        how these technical concepts can be combined to ensure
>>>>> that the
>>>>> >     >        Internet remains an enabling environment for human
>>>>> rights."
>>>>> >     >
>>>>> >     >
>>>>> >     >     >> same comment for the word impact, perhaps shape?
>>>>> influence? etc.
>>>>> >     >
>>>>> >     >
>>>>> >     >           3.1 <
>>>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05*section-3.1__;Iw!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw=
91NOgEgyZXjmpA9gGCELNgpD3MPnzmqu9haL4$>
>>>>> <
>>>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05*section-3.1__;Iw!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw=
91NOgEgyZXjmpA9gGCELNgpD3MPnzmqu9haL4$>>>.
>>>>> Human rights threats
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >      "Protocols and standards can harm or enable the right to
>>>>> freedom of
>>>>> >     >        expression, right to non-discrimination, right to equa=
l
>>>>> protection,
>>>>> >     >        right to participate in cultural life, arts and
>>>>> science, right to
>>>>> >     >
>>>>> >     >     freedom of assembly and association, and the right to
>>>>> security. "
>>>>> >     >
>>>>> >     >
>>>>> >     >     >> again, deterministic language. Perhaps soften or add
>>>>> more concrete examples for context, that draw from current IETF
>>>>> discussions/standards.
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >           3.3 <
>>>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05*section-3.3__;Iw!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw=
91NOgEgyZXjmpA9gGCELNgpD3MPnzmYPOkf-A$>
>>>>> <
>>>>> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3
>>>>> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05*section-3.3__;Iw!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw=
91NOgEgyZXjmpA9gGCELNgpD3MPnzmYPOkf-A$>>>.
>>>>> Guidelines for human rights considerations
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >     again, use of the word impact in the introduction.
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >
>>>>> >     >     --
>>>>> >     >     Corinne Cath - Speth
>>>>> >     >     Ph.D. Candidate, Oxford Internet Institute & Alan Turing
>>>>> Institute
>>>>> >     >
>>>>> >     >     Web: www.oii.ox.ac.uk/people/corinne-cath
>>>>> <https://urldefense.com/v3/__http://www.oii.ox.ac.uk/people/corinne-c=
ath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPn=
zmGORuL8k$>
>>>>> < http://www.oii.ox.ac.uk/people/corinne-cath
>>>>> <https://urldefense.com/v3/__http://www.oii.ox.ac.uk/people/corinne-c=
ath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPn=
zmGORuL8k$>>
>>>>> < http://www.oii.ox.ac.uk/people/corinne-cath
>>>>> <https://urldefense.com/v3/__http://www.oii.ox.ac.uk/people/corinne-c=
ath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPn=
zmGORuL8k$>
>>>>> < http://www.oii.ox.ac.uk/people/corinne-cath
>>>>> <https://urldefense.com/v3/__http://www.oii.ox.ac.uk/people/corinne-c=
ath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPn=
zmGORuL8k$>>>
>>>>>
>>>>> >     >     Email: ccath@turing.ac.uk <mailto: ccath@turing.ac.uk>
>>>>> <mailto: ccath@turing.ac.uk <mailto: ccath@turing.ac.uk>> &
>>>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com> <mailto:
>>>>> corinnecath@gmail.com <mailto: corinnecath@gmail.com>>
>>>>> >     >     Twitter: @C_CS
>>>>> >     >     _____________________________ __________________
>>>>> >     >     hrpc mailing list
>>>>> >     >      hrpc@irtf.org <mailto: hrpc@irtf.org> <mailto:
>>>>> hrpc@irtf.org <mailto: hrpc@irtf.org>>
>>>>> >     >      https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>
>>>>> < https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>>
>>>>> < https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>
>>>>> < https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>>>
>>>>>
>>>>> >     >
>>>>> >     >
>>>>> >     > ______________________________ _________________
>>>>> >     > hrpc mailing list
>>>>> >     > hrpc@irtf.org <mailto: hrpc@irtf.org>
>>>>> >     > https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>
>>>>> < https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>>
>>>>>
>>>>> >     >
>>>>> >
>>>>> >     --
>>>>> >     Niels ten Oever, PhD
>>>>> >     Postdoctoral Researcher - Media Studies Department - University
>>>>> of Amsterdam
>>>>> >     Postdoctoral Research Fellow - Communications Department - Texa=
s
>>>>> A&M University
>>>>> >     Research Fellow - Centre for Internet and Human Rights -
>>>>> European University Viadrina
>>>>> >     Associated Scholar - Centro de Tecnologia e Sociedade - Funda=
=C3=A7=C3=A3o
>>>>> Get=C3=BAlio Vargas
>>>>> >
>>>>> >     W: https://nielstenoever.net
>>>>> <https://urldefense.com/v3/__https://nielstenoever.net__;!!KwNVnqRv!U=
RgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmZWdheys$>
>>>>> < https://nielstenoever.net
>>>>> <https://urldefense.com/v3/__https://nielstenoever.net__;!!KwNVnqRv!U=
RgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmZWdheys$>>
>>>>>
>>>>> >     E: mail@nielstenoever.net <mailto: mail@nielstenoever.net>
>>>>> >     T: @nielstenoever
>>>>> >     P/S/WA: +31629051853
>>>>> >     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>>>>> >
>>>>> >     Read my dissertation 'Wired Norms' here:
>>>>> https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>>>>> <https://urldefense.com/v3/__https://pure.uva.nl/ws/files/50781961/Th=
esis.pdf__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgp=
D3MPnzmJOAMClE$>
>>>>> < https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>>>>> <https://urldefense.com/v3/__https://pure.uva.nl/ws/files/50781961/Th=
esis.pdf__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgp=
D3MPnzmJOAMClE$>>
>>>>>
>>>>> >     _____________________________ __________________
>>>>> >     hrpc mailing list
>>>>> >      hrpc@irtf.org <mailto: hrpc@irtf.org>
>>>>> >      https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>
>>>>> < https://www.irtf.org/mailman/listinfo/hrpc
>>>>> <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hr=
pc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mNdA9cSg$>>
>>>>>
>>>>> >
>>>>>
>>>>> --
>>>>> Niels ten Oever, PhD
>>>>> Postdoctoral Researcher - Media Studies Department - University of
>>>>> Amsterdam
>>>>> Postdoctoral Research Fellow - Communications Department - Texas A&M
>>>>> University
>>>>> Research Fellow - Centre for Internet and Human Rights - European
>>>>> University Viadrina
>>>>> Associated Scholar - Centro de Tecnologia e Sociedade - Funda=C3=A7=
=C3=A3o
>>>>> Get=C3=BAlio Vargas
>>>>>
>>>>> W: https://nielstenoever.net
>>>>> <https://urldefense.com/v3/__https://nielstenoever.net__;!!KwNVnqRv!U=
RgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmZWdheys$>
>>>>> E: mail@nielstenoever.net
>>>>> T: @nielstenoever
>>>>> P/S/WA: +31629051853
>>>>> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>>>>>
>>>>> Read my dissertation 'Wired Norms' here:
>>>>> https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>>>>> <https://urldefense.com/v3/__https://pure.uva.nl/ws/files/50781961/Th=
esis.pdf__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgp=
D3MPnzmJOAMClE$>
>>>>>
>>>>
>>
>> --
>> Farzaneh
>>
>>
> _______________________________________________
> hrpc mailing listhrpc@irtf.orghttps://www.irtf.org/mailman/listinfo/hrpc =
<https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!=
!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9c=
Sg$>
>
>
>
> <https://urldefense.com/v3/__https://www.avast.com/sig-email?utm_medium=
=3Demail&utm_source=3Dlink&utm_campaign=3Dsig-email&utm_content=3Demailclie=
nt__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mdWjSL3Q$> Garanti
> sans virus. www.avast.com
> <https://urldefense.com/v3/__https://www.avast.com/sig-email?utm_medium=
=3Demail&utm_source=3Dlink&utm_campaign=3Dsig-email&utm_content=3Demailclie=
nt__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnz=
mdWjSL3Q$>
> <#m_-3487738066469627961_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;=
!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9=
cSg$
>

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

<div dir=3D"ltr">I don&#39;t know what makes something officially a &quot;l=
ast call,&quot; but it sounds as if the discussion needs to be reopened.=C2=
=A0 There is a range of reasons why individuals may have been silent -- I m=
entioned one that affected me a few days ago -- but reopening it with activ=
e encouragement for those who have been silent to engage might bring additi=
onal others into the conversation in order to determine whether or not ther=
e is an actual consensus and, if not, where this should go.<div><br></div><=
div>One of the problems with determining a &quot;consensus,&quot; of course=
, is the question of who decides whether or not one has been achieved.=C2=
=A0 Humming is a lovely cultural tradition but not necessarily reflective o=
f genuine consensus among all those involved, for all of the reasons affect=
ing who even gets into that room in the first place and differences in how =
loudly people hum.=C2=A0 Beyond that problem, there is the question of cont=
rol over the consensus frame itself for a particular conversation.=C2=A0 Th=
e question of whether or not there is actually a consensus here is clearly =
significantly contested.=C2=A0=C2=A0</div><div><br></div><div><br></div><di=
v><br></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Tue, Feb 2, 2021 at 4:07 AM &lt;<a href=3D"ma=
ilto:hrpc-request@irtf.org">hrpc-request@irtf.org</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">Send hrpc mailing list sub=
missions to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc@irtf.org" target=3D"_bla=
nk">hrpc@irtf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://urldefense.com/v3/__https://=
www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq=
-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"_bl=
ank">https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc=
__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmN=
dA9cSg$</a> <br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-request@irtf.org" target=
=3D"_blank">hrpc-request@irtf.org</a><br>
<br>
You can reach the person managing the list at<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-owner@irtf.org" target=
=3D"_blank">hrpc-owner@irtf.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of hrpc digest...&quot;<br>
Today&#39;s Topics:<br>
<br>
=C2=A0 =C2=A01. Re: Comment on draft-guidelines for RG Last Call (Mark Perk=
ins)<br>
<br><br><br>---------- Forwarded message ----------<br>From:=C2=A0Mark Perk=
ins &lt;<a href=3D"mailto:marknoumea@yahoo.com" target=3D"_blank">marknoume=
a@yahoo.com</a>&gt;<br>To:=C2=A0<a href=3D"mailto:hrpc@irtf.org" target=3D"=
_blank">hrpc@irtf.org</a><br>Cc:=C2=A0<br>Bcc:=C2=A0<br>Date:=C2=A0Tue, 2 F=
eb 2021 21:06:27 +1100<br>Subject:=C2=A0Re: [hrpc] Comment on draft-guideli=
nes for RG Last Call<br>
 =20
   =20
 =20
  <div>
    <p>Not sure that Farzaneh is in the rough, I came out clearly
      against attribution a while ago (start of the discussion?).=C2=A0 Not
      sure how many others are also opposed, as not many have spoken -
      perhaps a straw poll is needed? My impression is that there is no
      consensus on this issue, more like a clear division.</p>
    <p>Mark P.<br>
    </p>
    <div>Le 02/02/2021 =C3=A0 18:57, Niels ten Oever
      a =C3=A9crit=C2=A0:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"auto">Dear Farzaneh,<br>
        <br>
      </div>
      <div dir=3D"auto">In the extensive discussion between you, John,
        Amelia, Pranesh and others you were the only one who said
        attribution has no role in this document whatsoever. You
        reiterate this position.=C2=A0 But that might mean that you are in
        the rough. <br>
        <br>
      </div>
      <div dir=3D"auto">Best,<br>
        <br>
      </div>
      <div dir=3D"auto">Niels</div>
      <div class=3D"gmail_quote">On Feb 2, 2021, at 02:06, farzaneh badii
        &lt;<a href=3D"mailto:farzaneh.badii@gmail.com" target=3D"_blank">f=
arzaneh.badii@gmail.com</a>&gt; wrote:
        <blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div> Niels,=C2=A0 <br>
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> I don&#39;t know how you come to consensus. I
            thought you as one of the drafters need to make changes that
            capture the consensus. Seems like you have had =E2=80=9Cmany
            discussions=E2=80=9D and all the points I have raised been reso=
lved
            satisfactorily in this group in my absence. Then the only
            thing I can do is to record my objection to paragraph
            3.3.20: Attribution.=C2=A0
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> I don&#39;t think the paragraph as is in that
            document is human rights enabling and frankly it has the
            potential to do the opposite. It is a mistake to bring court
            and law enforcement to the discussion when the scope of this
            group is &quot;enabling human rights&quot;. It is a mistake to =
make a
            distinction between natural and legal persons in this case
            and assume that natural persons may not be harmed in the
            process because the distinction =E2=80=9Cmay=E2=80=9D protect t=
hem.=C2=A0
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> I brought reasons and they don&#39;t seem to b=
e
            convincing to you or something you want to work with and it
            seems to me it is too late now. So I get out of your way and
            just record my objection to the paragraph.=C2=A0
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> Just to disclose: I have worked on cyber
            attack attribution processes academically, and believe that
            attribution is one way to hold cyber attackers accountable.
            I just don=E2=80=99t think we need the protocol developer think
            about ways of attribution to make it easier to attribute
            cyber attacks in court for legal remedy and include this in
            the guidelines for human rights protection document as a
            =E2=80=9Caccess to legal remedy=E2=80=9D. Anonymity makes attri=
bution harder
            but still not impossible. Many John Doe=E2=80=99s have had case=
s
            against them which provided the plaintiffs with the
            appropriate remedies.=C2=A0
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> <br>
          </div>
          <div dir=3D"auto"> <br>
            <div class=3D"gmail_quote" dir=3D"auto">
              <div dir=3D"ltr" class=3D"gmail_attr"> On Mon, Feb 1, 2021 at
                5:19 PM Niels ten Oever &lt; <a href=3D"mailto:mail@nielste=
noever.net" target=3D"_blank">mail@nielstenoever.net</a>&gt;
                wrote: <br>
              </div>
              <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                <div style=3D"zoom:0%">
                  <div dir=3D"auto"> Dear Farzaneh, <br>
                    <br>
                  </div>
                  <div dir=3D"auto"> Do your alterations reflect the
                    content of the discussion, or mere your opinion? <br>
                    <br>
                  </div>
                  <div dir=3D"auto"> I hope we&#39;re seeking to reach a
                    consensus during last call, not reopening the
                    discussion. <br>
                    <br>
                  </div>
                  <div dir=3D"auto"> Best, <br>
                    <br>
                  </div>
                  <div dir=3D"auto"> Niels <br>
                    <br>
                  </div>
                  <div class=3D"gmail_quote"> On Feb 1, 2021, at 22:22,
                    farzaneh badii &lt; <a href=3D"mailto:farzaneh.badii@gm=
ail.com" target=3D"_blank">farzaneh.badii@gmail.com</a>&gt;
                    wrote:
                    <blockquote class=3D"gmail_quote" style=3D"margin:0pt 0=
pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                      <div dir=3D"ltr">
                        <div class=3D"gmail_default" style=3D"font-family:v=
erdana,sans-serif"> Here
                          we go: </div>
                        <div class=3D"gmail_default" style=3D"font-family:v=
erdana,sans-serif"> <br>
                        </div>
                        <div class=3D"gmail_default" style=3D"font-family:v=
erdana,sans-serif"> <br>
                        </div>
                        <div class=3D"gmail_default" style=3D"font-family:v=
erdana,sans-serif">
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">Question(s):
                            Can your protocol facilitate a negatively
                            impacted</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>party&#39;s right to<font color=3D"#ff00=
00">=C2=A0the
                              appropriate </font> <strike> =C2=A0legal </st=
rike>remedy
                            without disproportionately impacting</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>other parties&#39; human rights,
                            especially their right to privacy?</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>Explanation:
                              Access to legal remedy is a human right
                              that ensures </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>that individ=
uals
                              whose rights have been violated can seek
                              remedies </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>through a
                              judicial authority. </strike><span>=C2=A0 </s=
pan>Attribution
                            (i.e. mechanisms in</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>protocols or architectures that are
                            designed to make communications</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>or artifacts attributable <font color=3D=
"#ff0000">might help with seeking
                              the appropriate remedy</font>.)=C2=A0 <strike=
>
                              to a certain computer or individual) </strike=
>
                            <strike> can be </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>a part of th=
is,
                              since it may allow law enforcement
                              agencies to </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>identify a
                              possible violator </strike>.<span>=C2=A0 </sp=
an>However,
                            attribution mechanisms may</p>
                        </div>
                      </div>
                    </blockquote>
                  </div>
                </div>
                <div style=3D"zoom:0%">
                  <div class=3D"gmail_quote">
                    <blockquote class=3D"gmail_quote" style=3D"margin:0pt 0=
pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                      <div dir=3D"ltr">
                        <div class=3D"gmail_default" style=3D"font-family:v=
erdana,sans-serif">
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>impede the exercise of the right to
                            privacy.<span>=C2=A0 </span>The Special
                            Rapporteur</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>for Freedom of Expression has also
                            argued that anonymity is an</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>inherent part of freedom of
                            expression.<span>=C2=A0 </span>[Kaye]
                            Considering the</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>adverse impact of attribution on the
                            right to privacy and freedom of</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>expression, attribution on an
                            individual level <strike> may </strike>=C2=A0<f=
ont color=3D"#ff0000">is=C2=A0</font>not <strike> be
                            </strike> consistent</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>with human rights.<span>=C2=A0 <strike> =
</strike></span>
                            <strike> However, attribution to corporate
                              entities, </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>associations=
,
                              and/or countries may not directly
                              negatively impact </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>human rights=
. </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>Impacts:</p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica;min-height:14px">
                            <strike> <br>
                            </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica">
                            <strike> <span>=C2=A0=C2=A0 </span>- <span>=C2=
=A0 </span>Right
                              to legal remedy </strike></p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                          </p>
                          <p style=3D"margin:0px;font-stretch:normal;font-s=
ize:12px;line-height:normal;font-family:Helvetica"><span>=C2=A0=C2=A0
                            </span>-<span>=C2=A0 </span>Right to security</=
p>
                        </div>
                      </div>
                    </blockquote>
                  </div>
                </div>
                <div style=3D"zoom:0%">
                  <div class=3D"gmail_quote">
                    <blockquote class=3D"gmail_quote" style=3D"margin:0pt 0=
pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                      <div dir=3D"ltr">
                        <div>
                          <div dir=3D"ltr">
                            <div dir=3D"ltr">
                              <div> <font face=3D"verdana, sans-serif">Farz=
aneh
                                </font> </div>
                            </div>
                          </div>
                        </div>
                        <br>
                      </div>
                    </blockquote>
                  </div>
                </div>
                <div style=3D"zoom:0%">
                  <div class=3D"gmail_quote">
                    <blockquote class=3D"gmail_quote" style=3D"margin:0pt 0=
pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
                      <div class=3D"gmail_quote">
                        <div dir=3D"ltr" class=3D"gmail_attr"> On Mon, Feb
                          1, 2021 at 2:38 PM Niels ten Oever &lt; <a href=
=3D"mailto:mail@nielstenoever.net" target=3D"_blank">mail@nielstenoever.net=
</a>&gt;
                          wrote: <br>
                        </div>
                        <blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> =
Hi
                          Farzaneh, <br>
                          <br>
                          On 31-01-2021 19:16, farzaneh badii wrote: <br>
                          &gt; Hello Niels. <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; I don&#39;t know how we measure consensus
                          here. But I remember weighing in back then as
                          well(When Mr. Curran weighed in back in 2019).
                          Here is the thread:=C2=A0 <a href=3D"https://urld=
efense.com/v3/__https://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribut=
ion__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPn=
zmlLt_T_4$" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.o=
rg/arch/browse/hrpc/?q=3Dattribution</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://mailarchive.ietf.org/arch/browse/hrpc/?q=3Dattribution__;!!KwNVnqRv!URgH=
L-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmlLt_T_4$" rel=3D"no=
referrer" target=3D"_blank">https://mailarchive.ietf.org/arch/browse/hrpc/?=
q=3Dattribution</a>&gt;
                          <br>
                          &gt; <br>
                          &gt; I can see that unfortunately I missed
                          the=C2=A0discussion on this topic during the past
                          year, and that&#39;s my fault, but I can bring
                          reasons not to add &quot;attribution and legal
                          remedy&quot; to this document at all.=C2=A0 <br>
                          &gt; <br>
                          &gt; 1. Access to legal remedy is something
                          that the States are supposedly in charge of
                          bringing to their citizens.Which should (in
                          theory) ensure that human rights are enforced.
                          I don&#39;t think there=C2=A0was an intention to=
=C2=A0
                          provide=C2=A0 mechanisms for &quot;enforcement&qu=
ot; of human
                          rights in various legal systems through
                          Internet protocols. As mentioned=C2=A0in the
                          beginning of your document:=C2=A0 <br>
                          &gt; &quot;Human rights threats on the Internet
                          come in a myriad of forms.*=C2=A0**P**rotocols an=
d
                          standards can harm or enable* the right to
                          freedom of=C2=A0expression, right to
                          non-discrimination, right to equal
                          protection,=C2=A0right to participate in cultural
                          life, arts and science, right to=C2=A0freedom of
                          assembly and association, and the right to
                          security.&quot;=C2=A0 <br>
                          &gt; <br>
                          &gt; So we are not in the business of
                          enforcing but providing=C2=A0an enabling
                          environment. Because=C2=A0if we want to help law
                          enforcement and the judicial authorities
                          enforce human rights
                          through=C2=A0Internet=C2=A0protocols we should be=
ar in
                          mind that that they are not always staunch
                          advocates of human rights. So what I assume we
                          are trying to do here is to help Internet
                          protocol not to facilitate harm and &quot;enable&=
quot;
                          human rights.=C2=A0 <br>
                          &gt; <br>
                          <br>
                          The text in the draft seeks to address this
                          risk. I have sought to address all points made
                          in that discussion, and I would not like to
                          re-open that debate. If you feel the text is
                          unbalanced, could you perhaps provide text
                          suggestions? <br>
                          <br>
                          &gt; 2. Attribution, section 3.3.20=C2=A0 of the
                          Guideline, the authors assert that: &quot;However=
,
                          attribution to corporate
                          entities,=C2=A0associations, and/or countries may
                          not directly negatively impact=C2=A0human rights.=
&quot;
                          I think this is not a very=C2=A0well backed up
                          claim. Because in some cases some associations
                          might be political or they might be human
                          rights associations dealing with a
                          dictatorship. Attribution to those
                          associations certainly can impact their human
                          rights negatively. Even when it comes to
                          corporations, some CEOs of digital companies
                          are put in jail because of the materials
                          posted on their websites. I don&#39;t think we ca=
n
                          argue that attribution to corporate entities
                          might not adversely impact human rights. <br>
                          &gt; <br>
                          <br>
                          Again, the keyword in that sentence is &#39;may&#=
39;,
                          so there is no strong claim made. <br>
                          <br>
                          &gt; All in all I think section 3.3.20 does
                          not help Internet Protocols enable human
                          rights and it can be misinterpreted. <br>
                          <br>
                          I think the text in there is not strong and
                          shows different perspectives and potential
                          consequences. But again, happy to receive text
                          suggestions. <br>
                          <br>
                          &gt; <br>
                          &gt; And in my previous email I talked about
                          the problems with threat intelligence agencies
                          and some of their conducts and the use of
                          WHOIS for attribution (which was actually not
                          designed to &quot;identify&quot; actors but
                          unfortunately was used for that) so I will not
                          reiterate here. <br>
                          <br>
                          From exactly that discussion we got the idea
                          to remove individuals, and leave non-natural
                          persons in. <br>
                          <br>
                          Best, <br>
                          <br>
                          Niels <br>
                          <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; <br>
                          &gt; On Sun, Jan 31, 2021 at 5:52 AM Niels ten
                          Oever &lt; <a href=3D"mailto:mail@nielstenoever.n=
et" target=3D"_blank">mail@nielstenoever.net</a>
                          &lt;mailto: <a href=3D"mailto:mail@nielstenoever.=
net" target=3D"_blank">mail@nielstenoever.net</a>&gt;&gt;
                          wrote: <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Hi Farzaneh, <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Thanks a lot for the revi=
ew! <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0On 30-01-2021 23:00, farz=
aneh badii
                          wrote: <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; Hello <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; Adding my comments o=
n this
                          document:=C2=A0 <a href=3D"https://urldefense.com=
/v3/__https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05__;!!KwNVnqR=
v!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmcgv0BsM$" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hr=
pc-guidelines-05</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05__;!!KwNVnqRv!URgHL-MGk=
V0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmcgv0BsM$" rel=3D"norefer=
rer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hrpc-guidelin=
es-05</a>&gt;
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05__;!!KwNVnqRv!URgHL-MGk=
V0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmcgv0BsM$" rel=3D"norefer=
rer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hrpc-guidelin=
es-05</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05__;!!KwNVnqRv!URgHL-MGk=
V0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmcgv0BsM$" rel=3D"norefer=
rer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-hrpc-guidelin=
es-05</a>&gt;
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; 1. One major issue t=
hat I see
                          here and you might be able to easily solve it
                          is that there is no distinction between user
                          facing protocols and other protocols. For
                          example, you ask for accessibility and
                          consideration of culture etc. Are you asking
                          all the protocols to be provided in multiple
                          languages, even those that only=C2=A0developers=
=C2=A0and
                          implementers use and not the actual users? You
                          might want to clarify that.=C2=A0 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0We had a quite extensive =
discussion
                          about this in relation to the presentation by
                          Ramsey Nasr who create Qalb, an Arabic
                          programming language. Programmers are the most
                          frequent &#39;users&#39; of protocols - if we con=
tinue
                          using only latin characters and English
                          documentation in protocols we are likely to
                          reproduce the existing lack of diversity in
                          protocol developers communities. But we can
                          make the text on this clearer as well! <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; 2.section 3.3.1 on c=
onnectivity,
                          you mention that &quot;considering the fact that
                          network quality and conditions vary across
                          geography and time it is also important to
                          design protocols such that they are reliable
                          even on low bandwidth ...&quot;. Then in your
                          example you say: Middleboxes (including
                          NAT).... can create potential for abuse. NAT
                          is a Network Address Translation protocol. I
                          don&#39;t think it has anything to do with
                          bandwidth. In this example you also mention
                          CDNs. Are you suggesting that the developer
                          should not consider &quot;Middleboxes&quot; proto=
cols? I
                          think you need to work on the example of
                          section 3.3.1 some more to make it clearer.=C2=A0=
 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Excellent point - we&#39;=
ll address this
                          in a future version. <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; 3. section 3.3.20 re=
medy and
                          attribution=C2=A0 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; This section worries=
 me. As a=C2=A0
                          scholar I have worked on cyber attribution to
                          some extent and believe=C2=A0in general when we
                          have the right processes in place,=C2=A0attributi=
on
                          is very important and can hold cyber-attackers
                          accountable. I am aware of some of the
                          attribution processes and unfortunately some
                          threat intelligence firms and open source
                          intelligence organizations can violate the
                          privacy of individuals by profiling them.
                          Also, uncontrolled attribution mechanisms can
                          lead to frivolous=C2=A0intellectual property
                          claims. Both some threat intelligence firms
                          and IP firms have used WHOIS extensively in
                          their favor to attribute cybersecurity attacks
                          and bring forward IP claims. WHOIS protocol
                          did not have the intention to actually
                          identify organizations and individuals, but to
                          make them &quot;contactable&quot;.and it was stil=
l used
                          and mined for so many years and those who have
                          abused WHOIS have not been held
                          accountable.When you suggest they consider
                          &quot;attribution&quot; when developing protocols=
 it <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; concerns me because =
it is not
                          enough that you limit attribution to
                          organizations and states. These kinds of
                          attributions can be used against individuals
                          and until we do not have the right preserving
                          processes to put in place for those who want
                          to be in the attribution business, rights of
                          the individual can be at risk. there are very
                          privacy conscious=C2=A0cybersecurity researchers
                          out there but unfortunately that does not
                          ensure a systematic=C2=A0practice of attribution =
in
                          a fair manner. And you mention attribution to
                          associations is fine and may not directly
                          negatively impact human rights. Associations
                          can themselves be at risk of frivolous=C2=A0attac=
ks
                          and frivolous=C2=A0attribution. I am concerned
                          about this paragraph. I think we should have a
                          conversation about it. <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0In the proposed text I tr=
ied to
                          capture the consensus that emerged from the
                          extensive discussion that was had on this
                          list. Do you have concrete suggestions on how
                          to better capture that conensensus? I am
                          afraid we would go back and repeat the same
                          discussion. <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; 4. Nice to see that =
you mention
                          DoH. It&#39;s a great privacy preserving
                          protocol.=C2=A0 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Thanks! <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Niels <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; Farzaneh <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; On Sat, Jan 30, 2021=
 at 10:35 AM
                          Corinne Cath &lt; <a href=3D"mailto:corinnecath@g=
mail.com" target=3D"_blank">corinnecath@gmail.com</a>
                          &lt;mailto: <a href=3D"mailto:corinnecath@gmail.c=
om" target=3D"_blank">corinnecath@gmail.com</a>&gt;
                          &lt;mailto: <a href=3D"mailto:corinnecath@gmail.c=
om" target=3D"_blank">corinnecath@gmail.com</a>
                          &lt;mailto: <a href=3D"mailto:corinnecath@gmail.c=
om" target=3D"_blank">corinnecath@gmail.com</a>&gt;&gt;&gt;
                          wrote: <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0H=
i all, <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0I=
 trust this email finds you
                          well. I did a review of the draft, from my
                          perspective as an academic. Take it as you
                          please. My main concern is that some of the
                          language reads a bit deterministic (as, I know
                          so does RFC 8280). It means that a lot of onus
                          is put on the impact of a protocol, as opposed
                          the role of the individuals that write them.=C2=
=A0
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0I=
 think through out the
                          document, it would be interesting (especially
                          in section 1 through 3.2.5) to see if you can
                          rewrite such that you speak more directly to
                          the protocol developers. I think that section
                          3.3 does that well, in terms of the tone it
                          takes. As it clearly connects the actions of
                          protocol developers to their potential
                          outcomes.=C2=A0 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0H=
ope this is helpful!=C2=A0 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0K=
ind regards,=C2=A0 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0C=
orinne <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0
                          =C2=A0----------------------------- ---- <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0*=
1. Introduction* <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&=
quot;It provides questions
                          engineers should ask <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 themselves when
                          developing or improving protocols if they want
                          to <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 understand their
                          potential human rights impact.&quot; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&=
gt;&gt; maybe if they want
                          to understand potential human rights concerns?
                          Impact seems a little deterministic, as you
                          also mention in the next sentence, I wonder if
                          you can prove such direct impact between
                          protocol development in the IETF and impact on
                          human rights. <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&=
quot;The research establishes <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 that human rights relate
                          to standards and protocols, and offers a <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 common vocabulary of
                          technical concepts that impact human rights
                          and <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 how these technical
                          concepts can be combined to ensure that the <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 Internet remains an
                          enabling environment for human rights.&quot; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&=
gt;&gt; same comment for
                          the word impact, perhaps shape? influence?
                          etc. <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A03.1 &lt; <a href=3D"https://urldefense.com/v3/__https:/=
/tools.ietf.org/html/draft-irtf-hrpc-guidelines-05*section-3.1__;Iw!!KwNVnq=
Rv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmqu9haL4$" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05#section-3.1</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05*section-3.1__;Iw!!KwNV=
nqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmqu9haL4$" =
rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf=
-hrpc-guidelines-05#section-3.1</a>&gt;&gt;.
                          Human rights threats <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
&quot;Protocols and standards
                          can harm or enable the right to freedom of <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 expression, right to
                          non-discrimination, right to equal protection,
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 right to participate in
                          cultural life, arts and science, right to <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0f=
reedom of assembly and
                          association, and the right to security. &quot; <b=
r>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&=
gt;&gt; again,
                          deterministic language. Perhaps soften or add
                          more concrete examples for context, that draw
                          from current IETF discussions/standards. <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A03.3 &lt; <a href=3D"https://urldefense.com/v3/__https:/=
/tools.ietf.org/html/draft-irtf-hrpc-guidelines-05*section-3.3__;Iw!!KwNVnq=
Rv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmYPOkf-A$" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf-h=
rpc-guidelines-05#section-3.3</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05*section-3.3__;Iw!!KwNV=
nqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmYPOkf-A$" =
rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-irtf=
-hrpc-guidelines-05#section-3.3</a>&gt;&gt;.
                          Guidelines for human rights considerations <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0a=
gain, use of the word
                          impact in the introduction. <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0-=
- <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0C=
orinne Cath - Speth <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0P=
h.D. Candidate, Oxford
                          Internet Institute &amp; Alan Turing Institute
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0W=
eb: <a href=3D"https://urldefense.com/v3/__http://www.oii.ox.ac.uk/people/c=
orinne-cath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCEL=
NgpD3MPnzmGORuL8k$" rel=3D"noreferrer" target=3D"_blank">www.oii.ox.ac.uk/p=
eople/corinne-cath</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__http:=
//www.oii.ox.ac.uk/people/corinne-cath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0=
P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmGORuL8k$" rel=3D"noreferrer" target=3D=
"_blank">http://www.oii.ox.ac.uk/people/corinne-cath</a>&gt;
                          &lt; <a href=3D"https://urldefense.com/v3/__http:=
//www.oii.ox.ac.uk/people/corinne-cath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0=
P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmGORuL8k$" rel=3D"noreferrer" target=3D=
"_blank">http://www.oii.ox.ac.uk/people/corinne-cath</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__http:=
//www.oii.ox.ac.uk/people/corinne-cath__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0=
P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmGORuL8k$" rel=3D"noreferrer" target=3D=
"_blank">http://www.oii.ox.ac.uk/people/corinne-cath</a>&gt;&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0E=
mail: <a href=3D"mailto:ccath@turing.ac.uk" target=3D"_blank">ccath@turing.=
ac.uk</a>
                          &lt;mailto: <a href=3D"mailto:ccath@turing.ac.uk"=
 target=3D"_blank">ccath@turing.ac.uk</a>&gt;
                          &lt;mailto: <a href=3D"mailto:ccath@turing.ac.uk"=
 target=3D"_blank">ccath@turing.ac.uk</a>
                          &lt;mailto: <a href=3D"mailto:ccath@turing.ac.uk"=
 target=3D"_blank">ccath@turing.ac.uk</a>&gt;&gt;
                          &amp; <a href=3D"mailto:corinnecath@gmail.com" ta=
rget=3D"_blank">corinnecath@gmail.com</a>
                          &lt;mailto: <a href=3D"mailto:corinnecath@gmail.c=
om" target=3D"_blank">corinnecath@gmail.com</a>&gt;
                          &lt;mailto: <a href=3D"mailto:corinnecath@gmail.c=
om" target=3D"_blank">corinnecath@gmail.com</a>
                          &lt;mailto: <a href=3D"mailto:corinnecath@gmail.c=
om" target=3D"_blank">corinnecath@gmail.com</a>&gt;&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0T=
witter: @C_CS <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0
                          =C2=A0_____________________________ _____________=
_____
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0h=
rpc mailing list <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>
                          &lt;mailto: <a href=3D"mailto:hrpc@irtf.org" targ=
et=3D"_blank">hrpc@irtf.org</a>&gt;
                          &lt;mailto: <a href=3D"mailto:hrpc@irtf.org" targ=
et=3D"_blank">hrpc@irtf.org</a>
                          &lt;mailto: <a href=3D"mailto:hrpc@irtf.org" targ=
et=3D"_blank">hrpc@irtf.org</a>&gt;&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
<a href=3D"https://urldefense.com/v3/__https://www.irtf.org/mailman/listinf=
o/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3=
MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"_blank">https://www.irtf.org/ma=
ilman/listinfo/hrpc</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P=
1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"=
_blank">https://www.irtf.org/mailman/listinfo/hrpc</a>&gt;
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P=
1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"=
_blank">https://www.irtf.org/mailman/listinfo/hrpc</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P=
1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"=
_blank">https://www.irtf.org/mailman/listinfo/hrpc</a>&gt;&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; ____________________=
__________ _________________
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; hrpc mailing list <b=
r>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <a href=3D"mailto:hr=
pc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>
                          &lt;mailto: <a href=3D"mailto:hrpc@irtf.org" targ=
et=3D"_blank">hrpc@irtf.org</a>&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <a href=3D"https://u=
rldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!=
URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=
=3D"noreferrer" target=3D"_blank">https://www.irtf.org/mailman/listinfo/hrp=
c</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P=
1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"=
_blank">https://www.irtf.org/mailman/listinfo/hrpc</a>&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0-- <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Niels ten Oever, PhD <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Postdoctoral Researcher -=
 Media
                          Studies Department - University of Amsterdam <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Postdoctoral Research Fel=
low -
                          Communications Department - Texas A&amp;M
                          University <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Research Fellow - Centre =
for Internet
                          and Human Rights - European University
                          Viadrina <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Associated Scholar - Cent=
ro de
                          Tecnologia e Sociedade - Funda=C3=A7=C3=A3o Get=
=C3=BAlio
                          Vargas <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0W: <a href=3D"https://url=
defense.com/v3/__https://nielstenoever.net__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjS=
ElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmZWdheys$" rel=3D"noreferrer" targe=
t=3D"_blank">https://nielstenoever.net</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://nielstenoever.net__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXj=
mpA9gGCELNgpD3MPnzmZWdheys$" rel=3D"noreferrer" target=3D"_blank">https://n=
ielstenoever.net</a>&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0E: <a href=3D"mailto:mail=
@nielstenoever.net" target=3D"_blank">mail@nielstenoever.net</a>
                          &lt;mailto: <a href=3D"mailto:mail@nielstenoever.=
net" target=3D"_blank">mail@nielstenoever.net</a>&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0T: @nielstenoever <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0P/S/WA: +31629051853 <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0PGP: 2458 0B70 5C4A FD8A =
9488 643A
                          0ED8 3F3A 468A C8B3 <br>
                          &gt; <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0Read my dissertation &#39=
;Wired Norms&#39;
                          here: <a href=3D"https://urldefense.com/v3/__http=
s://pure.uva.nl/ws/files/50781961/Thesis.pdf__;!!KwNVnqRv!URgHL-MGkV0X0jyCj=
jSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmJOAMClE$" rel=3D"noreferrer" tar=
get=3D"_blank">https://pure.uva.nl/ws/files/50781961/Thesis.pdf</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://pure.uva.nl/ws/files/50781961/Thesis.pdf__;!!KwNVnqRv!URgHL-MGkV0X0jyCjj=
SElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmJOAMClE$" rel=3D"noreferrer" targ=
et=3D"_blank">https://pure.uva.nl/ws/files/50781961/Thesis.pdf</a>&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0_________________________=
____ __________________
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0hrpc mailing list <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc@i=
rtf.org" target=3D"_blank">hrpc@irtf.org</a>
                          &lt;mailto: <a href=3D"mailto:hrpc@irtf.org" targ=
et=3D"_blank">hrpc@irtf.org</a>&gt;
                          <br>
                          &gt;=C2=A0 =C2=A0 =C2=A0 <a href=3D"https://urlde=
fense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgH=
L-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=3D"no=
referrer" target=3D"_blank">https://www.irtf.org/mailman/listinfo/hrpc</a>
                          &lt; <a href=3D"https://urldefense.com/v3/__https=
://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P=
1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"=
_blank">https://www.irtf.org/mailman/listinfo/hrpc</a>&gt;
                          <br>
                          &gt; <br>
                          <br>
                          -- <br>
                          Niels ten Oever, PhD <br>
                          Postdoctoral Researcher - Media Studies
                          Department - University of Amsterdam <br>
                          Postdoctoral Research Fellow - Communications
                          Department - Texas A&amp;M University <br>
                          Research Fellow - Centre for Internet and
                          Human Rights - European University Viadrina <br>
                          Associated Scholar - Centro de Tecnologia e
                          Sociedade - Funda=C3=A7=C3=A3o Get=C3=BAlio Varga=
s <br>
                          <br>
                          W: <a href=3D"https://urldefense.com/v3/__https:/=
/nielstenoever.net__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmp=
A9gGCELNgpD3MPnzmZWdheys$" rel=3D"noreferrer" target=3D"_blank">https://nie=
lstenoever.net</a>
                          <br>
                          E: <a href=3D"mailto:mail@nielstenoever.net" targ=
et=3D"_blank">mail@nielstenoever.net</a>
                          <br>
                          T: @nielstenoever <br>
                          P/S/WA: +31629051853 <br>
                          PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A
                          468A C8B3 <br>
                          <br>
                          Read my dissertation &#39;Wired Norms&#39; here: =
<a href=3D"https://urldefense.com/v3/__https://pure.uva.nl/ws/files/5078196=
1/Thesis.pdf__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCE=
LNgpD3MPnzmJOAMClE$" rel=3D"noreferrer" target=3D"_blank">https://pure.uva.=
nl/ws/files/50781961/Thesis.pdf</a>
                          <br>
                        </blockquote>
                      </div>
                    </blockquote>
                  </div>
                </div>
              </blockquote>
            </div>
          </div>
          <br>
          <br>
          -- <br>
          <div dir=3D"ltr">
            <div> <font face=3D"verdana, sans-serif">Farzaneh </font> </div=
>
          </div>
          <br>
        </blockquote>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
hrpc mailing list
<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a>
<a href=3D"https://urldefense.com/v3/__https://www.irtf.org/mailman/listinf=
o/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3=
MPnzmNdA9cSg$" target=3D"_blank">https://www.irtf.org/mailman/listinfo/hrpc=
</a>
</pre>
    </blockquote>
  <div id=3D"gmail-m_-3487738066469627961DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FD=
F2"><br> <table style=3D"border-top:1px solid rgb(211,212,222)">
	<tbody><tr>
      <td style=3D"width:55px;padding-top:18px"><a href=3D"https://urldefen=
se.com/v3/__https://www.avast.com/sig-email?utm_medium=3Demail&amp;utm_sour=
ce=3Dlink&amp;utm_campaign=3Dsig-email&amp;utm_content=3Demailclient__;!!Kw=
NVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmdWjSL3Q$=
" target=3D"_blank"><img src=3D"https://ipmcdn.avast.com/images/icons/icon-=
envelope-tick-round-orange-animated-no-repeat-v1.gif" alt=3D"" width=3D"46"=
 height=3D"29" style=3D"width: 46px; height: 29px;"></a></td>
		<td style=3D"width:470px;padding-top:17px;color:rgb(65,66,78);font-size:1=
3px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Garanti sans v=
irus. <a href=3D"https://urldefense.com/v3/__https://www.avast.com/sig-emai=
l?utm_medium=3Demail&amp;utm_source=3Dlink&amp;utm_campaign=3Dsig-email&amp=
;utm_content=3Demailclient__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOg=
EgyZXjmpA9gGCELNgpD3MPnzmdWjSL3Q$" style=3D"color:rgb(68,83,234)" target=3D=
"_blank">www.avast.com</a> 		</td>
	</tr>
</tbody></table>
<a href=3D"#m_-3487738066469627961_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" wi=
dth=3D"1" height=3D"1"> </a></div></div>

_______________________________________________<br>
hrpc mailing list<br>
<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a><br>
<a href=3D"https://urldefense.com/v3/__https://www.irtf.org/mailman/listinf=
o/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0jyCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3=
MPnzmNdA9cSg$" rel=3D"noreferrer" target=3D"_blank">https://urldefense.com/=
v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!URgHL-MGkV0X0j=
yCjjSElE0P1rq-lw91NOgEgyZXjmpA9gGCELNgpD3MPnzmNdA9cSg$</a> <br>
</blockquote></div>

--000000000000a86c8b05ba580df9--


From nobody Tue Feb  2 05:53:41 2021
Return-Path: <vittorio.bertola@open-xchange.com>
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 C6D993A1B0B for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 05:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 (2048-bit key) header.d=open-xchange.com
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 s_e0N_RQDCK1 for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 05:53:37 -0800 (PST)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 D01593A1B06 for <hrpc@irtf.org>; Tue,  2 Feb 2021 05:53:35 -0800 (PST)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.30.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPSA id D3B156A279; Tue,  2 Feb 2021 14:53:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1612274013; bh=Kyx9G12iMyPB1DVl1lLUIhOhShs4KEA0Tmy/TipU0m8=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=86Q2c2h2GuxzCIAWITakTLKhDS0r0kQ4xrOd3uXdc1b3HgB8jvm3uoJwzknxxCVbI jduIMuS8WZiJF2aK/tcJXdThIwdxswSlLX8GkH5GXfJfBE9MPpegZx0ssxa7hbhb8S 8til7J4RLw/9+EtbuykW7/LTroPcD7nJI4cjJ8xYamjOp0oldZbZ7hW5Ut5B/an+TE oT6N/YD5tq3iitwRTYjrtH3+aL7Vy0fIgTSEDCV5lG3LmbGZ8qiWzNcTp31MTXdyBu mmu54BbhY1efDi4BIg9cbg7IuGA4IQccUeSW8gtRJ2t+8OO03Tvx3sE/cNsO1xUF27 FtXtHeuqi4QLA==
Received: from appsuite-dev-gw1.open-xchange.com ([10.20.30.221]) by imap.open-xchange.com with ESMTPSA id hRWhM11ZGWAmWwAA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>); Tue, 02 Feb 2021 14:53:33 +0100
Date: Tue, 2 Feb 2021 14:53:33 +0100 (CET)
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Hrpc <hrpc@irtf.org>
Message-ID: <183095035.9756.1612274013800@appsuite-dev-gw1.open-xchange.com>
In-Reply-To: <20210201172346.GA24309@sources.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com> <20210201172346.GA24309@sources.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.5-Rev3
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/1vzaAGlkLsntZTEI__4S_LaT0WI>
Subject: Re: [hrpc] [EXT] Re:  Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 13:53:39 -0000

> Il 01/02/2021 18:23 Stephane Bortzmeyer <bortzmeyer@nic.fr> ha scritto:
> 
> So, the issue is not really about the proper balance between, say,
> freedom of speech and censorship of nazi/racist/sectarian speech. It
> is that we are a small force, developing techniques that fight against
> the interests of giants. We should not refrain ourselves to develop
> anti-censorship techniques because we (and the ordinary users) are
> already at a disadvantage.

I don't want to have the whole discussion again - I stated my concerns on the current draft and that's it - but I do want to say something on this narrative.

The above was perhaps true 30 years ago. Today, the IETF is the standardization arm of one of the biggest global industries, led by the five most valuable listed companies of the world, which is under antitrust investigation in almost every corner of the planet and which is strong enough to censor the sitting U.S. President if so decides. There is at least the same potential for human rights violations in what the Internet does than in what others do to the Internet.

Basically, the Internet used to be the new kid on the block - radical, innovative, brilliant, out of control and disruptive. But then, there is now an expectation that the Internet turns into a boring, well behaved adult.

-- 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy


From nobody Tue Feb  2 06:07:04 2021
Return-Path: <mellon@fugue.com>
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 E05863A1B1E for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 06:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 PULy0rxM-yDu for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 06:07:02 -0800 (PST)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (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 4623E3A1B1F for <hrpc@irtf.org>; Tue,  2 Feb 2021 06:07:01 -0800 (PST)
Received: by mail-qv1-xf35.google.com with SMTP id l11so9906113qvt.1 for <hrpc@irtf.org>; Tue, 02 Feb 2021 06:07:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=XFljG8jyVAeQa0nNP+yNg5NsSdRpl7VkyXKxTRb9qTU=; b=OIFvqymPaxQoyCkuwvxnUFHdQcWpOL0Eq+ZnV0CWeUqhxpJjdNDwN8+uusugXzOZw1 DKLVH5w94Zpd42yZqe6aPW3JvoFeLyexZTJQxErMi83vjCfGXBRm2ebWe7+BnIvpB6Uw 2nvPO+hyVUueM8vCOTytWB0JgUaENzeIdD3Ltz7dYSOV53IAjqy7rPH7Of3lfWM4+x4O wT9r4JAwupg9uCNLP4/DfCu98X3OpAma8DIAX5H+5S/JRsk51YMc0zq+M8DuGIP9fUyX 6hrmFfP6gAQgL9Z2PiLEDUC69PCcpmpQNFf2DNwq3iy8kZLVJdzkf1ixwclC4b54kV7/ hUaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=XFljG8jyVAeQa0nNP+yNg5NsSdRpl7VkyXKxTRb9qTU=; b=nr8w6aMpdTs+D2cXrcHhWLDb9yee8EP6r1dQdttC+RzJYNpbqHgLcGtTC1Qv/KOhqX Tk96McoSYPXve6h0K4nGPTexCLYwIiBvprHGCO8A0KFobJNuWzsEg4nPYX8a/ItZHEXC XtTu1LqCUY842qL7TFcKGYl92Ks0Pf/j35GUAtyvj2xC6wfE4WKdWD1GbD21vIc3/rDk 077qwaU8DQ999CvYYlUBzMdj5EY+KyuisMx2FUSR4pJZv9tgLuatHX2rl4//nIQKJAFq 0mXY0zj81T8kbOXRI7B4ONInBynAuZc+XizezbN59nGba3BweHqPYD1W8tFmI2/NtRIw /F5Q==
X-Gm-Message-State: AOAM532iU9KmVFoOHiwlwYU/zyubK37uybzVbz3J0V7b0QVn7go0LUPg KvHT9ukMxjwRaFfS1cw9H/yPCQ==
X-Google-Smtp-Source: ABdhPJx2drgdTV9YI4p4kSC2DEpH+LxTXH+kpbH9SK2jEJJBMa9A6MYSRJn9qhJa4VWEAdRpMAHc9w==
X-Received: by 2002:a0c:aed0:: with SMTP id n16mr20256931qvd.14.1612274820615;  Tue, 02 Feb 2021 06:07:00 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id k132sm16799182qke.77.2021.02.02.06.06.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Feb 2021 06:07:00 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_99675A4A-7DA6-4B67-8A6A-D81B29ABFE49"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Ted Lemon <mellon@fugue.com>
X-Priority: 3
In-Reply-To: <183095035.9756.1612274013800@appsuite-dev-gw1.open-xchange.com>
Date: Tue, 2 Feb 2021 09:06:58 -0500
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Hrpc <hrpc@irtf.org>
Message-Id: <0367CD3C-A072-4313-BA05-3510B9862662@fugue.com>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com> <20210201172346.GA24309@sources.org> <183095035.9756.1612274013800@appsuite-dev-gw1.open-xchange.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/rTYQv1WZbpC-NSSst8nFnXcBL6k>
Subject: Re: [hrpc] [EXT] Re:  Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 14:07:04 -0000

--Apple-Mail=_99675A4A-7DA6-4B67-8A6A-D81B29ABFE49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 2, 2021, at 8:53 AM, Vittorio Bertola =
<vittorio.bertola=3D40open-xchange.com@dmarc.ietf.org> wrote:
> The above was perhaps true 30 years ago. Today, the IETF is the =
standardization arm of one of the biggest global industries, led by the =
five most valuable listed companies of the world, which is under =
antitrust investigation in almost every corner of the planet and which =
is strong enough to censor the sitting U.S. President if so decides. =
There is at least the same potential for human rights violations in what =
the Internet does than in what others do to the Internet.

This is a nice little lark, Vittorio, but in fact we were never powerful =
enough to censor the U.S. president. There are people who are that =
powerful, perhaps. Perhaps some of us work for those people, at some =
deep remove. But we are not they.

Instead, what we have actually seen is that the powerful organization =
some of us might have wished would censor the U.S. president did not. =
The one organization that did finally censor him while he was still =
president only did so after he had done something so egregious that it =
seemed like a safe move.

What I=E2=80=99ve seen of this effort is that the intention seems more =
aimed at preventing people from being silenced than it is at giving =
people the tools they need to avoid hearing people whose speech toward =
them is unwelcome (online harassment, of which Trump is simply the most =
formerly powerful example). If there is anything missing from this =
effort, it is that: that I can=E2=80=99t just say =E2=80=9Cno, I won=E2=80=
=99t accept email from strangers,=E2=80=9D for example.

This is a hard problem, and one that we at the IETF are ill-equipped to =
address, since most unwelcome speech happens above the protocol level.


--Apple-Mail=_99675A4A-7DA6-4B67-8A6A-D81B29ABFE49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Feb 2, 2021, at 8:53 AM, Vittorio Bertola &lt;<a =
href=3D"mailto:vittorio.bertola=3D40open-xchange.com@dmarc.ietf.org" =
class=3D"">vittorio.bertola=3D40open-xchange.com@dmarc.ietf.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">The above was =
perhaps true 30 years ago. Today, the IETF is the standardization arm of =
one of the biggest global industries, led by the five most valuable =
listed companies of the world, which is under antitrust investigation in =
almost every corner of the planet and which is strong enough to censor =
the sitting U.S. President if so decides. There is at least the same =
potential for human rights violations in what the Internet does than in =
what others do to the Internet.</span><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">This is a nice little lark, Vittorio, but in =
fact we were never powerful enough to censor the U.S. president. There =
are people who are that powerful, perhaps. Perhaps some of us work for =
those people, at some deep remove. But we are not they.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Instead, what we have =
actually seen is that the powerful organization some of us might have =
wished would censor the U.S. president did not. The one organization =
that did finally censor him while he was still president only did so =
after he had done something so egregious that it seemed like a safe =
move.</div><div class=3D""><br class=3D""></div><div class=3D"">What =
I=E2=80=99ve seen of this effort is that the intention seems more aimed =
at preventing people from being silenced than it is at giving people the =
tools they need to avoid hearing people whose speech toward them is =
unwelcome (online harassment, of which Trump is simply the most formerly =
powerful example). If there is anything missing from this effort, it is =
that: that I can=E2=80=99t just say =E2=80=9Cno, I won=E2=80=99t accept =
email from strangers,=E2=80=9D for example.</div><div class=3D""><br =
class=3D""></div><div class=3D"">This is a hard problem, and one that we =
at the IETF are ill-equipped to address, since most unwelcome speech =
happens above the protocol level.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_99675A4A-7DA6-4B67-8A6A-D81B29ABFE49--


From nobody Tue Feb  2 06:07:16 2021
Return-Path: <stephen.farrell@cs.tcd.ie>
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 8655F3A1B2A for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 06:07:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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=cs.tcd.ie
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 rHtcPqdcNbq2 for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 06:07:13 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3140C3A1B59 for <hrpc@irtf.org>; Tue,  2 Feb 2021 06:07:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6B967BE2E; Tue,  2 Feb 2021 14:07:09 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4iQazbTPNMk; Tue,  2 Feb 2021 14:07:04 +0000 (GMT)
Received: from [10.244.2.242] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D8A6BBE1C; Tue,  2 Feb 2021 14:07:03 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1612274823; bh=pE3uWTXr/ndRJkC9grlf+n/g0FM265CPpuB/8//Qw5g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=h1+SHwHXNM+NyRhnN0eMWj3udIDJCViRlfWNTbHKjx0cwZExnjwWZakq649OmNHsq Jaa8N4lsJrG7/b88sSrELMzd85H5/V7Fr2IRUv+q7N7ba4+J/f0wR0pHEimF+UgSUn gmCEVSnqZMKaGlpaovPG7vEQnCCrfHWfGPSwYPEM=
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Hrpc <hrpc@irtf.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com> <20210201172346.GA24309@sources.org> <183095035.9756.1612274013800@appsuite-dev-gw1.open-xchange.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <50a633c0-6182-6cb9-0568-adadf1884025@cs.tcd.ie>
Date: Tue, 2 Feb 2021 14:07:03 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <183095035.9756.1612274013800@appsuite-dev-gw1.open-xchange.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CdoNiQqI6aRzheI71OdA0NMmtzi19TTJ1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/YSWyBHvzg6Vl95FO4gNK2rdeFVM>
Subject: Re: [hrpc] [EXT] Re: Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 14:07:15 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CdoNiQqI6aRzheI71OdA0NMmtzi19TTJ1
Content-Type: multipart/mixed; boundary="VIjcCXprWATSCAT1mY2TYFUZrP2EVM5cL";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>,
 Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Hrpc <hrpc@irtf.org>
Message-ID: <50a633c0-6182-6cb9-0568-adadf1884025@cs.tcd.ie>
Subject: Re: [hrpc] [EXT] Re: Comment on draft-guidelines for RG Last Call
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com>
 <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com>
 <1743678261.5108.1612173828380@appsuite-dev-gw1.open-xchange.com>
 <20210201172346.GA24309@sources.org>
 <183095035.9756.1612274013800@appsuite-dev-gw1.open-xchange.com>
In-Reply-To: <183095035.9756.1612274013800@appsuite-dev-gw1.open-xchange.com>

--VIjcCXprWATSCAT1mY2TYFUZrP2EVM5cL
Content-Type: multipart/mixed;
 boundary="------------B218832335451491CA8494A4"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------B218832335451491CA8494A4
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable


Hiya,

On 02/02/2021 13:53, Vittorio Bertola wrote:
> Today, the IETF is the standardization arm of one of the biggest
> global industries,

Stephane will correct me if needed, but I thought it was
pretty clear that the "we" to whom Stephane referred did
not really include those IT behemoth companies (though I
think it probably does include some but not all of their
employees). FWIW, I agree with him.

I'm also sad that you seem to think that the IETF is only
the plaything of large companies, and I think you're wrong
there. There's more to it than that.

Cheers,
S.

--------------B218832335451491CA8494A4
Content-Type: application/pgp-keys;
 name="OpenPGP_0x5AB2FAF17B172BEA.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="OpenPGP_0x5AB2FAF17B172BEA.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----

xsFNBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh5=
Cg8
gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+QtaFq=
978
CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKrEMjmL5VGu=
D/Q
9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZUbUv0Q+DnQAB/4=
tNn
cejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqOVz+7L+WiVfxLbeVqB=
wV+
4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJgb097ZaNyuY1ETghVB5Uir=
1GC
YChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k4LyM2lp5FmBKjG7cGcpBGmWav=
ACY
Ea7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK7uB7E7HlVE1IM1zNkVTYYGkKreU8D=
VQu
8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5XiHzFPJleXc0ksb9SkJokAfwTSZzTxeQPER=
8la
5lsEEPbU/cDTcwARAQABzSFTdGVwaGVuIEZhcnJlbGwgPHN0ZXBoZW5AamVsbC5pZT7CwX0EE=
wEI
ACcFAlo9UYwCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQWrL68XsXK+qGC=
xAA
pYHWYgGOIL3G6/OpkejdAkQoCVQAK8LJUSf6vzwost4iVfxIKcKW/3RqKNKkrRl8beJ7j1CWX=
Az9
+VXAOsE9+zNxXIDgGA7HlvJnhffl+qwibVgiHgUcJFhCSbBrsjC+1uULaTU8zYEyET//GOGPL=
F+X
+degkE/sesh4zcEAjF7fGPnlncdCCH3tvPZZsdTcjwOCRVonKsDgQzBTCMz/RPBfEFX44HZx4=
g1U
QAcCA4xlucY8QkJEyCrSNGpGnvGK8DcGSmnstl1/a9fnlhpdFxieX3oY2phJ1WKkYTn6Advre=
k3U
P71CKxpgtPmkd3iUUz/VZa0Cv6YxQXskspRDVEvdCMYSQBtJPQ4y2+5UxVR9GIQXenwYp9AP2=
niv
Voh+ITsDWWeWnnvYMq07rSDjq0nGdj41MJkNX+Yb2PXVyXItcj5ybE3T2+y3pSBGFEZYJGuaL=
4Nw
tBJFMOdOtBmUOPbetS2971EL3Izxb7ibOZWDwexv+8R6SWYfP1wVN3p46RyBQuXqJV8ccE11m=
6vt
ZTGSYgnLUUFZMRQYH+0hwuYe0T3AA18xDdSYsa8vovCCd3l5S4UNzIM2PMChqGrEzKapUpZg7=
+8A
CcxRU3b9Ihd7WYjJ+pQPCoWYKozvtEvenbNpE/govO/ED3B14e+R2yevRPjRrsN7PJzSf15fQ=
LvC
wFwEEAEIAAYFAlo9UqAACgkQLzyHNoBfjaLrSwf+MIHbFRQ4O5cmLYR5sIByWelN3SuRN/gW8=
rpK
o9OkCz6An8uV/iCXy5tNMLzzi0BFl8f22DwBcC5qy9qnlIAdogWam1qWoTAoAD8veEqmuKhYr=
qJs
CcAyNrKYmK0hP3rpHxx1LySDmKYXmw/8qtBXKHTouMm+5tSsznhykRMTAAr2p7PSaHgo+hIVa=
W/r
KSspHjDhhZS+G9mtOZad1IH29M6G1Q1NCO0Ywe8krKLQIAQlFxtgvOqpPOZNzeKBa/+KbE8TG=
gMW
rkOhC8OeEM5PVzdDhlhD9kPzB/pCKDF5DofJ/ZRqnDpbKPQ0bsW38AOig3kOc0A27awiBEw3u=
rqR
1cLBcwQQAQgAHRYhBH4XCgRchM9GDit5oBDvedn9g1MSBQJbtyScAAoJEBDvedn9g1MSI/oP/=
0A9
J9nrnBMqZpm857lfYWw+rshLK+tyeP4OQeOqnDFvs9jePpcyJLG3DF2r6VbVKPQq+AE6Uf5hc=
JBD
EN6BjEhRPSbLcqG3A1cz/nNwm8rPmNp+oKhmaBBQGxwciMLmzgynsDydnjPpMyEs04zvsbsl4=
vrp
2095o105l8KcrrxQrioFjbwveGwHQK9bxJKhx9D+gIk+MouBur45UDKTZkMZrr9FGrtkyXCGA=
xvK
dcNC5Oa8z9sj1rcUJfG/OpVAMWhArdlZbFUQyoX6pU2Zb1CR2qpWAVerGSfBhmfCyStjARqaK=
xlf
tjO+Bj3Jj73Cr5eqej3qB5+V4BCsPjr4RLvVbYUCPsRdxWc+nBLlfVYkRURu21g1hFm5KFPjg=
Uky
o1s4vjUOY8DyI+xLGF7f/IhUBG6l+Vswhpwu7ydalZkeFiPx5xna5NfbEYxvsIf71DvipGvIO=
aHv
X4egWoFgm8n/9c3rcMxJtpwHPSsUt5dgLsyu6VE0IbvOAc3dN7CWJ355DVFJq9Zg2YVf0izSp=
yyz
JeGsgkfjW6xpmdvZxuT2UcN4BTcm6vYqueASGrb3lfhzC5gpeVsc/MoSjTS65vNWbpzONZWMZ=
uLE
FraxWJzC0JrDK3NCd0VN3kstqGkVbUIiYOnUm8Vu4zoVMLlGWzHLIGoPRG2nRezn1YyNfyb5w=
sDc
BBABCgAGBQJbxcflAAoJEGo7ETk8pK1gE7QL/ApC5P68W5DrI1787WJVZv1u4t/g39vTr7Xer=
3UM
TVQg10vpa7pmqOGhjIDzDMg3Pe3K3M7fVzfAlUA1qw6ne4RCueVoRKpubeF4AlYbMr0K6hNCP=
jt5
uAxmbBVuejKTc6pru5rv5gKL0nDbr+Snft5xt7juBLSSimw0/41sZnkjCxo9rF/RA/v6+uWyK=
171
RKmsEYu8fFtw1eqUNt/Xj792TUixE3pxXheNtQtZGk/9P3W83ChhG4Fh5EQsn0pIh9wZIAbMR=
Lpg
RKyW87fWHZC8/YH8h7afarvn9Thl5pFUldCe22mNJj6KLChn2aEHQd+PdY1GBpZEcmNEUPuov=
wza
tM0h64hCzTm41eDqRfihZVBT7TbfXQnv8rywa42Mk756RGzzEZcQEhwQXZcMQUfxIQQ2VyJo0=
zG3
6VdZTQF7TF/4Lz7/3cJ56jOIm+dwPXtu+C2wAQuD4USOLt4JWPYpqzDfHYJIND/497P9Z9SuQ=
eah
r2ez3DRBg3qsHEjBV80yU3RlcGhlbiBGYXJyZWxsICgyMDE3KSA8c3RlcGhlbi5mYXJyZWxsQ=
GNz
LnRjZC5pZT7CwYAEEwEIACoCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AFAlo+o=
3cC
GQEACgkQWrL68XsXK+qO0A//ZsfQzyXrZlu/eEV5jU620yeOM3P7SW3C3UQYdCgZ/TlvxGgKo=
w5o
DSXgjMiUyq9csGqbPBxlDYSxFZHNeDVKYIuP2ZK24tw5k6duTh4+sFwUualTMlcp0zBCIzn3h=
Rcs
RvuPKHfl5+6oOi0+xqx3jX/s/69L/fvHmdSKet5LIUAxoYaZkTCruFrPWb01tgAl5JExWkhmC=
Y98
iD+EeiIMAWBjMw1xV+p0uCwNbN6XDzcToK7wsm+tAIiWUy3DpP60a6WbVwdV0HNt2WZq5U5Jd=
h2k
4S+sN2CnYk4tTW7jHjsWarV3FLISCOObADZuB7ljU4kYfdwZ+WzenXY4LGlxGQSlAblGjwZe4=
EIk
CXAJUtzJhoFUuGaF/PlWjxqV3UFRcgTERZTijguVyREre8GNERNgvDxZvuXssEjvz9X5JfcIZ=
DIJ
pdzhLiEIj9noUbfx1SzB5KDPQj0O7elMHa1671/rwWcpGr/MfVPTOik4H7F8rcVJelceZTzC4=
tvy
a7M+jM4fyFWWt8Y4atTixUiP7U9o4uBZCQ0GzvsmFA4XLqn2pA5rVizMXnGbGOjufAP/efEJ4=
ul3
qvjYe8ye8DXEDjKAxo/tuHYtk19XCi83QzFhWls5TT+XQeVTMEvVqo9Wek8yoxo67qvLKKqIc=
G9g
ivQd8MxYNAbNYgSPtkbhZ8TCwFwEEAEIAAYFAlo9UqAACgkQLzyHNoBfjaLzHAgAlWT6NXEGt=
w/r
1miKNGcopzvzILQ9oB8rKI9U9EL6tOf/y2V5oYee/GyQDb3ZdoPxxYYcJf+RyiH1nMoqUIZiZ=
Jaf
3bJXinDZ5+AdfE++UR2NBvqaNyC6u3r24jo1B/sagKbYtWgsYtRqHLD4IWi37MZrVyjBuF7u1=
4Q0
7+uhjq6mX2O/tHpCYw/Q82tbeTRPyUf1WQOAfD1kfBpW9PvAva5Iw9FWeXpCXRzwxnCZhYfGf=
qtu
Sw6CPBYLdbikqML6FZ7EDuTBb/8um1wK7Y9bgeIQC+CYjhYB5RXa1tDJRab2Js4luCvSR0w/C=
gHw
26293tlve2Q6UTrmHxP5U22DlsLBfQQTAQgAJwUCWj1QMgIbAwUJCZQmAAULCQgHAgYVCAkKC=
wIE
FgIDAQIeAQIXgAAKCRBasvrxexcr6tJpD/4rrILH+meP07vrx8wW5eYuqCiPGYnh/CXxIF8eL=
rfb
e5d4QRgtq+w6UeQPMyzKRIRiCoBXB2oJLBZHyxBPxZlg33dTMrEGn8QWKx2iNuz9rZMXyOSWF=
etu
O01d/aUPd5BnbLbIyK5of8xCQlXM6KH8bc+9gQ7edR9mfLTdvBf2FR522hg8BRBM1imKc3vO8=
v39
+qIHHRjuiwxBBCAOhHtHRsZXripS0uFA07dM46Oi/E8osjx6fQt/lH5z/PN+2adxYSrLSAXfr=
1oD
3RxYNhuWgyGFL64/VCQb1YGjf0Z5MBPnWm9jgUoOY5K9eNSS0L83WeJjlF5+Q/WOgB+rb49Pr=
m2D
Feo9+S9f2V53Llz1WIspXJg6f+n9lmHE94MfQj1GAHCzI0FeL19lvM+LhD8jJSCbhrC3+yoby=
y/A
UOs5Z3E+njjX1FF/VCVAs6iOa6i+XG+Y1hh3ir2y1kckJ5auT10MSU8GEZu9ayU4M3o3N9yxO=
jao
P0NuQ4MMLL/n/u4u94AeZaHPNBXn/hVfVRRmpRXtGKvJtFAEppGEYezB+bLKIm6XlpPkhnwYz=
leL
Z7AMEco2C6QM8QPB3g3JpS3sqRhA5rEP4lL16BmijmF+CHoPE/zwgKZbKpyVDqvIW5IDgvfIC=
2X4
pbZDRvGIUKaGSB4+ksZgUUnNyvfQr2p7jsLBcwQQAQgAHRYhBH4XCgRchM9GDit5oBDvedn9g=
1MS
BQJbtySbAAoJEBDvedn9g1MSeKkQAJm44jt1kwHgQgeDBKdjdvl0AjE0xVEQxriZ6lP/l//34=
YT0
auFfzsYIrChSpQXAEtobBAr4Ohw1Us+BZe+H5P8vm6LRuPwozC3SjwfX4Iec8+9ot6tIVg4sb=
edD
Sgb/CCFVjsmIGcQ1P73JLJTBJ6mxYCV/gn3QC6bwDOFo7kD9FDHCjRN8XfhHQ4Q9cYyt06uF3=
1qG
/aumgWYC9geCGgAwiHgwxNYb9GoJ0iZjCROwbYvLTcQgsVUW2bTmsVR13UVKDsdl02sRV7qcV=
YW6
R0a3Ra8KudX+nt25H5DRGd382KZ5W8pydsy/viTvD9z6v0ulChBYxAedIvGIClrhbxlLEPmIg=
4Im
VOLGqsUgVm32J95WOjEkk4PEZ12xSDBtwhSJqmJNboWlfmw43KdIbY8zNhffIO3N6O7FsdGxm=
qyH
eLoTpqY+ySVUPpbuyW8ujnI/J//+6hdTZ9dQsEJQlWngKuWOQ5ma58MPSN88zllsqhZAFQjNx=
qnk
SzL6ZQ+v/jvuRRe16B80AeO55DsmbWsMv/YLLD1mSi7+Khy2EtMBhgojWwrGMvdLN6X3mnzNJ=
Esc
YyLxM9tSk+iySP2sLthK0BVgpAzBSdaf/ezIz60P+neHDzteNFf8Mn7lmgYk1amvZoJ29s5+n=
2Hw
xyRL5dVMyMdyQmntubbctfqrZ0tIwsDcBBABCgAGBQJbxcflAAoJEGo7ETk8pK1gnCYMAJY4F=
eIY
jlIXGghFWzsB4fYwK1+iaFpU3fSto5qcrqVtVPjXpwqczqBWeXGyQxiB0kan4OVAXydIeaP8E=
AuF
CA7paP3s9STLJBO3KurkwyRkPW5zo0X7xVqaVToRsX2Ul98KVJoHYQD1KdezEtwlvpNwiiBr4=
2AY
R751Vm6JBVAbQXuFpB3c8bUV0OkkRxNFtL8/2PieHar58n5dntGkbPlPkztahsFqktgacIgXH=
X5v
aT+7YeeZ1DWLOYjGO0wNhkOSeroCmxwJUikU7joBp823L7r5KfpqWTPpSCzVstQKZUGmmoE1q=
Csw
Y/Ud5wvp9SccpIILkRXj0rZRtfnE5MpL3hjmtNzfDd9qIsJtBJlSB2hZwAsVm1l+EWN9hG3tq=
yA4
3niUMy2n6q690of3berSiQ+kvY/aC9Hx8I+bKzOV9/J2VUTqfaPZa4Uy2rVX5Q2p69n/PMj7m=
Eer
0rCL3j9V16J9c+s0BSkXoKdtYdB0TWVhBgUybd9qtYcwHWvhP80uU3RlcGhlbiBGYXJyZWxsI=
Dxz
dGVwaGVuQHRvbGVyYW50bmV0d29ya3MuY29tPsLBfQQTAQgAJwUCWj1RWgIbAwUJCZQmAAULC=
QgH
AgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBasvrxexcr6jscEADEcB0WQEZn2AkrzDs1RhL0Lp6cZ=
i0B
igofkbcGfdhJyMSs19C0dhvncrAFClVI6/Udw3yFtDyYtOCf2W3M3A1K6/RfEizCLzTsdFIhn=
i9g
OJLlUpXViQtgrlstjk7hqVV3Ooz4BlCqS4cG7rfqf4LQQPpTAuFUEV9I28FBUB2irqC+v4gTy=
sIg
pMw0bA1yBU9sX5jE/tRkzqnuzZrkwiobDtRFJ9qp+7O2JtcY4EsVtLAsaodJKc5cF8R4OvB1n=
66v
xxcgg9Eh4JNWZ47xsaCmAGo1Bcb2jIY35OtgAL7gCGLRSMKTtAaPy1/fEgIqhCljJ9x40Fkn/=
3r2
BX21WC9HFSPFTBz2RluLRzxdgxOrkYK8EiHUPoE5b1AEzZKw2AbeXfr57f5zYsN3IqfbQLUjM=
YtU
N1wK3Pjb+idD972wyXMWt8uOzlI7b9Ocu+nYm2whBfJv9Pmp3QYTmPz+LB9lH65VNVUSxSXVr=
5iW
XO3qx1HtEiGEqkporMQCTh3T5Ud3PvMSRBFFKNs9WhJ/Lxz+SV30WLwG6dr5mQqlzAhb4Phc/=
zek
ZyXRdS/oDKrBLUucS36O//49JeyRi1QvOfxnfmIqRIAf/k3PoYJmTo5E82//r5Qj3YGlRu78b=
a0H
Arxs+ACD6AnEHHcbswpbtVEKYzlSu0Ar0Dc7vRWM/IyQdMLAXAQQAQgABgUCWj1SoAAKCRAvP=
Ic2
gF+NosIsB/9f/29FNla3BJfGIEIDnhrqGD0i9bSa89SqBd++uG06TQgW5wsqtNcrwn81yZTq6=
XE6
i9VtD4GKfqC0d4KZJr9bnbeD81cI64VOdL8zJWJs0vj5EIXCobKyX74Kb4uePUyZqwT2Q74I1=
16u
/HwA9/FXsPo5isbh4ZqD4t0VHpWkmfq1FPT9a/JPyX46qKqB2Fce/7Qy+SQP1NfkuUlbhUH/J=
G9a
SSYvk3lznNiH41x9M+FDlL106itXOubrl3oi2fT3fsSedq7uzt+IV0DQEeNaoQAUuwEhdB8IW=
OMq
N2woDjGVKJftfsSWY9ilZrnDBNDrp0vRqcx33LUMkIw4d7iBwsFzBBABCAAdFiEEfhcKBFyEz=
0YO
K3mgEO952f2DUxIFAlu3JJwACgkQEO952f2DUxJjuw/6ApHSsVTWD4a0H6FJ23A9Ftpy+aXZ4=
vYl
zkSrfsn2ECrEfK3lXQh/uzwjJUDYZeB1/BQsFZtcYNQOJSSHbQ49BFRLwb1J/wBZG4bbmrkLx=
nNb
KDKQvzxEpclkMW0Dj0J6o7kGrmzIGGrhB+JJN99AcineHRug8ZSFIERRCmigxdhAKU0BFD7P+=
5HN
HltSL3DF1c2fFOf2JrgBKVoE+9RhMZjWNbYetFFLCkjXb5Rpay9zeMm1DxfSTGAnuOwUXW6qq=
4hn
l5+VC/48ceDZElLLfu7RQUZv44pkSTOWZs+iQoJiHMFHk9wPqyB2Vok1yJ2a2j27WhXrJlPwn=
Zbg
JO5RyWDG3p/eVmpl5Uuc2dsfIpR17KnAuWpghK6V+cyFncDoGCl/YG2MvoolsW08FiZh3Ej4d=
nJj
j25TZkeFG74JJDXLvMYpJfSBGnmETv4Dhcm2xPqVMuFuL1qJlMbVLrMo2GXeo03OzNyvbs+u8=
WLI
aGm5hC7N1CXY8wZs4jo6OJ/expvnc07dEuws4zT3AiWv3nIouWReRStZy9QkavDocqbyPmilc=
dPC
Yk4BsOlzpwwO74hNG7iyl0KdAlwTxGQ7y0rJou6HYa1TmRhIEr3vKvlW+JfUUrqtjXgsuacTX=
o4+
Ira2JUErL2cYzQMq1j4r1ZyhFnuz93s7Rsx/Nw0+0YvCwNwEEAEKAAYFAlvFx+UACgkQajsRO=
Tyk
rWCJqwv+NLVPE4sD4sDA2/6Ek7UsRIUkg+S39fhqWsLc4rtw/mDunv8Un61I3K04fZ2Ry4nF9=
hZM
0a710UvXFbStvrzRJO3EAAcdJR9LTCd19e8UeruQbIee3YT91U4NkC9JMpecfq62/teOAU2e5=
P3f
WYaLs5ZX7zCLwWuBcW2l3SyoljQczM85HhJ3XHm+FnwQ6D9xRle+lvWTcuC9d1yAyUb8IOosp=
cL2
lJTmy8e3r79R24hPlSB4LDe0wEN8AXbagrcAQZjwyaHyWxjJbTwZ0b43WGdfIqZ1ElOeoffbk=
etP
GRmWvx5xUvb2ALFBBdETzV270gs5XDJgJ1SIIKOyDADxwvroTe2jD8C/841eEql5QSow3s/U3=
zRq
k3mttto8Qw/DN71aeh6dmYSsvd2UjsHw/vofOPRBGxZLEkKTEvMnhmMW9hiKPkPia+QgevYE0=
20q
pKSxLEdWA8nprHwxmGiDNesCfXSC6vm1qfyj5g8HzxSckq9ZaMhKMCo7vxflUEDuzsFNBFo9U=
DIB
EAD6DdHQfMav8OXfhjTteoarOrlJTSdci727xiezGPuBHmpvceBRZgRasdbaMc4HJee+R9+5x=
/nL
PCuy/DxDyIjwIUeJNgc+l7LjI9WfpHTD8U4xxjvR5Mi7+ToQQUOUNuzT0O0pyuxP1uY3RehHE=
hOV
fBZO59ipSeZL5iQC6T5MsK1SKfs51pLa5ToC1rc8tBJ4zZmxRAyZiYc/AH2uZ/6rYjTTkAn1D=
VI9
DYo2D/zE4bGjXdJW5pKphFB2lX3dG4I7ODi+5e1H6A/QpCu6z8/ZkIQ+9T1xcX/YwiFeA7PbT=
uW/
eITbMbI1eV3+fyym9aT7Rsflmp31Zxtr+sZwGGZf00ooMBFmqOS//NUQ/Vf3vDUew1h5QU1yD=
aWT
3NApvi+XWPH9TPy6TMfZA2FThHf11sX/gDBa5JWQZbptPEcmoazpiKZt91CrFPOaoXDPck/Q6=
1df
mr/oPikfByYnASIM3OwEuXqyQ9JDRfKrem5r+oA/wxWb5jELElAhOpnyqMMvOh7uz1foUssL8=
MAv
2TGXmxpVJ8Nu4je6wf96Z22fQ0D38zud+CKH3bMP3ayXXJBcdPoENrzFbWP5FTg/4TTDJ3vOA=
HZR
5iCunYghx8b7Ffa4UbkwlD+dh8GiIAtvT51Ac0cO0Wc0Zjc57zPUz1zloMbf+zb1Bsn7DuEQo=
qj1
gwARAQABwsFlBBgBCAAPBQJaPVAyAhsMBQkJlCYAAAoJEFqy+vF7FyvqrC8P/1tF6TeR83xD6=
Mas
qXyrBjwcLmziaF0Mlkj8k/YUiZ/knb53n97xQnh9yxPv0TT8Wpfdn3BmvqGyh8+ouHX9jMOxi=
RkM
dNhIauVYY/8jmRfBSYWcFkfMzdYasvdLtmYJgx252HKTFdeOrszoOjWjEzwmh+tca3AFMu/nB=
++/
KAmi5UJV7zsZ7uYJ5jm97LV5SLjNJIXXM+lHqCDrjDaDhNczmq1LCRlU6/WDjvkuwaVhZG4lX=
xMD
rvKnXMkjseQ2oKjwrIdfQM86H1z5J31lfhqop+of0cimcIsBgSCPu+h96LHuAzeRBCbDKeqrf=
ZtA
ZAGsokRina9947fRWxXHh3O66ILmXKNRxxWbDkPvYnQWUat8SbSTDoPWrDIGDRIAypqYo3pcN=
2OE
0C1chqgDZQxkr+9kYZQpupOAN2TR+fM7JvbO9coKI8Uqog8CopoMeDQkd0YjcqlB1E0svODHT=
zcS
oRzogDBYDqNLP7qVkNXpcOAXSVioBgiSDf7o5RdS/qmUyXBIeq6I5z8xBcd+BQ/n/9Frkm6K7=
IKP
3ngUP4wEoiPx5ZE5+fPIScGmVUcZIMhkvMvem9XXh1yyhqN14gfjmLwPGdWbrgG8QUe0s2WeW=
Iys
s6uTiyF+ZbJSo2XOKVc3YFMVUUfgyudqAV1wWdZinUk+H3pkqOKoHAy/8fST
=3D40Nd
-----END PGP PUBLIC KEY BLOCK-----

--------------B218832335451491CA8494A4--

--VIjcCXprWATSCAT1mY2TYFUZrP2EVM5cL--

--CdoNiQqI6aRzheI71OdA0NMmtzi19TTJ1
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEW7Wm6ldl0sWGPK4nWrL68XsXK+oFAmAZXIcFAwAAAAAACgkQWrL68XsXK+rt
lxAAnHaEwrBvnyqBLEbhfd7cmyPW2HSuhXY+zGL/OUEw4rZ/4+VS1BFOy5xI2C7aFbj3ABjXcVBX
JU7/TiP46lg8FTWhNwpmxGAa0/f3tgDlAdraG8yYIJEzxDOZ3A3FRmsk9urJ5MzitfsqQedCyxcK
4ClmTjshgHECtTVDFIzeeGLN8HA/d3xzCUYzz6Ve3x6VmZWvNXyxXIA2dpJgk0vEQTw6N43NMgZ4
ycxTQFFHYWqh3f7+oeyV/vrMn8CudmcnvHK8xQhNmWVpKc4w+gPK5N0cSb/3Y7/P5c00k7s61fu2
uzcoHkIZJqsdqgSIkucrdJP4Zo6kfjv9Y7Ua5A/D+B8CLgZji4o4C+dvEWY7j6M/oJ1mjDMwUsB5
b/ZfIOm/g2Itdb+bW/5TdkznZvmLEsGKiW7Wyq25Xew+lzgEG90d53GSSJ47MuSHtW4t5Sb5SJEl
60uI4fO2t+1/EXJQfP9Xxm3NTwfLBv9uP/T7IxCKGBSo/iYSYhnAkin6Gdwgqyo4DNUSEzimuq9e
3XnMna8nhXW6mjBky24lVfmz4ysVwVx+yaocvXWjRlVkpDSSclOaJlfeWiB7nbDB8KCVN+zi5mP/
ZDIjZHFHFkD/dWOZy+JqXgGhvDQ1rRv6umeHbCl/G5O4oW56UF8Mzwfo6DC8RkJqFSBr40rzrAuh
kB0=
=UUaO
-----END PGP SIGNATURE-----

--CdoNiQqI6aRzheI71OdA0NMmtzi19TTJ1--


From nobody Tue Feb  2 06:16:03 2021
Return-Path: <ajs@anvilwalrusden.com>
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 9B33A3A1B2D for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 06:16:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=yitter.info header.b=hinoDnAY; dkim=pass (1024-bit key) header.d=yitter.info header.b=TVzOnDaO
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 ESL7Jn6TvV2Q for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 06:15:59 -0800 (PST)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9449E3A1B32 for <hrpc@irtf.org>; Tue,  2 Feb 2021 06:15:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 74DD2BD5C6 for <hrpc@irtf.org>; Tue,  2 Feb 2021 14:15:28 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1612275328; bh=rwKX9VzG5oja8hhkpQaQfcb2gP9YHVYrja23wlW2GPI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hinoDnAYPrHDrc6qS48hAIZz1Z5DwlsrQUzRBVd3wghCrDbdxmqR+umfJV1nrpZFY sIU96qIJWihVGmu98NdSg72mTeqbH9sdJrD1sX8O14LiOGRKlhvbu5h2LQoqd1C1o0 a9oCH2o1MJFSUFpRgmVylhpn7w2eC8LvJ7hm/vXk=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hsa_zQRZdvzO for <hrpc@irtf.org>; Tue,  2 Feb 2021 14:15:26 +0000 (UTC)
Date: Tue, 2 Feb 2021 09:15:25 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1612275326; bh=rwKX9VzG5oja8hhkpQaQfcb2gP9YHVYrja23wlW2GPI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=TVzOnDaOXqdVIVEbZROYRcIkqZOrWBiCwhOpfnpRGgvPztxxjluF8AeGvTQM5d21T HAykUukFXG+a1QvFBvqFTV3+/MRvPzMlEBS5t0MCaV0qY4IvG3k2HlNABqsxjd4ISU h+Bmyb9TbWcPhcio7eYlQid+plOmTSykwrSfcPDQ=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: hrpc@irtf.org
Message-ID: <20210202141525.6b7cldgdge45e3tu@crankycanuck.ca>
Mail-Followup-To: hrpc@irtf.org
References: <mailman.1401.1612260415.7093.hrpc@irtf.org> <CAB2unbMpgo4nDSDYW=gx8Xsts8gKiBEs0NyzC2JBd+19Npd0Ew@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <CAB2unbMpgo4nDSDYW=gx8Xsts8gKiBEs0NyzC2JBd+19Npd0Ew@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Fb2BhMg17FGfJB8xpBgSxhlyfPE>
Subject: [hrpc] Consensus and the RG (Was Re:  hrpc Digest, Vol 71, Issue 7)
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: Tue, 02 Feb 2021 14:16:02 -0000

(Still work for ISOC, this is still just my own opinion.)

On Tue, Feb 02, 2021 at 04:38:50AM -0600, Sandra Braman wrote:

>One of the problems with determining a "consensus," of course, is the
>question of who decides whether or not one has been achieved.

There is an RFC about this that was an IETF product, so at least there
is something to work on from the IETF context:
https://tools.ietf.org/html/rfc7282.  Of course, this RG isn't a part
of the IETF and has its own rules, but I understood the Chairs
previously to have said that they were following IETF process as
closely as possible for a RG to do.  I have previously expressed my
doubts about how well that could work, so I will refrain from
repeating myself.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Feb  2 08:49:14 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 6F3FB3A0BBC for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 08:49:12 -0800 (PST)
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 vdFMo6cvCm45 for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 08:49:11 -0800 (PST)
Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 D7B913A0BB3 for <hrpc@irtf.org>; Tue,  2 Feb 2021 08:49:10 -0800 (PST)
Received: by mail-qv1-xf32.google.com with SMTP id 2so10216800qvd.0 for <hrpc@irtf.org>; Tue, 02 Feb 2021 08:49:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=message-id:date:mime-version:user-agent:content-language:to :references:from:subject:in-reply-to:content-transfer-encoding; bh=uhiTUIFaFZQI3K1ilsz8hYzbB7BTEXI2TsaYw9PGC60=; b=cWcgklMDEfk6zuj8vpolMVpSiQQhiR20iJ7ISfXNhVymZSvKPJ7e2a14tpzuFz814R dxgKbReVp9eoyFk4SbI+8QEROzdrZADYyyzpz8dmMlW+BbHrefvKwGuiEIzT3m+lTcM7 AhYP8XTEpMnlmFL8QrvoeFO1cqeV29UeWMKPk=
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 :content-language:to:references:from:subject:in-reply-to :content-transfer-encoding; bh=uhiTUIFaFZQI3K1ilsz8hYzbB7BTEXI2TsaYw9PGC60=; b=lOzdmatbzI4A2+TT+iS4rFGoqOMN0KCu446yoRXEo75zmh7u3ijVdC204a89ggOJ/b Cv3+wZBEP+JLP/wRQXn985pnSurLJGyHCu92tma9Fm5UhYtkgUHqb7vTfCYkZ4xq3Uhb GQ+U1tRx/p8XTHu8gMmkrvR5PuXw4SX4FZrnzXIMbvtb3iPSEgJ7cgAYlakn12G05Otw BalOHUg7v3Hzalo/1fUVIYofjoY04NxZuvB/wr5cuchVOrGkx5ywoalkKxAekaKZzZuH nQ9o77Rl21diXnNNF1dxWaJLRb6n+INq45ipg1Xk7ytav1kRvZ9l2iLGRsWMKCLnnxnt lTZg==
X-Gm-Message-State: AOAM531BLJZyODmY6iVx+qxWHlSAKMZX1KdxyJa4bI7X1sPaankF6BpN T61WZY/UIQLwiFxdyqL5oh5GLMe/FcSx/65W
X-Google-Smtp-Source: ABdhPJz33UQeI1cgq2JRNOkKGhDw9azkbdYFd1RMF23QXs+zqBco6TzqMbnTOgItATBcsV21lV2BaQ==
X-Received: by 2002:a0c:f601:: with SMTP id r1mr21747326qvm.39.1612284549630;  Tue, 02 Feb 2021 08:49:09 -0800 (PST)
Received: from Mallorys-MacBook-Air.local (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with UTF8SMTPSA id x74sm16687365qkb.55.2021.02.02.08.49.08 for <hrpc@irtf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Feb 2021 08:49:09 -0800 (PST)
Message-ID: <ece7d9fa-c39e-7c2b-21e3-6b5b8ac530d9@cdt.org>
Date: Tue, 2 Feb 2021 11:49:08 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Thunderbird/86.0
Content-Language: en-US
To: hrpc@irtf.org
References: <mailman.1401.1612260415.7093.hrpc@irtf.org> <CAB2unbMpgo4nDSDYW=gx8Xsts8gKiBEs0NyzC2JBd+19Npd0Ew@mail.gmail.com> <20210202141525.6b7cldgdge45e3tu@crankycanuck.ca>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <20210202141525.6b7cldgdge45e3tu@crankycanuck.ca>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/7_OYzDmg9e1nb4ObIPe41ryHNXE>
Subject: Re: [hrpc] Consensus and the RG (Was Re: hrpc Digest, Vol 71, Issue 7)
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: Tue, 02 Feb 2021 16:49:12 -0000

On 2/2/21 9:15 AM, Andrew Sullivan wrote:

> (Still work for ISOC, this is still just my own opinion.)
>
> On Tue, Feb 02, 2021 at 04:38:50AM -0600, Sandra Braman wrote:
>
>> One of the problems with determining a "consensus," of course, is the
>> question of who decides whether or not one has been achieved.
>
> There is an RFC about this that was an IETF product, so at least there
> is something to work on from the IETF context:
> https://tools.ietf.org/html/rfc7282.  Of course, this RG isn't a part
> of the IETF and has its own rules, but I understood the Chairs
> previously to have said that they were following IETF process as
> closely as possible for a RG to do.  I have previously expressed my
> doubts about how well that could work, so I will refrain from
> repeating myself.

Only to clarify that as co-chair I am not in favour of a blanket rule 
for all HRPC drafts to reach consensus before publication. I think it 
makes sense in some cases but not in others. And to set the bar so high 
for research can disincentivise good, exploratory work. (I've said all 
of this many times before, nothing new just reminding folks of my position).

That said I do feel that draft-guidelines, because it's based on RFC 
8280 and meant to be usefully applied to IETF documents, should be at 
the end of the spectrum of *more* consensus than, say, draft-political 
or draft-feminism.

I also think that so far Gurshabad and Niels have done a stellar job of 
building this draft upon a strong foundation of group consensus. It was 
written with input from multiple people, notably those who have 
attempted to use it and they've been responsive to any and all feedback 
so far. It's a very strong document because of it.

Looking forward to the next version,

-Mallory

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


From nobody Tue Feb  2 09:03:55 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 7E6863A0C31 for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 jjWo6CPpCL5H for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:03:49 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 D243D3A0C74 for <hrpc@irtf.org>; Tue,  2 Feb 2021 09:03:48 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id r20so11868236qtm.3 for <hrpc@irtf.org>; Tue, 02 Feb 2021 09:03:48 -0800 (PST)
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:to :cc:references:from:in-reply-to; bh=GcC8PzuqS/uVhUBmS/vTX/qQEmrlsGAgCbtSERk0Mro=; b=Hi9+4zJ/DwrPTTyb4pxZZTcWDN8bVJWw7mq1m1ZukYr13DT7COk1g4FjYNN5IVmo2W sVnO0y8r7VJ//0Bqgt01G0KKCcju1zQ+ei7o75zpU8kjni7YXsVAF5ycZoB6pVV5NkOS B+GQuuIt2LtrGkK6SnBmHoKJ3D5c9Skz/4VQA=
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:to:cc:references:from:in-reply-to; bh=GcC8PzuqS/uVhUBmS/vTX/qQEmrlsGAgCbtSERk0Mro=; b=Cfw0RBrypSkJ21jQelu2NmJF0ef9HGBjC5D59YnofuvN2rIqo5Is4TurG+31vINqSh Y7Jk1GotImEzfsrCLhwlGgjIas247g135IVuhcK/diC3szAWZnn8/lCibyW6TVDKHZMc i3ZfsNQUubbChykXhFpwu8l0/RRQoR4oo8zxutFVJzhQJsZjGZNYk4ZDh2QYkFx9A9Jk QdmpF8hVU/56WY6DBTjvJSUKLpavVlGBAteoFxVXqQv4kqe95gDxnwAa6UNNezhGgh+9 VXkRFYUkU8R5SuiNfHuzuO3li2MgZk+lbJhQGZBvvgpalj0065f9IZXZS3XN1OH+gpcN fzBw==
X-Gm-Message-State: AOAM530YUFpuFLNCmba+61ns1v0JgEry44Xtuo3bAqxCe7xn9K0ipQYJ 2xvUTEF8n21D9WECu2VVe3rudlbyNyz8Zq/A
X-Google-Smtp-Source: ABdhPJzJKnBqPa9VgWJiQMdDQnxwcwtUeMdj7qg9CmANtmJ/HycswwXRKhY2lQYqJRkjQ+ggTexhzg==
X-Received: by 2002:ac8:3986:: with SMTP id v6mr20830605qte.308.1612285427569;  Tue, 02 Feb 2021 09:03:47 -0800 (PST)
Received: from Mallorys-MacBook-Air.local (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with UTF8SMTPSA id a47sm17283435qtk.44.2021.02.02.09.03.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Feb 2021 09:03:46 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------SAKqcmLEH7s739UXLpRX1mK6"
Message-ID: <6b1a8787-e9ea-71cd-e1d3-8b7ad15094e1@cdt.org>
Date: Tue, 2 Feb 2021 12:03:46 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Thunderbird/86.0
Content-Language: en-US
To: farzaneh badii <farzaneh.badii@gmail.com>, Niels ten Oever <mail@nielstenoever.net>
Cc: Hrpc <hrpc@irtf.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com> <08b61ab2-7840-d993-9946-c085861f4172@nielstenoever.net> <CAN1qJvBF5oUv1v0rrCixsO0ic-fVzor6egTSpO-s5xBmkdBS7g@mail.gmail.com> <1bbab056-2344-1ede-2462-6b7f40b93644@nielstenoever.net> <CAN1qJvCsbfnVePRFYAsySrgtaumUARc8PpnAX-cANu5Pgc7TMA@mail.gmail.com> <34ab9666-4521-49f7-831e-c22841743448@nielstenoever.net> <CAN1qJvB++T1u+vRWLDcb9YoO5J8mJ_-bwf1c3jSPVrmzk=GDJw@mail.gmail.com>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <CAN1qJvB++T1u+vRWLDcb9YoO5J8mJ_-bwf1c3jSPVrmzk=GDJw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/h32s0006ilm_ILLXaGcm-GTYp18>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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: Tue, 02 Feb 2021 17:03:54 -0000

This is a multi-part message in MIME format.
--------------SAKqcmLEH7s739UXLpRX1mK6
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

My suggestion to resolve the text is simply to minimise and make it 
netral. Perhaps something on attribution needs to be there as a 
reference to what is already in RFC 8280 and, even better, to serve as a 
pointer to future work that might deepen our collective understanding of 
attribution and protocols, even if that more thorough research uncovers 
restraint as a best practice.

-Mallory

On 2/1/21 8:06 PM, farzaneh badii wrote:
> Niels,Â
>
> I don't know how you come to consensus. I thought you as one of the 
> drafters need to make changes that capture the consensus. Seems like 
> you have had “many discussions” and all the points I have raised 
> been resolved satisfactorily in this group in my absence. Then the 
> only thing I can do is to record my objection to paragraph 3.3.20: 
> Attribution.Â
>
> I don't think the paragraph as is in that document is human rights 
> enabling and frankly it has the potential to do the opposite. It is a 
> mistake to bring court and law enforcement to the discussion when the 
> scope of this group is "enabling human rights". It is a mistake to 
> make a distinction between natural and legal persons in this case and 
> assume that natural persons may not be harmed in the process because 
> the distinction “may” protect them.Â
>
> I brought reasons and they don't seem to be convincing to you or 
> something you want to work with and it seems to me it is too late now. 
> So I get out of your way and just record my objection to the paragraph.Â
>
> Just to disclose: I have worked on cyber attack attribution processes 
> academically, and believe that attribution is one way to hold cyber 
> attackers accountable. I just don’t think we need the protocol 
> developer think about ways of attribution to make it easier to 
> attribute cyber attacks in court for legal remedy and include this in 
> the guidelines for human rights protection document as a “access to 
> legal remedy”. Anonymity makes attribution harder but still not 
> impossible. Many John Doe’s have had cases against them which 
> provided the plaintiffs with the appropriate remedies.Â
>
>
>
>
>
> On Mon, Feb 1, 2021 at 5:19 PM Niels ten Oever <mail@nielstenoever.net 
> <mailto:mail@nielstenoever.net>> wrote:
>
>     Dear Farzaneh,
>
>     Do your alterations reflect the content of the discussion, or mere
>     your opinion?
>
>     I hope we're seeking to reach a consensus during last call, not
>     reopening the discussion.
>
>     Best,
>
>     Niels
>
>     On Feb 1, 2021, at 22:22, farzaneh badii <farzaneh.badii@gmail.com
>     <mailto:farzaneh.badii@gmail.com>> wrote:
>
>         Here we go:
>
>
>         Question(s): Can your protocol facilitate a negatively impacted
>
>          Â party's right to the appropriate  legal remedy without
>         disproportionately impacting
>
>          Â other parties' human rights, especially their right to
>         privacy?
>
>
>          Â Explanation: Access to legal remedy is a human right that
>         ensures
>
>          Â that individuals whose rights have been violated can seek
>         remedies
>
>
>
>
>          Â through a judicial authority. Â Attribution (i.e.
>         mechanisms in
>
>          Â protocols or architectures that are designed to make
>         communications
>
>          Â or artifacts attributable might help with seeking the
>         appropriate remedy.)Â to a certain computer or individual) can be
>
>          Â a part of this, since it may allow law enforcement
>         agencies to
>
>          Â identify a possible violator .Â However, attribution
>         mechanisms may
>
>          Â impede the exercise of the right to privacy.Â The Special
>         Rapporteur
>
>          Â for Freedom of Expression has also argued that anonymity is an
>
>          Â inherent part of freedom of expression.Â [Kaye]
>         Considering the
>
>          Â adverse impact of attribution on the right to privacy and
>         freedom of
>
>          Â expression, attribution on an individual level may Â isÂ
>         not be consistent
>
>          Â with human rights.Â However, attribution to corporate
>         entities,
>
>          Â associations, and/or countries may not directly negatively
>         impact
>
>          Â human rights.
>
>
>          Â Impacts:
>
>
>          Â - Â Right to legal remedy
>
>
>          Â -Â Right to security
>
>         Farzaneh
>
>
>         On Mon, Feb 1, 2021 at 2:38 PM Niels ten Oever <
>         mail@nielstenoever.net <mailto:mail@nielstenoever.net>> wrote:
>
>             Hi Farzaneh,
>
>             On 31-01-2021 19:16, farzaneh badii wrote:
>             > Hello Niels.
>             >
>             >
>             > I don't know how we measure consensus here. But I
>             remember weighing in back then as well(When Mr. Curran
>             weighed in back in 2019). Here is the thread:Â
>             https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution
>             <https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution>
>             <
>             https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution
>             <https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution>>
>
>             >
>             > I can see that unfortunately I missed the discussion on
>             this topic during the past year, and that's my fault, but
>             I can bring reasons not to add "attribution and legal
>             remedy" to this document at all.Â
>             >
>             > 1. Access to legal remedy is something that the States
>             are supposedly in charge of bringing to their
>             citizens.Which should (in theory) ensure that human rights
>             are enforced. I don't think there was an intention to 
>             provide  mechanisms for "enforcement" of human rights in
>             various legal systems through Internet protocols. As
>             mentioned in the beginning of your document:Â
>             > "Human rights threats on the Internet come in a myriad
>             of forms.* **P**rotocols and standards can harm or
>             enable* the right to freedom of expression, right to
>             non-discrimination, right to equal protection, right to
>             participate in cultural life, arts and science, right
>             to freedom of assembly and association, and the right to
>             security."Â
>             >
>             > So we are not in the business of enforcing but
>             providing an enabling environment. Because if we want to
>             help law enforcement and the judicial authorities enforce
>             human rights through Internet protocols we should bear
>             in mind that that they are not always staunch advocates of
>             human rights. So what I assume we are trying to do here is
>             to help Internet protocol not to facilitate harm and
>             "enable" human rights.Â
>             >
>
>             The text in the draft seeks to address this risk. I have
>             sought to address all points made in that discussion, and
>             I would not like to re-open that debate. If you feel the
>             text is unbalanced, could you perhaps provide text
>             suggestions?
>
>             > 2. Attribution, section 3.3.20  of the Guideline, the
>             authors assert that: "However, attribution to corporate
>             entities, associations, and/or countries may not directly
>             negatively impact human rights." I think this is not a
>             very well backed up claim. Because in some cases some
>             associations might be political or they might be human
>             rights associations dealing with a dictatorship.
>             Attribution to those associations certainly can impact
>             their human rights negatively. Even when it comes to
>             corporations, some CEOs of digital companies are put in
>             jail because of the materials posted on their websites. I
>             don't think we can argue that attribution to corporate
>             entities might not adversely impact human rights.
>             >
>
>             Again, the keyword in that sentence is 'may', so there is
>             no strong claim made.
>
>             > All in all I think section 3.3.20 does not help Internet
>             Protocols enable human rights and it can be misinterpreted.
>
>             I think the text in there is not strong and shows
>             different perspectives and potential consequences. But
>             again, happy to receive text suggestions.
>
>             >
>             > And in my previous email I talked about the problems
>             with threat intelligence agencies and some of their
>             conducts and the use of WHOIS for attribution (which was
>             actually not designed to "identify" actors but
>             unfortunately was used for that) so I will not reiterate
>             here.
>
>             From exactly that discussion we got the idea to remove
>             individuals, and leave non-natural persons in.
>
>             Best,
>
>             Niels
>
>             >
>             >
>             >
>             >
>             >
>             >
>             >
>             > On Sun, Jan 31, 2021 at 5:52 AM Niels ten Oever <
>             mail@nielstenoever.net <mailto:mail@nielstenoever.net>
>             <mailto: mail@nielstenoever.net
>             <mailto:mail@nielstenoever.net>>> wrote:
>             >
>             >     Hi Farzaneh,
>             >
>             >     Thanks a lot for the review!
>             >
>             >     On 30-01-2021 23:00, farzaneh badii wrote:
>             >     > Hello
>             >     >
>             >     > Adding my comments on this document:Â
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>
>             <
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>>
>             <
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>
>             <
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05>>>
>             >     >
>             >     > 1. One major issue that I see here and you
>             might be able to easily solve it is that there is no
>             distinction between user facing protocols and other
>             protocols. For example, you ask for accessibility and
>             consideration of culture etc. Are you asking all the
>             protocols to be provided in multiple languages, even those
>             that only developers and implementers use and not the
>             actual users? You might want to clarify that.Â
>             >     >
>             >
>             >     We had a quite extensive discussion about this in
>             relation to the presentation by Ramsey Nasr who create
>             Qalb, an Arabic programming language. Programmers are the
>             most frequent 'users' of protocols - if we continue using
>             only latin characters and English documentation in
>             protocols we are likely to reproduce the existing lack of
>             diversity in protocol developers communities. But we can
>             make the text on this clearer as well!
>             >
>             >     > 2.section 3.3.1 on connectivity, you mention
>             that "considering the fact that network quality and
>             conditions vary across geography and time it is also
>             important to design protocols such that they are reliable
>             even on low bandwidth ...". Then in your example you say:
>             Middleboxes (including NAT).... can create potential for
>             abuse. NAT is a Network Address Translation protocol. I
>             don't think it has anything to do with bandwidth. In this
>             example you also mention CDNs. Are you suggesting that the
>             developer should not consider "Middleboxes" protocols? I
>             think you need to work on the example of section 3.3.1
>             some more to make it clearer.Â
>             >     >
>             >
>             >     Excellent point - we'll address this in a future
>             version.
>             >
>             >     > 3. section 3.3.20 remedy and attributionÂ
>             >     > This section worries me. As aÂ scholar I have
>             worked on cyber attribution to some extent and believe in
>             general when we have the right processes in
>             place, attribution is very important and can hold
>             cyber-attackers accountable. I am aware of some of the
>             attribution processes and unfortunately some threat
>             intelligence firms and open source intelligence
>             organizations can violate the privacy of individuals by
>             profiling them. Also, uncontrolled attribution mechanisms
>             can lead to frivolous intellectual property claims. Both
>             some threat intelligence firms and IP firms have used
>             WHOIS extensively in their favor to attribute
>             cybersecurity attacks and bring forward IP claims. WHOIS
>             protocol did not have the intention to actually identify
>             organizations and individuals, but to make them
>             "contactable".and it was still used and mined for so many
>             years and those who have abused WHOIS have not been held
>             accountable.When you suggest they consider "attribution"
>             when developing protocols it
>             >     > concerns me because it is not enough that you
>             limit attribution to organizations and states. These kinds
>             of attributions can be used against individuals and until
>             we do not have the right preserving processes to put in
>             place for those who want to be in the attribution
>             business, rights of the individual can be at risk. there
>             are very privacy conscious cybersecurity researchers out
>             there but unfortunately that does not ensure a
>             systematic practice of attribution in a fair manner. And
>             you mention attribution to associations is fine and may
>             not directly negatively impact human rights. Associations
>             can themselves be at risk of frivolous attacks and
>             frivolous attribution. I am concerned about this
>             paragraph. I think we should have a conversation about it.
>             >     >
>             >
>             >     In the proposed text I tried to capture the
>             consensus that emerged from the extensive discussion that
>             was had on this list. Do you have concrete suggestions on
>             how to better capture that conensensus? I am afraid we
>             would go back and repeat the same discussion.
>             >
>             >     > 4. Nice to see that you mention DoH. It's a
>             great privacy preserving protocol.Â
>             >     >
>             >     >
>             >
>             >     Thanks!
>             >
>             >     Niels
>             >
>             >     >
>             >     >
>             >     >
>             >     >
>             >     >
>             >     >
>             >     >
>             >     >
>             >     > Farzaneh
>             >     >
>             >     >
>             >     > On Sat, Jan 30, 2021 at 10:35 AM Corinne Cath <
>             corinnecath@gmail.com <mailto:corinnecath@gmail.com>
>             <mailto: corinnecath@gmail.com
>             <mailto:corinnecath@gmail.com>> <mailto:
>             corinnecath@gmail.com <mailto:corinnecath@gmail.com>
>             <mailto: corinnecath@gmail.com
>             <mailto:corinnecath@gmail.com>>>> wrote:
>             >     >
>             >     >     Hi all,
>             >     >
>             >     >     I trust this email finds you well. I did
>             a review of the draft, from my perspective as an academic.
>             Take it as you please. My main concern is that some of the
>             language reads a bit deterministic (as, I know so does RFC
>             8280). It means that a lot of onus is put on the impact of
>             a protocol, as opposed the role of the individuals that
>             write them.Â
>             >     >
>             >     >     I think through out the document, it
>             would be interesting (especially in section 1 through
>             3.2.5) to see if you can rewrite such that you speak more
>             directly to the protocol developers. I think that section
>             3.3 does that well, in terms of the tone it takes. As it
>             clearly connects the actions of protocol developers to
>             their potential outcomes.Â
>             >     >
>             >     >     Hope this is helpful!Â
>             >     >
>             >     >     Kind regards,Â
>             >     >
>             >     >     Corinne
>             >     >
>             >     >     ---------------------------------
>             >     >
>             >     >     *1. Introduction*
>             >     >
>             >     >     "It provides questions engineers should ask
>             >     >
>             >     >        themselves when developing or
>             improving protocols if they want to
>             >     >        understand their potential human
>             rights impact."
>             >     >
>             >     >
>             >     >     >> maybe if they want to understand
>             potential human rights concerns? Impact seems a little
>             deterministic, as you also mention in the next sentence, I
>             wonder if you can prove such direct impact between
>             protocol development in the IETF and impact on human rights.
>             >     >
>             >     >     "The research establishes
>             >     >
>             >     >        that human rights relate to
>             standards and protocols, and offers a
>             >     >        common vocabulary of technical
>             concepts that impact human rights and
>             >     >        how these technical concepts can be
>             combined to ensure that the
>             >     >        Internet remains an enabling
>             environment for human rights."
>             >     >
>             >     >
>             >     >     >> same comment for the word impact,
>             perhaps shape? influence? etc.
>             >     >
>             >     >
>             >     >           3.1 <
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1>
>             <
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1>>>.
>             Human rights threats
>             >     >
>             >     >
>             >     >
>             >     >      "Protocols and standards can harm or
>             enable the right to freedom of
>             >     >        expression, right to
>             non-discrimination, right to equal protection,
>             >     >        right to participate in cultural
>             life, arts and science, right to
>             >     >
>             >     >     freedom of assembly and association, and
>             the right to security. "
>             >     >
>             >     >
>             >     >     >> again, deterministic language.
>             Perhaps soften or add more concrete examples for context,
>             that draw from current IETF discussions/standards.
>             >     >
>             >     >
>             >     >
>             >     >           3.3 <
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3>
>             <
>             https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3
>             <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3>>>.
>             Guidelines for human rights considerations
>             >     >
>             >     >
>             >     >
>             >     >     again, use of the word impact in the
>             introduction.
>             >     >
>             >     >
>             >     >
>             >     >
>             >     >     --
>             >     >     Corinne Cath - Speth
>             >     >     Ph.D. Candidate, Oxford Internet
>             Institute & Alan Turing Institute
>             >     >
>             >     >     Web:
>             www.oii.ox.ac.uk/people/corinne-cath
>             <http://www.oii.ox.ac.uk/people/corinne-cath> <
>             http://www.oii.ox.ac.uk/people/corinne-cath
>             <http://www.oii.ox.ac.uk/people/corinne-cath>> <
>             http://www.oii.ox.ac.uk/people/corinne-cath
>             <http://www.oii.ox.ac.uk/people/corinne-cath> <
>             http://www.oii.ox.ac.uk/people/corinne-cath
>             <http://www.oii.ox.ac.uk/people/corinne-cath>>>
>             >     >     Email: ccath@turing.ac.uk
>             <mailto:ccath@turing.ac.uk> <mailto: ccath@turing.ac.uk
>             <mailto:ccath@turing.ac.uk>> <mailto: ccath@turing.ac.uk
>             <mailto:ccath@turing.ac.uk> <mailto: ccath@turing.ac.uk
>             <mailto:ccath@turing.ac.uk>>> & corinnecath@gmail.com
>             <mailto:corinnecath@gmail.com> <mailto:
>             corinnecath@gmail.com <mailto:corinnecath@gmail.com>>
>             <mailto: corinnecath@gmail.com
>             <mailto:corinnecath@gmail.com> <mailto:
>             corinnecath@gmail.com <mailto:corinnecath@gmail.com>>>
>             >     >     Twitter: @C_CS
>             >     >   
>              _______________________________________________
>             >     >     hrpc mailing list
>             >     >    Â hrpc@irtf.org <mailto:hrpc@irtf.org>
>             <mailto: hrpc@irtf.org <mailto:hrpc@irtf.org>> <mailto:
>             hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:
>             hrpc@irtf.org <mailto:hrpc@irtf.org>>>
>             >     >    Â
>             https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc> <
>             https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc>> <
>             https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc> <
>             https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc>>>
>             >     >
>             >     >
>             >     > _______________________________________________
>             >     > hrpc mailing list
>             >     > hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:
>             hrpc@irtf.org <mailto:hrpc@irtf.org>>
>             >     > https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc> <
>             https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc>>
>             >     >
>             >
>             >     --
>             >     Niels ten Oever, PhD
>             >     Postdoctoral Researcher - Media Studies
>             Department - University of Amsterdam
>             >     Postdoctoral Research Fellow - Communications
>             Department - Texas A&M University
>             >     Research Fellow - Centre for Internet and Human
>             Rights - European University Viadrina
>             >     Associated Scholar - Centro de Tecnologia e
>             Sociedade - Fundação Getúlio Vargas
>             >
>             >     W: https://nielstenoever.net
>             <https://nielstenoever.net> < https://nielstenoever.net
>             <https://nielstenoever.net>>
>             >     E: mail@nielstenoever.net
>             <mailto:mail@nielstenoever.net> <mailto:
>             mail@nielstenoever.net <mailto:mail@nielstenoever.net>>
>             >     T: @nielstenoever
>             >     P/S/WA: +31629051853
>             >     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A
>             C8B3
>             >
>             >     Read my dissertation 'Wired Norms' here:
>             https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>             <https://pure.uva.nl/ws/files/50781961/Thesis.pdf> <
>             https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>             <https://pure.uva.nl/ws/files/50781961/Thesis.pdf>>
>             >     _______________________________________________
>             >     hrpc mailing list
>             >    Â hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:
>             hrpc@irtf.org <mailto:hrpc@irtf.org>>
>             >    Â https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc> <
>             https://www.irtf.org/mailman/listinfo/hrpc
>             <https://www.irtf.org/mailman/listinfo/hrpc>>
>             >
>
>             -- 
>             Niels ten Oever, PhD
>             Postdoctoral Researcher - Media Studies Department -
>             University of Amsterdam
>             Postdoctoral Research Fellow - Communications Department -
>             Texas A&M University
>             Research Fellow - Centre for Internet and Human Rights -
>             European University Viadrina
>             Associated Scholar - Centro de Tecnologia e Sociedade -
>             Fundação Getúlio Vargas
>
>             W: https://nielstenoever.net <https://nielstenoever.net>
>             E: mail@nielstenoever.net <mailto:mail@nielstenoever.net>
>             T: @nielstenoever
>             P/S/WA: +31629051853
>             PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
>
>             Read my dissertation 'Wired Norms' here:
>             https://pure.uva.nl/ws/files/50781961/Thesis.pdf
>             <https://pure.uva.nl/ws/files/50781961/Thesis.pdf>
>
>
>
> -- 
> Farzaneh
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc

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

--------------SAKqcmLEH7s739UXLpRX1mK6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>My suggestion to resolve the text is simply to minimise and make
      it netral. Perhaps something on attribution needs to be there as a
      reference to what is already in RFC 8280 and, even better, to
      serve as a pointer to future work that might deepen our collective
      understanding of attribution and protocols, even if that more
      thorough research uncovers restraint as a best practice.</p>
    <p>-Mallory<br>
    </p>
    <div class="moz-cite-prefix">On 2/1/21 8:06 PM, farzaneh badii
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAN1qJvB++T1u+vRWLDcb9YoO5J8mJ_-bwf1c3jSPVrmzk=GDJw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div>Niels, <br>
      </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">I don't know how you come to consensus. I thought
        you as one of the drafters need to make changes that capture the
        consensus. Seems like you have had “many discussions” and all
        the points I have raised been resolved satisfactorily in this
        group in my absence. Then the only thing I can do is to record
        my objection to paragraph 3.3.20: Attribution. </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">I don't think the paragraph as is in that document
        is human rights enabling and frankly it has the potential to do
        the opposite. It is a mistake to bring court and law enforcement
        to the discussion when the scope of this group is "enabling
        human rights". It is a mistake to make a distinction between
        natural and legal persons in this case and assume that natural
        persons may not be harmed in the process because the distinction
        “may” protect them. </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">I brought reasons and they don't seem to be
        convincing to you or something you want to work with and it
        seems to me it is too late now. So I get out of your way and
        just record my objection to the paragraph. </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">Just to disclose: I have worked on cyber attack
        attribution processes academically, and believe that attribution
        is one way to hold cyber attackers accountable. I just don’t
        think we need the protocol developer think about ways of
        attribution to make it easier to attribute cyber attacks in
        court for legal remedy and include this in the guidelines for
        human rights protection document as a “access to legal remedy”.
        Anonymity makes attribution harder but still not impossible.
        Many John Doe’s have had cases against them which provided the
        plaintiffs with the appropriate remedies. </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto"><br>
        <div class="gmail_quote" dir="auto">
          <div dir="ltr" class="gmail_attr">On Mon, Feb 1, 2021 at 5:19
            PM Niels ten Oever &lt;<a
              href="mailto:mail@nielstenoever.net" target="_blank"
              moz-do-not-send="true">mail@nielstenoever.net</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div style="zoom:0%">
              <div dir="auto">Dear Farzaneh,<br>
                <br>
              </div>
              <div dir="auto">Do your alterations reflect the content of
                the discussion, or mere your opinion?<br>
                <br>
              </div>
              <div dir="auto">I hope we're seeking to reach a consensus
                during last call, not reopening the discussion.<br>
                <br>
              </div>
              <div dir="auto">Best,<br>
                <br>
              </div>
              <div dir="auto">Niels<br>
                <br>
              </div>
              <div class="gmail_quote">On Feb 1, 2021, at 22:22,
                farzaneh badii &lt;<a
                  href="mailto:farzaneh.badii@gmail.com" target="_blank"
                  moz-do-not-send="true">farzaneh.badii@gmail.com</a>&gt;
                wrote:
                <blockquote class="gmail_quote" style="margin:0pt 0pt
                  0pt 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div class="gmail_default"
                      style="font-family:verdana,sans-serif"> Here we
                      go: </div>
                    <div class="gmail_default"
                      style="font-family:verdana,sans-serif"> <br>
                    </div>
                    <div class="gmail_default"
                      style="font-family:verdana,sans-serif"> <br>
                    </div>
                    <div class="gmail_default"
                      style="font-family:verdana,sans-serif">
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">Question(s):
                        Can your protocol facilitate a negatively
                        impacted</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>party's right to<font color="#ff0000"> the
                          appropriate </font> <strike>  legal </strike>remedy
                        without disproportionately impacting</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>other parties' human rights, especially
                        their right to privacy?</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                      </p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>Explanation: Access
                          to legal remedy is a human right that ensures
                        </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>that individuals
                          whose rights have been violated can seek
                          remedies </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                      </p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                      </p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                      </p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>through a judicial
                          authority. </strike><span>  </span>Attribution
                        (i.e. mechanisms in</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>protocols or architectures that are
                        designed to make communications</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>or artifacts attributable <font
                          color="#ff0000">might help with seeking the
                          appropriate remedy</font>.)  <strike> to a
                          certain computer or individual) </strike> <strike>
                          can be </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>a part of this, since
                          it may allow law enforcement agencies to </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>identify a possible
                          violator </strike>.<span>  </span>However,
                        attribution mechanisms may</p>
                    </div>
                  </div>
                </blockquote>
              </div>
            </div>
            <div style="zoom:0%">
              <div class="gmail_quote">
                <blockquote class="gmail_quote" style="margin:0pt 0pt
                  0pt 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div class="gmail_default"
                      style="font-family:verdana,sans-serif">
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>impede the exercise of the right to
                        privacy.<span>  </span>The Special Rapporteur</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>for Freedom of Expression has also argued
                        that anonymity is an</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>inherent part of freedom of expression.<span> 
                        </span>[Kaye] Considering the</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>adverse impact of attribution on the
                        right to privacy and freedom of</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>expression, attribution on an individual
                        level <strike> may </strike> <font
                          color="#ff0000">is </font>not <strike> be </strike>
                        consistent</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>with human rights.<span>  <strike> </strike></span>
                        <strike> However, attribution to corporate
                          entities, </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>associations, and/or
                          countries may not directly negatively impact </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>human rights. </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                      </p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>Impacts:</p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px">
                        <strike> <br>
                        </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica">
                        <strike> <span>   </span>- <span>  </span>Right
                          to legal remedy </strike></p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px"><br>
                      </p>
                      <p
style="margin:0px;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span>  
                        </span>-<span>  </span>Right to security</p>
                    </div>
                  </div>
                </blockquote>
              </div>
            </div>
            <div style="zoom:0%">
              <div class="gmail_quote">
                <blockquote class="gmail_quote" style="margin:0pt 0pt
                  0pt 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div>
                      <div dir="ltr" data-smartmail="gmail_signature">
                        <div dir="ltr">
                          <div> <font face="verdana, sans-serif">Farzaneh
                            </font> </div>
                        </div>
                      </div>
                    </div>
                    <br>
                  </div>
                </blockquote>
              </div>
            </div>
            <div style="zoom:0%">
              <div class="gmail_quote">
                <blockquote class="gmail_quote" style="margin:0pt 0pt
                  0pt 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <br>
                  <div class="gmail_quote">
                    <div dir="ltr" class="gmail_attr"> On Mon, Feb 1,
                      2021 at 2:38 PM Niels ten Oever &lt; <a
                        href="mailto:mail@nielstenoever.net"
                        target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>&gt;
                      wrote: <br>
                    </div>
                    <blockquote class="gmail_quote" style="margin:0px
                      0px 0px 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex"> Hi Farzaneh, <br>
                      <br>
                      On 31-01-2021 19:16, farzaneh badii wrote: <br>
                      &gt; Hello Niels. <br>
                      &gt; <br>
                      &gt; <br>
                      &gt; I don't know how we measure consensus here.
                      But I remember weighing in back then as well(When
                      Mr. Curran weighed in back in 2019). Here is the
                      thread:  <a
                        href="https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://mailarchive.ietf.org/<wbr>arch/browse/hrpc/?q=<wbr>attribution</a>
                      &lt; <a
                        href="https://mailarchive.ietf.org/arch/browse/hrpc/?q=attribution"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://mailarchive.ietf.org/<wbr>arch/browse/hrpc/?q=<wbr>attribution</a>&gt;
                      <br>
                      &gt; <br>
                      &gt; I can see that unfortunately I missed
                      the discussion on this topic during the past year,
                      and that's my fault, but I can bring reasons not
                      to add "attribution and legal remedy" to this
                      document at all.  <br>
                      &gt; <br>
                      &gt; 1. Access to legal remedy is something that
                      the States are supposedly in charge of bringing to
                      their citizens.Which should (in theory) ensure
                      that human rights are enforced. I don't think
                      there was an intention to  provide  mechanisms for
                      "enforcement" of human rights in various legal
                      systems through Internet protocols. As
                      mentioned in the beginning of your document:  <br>
                      &gt; "Human rights threats on the Internet come in
                      a myriad of forms.* **P**rotocols and standards
                      can harm or enable* the right to freedom
                      of expression, right to non-discrimination, right
                      to equal protection, right to participate in
                      cultural life, arts and science, right to freedom
                      of assembly and association, and the right to
                      security."  <br>
                      &gt; <br>
                      &gt; So we are not in the business of enforcing
                      but providing an enabling environment. Because if
                      we want to help law enforcement and the judicial
                      authorities enforce human rights
                      through Internet protocols we should bear in mind
                      that that they are not always staunch advocates of
                      human rights. So what I assume we are trying to do
                      here is to help Internet protocol not to
                      facilitate harm and "enable" human rights.  <br>
                      &gt; <br>
                      <br>
                      The text in the draft seeks to address this risk.
                      I have sought to address all points made in that
                      discussion, and I would not like to re-open that
                      debate. If you feel the text is unbalanced, could
                      you perhaps provide text suggestions? <br>
                      <br>
                      &gt; 2. Attribution, section 3.3.20  of the
                      Guideline, the authors assert that: "However,
                      attribution to corporate entities, associations,
                      and/or countries may not directly negatively
                      impact human rights." I think this is not a
                      very well backed up claim. Because in some cases
                      some associations might be political or they might
                      be human rights associations dealing with a
                      dictatorship. Attribution to those associations
                      certainly can impact their human rights
                      negatively. Even when it comes to corporations,
                      some CEOs of digital companies are put in jail
                      because of the materials posted on their websites.
                      I don't think we can argue that attribution to
                      corporate entities might not adversely impact
                      human rights. <br>
                      &gt; <br>
                      <br>
                      Again, the keyword in that sentence is 'may', so
                      there is no strong claim made. <br>
                      <br>
                      &gt; All in all I think section 3.3.20 does not
                      help Internet Protocols enable human rights and it
                      can be misinterpreted. <br>
                      <br>
                      I think the text in there is not strong and shows
                      different perspectives and potential consequences.
                      But again, happy to receive text suggestions. <br>
                      <br>
                      &gt; <br>
                      &gt; And in my previous email I talked about the
                      problems with threat intelligence agencies and
                      some of their conducts and the use of WHOIS for
                      attribution (which was actually not designed to
                      "identify" actors but unfortunately was used for
                      that) so I will not reiterate here. <br>
                      <br>
                      From exactly that discussion we got the idea to
                      remove individuals, and leave non-natural persons
                      in. <br>
                      <br>
                      Best, <br>
                      <br>
                      Niels <br>
                      <br>
                      &gt; <br>
                      &gt; <br>
                      &gt; <br>
                      &gt; <br>
                      &gt; <br>
                      &gt; <br>
                      &gt; <br>
                      &gt; On Sun, Jan 31, 2021 at 5:52 AM Niels ten
                      Oever &lt; <a
                        href="mailto:mail@nielstenoever.net"
                        target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>
                      &lt;mailto: <a
                        href="mailto:mail@nielstenoever.net"
                        target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>&gt;&gt;
                      wrote: <br>
                      &gt; <br>
                      &gt;     Hi Farzaneh, <br>
                      &gt; <br>
                      &gt;     Thanks a lot for the review! <br>
                      &gt; <br>
                      &gt;     On 30-01-2021 23:00, farzaneh badii
                      wrote: <br>
                      &gt;     &gt; Hello <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; Adding my comments on this
                      document:  <a
                        href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>
                      &lt; <a
                        href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>&gt;
                      &lt; <a
                        href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>
                      &lt; <a
                        href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05</a>&gt;<wbr>&gt;
                      <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; 1. One major issue that I see here
                      and you might be able to easily solve it is that
                      there is no distinction between user facing
                      protocols and other protocols. For example, you
                      ask for accessibility and consideration of culture
                      etc. Are you asking all the protocols to be
                      provided in multiple languages, even those that
                      only developers and implementers use and not the
                      actual users? You might want to clarify that.  <br>
                      &gt;     &gt; <br>
                      &gt; <br>
                      &gt;     We had a quite extensive discussion about
                      this in relation to the presentation by Ramsey
                      Nasr who create Qalb, an Arabic programming
                      language. Programmers are the most frequent
                      'users' of protocols - if we continue using only
                      latin characters and English documentation in
                      protocols we are likely to reproduce the existing
                      lack of diversity in protocol developers
                      communities. But we can make the text on this
                      clearer as well! <br>
                      &gt; <br>
                      &gt;     &gt; 2.section 3.3.1 on connectivity, you
                      mention that "considering the fact that network
                      quality and conditions vary across geography and
                      time it is also important to design protocols such
                      that they are reliable even on low bandwidth ...".
                      Then in your example you say: Middleboxes
                      (including NAT).... can create potential for
                      abuse. NAT is a Network Address Translation
                      protocol. I don't think it has anything to do with
                      bandwidth. In this example you also mention CDNs.
                      Are you suggesting that the developer should not
                      consider "Middleboxes" protocols? I think you need
                      to work on the example of section 3.3.1 some more
                      to make it clearer.  <br>
                      &gt;     &gt; <br>
                      &gt; <br>
                      &gt;     Excellent point - we'll address this in a
                      future version. <br>
                      &gt; <br>
                      &gt;     &gt; 3. section 3.3.20 remedy and
                      attribution  <br>
                      &gt;     &gt; This section worries me. As a 
                      scholar I have worked on cyber attribution to some
                      extent and believe in general when we have the
                      right processes in place, attribution is very
                      important and can hold cyber-attackers
                      accountable. I am aware of some of the attribution
                      processes and unfortunately some threat
                      intelligence firms and open source intelligence
                      organizations can violate the privacy of
                      individuals by profiling them. Also, uncontrolled
                      attribution mechanisms can lead to
                      frivolous intellectual property claims. Both some
                      threat intelligence firms and IP firms have used
                      WHOIS extensively in their favor to attribute
                      cybersecurity attacks and bring forward IP claims.
                      WHOIS protocol did not have the intention to
                      actually identify organizations and individuals,
                      but to make them "contactable".and it was still
                      used and mined for so many years and those who
                      have abused WHOIS have not been held
                      accountable.When you suggest they consider
                      "attribution" when developing protocols it <br>
                      &gt;     &gt; concerns me because it is not enough
                      that you limit attribution to organizations and
                      states. These kinds of attributions can be used
                      against individuals and until we do not have the
                      right preserving processes to put in place for
                      those who want to be in the attribution business,
                      rights of the individual can be at risk. there are
                      very privacy conscious cybersecurity researchers
                      out there but unfortunately that does not ensure a
                      systematic practice of attribution in a fair
                      manner. And you mention attribution to
                      associations is fine and may not directly
                      negatively impact human rights. Associations can
                      themselves be at risk of frivolous attacks and
                      frivolous attribution. I am concerned about this
                      paragraph. I think we should have a conversation
                      about it. <br>
                      &gt;     &gt; <br>
                      &gt; <br>
                      &gt;     In the proposed text I tried to capture
                      the consensus that emerged from the extensive
                      discussion that was had on this list. Do you have
                      concrete suggestions on how to better capture that
                      conensensus? I am afraid we would go back and
                      repeat the same discussion. <br>
                      &gt; <br>
                      &gt;     &gt; 4. Nice to see that you mention DoH.
                      It's a great privacy preserving protocol.  <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt; <br>
                      &gt;     Thanks! <br>
                      &gt; <br>
                      &gt;     Niels <br>
                      &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; Farzaneh <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; On Sat, Jan 30, 2021 at 10:35 AM
                      Corinne Cath &lt; <a
                        href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                      &lt;mailto: <a
                        href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;
                      &lt;mailto: <a
                        href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                      &lt;mailto: <a
                        href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;&gt;&gt;
                      wrote: <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     Hi all, <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     I trust this email finds you
                      well. I did a review of the draft, from my
                      perspective as an academic. Take it as you please.
                      My main concern is that some of the language reads
                      a bit deterministic (as, I know so does RFC 8280).
                      It means that a lot of onus is put on the impact
                      of a protocol, as opposed the role of the
                      individuals that write them.  <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     I think through out the
                      document, it would be interesting (especially in
                      section 1 through 3.2.5) to see if you can rewrite
                      such that you speak more directly to the protocol
                      developers. I think that section 3.3 does that
                      well, in terms of the tone it takes. As it clearly
                      connects the actions of protocol developers to
                      their potential outcomes.  <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     Hope this is helpful!  <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     Kind regards,  <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     Corinne <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     -----------------------------<wbr>----
                      <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     *1. Introduction* <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     "It provides questions engineers
                      should ask <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;        themselves when developing or
                      improving protocols if they want to <br>
                      &gt;     &gt;        understand their potential
                      human rights impact." <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     &gt;&gt; maybe if they want to
                      understand potential human rights concerns? Impact
                      seems a little deterministic, as you also mention
                      in the next sentence, I wonder if you can prove
                      such direct impact between protocol development in
                      the IETF and impact on human rights. <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     "The research establishes <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;        that human rights relate to
                      standards and protocols, and offers a <br>
                      &gt;     &gt;        common vocabulary of
                      technical concepts that impact human rights and <br>
                      &gt;     &gt;        how these technical concepts
                      can be combined to ensure that the <br>
                      &gt;     &gt;        Internet remains an enabling
                      environment for human rights." <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     &gt;&gt; same comment for the
                      word impact, perhaps shape? influence? etc. <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;           3.1 &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.1</a>
                      &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.1"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.1</a>&gt;&gt;.
                      Human rights threats <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;      "Protocols and standards can
                      harm or enable the right to freedom of <br>
                      &gt;     &gt;        expression, right to
                      non-discrimination, right to equal protection, <br>
                      &gt;     &gt;        right to participate in
                      cultural life, arts and science, right to <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     freedom of assembly and
                      association, and the right to security. " <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     &gt;&gt; again, deterministic
                      language. Perhaps soften or add more concrete
                      examples for context, that draw from current IETF
                      discussions/standards. <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;           3.3 &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.3</a>
                      &lt; <a
href="https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#section-3.3"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-irtf-hrpc-guidelines-05#<wbr>section-3.3</a>&gt;&gt;.
                      Guidelines for human rights considerations <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     again, use of the word impact in
                      the introduction. <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     -- <br>
                      &gt;     &gt;     Corinne Cath - Speth <br>
                      &gt;     &gt;     Ph.D. Candidate, Oxford Internet
                      Institute &amp; Alan Turing Institute <br>
                      &gt;     &gt; <br>
                      &gt;     &gt;     Web: <a
                        href="http://www.oii.ox.ac.uk/people/corinne-cath"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">www.oii.ox.ac.uk/people/<wbr>corinne-cath</a>
                      &lt; <a
                        href="http://www.oii.ox.ac.uk/people/corinne-cath"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>&gt;
                      &lt; <a
                        href="http://www.oii.ox.ac.uk/people/corinne-cath"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>
                      &lt; <a
                        href="http://www.oii.ox.ac.uk/people/corinne-cath"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">http://www.oii.ox.ac.uk/<wbr>people/corinne-cath</a>&gt;&gt;
                      <br>
                      &gt;     &gt;     Email: <a
                        href="mailto:ccath@turing.ac.uk" target="_blank"
                        moz-do-not-send="true">ccath@turing.ac.uk</a>
                      &lt;mailto: <a href="mailto:ccath@turing.ac.uk"
                        target="_blank" moz-do-not-send="true">ccath@turing.ac.uk</a>&gt;
                      &lt;mailto: <a href="mailto:ccath@turing.ac.uk"
                        target="_blank" moz-do-not-send="true">ccath@turing.ac.uk</a>
                      &lt;mailto: <a href="mailto:ccath@turing.ac.uk"
                        target="_blank" moz-do-not-send="true">ccath@turing.ac.uk</a>&gt;&gt;
                      &amp; <a href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                      &lt;mailto: <a
                        href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;
                      &lt;mailto: <a
                        href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>
                      &lt;mailto: <a
                        href="mailto:corinnecath@gmail.com"
                        target="_blank" moz-do-not-send="true">corinnecath@gmail.com</a>&gt;&gt;
                      <br>
                      &gt;     &gt;     Twitter: @C_CS <br>
                      &gt;     &gt;     _____________________________<wbr>__________________
                      <br>
                      &gt;     &gt;     hrpc mailing list <br>
                      &gt;     &gt;      <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>
                      &lt;mailto: <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;
                      &lt;mailto: <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>
                      &lt;mailto: <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;&gt;
                      <br>
                      &gt;     &gt;      <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                      &lt; <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
                      &lt; <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                      &lt; <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;&gt;
                      <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; <br>
                      &gt;     &gt; ______________________________<wbr>_________________
                      <br>
                      &gt;     &gt; hrpc mailing list <br>
                      &gt;     &gt; <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>
                      &lt;mailto: <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;
                      <br>
                      &gt;     &gt; <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                      &lt; <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
                      <br>
                      &gt;     &gt; <br>
                      &gt; <br>
                      &gt;     -- <br>
                      &gt;     Niels ten Oever, PhD <br>
                      &gt;     Postdoctoral Researcher - Media Studies
                      Department - University of Amsterdam <br>
                      &gt;     Postdoctoral Research Fellow -
                      Communications Department - Texas A&amp;M
                      University <br>
                      &gt;     Research Fellow - Centre for Internet and
                      Human Rights - European University Viadrina <br>
                      &gt;     Associated Scholar - Centro de Tecnologia
                      e Sociedade - Fundação Getúlio Vargas <br>
                      &gt; <br>
                      &gt;     W: <a href="https://nielstenoever.net"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://nielstenoever.net</a>
                      &lt; <a href="https://nielstenoever.net"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://nielstenoever.net</a>&gt;
                      <br>
                      &gt;     E: <a
                        href="mailto:mail@nielstenoever.net"
                        target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>
                      &lt;mailto: <a
                        href="mailto:mail@nielstenoever.net"
                        target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>&gt;
                      <br>
                      &gt;     T: @nielstenoever <br>
                      &gt;     P/S/WA: +31629051853 <br>
                      &gt;     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8
                      3F3A 468A C8B3 <br>
                      &gt; <br>
                      &gt;     Read my dissertation 'Wired Norms' here:
                      <a
                        href="https://pure.uva.nl/ws/files/50781961/Thesis.pdf"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.pdf</a>
                      &lt; <a
                        href="https://pure.uva.nl/ws/files/50781961/Thesis.pdf"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.pdf</a>&gt;
                      <br>
                      &gt;     _____________________________<wbr>__________________
                      <br>
                      &gt;     hrpc mailing list <br>
                      &gt;      <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>
                      &lt;mailto: <a href="mailto:hrpc@irtf.org"
                        target="_blank" moz-do-not-send="true">hrpc@irtf.org</a>&gt;
                      <br>
                      &gt;      <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>
                      &lt; <a
                        href="https://www.irtf.org/mailman/listinfo/hrpc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://www.irtf.org/mailman/<wbr>listinfo/hrpc</a>&gt;
                      <br>
                      &gt; <br>
                      <br>
                      -- <br>
                      Niels ten Oever, PhD <br>
                      Postdoctoral Researcher - Media Studies Department
                      - University of Amsterdam <br>
                      Postdoctoral Research Fellow - Communications
                      Department - Texas A&amp;M University <br>
                      Research Fellow - Centre for Internet and Human
                      Rights - European University Viadrina <br>
                      Associated Scholar - Centro de Tecnologia e
                      Sociedade - Fundação Getúlio Vargas <br>
                      <br>
                      W: <a href="https://nielstenoever.net"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://nielstenoever.net</a>
                      <br>
                      E: <a href="mailto:mail@nielstenoever.net"
                        target="_blank" moz-do-not-send="true">mail@nielstenoever.net</a>
                      <br>
                      T: @nielstenoever <br>
                      P/S/WA: +31629051853 <br>
                      PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A
                      C8B3 <br>
                      <br>
                      Read my dissertation 'Wired Norms' here: <a
                        href="https://pure.uva.nl/ws/files/50781961/Thesis.pdf"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://pure.uva.nl/ws/files/<wbr>50781961/Thesis.pdf</a>
                      <br>
                    </blockquote>
                  </div>
                </blockquote>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
      <br>
      <br>
      -- <br>
      <div dir="ltr">
        <div><font face="verdana, sans-serif">Farzaneh </font></div>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
hrpc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hrpc@irtf.org">hrpc@irtf.org</a>
<a class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/hrpc">https://www.irtf.org/mailman/listinfo/hrpc</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780</pre>
  </body>
</html>
--------------SAKqcmLEH7s739UXLpRX1mK6--


From nobody Tue Feb  2 22:35:31 2021
Return-Path: <avri@apc.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 2BE7D3A14B9 for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 22:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 ca43aMJZLeOB for <hrpc@ietfa.amsl.com>; Tue,  2 Feb 2021 22:35:26 -0800 (PST)
Received: from mail.gn.apc.org (mail.gn.apc.org [37.220.108.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 527EB3A14B8 for <hrpc@irtf.org>; Tue,  2 Feb 2021 22:35:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.gn.apc.org (Postfix) with ESMTP id 08BCE2039125 for <hrpc@irtf.org>; Wed,  3 Feb 2021 06:35:24 +0000 (GMT)
X-Virus-Scanned: by amavisd-new at mail.gn.apc.org
Received: from mail.gn.apc.org ([127.0.0.1]) by localhost (mail.gn.apc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKvGe0dR213P; Wed,  3 Feb 2021 06:35:21 +0000 (GMT)
Received: from anonymous ([10.254.254.3])  (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: avri) by mail.gn.apc.org (Postfix) with ESMTPSA id AEAC72039079; Wed,  3 Feb 2021 06:35:20 +0000 (GMT)
To: hrpc@irtf.org
References: <mailman.1401.1612260415.7093.hrpc@irtf.org> <CAB2unbMpgo4nDSDYW=gx8Xsts8gKiBEs0NyzC2JBd+19Npd0Ew@mail.gmail.com> <20210202141525.6b7cldgdge45e3tu@crankycanuck.ca> <ece7d9fa-c39e-7c2b-21e3-6b5b8ac530d9@cdt.org>
From: avri doria <avri@apc.org>
Message-ID: <e76359e3-2e4e-71f7-01df-00e0f1993d8c@apc.org>
Date: Wed, 3 Feb 2021 01:35:19 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <ece7d9fa-c39e-7c2b-21e3-6b5b8ac530d9@cdt.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/OJsp_0rjBqI139l6by3Gwg7Odys>
Subject: Re: [hrpc] Consensus and the RG (Was Re: hrpc Digest, Vol 71, Issue 7)
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: Wed, 03 Feb 2021 06:35:29 -0000

Hi,

I believe that any RFC published by the HRPC RG should have rough
consensus for publication. That does not mean that all points in the
draft are consensus points, but there should be consensus for
publication as a complete document, though there may be some who do not
agree (the proverbial, in the rough).  This is the same criteria we used
for RFC8280.  When both co-chairs believe there is such consensus my
intention is that we confirm that with the RG and if confirmed, then
proceed to IESG review.

At this point I do not think we are there yet.

According to my understanding of the IRSG guidelines, we will need to
add a sentence or two indicating the process we went through and the
degree to which there is consensus.  We will also need to add a line to
the abstract indicating that it is an IRTF RG product. I will provide
text for these at the appropriate time.

I appreciate the efforts the author/editors are going through to try and
resolve the issues that people are bringing up. I also appreciate the
fact that there have been serious reviews with extended comments and
that there is a discussion on remaining issues.

Thanks

avri

(acting as shepherd for the document)


On 2/2/2021 11:49 AM, Mallory Knodel wrote:
> On 2/2/21 9:15 AM, Andrew Sullivan wrote:
>
>> (Still work for ISOC, this is still just my own opinion.)
>>
>> On Tue, Feb 02, 2021 at 04:38:50AM -0600, Sandra Braman wrote:
>>
>>> One of the problems with determining a "consensus," of course, is the
>>> question of who decides whether or not one has been achieved.
>>
>> There is an RFC about this that was an IETF product, so at least there
>> is something to work on from the IETF context:
>> https://tools.ietf.org/html/rfc7282.  Of course, this RG isn't a part
>> of the IETF and has its own rules, but I understood the Chairs
>> previously to have said that they were following IETF process as
>> closely as possible for a RG to do.  I have previously expressed my
>> doubts about how well that could work, so I will refrain from
>> repeating myself.
>
> Only to clarify that as co-chair I am not in favour of a blanket rule
> for all HRPC drafts to reach consensus before publication. I think it
> makes sense in some cases but not in others. And to set the bar so
> high for research can disincentivise good, exploratory work. (I've
> said all of this many times before, nothing new just reminding folks
> of my position).
>
> That said I do feel that draft-guidelines, because it's based on RFC
> 8280 and meant to be usefully applied to IETF documents, should be at
> the end of the spectrum of *more* consensus than, say, draft-political
> or draft-feminism.
>
> I also think that so far Gurshabad and Niels have done a stellar job
> of building this draft upon a strong foundation of group consensus. It
> was written with input from multiple people, notably those who have
> attempted to use it and they've been responsive to any and all
> feedback so far. It's a very strong document because of it.
>
> Looking forward to the next version,
>
> -Mallory
>


From nobody Thu Feb  4 07:24:24 2021
Return-Path: <braman@tamu.edu>
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 71E053A15B4 for <hrpc@ietfa.amsl.com>; Thu,  4 Feb 2021 07:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 yxLHY5DiWjFl for <hrpc@ietfa.amsl.com>; Thu,  4 Feb 2021 07:24:18 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 7E9943A15AD for <hrpc@irtf.org>; Thu,  4 Feb 2021 07:24:18 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id g9so2935680ilc.3 for <hrpc@irtf.org>; Thu, 04 Feb 2021 07:24:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=S0ukz/qJ0orbfXA2sLi+OweGqetJ3y6oxAayNersnjk=; b=FY3H5GMIAAYHExqZod6g7QAmmYW72Rvtg8/SQjgJa3C/4FENDmdpqFX7NX4GIwOBIn kkVGj4v5pJjaENUrDRiU7Ng9NzBcSbPqUuQjaDPJGmJ7HkQ0sYdp720ATqiv10wSLUzY yBfCrMbDt+4yI0yzhFnZz4usUl1LsWatauTTXOaV7PQwDjLaFntG3Tc2opTEqfHEaznF 96z7r4Uazl9C35uWtnWfITK+2Yj6KFsDCDSgnWSfDAFRfzbOoBh6935ZcioAnIvgfk8N Mf6cVqvqMUCKERWvb9dsVQGb9jx4ik0QIi8LhGt+y5FGORO0EDdR/5QLqI0YatBYKNCi F0Lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=S0ukz/qJ0orbfXA2sLi+OweGqetJ3y6oxAayNersnjk=; b=dkPydvcX3cwKADBTdOV4hSWfNtROiE6KLPlfjeLuio/SGRNTOnZkX16YXcEp7GsKSc Mc9HGZ7LRkp2+bpNtntfulVNQBNpQx7D/yjR2geovTVPr82ldP3LMCIUBEJEeb0fotjq /qlrvUMAVrgnXd9CzjwKUm0FDzkDCYxBlGaLy91fenz9lTvtcUR2285cr1itqUi6n19I EoP10hipZNzshwPYhbZ+e54H8scotDSw2Dj98T3Xj5SSNkeOs7S+9ax0Ik5/ybzD/Bwm MRc65Nza7xw8qlh2NBd6giM1XHCD019rEjHt/RbvvDPkqVck0tRowSnVhWYAV9ysh2Ei pZ2w==
X-Gm-Message-State: AOAM533Ez2D7amykrRjBwGJTTY9QkbAouuVKzqAuvTxHavNqi5ekwnWZ NcuiXgxTG8zPuyap16fYKlFoDRKu/UD7DA0yIOIjD+xC951YdA==
X-Google-Smtp-Source: ABdhPJxR6AALaglUmd47oF8hAaFI6R05qH1z3WGLH2r8jql4tMlEHMOHQIjGfzq8Wuht3/wDxxc5uWihRcF112hb+qE=
X-Received: by 2002:a05:6e02:138f:: with SMTP id d15mr7372828ilo.303.1612452257074;  Thu, 04 Feb 2021 07:24:17 -0800 (PST)
MIME-Version: 1.0
References: <mailman.46.1612382408.25140.hrpc@irtf.org>
In-Reply-To: <mailman.46.1612382408.25140.hrpc@irtf.org>
From: Sandra Braman <braman@tamu.edu>
Date: Thu, 4 Feb 2021 09:25:58 -0600
Message-ID: <CAB2unbPHs6by3KQJef5ye_k7kSq79XJaXaezMpYoeTrV900Gdg@mail.gmail.com>
To: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="00000000000000298205ba844c6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/9doRZm_U66UkZH99f2ckTlyGFYc>
Subject: Re: [hrpc] hrpc Digest, Vol 71, Issue 11
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, 04 Feb 2021 15:24:23 -0000

--00000000000000298205ba844c6c
Content-Type: text/plain; charset="UTF-8"

Thanks, Mallory and Avri.  Having gotten involved with those who are
working on design of quantum networks -- who are explicitly sensitive to
and thinking about social impact and polilcy issues even at this very early
stage of the design process in ways that have been incorporated into the
design process itself -- am aware that whatever is done in this terrain for
the Internet also has implications for what is to come using other
technologies, shaping expectations in path-dependent ways.  Back at you
soon with substantive comments.

Sandra Braman


On Wed, Feb 3, 2021 at 2:01 PM <hrpc-request@irtf.org> wrote:

> Send hrpc mailing list submissions to
>         hrpc@irtf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMsoU2CAaXKYYtf2Ng$
> or, via email, send a message with subject or body 'help' to
>         hrpc-request@irtf.org
>
> You can reach the person managing the list at
>         hrpc-owner@irtf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of hrpc digest..."
> Today's Topics:
>
>    1. Re: Consensus and the RG (Was Re: hrpc Digest, Vol 71, Issue
>       7) (avri doria)
>
>
>
> ---------- Forwarded message ----------
> From: avri doria <avri@apc.org>
> To: hrpc@irtf.org
> Cc:
> Bcc:
> Date: Wed, 3 Feb 2021 01:35:19 -0500
> Subject: Re: [hrpc] Consensus and the RG (Was Re: hrpc Digest, Vol 71,
> Issue 7)
> Hi,
>
> I believe that any RFC published by the HRPC RG should have rough
> consensus for publication. That does not mean that all points in the
> draft are consensus points, but there should be consensus for
> publication as a complete document, though there may be some who do not
> agree (the proverbial, in the rough).  This is the same criteria we used
> for RFC8280.  When both co-chairs believe there is such consensus my
> intention is that we confirm that with the RG and if confirmed, then
> proceed to IESG review.
>
> At this point I do not think we are there yet.
>
> According to my understanding of the IRSG guidelines, we will need to
> add a sentence or two indicating the process we went through and the
> degree to which there is consensus.  We will also need to add a line to
> the abstract indicating that it is an IRTF RG product. I will provide
> text for these at the appropriate time.
>
> I appreciate the efforts the author/editors are going through to try and
> resolve the issues that people are bringing up. I also appreciate the
> fact that there have been serious reviews with extended comments and
> that there is a discussion on remaining issues.
>
> Thanks
>
> avri
>
> (acting as shepherd for the document)
>
>
> On 2/2/2021 11:49 AM, Mallory Knodel wrote:
> > On 2/2/21 9:15 AM, Andrew Sullivan wrote:
> >
> >> (Still work for ISOC, this is still just my own opinion.)
> >>
> >> On Tue, Feb 02, 2021 at 04:38:50AM -0600, Sandra Braman wrote:
> >>
> >>> One of the problems with determining a "consensus," of course, is the
> >>> question of who decides whether or not one has been achieved.
> >>
> >> There is an RFC about this that was an IETF product, so at least there
> >> is something to work on from the IETF context:
> >>
> https://urldefense.com/v3/__https://tools.ietf.org/html/rfc7282__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMsoU2CAaXK2TP6ywA$
> .  Of course, this RG isn't a part
> >> of the IETF and has its own rules, but I understood the Chairs
> >> previously to have said that they were following IETF process as
> >> closely as possible for a RG to do.  I have previously expressed my
> >> doubts about how well that could work, so I will refrain from
> >> repeating myself.
> >
> > Only to clarify that as co-chair I am not in favour of a blanket rule
> > for all HRPC drafts to reach consensus before publication. I think it
> > makes sense in some cases but not in others. And to set the bar so
> > high for research can disincentivise good, exploratory work. (I've
> > said all of this many times before, nothing new just reminding folks
> > of my position).
> >
> > That said I do feel that draft-guidelines, because it's based on RFC
> > 8280 and meant to be usefully applied to IETF documents, should be at
> > the end of the spectrum of *more* consensus than, say, draft-political
> > or draft-feminism.
> >
> > I also think that so far Gurshabad and Niels have done a stellar job
> > of building this draft upon a strong foundation of group consensus. It
> > was written with input from multiple people, notably those who have
> > attempted to use it and they've been responsive to any and all
> > feedback so far. It's a very strong document because of it.
> >
> > Looking forward to the next version,
> >
> > -Mallory
> >
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMsoU2CAaXKYYtf2Ng$
>

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

<div dir=3D"ltr">Thanks, Mallory and Avri.=C2=A0 Having gotten involved wit=
h those who are working on design of quantum networks -- who are explicitly=
 sensitive to and thinking about social impact and polilcy issues even at t=
his very early stage of the design process in ways that have been incorpora=
ted into the design process itself -- am aware that whatever is done in thi=
s terrain for the Internet also has implications for what is to come using =
other technologies, shaping expectations in path-dependent ways.=C2=A0 Back=
 at you soon with substantive comments.<div><br></div><div>Sandra Braman</d=
iv><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Wed, Feb 3, 2021 at 2:01 PM &lt;<a href=3D"mailto:hrpc=
-request@irtf.org">hrpc-request@irtf.org</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">Send hrpc mailing list submissions =
to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc@irtf.org" target=3D"_bla=
nk">hrpc@irtf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://urldefense.com/v3/__https://=
www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5yW6Pgs_b=
iC7Gllk1zOa3jTYmqLu2ZCwMsoU2CAaXKYYtf2Ng$" rel=3D"noreferrer" target=3D"_bl=
ank">https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc=
__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMsoU2CAaXKY=
Ytf2Ng$</a> <br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-request@irtf.org" target=
=3D"_blank">hrpc-request@irtf.org</a><br>
<br>
You can reach the person managing the list at<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-owner@irtf.org" target=
=3D"_blank">hrpc-owner@irtf.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of hrpc digest...&quot;<br>
Today&#39;s Topics:<br>
<br>
=C2=A0 =C2=A01. Re: Consensus and the RG (Was Re: hrpc Digest, Vol 71, Issu=
e<br>
=C2=A0 =C2=A0 =C2=A0 7) (avri doria)<br>
<br><br><br>---------- Forwarded message ----------<br>From:=C2=A0avri dori=
a &lt;<a href=3D"mailto:avri@apc.org" target=3D"_blank">avri@apc.org</a>&gt=
;<br>To:=C2=A0<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.=
org</a><br>Cc:=C2=A0<br>Bcc:=C2=A0<br>Date:=C2=A0Wed, 3 Feb 2021 01:35:19 -=
0500<br>Subject:=C2=A0Re: [hrpc] Consensus and the RG (Was Re: hrpc Digest,=
 Vol 71, Issue 7)<br>Hi,<br>
<br>
I believe that any RFC published by the HRPC RG should have rough<br>
consensus for publication. That does not mean that all points in the<br>
draft are consensus points, but there should be consensus for<br>
publication as a complete document, though there may be some who do not<br>
agree (the proverbial, in the rough).=C2=A0 This is the same criteria we us=
ed<br>
for RFC8280.=C2=A0 When both co-chairs believe there is such consensus my<b=
r>
intention is that we confirm that with the RG and if confirmed, then<br>
proceed to IESG review.<br>
<br>
At this point I do not think we are there yet.<br>
<br>
According to my understanding of the IRSG guidelines, we will need to<br>
add a sentence or two indicating the process we went through and the<br>
degree to which there is consensus.=C2=A0 We will also need to add a line t=
o<br>
the abstract indicating that it is an IRTF RG product. I will provide<br>
text for these at the appropriate time.<br>
<br>
I appreciate the efforts the author/editors are going through to try and<br=
>
resolve the issues that people are bringing up. I also appreciate the<br>
fact that there have been serious reviews with extended comments and<br>
that there is a discussion on remaining issues.<br>
<br>
Thanks<br>
<br>
avri<br>
<br>
(acting as shepherd for the document)<br>
<br>
<br>
On 2/2/2021 11:49 AM, Mallory Knodel wrote:<br>
&gt; On 2/2/21 9:15 AM, Andrew Sullivan wrote:<br>
&gt;<br>
&gt;&gt; (Still work for ISOC, this is still just my own opinion.)<br>
&gt;&gt;<br>
&gt;&gt; On Tue, Feb 02, 2021 at 04:38:50AM -0600, Sandra Braman wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; One of the problems with determining a &quot;consensus,&quot; =
of course, is the<br>
&gt;&gt;&gt; question of who decides whether or not one has been achieved.<=
br>
&gt;&gt;<br>
&gt;&gt; There is an RFC about this that was an IETF product, so at least t=
here<br>
&gt;&gt; is something to work on from the IETF context:<br>
&gt;&gt; <a href=3D"https://urldefense.com/v3/__https://tools.ietf.org/html=
/rfc7282__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMso=
U2CAaXK2TP6ywA$" rel=3D"noreferrer" target=3D"_blank">https://urldefense.co=
m/v3/__https://tools.ietf.org/html/rfc7282__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5=
yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMsoU2CAaXK2TP6ywA$</a> .=C2=A0 Of course, th=
is RG isn&#39;t a part<br>
&gt;&gt; of the IETF and has its own rules, but I understood the Chairs<br>
&gt;&gt; previously to have said that they were following IETF process as<b=
r>
&gt;&gt; closely as possible for a RG to do.=C2=A0 I have previously expres=
sed my<br>
&gt;&gt; doubts about how well that could work, so I will refrain from<br>
&gt;&gt; repeating myself.<br>
&gt;<br>
&gt; Only to clarify that as co-chair I am not in favour of a blanket rule<=
br>
&gt; for all HRPC drafts to reach consensus before publication. I think it<=
br>
&gt; makes sense in some cases but not in others. And to set the bar so<br>
&gt; high for research can disincentivise good, exploratory work. (I&#39;ve=
<br>
&gt; said all of this many times before, nothing new just reminding folks<b=
r>
&gt; of my position).<br>
&gt;<br>
&gt; That said I do feel that draft-guidelines, because it&#39;s based on R=
FC<br>
&gt; 8280 and meant to be usefully applied to IETF documents, should be at<=
br>
&gt; the end of the spectrum of *more* consensus than, say, draft-political=
<br>
&gt; or draft-feminism.<br>
&gt;<br>
&gt; I also think that so far Gurshabad and Niels have done a stellar job<b=
r>
&gt; of building this draft upon a strong foundation of group consensus. It=
<br>
&gt; was written with input from multiple people, notably those who have<br=
>
&gt; attempted to use it and they&#39;ve been responsive to any and all<br>
&gt; feedback so far. It&#39;s a very strong document because of it.<br>
&gt;<br>
&gt; Looking forward to the next version,<br>
&gt;<br>
&gt; -Mallory<br>
&gt;<br>
<br>
<br>
_______________________________________________<br>
hrpc mailing list<br>
<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a><br>
<a href=3D"https://urldefense.com/v3/__https://www.irtf.org/mailman/listinf=
o/hrpc__;!!KwNVnqRv!VyGcWah21PtOvru_Xz5yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMsoU2=
CAaXKYYtf2Ng$" rel=3D"noreferrer" target=3D"_blank">https://urldefense.com/=
v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!VyGcWah21PtOvr=
u_Xz5yW6Pgs_biC7Gllk1zOa3jTYmqLu2ZCwMsoU2CAaXKYYtf2Ng$</a> <br>
</blockquote></div>

--00000000000000298205ba844c6c--


From nobody Sat Feb  6 00:34:18 2021
Return-Path: <braman@tamu.edu>
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 B44233A0D07 for <hrpc@ietfa.amsl.com>; Sat,  6 Feb 2021 00:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 4upv5Mr_2UGx for <hrpc@ietfa.amsl.com>; Sat,  6 Feb 2021 00:34:12 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 8E4453A0D66 for <hrpc@irtf.org>; Sat,  6 Feb 2021 00:34:11 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id q7so9785238iob.0 for <hrpc@irtf.org>; Sat, 06 Feb 2021 00:34:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=9KlaQRE/S2RxTmR/AWP0l548b2GslD6RQ2NN7gSI1wU=; b=XDR10s4VMYUTk091866wAORvkYDnJV54XbiOznLD5kOvybZtLsWKml8DuFPInWHZwE ueJNg0iV8rM/Gh6wtfDyOBH9fdtc+G6+dOHaCCQhuQ3hxdKFJgWSjtAjDC772GGQs4M2 xB6faoSBuWmeU1BjtBnXhX5iLmUZfICKLK+afv7r47QjCwgdauuciiRC0dpfhaAi8k2E W/5YxUa02AUCP+QDXgK/Io8mQVtpTPAKioTlz0AqfjqWFrcMxw125BBNql8NfhYNuugj 4tXHRtEjnJW8coZmEzGjCSNYLnGoM3nwKE7wUWtGWUZMHnfge909ZO6KgN0Yss/jOfhv 9ayw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9KlaQRE/S2RxTmR/AWP0l548b2GslD6RQ2NN7gSI1wU=; b=ZJPTUZznjjyoD9AtUI7UzeqSpuBlmHdyj0mQtc1px2Z2RxiEry8wQ/asz9Jz5CybRQ 8e6m321CpBTbDPeOq+0b+mTOjMOs30Ka6LrtaDE+/66fKmxN8Co2/J3PwhTro8AIa2O7 CGMY6DX0GXV8p2OojiQQydtkmmE0TftHFahMtVY+gGuI8bIIbr99EgztAOinJyAMmIj8 qKiOCFF04P5nCdnYpH8P/N8NX8espKLgmNrzkU8GKgz/wyj4+JaItv0cRNFvVhS3C7oG wzJwhxj0A6keGZUb+TmHQ3A032wpukpc9WXM7MoD2Z0vCjlvsEa7vJuHdbKFV6MfqpqZ NcFQ==
X-Gm-Message-State: AOAM530pjvB13w7IFTGqSH0a3JdmHNmYHmeiDjHAax94GM4vXDkkHsuO s5BIbDIx31FC5p++wkOP7GWc1AgTehCfR62aXcjKmD/im+l3aiKa
X-Google-Smtp-Source: ABdhPJwhEnS7jZVb1QbIO03VpG4L/yNSEIbn74BaGo6hu+pKSy9YVfSE1qzOk5CpnLSMhu/J7emUZcDleMBXNpd6cns=
X-Received: by 2002:a05:6602:24cb:: with SMTP id h11mr7786985ioe.79.1612600449953;  Sat, 06 Feb 2021 00:34:09 -0800 (PST)
MIME-Version: 1.0
From: Sandra Braman <braman@tamu.edu>
Date: Sat, 6 Feb 2021 02:35:56 -0600
Message-ID: <CAB2unbNHN6SnEWAmjj09EWL7e=NKhkcUe5vKSy2tXsje50HVmA@mail.gmail.com>
To: "hrpc@irtf.org" <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000fc086105baa6cc48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/8s_4c3DtRZQqTXcnnuFrSV2vyiM>
Subject: [hrpc] comments, draft association
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: Sat, 06 Feb 2021 08:34:17 -0000

--000000000000fc086105baa6cc48
Content-Type: text/plain; charset="UTF-8"

First, to the authors, congratulations on this piece.  Clearly a lot of
effort has gone into this.  Following are some thoughts regarding how this
piece could be strengthened if it is to serve as an informational RFC
rather than a journal article, organized by topic.  It is a background
assumption of these comments that the document is intended to have utility
to those involved in protocol design work via the IETF.  Long email alert.

Sandra Braman

----------------------------------------------------------------------------------

*Legal authorities used as justification*

*International Treaties*

The international treaties discussed in this draft are not a part of the
scholarly literature covered in literature reviews, but the legal
authorities on the basis of which claims made here are justified.  Although
I agree with the authors that this is not the place for a comprehensive
discussion and synthesis of the scholarly literature, coverage of the
pertinent treaty provisions *should* be comprehensive.  Treaty provisions
only matter, though, where treaties have been ratified.  It would also be
useful to the reader to know the extent to which these provisions have been
interpreted in courts in cases that have come their way involving assembly
and association.

Breaking out a paragraph for each treaty provision would highlight each for
the reader and provide the space to include information on how many
countries have actually ratified and thus are bound by the treaty, the
kinds of conflicts that have arisen historically under each provision in
the digital environment, and how those conflicts have been resolved.
Organizing the provisions chronologically by when the treaties were
initially signed (signing treaties and ratifying them are two separate
steps) would offer the authors an opportunity to present a sense of a
rising tide of appreciation of the importance of protecting the rights of
assembly and association.

*National Laws*

There is reference to protection of the rights of assembly and association
in national constitutions and laws.  It would strengthen the argument being
made here to provide information on how many geopolitically recognized
states (that is, those recognized by the UN) protect these rights and
trends in this area.  There is discussion by American authors of American
law in the literature review, by European Union groups about European law,
and about international law -- can literature about national law by
non-American authors about non-American treatment of assembly and
association also be included?

*Jurisprudence*

The word "jurisprudence" shows up towards the close of the piece but
jurisprudence is actually not discussed here.  An analysis of how courts
have treated assembly and association in the digital environment would be
invaluable.  There is a significant scholarly literature on this (that
could usefully be expanded), but it is strongly recommended that the
authors also actually go to the court opinions, which are themselves
sources of law as well and thus included in this section of these comments.

*Corporate Social Responsibility*

The issue of the relative importance of the private sector in many of the
factors affecting the rights to assembly and association runs throughout
the document.  It is now widely recognized that, effectively, "governance"
now includes not just what governments do, but also the formal and informal
processes, rules, and practices of private sector entities; indeed, ICANN,
the IAB, and the IETF are important examples of this.  The relative
importance of third party intermediaries in facilitating, controlling, or
preventing assembly and association makes this particularly important.
Finally and far from trivially, since so many of those involved in the IETF
are employees of corporations, including attention to this would speak very
directly to them.

It would thus significantly strengthen this document to include a section
on treatment of assembly and association by those who analyze, audit, and
develop best practices (*cum* rules) for private sector entities.  What
does Ranking Digital Rights, for example, have to say about this?  Whether
such entities do or do not explicitly address association and assembly, the
reader wants to know.  This section should look both at what such auditing
and best practice-setting organizations are doing, and at the significant
literature on corporate social responsibility in the digital environment.

*Literature Review*

In my view, so few items are relied upon, with those relied upon quite
heavily, that it is inaccurate to use "literature review" as a
sub-heading.  That is particularly the case since much of the discussion in
this draft's section by that title is actually not about the literature,
but about treaties -- legal authorities, as discussed above.  My personal
preference would be to see the authors taking advantage of more of the
really strong literature in these areas (the gap between what is here and
being comprehensive is very large), but whether or not that is done, I
encourage you to drop the sub-heading. Doing so would be a form of
"defensive writing," warding off an attack before it comes from those who
know the literature in this area and know what is out there that you
haven't taken advantage of.  You can attribute ideas and information from
items you rely on without using the phrase "literature review."

*Concepts*

*Public vs Private*

The tension between the sense of public discursive space and private
ownership of the infrastructure is in the opening of this document and runs
throughout.  However, that is not a binary distinction.  Rather, there is a
spectrum of types of relationships between the two developed long before we
entered the digital world.  In addition to "ownership" as a criterion of
determining what is what, other criteria include "control of the space" and
"history of use" in US law.  (I will discuss US law here as the body of law
which I know best, and also as a body of law that has been particularly
influential globally in areas such as this, but I strongly encourage the
authors to go further in their reading to learn more about how these
distinctions are made elsewhere both by states and in the international
environment -- again, jurisprudence will be invaluable here.)

The distinction as drawn in US law includes not only spaces that are purely
public (e.g., public parks and streets) and purely private (e.g., the
home), but also those that are quasi-public and quasi-private.
Quasi-public spaces are those that are owned and controlled by the public
(the government), but are devoted to very specific uses that courts and
legislatures have said justify restrictions on speech and assembly under
certain conditions.  Jails and military bases are examples of such spaces.
Quasi-private spaces are those that are owned and controlled by private
entities, but have specific uses that are experienced as public by people.
Because of that public dimension of these spaces, owners and/or controllers
must meet certain specific requirements in order to legally restrict speech
and assembly.  Examples of such spaces include shopping malls, company
towns, and fairgrounds.  Courts use the "strict scrutiny" test in either of
these conditions when conflicts over the exercise of rights arise.  Even in
purely public environments, legal systems justify restricting speech under
the kinds of conditions brought up in this document (e.g., threats to
national security) as a question although not discussed.

The concepts of quasi-public and quasi-private space have been used in
analysis of speech and assembly rights in the digital environments.  Over
the last couple of years, additional very interesting arguments are being
put forward to claim things like social media data as public rather than
private, drawing on analogues with telecommunications regulation.  The
notion that private entities must serve as "trustees" on behalf of the
public has been used to justify regulating telecommunications companies
since at least the 1930s and is now being discussed in association with
private companies that exert significant control over what we can do
online.  The notion that data about the public should be treated as a
public resource has been put forward in analog with treatment of the
electromagnetic spectrum as a public resource used by private entities.
More can be done here.

All of this is to say that in my view this document would be much stronger
if it unpacked the public/private problem rather than just mentioning it
several times in passing, as the issue of the kind of space involved is so
often important to assembly and association issues.  One place in the text
that invites this kind of unfolding is in your definition of connectivity,
which says it is "the *extent* to which a device or network is able to
reach other devices or networks," suggesting there is a spectrum of
possibilities.

*Assembly and Association*

The authors do a nice job of opening up the question of the distinction
between assembly and association.  The danger of not being very clear about
these concepts runs through some of the cases later discussed, as you don't
want to conflate either of these concepts with simply the right to
communicate.  I encourage the authors to go a further on this front,
drawing on explicit legal formulations in international law and exemplar
national and EU law.

The US government faced great difficulty when trying to figure out who
could be held liable for the massive WikiLeaks data dump that wound up with
Chelsea Manning in prison for a long while and Julian Assange in the
Ecuadorian Embassy in London.  Since autonomous networks don't exist as a
legal subject, efforts to determine accountability ranged from Manning only
all the way through to everyone who had looked at a tweet about the case (
https://ijoc.org/index.php/ijoc/article/view/2668).

You will want to conclude your discussion of assembly and association with
clear rules for how you would distinguish assembly from association in the
digital environment.  Which is WikiLeaks, given the shifting and anonymous
membership?  The distinction between the two matters for how each is
treated by legal systems.  In the case of the Jan. 6, 2021, event at the US
Capitol, legal matters are proceeding with great care to ensure that people
who assembled in the space but were not a part of an association committed
to violence are not treated as if they were a part of that association.
Legal liability for actions goes up in US law, and I'm sure under many
bodies of law, where there is association.  Thus the importance of
"conspiracy," "racketeering," and "collusion" as terms of importance in
resolving legal cases involving, in turn, illegal violent political action,
crime, and competition/antitrust law.

*Cases*

Any selection of cases needs justification.  The authors state at the
opening of the section discussing cases that not all of what is mentioned
is actually addressable at the protocol level that is the business of the
IETF to which this document is directed.  *By doing so, the authors provide
strong, active support for those who insist that the human rights issues
being discussed are just not the business of the IETF.*  I strongly
encourage the authors to include only cases for which they can demonstrate
the role of protocol design and network architecture.  For every such case,
the piece would be much stronger if an actual recommendation regarding
alternative choices for protocol design or network architecture are
offered. Dave Clark's *Designing an Internet* provides a superb model for
how this kind of linkage between the two kinds of concerns can be drawn.

*Writing Issues*

"Assembly" and "association" should be included among the terms defined at
the opening of the piece.

The pertinence of the cases will be more clear to the reader if you are
explicit in each one just how assembly or association are involved.

Bring the three separate notes on what the Internet is together into an
internally coherent paragraph.

The cases rely too much on quotes.

The reference list should include full citations in addition to links for
professionalism, and needs some cleaning up.

There are a number of word use, punctuation, and grammatical errors
throughout.

This draft concludes with some high-level statements and then all of a
sudden turns to introducing a new issue.  You can find a better close.

*Utility for IETF Readers*

Assuming you would like this to be actually used by IETF participants, can
you include, in the conclusion, a checklist of things that those involved
in protocol design and network architecture can actually look out for in
the course of their work?

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

<div dir=3D"ltr">First, to the authors, congratulations on this piece.=C2=
=A0 Clearly a lot of effort has gone into this.=C2=A0 Following are some th=
oughts regarding how this piece could be strengthened if it is to serve as =
an informational RFC rather than a journal article, organized by topic.=C2=
=A0 It is a background assumption of these comments that the document is in=
tended to have utility to those involved in protocol design work via the IE=
TF.=C2=A0 Long email alert.<div><br></div><div>Sandra Braman</div><div><br>=
</div><div>----------------------------------------------------------------=
------------------<br><div><br></div><div><u>Legal authorities used as just=
ification</u></div><div><br></div><div><i>International Treaties</i></div><=
div><br></div><div>The international treaties discussed in this draft are n=
ot a part of the scholarly literature covered in literature reviews, but th=
e legal authorities on the basis of which claims made here are justified.=
=C2=A0 Although I agree with the authors that this is not the place for a c=
omprehensive discussion and synthesis of the scholarly literature, coverage=
 of the pertinent treaty provisions <i>should</i> be comprehensive.=C2=A0 T=
reaty provisions only matter, though, where treaties have been ratified.=C2=
=A0 It would also be useful to the reader to know the extent to which these=
 provisions have been interpreted in courts in cases that have come their w=
ay involving assembly and association.</div><div><br></div><div>Breaking ou=
t a paragraph for each treaty provision would highlight each for the reader=
 and provide the space to include information on how many countries have ac=
tually ratified and thus are bound by the treaty, the kinds of conflicts th=
at have arisen historically under each provision in the digital environment=
, and how those conflicts have been resolved.=C2=A0 Organizing the provisio=
ns chronologically by when the treaties were initially signed (signing trea=
ties and ratifying them are two separate steps) would offer the authors an =
opportunity to present a sense of a rising tide of appreciation of the impo=
rtance of protecting the rights of assembly and association.</div><div><br>=
</div><div><i>National Laws</i></div><div><br></div><div>There is reference=
 to protection of the rights of assembly and association in national consti=
tutions and laws.=C2=A0 It would strengthen the argument being made here to=
 provide information on how many geopolitically recognized states (that is,=
 those recognized by the UN) protect these rights and trends in this area.=
=C2=A0 There is discussion by American authors of American law in the liter=
ature review, by European Union groups about European law, and about intern=
ational law -- can literature about national law by non-American authors ab=
out non-American treatment of assembly and association also be included?</d=
iv><div><br></div><div><i>Jurisprudence</i></div><div><i><br></i></div><div=
>The word &quot;jurisprudence&quot; shows up towards the close of the piece=
 but jurisprudence is actually not discussed here.=C2=A0 An analysis of how=
 courts have treated assembly and association in the digital environment wo=
uld be invaluable.=C2=A0 There is a significant scholarly literature on thi=
s (that could usefully be expanded), but it is strongly recommended that th=
e authors also actually go to the court opinions, which are themselves sour=
ces of law as well and thus included in this section of these comments.</di=
v><div><br></div><div><u>Corporate Social Responsibility</u></div><div><u><=
br></u></div><div>The issue of the relative importance of the private secto=
r in many of the factors affecting the rights to assembly and association r=
uns throughout the document.=C2=A0 It is now widely recognized that, effect=
ively, &quot;governance&quot; now includes not just what governments do, bu=
t also the formal and informal processes, rules, and practices of private s=
ector entities; indeed, ICANN, the IAB, and the IETF are important examples=
 of this.=C2=A0 The relative importance of third party intermediaries in fa=
cilitating, controlling, or preventing assembly and association makes this =
particularly important.=C2=A0 Finally and far from trivially, since so many=
 of those involved in the IETF are employees of corporations, including att=
ention to this would speak very directly to them.</div><div><br></div><div>=
It would thus significantly strengthen this document to include a section o=
n treatment of assembly and association by those who analyze, audit, and de=
velop best practices (<i>cum</i>=C2=A0rules) for private sector entities.=
=C2=A0 What does Ranking Digital Rights, for example, have to say about thi=
s?=C2=A0 Whether such entities do or do not explicitly address association =
and assembly, the reader wants to know.=C2=A0 This section should look both=
 at what such auditing and best practice-setting organizations are doing, a=
nd at the significant literature on corporate social responsibility in the =
digital environment.</div><div><br></div><div><u>Literature Review</u></div=
><div><u><br></u></div><div>In my view, so few items are relied upon, with =
those relied upon quite heavily, that it is inaccurate to use &quot;literat=
ure review&quot; as a sub-heading.=C2=A0 That is particularly the case sinc=
e much of the discussion in this draft&#39;s section by that title is actua=
lly not about the literature, but about treaties -- legal authorities, as d=
iscussed above.=C2=A0 My personal preference would be to see the authors ta=
king advantage of more of the really strong literature in these areas (the =
gap between what is here and being comprehensive is very large), but whethe=
r or not that is done, I encourage you to drop the sub-heading. Doing so wo=
uld be a form of &quot;defensive writing,&quot; warding off an attack befor=
e it comes from those who know the literature in this area and know what is=
 out there that you haven&#39;t taken advantage of.=C2=A0 You can attribute=
 ideas and information from items you rely on without using the phrase &quo=
t;literature review.&quot;</div><div><br></div><div><u>Concepts</u></div><d=
iv><u><br></u></div><div><i>Public vs Private</i></div><div><i><br></i></di=
v><div>The tension between the sense of public discursive space and private=
 ownership of the infrastructure is in the opening of this document and run=
s throughout.=C2=A0 However, that is not a binary distinction.=C2=A0 Rather=
, there is a spectrum of types of relationships between the two developed l=
ong before we entered the digital world.=C2=A0 In addition to &quot;ownersh=
ip&quot; as a criterion of determining what is what, other criteria include=
 &quot;control of the space&quot; and &quot;history of use&quot; in US law.=
=C2=A0 (I will discuss US law here as the body of law which I know best, an=
d also as a body of law that has been particularly influential globally in =
areas such as this, but I strongly encourage the authors to go further in t=
heir reading to learn more about how these distinctions are made elsewhere =
both by states and in the international environment -- again, jurisprudence=
 will be invaluable here.)</div><div><br></div><div>The distinction as draw=
n in US law includes not only spaces that are purely public (e.g., public p=
arks and streets) and purely private (e.g., the home), but also those that =
are quasi-public and quasi-private.=C2=A0 Quasi-public spaces are those tha=
t are owned and controlled by the public (the government), but are devoted =
to very specific uses that courts and legislatures have said justify restri=
ctions on speech and assembly under certain conditions.=C2=A0 Jails and mil=
itary bases are examples of such spaces.=C2=A0 Quasi-private spaces are tho=
se that are owned and controlled by private entities, but have specific use=
s that are experienced as public by people.=C2=A0 Because of that public di=
mension of these spaces, owners and/or controllers must meet certain specif=
ic requirements in order to legally restrict speech and assembly.=C2=A0 Exa=
mples of such spaces include shopping malls, company towns, and fairgrounds=
.=C2=A0 Courts use the &quot;strict scrutiny&quot; test in either of these =
conditions when conflicts over the exercise of rights arise.=C2=A0 Even in =
purely public environments, legal systems justify restricting speech under =
the kinds of conditions brought up in this document (e.g., threats to natio=
nal security) as a question although not discussed.</div><div><br></div><di=
v>The concepts of quasi-public and quasi-private space have been used in an=
alysis of speech and assembly rights in the digital environments.=C2=A0 Ove=
r the last couple of years, additional very interesting arguments are being=
 put forward to claim things like social media data as public rather than p=
rivate, drawing on analogues with telecommunications regulation.=C2=A0 The =
notion that private entities must serve as &quot;trustees&quot; on behalf o=
f the public has been used to justify regulating telecommunications compani=
es since at least the 1930s and is now being discussed in association with =
private companies that exert significant control over what we can do online=
.=C2=A0 The notion that data about the public should be treated as a public=
 resource has been put forward in analog with treatment of the electromagne=
tic spectrum as a public resource used by private entities.=C2=A0 More can =
be done here.</div><div><br></div><div>All of this is to say that in my vie=
w this document would be much stronger if it unpacked the public/private pr=
oblem rather than just mentioning it several times in passing, as the issue=
 of the kind of space involved is so often important to assembly and associ=
ation issues.=C2=A0 One place in the text that invites this kind of unfoldi=
ng is in your definition of connectivity, which says it is &quot;the <i>ext=
ent</i>=C2=A0to which a device or network is able to reach other devices or=
 networks,&quot; suggesting there is a spectrum of possibilities.</div><div=
><br></div><div><i>Assembly and Association</i></div><div><i><br></i></div>=
<div>The authors do a nice job of opening up the question of the distinctio=
n between assembly and association.=C2=A0 The danger of not being very clea=
r about these concepts runs through some of the cases later discussed, as y=
ou don&#39;t want to conflate either of these concepts with simply the righ=
t to communicate.=C2=A0 I encourage the authors to go a further on this fro=
nt, drawing on explicit legal formulations in international law and exempla=
r national and EU law.</div><div><br></div><div>The US government faced gre=
at difficulty when trying to figure out who could be held liable for the ma=
ssive WikiLeaks data dump that wound up with Chelsea Manning in prison for =
a long while and Julian Assange in the Ecuadorian Embassy in London.=C2=A0 =
Since autonomous networks don&#39;t exist as a legal subject, efforts to de=
termine accountability ranged from Manning only all the way through to ever=
yone who had looked at a tweet about the case (<a href=3D"https://ijoc.org/=
index.php/ijoc/article/view/2668">https://ijoc.org/index.php/ijoc/article/v=
iew/2668</a>).=C2=A0=C2=A0</div><div><br></div><div>You will want to conclu=
de your discussion of assembly and association with clear rules for how you=
 would distinguish assembly from association in the digital environment.=C2=
=A0 Which is WikiLeaks, given the shifting and anonymous membership?=C2=A0 =
The distinction between the two matters for how each is treated by legal sy=
stems.=C2=A0 In the case of the Jan. 6, 2021, event at the US Capitol, lega=
l matters are proceeding with great care to ensure that people who assemble=
d in the space but were not a part of an association committed to violence =
are not treated as if they were a part of that association.=C2=A0 Legal lia=
bility for actions goes up in US law, and I&#39;m sure under many bodies of=
 law, where there is association.=C2=A0 Thus the importance of &quot;conspi=
racy,&quot; &quot;racketeering,&quot; and &quot;collusion&quot; as terms of=
 importance in resolving legal cases involving, in turn, illegal violent po=
litical action, crime, and competition/antitrust law.</div><div><br></div><=
div><u>Cases</u></div><div><u><br></u></div><div>Any selection of cases nee=
ds justification.=C2=A0 The authors state at the opening of the section dis=
cussing cases that not all of what is mentioned is actually addressable at =
the protocol level that is the business of the IETF to which this document =
is directed.=C2=A0 <b>By doing so, the authors provide strong, active suppo=
rt for those who insist that the human rights issues being discussed are ju=
st not the business of the IETF.</b>=C2=A0 I strongly encourage the authors=
 to include only cases for which they can demonstrate the role of protocol =
design and network architecture.=C2=A0 For every such case, the piece would=
 be much stronger if an actual recommendation regarding alternative choices=
 for protocol design or network architecture are offered. Dave Clark&#39;s =
<i>Designing an Internet</i>=C2=A0provides a superb model for how this kind=
 of linkage between the two kinds of concerns can be drawn.</div><div><br><=
/div><div><u>Writing Issues</u></div><div><br></div><div>&quot;Assembly&quo=
t; and &quot;association&quot; should be included among the terms defined a=
t the opening of the piece.</div><div><br></div><div>The pertinence of the =
cases will be more clear to the reader if you are explicit in each one just=
 how assembly or association are involved.</div><div><br></div><div>Bring t=
he three separate notes on what the Internet is together into an internally=
 coherent paragraph.</div><div><br></div><div>The cases rely too much on qu=
otes.</div><div><br></div><div>The reference list should include full citat=
ions in addition to links for professionalism, and needs some cleaning up.<=
/div><div><br></div><div>There are a number of word use, punctuation, and g=
rammatical errors throughout.</div><div><br></div><div>This draft concludes=
 with some high-level statements and then all of a sudden turns to introduc=
ing a new issue.=C2=A0 You can find a better close.</div><div><br></div><di=
v><u>Utility for IETF Readers</u></div><div><u><br></u></div><div>Assuming =
you would like this to be actually used by IETF participants, can you inclu=
de, in the conclusion, a checklist of things that those involved in protoco=
l design and network architecture can actually look out for in the course o=
f their work?=C2=A0=C2=A0</div><div><br></div><div><br></div></div></div>

--000000000000fc086105baa6cc48--


From nobody Sat Feb  6 06:47:13 2021
Return-Path: <braman@tamu.edu>
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 44C8D3A136C for <hrpc@ietfa.amsl.com>; Sat,  6 Feb 2021 06:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 Voiq3cOi6G4u for <hrpc@ietfa.amsl.com>; Sat,  6 Feb 2021 06:47:04 -0800 (PST)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 8B4C63A136B for <hrpc@irtf.org>; Sat,  6 Feb 2021 06:47:03 -0800 (PST)
Received: by mail-il1-x12f.google.com with SMTP id z18so8609520ile.9 for <hrpc@irtf.org>; Sat, 06 Feb 2021 06:47:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ICpWdVByKL7ZtVIwFlecSh8rVQMEsETCvPhMT1ie4mQ=; b=Z85Mcx6h8Xk/+6Y0srY+bIgVbrM/zWl12SJMu5Acg7nk1R1eOKTmQwWKYurlv+yOD3 kBq0nGu10evrzhBj8+yKv1JtyHbMYYuzRNuKB+WdHgBmGt9HHfqf2ESXd4oNelX8yGLK 84v1iR6RrsC6NSnK4k+31OOrPRthYgPX2XYNa6mentr27kvxo8Rm58VMAUJqUxFjtgkS ojXfv5/hz52UikgH1zsIg1gWCpoS6xpR0S1m9IhvUBRotAzDLN3gxtKR3V5bepwZ8/3J JtzsWD8xcINQznJ3PuHnid2KymagRjkmpe+LROm9/KIMt7iaDagFxeg8Vap+YWLAu7cF buVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ICpWdVByKL7ZtVIwFlecSh8rVQMEsETCvPhMT1ie4mQ=; b=H+3mNtuVWoY1opoiZrTLCxqdTYYoUuEJJfBMNxHO8JfzxR8K/k/WlbwZi0X+tJYdCV +N2JtLjfD2OqU6v2bPaqllS4bGn7/ClHYCwB2dBk4zPzKnOcOMyYdDVRggx/MiaLi6qx G1lwLfQvy0puTRobYVaCzVlI9SVOvnI/E2C6OD/zIx+RJYEgDbdQXJW9xPOzHAlugHZO li+8zuEki/rgt0TrfcF0yyy6uF0hSl4rcqGj/wgC7yT/Q2GlFCRc4PwzRVQ9rS66uL7x BAJ80cUwo+vS4JskBrTn4BhZWgUMCPHOfvulcQd29/ZQHmr7JdP4lKbRrkHtbDXQpm3E Mlag==
X-Gm-Message-State: AOAM533AHdDGz2XauZdE+Hvny7nCt5bg3fHIHmJuW9NsMefUrDRHRVsY Je75JKt8aME6N5PbnqgdnKlpSIifU/nlwtM3IskcPztLJXyeBA==
X-Google-Smtp-Source: ABdhPJzp02nvE5iDiJ+WA/y0cOcDQnsmF7n5rkqng9TCFCN8B58HvNMocttOd+JDXe734konxUjPUTdBwrTf68jyolQ=
X-Received: by 2002:a92:ab10:: with SMTP id v16mr8784676ilh.100.1612622821690;  Sat, 06 Feb 2021 06:47:01 -0800 (PST)
MIME-Version: 1.0
References: <mailman.2188.1612600458.7093.hrpc@irtf.org>
In-Reply-To: <mailman.2188.1612600458.7093.hrpc@irtf.org>
From: Sandra Braman <braman@tamu.edu>
Date: Sat, 6 Feb 2021 08:48:49 -0600
Message-ID: <CAB2unbNd=Oe0mrufK3eVsaY93fJ1e22yXn0rLq7+fL2ZvgNckQ@mail.gmail.com>
To: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="00000000000071a8a205baac028f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/hdKrdD3ZA2B-q8Ei6e80iUBhP2Q>
Subject: [hrpc] further re draft association
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: Sat, 06 Feb 2021 14:47:11 -0000

--00000000000071a8a205baac028f
Content-Type: text/plain; charset="UTF-8"

Should have gone further myself re the concept of association.  In US law
-- again, only one body of national law, but illustrative of what work
further needs to be done on international law and on other national and
regional (EU) law as support for what needs to be further articulation of
what is meant by the concept of "association" here -- the concept of
association is reserved for those who have formally affiliated themselves
with a legally recognized group, whether that is a professional
association, a non-profit advocacy group, or a union.  Being a part of a
group that regularly communicates does not constitute "association" in US
law unless there is membership, etc., involved.  This is why WikiLeaks has
been so legally problematic.  The right of association itself provides
privacy protection under US law, as courts have recognized that requiring a
group to publish its list of members could infringe upon the right of
association if it means people will not join the group out of fear of
consequences if their membership were known.

This is why the cognate terms introduced earlier are so important
(conspiracy, racketeering, and collusion).  To correct what may have been
misleading in my earlier comment on investigations into conspiracy among
those who attacked the US Capitol in 2021, it is important to note that it
is conspiracy, not association, that is the word being used. For evidence
of conspiracy they are looking for a consistent pattern of communication
among the same people regarding the shared intention across time, and
specific plans for, engaging in specific illegal violent action. Those
involved will not be able to claim the right of association because in this
legal system is not involved.  The Proud Boys, for example, are not an
association.  When Communism was the issue, being a member of the Communist
Party involved association. Reading and discussing texts by Karl Marx and
others together outside of the formal Party context was not.

I don't know if signing up for a listserv quailifies as an association
under US law (and other laws), even though signing up is a contract to
conform to the rules for communication of the particular group involved;
with further research, the authors can find that out.  In the discussion of
mailing lists in the section on cases, there is reference to "free
association," meaning communication among a group of people, which in
itself does not reach the kind of formal association protected by US law.
Analyzing court cases for the various types of communication discussed in
cases included in the current draft on association, across jurisdictions,
would provide information on this point and related points that are
critical to the success of the argument being put forward here.  Being
involved with WikiLeaks is not association.

The fact that, as the authors discuss in their highlighting of points from
the APC manual in this draft, the Internet is useful for organizing
political protests does not mean that, under US law, the activities and
people involved are protected by the right of association (as inaccurately
claimed in this draft of the document) although their speech rights are
protected.  If it is, under other law, the authors need to clarify that and
be able to support the claim.

An important point to mention is the difference between prior restraint --
stopping something before it happens -- and punishment after the fact.
Prior restraint when it comes to speech rights include censorship, and the
kinds of interventions Internet protocols might put in place to make
particular kinds of intra-group communication difficult (if these authors
can specify what those might be).  Punishment after the fact includes being
held accountable for the consequences of one's speech.  As the authors of
this document note, the rights to freedom of expression and to assembly and
association are often related; the same distinction between prior restraint
and punishment after the fact applies.  Arresting people for engaging in
illegal violent action they took place in after assembling to express their
political views does not infringe on freedom of speech -- it is, if they
are convicted, punishment after the fact for illegal action.  On the speech
side, for those involved, if convicted, it would be punishment after the
fact for conspiracy to commit illegal violent action.

As mentioned earlier, it is necessary to distinguish the right to
association from the general right to communicate -- and from mob action.
DDOS is mob action, neither assembly nor association.  The authors really
do need to articulate the relationship between the issue discussed in each
case and either assembly or association as distinct from communication in
general.  Spam, in another example, for example, is about communication,
not assembly or association; limiting spam affects neither the right to
assemble or association.  If the authors want to argue otherwise
persuasively, they will need to fully develop the argument.  Peer-to-peer
networking is about communication, not association.  Yes, these matters are
intertwined, but in a court they are distinguished and need to be defended
separately, so it is separately that the arguments need to be made in a
document that is, as presented, intended to be specific to the rights of
assembly and association.

Be careful with the English language issue.  First, it is likely that these
authors, or at least some of them, support the notions of a "commons" for
use in as many areas as possible.  Having a shared language in which one
can communicate across geographies, societies, and cultures is a commons.
Second, the history of efforts by Internet designers to expand the capacity
of those using non-Roman alphabets online goes back to its earliest years
but faced a series of significant technical problems (I have a couple of
journal items documenting this via analysis of RFCs if anyone is
interested), so claiming those involved in the design process have been
inattentive is inaccurate.  Third, economists have pointed out that the use
of too many languages for a shared conversation (the quick rule is into two
digits or more) generates such enormous costs that doing so undermines the
political and other points of the shared conversation altogether.  Both the
European Union and South Africa (which has 11 official languages) have
suffered from this problem.  Note that the European Union does *not* publish
its documents in all of the languages of its member countries.  Fourth,
circling back to the first point, what is actually being recommended as an
alternative, and how could those involved in protocol design and network
architecture facilitate that alternative?

A couple of other small points:

- The use of "FAA" here unnecessarily adds jargon that is not in common use
among those who think about the rights of assembly and association (I've
never seen it used before in decades of reading and discussing such
matters), and is off-putting.  In the US, the "FAA" is the Federal Aviation
Agency.

- Are the authors treating assembly and association as two separate rights,
or as a single right?  The text goes back and forth on this point.  In US
law, the right to association is based on the right to assembly that is the
pertinent constitutional provision.  The extention to association developed
jurisprudentially.  I don't know the history of how the two concepts
developed and how they are related to and distinguished from each other in
other legal systems, but clarification on this point would also strengthen
this document.

- Internal consistency re terms used (such as either sociotechnical or
techno-social, but not both) will be helpful on the writing front as well.

- What do the authors mean by "holistic agency," both theoretically and
operationally?  The concept barely has a presence in the scholarly
literature.  It is not in wide use and its meaning is not clear.  Most of
that is found through a quick search on the phrase refers to a TV series
called "Dirk Gently's Holistic Detective Agency."

- Whether or not national laws that contravene international law is
"illegitimate" depends on which country, when, and how.  A country that has
not ratified a particular treaty is not bound to conform to its
provisions.  This problem with the document can be easily addressed with a
writing fix.


On Sat, Feb 6, 2021 at 2:34 AM <hrpc-request@irtf.org> wrote:

> Send hrpc mailing list submissions to
>         hrpc@irtf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!Tz24KK93zR7-vlgITffJXfcYuxYYLdJWEG_qIB6L-XN_o8XIxRb-e6k0uhG3L5TkV0s$
> or, via email, send a message with subject or body 'help' to
>         hrpc-request@irtf.org
>
> You can reach the person managing the list at
>         hrpc-owner@irtf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of hrpc digest..."
> Today's Topics:
>
>    1. comments, draft association (Sandra Braman)
>
>
>
> ---------- Forwarded message ----------
> From: Sandra Braman <braman@tamu.edu>
> To: "hrpc@irtf.org" <hrpc@irtf.org>
> Cc:
> Bcc:
> Date: Sat, 6 Feb 2021 02:35:56 -0600
> Subject: [hrpc] comments, draft association
> First, to the authors, congratulations on this piece.  Clearly a lot of
> effort has gone into this.  Following are some thoughts regarding how this
> piece could be strengthened if it is to serve as an informational RFC
> rather than a journal article, organized by topic.  It is a background
> assumption of these comments that the document is intended to have utility
> to those involved in protocol design work via the IETF.  Long email alert.
>
> Sandra Braman
>
>
> ----------------------------------------------------------------------------------
>
> *Legal authorities used as justification*
>
> *International Treaties*
>
> The international treaties discussed in this draft are not a part of the
> scholarly literature covered in literature reviews, but the legal
> authorities on the basis of which claims made here are justified.  Although
> I agree with the authors that this is not the place for a comprehensive
> discussion and synthesis of the scholarly literature, coverage of the
> pertinent treaty provisions *should* be comprehensive.  Treaty provisions
> only matter, though, where treaties have been ratified.  It would also be
> useful to the reader to know the extent to which these provisions have been
> interpreted in courts in cases that have come their way involving assembly
> and association.
>
> Breaking out a paragraph for each treaty provision would highlight each
> for the reader and provide the space to include information on how many
> countries have actually ratified and thus are bound by the treaty, the
> kinds of conflicts that have arisen historically under each provision in
> the digital environment, and how those conflicts have been resolved.
> Organizing the provisions chronologically by when the treaties were
> initially signed (signing treaties and ratifying them are two separate
> steps) would offer the authors an opportunity to present a sense of a
> rising tide of appreciation of the importance of protecting the rights of
> assembly and association.
>
> *National Laws*
>
> There is reference to protection of the rights of assembly and association
> in national constitutions and laws.  It would strengthen the argument being
> made here to provide information on how many geopolitically recognized
> states (that is, those recognized by the UN) protect these rights and
> trends in this area.  There is discussion by American authors of American
> law in the literature review, by European Union groups about European law,
> and about international law -- can literature about national law by
> non-American authors about non-American treatment of assembly and
> association also be included?
>
> *Jurisprudence*
>
> The word "jurisprudence" shows up towards the close of the piece but
> jurisprudence is actually not discussed here.  An analysis of how courts
> have treated assembly and association in the digital environment would be
> invaluable.  There is a significant scholarly literature on this (that
> could usefully be expanded), but it is strongly recommended that the
> authors also actually go to the court opinions, which are themselves
> sources of law as well and thus included in this section of these comments.
>
> *Corporate Social Responsibility*
>
> The issue of the relative importance of the private sector in many of the
> factors affecting the rights to assembly and association runs throughout
> the document.  It is now widely recognized that, effectively, "governance"
> now includes not just what governments do, but also the formal and informal
> processes, rules, and practices of private sector entities; indeed, ICANN,
> the IAB, and the IETF are important examples of this.  The relative
> importance of third party intermediaries in facilitating, controlling, or
> preventing assembly and association makes this particularly important.
> Finally and far from trivially, since so many of those involved in the IETF
> are employees of corporations, including attention to this would speak very
> directly to them.
>
> It would thus significantly strengthen this document to include a section
> on treatment of assembly and association by those who analyze, audit, and
> develop best practices (*cum* rules) for private sector entities.  What
> does Ranking Digital Rights, for example, have to say about this?  Whether
> such entities do or do not explicitly address association and assembly, the
> reader wants to know.  This section should look both at what such auditing
> and best practice-setting organizations are doing, and at the significant
> literature on corporate social responsibility in the digital environment.
>
> *Literature Review*
>
> In my view, so few items are relied upon, with those relied upon quite
> heavily, that it is inaccurate to use "literature review" as a
> sub-heading.  That is particularly the case since much of the discussion in
> this draft's section by that title is actually not about the literature,
> but about treaties -- legal authorities, as discussed above.  My personal
> preference would be to see the authors taking advantage of more of the
> really strong literature in these areas (the gap between what is here and
> being comprehensive is very large), but whether or not that is done, I
> encourage you to drop the sub-heading. Doing so would be a form of
> "defensive writing," warding off an attack before it comes from those who
> know the literature in this area and know what is out there that you
> haven't taken advantage of.  You can attribute ideas and information from
> items you rely on without using the phrase "literature review."
>
> *Concepts*
>
> *Public vs Private*
>
> The tension between the sense of public discursive space and private
> ownership of the infrastructure is in the opening of this document and runs
> throughout.  However, that is not a binary distinction.  Rather, there is a
> spectrum of types of relationships between the two developed long before we
> entered the digital world.  In addition to "ownership" as a criterion of
> determining what is what, other criteria include "control of the space" and
> "history of use" in US law.  (I will discuss US law here as the body of law
> which I know best, and also as a body of law that has been particularly
> influential globally in areas such as this, but I strongly encourage the
> authors to go further in their reading to learn more about how these
> distinctions are made elsewhere both by states and in the international
> environment -- again, jurisprudence will be invaluable here.)
>
> The distinction as drawn in US law includes not only spaces that are
> purely public (e.g., public parks and streets) and purely private (e.g.,
> the home), but also those that are quasi-public and quasi-private.
> Quasi-public spaces are those that are owned and controlled by the public
> (the government), but are devoted to very specific uses that courts and
> legislatures have said justify restrictions on speech and assembly under
> certain conditions.  Jails and military bases are examples of such spaces.
> Quasi-private spaces are those that are owned and controlled by private
> entities, but have specific uses that are experienced as public by people.
> Because of that public dimension of these spaces, owners and/or controllers
> must meet certain specific requirements in order to legally restrict speech
> and assembly.  Examples of such spaces include shopping malls, company
> towns, and fairgrounds.  Courts use the "strict scrutiny" test in either of
> these conditions when conflicts over the exercise of rights arise.  Even in
> purely public environments, legal systems justify restricting speech under
> the kinds of conditions brought up in this document (e.g., threats to
> national security) as a question although not discussed.
>
> The concepts of quasi-public and quasi-private space have been used in
> analysis of speech and assembly rights in the digital environments.  Over
> the last couple of years, additional very interesting arguments are being
> put forward to claim things like social media data as public rather than
> private, drawing on analogues with telecommunications regulation.  The
> notion that private entities must serve as "trustees" on behalf of the
> public has been used to justify regulating telecommunications companies
> since at least the 1930s and is now being discussed in association with
> private companies that exert significant control over what we can do
> online.  The notion that data about the public should be treated as a
> public resource has been put forward in analog with treatment of the
> electromagnetic spectrum as a public resource used by private entities.
> More can be done here.
>
> All of this is to say that in my view this document would be much stronger
> if it unpacked the public/private problem rather than just mentioning it
> several times in passing, as the issue of the kind of space involved is so
> often important to assembly and association issues.  One place in the text
> that invites this kind of unfolding is in your definition of connectivity,
> which says it is "the *extent* to which a device or network is able to
> reach other devices or networks," suggesting there is a spectrum of
> possibilities.
>
> *Assembly and Association*
>
> The authors do a nice job of opening up the question of the distinction
> between assembly and association.  The danger of not being very clear about
> these concepts runs through some of the cases later discussed, as you don't
> want to conflate either of these concepts with simply the right to
> communicate.  I encourage the authors to go a further on this front,
> drawing on explicit legal formulations in international law and exemplar
> national and EU law.
>
> The US government faced great difficulty when trying to figure out who
> could be held liable for the massive WikiLeaks data dump that wound up with
> Chelsea Manning in prison for a long while and Julian Assange in the
> Ecuadorian Embassy in London.  Since autonomous networks don't exist as a
> legal subject, efforts to determine accountability ranged from Manning only
> all the way through to everyone who had looked at a tweet about the case (
> https://ijoc.org/index.php/ijoc/article/view/2668
> <https://urldefense.com/v3/__https://ijoc.org/index.php/ijoc/article/view/2668__;!!KwNVnqRv!Tz24KK93zR7-vlgITffJXfcYuxYYLdJWEG_qIB6L-XN_o8XIxRb-e6k0uhG32RfJt2s$>
> ).
>
> You will want to conclude your discussion of assembly and association with
> clear rules for how you would distinguish assembly from association in the
> digital environment.  Which is WikiLeaks, given the shifting and anonymous
> membership?  The distinction between the two matters for how each is
> treated by legal systems.  In the case of the Jan. 6, 2021, event at the US
> Capitol, legal matters are proceeding with great care to ensure that people
> who assembled in the space but were not a part of an association committed
> to violence are not treated as if they were a part of that association.
> Legal liability for actions goes up in US law, and I'm sure under many
> bodies of law, where there is association.  Thus the importance of
> "conspiracy," "racketeering," and "collusion" as terms of importance in
> resolving legal cases involving, in turn, illegal violent political action,
> crime, and competition/antitrust law.
>
> *Cases*
>
> Any selection of cases needs justification.  The authors state at the
> opening of the section discussing cases that not all of what is mentioned
> is actually addressable at the protocol level that is the business of the
> IETF to which this document is directed.  *By doing so, the authors
> provide strong, active support for those who insist that the human rights
> issues being discussed are just not the business of the IETF.*  I
> strongly encourage the authors to include only cases for which they can
> demonstrate the role of protocol design and network architecture.  For
> every such case, the piece would be much stronger if an actual
> recommendation regarding alternative choices for protocol design or network
> architecture are offered. Dave Clark's *Designing an Internet* provides a
> superb model for how this kind of linkage between the two kinds of concerns
> can be drawn.
>
> *Writing Issues*
>
> "Assembly" and "association" should be included among the terms defined at
> the opening of the piece.
>
> The pertinence of the cases will be more clear to the reader if you are
> explicit in each one just how assembly or association are involved.
>
> Bring the three separate notes on what the Internet is together into an
> internally coherent paragraph.
>
> The cases rely too much on quotes.
>
> The reference list should include full citations in addition to links for
> professionalism, and needs some cleaning up.
>
> There are a number of word use, punctuation, and grammatical errors
> throughout.
>
> This draft concludes with some high-level statements and then all of a
> sudden turns to introducing a new issue.  You can find a better close.
>
> *Utility for IETF Readers*
>
> Assuming you would like this to be actually used by IETF participants, can
> you include, in the conclusion, a checklist of things that those involved
> in protocol design and network architecture can actually look out for in
> the course of their work?
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!Tz24KK93zR7-vlgITffJXfcYuxYYLdJWEG_qIB6L-XN_o8XIxRb-e6k0uhG3L5TkV0s$
>

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

<div dir=3D"ltr"><div>Should have gone further myself re the concept of ass=
ociation.=C2=A0 In US law -- again, only one body of national law, but illu=
strative of what work further needs to be done on international law and on =
other national and regional (EU) law as support for what needs to be furthe=
r articulation of what is meant by the concept of &quot;association&quot; h=
ere -- the concept of association is reserved for those who have formally a=
ffiliated themselves with a legally recognized group, whether that is a pro=
fessional association, a non-profit advocacy group, or a union.=C2=A0 Being=
 a part of a group that regularly communicates does not constitute &quot;as=
sociation&quot; in US law unless there is membership, etc., involved.=C2=A0=
 This is why WikiLeaks has been so legally problematic.=C2=A0 The right of =
association itself provides privacy protection under US law, as courts have=
 recognized that requiring a group to publish its list of members could inf=
ringe upon the right of association if it means people will not join the gr=
oup out of fear of consequences if their membership were known.</div><div><=
br></div><div>This is why the cognate terms introduced earlier are so impor=
tant (conspiracy, racketeering, and collusion).=C2=A0 To correct what may h=
ave been misleading in my earlier comment on investigations into conspiracy=
 among those who attacked the US Capitol in 2021, it is important to note t=
hat it is conspiracy, not association, that is the word being used. For evi=
dence of conspiracy they are looking for a consistent pattern of communicat=
ion among the same people regarding the shared intention across time, and s=
pecific plans for, engaging in specific illegal violent action. Those invol=
ved will not be able to claim the right of association because in this lega=
l system is not involved.=C2=A0 The Proud Boys, for example, are not an ass=
ociation.=C2=A0 When Communism was the issue, being a member of the Communi=
st Party involved association. Reading and discussing texts by Karl Marx an=
d others together outside of the formal Party context was not.</div><div><b=
r></div><div>I don&#39;t know if signing up for a listserv quailifies as an=
 association under US law (and other laws), even though signing up is a con=
tract to conform to the rules for communication of the particular group inv=
olved; with further research, the authors can find that out.=C2=A0 In the d=
iscussion of mailing lists in the section on cases, there is reference to &=
quot;free association,&quot; meaning communication among a group of people,=
 which in itself does not reach the kind of formal association protected by=
 US law. Analyzing court cases for the various types of communication discu=
ssed in cases included in the current draft on association, across jurisdic=
tions, would provide information on this point and related points that are =
critical to the success of the argument being put forward here.=C2=A0 Being=
 involved with WikiLeaks is not association.=C2=A0=C2=A0</div><div><br></di=
v><div>The fact that, as the authors discuss in their highlighting of point=
s from the APC manual in this draft, the Internet is useful for organizing =
political protests does not mean that, under US law, the activities and peo=
ple involved are protected by the right of association (as inaccurately cla=
imed in this draft of the document) although their speech rights are protec=
ted.=C2=A0 If it is, under other law, the authors need to clarify that and =
be able to support the claim.=C2=A0=C2=A0</div><div><br></div><div>An impor=
tant point to mention is the difference between prior restraint -- stopping=
 something before it happens -- and punishment after the fact.=C2=A0 Prior =
restraint when it comes to speech rights include censorship, and the kinds =
of interventions Internet protocols might put in place to make particular k=
inds of intra-group communication difficult (if these authors can specify w=
hat those might be).=C2=A0 Punishment after the fact includes being held ac=
countable for the consequences of one&#39;s speech.=C2=A0 As the authors of=
 this document note, the rights to freedom of expression and to assembly an=
d association are often related; the same distinction between prior restrai=
nt and punishment after the fact applies.=C2=A0 Arresting people for engagi=
ng in illegal violent action they took place in after assembling to express=
 their political views does not infringe on freedom of speech -- it is, if =
they are convicted, punishment after the fact for illegal action.=C2=A0 On =
the speech side, for those involved, if convicted, it would be punishment a=
fter the fact for conspiracy to commit illegal violent action.</div><div><b=
r></div><div>As mentioned earlier, it is necessary to distinguish the right=
 to association from the general right to communicate -- and from mob actio=
n.=C2=A0 DDOS is mob action, neither assembly nor association.=C2=A0 The au=
thors really do need to articulate the relationship between the issue discu=
ssed in each case and either assembly or association as distinct from commu=
nication in general.=C2=A0 Spam, in another example, for example, is about =
communication, not assembly or association; limiting spam affects neither t=
he right to assemble or association.=C2=A0 If the authors want to argue oth=
erwise persuasively, they will need to fully develop the argument.=C2=A0 Pe=
er-to-peer networking is about communication, not association.=C2=A0 Yes, t=
hese matters are intertwined, but in a court they are distinguished and nee=
d to be defended separately, so it is separately that the arguments need to=
 be made in a document that is, as presented, intended to be specific to th=
e rights of assembly and association.</div><div><br></div><div>Be careful w=
ith the English language issue.=C2=A0 First, it is likely that these author=
s, or at least some of them, support the notions of a &quot;commons&quot; f=
or use in as many areas as possible.=C2=A0 Having a shared language in whic=
h one can communicate across geographies, societies, and cultures is a comm=
ons.=C2=A0 Second, the history of efforts by Internet designers to expand t=
he capacity of those using non-Roman alphabets online goes back to its earl=
iest years but faced a series of significant technical problems (I have a c=
ouple of journal items documenting this via analysis of RFCs if anyone is i=
nterested), so claiming those involved in the design process have been inat=
tentive is inaccurate.=C2=A0 Third, economists have pointed out that the us=
e of too many languages for a shared conversation (the quick rule is into t=
wo digits or more) generates such enormous costs that doing so undermines t=
he political and other points of the shared conversation altogether.=C2=A0 =
Both the European Union and South Africa (which has 11 official languages) =
have suffered from this problem.=C2=A0 Note that the European Union does <i=
>not</i>=C2=A0publish its documents in all of the languages of its member c=
ountries.=C2=A0 Fourth, circling back to the first point, what is actually =
being recommended as an alternative, and how could those involved in protoc=
ol design and network architecture facilitate that alternative?</div><div><=
br></div><div>A couple of other small points:</div><div><br></div><div>- Th=
e use of &quot;FAA&quot; here unnecessarily adds jargon that is not in comm=
on use among those who think about the rights of assembly and association (=
I&#39;ve never seen it used before in decades of reading and discussing suc=
h matters), and is off-putting.=C2=A0 In the US, the &quot;FAA&quot; is the=
 Federal Aviation Agency.</div><div><br></div><div>- Are the authors treati=
ng assembly and association as two separate rights, or as a single right?=
=C2=A0 The text goes back and forth on this point.=C2=A0 In US law, the rig=
ht to association is based on the right to assembly that is the pertinent c=
onstitutional provision.=C2=A0 The extention to association developed juris=
prudentially.=C2=A0 I don&#39;t know the history of how the two concepts de=
veloped and how they are related to and distinguished from each other in ot=
her legal systems, but clarification on this point would also strengthen th=
is document.</div><div><br></div><div>- Internal consistency re terms used =
(such as either sociotechnical or techno-social, but not both) will be help=
ful on the writing front as well.</div><div><br></div><div>- What do the au=
thors mean by &quot;holistic agency,&quot; both theoretically and operation=
ally?=C2=A0 The concept barely has a presence in the scholarly literature.=
=C2=A0 It is not in wide use and its meaning is not clear.=C2=A0 Most of th=
at is found through a quick search on the phrase refers to a TV series call=
ed &quot;Dirk Gently&#39;s Holistic Detective Agency.&quot;=C2=A0</div><div=
><br></div><div>- Whether or not national laws that contravene internationa=
l law is &quot;illegitimate&quot; depends on which country, when, and how.=
=C2=A0 A country that has not ratified a particular treaty is not bound to =
conform to its provisions.=C2=A0 This problem with the document can be easi=
ly addressed with a writing fix.</div><div><br></div><div><br></div><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Feb 6, 20=
21 at 2:34 AM &lt;<a href=3D"mailto:hrpc-request@irtf.org">hrpc-request@irt=
f.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">Send hrpc mailing list submissions to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc@irtf.org" target=3D"_bla=
nk">hrpc@irtf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://urldefense.com/v3/__https://=
www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!Tz24KK93zR7-vlgITffJXfcYuxY=
YLdJWEG_qIB6L-XN_o8XIxRb-e6k0uhG3L5TkV0s$" rel=3D"noreferrer" target=3D"_bl=
ank">https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc=
__;!!KwNVnqRv!Tz24KK93zR7-vlgITffJXfcYuxYYLdJWEG_qIB6L-XN_o8XIxRb-e6k0uhG3L=
5TkV0s$</a> <br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-request@irtf.org" target=
=3D"_blank">hrpc-request@irtf.org</a><br>
<br>
You can reach the person managing the list at<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-owner@irtf.org" target=
=3D"_blank">hrpc-owner@irtf.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of hrpc digest...&quot;<br>
Today&#39;s Topics:<br>
<br>
=C2=A0 =C2=A01. comments, draft association (Sandra Braman)<br>
<br><br><br>---------- Forwarded message ----------<br>From:=C2=A0Sandra Br=
aman &lt;<a href=3D"mailto:braman@tamu.edu" target=3D"_blank">braman@tamu.e=
du</a>&gt;<br>To:=C2=A0&quot;<a href=3D"mailto:hrpc@irtf.org" target=3D"_bl=
ank">hrpc@irtf.org</a>&quot; &lt;<a href=3D"mailto:hrpc@irtf.org" target=3D=
"_blank">hrpc@irtf.org</a>&gt;<br>Cc:=C2=A0<br>Bcc:=C2=A0<br>Date:=C2=A0Sat=
, 6 Feb 2021 02:35:56 -0600<br>Subject:=C2=A0[hrpc] comments, draft associa=
tion<br><div dir=3D"ltr">First, to the authors, congratulations on this pie=
ce.=C2=A0 Clearly a lot of effort has gone into this.=C2=A0 Following are s=
ome thoughts regarding how this piece could be strengthened if it is to ser=
ve as an informational RFC rather than a journal article, organized by topi=
c.=C2=A0 It is a background assumption of these comments that the document =
is intended to have utility to those involved in protocol design work via t=
he IETF.=C2=A0 Long email alert.<div><br></div><div>Sandra Braman</div><div=
><br></div><div>-----------------------------------------------------------=
-----------------------<br><div><br></div><div><u>Legal authorities used as=
 justification</u></div><div><br></div><div><i>International Treaties</i></=
div><div><br></div><div>The international treaties discussed in this draft =
are not a part of the scholarly literature covered in literature reviews, b=
ut the legal authorities on the basis of which claims made here are justifi=
ed.=C2=A0 Although I agree with the authors that this is not the place for =
a comprehensive discussion and synthesis of the scholarly literature, cover=
age of the pertinent treaty provisions <i>should</i> be comprehensive.=C2=
=A0 Treaty provisions only matter, though, where treaties have been ratifie=
d.=C2=A0 It would also be useful to the reader to know the extent to which =
these provisions have been interpreted in courts in cases that have come th=
eir way involving assembly and association.</div><div><br></div><div>Breaki=
ng out a paragraph for each treaty provision would highlight each for the r=
eader and provide the space to include information on how many countries ha=
ve actually ratified and thus are bound by the treaty, the kinds of conflic=
ts that have arisen historically under each provision in the digital enviro=
nment, and how those conflicts have been resolved.=C2=A0 Organizing the pro=
visions chronologically by when the treaties were initially signed (signing=
 treaties and ratifying them are two separate steps) would offer the author=
s an opportunity to present a sense of a rising tide of appreciation of the=
 importance of protecting the rights of assembly and association.</div><div=
><br></div><div><i>National Laws</i></div><div><br></div><div>There is refe=
rence to protection of the rights of assembly and association in national c=
onstitutions and laws.=C2=A0 It would strengthen the argument being made he=
re to provide information on how many geopolitically recognized states (tha=
t is, those recognized by the UN) protect these rights and trends in this a=
rea.=C2=A0 There is discussion by American authors of American law in the l=
iterature review, by European Union groups about European law, and about in=
ternational law -- can literature about national law by non-American author=
s about non-American treatment of assembly and association also be included=
?</div><div><br></div><div><i>Jurisprudence</i></div><div><i><br></i></div>=
<div>The word &quot;jurisprudence&quot; shows up towards the close of the p=
iece but jurisprudence is actually not discussed here.=C2=A0 An analysis of=
 how courts have treated assembly and association in the digital environmen=
t would be invaluable.=C2=A0 There is a significant scholarly literature on=
 this (that could usefully be expanded), but it is strongly recommended tha=
t the authors also actually go to the court opinions, which are themselves =
sources of law as well and thus included in this section of these comments.=
</div><div><br></div><div><u>Corporate Social Responsibility</u></div><div>=
<u><br></u></div><div>The issue of the relative importance of the private s=
ector in many of the factors affecting the rights to assembly and associati=
on runs throughout the document.=C2=A0 It is now widely recognized that, ef=
fectively, &quot;governance&quot; now includes not just what governments do=
, but also the formal and informal processes, rules, and practices of priva=
te sector entities; indeed, ICANN, the IAB, and the IETF are important exam=
ples of this.=C2=A0 The relative importance of third party intermediaries i=
n facilitating, controlling, or preventing assembly and association makes t=
his particularly important.=C2=A0 Finally and far from trivially, since so =
many of those involved in the IETF are employees of corporations, including=
 attention to this would speak very directly to them.</div><div><br></div><=
div>It would thus significantly strengthen this document to include a secti=
on on treatment of assembly and association by those who analyze, audit, an=
d develop best practices (<i>cum</i>=C2=A0rules) for private sector entitie=
s.=C2=A0 What does Ranking Digital Rights, for example, have to say about t=
his?=C2=A0 Whether such entities do or do not explicitly address associatio=
n and assembly, the reader wants to know.=C2=A0 This section should look bo=
th at what such auditing and best practice-setting organizations are doing,=
 and at the significant literature on corporate social responsibility in th=
e digital environment.</div><div><br></div><div><u>Literature Review</u></d=
iv><div><u><br></u></div><div>In my view, so few items are relied upon, wit=
h those relied upon quite heavily, that it is inaccurate to use &quot;liter=
ature review&quot; as a sub-heading.=C2=A0 That is particularly the case si=
nce much of the discussion in this draft&#39;s section by that title is act=
ually not about the literature, but about treaties -- legal authorities, as=
 discussed above.=C2=A0 My personal preference would be to see the authors =
taking advantage of more of the really strong literature in these areas (th=
e gap between what is here and being comprehensive is very large), but whet=
her or not that is done, I encourage you to drop the sub-heading. Doing so =
would be a form of &quot;defensive writing,&quot; warding off an attack bef=
ore it comes from those who know the literature in this area and know what =
is out there that you haven&#39;t taken advantage of.=C2=A0 You can attribu=
te ideas and information from items you rely on without using the phrase &q=
uot;literature review.&quot;</div><div><br></div><div><u>Concepts</u></div>=
<div><u><br></u></div><div><i>Public vs Private</i></div><div><i><br></i></=
div><div>The tension between the sense of public discursive space and priva=
te ownership of the infrastructure is in the opening of this document and r=
uns throughout.=C2=A0 However, that is not a binary distinction.=C2=A0 Rath=
er, there is a spectrum of types of relationships between the two developed=
 long before we entered the digital world.=C2=A0 In addition to &quot;owner=
ship&quot; as a criterion of determining what is what, other criteria inclu=
de &quot;control of the space&quot; and &quot;history of use&quot; in US la=
w.=C2=A0 (I will discuss US law here as the body of law which I know best, =
and also as a body of law that has been particularly influential globally i=
n areas such as this, but I strongly encourage the authors to go further in=
 their reading to learn more about how these distinctions are made elsewher=
e both by states and in the international environment -- again, jurispruden=
ce will be invaluable here.)</div><div><br></div><div>The distinction as dr=
awn in US law includes not only spaces that are purely public (e.g., public=
 parks and streets) and purely private (e.g., the home), but also those tha=
t are quasi-public and quasi-private.=C2=A0 Quasi-public spaces are those t=
hat are owned and controlled by the public (the government), but are devote=
d to very specific uses that courts and legislatures have said justify rest=
rictions on speech and assembly under certain conditions.=C2=A0 Jails and m=
ilitary bases are examples of such spaces.=C2=A0 Quasi-private spaces are t=
hose that are owned and controlled by private entities, but have specific u=
ses that are experienced as public by people.=C2=A0 Because of that public =
dimension of these spaces, owners and/or controllers must meet certain spec=
ific requirements in order to legally restrict speech and assembly.=C2=A0 E=
xamples of such spaces include shopping malls, company towns, and fairgroun=
ds.=C2=A0 Courts use the &quot;strict scrutiny&quot; test in either of thes=
e conditions when conflicts over the exercise of rights arise.=C2=A0 Even i=
n purely public environments, legal systems justify restricting speech unde=
r the kinds of conditions brought up in this document (e.g., threats to nat=
ional security) as a question although not discussed.</div><div><br></div><=
div>The concepts of quasi-public and quasi-private space have been used in =
analysis of speech and assembly rights in the digital environments.=C2=A0 O=
ver the last couple of years, additional very interesting arguments are bei=
ng put forward to claim things like social media data as public rather than=
 private, drawing on analogues with telecommunications regulation.=C2=A0 Th=
e notion that private entities must serve as &quot;trustees&quot; on behalf=
 of the public has been used to justify regulating telecommunications compa=
nies since at least the 1930s and is now being discussed in association wit=
h private companies that exert significant control over what we can do onli=
ne.=C2=A0 The notion that data about the public should be treated as a publ=
ic resource has been put forward in analog with treatment of the electromag=
netic spectrum as a public resource used by private entities.=C2=A0 More ca=
n be done here.</div><div><br></div><div>All of this is to say that in my v=
iew this document would be much stronger if it unpacked the public/private =
problem rather than just mentioning it several times in passing, as the iss=
ue of the kind of space involved is so often important to assembly and asso=
ciation issues.=C2=A0 One place in the text that invites this kind of unfol=
ding is in your definition of connectivity, which says it is &quot;the <i>e=
xtent</i>=C2=A0to which a device or network is able to reach other devices =
or networks,&quot; suggesting there is a spectrum of possibilities.</div><d=
iv><br></div><div><i>Assembly and Association</i></div><div><i><br></i></di=
v><div>The authors do a nice job of opening up the question of the distinct=
ion between assembly and association.=C2=A0 The danger of not being very cl=
ear about these concepts runs through some of the cases later discussed, as=
 you don&#39;t want to conflate either of these concepts with simply the ri=
ght to communicate.=C2=A0 I encourage the authors to go a further on this f=
ront, drawing on explicit legal formulations in international law and exemp=
lar national and EU law.</div><div><br></div><div>The US government faced g=
reat difficulty when trying to figure out who could be held liable for the =
massive WikiLeaks data dump that wound up with Chelsea Manning in prison fo=
r a long while and Julian Assange in the Ecuadorian Embassy in London.=C2=
=A0 Since autonomous networks don&#39;t exist as a legal subject, efforts t=
o determine accountability ranged from Manning only all the way through to =
everyone who had looked at a tweet about the case (<a href=3D"https://urlde=
fense.com/v3/__https://ijoc.org/index.php/ijoc/article/view/2668__;!!KwNVnq=
Rv!Tz24KK93zR7-vlgITffJXfcYuxYYLdJWEG_qIB6L-XN_o8XIxRb-e6k0uhG32RfJt2s$" ta=
rget=3D"_blank">https://ijoc.org/index.php/ijoc/article/view/2668</a>).=C2=
=A0=C2=A0</div><div><br></div><div>You will want to conclude your discussio=
n of assembly and association with clear rules for how you would distinguis=
h assembly from association in the digital environment.=C2=A0 Which is Wiki=
Leaks, given the shifting and anonymous membership?=C2=A0 The distinction b=
etween the two matters for how each is treated by legal systems.=C2=A0 In t=
he case of the Jan. 6, 2021, event at the US Capitol, legal matters are pro=
ceeding with great care to ensure that people who assembled in the space bu=
t were not a part of an association committed to violence are not treated a=
s if they were a part of that association.=C2=A0 Legal liability for action=
s goes up in US law, and I&#39;m sure under many bodies of law, where there=
 is association.=C2=A0 Thus the importance of &quot;conspiracy,&quot; &quot=
;racketeering,&quot; and &quot;collusion&quot; as terms of importance in re=
solving legal cases involving, in turn, illegal violent political action, c=
rime, and competition/antitrust law.</div><div><br></div><div><u>Cases</u><=
/div><div><u><br></u></div><div>Any selection of cases needs justification.=
=C2=A0 The authors state at the opening of the section discussing cases tha=
t not all of what is mentioned is actually addressable at the protocol leve=
l that is the business of the IETF to which this document is directed.=C2=
=A0 <b>By doing so, the authors provide strong, active support for those wh=
o insist that the human rights issues being discussed are just not the busi=
ness of the IETF.</b>=C2=A0 I strongly encourage the authors to include onl=
y cases for which they can demonstrate the role of protocol design and netw=
ork architecture.=C2=A0 For every such case, the piece would be much strong=
er if an actual recommendation regarding alternative choices for protocol d=
esign or network architecture are offered. Dave Clark&#39;s <i>Designing an=
 Internet</i>=C2=A0provides a superb model for how this kind of linkage bet=
ween the two kinds of concerns can be drawn.</div><div><br></div><div><u>Wr=
iting Issues</u></div><div><br></div><div>&quot;Assembly&quot; and &quot;as=
sociation&quot; should be included among the terms defined at the opening o=
f the piece.</div><div><br></div><div>The pertinence of the cases will be m=
ore clear to the reader if you are explicit in each one just how assembly o=
r association are involved.</div><div><br></div><div>Bring the three separa=
te notes on what the Internet is together into an internally coherent parag=
raph.</div><div><br></div><div>The cases rely too much on quotes.</div><div=
><br></div><div>The reference list should include full citations in additio=
n to links for professionalism, and needs some cleaning up.</div><div><br><=
/div><div>There are a number of word use, punctuation, and grammatical erro=
rs throughout.</div><div><br></div><div>This draft concludes with some high=
-level statements and then all of a sudden turns to introducing a new issue=
.=C2=A0 You can find a better close.</div><div><br></div><div><u>Utility fo=
r IETF Readers</u></div><div><u><br></u></div><div>Assuming you would like =
this to be actually used by IETF participants, can you include, in the conc=
lusion, a checklist of things that those involved in protocol design and ne=
twork architecture can actually look out for in the course of their work?=
=C2=A0=C2=A0</div><div><br></div><div><br></div></div></div>
_______________________________________________<br>
hrpc mailing list<br>
<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a><br>
<a href=3D"https://urldefense.com/v3/__https://www.irtf.org/mailman/listinf=
o/hrpc__;!!KwNVnqRv!Tz24KK93zR7-vlgITffJXfcYuxYYLdJWEG_qIB6L-XN_o8XIxRb-e6k=
0uhG3L5TkV0s$" rel=3D"noreferrer" target=3D"_blank">https://urldefense.com/=
v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!Tz24KK93zR7-vl=
gITffJXfcYuxYYLdJWEG_qIB6L-XN_o8XIxRb-e6k0uhG3L5TkV0s$</a> <br>
</blockquote></div></div>

--00000000000071a8a205baac028f--


From nobody Sat Feb  6 13:22:13 2021
Return-Path: <bzs@theworld.com>
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 95B543A2C3F for <hrpc@ietfa.amsl.com>; Sat,  6 Feb 2021 13:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_SPF_HELO_TEMPERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 PkF_jeprJnf1 for <hrpc@ietfa.amsl.com>; Sat,  6 Feb 2021 13:22:07 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) (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 2C8793A2C3E for <hrpc@irtf.org>; Sat,  6 Feb 2021 13:22:06 -0800 (PST)
Received: from pcls8.std.com (pcls8.std.com [192.74.137.148]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id 116LLi8m004025; Sat, 6 Feb 2021 16:21:46 -0500
Received: from pcls8 (localhost [127.0.0.1]) by pcls8.std.com (8.14.5/8.14.5) with ESMTP id 116LLbaZ001500; Sat, 6 Feb 2021 16:21:39 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <24607.2145.970125.202721@gargle.gargle.HOWL>
Date: Sat, 6 Feb 2021 16:21:37 -0500
From: bzs@theworld.com
To: Sandra Braman <braman@tamu.edu>
Cc: hrpc@irtf.org
In-Reply-To: <CAB2unbNd=Oe0mrufK3eVsaY93fJ1e22yXn0rLq7+fL2ZvgNckQ@mail.gmail.com>
References: <mailman.2188.1612600458.7093.hrpc@irtf.org> <CAB2unbNd=Oe0mrufK3eVsaY93fJ1e22yXn0rLq7+fL2ZvgNckQ@mail.gmail.com>
X-Mailer: VM 8.2.0b under 24.3.1 (x86_64-suse-linux-gnu)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/-lV5_cX1Zb6JC34Y5J41lsOJP4k>
Subject: Re: [hrpc] further re draft association
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: Sat, 06 Feb 2021 21:22:12 -0000

On February 6, 2021 at 08:48 braman@tamu.edu (Sandra Braman) wrote:
 > Should have gone further myself re the concept of association.=A0 In=
 US law --
 > again, only one body of national law, but illustrative of what work =
further
 ...

Wow that was an excellent read. Thank you.

--=20
        -Barry Shein

Software Tool & Die    | bzs@TheWorld.com             | http://www.TheW=
orld.com
Purveyors to the Trade | Voice: +1 617-STD-WRLD       | 800-THE-WRLD
The World: Since 1989  | A Public Information Utility | *oo*


From nobody Thu Feb 11 15:23:18 2021
Return-Path: <braman@tamu.edu>
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 6E4383A0E0F for <hrpc@ietfa.amsl.com>; Thu, 11 Feb 2021 15:23:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 zZWsfrl0UKyG for <hrpc@ietfa.amsl.com>; Thu, 11 Feb 2021 15:23:10 -0800 (PST)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 1D2E53A0E11 for <hrpc@irtf.org>; Thu, 11 Feb 2021 15:23:09 -0800 (PST)
Received: by mail-il1-x133.google.com with SMTP id d20so1954311ilo.4 for <hrpc@irtf.org>; Thu, 11 Feb 2021 15:23:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=ee2IRgQuJe8pjqmWOzxBsIQQ+o7tQndDTvr/odaEqZ8=; b=1QSZxu3UwvPmMK99BfkpzqORxJtqqvcFxXYYb5t4/qwTAoopzWv/MtsinNZtM3zsYF gcaXJ79VYFH2rNKS9fXOKuuHZdjz4Y9bZ7B13vTgDGhi5ehVb2e/M//qGyG030rrbdUS bmDYAmODNa27bAk17oz3g8+fRKq9H4UPzdQkyLPYXf07mj3PblJRWWhZzfAB3v8nsrhq Kpu5OkajAAiO8u+id6wKQ7yTzoUw/0LqVxpOikwQlItrZagroxkL0gFs7BOspz3qNoT9 lt2eYkehA9yOyjcT43oa/vE2gJHN4QxvddwIdFDxm3CgU1TjifahGZ50lAJvqDQDG/Iy atNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ee2IRgQuJe8pjqmWOzxBsIQQ+o7tQndDTvr/odaEqZ8=; b=aXpe2uSmloWZkZoSuno/dXZo37FighKNkZZormOdwZBUPYJ7YkALu7vnFHMyet090o /UaUzKgdxtYHi7/adMNa7OjDGOe5LD+C26fVnZRHt1EPw3J05xEMu/1pfCQSEw2tyr73 oGwegxFspv5nRIGCrLf9XPfdOqbdL3TYrOHxKPKuNzW4t87PRvlMmRTwHdxy6/It5FBT 4Ey7G5twwRd3XYIxQlna5RcTSTIWpyYo+HzxOeCvoyUmXWMiNx/g9wXlKybZgh9CbDOj GsjbnU2lqjZ2oO/QI/PDyRH4f92x/0W1SubE1dZUsfLBtVSYQ7ymR24YKWO9onvq/B6/ GM9g==
X-Gm-Message-State: AOAM532uSuW4tE3IDqCQK0lp187VYakhYzGsVeRCv6MNg/syOVewl/WJ us3Han1hd+r1owAobqi5JVVTM/EuJKguRICLSl8JXyzbmQM24oF3
X-Google-Smtp-Source: ABdhPJxlq5j3YkNjUYH1HqU2tO6SuUeytcv2K9bpSILDx7TT0NAW7OT5m1WhhmZi6WYEl5c10q73DFrcJlNudGR0xL0=
X-Received: by 2002:a05:6e02:1c8e:: with SMTP id w14mr313559ill.303.1613085786608;  Thu, 11 Feb 2021 15:23:06 -0800 (PST)
MIME-Version: 1.0
From: Sandra Braman <braman@tamu.edu>
Date: Thu, 11 Feb 2021 17:25:04 -0600
Message-ID: <CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com>
To: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="0000000000004daffb05bb17cd1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/aaz9Lf-J-2U4ZoH_azJWDJBbbJk>
Subject: [hrpc] comments on draft 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, 11 Feb 2021 23:23:17 -0000

--0000000000004daffb05bb17cd1e
Content-Type: text/plain; charset="UTF-8"

Folks --

Following are some comments on draft guidelines, some of which echo points
already made on this list. If I've misunderstood anything, please let me
know.  Some of the comments are analytical.  Others are recommendations
that may make the document more effective.  Again, thanks to the authors
and those who provided feedback and input to the authors for all the labor
put in.

Sandra Braman

----------------------------------------------------------

*Human Rights*

Graph 2 on page 4 identifies key sources of human rights.  The manner of
presentation conflates documents from sources that are importantly
different regarding their source and, thus, relative weight.  A document
created by the Internet Governance Forum -- a talk shop only that has no
status within the international legal system on its own -- with United
Nations treaties.  This section of the document will be much stronger if
separate paragraphs discuss actual legal foundations for human rights and
other sources of proposals for things that should be considered human
rights in the Internet environment (the latter would include Hill 2014,
too, for example).  The IGF document is certainly pertinent, but should be
discussed in the manner one would discuss the scholarly literature and
"gray matter" (reports from advocacy groups and non-profit organizations,
etc.), not as if it were international law.

Which human rights will be discussed in this document should be clearly
articulated in the opening section, with definitions for the purposes of
this document and the sources of those rights, and then used consistently
throughout the document.  Late in the document the "right to security"
shows up; is this a rephrasing of Article 28 of the Universal Declaration
on Human Rights, or something else that is not mentioned on page 4?

Theoretically and operationally defining each concept presented as a human
right more thoroughly will be important.  There is confusion in this
document, for example, between the right to access government information,
which is included in a number of constitutions and constitution-like
documents around the world and is considered essential to the ability to
hold governments accountable for their action, and a right to access
information in general (more typically considered necessary to freedom of
expression, since in order to talk about something you have to have
information about it).

What arguments justify which two or three human rights of concern for each
item in section 3.3?  As presented in this draft, it seems essentially
random in a manner that is not persuasive regarding what is in and what is
out.

*Direct vs Indirect Violations of Human Rights*

Perhaps the most interesting thread running through this document is the
implicit suggestion that impediments to technological innovation can
themselves be understood as violations of human rights.  (Fully developing
that argument would make a great scholarly journal article!)  I buy that
argument, as innovations are often/may well be needed to develop
work-arounds for exercises of power that violate human rights in
traditionally understood ways, but this piece will be much more effective
and stronger if it makes that argument explicit and uses it as a tool in
the structuring of the narrative.

The suggestions are two:  (1) Add an explicit discussion of the distinction
between direct violations of human rights (e.g., censorship) and indirect
violations of human rights (e.g., innovation, which includes matters such
as "adaptability" as introduced in this draft). (2) Structure the
discussion of topics in Section 3.3 to clearly distinguish between the
two.  A recommendation for an alternative structuring of those topics can
be found below.

Another distinction that could usefully be introduced in this document is
the difference between short-term and long-term effects on human rights.
Censorship is a short-term, immediate effect.  Differential ability to
access information about one's environment and that provides the
affordances for effective political action -- what was first labelled "the
knowledge gap" in the 1970s and is now more commonly referred to as "the
digital divide" -- is better understood as a long-term effect on human
rights.

*Stages of the Internet Design Process and the Institutional Context*

This draft mentions that different human rights issues come up at different
stages of the protocol development process.  It also asks for a lot of
types of research and thinking that, as others have pointed out, are not
generally within the job description of those working on Internet protocols
and for which they may not have been trained -- these are actually matters
of organizational design.  This document would be much stronger if it
unbundled each of these things.

For stages of the protocol design process, please say more about which
issues should be considered when?  Doing so would require offering a model
of the stages of the protocol design process.  It would be great to have a
section that does that and that then specifies which issues would be of
concern when.  The authors will probably want to include "implementation"
among the stages discussed.

On the organizational design side, the document would be stronger if it
offered at least a model of what an organizational structure might be that
would include all of the different kinds of expertise required to do the
work asked for here, along with a mapping of the work flow across employees
with different types of expertise.

*Research on the Effects of Design Decisions*

A recurring problem in research on communication and the media is confusing
what can be learned from research on an actual text or set of visuals and
the effects of that text or visuals on those who receive it.  In that
context, textual analysis can only tell the researcher what is in the text;
for effects research, quite other research methods must be used.  The same
problem runs throughout this document.  The authors are encouraged to
clearly distinguish the features of a protocol itself, how the protocol
operates within the network (the technical "context" in the sense of how it
interacts with other protocols), how it is used in the application layer,
how applications are used, and the effects of the uses of those
applications.  A second issue raised by the methods introduced here is that
they run the danger of being limited to "looking under the streetlight"
(the familiar story about where a drunk is looking for keys, irrespective
of where they may be), although in terms of provenance that problem may be
more reflective of the fact that the full scholarly literature and what can
be learned from researchers outside of the HRPC have not yet been brought
to bear.

Different research methods will be needed to examine each of these.  This
document would be much stronger if it broke out which of the kinds of
questions raised can actually be the subjects of research at each stage of
this sequence, too.  The mixing of application layer and use issues with
protocol design in my view undermines the effectiveness of the argument
this reader, at least, understands the authors to be trying to make.

Research on designer perceptions of possible human rights risks can be
useful and interesting (I've done some of that research myself), but does
not tell the researcher anything about the actual risks as experienced or
as understood by social scientists who have studied those effects on the
ground. There are, however, several significant bodies of research that the
authors could mine for more empirical detail on the effects of specific
protocol design features rather than assuming that universe is bounded by
what one or a few members of HRPC have done or asking computer scientists
and electrical engineers to undertake all of that work.  It is incredibly
important to keep human rights issues in front of those doing technical
work, including regularly showing up in IETF meetings to alert those
designing protocols to specific issues, but for research on the effects of
those protocols HRPC should be turning to social scientists who are
actually studying the effects and who could be encouraged to go further in
this area, sometimes -- so valuably -- in collaboration with technical
experts who have given themselves to this specific task.  In this regard,
the work of Ron Deibert's group at the University of Toronto (Citizen Lab)
should be highlighted as a model (https://citizenlab.ca/).  Work in fields
such as anthropology, sociology, political science, information science,
communication, STS (studies of technology and society), and economics will
all be useful.

To date the HRPC (to my knowledge) has largely engaged with the communities
of researchers working in this area by bringing individuals to IETF
meetings for short presentations.  Given the relatively small number of
people active within HRPC who come from social science backgrounds and
limits on the time of everyone within HRPC, some assistance may be needed
to take advantage of the many additional research methods that should be
used to evaluate the effects of protocol design on human rights as well as
to incorporate findings from research in this area already conducted into
this document.  A few thoughts regarding how that might be done will be
offered in a separate email.

However it is done, going much further with research methods will
significantly increase the sophistication and utility of this document.  As
it currently stands, the section on "expert interviews" is confusing
because it appears to be asking computer scientists to be expert on social
science matters, for example.  Interviews with various types of experts
will indeed be among the kinds of methods that can be useful, but the
different types of expertise involved should be acknowledged and different
kinds of questions would be asked of different kinds of experts.

*Grouping of Section 3.3 Topics*

Three dimensions of analysis could be used to better structure the
sequencing of topics in Section 3.3.  The suggestion here is to use the
focus of attention as the highest level used to group related issues
together, and then discuss differences between direct and indirect effects
and between short-term and long-term effects within each of the
categories.  A suggestion what the top-level of categorization might look
like is offered here, with the current number of the topics to be included
within it.  Because some of the current topics combine types of issues, the
final category includes one item that in my view should be unbundled for
clarification for the purposes of this document and three items that in my
view should be deleted.  The following section discusses individual topics
and/or the combinations suggested here.

*Network Operations*

Connectivity (3.3.1)
Internationalization (3.3.5)
Localization (3.3.11)
Adaptability (3.3.17)

Open Standards (3.3.7)
Heterogeneity Support (3.3.8)

Decentralization (3.3.12)

Reliability (3.3.13)

*The Individual User*

Privacy (3.3.2)
Pseudonymity (3.3.9)
Confidentiality (3.3.14)
Anonymity (3.3.19)

Accessibility (3.3.10)

*Content*

Content Agnosticism (3.3.3)

Censorship Resistance (3.3.6)
Integrity (3.3.15)
Authenticity (3.3.16)

*To Be Unbundled*

Security (3.3.4)

*Delete*

Outcome Transparency (3.3.18)
Remedy and Attribution (3.3.20)
Miscellaneous Considerations (3.3.21)

*Discussion of Topics and Topic Groupings*

*Network Operations*

Decentralization is separated out because the extent to which
decentralization can occur operates at so many different levels of the
structures involved -- the network, applications, the social structure, and
political structure -- that it is different in kind from the first 5 items
above that seem to me (as someone who is NOT a technical expert) to be
related to each other.  Reliability also seems to me to be different in
kind.

In the scholarly journal article "The Framing Years," the concept of
"technological democracy" as a key design principle for the Internet was
introduced.  The topics of Open Standards and Heterogeneity additionally
can be distinguished by this feature.

The Decentralization topic mixes several different types of control from
diverse sources (governments, protocol limits, etc.) together without
distinguishing them.  The document will be stronger, clearer, and more
useful if it distinguishes them.

In the scholarly journal article "The Geopolitical and the Network
Political:  Internet Designers and Governance," the tension between
geopolitical citizenship (allegiance to one's identity as a citizen of a
geopolitically recognized state -- a government recognized by the UN) and
network citizenship (allegiance to one's identity as a user/citizen of the
Internet, the success of which is critical to the user) is explored.  There
are often instances in which what is required of the geopolitical citizen
is the opposite of what is required of the network citizen.  That is the
tension discussed on page 17, graph 2.

*The Individual User*

All of the topics related to the diverse dimensions of personal privacy
should be grouped together.  They would be best introduced with a general
introduction to RFC 4949.  Doing so would then facilitate further analysis
of what might differently be needed to attend to when thinking about each
of the concepts distinguished there (if there are differences).

Accessibility is different in kind as a topic.  However, the RFC referred
to in that discussion, as I understand it, actually refers to technical
limits and/or limits of access to images that may be in place because of a
particular tool a specific individual chooses to use, not to human
disability.  Is there anything else that deals with human disability at the
protocol level that can be called upon here more validly?  Most of what I
am aware of is at the application level.

*Content*

Content agnosticism is a tough one for two reasons.  First, any decision
about structure made by definition will preference some content or users
(and thus those users' content) over others -- for any door that is opened,
another door is shut.  By the close of the 1990s (the period through which
my own research went), several different models were experimented with to
achieve "fair queuing," and struggles with "quality of service" have
continued since.  What is said here about content agnosticism should
reference all of that history and make specific recommendations if it sees
a way out of this dilemma that others have not yet been able to discover.
Second, national governments are always going to assert priority access.
It is wishful thinking only to believe that would be otherwise.  The fix
here for this document would be to simply acknowledge that.

In the discussion of Authenticity, isn't there another scenario when
considering authentication?  This would add another line to the last
scenario provided:  Bob knows who or what altered the data that did not
come from Alice.  Why should this not also be a requirement?  Surveillance
should go both ways (that is why we have access to government information
as a fundamental constitutional principle).

*To be Unbundled*

The existing topic of "security" includes elements that would, in my view,
be more strongly included if they were unbundled, with elements dispersed
into the above categories to join those that are like of kind.

*To be Deleted*

Outcome Transparency -- This is a reasonable expectation only if every
organization employing those involved in the protocol design process were
to take up recommendations these authors have yet to develop for
organizational structure and work flow processes adequate to the range of
kinds of research being asked for here.  Since it is unlikely that those
recommendations for organizational structure and work flow processes, will
be forthcoming within the probable life cycle of the writing of this
document, and since it is even more unlikely that all of the organizations
involved would follow such recommendations if offered, in my view it would
strengthen the document by deleting this item.  Doing so would be a
defensive writing gesture warding off critiques of naivete.

Remedy and Attribution -- Others have made excellent points on this matter
on the listserv.  Everything that would be pertinent here should be covered
by the topics introduced that apply to individual users.  If that is not
the case, the authors need to make clear what else would be involved.
Delete as a topic but add to the discussion that introduces the document.

Miscellaneous Considerations -- Don't see what this obvious point adds.

*Other Conceptual Issues*

How do the authors distinguish between the effects of protocol-shaped
communications between humans, between humans and non-humans, and between
non-humans from a human rights perspective?  Protocol design features that
impede the ability to make effective use of what is learned from
environmental sensors, for example, could generage long-term human rights
impacts.  Not mentioned at all here but it would be a stronger document if
it were.

Page 6, graph 4 (in 3.3) -- What is meant by "misapplication of the
protocol or technology"?  That is really two questions in one.  First, how
do the authors distinguish an appropriate application from a
misapplication?  Second, as again has been brought up in discussion of this
draft on the list, isn't this about users and not the protocol design that
is the focus of the document?  Those involved with attempts to prevent uses
of dual use technologies for purposes of war rather than peace have
struggled with this for decades; the inability to meaningfully, defensibly,
and effectively grab ahold of it has essentially led to the abandonment of
the effort.

How do the authors evaluate the "adequacy" with which a given protocol
takes human rights into account?  (page 6, graph 5)

The question of whether or not protocols need to be understandable by
humans is one of the most amusing elements of discussion in the RFCs during
their first decade (1969-1979) (again, an article available if of
interest).  In 3.3.5, on internationalization (p. 9, second graph from
bottom), the question is about text strings that "have to be" understood or
entered by humans.  What about situations in which the more accurate verb
would be "can be"?

Re Internationalization -- See my comments on draft association re the
language issue.

In areas such as degradation, the distinction should be drawn between
degradation and knowledge of degradation.  That is also true for integrity
and in other areas that can, under some circumstances, also include even
censorship.

*Writing Issues*

3.2.1 -- This paragraph is opaque.

3.2.2 -- This paragraph is tautological.

3.3.2 -- Page 8, graph 3 -- The document on privacy is not an "example."

3.3.20 -- Page 23, graph 1 -- The reference to Kaye's thinking on freedom
of expression and the Internet belongs in the discussion of human rights
principles, not here.

There are a number of typographical and grammar errors throughout.

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

<div dir=3D"ltr">Folks --=C2=A0<div><br></div><div>Following are some comme=
nts on draft guidelines, some of which echo points already made on this lis=
t. If I&#39;ve misunderstood anything, please let me know.=C2=A0 Some of th=
e comments are analytical.=C2=A0 Others are recommendations that may make t=
he document more effective.=C2=A0 Again, thanks to the authors and those wh=
o provided feedback and input to the authors for all the labor put in.<br><=
/div><div><br>Sandra Braman</div><div><br></div><div>----------------------=
------------------------------------</div><div><br></div><div><u>Human Righ=
ts</u></div><div><br></div><div>Graph 2 on page 4 identifies key sources of=
 human rights.=C2=A0 The manner of presentation conflates documents from so=
urces that are importantly different regarding their source and, thus, rela=
tive weight.=C2=A0 A document created by the Internet Governance Forum -- a=
 talk shop only that has no status within the international legal system on=
 its own -- with United Nations treaties.=C2=A0 This section of the documen=
t will be much stronger if separate paragraphs discuss actual legal foundat=
ions for human rights and other sources of proposals for things that should=
 be considered human rights in the Internet environment (the latter would i=
nclude Hill 2014, too, for example).=C2=A0 The IGF document is certainly pe=
rtinent, but should be discussed in the manner one would discuss the schola=
rly literature and &quot;gray matter&quot; (reports from advocacy groups an=
d non-profit organizations, etc.), not as if it were international law.</di=
v><div><br></div><div>Which human rights will be discussed in this document=
 should be clearly articulated in the opening section, with definitions for=
 the purposes of this document and the sources of those rights, and then us=
ed consistently throughout the document.=C2=A0 Late in the document the &qu=
ot;right to security&quot; shows up; is this a rephrasing of Article 28 of =
the Universal Declaration on Human Rights, or something else that is not me=
ntioned on page 4?</div><div><br></div><div>Theoretically and operationally=
 defining each concept presented as a human right more thoroughly will be i=
mportant.=C2=A0 There is confusion in this document, for example, between t=
he right to access government information, which is included in a number of=
 constitutions and constitution-like documents around the world and is cons=
idered essential to the ability to hold governments accountable for their a=
ction, and a right to access information in general (more typically conside=
red necessary to freedom of expression, since in order to talk about someth=
ing you have to have information about it).</div><div><br></div><div>What a=
rguments justify which two or three human rights of concern for each item i=
n section 3.3?=C2=A0 As presented in this draft, it seems essentially rando=
m in a manner that is not persuasive regarding what is in and what is out.<=
/div><div><br></div><div><u>Direct vs Indirect Violations of Human Rights</=
u></div><div><u><br></u></div><div>Perhaps the most interesting thread runn=
ing through this document is the implicit suggestion that impediments to te=
chnological innovation can themselves be understood as violations of human =
rights.=C2=A0 (Fully developing that argument would make a great scholarly =
journal article!)=C2=A0 I buy that argument, as innovations are often/may w=
ell be needed to develop work-arounds for exercises of power that violate h=
uman rights in traditionally understood ways, but this piece will be much m=
ore effective and stronger if it makes that argument explicit and uses it a=
s a tool in the structuring of the narrative.</div><div><br></div><div>The =
suggestions are two:=C2=A0 (1) Add an explicit discussion of the distinctio=
n between direct violations of human rights (e.g., censorship) and indirect=
 violations of human rights (e.g., innovation, which includes matters such =
as &quot;adaptability&quot; as introduced in this draft). (2) Structure the=
 discussion of topics in Section 3.3 to clearly distinguish between the two=
.=C2=A0 A recommendation for an alternative structuring of those topics can=
 be found below.</div><div><br></div><div>Another distinction that could us=
efully be introduced in this document is the difference between short-term =
and long-term effects on human rights.=C2=A0 Censorship is a short-term, im=
mediate effect.=C2=A0 Differential ability to access information about one&=
#39;s environment and that provides the affordances for effective political=
 action -- what was first labelled &quot;the knowledge gap&quot; in the 197=
0s and is now more commonly referred to as &quot;the digital divide&quot; -=
- is better understood as a long-term effect on human rights.</div><div><br=
></div><div><u>Stages of the Internet Design Process and the Institutional =
Context</u></div><div><u><br></u></div><div>This draft mentions that differ=
ent human rights issues come up at different stages of the protocol develop=
ment process.=C2=A0 It also asks for a lot of types of research and thinkin=
g that, as others have pointed out, are not generally within the job descri=
ption of those working on Internet protocols and for which they may not hav=
e been trained -- these are actually matters of organizational design.=C2=
=A0 This document would be much stronger if it unbundled each of these thin=
gs.</div><div><br></div><div>For stages of the protocol design process, ple=
ase say more about which issues should be considered when?=C2=A0 Doing so w=
ould require offering a model of the stages of the protocol design process.=
=C2=A0 It would be great to have a section that does that and that then spe=
cifies which issues would be of concern when.=C2=A0 The authors will probab=
ly want to include &quot;implementation&quot; among the stages discussed.</=
div><div><br></div><div>On the organizational design side, the document wou=
ld be stronger if it offered at least a model of what an organizational str=
ucture might be that would include all of the different kinds of expertise =
required to do the work asked for here, along with a mapping of the work fl=
ow across employees with different types of expertise.</div><div><br></div>=
<div><u>Research on the Effects of Design Decisions</u></div><div><u><br></=
u></div><div>A recurring problem in research on communication and the media=
 is confusing what can be learned from research on an actual text or set of=
 visuals and the effects of that text or visuals on those who receive it.=
=C2=A0 In that context, textual analysis can only tell the researcher what =
is in the text; for effects research, quite other research methods must be =
used.=C2=A0 The same problem runs throughout this document.=C2=A0 The autho=
rs are encouraged to clearly distinguish the features of a protocol itself,=
 how the protocol operates within the network (the technical &quot;context&=
quot; in the sense of how it interacts with other protocols), how it is use=
d in the application layer, how applications are used, and the effects of t=
he uses of those applications.=C2=A0 A second issue raised by the methods i=
ntroduced here is that they run the danger of being limited to &quot;lookin=
g under the streetlight&quot; (the familiar story about where a drunk is lo=
oking for keys, irrespective of where they may be), although in terms of pr=
ovenance that problem may be more reflective of the fact that the full scho=
larly literature and what can be learned from researchers outside of the HR=
PC have not yet been brought to bear.</div><div><br></div><div>Different re=
search methods will be needed to examine each of these.=C2=A0 This document=
 would be much stronger if it broke out which of the kinds of questions rai=
sed can actually be the subjects of research at each stage of this sequence=
, too.=C2=A0 The mixing of application layer and use issues with protocol d=
esign in my view undermines the effectiveness of the argument this reader, =
at least, understands the authors to be trying to make.=C2=A0</div><div><br=
></div><div>Research on designer perceptions of possible human rights risks=
 can be useful and interesting (I&#39;ve done some of that research myself)=
, but does not tell the researcher anything about the actual risks as exper=
ienced or as understood by social scientists who have studied those effects=
 on the ground. There are, however, several significant bodies of research =
that the authors could mine for more empirical detail on the effects of spe=
cific protocol design features rather than assuming that universe is bounde=
d by what one or a few members of HRPC have done or asking computer scienti=
sts and electrical engineers to undertake all of that work.=C2=A0 It is inc=
redibly important to keep human rights issues in front of those doing techn=
ical work, including regularly showing up in IETF meetings to alert those d=
esigning protocols to specific issues, but for research on the effects of t=
hose protocols HRPC should be turning to social scientists who are actually=
 studying the effects and who could be encouraged to go further in this are=
a, sometimes -- so valuably -- in collaboration with technical experts who =
have given themselves to this specific task.=C2=A0 In this regard, the work=
 of Ron Deibert&#39;s group at the University of Toronto (Citizen Lab) shou=
ld be highlighted as a model (<a href=3D"https://citizenlab.ca/">https://ci=
tizenlab.ca/</a>).=C2=A0 Work in fields such as anthropology, sociology, po=
litical science, information science, communication, STS (studies of techno=
logy and society), and economics will all be useful.</div><div><br></div><d=
iv>To date the HRPC (to my knowledge) has largely engaged with the communit=
ies of researchers working in this area by bringing individuals to IETF mee=
tings for short presentations.=C2=A0 Given the relatively small number of p=
eople active within HRPC who come from social science backgrounds and limit=
s on the time of everyone within HRPC, some assistance may be needed to tak=
e advantage of the many additional research methods that should be used to =
evaluate the effects of protocol design on human rights as well as to incor=
porate findings from research in this area already conducted into this docu=
ment.=C2=A0 A few thoughts regarding how that might be done will be offered=
 in a separate email.</div><div><br></div><div>However it is done, going mu=
ch further with research methods will significantly increase the sophistica=
tion and utility of this document.=C2=A0 As it currently stands, the sectio=
n on &quot;expert interviews&quot; is confusing because it appears to be as=
king computer scientists to be expert on social science matters, for exampl=
e.=C2=A0 Interviews with various types of experts will indeed be among the =
kinds of methods that can be useful, but the different types of expertise i=
nvolved should be acknowledged and different kinds of questions would be as=
ked of different kinds of experts.</div><div><br></div><div><u>Grouping of =
Section 3.3 Topics</u></div><div><u><br></u></div><div>Three dimensions of =
analysis could be used to better structure the sequencing of topics in Sect=
ion 3.3.=C2=A0 The suggestion here is to use the focus of attention as the =
highest level used to group related issues together, and then discuss diffe=
rences between direct and indirect effects and between short-term and long-=
term effects within each of the categories.=C2=A0 A suggestion what the top=
-level of categorization might look like is offered here, with the current =
number of the topics to be included within it.=C2=A0 Because some of the cu=
rrent topics combine types of issues, the final category includes one item =
that in my view should be unbundled for clarification for the purposes of t=
his document and three items that in my view should be deleted.=C2=A0 The f=
ollowing section discusses individual topics and/or the combinations sugges=
ted here.=C2=A0</div><div><br></div><div><i>Network Operations</i></div><di=
v><i><br></i></div><div>Connectivity (3.3.1)</div><div>Internationalization=
 (3.3.5)</div><div>Localization (3.3.11)</div><div>Adaptability (3.3.17)<br=
></div><div><br></div><div><div>Open Standards (3.3.7)</div><div>Heterogene=
ity Support (3.3.8)</div></div><div><br></div><div>Decentralization (3.3.12=
)</div><div><br></div><div>Reliability (3.3.13)</div><div><br></div><div><i=
>The Individual User</i></div><div><i><br></i></div><div>Privacy (3.3.2)</d=
iv><div>Pseudonymity (3.3.9)</div><div>Confidentiality (3.3.14)</div><div>A=
nonymity (3.3.19)</div><div><br></div><div>Accessibility (3.3.10)</div><div=
><br></div><div><i>Content</i></div><div><i><br></i></div><div>Content Agno=
sticism (3.3.3)</div><div><br></div><div>Censorship Resistance (3.3.6)</div=
><div>Integrity (3.3.15)</div><div>Authenticity (3.3.16)</div><div><br></di=
v><div><i>To Be Unbundled</i></div><div><i><br></i></div><div>Security (3.3=
.4)=C2=A0</div><div><br></div><div><i>Delete</i></div><div><br></div><div>O=
utcome Transparency (3.3.18)</div><div>Remedy and Attribution (3.3.20)</div=
><div>Miscellaneous Considerations (3.3.21)</div><div><i><br></i></div><div=
><u>Discussion of Topics and Topic Groupings</u></div><div><u><br></u></div=
><div><i>Network Operations</i></div><div><i><br></i></div><div>Decentraliz=
ation is separated out because the extent to which decentralization can occ=
ur operates at so many different levels of the structures involved -- the n=
etwork, applications, the social structure, and political structure -- that=
 it is different in kind from the first 5 items above that seem to me (as s=
omeone who is NOT a technical expert) to be related to each other.=C2=A0 Re=
liability also seems to me to be different in kind.</div><div><br></div><di=
v>In the scholarly journal article &quot;The Framing Years,&quot; the conce=
pt of &quot;technological democracy&quot; as a key design principle for the=
 Internet was introduced.=C2=A0 The topics of Open Standards and Heterogene=
ity additionally can be distinguished by this feature.</div><div><br></div>=
<div>The Decentralization topic mixes several different types of control fr=
om diverse sources (governments, protocol limits, etc.) together without di=
stinguishing them.=C2=A0 The document will be stronger, clearer, and more u=
seful if it distinguishes them.</div><div><br></div><div>In the scholarly j=
ournal article &quot;The Geopolitical and the Network Political:=C2=A0 Inte=
rnet Designers and Governance,&quot; the tension between geopolitical citiz=
enship (allegiance to one&#39;s identity as a citizen of a geopolitically r=
ecognized state -- a government recognized by the UN) and network citizensh=
ip (allegiance to one&#39;s identity as a user/citizen of the Internet, the=
 success of which is critical to the user) is explored.=C2=A0 There are oft=
en instances in which what is required of the geopolitical citizen is the o=
pposite of what is required of the network citizen.=C2=A0 That is the tensi=
on discussed on page 17, graph 2.</div><div><br></div><div><i>The Individua=
l User</i></div><div><br></div><div>All of the topics related to the divers=
e dimensions of personal privacy should be grouped together.=C2=A0 They wou=
ld be best introduced with a general introduction to RFC 4949.=C2=A0 Doing =
so would then facilitate further analysis of what might differently be need=
ed to attend to when thinking about each of the concepts distinguished ther=
e (if there are differences).</div><div><br></div><div>Accessibility is dif=
ferent in kind as a topic.=C2=A0 However, the RFC referred to in that discu=
ssion, as I understand it, actually refers to technical limits and/or limit=
s of access to images that may be in place because of a particular tool a s=
pecific individual chooses to use, not to human disability.=C2=A0 Is there =
anything else that deals with human disability at the protocol level that c=
an be called upon here more validly?=C2=A0 Most of what I am aware of is at=
 the application level.</div><div><br></div><div><i>Content</i></div><div><=
br></div><div>Content agnosticism is a tough one for two reasons.=C2=A0 Fir=
st, any decision about structure made by definition will preference some co=
ntent or users (and thus those users&#39; content) over others -- for any d=
oor that is opened, another door is shut.=C2=A0 By the close of the 1990s (=
the period through which my own research went), several different models we=
re experimented with to achieve &quot;fair queuing,&quot; and struggles wit=
h &quot;quality of service&quot; have continued since.=C2=A0 What is said h=
ere about content agnosticism should reference all of that history and make=
 specific recommendations if it sees a way out of this dilemma that others =
have not yet been able to discover.=C2=A0 Second, national governments are =
always going to assert priority access.=C2=A0 It is wishful thinking only t=
o believe that would be otherwise.=C2=A0 The fix here for this document wou=
ld be to simply acknowledge that.</div><div><br></div><div>In the discussio=
n of Authenticity, isn&#39;t there another scenario when considering authen=
tication?=C2=A0 This would add another line to the last scenario provided:=
=C2=A0 Bob knows who or what altered the data that did not come from Alice.=
=C2=A0 Why should this not also be a requirement?=C2=A0 Surveillance should=
 go both ways (that is why we have access to government information as a fu=
ndamental constitutional principle).</div><div><br></div><div><i>To be Unbu=
ndled</i></div><div><i><br></i></div><div>The existing topic of &quot;secur=
ity&quot; includes elements that would, in my view, be more strongly includ=
ed if they were unbundled, with elements dispersed into the above categorie=
s to join those that are like of kind.</div><div><br></div><div><i>To be De=
leted</i></div><div><i><br></i></div><div>Outcome Transparency -- This is a=
 reasonable expectation only if every organization employing those involved=
 in the protocol design process were to take up recommendations these autho=
rs have yet to develop for organizational structure and work flow processes=
 adequate to the range of kinds of research being asked for here.=C2=A0 Sin=
ce it is unlikely that those recommendations for organizational structure a=
nd work flow processes, will be forthcoming within the probable life cycle =
of the writing of this document, and since it is even more unlikely that al=
l of the organizations involved would follow such recommendations if offere=
d, in my view it would strengthen the document by deleting this item.=C2=A0=
 Doing so would be a defensive writing gesture warding off critiques of nai=
vete.</div><div><br></div><div>Remedy and Attribution -- Others have made e=
xcellent points on this matter on the listserv.=C2=A0 Everything that would=
 be pertinent here should be covered by the topics introduced that apply to=
 individual users.=C2=A0 If that is not the case, the authors need to make =
clear what else would be involved.=C2=A0 Delete as a topic but add to the d=
iscussion that introduces the document.</div><div><br></div><div>Miscellane=
ous Considerations -- Don&#39;t see what this obvious point adds.</div><div=
><br></div><div><u>Other Conceptual Issues</u></div><div><u><br></u></div><=
div>How do the authors distinguish between the effects of protocol-shaped c=
ommunications between humans, between humans and non-humans, and between no=
n-humans from a human rights perspective?=C2=A0 Protocol design features th=
at impede the ability to make effective use of what is learned from environ=
mental sensors, for example, could generage long-term human rights impacts.=
=C2=A0 Not mentioned at all here but it would be a stronger document if it =
were.</div><div><br></div><div>Page 6, graph 4 (in 3.3) -- What is meant by=
 &quot;misapplication of the protocol or technology&quot;?=C2=A0 That is re=
ally two questions in one.=C2=A0 First, how do the authors distinguish an a=
ppropriate application from a misapplication?=C2=A0 Second, as again has be=
en brought up in discussion of this draft on the list, isn&#39;t this about=
 users and not the protocol design that is the focus of the document?=C2=A0=
 Those involved with attempts to prevent uses of dual use technologies for =
purposes of war rather than peace have struggled with this for decades; the=
 inability to meaningfully, defensibly, and effectively grab ahold of it ha=
s essentially led to the abandonment of the effort.</div><div><br></div><di=
v>How do the authors evaluate the &quot;adequacy&quot; with which a given p=
rotocol takes human rights into account?=C2=A0 (page 6, graph 5)</div><div>=
<br></div><div>The question of whether or not protocols need to be understa=
ndable by humans is one of the most amusing elements of discussion in the R=
FCs during their first decade (1969-1979) (again, an article available if o=
f interest).=C2=A0 In 3.3.5, on internationalization (p. 9, second graph fr=
om bottom), the question is about text strings that &quot;have to be&quot; =
understood or entered by humans.=C2=A0 What about situations in which the m=
ore accurate verb would be &quot;can be&quot;?</div><div><br></div><div>Re =
Internationalization -- See my comments on draft association re the languag=
e issue.</div><div><br></div><div>In areas such as degradation, the distinc=
tion should be drawn between degradation and knowledge of degradation.=C2=
=A0 That is also true for integrity and in other areas that can, under some=
 circumstances, also include even censorship.</div><div><br></div><div><u>W=
riting Issues</u><br></div><div><u><br></u></div><div>3.2.1 -- This paragra=
ph is opaque.</div><div><br></div><div>3.2.2 -- This paragraph is tautologi=
cal.</div><div><br></div><div>3.3.2 -- Page 8, graph 3 -- The document on p=
rivacy is not an &quot;example.&quot;</div><div><br></div><div>3.3.20 -- Pa=
ge 23, graph 1 -- The reference to Kaye&#39;s thinking on freedom of expres=
sion and the Internet belongs in the discussion of human rights principles,=
 not here.</div><div><br></div><div>There are a number of typographical and=
 grammar errors throughout.</div><div><br></div><div>=C2=A0</div><div><br><=
/div><div><br></div><div><u><br></u></div><div><br></div><div><u><br></u></=
div><div><br></div><div><u><br></u></div><div><br></div><div><br></div><div=
><u><br></u></div><div><u><br></u></div><div><br></div><div><br></div></div=
>

--0000000000004daffb05bb17cd1e--


From nobody Fri Feb 12 06:01:32 2021
Return-Path: <braman@tamu.edu>
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 8D4753A16A0 for <hrpc@ietfa.amsl.com>; Fri, 12 Feb 2021 06:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_DOTEDU=1.997] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 stMTWX1Ab1N7 for <hrpc@ietfa.amsl.com>; Fri, 12 Feb 2021 06:01:27 -0800 (PST)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 EAE193A16BC for <hrpc@irtf.org>; Fri, 12 Feb 2021 06:01:26 -0800 (PST)
Received: by mail-io1-xd30.google.com with SMTP id e133so9338422iof.8 for <hrpc@irtf.org>; Fri, 12 Feb 2021 06:01:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=xfqcNla/QunBBa+3qBrSW5A5VV3zflqqL69KB9kU+BI=; b=pAf3G3k4+3CHlVaYRY2NOsUArkVmenAoVvvaLFVFRp25Y1LXvXiAQ+/hUDOmPAXOVl 8D61OQU9IFA9H6V0/ck8W9eZt0Y1uJIkr8ieLc9t6yf6ZF54NbIoy5i7aO8MqQNyoYL2 ieMrP2cnvm/mSiY7xrpF7MLZJIET2nGiHVg7wPVXo9rRpweEd2MT1x6kyx764QUFmQcN yQD0Yx2BDGBu94AHmk0V2jgv9WAW3YihWiUnrCkLRet3TA/dQLoKqAXG5jqw/KNWbrhq UWNaqVMavt3qJUoj3uQqynDHvYJkS2hTauSeEvCNT+5Pr5wKcI7nDVSDz75lM/Jikhaw stjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xfqcNla/QunBBa+3qBrSW5A5VV3zflqqL69KB9kU+BI=; b=dIa5iYrIqsKUc1Roin84y2AW5DzqKawUIOeqCJWIfYntXM1u6oROupnYxSVMZypY6t MClx5SGHM3xWcu0oA2phuUjT/F5JZDrg6zoAuQWI3wR0ejj9GfFPZlIF0YTp3u2XhdqB XVbJ6dqaniNIkoLx+EBXtRs5UrENcMebzehtm4M6q4YpUzlbLG9NElaxD2/+3VpshVc2 dWxgmo2poVn3sb+pkcL1YFh95X+S0MOlVnDKLjYv+N8WDFlCdqFvPY+oDrXsk+YvYkTk 4JSrh3hwrVaC6+jPd9gnGpJVf7bTuJyRg0tfL1h4DxrV3Gq4Z1E7eJAFkltjPxYBPBFS WapQ==
X-Gm-Message-State: AOAM533oqvKZS5ORko6hg3Eff7zSR9zYqdX5cXMaKcXEa+19lNT/cwkw in1REK0DESs44zT4TYqerI2fm4xzdgKQebEa/1i1gnBMuaJ/i+rV
X-Google-Smtp-Source: ABdhPJxd7i59V9xRIuWy9GidC5aIyFm4Kr+79/iZSucZ4m33qguk7dfjj/Hwbv9ua8elnXo3XeV39UPL28+enrVRqPM=
X-Received: by 2002:a05:6638:33a0:: with SMTP id h32mr2802915jav.143.1613138482757;  Fri, 12 Feb 2021 06:01:22 -0800 (PST)
MIME-Version: 1.0
From: Sandra Braman <braman@tamu.edu>
Date: Fri, 12 Feb 2021 08:00:00 -0600
Message-ID: <CAB2unbNi=zDz+CyVsVC5qRopXouRH_9c_7BJ85vLg3GenXvjbg@mail.gmail.com>
To: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="0000000000003d217605bb24120e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ZAw4MVIAb5F1IFPdopnQGZscLiM>
Subject: [hrpc] some ideas for hrpc
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: Fri, 12 Feb 2021 14:01:31 -0000

--0000000000003d217605bb24120e
Content-Type: text/plain; charset="UTF-8"

Folks --

To complete what I've started, following are some ideas about ways HRPC
might enrich what it is doing going forward in the various areas in which
it is active.  Again, I may be misunderstanding the goals of the group,
there are always logistical issues, etc., but thought to put these out
there to get the conversation going.  There appear to be three functional
areas of what the group does, synergetically inter-related.

This is a very good time for HRPC to revisit its activities because the
decades-long struggle to bring the technical and policy communities into a
shared conversation has reached a new stage and now has a much more
significant institutional presence than it has historically.  (Hats off,
yet again and always, to groups such as the Center for Democracy and
Technology for providing leadership in this area so early, and to the other
non-profit groups that have now been in this terrain for a number of years,
such as Article 19 and the ACLU.)

Some of these ideas are relatively low-cost or no-cost.  Others would
require significant amounts of time investment by one or more individuals
and would probably need some grant-writing for support.  They also differ
in how pressing the need is.  For document development, in my view, the
need is very pressing.  The need to ensure and expand the presence of
knowledgeable individuals during IETF meetings is enduring.  The
development of pedagogical tools may be aspirational.

I look forward to hearing people's thoughts.

Sandra Braman

---------------------------------------------------------------------------------------------------------

*Arguments and Research Regarding Human Rights and Internet Protocols*

One strand of HRPC's activity involves the development of informational
RFCs suggesting relationships between human rights and Internet protocols
and encouraging the building of a research foundation to support ideas
about these relationships.  These documents will be stronger if they engage
more deeply with pertinent scholarly literature and with research
communities using a variety of methods to investigate such matters.

(1) One recommendation about how to achieve this would be to set up a
*scholarly
review board* that would review draft documents from a scholarly
perspective.  Participating in such a board would be very attractive to
academics who want to make a difference -- and who would definitely prefer
such meaningful institutionally-required service to many of the other
options on offer.  There is a model of this in at least one other of the
IRTF groups, so this works within the IETF context.

(2) So far HRPC has been bringing individual subject experts "in" to IETF;
that has been effective in multiple ways and I hope this will continue, if
not expand.  HRPC individuals going "out" to other communities would offer
additional benefits.  Thus a second recommendation in this area is for
authors to present *draft RFCs* to deep subject experts via *conference
presentations* on those researchers' own home turf for feedback.  This
would get a lot of feedback from people who are not otherwise involved with
HRPC and will lead authors into pertinent research findings and literatures
of which they may otherwise not be aware.

It would also serve the additional function of informing people in the many
professional scholarly associations that deal with technology policy
matters of the existence of HRPC  -- the vast majority of researchers
working in this area have no idea that HRPC exists even if they know about
the IETF.  That could lead to the involvement of many more people with
scholarly and social science research backgrounds in HRPC in an ongoing
way, whether in person at meetings or by providing continuing feedback on
draft documents via the listserv.  I could provide a starting list of
associations where such presentations would be welcome, and others in HRPC
I'm sure could add to it.  Once travel starts up again, perhaps funding
could be found to support travel to conferences, but meanwhile, this would
be a low-cost activity while we're doing virtual events.

*Ensuring a Human Rights Presence during IETF Meetings*

A second function of the group has been to have people on the ground during
IETF meetings bringing up specific human rights issues as raised by very
specific developments being discussed for particular protocols.  From my
own (limited) observation and informal reports from others, this is one of
the most effective things that HRPC does.  The goal here, of course, is to
expand on the number of people involved in this activity in a sustained
manner.

(3) An *HRPC (post)graduate student fellows program* could support the
participation of graduate (postgraduate) students studying the
Internet/policy nexus.  They could be recruited from the new and excellent
programs being set up of this kind, such as that at Tufts University in the
US (
https://asegrad.tufts.edu/academics/explore-graduate-programs/cybersecurity-and-public-policy).
These go under different names but typically cover much, if not all, of the
human rights terrain as defined by the HRPC, and they are now being found
all over the world.  Ideally students would be supported for travel to a
year of IETF meetings at a time, potentially renewable.  Perhaps funding
support for such a program could be found.

(4) *Onboarding materials specific to HRPC* would be useful both for
students who come to IETF as HRPC fellows and for academics invited to
speak.  When I was invited to speak, there was terrific informal support
from Niels ten Oever and Corinne Cath-Speth, both of whom made many
recommendations regarding meetings and events of particular interest
(thanks again to you both!), but if the numbers of visitors go up and to
relieve the pressure on those two individuals, it would be helpful to have
something in writing that would serve this function as well.  Those of you
with deep knowledge about what is going on could add a page of
meeting-specific recommendations before each event.  At least two or three
other IRTF groups are doing research pertinent to human rights, so those
meetings should be on this list as well.  This would be a different kind of
information from that provided for newcomers at each event, specific to
human rights concerns.

*Building the Epistemic Community*

Most, if not all, of the suggestions above would be significant
contributions to the important job of building a sociotechnical epistemic
community of those concerned about human rights in the digital environment
that involves a shared conversation between those with technical and those
with legal and policy expertise.  Bringing students to IETF, for example,
contributes to the building of a pipeline of individuals who will grow that
epistemic community throughout their careers.  Thinking specifically about
that problem as a function of the HRPC leads in another direction as well.

(5) *Tutorials* that are accessible to students and other interested people
explaining the policy dimensions of technical decisions would be valuable,
and again, I believe, has been modeled by at least one other IRTF group.

(6)  IEEE accredited computer science programs have to include courses on
"ethics."  Can HRPC members develop *curriculum materials *for such courses
in the area of human rights?  These could go beyond tutorials to include
recommended reading lists, perhaps exercises or simulations, etc.

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

<div dir=3D"ltr">Folks --<div><br></div><div>To complete what I&#39;ve star=
ted, following are some ideas about ways HRPC might enrich what it is doing=
 going forward in the various areas in which it is active.=C2=A0 Again, I m=
ay be misunderstanding the goals of the group, there are always logistical =
issues, etc., but thought to put these out there to get the conversation go=
ing.=C2=A0 There appear to be three functional areas of what the group does=
, synergetically inter-related.=C2=A0=C2=A0</div><div><br></div><div>This i=
s a very good time for HRPC to revisit its activities because the decades-l=
ong struggle to bring the technical and policy communities into a shared co=
nversation has reached a new stage and now has a much more significant inst=
itutional presence than it has historically.=C2=A0 (Hats off, yet again and=
 always, to groups such as the Center for Democracy and Technology for prov=
iding leadership in this area so early, and to the other non-profit groups =
that have now been in this terrain for a number of years, such as Article 1=
9 and the ACLU.)</div><div><br></div><div>Some of these ideas are relativel=
y low-cost or no-cost.=C2=A0 Others would require significant amounts of ti=
me investment by one or more individuals and would probably need some grant=
-writing for support.=C2=A0 They also differ in how pressing the need is.=
=C2=A0 For document development, in my view, the need is very pressing.=C2=
=A0 The need to ensure and expand the presence of knowledgeable individuals=
 during IETF meetings is enduring.=C2=A0 The development of pedagogical too=
ls may be aspirational.</div><div><br></div><div>I look forward to hearing =
people&#39;s thoughts.</div><div><br></div><div>Sandra Braman<br></div><div=
><br></div><div>-----------------------------------------------------------=
----------------------------------------------</div><div><br></div><div><u>=
Arguments and Research Regarding Human Rights and Internet Protocols</u></d=
iv><div><u><br></u></div><div>One strand of HRPC&#39;s activity involves th=
e development of informational RFCs suggesting relationships between human =
rights and Internet protocols and encouraging the building of a research fo=
undation to support ideas about these relationships.=C2=A0 These documents =
will be stronger if they engage more deeply with pertinent scholarly litera=
ture and with research communities using a variety of methods to investigat=
e such matters.</div><div><br></div><div>(1) One recommendation about how t=
o achieve this would be to set up a <i style=3D"text-decoration-line:underl=
ine">scholarly review board</i>=C2=A0that would review draft documents from=
 a scholarly perspective.=C2=A0 Participating in such a board would be very=
 attractive to academics who want to make a difference -- and who would def=
initely prefer such meaningful institutionally-required service to many of =
the other options on offer.=C2=A0 There is a model of this in at least one =
other of the IRTF groups, so this works within the IETF context.</div><div>=
<br></div><div>(2) So far HRPC has been bringing individual subject experts=
 &quot;in&quot; to IETF; that has been effective in multiple ways and I hop=
e this will continue, if not expand.=C2=A0 HRPC individuals going &quot;out=
&quot; to other communities would offer additional benefits.=C2=A0 Thus a s=
econd recommendation in this area is for authors to present <b>draft RFCs</=
b>=C2=A0to deep subject experts via <i><u>conference presentations</u></i>=
=C2=A0on those researchers&#39; own home turf for feedback.=C2=A0 This woul=
d get a lot of feedback from people who are not otherwise involved with HRP=
C and will lead authors into pertinent research findings and literatures of=
 which they may otherwise not be aware.=C2=A0=C2=A0</div><div><br></div><di=
v>It would also serve the additional function of informing people in the ma=
ny professional scholarly associations that deal with technology policy mat=
ters of the existence of HRPC=C2=A0=C2=A0-- the vast majority of researcher=
s working in this area have no idea that HRPC exists even if they know abou=
t the IETF.=C2=A0 That could lead to the involvement of many more people wi=
th scholarly and social science research backgrounds in HRPC in an ongoing =
way, whether in person at meetings or by providing continuing feedback on d=
raft documents via the listserv.=C2=A0 I could provide a starting list of a=
ssociations where such presentations would be welcome, and others in HRPC I=
&#39;m sure could add to it.=C2=A0 Once travel starts up again, perhaps fun=
ding could be found to support travel to conferences, but meanwhile, this w=
ould be a low-cost activity while we&#39;re doing virtual events.</div><div=
><br></div><div><u>Ensuring a Human Rights Presence during IETF Meetings</u=
></div><div><u><br></u></div><div>A second function of the group has been t=
o have people on the ground during IETF meetings bringing up specific human=
 rights issues as raised by very specific developments being discussed for =
particular protocols.=C2=A0 From my own (limited) observation and informal =
reports from others, this is one of the most effective things that HRPC doe=
s.=C2=A0 The goal here, of course, is to expand on the number of people inv=
olved in this activity in a sustained manner.</div><div><br></div><div>(3) =
An <i><u>HRPC (post)graduate student fellows program</u></i>=C2=A0could sup=
port the participation of graduate (postgraduate) students studying the Int=
ernet/policy nexus.=C2=A0 They could be recruited from the new and excellen=
t programs being set up of this kind, such as that at Tufts University in t=
he US (<a href=3D"https://asegrad.tufts.edu/academics/explore-graduate-prog=
rams/cybersecurity-and-public-policy" target=3D"_blank">https://asegrad.tuf=
ts.edu/academics/explore-graduate-programs/cybersecurity-and-public-policy<=
/a>).=C2=A0 These go under different names but typically cover much, if not=
 all, of the human rights terrain as defined by the HRPC, and they are now =
being found all over the world.=C2=A0 Ideally students would be supported f=
or travel to a year of IETF meetings at a time, potentially renewable.=C2=
=A0 Perhaps funding support for such a program could be found.=C2=A0</div><=
div><br></div><div>(4) <u style=3D"font-style:italic">Onboarding materials =
specific to HRPC</u>=C2=A0would be useful both for students who come to IET=
F as HRPC fellows and for academics invited to speak.=C2=A0 When I was invi=
ted to speak, there was terrific informal support from Niels ten Oever and =
Corinne Cath-Speth, both of whom made many recommendations regarding meetin=
gs and events of particular interest (thanks again to you both!), but if th=
e numbers of visitors go up and to relieve the pressure on those two indivi=
duals, it would be helpful to have something in writing that would serve th=
is function as well.=C2=A0 Those of you with deep knowledge about what is g=
oing on could add a page of meeting-specific recommendations before each ev=
ent.=C2=A0 At least two or three other IRTF groups are doing research perti=
nent to human rights, so those meetings should be on this list as well.=C2=
=A0 This would be a different kind of information from that provided for ne=
wcomers at each event, specific to human rights concerns.</div><div><br></d=
iv><div><u>Building the Epistemic Community</u></div><div><u><br></u></div>=
<div>Most, if not all, of the suggestions above would be significant contri=
butions to the important job of building a sociotechnical epistemic communi=
ty of those concerned about human rights in the digital environment that in=
volves a shared conversation between those with technical and those with le=
gal and policy expertise.=C2=A0 Bringing students to IETF, for example, con=
tributes to the building of a pipeline of individuals who will grow that ep=
istemic community throughout their careers.=C2=A0 Thinking specifically abo=
ut that problem as a function of the HRPC leads in another direction as wel=
l.</div><div><br></div><div>(5) <i><u>Tutorials</u></i>=C2=A0that are acces=
sible to students and other interested people explaining the policy dimensi=
ons of technical decisions would be valuable, and again, I believe, has bee=
n modeled by at least one other IRTF group.=C2=A0=C2=A0</div><div><br></div=
><div>(6)=C2=A0 IEEE accredited computer science programs have to include c=
ourses on &quot;ethics.&quot;=C2=A0 Can HRPC members develop=C2=A0<i><u>cur=
riculum materials</u>=C2=A0</i>for such courses in the area of human rights=
?=C2=A0 These could go beyond tutorials to include recommended reading list=
s, perhaps exercises or simulations, etc.</div><div><br></div><div><br></di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><u><br><=
/u></div><div><u><br></u></div><div><br></div><div><br></div></div>

--0000000000003d217605bb24120e--


From nobody Fri Feb 12 13:19:43 2021
Return-Path: <braman@tamu.edu>
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 A750D3A0F44 for <hrpc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 3LDRhoIqG6iZ for <hrpc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:19:33 -0800 (PST)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 5824B3A0F01 for <hrpc@irtf.org>; Fri, 12 Feb 2021 13:19:33 -0800 (PST)
Received: by mail-il1-x135.google.com with SMTP id o7so501324ils.2 for <hrpc@irtf.org>; Fri, 12 Feb 2021 13:19:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=YUUItA3wkrNaO4D+1a08b6ARju7OYqLXqLQsLTdXDSs=; b=O16wt4Q/lLD3kQLkjvMGH86PU/YAlUjvyMWJaeEdDVIT/MVYphboPW/k1fa75VjxNk xqGSkE5NDPDzK5yYttk5MaAT8XSoq5otJwQ0fLH1tP2DbsY9EACtmipTPZEWOjWvHouN B/se3cDr5h0siEfmapVNVzRC1/fo0CxSCkIkeOR/OQLm14pCZ29X8KyEYHXCOyUJtJoC MCp9S6tGrbcpMme11HsjjofbWahdFRnVo0rzoNofReUwGnAfBj53AQtxwFmTsd/4/tYl NLzcy/km7PSYeEpDDHdxKkRPErVVWVDw8TrVarbMZZe5IcoY6k/tGp7wzMchG5uCwSF4 o8eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=YUUItA3wkrNaO4D+1a08b6ARju7OYqLXqLQsLTdXDSs=; b=fP3lyrZ7LyJMU+Ri4FY4UfxTjZLy7+kT/b3NJiEFOfd0V1aCADnjK5zz5LRSKFpYjU pSDdp12rYO0thQQ0HARBSyfwOeX4CZAQgwQYIXrL7+J/hjlV/vsc2g1+l+W9bb1ps4ol +lkS8MNoPNeuGjic6d1JAQwwlhDa1CpWKHINJuu/UhKQVbMshzmj5PBFfltTKspb+USi PKjZ+Y7QPcq0zAyD9GeBa1qZDqdTy7MgyI4K5RCjDwsDe/g/jTzp5LDgtmoS3HCepccd chlhmYIWcbNiNtMRlv/oYfxRemS2jjvhAYT6ejTmTaneV6FprvyWwGrjzryRzCEtoIsf 9eWw==
X-Gm-Message-State: AOAM532psud8aQ+v2/2ba+ZLwdcEaqJSI6Ou5+smqA1glLiVfmHtwhVY 35pcyZb565xj4Kq9wlFc1jqLx/FSMqe9ZW7i4i703uxgb7V+9dHp
X-Google-Smtp-Source: ABdhPJwOY69bzNKl+RoDHTOVcxSmy82R982+9H8MqlFnljKaSEXiYq5BXKMs/Wu41DqnvY95bx6tH1YGyDSLZ1q3nn4=
X-Received: by 2002:a05:6e02:1be1:: with SMTP id y1mr3873854ilv.101.1613164770769;  Fri, 12 Feb 2021 13:19:30 -0800 (PST)
MIME-Version: 1.0
From: Sandra Braman <braman@tamu.edu>
Date: Fri, 12 Feb 2021 15:21:31 -0600
Message-ID: <CAB2unbO0XDzxcF8f9H3uVHQk_XaztiJ-0OKnLF1B4ct6PPCW3w@mail.gmail.com>
To: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="00000000000020542d05bb2a31e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/twLTNOBP2Q5YpuF6j0fy8RKHV2U>
Subject: [hrpc] and a correction
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: Fri, 12 Feb 2021 21:19:42 -0000

--00000000000020542d05bb2a31e4
Content-Type: text/plain; charset="UTF-8"

>From the comments on draft guidelines:

The text that reads:

"Graph 2 on page 4 identifies key sources of human rights.  The manner of
presentation conflates documents from sources that are importantly
different regarding their source and, thus, relative weight.  A document
created by the Internet Governance Forum -- a talk shop only that has no
status within the international legal system on its own -- with United
Nations treaties."  and so forth

Should read:

"Graph 2 on page 4 identifies key sources of human rights.  The manner of
presentation, however, mixes actual international law with materials that
have no legal weight in a way that can be misleading.  The document from
the Internet Governance Forum -- a talk shop created after WSIS to provide
a venue in which people could discuss their concerns but which has no
necessary influence on either Internet governance or what states do --
should not be treated as if it were a source of international law.  Rather,
it should be included in discussion of the treatment of Internet-related
human rights as discussed in the scholarly literature and in gray matter
(reports from non-profit advocacy groups, think tanks, etc.)."  again
etcetera

Sandra

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

<div dir=3D"ltr">From the comments on draft guidelines:<div><br></div><div>=
The text that reads:=C2=A0=C2=A0</div><div><br></div><div>&quot;Graph 2 on =
page 4 identifies key sources of human rights.=C2=A0 The manner of presenta=
tion conflates documents from sources that are importantly different regard=
ing their source and, thus, relative weight.=C2=A0 A document created by th=
e Internet Governance Forum -- a talk shop only that has no status within t=
he international legal system on its own -- with United Nations treaties.&q=
uot;=C2=A0 and so forth</div><div><br></div><div>Should read:</div><div><br=
></div><div>&quot;Graph 2 on page 4 identifies key sources of human rights.=
=C2=A0 The manner of presentation, however, mixes actual international law =
with materials that have no legal weight in a way that can be misleading.=
=C2=A0 The document from the Internet Governance Forum -- a talk shop creat=
ed after WSIS to provide a venue in which people could discuss their concer=
ns but which has no necessary influence on either Internet governance or wh=
at states do -- should not be treated as if it were a source of internation=
al law.=C2=A0 Rather, it should be included in discussion of the treatment =
of Internet-related human rights as discussed in the scholarly literature a=
nd in gray matter (reports from non-profit advocacy groups, think tanks, et=
c.).&quot;=C2=A0 again etcetera</div><div><br></div><div>Sandra</div><div><=
br></div><div><br></div></div>

--00000000000020542d05bb2a31e4--


From nobody Fri Feb 12 16:39:55 2021
Return-Path: <agenda@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 4FFD33A1186; Fri, 12 Feb 2021 16:33:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <hrpc-chairs@ietf.org>, <mknodel@cdt.org>
Cc: hrpc@irtf.org, irtf-chair@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161317641831.31337.4309993755292090373@ietfa.amsl.com>
Date: Fri, 12 Feb 2021 16:33:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/g8NBjuMcsSbrMaAvmt2CN84l1b4>
Subject: [hrpc] hrpc - Requested session has been scheduled for IETF 110
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: Sat, 13 Feb 2021 00:33:49 -0000

Dear Mallory Knodel,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    hrpc Session 1 (2:00 requested)
    Thursday, 11 March 2021, Session III 1700-1900
    Room Name: Room 3 size: 503
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics

Request Information:


---------------------------------------------------------
Working Group Name: Human Rights Protocol Considerations
Area Name: IRTF
Session Requester: Mallory Knodel


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 regext
 Key Participant Conflict: dnsop





People who must be present:
  Avri Doria
  Mallory Knodel

Resources Requested:

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



From nobody Sat Feb 13 05:10:20 2021
Return-Path: <lear@cisco.com>
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 A2D703A1190 for <hrpc@ietfa.amsl.com>; Sat, 13 Feb 2021 05:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 z87GIsS8ZMTt for <hrpc@ietfa.amsl.com>; Sat, 13 Feb 2021 05:10:18 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF4AE3A118F for <hrpc@irtf.org>; Sat, 13 Feb 2021 05:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2944; q=dns/txt; s=iport; t=1613221818; x=1614431418; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=eh9/k54Ba1ebOgEWc8v9XCWSmXgueLL+OYNF+Lk+RGU=; b=l/9JyCO3QlECjwVPsNCOUwEk1HdZe51OOshLzrZ9KxD8J+LD8JASmx+Z h+yrxfvrI/XzO5EiBoPvHL175OKIVIYriFxjVMU8hul9vGL0ovWMQOMOq qr++70nckAJr5CrjU29hv1JMAlueHDe8Clavmtt1HrGBmNL2qHHkYkahQ 4=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0AVAQD0zidglxbLJq1iDg4BAQEBAQEHAQESAQEEBAEBQ?= =?us-ascii?q?IFPgXaBK1YBJxIxjUWIKSUDgQWbQgQHAQEBCgMBAR0LDAQBAYRNAoIIJjgTA?= =?us-ascii?q?gMBAQEDAgMBAQEBBQEBAQIBBgQUAQEBAQEBAQGGNg2GRAEBAQMBAQFsCwULC?= =?us-ascii?q?xguJzAGE4JwAYJmIA+vQHSBNIVYhGkKBoE4gVOLb0KCAoERJwwQgiI1PoJGF?= =?us-ascii?q?wGFKoIrBIFVgVUBA1MTAQw7fh6dTpxIgwSDKoE6lyYDH4MxkA4sj0KyQoNzA?= =?us-ascii?q?gQGBQIWgWwhgVkzGggbFTsqAYI+PhIZDY45iGuFBEJAAy83AgYKAQEDCYwTA?= =?us-ascii?q?QE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,176,1610409600";  d="asc'?scan'208";a="33434958"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Feb 2021 13:10:13 +0000
Received: from [10.61.170.34] ([10.61.170.34]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 11DDACZ3005931 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 13 Feb 2021 13:10:13 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <87E8A5BE-FEDA-4643-A02D-37139D08570D@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F666279F-21EC-46E7-8C37-3CD7A59E78AD"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Sat, 13 Feb 2021 14:10:12 +0100
In-Reply-To: <CAB2unbO0XDzxcF8f9H3uVHQk_XaztiJ-0OKnLF1B4ct6PPCW3w@mail.gmail.com>
Cc: hrpc@irtf.org
To: Sandra Braman <braman@tamu.edu>
References: <CAB2unbO0XDzxcF8f9H3uVHQk_XaztiJ-0OKnLF1B4ct6PPCW3w@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.170.34, [10.61.170.34]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/aiTHWVdfmYGPjUV0E23RSWl0BzA>
Subject: Re: [hrpc] and a correction
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: Sat, 13 Feb 2021 13:10:20 -0000

--Apple-Mail=_F666279F-21EC-46E7-8C37-3CD7A59E78AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Sandra,

Thanks for these comments.  How I read them in their aggregate is that =
we should have an organizational issue to address.  Can a single =
document successfully cover the topic?  Should there be a bit of an =
outline or overview of the space, followed by a mapping of aspects that =
can be tackled?  That would then allow for some of this to be taken in =
bite sized pieces (or as we engineers might say, byte sized pieces).

Eliot

> On 12 Feb 2021, at 22:21, Sandra Braman <braman@tamu.edu> wrote:
>=20
> =46rom the comments on draft guidelines:
>=20
> The text that reads:
>=20
> "Graph 2 on page 4 identifies key sources of human rights.  The manner =
of presentation conflates documents from sources that are importantly =
different regarding their source and, thus, relative weight.  A document =
created by the Internet Governance Forum -- a talk shop only that has no =
status within the international legal system on its own -- with United =
Nations treaties."  and so forth
>=20
> Should read:
>=20
> "Graph 2 on page 4 identifies key sources of human rights.  The manner =
of presentation, however, mixes actual international law with materials =
that have no legal weight in a way that can be misleading.  The document =
from the Internet Governance Forum -- a talk shop created after WSIS to =
provide a venue in which people could discuss their concerns but which =
has no necessary influence on either Internet governance or what states =
do -- should not be treated as if it were a source of international law. =
 Rather, it should be included in discussion of the treatment of =
Internet-related human rights as discussed in the scholarly literature =
and in gray matter (reports from non-profit advocacy groups, think =
tanks, etc.)."  again etcetera
>=20
> Sandra
>=20
>=20
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc


--Apple-Mail=_F666279F-21EC-46E7-8C37-3CD7A59E78AD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmAnz7QACgkQh7ZrRtnS
ejMoiwf8C3pxvcZtcQZrJkw0aHZs3w4ojC17KkpKzijRgvn9ks3kKcTLlfPIK4Rb
xKBr7TPd1H5Y2OYNiZiqQi/wBlQO/m6/Iz3aB0ht9yuHKuttT831k0t5qr1NasGh
XhKXqAHtCLegKWD6Oo0Hfhm/9XANbcmzpywOurvUt0x6EwMKqsF10CnUNcyYWeo0
PC7puDdZYhPFV3N/n6oEn99cN0bv8Dq49ZDp7THy8EEp1/k0eCScvT+uvUDV3qql
z6uIyCeAQfKTioOHlgavEUGi/3p2JHxYLva+xDRCcj0vG0VATMsSAtxf09e3MDSf
i6ROJk1Z75DSMFEvhdClNdNxL9a2Rg==
=X9ah
-----END PGP SIGNATURE-----

--Apple-Mail=_F666279F-21EC-46E7-8C37-3CD7A59E78AD--


From nobody Sat Feb 13 08:04:05 2021
Return-Path: <braman@tamu.edu>
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 06BEA3A0D8A for <hrpc@ietfa.amsl.com>; Sat, 13 Feb 2021 08:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 IQURvimrq4sx for <hrpc@ietfa.amsl.com>; Sat, 13 Feb 2021 08:03:59 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 710003A0D86 for <hrpc@irtf.org>; Sat, 13 Feb 2021 08:03:59 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id u20so2399769iot.9 for <hrpc@irtf.org>; Sat, 13 Feb 2021 08:03:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HwiMeM0SWCJeXAfrPMpWOKo5+9Rk8P4uoq04/4TmQwg=; b=ml+GCvecFB9+82qh329hHFhVcRJgYmdUOhvWMaqc9JOs0ZCG4gHsAZ++kSEE0Fly91 4i4WHH8iPgP/pBK+GBx3xLeHnhOZgmGPuDaBXTRbXgW+SQcQJu4L/MD3Dkqc34yjg0Mn wdV6afhuUtQm/4n0PsfqfwJQwQ67knDOHhIm/ZV8o06AovReJoaETXxW/nNJXZe6VDzj WO+/KFr6/ye3Pf2q6cIQYZgCFdm3XzFO3Obx8MbkmiPyfJ92uTYhp73nUHDvWHLIJqiy e1KHZo+f4bQ4M6O6g7cckyIfzhJNC10HuDkZCe2EasdIc0q+AXyVgjVy6ODIpqaA2/JW R0bg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HwiMeM0SWCJeXAfrPMpWOKo5+9Rk8P4uoq04/4TmQwg=; b=UHHpaNjstV5Bzvbw1TPu1jASbStCdrpyEnX3ksBRprPUz58Gqc+B4xuJIFrF1Ju/p+ 7BY5PiK/VG9qAbJIxuARRFyrwNkV0JB7+6uzrPXeb4yxSZjBknJNO7iXwpTitJoNv7Cw 3MAINfXHRn2YoHWxvJFz9hx6QEeEbE9SRlNF1PZfY0VtOZAtqYwtv+lSeEOnu4Cz0QCb zvxwJClNJ4GmSVy1V//nDMZW9P3o31glkD1jBeqlypXn8j2z+BhqQgGbxoz4tI0WRbaJ lBjo487+V+C/ed3Ir5c5pzULN9nAV3y+T1FK40AAmY7zwGJ3ss2f4YPU2IPxYTGnMGn1 l+Jg==
X-Gm-Message-State: AOAM533ejzlhE4eJ5RAvGjzpxYHq9rm12V1W7yqhQD1XrhnNVdVkPShU Vd/uwnRTHGXpO7q+gQMHFXryXwcnbyletEfRVLAQsQ==
X-Google-Smtp-Source: ABdhPJwnEY8OF+dzlnP88bV1RZXHHFuGeQi+kWZeNHuAxd1/KeIIsWIxw9mMSAP+dVyNwOL4ZUcMXzU4UV2IlCc2eV0=
X-Received: by 2002:a05:6638:102:: with SMTP id x2mr7518719jao.82.1613232237889;  Sat, 13 Feb 2021 08:03:57 -0800 (PST)
MIME-Version: 1.0
References: <CAB2unbO0XDzxcF8f9H3uVHQk_XaztiJ-0OKnLF1B4ct6PPCW3w@mail.gmail.com> <87E8A5BE-FEDA-4643-A02D-37139D08570D@cisco.com>
In-Reply-To: <87E8A5BE-FEDA-4643-A02D-37139D08570D@cisco.com>
From: Sandra Braman <braman@tamu.edu>
Date: Sat, 13 Feb 2021 10:06:00 -0600
Message-ID: <CAB2unbNWXxTKKVct6DuCcFOs0tXET0QcevLuWNPw1_--ohpSUw@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="0000000000007ae11505bb39e61a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/lse26yplKwnzSxG90mF4ELHgnZc>
Subject: Re: [hrpc] and a correction
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: Sat, 13 Feb 2021 16:04:03 -0000

--0000000000007ae11505bb39e61a
Content-Type: text/plain; charset="UTF-8"

That's a good point, Eliot.  My sense has been that the authors (as of RFC
8280) thought a single document could successfully map the space and then
subsequent documents (e.g., draft association) would take particular issues
on to examine in depth. If we are to look at the technical analogue of this
sociotechnical problem, though, no single RFC ever provided an entire map
of the network as a design problem.

As we saw, even draft association dealt with at least three different
topics on the technical side in addition to the significant proportion of
the text spent on application level and uses issues that in my view are
better addressed elsewhere -- communication, assembly, and association --
with the latter two not yet having received operational definition for
Internet design purposes.  My recommendation there had been to at minimum
hive off the discussion of communication issues for separate treatment,
although given the historical relationships assembly and association in
legal thought and practice, treating those two together in one RFC makes
sense.



On Sat, Feb 13, 2021 at 7:10 AM Eliot Lear <lear@cisco.com> wrote:

> Sandra,
>
> Thanks for these comments.  How I read them in their aggregate is that we
> should have an organizational issue to address.  Can a single document
> successfully cover the topic?  Should there be a bit of an outline or
> overview of the space, followed by a mapping of aspects that can be
> tackled?  That would then allow for some of this to be taken in bite sized
> pieces (or as we engineers might say, byte sized pieces).
>
> Eliot
>
> > On 12 Feb 2021, at 22:21, Sandra Braman <braman@tamu.edu> wrote:
> >
> > From the comments on draft guidelines:
> >
> > The text that reads:
> >
> > "Graph 2 on page 4 identifies key sources of human rights.  The manner
> of presentation conflates documents from sources that are importantly
> different regarding their source and, thus, relative weight.  A document
> created by the Internet Governance Forum -- a talk shop only that has no
> status within the international legal system on its own -- with United
> Nations treaties."  and so forth
> >
> > Should read:
> >
> > "Graph 2 on page 4 identifies key sources of human rights.  The manner
> of presentation, however, mixes actual international law with materials
> that have no legal weight in a way that can be misleading.  The document
> from the Internet Governance Forum -- a talk shop created after WSIS to
> provide a venue in which people could discuss their concerns but which has
> no necessary influence on either Internet governance or what states do --
> should not be treated as if it were a source of international law.  Rather,
> it should be included in discussion of the treatment of Internet-related
> human rights as discussed in the scholarly literature and in gray matter
> (reports from non-profit advocacy groups, think tanks, etc.)."  again
> etcetera
> >
> > Sandra
> >
> >
> > _______________________________________________
> > hrpc mailing list
> > hrpc@irtf.org
> > https://www.irtf.org/mailman/listinfo/hrpc
>
>

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

<div dir=3D"ltr">That&#39;s a good point, Eliot.=C2=A0 My sense has been th=
at the authors (as of RFC 8280) thought a single document could successfull=
y map the space and then subsequent documents (e.g., draft association) wou=
ld take particular issues on to examine in depth. If we are to look at the =
technical analogue of this sociotechnical problem, though, no single RFC ev=
er provided an entire map of the network as a design problem.=C2=A0=C2=A0<d=
iv><br></div><div>As we saw, even draft association dealt with at least thr=
ee different topics on the technical side in addition to the significant pr=
oportion of the text spent on application level and uses issues that in my =
view are better addressed elsewhere -- communication, assembly, and associa=
tion -- with the latter two not yet having received operational definition =
for Internet design purposes.=C2=A0 My recommendation there had been to at =
minimum hive off the discussion of communication issues for separate treatm=
ent, although given the historical relationships assembly and association i=
n legal thought and practice, treating those two together in one RFC makes =
sense.</div><div><br></div><div><br></div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Feb 13, 2021 at 7:10 AM E=
liot Lear &lt;<a href=3D"mailto:lear@cisco.com">lear@cisco.com</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Sandra,<br>
<br>
Thanks for these comments.=C2=A0 How I read them in their aggregate is that=
 we should have an organizational issue to address.=C2=A0 Can a single docu=
ment successfully cover the topic?=C2=A0 Should there be a bit of an outlin=
e or overview of the space, followed by a mapping of aspects that can be ta=
ckled?=C2=A0 That would then allow for some of this to be taken in bite siz=
ed pieces (or as we engineers might say, byte sized pieces).<br>
<br>
Eliot<br>
<br>
&gt; On 12 Feb 2021, at 22:21, Sandra Braman &lt;<a href=3D"mailto:braman@t=
amu.edu" target=3D"_blank">braman@tamu.edu</a>&gt; wrote:<br>
&gt; <br>
&gt; From the comments on draft guidelines:<br>
&gt; <br>
&gt; The text that reads:<br>
&gt; <br>
&gt; &quot;Graph 2 on page 4 identifies key sources of human rights.=C2=A0 =
The manner of presentation conflates documents from sources that are import=
antly different regarding their source and, thus, relative weight.=C2=A0 A =
document created by the Internet Governance Forum -- a talk shop only that =
has no status within the international legal system on its own -- with Unit=
ed Nations treaties.&quot;=C2=A0 and so forth<br>
&gt; <br>
&gt; Should read:<br>
&gt; <br>
&gt; &quot;Graph 2 on page 4 identifies key sources of human rights.=C2=A0 =
The manner of presentation, however, mixes actual international law with ma=
terials that have no legal weight in a way that can be misleading.=C2=A0 Th=
e document from the Internet Governance Forum -- a talk shop created after =
WSIS to provide a venue in which people could discuss their concerns but wh=
ich has no necessary influence on either Internet governance or what states=
 do -- should not be treated as if it were a source of international law.=
=C2=A0 Rather, it should be included in discussion of the treatment of Inte=
rnet-related human rights as discussed in the scholarly literature and in g=
ray matter (reports from non-profit advocacy groups, think tanks, etc.).&qu=
ot;=C2=A0 again etcetera<br>
&gt; <br>
&gt; Sandra<br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; hrpc mailing list<br>
&gt; <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a><b=
r>
&gt; <a href=3D"https://www.irtf.org/mailman/listinfo/hrpc" rel=3D"noreferr=
er" target=3D"_blank">https://www.irtf.org/mailman/listinfo/hrpc</a><br>
<br>
</blockquote></div>

--0000000000007ae11505bb39e61a--


From nobody Sun Feb 14 17:49:30 2021
Return-Path: <paul@nohats.ca>
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 B20353A0FF4 for <hrpc@ietfa.amsl.com>; Sun, 14 Feb 2021 17:49:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=nohats.ca
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 W20wGtIdfncv for <hrpc@ietfa.amsl.com>; Sun, 14 Feb 2021 17:49:26 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 9D7F63A0FF2 for <hrpc@irtf.org>; Sun, 14 Feb 2021 17:49:25 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4Df6Tv1P6DzCw0; Mon, 15 Feb 2021 02:49:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1613353763; bh=Vll18P16dplbzlQdEJDxRkt+oSa4PRIKrWvDm1u/4qQ=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=k8KP7xFk8fCsO/OBpjnwU9/nsnfyzG/Xi7jisykVh/ScgcRdEbQ+/MWxg4lersvm3 sqk0BlZTz2Jzl+aB0x1yDU70OhmM2Z4ReYtnZX7nlKpxqiS7bhmLa9z+ktQuzsT/Qi 8JNMG4wjiONfFcSlhA+XGRznsc1QxKH0JU+8+dCY=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Bq_9qSber-bX; Mon, 15 Feb 2021 02:49:21 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 15 Feb 2021 02:49:21 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 30C1A6029BA0; Sun, 14 Feb 2021 20:49:20 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 2839566B1E; Sun, 14 Feb 2021 20:49:20 -0500 (EST)
Date: Sun, 14 Feb 2021 20:49:20 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Eric Rescorla <ekr@rtfm.com>
cc: Brian Haberman <brian@innovationslab.net>,  Tim Wicinski <tjw.ietf@gmail.com>, hrpc@irtf.org
In-Reply-To: <CABcZeBO54=rZXxZAAY1=M1su=utQ3_eRr_Ouna3QSUoyO-kT8Q@mail.gmail.com>
Message-ID: <30155faf-5cd4-f27b-2edf-d78c6099aa5@nohats.ca>
References: <428995ea-ead8-fd03-7d02-4640de50345f@innovationslab.net> <b7004f01-aca6-fcbe-04b1-d0ab9a76b6ed@innovationslab.net> <CABcZeBO54=rZXxZAAY1=M1su=utQ3_eRr_Ouna3QSUoyO-kT8Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/64c_gBG_3mk5s2IDZJI9CiHPVgk>
Subject: Re: [hrpc] [dns-privacy] WG Call for Adoption: draft-pp-recursive-authoritative-opportunistic
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, 15 Feb 2021 01:49:29 -0000

On Sat, 13 Feb 2021, Eric Rescorla wrote:

> I must say, I find this rather surprising.

> This thread had responses from 6 people, of whom three (Manu Bretelle, Paul Hoffman, and Stephen Farrell) expressed support for adoption, two
> (Paul Wouters and myself) expressed opposition, and one (Jim Reid) expressed an unclear but skeptical position. On what basis are you calling
> that consensus?

I'm also a bit surprised here. If anything, I would say there is no
clear interest to move forward with adoption yet, and the authors
should try to gain more support by finding more proponents or
by working with those who were against the proposal towards a
different method to solve the problems at hand.

The issue I have with the document overal, is that it presents
opportunistic as a step towards an authenticated solution, while
we have seen from disucssions in the past (eg overloading the DS
record for publishing public keys without leaking privacy) that
there is no way forward from opportunistic to authenticated. The
two problems are not two steps in the same direction.

I've added HRPC to the CC: so that they may also chime in with
their opinions about the possible negative affects of this draft.

Paul

> 
> On Sat, Feb 13, 2021 at 6:27 AM Brian Haberman <brian@innovationslab.net> wrote:
>       All,
>            The WGLC for adoption for this draft has completed. The chairs have
>       determined that there is consensus to adopt this document as a DPRIVE
>       working group document.
>
>            The authors should publish the next version of the document as
>       draft-ietf-dprive-recursive-authoritative-opportunistic-00. The intended
>       status of the document will be a part of the WG discussion on this draft.
>
>       Regards,
>       Brian & Tim
>
>       On 1/29/21 8:24 AM, Brian Haberman wrote:
>       > All,
>       >      This starts a DPRIVE WG call for adoption for
>       > draft-pp-recursive-authoritative-opportunistic
>       > (https://datatracker.ietf.org/doc/draft-pp-recursive-authoritative-opportunistic/).
>       > The focus of the call is the protocol defined in the draft. Please reply
>       > to the mailing list with your views on the WG adopting the document and
>       > your supporting arguments.
>       >
>       >      This call will end on February 12, 2021 at 11:59pm UTC.
>       >
>       > Regards,
>       > Brian & Tim
>       >
>
>       _______________________________________________
>       dns-privacy mailing list
>       dns-privacy@ietf.org
>       https://www.ietf.org/mailman/listinfo/dns-privacy
> 
> 
>


From nobody Sun Feb 14 19:07:42 2021
Return-Path: <marknoumea@yahoo.com>
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 8A6453A10E0 for <hrpc@ietfa.amsl.com>; Sun, 14 Feb 2021 19:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.189
X-Spam-Level: 
X-Spam-Status: No, score=-0.189 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 zEAeZQVHA22s for <hrpc@ietfa.amsl.com>; Sun, 14 Feb 2021 19:07:35 -0800 (PST)
Received: from sonic301-1.consmr.mail.bf2.yahoo.com (sonic301-1.consmr.mail.bf2.yahoo.com [74.6.129.40]) (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 71CE33A10DF for <hrpc@irtf.org>; Sun, 14 Feb 2021 19:07:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1613358454; bh=jejnlz/D99TF9pm6MVlpBLUQUKoPGwNAfo1T/3XH1cA=; h=Subject:To:References:From:Date:In-Reply-To:From:Subject:Reply-To; b=GDw2pjiyZIjKomH0OOU0vM52Q86SArED2fusejpXE/hkv/TxsNaRYWcJ4Uxv2HGhAAXLbOXJvo1ZmnVNUMcyb+gFhjlEL8BriIwoM45Dw62kdA+ejJkAYnIMPtymkjqVCWFDRVdzT/XIEX0Uon6AeYhsGr3HXkJqZoX7weWN4Agoks5BfDpc1J9y8JoMHsBNuHspAu7+Sw5vmEsZuXfvJzG0Dl6BcWuPriVQGyCbNSopWOs4XyTUH7a+YvnxU9OmxdPYE0GJP9rYZsuVyBHOJo4uIjQ8SaAQePlr4IflUCJPyiFhrzpser2/xr9taEj8A7NjByVVTPpNL1mhz7loZw==
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;  t=1613358454; bh=GUKGdInjoxcIfInh7l+6Uz+ARd94s5vVyJpmv2boKw4=;  h=X-Sonic-MF:Subject:To:From:Date:From:Subject; b=Vx4lw+CmVeC/Mej9TjoCBP6LQKswNbF/OTLFD9XQ10fQX6UpMscVftgjzRQiJniVYZGuK6AOM/nPJ2EmbDLXf/jVj3xgnJx3cw4k0SYkMBMItg4yBd+L4BKO6bJFjQ6pIQsoy4wYvVH2XWqu7y3winKtYqEae/otvB62MYc28ZTc5a/F1/53+iuwZe4j1TOtAaHQsTCCsr5EPgqTeZRfKI74bdfnNjH0PcTdtKL0hCePNLNd08bU/m9dwW3vyMF/tcAPL0hlH1Xl8DaFLmSRF3Ec1A7x9xlBCzIQ5rugT5zVV8emAPYGX8oMsPGG44n63NU5SF1jC/YG69upcXCZOQ==
X-YMail-OSG: R6Sc920VM1lfe_sOSGovvNC2O4bPFUedzwW1r923z1ZXCpSm9h7sRa1..6ddq9U me1iLEsW0S.3VyzU8zJdND9vLd9v0rHCUwzqd.MathRIPMdCSg0CRxT7lzB.AAurA7xrkEMbVY3o w5zoaTuJAeqMCJYPYa1GsYNu8mZBPhNo_Ul3uF27lSmOZMt1r9ZsqoXkJtsQh94AbS3IXPZHT81x WjGaHfGwp72n.Cpsuccxn0mkHRuY7riyUMAoTxKF6XK_AoLHCANQszNvvtdGkqMrBrozr4fquPPy 35rWa6OX2vShPsR6EJELL6u6a2QlJo5uNe7744pFEFhE9UfotjUHZCnWEpABCfR88AykzpegL1Rj 7AGqdujCx.OcLRjEP_6vj8eRmmBCCmupB9yLNG8wIBVjSTOBLdotXWuISN_1C7i26BZccDYp5evw vEyEQLgiYc7GxIYzNEyj8rOz89uWnHRMNR2NOezBpp1_m49nvae0eI1GIq0OInvVutyrLcbyCaqk ozJuyp1Ea7xOl0Ks.SKXNGKDFRtoqjlo2mRLk5XEAIwC9o3VUlYXiV0KXeP7TwoV3I_uFwjOc_6b 0AfMh_Q.ouXadMe7V9..Yw.IEfwFzYEgu1phvgFAFBPjgwgw3SOcT3657DS6CFqYRJIXvoJUxc3H 9pBXO_rqgTaMclS.8X1FG9Ub9RfyGfcaT8Vk2cfmsDqB3VRzzdTbVJY3jGNYVACyCyPAOZ_L.1f6 xIVE5km2CTT4YMvtZc7XBnbzzfn1Q0kRrcXI6dNSoj3vc2doZ.mbh5E66ewJee22k6MFWA84BsS2 Sm9sXHHG4kSW05KdIZCck5hp6_SLuzT9Azk8c0fD6UeFuMsowlW9xUXVvY8zI_pUb9xpTWE781sa bQw9gcv9f5PgAI5Kh4GNzDYR5Ul2anDFKN0zSBR3U9JeTqI7uoXcIWwxFSL.Qka9wdgxxuAi4v43 cRQTOW68m.AtztSYwtBl2NBpXCqpUCH5VorSsbxdb6Ymth4yl3bVwO749JfDeizfWGtlLBR4PpRC yGEKopdTCm5cIeNaxtUWK0Qiwn4Xrub1AqqmE__zmFLKaDYcpWZs9OodU4zImkLdcCBHQkrcAbtU .j8enmB7ddrtW7smvx66qiK0oh1pjY_bb1hHxEjVoOQjdMWr2Z7pUmSh4fmyEGAiKpwjWDH4iXQB JzhI0QrqxZ0qM_dy_Q2dTDnjtWCcNxTalbjltXVui_NNeJSNteiRPFL0Dof.xVJDJ6Hng_E_HYXV DPdX1Ct11SSHGvU6cYKtdi2y.5xUEHB4cYy7.w73sceYKdqLx6G2Tsunnyth4oRQ6MK7ZgNvR4bk TatugHV.N2uOgeBJm.G1SI1cJmSCCe4ujpX.WkRxHnkWv0YzdUbP7wbVUU0ApUKWacY1ohDrsg7p yFQrctebhadCN3Df_TW068NJQ2Qn_2T6K20ndoNWRkOIRTX59EWCJf8ROy781R.yMUIhJhE4SBOb lXubbbWM_uMZDXHW7Gh6wGDc17pG4IEJExEcqxjexDLRmCQ.LzEih1rgDMs2PxphJVh5ZoH5Z7Vr LupkPLapLiotTtVb_RCr0.A6ifAYqa_w2m7Jw.LzcHjyUenQnBmwJZXcdx1waZMwX.kiSHSdT8Yk r5Cfbf68c4Fg4CvqudtR9U6zvD7GKPKWegF3c4Kuj9TjPGak7siCZv80M5Uit_qg_hYwifS.rF7d QSdyPBhNetKrF68hNyWKpRcU7bvTtMUNMoj_Qd_cYcDR2IobQJh8gJhLHAzrNEY.fqRoDifZwwdY MobZs9i5otNuxX.4ad3XzCUaHWpp2R1LVKH3VCmLK_ZvFH0VOBJjUHuSnT7gAxH2X1DE8ULu6RoU AkyJ.eiqSU9y0OBwI6aZHfNA6NkZfslh2csGeEnuH9mqbvASsau1BVFHIt4R1znkLOpMTrak5i6s sx6dZG9CrINJWUajjijUGSvI17ABI5OjZ0GccIkoSlIBQIj.TQIbj8LqBg1EKxJy3nXyLYDRbcJE JbwW_fO.fTGvsIzdmbBARSqP47KEhUk6Wql.RacmSSwb5bvNETuZkBnbxDjFXezSsTVjV7exxeq5 M7d5ziryxetEJaHVjcja6GhG37lxIePpw7E8IaSSBS__.rl5ZENutsgVF1q83u4jqhNrTgThHLWS SF03LB7_OBW3rsRzXjhH9kU9XbXzNCAp9ky6fC05cIFL.iG.SScsDMCbjpLDX3yljWlFSIDgeJYF qsLFTgKeiDBoQk1hLeKEQUh2t0H5hwVIxZDlu.CzwVtMWiv6I17FjFCAlH3Cma103LjPM5.hyEh9 eW3PQ6tw.bIfV2WfurdnvZHgujf9qaAGDbZ_V4PVE.bPB7nnTlMA4.Q3ShAsBZURZ.NvZF.jBDRM iuw--
X-Sonic-MF: <marknoumea@yahoo.com>
Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.bf2.yahoo.com with HTTP; Mon, 15 Feb 2021 03:07:34 +0000
Received: by smtp409.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 04a36edad961a8a0e95023b19de48efe;  Mon, 15 Feb 2021 03:07:30 +0000 (UTC)
To: hrpc@irtf.org
References: <CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com>
From: Mark Perkins <marknoumea@yahoo.com>
Message-ID: <483c0aae-5346-4934-cd31-b30d3de02d66@yahoo.com>
Date: Mon, 15 Feb 2021 14:07:22 +1100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------E8287561E66483D80DBAF8CA"
Content-Language: fr
X-Antivirus: Avast (VPS 210214-4, 15/02/2021), Outbound message
X-Antivirus-Status: Clean
X-Mailer: WebService/1.1.17712 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo Apache-HttpAsyncClient/4.1.4 (Java/11.0.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/23iLfKc0IYF8WBdkhJZgHam6-Es>
Subject: Re: [hrpc] comments on draft 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, 15 Feb 2021 03:07:41 -0000

This is a multi-part message in MIME format.
--------------E8287561E66483D80DBAF8CA
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Thanks for the 'heavy lifting' done by Sandra

A few comments/issues:

The point on sources is well put, but the example 'right to access 
government information' is misused; the problem is more that the 
document has not taken into account the United Nations Human Rights 
Committee General Comments which indicate the official interpretation of 
the relevant articles, which indicates the need for 'separate paragraphs 
discuss actual legal foundations for human rights and other sources of 
proposals for things that should be considered human rights in the 
Internet environment' :

The United Nations Human Rights Committee confirmed in July 2011 that 
the right to freedom of expression protected by Article 19 of the 
International Covenant on Civil and Political Rights includes the right 
of access to information.The Committee said: “Article 19, paragraph 2 
embraces a right of access to information held by public bodies. Such 
information includes records held by a public body, regardless of the 
form in which the information is stored, its source and the date of 
production.”

Human Rights Committee, 102 nd session, Geneva, 11-29 July 2011
General comment No. 34 -vvArticle 19: Freedoms of opinion and expression

"Perhaps the most interesting thread running through this document is 
the implicit suggestion that impediments to technological innovation can 
themselves be understood as violations of human rights.  (Fully 
developing that argument would make a great scholarly journal article!)"

I agree - though perhaps Article 15 of International Covenant on 
Economic, Social and Cultural Rights would cover the question?

The distinction between short & long term effects needs to be drawn with 
care & the linkage between them made explicit:

While censorship can be seen as an 'immediate/short' term effect, such 
censorship can lead to long term effects, such as inability to hold 
government to account, inability to avoid hunger/famine, etc.

The digital divide (or knowledge gap) can be seen as a long term effect 
( affordances for effective political action) but for the individual it 
can have the same impact as censorship - inability to access 
information, ie. a short term effect.

'A second issue raised by the methods introduced here is that they run 
the danger of being limited to "looking under the streetlight" (the 
familiar story about where a drunk is looking for keys, irrespective of 
where they may be), although in terms of provenance that problem may be 
more reflective of the fact that the full scholarly literature and what 
can be learned from researchers outside of the HRPC have not yet been 
brought to bear.'

MP>>I would add the 'crooked neck' analogy (the story where everyone at 
a bus stop ends up looking in same direction, until someone asks the 
first in the queue what he is looking, & he replies - nothing, I have a 
crook in my neck). So 'full' scholarly literature should also include 
diversity...

'but for research on the effects of those protocols HRPC should be 
turning to social scientists who are actually studying the effects and 
who could be encouraged to go further in this area, sometimes -- so 
valuably -- in collaboration with technical experts who have given 
themselves to this specific task.  In this regard, the work of Ron 
Deibert's group at the University of Toronto (Citizen Lab) should be 
highlighted as a model (https://citizenlab.ca/ 
<https://citizenlab.ca/>).  Work in fields such as anthropology, 
sociology, political science, information science, communication, STS 
(studies of technology and society), and economics will all be useful.'

MP>> Oxford Internet Institute also, perhaps HRPC should try to create a 
listing of such groups?

Outcome Transparency: deleting this item.  Doing so would be a defensive 
writing gesture warding off critiques of naivete.

MP>>Disagree, perhaps needs to be reworded to indicate something to be 
aimed at, rather than something 'required'. Most references to human 
rights would be deleted if we followed the logic of expecting 
organizations to follow HR recommendations; international human rights 
are only normative, with no enforcement mechanism, this is especially 
true of the  International Covenant on Economic, Social and Cultural 
Rights, which is explictly has a 'Principle of progressive realisation'.

Best wishes, and again thanks to Sandra
Mark P.

Le 12/02/2021 à 10:25, Sandra Braman a écrit :
> Folks --
>
> Following are some comments on draft guidelines, some of which echo 
> points already made on this list. If I've misunderstood anything, 
> please let me know.  Some of the comments are analytical.  Others are 
> recommendations that may make the document more effective.  Again, 
> thanks to the authors and those who provided feedback and input to the 
> authors for all the labor put in.
>
> Sandra Braman
>
> ----------------------------------------------------------
>
> _Human Rights_
>
> Graph 2 on page 4 identifies key sources of human rights. The manner 
> of presentation conflates documents from sources that are importantly 
> different regarding their source and, thus, relative weight.  A 
> document created by the Internet Governance Forum -- a talk shop only 
> that has no status within the international legal system on its own -- 
> with United Nations treaties.  This section of the document will be 
> much stronger if separate paragraphs discuss actual legal foundations 
> for human rights and other sources of proposals for things that should 
> be considered human rights in the Internet environment (the latter 
> would include Hill 2014, too, for example).  The IGF document is 
> certainly pertinent, but should be discussed in the manner one would 
> discuss the scholarly literature and "gray matter" (reports from 
> advocacy groups and non-profit organizations, etc.), not as if it were 
> international law.
>
> Which human rights will be discussed in this document should be 
> clearly articulated in the opening section, with definitions for the 
> purposes of this document and the sources of those rights, and then 
> used consistently throughout the document.  Late in the document the 
> "right to security" shows up; is this a rephrasing of Article 28 of 
> the Universal Declaration on Human Rights, or something else that is 
> not mentioned on page 4?
>
> Theoretically and operationally defining each concept presented as a 
> human right more thoroughly will be important. There is confusion in 
> this document, for example, between the right to access government 
> information, which is included in a number of constitutions and 
> constitution-like documents around the world and is considered 
> essential to the ability to hold governments accountable for their 
> action, and a right to access information in general (more typically 
> considered necessary to freedom of expression, since in order to talk 
> about something you have to have information about it).
>
> What arguments justify which two or three human rights of concern for 
> each item in section 3.3?  As presented in this draft, it seems 
> essentially random in a manner that is not persuasive regarding what 
> is in and what is out.
>
> _Direct vs Indirect Violations of Human Rights_
> _
> _
> Perhaps the most interesting thread running through this document is 
> the implicit suggestion that impediments to technological innovation 
> can themselves be understood as violations of human rights.  (Fully 
> developing that argument would make a great scholarly journal 
> article!)  I buy that argument, as innovations are often/may well be 
> needed to develop work-arounds for exercises of power that violate 
> human rights in traditionally understood ways, but this piece will be 
> much more effective and stronger if it makes that argument explicit 
> and uses it as a tool in the structuring of the narrative.
>
> The suggestions are two:  (1) Add an explicit discussion of the 
> distinction between direct violations of human rights (e.g., 
> censorship) and indirect violations of human rights (e.g., innovation, 
> which includes matters such as "adaptability" as introduced in this 
> draft). (2) Structure the discussion of topics in Section 3.3 to 
> clearly distinguish between the two.  A recommendation for an 
> alternative structuring of those topics can be found below.
>
> Another distinction that could usefully be introduced in this document 
> is the difference between short-term and long-term effects on human 
> rights.  Censorship is a short-term, immediate effect.  Differential 
> ability to access information about one's environment and that 
> provides the affordances for effective political action -- what was 
> first labelled "the knowledge gap" in the 1970s and is now more 
> commonly referred to as "the digital divide" -- is better understood 
> as a long-term effect on human rights.
>
> _Stages of the Internet Design Process and the Institutional Context_
> _
> _
> This draft mentions that different human rights issues come up at 
> different stages of the protocol development process. It also asks for 
> a lot of types of research and thinking that, as others have pointed 
> out, are not generally within the job description of those working on 
> Internet protocols and for which they may not have been trained -- 
> these are actually matters of organizational design.  This document 
> would be much stronger if it unbundled each of these things.
>
> For stages of the protocol design process, please say more about which 
> issues should be considered when?  Doing so would require offering a 
> model of the stages of the protocol design process.  It would be great 
> to have a section that does that and that then specifies which issues 
> would be of concern when.  The authors will probably want to include 
> "implementation" among the stages discussed.
>
> On the organizational design side, the document would be stronger if 
> it offered at least a model of what an organizational structure might 
> be that would include all of the different kinds of expertise required 
> to do the work asked for here, along with a mapping of the work flow 
> across employees with different types of expertise.
>
> _Research on the Effects of Design Decisions_
> _
> _
> A recurring problem in research on communication and the media is 
> confusing what can be learned from research on an actual text or set 
> of visuals and the effects of that text or visuals on those who 
> receive it.  In that context, textual analysis can only tell the 
> researcher what is in the text; for effects research, quite other 
> research methods must be used. The same problem runs throughout this 
> document.  The authors are encouraged to clearly distinguish the 
> features of a protocol itself, how the protocol operates within the 
> network (the technical "context" in the sense of how it interacts with 
> other protocols), how it is used in the application layer, how 
> applications are used, and the effects of the uses of those 
> applications.  A second issue raised by the methods introduced here is 
> that they run the danger of being limited to "looking under the 
> streetlight" (the familiar story about where a drunk is looking for 
> keys, irrespective of where they may be), although in terms of 
> provenance that problem may be more reflective of the fact that the 
> full scholarly literature and what can be learned from researchers 
> outside of the HRPC have not yet been brought to bear.
>
> Different research methods will be needed to examine each of these.  
> This document would be much stronger if it broke out which of the 
> kinds of questions raised can actually be the subjects of research at 
> each stage of this sequence, too.  The mixing of application layer and 
> use issues with protocol design in my view undermines the 
> effectiveness of the argument this reader, at least, understands the 
> authors to be trying to make.
>
> Research on designer perceptions of possible human rights risks can be 
> useful and interesting (I've done some of that research myself), but 
> does not tell the researcher anything about the actual risks as 
> experienced or as understood by social scientists who have studied 
> those effects on the ground. There are, however, several significant 
> bodies of research that the authors could mine for more empirical 
> detail on the effects of specific protocol design features rather than 
> assuming that universe is bounded by what one or a few members of HRPC 
> have done or asking computer scientists and electrical engineers to 
> undertake all of that work.  It is incredibly important to keep human 
> rights issues in front of those doing technical work, including 
> regularly showing up in IETF meetings to alert those designing 
> protocols to specific issues, but for research on the effects of those 
> protocols HRPC should be turning to social scientists who are actually 
> studying the effects and who could be encouraged to go further in this 
> area, sometimes -- so valuably -- in collaboration with technical 
> experts who have given themselves to this specific task.  In this 
> regard, the work of Ron Deibert's group at the University of Toronto 
> (Citizen Lab) should be highlighted as a model (https://citizenlab.ca/ 
> <https://citizenlab.ca/>).  Work in fields such as anthropology, 
> sociology, political science, information science, communication, STS 
> (studies of technology and society), and economics will all be useful.
>
> To date the HRPC (to my knowledge) has largely engaged with the 
> communities of researchers working in this area by bringing 
> individuals to IETF meetings for short presentations.  Given the 
> relatively small number of people active within HRPC who come from 
> social science backgrounds and limits on the time of everyone within 
> HRPC, some assistance may be needed to take advantage of the many 
> additional research methods that should be used to evaluate the 
> effects of protocol design on human rights as well as to incorporate 
> findings from research in this area already conducted into this 
> document.  A few thoughts regarding how that might be done will be 
> offered in a separate email.
>
> However it is done, going much further with research methods will 
> significantly increase the sophistication and utility of this 
> document.  As it currently stands, the section on "expert interviews" 
> is confusing because it appears to be asking computer scientists to be 
> expert on social science matters, for example.  Interviews with 
> various types of experts will indeed be among the kinds of methods 
> that can be useful, but the different types of expertise involved 
> should be acknowledged and different kinds of questions would be asked 
> of different kinds of experts.
>
> _Grouping of Section 3.3 Topics_
> _
> _
> Three dimensions of analysis could be used to better structure the 
> sequencing of topics in Section 3.3.  The suggestion here is to use 
> the focus of attention as the highest level used to group related 
> issues together, and then discuss differences between direct and 
> indirect effects and between short-term and long-term effects within 
> each of the categories.  A suggestion what the top-level of 
> categorization might look like is offered here, with the current 
> number of the topics to be included within it.  Because some of the 
> current topics combine types of issues, the final category includes 
> one item that in my view should be unbundled for clarification for the 
> purposes of this document and three items that in my view should be 
> deleted.  The following section discusses individual topics and/or the 
> combinations suggested here.
>
> /Network Operations/
> /
> /
> Connectivity (3.3.1)
> Internationalization (3.3.5)
> Localization (3.3.11)
> Adaptability (3.3.17)
>
> Open Standards (3.3.7)
> Heterogeneity Support (3.3.8)
>
> Decentralization (3.3.12)
>
> Reliability (3.3.13)
>
> /The Individual User/
> /
> /
> Privacy (3.3.2)
> Pseudonymity (3.3.9)
> Confidentiality (3.3.14)
> Anonymity (3.3.19)
>
> Accessibility (3.3.10)
>
> /Content/
> /
> /
> Content Agnosticism (3.3.3)
>
> Censorship Resistance (3.3.6)
> Integrity (3.3.15)
> Authenticity (3.3.16)
>
> /To Be Unbundled/
> /
> /
> Security (3.3.4)
>
> /Delete/
>
> Outcome Transparency (3.3.18)
> Remedy and Attribution (3.3.20)
> Miscellaneous Considerations (3.3.21)
> /
> /
> _Discussion of Topics and Topic Groupings_
> _
> _
> /Network Operations/
> /
> /
> Decentralization is separated out because the extent to which 
> decentralization can occur operates at so many different levels of the 
> structures involved -- the network, applications, the social 
> structure, and political structure -- that it is different in kind 
> from the first 5 items above that seem to me (as someone who is NOT a 
> technical expert) to be related to each other.  Reliability also seems 
> to me to be different in kind.
>
> In the scholarly journal article "The Framing Years," the concept of 
> "technological democracy" as a key design principle for the Internet 
> was introduced.  The topics of Open Standards and Heterogeneity 
> additionally can be distinguished by this feature.
>
> The Decentralization topic mixes several different types of control 
> from diverse sources (governments, protocol limits, etc.) together 
> without distinguishing them.  The document will be stronger, clearer, 
> and more useful if it distinguishes them.
>
> In the scholarly journal article "The Geopolitical and the Network 
> Political:  Internet Designers and Governance," the tension between 
> geopolitical citizenship (allegiance to one's identity as a citizen of 
> a geopolitically recognized state -- a government recognized by the 
> UN) and network citizenship (allegiance to one's identity as a 
> user/citizen of the Internet, the success of which is critical to the 
> user) is explored.  There are often instances in which what is 
> required of the geopolitical citizen is the opposite of what is 
> required of the network citizen.  That is the tension discussed on 
> page 17, graph 2.
>
> /The Individual User/
>
> All of the topics related to the diverse dimensions of personal 
> privacy should be grouped together.  They would be best introduced 
> with a general introduction to RFC 4949. Doing so would then 
> facilitate further analysis of what might differently be needed to 
> attend to when thinking about each of the concepts distinguished there 
> (if there are differences).
>
> Accessibility is different in kind as a topic.  However, the RFC 
> referred to in that discussion, as I understand it, actually refers to 
> technical limits and/or limits of access to images that may be in 
> place because of a particular tool a specific individual chooses to 
> use, not to human disability. Is there anything else that deals with 
> human disability at the protocol level that can be called upon here 
> more validly? Most of what I am aware of is at the application level.
>
> /Content/
>
> Content agnosticism is a tough one for two reasons.  First, any 
> decision about structure made by definition will preference some 
> content or users (and thus those users' content) over others -- for 
> any door that is opened, another door is shut.  By the close of the 
> 1990s (the period through which my own research went), several 
> different models were experimented with to achieve "fair queuing," and 
> struggles with "quality of service" have continued since.  What is 
> said here about content agnosticism should reference all of that 
> history and make specific recommendations if it sees a way out of this 
> dilemma that others have not yet been able to discover.  Second, 
> national governments are always going to assert priority access.  It 
> is wishful thinking only to believe that would be otherwise.  The fix 
> here for this document would be to simply acknowledge that.
>
> In the discussion of Authenticity, isn't there another scenario when 
> considering authentication?  This would add another line to the last 
> scenario provided:  Bob knows who or what altered the data that did 
> not come from Alice.  Why should this not also be a requirement?  
> Surveillance should go both ways (that is why we have access to 
> government information as a fundamental constitutional principle).
>
> /To be Unbundled/
> /
> /
> The existing topic of "security" includes elements that would, in my 
> view, be more strongly included if they were unbundled, with elements 
> dispersed into the above categories to join those that are like of kind.
>
> /To be Deleted/
> /
> /
> Outcome Transparency -- This is a reasonable expectation only if every 
> organization employing those involved in the protocol design process 
> were to take up recommendations these authors have yet to develop for 
> organizational structure and work flow processes adequate to the range 
> of kinds of research being asked for here.  Since it is unlikely that 
> those recommendations for organizational structure and work flow 
> processes, will be forthcoming within the probable life cycle of the 
> writing of this document, and since it is even more unlikely that all 
> of the organizations involved would follow such recommendations if 
> offered, in my view it would strengthen the document by deleting this 
> item.  Doing so would be a defensive writing gesture warding off 
> critiques of naivete.
>
> Remedy and Attribution -- Others have made excellent points on this 
> matter on the listserv.  Everything that would be pertinent here 
> should be covered by the topics introduced that apply to individual 
> users.  If that is not the case, the authors need to make clear what 
> else would be involved. Delete as a topic but add to the discussion 
> that introduces the document.
>
> Miscellaneous Considerations -- Don't see what this obvious point adds.
>
> _Other Conceptual Issues_
> _
> _
> How do the authors distinguish between the effects of protocol-shaped 
> communications between humans, between humans and non-humans, and 
> between non-humans from a human rights perspective?  Protocol design 
> features that impede the ability to make effective use of what is 
> learned from environmental sensors, for example, could generage 
> long-term human rights impacts.  Not mentioned at all here but it 
> would be a stronger document if it were.
>
> Page 6, graph 4 (in 3.3) -- What is meant by "misapplication of the 
> protocol or technology"?  That is really two questions in one.  First, 
> how do the authors distinguish an appropriate application from a 
> misapplication? Second, as again has been brought up in discussion of 
> this draft on the list, isn't this about users and not the protocol 
> design that is the focus of the document?  Those involved with 
> attempts to prevent uses of dual use technologies for purposes of war 
> rather than peace have struggled with this for decades; the inability 
> to meaningfully, defensibly, and effectively grab ahold of it has 
> essentially led to the abandonment of the effort.
>
> How do the authors evaluate the "adequacy" with which a given protocol 
> takes human rights into account?  (page 6, graph 5)
>
> The question of whether or not protocols need to be understandable by 
> humans is one of the most amusing elements of discussion in the RFCs 
> during their first decade (1969-1979) (again, an article available if 
> of interest).  In 3.3.5, on internationalization (p. 9, second graph 
> from bottom), the question is about text strings that "have to be" 
> understood or entered by humans.  What about situations in which the 
> more accurate verb would be "can be"?
>
> Re Internationalization -- See my comments on draft association re the 
> language issue.
>
> In areas such as degradation, the distinction should be drawn between 
> degradation and knowledge of degradation.  That is also true for 
> integrity and in other areas that can, under some circumstances, also 
> include even censorship.
>
> _Writing Issues_
> _
> _
> 3.2.1 -- This paragraph is opaque.
>
> 3.2.2 -- This paragraph is tautological.
>
> 3.3.2 -- Page 8, graph 3 -- The document on privacy is not an "example."
>
> 3.3.20 -- Page 23, graph 1 -- The reference to Kaye's thinking on 
> freedom of expression and the Internet belongs in the discussion of 
> human rights principles, not here.
>
> There are a number of typographical and grammar errors throughout.
>
>
>
> _
> _
>
> _
> _
>
> _
> _
>
>
> _
> _
> _
> _
>
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc


-- 
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

--------------E8287561E66483D80DBAF8CA
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Thanks for the 'heavy lifting' done by Sandra</p>
    <p>A few comments/issues:</p>
    <p>The point on sources is well put, but the example 'right to
      access government information' is misused; the problem is more
      that the document has not taken into account the United Nations
      Human Rights Committee General Comments which indicate the
      official interpretation of the relevant articles, which indicates
      the need for 'separate paragraphs discuss actual legal foundations
      for human rights and other sources of proposals for things that
      should be considered human rights in the Internet environment' :<br>
    </p>
    <p>The United Nations Human Rights Committee confirmed in July 2011
      that the right to freedom of expression protected by Article 19 of
      the International Covenant on Civil and Political Rights includes
      the right of access to information.The Committee said: “Article
      19, paragraph 2 embraces a right of access to information held by
      public bodies. Such information includes records held by a public
      body, regardless of the form in which the information is stored,
      its source and the date of production.”<br>
      <br>
      Human Rights Committee, 102 nd session, Geneva, 11-29 July 2011<br>
      General comment No. 34 -vvArticle 19: Freedoms of opinion and
      expression</p>
    <p>"Perhaps the most interesting thread running through this
      document is the implicit suggestion that impediments to
      technological innovation can themselves be understood as
      violations of human rights.  (Fully developing that argument would
      make a great scholarly journal article!)"</p>
    <p>I agree - though perhaps Article 15 of International Covenant on
      Economic, Social and Cultural Rights would cover the question?<br>
    </p>
    <p>The distinction between short &amp; long term effects needs to be
      drawn with care &amp; the linkage between them made explicit: <br>
    </p>
    <p>While censorship can be seen as an 'immediate/short' term effect,
      such censorship can lead to long term effects, such as inability
      to hold government to account, inability to avoid hunger/famine,
      etc.</p>
    <p>The digital divide (or knowledge gap) can be seen as a long term
      effect ( affordances for effective political action) but for the
      individual it can have the same impact as censorship - inability
      to access information, ie. a short term effect.<br>
    </p>
    <p>'A second issue raised by the methods introduced here is that
      they run the danger of being limited to "looking under the
      streetlight" (the familiar story about where a drunk is looking
      for keys, irrespective of where they may be), although in terms of
      provenance that problem may be more reflective of the fact that
      the full scholarly literature and what can be learned from
      researchers outside of the HRPC have not yet been brought to
      bear.' <br>
    </p>
    <p>MP&gt;&gt;I would add the 'crooked neck' analogy (the story where
      everyone at a bus stop ends up looking in same direction, until
      someone asks the first in the queue what he is looking, &amp; he
      replies - nothing, I have a crook in my neck). So 'full' scholarly
      literature should also include diversity...</p>
    <p>'but for research on the effects of those protocols HRPC should
      be turning to social scientists who are actually studying the
      effects and who could be encouraged to go further in this area,
      sometimes -- so valuably -- in collaboration with technical
      experts who have given themselves to this specific task.  In this
      regard, the work of Ron Deibert's group at the University of
      Toronto (Citizen Lab) should be highlighted as a model (<a
        href="https://citizenlab.ca/">https://citizenlab.ca/</a>).  Work
      in fields such as anthropology, sociology, political science,
      information science, communication, STS (studies of technology and
      society), and economics will all be useful.' <br>
    </p>
    <p>MP&gt;&gt; Oxford Internet Institute also, perhaps HRPC should
      try to create a listing of such groups?</p>
    <p>Outcome Transparency: deleting this item.  Doing so would be a
      defensive writing gesture warding off critiques of naivete.</p>
    <p>MP&gt;&gt;Disagree, perhaps needs to be reworded to indicate
      something to be aimed at, rather than something 'required'. Most
      references to human rights would be deleted if we followed the
      logic of expecting organizations to follow HR recommendations;
      international human rights are only normative, with no enforcement
      mechanism, this is especially true of the  International Covenant
      on Economic, Social and Cultural Rights, which is explictly has a
      'Principle of progressive realisation'.<br>
    </p>
    <div>Best wishes, and again thanks to Sandra</div>
    <div>Mark P.</div>
    <div><br>
    </div>
    <div class="moz-cite-prefix">Le 12/02/2021 à 10:25, Sandra Braman a
      écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Folks -- 
        <div><br>
        </div>
        <div>Following are some comments on draft guidelines, some of
          which echo points already made on this list. If I've
          misunderstood anything, please let me know.  Some of the
          comments are analytical.  Others are recommendations that may
          make the document more effective.  Again, thanks to the
          authors and those who provided feedback and input to the
          authors for all the labor put in.<br>
        </div>
        <div><br>
          Sandra Braman</div>
        <div><br>
        </div>
        <div>----------------------------------------------------------</div>
        <div><br>
        </div>
        <div><u>Human Rights</u></div>
        <div><br>
        </div>
        <div>Graph 2 on page 4 identifies key sources of human rights. 
          The manner of presentation conflates documents from sources
          that are importantly different regarding their source and,
          thus, relative weight.  A document created by the Internet
          Governance Forum -- a talk shop only that has no status within
          the international legal system on its own -- with United
          Nations treaties.  This section of the document will be much
          stronger if separate paragraphs discuss actual legal
          foundations for human rights and other sources of proposals
          for things that should be considered human rights in the
          Internet environment (the latter would include Hill 2014, too,
          for example).  The IGF document is certainly pertinent, but
          should be discussed in the manner one would discuss the
          scholarly literature and "gray matter" (reports from advocacy
          groups and non-profit organizations, etc.), not as if it were
          international law.</div>
        <div><br>
        </div>
        <div>Which human rights will be discussed in this document
          should be clearly articulated in the opening section, with
          definitions for the purposes of this document and the sources
          of those rights, and then used consistently throughout the
          document.  Late in the document the "right to security" shows
          up; is this a rephrasing of Article 28 of the Universal
          Declaration on Human Rights, or something else that is not
          mentioned on page 4?</div>
        <div><br>
        </div>
        <div>Theoretically and operationally defining each concept
          presented as a human right more thoroughly will be important. 
          There is confusion in this document, for example, between the
          right to access government information, which is included in a
          number of constitutions and constitution-like documents around
          the world and is considered essential to the ability to hold
          governments accountable for their action, and a right to
          access information in general (more typically considered
          necessary to freedom of expression, since in order to talk
          about something you have to have information about it).</div>
        <div><br>
        </div>
        <div>What arguments justify which two or three human rights of
          concern for each item in section 3.3?  As presented in this
          draft, it seems essentially random in a manner that is not
          persuasive regarding what is in and what is out.</div>
        <div><br>
        </div>
        <div><u>Direct vs Indirect Violations of Human Rights</u></div>
        <div><u><br>
          </u></div>
        <div>Perhaps the most interesting thread running through this
          document is the implicit suggestion that impediments to
          technological innovation can themselves be understood as
          violations of human rights.  (Fully developing that argument
          would make a great scholarly journal article!)  I buy that
          argument, as innovations are often/may well be needed to
          develop work-arounds for exercises of power that violate human
          rights in traditionally understood ways, but this piece will
          be much more effective and stronger if it makes that argument
          explicit and uses it as a tool in the structuring of the
          narrative.</div>
        <div><br>
        </div>
        <div>The suggestions are two:  (1) Add an explicit discussion of
          the distinction between direct violations of human rights
          (e.g., censorship) and indirect violations of human rights
          (e.g., innovation, which includes matters such as
          "adaptability" as introduced in this draft). (2) Structure the
          discussion of topics in Section 3.3 to clearly distinguish
          between the two.  A recommendation for an alternative
          structuring of those topics can be found below.</div>
        <div><br>
        </div>
        <div>Another distinction that could usefully be introduced in
          this document is the difference between short-term and
          long-term effects on human rights.  Censorship is a
          short-term, immediate effect.  Differential ability to access
          information about one's environment and that provides the
          affordances for effective political action -- what was first
          labelled "the knowledge gap" in the 1970s and is now more
          commonly referred to as "the digital divide" -- is better
          understood as a long-term effect on human rights.</div>
        <div><br>
        </div>
        <div><u>Stages of the Internet Design Process and the
            Institutional Context</u></div>
        <div><u><br>
          </u></div>
        <div>This draft mentions that different human rights issues come
          up at different stages of the protocol development process. 
          It also asks for a lot of types of research and thinking that,
          as others have pointed out, are not generally within the job
          description of those working on Internet protocols and for
          which they may not have been trained -- these are actually
          matters of organizational design.  This document would be much
          stronger if it unbundled each of these things.</div>
        <div><br>
        </div>
        <div>For stages of the protocol design process, please say more
          about which issues should be considered when?  Doing so would
          require offering a model of the stages of the protocol design
          process.  It would be great to have a section that does that
          and that then specifies which issues would be of concern
          when.  The authors will probably want to include
          "implementation" among the stages discussed.</div>
        <div><br>
        </div>
        <div>On the organizational design side, the document would be
          stronger if it offered at least a model of what an
          organizational structure might be that would include all of
          the different kinds of expertise required to do the work asked
          for here, along with a mapping of the work flow across
          employees with different types of expertise.</div>
        <div><br>
        </div>
        <div><u>Research on the Effects of Design Decisions</u></div>
        <div><u><br>
          </u></div>
        <div>A recurring problem in research on communication and the
          media is confusing what can be learned from research on an
          actual text or set of visuals and the effects of that text or
          visuals on those who receive it.  In that context, textual
          analysis can only tell the researcher what is in the text; for
          effects research, quite other research methods must be used. 
          The same problem runs throughout this document.  The authors
          are encouraged to clearly distinguish the features of a
          protocol itself, how the protocol operates within the network
          (the technical "context" in the sense of how it interacts with
          other protocols), how it is used in the application layer, how
          applications are used, and the effects of the uses of those
          applications.  A second issue raised by the methods introduced
          here is that they run the danger of being limited to "looking
          under the streetlight" (the familiar story about where a drunk
          is looking for keys, irrespective of where they may be),
          although in terms of provenance that problem may be more
          reflective of the fact that the full scholarly literature and
          what can be learned from researchers outside of the HRPC have
          not yet been brought to bear.</div>
        <div><br>
        </div>
        <div>Different research methods will be needed to examine each
          of these.  This document would be much stronger if it broke
          out which of the kinds of questions raised can actually be the
          subjects of research at each stage of this sequence, too.  The
          mixing of application layer and use issues with protocol
          design in my view undermines the effectiveness of the argument
          this reader, at least, understands the authors to be trying to
          make. </div>
        <div><br>
        </div>
        <div>Research on designer perceptions of possible human rights
          risks can be useful and interesting (I've done some of that
          research myself), but does not tell the researcher anything
          about the actual risks as experienced or as understood by
          social scientists who have studied those effects on the
          ground. There are, however, several significant bodies of
          research that the authors could mine for more empirical detail
          on the effects of specific protocol design features rather
          than assuming that universe is bounded by what one or a few
          members of HRPC have done or asking computer scientists and
          electrical engineers to undertake all of that work.  It is
          incredibly important to keep human rights issues in front of
          those doing technical work, including regularly showing up in
          IETF meetings to alert those designing protocols to specific
          issues, but for research on the effects of those protocols
          HRPC should be turning to social scientists who are actually
          studying the effects and who could be encouraged to go further
          in this area, sometimes -- so valuably -- in collaboration
          with technical experts who have given themselves to this
          specific task.  In this regard, the work of Ron Deibert's
          group at the University of Toronto (Citizen Lab) should be
          highlighted as a model (<a href="https://citizenlab.ca/"
            moz-do-not-send="true">https://citizenlab.ca/</a>).  Work in
          fields such as anthropology, sociology, political science,
          information science, communication, STS (studies of technology
          and society), and economics will all be useful.</div>
        <div><br>
        </div>
        <div>To date the HRPC (to my knowledge) has largely engaged with
          the communities of researchers working in this area by
          bringing individuals to IETF meetings for short
          presentations.  Given the relatively small number of people
          active within HRPC who come from social science backgrounds
          and limits on the time of everyone within HRPC, some
          assistance may be needed to take advantage of the many
          additional research methods that should be used to evaluate
          the effects of protocol design on human rights as well as to
          incorporate findings from research in this area already
          conducted into this document.  A few thoughts regarding how
          that might be done will be offered in a separate email.</div>
        <div><br>
        </div>
        <div>However it is done, going much further with research
          methods will significantly increase the sophistication and
          utility of this document.  As it currently stands, the section
          on "expert interviews" is confusing because it appears to be
          asking computer scientists to be expert on social science
          matters, for example.  Interviews with various types of
          experts will indeed be among the kinds of methods that can be
          useful, but the different types of expertise involved should
          be acknowledged and different kinds of questions would be
          asked of different kinds of experts.</div>
        <div><br>
        </div>
        <div><u>Grouping of Section 3.3 Topics</u></div>
        <div><u><br>
          </u></div>
        <div>Three dimensions of analysis could be used to better
          structure the sequencing of topics in Section 3.3.  The
          suggestion here is to use the focus of attention as the
          highest level used to group related issues together, and then
          discuss differences between direct and indirect effects and
          between short-term and long-term effects within each of the
          categories.  A suggestion what the top-level of categorization
          might look like is offered here, with the current number of
          the topics to be included within it.  Because some of the
          current topics combine types of issues, the final category
          includes one item that in my view should be unbundled for
          clarification for the purposes of this document and three
          items that in my view should be deleted.  The following
          section discusses individual topics and/or the combinations
          suggested here. </div>
        <div><br>
        </div>
        <div><i>Network Operations</i></div>
        <div><i><br>
          </i></div>
        <div>Connectivity (3.3.1)</div>
        <div>Internationalization (3.3.5)</div>
        <div>Localization (3.3.11)</div>
        <div>Adaptability (3.3.17)<br>
        </div>
        <div><br>
        </div>
        <div>
          <div>Open Standards (3.3.7)</div>
          <div>Heterogeneity Support (3.3.8)</div>
        </div>
        <div><br>
        </div>
        <div>Decentralization (3.3.12)</div>
        <div><br>
        </div>
        <div>Reliability (3.3.13)</div>
        <div><br>
        </div>
        <div><i>The Individual User</i></div>
        <div><i><br>
          </i></div>
        <div>Privacy (3.3.2)</div>
        <div>Pseudonymity (3.3.9)</div>
        <div>Confidentiality (3.3.14)</div>
        <div>Anonymity (3.3.19)</div>
        <div><br>
        </div>
        <div>Accessibility (3.3.10)</div>
        <div><br>
        </div>
        <div><i>Content</i></div>
        <div><i><br>
          </i></div>
        <div>Content Agnosticism (3.3.3)</div>
        <div><br>
        </div>
        <div>Censorship Resistance (3.3.6)</div>
        <div>Integrity (3.3.15)</div>
        <div>Authenticity (3.3.16)</div>
        <div><br>
        </div>
        <div><i>To Be Unbundled</i></div>
        <div><i><br>
          </i></div>
        <div>Security (3.3.4) </div>
        <div><br>
        </div>
        <div><i>Delete</i></div>
        <div><br>
        </div>
        <div>Outcome Transparency (3.3.18)</div>
        <div>Remedy and Attribution (3.3.20)</div>
        <div>Miscellaneous Considerations (3.3.21)</div>
        <div><i><br>
          </i></div>
        <div><u>Discussion of Topics and Topic Groupings</u></div>
        <div><u><br>
          </u></div>
        <div><i>Network Operations</i></div>
        <div><i><br>
          </i></div>
        <div>Decentralization is separated out because the extent to
          which decentralization can occur operates at so many different
          levels of the structures involved -- the network,
          applications, the social structure, and political structure --
          that it is different in kind from the first 5 items above that
          seem to me (as someone who is NOT a technical expert) to be
          related to each other.  Reliability also seems to me to be
          different in kind.</div>
        <div><br>
        </div>
        <div>In the scholarly journal article "The Framing Years," the
          concept of "technological democracy" as a key design principle
          for the Internet was introduced.  The topics of Open Standards
          and Heterogeneity additionally can be distinguished by this
          feature.</div>
        <div><br>
        </div>
        <div>The Decentralization topic mixes several different types of
          control from diverse sources (governments, protocol limits,
          etc.) together without distinguishing them.  The document will
          be stronger, clearer, and more useful if it distinguishes
          them.</div>
        <div><br>
        </div>
        <div>In the scholarly journal article "The Geopolitical and the
          Network Political:  Internet Designers and Governance," the
          tension between geopolitical citizenship (allegiance to one's
          identity as a citizen of a geopolitically recognized state --
          a government recognized by the UN) and network citizenship
          (allegiance to one's identity as a user/citizen of the
          Internet, the success of which is critical to the user) is
          explored.  There are often instances in which what is required
          of the geopolitical citizen is the opposite of what is
          required of the network citizen.  That is the tension
          discussed on page 17, graph 2.</div>
        <div><br>
        </div>
        <div><i>The Individual User</i></div>
        <div><br>
        </div>
        <div>All of the topics related to the diverse dimensions of
          personal privacy should be grouped together.  They would be
          best introduced with a general introduction to RFC 4949. 
          Doing so would then facilitate further analysis of what might
          differently be needed to attend to when thinking about each of
          the concepts distinguished there (if there are differences).</div>
        <div><br>
        </div>
        <div>Accessibility is different in kind as a topic.  However,
          the RFC referred to in that discussion, as I understand it,
          actually refers to technical limits and/or limits of access to
          images that may be in place because of a particular tool a
          specific individual chooses to use, not to human disability. 
          Is there anything else that deals with human disability at the
          protocol level that can be called upon here more validly? 
          Most of what I am aware of is at the application level.</div>
        <div><br>
        </div>
        <div><i>Content</i></div>
        <div><br>
        </div>
        <div>Content agnosticism is a tough one for two reasons.  First,
          any decision about structure made by definition will
          preference some content or users (and thus those users'
          content) over others -- for any door that is opened, another
          door is shut.  By the close of the 1990s (the period through
          which my own research went), several different models were
          experimented with to achieve "fair queuing," and struggles
          with "quality of service" have continued since.  What is said
          here about content agnosticism should reference all of that
          history and make specific recommendations if it sees a way out
          of this dilemma that others have not yet been able to
          discover.  Second, national governments are always going to
          assert priority access.  It is wishful thinking only to
          believe that would be otherwise.  The fix here for this
          document would be to simply acknowledge that.</div>
        <div><br>
        </div>
        <div>In the discussion of Authenticity, isn't there another
          scenario when considering authentication?  This would add
          another line to the last scenario provided:  Bob knows who or
          what altered the data that did not come from Alice.  Why
          should this not also be a requirement?  Surveillance should go
          both ways (that is why we have access to government
          information as a fundamental constitutional principle).</div>
        <div><br>
        </div>
        <div><i>To be Unbundled</i></div>
        <div><i><br>
          </i></div>
        <div>The existing topic of "security" includes elements that
          would, in my view, be more strongly included if they were
          unbundled, with elements dispersed into the above categories
          to join those that are like of kind.</div>
        <div><br>
        </div>
        <div><i>To be Deleted</i></div>
        <div><i><br>
          </i></div>
        <div>Outcome Transparency -- This is a reasonable expectation
          only if every organization employing those involved in the
          protocol design process were to take up recommendations these
          authors have yet to develop for organizational structure and
          work flow processes adequate to the range of kinds of research
          being asked for here.  Since it is unlikely that those
          recommendations for organizational structure and work flow
          processes, will be forthcoming within the probable life cycle
          of the writing of this document, and since it is even more
          unlikely that all of the organizations involved would follow
          such recommendations if offered, in my view it would
          strengthen the document by deleting this item.  Doing so would
          be a defensive writing gesture warding off critiques of
          naivete.</div>
        <div><br>
        </div>
        <div>Remedy and Attribution -- Others have made excellent points
          on this matter on the listserv.  Everything that would be
          pertinent here should be covered by the topics introduced that
          apply to individual users.  If that is not the case, the
          authors need to make clear what else would be involved. 
          Delete as a topic but add to the discussion that introduces
          the document.</div>
        <div><br>
        </div>
        <div>Miscellaneous Considerations -- Don't see what this obvious
          point adds.</div>
        <div><br>
        </div>
        <div><u>Other Conceptual Issues</u></div>
        <div><u><br>
          </u></div>
        <div>How do the authors distinguish between the effects of
          protocol-shaped communications between humans, between humans
          and non-humans, and between non-humans from a human rights
          perspective?  Protocol design features that impede the ability
          to make effective use of what is learned from environmental
          sensors, for example, could generage long-term human rights
          impacts.  Not mentioned at all here but it would be a stronger
          document if it were.</div>
        <div><br>
        </div>
        <div>Page 6, graph 4 (in 3.3) -- What is meant by
          "misapplication of the protocol or technology"?  That is
          really two questions in one.  First, how do the authors
          distinguish an appropriate application from a misapplication? 
          Second, as again has been brought up in discussion of this
          draft on the list, isn't this about users and not the protocol
          design that is the focus of the document?  Those involved with
          attempts to prevent uses of dual use technologies for purposes
          of war rather than peace have struggled with this for decades;
          the inability to meaningfully, defensibly, and effectively
          grab ahold of it has essentially led to the abandonment of the
          effort.</div>
        <div><br>
        </div>
        <div>How do the authors evaluate the "adequacy" with which a
          given protocol takes human rights into account?  (page 6,
          graph 5)</div>
        <div><br>
        </div>
        <div>The question of whether or not protocols need to be
          understandable by humans is one of the most amusing elements
          of discussion in the RFCs during their first decade
          (1969-1979) (again, an article available if of interest).  In
          3.3.5, on internationalization (p. 9, second graph from
          bottom), the question is about text strings that "have to be"
          understood or entered by humans.  What about situations in
          which the more accurate verb would be "can be"?</div>
        <div><br>
        </div>
        <div>Re Internationalization -- See my comments on draft
          association re the language issue.</div>
        <div><br>
        </div>
        <div>In areas such as degradation, the distinction should be
          drawn between degradation and knowledge of degradation.  That
          is also true for integrity and in other areas that can, under
          some circumstances, also include even censorship.</div>
        <div><br>
        </div>
        <div><u>Writing Issues</u><br>
        </div>
        <div><u><br>
          </u></div>
        <div>3.2.1 -- This paragraph is opaque.</div>
        <div><br>
        </div>
        <div>3.2.2 -- This paragraph is tautological.</div>
        <div><br>
        </div>
        <div>3.3.2 -- Page 8, graph 3 -- The document on privacy is not
          an "example."</div>
        <div><br>
        </div>
        <div>3.3.20 -- Page 23, graph 1 -- The reference to Kaye's
          thinking on freedom of expression and the Internet belongs in
          the discussion of human rights principles, not here.</div>
        <div><br>
        </div>
        <div>There are a number of typographical and grammar errors
          throughout.</div>
        <div><br>
        </div>
        <div> </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><u><br>
          </u></div>
        <div><br>
        </div>
        <div><u><br>
          </u></div>
        <div><br>
        </div>
        <div><u><br>
          </u></div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><u><br>
          </u></div>
        <div><u><br>
          </u></div>
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
hrpc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hrpc@irtf.org">hrpc@irtf.org</a>
<a class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/hrpc">https://www.irtf.org/mailman/listinfo/hrpc</a>
</pre>
    </blockquote>
  <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table style="border-top: 1px solid #D3D4DE;">
	<tr>
      <td style="width: 55px; padding-top: 18px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
		<td style="width: 470px; padding-top: 17px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Garanti sans virus. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a> 		</td>
	</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>

--------------E8287561E66483D80DBAF8CA--


From nobody Mon Feb 15 05:27:22 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 74BEC3A09C0 for <hrpc@ietfa.amsl.com>; Mon, 15 Feb 2021 05:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=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 srdrxDFBir5M for <hrpc@ietfa.amsl.com>; Mon, 15 Feb 2021 05:27:18 -0800 (PST)
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 532623A09BE for <hrpc@irtf.org>; Mon, 15 Feb 2021 05:27:18 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org CC20F5806C016
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1613395620; bh=p6YGzlYZ2UuPNDlHLxHtjflyR/TpqGvIZwsBi2oCQW0=; h=To:From:Message-ID:Date:MIME-Version; b=QL3izDQjrnh9e6OPlBB/ZGmt3XFOfFcFGokIm0JJ1a5cV78t6PvGYqCVPBKJIZGp/ PkIh5c/FxnMbQHxFCNpkvxeVeIL1SxvJZgdKz6/cNWAUTPSXQGJZjYIl/3F6JjF78Z MgkNtX/71toBTdTHMT9aU5JIMTVA3s1r98l1fr8TABD4KF3xyfG7Pu7wxcOwY41w9a 2mP2y2Zk1mTsGN4rpUPQV3uzJtf3xmEd5jgp+Ws7bSBKa6sh+h7Pfuev9jsI3h7z3g bAiV5OF7Ont1LWVa3rhaqbGmY0+rykqe6rwpx8M11Mr6UY7hGj9IYUA2xYs6hQSpbo ZQ84oHbMdNErQ==
To: Sandra Braman <braman@tamu.edu>, hrpc@irtf.org
References: <CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com>
Cc: Corinne Cath <corinnecath@gmail.com>, Bill Woodcock <woody@pch.net>
From: Gurshabad Grover <gurshabad@cis-india.org>
Autocrypt: addr=gurshabad@cis-india.org; keydata= mQINBFriroIBEADfyDpCD8eborMUMXKtZzjo4t2KzrAlUVYgE/TFtrwUP+4Xw4dzakDIzST8 sVYmlXIWhM5NBBTZSQ190vsxrkbi0xxLcXYM2olZEtqkJ8zONZeZLBeGvcfMymtHqD4jHwYb Zm7OXnS45fWDL+HOoMP/VCwEn098rYfnllIkYQD1Gc28Ig+ywjGg8y5p0qMmmmhm2ckgLjnG MJX8t273MSc8wsn/UYH922yif3MQXmrzqgnRl9hRzf90SKqAw38bw7wccb55pIItloKYsi0r zYBKJSOPXn91Z21TpOSTy21M0MZYEAlDn1zeea+q8TggfHNWxOXoKrIm1pqZFRz0k+8i2siJ AHf8bRm/fhukA6szZ6b2nNPxjkAmOv9zvGu6RZGbmeLvQYVBSSnZ67ayZrkKwn7KIyAV6hQM /bVnD8eEZ2tZ0S8lxoZFYSNeMGt2b6WelFZO97/LbjxaJUHd9K8g5H0MwqN1NXoBxRwllVRC 3sVHVoWTBqnKo8qplzvQEAto69PpvuxxKTOFEJeQqmn1b/fo3sLRb4YiIg8Ax+Np7Huzzjk6 vKKgpIwIN7yEUj/ReWi/UA/W4wSg3XkcqTf7h73crnN/1At0PdgozbDV2UbcApaldStP4DfG UiQl0/7MiYLKapDDuSahmoeH3xrNnrzS9BAfuGHezzDbMyPLXQARAQABtCpHdXJzaGFiYWQg R3JvdmVyIDxndXJzaGFiYWRAY2lzLWluZGlhLm9yZz6JAj0EEwEIACcFAlriroICGyMFCQlm AYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQrbl/X+ubfC7/bQ//YQv7zqQE433xxsN/ 3GYKoOFccBy3WvV4DxrTskJ3n3k5lfcZolbc8TQksQOTzyerNt2ZA7fsGZa7eFSW+xR4Yq3/ C9o+5FOoHGhyZhb+x17MILhmyvyUNSj7SdKrRISgurMbV2Vv8LxmTcdrK6CdFF6JLH+opzU1 NlRKwZqROPgbYZEB2QFIUbGfgh2I5AXNyV2XbT7fagfkHk+v9AUV7POP2H1+AZ1xq6iFTm2o 9ufNZsp2bInsDohcVBKC3aH2cnFMjvIXpNoUOx8vb5A2xW0aBUTTJDB/uZw53WOg3kehrCNb ZkML3FnDZLRuu1e8DSWmwk5YIoDzt5bMCgfUwb0C6Q+JuM8lC+8CEEa9qamLc+fhvFAzcrWp VWuSaVeLdhe5NxmtlRYNZdGuKy6sRHjwsEWlwzRylhm74fiDR3aA1eIFsfmYLd4z+i1Fp23Y dHJf7/Gor2CmOxphog9DEA9WCuORXfx4De7hoMKwW4gWKw1A8B12Cv4EOkXmCsWsOnfDEarr 2Yl6elxkhQRfKjAesXb0cezRzZgwsWIsbeYsuWFF7Xi6IzUJ27lxU3p5PcyY8O8aDYOn+pu0 YFJ7s3u2VRRgptVZJmkcN3WTApXSHY8fGl5xAakM/bqFJj9uj5zlMnFN2EplC6/mQkfYfy2f siaGTP/GQV4OSuOeuMK5Ag0EWuKuggEQAJ4lAzB72gHw4+rbyxmQNNVmvgYVZPjFtO/MQdYi x1QwRP/gxxqPqTd/ZwQvmPGzXRKw10B7uKSRk6YP12+IG0mXJwHGp9q5CWJE0XNGqX3UWbAc KIzxqPNpsf8e6Bv7jdW0YwLBxJ+RW0NNL6uAxz0sr2frbnS+EZB3cU+zOZzp/9YfTUZO2lxF NzgJoErKe/HLp7aBeJXBBcwO0LQlIT80rTZx2KihBa/Ww/y9E9gV/HacJu/Ncb6E/G3e4xGj 9w9L+UW43q01wy+FSUKy9FLc7D40WqQsj8SXZEpl84SyLcJRoX3mtj59bX2SAN2VB2BAksTu qCh00IcIUGfyHziu5PwUWYM96gOhDSocP4wSeiQ8TwLzaffllz2qhdI296a9lCIYIeWVytEd NU9jJ3RbzXAgE0pnDauNXDaQv1FS5jYi8rlslJUxKnrS69BFNjM5RqQ16Cm0C4rKL7/a8wHC r4VjcjSCM8Lzv8YOOitJ9Yt4Y8SVfO5s3YvxcdSr56nX0W3B1kGbG1GpqWTzOgXzGF5bIsbV 7SPecwUs9ShvmLmZzDUxIQ68n4zj3lMZn5I+pP+Ew6nAAiuSmKdr5cygnCH/NVJzil07t+X4 uR6oKHBhuMFYF1c6Wxk36m+EZz5ZHFaT4rN0WDIJdAEqRzD0Z56V6ansDF8y+ksh0SHlABEB AAGJAiUEGAEIAA8FAlriroICGwwFCQlmAYAACgkQrbl/X+ubfC50rhAAloTaq/fZC1gtiVtU wOB+00gEkjgmzt+rLkW+l2EySTST7tje57W83UZwzCX746B2O//Bqardxz9R1Vr0VFiwHA8g 3qeBqPqiv1WoQch/iZ5d/1MxK4A9xDag1uyqLR8RuGlZ8lATmcP3IabKiuiBV4MlFZ7V2Ib6 5ToPf28xxSyjMzTjQObIG0e009uHlu2z+iQVshLyoyVVAOWWa88D6iuBDC/EtBRjlpjLAjuR YhWVYX6KHdVUijKMHN2RqjpX5O2wPL7NcMY/wsTq7EteUeI75hxFvargRXkEt1XR8t52LC0u IE2OjpzY5re/ROUbfsqL8trjAOrSJ+Fx5H8AYl9JaoVxohhxDZgNtgNtPbh/8Nnlf9daj/bh lZcTBO98XLQwMnyHGPdyhIodpWPq2C09Ys3TkQsbcdMMB1pqnEK5Vz1zIKkEEX7QVsLdrz7C 2CFsauc/9PHj+4njCHslXtzBOiVu5FXTnbCwPrLJs5iEUkUCb6qtE/2mSCTrAanzOTTOmqiM cnNTI1Tj0ht462S9VypppQnKCv8shGxXG7BadZTv+pNCA/WfB2kk1sS3ZwB0wBWX4p41fxs+ ArM9ew2SzQ/vBrEfO7ljPfZZmBqH4t/vgAZBnOtTxCGlPEIJqiMqtGHRqIqpiR20QfxEUuXI MfMfa9QJpisdNmqoUyc=
Message-ID: <e8d8627a-c224-3ed9-7fed-fc573c97fee6@cis-india.org>
Date: Mon, 15 Feb 2021 18:56:55 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com>
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: 8b6eb5f77c3a90e840792aa3f958687a
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/7vxzXVmK7h6cdgVVZFJNvqXCTBo>
Subject: Re: [hrpc] comments on draft 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, 15 Feb 2021 13:27:21 -0000

Prof. Braman,

Thanks for your detailed feedback.

Apologies for the silence on the list: just a note that we are working
on pushing a major update based on your comments and the suggestions
from Bill Woodcock, Corinne and others.

Will send a response to all the comments with the update as well.

Thank you.
-Gurshabad

On 2/12/21 4:55 AM, Sandra Braman wrote:
> Folks --=C2=A0
>=20
> Following are some comments on draft guidelines, some of which echo
> points already made on this list. If I've misunderstood anything, pleas=
e
> let me know.=C2=A0 Some of the comments are analytical.=C2=A0 Others ar=
e
> recommendations that may make the document more effective.=C2=A0 Again,
> thanks to the authors and those who provided feedback and input to the
> authors for all the labor put in.
>=20
> Sandra Braman
>=20
> ----------------------------------------------------------
>=20
> _Human Rights_
>=20
> Graph 2 on page 4 identifies key sources of human rights.=C2=A0 The man=
ner of
> presentation conflates documents from sources that are importantly
> different regarding their source and, thus, relative weight.=C2=A0 A do=
cument
> created by the Internet Governance Forum -- a talk shop only that has n=
o
> status within the international legal system on its own -- with United
> Nations treaties.=C2=A0 This section of the document will be much stron=
ger if
> separate paragraphs discuss actual legal foundations for human rights
> and other sources of proposals for things that should be considered
> human rights in the Internet environment (the latter would include Hill
> 2014, too, for example).=C2=A0 The IGF document is certainly pertinent,=
 but
> should be discussed in the manner one would discuss the scholarly
> literature and "gray matter" (reports from advocacy groups and
> non-profit organizations, etc.), not as if it were international law.
>=20
> Which human rights will be discussed in this document should be clearly
> articulated in the opening section, with definitions for the purposes o=
f
> this document and the sources of those rights, and then used
> consistently throughout the document.=C2=A0 Late in the document the "r=
ight
> to security" shows up; is this a rephrasing of Article 28 of the
> Universal Declaration on Human Rights, or something else that is not
> mentioned on page 4?
>=20
> Theoretically and operationally defining each concept presented as a
> human right more thoroughly will be important.=C2=A0 There is confusion=
 in
> this document, for example, between the right to access government
> information, which is included in a number of constitutions and
> constitution-like documents around the world and is considered essentia=
l
> to the ability to hold governments accountable for their action, and a
> right to access information in general (more typically considered
> necessary to freedom of expression, since in order to talk about
> something you have to have information about it).
>=20
> What arguments justify which two or three human rights of concern for
> each item in section 3.3?=C2=A0 As presented in this draft, it seems
> essentially random in a manner that is not persuasive regarding what is
> in and what is out.
>=20
> _Direct vs Indirect Violations of Human Rights_
> _
> _
> Perhaps the most interesting thread running through this document is th=
e
> implicit suggestion that impediments to technological innovation can
> themselves be understood as violations of human rights.=C2=A0 (Fully
> developing that argument would make a great scholarly journal article!)=
=C2=A0
> I buy that argument, as innovations are often/may well be needed to
> develop work-arounds for exercises of power that violate human rights i=
n
> traditionally understood ways, but this piece will be much more
> effective and stronger if it makes that argument explicit and uses it a=
s
> a tool in the structuring of the narrative.
>=20
> The suggestions are two:=C2=A0 (1) Add an explicit discussion of the
> distinction between direct violations of human rights (e.g., censorship=
)
> and indirect violations of human rights (e.g., innovation, which
> includes matters such as "adaptability" as introduced in this draft).
> (2) Structure the discussion of topics in Section 3.3 to clearly
> distinguish between the two.=C2=A0 A recommendation for an alternative
> structuring of those topics can be found below.
>=20
> Another distinction that could usefully be introduced in this document
> is the difference between short-term and long-term effects on human
> rights.=C2=A0 Censorship is a short-term, immediate effect.=C2=A0 Diffe=
rential
> ability to access information about one's environment and that provides
> the affordances for effective political action -- what was first
> labelled "the knowledge gap" in the 1970s and is now more commonly
> referred to as "the digital divide" -- is better understood as a
> long-term effect on human rights.
>=20
> _Stages of the Internet Design Process and the Institutional Context_
> _
> _
> This draft mentions that different human rights issues come up at
> different stages of the protocol development process.=C2=A0 It also ask=
s for
> a lot of types of research and thinking that, as others have pointed
> out, are not generally within the job description of those working on
> Internet protocols and for which they may not have been trained -- thes=
e
> are actually matters of organizational design.=C2=A0 This document woul=
d be
> much stronger if it unbundled each of these things.
>=20
> For stages of the protocol design process, please say more about which
> issues should be considered when?=C2=A0 Doing so would require offering=
 a
> model of the stages of the protocol design process.=C2=A0 It would be g=
reat
> to have a section that does that and that then specifies which issues
> would be of concern when.=C2=A0 The authors will probably want to inclu=
de
> "implementation" among the stages discussed.
>=20
> On the organizational design side, the document would be stronger if it
> offered at least a model of what an organizational structure might be
> that would include all of the different kinds of expertise required to
> do the work asked for here, along with a mapping of the work flow acros=
s
> employees with different types of expertise.
>=20
> _Research on the Effects of Design Decisions_
> _
> _
> A recurring problem in research on communication and the media is
> confusing what can be learned from research on an actual text or set of
> visuals and the effects of that text or visuals on those who receive
> it.=C2=A0 In that context, textual analysis can only tell the researche=
r what
> is in the text; for effects research, quite other research methods must
> be used.=C2=A0 The same problem runs throughout this document.=C2=A0 Th=
e authors
> are encouraged to clearly distinguish the features of a protocol itself=
,
> how the protocol operates within the network (the technical "context" i=
n
> the sense of how it interacts with other protocols), how it is used in
> the application layer, how applications are used, and the effects of th=
e
> uses of those applications.=C2=A0 A second issue raised by the methods
> introduced here is that they run the danger of being limited to "lookin=
g
> under the streetlight" (the familiar story about where a drunk is
> looking for keys, irrespective of where they may be), although in terms
> of provenance that problem may be more reflective of the fact that the
> full scholarly literature and what can be learned from researchers
> outside of the HRPC have not yet been brought to bear.
>=20
> Different research methods will be needed to examine each of these.=C2=A0
> This document would be much stronger if it broke out which of the kinds
> of questions raised can actually be the subjects of research at each
> stage of this sequence, too.=C2=A0 The mixing of application layer and =
use
> issues with protocol design in my view undermines the effectiveness of
> the argument this reader, at least, understands the authors to be tryin=
g
> to make.=C2=A0
>=20
> Research on designer perceptions of possible human rights risks can be
> useful and interesting (I've done some of that research myself), but
> does not tell the researcher anything about the actual risks as
> experienced or as understood by social scientists who have studied thos=
e
> effects on the ground. There are, however, several significant bodies o=
f
> research that the authors could mine for more empirical detail on the
> effects of specific protocol design features rather than assuming that
> universe is bounded by what one or a few members of HRPC have done or
> asking computer scientists and electrical engineers to undertake all of
> that work.=C2=A0 It is incredibly important to keep human rights issues=
 in
> front of those doing technical work, including regularly showing up in
> IETF meetings to alert those designing protocols to specific issues, bu=
t
> for research on the effects of those protocols HRPC should be turning t=
o
> social scientists who are actually studying the effects and who could b=
e
> encouraged to go further in this area, sometimes -- so valuably -- in
> collaboration with technical experts who have given themselves to this
> specific task.=C2=A0 In this regard, the work of Ron Deibert's group at=
 the
> University of Toronto (Citizen Lab) should be highlighted as a model
> (https://citizenlab.ca/).=C2=A0 Work in fields such as anthropology,
> sociology, political science, information science, communication, STS
> (studies of technology and society), and economics will all be useful.
>=20
> To date the HRPC (to my knowledge) has largely engaged with the
> communities of researchers working in this area by bringing individuals
> to IETF meetings for short presentations.=C2=A0 Given the relatively sm=
all
> number of people active within HRPC who come from social science
> backgrounds and limits on the time of everyone within HRPC, some
> assistance may be needed to take advantage of the many additional
> research methods that should be used to evaluate the effects of protoco=
l
> design on human rights as well as to incorporate findings from research
> in this area already conducted into this document.=C2=A0 A few thoughts
> regarding how that might be done will be offered in a separate email.
>=20
> However it is done, going much further with research methods will
> significantly increase the sophistication and utility of this document.=
=C2=A0
> As it currently stands, the section on "expert interviews" is confusing
> because it appears to be asking computer scientists to be expert on
> social science matters, for example.=C2=A0 Interviews with various type=
s of
> experts will indeed be among the kinds of methods that can be useful,
> but the different types of expertise involved should be acknowledged an=
d
> different kinds of questions would be asked of different kinds of exper=
ts.
>=20
> _Grouping of Section 3.3 Topics_
> _
> _
> Three dimensions of analysis could be used to better structure the
> sequencing of topics in Section 3.3.=C2=A0 The suggestion here is to us=
e the
> focus of attention as the highest level used to group related issues
> together, and then discuss differences between direct and indirect
> effects and between short-term and long-term effects within each of the
> categories.=C2=A0 A suggestion what the top-level of categorization mig=
ht
> look like is offered here, with the current number of the topics to be
> included within it.=C2=A0 Because some of the current topics combine ty=
pes of
> issues, the final category includes one item that in my view should be
> unbundled for clarification for the purposes of this document and three
> items that in my view should be deleted.=C2=A0 The following section
> discusses individual topics and/or the combinations suggested here.=C2=A0
>=20
> /Network Operations/
> /
> /
> Connectivity (3.3.1)
> Internationalization (3.3.5)
> Localization (3.3.11)
> Adaptability (3.3.17)
>=20
> Open Standards (3.3.7)
> Heterogeneity Support (3.3.8)
>=20
> Decentralization (3.3.12)
>=20
> Reliability (3.3.13)
>=20
> /The Individual User/
> /
> /
> Privacy (3.3.2)
> Pseudonymity (3.3.9)
> Confidentiality (3.3.14)
> Anonymity (3.3.19)
>=20
> Accessibility (3.3.10)
>=20
> /Content/
> /
> /
> Content Agnosticism (3.3.3)
>=20
> Censorship Resistance (3.3.6)
> Integrity (3.3.15)
> Authenticity (3.3.16)
>=20
> /To Be Unbundled/
> /
> /
> Security (3.3.4)=C2=A0
>=20
> /Delete/
>=20
> Outcome Transparency (3.3.18)
> Remedy and Attribution (3.3.20)
> Miscellaneous Considerations (3.3.21)
> /
> /
> _Discussion of Topics and Topic Groupings_
> _
> _
> /Network Operations/
> /
> /
> Decentralization is separated out because the extent to which
> decentralization can occur operates at so many different levels of the
> structures involved -- the network, applications, the social structure,
> and political structure -- that it is different in kind from the first =
5
> items above that seem to me (as someone who is NOT a technical expert)
> to be related to each other.=C2=A0 Reliability also seems to me to be
> different in kind.
>=20
> In the scholarly journal article "The Framing Years," the concept of
> "technological democracy" as a key design principle for the Internet wa=
s
> introduced.=C2=A0 The topics of Open Standards and Heterogeneity additi=
onally
> can be distinguished by this feature.
>=20
> The Decentralization topic mixes several different types of control fro=
m
> diverse sources (governments, protocol limits, etc.) together without
> distinguishing them.=C2=A0 The document will be stronger, clearer, and =
more
> useful if it distinguishes them.
>=20
> In the scholarly journal article "The Geopolitical and the Network
> Political:=C2=A0 Internet Designers and Governance," the tension betwee=
n
> geopolitical citizenship (allegiance to one's identity as a citizen of =
a
> geopolitically recognized state -- a government recognized by the UN)
> and network citizenship (allegiance to one's identity as a user/citizen
> of the Internet, the success of which is critical to the user) is
> explored.=C2=A0 There are often instances in which what is required of =
the
> geopolitical citizen is the opposite of what is required of the network
> citizen.=C2=A0 That is the tension discussed on page 17, graph 2.
>=20
> /The Individual User/
>=20
> All of the topics related to the diverse dimensions of personal privacy
> should be grouped together.=C2=A0 They would be best introduced with a
> general introduction to RFC 4949.=C2=A0 Doing so would then facilitate
> further analysis of what might differently be needed to attend to when
> thinking about each of the concepts distinguished there (if there are
> differences).
>=20
> Accessibility is different in kind as a topic.=C2=A0 However, the RFC
> referred to in that discussion, as I understand it, actually refers to
> technical limits and/or limits of access to images that may be in place
> because of a particular tool a specific individual chooses to use, not
> to human disability.=C2=A0 Is there anything else that deals with human
> disability at the protocol level that can be called upon here more
> validly?=C2=A0 Most of what I am aware of is at the application level.
>=20
> /Content/
>=20
> Content agnosticism is a tough one for two reasons.=C2=A0 First, any de=
cision
> about structure made by definition will preference some content or user=
s
> (and thus those users' content) over others -- for any door that is
> opened, another door is shut.=C2=A0 By the close of the 1990s (the peri=
od
> through which my own research went), several different models were
> experimented with to achieve "fair queuing," and struggles with "qualit=
y
> of service" have continued since.=C2=A0 What is said here about content
> agnosticism should reference all of that history and make specific
> recommendations if it sees a way out of this dilemma that others have
> not yet been able to discover.=C2=A0 Second, national governments are a=
lways
> going to assert priority access.=C2=A0 It is wishful thinking only to b=
elieve
> that would be otherwise.=C2=A0 The fix here for this document would be =
to
> simply acknowledge that.
>=20
> In the discussion of Authenticity, isn't there another scenario when
> considering authentication?=C2=A0 This would add another line to the la=
st
> scenario provided:=C2=A0 Bob knows who or what altered the data that di=
d not
> come from Alice.=C2=A0 Why should this not also be a requirement?=C2=A0
> Surveillance should go both ways (that is why we have access to
> government information as a fundamental constitutional principle).
>=20
> /To be Unbundled/
> /
> /
> The existing topic of "security" includes elements that would, in my
> view, be more strongly included if they were unbundled, with elements
> dispersed into the above categories to join those that are like of kind=
.
>=20
> /To be Deleted/
> /
> /
> Outcome Transparency -- This is a reasonable expectation only if every
> organization employing those involved in the protocol design process
> were to take up recommendations these authors have yet to develop for
> organizational structure and work flow processes adequate to the range
> of kinds of research being asked for here.=C2=A0 Since it is unlikely t=
hat
> those recommendations for organizational structure and work flow
> processes, will be forthcoming within the probable life cycle of the
> writing of this document, and since it is even more unlikely that all o=
f
> the organizations involved would follow such recommendations if offered=
,
> in my view it would strengthen the document by deleting this item.=C2=A0
> Doing so would be a defensive writing gesture warding off critiques of
> naivete.
>=20
> Remedy and Attribution -- Others have made excellent points on this
> matter on the listserv.=C2=A0 Everything that would be pertinent here s=
hould
> be covered by the topics introduced that apply to individual users.=C2=A0=
 If
> that is not the case, the authors need to make clear what else would be
> involved.=C2=A0 Delete as a topic but add to the discussion that introd=
uces
> the document.
>=20
> Miscellaneous Considerations -- Don't see what this obvious point adds.
>=20
> _Other Conceptual Issues_
> _
> _
> How do the authors distinguish between the effects of protocol-shaped
> communications between humans, between humans and non-humans, and
> between non-humans from a human rights perspective?=C2=A0 Protocol desi=
gn
> features that impede the ability to make effective use of what is
> learned from environmental sensors, for example, could generage
> long-term human rights impacts.=C2=A0 Not mentioned at all here but it =
would
> be a stronger document if it were.
>=20
> Page 6, graph 4 (in 3.3) -- What is meant by "misapplication of the
> protocol or technology"?=C2=A0 That is really two questions in one.=C2=A0=
 First,
> how do the authors distinguish an appropriate application from a
> misapplication?=C2=A0 Second, as again has been brought up in discussio=
n of
> this draft on the list, isn't this about users and not the protocol
> design that is the focus of the document?=C2=A0 Those involved with att=
empts
> to prevent uses of dual use technologies for purposes of war rather tha=
n
> peace have struggled with this for decades; the inability to
> meaningfully, defensibly, and effectively grab ahold of it has
> essentially led to the abandonment of the effort.
>=20
> How do the authors evaluate the "adequacy" with which a given protocol
> takes human rights into account?=C2=A0 (page 6, graph 5)
>=20
> The question of whether or not protocols need to be understandable by
> humans is one of the most amusing elements of discussion in the RFCs
> during their first decade (1969-1979) (again, an article available if o=
f
> interest).=C2=A0 In 3.3.5, on internationalization (p. 9, second graph =
from
> bottom), the question is about text strings that "have to be" understoo=
d
> or entered by humans.=C2=A0 What about situations in which the more acc=
urate
> verb would be "can be"?
>=20
> Re Internationalization -- See my comments on draft association re the
> language issue.
>=20
> In areas such as degradation, the distinction should be drawn between
> degradation and knowledge of degradation.=C2=A0 That is also true for
> integrity and in other areas that can, under some circumstances, also
> include even censorship.
>=20
> _Writing Issues_
> _
> _
> 3.2.1 -- This paragraph is opaque.
>=20
> 3.2.2 -- This paragraph is tautological.
>=20
> 3.3.2 -- Page 8, graph 3 -- The document on privacy is not an "example.=
"
>=20
> 3.3.20 -- Page 23, graph 1 -- The reference to Kaye's thinking on
> freedom of expression and the Internet belongs in the discussion of
> human rights principles, not here.
>=20
> There are a number of typographical and grammar errors throughout.
>=20
> =C2=A0
>=20
>=20
> _
> _
>=20
> _
> _
>=20
> _
> _
>=20
>=20
> _
> _
> _
> _
>=20
>=20
>=20
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>=20


From nobody Mon Feb 15 07:18:46 2021
Return-Path: <braman@tamu.edu>
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 241333A0C43 for <hrpc@ietfa.amsl.com>; Mon, 15 Feb 2021 07:18:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 NUbI_4oXXzlP for <hrpc@ietfa.amsl.com>; Mon, 15 Feb 2021 07:18:39 -0800 (PST)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 D94FA3A0C36 for <hrpc@irtf.org>; Mon, 15 Feb 2021 07:18:28 -0800 (PST)
Received: by mail-io1-xd29.google.com with SMTP id u8so7051799ior.13 for <hrpc@irtf.org>; Mon, 15 Feb 2021 07:18:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ECx9LhPzyiLFzWs2GUdyud9EEIN+CMcakhWvRbMUol4=; b=jebMF9krss1ikk0ihR4ajgbe8lxL/rLR8aYyfEwronUkMvwIezB80w7vpGuMdOFhxn vn9NTGVOsBS3B+IuoBZejrM66gT5rDiBAnCeCiQoZMdxglGeo3FXc5INIckfLN4epuKA NF+ZC91sBovRVnMBeuXDHzLiAM8j5LHU+fb8IDOJevLdWF/WYmLLAmyAgPrGIqxcdSkk R2+wreXnfevWE3VbKIDlJme6MFiBJm0NpVLynw9jxTgDGcHym4zLv5FoimBWaxyW3Nn5 OE+AL0nAOqurelJt90yQASL9HH1t1ZoYA+KT4mcovMQ6UcfncswvKH5TMbsvNc2yiOlG mwiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ECx9LhPzyiLFzWs2GUdyud9EEIN+CMcakhWvRbMUol4=; b=Pp1NG1LqLU1jfuqEFdMqUs/9Ckjik+PlS/mi3AEoonA4Vk9vosC4pBO3qKQlqLD4w8 T1XXjjF/h5M9BYT50yEm7xPKTo3R93gUNuB5g8lkTsBvLqC++78yVs4iALT8gxahSu/t gR1oSKD36eNid6LxQ8SMDs1oXvLgGpb/wETfRok+RoX9//n+h/7/YwL+Q3ahoNH0pXSr wsu6EXBPMl6HPoXyPmZyH7/R7C6gjqifxA+OUVM2iPsmvqKLgYhSrNq1v15gKuNH3UXd /z209yn2aYXARh5TnWpfVrgMDQpDiyqdZEHzUxdDhbJ/a7B6h8sySpGtGWkhu7z7pzvc 2fEQ==
X-Gm-Message-State: AOAM533nR+gkhaCnknoOCn1F8ESnx/7YA8KwrU015INAjuZXw+uWeGYG lgKmmI1llcV2tfwSYZ6dGD9i7eJI2GN7il8ETT6AsA==
X-Google-Smtp-Source: ABdhPJyWja9FWpTtHRx6ogVIVSkxRORNdDOFZyZIzf8wefv2T2NcCeOafDyZbzqqjzv+Nt6DUdM+k3Vr48+CGUt64zI=
X-Received: by 2002:a05:6602:24cb:: with SMTP id h11mr13433509ioe.79.1613402307347;  Mon, 15 Feb 2021 07:18:27 -0800 (PST)
MIME-Version: 1.0
References: <CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com> <e8d8627a-c224-3ed9-7fed-fc573c97fee6@cis-india.org>
In-Reply-To: <e8d8627a-c224-3ed9-7fed-fc573c97fee6@cis-india.org>
From: Sandra Braman <braman@tamu.edu>
Date: Mon, 15 Feb 2021 09:18:16 -0600
Message-ID: <CAB2unbMYZzf_HbnPSA4OYpRU20Uz+-Tsyon088m8jEbxAVWqxg@mail.gmail.com>
To: Gurshabad Grover <gurshabad@cis-india.org>
Cc: Bill Woodcock <woody@pch.net>, Corinne Cath <corinnecath@gmail.com>, hrpc@irtf.org
Content-Type: multipart/alternative; boundary="00000000000068e17605bb617f7e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/h_KMde9dARk9FXV6Ksaz1dX21AM>
Subject: Re: [hrpc] comments on draft 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, 15 Feb 2021 15:18:44 -0000

--00000000000068e17605bb617f7e
Content-Type: text/plain; charset="UTF-8"

Thanks for letting me know.  Will your response to comments include those
that came from Corinne, Bill, and others as well, so we can all understand
the arguments, corrections, additional points, etc., to which the new draft
is responding, since (unless I have missed it), these have not all been
shared with the list yet?

On Mon, Feb 15, 2021 at 7:27 AM Gurshabad Grover <gurshabad@cis-india.org>
wrote:

> Prof. Braman,
>
> Thanks for your detailed feedback.
>
> Apologies for the silence on the list: just a note that we are working
> on pushing a major update based on your comments and the suggestions
> from Bill Woodcock, Corinne and others.
>
> Will send a response to all the comments with the update as well.
>
> Thank you.
> -Gurshabad
>
> On 2/12/21 4:55 AM, Sandra Braman wrote:
> > Folks --
> >
> > Following are some comments on draft guidelines, some of which echo
> > points already made on this list. If I've misunderstood anything, please
> > let me know.  Some of the comments are analytical.  Others are
> > recommendations that may make the document more effective.  Again,
> > thanks to the authors and those who provided feedback and input to the
> > authors for all the labor put in.
> >
> > Sandra Braman
> >
> > ----------------------------------------------------------
> >
> > _Human Rights_
> >
> > Graph 2 on page 4 identifies key sources of human rights.  The manner of
> > presentation conflates documents from sources that are importantly
> > different regarding their source and, thus, relative weight.  A document
> > created by the Internet Governance Forum -- a talk shop only that has no
> > status within the international legal system on its own -- with United
> > Nations treaties.  This section of the document will be much stronger if
> > separate paragraphs discuss actual legal foundations for human rights
> > and other sources of proposals for things that should be considered
> > human rights in the Internet environment (the latter would include Hill
> > 2014, too, for example).  The IGF document is certainly pertinent, but
> > should be discussed in the manner one would discuss the scholarly
> > literature and "gray matter" (reports from advocacy groups and
> > non-profit organizations, etc.), not as if it were international law.
> >
> > Which human rights will be discussed in this document should be clearly
> > articulated in the opening section, with definitions for the purposes of
> > this document and the sources of those rights, and then used
> > consistently throughout the document.  Late in the document the "right
> > to security" shows up; is this a rephrasing of Article 28 of the
> > Universal Declaration on Human Rights, or something else that is not
> > mentioned on page 4?
> >
> > Theoretically and operationally defining each concept presented as a
> > human right more thoroughly will be important.  There is confusion in
> > this document, for example, between the right to access government
> > information, which is included in a number of constitutions and
> > constitution-like documents around the world and is considered essential
> > to the ability to hold governments accountable for their action, and a
> > right to access information in general (more typically considered
> > necessary to freedom of expression, since in order to talk about
> > something you have to have information about it).
> >
> > What arguments justify which two or three human rights of concern for
> > each item in section 3.3?  As presented in this draft, it seems
> > essentially random in a manner that is not persuasive regarding what is
> > in and what is out.
> >
> > _Direct vs Indirect Violations of Human Rights_
> > _
> > _
> > Perhaps the most interesting thread running through this document is the
> > implicit suggestion that impediments to technological innovation can
> > themselves be understood as violations of human rights.  (Fully
> > developing that argument would make a great scholarly journal article!)
> > I buy that argument, as innovations are often/may well be needed to
> > develop work-arounds for exercises of power that violate human rights in
> > traditionally understood ways, but this piece will be much more
> > effective and stronger if it makes that argument explicit and uses it as
> > a tool in the structuring of the narrative.
> >
> > The suggestions are two:  (1) Add an explicit discussion of the
> > distinction between direct violations of human rights (e.g., censorship)
> > and indirect violations of human rights (e.g., innovation, which
> > includes matters such as "adaptability" as introduced in this draft).
> > (2) Structure the discussion of topics in Section 3.3 to clearly
> > distinguish between the two.  A recommendation for an alternative
> > structuring of those topics can be found below.
> >
> > Another distinction that could usefully be introduced in this document
> > is the difference between short-term and long-term effects on human
> > rights.  Censorship is a short-term, immediate effect.  Differential
> > ability to access information about one's environment and that provides
> > the affordances for effective political action -- what was first
> > labelled "the knowledge gap" in the 1970s and is now more commonly
> > referred to as "the digital divide" -- is better understood as a
> > long-term effect on human rights.
> >
> > _Stages of the Internet Design Process and the Institutional Context_
> > _
> > _
> > This draft mentions that different human rights issues come up at
> > different stages of the protocol development process.  It also asks for
> > a lot of types of research and thinking that, as others have pointed
> > out, are not generally within the job description of those working on
> > Internet protocols and for which they may not have been trained -- these
> > are actually matters of organizational design.  This document would be
> > much stronger if it unbundled each of these things.
> >
> > For stages of the protocol design process, please say more about which
> > issues should be considered when?  Doing so would require offering a
> > model of the stages of the protocol design process.  It would be great
> > to have a section that does that and that then specifies which issues
> > would be of concern when.  The authors will probably want to include
> > "implementation" among the stages discussed.
> >
> > On the organizational design side, the document would be stronger if it
> > offered at least a model of what an organizational structure might be
> > that would include all of the different kinds of expertise required to
> > do the work asked for here, along with a mapping of the work flow across
> > employees with different types of expertise.
> >
> > _Research on the Effects of Design Decisions_
> > _
> > _
> > A recurring problem in research on communication and the media is
> > confusing what can be learned from research on an actual text or set of
> > visuals and the effects of that text or visuals on those who receive
> > it.  In that context, textual analysis can only tell the researcher what
> > is in the text; for effects research, quite other research methods must
> > be used.  The same problem runs throughout this document.  The authors
> > are encouraged to clearly distinguish the features of a protocol itself,
> > how the protocol operates within the network (the technical "context" in
> > the sense of how it interacts with other protocols), how it is used in
> > the application layer, how applications are used, and the effects of the
> > uses of those applications.  A second issue raised by the methods
> > introduced here is that they run the danger of being limited to "looking
> > under the streetlight" (the familiar story about where a drunk is
> > looking for keys, irrespective of where they may be), although in terms
> > of provenance that problem may be more reflective of the fact that the
> > full scholarly literature and what can be learned from researchers
> > outside of the HRPC have not yet been brought to bear.
> >
> > Different research methods will be needed to examine each of these.
> > This document would be much stronger if it broke out which of the kinds
> > of questions raised can actually be the subjects of research at each
> > stage of this sequence, too.  The mixing of application layer and use
> > issues with protocol design in my view undermines the effectiveness of
> > the argument this reader, at least, understands the authors to be trying
> > to make.
> >
> > Research on designer perceptions of possible human rights risks can be
> > useful and interesting (I've done some of that research myself), but
> > does not tell the researcher anything about the actual risks as
> > experienced or as understood by social scientists who have studied those
> > effects on the ground. There are, however, several significant bodies of
> > research that the authors could mine for more empirical detail on the
> > effects of specific protocol design features rather than assuming that
> > universe is bounded by what one or a few members of HRPC have done or
> > asking computer scientists and electrical engineers to undertake all of
> > that work.  It is incredibly important to keep human rights issues in
> > front of those doing technical work, including regularly showing up in
> > IETF meetings to alert those designing protocols to specific issues, but
> > for research on the effects of those protocols HRPC should be turning to
> > social scientists who are actually studying the effects and who could be
> > encouraged to go further in this area, sometimes -- so valuably -- in
> > collaboration with technical experts who have given themselves to this
> > specific task.  In this regard, the work of Ron Deibert's group at the
> > University of Toronto (Citizen Lab) should be highlighted as a model
> > (
> https://urldefense.com/v3/__https://citizenlab.ca/__;!!KwNVnqRv!RUZdCcJt8Ap1Rd6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLLyDMfrrza9gzw$
> ).  Work in fields such as anthropology,
> > sociology, political science, information science, communication, STS
> > (studies of technology and society), and economics will all be useful.
> >
> > To date the HRPC (to my knowledge) has largely engaged with the
> > communities of researchers working in this area by bringing individuals
> > to IETF meetings for short presentations.  Given the relatively small
> > number of people active within HRPC who come from social science
> > backgrounds and limits on the time of everyone within HRPC, some
> > assistance may be needed to take advantage of the many additional
> > research methods that should be used to evaluate the effects of protocol
> > design on human rights as well as to incorporate findings from research
> > in this area already conducted into this document.  A few thoughts
> > regarding how that might be done will be offered in a separate email.
> >
> > However it is done, going much further with research methods will
> > significantly increase the sophistication and utility of this document.
> > As it currently stands, the section on "expert interviews" is confusing
> > because it appears to be asking computer scientists to be expert on
> > social science matters, for example.  Interviews with various types of
> > experts will indeed be among the kinds of methods that can be useful,
> > but the different types of expertise involved should be acknowledged and
> > different kinds of questions would be asked of different kinds of
> experts.
> >
> > _Grouping of Section 3.3 Topics_
> > _
> > _
> > Three dimensions of analysis could be used to better structure the
> > sequencing of topics in Section 3.3.  The suggestion here is to use the
> > focus of attention as the highest level used to group related issues
> > together, and then discuss differences between direct and indirect
> > effects and between short-term and long-term effects within each of the
> > categories.  A suggestion what the top-level of categorization might
> > look like is offered here, with the current number of the topics to be
> > included within it.  Because some of the current topics combine types of
> > issues, the final category includes one item that in my view should be
> > unbundled for clarification for the purposes of this document and three
> > items that in my view should be deleted.  The following section
> > discusses individual topics and/or the combinations suggested here.
> >
> > /Network Operations/
> > /
> > /
> > Connectivity (3.3.1)
> > Internationalization (3.3.5)
> > Localization (3.3.11)
> > Adaptability (3.3.17)
> >
> > Open Standards (3.3.7)
> > Heterogeneity Support (3.3.8)
> >
> > Decentralization (3.3.12)
> >
> > Reliability (3.3.13)
> >
> > /The Individual User/
> > /
> > /
> > Privacy (3.3.2)
> > Pseudonymity (3.3.9)
> > Confidentiality (3.3.14)
> > Anonymity (3.3.19)
> >
> > Accessibility (3.3.10)
> >
> > /Content/
> > /
> > /
> > Content Agnosticism (3.3.3)
> >
> > Censorship Resistance (3.3.6)
> > Integrity (3.3.15)
> > Authenticity (3.3.16)
> >
> > /To Be Unbundled/
> > /
> > /
> > Security (3.3.4)
> >
> > /Delete/
> >
> > Outcome Transparency (3.3.18)
> > Remedy and Attribution (3.3.20)
> > Miscellaneous Considerations (3.3.21)
> > /
> > /
> > _Discussion of Topics and Topic Groupings_
> > _
> > _
> > /Network Operations/
> > /
> > /
> > Decentralization is separated out because the extent to which
> > decentralization can occur operates at so many different levels of the
> > structures involved -- the network, applications, the social structure,
> > and political structure -- that it is different in kind from the first 5
> > items above that seem to me (as someone who is NOT a technical expert)
> > to be related to each other.  Reliability also seems to me to be
> > different in kind.
> >
> > In the scholarly journal article "The Framing Years," the concept of
> > "technological democracy" as a key design principle for the Internet was
> > introduced.  The topics of Open Standards and Heterogeneity additionally
> > can be distinguished by this feature.
> >
> > The Decentralization topic mixes several different types of control from
> > diverse sources (governments, protocol limits, etc.) together without
> > distinguishing them.  The document will be stronger, clearer, and more
> > useful if it distinguishes them.
> >
> > In the scholarly journal article "The Geopolitical and the Network
> > Political:  Internet Designers and Governance," the tension between
> > geopolitical citizenship (allegiance to one's identity as a citizen of a
> > geopolitically recognized state -- a government recognized by the UN)
> > and network citizenship (allegiance to one's identity as a user/citizen
> > of the Internet, the success of which is critical to the user) is
> > explored.  There are often instances in which what is required of the
> > geopolitical citizen is the opposite of what is required of the network
> > citizen.  That is the tension discussed on page 17, graph 2.
> >
> > /The Individual User/
> >
> > All of the topics related to the diverse dimensions of personal privacy
> > should be grouped together.  They would be best introduced with a
> > general introduction to RFC 4949.  Doing so would then facilitate
> > further analysis of what might differently be needed to attend to when
> > thinking about each of the concepts distinguished there (if there are
> > differences).
> >
> > Accessibility is different in kind as a topic.  However, the RFC
> > referred to in that discussion, as I understand it, actually refers to
> > technical limits and/or limits of access to images that may be in place
> > because of a particular tool a specific individual chooses to use, not
> > to human disability.  Is there anything else that deals with human
> > disability at the protocol level that can be called upon here more
> > validly?  Most of what I am aware of is at the application level.
> >
> > /Content/
> >
> > Content agnosticism is a tough one for two reasons.  First, any decision
> > about structure made by definition will preference some content or users
> > (and thus those users' content) over others -- for any door that is
> > opened, another door is shut.  By the close of the 1990s (the period
> > through which my own research went), several different models were
> > experimented with to achieve "fair queuing," and struggles with "quality
> > of service" have continued since.  What is said here about content
> > agnosticism should reference all of that history and make specific
> > recommendations if it sees a way out of this dilemma that others have
> > not yet been able to discover.  Second, national governments are always
> > going to assert priority access.  It is wishful thinking only to believe
> > that would be otherwise.  The fix here for this document would be to
> > simply acknowledge that.
> >
> > In the discussion of Authenticity, isn't there another scenario when
> > considering authentication?  This would add another line to the last
> > scenario provided:  Bob knows who or what altered the data that did not
> > come from Alice.  Why should this not also be a requirement?
> > Surveillance should go both ways (that is why we have access to
> > government information as a fundamental constitutional principle).
> >
> > /To be Unbundled/
> > /
> > /
> > The existing topic of "security" includes elements that would, in my
> > view, be more strongly included if they were unbundled, with elements
> > dispersed into the above categories to join those that are like of kind.
> >
> > /To be Deleted/
> > /
> > /
> > Outcome Transparency -- This is a reasonable expectation only if every
> > organization employing those involved in the protocol design process
> > were to take up recommendations these authors have yet to develop for
> > organizational structure and work flow processes adequate to the range
> > of kinds of research being asked for here.  Since it is unlikely that
> > those recommendations for organizational structure and work flow
> > processes, will be forthcoming within the probable life cycle of the
> > writing of this document, and since it is even more unlikely that all of
> > the organizations involved would follow such recommendations if offered,
> > in my view it would strengthen the document by deleting this item.
> > Doing so would be a defensive writing gesture warding off critiques of
> > naivete.
> >
> > Remedy and Attribution -- Others have made excellent points on this
> > matter on the listserv.  Everything that would be pertinent here should
> > be covered by the topics introduced that apply to individual users.  If
> > that is not the case, the authors need to make clear what else would be
> > involved.  Delete as a topic but add to the discussion that introduces
> > the document.
> >
> > Miscellaneous Considerations -- Don't see what this obvious point adds.
> >
> > _Other Conceptual Issues_
> > _
> > _
> > How do the authors distinguish between the effects of protocol-shaped
> > communications between humans, between humans and non-humans, and
> > between non-humans from a human rights perspective?  Protocol design
> > features that impede the ability to make effective use of what is
> > learned from environmental sensors, for example, could generage
> > long-term human rights impacts.  Not mentioned at all here but it would
> > be a stronger document if it were.
> >
> > Page 6, graph 4 (in 3.3) -- What is meant by "misapplication of the
> > protocol or technology"?  That is really two questions in one.  First,
> > how do the authors distinguish an appropriate application from a
> > misapplication?  Second, as again has been brought up in discussion of
> > this draft on the list, isn't this about users and not the protocol
> > design that is the focus of the document?  Those involved with attempts
> > to prevent uses of dual use technologies for purposes of war rather than
> > peace have struggled with this for decades; the inability to
> > meaningfully, defensibly, and effectively grab ahold of it has
> > essentially led to the abandonment of the effort.
> >
> > How do the authors evaluate the "adequacy" with which a given protocol
> > takes human rights into account?  (page 6, graph 5)
> >
> > The question of whether or not protocols need to be understandable by
> > humans is one of the most amusing elements of discussion in the RFCs
> > during their first decade (1969-1979) (again, an article available if of
> > interest).  In 3.3.5, on internationalization (p. 9, second graph from
> > bottom), the question is about text strings that "have to be" understood
> > or entered by humans.  What about situations in which the more accurate
> > verb would be "can be"?
> >
> > Re Internationalization -- See my comments on draft association re the
> > language issue.
> >
> > In areas such as degradation, the distinction should be drawn between
> > degradation and knowledge of degradation.  That is also true for
> > integrity and in other areas that can, under some circumstances, also
> > include even censorship.
> >
> > _Writing Issues_
> > _
> > _
> > 3.2.1 -- This paragraph is opaque.
> >
> > 3.2.2 -- This paragraph is tautological.
> >
> > 3.3.2 -- Page 8, graph 3 -- The document on privacy is not an "example."
> >
> > 3.3.20 -- Page 23, graph 1 -- The reference to Kaye's thinking on
> > freedom of expression and the Internet belongs in the discussion of
> > human rights principles, not here.
> >
> > There are a number of typographical and grammar errors throughout.
> >
> >
> >
> >
> > _
> > _
> >
> > _
> > _
> >
> > _
> > _
> >
> >
> > _
> > _
> > _
> > _
> >
> >
> >
> > _______________________________________________
> > hrpc mailing list
> > hrpc@irtf.org
> >
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!RUZdCcJt8Ap1Rd6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLLyDMfrZoGjVnA$
> >
>

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

<div><div dir=3D"auto">Thanks for letting me know.=C2=A0 Will your response=
 to comments include those that came from Corinne, Bill, and others as well=
, so we can all understand the arguments, corrections, additional points, e=
tc., to which the new draft is responding, since (unless I have missed it),=
 these have not all been shared with the list yet?</div></div><div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 15=
, 2021 at 7:27 AM Gurshabad Grover &lt;<a href=3D"mailto:gurshabad@cis-indi=
a.org">gurshabad@cis-india.org</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">Prof. Braman,<br>
<br>
Thanks for your detailed feedback.<br>
<br>
Apologies for the silence on the list: just a note that we are working<br>
on pushing a major update based on your comments and the suggestions<br>
from Bill Woodcock, Corinne and others.<br>
<br>
Will send a response to all the comments with the update as well.<br>
<br>
Thank you.<br>
-Gurshabad<br>
<br>
On 2/12/21 4:55 AM, Sandra Braman wrote:<br>
&gt; Folks --=C2=A0<br>
&gt; <br>
&gt; Following are some comments on draft guidelines, some of which echo<br=
>
&gt; points already made on this list. If I&#39;ve misunderstood anything, =
please<br>
&gt; let me know.=C2=A0 Some of the comments are analytical.=C2=A0 Others a=
re<br>
&gt; recommendations that may make the document more effective.=C2=A0 Again=
,<br>
&gt; thanks to the authors and those who provided feedback and input to the=
<br>
&gt; authors for all the labor put in.<br>
&gt; <br>
&gt; Sandra Braman<br>
&gt; <br>
&gt; ----------------------------------------------------------<br>
&gt; <br>
&gt; _Human Rights_<br>
&gt; <br>
&gt; Graph 2 on page 4 identifies key sources of human rights.=C2=A0 The ma=
nner of<br>
&gt; presentation conflates documents from sources that are importantly<br>
&gt; different regarding their source and, thus, relative weight.=C2=A0 A d=
ocument<br>
&gt; created by the Internet Governance Forum -- a talk shop only that has =
no<br>
&gt; status within the international legal system on its own -- with United=
<br>
&gt; Nations treaties.=C2=A0 This section of the document will be much stro=
nger if<br>
&gt; separate paragraphs discuss actual legal foundations for human rights<=
br>
&gt; and other sources of proposals for things that should be considered<br=
>
&gt; human rights in the Internet environment (the latter would include Hil=
l<br>
&gt; 2014, too, for example).=C2=A0 The IGF document is certainly pertinent=
, but<br>
&gt; should be discussed in the manner one would discuss the scholarly<br>
&gt; literature and &quot;gray matter&quot; (reports from advocacy groups a=
nd<br>
&gt; non-profit organizations, etc.), not as if it were international law.<=
br>
&gt; <br>
&gt; Which human rights will be discussed in this document should be clearl=
y<br>
&gt; articulated in the opening section, with definitions for the purposes =
of<br>
&gt; this document and the sources of those rights, and then used<br>
&gt; consistently throughout the document.=C2=A0 Late in the document the &=
quot;right<br>
&gt; to security&quot; shows up; is this a rephrasing of Article 28 of the<=
br>
&gt; Universal Declaration on Human Rights, or something else that is not<b=
r>
&gt; mentioned on page 4?<br>
&gt; <br>
&gt; Theoretically and operationally defining each concept presented as a<b=
r>
&gt; human right more thoroughly will be important.=C2=A0 There is confusio=
n in<br>
&gt; this document, for example, between the right to access government<br>
&gt; information, which is included in a number of constitutions and<br>
&gt; constitution-like documents around the world and is considered essenti=
al<br>
&gt; to the ability to hold governments accountable for their action, and a=
<br>
&gt; right to access information in general (more typically considered<br>
&gt; necessary to freedom of expression, since in order to talk about<br>
&gt; something you have to have information about it).<br>
&gt; <br>
&gt; What arguments justify which two or three human rights of concern for<=
br>
&gt; each item in section 3.3?=C2=A0 As presented in this draft, it seems<b=
r>
&gt; essentially random in a manner that is not persuasive regarding what i=
s<br>
&gt; in and what is out.<br>
&gt; <br>
&gt; _Direct vs Indirect Violations of Human Rights_<br>
&gt; _<br>
&gt; _<br>
&gt; Perhaps the most interesting thread running through this document is t=
he<br>
&gt; implicit suggestion that impediments to technological innovation can<b=
r>
&gt; themselves be understood as violations of human rights.=C2=A0 (Fully<b=
r>
&gt; developing that argument would make a great scholarly journal article!=
)=C2=A0<br>
&gt; I buy that argument, as innovations are often/may well be needed to<br=
>
&gt; develop work-arounds for exercises of power that violate human rights =
in<br>
&gt; traditionally understood ways, but this piece will be much more<br>
&gt; effective and stronger if it makes that argument explicit and uses it =
as<br>
&gt; a tool in the structuring of the narrative.<br>
&gt; <br>
&gt; The suggestions are two:=C2=A0 (1) Add an explicit discussion of the<b=
r>
&gt; distinction between direct violations of human rights (e.g., censorshi=
p)<br>
&gt; and indirect violations of human rights (e.g., innovation, which<br>
&gt; includes matters such as &quot;adaptability&quot; as introduced in thi=
s draft).<br>
&gt; (2) Structure the discussion of topics in Section 3.3 to clearly<br>
&gt; distinguish between the two.=C2=A0 A recommendation for an alternative=
<br>
&gt; structuring of those topics can be found below.<br>
&gt; <br>
&gt; Another distinction that could usefully be introduced in this document=
<br>
&gt; is the difference between short-term and long-term effects on human<br=
>
&gt; rights.=C2=A0 Censorship is a short-term, immediate effect.=C2=A0 Diff=
erential<br>
&gt; ability to access information about one&#39;s environment and that pro=
vides<br>
&gt; the affordances for effective political action -- what was first<br>
&gt; labelled &quot;the knowledge gap&quot; in the 1970s and is now more co=
mmonly<br>
&gt; referred to as &quot;the digital divide&quot; -- is better understood =
as a<br>
&gt; long-term effect on human rights.<br>
&gt; <br>
&gt; _Stages of the Internet Design Process and the Institutional Context_<=
br>
&gt; _<br>
&gt; _<br>
&gt; This draft mentions that different human rights issues come up at<br>
&gt; different stages of the protocol development process.=C2=A0 It also as=
ks for<br>
&gt; a lot of types of research and thinking that, as others have pointed<b=
r>
&gt; out, are not generally within the job description of those working on<=
br>
&gt; Internet protocols and for which they may not have been trained -- the=
se<br>
&gt; are actually matters of organizational design.=C2=A0 This document wou=
ld be<br>
&gt; much stronger if it unbundled each of these things.<br>
&gt; <br>
&gt; For stages of the protocol design process, please say more about which=
<br>
&gt; issues should be considered when?=C2=A0 Doing so would require offerin=
g a<br>
&gt; model of the stages of the protocol design process.=C2=A0 It would be =
great<br>
&gt; to have a section that does that and that then specifies which issues<=
br>
&gt; would be of concern when.=C2=A0 The authors will probably want to incl=
ude<br>
&gt; &quot;implementation&quot; among the stages discussed.<br>
&gt; <br>
&gt; On the organizational design side, the document would be stronger if i=
t<br>
&gt; offered at least a model of what an organizational structure might be<=
br>
&gt; that would include all of the different kinds of expertise required to=
<br>
&gt; do the work asked for here, along with a mapping of the work flow acro=
ss<br>
&gt; employees with different types of expertise.<br>
&gt; <br>
&gt; _Research on the Effects of Design Decisions_<br>
&gt; _<br>
&gt; _<br>
&gt; A recurring problem in research on communication and the media is<br>
&gt; confusing what can be learned from research on an actual text or set o=
f<br>
&gt; visuals and the effects of that text or visuals on those who receive<b=
r>
&gt; it.=C2=A0 In that context, textual analysis can only tell the research=
er what<br>
&gt; is in the text; for effects research, quite other research methods mus=
t<br>
&gt; be used.=C2=A0 The same problem runs throughout this document.=C2=A0 T=
he authors<br>
&gt; are encouraged to clearly distinguish the features of a protocol itsel=
f,<br>
&gt; how the protocol operates within the network (the technical &quot;cont=
ext&quot; in<br>
&gt; the sense of how it interacts with other protocols), how it is used in=
<br>
&gt; the application layer, how applications are used, and the effects of t=
he<br>
&gt; uses of those applications.=C2=A0 A second issue raised by the methods=
<br>
&gt; introduced here is that they run the danger of being limited to &quot;=
looking<br>
&gt; under the streetlight&quot; (the familiar story about where a drunk is=
<br>
&gt; looking for keys, irrespective of where they may be), although in term=
s<br>
&gt; of provenance that problem may be more reflective of the fact that the=
<br>
&gt; full scholarly literature and what can be learned from researchers<br>
&gt; outside of the HRPC have not yet been brought to bear.<br>
&gt; <br>
&gt; Different research methods will be needed to examine each of these.=C2=
=A0<br>
&gt; This document would be much stronger if it broke out which of the kind=
s<br>
&gt; of questions raised can actually be the subjects of research at each<b=
r>
&gt; stage of this sequence, too.=C2=A0 The mixing of application layer and=
 use<br>
&gt; issues with protocol design in my view undermines the effectiveness of=
<br>
&gt; the argument this reader, at least, understands the authors to be tryi=
ng<br>
&gt; to make.=C2=A0<br>
&gt; <br>
&gt; Research on designer perceptions of possible human rights risks can be=
<br>
&gt; useful and interesting (I&#39;ve done some of that research myself), b=
ut<br>
&gt; does not tell the researcher anything about the actual risks as<br>
&gt; experienced or as understood by social scientists who have studied tho=
se<br>
&gt; effects on the ground. There are, however, several significant bodies =
of<br>
&gt; research that the authors could mine for more empirical detail on the<=
br>
&gt; effects of specific protocol design features rather than assuming that=
<br>
&gt; universe is bounded by what one or a few members of HRPC have done or<=
br>
&gt; asking computer scientists and electrical engineers to undertake all o=
f<br>
&gt; that work.=C2=A0 It is incredibly important to keep human rights issue=
s in<br>
&gt; front of those doing technical work, including regularly showing up in=
<br>
&gt; IETF meetings to alert those designing protocols to specific issues, b=
ut<br>
&gt; for research on the effects of those protocols HRPC should be turning =
to<br>
&gt; social scientists who are actually studying the effects and who could =
be<br>
&gt; encouraged to go further in this area, sometimes -- so valuably -- in<=
br>
&gt; collaboration with technical experts who have given themselves to this=
<br>
&gt; specific task.=C2=A0 In this regard, the work of Ron Deibert&#39;s gro=
up at the<br>
&gt; University of Toronto (Citizen Lab) should be highlighted as a model<b=
r>
&gt; (<a href=3D"https://urldefense.com/v3/__https://citizenlab.ca/__;!!KwN=
VnqRv!RUZdCcJt8Ap1Rd6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLLyDMfrrza9gzw$" rel=
=3D"noreferrer" target=3D"_blank">https://urldefense.com/v3/__https://citiz=
enlab.ca/__;!!KwNVnqRv!RUZdCcJt8Ap1Rd6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLLyD=
Mfrrza9gzw$</a> ).=C2=A0 Work in fields such as anthropology,<br>
&gt; sociology, political science, information science, communication, STS<=
br>
&gt; (studies of technology and society), and economics will all be useful.=
<br>
&gt; <br>
&gt; To date the HRPC (to my knowledge) has largely engaged with the<br>
&gt; communities of researchers working in this area by bringing individual=
s<br>
&gt; to IETF meetings for short presentations.=C2=A0 Given the relatively s=
mall<br>
&gt; number of people active within HRPC who come from social science<br>
&gt; backgrounds and limits on the time of everyone within HRPC, some<br>
&gt; assistance may be needed to take advantage of the many additional<br>
&gt; research methods that should be used to evaluate the effects of protoc=
ol<br>
&gt; design on human rights as well as to incorporate findings from researc=
h<br>
&gt; in this area already conducted into this document.=C2=A0 A few thought=
s<br>
&gt; regarding how that might be done will be offered in a separate email.<=
br>
&gt; <br>
&gt; However it is done, going much further with research methods will<br>
&gt; significantly increase the sophistication and utility of this document=
.=C2=A0<br>
&gt; As it currently stands, the section on &quot;expert interviews&quot; i=
s confusing<br>
&gt; because it appears to be asking computer scientists to be expert on<br=
>
&gt; social science matters, for example.=C2=A0 Interviews with various typ=
es of<br>
&gt; experts will indeed be among the kinds of methods that can be useful,<=
br>
&gt; but the different types of expertise involved should be acknowledged a=
nd<br>
&gt; different kinds of questions would be asked of different kinds of expe=
rts.<br>
&gt; <br>
&gt; _Grouping of Section 3.3 Topics_<br>
&gt; _<br>
&gt; _<br>
&gt; Three dimensions of analysis could be used to better structure the<br>
&gt; sequencing of topics in Section 3.3.=C2=A0 The suggestion here is to u=
se the<br>
&gt; focus of attention as the highest level used to group related issues<b=
r>
&gt; together, and then discuss differences between direct and indirect<br>
&gt; effects and between short-term and long-term effects within each of th=
e<br>
&gt; categories.=C2=A0 A suggestion what the top-level of categorization mi=
ght<br>
&gt; look like is offered here, with the current number of the topics to be=
<br>
&gt; included within it.=C2=A0 Because some of the current topics combine t=
ypes of<br>
&gt; issues, the final category includes one item that in my view should be=
<br>
&gt; unbundled for clarification for the purposes of this document and thre=
e<br>
&gt; items that in my view should be deleted.=C2=A0 The following section<b=
r>
&gt; discusses individual topics and/or the combinations suggested here.=C2=
=A0<br>
&gt; <br>
&gt; /Network Operations/<br>
&gt; /<br>
&gt; /<br>
&gt; Connectivity (3.3.1)<br>
&gt; Internationalization (3.3.5)<br>
&gt; Localization (3.3.11)<br>
&gt; Adaptability (3.3.17)<br>
&gt; <br>
&gt; Open Standards (3.3.7)<br>
&gt; Heterogeneity Support (3.3.8)<br>
&gt; <br>
&gt; Decentralization (3.3.12)<br>
&gt; <br>
&gt; Reliability (3.3.13)<br>
&gt; <br>
&gt; /The Individual User/<br>
&gt; /<br>
&gt; /<br>
&gt; Privacy (3.3.2)<br>
&gt; Pseudonymity (3.3.9)<br>
&gt; Confidentiality (3.3.14)<br>
&gt; Anonymity (3.3.19)<br>
&gt; <br>
&gt; Accessibility (3.3.10)<br>
&gt; <br>
&gt; /Content/<br>
&gt; /<br>
&gt; /<br>
&gt; Content Agnosticism (3.3.3)<br>
&gt; <br>
&gt; Censorship Resistance (3.3.6)<br>
&gt; Integrity (3.3.15)<br>
&gt; Authenticity (3.3.16)<br>
&gt; <br>
&gt; /To Be Unbundled/<br>
&gt; /<br>
&gt; /<br>
&gt; Security (3.3.4)=C2=A0<br>
&gt; <br>
&gt; /Delete/<br>
&gt; <br>
&gt; Outcome Transparency (3.3.18)<br>
&gt; Remedy and Attribution (3.3.20)<br>
&gt; Miscellaneous Considerations (3.3.21)<br>
&gt; /<br>
&gt; /<br>
&gt; _Discussion of Topics and Topic Groupings_<br>
&gt; _<br>
&gt; _<br>
&gt; /Network Operations/<br>
&gt; /<br>
&gt; /<br>
&gt; Decentralization is separated out because the extent to which<br>
&gt; decentralization can occur operates at so many different levels of the=
<br>
&gt; structures involved -- the network, applications, the social structure=
,<br>
&gt; and political structure -- that it is different in kind from the first=
 5<br>
&gt; items above that seem to me (as someone who is NOT a technical expert)=
<br>
&gt; to be related to each other.=C2=A0 Reliability also seems to me to be<=
br>
&gt; different in kind.<br>
&gt; <br>
&gt; In the scholarly journal article &quot;The Framing Years,&quot; the co=
ncept of<br>
&gt; &quot;technological democracy&quot; as a key design principle for the =
Internet was<br>
&gt; introduced.=C2=A0 The topics of Open Standards and Heterogeneity addit=
ionally<br>
&gt; can be distinguished by this feature.<br>
&gt; <br>
&gt; The Decentralization topic mixes several different types of control fr=
om<br>
&gt; diverse sources (governments, protocol limits, etc.) together without<=
br>
&gt; distinguishing them.=C2=A0 The document will be stronger, clearer, and=
 more<br>
&gt; useful if it distinguishes them.<br>
&gt; <br>
&gt; In the scholarly journal article &quot;The Geopolitical and the Networ=
k<br>
&gt; Political:=C2=A0 Internet Designers and Governance,&quot; the tension =
between<br>
&gt; geopolitical citizenship (allegiance to one&#39;s identity as a citize=
n of a<br>
&gt; geopolitically recognized state -- a government recognized by the UN)<=
br>
&gt; and network citizenship (allegiance to one&#39;s identity as a user/ci=
tizen<br>
&gt; of the Internet, the success of which is critical to the user) is<br>
&gt; explored.=C2=A0 There are often instances in which what is required of=
 the<br>
&gt; geopolitical citizen is the opposite of what is required of the networ=
k<br>
&gt; citizen.=C2=A0 That is the tension discussed on page 17, graph 2.<br>
&gt; <br>
&gt; /The Individual User/<br>
&gt; <br>
&gt; All of the topics related to the diverse dimensions of personal privac=
y<br>
&gt; should be grouped together.=C2=A0 They would be best introduced with a=
<br>
&gt; general introduction to RFC 4949.=C2=A0 Doing so would then facilitate=
<br>
&gt; further analysis of what might differently be needed to attend to when=
<br>
&gt; thinking about each of the concepts distinguished there (if there are<=
br>
&gt; differences).<br>
&gt; <br>
&gt; Accessibility is different in kind as a topic.=C2=A0 However, the RFC<=
br>
&gt; referred to in that discussion, as I understand it, actually refers to=
<br>
&gt; technical limits and/or limits of access to images that may be in plac=
e<br>
&gt; because of a particular tool a specific individual chooses to use, not=
<br>
&gt; to human disability.=C2=A0 Is there anything else that deals with huma=
n<br>
&gt; disability at the protocol level that can be called upon here more<br>
&gt; validly?=C2=A0 Most of what I am aware of is at the application level.=
<br>
&gt; <br>
&gt; /Content/<br>
&gt; <br>
&gt; Content agnosticism is a tough one for two reasons.=C2=A0 First, any d=
ecision<br>
&gt; about structure made by definition will preference some content or use=
rs<br>
&gt; (and thus those users&#39; content) over others -- for any door that i=
s<br>
&gt; opened, another door is shut.=C2=A0 By the close of the 1990s (the per=
iod<br>
&gt; through which my own research went), several different models were<br>
&gt; experimented with to achieve &quot;fair queuing,&quot; and struggles w=
ith &quot;quality<br>
&gt; of service&quot; have continued since.=C2=A0 What is said here about c=
ontent<br>
&gt; agnosticism should reference all of that history and make specific<br>
&gt; recommendations if it sees a way out of this dilemma that others have<=
br>
&gt; not yet been able to discover.=C2=A0 Second, national governments are =
always<br>
&gt; going to assert priority access.=C2=A0 It is wishful thinking only to =
believe<br>
&gt; that would be otherwise.=C2=A0 The fix here for this document would be=
 to<br>
&gt; simply acknowledge that.<br>
&gt; <br>
&gt; In the discussion of Authenticity, isn&#39;t there another scenario wh=
en<br>
&gt; considering authentication?=C2=A0 This would add another line to the l=
ast<br>
&gt; scenario provided:=C2=A0 Bob knows who or what altered the data that d=
id not<br>
&gt; come from Alice.=C2=A0 Why should this not also be a requirement?=C2=
=A0<br>
&gt; Surveillance should go both ways (that is why we have access to<br>
&gt; government information as a fundamental constitutional principle).<br>
&gt; <br>
&gt; /To be Unbundled/<br>
&gt; /<br>
&gt; /<br>
&gt; The existing topic of &quot;security&quot; includes elements that woul=
d, in my<br>
&gt; view, be more strongly included if they were unbundled, with elements<=
br>
&gt; dispersed into the above categories to join those that are like of kin=
d.<br>
&gt; <br>
&gt; /To be Deleted/<br>
&gt; /<br>
&gt; /<br>
&gt; Outcome Transparency -- This is a reasonable expectation only if every=
<br>
&gt; organization employing those involved in the protocol design process<b=
r>
&gt; were to take up recommendations these authors have yet to develop for<=
br>
&gt; organizational structure and work flow processes adequate to the range=
<br>
&gt; of kinds of research being asked for here.=C2=A0 Since it is unlikely =
that<br>
&gt; those recommendations for organizational structure and work flow<br>
&gt; processes, will be forthcoming within the probable life cycle of the<b=
r>
&gt; writing of this document, and since it is even more unlikely that all =
of<br>
&gt; the organizations involved would follow such recommendations if offere=
d,<br>
&gt; in my view it would strengthen the document by deleting this item.=C2=
=A0<br>
&gt; Doing so would be a defensive writing gesture warding off critiques of=
<br>
&gt; naivete.<br>
&gt; <br>
&gt; Remedy and Attribution -- Others have made excellent points on this<br=
>
&gt; matter on the listserv.=C2=A0 Everything that would be pertinent here =
should<br>
&gt; be covered by the topics introduced that apply to individual users.=C2=
=A0 If<br>
&gt; that is not the case, the authors need to make clear what else would b=
e<br>
&gt; involved.=C2=A0 Delete as a topic but add to the discussion that intro=
duces<br>
&gt; the document.<br>
&gt; <br>
&gt; Miscellaneous Considerations -- Don&#39;t see what this obvious point =
adds.<br>
&gt; <br>
&gt; _Other Conceptual Issues_<br>
&gt; _<br>
&gt; _<br>
&gt; How do the authors distinguish between the effects of protocol-shaped<=
br>
&gt; communications between humans, between humans and non-humans, and<br>
&gt; between non-humans from a human rights perspective?=C2=A0 Protocol des=
ign<br>
&gt; features that impede the ability to make effective use of what is<br>
&gt; learned from environmental sensors, for example, could generage<br>
&gt; long-term human rights impacts.=C2=A0 Not mentioned at all here but it=
 would<br>
&gt; be a stronger document if it were.<br>
&gt; <br>
&gt; Page 6, graph 4 (in 3.3) -- What is meant by &quot;misapplication of t=
he<br>
&gt; protocol or technology&quot;?=C2=A0 That is really two questions in on=
e.=C2=A0 First,<br>
&gt; how do the authors distinguish an appropriate application from a<br>
&gt; misapplication?=C2=A0 Second, as again has been brought up in discussi=
on of<br>
&gt; this draft on the list, isn&#39;t this about users and not the protoco=
l<br>
&gt; design that is the focus of the document?=C2=A0 Those involved with at=
tempts<br>
&gt; to prevent uses of dual use technologies for purposes of war rather th=
an<br>
&gt; peace have struggled with this for decades; the inability to<br>
&gt; meaningfully, defensibly, and effectively grab ahold of it has<br>
&gt; essentially led to the abandonment of the effort.<br>
&gt; <br>
&gt; How do the authors evaluate the &quot;adequacy&quot; with which a give=
n protocol<br>
&gt; takes human rights into account?=C2=A0 (page 6, graph 5)<br>
&gt; <br>
&gt; The question of whether or not protocols need to be understandable by<=
br>
&gt; humans is one of the most amusing elements of discussion in the RFCs<b=
r>
&gt; during their first decade (1969-1979) (again, an article available if =
of<br>
&gt; interest).=C2=A0 In 3.3.5, on internationalization (p. 9, second graph=
 from<br>
&gt; bottom), the question is about text strings that &quot;have to be&quot=
; understood<br>
&gt; or entered by humans.=C2=A0 What about situations in which the more ac=
curate<br>
&gt; verb would be &quot;can be&quot;?<br>
&gt; <br>
&gt; Re Internationalization -- See my comments on draft association re the=
<br>
&gt; language issue.<br>
&gt; <br>
&gt; In areas such as degradation, the distinction should be drawn between<=
br>
&gt; degradation and knowledge of degradation.=C2=A0 That is also true for<=
br>
&gt; integrity and in other areas that can, under some circumstances, also<=
br>
&gt; include even censorship.<br>
&gt; <br>
&gt; _Writing Issues_<br>
&gt; _<br>
&gt; _<br>
&gt; 3.2.1 -- This paragraph is opaque.<br>
&gt; <br>
&gt; 3.2.2 -- This paragraph is tautological.<br>
&gt; <br>
&gt; 3.3.2 -- Page 8, graph 3 -- The document on privacy is not an &quot;ex=
ample.&quot;<br>
&gt; <br>
&gt; 3.3.20 -- Page 23, graph 1 -- The reference to Kaye&#39;s thinking on<=
br>
&gt; freedom of expression and the Internet belongs in the discussion of<br=
>
&gt; human rights principles, not here.<br>
&gt; <br>
&gt; There are a number of typographical and grammar errors throughout.<br>
&gt; <br>
&gt; =C2=A0<br>
&gt; <br>
&gt; <br>
&gt; _<br>
&gt; _<br>
&gt; <br>
&gt; _<br>
&gt; _<br>
&gt; <br>
&gt; _<br>
&gt; _<br>
&gt; <br>
&gt; <br>
&gt; _<br>
&gt; _<br>
&gt; _<br>
&gt; _<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; hrpc mailing list<br>
&gt; <a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a><b=
r>
&gt; <a href=3D"https://urldefense.com/v3/__https://www.irtf.org/mailman/li=
stinfo/hrpc__;!!KwNVnqRv!RUZdCcJt8Ap1Rd6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLL=
yDMfrZoGjVnA$" rel=3D"noreferrer" target=3D"_blank">https://urldefense.com/=
v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!RUZdCcJt8Ap1Rd=
6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLLyDMfrZoGjVnA$</a> <br>
&gt; <br>
</blockquote></div></div>

--00000000000068e17605bb617f7e--


From nobody Mon Feb 15 07:19:51 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 9F9E23A0C36 for <hrpc@ietfa.amsl.com>; Mon, 15 Feb 2021 07:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=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 0SrW7H-xpWiZ for <hrpc@ietfa.amsl.com>; Mon, 15 Feb 2021 07:19:47 -0800 (PST)
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 0269E3A0C46 for <hrpc@irtf.org>; Mon, 15 Feb 2021 07:19:46 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org 019B45806C016
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1613402379; bh=Nmu+JG5anYNvVXV0OMSd5LjTjpHcalagv6VuFWoWnPc=; h=To:From:Message-ID:Date:MIME-Version; b=AaSJa0f2HAbBh5OQGm7bpVqfQlOnzgzxINBtRuD9cd4beqQoBg8eZvWrevKoyLgIA WaR/f7jZpieqksSAuO7taGG0OVDeawDXIqjO9PaidmhyqtOqFWRrxHtgRfo2IBqt4V v7j3+LSetoNITYih25r6OI+TNtLrhn9AuDA26q6sRgj/yONYjsBYzZmwLRbkgo3bc1 6UtDK1T2oh0DLYA6iFaXFmuIUVqd0PZQF2c6wLuNyPV/7cj7wyWCyCJtOhVeBlae1L CO5ttZUEzjgoCOiBLM0HUYdrmK/AUlHv5+iPCFQ5XCF5nTml2Ca06tQRBiXLPv3/xb U5MxXawrpXzRQ==
To: Sandra Braman <braman@tamu.edu>
Cc: Bill Woodcock <woody@pch.net>, Corinne Cath <corinnecath@gmail.com>, hrpc@irtf.org
References: <CAB2unbOo+rdQVfbCZYu0ZQ+-Kgn7D1-z8XKh+L3iWm26oR7JgA@mail.gmail.com> <e8d8627a-c224-3ed9-7fed-fc573c97fee6@cis-india.org> <CAB2unbMYZzf_HbnPSA4OYpRU20Uz+-Tsyon088m8jEbxAVWqxg@mail.gmail.com>
From: Gurshabad Grover <gurshabad@cis-india.org>
Autocrypt: addr=gurshabad@cis-india.org; keydata= mQINBFriroIBEADfyDpCD8eborMUMXKtZzjo4t2KzrAlUVYgE/TFtrwUP+4Xw4dzakDIzST8 sVYmlXIWhM5NBBTZSQ190vsxrkbi0xxLcXYM2olZEtqkJ8zONZeZLBeGvcfMymtHqD4jHwYb Zm7OXnS45fWDL+HOoMP/VCwEn098rYfnllIkYQD1Gc28Ig+ywjGg8y5p0qMmmmhm2ckgLjnG MJX8t273MSc8wsn/UYH922yif3MQXmrzqgnRl9hRzf90SKqAw38bw7wccb55pIItloKYsi0r zYBKJSOPXn91Z21TpOSTy21M0MZYEAlDn1zeea+q8TggfHNWxOXoKrIm1pqZFRz0k+8i2siJ AHf8bRm/fhukA6szZ6b2nNPxjkAmOv9zvGu6RZGbmeLvQYVBSSnZ67ayZrkKwn7KIyAV6hQM /bVnD8eEZ2tZ0S8lxoZFYSNeMGt2b6WelFZO97/LbjxaJUHd9K8g5H0MwqN1NXoBxRwllVRC 3sVHVoWTBqnKo8qplzvQEAto69PpvuxxKTOFEJeQqmn1b/fo3sLRb4YiIg8Ax+Np7Huzzjk6 vKKgpIwIN7yEUj/ReWi/UA/W4wSg3XkcqTf7h73crnN/1At0PdgozbDV2UbcApaldStP4DfG UiQl0/7MiYLKapDDuSahmoeH3xrNnrzS9BAfuGHezzDbMyPLXQARAQABtCpHdXJzaGFiYWQg R3JvdmVyIDxndXJzaGFiYWRAY2lzLWluZGlhLm9yZz6JAj0EEwEIACcFAlriroICGyMFCQlm AYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQrbl/X+ubfC7/bQ//YQv7zqQE433xxsN/ 3GYKoOFccBy3WvV4DxrTskJ3n3k5lfcZolbc8TQksQOTzyerNt2ZA7fsGZa7eFSW+xR4Yq3/ C9o+5FOoHGhyZhb+x17MILhmyvyUNSj7SdKrRISgurMbV2Vv8LxmTcdrK6CdFF6JLH+opzU1 NlRKwZqROPgbYZEB2QFIUbGfgh2I5AXNyV2XbT7fagfkHk+v9AUV7POP2H1+AZ1xq6iFTm2o 9ufNZsp2bInsDohcVBKC3aH2cnFMjvIXpNoUOx8vb5A2xW0aBUTTJDB/uZw53WOg3kehrCNb ZkML3FnDZLRuu1e8DSWmwk5YIoDzt5bMCgfUwb0C6Q+JuM8lC+8CEEa9qamLc+fhvFAzcrWp VWuSaVeLdhe5NxmtlRYNZdGuKy6sRHjwsEWlwzRylhm74fiDR3aA1eIFsfmYLd4z+i1Fp23Y dHJf7/Gor2CmOxphog9DEA9WCuORXfx4De7hoMKwW4gWKw1A8B12Cv4EOkXmCsWsOnfDEarr 2Yl6elxkhQRfKjAesXb0cezRzZgwsWIsbeYsuWFF7Xi6IzUJ27lxU3p5PcyY8O8aDYOn+pu0 YFJ7s3u2VRRgptVZJmkcN3WTApXSHY8fGl5xAakM/bqFJj9uj5zlMnFN2EplC6/mQkfYfy2f siaGTP/GQV4OSuOeuMK5Ag0EWuKuggEQAJ4lAzB72gHw4+rbyxmQNNVmvgYVZPjFtO/MQdYi x1QwRP/gxxqPqTd/ZwQvmPGzXRKw10B7uKSRk6YP12+IG0mXJwHGp9q5CWJE0XNGqX3UWbAc KIzxqPNpsf8e6Bv7jdW0YwLBxJ+RW0NNL6uAxz0sr2frbnS+EZB3cU+zOZzp/9YfTUZO2lxF NzgJoErKe/HLp7aBeJXBBcwO0LQlIT80rTZx2KihBa/Ww/y9E9gV/HacJu/Ncb6E/G3e4xGj 9w9L+UW43q01wy+FSUKy9FLc7D40WqQsj8SXZEpl84SyLcJRoX3mtj59bX2SAN2VB2BAksTu qCh00IcIUGfyHziu5PwUWYM96gOhDSocP4wSeiQ8TwLzaffllz2qhdI296a9lCIYIeWVytEd NU9jJ3RbzXAgE0pnDauNXDaQv1FS5jYi8rlslJUxKnrS69BFNjM5RqQ16Cm0C4rKL7/a8wHC r4VjcjSCM8Lzv8YOOitJ9Yt4Y8SVfO5s3YvxcdSr56nX0W3B1kGbG1GpqWTzOgXzGF5bIsbV 7SPecwUs9ShvmLmZzDUxIQ68n4zj3lMZn5I+pP+Ew6nAAiuSmKdr5cygnCH/NVJzil07t+X4 uR6oKHBhuMFYF1c6Wxk36m+EZz5ZHFaT4rN0WDIJdAEqRzD0Z56V6ansDF8y+ksh0SHlABEB AAGJAiUEGAEIAA8FAlriroICGwwFCQlmAYAACgkQrbl/X+ubfC50rhAAloTaq/fZC1gtiVtU wOB+00gEkjgmzt+rLkW+l2EySTST7tje57W83UZwzCX746B2O//Bqardxz9R1Vr0VFiwHA8g 3qeBqPqiv1WoQch/iZ5d/1MxK4A9xDag1uyqLR8RuGlZ8lATmcP3IabKiuiBV4MlFZ7V2Ib6 5ToPf28xxSyjMzTjQObIG0e009uHlu2z+iQVshLyoyVVAOWWa88D6iuBDC/EtBRjlpjLAjuR YhWVYX6KHdVUijKMHN2RqjpX5O2wPL7NcMY/wsTq7EteUeI75hxFvargRXkEt1XR8t52LC0u IE2OjpzY5re/ROUbfsqL8trjAOrSJ+Fx5H8AYl9JaoVxohhxDZgNtgNtPbh/8Nnlf9daj/bh lZcTBO98XLQwMnyHGPdyhIodpWPq2C09Ys3TkQsbcdMMB1pqnEK5Vz1zIKkEEX7QVsLdrz7C 2CFsauc/9PHj+4njCHslXtzBOiVu5FXTnbCwPrLJs5iEUkUCb6qtE/2mSCTrAanzOTTOmqiM cnNTI1Tj0ht462S9VypppQnKCv8shGxXG7BadZTv+pNCA/WfB2kk1sS3ZwB0wBWX4p41fxs+ ArM9ew2SzQ/vBrEfO7ljPfZZmBqH4t/vgAZBnOtTxCGlPEIJqiMqtGHRqIqpiR20QfxEUuXI MfMfa9QJpisdNmqoUyc=
Message-ID: <78cb130e-fe5b-58e6-8f0e-89979c0b1302@cis-india.org>
Date: Mon, 15 Feb 2021 20:49:33 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAB2unbMYZzf_HbnPSA4OYpRU20Uz+-Tsyon088m8jEbxAVWqxg@mail.gmail.com>
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: a3afecdc09d8217ed5ad3e377b985c15
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/MXWeni13aBvEY2VMFeB3LurrEys>
Subject: Re: [hrpc] comments on draft 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, 15 Feb 2021 15:19:50 -0000

Yes, will be sending a detailed response (including what changes were
made to address the feedback) to each review.

-Gurshabad

On 2/15/21 8:48 PM, Sandra Braman wrote:
> Thanks for letting me know.=C2=A0 Will your response to comments includ=
e
> those that came from Corinne, Bill, and others as well, so we can all
> understand the arguments, corrections, additional points, etc., to whic=
h
> the new draft is responding, since (unless I have missed it), these hav=
e
> not all been shared with the list yet?
>=20
> On Mon, Feb 15, 2021 at 7:27 AM Gurshabad Grover
> <gurshabad@cis-india.org <mailto:gurshabad@cis-india.org>> wrote:
>=20
>     Prof. Braman,
>=20
>     Thanks for your detailed feedback.
>=20
>     Apologies for the silence on the list: just a note that we are work=
ing
>     on pushing a major update based on your comments and the suggestion=
s
>     from Bill Woodcock, Corinne and others.
>=20
>     Will send a response to all the comments with the update as well.
>=20
>     Thank you.
>     -Gurshabad
>=20
>     On 2/12/21 4:55 AM, Sandra Braman wrote:
>     > Folks --=C2=A0
>     >
>     > Following are some comments on draft guidelines, some of which ec=
ho
>     > points already made on this list. If I've misunderstood anything,
>     please
>     > let me know.=C2=A0 Some of the comments are analytical.=C2=A0 Oth=
ers are
>     > recommendations that may make the document more effective.=C2=A0 =
Again,
>     > thanks to the authors and those who provided feedback and input t=
o the
>     > authors for all the labor put in.
>     >
>     > Sandra Braman
>     >
>     > ----------------------------------------------------------
>     >
>     > _Human Rights_
>     >
>     > Graph 2 on page 4 identifies key sources of human rights.=C2=A0 T=
he
>     manner of
>     > presentation conflates documents from sources that are importantl=
y
>     > different regarding their source and, thus, relative weight.=C2=A0=
 A
>     document
>     > created by the Internet Governance Forum -- a talk shop only that
>     has no
>     > status within the international legal system on its own -- with U=
nited
>     > Nations treaties.=C2=A0 This section of the document will be much
>     stronger if
>     > separate paragraphs discuss actual legal foundations for human ri=
ghts
>     > and other sources of proposals for things that should be consider=
ed
>     > human rights in the Internet environment (the latter would includ=
e
>     Hill
>     > 2014, too, for example).=C2=A0 The IGF document is certainly pert=
inent, but
>     > should be discussed in the manner one would discuss the scholarly
>     > literature and "gray matter" (reports from advocacy groups and
>     > non-profit organizations, etc.), not as if it were international =
law.
>     >
>     > Which human rights will be discussed in this document should be
>     clearly
>     > articulated in the opening section, with definitions for the
>     purposes of
>     > this document and the sources of those rights, and then used
>     > consistently throughout the document.=C2=A0 Late in the document =
the "right
>     > to security" shows up; is this a rephrasing of Article 28 of the
>     > Universal Declaration on Human Rights, or something else that is =
not
>     > mentioned on page 4?
>     >
>     > Theoretically and operationally defining each concept presented a=
s a
>     > human right more thoroughly will be important.=C2=A0 There is con=
fusion in
>     > this document, for example, between the right to access governmen=
t
>     > information, which is included in a number of constitutions and
>     > constitution-like documents around the world and is considered
>     essential
>     > to the ability to hold governments accountable for their action, =
and a
>     > right to access information in general (more typically considered
>     > necessary to freedom of expression, since in order to talk about
>     > something you have to have information about it).
>     >
>     > What arguments justify which two or three human rights of concern=
 for
>     > each item in section 3.3?=C2=A0 As presented in this draft, it se=
ems
>     > essentially random in a manner that is not persuasive regarding
>     what is
>     > in and what is out.
>     >
>     > _Direct vs Indirect Violations of Human Rights_
>     > _
>     > _
>     > Perhaps the most interesting thread running through this document
>     is the
>     > implicit suggestion that impediments to technological innovation =
can
>     > themselves be understood as violations of human rights.=C2=A0 (Fu=
lly
>     > developing that argument would make a great scholarly journal
>     article!)=C2=A0
>     > I buy that argument, as innovations are often/may well be needed =
to
>     > develop work-arounds for exercises of power that violate human
>     rights in
>     > traditionally understood ways, but this piece will be much more
>     > effective and stronger if it makes that argument explicit and use=
s
>     it as
>     > a tool in the structuring of the narrative.
>     >
>     > The suggestions are two:=C2=A0 (1) Add an explicit discussion of =
the
>     > distinction between direct violations of human rights (e.g.,
>     censorship)
>     > and indirect violations of human rights (e.g., innovation, which
>     > includes matters such as "adaptability" as introduced in this dra=
ft).
>     > (2) Structure the discussion of topics in Section 3.3 to clearly
>     > distinguish between the two.=C2=A0 A recommendation for an altern=
ative
>     > structuring of those topics can be found below.
>     >
>     > Another distinction that could usefully be introduced in this doc=
ument
>     > is the difference between short-term and long-term effects on hum=
an
>     > rights.=C2=A0 Censorship is a short-term, immediate effect.=C2=A0=
 Differential
>     > ability to access information about one's environment and that
>     provides
>     > the affordances for effective political action -- what was first
>     > labelled "the knowledge gap" in the 1970s and is now more commonl=
y
>     > referred to as "the digital divide" -- is better understood as a
>     > long-term effect on human rights.
>     >
>     > _Stages of the Internet Design Process and the Institutional Cont=
ext_
>     > _
>     > _
>     > This draft mentions that different human rights issues come up at
>     > different stages of the protocol development process.=C2=A0 It al=
so
>     asks for
>     > a lot of types of research and thinking that, as others have poin=
ted
>     > out, are not generally within the job description of those workin=
g on
>     > Internet protocols and for which they may not have been trained -=
-
>     these
>     > are actually matters of organizational design.=C2=A0 This documen=
t would be
>     > much stronger if it unbundled each of these things.
>     >
>     > For stages of the protocol design process, please say more about =
which
>     > issues should be considered when?=C2=A0 Doing so would require of=
fering a
>     > model of the stages of the protocol design process.=C2=A0 It woul=
d be great
>     > to have a section that does that and that then specifies which is=
sues
>     > would be of concern when.=C2=A0 The authors will probably want to=
 include
>     > "implementation" among the stages discussed.
>     >
>     > On the organizational design side, the document would be stronger
>     if it
>     > offered at least a model of what an organizational structure migh=
t be
>     > that would include all of the different kinds of expertise requir=
ed to
>     > do the work asked for here, along with a mapping of the work flow
>     across
>     > employees with different types of expertise.
>     >
>     > _Research on the Effects of Design Decisions_
>     > _
>     > _
>     > A recurring problem in research on communication and the media is
>     > confusing what can be learned from research on an actual text or
>     set of
>     > visuals and the effects of that text or visuals on those who rece=
ive
>     > it.=C2=A0 In that context, textual analysis can only tell the
>     researcher what
>     > is in the text; for effects research, quite other research method=
s
>     must
>     > be used.=C2=A0 The same problem runs throughout this document.=C2=
=A0 The authors
>     > are encouraged to clearly distinguish the features of a protocol
>     itself,
>     > how the protocol operates within the network (the technical
>     "context" in
>     > the sense of how it interacts with other protocols), how it is us=
ed in
>     > the application layer, how applications are used, and the effects
>     of the
>     > uses of those applications.=C2=A0 A second issue raised by the me=
thods
>     > introduced here is that they run the danger of being limited to
>     "looking
>     > under the streetlight" (the familiar story about where a drunk is
>     > looking for keys, irrespective of where they may be), although in
>     terms
>     > of provenance that problem may be more reflective of the fact tha=
t the
>     > full scholarly literature and what can be learned from researcher=
s
>     > outside of the HRPC have not yet been brought to bear.
>     >
>     > Different research methods will be needed to examine each of thes=
e.=C2=A0
>     > This document would be much stronger if it broke out which of the
>     kinds
>     > of questions raised can actually be the subjects of research at e=
ach
>     > stage of this sequence, too.=C2=A0 The mixing of application laye=
r and use
>     > issues with protocol design in my view undermines the effectivene=
ss of
>     > the argument this reader, at least, understands the authors to be
>     trying
>     > to make.=C2=A0
>     >
>     > Research on designer perceptions of possible human rights risks c=
an be
>     > useful and interesting (I've done some of that research myself), =
but
>     > does not tell the researcher anything about the actual risks as
>     > experienced or as understood by social scientists who have studie=
d
>     those
>     > effects on the ground. There are, however, several significant
>     bodies of
>     > research that the authors could mine for more empirical detail on=
 the
>     > effects of specific protocol design features rather than assuming=
 that
>     > universe is bounded by what one or a few members of HRPC have don=
e or
>     > asking computer scientists and electrical engineers to undertake
>     all of
>     > that work.=C2=A0 It is incredibly important to keep human rights =
issues in
>     > front of those doing technical work, including regularly showing =
up in
>     > IETF meetings to alert those designing protocols to specific
>     issues, but
>     > for research on the effects of those protocols HRPC should be
>     turning to
>     > social scientists who are actually studying the effects and who
>     could be
>     > encouraged to go further in this area, sometimes -- so valuably -=
- in
>     > collaboration with technical experts who have given themselves to=
 this
>     > specific task.=C2=A0 In this regard, the work of Ron Deibert's gr=
oup at the
>     > University of Toronto (Citizen Lab) should be highlighted as a mo=
del
>     >
>     (https://urldefense.com/v3/__https://citizenlab.ca/__;!!KwNVnqRv!RU=
ZdCcJt8Ap1Rd6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLLyDMfrrza9gzw$
>     ).=C2=A0 Work in fields such as anthropology,
>     > sociology, political science, information science, communication,=
 STS
>     > (studies of technology and society), and economics will all be us=
eful.
>     >
>     > To date the HRPC (to my knowledge) has largely engaged with the
>     > communities of researchers working in this area by bringing
>     individuals
>     > to IETF meetings for short presentations.=C2=A0 Given the relativ=
ely small
>     > number of people active within HRPC who come from social science
>     > backgrounds and limits on the time of everyone within HRPC, some
>     > assistance may be needed to take advantage of the many additional
>     > research methods that should be used to evaluate the effects of
>     protocol
>     > design on human rights as well as to incorporate findings from
>     research
>     > in this area already conducted into this document.=C2=A0 A few th=
oughts
>     > regarding how that might be done will be offered in a separate em=
ail.
>     >
>     > However it is done, going much further with research methods will
>     > significantly increase the sophistication and utility of this
>     document.=C2=A0
>     > As it currently stands, the section on "expert interviews" is
>     confusing
>     > because it appears to be asking computer scientists to be expert =
on
>     > social science matters, for example.=C2=A0 Interviews with variou=
s types of
>     > experts will indeed be among the kinds of methods that can be use=
ful,
>     > but the different types of expertise involved should be
>     acknowledged and
>     > different kinds of questions would be asked of different kinds of
>     experts.
>     >
>     > _Grouping of Section 3.3 Topics_
>     > _
>     > _
>     > Three dimensions of analysis could be used to better structure th=
e
>     > sequencing of topics in Section 3.3.=C2=A0 The suggestion here is=
 to
>     use the
>     > focus of attention as the highest level used to group related iss=
ues
>     > together, and then discuss differences between direct and indirec=
t
>     > effects and between short-term and long-term effects within each
>     of the
>     > categories.=C2=A0 A suggestion what the top-level of categorizati=
on might
>     > look like is offered here, with the current number of the topics =
to be
>     > included within it.=C2=A0 Because some of the current topics comb=
ine
>     types of
>     > issues, the final category includes one item that in my view shou=
ld be
>     > unbundled for clarification for the purposes of this document and
>     three
>     > items that in my view should be deleted.=C2=A0 The following sect=
ion
>     > discusses individual topics and/or the combinations suggested her=
e.=C2=A0
>     >
>     > /Network Operations/
>     > /
>     > /
>     > Connectivity (3.3.1)
>     > Internationalization (3.3.5)
>     > Localization (3.3.11)
>     > Adaptability (3.3.17)
>     >
>     > Open Standards (3.3.7)
>     > Heterogeneity Support (3.3.8)
>     >
>     > Decentralization (3.3.12)
>     >
>     > Reliability (3.3.13)
>     >
>     > /The Individual User/
>     > /
>     > /
>     > Privacy (3.3.2)
>     > Pseudonymity (3.3.9)
>     > Confidentiality (3.3.14)
>     > Anonymity (3.3.19)
>     >
>     > Accessibility (3.3.10)
>     >
>     > /Content/
>     > /
>     > /
>     > Content Agnosticism (3.3.3)
>     >
>     > Censorship Resistance (3.3.6)
>     > Integrity (3.3.15)
>     > Authenticity (3.3.16)
>     >
>     > /To Be Unbundled/
>     > /
>     > /
>     > Security (3.3.4)=C2=A0
>     >
>     > /Delete/
>     >
>     > Outcome Transparency (3.3.18)
>     > Remedy and Attribution (3.3.20)
>     > Miscellaneous Considerations (3.3.21)
>     > /
>     > /
>     > _Discussion of Topics and Topic Groupings_
>     > _
>     > _
>     > /Network Operations/
>     > /
>     > /
>     > Decentralization is separated out because the extent to which
>     > decentralization can occur operates at so many different levels o=
f the
>     > structures involved -- the network, applications, the social
>     structure,
>     > and political structure -- that it is different in kind from the
>     first 5
>     > items above that seem to me (as someone who is NOT a technical ex=
pert)
>     > to be related to each other.=C2=A0 Reliability also seems to me t=
o be
>     > different in kind.
>     >
>     > In the scholarly journal article "The Framing Years," the concept=
 of
>     > "technological democracy" as a key design principle for the
>     Internet was
>     > introduced.=C2=A0 The topics of Open Standards and Heterogeneity
>     additionally
>     > can be distinguished by this feature.
>     >
>     > The Decentralization topic mixes several different types of
>     control from
>     > diverse sources (governments, protocol limits, etc.) together wit=
hout
>     > distinguishing them.=C2=A0 The document will be stronger, clearer=
, and more
>     > useful if it distinguishes them.
>     >
>     > In the scholarly journal article "The Geopolitical and the Networ=
k
>     > Political:=C2=A0 Internet Designers and Governance," the tension =
between
>     > geopolitical citizenship (allegiance to one's identity as a
>     citizen of a
>     > geopolitically recognized state -- a government recognized by the=
 UN)
>     > and network citizenship (allegiance to one's identity as a
>     user/citizen
>     > of the Internet, the success of which is critical to the user) is
>     > explored.=C2=A0 There are often instances in which what is requir=
ed of the
>     > geopolitical citizen is the opposite of what is required of the
>     network
>     > citizen.=C2=A0 That is the tension discussed on page 17, graph 2.
>     >
>     > /The Individual User/
>     >
>     > All of the topics related to the diverse dimensions of personal
>     privacy
>     > should be grouped together.=C2=A0 They would be best introduced w=
ith a
>     > general introduction to RFC 4949.=C2=A0 Doing so would then facil=
itate
>     > further analysis of what might differently be needed to attend to=
 when
>     > thinking about each of the concepts distinguished there (if there=
 are
>     > differences).
>     >
>     > Accessibility is different in kind as a topic.=C2=A0 However, the=
 RFC
>     > referred to in that discussion, as I understand it, actually refe=
rs to
>     > technical limits and/or limits of access to images that may be in
>     place
>     > because of a particular tool a specific individual chooses to use=
, not
>     > to human disability.=C2=A0 Is there anything else that deals with=
 human
>     > disability at the protocol level that can be called upon here mor=
e
>     > validly?=C2=A0 Most of what I am aware of is at the application l=
evel.
>     >
>     > /Content/
>     >
>     > Content agnosticism is a tough one for two reasons.=C2=A0 First, =
any
>     decision
>     > about structure made by definition will preference some content o=
r
>     users
>     > (and thus those users' content) over others -- for any door that =
is
>     > opened, another door is shut.=C2=A0 By the close of the 1990s (th=
e period
>     > through which my own research went), several different models wer=
e
>     > experimented with to achieve "fair queuing," and struggles with
>     "quality
>     > of service" have continued since.=C2=A0 What is said here about c=
ontent
>     > agnosticism should reference all of that history and make specifi=
c
>     > recommendations if it sees a way out of this dilemma that others =
have
>     > not yet been able to discover.=C2=A0 Second, national governments=
 are
>     always
>     > going to assert priority access.=C2=A0 It is wishful thinking onl=
y to
>     believe
>     > that would be otherwise.=C2=A0 The fix here for this document wou=
ld be to
>     > simply acknowledge that.
>     >
>     > In the discussion of Authenticity, isn't there another scenario w=
hen
>     > considering authentication?=C2=A0 This would add another line to =
the last
>     > scenario provided:=C2=A0 Bob knows who or what altered the data t=
hat
>     did not
>     > come from Alice.=C2=A0 Why should this not also be a requirement?=
=C2=A0
>     > Surveillance should go both ways (that is why we have access to
>     > government information as a fundamental constitutional principle)=
.
>     >
>     > /To be Unbundled/
>     > /
>     > /
>     > The existing topic of "security" includes elements that would, in=
 my
>     > view, be more strongly included if they were unbundled, with elem=
ents
>     > dispersed into the above categories to join those that are like o=
f
>     kind.
>     >
>     > /To be Deleted/
>     > /
>     > /
>     > Outcome Transparency -- This is a reasonable expectation only if =
every
>     > organization employing those involved in the protocol design proc=
ess
>     > were to take up recommendations these authors have yet to develop=
 for
>     > organizational structure and work flow processes adequate to the =
range
>     > of kinds of research being asked for here.=C2=A0 Since it is unli=
kely that
>     > those recommendations for organizational structure and work flow
>     > processes, will be forthcoming within the probable life cycle of =
the
>     > writing of this document, and since it is even more unlikely that
>     all of
>     > the organizations involved would follow such recommendations if
>     offered,
>     > in my view it would strengthen the document by deleting this item=
.=C2=A0
>     > Doing so would be a defensive writing gesture warding off critiqu=
es of
>     > naivete.
>     >
>     > Remedy and Attribution -- Others have made excellent points on th=
is
>     > matter on the listserv.=C2=A0 Everything that would be pertinent =
here
>     should
>     > be covered by the topics introduced that apply to individual
>     users.=C2=A0 If
>     > that is not the case, the authors need to make clear what else
>     would be
>     > involved.=C2=A0 Delete as a topic but add to the discussion that =
introduces
>     > the document.
>     >
>     > Miscellaneous Considerations -- Don't see what this obvious point
>     adds.
>     >
>     > _Other Conceptual Issues_
>     > _
>     > _
>     > How do the authors distinguish between the effects of protocol-sh=
aped
>     > communications between humans, between humans and non-humans, and
>     > between non-humans from a human rights perspective?=C2=A0 Protoco=
l design
>     > features that impede the ability to make effective use of what is
>     > learned from environmental sensors, for example, could generage
>     > long-term human rights impacts.=C2=A0 Not mentioned at all here b=
ut it
>     would
>     > be a stronger document if it were.
>     >
>     > Page 6, graph 4 (in 3.3) -- What is meant by "misapplication of t=
he
>     > protocol or technology"?=C2=A0 That is really two questions in on=
e.=C2=A0 First,
>     > how do the authors distinguish an appropriate application from a
>     > misapplication?=C2=A0 Second, as again has been brought up in dis=
cussion of
>     > this draft on the list, isn't this about users and not the protoc=
ol
>     > design that is the focus of the document?=C2=A0 Those involved wi=
th
>     attempts
>     > to prevent uses of dual use technologies for purposes of war
>     rather than
>     > peace have struggled with this for decades; the inability to
>     > meaningfully, defensibly, and effectively grab ahold of it has
>     > essentially led to the abandonment of the effort.
>     >
>     > How do the authors evaluate the "adequacy" with which a given pro=
tocol
>     > takes human rights into account?=C2=A0 (page 6, graph 5)
>     >
>     > The question of whether or not protocols need to be understandabl=
e by
>     > humans is one of the most amusing elements of discussion in the R=
FCs
>     > during their first decade (1969-1979) (again, an article availabl=
e
>     if of
>     > interest).=C2=A0 In 3.3.5, on internationalization (p. 9, second =
graph from
>     > bottom), the question is about text strings that "have to be"
>     understood
>     > or entered by humans.=C2=A0 What about situations in which the mo=
re
>     accurate
>     > verb would be "can be"?
>     >
>     > Re Internationalization -- See my comments on draft association r=
e the
>     > language issue.
>     >
>     > In areas such as degradation, the distinction should be drawn bet=
ween
>     > degradation and knowledge of degradation.=C2=A0 That is also true=
 for
>     > integrity and in other areas that can, under some circumstances, =
also
>     > include even censorship.
>     >
>     > _Writing Issues_
>     > _
>     > _
>     > 3.2.1 -- This paragraph is opaque.
>     >
>     > 3.2.2 -- This paragraph is tautological.
>     >
>     > 3.3.2 -- Page 8, graph 3 -- The document on privacy is not an
>     "example."
>     >
>     > 3.3.20 -- Page 23, graph 1 -- The reference to Kaye's thinking on
>     > freedom of expression and the Internet belongs in the discussion =
of
>     > human rights principles, not here.
>     >
>     > There are a number of typographical and grammar errors throughout=
.
>     >
>     > =C2=A0
>     >
>     >
>     > _
>     > _
>     >
>     > _
>     > _
>     >
>     > _
>     > _
>     >
>     >
>     > _
>     > _
>     > _
>     > _
>     >
>     >
>     >
>     > _______________________________________________
>     > hrpc mailing list
>     > hrpc@irtf.org <mailto:hrpc@irtf.org>
>     >
>     https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/h=
rpc__;!!KwNVnqRv!RUZdCcJt8Ap1Rd6uZryyfmW8H5VGuVrmDYRRl9SFgVzE7xWxLLyDMfrZ=
oGjVnA$
>=20
>     >
>=20


From nobody Tue Feb 16 09:18:15 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 6AB713A0C6C for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 09:18:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 2PHcjsHaejw6 for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 09:18:11 -0800 (PST)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 7D9D13A0C5D for <hrpc@irtf.org>; Tue, 16 Feb 2021 09:18:11 -0800 (PST)
Received: by mail-qt1-x82d.google.com with SMTP id d3so7553568qtr.10 for <hrpc@irtf.org>; Tue, 16 Feb 2021 09:18:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=message-id:date:mime-version:user-agent:content-language:to:cc :references:from:subject:in-reply-to:content-transfer-encoding; bh=tKyLCjFtLlnxE3HrK+KETfAqEbRMN3sWXvM6IAhtFAU=; b=PjRaJ33vH9+7qAinapJ/ZllHUeDoYGoQFFO8vL8G0iQn++1kQs7CfA4uAoGQnaM0WQ lM6GouyqZSJk6nLXp4zznMCuLnDjufuC4MUkvBLDnmClvvwq95oD2Fb3Cb1MD24m2hFn /MfOyIRuknjl+PJb9WOQyEEQsZ/Qy8e55hKVo=
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 :content-language:to:cc:references:from:subject:in-reply-to :content-transfer-encoding; bh=tKyLCjFtLlnxE3HrK+KETfAqEbRMN3sWXvM6IAhtFAU=; b=uZrF4/C50bKYNHGTynEIF0tjehB+MUEEYenTOihZRwbVtTsA24qv2l9Yt75n3eb3f2 EQ9EbZN+qVQsI0GmurF6LnWLHPd/nxzsVmClp5h16I6culKes2DUVpSCnnNsqOCs0Xi1 SCCI2oJwHth6Ty6EpHR3uQFJzGaVrQNr/bG4+GmcH2Np7i9vPRZnF2VUoV32jwG/tWFs +W9LtMgj3xjjM88jTVSuuDUK0WCXjfyMu4ClDCZHxlWisiPczepq/gtWj07F2p8hIGy8 gscC/rfcfh2tipUeZNeblNt3eZLj5f9p6wjEQi848Ek9oyKZt4Y+OOmDFxdhU7lCRGzW /Iog==
X-Gm-Message-State: AOAM531pIrY2jyaP7JmblEQ/yik7QyCLAqepQYHjHjaFZge/aBYqdH+5 I5A69bUBj1yvRpQF4goTxTQJuS3vPEpo+z1v
X-Google-Smtp-Source: ABdhPJw2A4OgQJGF8OKbJqAN7eRHOOrxsoFS1D7pGvqoE4FlMYvjEJ0fcwi9AfaQ9o6zxR2GJJrM5A==
X-Received: by 2002:aed:2705:: with SMTP id n5mr19789237qtd.36.1613495888004;  Tue, 16 Feb 2021 09:18:08 -0800 (PST)
Received: from Mallorys-MacBook-Air.local (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with UTF8SMTPSA id f188sm14917195qkj.110.2021.02.16.09.18.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Feb 2021 09:18:07 -0800 (PST)
Message-ID: <584dbeea-0d2d-e69d-7272-37b847d35378@cdt.org>
Date: Tue, 16 Feb 2021 12:18:06 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Thunderbird/86.0
Content-Language: en-US
To: hrpc-chairs@ietf.org
Cc: hrpc@irtf.org
References: <161317641831.31337.4309993755292090373@ietfa.amsl.com>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <161317641831.31337.4309993755292090373@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Z7kWdvlrr01S_8_5RfbL91kzg2U>
Subject: [hrpc] agenda items Re: hrpc - Requested session has been scheduled for IETF 110
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: Tue, 16 Feb 2021 17:18:13 -0000

Hi everyone,

This is a draft agenda and call for additional agenda items:

----

      Agenda HRPC IETF 110

# Welcome and introduction (~0 minutes)

    Scribe, Note takers
    Agenda Review
    Research Group status

# Talk: JoAnne Yates and Craig Murphy (30 minutes)

    "Engineering Rules"

# Talk: Sebastian Benthall (30 minutes)

    "BigBang: Mailing list analysis tool"

# Update: Guidelines draft and short presentations from reviewers (20 
minutes)

    draft-irtf-hrpc-guidelines, Gurshabad Grover

# AOB

    TBD
----

If you're on the agenda, I'll need slides the night before to make sure 
we have a backup plan for slide progression, eg me!

Thanks,

-Mallory


On 2/12/21 7:33 PM, "IETF Secretariat" wrote:
> Dear Mallory Knodel,
>
> The session(s) that you have requested have been scheduled.
> Below is the scheduled session information followed by
> the original request.
>
>
>      hrpc Session 1 (2:00 requested)
>      Thursday, 11 March 2021, Session III 1700-1900
>      Room Name: Room 3 size: 503
>      ---------------------------------------------
>
>
> iCalendar: https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics
>
> Request Information:
>
>
> ---------------------------------------------------------
> Working Group Name: Human Rights Protocol Considerations
> Area Name: IRTF
> Session Requester: Mallory Knodel
>
>
> 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 regext
>   Key Participant Conflict: dnsop
>
>
>
>
>
> People who must be present:
>    Avri Doria
>    Mallory Knodel
>
> Resources Requested:
>
> Special Requests:
>    
> ---------------------------------------------------------
>
>
-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780


From nobody Tue Feb 16 09:18:38 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 AEC453A0C5D for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 09:18:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 4D3aw_a6E5yA for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 09:18:34 -0800 (PST)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 2EC933A0D6F for <hrpc@irtf.org>; Tue, 16 Feb 2021 09:18:24 -0800 (PST)
Received: by mail-qv1-xf2b.google.com with SMTP id e9so5006782qvy.3 for <hrpc@irtf.org>; Tue, 16 Feb 2021 09:18:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=message-id:date:mime-version:user-agent:content-language:to:cc :references:from:subject:in-reply-to:content-transfer-encoding; bh=tKyLCjFtLlnxE3HrK+KETfAqEbRMN3sWXvM6IAhtFAU=; b=Syw1HUDHlgWwYGs2TeD/lFRVaBvVra31o+eYm+/lG3mZePBY7rg/lMoRK9PAc8M1C0 Hkx7wMKXbP9T9mC55EPyUy7m1gXxfB8/YDmN3RMrGLQcMoZ6xADFEyTgN3fGOO8pQsgz SHAP6WhCqZY93q6/K5lf0LrtzPNxxE0VmcigU=
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 :content-language:to:cc:references:from:subject:in-reply-to :content-transfer-encoding; bh=tKyLCjFtLlnxE3HrK+KETfAqEbRMN3sWXvM6IAhtFAU=; b=Eza3f0xDvHPbR/W9YmH69gy+oUt1yTJcOOttY3rdZBaI4teXDiHTsnh1SbeeM8a86k Id6sZJ3uaOihPNgObN/rddHhfqHH6aMsj+wMj2krREToaSF5kFFiJcfCefuS2Hlw/wqa EMk4yuY4WW+jMGpICeW8bXG6imNiDpWfgB83iWFLO9uUE7hHabbSrayD6DmxUCROHzkP QI3PNu5RY9UTzSk3huppdgq4A4qtxMrFBS6U1DmsfaPPufkVn0RBK30UqEo6scwTUZMf I+x7L4S9PgIdE/+FvK1JKg6uniBi9cqdKlCRjhHfxAAbYICX9d5owy6KBMmHLkAJ7Ojh BiEQ==
X-Gm-Message-State: AOAM531SvuheLfz2I1hW3cToYmFBTG7KV8kO50bwTtN3LpoGtTvMKaQk l85KmsuzkPE/F0h5JDdVtioH5oN/UylHAWMr
X-Google-Smtp-Source: ABdhPJwhIRZ/pTmrtMYg2nfOdAqnE3YJipshj7RYTOZWiDyZf9QSq7Wu+wJLNAvnfFES14e3TJ6jPw==
X-Received: by 2002:a0c:b617:: with SMTP id f23mr20259233qve.44.1613495902581;  Tue, 16 Feb 2021 09:18:22 -0800 (PST)
Received: from Mallorys-MacBook-Air.local (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with UTF8SMTPSA id m186sm14597844qkd.111.2021.02.16.09.18.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Feb 2021 09:18:22 -0800 (PST)
Message-ID: <086685f1-d59b-3241-71b9-51ac6be04a66@cdt.org>
Date: Tue, 16 Feb 2021 12:18:21 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Thunderbird/86.0
Content-Language: en-US
To: hrpc-chairs@ietf.org
Cc: hrpc@irtf.org
References: <161317641831.31337.4309993755292090373@ietfa.amsl.com>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <161317641831.31337.4309993755292090373@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Lg3DBEfkg1YsdXxPsUstszglATY>
Subject: [hrpc] agenda items Re: hrpc - Requested session has been scheduled for IETF 110
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: Tue, 16 Feb 2021 17:18:37 -0000

Hi everyone,

This is a draft agenda and call for additional agenda items:

----

      Agenda HRPC IETF 110

# Welcome and introduction (~0 minutes)

    Scribe, Note takers
    Agenda Review
    Research Group status

# Talk: JoAnne Yates and Craig Murphy (30 minutes)

    "Engineering Rules"

# Talk: Sebastian Benthall (30 minutes)

    "BigBang: Mailing list analysis tool"

# Update: Guidelines draft and short presentations from reviewers (20 
minutes)

    draft-irtf-hrpc-guidelines, Gurshabad Grover

# AOB

    TBD
----

If you're on the agenda, I'll need slides the night before to make sure 
we have a backup plan for slide progression, eg me!

Thanks,

-Mallory


On 2/12/21 7:33 PM, "IETF Secretariat" wrote:
> Dear Mallory Knodel,
>
> The session(s) that you have requested have been scheduled.
> Below is the scheduled session information followed by
> the original request.
>
>
>      hrpc Session 1 (2:00 requested)
>      Thursday, 11 March 2021, Session III 1700-1900
>      Room Name: Room 3 size: 503
>      ---------------------------------------------
>
>
> iCalendar: https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics
>
> Request Information:
>
>
> ---------------------------------------------------------
> Working Group Name: Human Rights Protocol Considerations
> Area Name: IRTF
> Session Requester: Mallory Knodel
>
>
> 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 regext
>   Key Participant Conflict: dnsop
>
>
>
>
>
> People who must be present:
>    Avri Doria
>    Mallory Knodel
>
> Resources Requested:
>
> Special Requests:
>    
> ---------------------------------------------------------
>
>
-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780


From nobody Tue Feb 16 12:08:44 2021
Return-Path: <braman@tamu.edu>
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 CC20B3A1056 for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 12:08:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 (2048-bit key) header.d=tamu-edu.20150623.gappssmtp.com
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 MAQFL54A0V5w for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 12:08:40 -0800 (PST)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 D73883A1052 for <hrpc@irtf.org>; Tue, 16 Feb 2021 12:08:39 -0800 (PST)
Received: by mail-il1-x12f.google.com with SMTP id a16so9354559ilq.5 for <hrpc@irtf.org>; Tue, 16 Feb 2021 12:08:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tamu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=46DfUG+bvMh3wsZZXHOLeVsN+9Xyb+8NyLnTbfR/En4=; b=ilOY3Y4WAYDYE/RonIayK0C4B3WLjs2eB3P35YxjjJao7DUtson82EWAhI3yrTpb1q EE+v5Wu8g8RY1fJ7XQ3agF4wTefxifNw294no/iRzcn7fF8YzJCxiXUdxsDAxgT3fsuV jMF1KWzDE4Hfh8GgyEWOX8xWovIJpKGHYCSCC15mfdUnxwURkzqlTJiLBNHqyjmBsxy0 TxloX36/1LAqSl31uPIokxy4gczwisJ1G4nuLEfonbtYiZEbm7kniwjNbRJV+EMwUV2b F6m+XEt7zehhoqtouqJv/gAGpLUcEyTgXPDd0RKCJGbnsbQ121FKTbC3DNOKkl5Nupv5 tMcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=46DfUG+bvMh3wsZZXHOLeVsN+9Xyb+8NyLnTbfR/En4=; b=tBQfDKmLP76xB72RQCpOifgwDG4g2pKhEd/RvQwqSfKuQRqOCh3YetBDTUueGzvYoX pYg3TfAejD8rzKHLxY1CnCeatRCJknxvgmatFu4Tb2m5RAzVMhlMfdo4Wbh1rDGDXHuw hnbY4XJzlxlN+3TyiHtzEt4cwQ8hzSa4Roiix/DoNjloYW1UJMHN3m/h1UGAGxBz5baz ZPtoGM6fMAq0dXFc79kFiictRuA+U/ehxzwIS2yB5rku8sGVaL06Jt6YQ1Hf3OhDa3T7 r/H6SP1YuV2lg/jPIq5PKqCLNiO847yHPi5+UbtW0b0vg1QniHCemM1Limq+R5WNTNFR rfkQ==
X-Gm-Message-State: AOAM530khQ7xt2eq8B3qNABtv+Q9hY6WzkH6jEFeoelvIdhV+r5xs6xs fKCM84Ska6YYxyH5YghzUT/e6RkwtzSKZLQmJaV4KFsYqbo=
X-Google-Smtp-Source: ABdhPJzuXEM3ZVkq5+XY1HwEIG7bl6zYetRm5lu6C6n0YRPO5nN7/lunDgHxI5NQX+Q7o+0ybmlIWe0KNmD5STQXSbM=
X-Received: by 2002:a05:6e02:1be1:: with SMTP id y1mr17912068ilv.101.1613506118534;  Tue, 16 Feb 2021 12:08:38 -0800 (PST)
MIME-Version: 1.0
References: <mailman.76.1613505612.27842.hrpc@irtf.org>
In-Reply-To: <mailman.76.1613505612.27842.hrpc@irtf.org>
From: Sandra Braman <braman@tamu.edu>
Date: Tue, 16 Feb 2021 14:08:27 -0600
Message-ID: <CAB2unbMpgGX18qdy3BsSURT5ZD4b67HemRqAWARezD=wCb13eg@mail.gmail.com>
To: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="00000000000009decd05bb79abbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/0ffJ4gyHK9YZo6s25oCm93HaoL8>
Subject: Re: [hrpc] hrpc Digest, Vol 71, Issue 22
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: Tue, 16 Feb 2021 20:08:43 -0000

--00000000000009decd05bb79abbc
Content-Type: text/plain; charset="UTF-8"

Thanks for setting this up, Mallory.  Two questions:

Draft guidelines is on the agenda but draft association is not because a
new draft is in the works for the former and not for the latter?

And who among those who reviewed draft guidelines will be providing
comments?  I am among those who provided extensive comments on the most
recent draft made available who will be at the meeting.

Thanks -

Sandra Braman


On Tue, Feb 16, 2021 at 2:01 PM <hrpc-request@irtf.org> wrote:

> Send hrpc mailing list submissions to
>         hrpc@irtf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$
> or, via email, send a message with subject or body 'help' to
>         hrpc-request@irtf.org
>
> You can reach the person managing the list at
>         hrpc-owner@irtf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of hrpc digest..."
> Today's Topics:
>
>    1. agenda items Re: hrpc - Requested session has been scheduled
>       for IETF 110 (Mallory Knodel)
>    2. agenda items Re: hrpc - Requested session has been scheduled
>       for IETF 110 (Mallory Knodel)
>
>
>
> ---------- Forwarded message ----------
> From: Mallory Knodel <mknodel@cdt.org>
> To: hrpc-chairs@ietf.org
> Cc: hrpc@irtf.org
> Bcc:
> Date: Tue, 16 Feb 2021 12:18:06 -0500
> Subject: [hrpc] agenda items Re: hrpc - Requested session has been
> scheduled for IETF 110
> Hi everyone,
>
> This is a draft agenda and call for additional agenda items:
>
> ----
>
>       Agenda HRPC IETF 110
>
> # Welcome and introduction (~0 minutes)
>
>     Scribe, Note takers
>     Agenda Review
>     Research Group status
>
> # Talk: JoAnne Yates and Craig Murphy (30 minutes)
>
>     "Engineering Rules"
>
> # Talk: Sebastian Benthall (30 minutes)
>
>     "BigBang: Mailing list analysis tool"
>
> # Update: Guidelines draft and short presentations from reviewers (20
> minutes)
>
>     draft-irtf-hrpc-guidelines, Gurshabad Grover
>
> # AOB
>
>     TBD
> ----
>
> If you're on the agenda, I'll need slides the night before to make sure
> we have a backup plan for slide progression, eg me!
>
> Thanks,
>
> -Mallory
>
>
> On 2/12/21 7:33 PM, "IETF Secretariat" wrote:
> > Dear Mallory Knodel,
> >
> > The session(s) that you have requested have been scheduled.
> > Below is the scheduled session information followed by
> > the original request.
> >
> >
> >      hrpc Session 1 (2:00 requested)
> >      Thursday, 11 March 2021, Session III 1700-1900
> >      Room Name: Room 3 size: 503
> >      ---------------------------------------------
> >
> >
> > iCalendar:
> https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$
> >
> > Request Information:
> >
> >
> > ---------------------------------------------------------
> > Working Group Name: Human Rights Protocol Considerations
> > Area Name: IRTF
> > Session Requester: Mallory Knodel
> >
> >
> > 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 regext
> >   Key Participant Conflict: dnsop
> >
> >
> >
> >
> >
> > People who must be present:
> >    Avri Doria
> >    Mallory Knodel
> >
> > Resources Requested:
> >
> > Special Requests:
> >
> > ---------------------------------------------------------
> >
> >
> --
> Mallory Knodel
> CTO, Center for Democracy and Technology
> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Mallory Knodel <mknodel@cdt.org>
> To: hrpc-chairs@ietf.org
> Cc: hrpc@irtf.org
> Bcc:
> Date: Tue, 16 Feb 2021 12:18:21 -0500
> Subject: [hrpc] agenda items Re: hrpc - Requested session has been
> scheduled for IETF 110
> Hi everyone,
>
> This is a draft agenda and call for additional agenda items:
>
> ----
>
>       Agenda HRPC IETF 110
>
> # Welcome and introduction (~0 minutes)
>
>     Scribe, Note takers
>     Agenda Review
>     Research Group status
>
> # Talk: JoAnne Yates and Craig Murphy (30 minutes)
>
>     "Engineering Rules"
>
> # Talk: Sebastian Benthall (30 minutes)
>
>     "BigBang: Mailing list analysis tool"
>
> # Update: Guidelines draft and short presentations from reviewers (20
> minutes)
>
>     draft-irtf-hrpc-guidelines, Gurshabad Grover
>
> # AOB
>
>     TBD
> ----
>
> If you're on the agenda, I'll need slides the night before to make sure
> we have a backup plan for slide progression, eg me!
>
> Thanks,
>
> -Mallory
>
>
> On 2/12/21 7:33 PM, "IETF Secretariat" wrote:
> > Dear Mallory Knodel,
> >
> > The session(s) that you have requested have been scheduled.
> > Below is the scheduled session information followed by
> > the original request.
> >
> >
> >      hrpc Session 1 (2:00 requested)
> >      Thursday, 11 March 2021, Session III 1700-1900
> >      Room Name: Room 3 size: 503
> >      ---------------------------------------------
> >
> >
> > iCalendar:
> https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$
> >
> > Request Information:
> >
> >
> > ---------------------------------------------------------
> > Working Group Name: Human Rights Protocol Considerations
> > Area Name: IRTF
> > Session Requester: Mallory Knodel
> >
> >
> > 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 regext
> >   Key Participant Conflict: dnsop
> >
> >
> >
> >
> >
> > People who must be present:
> >    Avri Doria
> >    Mallory Knodel
> >
> > Resources Requested:
> >
> > Special Requests:
> >
> > ---------------------------------------------------------
> >
> >
> --
> Mallory Knodel
> CTO, Center for Democracy and Technology
> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
>
> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$
>

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

<div><div dir=3D"auto">Thanks for setting this up, Mallory.=C2=A0 Two quest=
ions: =C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Draft guide=
lines is on the agenda but draft association is not because a new draft is =
in the works for the former and not for the latter? =C2=A0</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">And who among those who reviewed draft g=
uidelines will be providing comments?=C2=A0 I am among those who provided e=
xtensive comments on the most recent draft made available who will be at th=
e meeting.</div></div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks =
-</div><div dir=3D"auto"><br></div><div dir=3D"auto">Sandra Braman</div><di=
v dir=3D"auto"><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Tue, Feb 16, 2021 at 2:01 PM &lt;<a href=3D"mail=
to:hrpc-request@irtf.org">hrpc-request@irtf.org</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">Send hrpc mailing list submissions to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc@irtf.org" target=3D"_bla=
nk">hrpc@irtf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://urldefense.com/v3/__https://=
www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7=
L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$" rel=3D"noreferrer" target=3D"_bl=
ank">https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc=
__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyf=
iVdzvY$</a> <br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-request@irtf.org" target=
=3D"_blank">hrpc-request@irtf.org</a><br>
<br>
You can reach the person managing the list at<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:hrpc-owner@irtf.org" target=
=3D"_blank">hrpc-owner@irtf.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of hrpc digest...&quot;<br>
Today&#39;s Topics:<br>
<br>
=C2=A0 =C2=A01. agenda items Re: hrpc - Requested session has been schedule=
d<br>
=C2=A0 =C2=A0 =C2=A0 for IETF 110 (Mallory Knodel)<br>
=C2=A0 =C2=A02. agenda items Re: hrpc - Requested session has been schedule=
d<br>
=C2=A0 =C2=A0 =C2=A0 for IETF 110 (Mallory Knodel)<br>
<br><br><br>---------- Forwarded message ----------<br>From:=C2=A0Mallory K=
nodel &lt;<a href=3D"mailto:mknodel@cdt.org" target=3D"_blank">mknodel@cdt.=
org</a>&gt;<br>To:=C2=A0<a href=3D"mailto:hrpc-chairs@ietf.org" target=3D"_=
blank">hrpc-chairs@ietf.org</a><br>Cc:=C2=A0<a href=3D"mailto:hrpc@irtf.org=
" target=3D"_blank">hrpc@irtf.org</a><br>Bcc:=C2=A0<br>Date:=C2=A0Tue, 16 F=
eb 2021 12:18:06 -0500<br>Subject:=C2=A0[hrpc] agenda items Re: hrpc - Requ=
ested session has been scheduled for IETF 110<br>Hi everyone,<br>
<br>
This is a draft agenda and call for additional agenda items:<br>
<br>
----<br>
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Agenda HRPC IETF 110<br>
<br>
# Welcome and introduction (~0 minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0Scribe, Note takers<br>
=C2=A0=C2=A0 =C2=A0Agenda Review<br>
=C2=A0=C2=A0 =C2=A0Research Group status<br>
<br>
# Talk: JoAnne Yates and Craig Murphy (30 minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0&quot;Engineering Rules&quot;<br>
<br>
# Talk: Sebastian Benthall (30 minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0&quot;BigBang: Mailing list analysis tool&quot;<br>
<br>
# Update: Guidelines draft and short presentations from reviewers (20 <br>
minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0draft-irtf-hrpc-guidelines, Gurshabad Grover<br>
<br>
# AOB<br>
<br>
=C2=A0=C2=A0 =C2=A0TBD<br>
----<br>
<br>
If you&#39;re on the agenda, I&#39;ll need slides the night before to make =
sure <br>
we have a backup plan for slide progression, eg me!<br>
<br>
Thanks,<br>
<br>
-Mallory<br>
<br>
<br>
On 2/12/21 7:33 PM, &quot;IETF Secretariat&quot; wrote:<br>
&gt; Dear Mallory Knodel,<br>
&gt;<br>
&gt; The session(s) that you have requested have been scheduled.<br>
&gt; Below is the scheduled session information followed by<br>
&gt; the original request.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 hrpc Session 1 (2:00 requested)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 Thursday, 11 March 2021, Session III 1700-1900<br>
&gt;=C2=A0 =C2=A0 =C2=A0 Room Name: Room 3 size: 503<br>
&gt;=C2=A0 =C2=A0 =C2=A0 ---------------------------------------------<br>
&gt;<br>
&gt;<br>
&gt; iCalendar: <a href=3D"https://urldefense.com/v3/__https://datatracker.=
ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBm=
Dwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$" rel=3D"noreferrer" target=3D=
"_blank">https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/1=
10/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTy=
Tj-368C-uLiv25mD9uyo2MzUjg$</a> <br>
&gt;<br>
&gt; Request Information:<br>
&gt;<br>
&gt;<br>
&gt; ---------------------------------------------------------<br>
&gt; Working Group Name: Human Rights Protocol Considerations<br>
&gt; Area Name: IRTF<br>
&gt; Session Requester: Mallory Knodel<br>
&gt;<br>
&gt;<br>
&gt; Number of Sessions: 1<br>
&gt; Length of Session(s):=C2=A0 2 Hours<br>
&gt; Number of Attendees: 100<br>
&gt; Conflicts to Avoid:<br>
&gt;=C2=A0 =C2=A0Chair Conflict: dprive gaia irtfopen pearg<br>
&gt;=C2=A0 =C2=A0Technology Overlap: mls regext<br>
&gt;=C2=A0 =C2=A0Key Participant Conflict: dnsop<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; People who must be present:<br>
&gt;=C2=A0 =C2=A0 Avri Doria<br>
&gt;=C2=A0 =C2=A0 Mallory Knodel<br>
&gt;<br>
&gt; Resources Requested:<br>
&gt;<br>
&gt; Special Requests:<br>
&gt;=C2=A0 =C2=A0 <br>
&gt; ---------------------------------------------------------<br>
&gt;<br>
&gt;<br>
-- <br>
Mallory Knodel<br>
CTO, Center for Democracy and Technology<br>
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780<br>
<br>
<br>
<br><br><br>---------- Forwarded message ----------<br>From:=C2=A0Mallory K=
nodel &lt;<a href=3D"mailto:mknodel@cdt.org" target=3D"_blank">mknodel@cdt.=
org</a>&gt;<br>To:=C2=A0<a href=3D"mailto:hrpc-chairs@ietf.org" target=3D"_=
blank">hrpc-chairs@ietf.org</a><br>Cc:=C2=A0<a href=3D"mailto:hrpc@irtf.org=
" target=3D"_blank">hrpc@irtf.org</a><br>Bcc:=C2=A0<br>Date:=C2=A0Tue, 16 F=
eb 2021 12:18:21 -0500<br>Subject:=C2=A0[hrpc] agenda items Re: hrpc - Requ=
ested session has been scheduled for IETF 110<br>Hi everyone,<br>
<br>
This is a draft agenda and call for additional agenda items:<br>
<br>
----<br>
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Agenda HRPC IETF 110<br>
<br>
# Welcome and introduction (~0 minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0Scribe, Note takers<br>
=C2=A0=C2=A0 =C2=A0Agenda Review<br>
=C2=A0=C2=A0 =C2=A0Research Group status<br>
<br>
# Talk: JoAnne Yates and Craig Murphy (30 minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0&quot;Engineering Rules&quot;<br>
<br>
# Talk: Sebastian Benthall (30 minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0&quot;BigBang: Mailing list analysis tool&quot;<br>
<br>
# Update: Guidelines draft and short presentations from reviewers (20 <br>
minutes)<br>
<br>
=C2=A0=C2=A0 =C2=A0draft-irtf-hrpc-guidelines, Gurshabad Grover<br>
<br>
# AOB<br>
<br>
=C2=A0=C2=A0 =C2=A0TBD<br>
----<br>
<br>
If you&#39;re on the agenda, I&#39;ll need slides the night before to make =
sure <br>
we have a backup plan for slide progression, eg me!<br>
<br>
Thanks,<br>
<br>
-Mallory<br>
<br>
<br>
On 2/12/21 7:33 PM, &quot;IETF Secretariat&quot; wrote:<br>
&gt; Dear Mallory Knodel,<br>
&gt;<br>
&gt; The session(s) that you have requested have been scheduled.<br>
&gt; Below is the scheduled session information followed by<br>
&gt; the original request.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 hrpc Session 1 (2:00 requested)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 Thursday, 11 March 2021, Session III 1700-1900<br>
&gt;=C2=A0 =C2=A0 =C2=A0 Room Name: Room 3 size: 503<br>
&gt;=C2=A0 =C2=A0 =C2=A0 ---------------------------------------------<br>
&gt;<br>
&gt;<br>
&gt; iCalendar: <a href=3D"https://urldefense.com/v3/__https://datatracker.=
ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBm=
Dwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$" rel=3D"noreferrer" target=3D=
"_blank">https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/1=
10/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTy=
Tj-368C-uLiv25mD9uyo2MzUjg$</a> <br>
&gt;<br>
&gt; Request Information:<br>
&gt;<br>
&gt;<br>
&gt; ---------------------------------------------------------<br>
&gt; Working Group Name: Human Rights Protocol Considerations<br>
&gt; Area Name: IRTF<br>
&gt; Session Requester: Mallory Knodel<br>
&gt;<br>
&gt;<br>
&gt; Number of Sessions: 1<br>
&gt; Length of Session(s):=C2=A0 2 Hours<br>
&gt; Number of Attendees: 100<br>
&gt; Conflicts to Avoid:<br>
&gt;=C2=A0 =C2=A0Chair Conflict: dprive gaia irtfopen pearg<br>
&gt;=C2=A0 =C2=A0Technology Overlap: mls regext<br>
&gt;=C2=A0 =C2=A0Key Participant Conflict: dnsop<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; People who must be present:<br>
&gt;=C2=A0 =C2=A0 Avri Doria<br>
&gt;=C2=A0 =C2=A0 Mallory Knodel<br>
&gt;<br>
&gt; Resources Requested:<br>
&gt;<br>
&gt; Special Requests:<br>
&gt;=C2=A0 =C2=A0 <br>
&gt; ---------------------------------------------------------<br>
&gt;<br>
&gt;<br>
-- <br>
Mallory Knodel<br>
CTO, Center for Democracy and Technology<br>
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780<br>
<br>
<br>
_______________________________________________<br>
hrpc mailing list<br>
<a href=3D"mailto:hrpc@irtf.org" target=3D"_blank">hrpc@irtf.org</a><br>
<a href=3D"https://urldefense.com/v3/__https://www.irtf.org/mailman/listinf=
o/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25=
mD9uyfiVdzvY$" rel=3D"noreferrer" target=3D"_blank">https://urldefense.com/=
v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcEr=
R4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$</a> <br>
</blockquote></div></div>

--00000000000009decd05bb79abbc--


From nobody Tue Feb 16 12:31:46 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 7FDC93A10B7 for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 12:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 rQ4ZQHvfSlC3 for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 12:31:41 -0800 (PST)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 81DC03A10B1 for <hrpc@irtf.org>; Tue, 16 Feb 2021 12:31:41 -0800 (PST)
Received: by mail-qt1-x831.google.com with SMTP id z32so7999888qtd.8 for <hrpc@irtf.org>; Tue, 16 Feb 2021 12:31:41 -0800 (PST)
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:to :references:from:in-reply-to; bh=5rgwLPRPpDmF3XmDVtc2ucaUIefiUoukKSWTAZoqh2w=; b=LD/J1rlpU41Ju8QosH5jWfHlUfLW3r17/nHCJMGOQVk49HmEj+Aouse4ZD+qHMVoUH mD+Z8UvvNL7COID3W4LugoPa51cUf66rZAvoIdK/3z6p041E6kkvA3b8zQVDac0hj35J PXaG3L/KLMrMOlp3sPFKrSGdpzHC7Lo54FdLw=
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:to:references:from:in-reply-to; bh=5rgwLPRPpDmF3XmDVtc2ucaUIefiUoukKSWTAZoqh2w=; b=JxuJH8RJWOuX17A/axKEpA0cpjTNRV26vyknRpIiMBXPJS2Sf+Np4c5ZmUPd7/BBJ4 G2CXAnHoTd9xUVe/FeyOVsVJUMOZToPuMXJWJ0Qorl67iKp8ROdfZcXKJ3QGvbnh289B WtlWTfuXHIshW6K4ej4uelfl8A6Fqk3zxirm5l61SLpV+rsvepFTtXWOQVOCRyFyD+Z7 k8/g18o1KmLiuDaLWjlSm6KQ38zeTfAdgjrj6KuF7FYrzwvLMaHVhb1LQPjCc0ktnmvt Ml8tQZXfbwwztaycWl/8aVKHPfg/sIUtpmEIviZBBYsfya7whFlNedldDoMc31LQx0Iz 2BXg==
X-Gm-Message-State: AOAM5325y/zUJOSUkNTLBwD0DZq3a5+XmNbWikf/eGDo7Dm32cz3f1J1 TQZX6W890dV08GCBQBJvphSHsKhsbitOqLwt
X-Google-Smtp-Source: ABdhPJzfb345hnhWnBtnZeYJ9qYm/X1yo2Q2h2Cxiv0ML1wGeDkxVKv5c04u4lPOuFrl1U03uOW/0g==
X-Received: by 2002:a05:622a:2d6:: with SMTP id a22mr20448227qtx.111.1613507499952;  Tue, 16 Feb 2021 12:31:39 -0800 (PST)
Received: from Mallorys-MacBook-Air.local (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with UTF8SMTPSA id w143sm20760qka.58.2021.02.16.12.31.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Feb 2021 12:31:39 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------PfGA1pKcOJDuwtYAaoEnuobJ"
Message-ID: <81973033-4853-a655-ffb5-892096dc5479@cdt.org>
Date: Tue, 16 Feb 2021 15:31:38 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Thunderbird/86.0
Content-Language: en-US
To: Sandra Braman <braman@tamu.edu>, hrpc@irtf.org
References: <mailman.76.1613505612.27842.hrpc@irtf.org> <CAB2unbMpgGX18qdy3BsSURT5ZD4b67HemRqAWARezD=wCb13eg@mail.gmail.com>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <CAB2unbMpgGX18qdy3BsSURT5ZD4b67HemRqAWARezD=wCb13eg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/sdR_3Vx9C0e-CJz9uGyrNYK5n1Q>
Subject: Re: [hrpc] hrpc Digest, Vol 71, Issue 22
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: Tue, 16 Feb 2021 20:31:45 -0000

This is a multi-part message in MIME format.
--------------PfGA1pKcOJDuwtYAaoEnuobJ
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Sandra,

On 2/16/21 3:08 PM, Sandra Braman wrote:
> Thanks for setting this up, Mallory.  Two questions: Â
>
> Draft guidelines is on the agenda but draft association is not because 
> a new draft is in the works for the former and not for the latter?Â
I would like draft association to be on the agenda but it depends on 
whether or not the co-authors have a new version and/or want to talk 
about it. I am only one of the co-authors and so at this point it 
remains to be seen.
>
> And who among those who reviewed draft guidelines will be providing 
> comments?  I am among those who provided extensive comments on the 
> most recent draft made available who will be at the meeting.

I can't speak specifically but generally if a comment has been made then 
the authors will have already treated it somehow. For the 110 agenda, 
the current authors will be presenting but I'm also not yet sure if 
there will be a new document version available by then. There will be 
Q&A in any case.

HTH,

-Mallory

>
> Thanks -
>
> Sandra Braman
>
>
> On Tue, Feb 16, 2021 at 2:01 PM <hrpc-request@irtf.org 
> <mailto:hrpc-request@irtf.org>> wrote:
>
>     Send hrpc mailing list submissions to
>           Â hrpc@irtf.org <mailto:hrpc@irtf.org>
>
>     To subscribe or unsubscribe via the World Wide Web, visit
>           Â
>     https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$
>     <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$>
>
>     or, via email, send a message with subject or body 'help' to
>           Â hrpc-request@irtf.org <mailto:hrpc-request@irtf.org>
>
>     You can reach the person managing the list at
>           Â hrpc-owner@irtf.org <mailto:hrpc-owner@irtf.org>
>
>     When replying, please edit your Subject line so it is more specific
>     than "Re: Contents of hrpc digest..."
>     Today's Topics:
>
>        1. agenda items Re: hrpc - Requested session has been scheduled
>           for IETF 110 (Mallory Knodel)
>        2. agenda items Re: hrpc - Requested session has been scheduled
>           for IETF 110 (Mallory Knodel)
>
>
>
>     ---------- Forwarded message ----------
>     From: Mallory Knodel <mknodel@cdt.org <mailto:mknodel@cdt.org>>
>     To:Â hrpc-chairs@ietf.org <mailto:hrpc-chairs@ietf.org>
>     Cc:Â hrpc@irtf.org <mailto:hrpc@irtf.org>
>     Bcc:Â
>     Date: Tue, 16 Feb 2021 12:18:06 -0500
>     Subject: [hrpc] agenda items Re: hrpc - Requested session has
>     been scheduled for IETF 110
>     Hi everyone,
>
>     This is a draft agenda and call for additional agenda items:
>
>     ----
>
>           Agenda HRPC IETF 110
>
>     # Welcome and introduction (~0 minutes)
>
>         Scribe, Note takers
>         Agenda Review
>         Research Group status
>
>     # Talk: JoAnne Yates and Craig Murphy (30 minutes)
>
>         "Engineering Rules"
>
>     # Talk: Sebastian Benthall (30 minutes)
>
>         "BigBang: Mailing list analysis tool"
>
>     # Update: Guidelines draft and short presentations from reviewers (20
>     minutes)
>
>         draft-irtf-hrpc-guidelines, Gurshabad Grover
>
>     # AOB
>
>         TBD
>     ----
>
>     If you're on the agenda, I'll need slides the night before to make
>     sure
>     we have a backup plan for slide progression, eg me!
>
>     Thanks,
>
>     -Mallory
>
>
>     On 2/12/21 7:33 PM, "IETF Secretariat" wrote:
>     > Dear Mallory Knodel,
>     >
>     > The session(s) that you have requested have been scheduled.
>     > Below is the scheduled session information followed by
>     > the original request.
>     >
>     >
>     >      hrpc Session 1 (2:00 requested)
>     >      Thursday, 11 March 2021, Session III 1700-1900
>     >      Room Name: Room 3 size: 503
>     >      ---------------------------------------------
>     >
>     >
>     > iCalendar:
>     https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$
>     <https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$>
>
>     >
>     > Request Information:
>     >
>     >
>     > ---------------------------------------------------------
>     > Working Group Name: Human Rights Protocol Considerations
>     > Area Name: IRTF
>     > Session Requester: Mallory Knodel
>     >
>     >
>     > 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 regext
>     >   Key Participant Conflict: dnsop
>     >
>     >
>     >
>     >
>     >
>     > People who must be present:
>     >    Avri Doria
>     >    Mallory Knodel
>     >
>     > Resources Requested:
>     >
>     > Special Requests:
>     >  Â
>     > ---------------------------------------------------------
>     >
>     >
>     -- 
>     Mallory Knodel
>     CTO, Center for Democracy and Technology
>     gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>
>
>
>
>
>     ---------- Forwarded message ----------
>     From: Mallory Knodel <mknodel@cdt.org <mailto:mknodel@cdt.org>>
>     To:Â hrpc-chairs@ietf.org <mailto:hrpc-chairs@ietf.org>
>     Cc:Â hrpc@irtf.org <mailto:hrpc@irtf.org>
>     Bcc:Â
>     Date: Tue, 16 Feb 2021 12:18:21 -0500
>     Subject: [hrpc] agenda items Re: hrpc - Requested session has
>     been scheduled for IETF 110
>     Hi everyone,
>
>     This is a draft agenda and call for additional agenda items:
>
>     ----
>
>           Agenda HRPC IETF 110
>
>     # Welcome and introduction (~0 minutes)
>
>         Scribe, Note takers
>         Agenda Review
>         Research Group status
>
>     # Talk: JoAnne Yates and Craig Murphy (30 minutes)
>
>         "Engineering Rules"
>
>     # Talk: Sebastian Benthall (30 minutes)
>
>         "BigBang: Mailing list analysis tool"
>
>     # Update: Guidelines draft and short presentations from reviewers (20
>     minutes)
>
>         draft-irtf-hrpc-guidelines, Gurshabad Grover
>
>     # AOB
>
>         TBD
>     ----
>
>     If you're on the agenda, I'll need slides the night before to make
>     sure
>     we have a backup plan for slide progression, eg me!
>
>     Thanks,
>
>     -Mallory
>
>
>     On 2/12/21 7:33 PM, "IETF Secretariat" wrote:
>     > Dear Mallory Knodel,
>     >
>     > The session(s) that you have requested have been scheduled.
>     > Below is the scheduled session information followed by
>     > the original request.
>     >
>     >
>     >      hrpc Session 1 (2:00 requested)
>     >      Thursday, 11 March 2021, Session III 1700-1900
>     >      Room Name: Room 3 size: 503
>     >      ---------------------------------------------
>     >
>     >
>     > iCalendar:
>     https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$
>     <https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$>
>
>     >
>     > Request Information:
>     >
>     >
>     > ---------------------------------------------------------
>     > Working Group Name: Human Rights Protocol Considerations
>     > Area Name: IRTF
>     > Session Requester: Mallory Knodel
>     >
>     >
>     > 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 regext
>     >   Key Participant Conflict: dnsop
>     >
>     >
>     >
>     >
>     >
>     > People who must be present:
>     >    Avri Doria
>     >    Mallory Knodel
>     >
>     > Resources Requested:
>     >
>     > Special Requests:
>     >  Â
>     > ---------------------------------------------------------
>     >
>     >
>     -- 
>     Mallory Knodel
>     CTO, Center for Democracy and Technology
>     gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>
>
>     _______________________________________________
>     hrpc mailing list
>     hrpc@irtf.org <mailto:hrpc@irtf.org>
>     https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$
>     <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$>
>
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc

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

--------------PfGA1pKcOJDuwtYAaoEnuobJ
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Sandra,</p>
    <div class="moz-cite-prefix">On 2/16/21 3:08 PM, Sandra Braman
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAB2unbMpgGX18qdy3BsSURT5ZD4b67HemRqAWARezD=wCb13eg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div>
        <div dir="auto">Thanks for setting this up, Mallory.  Two
          questions:  </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Draft guidelines is on the agenda but draft
          association is not because a new draft is in the works for the
          former and not for the latter?  <br>
        </div>
      </div>
    </blockquote>
    I would like draft association to be on the agenda but it depends on
    whether or not the co-authors have a new version and/or want to talk
    about it. I am only one of the co-authors and so at this point it
    remains to be seen.
    <blockquote type="cite"
cite="mid:CAB2unbMpgGX18qdy3BsSURT5ZD4b67HemRqAWARezD=wCb13eg@mail.gmail.com">
      <div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">And who among those who reviewed draft
          guidelines will be providing comments?  I am among those who
          provided extensive comments on the most recent draft made
          available who will be at the meeting.</div>
      </div>
    </blockquote>
    <p>I can't speak specifically but generally if a comment has been
      made then the authors will have already treated it somehow. For
      the 110 agenda, the current authors will be presenting but I'm
      also not yet sure if there will be a new document version
      available by then. There will be Q&amp;A in any case. <br>
    </p>
    <p>HTH,<br>
    </p>
    <p>-Mallory<br>
    </p>
    <blockquote type="cite"
cite="mid:CAB2unbMpgGX18qdy3BsSURT5ZD4b67HemRqAWARezD=wCb13eg@mail.gmail.com">
      <div dir="auto"><br>
      </div>
      <div dir="auto">Thanks -</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">Sandra Braman</div>
      <div dir="auto"><br>
      </div>
      <div><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Tue, Feb 16, 2021 at 2:01
            PM &lt;<a href="mailto:hrpc-request@irtf.org"
              moz-do-not-send="true">hrpc-request@irtf.org</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Send hrpc
            mailing list submissions to<br>
                    <a href="mailto:hrpc@irtf.org" target="_blank"
              moz-do-not-send="true">hrpc@irtf.org</a><br>
            <br>
            To subscribe or unsubscribe via the World Wide Web, visit<br>
                    <a
href="https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$</a>
            <br>
            or, via email, send a message with subject or body 'help' to<br>
                    <a href="mailto:hrpc-request@irtf.org"
              target="_blank" moz-do-not-send="true">hrpc-request@irtf.org</a><br>
            <br>
            You can reach the person managing the list at<br>
                    <a href="mailto:hrpc-owner@irtf.org"
              target="_blank" moz-do-not-send="true">hrpc-owner@irtf.org</a><br>
            <br>
            When replying, please edit your Subject line so it is more
            specific<br>
            than "Re: Contents of hrpc digest..."<br>
            Today's Topics:<br>
            <br>
               1. agenda items Re: hrpc - Requested session has been
            scheduled<br>
                  for IETF 110 (Mallory Knodel)<br>
               2. agenda items Re: hrpc - Requested session has been
            scheduled<br>
                  for IETF 110 (Mallory Knodel)<br>
            <br>
            <br>
            <br>
            ---------- Forwarded message ----------<br>
            From: Mallory Knodel &lt;<a href="mailto:mknodel@cdt.org"
              target="_blank" moz-do-not-send="true">mknodel@cdt.org</a>&gt;<br>
            To: <a href="mailto:hrpc-chairs@ietf.org" target="_blank"
              moz-do-not-send="true">hrpc-chairs@ietf.org</a><br>
            Cc: <a href="mailto:hrpc@irtf.org" target="_blank"
              moz-do-not-send="true">hrpc@irtf.org</a><br>
            Bcc: <br>
            Date: Tue, 16 Feb 2021 12:18:06 -0500<br>
            Subject: [hrpc] agenda items Re: hrpc - Requested session
            has been scheduled for IETF 110<br>
            Hi everyone,<br>
            <br>
            This is a draft agenda and call for additional agenda items:<br>
            <br>
            ----<br>
            <br>
                  Agenda HRPC IETF 110<br>
            <br>
            # Welcome and introduction (~0 minutes)<br>
            <br>
                Scribe, Note takers<br>
                Agenda Review<br>
                Research Group status<br>
            <br>
            # Talk: JoAnne Yates and Craig Murphy (30 minutes)<br>
            <br>
                "Engineering Rules"<br>
            <br>
            # Talk: Sebastian Benthall (30 minutes)<br>
            <br>
                "BigBang: Mailing list analysis tool"<br>
            <br>
            # Update: Guidelines draft and short presentations from
            reviewers (20 <br>
            minutes)<br>
            <br>
                draft-irtf-hrpc-guidelines, Gurshabad Grover<br>
            <br>
            # AOB<br>
            <br>
                TBD<br>
            ----<br>
            <br>
            If you're on the agenda, I'll need slides the night before
            to make sure <br>
            we have a backup plan for slide progression, eg me!<br>
            <br>
            Thanks,<br>
            <br>
            -Mallory<br>
            <br>
            <br>
            On 2/12/21 7:33 PM, "IETF Secretariat" wrote:<br>
            &gt; Dear Mallory Knodel,<br>
            &gt;<br>
            &gt; The session(s) that you have requested have been
            scheduled.<br>
            &gt; Below is the scheduled session information followed by<br>
            &gt; the original request.<br>
            &gt;<br>
            &gt;<br>
            &gt;      hrpc Session 1 (2:00 requested)<br>
            &gt;      Thursday, 11 March 2021, Session III 1700-1900<br>
            &gt;      Room Name: Room 3 size: 503<br>
            &gt;      ---------------------------------------------<br>
            &gt;<br>
            &gt;<br>
            &gt; iCalendar: <a
href="https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$</a>
            <br>
            &gt;<br>
            &gt; Request Information:<br>
            &gt;<br>
            &gt;<br>
            &gt;
            ---------------------------------------------------------<br>
            &gt; Working Group Name: Human Rights Protocol
            Considerations<br>
            &gt; Area Name: IRTF<br>
            &gt; Session Requester: Mallory Knodel<br>
            &gt;<br>
            &gt;<br>
            &gt; Number of Sessions: 1<br>
            &gt; Length of Session(s):  2 Hours<br>
            &gt; Number of Attendees: 100<br>
            &gt; Conflicts to Avoid:<br>
            &gt;   Chair Conflict: dprive gaia irtfopen pearg<br>
            &gt;   Technology Overlap: mls regext<br>
            &gt;   Key Participant Conflict: dnsop<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt; People who must be present:<br>
            &gt;    Avri Doria<br>
            &gt;    Mallory Knodel<br>
            &gt;<br>
            &gt; Resources Requested:<br>
            &gt;<br>
            &gt; Special Requests:<br>
            &gt;    <br>
            &gt;
            ---------------------------------------------------------<br>
            &gt;<br>
            &gt;<br>
            -- <br>
            Mallory Knodel<br>
            CTO, Center for Democracy and Technology<br>
            gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271
            BD3C C780<br>
            <br>
            <br>
            <br>
            <br>
            <br>
            ---------- Forwarded message ----------<br>
            From: Mallory Knodel &lt;<a href="mailto:mknodel@cdt.org"
              target="_blank" moz-do-not-send="true">mknodel@cdt.org</a>&gt;<br>
            To: <a href="mailto:hrpc-chairs@ietf.org" target="_blank"
              moz-do-not-send="true">hrpc-chairs@ietf.org</a><br>
            Cc: <a href="mailto:hrpc@irtf.org" target="_blank"
              moz-do-not-send="true">hrpc@irtf.org</a><br>
            Bcc: <br>
            Date: Tue, 16 Feb 2021 12:18:21 -0500<br>
            Subject: [hrpc] agenda items Re: hrpc - Requested session
            has been scheduled for IETF 110<br>
            Hi everyone,<br>
            <br>
            This is a draft agenda and call for additional agenda items:<br>
            <br>
            ----<br>
            <br>
                  Agenda HRPC IETF 110<br>
            <br>
            # Welcome and introduction (~0 minutes)<br>
            <br>
                Scribe, Note takers<br>
                Agenda Review<br>
                Research Group status<br>
            <br>
            # Talk: JoAnne Yates and Craig Murphy (30 minutes)<br>
            <br>
                "Engineering Rules"<br>
            <br>
            # Talk: Sebastian Benthall (30 minutes)<br>
            <br>
                "BigBang: Mailing list analysis tool"<br>
            <br>
            # Update: Guidelines draft and short presentations from
            reviewers (20 <br>
            minutes)<br>
            <br>
                draft-irtf-hrpc-guidelines, Gurshabad Grover<br>
            <br>
            # AOB<br>
            <br>
                TBD<br>
            ----<br>
            <br>
            If you're on the agenda, I'll need slides the night before
            to make sure <br>
            we have a backup plan for slide progression, eg me!<br>
            <br>
            Thanks,<br>
            <br>
            -Mallory<br>
            <br>
            <br>
            On 2/12/21 7:33 PM, "IETF Secretariat" wrote:<br>
            &gt; Dear Mallory Knodel,<br>
            &gt;<br>
            &gt; The session(s) that you have requested have been
            scheduled.<br>
            &gt; Below is the scheduled session information followed by<br>
            &gt; the original request.<br>
            &gt;<br>
            &gt;<br>
            &gt;      hrpc Session 1 (2:00 requested)<br>
            &gt;      Thursday, 11 March 2021, Session III 1700-1900<br>
            &gt;      Room Name: Room 3 size: 503<br>
            &gt;      ---------------------------------------------<br>
            &gt;<br>
            &gt;<br>
            &gt; iCalendar: <a
href="https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/110/sessions/hrpc.ics__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyo2MzUjg$</a>
            <br>
            &gt;<br>
            &gt; Request Information:<br>
            &gt;<br>
            &gt;<br>
            &gt;
            ---------------------------------------------------------<br>
            &gt; Working Group Name: Human Rights Protocol
            Considerations<br>
            &gt; Area Name: IRTF<br>
            &gt; Session Requester: Mallory Knodel<br>
            &gt;<br>
            &gt;<br>
            &gt; Number of Sessions: 1<br>
            &gt; Length of Session(s):  2 Hours<br>
            &gt; Number of Attendees: 100<br>
            &gt; Conflicts to Avoid:<br>
            &gt;   Chair Conflict: dprive gaia irtfopen pearg<br>
            &gt;   Technology Overlap: mls regext<br>
            &gt;   Key Participant Conflict: dnsop<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt; People who must be present:<br>
            &gt;    Avri Doria<br>
            &gt;    Mallory Knodel<br>
            &gt;<br>
            &gt; Resources Requested:<br>
            &gt;<br>
            &gt; Special Requests:<br>
            &gt;    <br>
            &gt;
            ---------------------------------------------------------<br>
            &gt;<br>
            &gt;<br>
            -- <br>
            Mallory Knodel<br>
            CTO, Center for Democracy and Technology<br>
            gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271
            BD3C C780<br>
            <br>
            <br>
            _______________________________________________<br>
            hrpc mailing list<br>
            <a href="mailto:hrpc@irtf.org" target="_blank"
              moz-do-not-send="true">hrpc@irtf.org</a><br>
            <a
href="https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!TaKlPSGF0sUcErR4QNMfPBmDwr7L1CYIXNwY04BTyTj-368C-uLiv25mD9uyfiVdzvY$</a>
            <br>
          </blockquote>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
hrpc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hrpc@irtf.org">hrpc@irtf.org</a>
<a class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/hrpc">https://www.irtf.org/mailman/listinfo/hrpc</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780</pre>
  </body>
</html>
--------------PfGA1pKcOJDuwtYAaoEnuobJ--


From nobody Tue Feb 16 14:44:00 2021
Return-Path: <csp@csperkins.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 20F8D3A11D6 for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 14:43:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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=csperkins.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 daBor765hP4r for <hrpc@ietfa.amsl.com>; Tue, 16 Feb 2021 14:43:56 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (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 D16373A0C4E for <hrpc@irtf.org>; Tue, 16 Feb 2021 14:43:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=yS4ibfS29AGYGnbnq6UDEudw8RSxqVMyQH4aZOI7dEI=; b=pgoAnUjyzD891I/5nRTOEIAKeF yBnrMAFTpLBDgXG+NByEGbWZaze+8EYEdNnPiIK+AP315PhONj+2KgZa1rDpCot22CX8OrGK2ShMP A6TbrvCG1TyUrIyVpPH7FdwM64WIIJLfuP1K/EiA8WBHTYDH8+zNd+925qzPL2zekXm8NhRgVH2C3 bcEEg1EtwIFy2dcN7jKml4GHzf0pyqur8jU47xEbZKKRvVckdd9MqWwk0fpZmQZvDbLVXBKlpQMfY 6V+ZOwNR/rnJsMKeOGhym1Fg1XxWpytWjHpSLKnKnPyNUHkJh1IlbUmLXxLcuH4cmBpAJXAYKwFwX H6TIPAZQ==;
Received: from [81.187.2.149] (port=36570 helo=[192.168.0.67]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1lC94T-0003eB-H4; Tue, 16 Feb 2021 22:43:53 +0000
From: Colin Perkins <csp@csperkins.org>
Message-Id: <AF1110F4-24D4-4309-A960-F95489581CFC@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E47EB3C4-F7D5-4292-A0BF-EDB4245F2DB8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Tue, 16 Feb 2021 22:43:49 +0000
In-Reply-To: <CAB2unbNi=zDz+CyVsVC5qRopXouRH_9c_7BJ85vLg3GenXvjbg@mail.gmail.com>
Cc: hrpc@irtf.org
To: Sandra Braman <braman@tamu.edu>
References: <CAB2unbNi=zDz+CyVsVC5qRopXouRH_9c_7BJ85vLg3GenXvjbg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.17)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/iZBJi4pS0OKSjtwBonm969I0PMA>
Subject: Re: [hrpc] some ideas for hrpc
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: Tue, 16 Feb 2021 22:43:59 -0000

--Apple-Mail=_E47EB3C4-F7D5-4292-A0BF-EDB4245F2DB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Sandra,

Thanks for sending these =E2=80=93 there are some interesting ideas to =
consider.

Colin



> On 12 Feb 2021, at 14:00, Sandra Braman <braman@tamu.edu> wrote:
>=20
> Folks --
>=20
> To complete what I've started, following are some ideas about ways =
HRPC might enrich what it is doing going forward in the various areas in =
which it is active.  Again, I may be misunderstanding the goals of the =
group, there are always logistical issues, etc., but thought to put =
these out there to get the conversation going.  There appear to be three =
functional areas of what the group does, synergetically inter-related. =20=

>=20
> This is a very good time for HRPC to revisit its activities because =
the decades-long struggle to bring the technical and policy communities =
into a shared conversation has reached a new stage and now has a much =
more significant institutional presence than it has historically.  (Hats =
off, yet again and always, to groups such as the Center for Democracy =
and Technology for providing leadership in this area so early, and to =
the other non-profit groups that have now been in this terrain for a =
number of years, such as Article 19 and the ACLU.)
>=20
> Some of these ideas are relatively low-cost or no-cost.  Others would =
require significant amounts of time investment by one or more =
individuals and would probably need some grant-writing for support.  =
They also differ in how pressing the need is.  For document development, =
in my view, the need is very pressing.  The need to ensure and expand =
the presence of knowledgeable individuals during IETF meetings is =
enduring.  The development of pedagogical tools may be aspirational.
>=20
> I look forward to hearing people's thoughts.
>=20
> Sandra Braman
>=20
> =
--------------------------------------------------------------------------=
-------------------------------
>=20
> Arguments and Research Regarding Human Rights and Internet Protocols
>=20
> One strand of HRPC's activity involves the development of =
informational RFCs suggesting relationships between human rights and =
Internet protocols and encouraging the building of a research foundation =
to support ideas about these relationships.  These documents will be =
stronger if they engage more deeply with pertinent scholarly literature =
and with research communities using a variety of methods to investigate =
such matters.
>=20
> (1) One recommendation about how to achieve this would be to set up a =
scholarly review board that would review draft documents from a =
scholarly perspective.  Participating in such a board would be very =
attractive to academics who want to make a difference -- and who would =
definitely prefer such meaningful institutionally-required service to =
many of the other options on offer.  There is a model of this in at =
least one other of the IRTF groups, so this works within the IETF =
context.
>=20
> (2) So far HRPC has been bringing individual subject experts "in" to =
IETF; that has been effective in multiple ways and I hope this will =
continue, if not expand.  HRPC individuals going "out" to other =
communities would offer additional benefits.  Thus a second =
recommendation in this area is for authors to present draft RFCs to deep =
subject experts via conference presentations on those researchers' own =
home turf for feedback.  This would get a lot of feedback from people =
who are not otherwise involved with HRPC and will lead authors into =
pertinent research findings and literatures of which they may otherwise =
not be aware. =20
>=20
> It would also serve the additional function of informing people in the =
many professional scholarly associations that deal with technology =
policy matters of the existence of HRPC  -- the vast majority of =
researchers working in this area have no idea that HRPC exists even if =
they know about the IETF.  That could lead to the involvement of many =
more people with scholarly and social science research backgrounds in =
HRPC in an ongoing way, whether in person at meetings or by providing =
continuing feedback on draft documents via the listserv.  I could =
provide a starting list of associations where such presentations would =
be welcome, and others in HRPC I'm sure could add to it.  Once travel =
starts up again, perhaps funding could be found to support travel to =
conferences, but meanwhile, this would be a low-cost activity while =
we're doing virtual events.
>=20
> Ensuring a Human Rights Presence during IETF Meetings
>=20
> A second function of the group has been to have people on the ground =
during IETF meetings bringing up specific human rights issues as raised =
by very specific developments being discussed for particular protocols.  =
=46rom my own (limited) observation and informal reports from others, =
this is one of the most effective things that HRPC does.  The goal here, =
of course, is to expand on the number of people involved in this =
activity in a sustained manner.
>=20
> (3) An HRPC (post)graduate student fellows program could support the =
participation of graduate (postgraduate) students studying the =
Internet/policy nexus.  They could be recruited from the new and =
excellent programs being set up of this kind, such as that at Tufts =
University in the US =
(https://asegrad.tufts.edu/academics/explore-graduate-programs/cybersecuri=
ty-and-public-policy =
<https://asegrad.tufts.edu/academics/explore-graduate-programs/cybersecuri=
ty-and-public-policy>).  These go under different names but typically =
cover much, if not all, of the human rights terrain as defined by the =
HRPC, and they are now being found all over the world.  Ideally students =
would be supported for travel to a year of IETF meetings at a time, =
potentially renewable.  Perhaps funding support for such a program could =
be found.=20
>=20
> (4) Onboarding materials specific to HRPC would be useful both for =
students who come to IETF as HRPC fellows and for academics invited to =
speak.  When I was invited to speak, there was terrific informal support =
from Niels ten Oever and Corinne Cath-Speth, both of whom made many =
recommendations regarding meetings and events of particular interest =
(thanks again to you both!), but if the numbers of visitors go up and to =
relieve the pressure on those two individuals, it would be helpful to =
have something in writing that would serve this function as well.  Those =
of you with deep knowledge about what is going on could add a page of =
meeting-specific recommendations before each event.  At least two or =
three other IRTF groups are doing research pertinent to human rights, so =
those meetings should be on this list as well.  This would be a =
different kind of information from that provided for newcomers at each =
event, specific to human rights concerns.
>=20
> Building the Epistemic Community
>=20
> Most, if not all, of the suggestions above would be significant =
contributions to the important job of building a sociotechnical =
epistemic community of those concerned about human rights in the digital =
environment that involves a shared conversation between those with =
technical and those with legal and policy expertise.  Bringing students =
to IETF, for example, contributes to the building of a pipeline of =
individuals who will grow that epistemic community throughout their =
careers.  Thinking specifically about that problem as a function of the =
HRPC leads in another direction as well.
>=20
> (5) Tutorials that are accessible to students and other interested =
people explaining the policy dimensions of technical decisions would be =
valuable, and again, I believe, has been modeled by at least one other =
IRTF group. =20
>=20
> (6)  IEEE accredited computer science programs have to include courses =
on "ethics."  Can HRPC members develop curriculum materials for such =
courses in the area of human rights?  These could go beyond tutorials to =
include recommended reading lists, perhaps exercises or simulations, =
etc.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc


--Apple-Mail=_E47EB3C4-F7D5-4292-A0BF-EDB4245F2DB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Sandra,<div class=3D""><br class=3D""></div><div =
class=3D"">Thanks for sending these =E2=80=93 there are some interesting =
ideas to consider.<br class=3D""><div class=3D""><div><br =
class=3D""></div><div>Colin</div><div><br class=3D""></div><div><br =
class=3D""></div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 12 Feb 2021, at 14:00, Sandra Braman =
&lt;<a href=3D"mailto:braman@tamu.edu" class=3D"">braman@tamu.edu</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D"">Folks --<div class=3D""><br class=3D""></div><div =
class=3D"">To complete what I've started, following are some ideas about =
ways HRPC might enrich what it is doing going forward in the various =
areas in which it is active.&nbsp; Again, I may be misunderstanding the =
goals of the group, there are always logistical issues, etc., but =
thought to put these out there to get the conversation going.&nbsp; =
There appear to be three functional areas of what the group does, =
synergetically inter-related.&nbsp;&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">This is a very good time for HRPC to =
revisit its activities because the decades-long struggle to bring the =
technical and policy communities into a shared conversation has reached =
a new stage and now has a much more significant institutional presence =
than it has historically.&nbsp; (Hats off, yet again and always, to =
groups such as the Center for Democracy and Technology for providing =
leadership in this area so early, and to the other non-profit groups =
that have now been in this terrain for a number of years, such as =
Article 19 and the ACLU.)</div><div class=3D""><br class=3D""></div><div =
class=3D"">Some of these ideas are relatively low-cost or no-cost.&nbsp; =
Others would require significant amounts of time investment by one or =
more individuals and would probably need some grant-writing for =
support.&nbsp; They also differ in how pressing the need is.&nbsp; For =
document development, in my view, the need is very pressing.&nbsp; The =
need to ensure and expand the presence of knowledgeable individuals =
during IETF meetings is enduring.&nbsp; The development of pedagogical =
tools may be aspirational.</div><div class=3D""><br class=3D""></div><div =
class=3D"">I look forward to hearing people's thoughts.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Sandra Braman<br =
class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D"">---------------------------------------------------------------=
------------------------------------------</div><div class=3D""><br =
class=3D""></div><div class=3D""><u class=3D"">Arguments and Research =
Regarding Human Rights and Internet Protocols</u></div><div class=3D""><u =
class=3D""><br class=3D""></u></div><div class=3D"">One strand of HRPC's =
activity involves the development of informational RFCs suggesting =
relationships between human rights and Internet protocols and =
encouraging the building of a research foundation to support ideas about =
these relationships.&nbsp; These documents will be stronger if they =
engage more deeply with pertinent scholarly literature and with research =
communities using a variety of methods to investigate such =
matters.</div><div class=3D""><br class=3D""></div><div class=3D"">(1) =
One recommendation about how to achieve this would be to set up a <i =
style=3D"text-decoration-line:underline" class=3D"">scholarly review =
board</i>&nbsp;that would review draft documents from a scholarly =
perspective.&nbsp; Participating in such a board would be very =
attractive to academics who want to make a difference -- and who would =
definitely prefer such meaningful institutionally-required service to =
many of the other options on offer.&nbsp; There is a model of this in at =
least one other of the IRTF groups, so this works within the IETF =
context.</div><div class=3D""><br class=3D""></div><div class=3D"">(2) =
So far HRPC has been bringing individual subject experts "in" to IETF; =
that has been effective in multiple ways and I hope this will continue, =
if not expand.&nbsp; HRPC individuals going "out" to other communities =
would offer additional benefits.&nbsp; Thus a second recommendation in =
this area is for authors to present <b class=3D"">draft RFCs</b>&nbsp;to =
deep subject experts via <i class=3D""><u class=3D"">conference =
presentations</u></i>&nbsp;on those researchers' own home turf for =
feedback.&nbsp; This would get a lot of feedback from people who are not =
otherwise involved with HRPC and will lead authors into pertinent =
research findings and literatures of which they may otherwise not be =
aware.&nbsp;&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">It would also serve the additional function of informing =
people in the many professional scholarly associations that deal with =
technology policy matters of the existence of HRPC&nbsp;&nbsp;-- the =
vast majority of researchers working in this area have no idea that HRPC =
exists even if they know about the IETF.&nbsp; That could lead to the =
involvement of many more people with scholarly and social science =
research backgrounds in HRPC in an ongoing way, whether in person at =
meetings or by providing continuing feedback on draft documents via the =
listserv.&nbsp; I could provide a starting list of associations where =
such presentations would be welcome, and others in HRPC I'm sure could =
add to it.&nbsp; Once travel starts up again, perhaps funding could be =
found to support travel to conferences, but meanwhile, this would be a =
low-cost activity while we're doing virtual events.</div><div =
class=3D""><br class=3D""></div><div class=3D""><u class=3D"">Ensuring a =
Human Rights Presence during IETF Meetings</u></div><div class=3D""><u =
class=3D""><br class=3D""></u></div><div class=3D"">A second function of =
the group has been to have people on the ground during IETF meetings =
bringing up specific human rights issues as raised by very specific =
developments being discussed for particular protocols.&nbsp; =46rom my =
own (limited) observation and informal reports from others, this is one =
of the most effective things that HRPC does.&nbsp; The goal here, of =
course, is to expand on the number of people involved in this activity =
in a sustained manner.</div><div class=3D""><br class=3D""></div><div =
class=3D"">(3) An <i class=3D""><u class=3D"">HRPC (post)graduate =
student fellows program</u></i>&nbsp;could support the participation of =
graduate (postgraduate) students studying the Internet/policy =
nexus.&nbsp; They could be recruited from the new and excellent programs =
being set up of this kind, such as that at Tufts University in the US =
(<a =
href=3D"https://asegrad.tufts.edu/academics/explore-graduate-programs/cybe=
rsecurity-and-public-policy" target=3D"_blank" =
class=3D"">https://asegrad.tufts.edu/academics/explore-graduate-programs/c=
ybersecurity-and-public-policy</a>).&nbsp; These go under different =
names but typically cover much, if not all, of the human rights terrain =
as defined by the HRPC, and they are now being found all over the =
world.&nbsp; Ideally students would be supported for travel to a year of =
IETF meetings at a time, potentially renewable.&nbsp; Perhaps funding =
support for such a program could be found.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">(4) <u style=3D"font-style:italic" =
class=3D"">Onboarding materials specific to HRPC</u>&nbsp;would be =
useful both for students who come to IETF as HRPC fellows and for =
academics invited to speak.&nbsp; When I was invited to speak, there was =
terrific informal support from Niels ten Oever and Corinne Cath-Speth, =
both of whom made many recommendations regarding meetings and events of =
particular interest (thanks again to you both!), but if the numbers of =
visitors go up and to relieve the pressure on those two individuals, it =
would be helpful to have something in writing that would serve this =
function as well.&nbsp; Those of you with deep knowledge about what is =
going on could add a page of meeting-specific recommendations before =
each event.&nbsp; At least two or three other IRTF groups are doing =
research pertinent to human rights, so those meetings should be on this =
list as well.&nbsp; This would be a different kind of information from =
that provided for newcomers at each event, specific to human rights =
concerns.</div><div class=3D""><br class=3D""></div><div class=3D""><u =
class=3D"">Building the Epistemic Community</u></div><div class=3D""><u =
class=3D""><br class=3D""></u></div><div class=3D"">Most, if not all, of =
the suggestions above would be significant contributions to the =
important job of building a sociotechnical epistemic community of those =
concerned about human rights in the digital environment that involves a =
shared conversation between those with technical and those with legal =
and policy expertise.&nbsp; Bringing students to IETF, for example, =
contributes to the building of a pipeline of individuals who will grow =
that epistemic community throughout their careers.&nbsp; Thinking =
specifically about that problem as a function of the HRPC leads in =
another direction as well.</div><div class=3D""><br class=3D""></div><div =
class=3D"">(5) <i class=3D""><u class=3D"">Tutorials</u></i>&nbsp;that =
are accessible to students and other interested people explaining the =
policy dimensions of technical decisions would be valuable, and again, I =
believe, has been modeled by at least one other IRTF =
group.&nbsp;&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">(6)&nbsp; IEEE accredited computer science programs have to =
include courses on "ethics."&nbsp; Can HRPC members develop&nbsp;<i =
class=3D""><u class=3D"">curriculum materials</u>&nbsp;</i>for such =
courses in the area of human rights?&nbsp; These could go beyond =
tutorials to include recommended reading lists, perhaps exercises or =
simulations, etc.</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><u class=3D""><br =
class=3D""></u></div><div class=3D""><u class=3D""><br =
class=3D""></u></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div></div>
_______________________________________________<br class=3D"">hrpc =
mailing list<br class=3D""><a href=3D"mailto:hrpc@irtf.org" =
class=3D"">hrpc@irtf.org</a><br =
class=3D"">https://www.irtf.org/mailman/listinfo/hrpc<br =
class=3D""></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_E47EB3C4-F7D5-4292-A0BF-EDB4245F2DB8--


From nobody Thu Feb 18 02:51:32 2021
Return-Path: <cattekwaad@gmail.com>
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 784AE3A1034 for <hrpc@ietfa.amsl.com>; Thu, 18 Feb 2021 02:51:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.097
X-Spam-Level: 
X-Spam-Status: No, score=-0.097 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, GB_VISITOURSITE=2, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 SuaxwHxPcDjD for <hrpc@ietfa.amsl.com>; Thu, 18 Feb 2021 02:51:28 -0800 (PST)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 CB8073A102B for <hrpc@irtf.org>; Thu, 18 Feb 2021 02:51:27 -0800 (PST)
Received: by mail-qk1-x730.google.com with SMTP id b14so1636548qkk.0 for <hrpc@irtf.org>; Thu, 18 Feb 2021 02:51:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=RHh3MS0DlNvP1g6JQ4Ud+l1sozE8a8pc9qZZLGO3ebs=; b=cKGefrU8TzL9rzhLh06sVmUEykMzUNXCJTDC1ziBBgYNoiyAjfYP128lnjal2cc8oa n/mgVZp3/uEfjmxr/xorEIIqOw87N+P0kOY7Phv0yDsmgCJz5QjMqMFAljQElxKDS1K/ 5ovkLFN6EwrwTepYA/io5YN0GjZqQuThZnrElSIfrreHlG1wzAtjn8RQFiCT/EzLNj/X FPb1a2j8qjlqs+ivQ6jMLB8GtJTDfFQtyvdP3/MMRLMgVpDmYRTFNbrTYVt2pNMebJN3 SBAFGRI3dNo2tTCG0mUWuw4Yuq6a+YcKtug6uj7ESTA0sps9IVvDX36k4HAc7kTBB0S5 nQfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RHh3MS0DlNvP1g6JQ4Ud+l1sozE8a8pc9qZZLGO3ebs=; b=YSuFsdZ3rWz2ASyndwO3tqYp+hmrkrBmvkwa5DxQIA9MC8hb+NnYDVn09lAEFhu0JU Nc2euBgJssaiP+9YSF9UNdz9P6suH4IsSQhxUa8roef3ok8RJvGaZYNa9l1BcrwI8QIP fqoOatPqN1hoxJB7RMBlaGIudU1IuDbMJAMYMfjE+oin7psiHENbaqcSaY2Wl60wgWV9 PWP5guXF0p61A8EOouaY1IuuQNSWIg0wvTrVM2RwF919l82Hws81702ie9/9oyMeppdD eEbhmR8SqFhsDfVj9TGMzeE+WcKoRio2IpouPwaPmFS53ddcPhkhbuff+o1huI5ibtkH UwUA==
X-Gm-Message-State: AOAM532AdkHXBYAcC5L+2Dv+pzQG1FQgUSpS2bteiUEnlyD1zYhk7G8J ykINJwkFpSEAktijq9mlR0zAvAItP7MTLqXPRTmbK8MMBko=
X-Google-Smtp-Source: ABdhPJySxlfuADa+Wqr9jHnKoJ4OqOFu5zNTasyZc6l6Ss58zCgXJpMgeRa4QIZtM1I3OyOMPVz0SfzRNJo1rUu5Pss=
X-Received: by 2002:a05:620a:2eb:: with SMTP id a11mr3424416qko.380.1613645486634;  Thu, 18 Feb 2021 02:51:26 -0800 (PST)
MIME-Version: 1.0
References: <FATML%202102180001180532.5766@LISTS.PRINCETON.EDU>
In-Reply-To: <FATML%202102180001180532.5766@LISTS.PRINCETON.EDU>
From: Corinne Cath <corinnecath@gmail.com>
Date: Thu, 18 Feb 2021 13:51:13 +0300
Message-ID: <CAD499eJScyu_4obhQr6XdvLkkiPuN6rokkDeXzebvmbTo5hkNw@mail.gmail.com>
To: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000063c8f05bb9a1eca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/qU8s80WXUr-xrv0-jTh6vnDxRTo>
Subject: [hrpc] Fwd: FATML Digest - 16 Feb 2021 to 17 Feb 2021 (#2021-11)
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, 18 Feb 2021 10:51:31 -0000

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

Hi all,

This obfuscation workshop might be of interest to people!

It=E2=80=99s very much open to non-academics :D

Kind regards,

Corinne

---------- Forwarded message ---------
From: FATML automatic digest system <listserv@princeton.edu>
Date: Thu, 18 Feb 2021 at 08:02
Subject: FATML Digest - 16 Feb 2021 to 17 Feb 2021 (#2021-11)
To: <FATML@lists.princeton.edu>


There is 1 message totaling 352 lines in this issue.

Topics of the day:

  1. CFP: 3rd Workshop on Obfuscation


**********
Fairness, Accountability, and Transparency in Machine Learning
https://fatml.org
https://fatconference.org

----------------------------------------------------------------------

Date:    Wed, 17 Feb 2021 12:03:13 +0100
From:    Seda Guerses <sguerses@ESAT.KULEUVEN.BE>
Subject: CFP: 3rd Workshop on Obfuscation



Hey everyone,
we were supposed to have the 3rd Obfuscation Workshop last May in the
Netherlands, but due to the pandemic, we had to postpone and evaluate how
to make it work =E2=80=9Conline=E2=80=9D.
To make up for the constraints of the online for community building, we
introduced a study group that meets before, during and after the actual
workshop.
I hope you consider joining us for the different parts of the program or
spreading the word.
Thank you!
s.



CALL FOR PARTICIPATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
3rd Workshop on Obfuscation
May 4 & 7, 2021. Online gathering
http://www.obfuscationworkshop.org <http://www.obfuscationworkshop.org/>
Cosponsored by TPM, TU Delft and DLI, Cornell Tech
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

In the Spring of 2020, as we were in full force preparing the 3rd Workshop
on Obfuscation, COVID-19 was recognized by the World Health Organization as
a pandemic, which led us to postpone indefinitely. Today we are pleased to
announce that the 3rd Workshop on Obfuscation will finally take place
online on May 4 and 7th, 2021. Everyone is welcome to participate, with or
without submission. Please visit our website
https://www.obfuscationworkshop.org <
https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.obfuscationworksh=
op.org&d=3DDwIFaQ&c=3DXYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=3DtmwsR=
ue_ShOLap4eEpbzSI1rNtQ8N_tcK3OVwf_95j8&m=3D3qGZ48Ca_f0esSm28Xk82x9KIvrTxvOa=
0fz9dG8bQQY&s=3DjWRcN2_7fd9M7uAvmtVkP0QBBJY5i7U0yjagZOxOACU&e=3D>
to register and for other details!

IMPORTANT DATES:
-------------------------------

        =E2=80=A2 Registration re-opens on: February 3, 2021
        =E2=80=A2 Submissions due: March 15, 2021
        =E2=80=A2 Notifications: April 1, 2021
        =E2=80=A2 Workshop: May 7, 2021
        =E2=80=A2 A vernissage will take place on May 4, 2021
        =E2=80=A2 Study group meets on: April 30, May 6 and May 19, 2021


Overview and topics:
-----------------------------

Obfuscation strategies represent creative ways to evade surveillance,
protect privacy, improve security; as well as protest, contest, resist and
sabotage technology. Obfuscation methods render data more ambiguous,
difficult to exploit and interpret, less useful. They rely on the addition
of gibberish, meaningless data; they pollute, add noise, randomize.
Obfuscation invokes an intuitive form of protection: it distorts that which
is visible to render it less (or in)visible. It hides the trees among the
forest.

The aim of the 3rd Workshop on Obfuscation is to foster interaction among
diverse communities of research, concern and practice interested in
obfuscation. We convene researchers, scientists, policy makers, developers,
journalists, activists, artists and other interested parties to discuss
obfuscation in environments and conditions of asymmetrical power and
information. We welcome and value a broad range of approaches, including
theories, tools, simulations and experimental methods from diverse
disciplines and spheres of practice. The workshop constitutes a wide
umbrella welcoming a diverse family of related topics and efforts,
including adversarial machine learning, protective optimization
technologies (POTs) and obfuscation in behavioral decision-making contexts
by humans and artificial agents. We encourage participants to contribute
with ideas about how obfuscation may (or may not) serve people in the
current context of ever greater power imbalances between people, societal
institutions and technology companies.

Submission types:
--------------------------

        =E2=80=A2 A (short) position paper or extended abstract of your wor=
k (this
can be work in progress).
        =E2=80=A2 A description of an interesting use case to be discussed =
(this
may be an academic or policy/practice-based case).
        =E2=80=A2 A description of a demo or prototype (of applications, ha=
rdware
or other artifacts), performance, artwork (in any media) or journalistic
piece relevant to the topic of obfuscation.
        =E2=80=A2 A description of a hands-on workshop or other interactive=
 format
that engages with obfuscation. We welcome and encourage participants to
organize their own session on a topic related to obfuscation. Please
provide details on method and logistic needs. Note that we have allocated
1-hour slots for invited sessions; let us know if you need additional time
so we can best accommodate your proposal.

Submissions will be peer-reviewed by the Workshop=E2=80=99s Organizing Comm=
ittee
and accepted based on relevance and potential to contribute to workshop
discussions and goals. The workshop will not publish formal (i.e. archival)
proceedings. With authors' permission, accepted submissions will be
included in the postscript we plan to release after the workshop.


Participate in the 3rd Workshop on Obfuscation Study Group:
---------------------------------------------------------------------------=
--------

We invite junior researchers, artists, activists and other interested
parties to join us in a study group that accompanies the Workshop on
Obfuscation. Our goal is to provide an arena for deeper reflection and
engagement, a more tight-knit and longer breathed space for collaboration
for those interested in obfuscation. The study group will be mentored by
leading researchers of obfuscation Finn Brunton and Helen Nissenbaum, as
well as other invited artists and researchers. We hope this will provide
the basis to collectively engage beyond the ephemeral and rectangled
formats of online events. Participation in the study group is
preconditioned on a submission.  A limited number of places will be
allocated based on submission merit. For more details about what you can
expect from the study group and a tentative schedule of activities, please
visit the study group page on our website.


Stipends:
---------------

In keeping with the Workshop on Obfuscation tradition of supporting artists
and independent researchers, we have a limited number of stipends
available. If you are an artist or independent researcher, please make sure
your submission includes a funds request (including project description and
production budget). We hope to provide stipends for 4-6 projects, with new
works receiving =E2=82=AC800 max and previosuly-produced works receiving a =
fixed
amount of =E2=82=AC400.


ORGANIZING COMMITTEE:
-----------------------------------------

Ero Balsa (Cornell Tech)
Seda Gurses (Delft University of Technology)
Helen Nissenbaum (Cornell Tech)
Jara Rocha (Independent Researcher)

This event is possible thanks to the kind support of The Digital Life
Initiative at Cornell Tech, European Research Council, Consolidator grant
724431-BEHAVE and TU Delft's Faculty of Technology, Policy and Management
(TPM)


For any questions, comments or requests, you can reach us at
obfuscation@cornell.edu <mailto:obfuscation@cornell.edu>.
Please feel encouraged to share this call in your circles. We are looking
forward to receiving your submissions and seeing you at the workshop!


**********
Fairness, Accountability, and Transparency in Machine Learning
https://fatml.org
https://fatconference.org

------------------------------

End of FATML Digest - 16 Feb 2021 to 17 Feb 2021 (#2021-11)
***********************************************************
--=20
Corinne Cath - Speth
Ph.D. Candidate, Oxford Internet Institute & Alan Turing Institute

Web: www.oii.ox.ac.uk/people/corinne-cath
Email: ccath@turing.ac.uk & corinnecath@gmail.com
Twitter: @C_CS

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

<div dir=3D"auto">Hi all,</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">This obfuscation workshop might be of interest to people!</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">It=E2=80=99s very much open to non-ac=
ademics :D</div><div dir=3D"auto"><br></div><div dir=3D"auto">Kind regards,=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">Corinne=C2=A0</div><div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">-----=
----- Forwarded message ---------<br>From: <strong class=3D"gmail_sendernam=
e" dir=3D"auto">FATML automatic digest system</strong> <span dir=3D"auto">&=
lt;<a href=3D"mailto:listserv@princeton.edu">listserv@princeton.edu</a>&gt;=
</span><br>Date: Thu, 18 Feb 2021 at 08:02<br>Subject: FATML Digest - 16 Fe=
b 2021 to 17 Feb 2021 (#2021-11)<br>To:  &lt;<a href=3D"mailto:FATML@lists.=
princeton.edu">FATML@lists.princeton.edu</a>&gt;<br></div><br><br>There is =
1 message totaling 352 lines in this issue.<br>
<br>
Topics of the day:<br>
<br>
=C2=A0 1. CFP: 3rd Workshop on Obfuscation<br>
<br>
<br>
**********<br>
Fairness, Accountability, and Transparency in Machine Learning<br>
<a href=3D"https://fatml.org" rel=3D"noreferrer" target=3D"_blank">https://=
fatml.org</a><br>
<a href=3D"https://fatconference.org" rel=3D"noreferrer" target=3D"_blank">=
https://fatconference.org</a><br>
<br>
----------------------------------------------------------------------<br>
<br>
Date:=C2=A0 =C2=A0 Wed, 17 Feb 2021 12:03:13 +0100<br>
From:=C2=A0 =C2=A0 Seda Guerses &lt;<a href=3D"mailto:sguerses@ESAT.KULEUVE=
N.BE" target=3D"_blank">sguerses@ESAT.KULEUVEN.BE</a>&gt;<br>
Subject: CFP: 3rd Workshop on Obfuscation<br>
<br>
<br>
<br>
Hey everyone,<br>
we were supposed to have the 3rd Obfuscation Workshop last May in the Nethe=
rlands, but due to the pandemic, we had to postpone and evaluate how to mak=
e it work =E2=80=9Conline=E2=80=9D.<br>
To make up for the constraints of the online for community building, we int=
roduced a study group that meets before, during and after the actual worksh=
op.<br>
I hope you consider joining us for the different parts of the program or sp=
reading the word.<br>
Thank you!<br>
s.<br>
<br>
<br>
<br>
CALL FOR PARTICIPATION<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
3rd Workshop on Obfuscation<br>
May 4 &amp; 7, 2021. Online gathering<br>
<a href=3D"http://www.obfuscationworkshop.org" rel=3D"noreferrer" target=3D=
"_blank">http://www.obfuscationworkshop.org</a> &lt;<a href=3D"http://www.o=
bfuscationworkshop.org/" rel=3D"noreferrer" target=3D"_blank">http://www.ob=
fuscationworkshop.org/</a>&gt;<br>
Cosponsored by TPM, TU Delft and DLI, Cornell Tech<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
In the Spring of 2020, as we were in full force preparing the 3rd Workshop =
on Obfuscation, COVID-19 was recognized by the World Health Organization as=
 a pandemic, which led us to postpone indefinitely. Today we are pleased to=
 announce that the 3rd Workshop on Obfuscation will finally take place onli=
ne on May 4 and 7th, 2021. Everyone is welcome to participate, with or with=
out submission. Please visit our website <a href=3D"https://www.obfuscation=
workshop.org" rel=3D"noreferrer" target=3D"_blank">https://www.obfuscationw=
orkshop.org</a> &lt;<a href=3D"https://urldefense.proofpoint.com/v2/url?u=
=3Dhttp-3A__www.obfuscationworkshop.org&amp;d=3DDwIFaQ&amp;c=3DXYzUhXBD2cD-=
CornpT4QE19xOJBbRy-TBPLK0X9U2o8&amp;r=3DtmwsRue_ShOLap4eEpbzSI1rNtQ8N_tcK3O=
Vwf_95j8&amp;m=3D3qGZ48Ca_f0esSm28Xk82x9KIvrTxvOa0fz9dG8bQQY&amp;s=3DjWRcN2=
_7fd9M7uAvmtVkP0QBBJY5i7U0yjagZOxOACU&amp;e=3D" rel=3D"noreferrer" target=
=3D"_blank">https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.obfus=
cationworkshop.org&amp;d=3DDwIFaQ&amp;c=3DXYzUhXBD2cD-CornpT4QE19xOJBbRy-TB=
PLK0X9U2o8&amp;r=3DtmwsRue_ShOLap4eEpbzSI1rNtQ8N_tcK3OVwf_95j8&amp;m=3D3qGZ=
48Ca_f0esSm28Xk82x9KIvrTxvOa0fz9dG8bQQY&amp;s=3DjWRcN2_7fd9M7uAvmtVkP0QBBJY=
5i7U0yjagZOxOACU&amp;e=3D</a>&gt;=C2=A0 to register and for other details!<=
br>
<br>
IMPORTANT DATES:<br>
-------------------------------<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 Registration re-opens on: February 3,=
 2021<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 Submissions due: March 15, 2021<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 Notifications: April 1, 2021<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 Workshop: May 7, 2021<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 A vernissage will take place on May 4=
, 2021<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 Study group meets on: April 30, May 6=
 and May 19, 2021<br>
<br>
<br>
Overview and topics:<br>
-----------------------------<br>
<br>
Obfuscation strategies represent creative ways to evade surveillance, prote=
ct privacy, improve security; as well as protest, contest, resist and sabot=
age technology. Obfuscation methods render data more ambiguous, difficult t=
o exploit and interpret, less useful. They rely on the addition of gibberis=
h, meaningless data; they pollute, add noise, randomize. Obfuscation invoke=
s an intuitive form of protection: it distorts that which is visible to ren=
der it less (or in)visible. It hides the trees among the forest.<br>
<br>
The aim of the 3rd Workshop on Obfuscation is to foster interaction among d=
iverse communities of research, concern and practice interested in obfuscat=
ion. We convene researchers, scientists, policy makers, developers, journal=
ists, activists, artists and other interested parties to discuss obfuscatio=
n in environments and conditions of asymmetrical power and information. We =
welcome and value a broad range of approaches, including theories, tools, s=
imulations and experimental methods from diverse disciplines and spheres of=
 practice. The workshop constitutes a wide umbrella welcoming a diverse fam=
ily of related topics and efforts, including adversarial machine learning, =
protective optimization technologies (POTs) and obfuscation in behavioral d=
ecision-making contexts by humans and artificial agents. We encourage parti=
cipants to contribute with ideas about how obfuscation may (or may not) ser=
ve people in the current context of ever greater power imbalances between p=
eople, societal institutions and technology companies.<br>
<br>
Submission types:<br>
--------------------------<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 A (short) position paper or extended =
abstract of your work (this can be work in progress).<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 A description of an interesting use c=
ase to be discussed (this may be an academic or policy/practice-based case)=
.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 A description of a demo or prototype =
(of applications, hardware or other artifacts), performance, artwork (in an=
y media) or journalistic piece relevant to the topic of obfuscation.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 A description of a hands-on workshop =
or other interactive format that engages with obfuscation. We welcome and e=
ncourage participants to organize their own session on a topic related to o=
bfuscation. Please provide details on method and logistic needs. Note that =
we have allocated 1-hour slots for invited sessions; let us know if you nee=
d additional time so we can best accommodate your proposal.<br>
<br>
Submissions will be peer-reviewed by the Workshop=E2=80=99s Organizing Comm=
ittee and accepted based on relevance and potential to contribute to worksh=
op discussions and goals. The workshop will not publish formal (i.e. archiv=
al) proceedings. With authors&#39; permission, accepted submissions will be=
 included in the postscript we plan to release after the workshop.<br>
<br>
<br>
Participate in the 3rd Workshop on Obfuscation Study Group:<br>
---------------------------------------------------------------------------=
--------<br>
<br>
We invite junior researchers, artists, activists and other interested parti=
es to join us in a study group that accompanies the Workshop on Obfuscation=
. Our goal is to provide an arena for deeper reflection and engagement, a m=
ore tight-knit and longer breathed space for collaboration for those intere=
sted in obfuscation. The study group will be mentored by leading researcher=
s of obfuscation Finn Brunton and Helen Nissenbaum, as well as other invite=
d artists and researchers. We hope this will provide the basis to collectiv=
ely engage beyond the ephemeral and rectangled formats of online events. Pa=
rticipation in the study group is preconditioned on a submission.=C2=A0 A l=
imited number of places will be allocated based on submission merit. For mo=
re details about what you can expect from the study group and a tentative s=
chedule of activities, please visit the study group page on our website.<br=
>
<br>
<br>
Stipends:<br>
---------------<br>
<br>
In keeping with the Workshop on Obfuscation tradition of supporting artists=
 and independent researchers, we have a limited number of stipends availabl=
e. If you are an artist or independent researcher, please make sure your su=
bmission includes a funds request (including project description and produc=
tion budget). We hope to provide stipends for 4-6 projects, with new works =
receiving =E2=82=AC800 max and previosuly-produced works receiving a fixed =
amount of =E2=82=AC400.<br>
<br>
<br>
ORGANIZING COMMITTEE:<br>
-----------------------------------------<br>
<br>
Ero Balsa (Cornell Tech)<br>
Seda Gurses (Delft University of Technology)<br>
Helen Nissenbaum (Cornell Tech)<br>
Jara Rocha (Independent Researcher)<br>
<br>
This event is possible thanks to the kind support of The Digital Life Initi=
ative at Cornell Tech, European Research Council, Consolidator grant 724431=
-BEHAVE and TU Delft&#39;s Faculty of Technology, Policy and Management (TP=
M)<br>
<br>
<br>
For any questions, comments or requests, you can reach us at <a href=3D"mai=
lto:obfuscation@cornell.edu" target=3D"_blank">obfuscation@cornell.edu</a> =
&lt;mailto:<a href=3D"mailto:obfuscation@cornell.edu" target=3D"_blank">obf=
uscation@cornell.edu</a>&gt;.<br>
Please feel encouraged to share this call in your circles. We are looking f=
orward to receiving your submissions and seeing you at the workshop!<br>
<br>
<br>
**********<br>
Fairness, Accountability, and Transparency in Machine Learning<br>
<a href=3D"https://fatml.org" rel=3D"noreferrer" target=3D"_blank">https://=
fatml.org</a><br>
<a href=3D"https://fatconference.org" rel=3D"noreferrer" target=3D"_blank">=
https://fatconference.org</a><br>
<br>
------------------------------<br>
<br>
End of FATML Digest - 16 Feb 2021 to 17 Feb 2021 (#2021-11)<br>
***********************************************************<br>
</div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmai=
l=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr">=
<div><div dir=3D"ltr"><div><div dir=3D"ltr"><span style=3D"font-family:verd=
ana,sans-serif">Corinne Cath - Speth<br>Ph.D. Candidate, Oxford Internet In=
stitute &amp; Alan Turing Institute <br><br><span style=3D"color:rgb(68,68,=
68)">Web: <a href=3D"http://www.oii.ox.ac.uk/people/corinne-cath" target=3D=
"_blank">www.oii.ox.ac.uk/people/corinne-cath</a> <br>Email: <a href=3D"mai=
lto:ccath@turing.ac.uk" target=3D"_blank">ccath@turing.ac.uk</a> &amp; <a h=
ref=3D"mailto:corinnecath@gmail.com" target=3D"_blank">corinnecath@gmail.co=
m</a><br>Twitter: @C_CS</span><br></span></div></div></div></div></div></di=
v></div></div></div></div></div></div></div></div></div></div>

--000000000000063c8f05bb9a1eca--


From nobody Fri Feb 19 14:23:23 2021
Return-Path: <joeysalazar@article19.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 BD2DC3A0BC5 for <hrpc@ietfa.amsl.com>; Fri, 19 Feb 2021 14:23:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, MIME_HTML_ONLY=0.1, RCVD_IN_MSPIKE_H3=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 (1024-bit key) header.d=article19.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 B_YN_Br8y7rx for <hrpc@ietfa.amsl.com>; Fri, 19 Feb 2021 14:23:16 -0800 (PST)
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 C79F73A0BD3 for <hrpc@irtf.org>; Fri, 19 Feb 2021 14:23:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=article19.org; s=mail; h=Content-Type:MIME-Version:Date:Message-ID:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=nqF2ojuAOyWfXfJiC6FIIUH6tCBYn730622yqyX5UnM=; b=heS0kq3/eBhJKU389FmoTjZsAL GmmVmfZCgxvTo+QuGKajG9AdiTIBkDBzh+6qv6ZWgMvw26/axkWf5PmTGH+QJE1MyYftyyaEvcluY AIa0uKYafzk82hts0NamsUeE+8JnbR8N87yxIRaeqpwsw1AURRwXORtPgMBE23U1Ll5c=;
To: hrpc@irtf.org
From: Joey S <joeysalazar@article19.org>
Message-ID: <04c3b56e-8b1e-179c-d0b8-94bd930789db@article19.org>
Date: Fri, 19 Feb 2021 16:23:00 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="s4asMzB7GjxiyKvaluoJJyhNG01C9JLhw"
X-Authenticated-As-Hash: 3c8a76879922505f22521320ab57e3bbe25ea7cc
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: d825756976bdd03eeab7bf7cffb9f8e1
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/4INmUIzCQ8j3Cr8X4QtZUzfctBQ>
Subject: [hrpc] adding comments on draft-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: Fri, 19 Feb 2021 22:23:19 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--s4asMzB7GjxiyKvaluoJJyhNG01C9JLhw
Content-Type: multipart/mixed; boundary="oZRWuagZIZLAKaABg45qyrgyYUnj2wcrQ";
 protected-headers="v1"
From: Joey S <joeysalazar@article19.org>
To: hrpc@irtf.org
Message-ID: <04c3b56e-8b1e-179c-d0b8-94bd930789db@article19.org>
Subject: [hrpc] adding comments on draft-guidelines

--oZRWuagZIZLAKaABg45qyrgyYUnj2wcrQ
Content-Type: text/html; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body>
    Hi all, GG, Niels,<br>
    <br>
    Thank you for all the work and effort put into this I-D.<br>
    <br>
    After going over it, I'm wondering about the scope and tone of some
    sections; <br>
    <br>
    <ul>
      <li>"Abstract: It provides questions engineers should ask
        themselves when developing or improving protocols if they want
        to understand their potential human rights impact."</li>
    </ul>
    Are these guidelines aimed at IETF participants only? Or also for
    the organisations and companies using and expanding the protocols
    stardardised at the IETF? If the latter is part of the aim/scope,
    then the abstract could use some rephrasing since the developers are
    not the decision-makers in most scenarios that involve the planning,
    design, implementation, and deployment of a protocol or extension.
    Implementers might be a better term here since it encompasses both
    the decision-makers and the devs actively coding.<br>
    <br>
    <ul>
      <li>Section 3.1: "several 'common' threats to human rights"</li>
    </ul>
    The meaning here doesn't seem clear to me. Do we mean, as phrased
    later in the document, "protocols and their (potential) impact" to
    human rights, or "human rights risks arising from potential
    misapplications of the protocol or technology"? Perhaps something
    along the lines of creating a "basis for discussion on whether the
    protocol adequately takes specific human rights threats into
    account" could also be included here for clarity.<br>
    <br>
    <ul>
      <li>Section 3.3 (and sub-sections 1-21):</li>
    </ul>
    I agree with CCS and also think it's nicely written regarding tone
    and scope, but it seems to be in a bit of a contrast with other
    sections of the I-D, specifically with 3.1 where the language and
    tone seem to be harsher/more narrow, as well as in its sub-sections
    1-21;<br>
    In hopes of more harmonious dialog (and less of the "hr-advocates vs
    developers" mentality and arguments some might have encountered), I
    think language here that is more collaborative might yield better
    results in practice and aid in opening dialog between different
    parties in other WGs/RGs when they use this draft as a reference or
    for reviews. Framing, for example, "Does your protocol maintain the
    confidentiality of metadata?" as "How can we ensure this protocol
    maintains the confidentiality of metadata?" instead, or "Does your
    protocol in any way allow for the data to be (intentionally or
    unintentionally) altered?" as "can the data handled by this protocol
    be (intentionally or unintentionally) altered? How can we prevent
    that?", could signal a shift where 'hr-advocates' are not seen as
    "regulators" (or trying to be regulators) but as the volunteers and
    contributors that also want to work together towards a better
    outcome. Sub-section 3.3.19. in paragraph 2 of the 'Explanation:' is
    a strong example, in my opinion, of a tone that might not be
    perceived as helpful or effective when we, as devs or advocates or
    participants working in public interest technologies, aim to have
    discussions with the devs/teams working on a protocol.<br>
    <br>
    <ul>
      <li>Sub-section 3.3.1:</li>
    </ul>
    This sub-section talks about "reliable even on low bandwidth and
    high latency connections". Here I wonder if we could give an example
    or talk about the impact that reliable connections have in the
    effective access to connectivity in remote/developing areas.<br>
    <br>
    <ul>
      <li>Sub-sections 3.3.14 and 3.3.19:</li>
    </ul>
    Lastly, and similar to issue #29 in github requesting explicit
    mention of 'Access to Information', although I see Anonymity and
    'clear text / data encryption' mentioned in these sub-sections, I
    wonder (without implying some rights/technologies are more or less
    important than others) if they could be more explicitly mentioned
    across the draft or given a bit more visibility somewhere (their
    mention in sub-section 3.3.19. seems to me somewhat hidden since
    it's towards the end of the ID).<br>
    <br>
    Looking forward to your thoughts,
    <pre class=3D"moz-signature" cols=3D"72">--
Joey Salazar
Digital Sr. Programme Officer
ARTICLE 19
6E9C 95E5 5BED 9413 5D08 55D5 0A40 4136 0DF0 1A91</pre>
  </body>
</html>


--oZRWuagZIZLAKaABg45qyrgyYUnj2wcrQ--

--s4asMzB7GjxiyKvaluoJJyhNG01C9JLhw
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQRunJXlW+2UE10IVdUKQEE2DfAakQUCYDA6RAUDAAAAAAAKCRAKQEE2DfAakV7b
AQCFL2mqMCqh+pRV/2/Ci/hVZnGOjCbXxHlE/EgCrHHKggD/Qv+iE/6xozN4LC4pIiZmqASwuKv/
9mD7AOgMs4CP7AY=
=xXSV
-----END PGP SIGNATURE-----

--s4asMzB7GjxiyKvaluoJJyhNG01C9JLhw--


From nobody Fri Feb 19 14:59:16 2021
Return-Path: <ajs@anvilwalrusden.com>
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 891F93A0CDF for <hrpc@ietfa.amsl.com>; Fri, 19 Feb 2021 14:59:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=yitter.info header.b=fb4i6q0s; dkim=pass (1024-bit key) header.d=yitter.info header.b=bYD1OS28
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 AttMgpJpeZeI for <hrpc@ietfa.amsl.com>; Fri, 19 Feb 2021 14:59:13 -0800 (PST)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C51C03A0CDC for <hrpc@irtf.org>; Fri, 19 Feb 2021 14:59:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 8B3BFBD5C6 for <hrpc@irtf.org>; Fri, 19 Feb 2021 22:58:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1613775522; bh=i5OuDFYCzJ3d9F01aD+2O0SzcQ3GnOvLAfGGj6oCeeg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=fb4i6q0sYi8glAcKCjtThbB3b5Ixg0h+elKaWZd6cw/X5ohITKljGb7Jw6NiumByN hxrQOQeZxiyYxJpN6arspIXXPz7O7z1OBaW20q/I2gTd/9a2xB/yPlFmfpSIx/VY4F r9Mx7PJwvue0iMiqRLW8EDny9IzkfRM/HUOWaTH0=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id erhADcrNK39Q for <hrpc@irtf.org>; Fri, 19 Feb 2021 22:58:41 +0000 (UTC)
Date: Fri, 19 Feb 2021 17:58:39 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1613775521; bh=i5OuDFYCzJ3d9F01aD+2O0SzcQ3GnOvLAfGGj6oCeeg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=bYD1OS28IZZJPyprKfw+41Kz84QuK9pcYIA+1H0b8f77n07sYVZnh20UPbPTlcrql ogK63WreTSw4yV5JFZ1MXArAYQ9UhfxIf4YRcvxJOf9OBPa9Qj9MQwa4wOwKWHJZvO jTyTj71TEUfTrEpfupJuT8J1zimaKmN6NG71W5ZA=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: hrpc@irtf.org
Message-ID: <20210219225839.75fiesklwcndpppo@crankycanuck.ca>
Mail-Followup-To: hrpc@irtf.org
References: <04c3b56e-8b1e-179c-d0b8-94bd930789db@article19.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <04c3b56e-8b1e-179c-d0b8-94bd930789db@article19.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/osy4ZNQ0uG8ml7hLWgwsG9kdOVQ>
Subject: Re: [hrpc] adding comments on draft-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: Fri, 19 Feb 2021 22:59:16 -0000

Hi,

(ObDisclaimer: I work for ISOC but this is just my opinion and not theirs)

On Fri, Feb 19, 2021 at 04:23:00PM -0600, Joey S wrote:
>  • "Abstract: It provides questions engineers should ask themselves when
>    developing or improving protocols if they want to understand their
>    potential human rights impact."
>
>Are these guidelines aimed at IETF participants only? Or also for the
>organisations and companies using and expanding the protocols stardardised at
>the IETF?

I think this goes to the scope question that I believe Stephane
Bortzmeyer asked at one point: is this about protocols,
specifications, or implementations (or maybe, even, the tools used to
make implementations)?  Assuming it's about protocols themselves, then
expanding it to organizations and companies wouldn't be correct, since
the protocols (at least in the IETF -- it's a different story
elsewhere) are developed by individuals who, as a matter of IETF
policy, do not participate as organizational representatives.  The
contributions to the IETF protocol development (which might turn up in
a specification in an RFC) are supposed to be individual ones.

If instead we're talking about implementation or deployment then it's
a different story (but also I'm not sure the document is aimed the
right way in that case).

Best regards,

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Fri Feb 19 23:04:17 2021
Return-Path: <bortzmeyer@nic.fr>
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 BA0D53A12E8 for <hrpc@ietfa.amsl.com>; Fri, 19 Feb 2021 23:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 4KkCymC0i_Cb for <hrpc@ietfa.amsl.com>; Fri, 19 Feb 2021 23:04:12 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 A0B0A3A12C8 for <hrpc@irtf.org>; Fri, 19 Feb 2021 23:04:11 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 02ABB28076A for <hrpc@irtf.org>; Sat, 20 Feb 2021 08:04:09 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id EF86C2817A9; Sat, 20 Feb 2021 08:04:08 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id E693E28076A for <hrpc@irtf.org>; Sat, 20 Feb 2021 08:04:08 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id E1E6A60911A0 for <hrpc@irtf.org>; Sat, 20 Feb 2021 08:04:08 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id D30333FF48; Sat, 20 Feb 2021 08:03:43 +0100 (CET)
Date: Sat, 20 Feb 2021 08:03:43 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: hrpc@irtf.org
Message-ID: <20210220070343.GA23902@nic.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="zhXaljGHf11kAtnf"
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 10.7
X-Kernel: Linux 4.19.0-14-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.4.9.2830568, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2021.2.20.65417, AntiVirus-Engine: 5.80.0, AntiVirus-Data: 2021.2.20.5800000
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/5EaDILbQ8sN7IlVI7mkqMAwIBxM>
Subject: [hrpc] [rfc-editor@rfc-editor.org: RFC 8980 on Report from the IAB Workshop on Design Expectations vs. Deployment Reality in Protocol Development]
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: Sat, 20 Feb 2021 07:04:15 -0000

--zhXaljGHf11kAtnf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

This RFC talks about how actual deployments can be surprising, making
difficult to assess if a new protocol is good or bad.


--zhXaljGHf11kAtnf
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: ietf-announce-bounces@ietf.org
Received: from hermes.prod-int.prive.sqy.nic.fr [10.10.81.60]
 by b12.tech.prive.nic.fr with IMAP (fetchmail-6.4.0.beta4)
 for <bortzmeyer@localhost> (single-drop); Sat, 20 Feb 2021 02:32:03 +0100 (CET)
Received: from hermes.prod-int.prive.sqy.nic.fr (LHLO zimbra.afnic.fr)
 (10.10.81.60) by zimbra.afnic.fr with LMTP; Sat, 20 Feb 2021 02:30:44 +0100
 (CET)
Received: from localhost (localhost [127.0.0.1])
 by zimbra.afnic.fr (Postfix) with ESMTP id B215E8C8002
 for <bortzmeyer@afnic.fr>; Sat, 20 Feb 2021 02:30:44 +0100 (CET)
X-Virus-Scanned: amavisd-new at zimbra.afnic.fr
X-Spam-Flag: NO
X-Spam-Score: 0.802
X-Spam-Level: 
X-Spam-Status: No, score=0.802 tagged_above=-10 required=6.6
 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_FAIL=0.001]
 autolearn=no autolearn_force=no
Authentication-Results: zimbra.afnic.fr (amavisd-new);
 dkim=pass (1024-bit key) header.d=ietf.org header.b=FvAFJkIR;
 dkim=pass (1024-bit key) header.d=ietf.org header.b=C5aqUfzD
Received: from zimbra.afnic.fr ([127.0.0.1])
 by localhost (zimbra.afnic.fr [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id k4Eg9SPuETYf for <bortzmeyer@afnic.fr>;
 Sat, 20 Feb 2021 02:30:43 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [10.1.50.11])
 by zimbra.afnic.fr (Postfix) with ESMTP id 3F7E38C8009
 for <bortzmeyer@hermes.nic.fr>; Sat, 20 Feb 2021 02:30:43 +0100 (CET)
Received: by relay01.prive.nic.fr (Postfix)
 id 169F06043EC9; Sat, 20 Feb 2021 02:30:43 +0100 (CET)
Delivered-To: bortzmeyer@nic.fr
Received: from mx5.nic.fr (mx5.nic.fr [IPv6:2001:67c:2218:2::4:13])
 by relay01.prive.nic.fr (Postfix) with ESMTP id 12EB26043EC4;
 Sat, 20 Feb 2021 02:30:43 +0100 (CET)
Received: from mx5.nic.fr (localhost [127.0.0.1])
 by mx5.nic.fr (Postfix) with SMTP id 0F9FA30012F;
 Sat, 20 Feb 2021 02:30:43 +0100 (CET)
Received: by mx5.nic.fr (Postfix, from userid 1137)
 id 8AAAE3002A2; Sat, 20 Feb 2021 02:30:42 +0100 (CET)
Received-SPF: pass (ietf.org: 4.31.198.44 is authorized to use
 'ietf-announce-bounces@ietf.org' in 'mfrom' identity (mechanism
 'ip4:4.31.198.32/27' matched)) receiver=mx5.nic.fr; identity=mailfrom;
 envelope-from="ietf-announce-bounces@ietf.org"; helo=mail.ietf.org;
 client-ip=4.31.198.44
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx5.nic.fr (Postfix) with ESMTPS id 36B2030012F;
 Sat, 20 Feb 2021 02:30:42 +0100 (CET)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id 904C93A12E7;
 Fri, 19 Feb 2021 17:29:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
 t=1613784591; bh=CxGx+4Wypi5R9ONj1lxv1fu7f75T9WNHNt1vTw9n/24=;
 h=To:Subject:From:Date:List-Id:List-Unsubscribe:List-Archive:
 List-Post:List-Help:List-Subscribe:Cc;
 b=FvAFJkIRA6q4gJ2l61LESDu65WfD2vfZs56P+hoS5ix7TQqM3ej4CFpMHZAeUcvCN
 gYVYdaEcNjvslJ2MCrFce8LhO5e7/mqI1AanMWxGElVpHSYB9PCPozlVtmkzEVr/Dx
 mSbYCn+oZ7vhgmmnyz37ca1855KOfRBaHjISA7Kw=
X-Mailbox-Line: From ietf-announce-bounces@ietf.org  Fri Feb 19 17:29:45 2021
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id 61D3B3A1057;
 Fri, 19 Feb 2021 17:28:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
 t=1613784532; bh=CxGx+4Wypi5R9ONj1lxv1fu7f75T9WNHNt1vTw9n/24=;
 h=To:Subject:From:Date:List-Id:List-Unsubscribe:List-Archive:
 List-Post:List-Help:List-Subscribe:Cc;
 b=C5aqUfzD5+wtI4A9D1oQwHIii1SebtH4uZQhwZM3xqBZ5dXTnZTOt2VlVmDgl95zi
 0W1nzmG7OvUA9wIBkDf2JSEqC5ZTBlvNqe1gqEz0rEvexouu98idIib5efh0t46jdP
 8UEVo4CyjQxq6wt4QlbZ3eRzkwqkEiPXBh0VScD8=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id D7A463A0FFD
 for <ietf-announce@ietfa.amsl.com>; Fri, 19 Feb 2021 17:28:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 u4B5JLdigTmt for <ietf-announce@ietfa.amsl.com>;
 Fri, 19 Feb 2021 17:28:39 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 673DF3A100A
 for <ietf-announce@ietf.org>; Fri, 19 Feb 2021 17:28:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30)
 id D1D2DF4075E; Fri, 19 Feb 2021 17:28:17 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Old-Subject: =?UTF-8?B?UkZDIDg5ODAgb24gUmVwb3J0IGZyb20gdGhlIElBQiBXb3Jrc2hvcCBvbiBEZXNpZ24gRXhwZWN0YXRpb25zIHZzLiBEZXBsb3ltZW50IFJlYWxpdHkgaW4gUHJvdG9jb2wgRGV2ZWxvcG1lbnQ=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
Old-From: rfc-editor@rfc-editor.org
Message-Id: <20210220012817.D1D2DF4075E@rfc-editor.org>
Date: Fri, 19 Feb 2021 17:28:17 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/bysAu4e6mn-9ztvscKFYCb2W2nA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>,
 <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
 <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ietf-announce-bounces@ietf.org
Sender: "IETF-Announce" <ietf-announce-bounces@ietf.org>
X-PMX-Version: 6.4.9.2830568, Antispam-Engine: 2.7.2.2107409,
 Antispam-Data: 2021.2.20.12117, AntiVirus-Engine: 5.80.0,
 AntiVirus-Data: 2021.2.19.5800002
X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report='
 MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05,
 BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0,
 BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, DKIM_SIGNATURE 0,
 FROM_SAME_AS_TO_DOMAIN 0, HAS_X_PHP_SCRIPT 0, KNOWN_MTA_TFX 0,
 LEGITIMATE_SIGNS 0, LIST_HEADER 0, MTA_POSTFIX_PHP_UID 0,
 MULTIPLE_REAL_RCPTS 0, NO_REAL_NAME 0, PRECEDENCE_HEADER 0, SENDER_NO_AUTH 0,
 SXL_IP_TFX_WM 0, URI_WITH_PATH_ONLY 0, __ANY_URI 0, __BODY_NO_MAILTO 0,
 __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_BODY_WEBMAIL 0,
 __FRAUD_WEBMAIL 0, __FROM_DOMAIN_IN_ANY_CC1 0, __FROM_DOMAIN_IN_RCPT 0,
 __FROM_NAME_NOT_IN_ADDR 0, __FROM_NAME_NOT_IN_BODY 0, __FROM_NO_NAME 0,
 __HAS_ARCHIVED_AT 0, __HAS_CC_HDR 0, __HAS_ERRORS_TO 0, __HAS_FROM 0,
 __HAS_LIST_ARCHIVE 0, __HAS_LIST_HEADER 0, __HAS_LIST_HELP 0, __HAS_LIST_ID 0,
 __HAS_LIST_POST 0, __HAS_LIST_SUBSCRIBE 0, __HAS_LIST_UNSUBSCRIBE 0, 
 __HAS_MSGID 0, __HAS_SENDER 0, __HAS_X_PHP_ORIG_SCRIPT 0, __HTTPS_URI 0,
 __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0,
 __MULTIPLE_RCPTS_CC_X2 0, __MULTIPLE_RCPTS_TO_X2 0, __MULTIPLE_URI_TEXT 0,
 __NO_HTML_TAG_RAW 0, __PRECEDENCE_LIST 0, __RCPT_DOMAIN_NOT_TO 0,
 __RCVD_FROM_DOMAIN 0, __RCVD_PASS 0, __RCVD_POSTFIX_UID 0, __SANE_MSGID 0,
 __SUBJ_ALPHA_NEGATE 0, __TO_DOMAIN_IN_FROM 0, __TO_DOMAIN_IN_MSGID 0,
 __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_HAS_HYPHEN_USC 0, __URI_IN_BODY 0,
 __URI_MAILTO 0, __URI_NOT_IMG 0, __URI_NS , __URI_WITH_PATH 0, __UTF8_SUBJ 0,
 __X_PHP_ORIG_UID 0'
X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4
Subject: RFC 8980 on Report from the IAB Workshop on Design Expectations vs.
 Deployment Reality in Protocol Development
From: rfc-editor@rfc-editor.org

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8980

        Title:      Report from the IAB Workshop on
                    Design Expectations vs. Deployment Reality 
                    in Protocol Development 
        Authors:    J. Arkko,
                    T. Hardie
        Status:     Informational
        Stream:     IAB
        Date:       February 2021
        Mailbox:    jari.arkko@piuha.net,
                    ted.ietf@gmail.com
        Pages:      16
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-dedr-report-01.txt

        URL:        https://www.rfc-editor.org/info/rfc8980

        DOI:        10.17487/RFC8980

The Design Expectations vs. Deployment Reality in Protocol
Development Workshop was convened by the Internet Architecture Board
(IAB) in June 2019. This report summarizes the workshop's significant
points of discussion and identifies topics that may warrant further
consideration.

Note that this document is a report on the proceedings of the
workshop.  The views and positions documented in this report are
those of the workshop participants and do not necessarily reflect IAB
views and positions.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

--zhXaljGHf11kAtnf--


From nobody Mon Feb 22 05:44:31 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 81C503A0A34; Mon, 22 Feb 2021 05:44:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: hrpc@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: hrpc@irtf.org
Message-ID: <161400146947.18991.13052022596064029819@ietfa.amsl.com>
Date: Mon, 22 Feb 2021 05:44:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/mlxLgE4f1zony7w2ALipV7bMKzM>
Subject: [hrpc] I-D Action: draft-irtf-hrpc-association-07.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, 22 Feb 2021 13:44:30 -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           : Freedom of Association on the Internet
        Authors         : Niels ten Oever
                          Gisela Perez de Acha
                          Stéphane Couture
                          Mallory Knodel
	Filename        : draft-irtf-hrpc-association-07.txt
	Pages           : 32
	Date            : 2021-02-22

Abstract:
   This document discusses the relationships between the Internet
   architecture and the ability of people to exercise their right to
   freedom of assembly and the right to association online.  The
   Internet increasingly mediates our lives, our relationships, and our
   ability to exercise our human rights.  As a global forum, the
   Internet provides a public space, yet it is predominantly built on
   private infrastructure.  Since Internet protocols play a central role
   in the management, development, and use of the Internet, we analyze
   the relation between protocols and the rights to assemble and
   associate to mitigate infringements on those rights.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-hrpc-association-07
https://datatracker.ietf.org/doc/html/draft-irtf-hrpc-association-07

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


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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



From nobody Mon Feb 22 07:02:43 2021
Return-Path: <mail@nielstenoever.net>
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 7EB023A10A7 for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:02:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 2bkD_ihKZ5y8 for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:02:34 -0800 (PST)
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 78C883A10B1 for <hrpc@irtf.org>; Mon, 22 Feb 2021 07:00:25 -0800 (PST)
To: "hrpc@irtf.org" <hrpc@irtf.org>
References: <161400146973.18991.17493323987737895361@ietfa.amsl.com>
From: Niels ten Oever <mail@nielstenoever.net>
Message-ID: <8b494bd2-2898-cb24-b12d-f57955ec1db5@nielstenoever.net>
Date: Mon, 22 Feb 2021 16:00:09 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <161400146973.18991.17493323987737895361@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 448baf4759cd3283a5930955cc61e1db
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/HkKiiZDdgKx4YPBfTPyTeNUDho0>
Subject: Re: [hrpc] New Version Notification for draft-irtf-hrpc-association-07.txt
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, 22 Feb 2021 15:02:42 -0000

Dear Chairs,

I'd like to discuss the new version of draft-association at the upcoming session if that could work!

Best,

Niels

On 22-02-2021 14:44, internet-drafts@ietf.org wrote:
> 
> A new version of I-D, draft-irtf-hrpc-association-07.txt
> has been successfully submitted by Niels ten Oever and posted to the
> IETF repository.
> 
> Name:		draft-irtf-hrpc-association
> Revision:	07
> Title:		Freedom of Association on the Internet
> Document date:	2021-02-22
> Group:		hrpc
> Pages:		32
> URL:            https://www.ietf.org/archive/id/draft-irtf-hrpc-association-07.txt
> Status:         https://datatracker.ietf.org/doc/draft-irtf-hrpc-association/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-irtf-hrpc-association
> Htmlized:       https://tools.ietf.org/html/draft-irtf-hrpc-association-07
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-irtf-hrpc-association-07
> 
> Abstract:
>    This document discusses the relationships between the Internet
>    architecture and the ability of people to exercise their right to
>    freedom of assembly and the right to association online.  The
>    Internet increasingly mediates our lives, our relationships, and our
>    ability to exercise our human rights.  As a global forum, the
>    Internet provides a public space, yet it is predominantly built on
>    private infrastructure.  Since Internet protocols play a central role
>    in the management, development, and use of the Internet, we analyze
>    the relation between protocols and the rights to assemble and
>    associate to mitigate infringements on those rights.
> 
>                                                                                   
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 

-- 
Niels ten Oever, PhD
Postdoctoral Researcher - Media Studies Department - University of Amsterdam
Research Fellow - Centre for Internet and Human Rights - European University Viadrina
Associated Scholar - Centro de Tecnologia e Sociedade - Fundação Getúlio Vargas

W: https://nielstenoever.net
E: mail@nielstenoever.net
T: @nielstenoever
P/S/WA: +31629051853
PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3

Read my dissertation 'Wired Norms' here: https://pure.uva.nl/ws/files/50781961/Thesis.pdf


From nobody Mon Feb 22 07:20:13 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 422DF3A0CEE for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.1
X-Spam-Level: 
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, 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 T3RG-HCQYqpj for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:20:07 -0800 (PST)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 624FB3A0990 for <hrpc@irtf.org>; Mon, 22 Feb 2021 07:17:27 -0800 (PST)
Received: by mail-oi1-x235.google.com with SMTP id 12so11488950oij.6 for <hrpc@irtf.org>; Mon, 22 Feb 2021 07:17:27 -0800 (PST)
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:to :references:from:in-reply-to:content-transfer-encoding; bh=8ESQSIN77WKPUo4rhv3d6j0e1+33/LXVd1suodmVLhw=; b=tU58+r2WfD+W1CxM7QqJzyAwMN2vz6NtVfj0Utd44sD9TI1OanG+CJbwbLv3TCQYmI eRiASVeM/biaykHF2strmxQx3yjxDTmICVpwe+vJ/XnAIvGDnJuGkx0nY0Ie/JnQQ4Kc /G5SrYsBYZz4IJ1dLl1X6woEgQPcPv2ogd9Ag=
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:to:references:from:in-reply-to :content-transfer-encoding; bh=8ESQSIN77WKPUo4rhv3d6j0e1+33/LXVd1suodmVLhw=; b=C+tyHKY+slLbDjrPCrDxO150lHFNZljvPSSTrp72UtEW2yu5vgFTocqOckUnmAoR04 sjSDLFBvS/pDxnGCn8xj/+m0St9FW+7KDLsOJWwCJizjriGHRBuZmUXz8gizGXBwTQ/G rDPeBD7UwTZ5NBFRibVgkL3ZGMTf0kiMW5Cin03X0zoZu4OIwvltZ6x+e2Ob0kecRxiE fd9nmtWqqit4Qj4wZ2YwkfQ0oRhdhbU/WxSW6IzEtZgnzZ3M/8ackNHB2z5at5S2kOxf YNi5phnA1kF+9c7qESnMOIV4WMGyAOMqqe3/XDV9XIQctKQnglJWbLLGk1vm97r99rxJ pDvg==
X-Gm-Message-State: AOAM531EPQzePHbLaHTVgq1fThphrxSwoNDGkDZprEqVMmSU9EJTHO1P 3odV1B7UI1mQW59qPqC0DDxLNYMAJp4B3QKo
X-Google-Smtp-Source: ABdhPJy/mRf9Vr03mY3vjHjzjgFowx4XNQUHLpxlvWlDasjdQ22ldmCRVGGo6cOb7aX0oQkYB8Tqhw==
X-Received: by 2002:a54:4007:: with SMTP id x7mr4491286oie.87.1614007046458; Mon, 22 Feb 2021 07:17:26 -0800 (PST)
Received: from [192.168.1.244] (dhcp-6-1c-15-7-d-c8.gpon.eaglecable.net. [66.232.219.23]) by smtp.gmail.com with UTF8SMTPSA id e20sm3605721oob.40.2021.02.22.07.17.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Feb 2021 07:17:26 -0800 (PST)
Message-ID: <e92652a7-2cb1-fa37-44ea-727d76b99cb4@cdt.org>
Date: Mon, 22 Feb 2021 09:17:25 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Thunderbird/86.0
Content-Language: en-US
To: Niels ten Oever <mail@nielstenoever.net>, "hrpc@irtf.org" <hrpc@irtf.org>
References: <161400146973.18991.17493323987737895361@ietfa.amsl.com> <8b494bd2-2898-cb24-b12d-f57955ec1db5@nielstenoever.net>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <8b494bd2-2898-cb24-b12d-f57955ec1db5@nielstenoever.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/PXA39M4ksKeRpy_mVFklEoxdgV4>
Subject: Re: [hrpc] New Version Notification for draft-irtf-hrpc-association-07.txt
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, 22 Feb 2021 15:20:12 -0000

Niels,

We can modify the 110 agenda to give you 15 minutes including discussion.

Thanks!

-Mallory

On 2/22/21 10:00 AM, Niels ten Oever wrote:
> Dear Chairs,
>
> I'd like to discuss the new version of draft-association at the upcoming session if that could work!
>
> Best,
>
> Niels
>
> On 22-02-2021 14:44, internet-drafts@ietf.org wrote:
>> A new version of I-D, draft-irtf-hrpc-association-07.txt
>> has been successfully submitted by Niels ten Oever and posted to the
>> IETF repository.
>>
>> Name:		draft-irtf-hrpc-association
>> Revision:	07
>> Title:		Freedom of Association on the Internet
>> Document date:	2021-02-22
>> Group:		hrpc
>> Pages:		32
>> URL:            https://www.ietf.org/archive/id/draft-irtf-hrpc-association-07.txt
>> Status:         https://datatracker.ietf.org/doc/draft-irtf-hrpc-association/
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-irtf-hrpc-association
>> Htmlized:       https://tools.ietf.org/html/draft-irtf-hrpc-association-07
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-irtf-hrpc-association-07
>>
>> Abstract:
>>     This document discusses the relationships between the Internet
>>     architecture and the ability of people to exercise their right to
>>     freedom of assembly and the right to association online.  The
>>     Internet increasingly mediates our lives, our relationships, and our
>>     ability to exercise our human rights.  As a global forum, the
>>     Internet provides a public space, yet it is predominantly built on
>>     private infrastructure.  Since Internet protocols play a central role
>>     in the management, development, and use of the Internet, we analyze
>>     the relation between protocols and the rights to assemble and
>>     associate to mitigate infringements on those rights.
>>
>>                                                                                    
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>
-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780


From nobody Mon Feb 22 10:25:20 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 0A01E3A1EBC; Mon, 22 Feb 2021 10:25:19 -0800 (PST)
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.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: hrpc@irtf.org
Message-ID: <161401831901.15036.13588267175742697354@ietfa.amsl.com>
Date: Mon, 22 Feb 2021 10:25:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/5JozbVbUon0G9FUofpfeq4pFcR8>
Subject: [hrpc] I-D Action: draft-irtf-hrpc-guidelines-06.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, 22 Feb 2021 18:25:19 -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-06.txt
	Pages           : 31
	Date            : 2021-02-22

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 are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-06
https://datatracker.ietf.org/doc/html/draft-irtf-hrpc-guidelines-06

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


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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



From nobody Mon Feb 22 10:33:49 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 D61033A1EC8 for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:33:47 -0800 (PST)
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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 u-HkxnpQ3wC0 for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:33:44 -0800 (PST)
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 986683A1EC6 for <hrpc@irtf.org>; Mon, 22 Feb 2021 10:33:44 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org 248165805C00A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1614018818; bh=dlJEMOPadE4F5IzTeeIHqZEeX31MlbJ/eaSntSDJAsc=; h=From:To:Message-ID:Date:MIME-Version; b=TDAKWtNX/OYwggOGt0elFz3gvv+SCze3YkcggtGmUdqg8ib36P0F6d2/wNBxvG/4T fWrLKKoPqgISLw2mHkKsDNMfJWBvatL8INe2glmEvrNtvRYiUYiPA/gqcuwVzdoe49 e2fqLSrNyYZHgJIsu0qreNZP7vvfKWOpKToKGM2RagUvY/orS/t83ivJgKNcuBsS2U FFxKfbHyjbePrlwUlvKyGyifC7jocLUbjH3aaKKxf76PEBEHKf51DVClqVgdpZiwXu aiOWd0GwxI2TMZottBNZMifGIehniaVO8E29OPlRVBCchJZXgBeILmPlSrVnOr6XoD VBpi0Q+AFJFhA==
From: Gurshabad Grover <gurshabad@cis-india.org>
To: Bill Woodcock <woody@pch.net>, hrpc@irtf.org
References: <B139C6B1-C49F-45A9-8E26-92D2E5E645C7@pch.net>
Autocrypt: addr=gurshabad@cis-india.org; keydata= mQINBFriroIBEADfyDpCD8eborMUMXKtZzjo4t2KzrAlUVYgE/TFtrwUP+4Xw4dzakDIzST8 sVYmlXIWhM5NBBTZSQ190vsxrkbi0xxLcXYM2olZEtqkJ8zONZeZLBeGvcfMymtHqD4jHwYb Zm7OXnS45fWDL+HOoMP/VCwEn098rYfnllIkYQD1Gc28Ig+ywjGg8y5p0qMmmmhm2ckgLjnG MJX8t273MSc8wsn/UYH922yif3MQXmrzqgnRl9hRzf90SKqAw38bw7wccb55pIItloKYsi0r zYBKJSOPXn91Z21TpOSTy21M0MZYEAlDn1zeea+q8TggfHNWxOXoKrIm1pqZFRz0k+8i2siJ AHf8bRm/fhukA6szZ6b2nNPxjkAmOv9zvGu6RZGbmeLvQYVBSSnZ67ayZrkKwn7KIyAV6hQM /bVnD8eEZ2tZ0S8lxoZFYSNeMGt2b6WelFZO97/LbjxaJUHd9K8g5H0MwqN1NXoBxRwllVRC 3sVHVoWTBqnKo8qplzvQEAto69PpvuxxKTOFEJeQqmn1b/fo3sLRb4YiIg8Ax+Np7Huzzjk6 vKKgpIwIN7yEUj/ReWi/UA/W4wSg3XkcqTf7h73crnN/1At0PdgozbDV2UbcApaldStP4DfG UiQl0/7MiYLKapDDuSahmoeH3xrNnrzS9BAfuGHezzDbMyPLXQARAQABtCpHdXJzaGFiYWQg R3JvdmVyIDxndXJzaGFiYWRAY2lzLWluZGlhLm9yZz6JAj0EEwEIACcFAlriroICGyMFCQlm AYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQrbl/X+ubfC7/bQ//YQv7zqQE433xxsN/ 3GYKoOFccBy3WvV4DxrTskJ3n3k5lfcZolbc8TQksQOTzyerNt2ZA7fsGZa7eFSW+xR4Yq3/ C9o+5FOoHGhyZhb+x17MILhmyvyUNSj7SdKrRISgurMbV2Vv8LxmTcdrK6CdFF6JLH+opzU1 NlRKwZqROPgbYZEB2QFIUbGfgh2I5AXNyV2XbT7fagfkHk+v9AUV7POP2H1+AZ1xq6iFTm2o 9ufNZsp2bInsDohcVBKC3aH2cnFMjvIXpNoUOx8vb5A2xW0aBUTTJDB/uZw53WOg3kehrCNb ZkML3FnDZLRuu1e8DSWmwk5YIoDzt5bMCgfUwb0C6Q+JuM8lC+8CEEa9qamLc+fhvFAzcrWp VWuSaVeLdhe5NxmtlRYNZdGuKy6sRHjwsEWlwzRylhm74fiDR3aA1eIFsfmYLd4z+i1Fp23Y dHJf7/Gor2CmOxphog9DEA9WCuORXfx4De7hoMKwW4gWKw1A8B12Cv4EOkXmCsWsOnfDEarr 2Yl6elxkhQRfKjAesXb0cezRzZgwsWIsbeYsuWFF7Xi6IzUJ27lxU3p5PcyY8O8aDYOn+pu0 YFJ7s3u2VRRgptVZJmkcN3WTApXSHY8fGl5xAakM/bqFJj9uj5zlMnFN2EplC6/mQkfYfy2f siaGTP/GQV4OSuOeuMK5Ag0EWuKuggEQAJ4lAzB72gHw4+rbyxmQNNVmvgYVZPjFtO/MQdYi x1QwRP/gxxqPqTd/ZwQvmPGzXRKw10B7uKSRk6YP12+IG0mXJwHGp9q5CWJE0XNGqX3UWbAc KIzxqPNpsf8e6Bv7jdW0YwLBxJ+RW0NNL6uAxz0sr2frbnS+EZB3cU+zOZzp/9YfTUZO2lxF NzgJoErKe/HLp7aBeJXBBcwO0LQlIT80rTZx2KihBa/Ww/y9E9gV/HacJu/Ncb6E/G3e4xGj 9w9L+UW43q01wy+FSUKy9FLc7D40WqQsj8SXZEpl84SyLcJRoX3mtj59bX2SAN2VB2BAksTu qCh00IcIUGfyHziu5PwUWYM96gOhDSocP4wSeiQ8TwLzaffllz2qhdI296a9lCIYIeWVytEd NU9jJ3RbzXAgE0pnDauNXDaQv1FS5jYi8rlslJUxKnrS69BFNjM5RqQ16Cm0C4rKL7/a8wHC r4VjcjSCM8Lzv8YOOitJ9Yt4Y8SVfO5s3YvxcdSr56nX0W3B1kGbG1GpqWTzOgXzGF5bIsbV 7SPecwUs9ShvmLmZzDUxIQ68n4zj3lMZn5I+pP+Ew6nAAiuSmKdr5cygnCH/NVJzil07t+X4 uR6oKHBhuMFYF1c6Wxk36m+EZz5ZHFaT4rN0WDIJdAEqRzD0Z56V6ansDF8y+ksh0SHlABEB AAGJAiUEGAEIAA8FAlriroICGwwFCQlmAYAACgkQrbl/X+ubfC50rhAAloTaq/fZC1gtiVtU wOB+00gEkjgmzt+rLkW+l2EySTST7tje57W83UZwzCX746B2O//Bqardxz9R1Vr0VFiwHA8g 3qeBqPqiv1WoQch/iZ5d/1MxK4A9xDag1uyqLR8RuGlZ8lATmcP3IabKiuiBV4MlFZ7V2Ib6 5ToPf28xxSyjMzTjQObIG0e009uHlu2z+iQVshLyoyVVAOWWa88D6iuBDC/EtBRjlpjLAjuR YhWVYX6KHdVUijKMHN2RqjpX5O2wPL7NcMY/wsTq7EteUeI75hxFvargRXkEt1XR8t52LC0u IE2OjpzY5re/ROUbfsqL8trjAOrSJ+Fx5H8AYl9JaoVxohhxDZgNtgNtPbh/8Nnlf9daj/bh lZcTBO98XLQwMnyHGPdyhIodpWPq2C09Ys3TkQsbcdMMB1pqnEK5Vz1zIKkEEX7QVsLdrz7C 2CFsauc/9PHj+4njCHslXtzBOiVu5FXTnbCwPrLJs5iEUkUCb6qtE/2mSCTrAanzOTTOmqiM cnNTI1Tj0ht462S9VypppQnKCv8shGxXG7BadZTv+pNCA/WfB2kk1sS3ZwB0wBWX4p41fxs+ ArM9ew2SzQ/vBrEfO7ljPfZZmBqH4t/vgAZBnOtTxCGlPEIJqiMqtGHRqIqpiR20QfxEUuXI MfMfa9QJpisdNmqoUyc=
Message-ID: <ec335a47-3b06-ad5b-0d69-b23fa9b7eb94@cis-india.org>
Date: Tue, 23 Feb 2021 00:03:33 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <B139C6B1-C49F-45A9-8E26-92D2E5E645C7@pch.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: base64
X-Authenticated-As-Hash: 3c8a76879922505f22521320ab57e3bbe25ea7cc
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 772dc6cdf0bcf4a097d049da95d3b395
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/lDSKA2BRBeTvNrnbeEDc-iKksbU>
Subject: Re: [hrpc] A bunch of comments on draft-irtf-hrpc-guidelines-05
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, 22 Feb 2021 18:33:48 -0000

QmlsbCwgdGhhbmtzIGEgbG90IGZvciB5b3VyIGNvbW1lbnRzIGFuZCBmZWVkYmFjayENCg0K
SSB0aGluayB0aGUgbmV3IHZlcnNpb24gYWRkcmVzc2VzIG1vc3Qgb2YgeW91ciBjb21tZW50
cy4gUGxlYXNlIHNlZQ0KaW4tbGluZSBpZiB5b3Ugd2FudCB0byB0cmFjayB3aGF0IGNoYW5n
ZXMgd2VyZSBtYWRlIGluIHJlc3BvbnNlIHRvIGVhY2gNCmNvbW1lbnQuDQoNCk9uIDEvMjkv
MjEgNDowOSBBTSwgQmlsbCBXb29kY29jayB3cm90ZToNCj4gU29ycnksIHRoZXNlIGFyZSBp
biBubyBwYXJ0aWN1bGFyIG9yZGVyLCBhbmQgbWFueSBvZiB0aGVtIHJlZ2FyZCBsYW5ndWFn
ZSByYXRoZXIgdGhhbiBzdWJzdGFuY2UsIGFsbCBtaXhlZCB0b2dldGhlci4gIEnigJlsbCB0
cnkgdG8gbWluaW1pemUgdGhlIG51bWJlciBvZiBvbmVzIGFib3V0IGxhbmd1YWdlLCBzaW5j
ZSBhIHByb2Zlc3Npb25hbCBjb3B5ZWRpdG9yIHdpbGwgZG8gYSBiZXR0ZXIgam9iLiAgQW5k
IHRoZSBzdWdnZXN0aW9ucyBJ4oCZdmUgbWFkZSBhcmUgbWluaW1hbGlzdCBvbmVzLCBpbnRl
bmRlZCB0byBkaXNydXB0IHRoZSBzdXJyb3VuZGluZyBzZW50ZW5jZSBhcyBsaXR0bGUgYXMg
cG9zc2libGU7IGEgYmV0dGVyIGNvcHllZGl0IHdvdWxkIG9mdGVuIHJlYXJyYW5nZSBzZXZl
cmFsIHNlbnRlbmNlcyB0b2dldGhlciB0byBhY2hpZXZlIGEgYmV0dGVyIHJlc3VsdC4NCj4g
DQo+IEFueXdheToNCj4gDQo+PiAidGhpcyBpcyBub3QgdW5zdXJwcmlzaW5n4oCdDQo+IA0K
PiBQcm9iYWJseSB0aGUgb3Bwb3NpdGUgb2Ygd2hhdCB5b3UgbWVhbiwgYnV0IHdlbGwgaWxs
dXN0cmF0ZXMgdGhlIGRhbmdlcnMgb2YgZG91YmxlLW5lZ2F0aXZlcy4NCj4gDQoNCkNoYW5n
ZWQgdG8gInRoaXMgaXMgbm90IHN1cnByaXNpbmciDQoNCj4+ICJDb25zaWRlcmluZyB0aGUg
ZmFjdCB0aGF0IG5ldHdvcmsgcXVhbGl0eSBhbmQgY29uZGl0aW9ucyB2YXJ5IGFjcm9zcw0K
Pj4gZ2VvZ3JhcGh5IGFuZCB0aW1lLCBpdCBpcyBhbHNvIGltcG9ydGFudCB0byBkZXNpZ24g
cHJvdG9jb2xzIHN1Y2gNCj4+IHRoYXQgdGhleSBhcmUgcmVsaWFibGUgZXZlbiBvbiBsb3cg
YmFuZHdpZHRoIGFuZCBoaWdoIGxhdGVuY3kNCj4+IGNvbm5lY3Rpb25zLiBbYWRkIGV4YW1w
bGVzXSINCj4+DQo+IFRoaXMgYnJpbmdzIHRvIG1pbmQgdGhlIGNhc2Ugb2YgZG93bnNhbXBs
aW5nIGludGVybWVkaWFyeSBpbWFnZSBjYWNoZXMuIEZvciBhIGxvbmcgdGltZSwgYSBwb3B1
bGFyIHVzZSBvZiBTcXVpZCB3YXMgdG8gZG93bnNhbXBsZSB0aGUgcmVzb2x1dGlvbiAob3Ig
aW5jcmVhc2UgdGhlIGNvbXByZXNzaW9uKSBvZiBpbWFnZXMgYmVmb3JlIHRoZXkgY3Jvc3Nl
ZCBhIHNhdGVsbGl0ZSBsaW5rLg0KPiANCj4gVGhhdCdzIGFuIGV4YW1wbGUgb2Ygc21hcnRz
IGluIGEgbWlkZGxlYm94IGRvaW5nIHNvbWV0aGluZyB2YWx1YWJsZSBmb3IgYW4gZW5kLXVz
ZXIsIHdoZW4gdGhlIGVuZC11c2VyIGlzIGluIGEgcGFydGljdWxhcmx5IHZ1bG5lcmFibGUg
c2l0dWF0aW9uLiAgQnV0LCBob3dldmVyLCB0aGVyZSBhcmUgYWxzbyByaXNrcyBhc3NvY2lh
dGVkIHdpdGggdGhlIHZlcnkgZXhpc3RlbmNlIG9mIGEgbWlkZGxlYm94IGluIHRoZSBwYXRo
Lg0KPiANCj4gTW9yZSBvZiBhIHJlY29nbml6ZWQgaXNzdWUgbm93IHRoYW4gaW4gdGhlIGhl
eWRheSBvZiBTcXVpZC4NCj4gDQoNClRoYW5rcyBmb3IgdGhpcyBpbnRlcmVzdGluZyBleGFt
cGxlLiBIYXZlIG1hZGUgbm8gY2hhbmdlIGluIHRoZSB0ZXh0IGJ1dA0KcmVtb3ZlZCB0aGF0
IGV4YW1wbGVzIGhhdmUgdG8gYmUgYWRkZWQuDQoNCj4+ICJvdGhlciBpbnRlcm1lZGlhcnkg
bm9kZXMgdGhhdCBwcm92aWRlIOKAmHNlcnZpY2VzJyBiZXNpZGVzIHJvdXRpbmcpIg0KPiAN
Cj4gSSB3b3VsZCBzYXkgInBhY2tldCBmb3J3YXJkaW5nIiByYXRoZXIgdGhhbiAicm91dGlu
Zy4iICBZb3UncmUgbm90IGludGVyZXN0ZWQgaW4gdGhlIHJvdXRlciBmdW5jdGlvbiBvZiBh
IHJvdXRlciwgeW91J3JlIGludGVyZXN0ZWQgaW4gdGhlIHBhY2tldCBmb3J3YXJkaW5nIGZ1
bmN0aW9uIG9mIHdoYXRldmVyIGhhcHBlbnMgdG8gYmUgdGhlcmUuDQo+IA0KDQpDaGFuZ2Vk
IHRvICJwYWNrZXQgZm9yd2FyZGluZyINCg0KPj4gSHVtYW4gcmlnaHRzIHRocmVhdHMgb24g
dGhlIEludGVybmV0IGNvbWUgaW4gYSBteXJpYWQgb2YgZm9ybXMuDQo+IA0KPiDigJxNYW55
4oCdIGluZGVlZCwgYnV0IHByb2JhYmx5IG5vdCBleGFjdGx5IHRlbiB0aG91c2FuZC4gIFRo
ZXJl4oCZcyBhIGZhaXIgYml0IG9mIHN5bGxhYmxlLWV4cGFuc2lvbi1ldXBoZW1pc20gaW4g
aGVyZSB0aGF0IHNob3VsZCBnZXQgY2xlYW5lZCB1cCBvbiB0aGUgY29weWVkaXRpbmcgcGFz
cy4gIExpa2V3aXNlLCB0aGUgd29yZCDigJxpbXBhY3TigJ0gaXMgdmFzdGx5IG92ZXJ1c2Vk
LCBhbmQgbmV2ZXIgdG8gbWVhbiDigJxoaXQu4oCdICBUaGVyZeKAmXMgYWx3YXlzIGEgYmV0
dGVyIHdvcmQuDQo+IA0KDQpUaGFua3MsIHJlcGhyYXNlZCwgYW5kIGNoYW5nZWQgdG8gIm1h
bnkiLg0KDQo+PiBBIHBlcnNvbiB3aG9zZSBjb21tdW5pY2F0aW9ucyBhcmUNCj4+IG1vbml0
b3JlZCBtYXkgYmUgcHJldmVudGVkIGZyb20gZXhlcmNpc2luZyB0aGVpciByaWdodCB0byBm
cmVlZG9tIG9mDQo+PiBhc3NvY2lhdGlvbiBvciBwYXJ0aWNpcGF0ZSBpbiBwb2xpdGljYWwg
cHJvY2Vzc2VzIFtQZW5uZXldLg0KPiANCj4g4oCmcHJldmVudGVkIE9SIERJU1NVQURFRCBm
cm9t4oCmDQo+IA0KPiBDaGlsbGluZyBlZmZlY3RzIGFyZSBtdWNoIG1vcmUgcHJldmFsZW50
IHRoYW4gZGlyZWN0IHN1cHByZXNzaW9uLg0KPiANCg0KVGhhbmtzLCBjaGFuZ2VkLg0KDQo+
PiBUaGlzIGRvY3VtZW50IGRldGFpbHMgc2V2ZXJhbCAnY29tbW9uJyB0aHJlYXRzIHRvIGh1
bWFuIHJpZ2h0cywNCj4gDQo+IOKAnENvbW1vbuKAnSBpcyBuZWl0aGVyIGEgbnVtYmVyIG9m
IGZlZXQgbm9yIGVuY2xvc2VkIHdpdGhpbiBhbm90aGVyIHF1b3RhdGlvbi4gIFNvLCB0aG9z
ZSBmb290LW1hcmtzIG5lZWQgdG8gZ28uDQo+IA0KDQpSaWdodC4gTWFkZSB0aGUgc2VudGVu
Y2UgbXVjaCBzaW1wbGVyLg0KDQo+PiBIdW1hbiByaWdodHMgcmV2aWV3cyBjYW4gdGFrZSBw
bGFjZSBpbiBkaWZmZXJlbnQgcGFydHMgb2YgdGhlDQo+PiBkZXZlbG9wbWVudCBwcm9jZXNz
IG9mIGFuIEludGVybmV0IERyYWZ0Lg0KPiANCj4g4oCmY2FuIHRha2UgcGxhY2UgQVQgZGlm
ZmVyZW50IFNUQUdFUyBvZiB0aGXigKYNCj4gDQoNClRoYW5rcywgZml4ZWQuDQoNCj4+IFRo
ZXJlIGl0IG1pZ2h0IGhlbHAgdGhlDQo+PiByZXZpZXcgdG8gdW5kZXJzdGFuZCBob3cgaXQg
aW1wYWN0cyB0aGUgcGVvcGxlIHRoYXQgdXNlIHRoZSBwcm90b2NvbCwNCj4+IGFuZCB0aGUg
cGVvcGxlIHdob3NlIGxpdmVzIGFyZSBpbXBhY3RlZCBieSB0aGUgcHJvdG9jb2wuDQo+IA0K
PiANCj4gV2hlcmU/DQo+IA0KPiBUaGUgd29yZCDigJxUaGVyZeKAnSBhdCB0aGUgYmVnaW5u
aW5nIG9mIHRoZSBzZW50ZW5jZSBpcyB1bm5lY2Vzc2FyeSBhbmQgY29uZnVzaW5nLg0KPiAN
Cg0KTWFkZSB0aGUgc2VudGVuY2UgbXVjaCBzaW1wbGVyLg0KDQo+PiBodW1hbiByaWdodHMg
c2hvdWxkIGFsd2F5cyBiZSB1bmRlcnN0b29kIGZyb20gdGhlIHJpZ2h0cy1ob2xkZXINCj4g
DQo+IOKApmh1bWFuIHJpZ2h0cyBBUkUgQkVTVCB1bmRlcnN0b29kIGZyb20gdGhlIFBFUlNQ
RUNUSVZFIE9GIHRoZSByaWdodHMtaG9sZGVy4oCmDQo+IA0KDQpDaGFuZ2VkIGFzIHN1Z2dl
c3RlZC4NCg0KPj4gT3RoZXIgdGhhbiByZXZpZXdpbmcgYSBkcmFmdCwgdGhpcyBhbGxvd3Mg
dGhlIHJldmlld2VyIHRvIHVuZGVyc3RhbmQNCj4gDQo+IEJZIENPTlRSQVNUIFdJVEggcmV2
aWV3aW5nIGEgZHJhZnQuLi4NCj4gDQoNCkNoYW5nZWQgdG8gImluIGNvbnRyYXN0IHRvIFsu
Li5dIGRyYWZ0IHRleHQiOyBvdGhlciBlZGl0b3JpYWwgY2hhbmdlcy4NCg0KPj4gQWxzbyBu
b3RlIHRoYXQgd2hpbGUgdGhlIHNlY3Rpb24gdXNlcyB0aGUgd29yZCwgJ3Byb3RvY29sJywg
dGhlDQo+PiBwcmluY2lwbGVzIGlkZW50aWZpZWQgaW4gdGhlc2UgcXVlc3Rpb25zIG1heSBi
ZSBhcHBsaWNhYmxlIHRvIG90aGVyDQo+PiB0eXBlcyBvZiBzb2x1dGlvbnMgKGV4dGVuc2lv
bnMgdG8gZXhpc3RpbmcgcHJvdG9jb2xzLCBhcmNoaXRlY3R1cmUNCj4+IG9yIHNvbHV0aW9u
cyB0byBzcGVjaWZpYyBwcm9ibGVtcywgZXRjLikuDQo+IA0KPiBUaGF04oCZcyBhIHVzZWZ1
bCBjYXZlYXQsIGhvd2V2ZXIgSSB0aGluayB0aGVyZeKAmXMgc29tZSBmdXp6eSB0aGlua2lu
ZyBnb2luZyBvbiBmdXJ0aGVyIGRvd24gaW4gdGhlIGRvY3VtZW50LCB3aGVyZSB3aGF0IHNl
ZW1zIHRvIGJlIHJlZmVycmVkIHRvIGlzIGFuIGFwcGxpY2F0aW9uLCByYXRoZXIgdGhhbiBh
IHByb3RvY29sLiAgRm9yIGluc3RhbmNlOg0KPiANCj4gRG9lcyB5b3VyIHByb3RvY29sIGhh
dmUgdGV4dCBzdHJpbmdzIHRoYXQgaGF2ZSB0byBiZQ0KPiAgICB1bmRlcnN0b29kIG9yIGVu
dGVyZWQgYnkgaHVtYW5zPw0KPiANCj4gT2ZmaGFuZCwgSSBjYW7igJl0IHRoaW5rIG9mIGFu
eSBfcHJvdG9jb2xzXywgbm9yIGV2ZW4gcHJvdG9jb2wgZXh0ZW5zaW9ucyBvciBhcmNoaXRl
Y3R1cmVzLCB3aGljaCAiaGF2ZSB0ZXh0IHN0cmluZ3MgdGhhdCBoYXZlIHRvIGJlIHVuZGVy
c3Rvb2Qgb3IgZW50ZXJlZCBieSBodW1hbnMu4oCdICBJIGNhbiB0aGluayBvZiBsb3RzIG9m
IF9hcHBsaWNhdGlvbnNfIHdoaWNoIGhhdmUgdGhhdCByZXF1aXJlbWVudCwgYnV0IG5vIF9w
cm90b2NvbHNfLiAgRG8geW91IGhhdmUgYW4gZXhhbXBsZT8NCj4gDQo+IFByb3RvY29scyBf
aGFuZGxlIHBheWxvYWRfIHRoYXQgaXMgdGhlIHByb2Nlc3Mgb2YgaHVtYW4gZGF0YS1lbnRy
eSwgYW5kIHByb3RvY29scyBzaG91bGQgYmUgZGVzaWduZWQgdG8gYmUgbGliZXJhbCBpbiB3
aGF0IHRoZXkgYWNjZXB0IGFzIHBheWxvYWQsIGFudGljaXBhdGluZyBhY2NvbW1vZGF0aW9u
cyBmb3IgZGlzYWJpbGl0eSwgYXMgd2VsbCBhcyBzdXBwb3J0IGZvciBpbnRlcm5hdGlvbmFs
aXplZCBjaGFyYWN0ZXIgc2V0cywgZXRjLg0KPiANCg0KW3RvLWRvXQ0KDQo+PiAzLjMuMi4g
IFByaXZhY3kNCj4gDQo+IEkgZmluZCBpdCB1c2VmdWwgdG8gZ2V0IHBlb3BsZSB0byB3cml0
ZSBvdXQgdGhlIG1pbmltdW0gbmVjZXNzYXJ5IGRhdGEsIGFzIGFuIGV4cGxpY2l0IGV4ZXJj
aXNlIGluIGRpc3Rpbmd1aXNoaW5nIHRoZSBkYXRhIHRoYXQncyBfbmVjZXNzYXJ5XyBmcm9t
IHRoZSBkYXRhIHRoYXQgIndvdWxkIGJlIG5pY2UgdG8gaGF2ZS7igJ0gVGhlICJ3b3VsZCBi
ZSBuaWNlIHRvIGhhdmVzIiBvZnRlbiBnZXQgc2VlbiBieSBiaXpkZXYgcGVvcGxlLCBhbmQg
c3VkZGVubHkgYmVjb21lICJlY29ub21pY2FsbHkgbmVjZXNzYXJ5LuKAnSBEb2N1bWVudGlu
ZyB3aGF0J3MgYWN0dWFsbHkgZnVuY3Rpb25hbGx5IG5lY2Vzc2FyeSBhdCB0aGUgb3V0c2V0
IG1pZ2h0IGhlbHAgZmlnaHQgdGhhdCBraW5kIG9mIG1hbGV2b2xlbnQgZmVhdHVyZS1jcmVl
cC4NCj4gDQoNCkRlZmluaXRlbHkgYWdyZWUuIEkgdGhpbmsgdGhhdCB0aGUgZGF0YSBtaW5p
bWlzYXRpb24gcHJpbmNpcGxlIGFscmVhZHkNCmNhcHR1cmVzIHRoaXMgZXhlcmNpc2U6ICJE
b2VzIHlvdXIgcHJvdG9jb2wgYWRoZXJlIHRvIGRhdGEgbWluaW1pemF0aW9uDQpwcmluY2lw
bGVzPyIgU28sIEkgaGF2ZSBub3QgbWFkZSBhbnkgZWRpdHMgcmlnaHQgbm93LCBidXQgaGFw
cHkgdG8NCmNoYW5nZSB0aGUgdGV4dCBoZXJlIGlmIHlvdSB0aGluayB0aGlzIGlzIG5vdCBh
ZGVxdWF0ZS4NCg0KPj4gMy4zLjYuICBDZW5zb3JzaGlwIHJlc2lzdGFuY2UNCj4gDQo+IA0K
PiBQcm9iYWJseSB3b3J0aCBzb21lIGRpc2N1c3Npb24gb2YgdmVyYm9zZSBlcnJvciBtZXNz
YWdlczsgbWVhbmluZyBoYXZpbmcgYSBwbGV0aG9yYSBvZiBkaWZmZXJlbnQgbWFjaGluZS1y
ZWFkYWJsZSBlcnJvciBtZXNzYWdlIGNvZGVzLCB3aGljaCBoYXZlIGNsZWFybHkgZGVmaW5l
ZCBtZWFuaW5ncyB0aGF0IGNhbiBiZSB0cmFuc2xhdGVkIGludG8gdGhlIHVzZXLigJlzIGxh
bmd1YWdlIGFuZCBwYXNzZWQgdGhyb3VnaCB0cmFuc3BhcmVudGx5LiAgQmVjYXVzZSB3aGVu
IHdlIGRvbuKAmXQgZG8gdGhpcyB1cC1mcm9udCwgaXQgaW52YXJpYWJseSBiZWNvbWVzIGFu
IGlzc3VlLCBhbmQgdGhlbiB3ZSBoYXZlIHRvIGRvIGRuc29wLWV4dGVuZGVkLWVycm9yLTk5
IG9yIHdoYXRldmVyLiAgU28sIGRpc3Rpbmd1aXNoaW5nIGJldHdlZW4g4oCcYmxvY2tlZCBi
eSBzaXRlIGFkbWluaXN0cmF0aXZlIHBvbGljeSzigJ0g4oCcYmxvY2tlZCBieSBjYXJyaWVy
IHBvbGljeSzigJ0g4oCcYmxvY2tlZCBieSByZWd1bGF0b3J5IHBvbGljeSBvZiBjb3VudHJ5
IENDLOKAnSDigJxibG9ja2VkIGJlY2F1c2Ugb2YgbWFsd2FyZSB0aHJlYXQsIHNlZSBodHRw
czovL2ZvbyBmb3IgZGV0YWlscyzigJ0g4oCcYmxvY2tlZCBiZWNhdXNlIG9mIGFnZSByZXN0
cmljdGlvbizigJ0g4oCcYmxvY2tlZCBieSBwYXJlbnRhbCByZXN0cmljdGlvbiBwb2xpY3ks
4oCdIGFyZSBhbGwgdXNlZnVsLCBmb3IgaW5zdGFuY2UuICBBbnkgaW5zdGFuY2Ugb2Ygb3Zl
cmxvYWRpbmcgaWRlbnRpZmllcnMgY3JlYXRlcyBhbWJpZ3VpdHkgYW5kIGZvZyBhbmQgaXMg
cHJvYmxlbWF0aWMgZm9yIHVzZXJzLg0KPiANCg0KIklmIGEgcHJvdG9jb2wgcG90ZW50aWFs
bHkgZW5hYmxlcyBjZW5zb3JzaGlwLCBwcm90b2NvbCBkZXNpZ25lcnMgc2hvdWxkDQpzdHJp
dmUgdG93YXJkcyBjcmVhdGluZyBlcnJvciBjb2RlcyB0aGF0IGNhcHR1cmUgZGlmZmVyZW5j
ZSBzY2VuYXJpb3MNCihibG9ja2VkIGR1ZSB0byBhZG1pbmlzdHJhdGl2ZSBwb2xpY3ksIHVu
YXZhaWxhYmxlIGJlY2F1c2Ugb2YgbGVnYWwNCnJlcXVpcmVtZW50cywgZXRjLikgdG8gbWlu
aW1pc2UgYW1iaWd1aXR5IGZvciBlbmQtdXNlcnMuIg0KDQoNCj4+IDMuMy43LiAgT3BlbiBT
dGFuZGFyZHMNCj4gDQo+IA0KPiBJIGxpa2UgZXZlcnl0aGluZyB0aGF04oCZcyBiZWluZyBz
YWlkIGhlcmUsIGJ1dCBJ4oCZbSBub3QgMTAwJSBjb252aW5jZWQgdGhhdCBpdCBiZWxvbmdz
IGluIHRoaXMgZG9jdW1lbnQuICBRdWl0ZSBwb3NzaWJseSBpdCBkb2VzLCBidXQgYSBzdHJv
bmdlciBjYXNlIGZvciB0aGUgY29ubmVjdGlvbiBiZXR3ZWVuIG9wZW4gc3RhbmRhcmRzIGFu
ZCBodW1hbiByaWdodHMgY291bGQgYmUgbWFkZeKApiAgQXJlIHByb3ByaWV0YXJ5IG9yIG5v
bi1zZWxmLWhvc3RhYmxlIHRoaW5ncyBkYW1hZ2luZyBpbiBzcGVjaWZpYyB3YXlzIHRvIHBl
b3BsZeKAmXMgc3BlY2lmaWMgcmlnaHRzPyAgQSBjYXNlIGNvdWxkIGJlIG1hZGUsIHVuZG91
YnRlZGx5LiAgT3IgYXJlIGNsb3NlZCBzeXN0ZW1zIGFuIGluaGVyZW50IGNoYWxsZW5nZSB0
byBwZW9wbGXigJlzIHJpZ2h0IHRvIGtub3cgd2hhdOKAmXMgZ29pbmcgb24gYXJvdW5kIHRo
ZW0gYW5kIGhvdyB0aGVpciBkYXRhIGlzIGJlaW5nIHVzZWQgYW5kIHRoZWlyIHJpZ2h0IG9m
IHBhcnRpY2lwYXRpb24gb3IgZnJlZSBhc3NvY2lhdGlvbiAod2l0aCBzb2Z0d2FyZSBwcm9k
dWN0cz8p4oCmIFRoYXQgc2VlbXMgbGlrZSBhIG11Y2ggbW9yZSBmdW5kYW1lbnRhbCBhc3Nl
cnRpb24sIGFuZCBhIGhhcmRlciBmaWdodCB0byBwaWNrLCBhbHRob3VnaCBJIGRvbuKAmXQg
ZGlzYWdyZWUgd2l0aCBpdCBlaXRoZXIuDQo+IA0KDQpIbW0uLi4gSSd2ZSBhZGRlZCB0aGlz
IGxpbmUgZm9yIG5vdzogIk9wZW4gc3RhbmRhcmRzIChhbmQgb3BlbiBzb3VyY2UNCnNvZnR3
YXJlKSBhbGxvdyB1c2VycyB0byBnbGVhbiBpbmZvcm1hdGlvbiBhYm91dCBob3cgdGhlIHRv
b2xzIHRoZXkgYXJlDQp1c2luZyB3b3JrLCBpbmNsdWRpbmcgdGhlIHRvb2xzJyBzZWN1cml0
eSBhbmQgcHJpdmFjeSBwcm9wZXJ0aWVzLiIgSQ0KaG9wZSB0aGlzIGNhbiBlc3RhYmxpc2gg
dGhhdCBvcGVuIHN0YW5kYXJkcyBhcmUgdXNlZnVsIGZvciBlbmFibGluZw0KYWNjZXNzIHRv
IGluZm9ybWF0aW9uIHRoYXQgaXMgcmVsZXZhbnQgdG8gb3RoZXIgcHJvdG9jb2wgcHJvcGVy
dGllcw0KZW51bWVyYXRlZCBpbiB0aGUgZG9jdW1lbnQuDQoNCk9wZW4gdG8gc3VnZ2VzdGlv
bnMgb24gaG93IHRoaXMgdGV4dCBjYW4gYmUgaW1wcm92ZWQsIEkgZG9uJ3QgdGhpbmsgSQ0K
aGF2ZSBhbnkgaW1tZWRpYXRlIHN1Z2dlc3Rpb25zIGVpdGhlci4NCg0KPj4gMy4zLjguICBI
ZXRlcm9nZW5laXR5IFN1cHBvcnQNCj4+ICAgIEltcGFjdHM6DQo+PiAgICAtICBSaWdodCB0
byBmcmVlZG9tIG9mIGV4cHJlc3Npb24NCj4+ICAgIC0gIFJpZ2h0IHRvIHBvbGl0aWNhbCBw
YXJ0aWNpcGF0aW9uDQo+IA0KPiANCj4gQWdhaW4sIEkgYWdyZWUgd2l0aCB0aGUgcG9pbnRz
IG1hZGUsIHRoZXnigJlyZSBnb29kIHBvaW50cywgYnV0IEnigJltIG5vdCBzdXJlIHRoZXkg
Y2xlYXJseSBsZWFkIHRvIGEgY29uY2x1c2lvbiB0aGF0IGVpdGhlciByaWdodHMgb2YgZnJl
ZWRvbSBvZiBleHByZXNzaW9uIG9yIHBvbGl0aWNhbCBwYXJ0aWNpcGF0aW9uIGFyZSBkaXJl
Y3RseSBhZmZlY3RlZC4NCj4gDQoNCkkndmUgdHJpZWQgdG8gbWFrZSB0aGUgbGluayBjbGVh
cmVyIHdpdGggdGhlIGFkZGl0aW9uIG9mIHRoaXMgc2VudGVuY2U6DQoiSGV0ZXJvZ2VuZWl0
eSBzdXBwb3J0IGluIHByb3RvY29scyBjYW4gdGh1cyBlbmFibGUgYSB3aWRlIHJhbmdlIG9m
DQpkZXZpY2VzIGFuZCAoYnkgZXh0ZW5zaW9uKSB1c2VycyB0byBwYXJ0aWNpcGF0ZSBvbiB0
aGUgbmV0d29yay4iDQoNCkhvcGUgdGhpcyBpcyBmaW5lLCBidXQgb3BlbiB0byBzdWdnZXN0
aW9ucyENCg0KPj4gMy4zLjkuICBQc2V1ZG9ueW1pdHkNCj4gDQo+IA0KPiBQc2V1ZG9ueW1p
dHksIG9uIHRoZSBvdGhlciBoYW5kLCBzZWVtcyB0byBtZSB0byBiZSB2ZXJ5IGRpcmVjdGx5
IHJlbGF0ZWQgdG8gZnJlZWRvbSBvZiBleHByZXNzaW9uLiAgU29tZSB0aGluZ3MgeW91IGNh
buKAmXQgc2F5IGlmIHlvdSBoYXZlIHRvIHNheSBpdCBwdWJsaWNseSB1c2luZyB5b3VyIGdl
bmVyYWwtcHVycG9zZSBpZGVudGl0eS4gIENoaWxsaW5nIGVmZmVjdHMsIGV0Yy4gIEFuZCB0
aGF0IGFsc28gaW1wYWN0cyByaWdodCB0byBwb2xpdGljYWwgcGFydGljaXBhdGlvbi4NCj4g
DQo+IEkgdGhpbmsgdGhlIHBvaW50IGNvdWxkIGJlIG1vcmUgY2xlYXJseSBtYWRlIHRoYXQg
d2hlbiBwcm90b2NvbHMgcmVxdWlyZSBpZGVudGlmaWVycywgdGhleSBzaG91bGQgYXR0ZW1w
dCB0byBiZSBhZ25vc3RpYyBhYm91dCB0aGUgZm9ybSBvZiB0aGUgaWRlbnRpZmllcuKApiAg
VGhlIHNhbWUgcHJvdG9jb2wgc2hvdWxkIGJlIGFibGUgdG8gYWNjZXB0IGEgcHJpdmF0ZS11
c2UgaWRlbnRpZmllciBmb3IgdXNlIHdpdGhpbiBhIGNvcnBvcmF0ZSBXQU4sIGEgZ292ZXJu
bWVudC1pc3N1ZWQgaWRlbnRpZmllciBmb3IgYWNjZXNzIHRvIGdvdmVybm1lbnQgc2Vydmlj
ZXMsIGEgdW5pcXVlIGlkZW50aWZpZXIgbm90IGFzc29jaWF0ZWQgd2l0aCB5b3VyIHB1Ymxp
YyBwZXJzb25hIGZvciBwdWJsaWMgY29tbXVuaWNhdGlvbnMgd2hpY2ggY2FuIGJlIG5vbnJl
cHVkaWF0YWJseSBsaW5rZWQgdG8gb3RoZXIgY29tbXVuaWNhdGlvbnMgZnJvbSB0aGUgc2Ft
ZSBpZGVudGlmaWVyLCBldGMuICBBbiBleGFtcGxlIG9mIGEgYmFkIHByb3RvY29sIHdvdWxk
IGJlIG9uZSB3aGljaCBzdHJ1Y3R1cmFsbHkgY291bGQgb25seSBhY2NlcHQgeW91ciBoYW0g
cmFkaW8gY2FsbC1zaWduIGFzIGFuIGlkZW50aWZpZXIsIGFuZCBicm9rZSBpZiB0d28gcGFy
dGllcyB0cmllZCB0byB1c2UgdGhlIHNhbWUgb25lLg0KPiANCj4gQW4gZXhhbXBsZSBvZiBn
b29kIHVzZSBvZiBwc2V1ZG9ueW1zIGluIHByb3RvY29sIGRlc2lnbiBpcyBEQU5FLCB3aGlj
aCBhbGxvd3MgdXNlcnMgdG8gZ2VuZXJhdGUgdGhlaXIgb3duIGNlcnRpZmljYXRlcywgYW5k
LCBtb3JlIGltcG9ydGFudGx5LCB2YXN0bHkgcmVzdHJpY3RzIHRoZSBudW1iZXIgb2Ygb3Ro
ZXIgcGVvcGxlIHdobyBjYW4gZ2VuZXJhdGUgYm9ndXMgY2VydGlmaWNhdGVzIGNsYWltaW5n
IHRvIGJlIHRoYXQgdXNlci4gIFRoZSBuZWVkIGZvciBEQU5FIGNvbWVzIGluIGNvdW50ZXJw
b2ludCB0byBDQSBjZXJ0cywgd2hpY2ggbXVzdCBoYXZlIHNlZW1lZCBsaWtlIGEgZ29vZCBp
ZGVhIHRvIHNvbWVvbmUgYXQgdGhlIHRpbWUsIGJ1dCBoYWQgdGhlIHNlZWRzIG9mIGl0cyBv
d24gZmFpbHVyZSBidWlsdC1pbjogaXQgYXNzdW1lZCB0aGF0IGEgc2luZ2xlLCBjZW50cmFs
aXplZCBleHRlcm5hbCBhdXRob3JpdHkgd291bGQgY3JlYXRlIGlkZW50aXRpZXMgYW5kIGRp
cmVjdGx5LCBwdWJsaWNseSwgcGFpciB0aGVtIHdpdGggc3RhdGUtZ2VuZXJhdGVkIGlkZW50
aXRpZXMuICBCdXQgb2YgY291cnNlIHRoZXJl4oCZcyBtb3JlIHRoYW4gb25lIHN0YXRlLiAg
QW5kIGFueSBnaWcgdGhhdCBnb29kIGlzIGdvbm5hIGdldCBkaXZ2aWVkIHVwIGFtb25nIG11
bHRpcGxlIGV4cGxvaXRlcnMsIG5vdCBqdXN0IHRoZSBmaXJzdCBvbmUsIGF0IHdoaWNoIHBv
aW50IGl04oCZcyBhIHJhY2UtdG8tdGhlLWJvdHRvbS4gIEFsbCBiZWNhdXNlIHRoZSBwcm90
b2NvbCB3YXMgZGVzaWduZWQgdG8gc2VydmUgdGhlIGJ1c2luZXNzIG1vZGVsIG9mIGEgc2lu
Z2xlIGNvbXBhbnksIHJhdGhlciB0aGFuIGRlc2lnbmVkIGluIGFuIG9wZW4gcHJvY2VzcyB0
byBzZXJ2ZSB0aGUgbmVlZHMgb2YgdXNlcnMuICBBbGwgYXZvaWRhYmxlLCBpZiB0aGV54oCZ
ZCBvbmx5IGhhZCB0aGlzIGludmFsdWFibGUgZ3VpZGUgdGhpcnR5IHllYXJzIGVhcmxpZXIh
ICA6LSkNCj4gDQoNCkFic29sdXRlbHksIGluY2x1ZGVkIHRoZSBwb2ludCBhYm91dCBmcmVl
ZG9tIG9mIGV4cHJlc3Npb24gYW5kIHBvbGl0aWNhbA0KcGFydGljaXBhdGlvbi4NCg0KSSB0
aGluayB0aGUgcG9pbnQgYWJvdXQgYWdub3N0aWNpc20gYWJvdXQgdGhlIGZvcm0gb2YgaWRl
bnRpZmllciBpcw0KYmV0dGVyIGNhcHR1cmVkIHVuZGVyIGhldGVyb2dlbmVpdHkgc3VwcG9y
dCB0aGFuIHRoaXMgcGFydGljdWxhciBvbmUuDQoNCj4+IElzIHlvdXIgcHJvdG9jb2wgZGVz
aWduZWQgdG8gcHJvdmlkZSBhbiBlbmFibGluZw0KPj4gZW52aXJvbm1lbnQgZm9yIHBlb3Bs
ZSB3aG8gYXJlIG5vdCBhYmxlLWJvZGllZD8NCj4gDQo+IEFjY2Vzc2libGUgZGVzaWduIGlz
IG1vcmUgYWNjZXNzaWJsZSBmb3IgZXZlcnlvbmUsIG5vdCBqdXN0IHRoZSBoYW5kaWNhcHBl
ZC4gIFJlLXdvcmQgdGhhdCB0byAiSXMgeW91ciBwcm90b2NvbCBkZXNpZ25lZCB0byBwcm92
aWRlIGFuIGVuYWJsaW5nIGVudmlyb25tZW50IGZvciBhbGw/Ig0KPiANCj4gU2VjdGlvbiAz
LjMuMTIgaXMgcGFydGljdWxhcmx5IHdlbGwtd3JpdHRlbi4NCj4gDQoNCkNoYW5nZWQgYXMg
c3VnZ2VzdGVkLg0KDQo+PiBBIHN5c3RlbSB0aGF0IGlzIHJlbGlhYmxlIGRlZ2VuZXJhdGVz
IGdyYWNlZnVsbHkNCj4gDQo+IERFR1JBREVTIGdyYWNlZnVsbHkuDQo+IA0KPiBZb3UgbWln
aHQgYWxzbyBjb25zaWRlciB0aGUgYXBwbGljYWJpbGl0eSBvZiB0aGUgd29yZCDigJxyZXNp
bGllbmNl4oCdIHdoaWNoIGNhcHR1cmVzIGEgbG90IG9mIHdoYXQgeW914oCZcmUgdGFsa2lu
ZyBhYm91dCBoZXJlLCBhbmQgaXMgZnJlcXVlbnRseSB1c2VkIGZvciB0aGlzIHB1cnBvc2Ug
aW4gbmV0d29yayBlbmdpbmVlcmluZyBkaXNjdXNzaW9ucy4NCj4gDQoNClRoYW5rcywgYWRk
ZWQuDQoNCj4gVGhyb3VnaG91dCB0aGUgZG9jdW1lbnQsIGJ1dCBwYXJ0aWN1bGFybHkgaW4g
c2VjdGlvbnMgMy4zLjEsIDMuMy4yLCAzLjMuMywgMy4zLjksIGFuZCAzLjMuMTQsIHRoZXJl
IGFyZSBkaXNjdXNzaW9ucyBvZiBiYWQgcHJhY3RpY2VzLCB3aXRoIGEgd2FybmluZyBub3Qg
dG8gZG8gdGhlbSBiZWNhdXNlIHRoZXnigJlyZSBiYWQsIGJ1dCBJIHRoaW5rIHRoaXMgbWF5
IG5vdCByZWFsbHkgZ2V0IHRoZSBhdHRlbnRpb24gb2YgdGhlIChtYW55KSBwZW9wbGUgd2hv
IGFyZSBkb2luZyB0aGVzZSBiYWQgdGhpbmdzIHJvdXRpbmVseSwgYW5kIGFscmVhZHkgaGVh
ciB0aGF0IHRoZXnigJlyZSBiYWQsIGFuZCBoYXZlIGFscmVhZHkgZXhjdXNlZCB0aGVtc2Vs
dmVzLiAgV2hhdCBJIHRoaW5rIGlzIG5lZWRlZCBpcyBhIOKAnHdha2UtdXAgY2FsbC7igJ0g
IE5vdCBhIHJlbWluZGVyIHRoYXQgdGhlc2UgdGhpbmdzIGFyZSBiYWQsIGJ1dCBhIGNhbGwg
Zm9yIGludHJvc3BlY3Rpb24gYW5kIGNvbnNpZGVyYXRpb246IGFzayB0aGUgcHJvdG9jb2wg
ZGVzaWduZXIgdG8gZXhwbGljaXRseSBzdGF0ZSB3aHkgZWFjaCDigJxiYWTigJ0gZGVjaXNp
b24gaXMgdGVjaG5pY2FsbHkgbmVjZXNzYXJ5IHRvIHRoZSBmdW5jdGlvbiBvZiB0aGUgcHJv
dG9jb2wuICBTbyBtYW55IGJhZCBkZWNpc2lvbnMgaGF2ZSBiZWVuIGp1c3RpZmllZCBvdmVy
IHRoZSBsYXN0IHR3ZW50eSB5ZWFycyBieSB0aGUgbm90aW9uIHRoYXQg4oCcd2UgbWlnaHQg
YmUgYWJsZSB0byBkbyBzb21ldGhpbmcgdXNlZnVsIHdpdGggdGhhdCBkYXRhIGluIHRoZSBm
dXR1cmXigJ0gb3Ig4oCcbGF3IGVuZm9yY2VtZW50IGluIHN1Y2gtYW5kLXN1Y2gtYS1tYXJr
ZXQtdGhhdC1vdXItYml6ZGV2LWd1eXMtYXJlLXJlYWxseS1leGNpdGVkLWFib3V0LXRoaXMt
d2VlayB3b3VsZCByZWFsbHkgbGlrZSB0aGlzIGlmIHRoZXkga25ldyBpdCB3YXMgcG9zc2li
bGXigJ0gdGhhdCB3ZSByZWFsbHkgbmVlZCB0byBlbmNvdXJhZ2UgcmF0aW9uYWwgbWluaW1h
bGlzbS4gIFNvbWV0aW1lcyBtb3JlIGRhdGEgcmVhbGx5IGlzIG5lY2Vzc2FyeSwgYnV0IGl0
IHBheXMgdG8gdGhpbmsgaXQgdGhyb3VnaCBhbmQgZGlzY3VzcyBpdCBpbiBwdWJsaWMgYW5k
IHNlZSBpZiBhbnlvbmUgaGFzIGEgYmV0dGVyIGlkZWEgdGhhdCBjb3VsZCBhY2NvbXBsaXNo
IHRoZSBzYW1lIGdvYWwgd2hpbGUgY29sbGVjdGluZyBsZXNzIGRhdGEgb3IgZGVsdmluZyBs
ZXNzIGZhciBpbnRvIHRoZSBoZWFkZXJzIG9yIGFsbG93aW5nIGEgYnJvYWRlciBjaG9pY2Ug
b2YgaWRlbnRpZmllcnMuICBXaGVuIHlvdSBhc2sg4oCcZG9lcyB5b3VyIHByb3RvY29sIGRv
IHRoaXMgYmFkIHRoaW5n4oCdIHRoZSBwZXJzb24gd2hv4oCZcyBkZXNpZ25lZCBpdCB0byBk
byB0aGUgYmFkIHRoaW5nIHdpbGwgYmxvdyBpdCBvZmYsIGJlY2F1c2UgaXTigJlzIGEgdmFs
dWUganVkZ2VtZW50IG9mIHRoZW0sIG9mIHRoZWlyIGNoYXJhY3RlciwgaWYgdGhleSB0YWtl
IGl0IHNlcmlvdXNseS4gIEFuZCBhdHRhY2tpbmcgdGhlbSBhbmQgbWFraW5nIHRoZW0gZmVl
bCBkZWZlbnNpdmUgZG9lc27igJl0IGFjaGlldmUgb3VyIGdvYWwuICBJbnN0ZWFkLCB3ZSBu
ZWVkIHRvIGdldCB0aGVtIHRvIHRoaW5rIGRpZmZlcmVudGx5LCBhbmQgdGhhdCBjYW4gb25s
eSBjb21lIGZyb20gaW50cm9zcGVjdGlvbiwgbm90IGZyb20gdXMgdGVsbGluZyB0aGVtIHRo
YXQgdGhleSB3YXkgdGhleSB0aGluayByaWdodCBub3cgaXMgYmFkLg0KPiANCg0KVGhhbmtz
LCB0aGUgdG9uZSBvZiB0aGUgZG9jdW1lbnQgaXMgaW1wb3J0YW50LCBvZiBjb3Vyc2UuIEkn
dmUgbWFya2VkDQp0aGlzIGFzIGEgdG8tZG8gZm9yIGFuIGVkaXQgcm91bmQ7IHRoZSB0ZXh0
IHNob3VsZCByZWFkIG1vcmUgbGlrZQ0KZ3VpZGFuY2UgaWYgaXQgYWxyZWFkeSBpc24ndC4N
Cg0KPj4gMy4zLjE3LiAgQWRhcHRhYmlsaXR5DQo+IA0KPiANCj4gSXQgZmVlbHMgd29ydGh3
aGlsZSB0byBtZSB0byBhZGQgc29tZSBkaXNjdXNzaW9uIGhlcmUgb2YgbGF5ZXJlZCBtb2Rl
bHMgYW5kIHRoZSBuZWVkIHRvIGF2b2lkIGxheWVyIGJvdW5kYXJ5IHZpb2xhdGlvbnMuICBU
aGluZ3MgbGlrZSBEUEkgYW5kIE5BVCBhbmQgRG9IIGFyZSB3aGF0IHlvdSBnZXQgaWYgeW91
IHByaW9yaXRpemUgeW91ciBidXNpbmVzcyBtb2RlbCBvdmVyIGxheWVycyBhbmQgZm9yZXRo
b3VnaHQuDQo+IA0KDQpJIHRoaW5rIHRoaXMgdmlldyBtYXkgYmUgbW9yZSBjb250cm92ZXJz
aWFsIHRoYW4gaXQgZmlyc3QgYXBwZWFycyA6KQ0KDQpJIGhhdmUgbm90IG1hZGUgYW55IGNo
YW5nZSBpbiB0aGlzIHJlZ2FyZCwgYnV0IGhhcHB5IHRvIGRvIHNvIGluIGNhc2UNCmZvbGtz
IHRoaW5rIHRoYXQgSSdtIG5vdCBzZW5zaW5nIHRoZSBjb25zZW5zdXMgb2YgdGhlIHJnIHBy
b3Blcmx5Lg0KDQo+PiAzLjMuMTkuICBBbm9ueW1pdHkNCj4gDQo+IA0KPiBJIHdvdWxkIGdy
b3VwIGFub255bWl0eSBhbmQgcHNldWRvbnltaXR5IGFkamFjZW50IHRvIGVhY2ggb3RoZXIs
IHNpbmNlIHRoZXnigJlyZSB2ZXJ5IHJlbGF0ZWQgZGlzY3Vzc2lvbnMsIHdpdGggdmVyeSBy
ZWxhdGVkIHByaW5jaXBsZXMuDQo+IA0KDQpEb25lLg0KDQo+PiAzLjMuMjAuICBSZW1lZHkg
YW5kIEF0dHJpYnV0aW9uDQo+IA0KPiANCj4gQW55Ym9keSBnb3QgYW4gZXhhbXBsZSBvZiB0
aGlzIHRoYXQgdGhleSBsaWtlLCB0aGF0IGRvZXNu4oCZdCBmbHkgaW4gdGhlIGZhY2Ugb2Yg
YWxsIHRoZSBvdGhlciBwcmluY2lwbGVzPyAgQmVjYXVzZSBhcyBzdGF0ZWQsIGl04oCZcyBh
IGxpdHRsZSBoYXJkIHRvIHJlY29uY2lsZSB3aXRoIHRoZSBvdGhlcnMuICBJdOKAmXMgYSBj
b21wbGV4IHdvcmxkLCB0aGVyZSBhcmUgbG90cyBvZiBkaWZmaWN1bHQtdG8tcmVjb25jaWxl
IHNpdHVhdGlvbnM7IHRoaXMganVzdCBkb2VzbuKAmXQgc2VlbSB0byBwcm92aWRlIG11Y2gg
Z3VpZGFuY2Ugb3IgaW5zaWdodC4NCj4gDQoNClJpZ2h0LiBUaGlzIGlzIGJlaW5nIGRpc2N1
c3NlZCBpbiBxdWl0ZSBzb21lIGxlbmd0aCBhbm90aGVyIHRocmVhZCwgYW5kDQpJJ3ZlIHNl
bnQgYSBwb3NzaWJsZSByZXNvbHV0aW9uIHRoZXJlLg0KDQo+IEFsbCBpbiBhbGwsIGdyZWF0
IHdvcmssIHNvcnJ5IEkgaGF2ZW7igJl0IGJlZW4gYWJsZSB0byBjb250cmlidXRlIG1vcmUg
b3IgZWFybGllciwgYW5kIG15IGFwb2xvZ2llcyBpZiBhbnkgb2YgdGhlIGFib3ZlIHJldHJl
YWRzIGFscmVhZHktaGFkIGFyZ3VtZW50cyB3aXRob3V0IGFkZGluZyB0byB0aGVtLg0KPiAN
Cg0KVGhhbmtzIGZvciB0aGUgZGV0YWlsZWQgcmV2aWV3LCBCaWxsLg0KDQotR3Vyc2hhYmFk
DQo=


From nobody Mon Feb 22 10:35:09 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 3A0B43A1ED5 for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:35:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H3=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 N5gJ-xi5zxeh for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:35:05 -0800 (PST)
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 439D83A1ECE for <hrpc@irtf.org>; Mon, 22 Feb 2021 10:35:04 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org B80A55806802D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1614018900; bh=piFtYqAbEgatpd5gULjs+S8I/EBe3DU/e3LZGPdSDoc=; h=From:To:Message-ID:Date:MIME-Version; b=sn+d921Gt75pcENPEhephOilG6tdrN5bapwmbaVW3J8LoYy7J6Sw7I4nCJvIIj7YA 28PJFxYKJeaCN18F35kVWXvaaKuOexH/DXxNpqhVTN0DLsZYHRtvogbp3jCLW2HByH 1YQVoVMnNRjijpadyc4xw5bQXx7tIueraozjdRWcvV+RjRG5Dz9Bf0f4z/IlSggcD2 QCX22fCevhpS4RMzbuoWRNyd7sENQpocj2ijaIig1QaVsDjrcG3a30rKYBHv+DAV0w AermeK5LLuk8xiExlhxD/uEKub+8EV1j4XX3sitr6lL2B4Q05luIh6aV4EBOroqei8 s8Gv2N0+oPNMQ==
From: Gurshabad Grover <gurshabad@cis-india.org>
To: Corinne Cath <corinnecath@gmail.com>, Hrpc <hrpc@irtf.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com>
Autocrypt: addr=gurshabad@cis-india.org; keydata= mQINBFriroIBEADfyDpCD8eborMUMXKtZzjo4t2KzrAlUVYgE/TFtrwUP+4Xw4dzakDIzST8 sVYmlXIWhM5NBBTZSQ190vsxrkbi0xxLcXYM2olZEtqkJ8zONZeZLBeGvcfMymtHqD4jHwYb Zm7OXnS45fWDL+HOoMP/VCwEn098rYfnllIkYQD1Gc28Ig+ywjGg8y5p0qMmmmhm2ckgLjnG MJX8t273MSc8wsn/UYH922yif3MQXmrzqgnRl9hRzf90SKqAw38bw7wccb55pIItloKYsi0r zYBKJSOPXn91Z21TpOSTy21M0MZYEAlDn1zeea+q8TggfHNWxOXoKrIm1pqZFRz0k+8i2siJ AHf8bRm/fhukA6szZ6b2nNPxjkAmOv9zvGu6RZGbmeLvQYVBSSnZ67ayZrkKwn7KIyAV6hQM /bVnD8eEZ2tZ0S8lxoZFYSNeMGt2b6WelFZO97/LbjxaJUHd9K8g5H0MwqN1NXoBxRwllVRC 3sVHVoWTBqnKo8qplzvQEAto69PpvuxxKTOFEJeQqmn1b/fo3sLRb4YiIg8Ax+Np7Huzzjk6 vKKgpIwIN7yEUj/ReWi/UA/W4wSg3XkcqTf7h73crnN/1At0PdgozbDV2UbcApaldStP4DfG UiQl0/7MiYLKapDDuSahmoeH3xrNnrzS9BAfuGHezzDbMyPLXQARAQABtCpHdXJzaGFiYWQg R3JvdmVyIDxndXJzaGFiYWRAY2lzLWluZGlhLm9yZz6JAj0EEwEIACcFAlriroICGyMFCQlm AYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQrbl/X+ubfC7/bQ//YQv7zqQE433xxsN/ 3GYKoOFccBy3WvV4DxrTskJ3n3k5lfcZolbc8TQksQOTzyerNt2ZA7fsGZa7eFSW+xR4Yq3/ C9o+5FOoHGhyZhb+x17MILhmyvyUNSj7SdKrRISgurMbV2Vv8LxmTcdrK6CdFF6JLH+opzU1 NlRKwZqROPgbYZEB2QFIUbGfgh2I5AXNyV2XbT7fagfkHk+v9AUV7POP2H1+AZ1xq6iFTm2o 9ufNZsp2bInsDohcVBKC3aH2cnFMjvIXpNoUOx8vb5A2xW0aBUTTJDB/uZw53WOg3kehrCNb ZkML3FnDZLRuu1e8DSWmwk5YIoDzt5bMCgfUwb0C6Q+JuM8lC+8CEEa9qamLc+fhvFAzcrWp VWuSaVeLdhe5NxmtlRYNZdGuKy6sRHjwsEWlwzRylhm74fiDR3aA1eIFsfmYLd4z+i1Fp23Y dHJf7/Gor2CmOxphog9DEA9WCuORXfx4De7hoMKwW4gWKw1A8B12Cv4EOkXmCsWsOnfDEarr 2Yl6elxkhQRfKjAesXb0cezRzZgwsWIsbeYsuWFF7Xi6IzUJ27lxU3p5PcyY8O8aDYOn+pu0 YFJ7s3u2VRRgptVZJmkcN3WTApXSHY8fGl5xAakM/bqFJj9uj5zlMnFN2EplC6/mQkfYfy2f siaGTP/GQV4OSuOeuMK5Ag0EWuKuggEQAJ4lAzB72gHw4+rbyxmQNNVmvgYVZPjFtO/MQdYi x1QwRP/gxxqPqTd/ZwQvmPGzXRKw10B7uKSRk6YP12+IG0mXJwHGp9q5CWJE0XNGqX3UWbAc KIzxqPNpsf8e6Bv7jdW0YwLBxJ+RW0NNL6uAxz0sr2frbnS+EZB3cU+zOZzp/9YfTUZO2lxF NzgJoErKe/HLp7aBeJXBBcwO0LQlIT80rTZx2KihBa/Ww/y9E9gV/HacJu/Ncb6E/G3e4xGj 9w9L+UW43q01wy+FSUKy9FLc7D40WqQsj8SXZEpl84SyLcJRoX3mtj59bX2SAN2VB2BAksTu qCh00IcIUGfyHziu5PwUWYM96gOhDSocP4wSeiQ8TwLzaffllz2qhdI296a9lCIYIeWVytEd NU9jJ3RbzXAgE0pnDauNXDaQv1FS5jYi8rlslJUxKnrS69BFNjM5RqQ16Cm0C4rKL7/a8wHC r4VjcjSCM8Lzv8YOOitJ9Yt4Y8SVfO5s3YvxcdSr56nX0W3B1kGbG1GpqWTzOgXzGF5bIsbV 7SPecwUs9ShvmLmZzDUxIQ68n4zj3lMZn5I+pP+Ew6nAAiuSmKdr5cygnCH/NVJzil07t+X4 uR6oKHBhuMFYF1c6Wxk36m+EZz5ZHFaT4rN0WDIJdAEqRzD0Z56V6ansDF8y+ksh0SHlABEB AAGJAiUEGAEIAA8FAlriroICGwwFCQlmAYAACgkQrbl/X+ubfC50rhAAloTaq/fZC1gtiVtU wOB+00gEkjgmzt+rLkW+l2EySTST7tje57W83UZwzCX746B2O//Bqardxz9R1Vr0VFiwHA8g 3qeBqPqiv1WoQch/iZ5d/1MxK4A9xDag1uyqLR8RuGlZ8lATmcP3IabKiuiBV4MlFZ7V2Ib6 5ToPf28xxSyjMzTjQObIG0e009uHlu2z+iQVshLyoyVVAOWWa88D6iuBDC/EtBRjlpjLAjuR YhWVYX6KHdVUijKMHN2RqjpX5O2wPL7NcMY/wsTq7EteUeI75hxFvargRXkEt1XR8t52LC0u IE2OjpzY5re/ROUbfsqL8trjAOrSJ+Fx5H8AYl9JaoVxohhxDZgNtgNtPbh/8Nnlf9daj/bh lZcTBO98XLQwMnyHGPdyhIodpWPq2C09Ys3TkQsbcdMMB1pqnEK5Vz1zIKkEEX7QVsLdrz7C 2CFsauc/9PHj+4njCHslXtzBOiVu5FXTnbCwPrLJs5iEUkUCb6qtE/2mSCTrAanzOTTOmqiM cnNTI1Tj0ht462S9VypppQnKCv8shGxXG7BadZTv+pNCA/WfB2kk1sS3ZwB0wBWX4p41fxs+ ArM9ew2SzQ/vBrEfO7ljPfZZmBqH4t/vgAZBnOtTxCGlPEIJqiMqtGHRqIqpiR20QfxEUuXI MfMfa9QJpisdNmqoUyc=
Message-ID: <9568132d-e35d-ab1f-82aa-769acbe199ed@cis-india.org>
Date: Tue, 23 Feb 2021 00:04:56 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com>
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: 4a4e1dd80dce9ac0d9378b25a0c059e8
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/z2byvhsnRC5r5H_UGv_PJmTVnII>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 22 Feb 2021 18:35:07 -0000

Dear Corinne,

Thank you very much for your comments! Please see below to track the
specific changes that were made in response to your feedback.

On 1/30/21 9:04 PM, Corinne Cath wrote:
>=20
> I think through out the document, it would be interesting (especially i=
n
> section 1 through 3.2.5) to see if you can rewrite such that you speak
> more directly to the protocol developers. I think that section 3.3 does
> that well, in terms of the tone it takes. As it clearly connects the
> actions of protocol developers to their potential outcomes.=C2=A0
> =20

Marked a tone review as a to-do for the next update.

> *1. Introduction*
>=20
> "It provides questions engineers should ask
>=20
>    themselves when developing or improving protocols if they want to
>    understand their potential human rights impact."
> >
>>> maybe if they want to understand potential human rights concerns? Imp=
act seems a little deterministic, as you also mention in the next sentenc=
e, I wonder if you can prove such direct impact between protocol developm=
ent in the IETF and impact on human rights.=20
>=20

Changed to something which I hope is less deterministic: "It provides
questions engineers should ask themselves when developing or improving
protocols if they want to understand how their decisions can potentially
influence the exercise of human rights on the Internet."

> "The research establishes
>=20
>    that human rights relate to standards and protocols, and offers a
>    common vocabulary of technical concepts that impact human rights and
>    how these technical concepts can be combined to ensure that the
>    Internet remains an enabling environment for human rights."
>=20
>=20
>>> same comment for the word impact, perhaps shape? influence? etc.=20
>=20

Changed.

>=20
>       3.1
>       <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sectio=
n-3.1>.
>       Human rights threats
>=20
>=20
>=20
>  "Protocols and standards can harm or enable the right to freedom of
>    expression, right to non-discrimination, right to equal protection,
>    right to participate in cultural life, arts and science, right to
>=20
> freedom of assembly and association, and the right to security. "
>=20
>=20
>>> again, deterministic language. Perhaps soften or add more concrete ex=
amples for context, that draw from current IETF discussions/standards.=20
>=20
>=20

Softened the language a bit.

>=20
>       3.3
>       <https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-05#sectio=
n-3.3>.
>       Guidelines for human rights considerations
>=20
>=20
>=20
> again, use of the word impact in the introduction.
>=20
>=20

Done.

Thanks again!
-Gurshabad


From nobody Mon Feb 22 10:36:59 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 7598F3A1EDB; Mon, 22 Feb 2021 10:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H3=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 bSAefYTaxRpk; Mon, 22 Feb 2021 10:36:55 -0800 (PST)
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 97A1D3A1ED5; Mon, 22 Feb 2021 10:36:52 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org 207505805C00A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1614019007; bh=f41VYzGLiExaRGQlpTeNJ466hSD1ZzpCb6zFIOkNcQQ=; h=From:To:Message-ID:Date:MIME-Version; b=NoAceTS10AStsSHK/1OxgZva9USLsiKLftbqI8UieflNGNCJHS4ixKG+Wkl9/tFKL M6RearQsYZiUj8In7bV/QF7c5gUCCSnlwmCaNJOStJa6VksTvXV/XQbon8o6bKPWxt o1j0uk2GyjXdPAVUl48q6bm0ZKL4v23kifEKTWOykkLpht3LNZy/iOKs2MDNg6c44j n7nzFo1jvYebejatfhidV5AFMjUPXMZvqogwqnWu48cacAEpjiPwDpUWv7PL2rlBiZ WiHhEY5Tgiv8VEVlayK9LRUHxvt6W45akbzPDBz9XosT+6yiTh2UUWhwJPGjQawa+0 GwwDgNIuPb9WA==
From: Gurshabad Grover <gurshabad@cis-india.org>
To: Joey S <joeysalazar=40article19.org@dmarc.ietf.org>, hrpc@irtf.org
References: <04c3b56e-8b1e-179c-d0b8-94bd930789db@article19.org>
Autocrypt: addr=gurshabad@cis-india.org; keydata= mQINBFriroIBEADfyDpCD8eborMUMXKtZzjo4t2KzrAlUVYgE/TFtrwUP+4Xw4dzakDIzST8 sVYmlXIWhM5NBBTZSQ190vsxrkbi0xxLcXYM2olZEtqkJ8zONZeZLBeGvcfMymtHqD4jHwYb Zm7OXnS45fWDL+HOoMP/VCwEn098rYfnllIkYQD1Gc28Ig+ywjGg8y5p0qMmmmhm2ckgLjnG MJX8t273MSc8wsn/UYH922yif3MQXmrzqgnRl9hRzf90SKqAw38bw7wccb55pIItloKYsi0r zYBKJSOPXn91Z21TpOSTy21M0MZYEAlDn1zeea+q8TggfHNWxOXoKrIm1pqZFRz0k+8i2siJ AHf8bRm/fhukA6szZ6b2nNPxjkAmOv9zvGu6RZGbmeLvQYVBSSnZ67ayZrkKwn7KIyAV6hQM /bVnD8eEZ2tZ0S8lxoZFYSNeMGt2b6WelFZO97/LbjxaJUHd9K8g5H0MwqN1NXoBxRwllVRC 3sVHVoWTBqnKo8qplzvQEAto69PpvuxxKTOFEJeQqmn1b/fo3sLRb4YiIg8Ax+Np7Huzzjk6 vKKgpIwIN7yEUj/ReWi/UA/W4wSg3XkcqTf7h73crnN/1At0PdgozbDV2UbcApaldStP4DfG UiQl0/7MiYLKapDDuSahmoeH3xrNnrzS9BAfuGHezzDbMyPLXQARAQABtCpHdXJzaGFiYWQg R3JvdmVyIDxndXJzaGFiYWRAY2lzLWluZGlhLm9yZz6JAj0EEwEIACcFAlriroICGyMFCQlm AYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQrbl/X+ubfC7/bQ//YQv7zqQE433xxsN/ 3GYKoOFccBy3WvV4DxrTskJ3n3k5lfcZolbc8TQksQOTzyerNt2ZA7fsGZa7eFSW+xR4Yq3/ C9o+5FOoHGhyZhb+x17MILhmyvyUNSj7SdKrRISgurMbV2Vv8LxmTcdrK6CdFF6JLH+opzU1 NlRKwZqROPgbYZEB2QFIUbGfgh2I5AXNyV2XbT7fagfkHk+v9AUV7POP2H1+AZ1xq6iFTm2o 9ufNZsp2bInsDohcVBKC3aH2cnFMjvIXpNoUOx8vb5A2xW0aBUTTJDB/uZw53WOg3kehrCNb ZkML3FnDZLRuu1e8DSWmwk5YIoDzt5bMCgfUwb0C6Q+JuM8lC+8CEEa9qamLc+fhvFAzcrWp VWuSaVeLdhe5NxmtlRYNZdGuKy6sRHjwsEWlwzRylhm74fiDR3aA1eIFsfmYLd4z+i1Fp23Y dHJf7/Gor2CmOxphog9DEA9WCuORXfx4De7hoMKwW4gWKw1A8B12Cv4EOkXmCsWsOnfDEarr 2Yl6elxkhQRfKjAesXb0cezRzZgwsWIsbeYsuWFF7Xi6IzUJ27lxU3p5PcyY8O8aDYOn+pu0 YFJ7s3u2VRRgptVZJmkcN3WTApXSHY8fGl5xAakM/bqFJj9uj5zlMnFN2EplC6/mQkfYfy2f siaGTP/GQV4OSuOeuMK5Ag0EWuKuggEQAJ4lAzB72gHw4+rbyxmQNNVmvgYVZPjFtO/MQdYi x1QwRP/gxxqPqTd/ZwQvmPGzXRKw10B7uKSRk6YP12+IG0mXJwHGp9q5CWJE0XNGqX3UWbAc KIzxqPNpsf8e6Bv7jdW0YwLBxJ+RW0NNL6uAxz0sr2frbnS+EZB3cU+zOZzp/9YfTUZO2lxF NzgJoErKe/HLp7aBeJXBBcwO0LQlIT80rTZx2KihBa/Ww/y9E9gV/HacJu/Ncb6E/G3e4xGj 9w9L+UW43q01wy+FSUKy9FLc7D40WqQsj8SXZEpl84SyLcJRoX3mtj59bX2SAN2VB2BAksTu qCh00IcIUGfyHziu5PwUWYM96gOhDSocP4wSeiQ8TwLzaffllz2qhdI296a9lCIYIeWVytEd NU9jJ3RbzXAgE0pnDauNXDaQv1FS5jYi8rlslJUxKnrS69BFNjM5RqQ16Cm0C4rKL7/a8wHC r4VjcjSCM8Lzv8YOOitJ9Yt4Y8SVfO5s3YvxcdSr56nX0W3B1kGbG1GpqWTzOgXzGF5bIsbV 7SPecwUs9ShvmLmZzDUxIQ68n4zj3lMZn5I+pP+Ew6nAAiuSmKdr5cygnCH/NVJzil07t+X4 uR6oKHBhuMFYF1c6Wxk36m+EZz5ZHFaT4rN0WDIJdAEqRzD0Z56V6ansDF8y+ksh0SHlABEB AAGJAiUEGAEIAA8FAlriroICGwwFCQlmAYAACgkQrbl/X+ubfC50rhAAloTaq/fZC1gtiVtU wOB+00gEkjgmzt+rLkW+l2EySTST7tje57W83UZwzCX746B2O//Bqardxz9R1Vr0VFiwHA8g 3qeBqPqiv1WoQch/iZ5d/1MxK4A9xDag1uyqLR8RuGlZ8lATmcP3IabKiuiBV4MlFZ7V2Ib6 5ToPf28xxSyjMzTjQObIG0e009uHlu2z+iQVshLyoyVVAOWWa88D6iuBDC/EtBRjlpjLAjuR YhWVYX6KHdVUijKMHN2RqjpX5O2wPL7NcMY/wsTq7EteUeI75hxFvargRXkEt1XR8t52LC0u IE2OjpzY5re/ROUbfsqL8trjAOrSJ+Fx5H8AYl9JaoVxohhxDZgNtgNtPbh/8Nnlf9daj/bh lZcTBO98XLQwMnyHGPdyhIodpWPq2C09Ys3TkQsbcdMMB1pqnEK5Vz1zIKkEEX7QVsLdrz7C 2CFsauc/9PHj+4njCHslXtzBOiVu5FXTnbCwPrLJs5iEUkUCb6qtE/2mSCTrAanzOTTOmqiM cnNTI1Tj0ht462S9VypppQnKCv8shGxXG7BadZTv+pNCA/WfB2kk1sS3ZwB0wBWX4p41fxs+ ArM9ew2SzQ/vBrEfO7ljPfZZmBqH4t/vgAZBnOtTxCGlPEIJqiMqtGHRqIqpiR20QfxEUuXI MfMfa9QJpisdNmqoUyc=
Message-ID: <11cffa08-9171-a45e-ece9-bc7e1847e549@cis-india.org>
Date: Tue, 23 Feb 2021 00:06:43 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <04c3b56e-8b1e-179c-d0b8-94bd930789db@article19.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Authenticated-As-Hash: 3c8a76879922505f22521320ab57e3bbe25ea7cc
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 63453eee11fb90e6254115624a40dc2b
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/0CXkdOQwVoJZhV30Z0VevtLHC2E>
Subject: Re: [hrpc] adding comments on draft-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, 22 Feb 2021 18:36:58 -0000

Hiya,

Thanks for the review, Joey! I've incorporated all the issues your
raised on Github. And some comments also below.

On 2/20/21 3:53 AM, Joey S wrote:
> Hi all, GG, Niels,
> 
> Thank you for all the work and effort put into this I-D.
> 
> After going over it, I'm wondering about the scope and tone of some
> sections;
> 
>   * "Abstract: It provides questions engineers should ask themselves
>     when developing or improving protocols if they want to understand
>     their potential human rights impact."
> 
> Are these guidelines aimed at IETF participants only? Or also for the
> organisations and companies using and expanding the protocols
> stardardised at the IETF? If the latter is part of the aim/scope, then
> the abstract could use some rephrasing since the developers are not the
> decision-makers in most scenarios that involve the planning, design,
> implementation, and deployment of a protocol or extension. Implementers
> might be a better term here since it encompasses both the
> decision-makers and the devs actively coding.
> 

I presume that these guidelines may be useful for companies and
implementers, but I do not think they are an intended primary audience
for this draft (and intentionally so). This document is primarily aimed
at those designing protocols and developing specifications.

A sentence in the introduction captures that "the [final] impact of a
protocol cannot solely be deduced from its design, but its usage and
implementation should also be studied to form a full protocol human
rights impact assessment." I personally think that this caveat is
implying the clarification on the scope, but happy to make this even
more explicit in the next versions if it is not clear already.

>   * Section 3.1: "several 'common' threats to human rights"
> 
> The meaning here doesn't seem clear to me. Do we mean, as phrased later
> in the document, "protocols and their (potential) impact" to human
> rights, or "human rights risks arising from potential misapplications of
> the protocol or technology"? Perhaps something along the lines of
> creating a "basis for discussion on whether the protocol adequately
> takes specific human rights threats into account" could also be included
> here for clarity.
> 

Thanks, this sentence has now been changed (as Bill suggested in their
review).

>   * Section 3.3 (and sub-sections 1-21):
> 
> I agree with CCS and also think it's nicely written regarding tone and
> scope, but it seems to be in a bit of a contrast with other sections of
> the I-D, specifically with 3.1 where the language and tone seem to be
> harsher/more narrow, as well as in its sub-sections 1-21;
> In hopes of more harmonious dialog (and less of the "hr-advocates vs
> developers" mentality and arguments some might have encountered), I
> think language here that is more collaborative might yield better
> results in practice and aid in opening dialog between different parties
> in other WGs/RGs when they use this draft as a reference or for reviews.
> Framing, for example, "Does your protocol maintain the confidentiality
> of metadata?" as "How can we ensure this protocol maintains the
> confidentiality of metadata?" instead, or "Does your protocol in any way
> allow for the data to be (intentionally or unintentionally) altered?" as
> "can the data handled by this protocol be (intentionally or
> unintentionally) altered? How can we prevent that?", could signal a
> shift where 'hr-advocates' are not seen as "regulators" (or trying to be
> regulators) but as the volunteers and contributors that also want to
> work together towards a better outcome. Sub-section 3.3.19. in paragraph
> 2 of the 'Explanation:' is a strong example, in my opinion, of a tone
> that might not be perceived as helpful or effective when we, as devs or
> advocates or participants working in public interest technologies, aim
> to have discussions with the devs/teams working on a protocol.
> 

Thanks, Joey. Could not address this feedback in the current update, but
have noted it in the to-do list that I have shared on the list.

>   * Sub-section 3.3.1:
> 
> This sub-section talks about "reliable even on low bandwidth and high
> latency connections". Here I wonder if we could give an example or talk
> about the impact that reliable connections have in the effective access
> to connectivity in remote/developing areas.
> 

Added: Encrypting connections, like done with HTTPS, can add a
significant network overhead and consequently make web resources less
accessible to those with low bandwidth and/or high latency connections.
[ref] Encrypting traffic is a net positive for privacy and
security, and thus protocol designers can acknowledge the tradeoffs of
connectivity made by such decisions.

>   * Sub-sections 3.3.14 and 3.3.19:
> 
> Lastly, and similar to issue #29 in github requesting explicit mention
> of 'Access to Information', although I see Anonymity and 'clear text /
> data encryption' mentioned in these sub-sections, I wonder (without
> implying some rights/technologies are more or less important than
> others) if they could be more explicitly mentioned across the draft or
> given a bit more visibility somewhere (their mention in sub-section
> 3.3.19. seems to me somewhat hidden since it's towards the end of the ID).
> 

Yes. Incorporated the edit you suggested on Github. We note in the
introduction that the draft "is by no means an attempt to exclude
specific rights"; and happy to incorporate any edits where you think we
may need to visibilise certain rights more.

Thank you.
-Gurshabad


From nobody Mon Feb 22 10:39:15 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 A90953A1DF3 for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:39:12 -0800 (PST)
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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=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 I9O65O8jBzUv for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:39:10 -0800 (PST)
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 B46A23A0B01 for <hrpc@irtf.org>; Mon, 22 Feb 2021 10:39:10 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org A23F25805C00A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1614019145; bh=FULOiDFfYSEh2ucJM2hkO0KBL1fM17ICkaApUO5/zXw=; h=From:To:Message-ID:Date:MIME-Version; b=C58cNvfsAzl3g0GpZr2oaVJgKP9q1rdlQWSokqKHJCK6E7Q2vara8wkqrzkiOPHFj lO1CX4c8fhSyiYeWObj2iol0mnVS7JL1EX+Mah0ZXccRE8ZipC5UhizoqZNjLPU9Do EEgRbeD+22Fjpelk7pfXNm/OTNEzWcmUyzC/C9PAV+BJhk5xG8NhkJa2UD3rv6RFxS 9qUYmYloAu9JmDUvztyXqlBr31i+P4Brz0Z/GyIiy+Oz3FsvQNeZ11Cw8gXi5EPo0r rbbFpuZ0SW1PFWm0uMf3mQ9pMNXsYUhAa0VbEjBWd00TcPZLvh1NksOq3EgOpsPtoC AR9vq1YjmrM3A==
From: Gurshabad Grover <gurshabad@cis-india.org>
To: farzaneh badii <farzaneh.badii@gmail.com>, Corinne Cath <corinnecath@gmail.com>
Cc: Hrpc <hrpc@irtf.org>
References: <CAD499eJqGbdodAJOQU94DPacy1_YkmnpKBLBdWpYXnYMeegojw@mail.gmail.com> <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com>
Autocrypt: addr=gurshabad@cis-india.org; keydata= mQINBFriroIBEADfyDpCD8eborMUMXKtZzjo4t2KzrAlUVYgE/TFtrwUP+4Xw4dzakDIzST8 sVYmlXIWhM5NBBTZSQ190vsxrkbi0xxLcXYM2olZEtqkJ8zONZeZLBeGvcfMymtHqD4jHwYb Zm7OXnS45fWDL+HOoMP/VCwEn098rYfnllIkYQD1Gc28Ig+ywjGg8y5p0qMmmmhm2ckgLjnG MJX8t273MSc8wsn/UYH922yif3MQXmrzqgnRl9hRzf90SKqAw38bw7wccb55pIItloKYsi0r zYBKJSOPXn91Z21TpOSTy21M0MZYEAlDn1zeea+q8TggfHNWxOXoKrIm1pqZFRz0k+8i2siJ AHf8bRm/fhukA6szZ6b2nNPxjkAmOv9zvGu6RZGbmeLvQYVBSSnZ67ayZrkKwn7KIyAV6hQM /bVnD8eEZ2tZ0S8lxoZFYSNeMGt2b6WelFZO97/LbjxaJUHd9K8g5H0MwqN1NXoBxRwllVRC 3sVHVoWTBqnKo8qplzvQEAto69PpvuxxKTOFEJeQqmn1b/fo3sLRb4YiIg8Ax+Np7Huzzjk6 vKKgpIwIN7yEUj/ReWi/UA/W4wSg3XkcqTf7h73crnN/1At0PdgozbDV2UbcApaldStP4DfG UiQl0/7MiYLKapDDuSahmoeH3xrNnrzS9BAfuGHezzDbMyPLXQARAQABtCpHdXJzaGFiYWQg R3JvdmVyIDxndXJzaGFiYWRAY2lzLWluZGlhLm9yZz6JAj0EEwEIACcFAlriroICGyMFCQlm AYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQrbl/X+ubfC7/bQ//YQv7zqQE433xxsN/ 3GYKoOFccBy3WvV4DxrTskJ3n3k5lfcZolbc8TQksQOTzyerNt2ZA7fsGZa7eFSW+xR4Yq3/ C9o+5FOoHGhyZhb+x17MILhmyvyUNSj7SdKrRISgurMbV2Vv8LxmTcdrK6CdFF6JLH+opzU1 NlRKwZqROPgbYZEB2QFIUbGfgh2I5AXNyV2XbT7fagfkHk+v9AUV7POP2H1+AZ1xq6iFTm2o 9ufNZsp2bInsDohcVBKC3aH2cnFMjvIXpNoUOx8vb5A2xW0aBUTTJDB/uZw53WOg3kehrCNb ZkML3FnDZLRuu1e8DSWmwk5YIoDzt5bMCgfUwb0C6Q+JuM8lC+8CEEa9qamLc+fhvFAzcrWp VWuSaVeLdhe5NxmtlRYNZdGuKy6sRHjwsEWlwzRylhm74fiDR3aA1eIFsfmYLd4z+i1Fp23Y dHJf7/Gor2CmOxphog9DEA9WCuORXfx4De7hoMKwW4gWKw1A8B12Cv4EOkXmCsWsOnfDEarr 2Yl6elxkhQRfKjAesXb0cezRzZgwsWIsbeYsuWFF7Xi6IzUJ27lxU3p5PcyY8O8aDYOn+pu0 YFJ7s3u2VRRgptVZJmkcN3WTApXSHY8fGl5xAakM/bqFJj9uj5zlMnFN2EplC6/mQkfYfy2f siaGTP/GQV4OSuOeuMK5Ag0EWuKuggEQAJ4lAzB72gHw4+rbyxmQNNVmvgYVZPjFtO/MQdYi x1QwRP/gxxqPqTd/ZwQvmPGzXRKw10B7uKSRk6YP12+IG0mXJwHGp9q5CWJE0XNGqX3UWbAc KIzxqPNpsf8e6Bv7jdW0YwLBxJ+RW0NNL6uAxz0sr2frbnS+EZB3cU+zOZzp/9YfTUZO2lxF NzgJoErKe/HLp7aBeJXBBcwO0LQlIT80rTZx2KihBa/Ww/y9E9gV/HacJu/Ncb6E/G3e4xGj 9w9L+UW43q01wy+FSUKy9FLc7D40WqQsj8SXZEpl84SyLcJRoX3mtj59bX2SAN2VB2BAksTu qCh00IcIUGfyHziu5PwUWYM96gOhDSocP4wSeiQ8TwLzaffllz2qhdI296a9lCIYIeWVytEd NU9jJ3RbzXAgE0pnDauNXDaQv1FS5jYi8rlslJUxKnrS69BFNjM5RqQ16Cm0C4rKL7/a8wHC r4VjcjSCM8Lzv8YOOitJ9Yt4Y8SVfO5s3YvxcdSr56nX0W3B1kGbG1GpqWTzOgXzGF5bIsbV 7SPecwUs9ShvmLmZzDUxIQ68n4zj3lMZn5I+pP+Ew6nAAiuSmKdr5cygnCH/NVJzil07t+X4 uR6oKHBhuMFYF1c6Wxk36m+EZz5ZHFaT4rN0WDIJdAEqRzD0Z56V6ansDF8y+ksh0SHlABEB AAGJAiUEGAEIAA8FAlriroICGwwFCQlmAYAACgkQrbl/X+ubfC50rhAAloTaq/fZC1gtiVtU wOB+00gEkjgmzt+rLkW+l2EySTST7tje57W83UZwzCX746B2O//Bqardxz9R1Vr0VFiwHA8g 3qeBqPqiv1WoQch/iZ5d/1MxK4A9xDag1uyqLR8RuGlZ8lATmcP3IabKiuiBV4MlFZ7V2Ib6 5ToPf28xxSyjMzTjQObIG0e009uHlu2z+iQVshLyoyVVAOWWa88D6iuBDC/EtBRjlpjLAjuR YhWVYX6KHdVUijKMHN2RqjpX5O2wPL7NcMY/wsTq7EteUeI75hxFvargRXkEt1XR8t52LC0u IE2OjpzY5re/ROUbfsqL8trjAOrSJ+Fx5H8AYl9JaoVxohhxDZgNtgNtPbh/8Nnlf9daj/bh lZcTBO98XLQwMnyHGPdyhIodpWPq2C09Ys3TkQsbcdMMB1pqnEK5Vz1zIKkEEX7QVsLdrz7C 2CFsauc/9PHj+4njCHslXtzBOiVu5FXTnbCwPrLJs5iEUkUCb6qtE/2mSCTrAanzOTTOmqiM cnNTI1Tj0ht462S9VypppQnKCv8shGxXG7BadZTv+pNCA/WfB2kk1sS3ZwB0wBWX4p41fxs+ ArM9ew2SzQ/vBrEfO7ljPfZZmBqH4t/vgAZBnOtTxCGlPEIJqiMqtGHRqIqpiR20QfxEUuXI MfMfa9QJpisdNmqoUyc=
Message-ID: <3ef199d7-7b8d-b1e2-bd78-72e86b9ecd90@cis-india.org>
Date: Tue, 23 Feb 2021 00:09:00 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAN1qJvDRHP5Bd5pwS=A2CkKErtM42VSbNYJwDLVTqXnzEZU9Rg@mail.gmail.com>
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: 6afe0509a8fa736d7bae96a824aab2db
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ENKDmfW_KzhzSTgT4jB1uz4w3bQ>
Subject: Re: [hrpc] Comment on draft-guidelines for RG Last Call
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, 22 Feb 2021 18:39:13 -0000

Thanks so much for your review, Farzaneh!

Just two thoughts in-line.

On 1/31/21 3:30 AM, farzaneh badii wrote:
> Hello
> =20
> 2.section 3.3.1 on connectivity, you mention that "considering the fact
> that network quality and conditions vary across geography and time it i=
s
> also important to design protocols such that they are reliable even on
> low bandwidth ...". Then in your example you say: Middleboxes (includin=
g
> NAT).... can create potential for abuse. NAT is a Network Address
> Translation protocol. I don't think it has anything to do with
> bandwidth. In this example you also mention CDNs. Are you suggesting
> that the developer should not consider "Middleboxes" protocols? I think
> you need to work on the example of section 3.3.1 some more to make it
> clearer.=C2=A0
>=20

Thanks, added an example that relates to bandwidth and connectivity. And
have marked as to-do to remove the unnecessary text from this section.

> 3. section 3.3.20 remedy and attribution=C2=A0
> This section worries me. As a=C2=A0 scholar I have worked on cyber
> attribution to some extent and believe=C2=A0in general when we have the=
 right
> processes in place,=C2=A0attribution is very important and can hold
> cyber-attackers accountable. I am aware of some of the attribution
> processes and unfortunately some threat intelligence firms and open
> source intelligence organizations can violate the privacy of individual=
s
> by profiling them. Also, uncontrolled attribution mechanisms can lead t=
o
> frivolous=C2=A0intellectual property claims. Both some threat intellige=
nce
> firms and IP firms have used WHOIS extensively in their favor to
> attribute cybersecurity attacks and bring forward IP claims. WHOIS
> protocol did not have the intention to actually identify organizations
> and individuals, but to make them "contactable".and it was still used
> and mined for so many years and those who have abused WHOIS have not
> been held accountable.When you suggest they consider "attribution" when
> developing protocols it concerns me because it is not enough that you
> limit attribution to organizations and states. These kinds of
> attributions can be used against individuals and until we do not have
> the right preserving processes to put in place for those who want to be
> in the attribution business, rights of the individual can be at risk.
> there are very privacy conscious=C2=A0cybersecurity researchers out the=
re but
> unfortunately that does not ensure a systematic=C2=A0practice of attrib=
ution
> in a fair manner. And you mention attribution to associations is fine
> and may not directly negatively impact human rights. Associations can
> themselves be at risk of frivolous=C2=A0attacks and frivolous=C2=A0attr=
ibution. I
> am concerned about this paragraph. I think we should have a conversatio=
n
> about it.
>=20

For now, I have changed the text to (very close to) what you suggested
subsequently in this thread. What you suggested reflects my views as
well. I did not sense a strong pushback on it in the thread. However,
given the comments about whether the text in the section has rg
consensus, I've kept this the discussion as a to-do.

Hope that's alright, and thanks again!

-Gurshabad


From nobody Mon Feb 22 10:42:35 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 E51753A1EE2 for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H3=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 xoZ4m3dRLNYy for <hrpc@ietfa.amsl.com>; Mon, 22 Feb 2021 10:42:32 -0800 (PST)
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 EFFB43A1E99 for <hrpc@irtf.org>; Mon, 22 Feb 2021 10:42:31 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cis-india.org 635B85805C00A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cis-india.org; s=6F901CFA-19A8-11E9-98F1-CB07954443DB; t=1614019346; bh=ZM2RnUfyVSXwg1kKcy92EBhlSdWE1H3/mxfTh8oupeg=; h=To:From:Message-ID:Date:MIME-Version; b=Azmo6YMZX3vkBcYafM/Ulre6A8aNLPL1hZMUNEYr3+LH+8kymjkFw83iJEjxGSOhj zgk37Ji4ljo82Yt8yYGgpBZvdSRHAeWwQZ229idvRg/DRldp99hG5MOo67DQK33CgU fSw4uuZ6PpCO9VIWDirv3yuk/n1C8Ue5FRq5XBO+Rxjap9hQ/U47sO9wCCDkA1uYjx Rb+oQYrBcq67TCpV/dypPPtwtUt0fhr29rl+XlLj9WYu2+AONS2gZox9gjnEbmS5rS qYGUlYD+rcibPWiJZHPlNc5l+NCtPimADwHLxS7a0ztV5LCSPWsvz+7hR9N195XB+g 7zdJ60t/iPDxA==
To: hrpc@irtf.org
References: <161401831901.15036.13588267175742697354@ietfa.amsl.com>
From: Gurshabad Grover <gurshabad@cis-india.org>
Autocrypt: addr=gurshabad@cis-india.org; keydata= mQINBFriroIBEADfyDpCD8eborMUMXKtZzjo4t2KzrAlUVYgE/TFtrwUP+4Xw4dzakDIzST8 sVYmlXIWhM5NBBTZSQ190vsxrkbi0xxLcXYM2olZEtqkJ8zONZeZLBeGvcfMymtHqD4jHwYb Zm7OXnS45fWDL+HOoMP/VCwEn098rYfnllIkYQD1Gc28Ig+ywjGg8y5p0qMmmmhm2ckgLjnG MJX8t273MSc8wsn/UYH922yif3MQXmrzqgnRl9hRzf90SKqAw38bw7wccb55pIItloKYsi0r zYBKJSOPXn91Z21TpOSTy21M0MZYEAlDn1zeea+q8TggfHNWxOXoKrIm1pqZFRz0k+8i2siJ AHf8bRm/fhukA6szZ6b2nNPxjkAmOv9zvGu6RZGbmeLvQYVBSSnZ67ayZrkKwn7KIyAV6hQM /bVnD8eEZ2tZ0S8lxoZFYSNeMGt2b6WelFZO97/LbjxaJUHd9K8g5H0MwqN1NXoBxRwllVRC 3sVHVoWTBqnKo8qplzvQEAto69PpvuxxKTOFEJeQqmn1b/fo3sLRb4YiIg8Ax+Np7Huzzjk6 vKKgpIwIN7yEUj/ReWi/UA/W4wSg3XkcqTf7h73crnN/1At0PdgozbDV2UbcApaldStP4DfG UiQl0/7MiYLKapDDuSahmoeH3xrNnrzS9BAfuGHezzDbMyPLXQARAQABtCpHdXJzaGFiYWQg R3JvdmVyIDxndXJzaGFiYWRAY2lzLWluZGlhLm9yZz6JAj0EEwEIACcFAlriroICGyMFCQlm AYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQrbl/X+ubfC7/bQ//YQv7zqQE433xxsN/ 3GYKoOFccBy3WvV4DxrTskJ3n3k5lfcZolbc8TQksQOTzyerNt2ZA7fsGZa7eFSW+xR4Yq3/ C9o+5FOoHGhyZhb+x17MILhmyvyUNSj7SdKrRISgurMbV2Vv8LxmTcdrK6CdFF6JLH+opzU1 NlRKwZqROPgbYZEB2QFIUbGfgh2I5AXNyV2XbT7fagfkHk+v9AUV7POP2H1+AZ1xq6iFTm2o 9ufNZsp2bInsDohcVBKC3aH2cnFMjvIXpNoUOx8vb5A2xW0aBUTTJDB/uZw53WOg3kehrCNb ZkML3FnDZLRuu1e8DSWmwk5YIoDzt5bMCgfUwb0C6Q+JuM8lC+8CEEa9qamLc+fhvFAzcrWp VWuSaVeLdhe5NxmtlRYNZdGuKy6sRHjwsEWlwzRylhm74fiDR3aA1eIFsfmYLd4z+i1Fp23Y dHJf7/Gor2CmOxphog9DEA9WCuORXfx4De7hoMKwW4gWKw1A8B12Cv4EOkXmCsWsOnfDEarr 2Yl6elxkhQRfKjAesXb0cezRzZgwsWIsbeYsuWFF7Xi6IzUJ27lxU3p5PcyY8O8aDYOn+pu0 YFJ7s3u2VRRgptVZJmkcN3WTApXSHY8fGl5xAakM/bqFJj9uj5zlMnFN2EplC6/mQkfYfy2f siaGTP/GQV4OSuOeuMK5Ag0EWuKuggEQAJ4lAzB72gHw4+rbyxmQNNVmvgYVZPjFtO/MQdYi x1QwRP/gxxqPqTd/ZwQvmPGzXRKw10B7uKSRk6YP12+IG0mXJwHGp9q5CWJE0XNGqX3UWbAc KIzxqPNpsf8e6Bv7jdW0YwLBxJ+RW0NNL6uAxz0sr2frbnS+EZB3cU+zOZzp/9YfTUZO2lxF NzgJoErKe/HLp7aBeJXBBcwO0LQlIT80rTZx2KihBa/Ww/y9E9gV/HacJu/Ncb6E/G3e4xGj 9w9L+UW43q01wy+FSUKy9FLc7D40WqQsj8SXZEpl84SyLcJRoX3mtj59bX2SAN2VB2BAksTu qCh00IcIUGfyHziu5PwUWYM96gOhDSocP4wSeiQ8TwLzaffllz2qhdI296a9lCIYIeWVytEd NU9jJ3RbzXAgE0pnDauNXDaQv1FS5jYi8rlslJUxKnrS69BFNjM5RqQ16Cm0C4rKL7/a8wHC r4VjcjSCM8Lzv8YOOitJ9Yt4Y8SVfO5s3YvxcdSr56nX0W3B1kGbG1GpqWTzOgXzGF5bIsbV 7SPecwUs9ShvmLmZzDUxIQ68n4zj3lMZn5I+pP+Ew6nAAiuSmKdr5cygnCH/NVJzil07t+X4 uR6oKHBhuMFYF1c6Wxk36m+EZz5ZHFaT4rN0WDIJdAEqRzD0Z56V6ansDF8y+ksh0SHlABEB AAGJAiUEGAEIAA8FAlriroICGwwFCQlmAYAACgkQrbl/X+ubfC50rhAAloTaq/fZC1gtiVtU wOB+00gEkjgmzt+rLkW+l2EySTST7tje57W83UZwzCX746B2O//Bqardxz9R1Vr0VFiwHA8g 3qeBqPqiv1WoQch/iZ5d/1MxK4A9xDag1uyqLR8RuGlZ8lATmcP3IabKiuiBV4MlFZ7V2Ib6 5ToPf28xxSyjMzTjQObIG0e009uHlu2z+iQVshLyoyVVAOWWa88D6iuBDC/EtBRjlpjLAjuR YhWVYX6KHdVUijKMHN2RqjpX5O2wPL7NcMY/wsTq7EteUeI75hxFvargRXkEt1XR8t52LC0u IE2OjpzY5re/ROUbfsqL8trjAOrSJ+Fx5H8AYl9JaoVxohhxDZgNtgNtPbh/8Nnlf9daj/bh lZcTBO98XLQwMnyHGPdyhIodpWPq2C09Ys3TkQsbcdMMB1pqnEK5Vz1zIKkEEX7QVsLdrz7C 2CFsauc/9PHj+4njCHslXtzBOiVu5FXTnbCwPrLJs5iEUkUCb6qtE/2mSCTrAanzOTTOmqiM cnNTI1Tj0ht462S9VypppQnKCv8shGxXG7BadZTv+pNCA/WfB2kk1sS3ZwB0wBWX4p41fxs+ ArM9ew2SzQ/vBrEfO7ljPfZZmBqH4t/vgAZBnOtTxCGlPEIJqiMqtGHRqIqpiR20QfxEUuXI MfMfa9QJpisdNmqoUyc=
Message-ID: <337803b6-74bc-41ce-042e-26df28b48a6d@cis-india.org>
Date: Tue, 23 Feb 2021 00:12:22 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <161401831901.15036.13588267175742697354@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Authenticated-As-Hash: 3c8a76879922505f22521320ab57e3bbe25ea7cc
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 4a4e1dd80dce9ac0d9378b25a0c059e8
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/RxK-aUPvGNF6A6aT-TE3HGIo4-Q>
Subject: Re: [hrpc] I-D Action: draft-irtf-hrpc-guidelines-06.txt
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, 22 Feb 2021 18:42:34 -0000

Hi, all.

First, huge thanks to everyone who has commented on draft-guidelines in
the past few weeks. A new version is up. I'm sorry that we could not get
to every review and comment, but have tried to reply in detail to each
thread where comments were addressed.

The updates to the draft are in lots of sections, so no easy way to
summarise them. But I hope the new version incorporates most edits
proposed by Bill, Joey, Corinne and Farzaneh.

To do for next version:
- do a 'tone' review: (1) speak directly to protocol developers where
possible; [0] and (2) be more solution-oriented [1]; (3) read more like
guidance than a list of 'bad practices' [4]
- fix mistakes in the 'connectivity' section [2]
- see whether changes are needed to internationalisation/localisation
based on recent reviews [2, 4]
- address Sandra Braman's review [3]
- discuss whether current text on attribution/legal remedy captures rg
consensus [2]

We hope to work through this to-do list in March. In the meanwhile, more
comments and pull requests always welcome :)

See you (virtually) at IETF110!

Thank you.
-Gurshabad

[0] Corinne's review:
https://mailarchive.ietf.org/arch/msg/hrpc/_bxVxqpbS695pJS3ZCLGsg4DtP0/
[1] Joey's review:
https://mailarchive.ietf.org/arch/msg/hrpc/4INmUIzCQ8j3Cr8X4QtZUzfctBQ/
[2] Farzaneh's comments and subsequent discussion:
https://mailarchive.ietf.org/arch/msg/hrpc/vppPmMvdTp-zlBsBzGM8Ql2Cv4M/
[3] Prof. Sandra Braman's review:
https://mailarchive.ietf.org/arch/msg/hrpc/aaz9Lf-J-2U4ZoH_azJWDJBbbJk/;
and subsequent correction:
https://mailarchive.ietf.org/arch/msg/hrpc/twLTNOBP2Q5YpuF6j0fy8RKHV2U/
[4] Bill Woodcock's review:
https://mailarchive.ietf.org/arch/msg/hrpc/ewl28FzImOj9TECiq0lD8Gy3LNE/

On 2/22/21 11:55 PM, internet-drafts@ietf.org wrote:
> 
> 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-06.txt
> 	Pages           : 31
> 	Date            : 2021-02-22
> 
> 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 are also htmlized versions available at:
> https://tools.ietf.org/html/draft-irtf-hrpc-guidelines-06
> https://datatracker.ietf.org/doc/html/draft-irtf-hrpc-guidelines-06
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-irtf-hrpc-guidelines-06
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
> 

