[OIDFSC] OpenID Artifact Binding Working Group Proposal

[David Recordon]

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.

Personally I'm worried about the additional complexity given a relatively
narrow group of implementors calling for the feature.

--David

On Fri, Feb 5, 2010 at 4:01 PM, John Bradley <john.bradley at wingaa.com>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 <sakimura at gmail.com> 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, breno at google.com. Google, Inc.
>>    - Hideki Nara, hdknr at ic-tact.co.jp, Tact Communications
>>    - Nat Sakimura, n-sakimura at nri.co.jp, Nomura Research Institute, Ltd.
>>     (editor)
>>    - John Bradley, ve7jtb at ve7jtb.com
>>    - Allen Tom, atom at yahoo-inc.com, Yahoo!
>>    - Will Norris, will at willnorris.com
>>
>> ------------------------------
>> *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
> specs at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20100205/0ffa4dbf/attachment-0001.htm>