RFC 3232

Assigned Numbers: RFC 1700 is Replaced by an On-line Database

📅 published January 2002, from ietf

RFC 3232: Assigned Numbers, RFC 1700 Is Replaced by an On-line Database 💖

Okay bestie, this one is a whole glow-up story. ✨ It's a January 2002 doc, written by J. Reynolds as Editor from the RFC Editor crew, and it's Informational, so it's just info, not a rule. 🎀 It obsoletes RFC 1700 and doesn't list any updates. 🦋

Status of this Memo 📜

No standards energy here, babe. 💅 This memo gives information to the Internet community. It does not specify an Internet standard of any kind. Distribution of it is unlimited. 🌈

Copyright (C) The Internet Society (2002). All Rights Reserved. 🔒

Abstract 🍓

This memo replaces RFC 1700 (STD 2), "Assigned Numbers." That one was a snapshot from October 1994 of the assigned Internet protocol parameters. 🧚

Description 🌸

So, from November 1977 through October 1994, IANA (the Internet Assigned Numbers Authority) kept posting tables of Internet protocol parameter assignments inside RFCs called "Assigned Numbers." ✨ The newest ones had Standard status and got the STD 2 label, and at this point the latest STD 2 is RFC 1700. 👑

Since 1994, those RFCs have been swapped out for an online database you can check on a web page (right now that's www.iana.org). 💻 This RFC is basically here to say that out loud, and to officially obsolete RFC 1700, which moves to Historic status. 🕰️

RFC 1700 is obsolete. Its values are incomplete, and in some cases they may be wrong. 💀 Don't trust the old tables for anything real!

We expect this series to come back someday under the new IANA organization. 🦋

Security Considerations 🔐

This memo does not affect the technical security of the Internet. 🫶

Author's Address 📮

Joyce K. Reynolds
RFC Editor
4676 Admiralty Way
Marina del Rey, CA  90292
USA

EMail: rfc-editor@rfc-editor.org

Copyright (C) The Internet Society (2002). All Rights Reserved. 🌈

Here's the legal tea, fully intact. 🍵 You can copy and share this document and translations of it, and you can make derivative works that comment on or explain it, or help implement it. You can publish and distribute those in whole or in part, with no restrictions, as long as the copyright notice and this paragraph stay on every copy and derivative work. 🎀

BUT the document itself can't be modified in any way. That means you can't remove the copyright notice or the references to the Internet Society or other Internet organizations. The exceptions are when you need to develop Internet standards (then the copyright procedures in the Internet Standards process have to be followed) or when you need to translate it into a language other than English. 💅

The limited permissions above are perpetual, and the Internet Society or its successors or assigns will not revoke them. 💖

This document and the information in it are provided on an "AS IS" basis. THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 🙈

Acknowledgement 🫶

Funding for the RFC Editor function is currently provided by the Internet Society. 🌟

📦 where this page comes from