RE: iSCSI: Decimal encoding - why 64 bits ?

["THALER,PAT (A-Roseville,ex1)" <pat_thaler@agilent.com>]

Bill,

I also thought that the result of the reflector discussion was agreement that decimal would only be used for numbers and not be used for strings that are sometimes longer than the 64 bit limit like CHAP and SRP strings. That seems to be partially implemented in that the Kerbos and SPKM sections call for large-binary-values, but it was done incompletely.

Regards,
Pat

-----Original Message-----
From: Bill Studenmund [mailto:wrstuden@wasabisystems.com]
Sent: Tuesday, July 02, 2002 12:03 PM
To: THALER,PAT (A-Roseville,ex1)
Cc: LEMAY,KEVIN (A-Roseville,ex1); Julian_Satran@il.ibm.com;
ips@ece.cmu.edu
Subject: RE: iSCSI: Decimal encoding - why 64 bits ?


On Tue, 2 Jul 2002, THALER,PAT (A-Roseville,ex1) wrote:

> Bill,
>

> The decimal encoding is not just for numbers. It is also allowed for
> binary-values. Both CHAP and SRP exchange items that are identified as
> binary-values. In general these will be longer than 64 bits, but in
> cases where they are 64 bits or less the decimal encoding is currently
> allowed so we would have to support it.

I thought we had a big discussion about this, and we decided that decimal
was only used for numbers, hex for numbers and binary, and base64 only for
binary items. ??

Doh! I just looked in -14, and the text doesn't reflect that
understanding. Hmmm.

> The issue is that currently decimal encoding is allowed for
> binary-values and numbers less than 64 bits. There is little need for
> it over 32 bits. We have two other entirely adequate representations
> for those numbers. Why have something in there that causes extra code
> for no benefit?

All I can say is I thought it was removed. :-|

Take care,

Bill