On Wed, Apr 08, 2020 at 12:58:41PM +0200, Carsten Bormann wrote: > On 2020-04-08, at 10:49, Carsten Bormann <[email protected]> wrote: > > > > One way to build a content-type from a media-type name is to add a > > parameter: > > > > application/yang-data+cbor; id=name > > application/yang-data+cbor; id=sid > > Ha. > > Let’s create a registry in yang-cbor for id= values (initially filled with > id=name). > -sid can then register id=sid in that.
He? yang-cbor defines how to use sids as ids so I see no reason to not also register the id=sid in yang-cbor. I thought we settled on yang-cbor defines what sids are and the sid id details how they are assigned and how the number space is managed. This way, yang-cbor is the base document and the sid document has a normative reference to yang-cbor and comi has a normative reference to yang-cbor. Is there a reason that speaks against this? /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
