Re: Newly revised standards-track RFC

fab@fab.md.interlink.com Tue, 29 March 1994 16:45 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03854; 29 Mar 94 11:45 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03850; 29 Mar 94 11:45 EST
Received: from list.nih.gov by CNRI.Reston.VA.US id aa08616; 29 Mar 94 11:45 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 9192; Tue, 29 Mar 94 11:43:00 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 9190; Tue, 29 Mar 94 11:42:54 EST
Date: Tue, 29 Mar 1994 11:45:00 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: fab@fab.md.interlink.com
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: <9403291145.aa08616@CNRI.Reston.VA.US>

Bill,

Section 8 has a paragraph that starts:
>    Note also that Telnet commands may appear anywhere in the Telnet
>    stream.  For this reason,...

This seems to conflict with the paragraph just added:

>    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.

I suggest we delete the first sentence and first phrase.  Start that
paragraph with:
>    If either side wishes to transmit the decimal value 255...


Fred