From sakimura at gmail.com  Wed Jun  3 03:23:30 2009
From: sakimura at gmail.com (Nat Sakimura)
Date: Wed, 3 Jun 2009 19:23:30 +0900
Subject: [Specs-cx] NRI Contribution Agreement
Message-ID: <bf26e2340906030323p7b645126mef3f3a6fceed925d@mail.gmail.com>

--0016e64ec8fc0a9437046b6f0d26
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I did not see my contribution agreement on the OIDF web so I am
posting it here as a proof.
It would probably have to be counter singed by Don, but to me, this
form is mysterious.
Just unilateral contribution should work...

Anyways,

Cheers,

-- 
Nat Sakimura (=nat)
http://www.sakimura.org/en/

--0016e64ec8fc0a9437046b6f0d26
Content-Disposition: attachment; 
	filename="NRI-Contribution-Agreement-CX.pdf"
X-Attachment-Id: f_fvhw263e0
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

A non-text attachment was scrubbed...
Name: NRI-Contribution-Agreement-CX.pdf
Type: application/pdf
Size: 152860 bytes
Desc: not available
URL: <http://openid.net/pipermail/specs-cx/attachments/20090603/38e1c87e/attachment-0001.pdf>

--0016e64ec8fc0a9437046b6f0d26--

From hdknr at ic-tact.co.jp  Thu Jun  4 23:53:53 2009
From: hdknr at ic-tact.co.jp (nara hideki)
Date: Fri, 5 Jun 2009 15:53:53 +0900
Subject: [Specs-cx] my contribution agreement
Message-ID: <c66ea5be0906042353v49c57bd8x4783ffc4bd33cd6a@mail.gmail.com>

--0015174c0fa80ccc2e046b945b63
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dear all

=hdknr has provided my contribution agreement on my pubic repository.

URL is here:
http://code.hdknr.com/OpenID/contribution-agreement-cx.pdf

Please tell me if there is something wrong with that.

Thanks.
-----
http://xri.net/=hdknr/(+resume)

--0015174c0fa80ccc2e046b945b63
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dear all<br><br>=hdknr has provided my contribution agreement on my pubic repository.<br><br>URL is here:<br><a href="http://code.hdknr.com/OpenID/contribution-agreement-cx.pdf">http://code.hdknr.com/OpenID/contribution-agreement-cx.pdf</a><br>
<br>Please tell me if there is something wrong with that.<br><br>Thanks.<br>-----<br><a href="http://xri.net/=hdknr/(+resume)">http://xri.net/=hdknr/(+resume)</a><br>

--0015174c0fa80ccc2e046b945b63--

From david.garcia at tractis.com  Fri Jun  5 02:45:02 2009
From: david.garcia at tractis.com (David Garcia)
Date: Fri, 5 Jun 2009 11:45:02 +0200
Subject: [Specs-cx] Contribution Agreement to for CX scpecs list
Message-ID: <7d9a3d920906050245s1a1a47d1o68cbe54a61c2bd5a@mail.gmail.com>

--001e6837894720f97d046b96bfd4
Content-Type: multipart/alternative; boundary=001e6837894720f95e046b96bfd2

--001e6837894720f95e046b96bfd2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

My name's Dave Garcia CTO at Tractis.com . I'm submitting the agreement.
Hope all needed data is filled but is something is missing or wrong please
contact me and I'll fix it at the moment.

In an additional way I want to offer the service that my company is offering
(online contracts) for free with no limit for this comitee If you want to
make this process faster allowing online agreement signing on our site.

Best regards

Dave Garcia

-- 
David Garcia
CTO

Tractis - Online contracts you can enforce
http://www.tractis.com
--
Tel: (34) 93 551 96 60 (ext. 260)

Email: david.garcia at tractis.com
Blog: http://blog.negonation.com
Twitter: http://twitter.com/tractis

