-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>
>
> There is a difference between being able to use the d= signing
> domain versus
> having deep knowledge about the underlying intent behind encoding
> choices for it.
>
> You know my name is David. You do not know why my parents chose
> that name, and
> it doesn't matter for your use of it as an identifier.
Let me riff on this for second.
We *don't* know your name is David. We commonly use the identifier
"Dave" for you, and while it's reasonable to suppose that Dave comes
from David, we don't know that. If a metaphorical i= has Dave there,
we can't back-translate to David, error-free.
I mention this because my father's given name is a common nickname. I
won't bore you with the tale of his immigrant father and
transliteration of names into the Roman character set, but you get the
picture.
Like i=, "Dave" is an opaque identifier. One can often peer into the
opacity and discover that it is translucent, but the process is not
error-free, and this is why we say in DKIM that it is opaque.
Jon
-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.6.3
Charset: US-ASCII
wj8DBQFJiv/VsTedWZOD3gYRAul4AKC6M2ZX8C836wI+Bg2DexE+tCK0YwCdGTN3
QTq0iHC4JnjbLzyIq+QDc2o=
=mD8I
-----END PGP SIGNATURE-----
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
