Identity/Verified Email Protocol: Difference between revisions
< Identity
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
== Next Steps == | == Next Steps == | ||
* Deal with TODOs in Verified Email doc | * Deal with TODOs in Verified Email doc | ||
** cert refresh - decide on long-lived (reusable) keys or not | |||
* Polish/expand session API specification doc | * Polish/expand session API specification doc | ||
* Security review | * Security review | ||
Revision as of 21:28, 24 May 2011
| Feature | Status | ETA | Owner |
| Verified Email Protocol | First draft done. Refining/polishing. | TBD | 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
- Deal with TODOs in Verified Email doc
- cert refresh - decide on long-lived (reusable) keys or not
- Polish/expand session API specification doc
- Security review
- Privacy review
Protocol Links
- Current
- Archived
Open Issues
Use Cases
Goals
Non-Goals
Other Documentation
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. |