On Sat, Feb 6, 2010 at 1:07 AM, David Recordon <[email protected]> wrote:
> I'm really weary of making non-compatible protocol changes > as separate efforts. If this is going to be done then it should happen > within the context of the main specification. As JohnB mentioned, it is just an additional layer. If the RP supports only the conventional one, it is fine. If the RP supports it but if OP does not, the RP can find it out and falls back to the POST binding. > > Personally I'm worried about the additional complexity given a relatively > narrow group of implementors calling for the feature. > Could you kindly define what you mean by "relatively narrow"? If you think it is only the proposers who wants this feature, you are mistaken. Also, from the implementation side, it is not that complex. Frankly speaking, I think OpenID will die if we do not support this kind of feature because it is not viable in the mobile world. > > --David > > > On Fri, Feb 5, 2010 at 4:01 PM, John Bradley <[email protected]>wrote: > >> This creates a new direct message type. I thought extensions were >> extending the existing messages. >> >> It is probably a grey area. >> >> Other protocols consider this to be a separate protocol binding rather >> than an extension of the redirect or POST binding. >> >> John B. >> >> >> On 2010-02-05, at 12:23 PM, David Recordon wrote: >> >> Hey Nat, >> Shouldn't this be considered an extension? >> >> --David >> >> On Fri, Feb 5, 2010 at 2:54 PM, Nat Sakimura <[email protected]> wrote: >> >>> *OpenID Artifact Binding Working Group* >>> ------------------------------ >>> *Charter Proposal* >>> 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 proposed >>> charter is below. >>> ------------------------------ >>> *I. Name* >>> Artifact Binding Working Group (AB) >>> ------------------------------ >>> *II. Statement of Purpose* >>> Produce a binding of OpenID requests and response (assertion) that uses >>> direct communication for main payload and indirect communication for a small >>> reference data called Artifact to cope with long URL limits experienced by >>> man >>> ------------------------------ >>> *III. Scope* >>> Create the Artifact Binding to support the identified needs. Currently >>> identified: >>> >>> - Cope with long url problem, especially for mobile browsers. >>> - Cope with the security problems of non-encrypted payload to go >>> through the user agents which may act as a man-in-the-middle. >>> >>> ------------------------------ >>> *IV. Specifications* >>> OpenID Artifact Binding 1.0 >>> ------------------------------ >>> *V. Anticipated audience* >>> All those interested in using OpenID in mobile and other constrained >>> browser and server elements. >>> ------------------------------ >>> *VI. Language of business* >>> English. >>> ------------------------------ >>> *VII. Method of work* >>> Mailing list discussion. Posting of intermediate drafts in the OpenID >>> Wiki. Virtual conferencing on an ad-hoc basis. >>> ------------------------------ >>> *VIII. Basis for completion of the activity* >>> The Artifact Binding 1.0 spec made final. >>> ------------------------------ >>> *Background Information* >>> ------------------------------ >>> *I. Related Work* >>> SAML Artifact Binding >>> OAuth >>> Wrap >>> Contract Exchange >>> ------------------------------ >>> *II. Initial Membership* >>> >>> - Breno de Medeiros, [email protected]. Google, Inc. >>> - Hideki Nara, [email protected], Tact Communications >>> - Nat Sakimura, [email protected], Nomura Research Institute, Ltd. >>> (editor) >>> - John Bradley, [email protected] >>> - Allen Tom, [email protected], Yahoo! >>> - Will Norris, [email protected] >>> >>> ------------------------------ >>> *III. Expected contribution* >>> >>> >>> Draft: OpenID Artifact Binding 1.0 - Draft 01, >>> http://www.sakimura.org/specs/ab/1.0/ >>> >>> -- >>> Nat Sakimura (=nat) >>> http://www.sakimura.org/en/ >>> http://twitter.com/_nat_en >>> >> >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs >> >> >> > -- Nat Sakimura (=nat) http://www.sakimura.org/en/ http://twitter.com/_nat_en
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
