A new Request for Comments is now available in online RFC libraries.


        RFC 1571:

        Title:      Telnet Environment Option Interoperability Issues 
        Author:     D. Borman
        Mailbox:    dab@CRAY.COM
        Pages:      4
        Characters: 8,117
        Updates:    1408


RFC 1408, the specification for the Telnet Environment Option,
specifies definitions for VAR and VALUE that are reversed from the BSD
implementation of the Telnet Environment option.  Since the BSD
implementation was the reference implementation that the RFC was
supposed to document, and is the base for many existing
implementations, there exists an interoperability problem between
implementations with conflicting definitions for VAR and VALUE.  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
document is the product of the TELNET Working Group of the IETF.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute