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] | [List Home]

Subject: RE: [ebxml-msg] CSD03 for AS4

Replying to this as it was copied in the AS4 draft spec:

I agree with you on the sequence acknowledgments,  but the
ebMS 2.0 receipt actually does seem to support NRR because
an eb2:Acknowledgment includes:

1) The unique identifier of the received message
2) A digest value(s) of the received message (parts)
3) A timestamp when the receipt occurred
4) A signature covering 1, 2 and 4 above

Here is an example (from a test message I generated years
ago) that illustrates (1)-(4):

        <eb:PartyId eb:type="string">Partner
      <ds:Reference URI=""
        <ds:Transforms><-- omitted --></ds:Transforms>


-----Original Message-----
From: Timothy Bennett [mailto:timothy@drummondgroup.com] 
Sent: 02 March 2011 22:00
To: ebxml-msg@lists.oasis-open.org
Subject: Re: [ebxml-msg] CSD03 for AS4

The use of the phrase 'business receipt' in AS4 was to
distinguish the nature of the AS4/ebMS3 receipt as being
sufficient for NRR (non-repuation of receipt).  In this
sense it is very similar to the
RFC3798 Message Disposition Notification response that is
used by AS2 as a business receipt for non-repudiation.  This
receipt in AS4/ebMS3 contains the same information as the
MDN, and thus distinguishes itself from the ebMS2
'acknowledgment' or web services reliable messaging

On 3/2/2011 7:26 AM, Theo Kramer wrote:
> My understanding of a 'business receipt' is exactly that,
ie. the business has received the message and the receipt is
the notification thereof.
> <snip>

To unsubscribe from this mail list, you must leave the OASIS
TC that generates this mail.  Follow this link to all your
TCs in OASIS at:

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