File: rfc8280.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (4533 lines) | stat: -rw-r--r-- 267,022 bytes
parent folder | download | duplicates (2)
<pre>Internet Research Task Force (IRTF)                         N. ten Oever
Request for Comments: 8280                                    ARTICLE 19
Category: Informational                                          C. Cath
ISSN: 2070-1721                                Oxford Internet Institute
                                                            October 2017


           <span class="h1">Research into Human Rights Protocol Considerations</span>

Abstract

   This document aims to propose guidelines for human rights
   considerations, similar to the work done on the guidelines for
   privacy considerations (<a href="./rfc6973">RFC 6973</a>).  The other parts of this document
   explain the background of the guidelines and how they were developed.

   This document is the first milestone in a longer-term research
   effort.  It has been reviewed by the Human Rights Protocol
   Considerations (HRPC) Research Group and also by individuals from
   outside the research group.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Research Task Force
   (IRTF).  The IRTF publishes the results of Internet-related research
   and development activities.  These results might not be suitable for
   deployment.  This RFC represents the consensus of the Human Rights
   Protocol Considerations Research Group of the Internet Research Task
   Force (IRTF).  Documents approved for publication by the IRSG are not
   a candidate for any level of Internet Standard; see <a href="./rfc7841#section-2">Section&nbsp;2 of
   RFC 7841</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc8280">https://www.rfc-editor.org/info/rfc8280</a>.













<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.








































<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
   <a href="#section-2">2</a>. Vocabulary Used .................................................<a href="#page-6">6</a>
   <a href="#section-3">3</a>. Research Questions .............................................<a href="#page-12">12</a>
   <a href="#section-4">4</a>. Literature and Discussion Review ...............................<a href="#page-12">12</a>
   <a href="#section-5">5</a>. Methodology ....................................................<a href="#page-15">15</a>
      <a href="#section-5.1">5.1</a>. Data Sources ..............................................<a href="#page-17">17</a>
           <a href="#section-5.1.1">5.1.1</a>. Discourse Analysis of RFCs .........................<a href="#page-17">17</a>
           <a href="#section-5.1.2">5.1.2</a>. Interviews with Members of the IETF Community ......<a href="#page-17">17</a>
           <a href="#section-5.1.3">5.1.3</a>. Participant Observation in Working Groups ..........<a href="#page-17">17</a>
      <a href="#section-5.2">5.2</a>. Data Analysis Strategies ..................................<a href="#page-18">18</a>
           5.2.1. Identifying Qualities of Technical Concepts
                  That Relate to Human Rights ........................<a href="#page-18">18</a>
           <a href="#section-5.2.2">5.2.2</a>. Relating Human Rights to Technical Concepts ........<a href="#page-20">20</a>
           5.2.3. Mapping Cases of Protocols, Implementations, and
                  Networking Paradigms That Adversely Impact Human
                  Rights or Are Enablers Thereof .....................<a href="#page-21">21</a>
   <a href="#section-6">6</a>. Model for Developing Human Rights Protocol Considerations ......<a href="#page-40">40</a>
      <a href="#section-6.1">6.1</a>. Human Rights Threats ......................................<a href="#page-40">40</a>
      <a href="#section-6.2">6.2</a>. Guidelines for Human Rights Considerations ................<a href="#page-42">42</a>
           <a href="#section-6.2.1">6.2.1</a>. Connectivity .......................................<a href="#page-43">43</a>
           <a href="#section-6.2.2">6.2.2</a>. Privacy ............................................<a href="#page-43">43</a>
           <a href="#section-6.2.3">6.2.3</a>. Content Agnosticism ................................<a href="#page-44">44</a>
           <a href="#section-6.2.4">6.2.4</a>. Security ...........................................<a href="#page-45">45</a>
           <a href="#section-6.2.5">6.2.5</a>. Internationalization ...............................<a href="#page-46">46</a>
           <a href="#section-6.2.6">6.2.6</a>. Censorship Resistance ..............................<a href="#page-47">47</a>
           <a href="#section-6.2.7">6.2.7</a>. Open Standards .....................................<a href="#page-48">48</a>
           <a href="#section-6.2.8">6.2.8</a>. Heterogeneity Support ..............................<a href="#page-50">50</a>
           <a href="#section-6.2.9">6.2.9</a>. Anonymity ..........................................<a href="#page-51">51</a>
           <a href="#section-6.2.10">6.2.10</a>. Pseudonymity ......................................<a href="#page-51">51</a>
           <a href="#section-6.2.11">6.2.11</a>. Accessibility .....................................<a href="#page-53">53</a>
           <a href="#section-6.2.12">6.2.12</a>. Localization ......................................<a href="#page-53">53</a>
           <a href="#section-6.2.13">6.2.13</a>. Decentralization ..................................<a href="#page-54">54</a>
           <a href="#section-6.2.14">6.2.14</a>. Reliability .......................................<a href="#page-55">55</a>
           <a href="#section-6.2.15">6.2.15</a>. Confidentiality ...................................<a href="#page-56">56</a>
           <a href="#section-6.2.16">6.2.16</a>. Integrity .........................................<a href="#page-58">58</a>
           <a href="#section-6.2.17">6.2.17</a>. Authenticity ......................................<a href="#page-59">59</a>
           <a href="#section-6.2.18">6.2.18</a>. Adaptability ......................................<a href="#page-60">60</a>
           <a href="#section-6.2.19">6.2.19</a>. Outcome Transparency ..............................<a href="#page-61">61</a>
   <a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-61">61</a>
   <a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-61">61</a>
   <a href="#section-9">9</a>. Research Group Information .....................................<a href="#page-62">62</a>
   <a href="#section-10">10</a>. Informative References ........................................<a href="#page-62">62</a>
   Acknowledgements ..................................................<a href="#page-80">80</a>
   Authors' Addresses ................................................<a href="#page-81">81</a>





<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   "There's a freedom about the Internet: As long as we accept the rules
   of sending packets around, we can send packets containing anything to
   anywhere."  [<a href="#ref-Berners-Lee">Berners-Lee</a>]

   "The Internet isn't value-neutral, and neither is the IETF."
   [<a href="./rfc3935" title="&quot;A Mission Statement for the IETF&quot;">RFC3935</a>]

   The ever-growing interconnectedness of the Internet and society
   increases the impact of the Internet on the lives of individuals.
   Because of this, the design and development of the Internet
   infrastructure also have a growing impact on society.  This has led
   to a broad recognition that human rights [<a href="#ref-UDHR" title="&quot;The Universal Declaration of Human Rights&quot;">UDHR</a>] [<a href="#ref-ICCPR" title="&quot;International Covenant on Civil and Political Rights&quot;">ICCPR</a>] [<a href="#ref-ICESCR" title="&quot;International Covenant on Economic, Social and Cultural Rights&quot;">ICESCR</a>] have
   a role in the development and management of the Internet [<a href="#ref-UNGA2013" title="&quot;UN General Assembly Resolution &quot;">UNGA2013</a>]
   [<a href="#ref-NETmundial">NETmundial</a>].  It has also been argued that the Internet should be
   strengthened as an enabling environment for human rights [<a href="#ref-Brown" title="&quot;A Prehistory of Internet Governance&quot;">Brown</a>].

   This document aims to (1) expose the relationship between protocols
   and human rights, (2) propose possible guidelines to protect the
   Internet as an enabling environment for human rights in future
   protocol development, in a manner similar to the work done for
   privacy considerations [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>], and (3) increase the awareness, in
   both the human rights community and the technical community, of the
   importance of the technical workings of the Internet and its impact
   on human rights.

   Document authors who want to apply this work to their own can go
   directly to <a href="#section-6">Section 6</a> of this document.

   Open, secure, and reliable connectivity is necessary (although not
   sufficient) to exercise human rights such as freedom of expression
   and freedom of association [<a href="#ref-FOC" title="&quot;The Tallinn Agenda - Recommendations for Freedom Online&quot;">FOC</a>], as defined in the Universal
   Declaration of Human Rights [<a href="#ref-UDHR" title="&quot;The Universal Declaration of Human Rights&quot;">UDHR</a>].  The purpose of the Internet is
   to be a global network of networks that provides unfettered
   connectivity to all users, and for any content [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>].  This
   objective of stimulating global connectivity contributes to the
   Internet's role as an enabler of human rights.  The Internet has
   given people a platform to exchange opinions and gather information;
   it has enabled people of different backgrounds and genders to
   participate in the public debate; it has also allowed people to
   congregate and organize.  Next to that, the strong commitment to
   security [<a href="./rfc1984" title="&quot;IAB and IESG Statement on Cryptographic Technology and the Internet&quot;">RFC1984</a>] [<a href="./rfc3365" title="&quot;Strong Security Requirements for Internet Engineering Task Force Standard Protocols&quot;">RFC3365</a>] and privacy [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>] [<a href="./rfc7258" title="&quot;Pervasive Monitoring Is an Attack&quot;">RFC7258</a>] in the
   Internet's architectural design contributes to the strengthening of
   the Internet as an enabling environment for human rights.  One could
   even argue that the Internet is not only an enabler of human rights
   but that human rights lie at the base of, and are ingrained in, the
   architecture of the networks that make up the Internet.  Internet



<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   connectivity increases the capacity for individuals to exercise their
   rights; the core of the Internet -- its architectural design -- is
   therefore closely intertwined with the human rights framework
   [<a href="#ref-CathFloridi">CathFloridi</a>].  The quintessential link between the Internet's
   infrastructure and human rights has been argued by many.  [<a href="#ref-Bless1" title="&quot;Values and Networks - Steps Toward Exploring their Relationships&quot;">Bless1</a>],
   for instance, argues that "to a certain extent, the Internet and its
   protocols have already facilitated the realization of human rights,
   e.g., the freedom of assembly and expression.  In contrast, measures
   of censorship and pervasive surveillance violate fundamental human
   rights."  [<a href="#ref-DeNardis15">DeNardis15</a>] argues that "Since the first hints of Internet
   commercialization and internationalization, the IETF has supported
   strong security in protocol design and has sometimes served as a
   force resisting protocol-enabled surveillance features."  By doing
   so, the IETF enabled the manifestation of the right to privacy,
   through the Internet's infrastructure.  Additionally, access to
   freely available information gives people access to knowledge that
   enables them to help satisfy other human rights; as such, the
   Internet increasingly becomes a precondition for human rights rather
   than a supplement.

   Human rights can be in conflict with each other, such as the right to
   freedom of expression and the right to privacy.  In such cases, the
   different affected rights need to be balanced.  To do this, it is
   crucial that the impacts on rights are clearly documented in order to
   mitigate potential harm.  This research aims to ultimately contribute
   to making that process tangible and practical for protocol
   developers.  Technology can never be fully equated with a human
   right.  Whereas a specific technology might be a strong enabler of a
   specific human right, it might have an adverse impact on another
   human right.  In this case, decisions on design and deployment need
   to take this into account.

   The open nature of the initial technical design and its open
   standards, as well as developments like open source, fostered freedom
   of communication.  What emerged was a network of networks that could
   enable everyone to connect and to exchange data, information, and
   code.  For many, enabling such connections became a core value.
   However, as the scale and the commercialization of the Internet grew,
   topics like access, rights, and connectivity have been forced to
   compete with other values.  Therefore, important characteristics of
   the Internet that enable human rights might be degraded if they're
   not properly defined, described, and protected as such.  Conversely,
   not protecting characteristics that enable human rights could also
   result in (partial) loss of functionality and connectivity, along
   with other inherent parts of the Internet's architecture of networks.
   New protocols, particularly those that upgrade the core
   infrastructure of the network, should be designed to continue to
   enable fundamental human rights.



<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   The IETF has produced guidelines and procedures to ensure and
   galvanize the privacy of individuals and security of the network in
   protocol development.  This document aims to explore the possibility
   of developing similar procedures for guidelines for human rights
   considerations to ensure that protocols developed in the IETF do not
   have an adverse impact on the realization of human rights on the
   Internet.  By carefully considering the answers to the questions
   posed in <a href="#section-6">Section 6</a> of this document, document authors should be
   (1) able to produce a comprehensive analysis that can serve as the
   basis for discussion on whether the protocol adequately protects
   against specific human rights threats and (2) potentially stimulated
   to think about alternative design choices.

   This document was developed within the framework of the Human Rights
   Protocol Considerations (HRPC) Research Group, based on discussions
   on the HRPC mailing list (<a href="#section-9">Section 9</a>); this document was also
   extensively discussed during HRPC sessions.  This document has
   received eleven in-depth reviews on the mailing list, and it received
   many comments from inside and outside the IRTF and IETF communities.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Vocabulary Used</span>

   In the discussion of human rights and Internet architecture, concepts
   developed in computer science, networking, law, policy-making, and
   advocacy are coming together [<a href="#ref-Dutton" title="&quot;Freedom of Connection, Freedom of Expression: The Changing Legal and Regulatory Ecology Shaping the Internet&quot;">Dutton</a>] [<a href="#ref-Kaye" title="&quot;Freedom of expression and the private sector in the digital age&quot;">Kaye</a>] [<a href="#ref-Franklin" title="&quot;The Real World of Technology&quot;">Franklin</a>] [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>].
   The same concepts might have a very different meaning and
   implications in other areas of expertise.  In order to foster a
   constructive interdisciplinary debate and minimize differences in
   interpretation, the following glossary is provided.  It builds as
   much as possible on existing definitions; when definitions were not
   available in IETF documents, definitions were taken from other
   Standards Development Organizations (SDOs) or academic literature.

   Accessibility:  "Full Internet Connectivity", as described in
      [<a href="./rfc4084" title="&quot;Terminology for Describing Internet Connectivity&quot;">RFC4084</a>], to provide unfettered access to the Internet.

      The design of protocols, services, or implementations that provide
      an enabling environment for people with disabilities.

      The ability to receive information available on the Internet.

   Anonymity:  The condition of an identity being unknown or concealed
      [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].

   Anonymous:  A state of an individual in which an observer or attacker
      cannot identify the individual within a set of other individuals
      (the anonymity set) [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>].




<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Authenticity:  The property of being genuine and able to be verified
      and be trusted [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].

   Blocking:  The practice of preventing access to resources in the
      aggregate [<a href="./rfc7754" title="&quot;Technical Considerations for Internet Service Blocking and Filtering&quot;">RFC7754</a>].  Both blocking and filtering can be
      implemented at the level of "services" (web hosting or video
      streaming, for example) or at the level of particular "content"
      [<a href="./rfc7754" title="&quot;Technical Considerations for Internet Service Blocking and Filtering&quot;">RFC7754</a>].

   Censorship:  Technical mechanisms, including both blocking and
      filtering, that certain political or private actors around the
      world use to block or degrade Internet traffic.  For further
      details on the various elements of Internet censorship, see
      [<a href="#ref-Hall" title="&quot;A Survey of Worldwide Censorship Techniques&quot;">Hall</a>].

   Censorship resistance:  Methods and measures to mitigate Internet
      censorship.

   Confidentiality:  The property that data is not disclosed to system
      entities unless they have been authorized to know the data
      [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].

   Connectivity:  The extent to which a device or network is able to
      reach other devices or networks to exchange data.  The Internet is
      the tool for providing global connectivity [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>].  Different
      types of connectivity are further specified in [<a href="./rfc4084" title="&quot;Terminology for Describing Internet Connectivity&quot;">RFC4084</a>].

      The end-to-end principle, interoperability, distributed
      architecture, resilience, reliability, and robustness in
      combination constitute the enabling factors that result in
      connectivity to, and on, the Internet.

   Content agnosticism:  Treating network traffic identically regardless
      of content.

   Decentralized:  Implementation or deployment of standards, protocols,
      or systems without one single point of control.

   End-to-end principle:  The principle that application-specific
      functions should not be embedded into the network and thus stay at
      the endpoints.  In many cases, especially when dealing with
      failures, the right decisions can only be made with the
      corresponding application-specific knowledge, which is available
      at endpoints not in the network.

      The end-to-end principle is one of the key architectural
      guidelines of the Internet.  The argument in favor of the
      end-to-end approach to system design is laid out in the



<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      fundamental papers by Saltzer, Reed, and Clark [<a href="#ref-Saltzer" title="&quot;End-to-End Arguments in System Design&quot;">Saltzer</a>] [<a href="#ref-Clark" title="&quot;The Design Philosophy of the DARPA Internet Protocols&quot;">Clark</a>].
      In these papers, the authors argue in favor of radical
      simplification: system designers should only build the essential
      and shared functions into the network, as most functions can only
      be implemented at network endpoints.  Building features into the
      network for the benefit of certain applications will come at the
      expense of others.  As such, in general system designers should
      attempt to steer clear of building anything into the network that
      is not a bare necessity for its functioning.  Following the
      end-to-end principle is crucial for innovation, as it makes
      innovation at the edges possible without having to make changes to
      the network, and it protects the robustness of the network.
      [<a href="./rfc2775" title="&quot;Internet Transparency&quot;">RFC2775</a>] further elaborates on various aspects of end-to-end
      connectivity.

   Federation:  The possibility of connecting autonomous and possibly
      centralized systems into a single system without a central
      authority.

   Filtering:  The practice of preventing access to specific resources
      within an aggregate [<a href="./rfc7754" title="&quot;Technical Considerations for Internet Service Blocking and Filtering&quot;">RFC7754</a>].

   Heterogeneity:  "The Internet is characterized by heterogeneity on
      many levels: devices and nodes, router scheduling algorithms and
      queue management mechanisms, routing protocols, levels of
      multiplexing, protocol versions and implementations, underlying
      link layers (e.g., point-to-point, multi-access links, wireless,
      FDDI, etc.), in the traffic mix and in the levels of congestion at
      different times and places.  Moreover, as the Internet is composed
      of autonomous organizations and internet service providers, each
      with their own separate policy concerns, there is a large
      heterogeneity of administrative domains and pricing structures."
      [<a href="#ref-FIArch" title="&quot;Future Internet Design Principles&quot;">FIArch</a>]

      As a result, per [<a href="#ref-FIArch" title="&quot;Future Internet Design Principles&quot;">FIArch</a>], the heterogeneity principle proposed in
      [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>] needs to be supported by design.

   Human rights:  Principles and norms that are indivisible,
      interrelated, unalienable, universal, and mutually reinforcing.
      Human rights have been codified in national and international
      bodies of law.  The Universal Declaration of Human Rights [<a href="#ref-UDHR" title="&quot;The Universal Declaration of Human Rights&quot;">UDHR</a>]
      is the most well-known document in the history of human rights.
      The aspirations from [<a href="#ref-UDHR" title="&quot;The Universal Declaration of Human Rights&quot;">UDHR</a>] were later codified into treaties such
      as the International Covenant on Civil and Political Rights
      [<a href="#ref-ICCPR" title="&quot;International Covenant on Civil and Political Rights&quot;">ICCPR</a>] and the International Covenant on Economic, Social and
      Cultural Rights [<a href="#ref-ICESCR" title="&quot;International Covenant on Economic, Social and Cultural Rights&quot;">ICESCR</a>], after which signatory countries were





<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      obliged to reflect them in their national bodies of law.  There is
      also a broad recognition that not only states have obligations
      vis-a-vis human rights, but non-state actors do as well.

   Integrity:  The property that data has not been changed, destroyed,
      or lost in an unauthorized or accidental manner [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].

   Internationalization (i18n):  The practice of making protocols,
      standards, and implementations usable in different languages and
      scripts (see <a href="#section-6.2.12">Section 6.2.12</a> ("Localization")).

      "In the IETF, 'internationalization' means to add or improve the
      handling of non-ASCII text in a protocol" [<a href="./rfc6365" title="&quot;Terminology Used in Internationalization in the IETF&quot;">RFC6365</a>].

      A different perspective, more appropriate to protocols that are
      designed for global use from the beginning, is the definition used
      by the World Wide Web Consortium (W3C) [<a href="#ref-W3Ci18nDef">W3Ci18nDef</a>]:
      "Internationalization is the design and development of a product,
      application or document content that enables easy localization for
      target audiences that vary in culture, region, or language."

      Many protocols that handle text only handle one charset
      (US-ASCII), or they leave the question of encoding up to local
      guesswork (which leads, of course, to interoperability problems)
      [<a href="./rfc3536" title="&quot;Terminology Used in Internationalization in the IETF&quot;">RFC3536</a>].  If multiple charsets are permitted, they must be
      explicitly identified [<a href="./rfc2277" title="&quot;IETF Policy on Character Sets and Languages&quot;">RFC2277</a>].  Adding non-ASCII text to a
      protocol allows the protocol to handle more scripts, hopefully all
      scripts in use in the world.  In today's world, that is normally
      best accomplished by allowing Unicode encoded in UTF-8 only,
      thereby shifting conversion issues away from ad hoc choices.

   Interoperable:  A property of a documented standard or protocol that
      allows different independent implementations to work with each
      other without any restriction on functionality.

   Localization (l10n):  The practice of translating an implementation
      to make it functional in a specific language or for users in a
      specific locale (see <a href="#section-6.2.5">Section 6.2.5</a> ("Internationalization")).

      (cf. [<a href="./rfc6365" title="&quot;Terminology Used in Internationalization in the IETF&quot;">RFC6365</a>]): The process of adapting an internationalized
      application platform or application to a specific cultural
      environment.  In localization, the same semantics are preserved
      while the syntax may be changed [<a href="#ref-FRAMEWORK">FRAMEWORK</a>].

      Localization is the act of tailoring an application for a
      different language, script, or culture.  Some internationalized
      applications can handle a wide variety of languages.  Typical
      users only understand a small number of languages, so the program



