[media-types] Re: Media types for draft-ietf-privacypass-bat ched-tokens

I have seen pushback when many media types are registered together,
especially when a parameter could have collapsed them.

That said, parameters are complexity which often folks are intentionally
avoiding.... String matching and parsing issues are a significant reason
for this avoidance.

This is probably a better question for DEs to answer.

OS, (no hats)

On Fri, Feb 27, 2026 at 12:11 PM Thibault Meunier <[email protected]>
wrote:

> Hi Orie,
>
> Existing Privacy Pass media types are not parametarised defined in RFC
> 9578 [1], so this aligns with them.
>
> Also, on the contrary to existing tokens defined in RFC 9578, for which
> parameterasation probably would have made sense when they where defined
> (`token_type` for instance), amortized and generic have actually different
> purposes and structure. I believe two media types for them makes it cleaner.
>
> As for request and responses, given there are only two, it feels simpler
> to fit them in the media-type.
>
> On the side, this made me wonder if parameters are common and if there are
> more risks on the implementation side. For instance, having unknown
> `tbd_mode` or a different ordering for `tbd_mode` and `tbd_type`.
>
> Thibault
>
>
> [1] https://datatracker.ietf.org/doc/html/rfc9578#name-media-types
> On Thursday, February 26th, 2026 at 17:45, Orie <[email protected]> wrote:
>
> > Hi,
> >
> > Why not use parameters?
> >
> > ```
> > application/privacy-pass-batch-token; tbd_mode=amortized/generic;
> tbd_type=request/response
> > ```
> >
> > Just a thought. (no hats)
> >
> > Regards,
> >
> > OS
> >
> >
> >
> >
> >
> > On Thu, Feb 26, 2026 at 10:37 AM Thibault Meunier <ot-ietf=
> [email protected]> wrote:
> >
> > > Hi IANA reviewers,
> > >
> > > One of the Privacy Pass working group document
> (draft-ietf-privacypass-batched-tokens) makes four media type registrations:
> > >
> > > 1. application/private-token-amortized-batch-request
> > > 2. application/private-token-amortized-batch-response
> > > 3. application/private-token-generic-batch-request
> > > 4. application/private-token-generic-batch-response
> > >
> > > The information for each is detailed in [1].
> > >
> > > Could folks please review?
> > >
> > > Thanks,
> > > Thibault
> > >
> > > [1]
> https://www.ietf.org/archive/id/draft-ietf-privacypass-batched-tokens-07.html#name-media-types
> > >
> > >
> > > _______________________________________________
> > > media-types mailing list -- [email protected]
> > > To unsubscribe send an email to [email protected]
>

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]