--- 1/draft-ietf-httpbis-legally-restricted-status-02.txt 2015-11-05 22:15:23.046619409 -0800 +++ 2/draft-ietf-httpbis-legally-restricted-status-03.txt 2015-11-05 22:15:23.066619890 -0800 @@ -1,18 +1,18 @@ HTTP Working Group T. Bray Internet-Draft Textuality -Intended status: Standards Track August 31, 2015 -Expires: March 3, 2016 +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-02 + 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 @@ -29,54 +29,55 @@ 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 March 3, 2016. + 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 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 . . . . . . . . . . . . . . 2 + 3. 451 Unavailable For Legal Reasons . . . . . . . . . . . . . . 3 4. Identifying Blocking Entities . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 - 7. Normative References . . . . . . . . . . . . . . . . . . . . 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 a received a legal demand to - deny access to a resource. + 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. @@ -97,20 +98,21 @@ 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: ; rel="blocked-by" Content-Type: text/html Unavailable For Legal Reasons

Unavailable For Legal Reasons

This request may not be serviced in the Roman Province of Judea due to the Lex Julia Majestatis, which disallows access to resources hosted on servers deemed to be operated by the People's Front of Judea.

@@ -146,39 +148,47 @@ purpose, the "Link" header field MUST have a "rel" parameter whose value is "blocked-by". The intent is that the header be used to identify the entity actually implementing blockage, not any other entity mandating it. A human readable response body, as discussed above, is the appropriate location for discussion of administrative and policy issues. 5. Security Considerations -5.1. 451 Unavailable for Legal Reasons - - The 451 status code is optional; clients cannot rely upon its use. - It is possible that certain legal authorities might wish to avoid + Clients cannot rely upon the use of the 451 status code. It is + possible that certain legal authorities might wish to avoid transparency, and not only demand the restriction of access to certain resources, but also avoid disclosing that the demand was made. 6. IANA Considerations The HTTP Status Codes Registry should be updated with the following entry: o Code: 451 o Description: Unavailable for Legal Reasons o Specification: [ this document ] + The Link Relation Type Registry should updated with the following + entry: + + o Relation Name: blocked-by + + o Description: Identifies the entity blocking access to a resource + folllowing on receipt of a legal demand. + + o Reference: This document + 7. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ RFC2119, March 1997, . [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005,