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

This draft should go through the HTTPBIS working group, not as an individual submission.  The working group does not have the interest in handling it now, but might reconsider it in the future.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-sahib-451-new-protocol-elements-01. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator understands that, upon approval of this document, there are two actions which we must complete.

First, in the Link Relation Types registry located at:

https://www.iana.org/assignments/link-relations/

a single, new relation name will be added to the registry as follows:

Relation Name: blocking-authority
Description: Identifies the authority that has issued the block.
Reference: [ RFC-to-be ]

As this document requests registrations in a Specification Required (see RFC 8126) registry, we will initiate the required Expert Review via a separate request. Expert review will need to be completed before your document can be approved for publication as an RFC.

Second, in the Provisional Message Header Field Names registry on the Message Headers registry page located at:

https://www.iana.org/assignments/message-headers/

a single, new header field name will be registered as follows:

Header Field Name: geo-scope-block
Template:
Protocol: http
Status: provisional
Reference: [ RFC-to-be ]

As this also requests registration in an Expert Review (see RFC 8126) registry, we will initiate the required Expert Review via a separate request. Expert review will need to be completed before your document can be approved for publication as an RFC.

The IANA Functions Operator understands that these are the only actions required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

The following Last Call announcement was sent out (ends 2018-07-30):

From: The IESG
To: IETF-Announce
CC: draft-sahib-451-new-protocol-elements@ietf.org, alexey.melnikov@isode.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (New protocol elements for HTTP Status Code 451) to Informational RFC


The IESG has received a request from an individual submitter to consider the
following document: - 'New protocol elements for HTTP Status Code 451'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-07-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  This draft recommends protocol updates to Hypertext Transfer Protocol
  (HTTP) status code 451 (defined by RFC7725) based on an examination
  of how the new status code is being used by parties involved in
  denial of Internet resources because of legal demands.  Also included
  is an analysis of HTTP 451 from a human rights perspective using
  guidelines from RFC8280.

  Discussion of this draft is at https://www.irtf.org/mailman/listinfo/
  hrpc [1] and https://lists.ghserv.net/mailman/listinfo/statuscode451
  [2].




The file can be obtained via
https://datatracker.ietf.org/doc/draft-sahib-451-new-protocol-elements/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-sahib-451-new-protocol-elements/ballot/


No IPR declarations have been submitted directly on this I-D.