As I noted, there are many text-centric messaging channels that are in wide use but are not in any sense email. Um, I’m suggesting registering a media type for a message format that is: - specified in a standards-track RFC (See RFC4880, sections 2.4 and 6) - widely supported in software in a variety of programming languages (references on request) - currently being used in deployed apps (once again, see https://www.youtube.com/channel/UCZYI0JHoJCILEegRJsWufXQ) Media types are supposed to be useful for dispatching payloads in well-known formats to the appropriate software modules. Why is this controversial? Anyhow, this discussion has revealed that there apparently isn’t a registered media-type for this purpose, so I’ll write a draft and we’ll have something concrete to argue about. On Mon, Oct 13, 2014 at 5:58 PM, John Levine <johnl@xxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In article <2684567.G0MAaMzsuj@kitterman-optiplex-9020m> you write: >>I went back and looked at a random sampling of the PGP encrypted mails I've >>received over the last couple of years. 100% of them were multipart: > > You might want to check stuff that's PGP signed. In my experience, the > majority is still ASCII armored, not MIME. > > R's, > John > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlQ8dSoACgkQkEiFRdeC/kUYkQCfeGeIH7jsz5JiWRFSSPgSKZZu > 9lgAniY4RINAwBKJH9/4V4X/MIGnAkPi > =q6OX > -----END PGP SIGNATURE----- > -- - Tim Bray (If you’d like to send me a private message, see https://keybase.io/timbray)