idnits 2.17.1 draft-nottingham-thanks-larry-00.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 ([RFC2324]), 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 11, 2017) is 2449 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 httpbis M. Nottingham 3 Internet-Draft August 11, 2017 4 Intended status: Standards Track 5 Expires: February 12, 2018 7 Reserving the 418 HTTP Status Code 8 draft-nottingham-thanks-larry-00 10 Abstract 12 [RFC2324] was an April 1 RFC that lampooned the various ways HTTP was 13 abused; one such abuse was the definition of the application-specific 14 418 (I'm a Teapot) status code. 16 In the intervening years, this status code has been widely 17 implemented as an "easter egg", and therefore is effectively consumed 18 by this use. 20 This document changes 418 to the status of "Reserved" in the IANA 21 HTTP Status Code registry to reflect that. 23 Note to Readers 25 _RFC EDITOR: please remove this section before publication_ 27 The issues list for this draft can be found at 28 https://github.com/mnot/I-D/labels/thanks-larry. 30 The most recent (often, unpublished) draft is at 31 https://mnot.github.io/I-D/thanks-larry/. 33 Recent changes are listed at https://github.com/mnot/I-D/commits/gh- 34 pages/thanks-larry. 36 See also the draft's current status in the IETF datatracker, at 37 https://datatracker.ietf.org/doc/draft-nottingham-thanks-larry/. 39 Status of This Memo 41 This Internet-Draft is submitted in full conformance with the 42 provisions of BCP 78 and BCP 79. 44 Internet-Drafts are working documents of the Internet Engineering 45 Task Force (IETF). Note that other groups may also distribute 46 working documents as Internet-Drafts. The list of current Internet- 47 Drafts is at http://datatracker.ietf.org/drafts/current/. 49 Internet-Drafts are draft documents valid for a maximum of six months 50 and may be updated, replaced, or obsoleted by other documents at any 51 time. It is inappropriate to use Internet-Drafts as reference 52 material or to cite them other than as "work in progress." 54 This Internet-Draft will expire on February 12, 2018. 56 Copyright Notice 58 Copyright (c) 2017 IETF Trust and the persons identified as the 59 document authors. All rights reserved. 61 This document is subject to BCP 78 and the IETF Trust's Legal 62 Provisions Relating to IETF Documents 63 (http://trustee.ietf.org/license-info) in effect on the date of 64 publication of this document. Please review these documents 65 carefully, as they describe your rights and restrictions with respect 66 to this document. Code Components extracted from this document must 67 include Simplified BSD License text as described in Section 4.e of 68 the Trust Legal Provisions and are provided without warranty as 69 described in the Simplified BSD License. 71 Table of Contents 73 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 74 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 75 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 76 4. Informative References . . . . . . . . . . . . . . . . . . . 3 77 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 79 1. Introduction 81 [RFC2324] was an April 1 RFC that lampooned the various ways HTTP was 82 abused; one such abuse was the definition of the application-specific 83 418 (I'm a Teapot) status code. 85 In the intervening years, this status code has been widely 86 implemented as an "Easter Egg", and therefore is effectively consumed 87 by this use. 89 This document changes 418 to the status of "Reserved" in the IANA 90 HTTP Status Code registry to reflect that. 92 This indicates that the status code cannot be assigned to other 93 applications currently. If future circumstances require its use 94 (e.g., exhaustion of all other 4NN status codes), it can be re- 95 assigned to another use. 97 Implementations are encouraged to avoid "squatting" on status codes 98 in this manner; while there are a number of unassigned status codes 99 in each range currently, unofficial, uncoordinated use makes the 100 definition of new status codes more difficult over the lifetime of 101 HTTP, which (hopefully) is a potentially very long period of time. 103 2. IANA Considerations 105 This document updates the following entry in the Hypertext Transfer 106 Protocol (HTTP) Status Code Registry: 108 o Value: 418 110 o Description: Reserved 112 o Reference: [this document] 114 IANA should also typographically distinguish "Unassigned" and 115 "Reserved" in the registry descriptions, to prevent confusion. 117 3. Security Considerations 119 This document has no security content. 121 4. Informative References 123 [RFC2324] Masinter, L., "Hyper Text Coffee Pot Control Protocol 124 (HTCPCP/1.0)", RFC 2324, DOI 10.17487/RFC2324, April 1998, 125 . 127 Author's Address 129 Mark Nottingham 131 Email: mnot@mnot.net 132 URI: https://www.mnot.net/