RFC 6360

Conclusion of FYI RFC Sub-Series

📅 published August 2011, from ietf

Conclusion of FYI RFC Sub-Series ✨

Okay bestie, here's the vibe check on this one: RFC 6360 🎀 It's an Informational doc (not Standards Track, so no pressure 💅), written by R. Housley of Vigil Security, dated August 2011. It obsoletes RFC 1150 and basically puts that one on the Historic shelf 🌸. ISSN: 2070-1721.

Abstract 🦋

Okay so this doc is literally closing the book on the For Your Information (FYI) sub-series 📚. That sub-series was created by RFC 1150 for the IETF User Services Area, which doesn't exist anymore 💀. The IESG (the folks running the show 👑) is NOT adding anything else to this sub-series, and this doc is just the official receipt of that decision 🧾. It also obsoletes RFC 1150 and moves it to Historic. Iconic retirement arc 😭🫶

Status of This Memo 💜

Quick reminder: this is not an Internet Standards Track spec. It's just published for info 🌈

It's a product of the IETF 🌸, it reflects the community's consensus ✨, it got public review 👀, and the IESG approved it for publication 🔥. Not every IESG-approved doc is up for any level of Internet Standard, so check Section 2 of RFC 5741 if you're curious 🙈

For the current status, errata, or to leave feedback, head to http://www.rfc-editor.org/info/rfc6360 🦋

Copyright (c) 2011 IETF Trust and the document authors. All rights reserved 💅

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions (http://trustee.ietf.org/license-info) as of the publication date. Read them carefully, because they spell out what you can and can't do with it 📜. Any Code Components pulled from this doc must include the Simplified BSD License text (see Section 4.e of the Trust Legal Provisions), and they come with no warranty, same as the Simplified BSD License says 🌈

1. Background 📚

So the FYI sub-series started with RFC 1150 [RFC1150] back in 1990 🕰️ for the IETF User Services Area. That group hasn't met since IETF 53 in March 2001, so it's been a minute 😭. The whole point was to give Internet users a stash of info that might be interesting to a wide range of people 🧚

RFC 1150 [RFC1150] is what introduced FYI. Since then, 38 FYI numbers have been handed out 🔢. Plenty of other Informational RFCs exist too, they just aren't part of FYI 💖

You can find the full FYI list on the RFC Editor website [INDEX] 🌐

2. Conclusion of the FYI Sub-Series 👑

The IESG is done adding to FYI ✋. They'll keep making Informational RFCs, but none of those get an FYI number 🙅‍♀️

Every FYI doc that's already published keeps its number 💜. Those numbers are still useful reference points, and you can cite a doc by its FYI number 🎀

If a future RFC obsoletes something already in FYI, that new RFC won't get an FYI number either 🫶

3. RFC 1150 Moved to Historic 🌸

This doc moves RFC 1150 [RFC1150] to Historic 🕰️. The procedures in RFC 1150 are no longer valid 💀. If anyone wants to add to FYI someday, new procedures can be written to replace this doc ✨

4. Security Considerations 🔐

No Internet security issues are expected from the actions in this doc 🧚

5. References 📖

5.1. Normative Reference

  • [RFC1150] Malkin, G. and J. Reynolds, "FYI on FYI: Introduction to the FYI Notes", FYI 1, RFC 1150, March 1990.

5.2. Informative Reference

Author's Address 🦋

Russell Housley 💖 Vigil Security, LLC 918 Spring Knoll Drive Herndon, VA 20170 USA EMail: housley@vigilsec.com

📦 where this page comes from