RFC 6393

RFC 6393: Moving RFC 4693 to Historic 🎀

okay bestie, this is the paper trail for RFC 6393 ✨ It's called "Moving RFC 4693 to Historic" and it was written by M. Yevstifeyev (that's Mykyta Yevstifeyev 💅) in September 2011. It's Informational, so it's published for info and it's not a standards-track spec. It obsoletes RFC 4693, and its ISSN is 2070-1721 🦋

Abstract 💖

okay so this doc moves RFC 4693 to Historic status ✨ and it also obsoletes RFC 4693 🌸

Status of This Memo 🌈

this one is not an Internet Standards Track spec, it's just published for info 💅

it's a product of the IETF (Internet Engineering Task Force), so it represents the consensus of the IETF community 🫶 it got public review and was approved for publication by the IESG (Internet Engineering Steering Group). not every IESG-approved doc is a candidate for any level of Internet Standard, so see Section 2 of RFC 5741 for that tea 🍓

for the current status, errata, and how to give feedback, check http://www.rfc-editor.org/info/rfc6393 🧚

Copyright Notice 🎀

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. 💜

this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as in effect on the date of publication. please actually read these, bestie, because they explain your rights and restrictions 🙈 Code Components pulled out of this doc must include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in the Simplified BSD License ⚠️

1. Introduction 🌸

okay so this doc moves RFC 4693 [RFC4693] to Historic status, and it also obsoletes that document ✨

2. Moving RFC 4693 to Historic Status 🦋

RFC 4693 [RFC4693] set up the IETF Operational Notes (IONs) series as an experiment [RFC3933]. the whole point of this series was to talk about the procedures the IETF follows, but where the RFC publication process is the wrong place to document them 💅

per RFC 3933 [RFC3933], the IESG decided in March 2008 to end the IONs process experiment [IESG-IONS] 😭 this doc moves RFC 4693 to Historic status, per [HISTORIC], to reflect that the experiment is closed 🥀

if you want the details, like why it was terminated and what happens to IONs next, hit up the IESG at <iesg@ietf.org> 🫶

3. Security Considerations 🔒

okay this one is serious: this doc is administrative in nature only, so there are no security issues related to it 💀

4. Acknowledgments 👑

shoutout to everyone who gave discussions, valuable comments, and criticism on earlier versions of this doc 🙌 in alphabetical order: Harald Alvestrand, Brian Carpenter, Russ Housley, John Klensin, Barry Leiba, and Subramanian Moonesamy 💖 Harald Alvestrand also gets extra love for his work on RFC 4693 ✨

5. References 📚

5.1. Normative References 💜

[RFC4693]   Alvestrand, H., "IETF Operational Notes", RFC 4693,
            October 2006.

5.2. Informative References 🌈

[IESG-IONS] Housley, R., "IETF Operational Notes", April 2008,
            <http://www.ietf.org/old/2009/u/iesgcontent/ions.html>.

[HISTORIC]  The IESG, "IESG Statement on Designating RFCs as
            Historic", IESG Statement, June 2011,
            <http://www.ietf.org/iesg/statement/designating-rfcs-as-
            historic.html>.

[RFC3933]   Klensin, J. and S. Dawkins, "A Model for IETF Process
            Experiments", BCP 93, RFC 3933, November 2004.

Author's Address 🧚

Mykyta Yevstifeyev
8 Kuzovkov St., Apt. 25
Kotovsk
Ukraine

EMail: evnikita2@gmail.com

that's the whole doc, bestie! 🌈💖✨