idnits 2.17.1 draft-thomson-gendispatch-no-expiry-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 a Security Considerations section. ** The abstract seems to contain references ([2], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The draft header indicates that this document updates RFC2418, but the abstract doesn't seem to directly say this. It does mention RFC2418 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC2418, updated by this document, for RFC5378 checks: 1997-03-25) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 4, 2019) is 1607 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 136 -- Looks like a reference, but probably isn't: '2' on line 138 -- Looks like a reference, but probably isn't: '3' on line 140 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 GENDISPATCH M. Thomson 3 Internet-Draft Mozilla 4 Updates: 2418 (if approved) November 4, 2019 5 Intended status: Best Current Practice 6 Expires: May 7, 2020 8 Internet-Drafts Don't Expire 9 draft-thomson-gendispatch-no-expiry-00 11 Abstract 13 The long-standing insistence that Internet-Drafts carry expiration 14 dates is a concept that is no longer necessary. This document 15 removes requirements for expiration for Internet-Drafts from RFC 16 2418/BCP 25. 18 Note to Readers 20 Discussion of this document takes place on the GENDISPATCH Working 21 Group mailing list (gendispatch@ietf.org), which is archived at 22 https://mailarchive.ietf.org/arch/browse/gendispatch/ [1]. 24 Source for this draft and an issue tracker can be found at 25 https://github.com/martinthomson/no-expiry [2]. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on May 7, 2020. 44 Copyright Notice 46 Copyright (c) 2019 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Removing Internet-Draft Expiration . . . . . . . . . . . . . 2 63 3. Security and Privacy Considerations . . . . . . . . . . . . . 3 64 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 65 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 67 5.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 70 1. Introduction 72 The I-D Guidelines [3] declares that Internet Drafts expire 185 days 73 after their posting unless replaced or under a range of special 74 conditions, such as when the document is under IESG review. 76 Expiration of drafts is believed to encourage authors to update 77 drafts that they wish to discuss. Expired drafts are no longer 78 served from the primary IETF servers. 80 Copies of expired drafts are retained and can be obtained using other 81 services. Expired drafts are routinely cited and referenced. 82 Published RFCs routinely include informative references to drafts, 83 which then usually expire. 85 Forced expiration serves no purpose that is not adequately served by 86 the publication date on the document. 88 2. Removing Internet-Draft Expiration 90 The date of posting for an Internet-Draft is sufficient information 91 for readers to understand validity. 93 This document proposes that the "Expires:" field be removed from the 94 header of submitted Internet-Drafts, and that the boilerplate be 95 amended as follows: 97 OLD: 99 Internet-Drafts are draft documents valid for a maximum of six 100 months and may be updated, replaced, or obsoleted by other 101 documents at any time. It is inappropriate to use Internet-Drafts 102 as reference material or to cite them other than as "work in 103 progress." 105 NEW: 107 Internet-Drafts are draft documents that may be updated, replaced, 108 or obsoleted by other documents at any time. It is inappropriate 109 to use Internet-Drafts as reference material or to cite them other 110 than as "work in progress." 112 Creating a revision to the I-D Guidelines will be necessary to remove 113 references to expiration. 115 This document updates RFC 2418 [WG] to remove a single mention of 116 expiration from Section 7.2. 118 3. Security and Privacy Considerations 120 This document has no direct implications on security or privacy. 122 4. IANA Considerations 124 This document makes no request of IANA. 126 5. References 128 5.1. Normative References 130 [WG] Bradner, S., "IETF Working Group Guidelines and 131 Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, 132 September 1998, . 134 5.2. URIs 136 [1] https://mailarchive.ietf.org/arch/browse/gendispatch/ 138 [2] https://github.com/martinthomson/no-expiry 140 [3] https://www.ietf.org/standards/ids/guidelines/ 142 Author's Address 144 Martin Thomson 145 Mozilla 147 Email: mt@lowentropy.net