Enterprise Requirements for Secure Email Key Management
draft-osterweil-dane-ent-email-reqs-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Eric Osterweil , Scott Rose , Doug Montgomery | ||
| Last updated | 2015-05-29 (Latest revision 2014-11-25) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Individuals and organizations have expressed a wish to have the ability to send encrypted and/or digitally signed email end-to-end. One key obstacle to end-to-end email security is the difficulty in discovering, obtaining, and validating email credentials across administrative domains. This document addresses foreseeable adoption obstacles for encrypted and digitally signed email in enterprises, and outlines requirements. Some of the requirements below are not DANE specific, and all may not be solvable with a DANE solution, but are included for completeness and as an attempt to give a holistic view of enterprise email security requirements.
Authors
Eric Osterweil
Scott Rose
Doug Montgomery
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)