> Can you explain how this "information" somehow doesn't qualify as > "state". Doesn't the next expected sequence number at the very least > need to be updated? una? etc...?> > Could you also include the "non-state-full" information necessary to do > iSCSI header digest validation, data placement, and marker removal?

It's stateless because the full packet traverses the real networkingstack and thus can be treated like any other packet.

The data placement is a side effect that the networking stack cancompletely ignore if it chooses to.