Comments to the TN3270E RFC (fwd)

Bill Kelly <kellywh@mail.auburn.edu> Mon, 19 July 1993 19:13 UTC

Date: Mon, 19 Jul 1993 13:58:20 -0500
Reply-To: 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: Comments to the TN3270E RFC (fwd)
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9307191513.aa12842@CNRI.Reston.VA.US>

Hi all,

Here are a couple of private mailings that have been exchanged regarding
the draft TN3270E document.  I thought people on the list might find them
of some use.

-Bill

Bill Kelly               phone: (205) 844-4512
Auburn University     Internet: kellywh@mail.auburn.edu

---------- Forwarded message ----------
Date: Mon, 19 Jul 93 14:43:09 +0200
From: azi <rndi!azi@uunet.UU.NET>
To: uunet!mail.auburn.edu!kellywh@uunet.UU.NET
Subject: Comments to the TN3270E RFC


Bill,

I read the July 1993 edition of the TN3270E RFC and I have the following
comments:

1. In section 10.3 - Why is the BIND image limited to display terminals ?
   Why can't printer emulation use this function ?

2. Why there is no support for SCS under terminals ? This will solve the
   SSCP-LU session, not supported in current TN3270. This will also
   give immediate solution for the SYS-REQ. The fact that the client
   sends SCS data implies that the user pressed the SYS-REQ key.

3. Section 10.3 - Whatif the BIND data is not received by the server at
   the time of request ?

4. When should the server create the LU-LU session with the SNA host ?
   Where is the application LU name is taken from ? (assuming that SSCP-LU
   session is not supported).

Thanks, and I appreciate the good work done on this RFC.

Elazar (Azi) Ronen
Software development manager,RADLINX Ltd.
7 Arad st.
Tel Aviv 69710
Israel

Tel: 972-3-6475188
Fax: 972-3-6475057
Email: rndi!azi@uunet.uu.net or uunet.uu.net!rndi!azi

Comments to the TN3270E RFC (fwd) Bill Kelly
Re: Comments to the TN3270E RFC (fwd) Bill Kelly