CurrentINFORMATIONALLegacy stream

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

In plain English — editorial summary, not part of the RFC

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

Document record

Document ID
RFC3232
Published
January 2002
Authors
J. Reynolds
Status
INFORMATIONAL
Stream
Legacy
Area
Pages
3
Also known as
Obsoletes:
RFC 1700

Topics

Standards lineage

This document is one revision in a chain of 25 RFCs, each formally replacing the one before it.

  1. RFC 317 (1972)
  2. RFC 349 (1972)
  3. RFC 433 (1972)
  4. RFC 503 (1973)
  5. RFC 604 (1973)
  6. RFC 739 (1977)
  7. RFC 750 (1978)
  8. RFC 755 (1979)
  9. RFC 758 (1979)
  10. RFC 762 (1980)
  11. RFC 770 (1980)
  12. RFC 776 (1981)
  13. RFC 790 (1981)
  14. RFC 820 (1982)
  15. RFC 870 (1983)
  16. RFC 900 (1984)
  17. RFC 923 (1984)
  18. RFC 943 (1985)
  19. RFC 960 (1985)
  20. RFC 990 (1986)
  21. RFC 1010 (1987)
  22. RFC 1060 (1990)
  23. RFC 1340 (1992)
  24. RFC 1700 (1994)
  25. RFC 3232 (2002)

Read the full history of Assigned Numbers: RFC 1700 is Replaced by an On-line Database

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3232-assigned-numbers-rfc-1700-is-replaced-by-an-on-line-database