|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iSCSI: length and sizeI don't understand
why you find that.
Pat
-----Original Message----- From: Julian Satran [mailto:Julian_Satran@il.ibm.com] Sent: Monday, June 17, 2002 9:54 AM To: pat_thaler@agilent.com Cc: ips@ece.cmu.edu; owner-ips@ece.cmu.edu; pat_thaler@agilent.com Subject: RE: iSCSI: length and size I personally find this as an abuse of the last call process. Julo
Julian, It is an issue for last call. Pat -----Original Message----- From: Julian Satran [mailto:Julian_Satran@il.ibm.com] Sent: Saturday, June 15, 2002 9:06 AM To: THALER,PAT (A-Roseville,ex1) Cc: ips@ece.cmu.edu; owner-ips@ece.cmu.edu Subject: Re: iSCSI: length and size Pat, Is this a wish or an issue for the WG last call? Julo
Julian, iSCSI-13 uses "length" quite a bit more than 100 times. Many of those times are in regard to the length of data, headers, and PDUs e.g. The basic header segment has a fixed length of 48 bytes. Expected Data Transfer Length Each PDU contains the payload length and the data offset.... It also uses size about 40 times with the same meaning as length. Most of these are the terms MaxBurstSize and FirstBurstSize and text associated with those terms. It would be better (less likely to confuse readers and better for those of us who look for information using search tools) to choose one of those terms and always use it when talking about length/size. I don't care which is chosen. Pat
Home Last updated: Tue Jun 18 20:18:45 2002 10875 messages in chronological order |