draft-ietf-httpbis-legally-restricted-status-00.txt   draft-ietf-httpbis-legally-restricted-status-01.txt 
HTTP Working Group T. Bray HTTP Working Group T. Bray
Internet-Draft Textuality Internet-Draft Textuality
Updates: 2616 (if approved) April 25, 2015 Updates: 2616 (if approved) June 28, 2015
Intended status: Standards Track Intended status: Standards Track
Expires: October 27, 2015 Expires: December 30, 2015
An HTTP Status Code to Report Legal Obstacles An HTTP Status Code to Report Legal Obstacles
draft-ietf-httpbis-legally-restricted-status-00 draft-ietf-httpbis-legally-restricted-status-01
Abstract Abstract
This document specifies a Hypertext Transfer Protocol (HTTP) status This document specifies a Hypertext Transfer Protocol (HTTP) status
code for use when resource access is denied as a consequence of legal code for use when resource access is denied as a consequence of legal
demands. demands.
Editorial Note (To be removed by RFC Editor before publication) Editorial Note (To be removed by RFC Editor before publication)
Discussion of this draft takes place on the HTTPBIS working group Discussion of this draft takes place on the HTTPBIS working group
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 October 27, 2015. This Internet-Draft will expire on December 30, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 2, line 18 skipping to change at page 2, line 18
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 2
3. 451 Unavailable For Legal Reasons . . . . . . . . . . . . . . 2 3. 451 Unavailable For Legal Reasons . . . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . 4
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 4 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
This document specifies a Hypertext Transfer Protocol (HTTP) status This document specifies a Hypertext Transfer Protocol (HTTP) status
code for use when a server operator has a received a legal demand to code for use when a server operator has a received a legal demand to
deny access to a resource. deny access to a resource.
skipping to change at page 3, line 36 skipping to change at page 3, line 36
</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 demands were removed, a request for the is possible that if the legal demands were removed, a request for the
resource still might not succeed. resource still might not succeed.
Note that in many cases clients can still access the denied resource Note that in many cases clients can still access the denied resource
by using technical countermeasures such as a VPN or the Tor network. by using technical countermeasures such as a VPN or the Tor network.
A 451 response is cacheable by default; i.e., unless otherwise
indicated by the method definition or explicit cache controls; see
[RFC7234].
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 possible that certain legal authorities may wish to avoid It is possible that certain legal authorities may wish to avoid
transparency, and not only demand the restriction of access to transparency, and not only demand the restriction of access to
certain resources, but also avoid disclosing that the demand was certain resources, but also avoid disclosing that the demand was
made. made.
skipping to change at page 4, line 4 skipping to change at page 4, line 11
transparency, and not only demand the restriction of access to transparency, and not only demand the restriction of access to
certain resources, but also avoid disclosing that the demand was certain resources, but also avoid disclosing that the demand was
made. 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, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4084] Klensin, J., "Terminology for Describing Internet [RFC4084] Klensin, J., "Terminology for Describing Internet
Connectivity", BCP 104, RFC 4084, May 2005, Connectivity", BCP 104, RFC 4084, DOI 10.17487/RFC4084,
<http://www.rfc-editor.org/info/rfc4084>. May 2005, <http://www.rfc-editor.org/info/rfc4084>.
[RFC4924] Aboba, B. and E. Davies, "Reflections on Internet [RFC4924] Aboba, B. and E. Davies, "Reflections on Internet
Transparency", RFC 4924, July 2007, Transparency", RFC 4924, DOI 10.17487/RFC4924, July 2007,
<http://www.rfc-editor.org/info/rfc4924>. <http://www.rfc-editor.org/info/rfc4924>.
[RFC7234] Fielding, R., Nottingham, M., and J. Reschke, "Hypertext
Transfer Protocol (HTTP/1.1): Caching", RFC 7234, DOI
10.17487/RFC7234, June 2014,
<http://www.rfc-editor.org/info/rfc7234>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Thanks to Terence Eden, who observed that the existing status code Thanks to Terence Eden, who observed that the existing status code
403 was not really suitable for this situation, and suggested the 403 was not really suitable for this situation, and suggested 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.
Author's Address Author's Address
Tim Bray Tim Bray
Textuality Textuality
Email: tbray@textuality.com Email: tbray@textuality.com
URI: http://www.tbray.org/ongoing/ URI: http://www.tbray.org/ongoing/
 End of changes. 12 change blocks. 
11 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/