Identity/Verified Email Protocol: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 58: Line 58:


[[File:Verified_Email_Primary_Authority_Flow.jpg|200px|thumb|left|'''Protocol flow'''<br>Primary Authority + Relying Party verification using crypto]]
[[File:Verified_Email_Primary_Authority_Flow.jpg|200px|thumb|left|'''Protocol flow'''<br>Primary Authority + Relying Party verification using crypto]]
[[File:Verified_Email_Secondary_Authority_Flow.jpg|200px|thumb|left|'''Protocol flow'''<br>Secondary Authority + Relying Party verification using crypto]]


<br clear="all"/>
<br clear="all"/>

Revision as of 23:26, 11 May 2011

Feature Status ETA Owner
Verified Email Protocol Draft 1 on-schedule for 05.10 2011.05.10 Dan Mills

Summary

Team

Who's working on this?

  • Feature Manager: Dan Mills
  • Lead Author: Michael Hanson
  • Product Manager: Dan Mills
  • Security: Michael Coates
  • Privacy: Sid Stamm

Next Steps

  • Spec changes
    • Use certification flow (exclusively)
    • Rewrite to be more spec-like (MUSTs and so on)
    • Add nonces to assertions so they may be single-use
    • Add session API
  • Figure out delta from previous spec
  • Security review
  • Privacy review

Protocol Links

Current
Archived

Open Issues

Use Cases

Goals

Non-Goals

Other Documentation

Protocol flow
Primary Authority + Relying Party verification using crypto
Protocol flow
Secondary Authority + Relying Party verification using crypto


Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.