T2 Asynchronous Receipts

With large files it is often not advisable to block open the HTTP(S) connection
while waiting for decryption or Hash/MIC generation.  This would be a case where
a basic Ack would be sent back to the previous hop, the connection would be
dropped, the DeliveryReceipt would be generated and the reverse connection
re-established for delivery of the DeliveryReceipt.  This would be called
Asynchronous Receipts.  How would this behavior be represented using the current
headers?

All this is still non-business level activity since it ONLY applies to
security-level encryption or signature generation/verification.  This would
still be within our scope.

This might be new functionality.  If so, then this should go to T3.

Regards,

David Fischer
Drummond Group.