idnits 2.17.1 draft-sahib-451-new-protocol-elements-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([2], [3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 01, 2018) is 2095 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 174 -- Looks like a reference, but probably isn't: '2' on line 176 -- Looks like a reference, but probably isn't: '3' on line 178 Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Sahib 3 Internet-Draft August 01, 2018 4 Intended status: Informational 5 Expires: February 2, 2019 7 New protocol elements for HTTP Status Code 451 8 draft-sahib-451-new-protocol-elements-03 10 Abstract 12 This document recommends additional protocol elements to Hypertext 13 Transfer Protocol (HTTP) status code 451 (defined by RFC7725). 15 Discussion of this document was conducted on the Human Rights 16 Protocol Considerations Research Group mailing list 17 https://www.irtf.org/mailman/listinfo/hrpc [1], briefly on the 18 HTTPBIS Working Group mailing list ietf-http-wg@w3.org [2] and on 19 https://lists.ghserv.net/mailman/listinfo/statuscode451 [3]. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on February 2, 2019. 38 Copyright Notice 40 Copyright (c) 2018 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. New Protocol Elements . . . . . . . . . . . . . . . . . . . . 2 57 2.1. Blocking Authority . . . . . . . . . . . . . . . . . . . 2 58 2.2. Geographical Scope of Block . . . . . . . . . . . . . . . 3 59 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 60 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 61 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 3 62 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 6.2. Informative References . . . . . . . . . . . . . . . . . 4 65 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 68 1. Introduction 70 [RFC7725] was standardized by the IETF in February 2016. It defined 71 HTTP status code 451 - to be used when "a server operator has 72 received a legal demand to deny access to a resource or to a set of 73 resources". 75 This document attempts to outline protocol recommendations that would 76 help make the status code more useful to users. 78 2. New Protocol Elements 80 2.1. Blocking Authority 82 An HTTP response with status code 451 should include a "Link" HTTP 83 header field [RFC8288] which has a "rel" parameter whose value is 84 "blocking-authority", in addition to the "blocked-by" header 85 specified in [RFC7725]. It's important to distinguish between the 86 implementer of the block, and the authority that mandated the block 87 in the first place [ERRATA_ID-5181]. This is because these two 88 organizations might not be the same - a government (the blocking 89 authority) could force an Internet Service Provider (the implementer 90 of the block) to deny access to a certain resource. Both provide 91 essential information about the legal block. 93 2.2. Geographical Scope of Block 95 HTTP status code 451 is increasingly being used to deny access to 96 resources based on geographical location. The response should 97 contain a provisional header named "geo-scope-block" that specifies 98 the countries in which a resource is blocked. This scope should 99 correspond to a comma-separated list of alpha-2 country codes defined 100 in [ISO.3166-1]. The rationale for keeping the geographical scope to 101 country-level granularity is that most blocks are mandated by 102 national governments [IMPL_REPORT], [AUTOMATTIC_COUNTRY_BLOCK_LIST]. 104 3. Security Considerations 106 This document does not add additional security considerations to 107 [RFC7725]. 109 4. IANA Considerations 111 The Link Relation Type Registry should be updated with the following 112 entry: 114 - Relation Name: blocking-authority 116 - Description: Identifies the authority that has issued the block. 118 - Reference: this document 120 In addition, IANA should be updated with the following provisional 121 header: 123 - Header field name: geo-scope-block 125 - Applicable protocol: http 127 - Status: provisional 129 - Specification document(s): this document 131 Acknowledgements 133 Thanks to Alp Toker, Niels ten Oever, Stephane Bortzmeyer, Corinne 134 Cath, Christine Runnegar, and many others on the HRPC mailing list 135 (linked above) for reviewing and brainstorming. 137 6. References 139 6.1. Normative References 141 [ERRATA_ID-5181] 142 Bortzmeyer, S., "[Technical Errata Reported] RFC7725 143 (5181)", 2017, 144 . 146 [ISO.3166-1] 147 International Organization for Standardization, "Codes for 148 the representation of names of countries and their 149 subdivisions - Part 1: Country code", ISO Standard 3166- 150 1:1997 , 1997. 152 [RFC7725] Bray, T., "An HTTP Status Code to Report Legal Obstacles", 153 RFC 7725, DOI 10.17487/RFC7725, February 2016, 154 . 156 [RFC8288] Nottingham, M., "Web Linking", RFC 8288, 157 DOI 10.17487/RFC8288, October 2017, 158 . 160 6.2. Informative References 162 [AUTOMATTIC_COUNTRY_BLOCK_LIST] 163 "Automattic - Country Block List", 2018, 164 . 166 [IMPL_REPORT] 167 Abraham, S., Canales, MP., Hall, J., Khrustaleva, O., ten 168 Oever, N., Runnegar, C., and S. Sahib, "Implementation 169 Report for HTTP Status Code 451", 2017, 170 . 172 6.3. URIs 174 [1] https://www.irtf.org/mailman/listinfo/hrpc 176 [2] mailto:ietf-http-wg@w3.org 178 [3] https://lists.ghserv.net/mailman/listinfo/statuscode451 180 Author's Address 182 Shivan Kaul Sahib 184 EMail: shivankaulsahib@gmail.com