Carsten Bormann <[email protected]> wrote:
    >> (in general, I find the relationship between IANA Registries and YANG
    >> to be problematic.  Yes, IANA knows how to revise YANG modules when
    >> registries are updated, but this seems far too heavyweight to me)

    > It seems to me we want to have a well-defined way to generate a YANG
    > module that mirrors a registry directly from the registry without
    > manual intervention.  Repeatably doing that may add some requirements
    > to IANA’s registry management and to the stability of registry
    > representation.

Are you envisioning a XSLT or Python/Ruby/Perl/GO/ that
injests the CSV/XML of the registry and produces a YANG module?
That would just automate what IANA does, which is not silly.

But, I'm suggesting that YANG needs a way to reference a registry directly.
getservent(3)-ish, but not specific to services, or backed by /etc/services, 
etc.

    > (We'll likely have something in CDDL soon that does this [1] [2]; maybe
    > YANG can then learn from our mistakes…)

    > Grüße, Carsten

    > [1]:
    > 
https://www.ietf.org/archive/id/draft-bormann-cbor-cddl-2-draft-08.html#name-iana-references

Section A.2.1 _IANA references_ I guess.
Messy.

    > [2]:
    > 
https://www.ietf.org/archive/id/draft-bormann-cbor-rfc-cddl-models-07.html#name-dns-record-types

section 3.  3.2, ruby code, I think. (language not marked)

I think later binding is often needed.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [email protected]  http://www.sandelman.ca/        |   ruby on rails    [
]       My working hours and your working hours may be different.            [
]  Please do not feel obligated to reply outside your normal working hours   [


Attachment: signature.asc
Description: PGP signature

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

Reply via email to