Newly revised standards-track RFC
Bill Kelly <kellywh@mail.auburn.edu> Mon, 21 March 1994 20:52 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12156; 21 Mar 94 15:52 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12152; 21 Mar 94 15:52 EST
Received: from [128.231.64.10] by CNRI.Reston.VA.US id aa28037; 21 Mar 94 15:52 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 7619; Mon, 21 Mar 94 15:47:55 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 7616; Mon, 21 Mar 94 15:35:13 EST
Date: Mon, 21 Mar 1994 14:24:22 -0600
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: Bill Kelly <kellywh@mail.auburn.edu>
Subject: Newly revised standards-track RFC
X-To: TN3270E list <tn3270e@list.nih.gov>
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9403211552.aa28037@CNRI.Reston.VA.US>
Hi, I've sent a copy of the revised standards-track tn3270e RFC to Roger and Bob. The only changes since the previous version are: - dates revised as appropriate - I copied in verbatim the current version of the standard "disclaimer" that the IETF wants at the beginning of every draft (the "Status of this Memo" section). There were minor changes in capitalization, etc. - the following text has been added to section 8 after the paragraph that begins "Note also that Telnet commands may appear anywhere in the Telnet stream...": 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. Please let me know whether or not the above text is good enough to resolve the issue of mixing IACs with 3270 data. Thanks, Bill Bill Kelly phone: (205) 844-4512 Auburn University Internet: kellywh@mail.auburn.edu
- Newly revised standards-track RFC Bill Kelly
- Re: Newly revised standards-track RFC Roger Fajman
- Re: Newly revised standards-track RFC Roger Fajman
- Re: Newly revised standards-track RFC fab
- Re: Newly revised standards-track RFC Bill Kelly
- Re: Newly revised standards-track RFC fab
- Re: Newly revised standards-track RFC David A. Borman
- Re: Newly revised standards-track RFC Bill Kelly
- Re: Newly revised standards-track RFC fab
- Re: Newly revised standards-track RFC David A. Borman
- Re: Newly revised standards-track RFC Robert G. Moskowitz
- Re: Newly revised standards-track RFC Roger Fajman
- Re: Newly revised standards-track RFC Jagan Bearelly
- Re: Newly revised standards-track RFC fab
- Re: Newly revised standards-track RFC David A. Borman
- Re: Newly revised standards-track RFC fab
- Re: Newly revised standards-track RFC Roger Fajman
- Re: Newly revised standards-track RFC David A. Borman
- Re: Newly revised standards-track RFC Robert G. Moskowitz
- Re: Newly revised standards-track RFC Bill Kelly
- Re: Newly revised standards-track RFC Roger Fajman
- Re: Newly revised standards-track RFC Pierre Goyette - The 3270 Man
- Re: Newly revised standards-track RFC Peter DiCamillo