As mentioned in previous emails, acks are doing more than in 1.0. They
replaced Delivery Receipt which means that they can be used for
Non-repudiation of receipt. If you can't report an error when a received ack
doesn't conform to the CPA, fails to verify the signature or is missing the
ds:References than there would be no error reporting for a "receipt". This
would be a reduction in functionality from 1.0.
Cliff
>
>
> 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>
>