[Specs-cx] Partial Contract for each party

[nara hideki]

Thank you for your comment.

Problem is that each party's privacy data must be encrypted its public key.
If 4 parties are included in a single contract, my PPIDs(me as an End
User) are all different from each other for each party so that
my OP must encrypt 4 times with different public keys. And OP should
send encrypted contract for each party at the time
the contract is provided for the purpose of party authentication.

Splitting a single contract into 4 partial contract could reduce the
encryption times because encryption for the party authentication is
enough
to keep the privacy from the other parties. Also it  simplify the
format fo the CX contract.

---
hideki nara

2010/8/28 John Bradley <ve7jtb at ve7jtb.com>:
> If any part of the document is RSA encrypted the time is constant.
>
> Only the symmetric key for the AES encryption is RSA encrypted.
>
> AES128 is relatively fast, so you will not save much by only encrypting part of the document.
>
> The same is true for signatures.
>
> John B.
> On 2010-08-27, at 1:36 AM, nara hideki wrote:
>
>> Hi experts.
>>
>> Contract files including all parties private data must be encryption intensive.
>> So I'm thinking of "partial contract" for each party to reduce RSA encryption.
>>
>> http://lafoglia.posterous.com/tag/partialcontract
>>
>> Rewriting draft 3 with this. Any idea is welcome.
>>
>> Thanks in advance.
>> ---
>> hideki nara
>> _______________________________________________
>> Specs-cx mailing list
>> Specs-cx at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-cx
>
>