Re: [hrpc] resolving pending charter issues

Corinne Cath <cattekwaad@gmail.com> Sat, 28 November 2015 19:28 UTC

Return-Path: <cattekwaad@gmail.com>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED281B3479 for <hrpc@ietfa.amsl.com>; Sat, 28 Nov 2015 11:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level:
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 hk0f3z9xSnWg for <hrpc@ietfa.amsl.com>; Sat, 28 Nov 2015 11:28:21 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 1403A1B347C for <hrpc@irtf.org>; Sat, 28 Nov 2015 11:28:21 -0800 (PST)
Received: by wmvv187 with SMTP id v187so107095398wmv.1 for <hrpc@irtf.org>; Sat, 28 Nov 2015 11:28:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FBjnUULAnrtnaQQrgPaBbcmpfVu80dcs1Qypq9vWCwU=; b=EC7rdyUkJBU1sz3IMMmTwuK9nHeA82rENZA2rbOnW8ak4wU/HZYIMTzrGWwyd2ZAd6 SrVxf1pfx9v/A9VKyu/kQLfRs/aUt8hcDt1k/EnQnElzonemUcCFksTAicYt/dUnC+9Y rWGta+mgojBJK5heqgtK7bB3g4itar9xQJGfliAF4m427Ukncb9oQckmRBj2fdvVKLWx i7maVLLGNC84kieYbnYWLdFSD7nYmIYLfA2n37e6NntxzhewGJIairtIcIO1YmC8bKJ4 X6/iykjp7MEpnriFjWxvhjzieLbU2SYRz5BJrqk5riTN3BOtfX/JZDWBTYOV5jUXpfsv YIDw==
MIME-Version: 1.0
X-Received: by 10.28.23.83 with SMTP id 80mr18462690wmx.78.1448738899454; Sat, 28 Nov 2015 11:28:19 -0800 (PST)
Received: by 10.194.89.129 with HTTP; Sat, 28 Nov 2015 11:28:19 -0800 (PST)
In-Reply-To: <56587CB4.2000809@article19.org>
References: <5654E952.3070707@article19.org> <45272FFA14C4DA4D9E98923BA818A06D153B211D@ADFAPWEXMBX02.ad.adfa.edu.au> <56587CB4.2000809@article19.org>
Date: Sat, 28 Nov 2015 19:28:19 +0000
Message-ID: <CAD499eKxdgROSArwBcngD9xDojdEAcZpgCEFig2NjM6DKzhKCg@mail.gmail.com>
From: Corinne Cath <cattekwaad@gmail.com>
To: Niels ten Oever <niels@article19.org>
Content-Type: multipart/alternative; boundary="001a1146e1a279724e05259ecf00"
Archived-At: <http://mailarchive.ietf.org/arch/msg/hrpc/rdkZZ6FITkYUgToAMAlq06otYWw>
Cc: Stanley Shanapinda <Stanley.Shanapinda@student.adfa.edu.au>, "hrpc@irtf.org" <hrpc@irtf.org>
Subject: Re: [hrpc] resolving pending charter issues
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "niels@article19.org" <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, 28 Nov 2015 19:28:25 -0000

Looks great!

Minor suggestion: change 'expose' (the relation between protocols and human
rights) to 'clarify' (the relation between protocols and human rights).
Expose feels a little like, I open the hood of the car and there by expose
its underlying workings but what we are really doing goes one step beyond
that we are actually trying to understand and make explicit the relations
between protocols and human rights. But might be nit-picking.

Best,

Corinne

