[openpgp] Re: Fwd: New Version Notification for draft-gall agher-openpgp-media-types-00.txt

Andrew Gallagher <[email protected]> Mon, 17 Nov 2025 22:23:18 +0000
Newsgroups gmane.ietf.openpgp
Message-ID <[email protected]>
On 17 Nov 2025, at 21:02, Daniel Kahn Gillmor <[email protected]> wrote:
> 
> With no hats on, i think i agree with Simon here -- when we start
> parameterizing, we create combinatorial complexity.  Combinatorics are
> great for extensibility, but we're not really looking for extensibility.
> we want a fixed name for a thing.

I think the fundamental question here is “how many things do we need to name?”

> The fact that some OpenPGP tooling can ingest an armored object the same
> way as a non-armored object is cute: application code that knows its
> OpenPGP tooling has that capacity can check the non-parameterized name
> and ignore the parameters in that case.

Right, but if the same media type represents both armored and non-armored formats, then we’re effectively mandating that cuteness into the future. And if we can’t use either content-encoding or parameters to denote armor, we leave an important metadata detail untepresentable (within an HTTP API context). 

A
_______________________________________________
openpgp mailing list -- [email protected]
To unsubscribe send an email to [email protected]