[openpgp] Re: Fwd: New Version Notification for draft-gall agher-openpgp-media-types-00.txt
Simon Josefsson <[email protected]> Wed, 05 Nov 2025 17:14:54 +0100
| Newsgroups | gmane.ietf.openpgp |
|---|---|
| Message-ID | <[email protected]> |
Hi. I think this document is a great initiative -- media types for many old protocols and applications are often under-specified, and PGP isn't any exception. I'm happy to review the document. Re section 5 that introduces new media type parameters, is this documenting any existing deployment, or is this a purely new idea [that is open for discussion]? What do you think about not doing parametrization but instead define two separate self-contained media types for each format? For example: application/pgp-secret-keys application/pgp-secret-keys-unarmored or even text/pgp-secret-keys application/pgp-secret-keys although text/* is often complicated due to i18n concerns, and I suppose we use application/pgp-* for armored PGP blobs already so this would be a strange pattern. Compare with: application/pgp-secret-keys; armored=false application/pgp-secret-keys; armored=true which leads to the default value complexity. My experience with parametrized media types is that it creates implementation complexity and I've rarely seen this paramtrization contribute to anything over having two separate media types for each specific format. I may be missing some context here, maybe using a parameter is the only feasible approach because of some concern that I'm not seeing. /Simon Andrew Gallagher <[email protected]> writes: > Hi, all. > > I have uploaded a new draft (mainly so that I can reference it from > draft-hkp!) specifying some updates to the current OpenPGP entries in > the Media Types registry. In particular, this draft defines: > > * new media types `application/pgp-secret-keys` and `application/pgp-message` > * a media type parameter `armor`, with value `true` or `false`, to > indicate the use or lack of ASCII armor > > Together I believe these cover all the missing types of OpenPGP data > in common use. Comments welcome! > > Thanks, > A > >> Begin forwarded message: >> >> From: [email protected] >> Subject: New Version Notification for >> draft-gallagher-openpgp-media-types-00.txt >> Date: 8 August 2025 at 18:25:03 IST >> To: "Andrew Gallagher" <[email protected]> >> >> A new version of Internet-Draft draft-gallagher-openpgp-media-types-00.txt has >> been successfully submitted by Andrew Gallagher and posted to the >> IETF repository. >> >> Name: draft-gallagher-openpgp-media-types >> Revision: 00 >> Title: Media Types for OpenPGP >> Date: 2025-08-08 >> Group: Individual Submission >> Pages: 12 >> URL: >> https://www.ietf.org/archive/id/draft-gallagher-openpgp-media-types-00.txt >> Status: >> https://datatracker.ietf.org/doc/draft-gallagher-openpgp-media-types/ >> HTMLized: >> https://datatracker.ietf.org/doc/html/draft-gallagher-openpgp-media-types >> >> >> Abstract: >> >> This document updates the specification of existing media types, and >> specifies additional media types, for the identification of OpenPGP >> data in non-MIME contexts. >> >> >> >> The IETF Secretariat >> >> > > _______________________________________________ > openpgp mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ openpgp mailing list -- [email protected] To unsubscribe send an email to [email protected]
signature.asc
(application/pgp-signature, 1.2 KB)
-----BEGIN PGP SIGNATURE----- iQNoBAEWCAMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmkLd/4UHHNpbW9uQGpv c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh BLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XQkBQkNZGbwAAoJENc89jjFPAa+BtIA /iR73CfBurG9y8pASh3cbGOMHpDZfMAtosu6jbpO69GHAP4p7l57d+iVty2VQMsx +3TCSAvZkpr4P/FuTzZ8JZe8BrgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0 +MTXPPY4xTwGvgUCZ9F0SgUJDWRmSQCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE 8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J ENc89jjFPAa+wUUBAO64fbZek6FPlRK0DrlWsrjCXuLi6PUxyzCAY6lG2nhUAQC6 qobB9mkZlZ0qihy1x4JRtflqFcqqT9n7iUZkCDIiDbg4BFySz2oSCisGAQQBl1UB BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XTSBQkNZGboAAoJENc89jjF PAa+0M0BAPPRq73kLnHYNDMniVBOzUdi2XeF32idjEWWfjvyIJUOAP4wZ+ALxIeh is3Uw2BzGZE6ttXQ2Q+DeCJO3TPpIqaXDAAKCRBRcisI/kdFovq0AP9T01fG4Olr PB6nlVJkPxfph1HjtbfMPlAWSFFzQe5OmAD+OPd90Z9vFynF5D7hzHiAFEdQ4Fx2 jRoV/jQvoNjA1g4= =hEje -----END PGP SIGNATURE-----