<span class="grey">Ten Oever &amp; Cath              Informational                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      must be tailored to interact with users in just the languages they
      know.  The major work of localization is translating the user
      interface and documentation.  Localization involves not only
      changing the language interaction but also other relevant changes,
      such as display of numbers, dates, currency, and so on.  The
      better internationalized an application is, the easier it is to
      localize it for a particular language and character-encoding
      scheme.

   Open standards:  Conform with [<a href="./rfc2026" title="&quot;The Internet Standards Process -- Revision 3&quot;">RFC2026</a>], which states the following:
      "Various national and international standards bodies, such as
      ANSI, ISO, IEEE, and ITU-T, develop a variety of protocol and
      service specifications that are similar to Technical
      Specifications defined here.  National and international groups
      also publish 'implementors' agreements' that are analogous to
      Applicability Statements, capturing a body of implementation-
      specific detail concerned with the practical application of their
      standards.  All of these are considered to be 'open external
      standards' for the purposes of the Internet Standards Process."

   Openness:  Absence of centralized points of control -- "a feature
      that is assumed to make it easy for new users to join and new uses
      to unfold" [<a href="#ref-Brown" title="&quot;A Prehistory of Internet Governance&quot;">Brown</a>].

   Permissionless innovation:  The freedom and ability to freely create
      and deploy new protocols on top of the communications constructs
      that currently exist.

   Privacy:  The right of an entity (normally a person), acting on its
      own behalf, to determine the degree to which it will interact with
      its environment, including the degree to which the entity is
      willing to share its personal information with others [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].

      The right of individuals to control or influence what information
      related to them may be collected and stored, and by whom and to
      whom that information may be disclosed.

      Privacy is a broad concept relating to the protection of
      individual or group autonomy and the relationship between an
      individual or group and society, including government, companies,
      and private individuals.  It is often summarized as "the right to
      be left alone", but it encompasses a wide range of rights,
      including protections from intrusions into family and home life,
      control of sexual and reproductive rights, and communications
      secrecy.  It is commonly recognized as a core right that underpins
      human dignity and other values such as freedom of association and
      freedom of speech.




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      The right to privacy is also recognized in nearly every national
      constitution and in most international human rights treaties.  It
      has been adjudicated upon by both international and regional
      bodies.  The right to privacy is also legally protected at the
      national level through provisions in civil and/or criminal codes.

   Reliability:  Ensures that a protocol will execute its function
      consistently as described and function without unexpected results.
      A system that is reliable degenerates gracefully and will have a
      documented way to announce degradation.  It also has mechanisms to
      recover from failure gracefully and, if applicable, allow for
      partial healing [<a href="#ref-dict" title="&quot;Reliability (dictionary entry)&quot;">dict</a>].

   Resilience:  The maintaining of dependability and performance in the
      face of unanticipated changes and circumstances [<a href="#ref-Meyer" title="&quot;Defining and Evaluating Resilience: A Performability Perspective&quot;">Meyer</a>].

   Robustness:  The resistance of protocols and their implementations to
      errors, and resistance to involuntary, legal, or malicious
      attempts to disrupt their modes of operation [<a href="./rfc760" title="&quot;DoD standard Internet Protocol&quot;">RFC760</a>] [<a href="./rfc791" title="&quot;Internet Protocol&quot;">RFC791</a>]
      [<a href="./rfc793" title="&quot;Transmission Control Protocol&quot;">RFC793</a>] [<a href="./rfc1122" title="&quot;Requirements for Internet Hosts - Communication Layers&quot;">RFC1122</a>].  Or, framed more positively, a system can
      provide functionality consistently and without errors despite
      involuntary, legal, or malicious attempts to disrupt its mode of
      operation.

   Scalability:  The ability to handle increased or decreased system
      parameters (number of end systems, users, data flows, routing
      entries, etc.) predictably within defined expectations.  There
      should be a clear definition of its scope and applicability.  The
      limits of a system's scalability should be defined.  Growth or
      shrinkage of these parameters is typically considered by orders of
      magnitude.

   Strong encryption / cryptography:  Used to describe a cryptographic
      algorithm that would require a large amount of computational power
      to defeat it [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].  In the modern usage of the definition of
      "strong encryption", this refers to an amount of computing power
      currently not available, not even to major state-level actors.

   Transparency:  In this context, linked to the comprehensibility of a
      protocol in relation to the choices it makes for users, protocol
      developers, and implementers, and to its outcome.

      Outcome transparency is linked to the comprehensibility of the
      effects of a protocol in relation to the choices it makes for
      users, protocol developers, and implementers, including the
      comprehensibility of possible unintended consequences of protocol
      choices (e.g., lack of authenticity may lead to lack of integrity
      and negative externalities).



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Research Questions</span>

   The Human Rights Protocol Considerations (HRPC) Research Group in the
   Internet Research Task Force (IRTF) embarked on its mission to answer
   the following two questions, which are also the main two questions
   that this document seeks to answer:

   1.  How can Internet protocols and standards impact human rights, by
       either enabling them or creating a restrictive environment?

   2.  Can guidelines be developed to improve informed and transparent
       decision-making about the potential impact of protocols on human
       rights?

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Literature and Discussion Review</span>

   Protocols and standards are regularly seen as merely performing
   technical functions.  However, these protocols and standards do not
   exist outside of their technical context, nor do they exist outside
   of their political, historical, economic, legal, or cultural context.
   This is best exemplified by the way in which some Internet processes
   and protocols have become part and parcel of political processes and
   public policies: one only has to look at the IANA transition,
   [<a href="./rfc7258" title="&quot;Pervasive Monitoring Is an Attack&quot;">RFC7258</a>] ("Pervasive Monitoring Is an Attack"), or global innovation
   policy, for concrete examples [<a href="#ref-DeNardis15">DeNardis15</a>].  According to [<a href="#ref-Abbate" title="&quot;Inventing the Internet&quot;">Abbate</a>],
   "protocols are politics by other means."  This statement would
   probably not garner IETF consensus, but it nonetheless reveals that
   protocols are based on decision-making, most often by humans.  In
   this process, the values and ideas about the role that a particular
   technology should perform in society are embedded into the design.
   Often, these design decisions are partly "purely technical" and
   partly inspired by a certain world view of how technology should
   function that is inspired by personal, corporate, and political
   views.  Within the community of IETF participants, there is a strong
   desire to solve technical problems and to minimize engagement with
   political processes and non-protocol-related political issues.

   Since the late 1990s, a burgeoning group of academics and
   practitioners researched questions surrounding the societal impact of
   protocols, as well as the politics of protocols.  These studies vary
   in focus and scope: some focus on specific standards [<a href="#ref-Davidson-etal">Davidson-etal</a>]
   [<a href="#ref-Musiani" title="&quot;Giants, Dwarfs and Decentralized Alternatives to Internet-based Services: An Issue of Internet Governance&quot;">Musiani</a>]; others look into the political, legal, commercial, or
   social impact of protocols [<a href="#ref-BrownMarsden">BrownMarsden</a>] [<a href="#ref-Lessig" title="&quot;Code and Other Laws of Cyberspace, Version 2.0 ('Codev2')&quot;">Lessig</a>] [<a href="#ref-Mueller" title="&quot;Networks and States: The Global Politics of Internet Governance&quot;">Mueller</a>]; and yet
   others look at how the engineers' personal set of values get
   translated into technology [<a href="#ref-Abbate" title="&quot;Inventing the Internet&quot;">Abbate</a>] [<a href="#ref-CathFloridi">CathFloridi</a>] [<a href="#ref-DeNardis15">DeNardis15</a>]
   [<a href="#ref-WynsbergheMoura">WynsbergheMoura</a>].





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Commercial and political influences on the management of the
   Internet's infrastructure are well documented in the academic
   literature and will thus not be discussed here; see [<a href="#ref-Benkler" title="&quot;The Wealth of Networks - How Social Production Transforms Markets and Freedom&quot;">Benkler</a>],
   [<a href="#ref-Brown-etal">Brown-etal</a>], [<a href="#ref-DeNardis15">DeNardis15</a>], [<a href="#ref-Lessig" title="&quot;Code and Other Laws of Cyberspace, Version 2.0 ('Codev2')&quot;">Lessig</a>], [<a href="#ref-Mueller" title="&quot;Networks and States: The Global Politics of Internet Governance&quot;">Mueller</a>], and [<a href="#ref-Zittrain" title="&quot;The Future of the Internet - And How to Stop It&quot;">Zittrain</a>].  It
   is sufficient to say that the IETF community consistently tries to
   push back against the standardization of surveillance and certain
   other issues that negatively influence an end user's experience of,
   and trust in, the Internet [<a href="#ref-DeNardis14">DeNardis14</a>].  The role that human rights
   play in engineering, infrastructure maintenance, and protocol design
   is much less clear.

   It is very important to understand how protocols and standards impact
   human rights, in particular because SDOs are increasingly becoming
   venues where social values (like human rights) are discussed,
   although often from a technological point of view.  These SDOs are
   becoming a new focal point for discussions about "values by design"
   and the role of technical engineers in protecting or enabling human
   rights [<a href="#ref-Brown-etal">Brown-etal</a>] [<a href="#ref-Clark-etal">Clark-etal</a>] [<a href="#ref-DeNardis14">DeNardis14</a>] [<a href="#ref-CathFloridi">CathFloridi</a>] [<a href="#ref-Lessig" title="&quot;Code and Other Laws of Cyberspace, Version 2.0 ('Codev2')&quot;">Lessig</a>]
   [<a href="#ref-Rachovitsa">Rachovitsa</a>].

   In the academic literature, five clear positions can be discerned in
   relation to the role of human rights in protocol design and how to
   account for these human rights in protocol development: Clark
   et al. [<a href="#ref-Clark-etal">Clark-etal</a>] argue that there is a need to design "for
   variation in outcome -- so that the outcome can be different in
   different places, and the tussle takes place within the design (...)"
   [as] "Rigid designs will be broken; designs that permit variation
   will flex under pressure and survive."  They hold that human rights
   should not be hard-coded into protocols for three reasons: First, the
   rights in the UDHR are not absolute.  Second, technology is not the
   only tool in the tussle over human rights.  And last but not least,
   it is dangerous to make promises that can't be kept.  The open nature
   of the Internet will never, they argue, be enough to fully protect
   individuals' human rights.

   Conversely, Brown et al. [<a href="#ref-Brown-etal">Brown-etal</a>] state that "some key, universal
   values -- of which the UDHR is the most legitimate expression --
   should be baked into the architecture at design time."  They argue
   that design choices have offline consequences and are able to shape
   the power positions of groups or individuals in society.  As such,
   the individuals making these technical decisions have a moral
   obligation to take into account the impact of their decisions on
   society and, by extension, human rights.  Brown et al. recognize that
   values and the implementation of human rights vary across the globe.
   Yet they argue that all members of the United Nations have found
   "common agreement on the values proclaimed in the Universal
   Declaration of Human Rights.  In looking for the most legitimate set




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   of global values to embed in the future Internet architectures, the
   UDHR has the democratic assent of a significant fraction of the
   planet's population, through their elected representatives."

   The main disagreement between these two academic positions lies
   mostly in the question of whether (1) a particular value system
   should be embedded into the Internet's architectures or (2) the
   architectures need to account for a varying set of values.

   A third position, which is similar to that of Brown et al., is taken
   by [<a href="#ref-Broeders" title="&quot;The public core of the Internet. An international agenda for Internet governance&quot;">Broeders</a>], in which Broeders argues that "we must find ways to
   continue guaranteeing the overall integrity and functionality of the
   public core of the Internet."  He argues that the best way to do this
   is by declaring the backbone of the Internet -- which includes the
   TCP/IP protocol suite, numerous standards, the Domain Name System
   (DNS), and routing protocols -- a common public good.  This is a
   different approach than those of [<a href="#ref-Clark-etal">Clark-etal</a>] and [<a href="#ref-Brown-etal">Brown-etal</a>]
   because Broeders does not suggest that social values should (or
   should not) be explicitly coded into the Internet, but rather that
   the existing infrastructure should be seen as an entity of public
   value.

   Bless and Orwat [<a href="#ref-Bless2" title="&quot;Values and Networks&quot;">Bless2</a>] represent a fourth position.  They argue
   that it is too early to make any definitive claims but that there is
   a need for more careful analysis of the impact of protocol design
   choices on human rights.  They also argue that it is important to
   search for solutions that "create awareness in the technical
   community about impact of design choices on social values" and "work
   towards a methodology for co-design of technical and institutional
   systems."

   Berners-Lee and Halpin [<a href="#ref-BernersLeeHalpin">BernersLeeHalpin</a>] represent a fifth position.
   They argue that the Internet could lead to even newer capacities, and
   these capacities may over time be viewed as new kinds of rights.  For
   example, Internet access may be viewed as a human right in and of
   itself if it is taken to be a precondition for other rights, even if
   it could not have been predicted at the time that the UDHR was
   written (after the end of World War II).

   It is important to contextualize the technical discussion with the
   academic discussions on this issue.  The academic discussions are
   also important to document, as they inform the position of the
   authors of this document.  The research group's position is that
   hard-coding human rights into protocols is complicated and changes
   with the context.  At this point, it is difficult to say whether or
   not hard-coding human rights into protocols is wise or feasible.
   Additionally, there are many human rights, but not all are relevant
   for information and communications technologies (ICTs).  A partial



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   catalog (with references to sources) of human rights related to ICTs
   can be found in [<a href="#ref-Hill2014" title="&quot;Partial Catalog of Human Rights Related to ICT Activities&quot;">Hill2014</a>].  It is, however, important to make
   conscious and explicit design decisions that take into account the
   human rights protocol considerations guidelines developed below.
   This will contribute to the understanding of the impact that
   protocols can have on human rights, for both developers and users.
   In addition, it contributes to (1) the careful consideration of the
   impact that a specific protocol might have on human rights and
   (2) the dissemination of the practice of documenting protocol design
   decisions related to human rights.

   Pursuant to the principle of constant change, because the function
   and scope of the Internet evolve, so does the role of the IETF in
   developing standards.  Internet Standards are adopted based on a
   series of criteria, including high technical quality, support by
   community consensus, and their overall benefit to the Internet.  The
   latter calls for an assessment of the interests of all affected
   parties and the specifications' impact on the Internet's users.  In
   this respect, the effective exercise of the human rights of the
   Internet users is a relevant consideration that needs to be
   appreciated in the standardization process insofar as it is directly
   linked to the reliability and core values of the Internet [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>]
   [<a href="./rfc2775" title="&quot;Internet Transparency&quot;">RFC2775</a>] [<a href="./rfc3439" title="&quot;Some Internet Architectural Guidelines and Philosophy&quot;">RFC3439</a>] [<a href="./rfc3724" title="&quot;The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture&quot;">RFC3724</a>].

   This document details the steps taken in the research into human
   rights protocol considerations by the HRPC Research Group to clarify
   the relationship between technical concepts used in the IETF and
   human rights.  This document sets out some preliminary steps and
   considerations for engineers to take into account when developing
   standards and protocols.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Methodology</span>

   Mapping the relationship between human rights, protocols, and
   architectures is a new research challenge that requires a good amount
   of interdisciplinary and cross-organizational cooperation to develop
   a consistent methodology.

   The methodological choices made in this document are based on the
   political-science-based method of discourse analysis and ethnographic
   research methods [<a href="#ref-Cath" title="&quot;A Case Study of Coding Rights: Should Freedom of Speech Be Instantiated in the Protocols and Standards Designed by the Internet Engineering Task Force?&quot;">Cath</a>].  This work departs from the assumption that
   language reflects the understanding of concepts.  Or, as [<a href="#ref-Jabri" title="&quot;Discourses on violence: conflict analysis reconsidered&quot;">Jabri</a>]
   holds, policy documents are "social relations represented in texts
   where the language contained within these texts is used to construct
   meaning and representation."  This process happens in society
   [<a href="#ref-Denzin" title="&quot;The SAGE Handbook of Qualitative Research&quot;">Denzin</a>] and manifests itself in institutions and organizations
   [<a href="#ref-King" title="&quot;Power, Social Violence and Civil Wars&quot;">King</a>], exposed using the ethnographic methods of semi-structured
   interviews and participant observation.  Or, in non-academic



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   language, the way the language in IETF/IRTF documents describes and
   approaches the issues they are trying to address is an indication of
   the underlying social assumptions and relationships of the engineers
   to their engineering.  By reading and analyzing these documents, as
   well as interviewing engineers and participating in the IETF/IRTF
   working groups, it is possible to distill the relationship between
   human rights, protocols, and the Internet's infrastructure as it
   pertains to the work of the IETF.

   The discourse analysis was operationalized using qualitative and
   quantitative means.  The first step taken by the authors and
   contributors was reading RFCs and other official IETF documents.  The
   second step was the use of a Python-based analyzer, using the
   "Bigbang" tool, adapted by Nick Doty [<a href="#ref-Doty" title="&quot;Automated text analysis of Requests for Comment (RFCs)&quot;">Doty</a>], to scan for the concepts
   that were identified as important architectural principles (distilled
   on the initial reading and supplemented by the interviews and
   participant observation).  Such a quantitative method is very precise
   and speeds up the research process [<a href="#ref-Ritchie" title="&quot;Qualitative Research Practice: A Guide for Social Science Students and Researchers&quot;">Ritchie</a>].  But this tool is
   unable to understand "latent meaning" [<a href="#ref-Denzin" title="&quot;The SAGE Handbook of Qualitative Research&quot;">Denzin</a>].  In order to mitigate
   these issues of automated word-frequency-based approaches and to get
   a sense of the "thick meaning" [<a href="#ref-Geertz" title="&quot;Kinship in Bali&quot;">Geertz</a>] of the data, a second
   qualitative analysis of the data set was performed.  These various
   rounds of discourse analysis were used to inform the interviews and
   further data analysis.  As such, the initial rounds of quantitative
   discourse analysis were used to inform the second rounds of
   qualitative analysis.  The results from the qualitative interviews
   were again used to feed new concepts into the quantitative discourse
   analysis.  As such, the two methods continued to support and enrich
   each other.

   The ethnographic methods of the data collection and processing
   allowed the research group to acquire the data necessary to "provide
   a holistic understanding of research participants' views and actions"
   [<a href="#ref-Denzin" title="&quot;The SAGE Handbook of Qualitative Research&quot;">Denzin</a>] that highlighted ongoing issues and case studies where
   protocols impact human rights.  The interview participants were
   selected through purposive sampling [<a href="#ref-Babbie" title="&quot;The Basics of Social Research&quot;">Babbie</a>], as the research group
   was interested in getting a wide variety of opinions on the role of
   human rights in guiding protocol development.  This sampling method
   also ensured that individuals with extensive experience working at
   the IETF in various roles were targeted.  The interviewees included
   individuals in leadership positions (Working Group (WG) chairs, Area
   Directors (ADs)), "regular participants", and individuals working for
   specific entities (corporate, civil society, political, academic) and
   represented various backgrounds, nationalities, and genders.







<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  Data Sources</span>

   In order to map the potential relationship between human rights and
   protocols, the HRPC Research Group gathered data from three specific
   sources:

<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>.  Discourse Analysis of RFCs</span>

   To start addressing the issue, a mapping exercise analyzing Internet
   infrastructure and protocol features vis-a-vis their possible impact
   on human rights was undertaken.  Therefore, research on (1) the
   language used in current and historic RFCs and (2) information
   gathered from mailing-list discussions was undertaken to expose core
   architectural principles, language, and deliberations on the human
   rights of those affected by the network.

<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>.  Interviews with Members of the IETF Community</span>

   Over 30 interviews with the current and past members of the Internet
   Architecture Board (IAB), current and past members of the Internet
   Engineering Steering Group (IESG), chairs of selected working groups,
   and RFC authors were done at the IETF 92 meeting in Dallas in
   March 2015 to get an insider's understanding of how they view the
   relationship (if any) between human rights and protocols, and how
   this relationship plays out in their work.  Several of the
   participants opted to remain anonymous.  If you are interested in
   this data set, please contact the authors of this document.

<span class="h4"><a class="selflink" id="section-5.1.3" href="#section-5.1.3">5.1.3</a>.  Participant Observation in Working Groups</span>

   By participating in various working groups, in person at IETF
   meetings, and on mailing lists, information about the IETF's
   day-to-day workings was gathered, from which general themes,
   technical concepts, and use cases about human rights and protocols
   were extracted.  This process started at the IETF 91 meeting in
   Honolulu and continues today.















<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  Data Analysis Strategies</span>

   The data above was processed using three consecutive strategies:
   mapping protocols related to human rights, extracting concepts from
   these protocols, and creation of a common glossary (detailed under
   <a href="#section-2">Section 2</a>).  Before going over these strategies, some elaboration on
   the process of identifying technical concepts as they relate to human
   rights is needed:

<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>.  Identifying Qualities of Technical Concepts That Relate to Human</span>
<span class="h4">        Rights</span>

<span class="h5"><a class="selflink" id="section-5.2.1.1" href="#section-5.2.1.1">5.2.1.1</a>.  Mapping Protocols and Standards to Human Rights</span>

   By combining data from the three data sources named above, an
   extensive list of protocols and standards that potentially enable the
   Internet as a tool for freedom of expression and association was
   created.  In order to determine the enabling (or inhibiting)
   features, we relied on direct references in the RFCs as related to
   such impacts, as well as input from the community.  Based on this
   analysis, a list of RFCs that describe standards and protocols that
   are potentially closely related to human rights was compiled.

<span class="h5"><a class="selflink" id="section-5.2.1.2" href="#section-5.2.1.2">5.2.1.2</a>.  Extracting Concepts from Selected RFCs</span>

   The first step was to identify the protocols and standards that are
   related to human rights and to create an environment that enables
   human rights.  For that, we needed to focus on specific technical
   concepts that underlie these protocols and standards.  Based on this
   list, a number of technical concepts that appeared frequently were
   extracted and used to create a second list of technical terms that,
   when combined and applied in different circumstances, create an
   enabling environment for exercising human rights on the Internet.

<span class="h5"><a class="selflink" id="section-5.2.1.3" href="#section-5.2.1.3">5.2.1.3</a>.  Building a Common Vocabulary of Technical Concepts That Impact</span>
<span class="h5">          Human Rights</span>

   While interviewing experts, investigating RFCs, and compiling
   technical definitions, several concepts of convergence and divergence
   were identified.  To ensure that the discussion was based on a common
   understanding of terms and vocabulary, a list of definitions was
   created.  The definitions are based on the wording found in various
   IETF documents; if the definitions were not available therein,
   definitions were taken from other SDOs or academic literature, as
   indicated in <a href="#section-2">Section 2</a>.






<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h5"><a class="selflink" id="section-5.2.1.4" href="#section-5.2.1.4">5.2.1.4</a>.  Translating Human Rights Concepts into Technical Definitions</span>

   The previous steps allowed for the clarification of relationships
   between human rights and technical concepts.  The steps taken show
   how the research process "zoomed in", from compiling a broad list of
   protocols and standards that relate to human rights to extracting the
   precise technical concepts that make up these protocols and
   standards, in order to understand the relationship between the two.
   This subsection presents the next step: translating human rights to
   technical concepts by matching the individual components of the
   rights to the accompanying technical concepts, allowing for the
   creation of a list of technical concepts that, when partially
   combined, can create an enabling environment for human rights.

<span class="h5"><a class="selflink" id="section-5.2.1.5" href="#section-5.2.1.5">5.2.1.5</a>.  List of Technical Terms That, When Partially Combined, Can</span>
<span class="h5">          Create an Enabling Environment for Human Rights</span>

   Based on the prior steps, the following list of technical terms was
   drafted.  When partially combined, this list can create an enabling
   environment for human rights, such as freedom of expression and
   freedom of association.

     Architectural principles                    Enabling features
       and system properties                        for user rights

                      /------------------------------------------------\
                      |                                                |
    +=================|=============================+                  |
    =                 |                             =                  |
    =                 |           End-to-end        =                  |
    =                 |          Reliability        =                  |
    =                 |           Resilience        =  Access as       |
    =                 |        Interoperability     =   human right    |
    =    Good enough  |          Transparency       =                  |
    =     principle   |       Data minimization     =                  |
    =                 |  Permissionless innovation  =                  |
    =    Simplicity   |     Graceful degradation    =                  |
    =                 |          Connectivity       =                  |
    =                 |      Heterogeneity support  =                  |
    =                 |                             =                  |
    =                 |                             =                  |
    =                 \------------------------------------------------/
    =                                               =
    +===============================================+

   Figure 1: Relationship between Architectural Principles and Enabling
                         Features for User Rights




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>.  Relating Human Rights to Technical Concepts</span>

   The technical concepts listed in the steps above have been grouped
   according to their impact on specific rights, as mentioned in the
   interviews done at IETF 92 as well as the study of literature (see
   <a href="#section-4">Section 4</a> ("Literature and Discussion Review") above).

   This analysis aims to assist protocol developers in better
   understanding the roles that specific technical concepts have with
   regard to their contribution to an enabling environment for people to
   exercise their human rights.

   This analysis does not claim to be a complete or exhaustive mapping
   of all possible ways in which protocols could potentially impact
   human rights, but it presents a mapping of initial concepts based on
   interviews and on discussion and review of the literature.

   +-----------------------+-----------------------------------------+
   | Technical Concepts    | Rights Potentially Impacted             |
   +-----------------------+-----------------------------------------+
   | Connectivity          |                                         |
   | Privacy               |                                         |
   | Security              |                                         |
   | Content agnosticism   | Right to freedom of expression          |
   | Internationalization  |                                         |
   | Censorship resistance |                                         |
   | Open standards        |                                         |
   | Heterogeneity support |                                         |
   +-----------------------+-----------------------------------------+
   | Anonymity             |                                         |
   | Privacy               |                                         |
   | Pseudonymity          | Right to non-discrimination             |
   | Accessibility         |                                         |
   +-----------------------+-----------------------------------------+
   | Content agnosticism   |                                         |
   | Security              | Right to equal protection               |
   +-----------------------+-----------------------------------------+
   | Accessibility         |                                         |
   | Internationalization  | Right to political participation        |
   | Censorship resistance |                                         |
   | Connectivity          |                                         |
   +-----------------------+-----------------------------------------+
   | Open standards        |                                         |
   | Localization          | Right to participate in cultural life,  |
   | Internationalization  |    arts, and science, and               |
   | Censorship resistance | Right to education                      |
   | Accessibility         |                                         |




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   +-----------------------+-----------------------------------------+
   | Connectivity          |                                         |
   | Decentralization      |                                         |
   | Censorship resistance | Right to freedom of assembly            |
   | Pseudonymity          |    and association                      |
   | Anonymity             |                                         |
   | Security              |                                         |
   +-----------------------+-----------------------------------------+
   | Reliability           |                                         |
   | Confidentiality       |                                         |
   | Integrity             | Right to security                       |
   | Authenticity          |                                         |
   | Anonymity             |                                         |
   |                       |                                         |
   +-----------------------+-----------------------------------------+

        Figure 2: Relationship between Specific Technical Concepts
       with Regard to Their Contribution to an Enabling Environment
                 for People to Exercise Their Human Rights

<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>.  Mapping Cases of Protocols, Implementations, and Networking</span>
<span class="h4">        Paradigms That Adversely Impact Human Rights or Are Enablers</span>
        Thereof

   Given the information above, the following list of cases of
   protocols, implementations, and networking paradigms that either
   adversely impact or enable human rights was formed.

   It is important to note that the assessment here is not a general
   judgment on these protocols, nor is it an exhaustive listing of all
   the potential negative or positive impacts on human rights that these
   protocols might have.  When these protocols were conceived, there
   were many criteria to take into account.  For instance, relying on a
   centralized service can be bad for freedom of speech (it creates one
   more control point, where censorship could be applied), but it may be
   a necessity if the endpoints are not connected and reachable
   permanently.  So, when we say "protocol X has feature Y, which may
   endanger freedom of speech," it does not mean that protocol X is bad,
   much less that its authors were evil.  The goal here is to show, with
   actual examples, that the design of protocols has practical
   consequences for some human rights and that these consequences have
   to be considered in the design phase.









