idnits 2.17.1 draft-yevstifeyev-ion-report-07.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 IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 7, 2011) is 4645 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4693 (Obsoleted by RFC 6393) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT M. Yevstifeyev 3 Intended Status: Informational August 7, 2011 4 Obsoletes: 4693 (if approved) 5 Expires: February 8, 2012 7 Moving RFC 4693 to Historic 8 draft-yevstifeyev-ion-report-07 10 Abstract 12 This document requests RFC 4693 to be moved to Historic status. It 13 also obsoletes RFC 4693. 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright and License Notice 38 Copyright (c) 2011 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 1. Introduction 53 This document requests RFC 4693 [RFC4693] to be moved to Historic 54 status. It also obsoletes that document. 56 2. Moving RFC 4693 to Historic status 58 RFC 4693 [RFC4693] established the IETF Operational Notes (IONs) 59 series of documents on the experimental basis [RFC3933]. This series 60 was intended to discuss the set of procedures that the IETF follows, 61 but for which the RFC publication process is an inappropriate 62 documentation vehicle. 64 Per RFC 3933 [RFC3933], in March 2008 the IESG decided to terminate 65 the IONs process experiment [IESG-IONS]. This document moves RFC 66 4693 to Historic status, per [HISTORIC], to reflect experiment 67 closure. Please contact the IESG at for further 68 details, including motivation for the termination and further destiny 69 of IONs. 71 3. Security Considerations 73 This document is of administrative nature only and therefore there 74 are no security issues related to it. 76 4. Acknowledgments 78 Various discussions of, valuable comments on and criticism of 79 previous versions of this document were provided by (in alphabetical 80 order) Harald Alvestrand, Brian Carpenter, Russ Housley, John 81 Klensin, Barry Leiba, and Subramanian Moonesamy. Harald Alvestrand 82 is also acknowledged for his work on RFC 4693. 84 5. References 86 5.1. Normative References 88 [RFC4693] Alvestrand, H., "IETF Operational Notes", RFC 4693, 89 October 2006. 91 5.2. Informative References 93 [IESG-IONS] Housley, R., "IETF Operational Notes", Web Page, April 94 2008, 95 . 97 [HISTORIC] The IESG, "IESG Statement on Designating RFCs as 98 Historic", IESG Statement, June 2011, 99 . 102 [RFC3933] Klensin, J. and S. Dawkins, "A Model for IETF Process 103 Experiments", BCP 93, RFC 3933, November 2004. 105 Author's Addresses 107 Mykyta Yevstifeyev 108 8 Kuzovkov St., Apt. 25 109 Kotovsk 110 Ukraine 112 EMail: evnikita2@gmail.com