legalxml-courtfiling — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [legalxml-courtfiling] Strawman non-repudiation issues
MHonArc v2.5.0b2 -->legalxml-courtfiling message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [legalxml-courtfiling] Strawman non-repudiation issues
- From: "Dallas Powell" <[email protected]>
- To: "Nick Pope" <[email protected]>,<[email protected]>,<[email protected]>
- Date: Wed, 4 May 2005 10:09:42 -0600
|
It is my understanding that we introduced the
Entity Seal that as provided by DSS to help create a new method of
non-repudiation that was separate from the messaging layer. We have also
agreed within Blue that there is a separation between authentication of the
message layer and who actually signs or approves the submission. Using the
message layer security would restrict any possible non-repudiation to just the
sender, which may not be the signer of the documents.
I have not had time to read the documents posted
yet, so I recognize that I have some work to do before I give further comment,
however, for each attachment there needs to be a block of data that includes the
information about who is authorizing or signing the document, and from New
Orleans we agreed to a either a hash or a digital signature per attachment, and
then strongly recommend the Entity seal around the package, and that all these
items be embedded within the envelope, which we now have agreed to in New
Orleans to be embedded in within the body element of SOAP. My
interpretation of this is that what we once referred to as the legalxml root
element is now the body element of SOAP. This does not mean that when you
use SOAP messaging layer you can eleminate the requirements within the
body.
Dallas
|