<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h5"><a class="selflink" id="section-5.2.3.1" href="#section-5.2.3.1">5.2.3.1</a>.  IPv4</span>

   The Internet Protocol version 4 (IPv4), also known as "Layer 3" of
   the Internet and specified with a common encapsulation and protocol
   header, is defined in [<a href="./rfc791" title="&quot;Internet Protocol&quot;">RFC791</a>].  The evolution of Internet
   communications led to continued development in this area,
   "encapsulated" in the development of version 6 (IPv6) of the protocol
   [<a href="./rfc8200" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">RFC8200</a>].  In spite of this updated protocol, we find that 23 years
   after the specification of IPv6 the older IPv4 standard continues to
   account for a sizable majority of Internet traffic.  Most of the
   issues discussed here (Network Address Translators (NATs) are a major
   exception; see <a href="#section-5.2.3.1.2">Section 5.2.3.1.2</a> ("Address Translation and
   Mobility")) are valid for IPv4 as well as IPv6.

   The Internet was designed as a platform for free and open
   communication, most notably encoded in the end-to-end principle, and
   that philosophy is also present in the technical implementation of IP
   [<a href="./rfc3724" title="&quot;The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture&quot;">RFC3724</a>].  While the protocol was designed to exist in an
   environment where intelligence is at the end hosts, it has proven to
   provide sufficient information that a more intelligent network core
   can make policy decisions and enforce policy-based traffic shaping,
   thereby restricting the communications of end hosts.  These
   capabilities for network control and for limitations on freedom of
   expression by end hosts can be traced back to the design of IPv4,
   helping us to understand which technical protocol decisions have led
   to harm to this human right.  A feature that can harm freedom of
   expression as well as the right to privacy through misuse of IP is
   the exploitation of the public visibility of the host pairs for all
   communications and the corresponding ability to differentiate and
   block traffic as a result of that metadata.

<span class="h6"><a class="selflink" id="section-5.2.3.1.1" href="#section-5.2.3.1.1">5.2.3.1.1</a>.  Network Visibility of Source and Destination</span>

   The IPv4 protocol header contains fixed location fields for both the
   source IP address and destination IP address [<a href="./rfc791" title="&quot;Internet Protocol&quot;">RFC791</a>].  These
   addresses identify both the host sending and the host receiving each
   message; they also allow the core network to understand who is
   talking to whom and to practically limit communication selectively
   between pairs of hosts.  Blocking of communication based on the pair
   of source and destination is one of the most common limitations on
   the ability for people to communicate today [<a href="#ref-CAIDA" title="&quot;Analysis of Country-wide Internet Outages Caused by Censorship&quot;">CAIDA</a>] and can be seen
   as a restriction of the ability for people to assemble or to
   consensually express themselves.

   Inclusion of an Internet-wide identified source in the IP header
   is not the only possible design, especially since the protocol is
   most commonly implemented over Ethernet networks exposing only
   link-local identifiers [<a href="./rfc894" title="&quot;A Standard for the Transmission of IP Datagrams over Ethernet Networks&quot;">RFC894</a>].



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   A variety of alternative designs do exist, such as the Accountable
   and Private Internet Protocol [<a href="#ref-APIP" title="&quot;Balancing accountability and privacy in the network&quot;">APIP</a>] and High-speed Onion Routing at
   the Network Layer (HORNET) [<a href="#ref-HORNET" title="&quot;HORNET: High-speed Onion Routing at the Network Layer&quot;">HORNET</a>] as well as source routing.  The
   latter would allow the sender to choose a predefined (safe) route and
   spoofing of the source IP address, which are technically supported by
   IPv4, but neither are considered good practice on the Internet
   [<a href="#ref-Farrow" title="&quot;Source Address Spoofing&quot;">Farrow</a>].  While projects like [<a href="#ref-TorProject">TorProject</a>] provide an alternative
   implementation of anonymity in connections, they have been developed
   in spite of the IPv4 protocol design.

<span class="h6"><a class="selflink" id="section-5.2.3.1.2" href="#section-5.2.3.1.2">5.2.3.1.2</a>.  Address Translation and Mobility</span>

   A major structural shift in the Internet that undermined the protocol
   design of IPv4, and significantly reduced the freedom of end users to
   communicate and assemble, was the introduction of network address
   translation [<a href="./rfc3022" title="&quot;Traditional IP Network Address Translator (Traditional NAT)&quot;">RFC3022</a>].  Network address translation is a process
   whereby organizations and autonomous systems connect two networks by
   translating the IPv4 source and destination addresses between them.
   This process puts the router performing the translation in a
   privileged position, where it is predetermined which subset of
   communications will be translated.

   This process of translation has widespread adoption despite promoting
   a process that goes against the stated end-to-end process of the
   underlying protocol [<a href="#ref-NATusage" title="&quot;NAT usage in Residential Broadband networks&quot;">NATusage</a>].  In contrast, the proposed mechanism
   to provide support for mobility and forwarding to clients that may
   move -- encoded instead as an option in IP [<a href="./rfc5944" title="&quot;IP Mobility Support for IPv4, Revised&quot;">RFC5944</a>] -- has failed to
   gain traction.  In this situation, the compromise made in the design
   of the protocol resulted in a technology that is not coherent with
   the end-to-end principles and thus creates an extra possible hurdle
   for freedom of expression in its design, even though a viable
   alternative exists.  There is a particular problem surrounding NATs
   and Virtual Private Networks (VPNs) (as well as other connections
   used for privacy purposes), as NATs sometimes cause VPNs not to work.

<span class="h5"><a class="selflink" id="section-5.2.3.2" href="#section-5.2.3.2">5.2.3.2</a>.  DNS</span>

   The Domain Name System (DNS) [<a href="./rfc1035" title="&quot;Domain names - implementation and specification&quot;">RFC1035</a>] provides service discovery
   capabilities and provides a mechanism to associate human-readable
   names with services.  The DNS is organized around a set of
   independently operated "root servers" run by organizations that
   function in line with ICANN's policy by answering queries for which
   organizations have been delegated to manage registration under each
   Top-Level Domain (TLD).  The DNS is organized as a rooted tree, and
   this brings up political and social concerns over control.  TLDs are
   maintained and determined by ICANN.  These namespaces encompass
   several classes of services.  The initial namespaces, including
   ".com" and ".net", provide common spaces for expression of ideas,



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   though their policies are enacted through US-based companies.  Other
   namespaces are delegated to specific nationalities and may impose
   limits designed to focus speech in those forums, to both (1) promote
   speech from that nationality and (2) comply with local limits on
   expression and social norms.  Finally, the system has recently been
   expanded with additional generic and sponsored namespaces -- for
   instance, ".travel" and ".ninja" -- that are operated by a range of
   organizations that may independently determine their registration
   policies.  This new development has both positive and negative
   implications in terms of enabling human rights.  Some individuals
   argue that it undermines the right to freedom of expression because
   some of these new generic TLDs have restricted policies on
   registration and particular rules on hate speech content.  Others
   argue that precisely these properties are positive because they
   enable certain (mostly minority) communities to build safer spaces
   for association, thereby enabling their right to freedom of
   association.  An often-mentioned example is an application like
   .gay [<a href="#ref-CoE" title="&quot;Applications to ICANN for Community- based New Generic Top Level Domains (gTLDs): Opportunities and challenges from a human rights perspective&quot;">CoE</a>].

   As discussed in [<a href="./rfc7626" title="&quot;DNS Privacy Considerations&quot;">RFC7626</a>], DNS has significant privacy issues.  Most
   notable is the lack of encryption to limit the visibility of requests
   for domain resolution from intermediary parties, and a limited
   deployment of DNSSEC to provide authentication, allowing the client
   to know that they received a correct, "authoritative" answer to a
   query.  In response to the privacy issues, the IETF DNS Private
   Exchange (DPRIVE) Working Group is developing mechanisms to provide
   confidentiality to DNS transactions, to address concerns surrounding
   pervasive monitoring [<a href="./rfc7258" title="&quot;Pervasive Monitoring Is an Attack&quot;">RFC7258</a>].

   Authentication through DNSSEC creates a validation path for records.
   This authentication protects against forged or manipulated DNS data.
   As such, DNSSEC protects directory lookups and makes it harder to
   hijack a session.  This is important because interference with the
   operation of the DNS is currently becoming one of the central
   mechanisms used to block access to websites.  This interference
   limits both the freedom of expression of the publisher to offer their
   content and the freedom of assembly for clients to congregate in a
   shared virtual space.  Even though DNSSEC doesn't prevent censorship,
   it makes it clear that the returned information is not the
   information that was requested; this contributes to the right to
   security and increases trust in the network.  It is, however,
   important to note that DNSSEC is currently not widely supported or
   deployed by domain name registrars, making it difficult to
   authenticate and use correctly.







<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h6"><a class="selflink" id="section-5.2.3.2.1" href="#section-5.2.3.2.1">5.2.3.2.1</a>.  Removal of Records</span>

   There have been a number of cases where the records for a domain are
   removed from the name system due to political events.  Examples of
   this removal include the "seizure" of wikileaks [<a href="#ref-BBC-wikileaks">BBC-wikileaks</a>] and
   the names of illegally operating gambling operations by the United
   States Immigration and Customs Enforcement (ICE) unit.  In the first
   case, a US court ordered the registrar to take down the domain.  In
   the second, ICE compelled the US-based registry in charge of the .com
   TLD to hand ownership of those domains over to the US government.
   The same technique has been used in Libya to remove sites in
   violation of "our Country's Law and Morality (which) do not allow any
   kind of pornography or its promotion."  [<a href="#ref-techyum" title="&quot;Official - vb.ly Link Shortener Seized by Libyan Government&quot;">techyum</a>]

   At a protocol level, there is no technical auditing for name
   ownership, as in alternate systems like Namecoin [<a href="#ref-Namecoin" title="&quot;Namecoin&quot;">Namecoin</a>].  As a
   result, there is no ability for users to differentiate seizure from
   the legitimate transfer of name ownership, which is purely a policy
   decision made by registrars.  While DNSSEC addresses the network
   distortion events described below, it does not tackle this problem.

   (Although we mention alternative techniques, this is not a comparison
   of DNS with Namecoin: the latter has its own problems and
   limitations.  The idea here is to show that there are several
   possible choices, and they have consequences for human rights.)

<span class="h6"><a class="selflink" id="section-5.2.3.2.2" href="#section-5.2.3.2.2">5.2.3.2.2</a>.  Distortion of Records</span>

   The most common mechanism by which the DNS is abused to limit freedom
   of expression is through manipulation of protocol messages by the
   network.  One form occurs at an organizational level, where client
   computers are instructed to use a local DNS resolver controlled by
   the organization.  The DNS resolver will then selectively distort
   responses rather than request the authoritative lookup from the
   upstream system.  The second form occurs through the use of Deep
   Packet Inspection (DPI), where all DNS protocol messages are
   inspected by the network and objectionable content is distorted, as
   can be observed in Chinese networks.

   A notable instance of distortion occurred in Greece [<a href="#ref-Ververis" title="&quot;Understanding Internet Censorship Policy: The Case of Greece&quot;">Ververis</a>], where
   a study found evidence of both (1) DPI to distort DNS replies and
   (2) more excessive blocking of content than was legally required or
   requested (also known as "overblocking").  Internet Service Providers
   (ISPs), obeying a governmental order, prevented clients from
   resolving the names of domains, thereby prompting this particular
   blocking of systems there.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   At a protocol level, the effectiveness of these attacks is made
   possible by a lack of authentication in the DNS protocol.  DNSSEC
   provides the ability to determine the authenticity of responses when
   used, but it is not regularly checked by resolvers.  DNSSEC is not
   effective when the local resolver for a network is complicit in the
   distortion -- for instance, when the resolver assigned for use by an
   ISP is the source of injection.  Selective distortion of records is
   also made possible by the predictable structure of DNS messages,
   which makes it computationally easy for a network device to watch all
   passing messages even at high speeds, and the lack of encryption,
   which allows the network to distort only an objectionable subset of
   protocol messages.  Specific distortion mechanisms are discussed
   further in [<a href="#ref-Hall" title="&quot;A Survey of Worldwide Censorship Techniques&quot;">Hall</a>].

   Users can switch to another resolver -- for instance, a public
   resolver.  The distorter can then try to block or hijack the
   connection to this resolver.  This may start an arms race, with the
   user switching to secured connections to this alternative resolver
   [<a href="./rfc7858" title="&quot;Specification for DNS over Transport Layer Security (TLS)&quot;">RFC7858</a>] and the distorter then trying to find more sophisticated
   ways to block or hijack the connection.  In some cases, this search
   for an alternative, non-disrupting resolver may lead to more
   centralization because many people are switching to a few big
   commercial public resolvers.

<span class="h6"><a class="selflink" id="section-5.2.3.2.3" href="#section-5.2.3.2.3">5.2.3.2.3</a>.  Injection of Records</span>

   Responding incorrectly to requests for name lookups is the most
   common mechanism that in-network devices use to limit the ability of
   end users to discover services.  A deviation that accomplishes a
   similar objective and may be seen as different from a "freedom of
   expression" perspective is the injection of incorrect responses to
   queries.  The most prominent example of this behavior occurs in
   China, where requests for lookups of sites deemed inappropriate will
   trigger the network to return a false response, causing the client to
   ignore the real response when it subsequently arrives
   [<a href="#ref-greatfirewall">greatfirewall</a>].  Unlike the other network paradigms discussed above,
   injection does not stifle the ability of a server to announce its
   name; it instead provides another voice that answers sooner.  This is
   effective because without DNSSEC, the protocol will respond to
   whichever answer is received first, without listening for subsequent
   answers.

<span class="h5"><a class="selflink" id="section-5.2.3.3" href="#section-5.2.3.3">5.2.3.3</a>.  HTTP</span>

   The Hypertext Transfer Protocol (HTTP) version 1.1 [<a href="./rfc7230" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing&quot;">RFC7230</a>]
   [<a href="./rfc7231" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content&quot;">RFC7231</a>] [<a href="./rfc7232" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests&quot;">RFC7232</a>] [<a href="./rfc7233" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Range Requests&quot;">RFC7233</a>] [<a href="./rfc7234" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Caching&quot;">RFC7234</a>] [<a href="./rfc7235" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Authentication&quot;">RFC7235</a>] [<a href="./rfc7236" title="&quot;Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme Registrations&quot;">RFC7236</a>] [<a href="./rfc7237" title="&quot;Initial Hypertext Transfer Protocol (HTTP) Method Registrations&quot;">RFC7237</a>]
   is a request-response application protocol developed throughout the
   1990s.  HTTP factually contributed to the exponential growth of the



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Internet and the interconnection of populations around the world.
   Its simple design strongly contributed to the fact that HTTP has
   become the foundation of most modern Internet platforms and
   communication systems, from websites to chat systems and computer-to-
   computer applications.  In its manifestation in the World Wide Web,
   HTTP radically revolutionized the course of technological development
   and the ways people interact with online content and with each other.

   However, HTTP is also a fundamentally insecure protocol that doesn't
   natively provide encryption properties.  While the definition of the
   Secure Sockets Layer (SSL) [<a href="./rfc6101" title="&quot;The Secure Sockets Layer (SSL) Protocol Version 3.0&quot;">RFC6101</a>], and later of Transport Layer
   Security (TLS) [<a href="./rfc5246" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">RFC5246</a>], also happened during the 1990s, the fact
   that HTTP doesn't mandate the use of such encryption layers by
   developers and service providers was one of the reasons for a very
   late adoption of encryption.  Only in the middle of the 2000s did we
   observe big ISPs, such as Google, starting to provide encrypted
   access to their web services.

   The lack of sensitivity and understanding of the critical importance
   of securing web traffic incentivized certain (offensive) actors to
   develop, deploy, and utilize interception systems at large and to
   later launch active injection attacks, in order to swipe large
   amounts of data and compromise Internet-enabled devices.  The
   commercial availability of systems and tools to perform these types
   of attacks also led to a number of human rights abuses that have been
   discovered and reported over the years.

   Generally, we can identify traffic interception (<a href="#section-5.2.3.3.1">Section 5.2.3.3.1</a>)
   and traffic manipulation (<a href="#section-5.2.3.3.2">Section 5.2.3.3.2</a>) as the two most
   problematic attacks that can be performed against applications
   employing a cleartext HTTP transport layer.  That being said, the
   IETF is taking steady steps to move to the encrypted version of HTTP,
   HTTP Secure (HTTPS).

   While this is commendable, we must not lose track of the fact that
   different protocols, implementations, configurations, and networking
   paradigms can intersect such that they (can be used to) adversely
   impact human rights.  For instance, to facilitate surveillance,
   certain countries will throttle HTTPS connections, forcing users to
   switch to (unthrottled) HTTP [<a href="#ref-Aryan-etal">Aryan-etal</a>].

<span class="h6"><a class="selflink" id="section-5.2.3.3.1" href="#section-5.2.3.3.1">5.2.3.3.1</a>.  Traffic Interception</span>

   While we are seeing an increasing trend in the last couple of years
   to employ SSL/TLS as a secure traffic layer for HTTP-based
   applications, we are still far from seeing a ubiquitous use of
   encryption on the World Wide Web.  It is important to consider that
   the adoption of SSL/TLS is also a relatively recent phenomenon.



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Email providers such as riseup.net were the first to enable SSL by
   default.  Google did not introduce an option for its Gmail users to
   navigate with SSL until 2008 [<a href="#ref-Rideout" title="&quot;Making security easier&quot;">Rideout</a>] and turned TLS on by default
   later, in 2010 [<a href="#ref-Schillace" title="&quot;Default https access for Gmail&quot;">Schillace</a>].  It took an increasing amount of security
   breaches and revelations on global surveillance from Edward Snowden
   before other mail service providers followed suit.  For example,
   Yahoo did not enable SSL/TLS by default on its webmail services until
   early 2014 [<a href="#ref-Peterson" title="&quot;Yahoo to make SSL encryption the default for Webmail users. Finally.&quot;">Peterson</a>].

   TLS itself has been subject to many attacks and bugs; this situation
   can be attributed to some fundamental design weaknesses, such as lack
   of a state machine (which opens a vulnerability for triple handshake
   attacks) and flaws caused by early US government restrictions on
   cryptography, leading to cipher-suite downgrade attacks (Logjam
   attacks).  These vulnerabilities are being corrected in TLS 1.3
   [<a href="#ref-Bhargavan">Bhargavan</a>] [<a href="#ref-Adrian" title="&quot;Imperfect Forward Secrecy: How Diffie-Hellman Fails in Practice&quot;">Adrian</a>].

   HTTP upgrading to HTTPS is also vulnerable to having an attacker
   remove the "s" in any links to HTTPS URIs from a web page transferred
   in cleartext over HTTP -- an attack called "SSL Stripping"
   [<a href="#ref-sslstrip" title="&quot;Software &gt;&gt; sslstrip&quot;">sslstrip</a>].  Thus, for high-security use of HTTPS, IETF standards
   such as HTTP Strict Transport Security (HSTS) [<a href="./rfc6797" title="&quot;HTTP Strict Transport Security (HSTS)&quot;">RFC6797</a>], certificate
   pinning [<a href="./rfc7469" title="&quot;Public Key Pinning Extension for HTTP&quot;">RFC7469</a>], and/or DNS-Based Authentication of Named Entities
   (DANE) [<a href="./rfc6698" title="&quot;The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA&quot;">RFC6698</a>] should be used.

   As we learned through Snowden's revelations, intelligence agencies
   have been intercepting and collecting unencrypted traffic at large
   for many years.  There are documented examples of such
   mass-surveillance programs with the Government Communications
   Headquarters's (GCHQ's) Tempora [<a href="#ref-WP-Tempora">WP-Tempora</a>] and the National
   Security Agency's (NSA's) XKeyscore [<a href="#ref-Greenwald">Greenwald</a>].  Through these
   programs, the NSA and the GCHQ have been able to swipe large amounts
   of data, including email and instant messaging communications that
   have been transported in the clear for years by providers
   unsuspecting of the pervasiveness and scale of governments' efforts
   and investment in global mass-surveillance capabilities.

   However, similar mass interception of unencrypted HTTP communications
   is also often employed at the national level by some democratic
   countries, by exercising control over state-owned ISPs and through
   the use of commercially available monitoring, collection, and
   censorship equipment.  Over the last few years, a lot of information
   has come to public attention on the role and scale of a surveillance
   industry dedicated to developing different types of interception
   gear, making use of known and unknown weaknesses in existing
   protocols [<a href="./rfc7258" title="&quot;Pervasive Monitoring Is an Attack&quot;">RFC7258</a>].  We have several records of such equipment being
   sold and utilized by some regimes in order to monitor entire segments
   of a population, especially at times of social and political



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   distress, uncovering massive human rights abuses.  For example, in
   2013, the group Telecomix revealed that the Syrian regime was making
   use of Blue Coat products in order to intercept cleartext traffic as
   well as to enforce censorship of unwanted content [<a href="#ref-RSF" title="&quot;Syria using 34 Blue Coat servers to spy on Internet users&quot;">RSF</a>].  Similarly,
   in 2011, it was found that the French technology firm Amesys provided
   the Gadhafi government with equipment able to intercept emails,
   Facebook traffic, and chat messages at a country-wide level [<a href="#ref-WSJ" title="&quot;Firms Aided Libyan Spies&quot;">WSJ</a>].
   The use of such systems, especially in the context of the Arab Spring
   and of civil uprisings against the dictatorships, has caused serious
   concerns regarding significant human rights abuses in Libya.

<span class="h6"><a class="selflink" id="section-5.2.3.3.2" href="#section-5.2.3.3.2">5.2.3.3.2</a>.  Traffic Manipulation</span>

   The lack of a secure transport layer under HTTP connections not only
   exposes users to interception of the content of their communications
   but is more and more commonly abused as a vehicle for actively
   compromising computers and mobile devices.  If an HTTP session
   travels in the clear over the network, any node positioned at any
   point in the network is able to perform man-in-the-middle attacks;
   the node can observe, manipulate, and hijack the session and can
   modify the content of the communication in order to trigger
   unexpected behavior by the application generating the traffic.  For
   example, in the case of a browser, the attacker would be able to
   inject malicious code in order to exploit vulnerabilities in the
   browser or any of its plugins.  Similarly, the attacker would be able
   to intercept, add malware to, and repackage binary software updates
   that are very commonly downloaded in the clear by applications such
   as word processors and media players.  If the HTTP session were
   encrypted, the tampering of the content would not be possible, and
   these network injection attacks would not be successful.

   While traffic manipulation attacks have long been known, documented,
   and prototyped, especially in the context of Wi-Fi and LAN networks,
   in the last few years we have observed an increasing investment in
   the production and sale of network injection equipment that is both
   commercially available and deployed at scale by intelligence
   agencies.

   For example, we learned from some of the documents provided by Edward
   Snowden to the press that the NSA has constructed a global network
   injection infrastructure, called "QUANTUM", able to leverage mass
   surveillance in order to identify targets of interest and
   subsequently task man-on-the-side attacks to ultimately compromise a
   selected device.  Among other attacks, the NSA makes use of an attack
   called "QUANTUMINSERT" [<a href="#ref-Haagsma" title="&quot;Deep dive into QUANTUM INSERT&quot;">Haagsma</a>], which intercepts and hijacks an
   unencrypted HTTP communication and forces the requesting browser to
   redirect to a host controlled by the NSA instead of the intended
   website.  Normally, the new destination would be an exploitation



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   service, referred to in Snowden documents as "FOXACID", which would
   attempt to execute malicious code in the context of the target's
   browser.  The Guardian reported in 2013 that the NSA has, for
   example, been using these techniques to target users of the popular
   anonymity service Tor [<a href="#ref-Schneier" title="&quot;Attacking Tor: how the NSA targets users' online anonymity&quot;">Schneier</a>].  The German Norddeutscher Rundfunk
   (NDR) reported in 2014 that the NSA has also been using its
   mass-surveillance capabilities to identify Tor users at large
   [<a href="#ref-Appelbaum">Appelbaum</a>].

   Recently, similar capabilities used by Chinese authorities have been
   reported as well in what has been informally called the "Great
   Cannon" [<a href="#ref-Marcak" title="&quot;China's Great Cannon&quot;">Marcak</a>], which raised numerous concerns on the potential
   curb on human rights and freedom of speech due to the increasingly
   tighter control of Chinese Internet communications and access to
   information.

   Network injection attacks are also made widely available to state
   actors around the world through the commercialization of similar,
   smaller-scale equipment that can be easily acquired and deployed at a
   country-wide level.  Certain companies are known to have network
   injection gear within their products portfolio [<a href="#ref-Marquis-Boire">Marquis-Boire</a>].  The
   technology devised and produced by some of them to perform network
   traffic manipulation attacks on HTTP communications is even the
   subject of a patent application in the United States [<a href="#ref-Googlepatent">Googlepatent</a>].
   Access to offensive technologies available on the commercial lawful
   interception market has led to human rights abuses and illegitimate
   surveillance of journalists, human rights defenders, and political
   activists in many countries around the world [<a href="#ref-Collins" title="&quot;Hacking Team's oppressive regimes customer list revealed in hack&quot;">Collins</a>].  While
   network injection attacks haven't been the subject of much attention,
   they do enable even unskilled attackers to perform silent and very
   resilient compromises, and unencrypted HTTP remains one of the main
   vehicles.

   There is a new version of HTTP, called "HTTP/2" [<a href="./rfc7540" title="&quot;Hypertext Transfer Protocol Version 2 (HTTP/2)&quot;">RFC7540</a>], which aims
   to be largely backwards compatible while also offering new options
   such as data compression of HTTP headers, pipelining of requests, and
   multiplexing multiple requests over a single TCP connection.  In
   addition to decreasing latency to improve page-loading speeds, it
   also facilitates more efficient use of connectivity in low-bandwidth
   environments, which in turn enables freedom of expression; the right
   to assembly; the right to political participation; and the right to
   participate in cultural life, arts, and science.  [<a href="./rfc7540" title="&quot;Hypertext Transfer Protocol Version 2 (HTTP/2)&quot;">RFC7540</a>] does not
   mandate TLS or any other form of encryption, nor does it support
   opportunistic encryption even though opportunistic encryption is now
   addressed in [<a href="./rfc8164" title="&quot;Opportunistic Security for HTTP/2&quot;">RFC8164</a>].






<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h5"><a class="selflink" id="section-5.2.3.4" href="#section-5.2.3.4">5.2.3.4</a>.  XMPP</span>

   The Extensible Messaging and Presence Protocol (XMPP), specified in
   [<a href="./rfc6120" title="&quot;Extensible Messaging and Presence Protocol (XMPP): Core&quot;">RFC6120</a>], provides a standard for interactive chat messaging and has
   evolved to encompass interoperable text, voice, and video chat.  The
   protocol is structured as a federated network of servers, similar to
   email, where users register with a local server that acts on their
   behalf to cache and relay messages.  This protocol design has many
   advantages, allowing servers to shield clients from denial of service
   and other forms of retribution for their expression; it is also
   designed to avoid central entities that could control the ability to
   communicate or assemble using the protocol.

   Nonetheless, there are plenty of aspects of the protocol design of
   XMPP that shape the ability for users to communicate freely and to
   assemble via the protocol.

<span class="h6"><a class="selflink" id="section-5.2.3.4.1" href="#section-5.2.3.4.1">5.2.3.4.1</a>.  User Identification</span>

   The XMPP specification [<a href="./rfc6120" title="&quot;Extensible Messaging and Presence Protocol (XMPP): Core&quot;">RFC6120</a>] dictates that clients are identified
   with a resource (&lt;node@domain/home&gt; / &lt;node@domain/work&gt;) to
   distinguish the conversations to specific devices.  While the
   protocol does not specify that the resource must be exposed by the
   client's server to remote users, in practice this has become the
   default behavior.  In doing so, users can be tracked by remote
   friends and their servers, who are able to monitor the presence of
   not just the user but of each individual device the user logs in
   with.  This has proven to be misleading to many users [<a href="#ref-Pidgin" title="&quot;[XMPP] Invisible mode violating standard&quot;">Pidgin</a>], since
   many clients only expose user-level rather than device-level
   presence.  Likewise, user invisibility so that communication can
   occur while users don't notify all buddies and other servers of their
   availability is not part of the formal protocol and has only been
   added as an extension within the XML stream rather than enforced by
   the protocol.

<span class="h6"><a class="selflink" id="section-5.2.3.4.2" href="#section-5.2.3.4.2">5.2.3.4.2</a>.  Surveillance of Communication</span>

   XMPP specifies the standard by which communications channels may be
   encrypted, but it does not provide visibility to clients regarding
   whether their communications are encrypted on each link.  In
   particular, even when both clients ensure that they have an encrypted
   connection to their XMPP server to ensure that their local network is
   unable to read or disrupt the messages they send, the protocol does
   not provide visibility into the encryption status between the two
   servers.  As such, clients may be subject to selective disruption of
   communications by an intermediate network that disrupts
   communications based on keywords found through DPI.  While many
   operators have committed to only establishing encrypted links from



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   their servers in recognition of this vulnerability, it remains
   impossible for users to audit this behavior, and encrypted
   connections are not required by the protocol itself [<a href="#ref-XMPP-Manifesto">XMPP-Manifesto</a>].

   In particular, <a href="#section-13.14">Section 13.14</a> of the XMPP specification [<a href="./rfc6120" title="&quot;Extensible Messaging and Presence Protocol (XMPP): Core&quot;">RFC6120</a>]
   explicitly acknowledges the existence of a downgrade attack where an
   adversary controlling an intermediate network can force the
   inter-domain federation between servers to revert to a non-encrypted
   protocol where selective messages can then be disrupted.

<span class="h6"><a class="selflink" id="section-5.2.3.4.3" href="#section-5.2.3.4.3">5.2.3.4.3</a>.  Group Chat Limitations</span>

   Group chat in XMPP is defined as an extension within the XML
   specification of XMPP (<a href="https://xmpp.org/extensions/xep-0045.html">https://xmpp.org/extensions/xep-0045.html</a>).
   However, it is not encoded or required at a protocol level and is not
   uniformly implemented by clients.

   The design of multi-user chat in XMPP suffers from extending a
   protocol that was not designed with assembly of many users in mind.
   In particular, in the federated protocol provided by XMPP, multi-user
   communities are implemented with a distinguished "owner" who is
   granted control over the participants and structure of the
   conversation.

   Multi-user chat rooms are identified by a name specified on a
   specific server, so that while the overall protocol may be federated,
   the ability for users to assemble in a given community is moderated
   by a single server.  That server may block the room and prevent
   assembly unilaterally, even between two users, neither of whom trust
   or use that server directly.

<span class="h5"><a class="selflink" id="section-5.2.3.5" href="#section-5.2.3.5">5.2.3.5</a>.  Peer-to-Peer</span>

   Peer-to-Peer (P2P) is a distributed network architecture [<a href="./rfc5694" title="&quot;Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and Applicability&quot;">RFC5694</a>] in
   which all the participant nodes can be responsible for the storage
   and dissemination of information from any other node (see [<a href="./rfc7574" title="&quot;Peer-to- Peer Streaming Peer Protocol (PPSPP)&quot;">RFC7574</a>],
   an IETF standard that discusses a P2P architecture called the
   "Peer-to-Peer Streaming Peer Protocol" (PPSPP)).  A P2P network is a
   logical overlay that lives on top of the physical network and allows
   nodes (or "peers") participating in it to establish contact and
   exchange information directly with each other.  The implementation of
   a P2P network may vary widely: it may be structured or unstructured,
   and it may implement stronger or weaker cryptographic and anonymity
   properties.  While its most common application has traditionally been
   file-sharing (and other types of content delivery systems), P2P is a
   popular architecture for networks and applications that require (or
   encourage) decentralization.  Prime examples include Bitcoin and
   other proprietary multimedia applications.



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   In a time of heavily centralized online services, P2P is regularly
   described as an alternative, more democratic, and resistant option
   that displaces structures of control over data and communications and
   delegates all peers to be equally responsible for the functioning,
   integrity, and security of the data.  While in principle P2P remains
   important to the design and development of future content
   distribution, messaging, and publishing systems, it poses numerous
   security and privacy challenges that are mostly delegated to
   individual developers to recognize, analyze, and solve in each
   implementation of a given P2P network.

<span class="h6"><a class="selflink" id="section-5.2.3.5.1" href="#section-5.2.3.5.1">5.2.3.5.1</a>.  Network Poisoning</span>

   Since content, and sometimes peer lists, are safeguarded and
   distributed by their members, P2P networks are prone to what are
   generally defined as "poisoning attacks".  Poisoning attacks might be
   aimed directly at the data that is being distributed, for example,
   (1) by intentionally corrupting the data, (2) at the index tables
   used to instruct the peers where to fetch the data, or (3) at routing
   tables, with an attempt to provide connecting peers with lists of
   rogue or nonexistent peers, with the intention to effectively cause a
   denial of service on the network.

<span class="h6"><a class="selflink" id="section-5.2.3.5.2" href="#section-5.2.3.5.2">5.2.3.5.2</a>.  Throttling</span>

   P2P traffic (and BitTorrent in particular) represents a significant
   percentage of global Internet traffic [<a href="#ref-Sandvine" title="&quot;Sandvine: Over 70% Of North American Traffic Is Now Streaming Video And Audio&quot;">Sandvine</a>], and it has become
   increasingly popular for ISPs to perform throttling of customers'
   lines in order to limit bandwidth usage [<a href="#ref-torrentfreak1">torrentfreak1</a>] and,
   sometimes, probably as an effect of the ongoing conflict between
   copyright holders and file-sharing communities [<a href="#ref-wikileaks">wikileaks</a>].  Such
   throttling undermines the end-to-end principle.

   Throttling the P2P traffic makes some uses of P2P networks
   ineffective; this throttling might be coupled with stricter
   inspection of users' Internet traffic through DPI techniques,
   possibly posing additional security and privacy risks.

<span class="h6"><a class="selflink" id="section-5.2.3.5.3" href="#section-5.2.3.5.3">5.2.3.5.3</a>.  Tracking and Identification</span>

   One of the fundamental and most problematic issues with traditional
   P2P networks is a complete lack of anonymization of their users.  For
   example, in the case of BitTorrent, all peers' IP addresses are
   openly available to the other peers.  This has led to ever-increasing
   tracking of P2P and file-sharing users [<a href="#ref-ars" title="&quot;P2P researchers: use a blocklist or you will be tracked... 100% of the time&quot;">ars</a>].  As the geographical
   location of the user is directly exposed, as could also be his
   identity, the user might become a target of additional harassment and
   attacks of a physical or legal nature.  For example, it is known that



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   in Germany law firms have made extensive use of P2P and file-sharing
   tracking systems in order to identify downloaders and initiate legal
   actions looking for compensations [<a href="#ref-torrentfreak2">torrentfreak2</a>].

   It is worth noting that there are some varieties of P2P networks that
   implement cryptographic practices and that introduce anonymization of
   their users.  Such implementations may be proved to be successful in
   resisting censorship of content and tracking of network peers.  A
   prime example is Freenet [<a href="#ref-freenet1" title="&quot;What is Freenet?&quot;">freenet1</a>], a free software application that
   is (1) designed to make it significantly more difficult to identify
   users and content and (2) dedicated to fostering freedom of speech
   online [<a href="#ref-freenet2" title="&quot;The Philosophy behind Freenet&quot;">freenet2</a>].

<span class="h6"><a class="selflink" id="section-5.2.3.5.4" href="#section-5.2.3.5.4">5.2.3.5.4</a>.  Sybil Attacks</span>

   In open-membership P2P networks, a single attacker can pretend to be
   many participants, typically by creating multiple fake identities of
   whatever kind the P2P network uses [<a href="#ref-Douceur" title="&quot;The Sybil Attack&quot;">Douceur</a>].  Attackers can use
   Sybil attacks to bias choices that the P2P network makes collectively
   to the attacker's advantage, e.g., by making it more likely that a
   particular data item (or some threshold of the replicas or shares of
   a data item) is assigned to attacker-controlled participants.  If the
   P2P network implements any voting, moderation, or peer-review-like
   functionality, Sybil attacks may be used to "stuff the ballots" to
   benefit the attacker.  Companies and governments can use Sybil
   attacks on discussion-oriented P2P systems for "astroturfing" or
   creating the appearance of mass grassroots support for some position
   where in reality there is none.  It is important to know that there
   are no known complete, environmentally sustainable, and fully
   distributed solutions to Sybil attacks, and routing via "friends"
   allows users to be de-anonymized via their social graph.  It is
   important to note that Sybil attacks in this context (e.g.,
   astroturfing) are relevant to more than P2P protocols; they are also
   common on web-based systems, and they are exploited by governments
   and commercial entities.

   Encrypted P2P and anonymous P2P networks have already emerged.  They
   provide viable platforms for sharing material [<a href="#ref-Tribler" title="&quot;About Tribler&quot;">Tribler</a>], publishing
   content anonymously, and communicating securely [<a href="#ref-Bitmessage">Bitmessage</a>].  These
   platforms are not perfect, and more research needs to be done.  If
   adopted at large, well-designed and resistant P2P networks might
   represent a critical component of a future secure and distributed
   Internet, enabling freedom of speech and freedom of information
   at scale.







<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 34]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h5"><a class="selflink" id="section-5.2.3.6" href="#section-5.2.3.6">5.2.3.6</a>.  Virtual Private Networks</span>

   The VPNs discussed here are point-to-point connections that enable
   two computers to communicate over an encrypted tunnel.  There are
   multiple implementations and protocols used in the deployment of
   VPNs, and they generally diversify by encryption protocol or
   particular requirements, most commonly in proprietary and enterprise
   solutions.  VPNs are commonly used to (1) enable some devices to
   communicate through peculiar network configurations, (2) use some
   privacy and security properties in order to protect the traffic
   generated by the end user, or both.  VPNs have also become a very
   popular technology among human rights defenders, dissidents, and
   journalists worldwide to avoid local monitoring and eventually also
   to circumvent censorship.  VPNs are often debated among human rights
   defenders as a potential alternative to Tor or other anonymous
   networks.  Such comparisons are misleading, as some of the privacy
   and security properties of VPNs are often misunderstood by less
   tech-savvy users and could ultimately lead to unintended problems.

   As VPNs have increased in popularity, commercial VPN providers have
   started growing as businesses and are very commonly picked by human
   rights defenders and people at risk, as they are normally provided
   with an easy-to-use service and, sometimes, even custom applications
   to establish the VPN tunnel.  Not being able to control the
   configuration of the network, let alone the security of the
   application, assessing the general privacy and security state of
   common VPNs is very hard.  Such services have often been discovered
   to be leaking information, and their custom applications have been
   found to be flawed.  While Tor and similar networks receive a lot of
   scrutiny from the public and the academic community, commercial or
   non-commercial VPNs are far less analyzed and understood [<a href="#ref-Insinuator">Insinuator</a>]
   [<a href="#ref-Alshalan-etal">Alshalan-etal</a>], and it might be valuable to establish some standards
   to guarantee a minimal level of privacy and security to those who
   need them the most.

<span class="h6"><a class="selflink" id="section-5.2.3.6.1" href="#section-5.2.3.6.1">5.2.3.6.1</a>.  No Anonymity against VPN Providers</span>

   One of the common misconceptions among users of VPNs is the level of
   anonymity that VPNs can provide.  This sense of anonymity can be
   betrayed by a number of attacks or misconfigurations of the VPN
   provider.  It is important to remember that, in contrast to Tor and
   similar systems, VPNs were not designed to provide anonymity
   properties.  From a technical point of view, a VPN might leak
   identifiable information or might be the subject of correlation
   attacks that could expose the originating address of a connecting
   user.  Most importantly, it is vital to understand that commercial
   and non-commercial VPN providers are bound by the law of the
   jurisdiction in which they reside or in which their infrastructure is



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 35]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   located, and they might be legally forced to turn over data of
   specific users if legal investigations or intelligence requirements
   dictate so.  In such cases, if the VPN providers retain logs, it is
   possible that a user's information could be provided to the user's
   adversary and lead to his or her identification.

<span class="h6"><a class="selflink" id="section-5.2.3.6.2" href="#section-5.2.3.6.2">5.2.3.6.2</a>.  Logging</span>

   Because VPNs are point-to-point connections, the service providers
   are in fact able to observe the original location of connecting
   users, and they are able to track at what time they started their
   session and, eventually, also to which destinations they're trying to
   connect.  If the VPN providers retain logs for a long enough time,
   they might be forced to turn over the relevant data or they might be
   otherwise compromised, leading to the same data getting exposed.  A
   clear log-retention policy could be enforced, but considering that
   countries enforce different levels of data-retention policies, VPN
   providers should at least be transparent regarding what information
   they store and for how long it is being kept.

<span class="h6"><a class="selflink" id="section-5.2.3.6.3" href="#section-5.2.3.6.3">5.2.3.6.3</a>.  Third-Party Hosting</span>

   VPN providers very commonly rely on third parties to provision the
   infrastructure that is later going to be used to run VPN endpoints.
   For example, they might rely on external dedicated server providers
   or on uplink providers.  In those cases, even if the VPN provider
   itself isn't retaining any significant logs, the information on
   connecting users might be retained by those third parties instead,
   introducing an additional collection point for the adversary.

<span class="h6"><a class="selflink" id="section-5.2.3.6.4" href="#section-5.2.3.6.4">5.2.3.6.4</a>.  IPv6 Leakage</span>

   Some studies proved that several commercial VPN providers and
   applications suffer from critical leakage of information through IPv6
   due to improper support and configuration [<a href="#ref-PETS2015VPN">PETS2015VPN</a>].  This is
   generally caused by a lack of proper configuration of the client's
   IPv6 routing tables.  Considering that most popular browsers and
   similar applications have been supporting IPv6 by default, if the
   host is provided with a functional IPv6 configuration, the traffic
   that is generated might be leaked if the VPN application isn't
   designed to manipulate such traffic properly.










<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 36]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h6"><a class="selflink" id="section-5.2.3.6.5" href="#section-5.2.3.6.5">5.2.3.6.5</a>.  DNS Leakage</span>

   Similarly, VPN services that aren't handling DNS requests and aren't
   running DNS servers of their own might be prone to DNS leaking that
   might not only expose sensitive information on the activity of a user
   but could also potentially lead to DNS hijacking attacks and
   subsequent compromises.

<span class="h6"><a class="selflink" id="section-5.2.3.6.6" href="#section-5.2.3.6.6">5.2.3.6.6</a>.  Traffic Correlation</span>

   Some VPN implementations appear to be particularly vulnerable to
   identification and collection of key exchanges that, some Snowden
   documents revealed, are systematically collected and stored for
   future reference.  The ability of an adversary to monitor network
   connections at many different points over the Internet can allow them
   to perform traffic correlation attacks and identify the origin of
   certain VPN traffic by cross-referencing the connection time of the
   user to the endpoint and the connection time of the endpoint to the
   final destination.  These types of attacks, although very expensive
   and normally only performed by very resourceful adversaries, have
   been documented [<a href="#ref-SPIEGEL" title="&quot;Prying Eyes - Inside the NSA's War on Internet Security&quot;">SPIEGEL</a>] to be already in practice, and they could
   completely nullify the use of a VPN and ultimately expose the
   activity and the identity of a user at risk.

<span class="h5"><a class="selflink" id="section-5.2.3.7" href="#section-5.2.3.7">5.2.3.7</a>.  HTTP Status Code 451</span>

   "Every Internet user has run into the '404 Not Found' Hypertext
   Transfer Protocol (HTTP) status code when trying, and failing, to
   access a particular website" [<a href="#ref-Cath" title="&quot;A Case Study of Coding Rights: Should Freedom of Speech Be Instantiated in the Protocols and Standards Designed by the Internet Engineering Task Force?&quot;">Cath</a>].  It is a response status that
   the server sends to the browser when the server cannot locate the
   URL. "403 Forbidden" is another example of this class of code signals
   that gives users information about what is going on.  In the "403"
   case, the server can be reached but is blocking the request because
   the user is trying to access content forbidden to them, typically
   because some content is only for identified users, based on a payment
   or on special status in the organization.  Most of the time, 403 is
   sent by the origin server, not by an intermediary.  If a firewall
   prevents a government employee from accessing pornography on a work
   computer, it does not use 403.












<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 37]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   As surveillance and censorship of the Internet are becoming more
   commonplace, voices were raised at the IETF to introduce a new status
   code that indicates when something is not available for "legal
   reasons" (like censorship):

   The 451 status code would allow server operators to operate with
   greater transparency in circumstances where issues of law or public
   policy affect their operation.  This transparency may be beneficial
   to both (1) these operators and (2) end users [<a href="./rfc7725" title="&quot;An HTTP Status Code to Report Legal Obstacles&quot;">RFC7725</a>].

   The status code is named "451" in reference to both Bradbury's famous
   novel "Fahrenheit 451" and to 451 degrees Fahrenheit (the temperature
   at which some claim book paper autoignites).

   During the IETF 92 meeting in Dallas, there was discussion about the
   usefulness of 451.  The main tension revolved around the lack of an
   apparent machine-readable technical use of the information.  The
   extent to which 451 is just "political theatre" or whether it has a
   concrete technical use was heatedly debated.  Some argued that "the
   451 status code is just a status code with a response body"; others
   said it was problematic because "it brings law into the picture."
   Still others argued that it would be useful for individuals or for
   organizations like the "Chilling Effects" project that are crawling
   the Web to get an indication of censorship (IETF discussion on 451 --
   author's field notes, March 2015).  There was no outright objection
   during the Dallas meeting against moving forward on status code 451,
   and on December 18, 2015, the IESG approved "An HTTP Status Code to
   Report Legal Obstacles" (now [<a href="./rfc7725" title="&quot;An HTTP Status Code to Report Legal Obstacles&quot;">RFC7725</a>]) for publication.  HTTP status
   code 451 is now an IETF-approved HTTP status code that signals when
   resource access is denied as a consequence of legal demands.

   What is interesting about this particular case is that not only
   technical arguments but also the status code's outright potential
   political use for civil society played a substantial role in shaping
   the discussion and the decision to move forward with this technology.

   It is nonetheless important to note that HTTP status code 451 is not
   a solution to detect all occasions of censorship.  A large swath of
   Internet filtering occurs in the network, at a lower level than HTTP,
   rather than at the server itself.  For these forms of censorship, 451
   plays a limited role, as typical censoring intermediaries won't
   generate it.  Besides technical reasons, such filtering regimes are
   unlikely to voluntarily inject a 451 status code.  The use of 451 is
   most likely to apply in the case of cooperative, legal versions of
   content removal resulting from requests to providers.  One can think
   of content that is removed or blocked for legal reasons, like
   copyright infringement, gambling laws, child abuse, etc.  Large




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 38]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Internet companies and search engines are constantly asked to censor
   content in various jurisdictions.  451 allows this to be easily
   discovered -- for instance, by initiatives like the Lumen Database.

   Overall, the strength of 451 lies in its ability to provide
   transparency by giving the reason for blocking and giving the
   end user the ability to file a complaint.  It allows organizations to
   easily measure censorship in an automated way and prompts the user to
   access the content via another path (e.g., Tor, VPNs) when (s)he
   encounters the 451 status code.

   Status code 451 impacts human rights by making censorship more
   transparent and measurable.  It increases transparency by signaling
   the existence of censorship (instead of a much broader HTTP error
   message such as HTTP status code 404) as well as providing details of
   the legal restriction, which legal authority is imposing it, and to
   what class of resources it applies.  This empowers the user to seek
   redress.

<span class="h5"><a class="selflink" id="section-5.2.3.8" href="#section-5.2.3.8">5.2.3.8</a>.  DDoS Attacks</span>

   Many individuals, including IETF engineers, have argued that DDoS
   attacks are fundamentally against freedom of expression.
   Technically, DDoS attacks are attacks where one host or multiple
   hosts overload the bandwidth or resources of another host by flooding
   it with traffic or making resource-intensive requests, causing it to
   temporarily stop being available to users.  One can roughly
   differentiate three types of DDoS attacks:

   1.  volume-based attacks (which aim to make the host unreachable by
       using up all its bandwidth; often-used techniques are UDP floods
       and ICMP floods)

   2.  protocol attacks (which aim to use up actual server resources;
       often-used techniques are SYN floods, fragmented packet attacks,
       and "ping of death" [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>])

   3.  application-layer attacks (which aim to bring down a server, such
       as a web server)

   DDoS attacks can thus stifle freedom of expression and complicate the
   ability of independent media and human rights organizations to
   exercise their right to (online) freedom of association, while
   facilitating the ability of governments to censor dissent.  When it
   comes to comparing DDoS attacks to protests in offline life, it is
   important to remember that only a limited number of DDoS attacks
   solely involved willing participants.  In the overwhelming majority
   of cases, the clients are hacked hosts of unrelated parties that



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 39]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   have not consented to being part of a DDoS (for exceptions, see
   Operation Ababil [<a href="#ref-Ababil" title="&quot;Dissecting 'Operation Ababil' - an OSINT Analysis&quot;">Ababil</a>] or the Iranian Green Movement's DDoS
   campaign at election time [<a href="#ref-GreenMovement">GreenMovement</a>]).  In addition,
   DDoS attacks are increasingly used as an extortion tactic.

   All of these issues seem to suggest that the IETF should try to
   ensure that their protocols cannot be used for DDoS attacks; this is
   consistent with the long-standing IETF consensus that DDoS is an
   attack that protocols should mitigate to the extent they can [<a href="#ref-BCP72" title="&quot;Guidelines for Writing RFC Text on Security Considerations&quot;">BCP72</a>].
   Decreasing the number of vulnerabilities in protocols and (outside of
   the IETF) the number of bugs in the network stacks of routers or
   computers could address this issue.  The IETF can clearly play a role
   in bringing about some of these changes, but the IETF cannot be
   expected to take a positive stance on (specific) DDoS attacks or to
   create protocols that enable some attacks and inhibit others.  What
   the IETF can do is critically reflect on its role in the development
   of the Internet and how this impacts the ability of people to
   exercise their human rights, such as freedom of expression.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Model for Developing Human Rights Protocol Considerations</span>

   This section outlines a set of human rights protocol considerations
   for protocol developers.  It provides questions that engineers should
   ask themselves when developing or improving protocols if they want to
   understand their impact on human rights.  It should, however, be
   noted that the impact of a protocol cannot be solely deduced from its
   design; its usage and implementation should also be studied to form a
   full assessment of the impact of the protocol on human rights.

   The questions are based on the research performed by the HRPC
   Research Group.  This research was documented prior to the writing of
   these considerations.  The research establishes that human rights
   relate to standards and protocols; it also 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.  With this, a model
   for developing human rights protocol considerations has taken shape.

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  Human Rights Threats</span>

   Human rights threats on the Internet come in a myriad of forms.
   Protocols and standards can either harm or enable the right to
   freedom of expression; the right to non-discrimination; the right to
   equal protection; the right to participate in cultural life, arts,
   and science; the right to freedom of assembly and association; and
   the right to security.  An end user who is denied access to certain
   services, data, or websites may be unable to disclose vital
   information about malpractice on the part of a government or other



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 40]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   authority.  A person whose communications are monitored may be
   prevented from exercising their right to freedom of association or
   participation in political processes [<a href="#ref-Penney" title="&quot;Chilling Effects: Online Surveillance and Wikipedia Use&quot;">Penney</a>].  In a worst-case
   scenario, protocols that leak information can lead to physical
   danger.  A realistic example to consider is when, based on
   information gathered by state agencies through information leakage in
   protocols, individuals perceived as threats to the state are
   subjected to torture, extrajudicial killings, or detention.

   This section details several "common" threats to human rights,
   indicating how each of these can lead to harm to, or violations of,
   human rights.  It also presents several examples of how these threats
   to human rights materialize on the Internet.  This threat modeling is
   inspired by [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>] ("Privacy Considerations for Internet
   Protocols"), which is based on security threat analysis.  This method
   is by no means a perfect solution for assessing human rights risks in
   Internet protocols and systems; it is, however, the best approach
   currently available.  Certain specific human rights threats are
   indirectly considered in Internet protocols as part of their security
   considerations [<a href="#ref-BCP72" title="&quot;Guidelines for Writing RFC Text on Security Considerations&quot;">BCP72</a>], but privacy guidelines [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>] or reviews,
   let alone the assessments of the impact of protocols on human rights,
   are not standardized or implemented.

   Many threats, enablers, and risks are linked to different rights.
   This is not surprising if one takes into account that human rights
   are interrelated, interdependent, and indivisible.  Here, however,
   we're not discussing all human rights, because not all human rights
   are relevant to ICTs in general and to protocols and standards in
   particular [<a href="#ref-Bless1" title="&quot;Values and Networks - Steps Toward Exploring their Relationships&quot;">Bless1</a>]:

      The main source of the values of human rights is the International
      Bill of Human Rights that is composed of the Universal Declaration
      of Human Rights [<a href="#ref-UDHR" title="&quot;The Universal Declaration of Human Rights&quot;">UDHR</a>] along with the International Covenant on
      Civil and Political Rights [<a href="#ref-ICCPR" title="&quot;International Covenant on Civil and Political Rights&quot;">ICCPR</a>] and the International Covenant
      on Economic, Social and Cultural Rights [<a href="#ref-ICESCR" title="&quot;International Covenant on Economic, Social and Cultural Rights&quot;">ICESCR</a>].  In the light of
      several cases of Internet censorship, the Human Rights Council
      Resolution 20/8 was adopted in 2012 [<a href="#ref-UNHRC2016">UNHRC2016</a>], affirming "...
      that the same rights that people have offline must also be
      protected online ..."  In 2015, the Charter of Human Rights and
      Principles for the Internet [<a href="#ref-IRP" title="&quot;10 Internet Rights &amp; Principles&quot;">IRP</a>] was developed and released.
      According to these documents, some examples of human rights
      relevant for ICT systems are human dignity (Art. 1 UDHR),
      non-discrimination (Art. 2), rights to life, liberty and security
      (Art. 3), freedom of opinion and expression (Art. 19), freedom of
      assembly and association (Art. 20), rights to equal protection,
      legal remedy, fair trial, due process, presumed innocent
      (Art. 7-11), appropriate social and international order (Art. 28),




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 41]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      participation in public affairs (Art. 21), participation in
      cultural life, protection of intellectual property (Art. 27), and
      privacy (Art. 12).

   A partial catalog of human rights related to ICTs, including economic
   rights, can be found in [<a href="#ref-Hill2014" title="&quot;Partial Catalog of Human Rights Related to ICT Activities&quot;">Hill2014</a>].

   This is by no means an attempt to exclude specific rights or
   prioritize some rights over others.  If other rights seem relevant,
   please contact the authors of this document.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  Guidelines for Human Rights Considerations</span>

   This section provides guidance for document authors in the form of a
   questionnaire about protocols and their (potential) impact.  The
   questionnaire may be useful at any point in the design process,
   particularly after document authors have developed a high-level
   protocol model as described in [<a href="./rfc4101" title="&quot;Writing Protocol Models&quot;">RFC4101</a>].  These guidelines do not
   seek to replace any existing referenced specifications; rather, they
   contribute to them and look at the design process from a human rights
   perspective.

   Protocols and Internet Standards might benefit from a documented
   discussion of potential human rights risks arising from potential
   misapplications of the protocol or technology described in the RFC in
   question.  This might be coupled with an Applicability Statement for
   that RFC.

   Note that the guidance provided in this section does not recommend
   specific practices.  The range of protocols developed in the IETF is
   too broad to make recommendations about particular uses of data or
   how human rights might be balanced against other design goals.
   However, by carefully considering the answers to the following
   questions, document authors should be able to produce a comprehensive
   analysis that can serve as the basis for discussion on whether the
   protocol adequately takes specific human rights threats into account.
   This guidance is meant to help the thought process of a human rights
   analysis; it does not provide specific directions for how to write a
   human rights protocol considerations section (following the example
   set in [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>]), and the addition of a human rights protocol
   considerations section has also not yet been proposed.  In
   considering these questions, authors will need to be aware of the
   potential of technical advances or the passage of time to undermine
   protections.  In general, considerations of rights are likely to be
   more effective if they are considered given a purpose and specific
   use cases, rather than as abstract absolute goals.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 42]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>.  Connectivity</span>

   Questions:

   -  Does your protocol add application-specific functions to
      intermediary nodes?

   -  Could this functionality be added to end nodes instead of
      intermediary nodes?

   -  Is your protocol optimized for low bandwidth and high-latency
      connections?

   -  Could your protocol also be developed in a stateless manner?

   Explanation:  The end-to-end principle [<a href="#ref-Saltzer" title="&quot;End-to-End Arguments in System Design&quot;">Saltzer</a>] holds that "the
      intelligence is end to end rather than hidden in the network"
      [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>].  The end-to-end principle is important for the
      robustness of the network and innovation.  Such robustness of the
      network is crucial to enabling human rights like freedom of
      expression.

   Example:  Middleboxes (which can be content delivery networks,
      firewalls, NATs, or other intermediary nodes that provide
      "services" other than routing) serve many legitimate purposes.
      But the protocols guiding them can influence individuals' ability
      to communicate online freely and privately.  The potential for
      abuse, intentional and unintentional censoring, and limiting
      permissionless innovation -- and thus, ultimately, the impact of
      middleboxes on the Internet as a place of unfiltered, unmonitored
      freedom of speech -- is real.

   Impacts:

   -  Right to freedom of expression

   -  Right to freedom of assembly and association

