RFC 617: Note on socket number assignment
In plain English — editorial summary, not part of the RFC
Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451.
Document record
- Document ID
- RFC617
- Published
- February 1974
- Authors
- E.A. Taft
- Status
- UNKNOWN
- Stream
- Legacy
- Area
- —
- Pages
- 3
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 624Comments on the File Transfer ProtocolCurrent
February 1974
- RFC 854Telnet Protocol SpecificationUpdated
May 1983
- RFC 855Telnet Option SpecificationsCurrent
May 1983
- RFC 1739A Primer On Internet and TCP/IP ToolsObsoleted
December 1994
- RFC 1922Chinese Character Encoding for Internet MessagesCurrent
March 1996
- RFC 2943TELNET Authentication Using DSACurrent
September 2000
- RFC 2944Telnet Authentication: SRPCurrent
September 2000
- RFC 2946Telnet Data Encryption OptionCurrent
September 2000
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?