We submitted a new version of the email-reqs draft. This version is likely not perfect, but I wanted it to appear before the US Thanksgiving holiday so people have a chance to look at it before the interim meeting.
Text and requirements are cleaned up a bit and added example use cases for non-trivial requirements. Also added a new section of requirements that are not really DANE relevant, but added for completeness and just to have them documented somewhere. A new DANE type is probably not the ideal solution for all of these requirements. Comments welcome, now or during/after the interim meeting, Scott Begin forwarded message: > From: <[email protected]> > Subject: New Version Notification for > draft-osterweil-dane-ent-email-reqs-01.txt > Date: November 25, 2014 at 7:03:29 PM EST > To: Scott Rose <[email protected]>, Doug Montgomery <[email protected]>, "Doug > Montgomery" <[email protected]>, Scott Rose <[email protected]> > > > A new version of I-D, draft-osterweil-dane-ent-email-reqs-01.txt > has been successfully submitted by Scott Rose and posted to the > IETF repository. > > Name: draft-osterweil-dane-ent-email-reqs > Revision: 01 > Title: Enterprise Requirements for Secure Email Key Management > Document date: 2014-11-25 > Group: Individual Submission > Pages: 7 > URL: > http://www.ietf.org/internet-drafts/draft-osterweil-dane-ent-email-reqs-01.txt > Status: > https://datatracker.ietf.org/doc/draft-osterweil-dane-ent-email-reqs/ > Htmlized: > http://tools.ietf.org/html/draft-osterweil-dane-ent-email-reqs-01 > Diff: > http://www.ietf.org/rfcdiff?url2=draft-osterweil-dane-ent-email-reqs-01 > > 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. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > =================================== Scott Rose NIST [email protected] +1 301-975-8439 Google Voice: +1 571-249-3671 http://www.dnsops.gov/ https://www.had-pilot.com/ =================================== _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
