[hrpc] Draft association : Extended litterature review

Stéphane Couture <listes@stephcouture.info> Tue, 23 June 2020 03:04 UTC

Return-Path: <listes@stephcouture.info>
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 453EB3A170F for <hrpc@ietfa.amsl.com>; Mon, 22 Jun 2020 20:04:22 -0700 (PDT)
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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 Hen6LowIbZmf for <hrpc@ietfa.amsl.com>; Mon, 22 Jun 2020 20:04:20 -0700 (PDT)
Received: from homere.koumbit.net (homere.koumbit.net [199.58.80.81]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61A093A170D for <hrpc@irtf.org>; Mon, 22 Jun 2020 20:04:20 -0700 (PDT)
Received: from mail-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: steph@stephcouture.info) by homere.koumbit.net (Postfix) with ESMTPSA id F2E301E41B1B for <hrpc@irtf.org>; Mon, 22 Jun 2020 23:04:18 -0400 (EDT)
Received: by mail-wr1-f47.google.com with SMTP id a6so16930198wrm.4 for <hrpc@irtf.org>; Mon, 22 Jun 2020 20:04:18 -0700 (PDT)
X-Gm-Message-State: AOAM530KMcUKQTMV2+cIRZj2pX1/AfMvbeDnUgadyOKXxJxpavbg4oVt FLjBR5A9ewEzWmruwRYZgcdX25JK2HksYKcmEEg=
X-Google-Smtp-Source: ABdhPJyucYBf9B4JyyuFlyxp24Im02EsaYmBhKAOYco4AwyNhYNdLryFPkDZneFVE7rRvuZv5CVfZNsPxU1Bk9uxJN4=
X-Received: by 2002:adf:fd48:: with SMTP id h8mr24002124wrs.226.1592881457666; Mon, 22 Jun 2020 20:04:17 -0700 (PDT)
MIME-Version: 1.0
From: Stéphane Couture <listes@stephcouture.info>
Date: Mon, 22 Jun 2020 23:04:06 -0400
X-Gmail-Original-Message-ID: <CANZrNV_RW4aGK+cJS+_DP5j=yG7QDF2gsjzkMgvuqUCRTuqUhQ@mail.gmail.com>
Message-ID: <CANZrNV_RW4aGK+cJS+_DP5j=yG7QDF2gsjzkMgvuqUCRTuqUhQ@mail.gmail.com>
To: Hrpc <hrpc@irtf.org>
Content-Type: multipart/mixed; boundary="000000000000743a5505a8b79d69"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/RdVhmM7dQwqGXH82M9bez2_gGwk>
Subject: [hrpc] Draft association : Extended litterature review
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, 23 Jun 2020 03:04:22 -0000

Dear all,

I'd like to finally send you - in odt format, not on github (sorry for
this) - the work I did in expanding the literature review on draft
association. Thank you  Mallory for a the few working sessions we had in
the last weeks on this, and to Melinda Shore for converting the document in
Word and all other who discussed with me before (Niels and Avri, notably)

At this point, I'd like to pass the responsibility of the draft to someone
else as I have difficulties bringing this draft to another step, both
because of lack of time and lack of vision on how to proceed from there
while keeping the "spirit" of the initial draft.

In this document, I am only sending you the first part of the draft
(literature review), which is the part I worked. My approach was to start
with what exists in the literature review, and then raise questions that
are relevant to IETF and protocol development more broadly. The section on
"Cases and examples" is not included in this document, as I did not work on
it, and still don't know what to do with it. In particular, I feel it is
not aligned with the questions raised by the literature.

One important thing in this document is that we tried (again) to change the
central question. It is now : "*What are the considerations of the right to
freedom of assembly and association for protocol development?*", which
seems more aligned to the research group title. The original question was
"How does the architecture of the internet enable and/or inhibit the right
to freedom of assembly and association?". I think these two questions
do not orient us exactly to the same analysis, something that I feel might
be important to note.

And here are other questions I felt were raised from the literature review.
Maybe just raising the questions could be a good contribution in itself...

1. As a general matter, what are the features of protocols that enable
freedom of association and assembly? Can protocols facilitate agency of
membership in associations, assemblies and interactions? Where in the stack
do we care for FAA?

2. Does protocol development sufficiently consider the enabling of freedom
of association without discrimination as to race, colour, national, ethnic
origin?

3.  Does protocol development sufficiently consider usable and accessible
formats and technologies appropriate for persons with different kinds of
disabilities?

4.  Is it possible to distinguish “peaceful” and “non-peaceful” association
from the perspective of protocol development? If yes, can and should
protocols be designed to limit “non-peaceful” association?

5. In particular, should protocols be designed to enable legitimate
limitations on association in the interests of “national security or public
safety, public order, the protection of public health or morals or the
protection of the rights and freedoms of others”, as stated in the ICCPR
article 21?

6. Can a protocol be designed to legitimately exclude someone from an
association?

7. In general, what kind of human rights impact assessments should be made
to incorporate the rights to freedom of peaceful assembly and of
association when developing protocols, as recommended by SpecialRapporteur
on the rights to freedom of peaceful assembly and of association.

I hope this would be helpful,

Best,

Stéphane