Network Working Group A. Roach Internet-Draft Mozilla Updates: 2026 (if approved) April 06, 2018 Intended status: Best Current Practice Expires: October 8, 2018 Referring to Internet Drafts as 'Internet Drafts' Rather Than 'Works in Progress' draft-roach-id-cite-00 Abstract This document updates RFC 2026 to change the term "Work in Progress" to "Internet Draft." Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on October 8, 2018. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Roach Expires October 8, 2018 [Page 1]
Internet-Draft Internet Draft April 2018 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Change to RFC 2026 . . . . . . . . . . . . . . . . . . . . . 2 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction Section 2.2. of [RFC2026] allows publication of RFC with references to Internet-Drafts, with the requirement that such citations indicate that the Internet-Draft is labeled as a "Work in Progress." While this designation is frequently accurate when used in this way, it is sometimes useful for RFCs to refer to Internet Drafts that are not being actively maintained and which will likely never be published. As such documents are not technically "Works in Progress," this specification updates RFC 2026's language to use the more broadly applicable phrase "Internet Draft." 2. Change to RFC 2026 This document updates RFC 2026 by replacing the final paragraph of its section 2.2 with the following text: Note: It is acceptable to reference a standards-track specification that may reasonably be expected to be published as an RFC using the phrase "Internet Draft" without referencing an Internet-Draft. This may also be done in a standards track document itself as long as the specification in which the reference is made would stand as a complete and understandable document with or without the reference to the "Internet Draft". Roach Expires October 8, 2018 [Page 2]
Internet-Draft Internet Draft April 2018 3. Security Considerations This change is administrative, and should have no significant impact on security. 4. IANA Considerations This document requires no actions from IANA. 5. Normative References [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, <https://www.rfc-editor.org/info/rfc2026>. Author's Address Adam Roach Mozilla \ Dallas US Phone: +1 650 903 0800 x863 Email: adam@nostrum.com Roach Expires October 8, 2018 [Page 3]