|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: iSCSI: length and size
Julian,
I tend
to agree with Pat - this is an editorial issue
regarding
clarity of the document, and raising it is not
abuse of
the
WG Last Call process. It's ok to raise
the issue -
given your (document editor/primary author)
reluctance
to make the requested change, the WG co-chairs
will have to
make a decision about how to resolve this
(probably
around the end of the Last Call period) - one
possible
resolution is to decide that the document is ok
without the
change.
BTW - this
is a general principle of WG Last Call - the
WG co-chairs
have some discretion (particularly with editorial
comments) in
deciding whether an issue raised during WG
Last Call
requires changes in the draft.
Thanks,
--David
--------------------------------------------------- David L.
Black, Senior Technologist EMC Corporation, 42 South St., Hopkinton, MA
01748 +1 (508) 249-6449 *NEW* FAX: +1 (508)
497-8500 black_david@emc.com
Cell: +1 (978)
394-7754 ---------------------------------------------------
I don't understand
why you find that.
Pat
I
personally find this as an abuse of the last call process.
Julo
| pat_thaler@agilent.com
06/17/2002 07:14 PM Please respond to pat_thaler
| To:
Julian Satran/Haifa/IBM@IBMIL,
pat_thaler@agilent.com
cc: ips@ece.cmu.edu,
owner-ips@ece.cmu.edu
Subject: RE: iSCSI:
length and size
|
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
| "THALER,PAT
(A-Roseville,ex1)" <pat_thaler@agilent.com> Sent by: owner-ips@ece.cmu.edu
06/15/2002 02:50 AM Please respond to "THALER,PAT (A-Roseville,ex1)"
|
To:
Julian Satran/Haifa/IBM@IBMIL cc:
ips@ece.cmu.edu
Subject: iSCSI: length and
size
|
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
|