Re: some numbering clarifications

[Matt Wakeley <matt_wakeley@agilent.com>]

Julian,

As Mallikarjun pointed out, you have conflicting paragraphs:

julian_satran@il.ibm.com wrote:

> 1.1.1     Ordering and iSCSI numbering
>
>    The NOP message PDUs are not associated with a task, are meant for
>    immediate delivery, and their only purpose is synchronizing the ordering
>    registers of the target and initiator.

Here you say NOPs are not associated with a task...


> 1.1.1.3   Data PDU numbering
>
>    Incoming Data PDUs MAY be numbered by a target to enable fast recovery
>    of long running READ commands.
>    Data PDUs are numbered with DataRN.  NOP command PDUs carrying the same
>    Initiator Tag as the Data PDUs are used to acknowledge the incoming Data
>    PDUs.  Support for Data PDU acknowledgement and the
>    maximum number of unacknowledged data PDUs are negotiated at login.
>    In a PDU carrying both data and status the number refers to the Status
>    and the last set of data blocks is implicitly acknowledged when Status
>    is acknowledged.

Here you say NOPs carry a task tag and are associated with the Data PDUs of a
task...

-Matt