Re: Automatic Signon/Telnet: How can the 5250 client differentiate between V5R1 and Pre-V5R1 Releases at signon time?

Hi, Pat (et al):

Just a thought -- shouldn't this kind of low-level protocol stuff be
officially documented somewhere, such as in an RFC, e.g. for TN3270 and
TN5250, etc.?

Regards,

Mark S. Waterbury

----- Original Message -----
> From: "Patrick Botz" <botz@xxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Thursday, February 10, 2005 9:13 AM
> Subject: RE: Automatic Signon/Telnet: How can the 5250 client
differentiate
> between V5R1 and Pre-V5R1 Releases at signon time?
>

> The bit's are exchanged in the 2 byte header id (first byte is for client,
> second is for host).  On the client seed flow up, set the client byte to 1
> indicating the client can support SHA.  Then in the reply, the host byte
> will be 0 or 1 for DES, or 2 or 3 for SHA.
>
> FYI...I'm getting this info from someone on the Client Access team (I
don't
> know this stuff personally :-) )...
>
> Patrick Botz
> Senior Technical Staff Member
> eServer Security Architect
> (507) 253-0917, T/L 553-0917
> email: botz@xxxxxxxxxx
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>