RE: iSCSI Data Integrity - Digests

["Y P Cheng" <ycheng@advansys.com>]

> You are free to add non-standard TCP and perhaps both server and
> client may
> implement the same level of alteration. Change aggressiveness of the TCP
> congestion algorithm, force framing, implement non-standard definitions of
> urgent pointers, add special flags, and seldom seen options.  View TCP as
> important in name only or wire only.  An alternative to chaos generated by
> multitudes of such clever creations would be adoption of SCTP to provide
> options already found within this standard.

Doug,

May be I am mistaken, but I don't think what I am suggesting is doing
non-standard TCP.  What is a non-standard TCP if I follow all the RFCs
approved by IETF?  What I think you are referring to the non-standard
implementation, i.e., not working working with existing TCP stacks.

The urgent pointer, 32-bit TCP window, one segment per PDU, even with the
addition of SACK are all part of "standard" TCP, just not every TCP
implementations are supporting them.  This is why option negotiation comes
in.  I hope I am not mistaken.

Y.P.