An HTTP Status Code to Report Legal Obstacles
draft-ietf-httpbis-legally-restricted-status-03

The information below is for an old version of the document
Document Type Active Internet-Draft (httpbis WG)
Last updated 2015-11-05
Replaces draft-tbray-http-legally-restricted-status
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state Waiting for WG Chair Go-Ahead
Revised I-D Needed - Issue raised by WGLC
Document shepherd Mark Nottingham
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HTTP Working Group                                               T. Bray
Internet-Draft                                                Textuality
Intended status: Standards Track                        November 5, 2015
Expires: May 8, 2016

             An HTTP Status Code to Report Legal Obstacles
            draft-ietf-httpbis-legally-restricted-status-03

Abstract

   This document specifies a Hypertext Transfer Protocol (HTTP) status
   code for use when resource access is denied as a consequence of legal
   demands.

Editorial Note (To be removed by RFC Editor before publication)

   Discussion of this draft takes place on the HTTPBIS working group
   mailing list (ietf-http-wg@w3.org), which is archived at [1].

   Working Group information can be found at [2] and [3]; source code
   and issues list for this draft can be found at [4].

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 May 8, 2016.

Copyright Notice

   Copyright (c) 2015 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

Bray                       Expires May 8, 2016                  [Page 1]
Internet-Draft               HTTP-status-451               November 2015

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  451 Unavailable For Legal Reasons . . . . . . . . . . . . . .   3
   4.  Identifying Blocking Entities . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   This document specifies a Hypertext Transfer Protocol (HTTP) status
   code for use when a server operator has received a legal demand to
   deny access to a resource or to a set of resources which includes the
   requested resource.

   This status code can be used to provide transparency in circumstances
   where issues of law or public policy affect server operations.  This
   transparency may be beneficial both to these operators and to end
   users.

   [RFC4924] discusses the forces working against transparent operation
   of the Internet; these clearly include legal interventions to
   restrict access to content.  As that document notes, and as Section 4
   of [RFC4084] states, such restrictions should be made explicit.

   Feedback should occur on the ietf-http-wg@w3.org mailing list.

2.  Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Bray                       Expires May 8, 2016                  [Page 2]
Internet-Draft               HTTP-status-451               November 2015

3.  451 Unavailable For Legal Reasons

   This status code indicates that the server is denying access to the
   resource as a consequence of a legal demand.

   The server in question might not be an origin server.  This type of
   legal demand typically most directly affects the operations of ISPs
   and search engines.

   Responses using this status code SHOULD include an explanation, in
   the response body, of the details of the legal demand: the party
   making it, the applicable legislation or regulation, and what classes
   of person and resource it applies to.  For example:

   HTTP/1.1 451 Unavailable For Legal Reasons
   Link: <https://spqr.example.org/legislatione>; rel="blocked-by"
Show full document text