<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>.  Privacy</span>

   Questions:

   -  Did you have a look at the guidelines in <a href="./rfc6973#section-7">Section&nbsp;7 of [RFC6973]</a>
      ("Privacy Considerations for Internet Protocols")?

   -  Could your protocol in any way impact the confidentiality of
      protocol metadata?




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 43]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   -  Could your protocol counter traffic analysis?

   -  Could your protocol improve data minimization?

   -  Does your document identify potentially sensitive data logged by
      your protocol and/or for how long that data needs to be retained
      for technical reasons?

   Explanation:  "Privacy" refers to the right of an entity (normally a
      person), acting on its own behalf, to determine the degree to
      which it will interact with its environment, including the degree
      to which the entity is willing to share its personal information
      with others [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].  If a protocol provides insufficient
      privacy protection, it may have a negative impact on freedom of
      expression as users self-censor for fear of surveillance or find
      themselves unable to express themselves freely.

   Example:  See [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>].

   Impacts:

   -  Right to freedom of expression

   -  Right to non-discrimination

<span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>.  Content Agnosticism</span>

   Questions:

   -  If your protocol impacts packet handling, does it use user data
      (packet data that is not included in the header)?

   -  Does your protocol make decisions based on the payload of the
      packet?

   -  Does your protocol prioritize certain content or services over
      others in the routing process?

   -  Is the protocol transparent about the prioritization that is made
      (if any)?

   Explanation:  "Content agnosticism" refers to the notion that network
      traffic is treated identically regardless of payload, with some
      exceptions when it comes to effective traffic handling -- for
      instance, delay-tolerant or delay-sensitive packets based on the
      header.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 44]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Example:  Content agnosticism prevents payload-based discrimination
      against packets.  This is important because changes to this
      principle can lead to a two-tiered Internet, where certain packets
      are prioritized over others based on their content.  Effectively,
      this would mean that although all users are entitled to receive
      their packets at a certain speed, some users become more equal
      than others.

   Impacts:

   -  Right to freedom of expression

   -  Right to non-discrimination

   -  Right to equal protection

<span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>.  Security</span>

   Questions:

   -  Did you have a look at [<a href="#ref-BCP72" title="&quot;Guidelines for Writing RFC Text on Security Considerations&quot;">BCP72</a>] ("Guidelines for Writing RFC Text
      on Security Considerations")?

   -  Have you found any attacks that are somewhat related to your
      protocol yet considered out of scope for your document?

   -  Would these attacks be pertinent to the features of the Internet
      that enable human rights (as described throughout this document)?

   Explanation:  Most people speak of security as if it were a single
      monolithic property of a protocol or system; however, upon
      reflection one realizes that it is clearly not true.  Rather,
      security is a series of related but somewhat independent
      properties.  Not all of these properties are required for every
      application.  Since communications are carried out by systems and
      access to systems is through communications channels, these goals
      obviously interlock, but they can also be independently provided
      [<a href="#ref-BCP72" title="&quot;Guidelines for Writing RFC Text on Security Considerations&quot;">BCP72</a>].

   Example:  See [<a href="#ref-BCP72" title="&quot;Guidelines for Writing RFC Text on Security Considerations&quot;">BCP72</a>].











<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 45]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Impacts:

   -  Right to freedom of expression

   -  Right to freedom of assembly and association

   -  Right to non-discrimination

   -  Right to security

<span class="h4"><a class="selflink" id="section-6.2.5" href="#section-6.2.5">6.2.5</a>.  Internationalization</span>

   Questions:

   -  Does your protocol have text strings that have to be understood or
      entered by humans?

   -  Does your protocol allow Unicode?  If so, do you accept texts in
      one charset (which must be UTF-8) or several (which is dangerous
      for interoperability)?

   -  If character sets or encodings other than UTF-8 are allowed, does
      your protocol mandate proper tagging of the charset?

   -  Did you have a look at [<a href="./rfc6365" title="&quot;Terminology Used in Internationalization in the IETF&quot;">RFC6365</a>]?

   Explanation:  "Internationalization" refers to the practice of making
      protocols, standards, and implementations usable in different
      languages and scripts (see <a href="#section-6.2.12">Section 6.2.12</a> ("Localization")).  "In
      the IETF, 'internationalization' means to add or improve the
      handling of non-ASCII text in a protocol" [<a href="./rfc6365" title="&quot;Terminology Used in Internationalization in the IETF&quot;">RFC6365</a>].

      A different perspective, more appropriate to protocols that are
      designed for global use from the beginning, is the definition used
      by the W3C [<a href="#ref-W3Ci18nDef">W3Ci18nDef</a>]: "Internationalization is the design and
      development of a product, application or document content that
      enables easy localization for target audiences that vary in
      culture, region, or language."

      Many protocols that handle text only handle one charset
      (US-ASCII), or they leave the question of what coded character set
      (CCS) and encoding are used up to local guesswork (which leads, of
      course, to interoperability problems) [<a href="./rfc3536" title="&quot;Terminology Used in Internationalization in the IETF&quot;">RFC3536</a>].  If multiple
      charsets are permitted, they must be explicitly identified
      [<a href="./rfc2277" title="&quot;IETF Policy on Character Sets and Languages&quot;">RFC2277</a>].  Adding non-ASCII text to a protocol allows the
      protocol to handle more scripts, hopefully all scripts in use in
      the world.  In today's world, that is normally best accomplished
      by allowing Unicode encoded in UTF-8 only.



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 46]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      In the current IETF policy [<a href="./rfc2277" title="&quot;IETF Policy on Character Sets and Languages&quot;">RFC2277</a>], internationalization is
      aimed at user-facing strings, not protocol elements, such as the
      verbs used by some text-based protocols.  (Do note that some
      strings, such as identifiers, are both content and protocol
      elements.)  If the Internet wants to be a global network of
      networks, the protocols should work with languages other than
      English and character sets other than Latin characters.  It is
      therefore crucial that at least the content carried by the
      protocol can be in any script and that all scripts are treated
      equally.

   Example:  See <a href="#section-6.2.12">Section 6.2.12</a> ("Localization").

   Impacts:

   -  Right to freedom of expression

   -  Right to political participation

   -  Right to participate in cultural life, arts, and science

<span class="h4"><a class="selflink" id="section-6.2.6" href="#section-6.2.6">6.2.6</a>.  Censorship Resistance</span>

   Questions:

   -  Does this protocol introduce new identifiers or reuse existing
      identifiers (e.g., Media Access Control (MAC) addresses) that
      might be associated with persons or content?

   -  Does your protocol make it apparent or transparent when access to
      a resource is restricted?

   -  Can your protocol contribute to filtering in such a way that it
      could be implemented to censor data or services?  If so, could
      your protocol be designed to ensure that this doesn't happen?

   Explanation:  "Censorship resistance" refers to the methods and
      measures to prevent Internet censorship.

   Example:  When IPv6 was developed, embedding a MAC address into
      unique IP addresses was discussed.  This makes it possible, per
      [<a href="./rfc4941" title="&quot;Privacy Extensions for Stateless Address Autoconfiguration in IPv6&quot;">RFC4941</a>], for "eavesdroppers and other information collectors to
      identify when different addresses used in different transactions
      actually correspond to the same node."  This is why privacy
      extensions for stateless address autoconfiguration in IPv6
      [<a href="./rfc4941" title="&quot;Privacy Extensions for Stateless Address Autoconfiguration in IPv6&quot;">RFC4941</a>] have been introduced.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 47]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      Identifiers of content exposed within a protocol might be used to
      facilitate censorship, as in the case of application-layer-based
      censorship, which affects protocols like HTTP.  Denial or
      restriction of access can be made apparent by the use of status
      code 451, thereby allowing server operators to operate with
      greater transparency in circumstances where issues of law or
      public policy affect their operation [<a href="./rfc7725" title="&quot;An HTTP Status Code to Report Legal Obstacles&quot;">RFC7725</a>].

   Impacts:

   -  Right to freedom of expression

   -  Right to political participation

   -  Right to participate in cultural life, arts, and science

   -  Right to freedom of assembly and association

<span class="h4"><a class="selflink" id="section-6.2.7" href="#section-6.2.7">6.2.7</a>.  Open Standards</span>

   Questions:

   -  Is your protocol fully documented in such a way that it could be
      easily implemented, improved, built upon, and/or further
      developed?

   -  Do you depend on proprietary code for the implementation, running,
      or further development of your protocol?

   -  Does your protocol favor a particular proprietary specification
      over technically equivalent and competing specification(s) -- for
      instance, by making any incorporated vendor specification
      "required" or "recommended" [<a href="./rfc2026" title="&quot;The Internet Standards Process -- Revision 3&quot;">RFC2026</a>]?

   -  Do you normatively reference another standard that is not
      available without cost (and could you possibly do without it)?

   -  Are you aware of any patents that would prevent your standard from
      being fully implemented [<a href="./rfc6701" title="&quot;Sanctions Available for Application to Violators of IETF IPR Policy&quot;">RFC6701</a>] [<a href="./rfc8179" title="&quot;Intellectual Property Rights in IETF Technology&quot;">RFC8179</a>]?

   Explanation:  The Internet was able to be developed into the global
      network of networks because of the existence of open,
      non-proprietary standards [<a href="#ref-Zittrain" title="&quot;The Future of the Internet - And How to Stop It&quot;">Zittrain</a>].  They are crucial for
      enabling interoperability.  Yet, open standards are not explicitly
      defined within the IETF.  On the subject, [<a href="./rfc2026" title="&quot;The Internet Standards Process -- Revision 3&quot;">RFC2026</a>] states the
      following: "Various national and international standards bodies,
      such as ANSI, ISO, IEEE, and ITU-T, develop a variety of protocol
      and service specifications that are similar to Technical



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 48]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      Specifications defined" at the IETF.  "National and international
      groups also publish 'implementors' agreements' that are analogous
      to Applicability Statements, capturing a body of implementation-
      specific detail concerned with the practical application of their
      standards.  All of these are considered to be 'open external
      standards' for the purposes of the Internet Standards Process."
      Similarly, [<a href="./rfc3935" title="&quot;A Mission Statement for the IETF&quot;">RFC3935</a>] does not define open standards but does
      emphasize the importance of "open process": any interested person
      can participate in the work, know what is being decided, and make
      his or her voice heard on the issue.  Part of this principle is
      the IETF's commitment to making its documents, WG mailing lists,
      attendance lists, and meeting minutes publicly available on the
      Internet.

      Open standards are important, as they allow for permissionless
      innovation, which in turn is important for maintaining the freedom
      and ability to freely create and deploy new protocols on top of
      the communications constructs that currently exist.  It is at the
      heart of the Internet as we know it, and to maintain its
      fundamentally open nature, we need to be mindful of the need for
      developing open standards.

      All standards that need to be normatively implemented should be
      freely available and should provide reasonable protection against
      patent infringement claims, so that it can also be implemented in
      open-source or free software.  Patents have often held back open
      standardization or have been used against those deploying open
      standards, particularly in the domain of cryptography [<a href="#ref-Newegg" title="&quot;Newegg on trial: Mystery company TQP rewrites the history of encryption&quot;">Newegg</a>].
      An exemption is sometimes made when a protocol that normatively
      relies on specifications produced by other SDOs that are not
      freely available is standardized.  Patents in open standards or in
      normative references to other standards should have a patent
      disclosure [<a href="#ref-notewell" title="&quot;Note Well&quot;">notewell</a>], royalty-free licensing [<a href="#ref-patentpolicy">patentpolicy</a>], or
      some other form of reasonable protection.  Reasonable patent
      protection should include, but is not limited to, cryptographic
      primitives.

   Example:  [<a href="./rfc6108" title="&quot;Comcast's Web Notification System Design&quot;">RFC6108</a>] describes a system deployed by Comcast, an ISP,
      for providing critical end-user notifications to web browsers.
      Such a notification system is being used to provide
      almost-immediate notifications to customers, such as warning them
      that their traffic exhibits patterns that are indicative of
      malware or virus infection.  There are other proprietary systems
      that can perform such notifications, but those systems utilize
      Deep Packet Inspection (DPI) technology.  In contrast to DPI,
      [<a href="./rfc6108" title="&quot;Comcast's Web Notification System Design&quot;">RFC6108</a>] describes a system that does not rely upon DPI and is
      instead based on open IETF standards and open-source applications.




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 49]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Impacts:

   -  Right to freedom of expression

   -  Right to participate in cultural life, arts, and science

<span class="h4"><a class="selflink" id="section-6.2.8" href="#section-6.2.8">6.2.8</a>.  Heterogeneity Support</span>

   Questions:

   -  Does your protocol support heterogeneity by design?

   -  Does your protocol allow for multiple types of hardware?

   -  Does your protocol allow for multiple types of application
      protocols?

   -  Is your protocol liberal in what it receives and handles?

   -  Will your protocol remain usable and open if the context changes?

   -  Does your protocol allow well-defined extension points?  If so, do
      these extension points allow for open innovation?

   Explanation:  [<a href="#ref-FIArch" title="&quot;Future Internet Design Principles&quot;">FIArch</a>] notes the following: "The Internet is
      characterized by heterogeneity on many levels: devices and nodes,
      router scheduling algorithms and queue management mechanisms,
      routing protocols, levels of multiplexing, protocol versions and
      implementations, underlying link layers (e.g., point-to-point,
      multi-access links, wireless, FDDI, etc.), in the traffic mix and
      in the levels of congestion at different times and places.
      Moreover, as the Internet is composed of autonomous organizations
      and internet service providers, each with their own separate
      policy concerns, there is a large heterogeneity of administrative
      domains and pricing structures."  As a result, as also noted in
      [<a href="#ref-FIArch" title="&quot;Future Internet Design Principles&quot;">FIArch</a>], the heterogeneity principle proposed in [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>] needs
      to be supported by design.

   Example:  Heterogeneity is inevitable and needs to be supported by
      design.  For example, multiple types of hardware must be allowed
      for transmission speeds differing by at least seven orders of
      magnitude, various computer word lengths, and hosts ranging from
      memory-starved microprocessors up to massively parallel
      supercomputers.  As noted in [<a href="./rfc1958" title="&quot;Architectural Principles of the Internet&quot;">RFC1958</a>], "Multiple types of
      application protocol must be allowed for, ranging from the
      simplest such as remote login up to the most complex such as
      distributed databases."




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 50]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Impacts:

   -  Right to freedom of expression

   -  Right to political participation

<span class="h4"><a class="selflink" id="section-6.2.9" href="#section-6.2.9">6.2.9</a>.  Anonymity</span>

   Question:

   -  Did you have a look at [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>] ("Privacy Considerations for
      Internet Protocols"), especially <a href="#section-6.1.1">Section 6.1.1</a> of that document?

   Explanation:  "Anonymity" refers to the condition of an identity
      being unknown or concealed [<a href="./rfc4949" title="&quot;Internet Security Glossary, Version 2&quot;">RFC4949</a>].  Even though full anonymity
      is hard to achieve, it is a non-binary concept.  Making pervasive
      monitoring and tracking harder is important for many users as well
      as for the IETF [<a href="./rfc7258" title="&quot;Pervasive Monitoring Is an Attack&quot;">RFC7258</a>].  Achieving a higher level of anonymity
      is an important feature for many end users, as it allows them
      different degrees of privacy online.

   Example:  Protocols often expose personal data; it is therefore
      important to consider ways to mitigate the obvious impacts on
      privacy.  A protocol that uses data that could help identify a
      sender (items of interest) should be protected from third parties.
      For instance, if one wants to hide the source/destination IP
      addresses of a packet, the use of IPsec in tunneling mode (e.g.,
      inside a VPN) can help protect against third parties likely to
      eavesdrop packets exchanged between the tunnel endpoints.

   Impacts:

   -  Right to non-discrimination

   -  Right to political participation

   -  Right to freedom of assembly and association

   -  Right to security

<span class="h4"><a class="selflink" id="section-6.2.10" href="#section-6.2.10">6.2.10</a>.  Pseudonymity</span>

   Questions:

   -  Have you considered [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>] ("Privacy Considerations for
      Internet Protocols"), especially <a href="#section-6.1.2">Section 6.1.2</a> of that document?

   -  Does the protocol collect personally derived data?



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 51]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   -  Does the protocol generate or process anything that can be, or
      that can be tightly correlated with, personally identifiable
      information?

   -  Does the protocol utilize data that is personally derived, i.e.,
      derived from the interaction of a single person or from their
      device or address?

   -  Does this protocol generate personally derived data?  If so, how
      will that data be handled?

   Explanation:  Pseudonymity -- the ability to use a persistent
      identifier that is not immediately linked to one's offline
      identity -- is an important feature for many end users, as it
      allows them different degrees of disguised identity and privacy
      online.

   Example:  When designing a standard that exposes personal data, it is
      important to consider ways to mitigate the obvious impacts.  While
      pseudonyms cannot easily be reverse-engineered -- for example,
      some early approaches used such techniques as simple hashing of IP
      addresses that could in turn be easily reversed by generating a
      hash for each potential IP address and comparing it to the
      pseudonym -- limiting the exposure of personal data remains
      important.

      "Pseudonymity" means using a pseudonym instead of one's "real"
      name.  There are many reasons for users to use pseudonyms -- for
      instance, to hide their gender; protect themselves against
      harassment; protect their families' privacy; frankly discuss
      sexuality; or develop an artistic or journalistic persona without
      retribution from an employer, (potential) customers, or social
      surroundings [<a href="#ref-geekfeminism">geekfeminism</a>].  The difference between anonymity and
      pseudonymity is that a pseudonym is often persistent.
      "Pseudonymity is strengthened when less personal data can be
      linked to the pseudonym; when the same pseudonym is used less
      often and across fewer contexts; and when independently chosen
      pseudonyms are more frequently used for new actions (making them,
      from an observer's or attacker's perspective, unlinkable)."
      [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>]

   Impacts:

   -  Right to non-discrimination

   -  Right to freedom of assembly and association





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 52]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h4"><a class="selflink" id="section-6.2.11" href="#section-6.2.11">6.2.11</a>.  Accessibility</span>

   Questions:

   -  Is your protocol designed to provide an enabling environment for
      people who are not able-bodied?

   -  Have you looked at the W3C Web Accessibility Initiative
      [<a href="#ref-W3CAccessibility">W3CAccessibility</a>] for examples and guidance?

   Explanation:  The Internet is fundamentally designed to work for all
      people, whatever their hardware, software, language, culture,
      location, or physical or mental ability.  When the Internet meets
      this goal, it is accessible to people with a diverse range of
      hearing, movement, sight, and cognitive abilities
      [<a href="#ref-W3CAccessibility">W3CAccessibility</a>].  Sometimes, in the design of protocols,
      websites, web technologies, or web tools, barriers that exclude
      people from using the Web are created.

   Example:  The HTML protocol as defined in [<a href="#ref-HTML5" title="&quot;HTML5&quot;">HTML5</a>] specifically
      requires that (with a few exceptions) every image must have an
      "alt" attribute to ensure that images are accessible for people
      that cannot themselves decipher non-text content in web pages.

   Impacts:

   -  Right to non-discrimination

   -  Right to freedom of assembly and association

   -  Right to education

   -  Right to political participation

<span class="h4"><a class="selflink" id="section-6.2.12" href="#section-6.2.12">6.2.12</a>.  Localization</span>

   Questions:

   -  Does your protocol uphold the standards of internationalization?

   -  Have you taken any concrete steps towards localizing your protocol
      for relevant audiences?

   Explanation:  Per [<a href="#ref-W3Ci18nDef">W3Ci18nDef</a>], "Localization refers to the
      adaptation of a product, application or document content to meet
      the language, cultural and other requirements of a specific target
      market (a 'locale')."  It is also described as the practice of




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 53]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      translating an implementation to make it functional in a specific
      language or for users in a specific locale (see <a href="#section-6.2.5">Section 6.2.5</a>
      ("Internationalization")).

   Example:  The Internet is a global medium, but many of its protocols
      and products are developed with a certain audience in mind; this
      audience often shares particular characteristics like knowing how
      to read and write in ASCII and knowing English.  This limits the
      ability of a large part of the world's online population to use
      the Internet in a way that is culturally and linguistically
      accessible.  An example of a protocol that has taken into account
      the view that individuals like to have access to data in their
      native language can be found in [<a href="./rfc5646" title="&quot;Tags for Identifying Languages&quot;">RFC5646</a>]; such a protocol would
      label the information content with an identifier for the language
      in which it is written and would allow information to be presented
      in more than one language.

   Impacts:

   -  Right to non-discrimination

   -  Right to participate in cultural life, arts, and science

   -  Right to freedom of expression

<span class="h4"><a class="selflink" id="section-6.2.13" href="#section-6.2.13">6.2.13</a>.  Decentralization</span>

   Questions:

   -  Can your protocol be implemented without one single point of
      control?

   -  If applicable, can your protocol be deployed in a federated
      manner?

   -  What is the potential for discrimination against users of your
      protocol?

   -  Can your protocol be used to negatively implicate users (e.g.,
      incrimination, accusation)?

   -  Does your protocol create additional centralized points of
      control?

   Explanation:  Decentralization is one of the central technical
      concepts of the architecture of networks and is embraced as such
      by the IETF [<a href="./rfc3935" title="&quot;A Mission Statement for the IETF&quot;">RFC3935</a>].  It refers to the absence or minimization
      of centralized points of control -- "a feature that is assumed to



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 54]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      make it easy for new users to join and new uses to unfold"
      [<a href="#ref-Brown" title="&quot;A Prehistory of Internet Governance&quot;">Brown</a>].  It also reduces issues surrounding single points of
      failure and distributes the network such that it continues to
      function if one or several nodes are disabled.  With the
      commercialization of the Internet in the early 1990s, there has
      been a slow trend toward moving away from decentralization, to the
      detriment of any technical benefits that having a decentralized
      Internet otherwise provides.

   Example:  The bits traveling the Internet are increasingly
      susceptible to monitoring and censorship, from both governments
      and ISPs, as well as third (malicious) parties.  The ability to
      monitor and censor is further enabled by increased centralization
      of the network, creating central infrastructure points that can be
      tapped into.  The creation of P2P networks and the development of
      voice-over-IP protocols using P2P technology in combination with a
      distributed hash table (DHT) for scalability are examples of how
      protocols can preserve decentralization [<a href="#ref-Pouwelse" title="&quot;Media without censorship (CensorFree) scenarios&quot;">Pouwelse</a>].

   Impacts:

   -  Right to freedom of expression

   -  Right to freedom of assembly and association

<span class="h4"><a class="selflink" id="section-6.2.14" href="#section-6.2.14">6.2.14</a>.  Reliability</span>

   Questions:

   -  Is your protocol fault tolerant?

   -  Does your protocol degrade gracefully?

   -  Can your protocol resist malicious degradation attempts?

   -  Do you have a documented way to announce degradation?

   -  Do you have measures in place for recovery or partial healing from
      failure?

   -  Can your protocol maintain dependability and performance in the
      face of unanticipated changes or circumstances?

   Explanation:  Reliability ensures that a protocol will execute its
      function consistently, be error resistant as described, and
      function without unexpected results.  A system that is reliable
      degenerates gracefully and will have a documented way to announce
      degradation.  It also has mechanisms to recover from failure



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 55]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


      gracefully and, if applicable, to allow for partial healing.  It
      is important here to draw a distinction between random degradation
      and malicious degradation.  Many current attacks against TLS, for
      example, exploit TLS's ability to gracefully degrade to older
      cipher suites; from a functional perspective, this ability is
      good, but from a security perspective, it can be very bad.  As
      with confidentiality, the growth of the Internet and fostering
      innovation in services depend on users having confidence and trust
      [<a href="./rfc3724" title="&quot;The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture&quot;">RFC3724</a>] in the network.  For reliability, it is necessary that
      services notify users if packet delivery fails.  In the case of
      real-time systems, the protocol needs to safeguard timeliness in
      addition to providing reliable delivery.

   Example:  In the modern IP stack structure, a reliable transport
      layer requires an indication that transport processing has
      successfully completed, such as the indication given by TCP's ACK
      message [<a href="./rfc793" title="&quot;Transmission Control Protocol&quot;">RFC793</a>] and not simply an indication from the IP layer
      that the packet arrived.  Similarly, an application-layer protocol
      may require an application-specific acknowledgement that contains,
      among other things, a status code indicating the disposition of
      the request (see [<a href="./rfc3724" title="&quot;The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture&quot;">RFC3724</a>]).

   Impacts:

   -  Right to freedom of expression

   -  Right to security

