Overview

For all of you that wish OpenID had feature X or worked like Y, this is the OpenID Summit for YOU!

This Summit will be for participants ONLY.

You are either part of the Problem (you don't use OpenID because of X or Y and are willing to present), or you are part of the Solution (you are or will be active in an OpenID Working Group).

This is NOT a Summit for those that want to learn about OpenID.

We will start off after lunch on Monday, April 5th with short presentations about the Problem, followed by an evening of beer and food and lively discussion. 

Tuesday, April 6th will be a full day (starting at 9am) where we will have technology presentations, open space for ad hoc topics, and then next step discussions for Working Groups.

The 2010 theme for the OpenID Technical Committee is OpenID v Next. Our goal is to pull the community together so that we can understand what we collectively need the technology to do next, and kick off Working Groups to make that happen. This Summit is that start of the process. 

Agenda suggestions? Interested in giving a presentation? Other questions? Shoot specs@openid.net an email.

RSVP At

http://www.eventbrite.com/event/417522822

Time & Location

Microsoft

1065 La Avenida Street

Mountain View CA

Monday, April 05, 2010 at 12:00 PM - Tuesday, April 06, 2010 at 5:00 PM

Tentative Agenda

Day 1 (April 5th)

11:30-1pm - Lunch

1:00-1:15 - Kickoff

1:15-2:15 - Problem Talks A

• 1:15 - Eric Sachs (Google) - What OpenID needs to do in the future
• 1:30 - Bill Shupp (Digg) - Lessons learned from Digg's experience accepting OpenID
• 1:45 - Luke Shepard (Facebook) - Why OpenID doesn't work great for Facebook today
• 2:00 - Raffi Krikorian (Twitter) - Why doesn't OpenID make sense for Twitter today? (TBD)

2:45-3:45 - Problem Talks B

• 2:45 - Sabari Devadoss (Yahoo!) - Concerns/issues on adoption for ecommerce sites 
• 3:00 - TBD (LinkedIn) - Does OpenID fit into our perspective on the identity space?
• 3:15 - TBD (Palm) - What's missing from OpenID to make it rock on mobile?
• 3:30 - tbd 

4:15-5:15 - Problem Talks  C

• 4:15 - John Bradley (Protiviti) - What's missing for OpenID to be used in higher-security government deployments
• 4:30 - tbd
• 4:45 - tbd
• 5:00 - tbd

5:15 - Break

6:00 - Dinner/drinks nearby 

Day 2 (April 6th)

9:00-9:15 - Kickoff

9:15-10:15 - Solution Talks A

• 9:15 - Andrew Arnott - A JavaScript OpenID selector
• 9:30 - tbd
• 9:45 - Breno de Medeiros (Google) - Artifact binding for OpenID
• 10:00 - tbd

10:15-10:45 - Break

10:45-11:45 - Solution Talks B

• 10:45 - Eran Hammer-Lahav (Yahoo!) - WebFinger, LRDD, and service discovery (TBD)
• 11:00 - John Panzer (Google) - Magic signatures from Salmon (TBD)
• 11:15 - tbd
• 11:30 - tbd

noon - Lunch

1:00-2:00 - Open Space/Discussion (topic tbd)

2:30-3:30 - Open Space/Discussion (topic tbd) 

4:00-5:00 - New working group organization

5:30 - Drinks nearby

Hosts

Google & Microsoft

Possible topics

New features:

• enable discovery of additional classes of OpenID identifiers, including those utilizing e-mail address syntax,
• enable optimized protocol flows combining authentication, attribute release, and resource authorization,
• enable authentication to and use of attributes by non-browser applications,

User experience:

• enable less intrusive authentication user experiences than full-page browser redirect,
• enable support for a spectrum of clients, including passive clients per current usage, thin active clients, and active clients with OP functionality,

Attributes:

• include support for controlled release of attributes in the core specification,

Removing limitations:

• ensure the usability of OpenID on mobile devices,
• ensure the usability of OpenID on existing browsers with URL length restrictions,
• define profiles and support features intended to enable OpenID to be used at levels of assurance higher than NIST level 1,
• enable the use of public key technology to enhance scalability and performance. 

Possible breakout sessions

1. Additional technical and legal agreements for Open Identity Trust Framework providers for:
   1. Use of case of just synchronous e-mail validation (replacing the existing practice today of sending e-mail verification messages with unique links).
   2. Use of case of a website who wants to be PCI Compliant for traditional retail E-commerce transactions, and wants to be an IDP.
   3. If larger IDPs were to become RPs to each other, what type of OIX certification profile would be needed for those IDPs?
2. Governance Models
   1. Discuss the various governance models for Open Identity Trust Frameworks.