Re: Newly revised standards-track RFC

"David A. Borman" <dab@berserkly.cray.com> Wed, 06 April 1994 18:18 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08649; 6 Apr 94 14:18 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08645; 6 Apr 94 14:18 EDT
Received: from list.nih.gov by CNRI.Reston.VA.US id aa18966; 6 Apr 94 14:18 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 2971; Wed, 06 Apr 94 14:17:14 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 2970; Wed, 06 Apr 94 13:59:01 EDT
Date: Wed, 6 Apr 1994 12:56:50 CDT
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: "David A. Borman" <dab@berserkly.cray.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: <9404061418.aa18966@CNRI.Reston.VA.US>

> This language is not strong enough and precise enough for me.  How about
> saying that IAC sequences (other than IAC-IAC) WILL be handled as if they
> appeared AFTER the IAC EOR if they appear inside a TN3270E frame.
> For this reason, they SHOULD be sent outside a TN3270E frame.
>
> Fred

Ah, a good way of putting it.  This makes sure that all IAC commands
are properly dealt with as per the Telnet protocol, and still strongly
encourages developers to defer sending any IAC commands until after a
complete TN3270E frame has been sent.
                        -David Borman, dab@cray.com