-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 16 April 2004 11.24, Will Price wrote:
[...]
Email formats are becoming ever more complex. PGP/MIME is the only
standard solution on the table.
[...]
- some people are not able to or do not want to use PGP/MIME for
whatever reason
- PGP/MIME might be replaced by yet another standard in the future.
I think, since userid are quite tightly bound to email addresses, that a
way to tell the sender how the key owner expects to receive digitally
signed/encrypted email is something that would solve an actual problem.
Remember, rfc1847 is now almost 10 years old, and rfc2015[*] is 8 years
old, and still the dominant email client fails horribly on such
messages, and still inline signed email is widely in use (you said that
not many PGP product until recently supported PGP/MIME.) So I think
being friendly to users of legacy solutions is one lession one should
have learned by now in the IT world.
greetings
- -- vbi
[*] yes, I know the current standard is 3156, but I think the
differencies do not matter for mailers *not* supporting that standard.
In case the MIME rfcs are unclear on what to do with
multipart/<unknown> messages, rfc1847 should be enough for people to be
aware of the existence of such messages.
- --
featured link: http://fortytwo.ch/gpg/intro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: get my key from http://fortytwo.ch/gpg/92082481
iKcEARECAGcFAkB/sLFgGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h
aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjUmbWQ1c3VtPTVkZmY4NjhkMTE4NDMyNzYw
NzFiMjVlYjcwMDZkYTNlAAoJECqqZti935l6mlYAoI9BucT9hemvtz3tpTmxRFgs
dT1PAJ4uvlfcXXe0axNx/GBJUri05JIYPg==
=vlLu
-----END PGP SIGNATURE-----