--001e6837894720f95e046b96bfd2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>My name&#39;s Dave Garcia CTO at Tractis.com . I&#39;m submittin=
g the agreement. Hope all needed data is filled but is something is missing=
 or wrong please contact me and I&#39;ll fix it at the moment.<br><br>In an=
 additional way I want to offer the service that my company is offering (on=
line contracts) for free with no limit for this comitee If you want to make=
 this process faster allowing online agreement signing on our site.<br>
=A0
 <br clear=3D"all">Best regards<br><br>Dave Garcia<br><br>-- <br>David Garc=
ia<br>CTO<br><br>Tractis - Online contracts you can enforce<br><a href=3D"h=
ttp://www.tractis.com">http://www.tractis.com</a><br>--<br>Tel: (34) 93 551=
 96 60 (ext. 260) <br>
<br>Email: <a href=3D"mailto:david.garcia at tractis.com">david.garcia at tractis=
.com</a><br>Blog: <a href=3D"http://blog.negonation.com">http://blog.negona=
tion.com</a><br>Twitter: <a href=3D"http://twitter.com/tractis">http://twit=
ter.com/tractis</a><br>


--001e6837894720f95e046b96bfd2--
--001e6837894720f97d046b96bfd4
Content-Disposition: attachment; 
	filename="paper-contribution-agr-final-clean-20080107.doc"
X-Attachment-Id: f_fvkpkds00
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

A non-text attachment was scrubbed...
Name: paper-contribution-agr-final-clean-20080107.doc
Type: application/msword
Size: 128512 bytes
Desc: not available
URL: <http://openid.net/pipermail/specs-cx/attachments/20090605/c21daf16/attachment-0001.doc>

--001e6837894720f97d046b96bfd4--

From sakimura at gmail.com  Mon Jun  8 03:50:57 2009
From: sakimura at gmail.com (Nat Sakimura)
Date: Mon, 8 Jun 2009 19:50:57 +0900
Subject: [Specs-cx] Intro. to the concept behind CX
Message-ID: <bf26e2340906080350m7a60822bp518ad8a716c2187c@mail.gmail.com>

--0016361e88c65e8cd4046bd404a6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

=3Dhdknr is busily preparing the initial document for the current thought n=
ow
(which is going to be submit around Wednesday), but I will start introducin=
g
concept here little by little. (I thought of using wiki.openid.net but I di=
d
not know whether I can control the edits so that we do not get exposed to
IPR pollution, so I am doing it here.)

The main concept of the Contract Exchange is to exchange the public key
signed contract among =93parties=94. Basic model calls for two parties, wit=
h two
additional signatories. Under current situation, Signatories are typically
servers/services.

There will be a contract proposal (offer) on the table to start with. It is
signed by the Offerer. The signature achieves two things:

1) Non-repudiation: The offerer really made the offer.
2) Integrity: The accepting party cannot change the offer.

Once the accepting party reads the offer and agrees to it, the contract is
established, and to signify it, the accepting party will counter-sign the
document.

That=92s all what it does.
It could subsequently be used as a token to obtain further data or service,
i.e., just like an Access Token of OAuth.

The protocol that we have been talking at various venues (such as IIW) is
actually very simple. It is almost a simplified version of OAuth with a bit
of  tweaks.

So, now you understand: There are two important parts in CX.

1) Contract Format
2) Protocol to exchange signed contract.

Of the two, 2) is actually easier, as I mentioned above.

In the following posts, I will talk about each.


--=20
Nat Sakimura (=3Dnat)
http://www.sakimura.org/en/

--0016361e88c65e8cd4046bd404a6
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<p>=3Dhdknr is busily preparing the initial document for the current
thought now (which is going to be submit around Wednesday), but I will
start introducing concept here little by little. (I thought of using
<a href=3D"http://wiki.openid.net">wiki.openid.net</a> but I did not know w=
hether I can control the edits so
that we do not get exposed to IPR pollution, so I am doing it here.) </p>
	<p>The
main concept of the Contract Exchange is to exchange the public key
signed contract among =93parties=94. Basic model calls for two parties,
with two additional signatories. Under current situation, Signatories
are typically servers/services. </p>
	<p>There will be a contract proposal
(offer) on the table to start with. It is signed by the Offerer. The
signature achieves two things: </p>
	<p>1) Non-repudiation: The offerer really made the offer.<br>
2) Integrity: The accepting party cannot change the offer. </p>
	<p>Once
the accepting party reads the offer and agrees to it, the contract is
established, and to signify it, the accepting party will counter-sign
the document. </p>
	<p>That=92s all what it does.<br>
It could subsequently be used as a token to obtain further data or service,=
 i.e., just like an Access Token of OAuth. </p>
	<p>The
protocol that we have been talking at various venues (such as IIW) is
actually very simple. It is almost a simplified version of OAuth with a bit=
 of=A0
tweaks. </p>
	<p>So, now you understand: There are two important parts in CX. </p>
	<p>1) Contract Format<br>
2) Protocol to exchange signed contract. </p>
	<p>Of the two, 2) is actually easier, as I mentioned above. </p>
	<p>In the following posts, I will talk about each.
</p><br clear=3D"all"><br>-- <br>Nat Sakimura (=3Dnat)<br><a href=3D"http:/=
/www.sakimura.org/en/">http://www.sakimura.org/en/</a><br>

--0016361e88c65e8cd4046bd404a6--

From diana.r.almeida at gmail.com  Thu Jun 25 07:12:49 2009
From: diana.r.almeida at gmail.com (Diana Almeida)
Date: Thu, 25 Jun 2009 15:12:49 +0100
Subject: [Specs-cx] [specs-cx] My contribution agreement
Message-ID: <4A4385E1.9030208@dcc.fc.up.pt>

This is a multi-part message in MIME format.
--------------030902090900020304090002
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello all :)

In attachment i send my contribution agreement.

I had already send it to Nat and Don but i forgot to send it to the 
list, sorry.

Please let me know if something isn't wright.

Thanks,
Diana

--------------030902090900020304090002
Content-Disposition: inline;
 filename="Diana_Almeida_ContributionAgreement.pdf"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

A non-text attachment was scrubbed...
Name: Diana_Almeida_ContributionAgreement.pdf
Type: application/pdf
Size: 1054858 bytes
Desc: not available
URL: <http://openid.net/pipermail/specs-cx/attachments/20090625/0230a78e/attachment-0001.pdf>

--------------030902090900020304090002--

From sakimura at gmail.com  Wed Jun  3 10:23:30 2009
From: sakimura at gmail.com (Nat Sakimura)
Date: Wed, 3 Jun 2009 19:23:30 +0900
Subject: [Specs-cx] NRI Contribution Agreement
Message-ID: <bf26e2340906030323p7b645126mef3f3a6fceed925d@mail.gmail.com>

I did not see my contribution agreement on the OIDF web so I am
posting it here as a proof.
It would probably have to be counter singed by Don, but to me, this
form is mysterious.
Just unilateral contribution should work...

Anyways,

Cheers,

-- 
Nat Sakimura (=nat)
http://www.sakimura.org/en/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NRI-Contribution-Agreement-CX.pdf
Type: application/pdf
Size: 152860 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20090603/38e1c87e/attachment-0002.pdf>

From hdknr at ic-tact.co.jp  Fri Jun  5 06:53:53 2009
From: hdknr at ic-tact.co.jp (nara hideki)
Date: Fri, 5 Jun 2009 15:53:53 +0900
Subject: [Specs-cx] my contribution agreement
Message-ID: <c66ea5be0906042353v49c57bd8x4783ffc4bd33cd6a@mail.gmail.com>

Dear all

=hdknr has provided my contribution agreement on my pubic repository.

URL is here:
http://code.hdknr.com/OpenID/contribution-agreement-cx.pdf

Please tell me if there is something wrong with that.

Thanks.
-----
http://xri.net/=hdknr/(+resume)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20090605/57d81046/attachment.htm>

From david.garcia at tractis.com  Fri Jun  5 09:45:02 2009
From: david.garcia at tractis.com (David Garcia)
Date: Fri, 5 Jun 2009 11:45:02 +0200
Subject: [Specs-cx] Contribution Agreement to for CX scpecs list
Message-ID: <7d9a3d920906050245s1a1a47d1o68cbe54a61c2bd5a@mail.gmail.com>

Hi,

My name's Dave Garcia CTO at Tractis.com . I'm submitting the agreement.
Hope all needed data is filled but is something is missing or wrong please
contact me and I'll fix it at the moment.

In an additional way I want to offer the service that my company is offering
(online contracts) for free with no limit for this comitee If you want to
make this process faster allowing online agreement signing on our site.

Best regards

Dave Garcia

-- 
David Garcia
CTO

Tractis - Online contracts you can enforce
http://www.tractis.com
--
Tel: (34) 93 551 96 60 (ext. 260)

Email: david.garcia at tractis.com
Blog: http://blog.negonation.com
Twitter: http://twitter.com/tractis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20090605/c21daf16/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paper-contribution-agr-final-clean-20080107.doc
Type: application/msword
Size: 128512 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20090605/c21daf16/attachment-0002.doc>

From sakimura at gmail.com  Mon Jun  8 10:50:57 2009
From: sakimura at gmail.com (Nat Sakimura)
Date: Mon, 8 Jun 2009 19:50:57 +0900
Subject: [Specs-cx] Intro. to the concept behind CX
Message-ID: <bf26e2340906080350m7a60822bp518ad8a716c2187c@mail.gmail.com>

=hdknr is busily preparing the initial document for the current thought now
(which is going to be submit around Wednesday), but I will start introducing
concept here little by little. (I thought of using wiki.openid.net but I did
not know whether I can control the edits so that we do not get exposed to
IPR pollution, so I am doing it here.)

The main concept of the Contract Exchange is to exchange the public key
signed contract among ?parties?. Basic model calls for two parties, with two
additional signatories. Under current situation, Signatories are typically
servers/services.

There will be a contract proposal (offer) on the table to start with. It is
signed by the Offerer. The signature achieves two things:

1) Non-repudiation: The offerer really made the offer.
2) Integrity: The accepting party cannot change the offer.

Once the accepting party reads the offer and agrees to it, the contract is
established, and to signify it, the accepting party will counter-sign the
document.

That?s all what it does.
It could subsequently be used as a token to obtain further data or service,
i.e., just like an Access Token of OAuth.

The protocol that we have been talking at various venues (such as IIW) is
actually very simple. It is almost a simplified version of OAuth with a bit
of  tweaks.

So, now you understand: There are two important parts in CX.

1) Contract Format
2) Protocol to exchange signed contract.

Of the two, 2) is actually easier, as I mentioned above.

In the following posts, I will talk about each.


-- 
Nat Sakimura (=nat)
http://www.sakimura.org/en/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20090608/731f9c81/attachment.htm>

From diana.r.almeida at gmail.com  Thu Jun 25 14:12:49 2009
From: diana.r.almeida at gmail.com (Diana Almeida)
Date: Thu, 25 Jun 2009 15:12:49 +0100
Subject: [Specs-cx] [specs-cx] My contribution agreement
Message-ID: <4A4385E1.9030208@dcc.fc.up.pt>

Hello all :)

In attachment i send my contribution agreement.

I had already send it to Nat and Don but i forgot to send it to the 
list, sorry.

Please let me know if something isn't wright.

Thanks,
Diana
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Diana_Almeida_ContributionAgreement.pdf
Type: application/pdf
Size: 1054858 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20090625/0230a78e/attachment-0002.pdf>