On Wed, Jun 29, 2022 at 4:12 PM Carsten Bormann <[email protected]> wrote:

> >
> > Yes.  E.g, the constrained-voucher spec could define a new media type,
> ZANG-data+CBOR, which is defined to be almost identical to YANG-data+CBOR,
> except that in a few places (small matter of defining this properly, e.g.,
> based on SIDs) the encoding deviates.
> >
> >
> > There will be more optimizations that will be added over time.
> > Would it be possible to use a media-type parameter to identify each of
> the almost-identical variants?
>
> There could be a version number (zang-data+cbor; v=3), with increasing
> sets of optimizations being factored in at each version.
>
> > I new media type for each variant seems like too much cut-and-paste.
>
> A bit field (enumerating the powerset) would be another way, but would
> also be an interop testing nightmare.
>
>
A version or variant also requires both peers to agree on the supported
subset (if any).
Maybe better to forget any parameter.



> Grüße, Carsten
>
>
>
Andy
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima

Reply via email to