Implementation Report for HTTP Status Code 451 (RFC 7725)
draft-451-imp-report-00

Document Type Active Internet-Draft (individual)
Last updated 2017-07-17
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
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)
Human Rights Protocol Considerations Research Group           S. Abraham
Internet-Draft                                                 CIS India
Intended status: Informational                               MP. Canales
Expires: January 16, 2018                             Derechos Digitales
                                                                 J. Hall
                                                                     CDT
                                                          O. Khrustaleva
                                                     American University
                                                            N. ten Oever
                                                              ARTICLE 19
                                                             C. Runnegar
                                                                    ISOC
                                                                S. Sahib
                                                           Cisco Systems
                                                           July 15, 2017

       Implementation Report for HTTP Status Code 451 (RFC 7725)
                        draft-451-imp-report-00

Abstract

   This report describes implementation experience between various
   components working with the HTTP Status Code 451 [RFC7725], a risk
   assessment and recommendation for improvements.

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 January 16, 2018.

Copyright Notice

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

Abraham, et al.         Expires January 16, 2018                [Page 1]
Internet-Draft                451ImpReport                     July 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Vocabulary  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Target audiences  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Who is likely to implement the 451 status code? . . . . . . .   4
     4.1.  Server operators  . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Intermediaries  . . . . . . . . . . . . . . . . . . . . .   4
   5.  Who is likely to use the 451 status code data?  . . . . . . .   4
     5.1.  Browser vendors . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  End users . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.3.  Researchers . . . . . . . . . . . . . . . . . . . . . . .   4
     5.4.  Civil society . . . . . . . . . . . . . . . . . . . . . .   4
     5.5.  Governments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Current Usage . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Trends and observations . . . . . . . . . . . . . . . . . . .   6
   9.  Potential negative or positive impacts  . . . . . . . . . . .   6
   10. What are features of a blocking reporting infrastructure that
       would be useful?  . . . . . . . . . . . . . . . . . . . . . .   7
   11. What features of blocking events are supported by the
       existing 451 status code, and what features do we need to
       add?  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   12. Appendix: Legal Realities . . . . . . . . . . . . . . . . . .   9
   13. Russia  . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     13.1.  Federal Law of 27 July 2006  . . . . . . . . . . . . . .   9
     13.2.  "Yarovaya laws"  . . . . . . . . . . . . . . . . . . . .  10
   14. Chile . . . . . . . . . . . . . . . . . . . . . . . . . . . .  10
Show full document text