On Sun, 29 Mar 2015, John R Levine wrote:
Second you should really have the email address listed as ID on you
openpgp key entry anyway.
I do, and thousands of subaddresses, too, and I'd like to let people send me
mail just like they do now, only encrypted.
This draft is about the use of openpgp and email. It is not a swiss-army
knife of email encryption. Note that I said "should have the email
address", and it is explictly not a requirement in the document, exactly
so you that do not need to add dozens of IDs if you do not want to.
Third, you can keep doing this fine and not receive encrypred email,
just like you have been doing all of those years.
I'm not very interested in a "solution" that doesn't match the way e-mail
works, and has worked for decades. At the session in Dallas, it was pretty
clear that the other people at the mike with extensive e-mail experience
aren't either.
You are confused about the document. This document is for:
OpenPGP is a message format for email (and file) encryption, that
lacks a standardized lookup mechanism to obtain OpenPGP public keys.
This document specifies a method for securely publishing and locating
OpenPGP public keys in DNS using a new OPENPGPKEY DNS Resource
Record.
It does not have as goal to design a method for ubiquitous email
encryption for all possible uses of email and encryption technologies.
I am happy to see that the openpgpkey draft reinvigorated the email people
into looking at a solution for the generic email address to recipient
mapping. I will keep a close eye on the progress made by the APP area
and email experts. I'd be happy to write up a bis document to the
openpgpkey document once the APP area has a draft document out on this
issue.
Paul
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