<span class="h4"><a class="selflink" id="section-6.2.15" href="#section-6.2.15">6.2.15</a>.  Confidentiality</span>

   Questions:

   -  Does this protocol expose information related to identifiers or
      data?  If so, does it do so to each of the other protocol entities
      (i.e., recipients, intermediaries, and enablers) [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>]?

   -  What options exist for protocol implementers to choose to limit
      the information shared with each entity?

   -  What operational controls are available to limit the information
      shared with each entity?

   -  What controls or consent mechanisms does the protocol define or
      require before personal data or identifiers are shared or exposed
      via the protocol?  If no such mechanisms or controls are
      specified, is it expected that control and consent will be handled
      outside of the protocol?




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 56]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   -  Does the protocol provide ways for initiators to share different
      pieces of information with different recipients?  If not, are
      there mechanisms that exist outside of the protocol to provide
      initiators with such control?

   -  Does the protocol provide ways for initiators to limit which
      information is shared with intermediaries?  If not, are there
      mechanisms that exist outside of the protocol to provide users
      with such control?

   -  Is it expected that users will have relationships that govern the
      use of the information (contractual or otherwise) with those who
      operate these intermediaries?

   -  Does the protocol prefer encryption over cleartext operation?

   -  Does the protocol provide ways for initiators to express
      individuals' preferences to recipients or intermediaries with
      regard to the collection, use, or disclosure of their personal
      data?

   Explanation:  "Confidentiality" refers to keeping a user's data
      secret from unintended listeners [<a href="#ref-BCP72" title="&quot;Guidelines for Writing RFC Text on Security Considerations&quot;">BCP72</a>].  The growth of the
      Internet depends on users having confidence that the network
      protects their personal data [<a href="./rfc1984" title="&quot;IAB and IESG Statement on Cryptographic Technology and the Internet&quot;">RFC1984</a>].

   Example:  Protocols that do not encrypt their payload make the entire
      content of the communication available to the idealized attacker
      along their path [<a href="./rfc7624" title="&quot;Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement&quot;">RFC7624</a>].  Following the advice in [<a href="./rfc3365" title="&quot;Strong Security Requirements for Internet Engineering Task Force Standard Protocols&quot;">RFC3365</a>],
      most such protocols have a secure variant that encrypts the
      payload for confidentiality, and these secure variants are seeing
      ever-wider deployment.  A noteworthy exception is DNS [<a href="./rfc1035" title="&quot;Domain names - implementation and specification&quot;">RFC1035</a>],
      as DNSSEC [<a href="./rfc4033" title="&quot;DNS Security Introduction and Requirements&quot;">RFC4033</a>] does not have confidentiality as a
      requirement.  This implies that, in the absence of changes to the
      protocol as presently under development in the IETF's DNS Private
      Exchange (DPRIVE) Working Group, all DNS queries and answers
      generated by the activities of any protocol are available to the
      attacker.  When store-and-forward protocols are used (e.g., SMTP
      [<a href="./rfc5321" title="&quot;Simple Mail Transfer Protocol&quot;">RFC5321</a>]), intermediaries leave this data subject to observation
      by an attacker that has compromised these intermediaries, unless
      the data is encrypted end to end by the application-layer protocol
      or the implementation uses an encrypted store for this data
      [<a href="./rfc7624" title="&quot;Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement&quot;">RFC7624</a>].








<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 57]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Impacts:

   -  Right to privacy

   -  Right to security

<span class="h4"><a class="selflink" id="section-6.2.16" href="#section-6.2.16">6.2.16</a>.  Integrity</span>

   Questions:

   -  Does your protocol maintain, assure, and/or verify the accuracy of
      payload data?

   -  Does your protocol maintain and assure the consistency of data?

   -  Does your protocol in any way allow the data to be (intentionally
      or unintentionally) altered?

   Explanation:  "Integrity" refers to the maintenance and assurance of
      the accuracy and consistency of data to ensure that it has not
      been (intentionally or unintentionally) altered.

   Example:  Integrity verification of data is important for preventing
      vulnerabilities and attacks such as man-in-the-middle attacks.
      These attacks happen when a third party (often for malicious
      reasons) intercepts a communication between two parties, inserting
      themselves in the middle and changing the content of the data.  In
      practice, this looks as follows:

      Alice wants to communicate with Bob.
      Corinne forges and sends a message to Bob, impersonating Alice.
      Bob cannot see that the data from Alice was altered by Corinne.
      Corinne intercepts and alters the communication as it is sent
      between Alice and Bob.
      Corinne is able to control the communication content.

   Impacts:

   -  Right to freedom of expression

   -  Right to security










<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 58]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h4"><a class="selflink" id="section-6.2.17" href="#section-6.2.17">6.2.17</a>.  Authenticity</span>

   Questions:

   -  Do you have sufficient measures in place to confirm the truth of
      an attribute of an entity or of a single piece of data?

   -  Can attributes get garbled along the way (see <a href="#section-6.2.4">Section 6.2.4</a>
      ("Security"))?

   -  If relevant, have you implemented IPsec, DNSSEC, HTTPS, and other
      standard security best practices?

   Explanation:  Authenticity ensures that data does indeed come from
      the source it claims to come from.  This is important for
      preventing (1) certain attacks or (2) unauthorized access to, and
      use of, data.

   Example:  Authentication of data is important for preventing
      vulnerabilities and attacks such as man-in-the-middle attacks.
      These attacks happen when a third party (often for malicious
      reasons) intercepts a communication between two parties, inserting
      themselves in the middle and posing as both parties.  In practice,
      this looks as follows:

      Alice wants to communicate with Bob.
      Alice sends data to Bob.
      Corinne intercepts the data sent to Bob.
      Corinne reads and alters the message to Bob.
      Bob cannot see that the data did not come from Alice but instead
      came from Corinne.

      When there is proper authentication, the scenario would be as
      follows:

      Alice wants to communicate with Bob.
      Alice sends data to Bob.
      Corinne intercepts the data sent to Bob.
      Corinne reads and alters the message to Bob.
      Bob can see that the data did not come from Alice but instead came
      from Corinne.










<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 59]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   Impacts:

   -  Right to privacy

   -  Right to freedom of expression

   -  Right to security

<span class="h4"><a class="selflink" id="section-6.2.18" href="#section-6.2.18">6.2.18</a>.  Adaptability</span>

   Questions:

   -  Is your protocol written in such a way that it would be easy for
      other protocols to be developed on top of it or to interact
      with it?

   -  Does your protocol impact permissionless innovation (see
      <a href="#section-6.2.1">Section 6.2.1</a> ("Connectivity") above)?

   Explanation:  Adaptability is closely interrelated with
      permissionless innovation; both maintain the freedom and ability
      to freely create and deploy new protocols on top of the
      communications constructs that currently exist.  Permissionless
      innovation is at the heart of the Internet as we know it.  To
      maintain the Internet's fundamentally open nature and ensure that
      it can continue to develop, we need to be mindful of the impact of
      protocols on maintaining or reducing permissionless innovation.

   Example:  WebRTC generates audio and/or video data.  In order to
      ensure that WebRTC can be used in different locations by different
      parties, it is important that standard JavaScript APIs be
      developed to support applications from different voice service
      providers.  Multiple parties will have similar capabilities; in
      order to ensure that all parties can build upon existing
      standards, these standards need to be adaptable and allow for
      permissionless innovation.

   Impacts:

   -  Right to education

   -  Right to freedom of expression

   -  Right to freedom of assembly and association







<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 60]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h4"><a class="selflink" id="section-6.2.19" href="#section-6.2.19">6.2.19</a>.  Outcome Transparency</span>

   Question:

   -  Are the effects of your protocol fully and easily comprehensible,
      including with respect to unintended consequences of protocol
      choices?

   Explanation:  Certain technical choices may have unintended
      consequences.

   Example:  Lack of authenticity may lead to lack of integrity and
      negative externalities; spam is an example.  Lack of data that
      could be used for billing and accounting can lead to so-called
      "free" arrangements that obscure the actual costs and distribution
      of the costs -- for example, (1) the barter arrangements that are
      commonly used for Internet interconnection and (2) the commercial
      exploitation of personal data for targeted advertising, which is
      the most common funding model for the so-called "free" services
      such as search engines and social networks.

   Impacts:

   -  Right to freedom of expression

   -  Right to privacy

   -  Right to freedom of assembly and association

   -  Right to access to information

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Security Considerations</span>

   As this document discusses research, there are no security
   considerations.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  IANA Considerations</span>

   This document does not require any IANA actions.












<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 61]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  Research Group Information</span>

   The discussion list for the IRTF Human Rights Protocol Considerations
   Research Group is located at the email address &lt;hrpc@ietf.org&gt;.
   Information on the group and information on how to subscribe to the
   list are provided at &lt;<a href="https://www.irtf.org/mailman/listinfo/hrpc">https://www.irtf.org/mailman/listinfo/hrpc</a>&gt;.

   Archives of the list can be found at
   &lt;<a href="https://www.irtf.org/mail-archive/web/hrpc/current/index.html">https://www.irtf.org/mail-archive/web/hrpc/current/index.html</a>&gt;.

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  Informative References</span>

   [<a id="ref-Ababil">Ababil</a>]   Danchev, D., "Dissecting 'Operation Ababil' - an OSINT
              Analysis", September 2012, &lt;<a href="http://ddanchev.blogspot.be/2012/09/dissecting-operation-ababil-osint.html">http://ddanchev.blogspot.be/</a>
              <a href="http://ddanchev.blogspot.be/2012/09/dissecting-operation-ababil-osint.html">2012/09/dissecting-operation-ababil-osint.html</a>&gt;.

   [<a id="ref-Abbate">Abbate</a>]   Abbate, J., "Inventing the Internet", MIT Press, 2000,
              &lt;<a href="https://mitpress.mit.edu/books/inventing-internet">https://mitpress.mit.edu/books/inventing-internet</a>&gt;.

   [<a id="ref-Adrian">Adrian</a>]   Adrian, D., Bhargavan, K., Durumeric, Z., Gaudry, P.,
              Green, M., Halderman, J., Heninger, N., Springall, D.,
              Thome, E., Valenta, L., VanderSloot, B., Wustrow, E.,
              Zanella-Beguelin, S., and P. Zimmermann, "Imperfect
              Forward Secrecy: How Diffie-Hellman Fails in Practice",
              Proceedings of the 22nd ACM SIGSAC Conference on Computer
              and Communications Security, pp. 5-17,
              DOI 10.1145/2810103.2813707, October 2015.

   [<a id="ref-Alshalan-etal">Alshalan-etal</a>]
              Alshalan, A., Pisharody, S., and D. Huang, "A Survey of
              Mobile VPN Technologies", IEEE Communications Surveys &amp;
              Tutorials, Volume 18, Issue 2, pp. 1177-1196,
              DOI 10.1109/COMST.2015.2496624, 2016,
              &lt;<a href="http://ieeexplore.ieee.org/document/7314859/?arnumber=7314859">http://ieeexplore.ieee.org/</a>
              <a href="http://ieeexplore.ieee.org/document/7314859/?arnumber=7314859">document/7314859/?arnumber=7314859</a>&gt;.

   [<a id="ref-APIP">APIP</a>]     Naylor, D., Mukerjee, M., and P. Steenkiste, "Balancing
              accountability and privacy in the network", SIGCOMM '14,
              Proceedings of the 2014 ACM Conference on
              SIGCOMM, pp. 75-86, DOI 10.1145/2740070.2626306,
              October 2014,
              &lt;<a href="https://dl.acm.org/citation.cfm?id=2626306">https://dl.acm.org/citation.cfm?id=2626306</a>&gt;.

   [<a id="ref-Appelbaum">Appelbaum</a>]
              Appelbaum, J., Gibson, A., Goetz, J., Kabisch, V., Kampf,
              L., and L. Ryge, "NSA targets the privacy-conscious",
              2014, &lt;<a href="http://daserste.ndr.de/panorama/aktuell/nsa230_page-1.html">http://daserste.ndr.de/panorama/aktuell/</a>
              <a href="http://daserste.ndr.de/panorama/aktuell/nsa230_page-1.html">nsa230_page-1.html</a>&gt;.



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 62]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-ars">ars</a>]      Anderson, N., "P2P researchers: use a blocklist or you
              will be tracked... 100% of the time", October 2007,
              &lt;<a href="http://arstechnica.com/uncategorized/2007/10/p2p-researchers-use-a-blocklist-or-you-will-be-tracked-100-of-the-time/">http://arstechnica.com/uncategorized/2007/10/</a>
              <a href="http://arstechnica.com/uncategorized/2007/10/p2p-researchers-use-a-blocklist-or-you-will-be-tracked-100-of-the-time/">p2p-researchers-use-a-blocklist-or-you-will-be-tracked-</a>
              <a href="http://arstechnica.com/uncategorized/2007/10/p2p-researchers-use-a-blocklist-or-you-will-be-tracked-100-of-the-time/">100-of-the-time/</a>&gt;.

   [<a id="ref-Aryan-etal">Aryan-etal</a>]
              Aryan, S., Aryan, H., and J. Alex Halderman, "Internet
              Censorship in Iran: A First Look", 2013,
              &lt;<a href="https://jhalderm.com/pub/papers/iran-foci13.pdf">https://jhalderm.com/pub/papers/iran-foci13.pdf</a>&gt;.

   [<a id="ref-Babbie">Babbie</a>]   Babbie, E., "The Basics of Social Research",
              Cengage, Belmont, CA, 2017.

   [<a id="ref-BBC-wikileaks">BBC-wikileaks</a>]
              BBC, "Whistle-blower site taken offline", February 2008,
              &lt;<a href="http://news.bbc.co.uk/2/hi/technology/7250916.stm">http://news.bbc.co.uk/2/hi/technology/7250916.stm</a>&gt;.

   [<a id="ref-BCP72">BCP72</a>]    Rescorla, E. and B. Korver, "Guidelines for Writing RFC
              Text on Security Considerations", <a href="https://www.rfc-editor.org/bcp/bcp72">BCP 72</a>, <a href="./rfc3552">RFC 3552</a>,
              July 2003, &lt;<a href="https://www.rfc-editor.org/info/bcp72">https://www.rfc-editor.org/info/bcp72</a>&gt;.

   [<a id="ref-Benkler">Benkler</a>]  Benkler, Y., "The Wealth of Networks - How Social
              Production Transforms Markets and Freedom", Yale
              University Press, New Haven and London, 2006,
              &lt;<a href="http://is.gd/rxUpTQ">http://is.gd/rxUpTQ</a>&gt;.

   [<a id="ref-Berners-Lee">Berners-Lee</a>]
              Berners-Lee, T. and M. Fischetti, "Weaving the Web: The
              Original Design and Ultimate Destiny of the World Wide
              Web", HarperCollins, p. 208, 1999.

   [<a id="ref-BernersLeeHalpin">BernersLeeHalpin</a>]
              Berners-Lee, T. and H. Halpin, "Internet Access is a Human
              Right", 2012, &lt;<a href="http://www.ibiblio.org/hhalpin/homepage/publications/def-timbl-halpin.pdf">http://www.ibiblio.org/hhalpin/homepage/</a>
              <a href="http://www.ibiblio.org/hhalpin/homepage/publications/def-timbl-halpin.pdf">publications/def-timbl-halpin.pdf</a>&gt;.

   [<a id="ref-Bhargavan">Bhargavan</a>]
              Bhargavan, K., Delignat-Lavaud, A., Fournet, C., Pironti,
              A., and P. Strub, "Triple Handshakes and Cookie Cutters:
              Breaking and Fixing Authentication over TLS", 2014 IEEE
              Symposium on Security and Privacy, pp. 98-113,
              DOI 10.1109/SP.2014.14, May 2014.

   [<a id="ref-Bitmessage">Bitmessage</a>]
              Bitmessage, "Bitmessage Wiki", March 2017,
              &lt;<a href="https://bitmessage.org/wiki/Main_Page">https://bitmessage.org/wiki/Main_Page</a>&gt;.




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 63]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-Bless1">Bless1</a>]   Orwat, C. and R. Bless, "Values and Networks - Steps
              Toward Exploring their Relationships", ACM SIGCOMM
              Computer Communication Review, Volume 46, Number 2,
              pp. 25-31, DOI 10.1145/2935634.2935640, April 2016,
              &lt;<a href="http://www.sigcomm.org/sites/default/files/ccr/papers/2016/April/0000000-0000003.pdf">http://www.sigcomm.org/sites/default/files/ccr/</a>
              <a href="http://www.sigcomm.org/sites/default/files/ccr/papers/2016/April/0000000-0000003.pdf">papers/2016/April/0000000-0000003.pdf</a>&gt;.

   [<a id="ref-Bless2">Bless2</a>]   Bless, R. and C. Orwat, "Values and Networks", July 2015,
              &lt;<a href="https://www.ietf.org/proceedings/93/slides/slides-93-hrpc-2.pdf">https://www.ietf.org/proceedings/93/slides/</a>
              <a href="https://www.ietf.org/proceedings/93/slides/slides-93-hrpc-2.pdf">slides-93-hrpc-2.pdf</a>&gt;.

   [<a id="ref-Broeders">Broeders</a>] Broeders, D., "The public core of the Internet.  An
              international agenda for Internet governance", The
              Netherlands Scientific Council for Government Policy (WRR)
              Report No. 94 (under "Reports to the government"), 2015,
              &lt;<a href="https://english.wrr.nl/publications/reports/2015/10/01/the-public-core-of-the-internet">https://english.wrr.nl/publications/reports/2015/10/01/</a>
              <a href="https://english.wrr.nl/publications/reports/2015/10/01/the-public-core-of-the-internet">the-public-core-of-the-internet</a>&gt;

   [<a id="ref-Brown">Brown</a>]    Ziewitz, M. and I. Brown, Ed., "A Prehistory of Internet
              Governance", Research Handbook on Governance of the
              Internet, Part 1, Chapter 1 (pp. 3-26), Edward Elgar
              Publishing Ltd, Cheltenham, DOI 10.4337/9781849805049,
              2013.

   [<a id="ref-Brown-etal">Brown-etal</a>]
              Brown, I., Clark, D., and D. Trossen, "Should Specific
              Values Be Embedded In The Internet Architecture?",
              ReARCH '10, Proceedings of the Re-Architecting the
              Internet Workshop, Article No. 10,
              DOI 10.1145/1921233.1921246, November 2010,
              &lt;<a href="http://conferences.sigcomm.org/co-next/2010/Workshops/REARCH/ReArch_papers/10-Brown.pdf">http://conferences.sigcomm.org/co-next/2010/Workshops/</a>
              <a href="http://conferences.sigcomm.org/co-next/2010/Workshops/REARCH/ReArch_papers/10-Brown.pdf">REARCH/ReArch_papers/10-Brown.pdf</a>&gt;.

   [<a id="ref-BrownMarsden">BrownMarsden</a>]
              Brown, I. and C. Marsden, "Regulating Code: Good
              Governance and Better Regulation in the Information Age",
              MIT Press, 2013,
              &lt;<a href="https://mitpress.mit.edu/books/regulating-code">https://mitpress.mit.edu/books/regulating-code</a>&gt;.

   [<a id="ref-CAIDA">CAIDA</a>]    Dainotti, A., Squarcella, C., Aben, E., Claffy, K.,
              Chiesa, M., Russo, M., and A. Pescape, "Analysis of
              Country-wide Internet Outages Caused by Censorship",
              DOI 10.1109/TNET.2013.2291244, December 2013,
              &lt;<a href="http://www.caida.org/publications/papers/2014/outages_censorship/outages_censorship.pdf">http://www.caida.org/publications/papers/2014/</a>
              <a href="http://www.caida.org/publications/papers/2014/outages_censorship/outages_censorship.pdf">outages_censorship/outages_censorship.pdf</a>&gt;.






<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 64]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-Cath">Cath</a>]     Cath, C., "A Case Study of Coding Rights: Should Freedom
              of Speech Be Instantiated in the Protocols and Standards
              Designed by the Internet Engineering Task Force?",
              August 2015, &lt;<a href="https://www.ietf.org/mail-archive/web/hrpc/current/pdf36GrmRM84S.pdf">https://www.ietf.org/mail-archive/web/</a>
              <a href="https://www.ietf.org/mail-archive/web/hrpc/current/pdf36GrmRM84S.pdf">hrpc/current/pdf36GrmRM84S.pdf</a>&gt;.

   [<a id="ref-CathFloridi">CathFloridi</a>]
              Cath, C. and L. Floridi, "The Design of the Internet's
              Architecture by the Internet Engineering Task Force (IETF)
              and Human Rights", April 2017.

   [<a id="ref-Clark">Clark</a>]    Clark, D., "The Design Philosophy of the DARPA Internet
              Protocols", SIGCOMM '88, Proceedings of the ACM CCR,
              Volume 18, Number 4, pp. 106-114, DOI 10.1145/52324.52336,
              August 1988.

   [<a id="ref-Clark-etal">Clark-etal</a>]
              Clark, D., Wroclawski, J., Sollins, K., and R. Braden,
              "Tussle in cyberspace: defining tomorrow's Internet",
              IEEE/ACM Transactions on Networking (TON) archive,
              Volume 13, Issue 3, pp. 462-475,
              DOI 10.1109/TNET.2005.850224, June 2005,
              &lt;<a href="https://dl.acm.org/citation.cfm?id=1074049">https://dl.acm.org/citation.cfm?id=1074049</a>&gt;.

   [<a id="ref-CoE">CoE</a>]      Council of Europe, "Applications to ICANN for Community-
              based New Generic Top Level Domains (gTLDs): Opportunities
              and challenges from a human rights perspective", 2016,
              &lt;<a href="https://rm.coe.int/CoERMPublicCommonSearchServices/DisplayDCTMContent?documentId=09000016806b5a14">https://rm.coe.int/CoERMPublicCommonSearchServices/</a>
              <a href="https://rm.coe.int/CoERMPublicCommonSearchServices/DisplayDCTMContent?documentId=09000016806b5a14">DisplayDCTMContent?documentId=09000016806b5a14</a>&gt;.

   [<a id="ref-Collins">Collins</a>]  Collins, K., "Hacking Team's oppressive regimes customer
              list revealed in hack", July 2015,
              &lt;<a href="http://www.wired.co.uk/news/archive/2015-07/06/hacking-team-spyware-company-hacked">http://www.wired.co.uk/news/archive/2015-07/06/</a>
              <a href="http://www.wired.co.uk/news/archive/2015-07/06/hacking-team-spyware-company-hacked">hacking-team-spyware-company-hacked</a>&gt;.

   [<a id="ref-Davidson-etal">Davidson-etal</a>]
              Davidson, A., Morris, J., and R. Courtney, "Strangers in a
              Strange Land: Public Interest Advocacy and Internet
              Standards", Telecommunications Policy Research
              Conference, Alexandria, VA, September 2002,
              &lt;<a href="https://www.cdt.org/files/publications/piais.pdf">https://www.cdt.org/files/publications/piais.pdf</a>&gt;.

   [<a id="ref-DeNardis14">DeNardis14</a>]
              DeNardis, L., "The Global War for Internet Governance",
              Yale University Press, 2014,
              &lt;<a href="https://www.jstor.org/stable/j.ctt5vkz4n">https://www.jstor.org/stable/j.ctt5vkz4n</a>&gt;.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 65]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-DeNardis15">DeNardis15</a>]
              DeNardis, L., "The Internet Design Tension between
              Surveillance and Security", IEEE Annals of the History of
              Computing, Volume 37, Issue 2, DOI 10.1109/MAHC.2015.29,
              2015, &lt;<a href="http://is.gd/7GAnFy">http://is.gd/7GAnFy</a>&gt;.

   [<a id="ref-Denzin">Denzin</a>]   Denzin, N., Ed., and Y. Lincoln, Ed., "The SAGE Handbook
              of Qualitative Research", SAGE Handbooks, Thousand Oaks,
              CA, 2011, &lt;<a href="http://www.amazon.com/SAGE-Handbook-Qualitative-Research-Handbooks/dp/1412974178">http://www.amazon.com/</a>
              <a href="http://www.amazon.com/SAGE-Handbook-Qualitative-Research-Handbooks/dp/1412974178">SAGE-Handbook-Qualitative-Research-Handbooks/</a>
              <a href="http://www.amazon.com/SAGE-Handbook-Qualitative-Research-Handbooks/dp/1412974178">dp/1412974178</a>&gt;.

   [<a id="ref-dict">dict</a>]     BusinessDictionary.com, "Reliability (dictionary entry)",
              WebFinance, Inc., 2017,
              &lt;<a href="http://www.businessdictionary.com/definition/reliability.html">http://www.businessdictionary.com/</a>
              <a href="http://www.businessdictionary.com/definition/reliability.html">definition/reliability.html</a>&gt;.

   [<a id="ref-Doty">Doty</a>]     Doty, N., "Automated text analysis of Requests for Comment
              (RFCs)", 2014, &lt;<a href="https://github.com/npdoty/rfc-analysis">https://github.com/npdoty/rfc-analysis</a>&gt;.

   [<a id="ref-Douceur">Douceur</a>]  Douceur, J., "The Sybil Attack", 2002,
              &lt;<a href="https://www.microsoft.com/en-us/research/wp-content/uploads/2002/01/IPTPS2002.pdf">https://www.microsoft.com/en-us/research/wp-content/</a>
              <a href="https://www.microsoft.com/en-us/research/wp-content/uploads/2002/01/IPTPS2002.pdf">uploads/2002/01/IPTPS2002.pdf</a>&gt;.

   [<a id="ref-Dutton">Dutton</a>]   Dutton, W., Dopatka, A., Law, G., and V. Nash, "Freedom of
              Connection, Freedom of Expression: The Changing Legal and
              Regulatory Ecology Shaping the Internet", 2011,
              &lt;<a href="http://www.unesco.org/new/en/communication-and-">http://www.unesco.org/new/en/communication-and-</a>
              information/resources/publications-and-communication-
              materials/publications/full-list/freedom-of-connection-
              freedom-of-expression-the-changing-legal-and-regulatory-
              ecology-shaping-the-internet/&gt;.

   [<a id="ref-Farrow">Farrow</a>]   Farrow, R., "Source Address Spoofing", 2016,
              &lt;<a href="https://technet.microsoft.com/library/cc723706.aspx">https://technet.microsoft.com/library/cc723706.aspx</a>&gt;.

   [<a id="ref-FIArch">FIArch</a>]   "Future Internet Design Principles", January 2012,
              &lt;<a href="http://www.future-internet.eu/uploads/media/FIArch_Design_Principles_V1.0.pdf">http://www.future-internet.eu/uploads/media/</a>
              <a href="http://www.future-internet.eu/uploads/media/FIArch_Design_Principles_V1.0.pdf">FIArch_Design_Principles_V1.0.pdf</a>&gt;.

   [<a id="ref-FOC">FOC</a>]      Ministers of the Freedom Online Coalition, "The Tallinn
              Agenda - Recommendations for Freedom Online", 2014,
              &lt;<a href="https://www.freedomonlinecoalition.com/wp-content/uploads/2014/04/FOC-recommendations-consensus.pdf">https://www.freedomonlinecoalition.com/wp-content/</a>
              <a href="https://www.freedomonlinecoalition.com/wp-content/uploads/2014/04/FOC-recommendations-consensus.pdf">uploads/2014/04/FOC-recommendations-consensus.pdf</a>&gt;.







