-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Marc" == Marc Mutz <Marc.Mutz@xxxxxxxxxxxxxxxx> writes: Marc> On Thursday 02 August 2001 21:35, Hubert Chan wrote: <snip> >> RFC2046, section 6 (Experimental Media Type Values): >> ,---- >> | Any format without a rigorous and public definition must be named >> | with an "X-" prefix... >> `---- >> >> I believe that is what Marc was referring to. >> >> So the MIME type should have been called "application/x-ms-tnef". Marc> <snip> Marc> Actually, they (MS) registered ms-tnef with IANA, but as Marc> application/vnd.ms-tnef. http://www.isi.edu/in-notes/iana/assignments/media-types/application/vnd.ms-tnef Hmm. The RFC says that the format needs a "public definition". Does this "public definition" mean the definition included in the referenced page? Or does it mean that the file format itself has to have a public definition? Judging from all the registered application/vnd.* types, I'm guessing the former (though I'd much more prefer the latter). - -- Hubert Chan <hackerhue@xxxxxxxx> - http://www.geocities.com/hubertchan/ PGP/GnuPG key: 1024D/651854DF71FDA37F Fingerprint: 6CC5 822D 2E55 494C 81DD 6F2C 6518 54DF 71FD A37F Key available at wwwkeys.pgp.net. Please encrypt *all* e-mail to me. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7adLiZRhU33H9o38RAtLgAJ99sIUnBR6KZcGkQCcc45C4RlpFsQCfYVC8 Pi0yGfvwdbCpcyzeqqgmprE= =eC8v -----END PGP SIGNATURE----- Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
