Re: iSCSI/iWARP drafts and flow control

[Caitlin Bestler <cait@asomi.com>]

On Tuesday, July 29, 2003, at 08:58 PM, Mallikarjun C. wrote:

> However, it turns out that there are certain
> opcode types that are used very rarely that are not governed
> by the CmdSN-based flow control - immediate commands,
> SNACK, unsolicited NOP-In, Reject, and Async Messages.
>

Wouldn't the appropriate rule for SNACK messages be "don't"?

iSER is running on top of a reliable CRC32c error checked
transport protocol. What possible reason could there be
for requesting a retransmission? Especially when iSER
mandates that iSCSI payload authentication be turned off?