idnits 2.17.1 draft-thomson-http-teapot-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 document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 12, 2017) is 2418 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 7231 (Obsoleted by RFC 9110) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Thomson 3 Internet-Draft Mozilla 4 Intended status: Informational September 12, 2017 5 Expires: March 16, 2018 7 The Teapot Exists 8 draft-thomson-http-teapot-00 10 Abstract 12 The teapot exists. 14 Status of This Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at https://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on March 16, 2018. 31 Copyright Notice 33 Copyright (c) 2017 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (https://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 1. The Existence of Teapots 48 In an unpublished article in 1952 [TEAPOT], Bertrand Russell 49 postulated the existence of a teapot: 51 To take another illustration: nobody can prove that there is not 52 between the Earth and Mars a china teapot revolving in an 53 elliptical orbit, but nobody thinks this sufficiently likely to be 54 taken into account in practice. 56 Though mentioned originally in jest and without solid evidence of its 57 existence, first by Russell and later by Masinter [HTCPCP], sightings 58 have increased in recent years. 60 The teapot exists. 62 2. Philosophical Considerations 64 We cannot be certain whether the teapot is cognizant of its own 65 existence. Though Decartes [COGITO] used thought as the basis of his 66 theory of existence, it's not established whether thought is a 67 necessary precondition for existence. 69 (418) 70 o 71 _,_ 72 c(___)r 74 3. Security Considerations 76 Even jokes can have serious consequences. Arguably, the best jokes 77 always have consequences. 79 4. IANA Considerations 81 IANA shall register the 418 (I'm a Teapot) status code in the 82 Hypertext Transfer Protocol (HTTP) Status Code Registry, citing this 83 document. 85 As recommended by [RFC7231], this document refines the definition of 86 the 418 status code. Being a teapot is irrevocable, therefore this 87 status code is cacheable. The payload of a response with a 418 88 status code isn't a representation of the effective request URI 89 unless the Content-Location header field contains the effective 90 request URI. 92 5. References 94 5.1. Normative References 96 [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer 97 Protocol (HTTP/1.1): Semantics and Content", RFC 7231, 98 DOI 10.17487/RFC7231, June 2014, 99 . 101 5.2. Informative References 103 [COGITO] Descartes, R., "Discourse on the Method", 1637. 105 [HTCPCP] Masinter, L., "Hyper Text Coffee Pot Control Protocol 106 (HTCPCP/1.0)", RFC 2324, DOI 10.17487/RFC2324, April 1998, 107 . 109 [TEAPOT] Russell, B., "Is There a God?", Never published , 1952, 110 . 113 Author's Address 115 Martin Thomson 116 Mozilla 118 Email: martin.thomson@gmail.com