ObsoletedHISTORICLegacy stream

RFC 943: Assigned numbers

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 960.

Current document in this lineage: RFC 3232Assigned Numbers: RFC 1700 is Replaced by an On-line Database

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

This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997.

Document record

Document ID
RFC943
Published
April 1985
Authors
J.K. Reynolds; J. Postel
Status
HISTORIC
Stream
Legacy
Area
Pages
50
Also known as
Obsoletes:
RFC 923
Obsoleted by:
RFC 960

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

Referenced by

One later RFC formally updates or obsoletes part of this document.

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/943-assigned-numbers