IETF Logo Mail Archive

RFC Comments

azi <rndi!azi@uunet.uu.net> Wed, 21 July 1993 05:06 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23180; 21 Jul 93 1:06 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa23176; 21 Jul 93 1:06 EDT
Received: from list.nih.gov by CNRI.Reston.VA.US id aa06488; 21 Jul 93 1:06 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 0723; Wed, 21 Jul 93 01:05:39 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 0718; Wed, 21 Jul 93 01:05:32 EDT
Date: Wed, 21 Jul 1993 07:45:50 +0200
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: azi <rndi!azi@uunet.uu.net>
Subject: RFC Comments
X-To: uunet!list.nih.gov!tn3270e@uunet.UU.NET
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9307210106.aa06488@CNRI.Reston.VA.US>

Hi everyone,

I still have two points:

1) What about the SCS encoded (and not 3270 formatted) SSCP-LU session
  support ? Everything is ready - why dont use it ? (also solves the
  SYS_REQ issue)

2) A small challenge to the all : Why wasn't the SNA RH format chosen
   as the TN3270E-header ? This will allow us to use all SNA functions
   (including chaining).  Currently we just have to define which functions
   are supported, but for future use - we have all the SNA information, and
   it is even shorter !


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

v2.23.0 | Report a Bug | By Email