OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: T2 Clarify TimeToLive


A few comments below.

David

-----Original Message-----
From: Dan Weinreb [mailto:dlw@exceloncorp.com]
Sent: Saturday, September 15, 2001 10:47 PM
To: david.burdett@commerceone.com
Cc: arvola@tibco.com; david@drummondgroup.com;
ebxml-msg@lists.oasis-open.org
Subject: Re: T2 Clarify TimeToLive


   Date: Wed, 12 Sep 2001 11:51:38 -0700
   From: "Burdett, David" <david.burdett@commerceone.com>

   The spec already says that an error should be reported if the To MSH
   receives a message where Time To Live has passed. It doesn't though say
that
   the message must be ignored. This is a small useful clarification.

<DB>Section 10.2.3 says that if a message is received and it's time to live
has passed then an error message is generated with SEVERITY SET TO ERROR.
Any message which has a severity of ERROR is not processed.</DB>

It's not clear to me that an error should be reported in this case.

It must means that somewhere inside the Internet, a copy of this
message was passed along after a long delay.  This is inevitable,
particularly noting that messages can disappear into the Internet and
come back a *long* time later.  We are already assuming that this can
happen; it's part of our failure model.  So the fact that a late
straggling message came in is not evidence that anything is incorrect.

<DB>All this error message does is say that the message you sent me arrived
late. It might not be that useful, but I don't think we should change the
spec as it does not do any harm.</DB>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC