IETF conflict review for draft-nottingham-safe-hint
conflict-review-nottingham-safe-hint-04

Document Conflict review draft-nottingham-safe-hint-11 ISE stream
Last updated 2019-07-01
State Approved No Problem - announcement sent
IESG Shepherding AD Barry Leiba
Telechat date (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>, draft-nottingham-safe-hint@ietf.org

Conflict review
draft-nottingham-safe-hint-11

   
The IESG has concluded that this work is related to IETF work done in WG
httpbis , but this relationship does not prevent publishing.

The IESG would like the following IESG note added to the document:

-----------------------

Given the current requirements for registering HTTP preferences [RFC7420], the
relationship between this document and those registry requirements is unclear.
The document claims that its purpose is to specify a common understanding of
how the "safe" HTTP preference operates, but this is not achieved
since there is no semantic defined for "safe." The registration
policy for the HTTP preferences registry is Specification Required, so an RFC
is not necessary in order to simply register this preference.

This mechanism was presented for publication as an IETF Proposed Standard, but
was not approved for publication by the IESG. Concerns raised by the IESG
remain valid. Some of these concerns are addressed or discussed in the
document, but others are not, such as how the use of this preference may
incentivize increased censorship and/or targeting of minors.

-----------------------