Andy Bierman wrote:
>> 2) some kind of extension where when I *use* yang:ipv6-address that I
>> say that it should be encoded in CBOR using tag . Also specific
>> to that document/module, but the YANG knows. Russ speculated on the
>> ways in which one could use the right yang
On Sat, Jul 30, 2022 at 10:05 PM Carsten Bormann wrote:
> On 31. Jul 2022, at 02:12, Andy Bierman wrote:
> >
> > leaf foo {
> > type inet:ipv6-address;
> > ext:cbor-type cbor:bin-ipv6-address;
> > }
>
> This looks like the right thing to do.
> But it touches many moving
On 31. Jul 2022, at 02:12, Andy Bierman wrote:
>
> leaf foo {
> type inet:ipv6-address;
> ext:cbor-type cbor:bin-ipv6-address;
> }
This looks like the right thing to do.
But it touches many moving parts, and I’m wondering whether we cannot do
something with a more
Hi,
On Sat, Jul 30, 2022 at 1:54 PM Michael Richardson
wrote:
>
> I had a few (well.. two) hallway conversations about RFC9164 (IPv4/IPv6)
> tags
> for CBOR this week.
>
> Specifically... in large YANG described dumps (such as a BGP FIB table) it
> becomes critical not spend so many bytes on
I had a few (well.. two) hallway conversations about RFC9164 (IPv4/IPv6) tags
for CBOR this week.
Specifically... in large YANG described dumps (such as a BGP FIB table) it
becomes critical not spend so many bytes on some fundamental datatypes when
there are hundreds of thousands of entries.
