<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="&#1;" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I believe that abstaining is acceptable.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>                                                                --
Mike<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
specs-council-bounces@openid.net [mailto:specs-council-bounces@openid.net] <b>On
Behalf Of </b>Brad Fitzpatrick<br>
<b>Sent:</b> Friday, January 30, 2009 10:26 AM<br>
<b>To:</b> David Recordon<br>
<b>Cc:</b> Johnny Bufu; Allen Tom; Mike Jones; specs-council@openid.net; Josh
Hoyt; Dick Hardt<br>
<b>Subject:</b> Re: [OIDFSC] [VOTE] Contract Exchange Working Group Proposal<o:p></o:p></span></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Can I vote neutral? &nbsp;While I'm very much +1 on the
previously discussed OpenID/OAuth hybrid proposal, this one's more
&quot;meh&quot; to me. &nbsp;I'm not against it, though. &nbsp;Its charter page
doesn't even explain use cases or what a &quot;contact&quot; is (though I was
amused to see it put in quotes and then later never explained.)<o:p></o:p></p>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<div>

<div>

<div>

<p class=MsoNormal>On Wed, Jan 28, 2009 at 11:09 AM, David Recordon &lt;<a
href="mailto:recordond@gmail.com">recordond@gmail.com</a>&gt; wrote:<o:p></o:p></p>

<p class=MsoNormal>Since we've had so many different threads on this proposal,
I'd like<br>
to have one final thread where there is a clear vote held on the<br>
latest revision of the proposal. &nbsp;The proposal can be found at<br>
<a href="http://wiki.openid.net/Working_Groups%3AContract_Exchange_1"
target="_blank">http://wiki.openid.net/Working_Groups%3AContract_Exchange_1</a>
and in the<br>
email below. &nbsp;If you're a member of the Specs Council, please respond<br>
ASAP.<br>
<br>
Thanks,<br>
--David<br>
<br>
(i) WG name<br>
Contract Exchange Extension Working Group<br>
<br>
(ii) Purpose<br>
The purpose of this WG is to produce a standard OpenID extension to<br>
the OpenID Authentication protocol that enables arbitrary parties to<br>
create and exchange a mutually-digitally-signed &quot;contract&quot;. This<br>
contract can be both broadband and mobile friendly through appropriate<br>
bindings that will be defined for each use case.<br>
<br>
(iii) Scope<br>
Development of a specification that allows parties to exchange a<br>
mutually-digitally-signed contract leveraging on OpenID Authentication<br>
2.0 and OpenID Attribute Exchange 2.0 via the appropriate bindings<br>
defined in the specification.<br>
<br>
Out of scope<br>
<br>
&nbsp; &nbsp;* UI and user experience: The Working Group will develop the wire<br>
protocol and and any related processing mechanisms required to support<br>
it but user interface and experience is out of scope.<br>
&nbsp; &nbsp;* Public Key Discovery method: This functionality will be either<br>
defined in the XRD 1.0 specification currently in progress at the<br>
OASIS XRI TC or a mechanism that works with OpenID Authentication<br>
2.0/2.1 discovery will be defined independently.<br>
&nbsp; &nbsp;* Terms negotiation: Actual negotiation of the terms of a contract<br>
should be dealt with out-of-band or by other specifications.<br>
&nbsp; &nbsp;* Assurance: These will be handled by third-party assurance<br>
programs or other identity governance frameworks.<br>
&nbsp; &nbsp;* Trust hierarchies. It is the intent that this specification be<br>
usable by any trust community, whether it uses conventional PKI<br>
hierarchies, peer-to-peer trust mechanisms, reputation systems, or<br>
other forms of trust assurance. The specification of any particular<br>
trust root, trust hierarchy, or trust policy is explicitly out of<br>
scope.<br>
<br>
(iv) Proposed List of Specifications<br>
&nbsp; &nbsp;* Contract Exchange 1.0 - Expected completion of the first<br>
iteration is in Q1 2009.<br>
<br>
(v) Anticipated audience or users of the work<br>
Implementers of OpenID Providers and Relying Parties, especially those<br>
who require security and accountability features to exchange sensitive<br>
customer information (e.g. personally identifiable information and<br>
credit card numbers) responsibly among trusted parties.<br>
<br>
(vi) Language in which the WG will conduct business<br>
English.<br>
<br>
(vii) Method of work<br>
E-mail discussions on the working group mailing list, working group<br>
conference calls, and possibly face-to-face meetings at conferences.<br>
<br>
(viii) Basis for determining when the work of the WG is completed<br>
Drafts will be evaluated on the basis of whether they increase or<br>
decrease consensus within the working group. The work will be<br>
completed once it is apparent that maximal consensus on the drafts has<br>
been achieved, consistent with the purpose and scope.<br>
<br>
(b) Background Information.<br>
(i) Related work being done by other WGs or organizations<br>
&nbsp; &nbsp;* OpenID Authentication 2.1 [AN]<br>
&nbsp; &nbsp;* OpenID Attribute Exchange Extension 2.0 [AX]<br>
&nbsp; &nbsp;* LIberty Alliance Identity Governance Framework [IGF] 1.0 Draft<br>
&nbsp; &nbsp;* XML Advanced Electronic Signatures [XAdES]<br>
&nbsp; &nbsp;* WS-Trust 1.3 [WS-trust]<br>
&nbsp; &nbsp;* XRI 2.0 and XRI 3.0 [XRI]<br>
&nbsp; &nbsp;* XRD 1.0 [XRI]<br>
&nbsp; &nbsp;* XDI 1.0 [XDI]<br>
&nbsp; &nbsp;* Vendor Relationship Management [VRM]<br>
<br>
(ii) Proposers<br>
&nbsp; &nbsp;* Drummond Reed, =drummond, <a
href="mailto:drummond.reed@parity.com">drummond.reed@parity.com</a>,<br>
Cordance/Parity/OASIS (U.S.A)<br>
&nbsp; &nbsp;* Henrik Biering, <a href="mailto:hb@netamia.com">hb@netamia.com</a>,
Netamia (Denmark)<br>
&nbsp; &nbsp;* Hideki Nara, <a href="mailto:hdknr@ic-tact.co.jp">hdknr@ic-tact.co.jp</a>,
Tact Communications (Japan)<br>
&nbsp; &nbsp;* John Bradeley, <a href="mailto:jbradley@mac.com">jbradley@mac.com</a>,
OASIS IDTrust Member Section (Canada)<br>
&nbsp; &nbsp;* Mike Graves, <a href="mailto:mgraves@janrain.com">mgraves@janrain.com</a>,
JanRain, Inc. (U.S.A.)<br>
&nbsp; &nbsp;* Nat Sakimura, <a href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>,
Nomura Research Institute, Ltd.(Japan)<br>
&nbsp; &nbsp;* Robert Ott, <a href="mailto:robert.ott@clavid.com">robert.ott@clavid.com</a>,
Clavid (Switzerland)<br>
&nbsp; &nbsp;* Tatsuki Sakushima, <a href="mailto:tatsuki@nri.com">tatsuki@nri.com</a>,
NRI America, Inc. (U.S.A.)<br>
&nbsp; &nbsp;* Toru Yamaguchi, <a href="mailto:trymch@gmail.com">trymch@gmail.com</a>,
DeNA Co. Ltd. &nbsp;(Japan)<br>
<br>
Editors:<br>
Nat Sakimura, <a href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>,
Nomura Research Institute, Ltd.<br>
<br>
(iii) Anticipated Contributions<br>
&nbsp; &nbsp;* Sakimura, N., et. al &quot;OpenID Trusted data eXchange
Extention<br>
Specification (draft)&quot;, Oct. 2008. [TX2008].<o:p></o:p></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

</div>

</div>

</div>

</body>

</html>