[pnfs] [PATCH 12/17] Reroute a callback to be processed by thecallback service.

[Talpey, Thomas]

At 05:34 AM 5/22/2007, Benny Halevy wrote: 
>Like the spec says.  Keep returning errors or disconnect but you MUST NOT
>silently drop requests. Error handling should just escalate.  First return an
>error, then, if that doesn't help, disconnect the connection and re-establish
>the connection and back channel, then disconnect all connections and 

Agreed, absolutely the receiver should drop the connection. It's critical to the
ordering principle to not silently drop requests, and in the case of a wildly
misbehaving peer, I don't see what other recourse the receiver has. Trying
to salvage the protocol by violatiing it doesn't seem like it accomplishes
anything, the association is pretty much dead.

This does raise an interesting question of how a server protects itself from
a continuous invalid-request attack. But, I think that's another issue, and
can be resolved in the transport btw, through rate-limiting of repeated
incoming connections, etc.

Tom.