RFC 1571: Telnet Environment Option Interoperability Issues
In plain English — editorial summary, not part of the RFC
This document describes a method for allowing implementors to ensure that their implementation of the Environment option will be interoperable with as many other implementations as possible, by providing a set of heuristics that can be used to help identify which definitions for VAR and VALUE are being used by the other side of the connection. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1571
- Published
- January 1994
- Authors
- D. Borman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 1408
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1572Telnet Environment OptionCurrent
January 1994
- RFC 1567X.500 Directory Monitoring MIBObsoleted
January 1994
- RFC 1576TN3270 Current PracticesCurrent
January 1994
- RFC 1566Mail Monitoring MIBObsoleted
January 1994
- RFC 1565Network Services Monitoring MIBObsoleted
January 1994
- RFC 1564DSA Metrics (OSI-DS 34 (v3))Current
January 1994
- RFC 1544The Content-MD5 Header FieldObsoleted
November 1993
- RFC 1537Common DNS Data File Configuration ErrorsObsoleted
October 1993
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?