< draft-tbray-http-legally-restricted-status-00.txt   draft-tbray-http-legally-restricted-status-01.txt >
Network Working Group T. Bray Network Working Group T. Bray
Internet-Draft Google Internet-Draft Google
Updates: 2616 (if approved) June 11, 2012 Updates: 2616 (if approved) July 10, 2012
Intended status: Standards Track Intended status: Standards Track
Expires: December 13, 2012 Expires: January 11, 2013
A New HTTP Status Code for Legally-restricted Resources A New HTTP Status Code to Report Legal Obstacles
draft-tbray-http-legally-restricted-status-00 draft-tbray-http-legally-restricted-status-01
Abstract Abstract
This document specifies an additional Hypertext Transfer Protocol This document specifies an additional Hypertext Transfer Protocol
(HTTP) status code for use when resource access is denied for legal (HTTP) status code for use when resource access is denied due to
reasons. legal demands.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 13, 2012. This Internet-Draft will expire on January 11, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 8 skipping to change at page 3, line 8
3. 451 Unavailable For Legal Reasons . . . . . . . . . . . . . . . 3 3. 451 Unavailable For Legal Reasons . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
This document specifies an additional Hypertext Transfer Protocol This document specifies an additional Hypertext Transfer Protocol
(HTTP) status code for use when resource access is denied for legal (HTTP) status code for use when resource access is denied due to
reasons. This allows server operators to operate with greater legal demands. This allows server operators to provide greater
transparency in circumstances where issues of law or public policy transparency in circumstances where issues of law or public policy
affect their operation. This transparency may be beneficial both to affect their operation. This transparency may be beneficial both to
these operators and to end users. these operators and to end users.
Feedback should occur on the ietf-http-wg@w3.org mailing list, Feedback should occur on the ietf-http-wg@w3.org mailing list,
although this draft is NOT a work item of the IETF HTTPbis Working although this draft is NOT a work item of the IETF HTTPbis Working
Group. Group.
2. Requirements 2. Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. 451 Unavailable For Legal Reasons 3. 451 Unavailable For Legal Reasons
This status code indicates that the server is subject to legal This status code indicates that the server is denying access to the
restrictions which prevent it servicing the request. resource in response to a legal demand.
Since such restrictions typically apply to all operators in a legal Since such demands typically apply to all operators in a legal
jurisdiction, the server in question may or may not be an origin jurisdiction, the server in question may or may not be an origin
server. The restrictions typically most directly affect the server. The demands typically most directly affect the operations of
operations of ISPs and search engines. ISPs and search engines.
Responses using this status code SHOULD include an explanation, in Responses using this status code SHOULD include an explanation, in
the response body, of the details of the legal restriction; which the response body, of the details of the legal demand: which legal
legal authority is imposing it, and what class of resources it authority is making it, and what class of resources it applies to.
applies to. For example: For example:
HTTP/1.1 451 Unavailable For Legal Reasons HTTP/1.1 451 Unavailable For Legal Reasons
Content-Type: text/html Content-Type: text/html
<html> <html>
<head> <head>
<title>Unavailable For Legal Reasons</title> <title>Unavailable For Legal Reasons</title>
</head> </head>
<body> <body>
<h1>Unavailable For Legal Reasons</h1> <h1>Unavailable For Legal Reasons</h1>
<p>This request may not be serviced in the Roman Province of <p>This request may not be serviced in the Roman Province
Judea due to Lex3515, the Legem Ne Subversionem Act of AUC755, of Judea due to the Lex Julia Majestatis, which disallows
which disallows access to resources hosted on servers deemed access to resources hosted on servers deemed to be
to be operated by the Judean Liberation Front.</p> operated by the People's Front of Judea.</p>
</body> </body>
</html> </html>
The use of the 451 status code implies neither the existence nor non- The use of the 451 status code implies neither the existence nor non-
existence of the resource named in the request. That is to say, it existence of the resource named in the request. That is to say, it
is possible that if the legal restriction were removed, a request for is possible that if the legal demands were removed, a request for the
the resource might still not succeed. resource still might not succeed.
4. Security Considerations 4. Security Considerations
4.1. 451 Unavailable for Legal Reasons 4.1. 451 Unavailable for Legal Reasons
The 451 status code is optional; clients cannot rely upon its use. The 451 status code is optional; clients cannot rely upon its use.
It is imaginable that certain legal authorities may wish to avoid It is possible that certain legal authorities may wish to avoid
transparency, and not only forbid access to certain resources, but transparency, and not only demand the restriction of access to
also disclosure that the restriction exists. certain resources, but also avoid disclosing that the demand was
made.
5. IANA Considerations 5. IANA Considerations
The HTTP Status Codes Registry should be updated with the following The HTTP Status Codes Registry should be updated with the following
entries: entries:
o Code: 451 o Code: 451
o Description: Unavailable for Legal Reasons o Description: Unavailable for Legal Reasons
o Specification: [ this document ] o Specification: [ this document ]
6. Normative References 6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Thanks to Terence Eden, whose blog observed that the existing status Thanks to Terence Eden, who observed that the existing status code
code 403 was not really suitable for this situation, and suggested 403 was not really suitable for this situation, and suggested the
the creation of a new status code creation of a new status code.
Thanks also to Ray Bradbury. Thanks also to Ray Bradbury.
The author takes all responsibility for errors and omissions. The author takes all responsibility for errors and omissions.
Author's Address Author's Address
Tim Bray Tim Bray
Google Google
 End of changes. 14 change blocks. 
29 lines changed or deleted 30 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/
X-Generator: pyht 0.35