RFCS
Tom Butts <tom@hpsccs.oc.com> Wed, 30 March 1994 16:40 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02822; 30 Mar 94 11:40 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02818; 30 Mar 94 11:40 EST
Received: from list.nih.gov by CNRI.Reston.VA.US id aa08993; 30 Mar 94 11:40 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 1573; Wed, 30 Mar 94 11:38:01 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 1570; Wed, 30 Mar 94 11:31:21 EST
Date: Wed, 30 Mar 1994 10:28:44 -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: Tom Butts <tom@hpsccs.oc.com>
Subject: RFCS
X-To: tn3270e@list.nih.gov
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9403301140.aa08993@CNRI.Reston.VA.US>
Section 10.3 "When establishing an SNA session on behalf of a client, the server will receive a Bind RU from the host application. It will also receive a Start Data Traffic RU. Once both of these have been responded to positively by the server, it must then inform the client of the presence of this session by sending it a data message with the DATA-TYPE flag set to BIND-IMAGE. The data portion of this message must contain the bind image exactly as it was received in the Bind RU that the server accepted on behalf of the client." Why not allow the client to see the BIND-IMAGE and respond to it (positively or negatively)? Also why require the server to keep a BIND-IMAGE around for each session -- just send it when the server is going to positively respond to the BIND. --