RFC 854: Telnet Protocol Specification
In plain English — editorial summary, not part of the RFC
This is the specification of the Telnet protocol used for remote terminal access in the ARPA Internet. The purpose of the TELNET Protocol is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. It is envisioned that the protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation). This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 18639.
Document record
- Document ID
- RFC854
- Published
- May 1983
- Authors
- J. Postel; J.K. Reynolds
- Status
- INTERNET STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 15
- Also known as
- STD8
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 855Telnet Option SpecificationsCurrent
May 1983
- RFC 624Comments on the File Transfer ProtocolCurrent
February 1974
- RFC 617Note on socket number assignmentCurrent
February 1974
- 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?