Did you want to be added as a prooser Phillip? -- Dick
On 2010-05-25, at 7:57 AM, Phillip Hallam-Baker <[email protected]> wrote: > This works for me > > On Mon, May 24, 2010 at 10:12 PM, Dick Hardt <[email protected]> > wrote: >> This is a formal submission to the OpenID Specs Council to approve >> the v.Next Core Protocol Working Group. >> Changes to since the last draft are: >> >> · evaluate mechanisms for providing redundancy >> >> · depreciate redundant or unused mechanisms >> >> -- Dick >> >> (a) Charter. >> >> (i) WG name: OpenID v.Next Core Protocol. >> >> (ii) Purpose: Produce a core protocol >> specification or >> family of specifications for OpenID v.Next that address the >> limitations and >> drawbacks present in OpenID 2.0 that limit OpenID’s applicability, >> adoption, >> usability, privacy, and security. Specific goals are: >> >> · define core message flows and verification methods, >> >> · enable support for controlled release of attributes, >> >> · enable aggregation of attributes from multiple attribute >> sources, >> >> · enable attribute sources to provide verified attributes, >> >> · enable the sources of attributes to be verified, >> >> · enable support for a spectrum of clients, including passiv >> e clients >> per current usage, thin active clients, and active clients with OP >> functionality, >> >> · enable authentication to and use of attributes by non-brow >> ser >> applications, >> >> · enable optimized protocol flows combining authentication, >> attribute >> release, and resource authorization, >> >> · define profiles and support features intended to enable Op >> enID to be >> used at levels of assurance higher than NIST SP800-63 v2 level 1 , >> >> · ensure the use of OpenID on mobile and other emerging devi >> ces, >> >> · ensure the use of OpenID on existing browsers with URL len >> gth >> restrictions, >> >> · define an extension mechanism for identified capabilities >> that are >> not in the core specification >> >> · evaluate the use of public key technology to enhance, secur >> ity, >> scalability and performance, >> >> · evaluate inclusion of single sign out >> >> · evaluate mechanisms for providing redundancy >> >> · complement OAuth 2.0 >> >> · minimize migration effort from OpenID 2.0 >> >> · seamlessly integrate with and complement the other OpenID >> v.Next >> specifications. >> >> · depreciate redundant or unused mechanisms >> >> Compatibility with OpenID 2.0 is an explicit non-goal for this work. >> >> (iii) Scope: Produce a next generation OpenID core >> protocol specification or specifications, consistent with the purpose >> statement. >> >> (iv) Proposed List of Specifications: OpenID >> v.Next Core >> Protocol and possibly related specifications. >> >> (v) Anticipated audience or users of the work: >> Implementers of OpenID Providers, Relying Parties, Active Clients, >> and >> non-browser applications utilizing OpenID. >> >> (vi) Language in which the WG will conduct business: >> English. >> >> (vii) Method of work: E-mail discussions on the >> working >> group mailing list, working group conference calls, and face-to-face >> meetings at the Internet Identity Workshop and OpenID summits. >> >> (viii) Basis for determining when the work of the >> WG is >> completed: Work will not be deemed to be complete until there is a >> rough >> consensus that the resulting protocol specification or family of >> specifications fulfills the working group goals. Additional proposed >> changes beyond that initial consensus 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 rough consensus on >> the draft >> has been achieved and there are two working, interoperating >> implementations, >> consistent with the purpose and scope. >> >> (b) Background Information. >> >> (i) Related work being done in other WGs or >> organizations: >> OpenID Authentication 2.0 and related specifications, including >> Attribute >> Exchange (AX), Contract Exchange (CX), Provider Authentication Policy >> Extension (PAPE), Artifact Binding (AB) and the draft User >> Interface (UI) >> Extension. OAuth 2.0, SAML 2.0 Core and SAML Authn Context. >> >> (ii) Proposers: >> >> Dick Hardt, [email protected] (chair) >> >> Michael B. Jones, [email protected] >> >> Breno de Medeiros, [email protected] >> >> Ashish Jain, [email protected] >> >> George Fletcher, [email protected] >> >> John Bradley, [email protected] >> >> Nat Sakimura, [email protected] >> >> Shade, [email protected] >> >> >> >> (iii) Anticipated Contributions: None. >> >> >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs >> >> > > > > -- > Website: http://hallambaker.com/ _______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
