RFC 1150
FYI on FYI: Introduction to the FYI Notes
F.Y.I. on F.Y.I. π
Introduction to the F.Y.I. Notes π
Okay bestie, here's the title block tea β:
- It's from the Network Working Group and it's RFC 1150, which is also FYI: 1 π¦
- Written by G. Malkin at Proteon and J. Reynolds at ISI π«Ά
- Dated March 1990 πΈ
- No Obsoletes or Updates are listed, so it's standing on its own π
Status of this Memo π
This RFC is the first in a new sub-series of RFCs called FYIs (For Your Information). It gives information to the Internet community and does not specify any standard. Distribution of this memo is unlimited π
1. Introduction β¨
The FYI series is basically a central home base for info about anything Internet-related π‘ Topics can be as wild as historical memos on "Why it was was done this way" or as practical as answers to the operational questions everyone keeps asking π
FYIs are for a wide crowd. Some are beginner-friendly and some go deep. Anyone with something worth sharing and the time to write it can submit one π
2. Why RFCs π
FYIs live inside the bigger RFC series for a few reasons. The main one is that RFC distribution is tried and true π₯ If you can get an RFC, you automatically get an FYI too. And if you already know the RFC series, you can easily find out what FYIs exist π
Another reason is that RFCs already have maintenance processes in place and funded, so it makes sense to keep similar documents maintained the same way. After all, there have been informational RFCs before π
Last but not least, the name RFC has credibility. Memos with the RFC label are taken seriously, and FYIs should get that same respect β
3. Format Rules π
Since FYIs are part of the RFC series, they must conform to RFC-1111 (Request for Comments on Request for Comments: Instructions to RFC Authors) when it comes to format. Ideally, they should be submitted in ASCII format, as described by section 2a, of RFC-1111 β¨
4. Status Statement π
Every RFC must include a "Status of this Memo" section on its first page, with a paragraph that explains what the RFC is meant to do. This section shows the status the RFC Editor and the Internet Activities Board (IAB) gave it π§ People publish RFCs for lots of reasons: to share info with interested folks, to start or keep a discussion going about an interesting idea, or to publish the specification of a protocol π¦
For example, the status text reads:
This RFC is the first in a new sub-series of RFCs called FYIs (For
Your Information). This memo provides information for the Internet
community. It does not specify any standard. Distribution of this
memo is unlimited.
5. Distribution Statement πΈ
Each FYI also needs a "distribution statement" π The whole point of FYIs is to spread info around, so there's no reason for distribution to be anything other than "unlimited" π
Usually the distribution statement is just the sentence "Distribution of this memo is unlimited." tacked onto the end of the "Status of this Memo" section β¨
6. Security Considerations π₯
All FYIs must contain a section that discusses the security considerations of the procedures that are the main topic of the RFC. This one is not optional, no cap π
7. Author's Address π«Ά
Each FYI must end with a section giving the author's address. That includes the name and postal address, the telephone number, and the Internet email address π
8. Relation to other FYIs π¦
Sometimes an FYI adds info on a topic covered by an earlier FYI, or completely replaces one. There are two terms for those cases: UPDATES and OBSOLETES. A document that obsoletes an earlier one can stand on its own. A document that only updates an earlier one can't stand on its own. It has to be added to or inserted into the existing document, so on its own it has limited usefulness π§©
UPDATES
This is used as a reference from a new item that can't be used alone, meaning one that supplements a previous document. It points back to that previous document. The newer publication is a part that supplements or gets added onto the existing document, like an addendum or separate extra info meant to join the original π
OBSOLETES
This is used to refer to an earlier document that this document replaces. This document either has revised info, or all of the same info plus some new info, however big or small that new info is. In other words, this document can be used alone without referring to the older one π
OBSOLETED-BY
This is used to refer to the newer document that replaces the older one π
UPDATED-BY
This is used to refer to the newer document that adds info to an existing document that's still useful π
9. The FYI Editors π
All FYIs go to the IETF User Services Working Group for review before they're submitted to the RFC Editor π Submissions can be sent to:
Joyce K. Reynolds
Chair, User Services Working Group
USC - Information Sciences Institute
4676 Admiralty Way
Marina del Rey, California 90292-6695
Phone: (213) 822-1511
Electronic mail: JKREY@ISI.EDU
10. The FYI Announcement List π£
New FYIs get announced to the RFC distribution list run by the SRI Network Information Center (NIC). To get added to or removed from this list, contact the SRI-NIC by emailing RFC-REQUEST@NIC.DDN.MIL π
11. Obtaining FYIs π§
You can grab FYIs over FTP from NIC.DDN.MIL, using the pathname FYI:mm.TXT or RFC:RFCnnnn.TXT. Here mm is the FYI number and nnnn is the RFC number π¦ Log in with FTP using username ANONYMOUS and password GUEST.
If your site can't use FTP, the NIC has an automatic mail service too π¬ Send your request to SERVICE@NIC.DDN.MIL, and put the FYI or RFC number in the subject line, like Subject: FYI mm or Subject: RFC nnnn β¨
Security Considerations π
Security issues are not discussed in this memo. π Yes, that's the whole section, and yes, I'm side-eyeing it hard π
Authors' Addresses π«Ά
Gary Scott Malkin
Proteon, Inc.
2 Technology Drive
Westborough, MA 01581-5008
Phone: (508) 898-2800
EMail: gmalkin@proteon.com
Joyce K. Reynolds
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
EMail: jkrey@isi.edu
That's the whole FYI on FYI, bestie! ππ β¨
π¦ where this page comes from
- ietf: rfc1150 1990-03
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms