|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: iSCSI: markers explanation
OK
The reason for this design is to keep the marker content independent of the marker interval.
Please note also that in calculating where to place markers you should assume that markers have been inserted everywhere (including Login) although they are not inserted during login. This will allow parties not to remember where login ended.
Julo
| "Eddy Quicksall" <Eddy_Quicksall@ivivity.com>
Sent by: owner-ips@ece.cmu.edu
14-12-01 19:12
|
To: "ips@ece. cmu. edu \(E-mail\)" <ips@ece.cmu.edu>
cc:
Subject: iSCSI: markers explanation
| |
Julian,
The explanation of markers says:
Anything counted in the TCP sequence-number is
counted for the offset. Specifically this includes any bytes
"inserted" in the TCP stream by an UFL and it excludes any other
markers inserted between the one we are examining and the next PDU
header.
The part that says “specifically” seems to contradict the previous sentence because the markers are counted in the TCP sequence-number. May I suggest changing it to:
With one exception, anything counted in the TCP sequence-number is
counted for the offset. Specifically this includes any bytes
"inserted" in the TCP stream by an UFL. The exception excludes any other
markers inserted between the one we are examining and the next PDU
header.
Eddy
Home
Last updated: Fri Dec 14 13:17:43 2001
8061 messages in chronological order
|