RE: [ebxml-msg] Receipt required and Non-Repudiation of receipt when the original user message is signed

["Pim van der Eijk" <pvde@sonnenglanz.net>]

Rong,

Whether or not a user message is (expected to be) signed is
determined by the Pmode[].Security.Sign parameter.

Whether or not a receipt is (expected to be) returned is
determined by the Pmode[].Security.SendReceipt parameter.

AS4 section 5.1.8 ties the two:  receipts are to be signed
if and only if the message they are receipts for are
(expected to be) signed.  Appendix B illustrates this using
XSLT.

Issue https://tools.oasis-open.org/issues/browse/EBXMLMSG-15
suggests that for AS4 the same should be said for errors. 

The ebMS 3.0 Core specification is missing a mechanism to
specify expected security of receipts and signals as Pmode
parameters.

Pim
 

-----Original Message-----
From: ebxml-msg@lists.oasis-open.org
[mailto:ebxml-msg@lists.oasis-open.org] On Behalf Of Rong
Xing
Sent: 01 July 2013 21:26
To: Theo Kramer; ebxml-msg@lists.oasis-open.org
Subject: [ebxml-msg] Receipt required and Non-Repudiation of
receipt when the original user message is signed

Hi Theo and all,

I have a question about receipt generation. 

First if the original User Message is digital signed, is the
receipt required to be generated and sent back by the
message receiver?

Secondly, if the receipt is to be generated, does the
receipt have to be non-repudiation (signed) also in the case
that the original User Message is signed? Or it can just be
Reception Awareness?

The spec seems not mandate these but I would like to ask for
confirmation.

Thanks,
Rong

------------------------------------------------------------
---------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_work
groups.php