New protocol elements for HTTP Status Code 451
draft-sahib-451-new-protocol-elements-02

Document Type Active Internet-Draft (individual in art area)
Last updated 2018-07-16
Replaces draft-451-new-protocol-elements
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state In Last Call (ends 2018-07-30)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alexey Melnikov
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                           S. Sahib
Internet-Draft                                             July 16, 2018
Intended status: Informational
Expires: January 17, 2019

             New protocol elements for HTTP Status Code 451
                draft-sahib-451-new-protocol-elements-02

Abstract

   This document recommends additional protocol elements to Hypertext
   Transfer Protocol (HTTP) status code 451 (defined by RFC7725).

   Discussion of this document was conducted on the Human Rights
   Protocol Considerations Research Group mailing list
   https://www.irtf.org/mailman/listinfo/hrpc [1], briefly on the
   HTTPBIS Working Group mailing list ietf-http-wg@w3.org [2] and on
   https://lists.ghserv.net/mailman/listinfo/statuscode451 [3].

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 https://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 17, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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

Sahib                   Expires January 17, 2019                [Page 1]
Internet-Draft          New elements for HTTP 451              July 2018

   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.  New Protocol Elements . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Blocking Authority  . . . . . . . . . . . . . . . . . . .   2
     2.2.  Geographical Scope of Block . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
     6.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [RFC7725] was standardized by the IETF in February 2016.  It defined
   HTTP status code 451 - to be used when "a server operator has
   received a legal demand to deny access to a resource or to a set of
   resources".

   This document attempts to outline protocol recommendations that would
   help make the status code more useful to users.

2.  New Protocol Elements

2.1.  Blocking Authority

   In addition to the "blocked-by" header specified in [RFC7725], an
   HTTP response with status code 451 would benefit from including
   another "Link" HTTP header field [RFC5988] which has a "rel"
   parameter whose value is "blocking-authority".  It's important to
   distinguish between the implementer of the block, and the authority
   that mandated the block in the first place.  This is because these
   two organizations might not be the same - a government (the blocking
   authority) could force an Internet Service Provider (the implementer
   of the block) to deny access to a certain resource.  There is
   confusion amongst implementors of [RFC7725] about the meaning of the
   term "blocked-by", perhaps in part because of the example given in
   the RFC [ERRATA_ID-5181] - it would be useful to explicitly include
   space for both, as both provide essential information about the legal
   block.

Sahib                   Expires January 17, 2019                [Page 2]
Internet-Draft          New elements for HTTP 451              July 2018

2.2.  Geographical Scope of Block

   HTTP status code 451 is increasingly being used to deny access to
   resources based on geographical IP.  The response should contain a
   provisional header with geographical scope of block.  This scope
   should correspond to comma-separated list of alpha-2 country codes
Show full document text