[ofw] RE: [PATCH] Support for ND over WV (incomplete)

[Sean Hefty]

>If the user wants to call Disconnect, they no longer need their outstanding
>NotifyDisconnect.  They can call CancelOverlappedRequests, and once the single
>overlapped is complete, they can reuse it to call Disconnect.

This ends up being awkward.  I'm hoping a way can be found that's as easy as
using the existing interface.  The user waits for NotifyDisconnect to complete,
then reuses the overlap for Modify.

The proposed changes work well for active/passive disconnect models.  They're
just difficult for peer to peer.  And unfortunately, since the current users of
the interface are libraries, they end up assuming peer to peer disconnect as the
worst case.

Maybe there's a clever way to tie the Modify to the NotifyDisconnect call,
rather than Disconnect, in certain cases.

- Sean