RFC 3232 INFORMATIONAL REGISTRIES · IANA

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

The memo that retired the printed Assigned Numbers RFC in favor of an online database.

On rfc-editor.org ↗
PUBLISHED
January 2002
AUTHORS
J. Reynolds
STREAM
Legacy
BUILDS ON
RFC 1700 — Assigned Numbers
SERIES RAN
November 1977 to October 1994
RFC 1700 STATUS
Historic
DOI
10.17487/RFC3232

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                J. Reynolds, Editor
Request for Comments: 3232                                    RFC Editor
Obsoletes: 1700                                             January 2002
Category: Informational


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

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

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

Abstract

   This memo obsoletes RFC 1700 (STD 2) "Assigned Numbers", which
   contained an October 1994 snapshot of assigned Internet protocol
   parameters.

Description

   From November 1977 through October 1994, the Internet Assigned
   Numbers Authority (IANA) periodically published tables of the
   Internet protocol parameter assignments in RFCs entitled, "Assigned
   Numbers".  The most current of these Assigned Numbers RFCs had
   Standard status and carried the designation: STD 2.  At this time,
   the latest STD 2 is RFC 1700.

   Since 1994, this sequence of RFCs have been replaced by an online
   database accessible through a web page (currently, www.iana.org).
   The purpose of the present RFC is to note this fact and to officially
   obsolete RFC 1700, whose status changes to Historic.  RFC 1700 is
   obsolete, and its values are incomplete and in some cases may be
   wrong.

   We expect this series to be revived in the future by 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

Full Copyright Statement

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

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and 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.

AI ELI5

On this page
PROBLEMFor years the IANA published tables of Internet protocol parameter assignments as "Assigned Numbers" RFCs, but a printed snapshot goes out of date.
MECHANISMRFC 3232 notes that the series has been replaced by an online database and officially obsoletes RFC 1700, changing its status to Historic.
WHY IT MATTERSRFC 1700 is obsolete, and its values are incomplete and in some cases may be wrong. The current values live in the online database instead.

§1The Assigned Numbers Series

From November 1977 through October 1994, the Internet Assigned Numbers Authority (IANA) periodically published tables of Internet protocol parameter assignments in RFCs titled "Assigned Numbers". The most current of these had Standard status and carried the designation STD 2. At the time of this memo the latest STD 2 is RFC 1700.

That RFC holds an October 1994 snapshot of the assignments.

For many years the number keepers printed a big list of Internet numbers every so often. The last printed list was from October 1994.

§2RFC 1700 Is Obsoleted

Since 1994, this sequence of RFCs has been replaced by an online database accessible through a web page. The purpose of RFC 3232 is to note this fact and to officially obsolete RFC 1700, whose status changes to Historic.

The memo is blunt about the old list: RFC 1700 is obsolete, and its values are incomplete and in some cases may be wrong. It also says the authors expect the series to be revived in the future by the new IANA organization.

The printed list is now old news and may have mistakes. Use the live website. The memo adds that the printed list might come back someday.

§3Security Considerations

The memo states that it does not affect the technical security of the Internet. It defines no protocol, so there is nothing further to secure.

This memo only points to a new place to look things up, so it does not change how safe the Internet is.

§4References