RFC 2066: TELNET CHARSET Option
In plain English — editorial summary, not part of the RFC
This document specifies a mechanism for passing character set and translation information between a TELNET client and server. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2066
- Published
- January 1997
- Authors
- R. Gellens
- Status
- EXPERIMENTAL
- Stream
- Legacy
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1947Greek Character Encoding for Electronic Mail MessagesCurrent
May 1996
- RFC 2237Japanese Character Encoding for Internet MessagesCurrent
November 1997
- RFC 2278IANA Charset Registration ProceduresObsoleted
January 1998
- RFC 1642UTF-7 - A Mail-Safe Transformation Format of UnicodeObsoleted
July 1994
- RFC 1641Using Unicode with MIMECurrent
July 1994
- RFC 1456Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable SpecificationCurrent
May 1993
- RFC 2978IANA Charset Registration ProceduresCurrent
October 2000
- RFC 2367PF_KEY Key Management API, Version 2Current
July 1998
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?