IETF Logo Mail Archive

Re: environment option draft

Jordan Brown <jbrown@qdeck.com> Tue, 12 October 1993 22:49 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02754; 12 Oct 93 18:49 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02749; 12 Oct 93 18:49 EDT
Received: from timbuk.cray.com by CNRI.Reston.VA.US id aa22604; 12 Oct 93 18:49 EDT
Received: from hemlock.cray.com by cray.com (4.1/CRI-MX 2.19btd) id AA14350; Tue, 12 Oct 93 17:49:41 CDT
Received: by hemlock.cray.com id AA19263; 4.1/CRI-5.6; Tue, 12 Oct 93 17:49:37 CDT
Received: from cray.com (timbuk.cray.com) by hemlock.cray.com id AA19258; 4.1/CRI-5.6; Tue, 12 Oct 93 17:49:33 CDT
Received: from rockall.qdeck.com (qdeck.com) by cray.com (4.1/CRI-MX 2.19btd) id AA14304; Tue, 12 Oct 93 17:49:30 CDT
Received: from angel.qdeck.com by rockall.qdeck.com (4.1/SMI-4.1) id AA26304; Tue, 12 Oct 93 15:32:51 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jordan Brown <jbrown@qdeck.com>
To: marjo@hpindsy.cup.hp.com
Subject: Re: environment option draft
Cc: telnet-ietf@cray.com
X-Mailer: ScoMail 1.0
Date: Tue, 12 Oct 1993 15:32:54 -0700
Message-Id: <9310121532.aa09513@angel.qdeck.com>

> I suggest that in order to maximize the probability of future interoperability 
> with implementors of RFC 1408 that we require that the heuristics be 
> implemented.

RFC 1408 was a botch all around, and I for one don't want to encourage
use of it.  I'm quite unlikely to support the RFC 1408 ENVIRON option AT ALL.

v2.23.0 | Report a Bug | By Email