On Wed, Apr 8, 2020 at 3:58 AM Carsten Bormann <[email protected]> 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. > > Look, ma, no normative references! > > Grüße, Carsten > > PS. If you wonder why I care about normative references: RFC 7252 got > stuck for a year in 2013 for an ill-advised normative reference. And have > a look at > https://www.rfc-editor.org/current_queue.php#draft-ietf-anima-grasp — > 140+ weeks of waiting for a (totally unneeded) normative reference… > > draft-ietf-netmod-syslog-model-26 has been in MISREF state for 754 days and counting. Talk about ill-advised normative references...
Andy > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
