Re: [hrpc] hrpc Digest, Vol 4, Issue 1
Corinne Cath <cattekwaad@gmail.com> Tue, 20 January 2015 16:04 UTC
Received: from mx1.lan ([10.10.12.44] helo=mx1.greenhost.nl) by mailman.lan with esmtp (Exim 4.72) (envelope-from <cattekwaad@gmail.com>) id 1YDbIZ-00037J-MJ for hrpc@article19.io; Tue, 20 Jan 2015 17:04:59 +0100
Received: from mail-wi0-f171.google.com ([209.85.212.171]) by mx1.greenhost.nl with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <cattekwaad@gmail.com>) id 1YDbIX-0005Qm-9S for hrpc@article19.io; Tue, 20 Jan 2015 17:04:59 +0100
Received: by mail-wi0-f171.google.com with SMTP id l15so16944889wiw.4 for <hrpc@article19.io>; Tue, 20 Jan 2015 08:04:56 -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 :content-type; bh=H0JIX0D+WrgfjRMlILLyRI4wQtH2f+NKHLMIj+kEpNY=; b=V3J7pNlhvM9B81JT8pVoQEBegATJSrdNSARB2bPwsTkYqlhq4uubDzlXB8L0Epkqv1 mP70+4tGy2TGH8Jgej1aTQsCh4yxaaRhd6Ro9zAU7nK/VlytNu2BQvkD82FkAB3HmN6G Mdu3HHFMpnRR3kKANJpwhB2Ux2rFcMUfMTrmRoUChmq+OkI7hey9IFt6T3r6d753WigN YSBMZmFuEAnKHmyw87D6lK0TF3+e5va+T2hC9UxF/QN4qzrzHCg63DNvTfsHQdOFffJ1 v4JOBmYi09LFmuSyvqkaUBMmyCKCTCha2owXhnBvACy5w4J2o8HoszegcHb6TJOA59c3 2xDg==
MIME-Version: 1.0
X-Received: by 10.194.8.232 with SMTP id u8mr19101882wja.47.1421769896633; Tue, 20 Jan 2015 08:04:56 -0800 (PST)
Received: by 10.194.219.194 with HTTP; Tue, 20 Jan 2015 08:04:56 -0800 (PST)
In-Reply-To: <mailman.4060.1421768323.4946.hrpc@article19.io>
References: <mailman.4060.1421768323.4946.hrpc@article19.io>
Date: Tue, 20 Jan 2015 16:04:56 +0000
Message-ID: <CAD499eJcrnRvYV6o=RyNwooUDjv1KPGGDopBzwwgNujrD4e0CQ@mail.gmail.com>
From: Corinne Cath <cattekwaad@gmail.com>
To: hrpc@article19.io
Content-Type: multipart/alternative; boundary="047d7b5d348ca42b63050d1799e9"
X-Spam-Level: /
X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_50, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_LOW, SPF_PASS autolearn=disabled version=3.3.2
X-Spam-Score: -0.1
X-Virus-Scanned: by Greenhost Virus Scanner
X-Scan-Signature: 30614a4a4c7691bf7a48158e1ee8c11c
Subject: Re: [hrpc] hrpc Digest, Vol 4, Issue 1
X-BeenThere: hrpc@article19.io
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Human Rights Protocol Consideration Discussion list <hrpc.article19.io>
List-Unsubscribe: <https://lists.ghserv.net/mailman/options/hrpc>, <mailto:hrpc-request@article19.io?subject=unsubscribe>
List-Archive: <http://lists.ghserv.net/pipermail/hrpc>
List-Post: <mailto:hrpc@article19.io>
List-Help: <mailto:hrpc-request@article19.io?subject=help>
List-Subscribe: <https://lists.ghserv.net/mailman/listinfo/hrpc>, <mailto:hrpc-request@article19.io?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 16:05:00 -0000
Hello all, I would love to be involved in this research! I'm currently a master student at the Oxford Internet Institute and have a background in human rights and tech. please let me know in what capacity I could be of use. Best, Corinne On Tue, Jan 20, 2015 at 3:38 PM, <hrpc-request@article19.io> wrote: > Send hrpc mailing list submissions to > hrpc@article19.io > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ghserv.net/mailman/listinfo/hrpc > or, via email, send a message with subject or body 'help' to > hrpc-request@article19.io > > You can reach the person managing the list at > hrpc-owner@article19.io > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of hrpc digest..." > > > Today's Topics: > > 1. Summary ID on Human Rights presentation & next steps (Joana Varon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 Jan 2015 13:34:16 -0200 > From: Joana Varon <joana@varonferraz.com> > To: hrpc@article19.io > Subject: [hrpc] Summary ID on Human Rights presentation & next steps > Message-ID: <54BE7578.3010503@varonferraz.com> > Content-Type: text/plain; charset="iso-8859-1" > > Dear all, > > Happy 2015! We hope it will bring us the opportunity for enlightening > and rich debates on human rights and protocols over here. > > For the purpose of doing so, this is an attempt to summarize and and > structure our work. So, please, find underneath (a) the summary of the > session at IETF91 where we presented the Internet Draft on Human Rights > considerations for Internet protocols and (b) a brainstorming of some > research priorities for the coming time. > > At the bottom you can also find the links for the records of the session > and related documents. The full transcription of the Q&A are also here > attached. > > All comments, questions and suggestions for research methods and angles > are very welcome. We are also looking for more help of researchers who > are interested in helping us with researching specific RFCs to help us > refine the methodology. Please, feel free to ping us on or offlist. > > Best, > > Joana and Niels > > * > **a) Summary of the Session* > > An active debate about standards, protocols and human rights took place > during the meeting of the Security Area Advisory Group -- SAAG at IETF > 91, Hawaii. The discussion was framed by the Internet Draft "Proposal > for research on human rights protocol considerations". [1] > > The Draft departs from the work that has been done by IETF on privacy > and Internet protocols, such as RFC 6973 on Privacy Consideration > guidelines [2], suggesting that some standards and protocols can > solidify, enable or threaten human rights, such as freedom of expression > and the right to association online. The proposal aims to establish a > research group under the IRTF to study the structural relationship and > impact between Internet standards and protocols and freedom of > expression and association. > > A deeper rationale for presenting such proposal was explained during the > presentation at SAAG. The presenters, who are also the authors of this > note highlighted that the Internet was designed with freedom and > openness of communications as core values, but were also questioning > whether this a structural value that can or needs to be preserved on a > technical level. As the politicization of the Internet management space > increases, it is argued that IETF should have an active role to promote > a more structured and holistic approach. This would allow sustained > future proofing of standards and protocols to avoid ad hoc decisions > following incidents or disclosures at a variety of other foras and actors. > > The proposal raised some eyebrows and concerns about the politicization > of the work of the community. Dan Harkins posed that: "doing the human > rights study will likely politicize protocols. Not want the technology > to have political context. I want technology to be so unpolitical as > possible." This sparked a discussion with a rapid follow up by Justin, > who stated that "we have to stop pretending that technology is a > non-political decision", a remark that was followed by a round of > applause. One of the presenters responded that the research proposal was > exactly aimed at avoiding further politicization of protocols or the > community, but rather give the community time in a proper process to > define its position. > > Both John Levine and Alissa Cooper remarked that it is crucial to start > of with a focus on specific human rights, because it will help keep the > research manageable and help start the thinking about the balancing of > different rights. The presenters reaffirmed that the primary focus will > indeed be on the rights to freedom of expression and right to > association. Alissa Cooper mentioned the IAB ID on filtering > considerations [3] and the RFC Policy Considerations for Internet > Protocols [4] as relevant sources for research. > > Several RFCs already make quite explicit statement about the objectives > of the Internet, such as RFC1958 which mentions 'the community believes > that the goal [of the Internet] is connectivity, the tool is the > Internet Protocol'. It continues a bit further: 'The current > exponential growth of the network seems to show that connectivity is its > own reward, and is more valuable than any individual application such > as mail or the World-Wide Web.' This marks the intrinsic value of > connectivity which is facilitated by the Internet, both in principle, > and in practice. This shows that the underlying principles of the > Internet aim to preserve connectivity, which is fundamental and similar > to the part of article 19 of the Universal Declaration of Human Rights, > which defines a right to receive and to impart information. > > But there are also protocols that enable freedom of expression and > access to information in an unprecedented way, such as HTTP. Even though > there is not an explicit reference to rights in RFC7230, it does form > the basis for a rights enabling architecture. The challenge of the > research would be to seek out the specific protocol attribute(s) that > enable that protocol to affect a specific human right. > > The major challenge as next step would be to developed to develop an > appropriate methodology to research the existing implicit safeguards in > current standards and protocols, and making them explicit. Open > discussions already gave some insights for possible methodological > approaches. Richard Barnes suggests: "seems that you are reading RFCs > and that you are looking for statement on rights and human rights that > are laid out in RFCs. You might risk irritating people at least by > reading reading technical documents as political statements. I think it > might be more useful to use RFCs as a window into the rights that the > community that developed these RFCs presumes." Mark Nottingham also > proposed a perspective of stakeholder prioritization as described in ID > Representing Stakeholder Rights in Internet Protocols [5] which is as > already implemented at the W3C. > > Other very useful remarks were made during and after the session, as > well on the mailinglist [6] which are currently being used to improve > the next version of the draft, possibly, to be further discussed at a > Birds of Feather session in Dallas. > * > **b) Research priorities and next steps* > > The proceedings of this session lead the presenters and authors of the > ID to conclude that the subject and the research raised interest in the > community. Their aim is to continue the research work an produce an > updated ID before the Dallas meeting. > > The research in the coming time will focus on documenting the specific > protocol attributes that explicitly or implicitly affect specific human > rights. For achieving that, a research methodology will be further > developed; suggestions for the first steps consist of: > > a) improving the list of RFCs that possibly have attributes to the right > to freedom of expression and association; > > b) conduct interviews at the Dallas meeting to further understand the > intention that Area Directors and RFC authors have with specific > protocols and how rights play a role in that; > > c) set a common template to analyze standards and protocols describing > the exact features, functions, characteristics or entities that allow a > more defined understanding on the relation between them and the right to > freedom of expression and association. > > Nevertheless, these are just our suggestions to keep developing the ID > and the work ahead of it. Comments, suggestions, hints are more then > welcome and very much appreciated. > > > *References* > [1] Proposal for research on human rights protocol considerations, > http://www.ietf.org/id/draft-doria-hrpc-proposal-00.txt > > [2] RFC 6973 on Privacy Considerations for Internet Protocols > https://www.rfc-editor.org/rfc/rfc6973.txt > > [3] Technical Considerations for Internet Service Blocking and Filtering > http://www.ietf.org/archive/id/draft-iab-filtering-considerations-06.txts > > [4] Policy Considerations for Internet Protocols > https://tools.ietf.org/html/draft-morris-policy-cons-00 > > [5] Representing Stakeholder Rights in Internet Protocols, > https://tools.ietf.org/id/draft-nottingham-stakeholder-rights-00.txt > > [6] https://lists.ghserv.net/mailman/listinfo/hrpc > > * Other relevant links and information* > IETF91 SAAG Agenda: > http://www.ietf.org/proceedings/91/agenda/agenda-91-saag > IETF 91 SAAG minutes: > http://www.ietf.org/proceedings/91/minutes/minutes-91-saag > IETF 91 SAAG audio recording: > http://www.ietf.org/audio/ietf91/ietf91-coral3-20141113-1300-pm1.mp3 > Presentation starts at 40:15 > Presentation: > http://www.ietf.org/proceedings/91/slides/slides-91-saag-6.pdf > > -- > -- > Joana Varon > @joana_varon > https://antivigilancia.org > Fingerprint > 239D E977 32D0 28BC 297F 64B6 3B69 BDE4 016B 8E73 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.ghserv.net/pipermail/hrpc/attachments/20150120/67c01860/attachment.html > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: Transcription of the Q&A at SAAG IETF91 Hawaii.doc > Type: application/msword > Size: 29696 bytes > Desc: not available > URL: < > http://lists.ghserv.net/pipermail/hrpc/attachments/20150120/67c01860/attachment.doc > > > > ------------------------------ > > _______________________________________________ > hrpc mailing list > hrpc@article19.io > https://lists.ghserv.net/mailman/listinfo/hrpc > > End of hrpc Digest, Vol 4, Issue 1 > ********************************** > -- 'The management of normality is hard work'
- Re: [hrpc] hrpc Digest, Vol 4, Issue 1 Corinne Cath