Please see also https://www.ietf.org/id/draft-thaler-iftype-reg-04.txt.
Dave Thaler has a slot to present and discuss this I-D in in the INTAREA WG today (15:20-16:50)
Regards,
Dan
On Mon, Jul 22, 2019 at 9:57 PM Ladislav Lhotka <lhotka@xxxxxx> wrote:
On Mon, 2019-07-22 at 14:39 -0400, Michael Richardson wrote:
> Ladislav Lhotka <lhotka@xxxxxx> wrote:
> > The experience with other similar YANG modules indicates that the
> > process can actually work, see for example
>
> > https://www.iana.org/assignments/iana-if-type/iana-if-type.xhtml
>
> > For users of such modules, it is important to grab the latest revision
> > from IANA rather than use the initial revision that appeared in the
> > RFC. Perhaps this could be more strongly emphasized in the kick-off
> > RFCs.
>
> > While we can think about other procedures and mechanisms, I'd suggest
> > that we stick to the current procedure, until something better is
> > available.
>
> To be clear... the current proceedure is:
>
> 1) we publish an RFC with a YANG module in it, with the current IANA
> list from a registry in it.
>
> 2) as part of the publication, IANA extracts the YANG modules and puts
> it into a repository.
>
> 3) when IANA extends the registry, they update the YANG module.
Yes, and for the iana-if-types it has worked satisfactorily since 2014.
It is important though that domain experts (which is the DNSOP WG in the current
case) decide about the design of the YANG module and put together the initial
revision.
Lada
>
> --
> ] Never tell me the odds! | ipv6 mesh networks [
> ] Michael Richardson, Sandelman Software Works | network architect [
> ] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
>
>
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
