Re: RFCS - Telnet commands mixed with 3270 data

fab@fab.md.interlink.com Thu, 03 March 1994 17:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06405; 3 Mar 94 12:19 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06401; 3 Mar 94 12:19 EST
Received: from list.nih.gov by CNRI.Reston.VA.US id aa11216; 3 Mar 94 12:19 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 4519; Thu, 03 Mar 94 12:17:33 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 4517; Thu, 03 Mar 94 12:17:23 EST
Date: Thu, 03 Mar 1994 12:21:10 -0500
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: RFCS - Telnet commands mixed with 3270 data
X-To: TN3270E@LIST.NIH.GOV
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9403031219.aa11216@CNRI.Reston.VA.US>

> I have one comment on the RFCS draft:  it might be a good idea
> to specify what happens if IACs occur in the middle of a 3270
> block.  This is especially true for those that have meaning
> in the protocol, such as ATTN and SYSREQ commands.
>
I thought our agreement was that these would be prohibited.  IACs would
only occur inside a block for IAC doubling.  Otherwise, hold off until
after the IAC EOR, then put in your IAC whatever.

However, I see that section 8 introduction says just the opposite!

Fred