New protocol elements for HTTP Status Code 451
draft-sahib-451-new-protocol-elements-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-03-19
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           S. Sahib
Internet-Draft                                            March 19, 2018
Intended status: Informational
Expires: September 20, 2018

             New protocol elements for HTTP Status Code 451
                draft-sahib-451-new-protocol-elements-00

Abstract

   This draft recommends protocol updates to Hypertext Transfer Protocol
   (HTTP) status code 451 (defined by RFC7725) based on an examination
   of how the new status code is being used by parties involved in
   denial of Internet resources because of legal demands.  Also included
   is an analysis of HTTP 451 from a human rights perspective using
   guidelines from RFC8280.

   Discussion of this draft is at https://www.irtf.org/mailman/listinfo/
   hrpc and https://lists.ghserv.net/mailman/listinfo/statuscode451.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 20, 2018.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Sahib                  Expires September 20, 2018               [Page 1]
Internet-Draft          New elements for HTTP 451             March 2018

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Existing Protocol Elements  . . . . . . . . . . . . . . . . .   3
   4.  Recommendations . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Human Rights Considerations . . . . . . . . . . . . . . . . .   4
     7.1.  Connectivity  . . . . . . . . . . . . . . . . . . . . . .   4
     7.2.  Privacy . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.3.  Content Agnosticism . . . . . . . . . . . . . . . . . . .   5
     7.4.  Security  . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.5.  Internationalization  . . . . . . . . . . . . . . . . . .   5
     7.6.  Censorship Resistance . . . . . . . . . . . . . . . . . .   5
     7.7.  Open Standards  . . . . . . . . . . . . . . . . . . . . .   5
     7.8.  Heterogeneity Support . . . . . . . . . . . . . . . . . .   5
     7.9.  Anonymity . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.10. Pseudonymity  . . . . . . . . . . . . . . . . . . . . . .   6
     7.11. Accessibility . . . . . . . . . . . . . . . . . . . . . .   6
     7.12. Localization  . . . . . . . . . . . . . . . . . . . . . .   6
     7.13. Decentralization  . . . . . . . . . . . . . . . . . . . .   6
     7.14. Reliability . . . . . . . . . . . . . . . . . . . . . . .   6
     7.15. Confidentiality . . . . . . . . . . . . . . . . . . . . .   6
     7.16. Integrity . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.17. Authenticity  . . . . . . . . . . . . . . . . . . . . . .   7
     7.18. Adaptability  . . . . . . . . . . . . . . . . . . . . . .   7
     7.19. Outcome Transparency  . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   [RFC7725] was standardized by the IETF in February 2016.  It defined
   HTTP status code 451 - to be used when a "a server operator has
   received a legal demand to deny access to a resource or to a set of
   resources".

   Subsequently, an effort was made to investigate usage of HTTP 451 and
   evaluate if it fulfills its mandate of providing "transparency in
   circumstances where issues of law or public policy affect server
   operations" [IMPL_REPORT_DRAFT].  This draft attempts to explicate
Show full document text