RE: Timeout on asynchronous MDNs

Since the AS2 internet draft (recently approved) does not require any
synchronization between processes before sending the MDN on a new TCP
connection, an application really must be prepared for receiving it at
any time after it has started sending. In particular, applications
cannot count on the original connection being seen as closed by both
sides before the MDN is sent. Someone from the testing side should say
whether there is something that they test in this regard, but from the
I-D itself, no mandatory synchronization (by some distributed mutex or
critical region guard) is present and so none should be expected before
sending/receiving the MDN.


Dale Moberg


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Joachim Just
Sent: Wednesday, February 02, 2005 8:31 AM
To: [email protected]
Subject: Timeout on asynchronous MDNs


Hi everybody,

I've got a question concerning the delay after which an asynchronous MDN

can be sent back. The draft paper does not say anything about this. To 
my understanding it only says it will be send in a separate TCP/IP 
session to the address and with the transport protocol specified in the 
"Receipt-Delivery-Option"  field.

When  conformance and interoperability tests are being done in the 
certification process are there any limits imposed when the requested 
asynchronous MDN can arrive?

I'll appreciate very much your comments.

Joachim Just