Re: [ebxml-msg] Issue 34: Reliable error delivery

[Doug Bunting <dougb62@yahoo.com>]

I've talked to a few other people who remained on the conference call after I had
to leave.  They mentioned "deferred" status was used to defer things to later
email discussions as well as to defer to 3.0.  In hopes we didn't leave this
technical conflict open until a much later specification, I'm raising the issue
via email.

thanx,
    doug

David Fischer wrote:

> This too, we went over at the Con Call and decided to mark as Deferred.
>
> David.
>
> -----Original Message-----
> From: Doug Bunting [mailto:dougb62@yahoo.com]
> Sent: Tuesday, February 12, 2002 4:55 PM
> To: ebXML
> Subject: [ebxml-msg] Issue 34: Reliable error delivery
>
> I agree we need a formal vote, again, on this issue though it was agreed to
> allow ack on error in previous meetings.  The current text already disallows
> Ack on Ack and Error on Error so Ack on Error can't result in a loop.  From a
> quick scan of the 1.0 document, I believe we supported Error on Ack in that
> version, meaning the current text in 7.3.1.4 and 7.3.2.8 reduces the feature
> set of our specification unnecessarily.
>
> I propose the following email motion: We formally accept that reliable errors
> are supported in ebXML Messaging.
>
> If necessary, this motion may be deferred until the next teleconference.  Ian?
>
> thanx,
>     doug
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>