Whether to include these amt.* in it as a generic item or not is what is needed to be discussed in the WG, I think. I have thrown those in as in most "contracts" these are needed. (Note: unit does not have to be a monetary one.) As a summary value, in the actual transactions, they happen to be pretty useful. <br>
<br>As to AX+SAML (or for that matter XAdES) is concerned, that is a valid approach, but if I were to use SAML, I would use XRDS based trusted discovery + ID-WSF (preferably RESTful version) rather than OpenID because it implies that you have SAML processor including XMLEncryption and XMLSig (which seems to hinder the adoption right now in many scripting language.) TX as it stands now is trying to avoid this issue by being purely tag-value based. Also, it is trying to be mobile friendly, which is kind of hard with AX partly because of its extensibility feature. Having said that, I think it is important to be able to translate TX message to SAML ro WS-Trust based messages for the harmonization reason. <br>
<br>Whether it has a future or not is not something a spec writer should determine, but it is something that the market should determine, IMHO. Is there an example of AX+SAML deployed and making transaction of monetary value right now or in the near future? An earlier version of TX is doing millions of dollars right now and is set to expand in the coming years (hopefully quite drastically.) You can start guessing by looking at the member list of OpenID Japan (note: not all of them are in the list. Some of them are still in process, and some of them would not like to be identified.) and why some "peculiar" variables are defined in the proposed TX spec. <br>
<br>=nat<br><br><div class="gmail_quote">On Sun, Nov 9, 2008 at 4:29 PM, David Recordon <span dir="ltr"><<a href="mailto:drecordon@sixapart.com">drecordon@sixapart.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">After reading the extension a few times, I'm getting caught up in 4.1.6 (<a href="http://svn.sourceforge.jp/cgi-bin/viewcvs.cgi/*checkout*/spec/openid-trust-exchange-1_0.html?root=openidtx#anchor7%29" target="_blank">http://svn.sourceforge.jp/cgi-bin/viewcvs.cgi/*checkout*/spec/openid-trust-exchange-1_0.html?root=openidtx#anchor7)</a> which references amounts being paid, currency, contracts, terms of the contract, etc. Overall, I'm pretty confused about what this extension does (it seems to do a lot of different things) which is making it hard for me to determine a better name. I also still feel that the reuse of AX (for it's extensibility) combined with the ability to exchange signed SAML tokens is a more future proof method and something that will be easier to be widely adopted as OpenID continues to evolve.<div>
<div><br></div><div>--David</div><div><br><div><div><div></div><div class="Wj3C7c"><div>On Nov 8, 2008, at 11:14 PM, Drummond Reed wrote:</div><br></div></div><blockquote type="cite"><span style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div link="blue" vlink="blue" lang="EN-US">
<div><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">+1. "OpenID Trust Extension" seems like a good fit.</span></font></div>
<div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">=Drummond</span></font></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></div>
</div></div><div style="border-style: none none none solid; border-left: 1.5pt solid blue; padding: 0pt 0pt 0pt 4pt;"><div><div></div><div class="Wj3C7c"><div><div style="margin: 0pt 0pt 0.0001pt; text-align: center; font-size: 12pt;" align="center">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;"><hr align="center" size="2" width="100%"></span></font></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma;"><span> </span><a href="mailto:specs-bounces@openid.net" target="_blank">specs-bounces@openid.net</a> [<a href="mailto:specs-bounces@openid.net" style="color: blue; text-decoration: underline;" target="_blank">mailto:specs-bounces@openid.net</a>]<span> </span><b><span style="font-weight: bold;">On Behalf Of<span> </span></span></b>Nat Sakimura<br>
<b><span style="font-weight: bold;">Sent:</span></b><span> </span>Saturday, November 08, 2008 12:22 PM<br><b><span style="font-weight: bold;">To:</span></b><span> </span><a href="mailto:david@sixapart.com" style="color: blue; text-decoration: underline;" target="_blank">david@sixapart.com</a><br>
<b><span style="font-weight: bold;">Cc:</span></b><span> </span><a href="mailto:specs@openid.net" style="color: blue; text-decoration: underline;" target="_blank">specs@openid.net</a><br><b><span style="font-weight: bold;">Subject:</span></b><span> </span>Re: Proposal to create the TX working group</span></font></div>
</div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Maybe just OpenID Trust Extension just like WS-Trust? </span></font></div>
<div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">=nat</span></font></div><div><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">On Sun, Nov 9, 2008 at 5:06 AM, Nat Sakimura <<a href="mailto:sakimura@gmail.com" style="color: blue; text-decoration: underline;" target="_blank">sakimura@gmail.com</a>> wrote:</span></font></div>
<div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Hi David, </span></font></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">I do not have any particular attachment to "trust exchange". So, I am ok in changing it but it would be nice if I can preserve "TX" acronym though. Do you have any specific suggestions? </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font color="#888888" face="Times New Roman" size="3"><span style="font-size: 12pt; color: rgb(136, 136, 136);">=nat</span></font></div><div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div>
<div><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">On Sun, Nov 9, 2008 at 3:50 AM, David Recordon <<a href="mailto:drecordon@sixapart.com" style="color: blue; text-decoration: underline;" target="_blank">drecordon@sixapart.com</a>> wrote:</span></font></div>
</div></div><div style=""><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Hi Nat,</span></font></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">Thanks. I still would really like to see the name changed for when we think about the World-wide market. Do others disagree? OpenID Trust Exchange just feels like it doesn't actually describe what the spec does nor how you can actually exchange "trust".</span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font color="#888888" face="Times New Roman" size="3"><span style="font-size: 12pt; color: rgb(136, 136, 136);">--David</span></font></div></div></div></div><div><div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div><div><div><div></div><div class="Wj3C7c"><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">On Nov 1, 2008, at 2:19 AM, Nat Sakimura wrote:</span></font></div>
</div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"><br><br></span></font></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Hi David, </span></font></div>
<div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Thanks for your comments. My reply inline below: </span></font></div>
</div></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div><div><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">2008/11/1 David Recordon <<a href="mailto:drecordon@sixapart.com" style="color: blue; text-decoration: underline;" target="_blank">drecordon@sixapart.com</a>></span></font></div>
<div style=""><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Hey Nat,</span></font></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">Do you see this as being built atop Attribute Exchange for transport or as something new that TX defines? I know Sxip had done work with AX to enable passing signed and encrypted attributes using SAML assertions.</span></font></div>
</div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">I have thought of using AX as transport once, then gave up on it when I was thinking of a mobile use case where the amount of payload that could be carried with was very limited (URL length in GET is limited to one of 128bytes, 256bytes or 512bytes depending on the handset). So, the current draft looks a lot like AX with bunch of hard coded attribute types in a way. </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">As far as carrying SAML token etc. in AX are concerned, similar thing has also been done by one of the proposer, Robert Ott of Clavid. Martin Paljak of Estonia (<a href="http://openid.ee" style="color: blue; text-decoration: underline;" target="_blank">openid.ee</a>) has been using XAdES with AX. </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">These approach are valid. However, I thought the approach partly defeats the purpose of OpenID. </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">If we were using SAML, then we could have used it through out. </span></font></div></div>
<div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">I wanted to make it easier for the developers by sticking to the tag-value approach. </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">This made us define some of the attribute types defined in SAML and XAdES to be defined as tag-value tag. </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><blockquote style="border-style: none none none solid; border-left: 1pt solid rgb(204, 204, 204); padding: 0pt 0pt 0pt 6pt; margin-left: 4.8pt; margin-right: 0pt;">
<div style=""><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">Is "Trust Exchange" really the best name? Seems like "trust" is quite a broad concept so something more specific might be better.</span></font></div>
</div></div></blockquote><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">Right. Naming was a bit problematic. I started using "Trust" because the messaging model is not dis-similar to WS-Trust. Now, the "trust" defined in WS-Trust in our context is essentially "Contract". So I thought of changing it to "CX" or something, but then, at least in Japan, quite a few key people were already exposed to "TX" by now and thus I kept the name "TX". </span></font></div>
</div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div></div></div><blockquote style="border-style: none none none solid; border-left: 1pt solid rgb(204, 204, 204); padding: 0pt 0pt 0pt 6pt; margin-left: 4.8pt; margin-right: 0pt;">
<div style=""><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">--David</span></font></div></div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div>
</div><div><div><div></div><div class="Wj3C7c"><div><div><div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">On Oct 31, 2008, at 4:21 AM, Nat Sakimura wrote:</span></font></div>
</div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div></div></div></div><blockquote type="cite" style="margin-top: 5pt; margin-bottom: 5pt;">
<div><div><div bgcolor="#ffffff" text="#000000"><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Dear Specification Council members:<span> </span><br>
<br>In accordance with the OpenID Foundation<span> </span><a href="http://openid.net/foundation/intellectual-property/" style="color: blue; text-decoration: underline;" target="_blank">IPR policies and procedures</a><span> </span>this note proposes the formation of a new working group chartered to produce an OpenID specification. As per Section 4.1 of the Policies, the specifics of the proposed working group are:</span></font></div>
<h3 style="margin-right: 0pt; margin-left: 0pt; font-size: 13.5pt; font-weight: bold;"><b><font face="Times New Roman" size="4"><span style="font-size: 13.5pt;"> </span></font></b></h3><h3 style="margin-right: 0pt; margin-left: 0pt; font-size: 13.5pt; font-weight: bold;">
<b><font face="MS PGothic" size="4"><span style="font-size: 13.5pt;">Trust Exchange (TX) Extension WG Charter</span></font></b></h3></div></div><div><div><p style="margin-right: 0pt; margin-left: 0pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"><div>
<div></div><div class="Wj3C7c">In accordance with the OpenID Foundation IPR policies and procedures this note proposes the formation of a new working group chartered to produce an OpenID specification. As per Section 4.1 of the Policies, the specifics of the proposed working group are:<br>
<br><br>Proposal:<br><br>(a) Charter.<br><br> (i) WG name: Trust Exchange Extension (TX)<br><br></div></div> (ii) Purpose: The purpose of this WG is to produce a standard OpenID extension to the OpenID Authentication protocol that enable<font color="navy"><span style="color: navy;">s</span></font>arbitrary parties to create and exchange<span> </span><font color="navy"><span style="color: navy;">a</span></font><span> </span>mutually<font color="navy"><span style="color: navy;">-</span></font>digitally<font color="navy"><span style="color: navy;">-</span></font>signed legally binding "contract". This protocol extension aims to be both broadband and mobile friendly by defining appropriate bindings for each use case. <div>
<div></div><div class="Wj3C7c"><br><br>Although this specification defines one default protocol for transfering data based on the contract, the data transfer portion is intended to be pluggable so that other protocols may also be used for this purpose.<span> </span><br>
<br><font color="black"><span style="color: black;">The extension is not intended to be a general method for defining attributes; the scope is limited to a specific set of attributes necessary for contract semantics. The extension will also define a contract signature based on public key cryptography. When used with a digital certificate signed by a third party, the contract and signature can be used as an assertion of conformance to an applicable assurance program.</span></font><br>
<br> (iii) Scope:<span> </span><br><br>Scope of the work</div></div></span></font></p><div><div></div><div class="Wj3C7c"><ul style="margin-bottom: 0pt;" type="disc"><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="MS PGothic" size="3"><span style="font-size: 12pt;"> Development of the specification including:</span></font></li></ul><ul style="margin-bottom: 0pt;" type="disc"><ul style="margin-bottom: 0pt;" type="circle">
<li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;">An extensible tag-value contract format</span></font></li><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="MS PGothic" size="3"><span style="font-size: 12pt;">Public Key Cryptography based digital signature method applied to the above contract format</span></font></li><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="MS PGothic" size="3"><span style="font-size: 12pt;">Query/response communication protocols for establishing the contract</span></font></li><li style="margin: 0pt 0pt 0.0001pt; color: navy; font-size: 12pt;"><font color="black" face="MS PGothic" size="3"><span style="font-size: 12pt; color: windowtext;">Default data transfer protocol based on the contract</span></font></li>
<li style="margin: 0pt 0pt 0.0001pt; color: navy; font-size: 12pt;"><font color="black" face="MS PGothic" size="3"><span style="font-size: 12pt; color: windowtext;">Conformance requirements for other data transfer protocol bindings</span></font></li>
</ul></ul><ul style="margin-bottom: 0pt;" type="disc"><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;">Security, threats and Risk analysis</span></font></li>
</ul><ul style="margin-bottom: 0pt;" type="disc"><ul style="margin-bottom: 0pt;" type="circle"><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;">Perform Security Risk analysis and profiles for best practice</span></font></li>
</ul></ul><p style="margin-right: 0pt; margin-left: 0pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"> Out of scope</span></font></p><ul style="margin-bottom: 0pt;" type="disc"><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">Term negotiation: Actual negotiation of the terms of a contract should be dealt with out-of-band or by other specifications.</span></font></li><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;">General purpose data type identifiers: this should be determined on a per-community bases using other specifications such as OpenID Attribute Exchange.</span></font></li>
<li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;">Assurance programs or other identity governance frameworks.</span></font></li><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="MS PGothic" size="3"><span style="font-size: 12pt;">It is the intent that this specification be usable by any trust community, whether it uses conventional PKI hierarchies, peer-to-peer trust mechanisms, reputation systems, or other forms of trust assurance. The specification of any particular trust root, trust hierarchy, or trust policy is explicitly out of scope.</span></font></li>
</ul><p style="margin-bottom: 12pt; margin-right: 0pt; margin-left: 0pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"><br> (iv) Proposed List of Specifications: TX 1.0, spec completion expected in January 2009.<br>
<br> (v) Anticipated audience or users of the work: Implementers of OpenID Providers and Relying Parties, especially those who require security and accountability features to exchange sensitive customer information (e.g. personally identifiable information and credit card numbers) responsibly among trusted parties.<br>
<br> (vi) Language in which the WG will conduct business: English.<br><br> (vii) Method of work: E-mail discussions on the working group mailing list, working group conference calls, and possibly face-to-face meetings at conferences.<br>
<br> (viii) Basis for determining when the work of the WG is completed: Draft 1 will be evaluated on the basis of whether they increase or decrease consensus within the working group. The work will be completed once it is apparent that maximal consensus on the draft has been achieved, consistent with the purpose and scope.<br>
<br>(b) Background Information.<br><br> (i) Related work being done by other WGs or organizations:</span></font></p><ul style="margin-bottom: 0pt;" type="disc"><li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"><a href="http://www.projectliberty.org/liberty/content/download/4329/28939/file/liberty-igf-draft-1.0-2008-06-21.zip" style="color: blue; text-decoration: underline;" target="_blank">LIberty Alliance Identity Governance Framework (IGF) 1.0 Draft</a></span></font></li>
<li style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"><a href="http://www.w3.org/TR/XAdES/" style="color: blue; text-decoration: underline;" target="_blank">XML Advanced Electronic Signatures (XAdES)</a></span></font></li>
</ul><p style="margin-bottom: 12pt; margin-right: 0pt; margin-left: 0pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"> <span> </span></span></font><br><font face="MS PGothic"><span> (ii) Proposers:</span></font></p>
<div><p style="margin-right: 0pt; margin-left: 0pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"> Drummond Reed,<span> </span><a href="mailto:drummond.reed@parity.com" style="color: blue; text-decoration: underline;" target="_blank">drummond.reed@parity.com</a>, Cordance/Parity/OASIS (U.S.A)<br>
Henrik Biering,<span> </span><a href="mailto:hb@netamia.com" style="color: blue; text-decoration: underline;" target="_blank">hb@netamia.com</a>, Netamia (Denmark)<br> Hideki Nara,<span> </span><a href="mailto:hdknr@ic-tact.co.jp" style="color: blue; text-decoration: underline;" target="_blank">hdknr@ic-tact.co.jp</a>, Tact Communications (Japan)<br>
John Bradeley,<span> </span><a href="mailto:jbradley@mac.com" style="color: blue; text-decoration: underline;" target="_blank">jbradley@mac.com</a>, OASIS IDTrust Member Section (Canada)</span></font><br> Mike Graves,<span> </span><a href="mailto:mgraves@janrain.com" style="color: blue; text-decoration: underline;" target="_blank">mgraves@janrain.com</a>, JanRain, Inc. (U.S.A.)<br>
Nat Sakimura,<span> </span><a href="mailto:n-sakimura@nri.co.jp" style="color: blue; text-decoration: underline;" target="_blank">n-sakimura@nri.co.jp</a>, Nomura Research Institute, Ltd.(Japan)<br> Robert Ott,<span> </span><a href="mailto:robert.ott@clavid.com" style="color: blue; text-decoration: underline;" target="_blank">robert.ott@clavid.com</a>, Clavid (Switzerland)<font face="MS PGothic"><span><br>
Tatsuki Sakushima,<span> </span><a href="mailto:tatsuki@nri.com" style="color: blue; text-decoration: underline;" target="_blank">tatsuki@nri.com</a>, NRI America, Ltd. (U.S.A.)<br> Toru Yamaguchi,<span> </span><a href="mailto:trymch@gmail.com" style="color: blue; text-decoration: underline;" target="_blank">trymch@gmail.com</a>, Cyboze Lab (Japan)</span></font></p>
<div><div><div><div><p style="margin-right: 0pt; margin-left: 0pt; font-size: 12pt;"><font face="MS PGothic" size="3"><span style="font-size: 12pt;"><br> Editors:<br><br> Nat Sakimura,<span> </span><a href="mailto:n-sakimura@nri.co.jp" style="color: blue; text-decoration: underline;" target="_blank">n-sakimura@nri.co.jp</a>, Nomura Research Institute, Ltd.<br>
<br> (iii) Anticipated Contributions: <span> </span><br> (1)<span> </span><a href="http://svn.sourceforge.jp/cgi-bin/viewcvs.cgi/*checkout*/spec/openid-trust-exchange-1_0.html?root=openidtx" style="color: blue; text-decoration: underline;" target="_blank">Sakimura, N., et. al "OpenID Trusted data eXchange Extention Specification (draft)", Oct. 2008. [TX2008]</a>.</span></font></p>
</div></div></div></div></div></div></div></div></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div></div></div><div>
<div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">_______________________________________________<br>specs mailing list<br>
<a href="mailto:specs@openid.net" style="color: blue; text-decoration: underline;" target="_blank">specs@openid.net</a><br><a href="http://openid.net/mailman/listinfo/specs" style="color: blue; text-decoration: underline;" target="_blank">http://openid.net/mailman/listinfo/specs</a></span></font></div>
</div></div></blockquote></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;">
<font face="Times New Roman" size="3"><span style="font-size: 12pt;"><br>_______________________________________________<br>specs mailing list<br><a href="mailto:specs@openid.net" style="color: blue; text-decoration: underline;" target="_blank">specs@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/specs" style="color: blue; text-decoration: underline;" target="_blank">http://openid.net/mailman/listinfo/specs</a></span></font></div></div></div></blockquote></div><div><div>
</div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"><br><br clear="all"><br>--<span> </span><br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" style="color: blue; text-decoration: underline;" target="_blank">http://www.sakimura.org/en/</a></span></font></div>
</div></div></div></div><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></div></div></div></div></div></div><div><div></div><div class="Wj3C7c">
<div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"><br><br clear="all"><br>--<span> </span><br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" style="color: blue; text-decoration: underline;" target="_blank">http://www.sakimura.org/en/</a></span></font></div>
</div></div></div></div></div></div><div><div></div><div class="Wj3C7c"><div style="margin: 0pt 0pt 0.0001pt; font-size: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"><br><br clear="all"><br>
--<span> </span><br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" style="color: blue; text-decoration: underline;" target="_blank">http://www.sakimura.org/en/</a></span></font></div></div></div></div></div>
</div></div></span></blockquote></div><br></div></div></div></blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br>