At 08:56 AM 11/9/95 -0800, Ali Bahreman wrote:
Am I making sense saying that non-repudiation of "message receipt" is a
different service than non-repudiation of "receipt". The latter means that the
"receipt" is digitally signed, whereas the former implies that the recipient
cannot repudiate having received the message. These are two different services
and need two different mechanisms to support them.
Ali
The first asserts the MTS performed its delivery operation sucessfully, and
has proof/corroboration of this event.
X.402: "10.2.1.3 Proof of Delivery security service
This security service enables the originator of a message to obtain
corroboration that it has been delivered by the MTS to its
intended recipient(s)."
The second asserts that the MHS released the content to a user who
has provided a message to acknowlege receipt in a manner which protects
against denial of having originated *and sent* the ack.
F.435: "Proof of EDI notification: Enables the recipient of an EDIM to
create an
EDIN which may be used by the recipient of the EDIN to authenticate the
originator of the EDIN.
Non-repudiation of the EDI notification: Provides the recipient of
an EDIN with proof of the origin of the EDIN which will protect against any
attempt by the originator of the EDIN from falsely denying sending the EDIN."