On 3/11/2016 4:51 AM, Paul Wouters wrote:
On Wed, 9 Mar 2016, Sean Leonard wrote:
Subject: [dane] "decoded local-part" for dane-smime and dane-openpgp
The problem is that this text does not distinguish between the
local-part production, and the decoded (unescaped) local-part
characters.
As I am discussing in another Internet-Draft elsewhere (in progress,
not necessary to cover right now here), the local-part has evolved
basically to be a string of Unicode scalar values, which may or may
not be escaped or quoted. Specifically:
It is therefore appropriate that the local-part be isolated from the
entire e-mail address production, and unescaped/unquoted (i.e.,
decoded). All three
I propose similar text for draft-ietf-dane-openpgpkey. Assuming we
have agreement, I can tackle that draft accordingly.
I believe the chairs stated that the experiments of dane for
openpgpkey and smime can continue without tackling every corner case
of local-parts. Fixing the local-parts is up to th email community,
not the dane community.
There is nothing to "fix" in this comment.
"paul"@nohats.ca
"p\a\u\l"@nohats.ca
paul(_at_)nohats(_dot_)ca
are all distinct e-mail address strings, that represent the local part:
paul
This is hardly a corner case; it's just the way that e-mail addresses work.
Are you saying that you believe that those three variations should
result in three different SHA-256 hashes?
Sean
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp