Re: Newly revised standards-track RFC

Roger Fajman <RAF@cu.nih.gov> Mon, 21 March 1994 23:37 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17186; 21 Mar 94 18:37 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa17178; 21 Mar 94 18:37 EST
Received: from list.nih.gov by CNRI.Reston.VA.US id aa02959; 21 Mar 94 18:37 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 8262; Mon, 21 Mar 94 18:35:09 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 8261; Mon, 21 Mar 94 18:32:49 EST
Date: Mon, 21 Mar 1994 18:30:29 EST
Reply-To: IETF TN3270E Working Group List <TN3270E@list.nih.gov>
X-Orig-Sender: IETF TN3270E Working Group List <TN3270E@list.nih.gov>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Roger Fajman <RAF@cu.nih.gov>
Subject: Re: Newly revised standards-track RFC
X-To: TN3270E@LIST.NIH.GOV
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9403211837.aa02959@CNRI.Reston.VA.US>

>    The presence of Telnet commands within a TN3270E data message
>    (i.e., between the header and the trailing IAC EOR) is not
>    supported; neither clients nor servers should send such data.  If a
>    TN3270E data message containing an IAC-command sequence (other than
>    IAC IAC) is received, the receiver should discard the IAC-command
>    sequence and continue processing the TN3270E data message.
>    IAC-commands should be sent between TN3270E data messages, with no
>    header and no trailing IAC EOR.

Sounds OK to me.

Roger Fajman                                   Telephone:  +1 301 402 4265
National Institutes of Health                  BITNET:     RAF@NIHCU
Bethesda, Maryland, USA                        Internet:   RAF@CU.NIH.GOV