<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 66]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-FRAMEWORK">FRAMEWORK</a>]
              ISO/IEC, "Information technology - Framework for
              internationalization", prepared by ISO/IEC
              JTC 1/SC 22/WG 20 ISO/IEC TR 11017, 1998.

   [<a id="ref-Franklin">Franklin</a>] Franklin, U., "The Real World of Technology", June 1999,
              &lt;<a href="http://houseofanansi.com/products/the-real-world-of-technology-digital">http://houseofanansi.com/products/</a>
              <a href="http://houseofanansi.com/products/the-real-world-of-technology-digital">the-real-world-of-technology-digital</a>&gt;.

   [<a id="ref-freenet1">freenet1</a>] Freenet, "What is Freenet?", n.d.,
              &lt;<a href="https://freenetproject.org/whatis.html">https://freenetproject.org/whatis.html</a>&gt;.

   [<a id="ref-freenet2">freenet2</a>] Clarke, I., "The Philosophy behind Freenet", n.d.,
              &lt;<a href="https://freenetproject.org/pages/about.html">https://freenetproject.org/pages/about.html</a>&gt;.

   [<a id="ref-geekfeminism">geekfeminism</a>]
              Geek Feminism Wiki, "Pseudonymity", 2015,
              &lt;<a href="http://geekfeminism.wikia.com/wiki/Pseudonymity">http://geekfeminism.wikia.com/wiki/Pseudonymity</a>&gt;.

   [<a id="ref-Geertz">Geertz</a>]   Geertz, H. and C. Geertz, "Kinship in Bali", University of
              Chicago Press, Chicago, 1975,
              &lt;<a href="http://press.uchicago.edu/ucp/books/book/chicago/K/bo25832222.html">http://press.uchicago.edu/ucp/books/book/chicago/K/</a>
              <a href="http://press.uchicago.edu/ucp/books/book/chicago/K/bo25832222.html">bo25832222.html</a>&gt;.

   [<a id="ref-Googlepatent">Googlepatent</a>]
              Google, "Method and device for network traffic
              manipulation", 2012,
              &lt;<a href="https://www.google.com/patents/EP2601774A1?cl=en">https://www.google.com/patents/EP2601774A1?cl=en</a>&gt;.

   [<a id="ref-greatfirewall">greatfirewall</a>]
              Anonymous, "Towards a Comprehensive Picture of the Great
              Firewall's DNS Censorship", 4th USENIX Workshop on Free
              and Open Communications on the Internet (FOCI) '14,
              August 2014, &lt;<a href="https://www.usenix.org/system/files/conference/foci14/foci14-anonymous.pdf">https://www.usenix.org/system/files/</a>
              <a href="https://www.usenix.org/system/files/conference/foci14/foci14-anonymous.pdf">conference/foci14/foci14-anonymous.pdf</a>&gt;.

   [<a id="ref-GreenMovement">GreenMovement</a>]
              Villeneuve, N., "Iran DDoS", 2009,
              &lt;<a href="https://www.nartv.org/2009/06/16/iran-ddos/">https://www.nartv.org/2009/06/16/iran-ddos/</a>&gt;.

   [<a id="ref-Greenwald">Greenwald</a>]
              Greenwald, G., "XKeyscore: NSA tool collects 'nearly
              everything a user does on the internet'", July 2013,
              &lt;<a href="https://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data">https://www.theguardian.com/world/2013/jul/31/</a>
              <a href="https://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data">nsa-top-secret-program-online-data</a>&gt;.






<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 67]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-Haagsma">Haagsma</a>]  Haagsma, L., "Deep dive into QUANTUM INSERT", April 2015,
              &lt;<a href="http://blog.fox-it.com/2015/04/20/deep-dive-into-quantum-insert/">http://blog.fox-it.com/2015/04/20/</a>
              <a href="http://blog.fox-it.com/2015/04/20/deep-dive-into-quantum-insert/">deep-dive-into-quantum-insert/</a>&gt;.

   [<a id="ref-Hall">Hall</a>]     Hall, J., Aaron, M., Jones, B., and N. Feamster, "A Survey
              of Worldwide Censorship Techniques", Work in Progress,
              <a href="./draft-hall-censorship-tech-04">draft-hall-censorship-tech-04</a>, July 2016.

   [<a id="ref-Hill2014">Hill2014</a>] Hill, R., "Partial Catalog of Human Rights Related to ICT
              Activities", May 2014,
              &lt;<a href="http://www.apig.ch/UNIGE%20Catalog.pdf">http://www.apig.ch/UNIGE%20Catalog.pdf</a>&gt;.

   [<a id="ref-HORNET">HORNET</a>]   Chen, C., Asoni, D., Barrera, D., Danezis, G., and A.
              Perrig, "HORNET: High-speed Onion Routing at the Network
              Layer", CCS '15, Proceedings of the 22nd ACM SIGSAC
              Conference on Computer and Communications
              Security, pp. 1441-1454, DOI 10.1145/2810103.2813628,
              October 2015,
              &lt;<a href="https://dl.acm.org/citation.cfm?id=2813628">https://dl.acm.org/citation.cfm?id=2813628</a>&gt;.

   [<a id="ref-HTML5">HTML5</a>]    Hickson, I., Ed., Berjon, R., Ed., Faulkner, S., Ed.,
              Leithead, T., Ed., Navara, E., Ed., O'Connor, E., Ed., and
              S. Pfeiffer, Ed., "HTML5", W3C Recommendation,
              October 2014, &lt;<a href="https://www.w3.org/TR/html5/">https://www.w3.org/TR/html5/</a>&gt;.

   [<a id="ref-ICCPR">ICCPR</a>]    United Nations General Assembly, "International Covenant
              on Civil and Political Rights", 1966,
              &lt;<a href="http://www.ohchr.org/EN/ProfessionalInterest/Pages/CCPR.aspx">http://www.ohchr.org/EN/ProfessionalInterest/Pages/</a>
              <a href="http://www.ohchr.org/EN/ProfessionalInterest/Pages/CCPR.aspx">CCPR.aspx</a>&gt;.

   [<a id="ref-ICESCR">ICESCR</a>]   United Nations General Assembly, "International Covenant
              on Economic, Social and Cultural Rights", 1966,
              &lt;<a href="http://www.ohchr.org/EN/ProfessionalInterest/Pages/CESCR.aspx">http://www.ohchr.org/EN/ProfessionalInterest/Pages/</a>
              <a href="http://www.ohchr.org/EN/ProfessionalInterest/Pages/CESCR.aspx">CESCR.aspx</a>&gt;.

   [<a id="ref-Insinuator">Insinuator</a>]
              Schiess, N., "Vulnerabilities &amp; attack vectors of VPNs
              (Pt 1)", August 2013, &lt;<a href="https://www.insinuator.net/2013/08/vulnerabilities-attack-vectors-of-vpns-pt-1/">https://www.insinuator.net/2013/08/</a>
              <a href="https://www.insinuator.net/2013/08/vulnerabilities-attack-vectors-of-vpns-pt-1/">vulnerabilities-attack-vectors-of-vpns-pt-1/</a>&gt;.

   [<a id="ref-IRP">IRP</a>]      Internet Rights and Principles Dynamic Coalition,
              "10 Internet Rights &amp; Principles", 2017,
              &lt;<a href="http://internetrightsandprinciples.org/site/campaign/">http://internetrightsandprinciples.org/site/campaign/</a>&gt;.

   [<a id="ref-Jabri">Jabri</a>]    Jabri, V., "Discourses on violence: conflict analysis
              reconsidered", Manchester University Press, 1996.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 68]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-Kaye">Kaye</a>]     Kaye, D., "Freedom of expression and the private sector in
              the digital age", 2016, &lt;<a href="http://www.ohchr.org/EN/Issues/FreedomOpinion/Pages/Privatesectorinthedigitalage.aspx">http://www.ohchr.org/EN/Issues/</a>
              <a href="http://www.ohchr.org/EN/Issues/FreedomOpinion/Pages/Privatesectorinthedigitalage.aspx">FreedomOpinion/Pages/Privatesectorinthedigitalage.aspx</a>&gt;.

   [<a id="ref-King">King</a>]     King, C., "Power, Social Violence and Civil Wars",
              Chapter 8 of "Leashing the Dogs of War: Conflict
              Management in a Divided World", United States Institute of
              Peace Press, Washington, D.C., 2007.

   [<a id="ref-Lessig">Lessig</a>]   Lessig, L., "Code and Other Laws of Cyberspace,
              Version 2.0 ('Codev2')", Basic Books, New York, 2006,
              &lt;<a href="http://codev2.cc/">http://codev2.cc/</a>&gt;.

   [<a id="ref-Marcak">Marcak</a>]   Marcak, B., Weaver, N., Dalek, J., Ensafi, R., Fifield,
              D., McKune, S., Rey, A., Scott-Railton, J., Deibert, R.,
              and V. Paxson, "China's Great Cannon", April 2015,
              &lt;<a href="https://citizenlab.org/2015/04/chinas-great-cannon/">https://citizenlab.org/2015/04/chinas-great-cannon/</a>&gt;.

   [<a id="ref-Marquis-Boire">Marquis-Boire</a>]
              Marquis-Boire, M., "Schrodinger's Cat Video and the Death
              of Clear-Text", August 2014, &lt;<a href="https://citizenlab.org/2014/08/cat-video-and-the-death-of-clear-text/">https://citizenlab.org/</a>
              <a href="https://citizenlab.org/2014/08/cat-video-and-the-death-of-clear-text/">2014/08/cat-video-and-the-death-of-clear-text/</a>&gt;.

   [<a id="ref-Meyer">Meyer</a>]    Meyer, J., "Defining and Evaluating Resilience: A
              Performability Perspective", presentation at International
              Workshop on Performability Modeling of Computer and
              Communication Systems, September 2009.

   [<a id="ref-Mueller">Mueller</a>]  Mueller, M., "Networks and States: The Global Politics of
              Internet Governance", MIT Press,
              DOI 10.7551/mitpress/9780262014595.001.0001, 2010,
              &lt;<a href="https://mitpress.mit.edu/books/networks-and-states">https://mitpress.mit.edu/books/networks-and-states</a>&gt;.

   [<a id="ref-Musiani">Musiani</a>]  Musiani, F., "Giants, Dwarfs and Decentralized
              Alternatives to Internet-based Services: An Issue of
              Internet Governance", Westminster Papers in Communication
              and Culture, 10(1), pp. 81-94, DOI 10.16997/wpcc.214,
              2015, &lt;<a href="https://www.westminsterpapers.org/articles/10.16997/wpcc.214/">https://www.westminsterpapers.org/</a>
              <a href="https://www.westminsterpapers.org/articles/10.16997/wpcc.214/">articles/10.16997/wpcc.214/</a>&gt;.

   [<a id="ref-Namecoin">Namecoin</a>] Namecoin, "Namecoin", 2015, &lt;<a href="https://namecoin.info/">https://namecoin.info/</a>&gt;.










<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 69]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-NATusage">NATusage</a>] Maier, G., Schneider, F., and A. Feldmann, "NAT usage in
              Residential Broadband networks", PAM: International
              Conference on Passive and Active Network
              Measurement Lecture Notes in Computer Science,
              Volume 6579, Springer, Berlin and Heidelberg,
              DOI 10.1007/978-3-642-19260-9_4, 2011,
              &lt;<a href="http://www.icsi.berkeley.edu/pubs/networking/NATusage11.pdf">http://www.icsi.berkeley.edu/pubs/networking/</a>
              <a href="http://www.icsi.berkeley.edu/pubs/networking/NATusage11.pdf">NATusage11.pdf</a>&gt;.

   [<a id="ref-NETmundial">NETmundial</a>]
              NETmundial, "NETmundial Multistakeholder Statement",
              April 2014, &lt;<a href="http://netmundial.br/wp-content/uploads/2014/04/NETmundial-Multistakeholder-Document.pdf">http://netmundial.br/wp-content/</a>
              <a href="http://netmundial.br/wp-content/uploads/2014/04/NETmundial-Multistakeholder-Document.pdf">uploads/2014/04/NETmundial-Multistakeholder-Document.pdf</a>&gt;.

   [<a id="ref-Newegg">Newegg</a>]   Mullin, J., "Newegg on trial: Mystery company TQP rewrites
              the history of encryption", November 2013,
              &lt;<a href="http://arstechnica.com/tech-policy/2013/11/newegg-on-trial-mystery-company-tqp-re-writes-the-history-of-encryption/">http://arstechnica.com/tech-policy/2013/11/newegg-on-</a>
              <a href="http://arstechnica.com/tech-policy/2013/11/newegg-on-trial-mystery-company-tqp-re-writes-the-history-of-encryption/">trial-mystery-company-tqp-re-writes-the-history-of-</a>
              <a href="http://arstechnica.com/tech-policy/2013/11/newegg-on-trial-mystery-company-tqp-re-writes-the-history-of-encryption/">encryption/</a>&gt;.

   [<a id="ref-notewell">notewell</a>] IETF, "Note Well", 2015,
              &lt;<a href="https://www.ietf.org/about/note-well.html">https://www.ietf.org/about/note-well.html</a>&gt;.

   [<a id="ref-patentpolicy">patentpolicy</a>]
              Weitzner, D., Ed., "W3C Patent Policy", World Wide
              Web Consortium, February 2004,
              &lt;<a href="https://www.w3.org/Consortium/Patent-Policy-20040205/">https://www.w3.org/Consortium/Patent-Policy-20040205/</a>&gt;.

   [<a id="ref-Penney">Penney</a>]   Penney, J., "Chilling Effects: Online Surveillance and
              Wikipedia Use", 2016, &lt;<a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2769645">http://papers.ssrn.com/sol3/</a>
              <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2769645">papers.cfm?abstract_id=2769645</a>&gt;.

   [<a id="ref-Peterson">Peterson</a>] Peterson, A., Gellman, B., and A. Soltani, "Yahoo to make
              SSL encryption the default for Webmail users.  Finally.",
              October 2013, &lt;<a href="https://www.washingtonpost.com/">https://www.washingtonpost.com/</a>
              news/the-switch/wp/2013/10/14/
              yahoo-to-make-ssl-encryption-the-default-
              for-webmail-users-finally/?utm_term=.a17eca45ddfe&gt;.

   [<a id="ref-PETS2015VPN">PETS2015VPN</a>]
              Perta, V., Barbera, M., Tyson, G., Haddadi, H., and A.
              Mei, "A Glance through the VPN Looking Glass: IPv6 Leakage
              and DNS Hijacking in Commercial VPN clients",
              DOI 10.1515/popets-2015-0006, 2015,
              &lt;<a href="http://www.eecs.qmul.ac.uk/~hamed/papers/PETS2015VPN.pdf">http://www.eecs.qmul.ac.uk/~hamed/papers/</a>
              <a href="http://www.eecs.qmul.ac.uk/~hamed/papers/PETS2015VPN.pdf">PETS2015VPN.pdf</a>&gt;.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 70]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-Pidgin">Pidgin</a>]   js and Pidgin Developers, "[XMPP] Invisible mode violating
              standard", 2007,
              &lt;<a href="https://developer.pidgin.im/ticket/4322">https://developer.pidgin.im/ticket/4322</a>&gt;.

   [<a id="ref-Pouwelse">Pouwelse</a>] Pouwelse, J., Ed., "Media without censorship (CensorFree)
              scenarios", Work in Progress, <a href="./draft-pouwelse-censorfree-scenarios-02">draft-pouwelse-censorfree-</a>
              <a href="./draft-pouwelse-censorfree-scenarios-02">scenarios-02</a>, October 2012.

   [<a id="ref-Rachovitsa">Rachovitsa</a>]
              Rachovitsa, A., "Engineering and lawyering privacy by
              design: understanding online privacy both as a technical
              and an international human rights issue", International
              Journal of Law and Information Technology, Volume 24,
              Issue 4, pp. 374-399, DOI 10.1093/ijlit/eaw012,
              December 2016, &lt;<a href="https://academic.oup.com/ijlit/article/24/4/374/2566975/Engineering-and-lawyering-privacy-by-design">https://academic.oup.com/ijlit/</a>
              <a href="https://academic.oup.com/ijlit/article/24/4/374/2566975/Engineering-and-lawyering-privacy-by-design">article/24/4/374/2566975/</a>
              <a href="https://academic.oup.com/ijlit/article/24/4/374/2566975/Engineering-and-lawyering-privacy-by-design">Engineering-and-lawyering-privacy-by-design</a>&gt;.

   [<a id="ref-RFC760">RFC760</a>]   Postel, J., "DoD standard Internet Protocol", <a href="./rfc760">RFC 760</a>,
              DOI 10.17487/RFC0760, January 1980,
              &lt;<a href="https://www.rfc-editor.org/info/rfc760">https://www.rfc-editor.org/info/rfc760</a>&gt;.

   [<a id="ref-RFC791">RFC791</a>]   Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>,
              DOI 10.17487/RFC0791, September 1981,
              &lt;<a href="https://www.rfc-editor.org/info/rfc791">https://www.rfc-editor.org/info/rfc791</a>&gt;.

   [<a id="ref-RFC793">RFC793</a>]   Postel, J., "Transmission Control Protocol", STD 7,
              <a href="./rfc793">RFC 793</a>, DOI 10.17487/RFC0793, September 1981,
              &lt;<a href="https://www.rfc-editor.org/info/rfc793">https://www.rfc-editor.org/info/rfc793</a>&gt;.

   [<a id="ref-RFC894">RFC894</a>]   Hornig, C., "A Standard for the Transmission of IP
              Datagrams over Ethernet Networks", STD 41, <a href="./rfc894">RFC 894</a>,
              DOI 10.17487/RFC0894, April 1984,
              &lt;<a href="https://www.rfc-editor.org/info/rfc894">https://www.rfc-editor.org/info/rfc894</a>&gt;.

   [<a id="ref-RFC1035">RFC1035</a>]  Mockapetris, P., "Domain names - implementation and
              specification", STD 13, <a href="./rfc1035">RFC 1035</a>, DOI 10.17487/RFC1035,
              November 1987, &lt;<a href="https://www.rfc-editor.org/info/rfc1035">https://www.rfc-editor.org/info/rfc1035</a>&gt;.

   [<a id="ref-RFC1122">RFC1122</a>]  Braden, R., Ed., "Requirements for Internet Hosts -
              Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>,
              DOI 10.17487/RFC1122, October 1989,
              &lt;<a href="https://www.rfc-editor.org/info/rfc1122">https://www.rfc-editor.org/info/rfc1122</a>&gt;.

   [<a id="ref-RFC1958">RFC1958</a>]  Carpenter, B., Ed., "Architectural Principles of the
              Internet", <a href="./rfc1958">RFC 1958</a>, DOI 10.17487/RFC1958, June 1996,
              &lt;<a href="https://www.rfc-editor.org/info/rfc1958">https://www.rfc-editor.org/info/rfc1958</a>&gt;.




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 71]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-RFC1984">RFC1984</a>]  IAB and IESG, "IAB and IESG Statement on Cryptographic
              Technology and the Internet", <a href="https://www.rfc-editor.org/bcp/bcp200">BCP 200</a>, <a href="./rfc1984">RFC 1984</a>,
              DOI 10.17487/RFC1984, August 1996,
              &lt;<a href="https://www.rfc-editor.org/info/rfc1984">https://www.rfc-editor.org/info/rfc1984</a>&gt;.

   [<a id="ref-RFC2026">RFC2026</a>]  Bradner, S., "The Internet Standards Process --
              Revision 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, DOI 10.17487/RFC2026,
              October 1996, &lt;<a href="https://www.rfc-editor.org/info/rfc2026">https://www.rfc-editor.org/info/rfc2026</a>&gt;.

   [<a id="ref-RFC2277">RFC2277</a>]  Alvestrand, H., "IETF Policy on Character Sets and
              Languages", <a href="https://www.rfc-editor.org/bcp/bcp18">BCP 18</a>, <a href="./rfc2277">RFC 2277</a>, DOI 10.17487/RFC2277,
              January 1998, &lt;<a href="https://www.rfc-editor.org/info/rfc2277">https://www.rfc-editor.org/info/rfc2277</a>&gt;.

   [<a id="ref-RFC2775">RFC2775</a>]  Carpenter, B., "Internet Transparency", <a href="./rfc2775">RFC 2775</a>,
              DOI 10.17487/RFC2775, February 2000,
              &lt;<a href="https://www.rfc-editor.org/info/rfc2775">https://www.rfc-editor.org/info/rfc2775</a>&gt;.

   [<a id="ref-RFC3022">RFC3022</a>]  Srisuresh, P. and K. Egevang, "Traditional IP Network
              Address Translator (Traditional NAT)", <a href="./rfc3022">RFC 3022</a>,
              DOI 10.17487/RFC3022, January 2001,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3022">https://www.rfc-editor.org/info/rfc3022</a>&gt;.

   [<a id="ref-RFC3365">RFC3365</a>]  Schiller, J., "Strong Security Requirements for Internet
              Engineering Task Force Standard Protocols", <a href="https://www.rfc-editor.org/bcp/bcp61">BCP 61</a>,
              <a href="./rfc3365">RFC 3365</a>, DOI 10.17487/RFC3365, August 2002,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3365">https://www.rfc-editor.org/info/rfc3365</a>&gt;.

   [<a id="ref-RFC3439">RFC3439</a>]  Bush, R. and D. Meyer, "Some Internet Architectural
              Guidelines and Philosophy", <a href="./rfc3439">RFC 3439</a>,
              DOI 10.17487/RFC3439, December 2002,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3439">https://www.rfc-editor.org/info/rfc3439</a>&gt;.

   [<a id="ref-RFC3536">RFC3536</a>]  Hoffman, P., "Terminology Used in Internationalization in
              the IETF", <a href="./rfc3536">RFC 3536</a>, DOI 10.17487/RFC3536, May 2003,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3536">https://www.rfc-editor.org/info/rfc3536</a>&gt;.

   [<a id="ref-RFC3724">RFC3724</a>]  Kempf, J., Ed., Austein, R., Ed., and IAB, "The Rise of
              the Middle and the Future of End-to-End: Reflections on
              the Evolution of the Internet Architecture", <a href="./rfc3724">RFC 3724</a>,
              DOI 10.17487/RFC3724, March 2004,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3724">https://www.rfc-editor.org/info/rfc3724</a>&gt;.

   [<a id="ref-RFC3935">RFC3935</a>]  Alvestrand, H., "A Mission Statement for the IETF",
              <a href="https://www.rfc-editor.org/bcp/bcp95">BCP 95</a>, <a href="./rfc3935">RFC 3935</a>, DOI 10.17487/RFC3935, October 2004,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3935">https://www.rfc-editor.org/info/rfc3935</a>&gt;.






<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 72]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-RFC4033">RFC4033</a>]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "DNS Security Introduction and Requirements",
              <a href="./rfc4033">RFC 4033</a>, DOI 10.17487/RFC4033, March 2005,
              &lt;<a href="https://www.rfc-editor.org/info/rfc4033">https://www.rfc-editor.org/info/rfc4033</a>&gt;.

   [<a id="ref-RFC4084">RFC4084</a>]  Klensin, J., "Terminology for Describing Internet
              Connectivity", <a href="https://www.rfc-editor.org/bcp/bcp104">BCP 104</a>, <a href="./rfc4084">RFC 4084</a>, DOI 10.17487/RFC4084,
              May 2005, &lt;<a href="https://www.rfc-editor.org/info/rfc4084">https://www.rfc-editor.org/info/rfc4084</a>&gt;.

   [<a id="ref-RFC4101">RFC4101</a>]  Rescorla, E. and IAB, "Writing Protocol Models", <a href="./rfc4101">RFC 4101</a>,
              DOI 10.17487/RFC4101, June 2005,
              &lt;<a href="https://www.rfc-editor.org/info/rfc4101">https://www.rfc-editor.org/info/rfc4101</a>&gt;.

   [<a id="ref-RFC4941">RFC4941</a>]  Narten, T., Draves, R., and S. Krishnan, "Privacy
              Extensions for Stateless Address Autoconfiguration in
              IPv6", <a href="./rfc4941">RFC 4941</a>, DOI 10.17487/RFC4941, September 2007,
              &lt;<a href="https://www.rfc-editor.org/info/rfc4941">https://www.rfc-editor.org/info/rfc4941</a>&gt;.

   [<a id="ref-RFC4949">RFC4949</a>]  Shirey, R., "Internet Security Glossary, Version 2",
              FYI 36, <a href="./rfc4949">RFC 4949</a>, DOI 10.17487/RFC4949, August 2007,
              &lt;<a href="https://www.rfc-editor.org/info/rfc4949">https://www.rfc-editor.org/info/rfc4949</a>&gt;.

   [<a id="ref-RFC5246">RFC5246</a>]  Dierks, T. and E. Rescorla, "The Transport Layer Security
              (TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>,
              DOI 10.17487/RFC5246, August 2008,
              &lt;<a href="https://www.rfc-editor.org/info/rfc5246">https://www.rfc-editor.org/info/rfc5246</a>&gt;.

   [<a id="ref-RFC5321">RFC5321</a>]  Klensin, J., "Simple Mail Transfer Protocol", <a href="./rfc5321">RFC 5321</a>,
              DOI 10.17487/RFC5321, October 2008,
              &lt;<a href="https://www.rfc-editor.org/info/rfc5321">https://www.rfc-editor.org/info/rfc5321</a>&gt;.

   [<a id="ref-RFC5646">RFC5646</a>]  Phillips, A., Ed., and M. Davis, Ed., "Tags for
              Identifying Languages", <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="./rfc5646">RFC 5646</a>,
              DOI 10.17487/RFC5646, September 2009,
              &lt;<a href="https://www.rfc-editor.org/info/rfc5646">https://www.rfc-editor.org/info/rfc5646</a>&gt;.

   [<a id="ref-RFC5694">RFC5694</a>]  Camarillo, G., Ed., and IAB, "Peer-to-Peer (P2P)
              Architecture: Definition, Taxonomies, Examples, and
              Applicability", <a href="./rfc5694">RFC 5694</a>, DOI 10.17487/RFC5694,
              November 2009, &lt;<a href="https://www.rfc-editor.org/info/rfc5694">https://www.rfc-editor.org/info/rfc5694</a>&gt;.

   [<a id="ref-RFC5944">RFC5944</a>]  Perkins, C., Ed., "IP Mobility Support for IPv4, Revised",
              <a href="./rfc5944">RFC 5944</a>, DOI 10.17487/RFC5944, November 2010,
              &lt;<a href="https://www.rfc-editor.org/info/rfc5944">https://www.rfc-editor.org/info/rfc5944</a>&gt;.







<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 73]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-RFC6101">RFC6101</a>]  Freier, A., Karlton, P., and P. Kocher, "The Secure
              Sockets Layer (SSL) Protocol Version 3.0", <a href="./rfc6101">RFC 6101</a>,
              DOI 10.17487/RFC6101, August 2011,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6101">https://www.rfc-editor.org/info/rfc6101</a>&gt;.

   [<a id="ref-RFC6108">RFC6108</a>]  Chung, C., Kasyanov, A., Livingood, J., Mody, N., and B.
              Van Lieu, "Comcast's Web Notification System Design",
              <a href="./rfc6108">RFC 6108</a>, DOI 10.17487/RFC6108, February 2011,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6108">https://www.rfc-editor.org/info/rfc6108</a>&gt;.

   [<a id="ref-RFC6120">RFC6120</a>]  Saint-Andre, P., "Extensible Messaging and Presence
              Protocol (XMPP): Core", <a href="./rfc6120">RFC 6120</a>, DOI 10.17487/RFC6120,
              March 2011, &lt;<a href="https://www.rfc-editor.org/info/rfc6120">https://www.rfc-editor.org/info/rfc6120</a>&gt;.

   [<a id="ref-RFC6365">RFC6365</a>]  Hoffman, P. and J. Klensin, "Terminology Used in
              Internationalization in the IETF", <a href="https://www.rfc-editor.org/bcp/bcp166">BCP 166</a>, <a href="./rfc6365">RFC 6365</a>,
              DOI 10.17487/RFC6365, September 2011,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6365">https://www.rfc-editor.org/info/rfc6365</a>&gt;.

   [<a id="ref-RFC6698">RFC6698</a>]  Hoffman, P. and J. Schlyter, "The DNS-Based Authentication
              of Named Entities (DANE) Transport Layer Security (TLS)
              Protocol: TLSA", <a href="./rfc6698">RFC 6698</a>, DOI 10.17487/RFC6698,
              August 2012, &lt;<a href="https://www.rfc-editor.org/info/rfc6698">https://www.rfc-editor.org/info/rfc6698</a>&gt;.

   [<a id="ref-RFC6701">RFC6701</a>]  Farrel, A. and P. Resnick, "Sanctions Available for
              Application to Violators of IETF IPR Policy", <a href="./rfc6701">RFC 6701</a>,
              DOI 10.17487/RFC6701, August 2012,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6701">https://www.rfc-editor.org/info/rfc6701</a>&gt;.

   [<a id="ref-RFC6797">RFC6797</a>]  Hodges, J., Jackson, C., and A. Barth, "HTTP Strict
              Transport Security (HSTS)", <a href="./rfc6797">RFC 6797</a>,
              DOI 10.17487/RFC6797, November 2012,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6797">https://www.rfc-editor.org/info/rfc6797</a>&gt;.

   [<a id="ref-RFC6973">RFC6973</a>]  Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
              Morris, J., Hansen, M., and R. Smith, "Privacy
              Considerations for Internet Protocols", <a href="./rfc6973">RFC 6973</a>,
              DOI 10.17487/RFC6973, July 2013,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6973">https://www.rfc-editor.org/info/rfc6973</a>&gt;.

   [<a id="ref-RFC7230">RFC7230</a>]  Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
              Transfer Protocol (HTTP/1.1): Message Syntax and Routing",
              <a href="./rfc7230">RFC 7230</a>, DOI 10.17487/RFC7230, June 2014,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7230">https://www.rfc-editor.org/info/rfc7230</a>&gt;.







<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 74]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-RFC7231">RFC7231</a>]  Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
              Transfer Protocol (HTTP/1.1): Semantics and Content",
              <a href="./rfc7231">RFC 7231</a>, DOI 10.17487/RFC7231, June 2014,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7231">https://www.rfc-editor.org/info/rfc7231</a>&gt;.

   [<a id="ref-RFC7232">RFC7232</a>]  Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
              Transfer Protocol (HTTP/1.1): Conditional Requests",
              <a href="./rfc7232">RFC 7232</a>, DOI 10.17487/RFC7232, June 2014,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7232">https://www.rfc-editor.org/info/rfc7232</a>&gt;.

   [<a id="ref-RFC7233">RFC7233</a>]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
              <a href="./rfc7233">RFC 7233</a>, DOI 10.17487/RFC7233, June 2014,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7233">https://www.rfc-editor.org/info/rfc7233</a>&gt;.

   [<a id="ref-RFC7234">RFC7234</a>]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
              <a href="./rfc7234">RFC 7234</a>, DOI 10.17487/RFC7234, June 2014,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7234">https://www.rfc-editor.org/info/rfc7234</a>&gt;.

   [<a id="ref-RFC7235">RFC7235</a>]  Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
              Transfer Protocol (HTTP/1.1): Authentication", <a href="./rfc7235">RFC 7235</a>,
              DOI 10.17487/RFC7235, June 2014,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7235">https://www.rfc-editor.org/info/rfc7235</a>&gt;.

   [<a id="ref-RFC7236">RFC7236</a>]  Reschke, J., "Initial Hypertext Transfer Protocol (HTTP)
              Authentication Scheme Registrations", <a href="./rfc7236">RFC 7236</a>,
              DOI 10.17487/RFC7236, June 2014,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7236">https://www.rfc-editor.org/info/rfc7236</a>&gt;.

   [<a id="ref-RFC7237">RFC7237</a>]  Reschke, J., "Initial Hypertext Transfer Protocol (HTTP)
              Method Registrations", <a href="./rfc7237">RFC 7237</a>, DOI 10.17487/RFC7237,
              June 2014, &lt;<a href="https://www.rfc-editor.org/info/rfc7237">https://www.rfc-editor.org/info/rfc7237</a>&gt;.

   [<a id="ref-RFC7258">RFC7258</a>]  Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
              Attack", <a href="https://www.rfc-editor.org/bcp/bcp188">BCP 188</a>, <a href="./rfc7258">RFC 7258</a>, DOI 10.17487/RFC7258,
              May 2014, &lt;<a href="https://www.rfc-editor.org/info/rfc7258">https://www.rfc-editor.org/info/rfc7258</a>&gt;.

   [<a id="ref-RFC7469">RFC7469</a>]  Evans, C., Palmer, C., and R. Sleevi, "Public Key Pinning
              Extension for HTTP", <a href="./rfc7469">RFC 7469</a>, DOI 10.17487/RFC7469,
              April 2015, &lt;<a href="https://www.rfc-editor.org/info/rfc7469">https://www.rfc-editor.org/info/rfc7469</a>&gt;.

   [<a id="ref-RFC7540">RFC7540</a>]  Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext
              Transfer Protocol Version 2 (HTTP/2)", <a href="./rfc7540">RFC 7540</a>,
              DOI 10.17487/RFC7540, May 2015,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7540">https://www.rfc-editor.org/info/rfc7540</a>&gt;.





<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 75]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-RFC7574">RFC7574</a>]  Bakker, A., Petrocco, R., and V. Grishchenko, "Peer-to-
              Peer Streaming Peer Protocol (PPSPP)", <a href="./rfc7574">RFC 7574</a>,
              DOI 10.17487/RFC7574, July 2015,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7574">https://www.rfc-editor.org/info/rfc7574</a>&gt;.

   [<a id="ref-RFC7624">RFC7624</a>]  Barnes, R., Schneier, B., Jennings, C., Hardie, T.,
              Trammell, B., Huitema, C., and D. Borkmann,
              "Confidentiality in the Face of Pervasive Surveillance: A
              Threat Model and Problem Statement", <a href="./rfc7624">RFC 7624</a>,
              DOI 10.17487/RFC7624, August 2015,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7624">https://www.rfc-editor.org/info/rfc7624</a>&gt;.

   [<a id="ref-RFC7626">RFC7626</a>]  Bortzmeyer, S., "DNS Privacy Considerations", <a href="./rfc7626">RFC 7626</a>,
              DOI 10.17487/RFC7626, August 2015,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7626">https://www.rfc-editor.org/info/rfc7626</a>&gt;.

   [<a id="ref-RFC7725">RFC7725</a>]  Bray, T., "An HTTP Status Code to Report Legal Obstacles",
              <a href="./rfc7725">RFC 7725</a>, DOI 10.17487/RFC7725, February 2016,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7725">https://www.rfc-editor.org/info/rfc7725</a>&gt;.

   [<a id="ref-RFC7754">RFC7754</a>]  Barnes, R., Cooper, A., Kolkman, O., Thaler, D., and E.
              Nordmark, "Technical Considerations for Internet Service
              Blocking and Filtering", <a href="./rfc7754">RFC 7754</a>, DOI 10.17487/RFC7754,
              March 2016, &lt;<a href="https://www.rfc-editor.org/info/rfc7754">https://www.rfc-editor.org/info/rfc7754</a>&gt;.

   [<a id="ref-RFC7858">RFC7858</a>]  Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D.,
              and P. Hoffman, "Specification for DNS over Transport
              Layer Security (TLS)", <a href="./rfc7858">RFC 7858</a>, DOI 10.17487/RFC7858,
              May 2016, &lt;<a href="https://www.rfc-editor.org/info/rfc7858">https://www.rfc-editor.org/info/rfc7858</a>&gt;.

   [<a id="ref-RFC8164">RFC8164</a>]  Nottingham, M. and M. Thomson, "Opportunistic Security for
              HTTP/2", <a href="./rfc8164">RFC 8164</a>, DOI 10.17487/RFC8164, May 2017,
              &lt;<a href="https://www.rfc-editor.org/info/rfc8164">https://www.rfc-editor.org/info/rfc8164</a>&gt;.

   [<a id="ref-RFC8179">RFC8179</a>]  Bradner, S. and J. Contreras, "Intellectual Property
              Rights in IETF Technology", <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>, <a href="./rfc8179">RFC 8179</a>,
              DOI 10.17487/RFC8179, May 2017,
              &lt;<a href="https://www.rfc-editor.org/info/rfc8179">https://www.rfc-editor.org/info/rfc8179</a>&gt;.

   [<a id="ref-RFC8200">RFC8200</a>]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", STD 86, <a href="./rfc8200">RFC 8200</a>,
              DOI 10.17487/RFC8200, July 2017,
              &lt;<a href="https://www.rfc-editor.org/info/rfc8200">https://www.rfc-editor.org/info/rfc8200</a>&gt;.

   [<a id="ref-Rideout">Rideout</a>]  Rideout, A., "Making security easier", July 2008,
              &lt;<a href="http://gmailblog.blogspot.de/2008/07/making-security-easier.html">http://gmailblog.blogspot.de/2008/07/</a>
              <a href="http://gmailblog.blogspot.de/2008/07/making-security-easier.html">making-security-easier.html</a>&gt;.




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 76]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-Ritchie">Ritchie</a>]  Ritchie, J. and J. Lewis, "Qualitative Research Practice:
              A Guide for Social Science Students and Researchers", SAGE
              Publishing, London, 2003, &lt;<a href="http://www.amazon.co.uk/Qualitative-Research-Practice-Students-Researchers/dp/0761971106">http://www.amazon.co.uk/</a>
              <a href="http://www.amazon.co.uk/Qualitative-Research-Practice-Students-Researchers/dp/0761971106">Qualitative-Research-Practice-Students-Researchers/</a>
              <a href="http://www.amazon.co.uk/Qualitative-Research-Practice-Students-Researchers/dp/0761971106">dp/0761971106</a>&gt;.

   [<a id="ref-RSF">RSF</a>]      Reporters Without Borders (RSF), "Syria using 34 Blue Coat
              servers to spy on Internet users", January 2016,
              &lt;<a href="https://rsf.org/en/news/syria-using-34-blue-coat-servers-spy-internet-users">https://rsf.org/en/news/</a>
              <a href="https://rsf.org/en/news/syria-using-34-blue-coat-servers-spy-internet-users">syria-using-34-blue-coat-servers-spy-internet-users</a>&gt;.

   [<a id="ref-Saltzer">Saltzer</a>]  Saltzer, J., Reed, D., and D. Clark, "End-to-End Arguments
              in System Design", ACM Transactions on Computer Systems
              (TOCS), Volume 2, Number 4, pp. 277-288,
              DOI 10.1145/357401.357402, November 1984.

   [<a id="ref-Sandvine">Sandvine</a>] Sandvine, "Sandvine: Over 70% Of North American Traffic Is
              Now Streaming Video And Audio", December 2015,
              &lt;<a href="https://www.sandvine.com/pr/2015/12/7/sandvine-over-70-of-north-american-traffic-is-now-streaming-video-and-audio.html">https://www.sandvine.com/pr/2015/12/7/sandvine-over-70-</a>
              <a href="https://www.sandvine.com/pr/2015/12/7/sandvine-over-70-of-north-american-traffic-is-now-streaming-video-and-audio.html">of-north-american-traffic-is-now-streaming-video-and-</a>
              <a href="https://www.sandvine.com/pr/2015/12/7/sandvine-over-70-of-north-american-traffic-is-now-streaming-video-and-audio.html">audio.html</a>&gt;.

   [<a id="ref-Schillace">Schillace</a>] Schillace, S., "Default https access for Gmail",
              January 2010, &lt;<a href="http://gmailblog.blogspot.de/2010/01/default-https-access-for-gmail.html">http://gmailblog.blogspot.de/2010/01/</a>
              <a href="http://gmailblog.blogspot.de/2010/01/default-https-access-for-gmail.html">default-https-access-for-gmail.html</a>&gt;.

   [<a id="ref-Schneier">Schneier</a>] Schneier, B., "Attacking Tor: how the NSA targets users'
              online anonymity", October 2013,
              &lt;<a href="http://www.theguardian.com/world/2013/oct/04/tor-attacks-nsa-users-online-anonymity">http://www.theguardian.com/world/2013/oct/04/</a>
              <a href="http://www.theguardian.com/world/2013/oct/04/tor-attacks-nsa-users-online-anonymity">tor-attacks-nsa-users-online-anonymity</a>&gt;.

   [<a id="ref-SPIEGEL">SPIEGEL</a>]  SPIEGEL, "Prying Eyes - Inside the NSA's War on Internet
              Security", December 2014,
              &lt;<a href="http://www.spiegel.de/international/germany/inside-the-nsa-s-war-on-internet-security-a-1010361.html">http://www.spiegel.de/international/germany/</a>
              <a href="http://www.spiegel.de/international/germany/inside-the-nsa-s-war-on-internet-security-a-1010361.html">inside-the-nsa-s-war-on-internet-security-a-1010361.html</a>&gt;.

   [<a id="ref-sslstrip">sslstrip</a>] Marlinspike, M., "Software &gt;&gt; sslstrip", 2011,
              &lt;<a href="https://moxie.org/software/sslstrip/">https://moxie.org/software/sslstrip/</a>&gt;.

   [<a id="ref-techyum">techyum</a>]  Violet, "Official - vb.ly Link Shortener Seized by Libyan
              Government", October 2010, &lt;<a href="http://techyum.com/2010/10/official-vb-ly-link-shortener-seized-by-libyan-government/">http://techyum.com/2010/10/</a>
              <a href="http://techyum.com/2010/10/official-vb-ly-link-shortener-seized-by-libyan-government/">official-vb-ly-link-shortener-seized-by-libyan-</a>
              <a href="http://techyum.com/2010/10/official-vb-ly-link-shortener-seized-by-libyan-government/">government/</a>&gt;.

   [<a id="ref-TorProject">TorProject</a>]
              The Tor Project, "Anonymity Online", 2006,
              &lt;<a href="https://www.torproject.org/">https://www.torproject.org/</a>&gt;.




<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 77]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-torrentfreak1">torrentfreak1</a>]
              Van der Sar, E., "Is Your ISP Messing With BitTorrent
              Traffic?  Find Out", January 2014,
              &lt;<a href="https://torrentfreak.com/is-your-isp-messing-with-bittorrent-traffic-find-out-140123/">https://torrentfreak.com/is-your-isp-messing-with-</a>
              <a href="https://torrentfreak.com/is-your-isp-messing-with-bittorrent-traffic-find-out-140123/">bittorrent-traffic-find-out-140123/</a>&gt;.

   [<a id="ref-torrentfreak2">torrentfreak2</a>]
              Andy, "Lawyers Sent 109,000 Piracy Threats in Germany
              During 2013", March 2014, &lt;<a href="https://torrentfreak.com/lawyers-sent-109000-piracy-threats-in-germany-during-2013-140304/">https://torrentfreak.com/</a>
              <a href="https://torrentfreak.com/lawyers-sent-109000-piracy-threats-in-germany-during-2013-140304/">lawyers-sent-109000-piracy-threats-in-germany-during-</a>
              <a href="https://torrentfreak.com/lawyers-sent-109000-piracy-threats-in-germany-during-2013-140304/">2013-140304/</a>&gt;.

   [<a id="ref-Tribler">Tribler</a>]  Delft University of Technology, Department EWI/PDS/
              Tribler, "About Tribler", 2013,
              &lt;<a href="https://www.tribler.org/about.html">https://www.tribler.org/about.html</a>&gt;.

   [<a id="ref-UDHR">UDHR</a>]     United Nations General Assembly, "The Universal
              Declaration of Human Rights", 1948, &lt;<a href="http://www.un.org/en/universal-declaration-human-rights/index.html">http://www.un.org/en/</a>
              <a href="http://www.un.org/en/universal-declaration-human-rights/index.html">universal-declaration-human-rights/index.html</a>&gt;.

   [<a id="ref-UNGA2013">UNGA2013</a>] United Nations General Assembly, "UN General Assembly
              Resolution "The right to privacy in the digital age"
              (A/C.3/68/L.45)", 2013,
              &lt;<a href="https://documents-dds-ny.un.org/doc/UNDOC/LTD/N13/576/77/PDF/N1357677.pdf?OpenElement">https://documents-dds-ny.un.org/doc/UNDOC/LTD/N13/</a>
              <a href="https://documents-dds-ny.un.org/doc/UNDOC/LTD/N13/576/77/PDF/N1357677.pdf?OpenElement">576/77/PDF/N1357677.pdf?OpenElement</a>&gt;.

   [<a id="ref-UNHRC2016">UNHRC2016</a>]
              United Nations Human Rights Council, "The promotion,
              protection and enjoyment of human rights on the Internet",
              Resolution A/HRC/32/L.20, 2016,
              &lt;<a href="http://ap.ohchr.org/documents/alldocs.aspx?doc_id=20340">http://ap.ohchr.org/documents/alldocs.aspx?doc_id=20340</a>&gt;.

   [<a id="ref-Ververis">Ververis</a>] Ververis, V., Kargiotakis, G., Filasto, A., Fabian, B.,
              and A. Alexandros, "Understanding Internet Censorship
              Policy: The Case of Greece", 5th USENIX Workshop on Free
              and Open Communications on the Internet (FOCI) '15,
              August 2015, &lt;<a href="https://www.usenix.org/system/files/conference/foci15/foci15-paper-ververis-update.pdf">https://www.usenix.org/system/files/</a>
              <a href="https://www.usenix.org/system/files/conference/foci15/foci15-paper-ververis-update.pdf">conference/foci15/foci15-paper-ververis-update.pdf</a>&gt;.

   [<a id="ref-W3CAccessibility">W3CAccessibility</a>]
              World Wide Web Consortium, "Accessibility", 2016,
              &lt;<a href="https://www.w3.org/standards/webdesign/accessibility">https://www.w3.org/standards/webdesign/accessibility</a>&gt;.

   [<a id="ref-W3Ci18nDef">W3Ci18nDef</a>]
              Ishida, R. and S. Miller, "Localization vs.
              Internationalization", World Wide Web Consortium,
              April 2015, &lt;<a href="http://www.w3.org/International/questions/qa-i18n.en">http://www.w3.org/International/</a>
              <a href="http://www.w3.org/International/questions/qa-i18n.en">questions/qa-i18n.en</a>&gt;.



<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 78]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


   [<a id="ref-wikileaks">wikileaks</a>]
              Sladek, T. and E. Broese, "Market Survey: Detection &amp;
              Filtering Solutions to Identify File Transfer of Copyright
              Protected Content for Warner Bros. and movielabs", 2011,
              &lt;<a href="https://wikileaks.org/sony/docs/05/docs/Anti-Piracy/CDSA/EANTC-Survey-1.5-unsecured.pdf">https://wikileaks.org/sony/docs/05/docs/Anti-Piracy/CDSA/</a>
              <a href="https://wikileaks.org/sony/docs/05/docs/Anti-Piracy/CDSA/EANTC-Survey-1.5-unsecured.pdf">EANTC-Survey-1.5-unsecured.pdf</a>&gt;.

   [<a id="ref-WP-Tempora">WP-Tempora</a>]
              Wikipedia, "Tempora", September 2017,
              &lt;<a href="https://en.wikipedia.org/wiki/Tempora">https://en.wikipedia.org/wiki/Tempora</a>&gt;.

   [<a id="ref-WSJ">WSJ</a>]      Sonne, P. and M. Coker, "Firms Aided Libyan Spies", The
              Wall Street Journal, August 2011,
              &lt;<a href="http://www.wsj.com/articles/SB10001424053111904199404576538721260166388">http://www.wsj.com/articles/</a>
              <a href="http://www.wsj.com/articles/SB10001424053111904199404576538721260166388">SB10001424053111904199404576538721260166388</a>&gt;.

   [<a id="ref-WynsbergheMoura">WynsbergheMoura</a>]
              Nguyen, B., Ed., van Wynsberghe, A., van Wynsberghe, A.,
              and G. Moreira Moura, "The concept of embedded values and
              the example of internet security", June 2013,
              &lt;<a href="http://doc.utwente.nl/87095/">http://doc.utwente.nl/87095/</a>&gt;.

   [<a id="ref-XMPP-Manifesto">XMPP-Manifesto</a>]
              Saint-Andre, P. and XMPP Operators, "A Public Statement
              Regarding Ubiquitous Encryption on the XMPP Network",
              March 2014, &lt;<a href="https://raw.githubusercontent.com/stpeter/manifesto/master/manifesto.txt">https://raw.githubusercontent.com/</a>
              <a href="https://raw.githubusercontent.com/stpeter/manifesto/master/manifesto.txt">stpeter/manifesto/master/manifesto.txt</a>&gt;.

   [<a id="ref-Zittrain">Zittrain</a>] Zittrain, J., "The Future of the Internet - And How to
              Stop It", Yale University Press &amp; Penguin UK, 2008,
              &lt;<a href="https://dash.harvard.edu/bitstream/handle/1/4455262/Zittrain_Future%20of%20the%20Internet.pdf?sequence=1">https://dash.harvard.edu/bitstream/handle/1/4455262/</a>
              <a href="https://dash.harvard.edu/bitstream/handle/1/4455262/Zittrain_Future%20of%20the%20Internet.pdf?sequence=1">Zittrain_Future%20of%20the%20Internet.pdf?sequence=1</a>&gt;.



















<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 79]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


Acknowledgements

   A special thanks to all members of the HRPC Research Group who
   contributed to this document.  The following deserve a special
   mention:

   -  Joana Varon for helping draft the first iteration of the
      methodology and previous drafts, and for directing the film "Net
      of Rights" and working on the interviews at IETF 92 in Dallas.

   -  Daniel Kahn Gillmor (dkg) for helping with the first iteration of
      the glossary (<a href="#section-2">Section 2</a>) as well as a lot of technical guidance,
      support, and language suggestions.

   -  Claudio Guarnieri for writing the first iterations of the case
      studies on VPNs, HTTP, and P2P.

   -  Will Scott for writing the first iterations of the case studies on
      DNS, IP, and XMPP.

   -  Avri Doria for proposing writing a glossary in the first place,
      help with writing the initial proposals and Internet-Drafts, her
      reviews, and her contributions to the glossary.

   Thanks also to Stephane Bortzmeyer, John Curran, Barry Shein, Joe
   Hall, Joss Wright, Harry Halpin, and Tim Sammut, who made a lot of
   excellent suggestions, many of which found their way directly into
   the text.  We want to thank Amelia Andersdotter, Stephen Farrell,
   Stephane Bortzmeyer, Shane Kerr, Giovane Moura, James Gannon, Alissa
   Cooper, Andrew Sullivan, S. Moonesamy, Roland Bless, and Scott Craig
   for their reviews and for testing the HRPC guidelines in the wild.
   We would also like to thank Molly Sauter, Arturo Filasto, Nathalie
   Marechal, Eleanor Saitta, Richard Hill, and all others who provided
   input on this document or the conceptualization of the idea.  Thanks
   to Edward Snowden for his comments at IETF 93 in Prague regarding the
   impact of protocols on the rights of users.















<span class="grey">Ten Oever &amp; Cath              Informational                    [Page 80]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span>
<span class="grey"><a href="./rfc8280">RFC 8280</a>          Human Rights Protocol Considerations      October 2017</span>


Authors' Addresses

   Niels ten Oever
   ARTICLE 19

   Email: mail@nielstenoever.net


   Corinne Cath
   Oxford Internet Institute

   Email: corinnecath@gmail.com







































Ten Oever &amp; Cath              Informational                    [Page 81]
</pre>