On Fri, Nov 27, 2015 at 3:54 PM, Niels ten Oever <niels@article19.org>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi Stanley,
>
> Thanks a lot for your question. Privacy is not specifically mentioned
> because the problem of security as well as privacy are already much
> better understood in the IETF than other rights concepts.
> Privacy for instance is already mentioned in RFC1087 [0] and
> culminated in the great document RFC6973 [1] to which we are referring
> in the charter.
>
> So I would think it is sufficiently covered, let me know if after this
> you still think differently.
>
> Another nice piece of reading on this topic is by Nick Doty [2].
>
> Happy to discuss!
>
> Best,
>
> Niels
>
>
>
> [0] https://tools.ietf.org/html/rfc1087
> [1] https://tools.ietf.org/html/rfc6973
> [2] https://npdoty.name/privacy-reviews/iwpe/
>
> Niels ten Oever
> Head of Digital
>
> Article 19
> www.article19.org
>
> PGP fingerprint    8D9F C567 BEE4 A431 56C4
>                    678B 08B5 A0F2 636D 68E9
>
> On 11/26/2015 01:53 AM, Stanley Shanapinda wrote:
> > Dear All, Thanks Niels, it looks and reads pretty well. Is there a
> > particular reason "the right to privacy' was not specified as well
> > but is simply implied in the overall human rights context? One of
> > the fundamental issues considered in every protocol is security,
> > i.e. "security" from unauthorized access and interference. Secure
> > communications denotes "private' communications, In would like to
> > think. Thanks and regards Stanley
> > ________________________________________ From: Niels ten Oever
> > [niels@article19.org] Sent: Wednesday, November 25, 2015 9:48 AM
> > To: hrpc@irtf.org Subject: [hrpc] resolving pending charter issues
> >
> > Hello everyone,
> >
> > I looked at all comments provided on this list and other list and
> > have tried to resolve them below. Let me know what you think. The
> > edited version you can find on here on git:
> > https://github.com/nllz/IRTF-HRPC/blob/master/hrpc%20charter.txt
> >
> > Looking forward to hear if any questions, comments or burning
> > issues remain.
> >
> > Best,
> >
> > Niels
> >
> >
> > Background The Human Rights Protocol Consideration Proposed
> > Research Group is chartered to research whether standards and
> > protocols can enable, strengthen or threaten human rights, as
> > defined in the Universal Declaration of Human Rights (UDHR) [0] and
> > the International Covenant on Civil and Political Rights (ICCPR)
> > [1], specifically, but not limited to the right to freedom of
> > expression and the right to freedom of assembly.
> >
> > The research group takes as its starting point the problem
> > statement that human-rights-enabling characteristics of the
> > Internet might be degraded if they're not properly defined,
> > described and sufficiently taken into account in protocol
> > development. Not protecting these characteristics could result in
> > (partial) loss of functionality and connectivity.
> >
> > # Mat Ford pointed out that this is not a direct quote from
> > RFC1958, so # I changed 'stated in' into 'evinced by'.
> >
> > As evinced by RFC 1958, the Internet aims to be the global network
> > of networks that provides unfettered connectivity to all users at
> > all times and for any content. Open, secure and reliable
> > connectivity is essential for rights such as freedom of expression
> > and freedom of association. Since the Internet's objective of
> > connectivity makes it an enabler of human rights, its architectural
> > design converges with the human rights framework.
> >
> > # Both Ted Hardie and Robin Wilton made the remark that the
> > sentence # "Concerns for freedom of expression and association were
> > a strong part # of the world-view of the community involved in
> > developing the first # Internet protocols." might be a stretch, so
> > I removed it.
> >
> > The Internet was designed with freedom and openness of
> > communications as core values. But as the scale and the
> > industrialization of the Internet has grown greatly, the influence
> > of such world-views started to compete with other values.
> >
> > # Ted Hardie suggested 'explore' instead of 'expose' since 'exposed
> > # might sound a bit hostile. I have no problems with that.
> >
> > This research group aims to explore the relations between human
> > rights and protocols and to provide guidelines to inform future
> > protocol development and decision making where protocols impact
> > the effective exercise of the rights to freedom of expression or
> > association.
> >
> > Objective This research has two major aims: - to expose the
> > relation between protocols and human rights, with a focus on the
> > rights to freedom of expression and freedom of assembly, and
> >
> > - to propose guidelines to protect the Internet as a human-rights-
> >  enabling environment in future protocol development, in a manner
> > similar to the work done for Privacy Considerations in RFC 6973.
> >
> > # Introducing awareness raising as objective as per comment of
> > Stephen # and supported by Robin and dkg
> >
> > - to increase the awareness in both the human rights community and
> > the technical community on the importance of the technical
> > workings of the Internet and its impact on human rights.
> >
> > Outputs The research group plans on using  a variety of research
> > methods to create different outputs including (but not limited
> > to):
> >
> > # As Lars and Mat Ford pointed out, IRSG RFC track should be IRSG
> > RFC # stream, and a Dirk pointed out 'tracking' might be a bit
> > vague, to I # replaced it with 'documenting the progress'
> >
> > - Internet drafts - (some of which may be put on IRSG RFC stream)
> > These would concern documenting the progress of the project,
> > methodology, and would define any possible protocol
> > considerations.
> >
> > - Policy and academic papers For in depth analysis and discussion
> > on the relationship between human rights and the Internet
> > architecture and protocols.
> >
> > # Based on the comments of Mary Burnes 'a diverse set' is
> > introduced # in the following para:
> >
> > - Film and textual interviews with a diverse set of community
> > members, to give an accessible insight into the variety of
> > opinions on this topic represented in the IETF.
> >
> > - Data analysis and visualization To research and visualize the
> > language used in current and historic RFCs and mailinglist
> > discussions to expose core architectural principles, language and
> > deliberations on human rights of those affected by the network.
> >
> > # As suggested by Seda and supported by dkg, including some
> > language # suggestion from me:
> >
> > - Protocol analysis Data analysis and visualization of (existing)
> > protocols in the wild to research their concrete impact on human
> > rights.
> >
> > Membership Membership is open to any interested parties who intend
> > to remain current with the published documents and mailing list
> > issues.
> >
> > [0] http://www.un.org/en/documents/udhr/ [1]
> > http://www.ohchr.org/EN/ProfessionalInterest/Pages/CCPR.aspx
> >
> >
> >
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJWWHy0AAoJEAi1oPJjbWjpGkoH/1dmcKIXgwNfW3FitXoyrdaq
> EZoQo1DhOCCPXm/zHBkYs+fPIgztRFmF1asIxDHstB6AUdn5G12a+z+4Jn8vYwTg
> MKyGjpewQzN+LaVR494FyGvLJKih5xumWP6mZNLWIcNu1KxjhNGBT1GGjordyCtu
> JuEB6YYFRM/iH9NClPez9MCll0sunN5lIpdGMkI+nJT91erD487IvQdGzcBhYWS8
> OFcsCW3FEYpvmpyJhxcHGPFdkQANSAgjpISzmno9bX52yp+fqzJrSAHETan+cv2j
> slq33MMbqi8jcXHCsYbGYFKw/Mq7binNf/tze/Weu3iO5Ea3fdMWNT6CvbWMo7c=
> =gWV/
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>



-- 


'The management of normality is hard work'