Re: [netmod] IANA modules

Martin Bjorklund <mbj@tail-f.com> Wed, 10 April 2019 14:19 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16F3512012E for <netmod@ietfa.amsl.com>; Wed, 10 Apr 2019 07:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPtgGQtjsZst for <netmod@ietfa.amsl.com>; Wed, 10 Apr 2019 07:19:26 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id D4683120006 for <netmod@ietf.org>; Wed, 10 Apr 2019 07:19:25 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 32BD91AE0312; Wed, 10 Apr 2019 16:19:23 +0200 (CEST)
Date: Wed, 10 Apr 2019 16:19:25 +0200 (CEST)
Message-Id: <20190410.161925.1650103041187977910.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <2b7e7a35d12f273f8fea55aded8f06987afd37b7.camel@nic.cz>
References: <b0f4f047f70aaea32265ed51ec709855254a2758.camel@nic.cz> <20190410.151506.1911583674051661049.mbj@tail-f.com> <2b7e7a35d12f273f8fea55aded8f06987afd37b7.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/t1Yf89CkS2K7MiPmEsFwa9GSLIU>
Subject: Re: [netmod] IANA modules
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 14:19:28 -0000

Ladislav Lhotka <lhotka@nic.cz>; wrote:
> Martin Bjorklund píše v St 10. 04. 2019 v 15:15 +0200:
> > Ladislav Lhotka <lhotka@nic.cz>; wrote:
> > > Martin Bjorklund píše v St 10. 04. 2019 v 14:26 +0200:
> > > > Ladislav Lhotka <lhotka@nic.cz>; wrote:
> > > > > Hi,
> > > > > 
> > > > > in a discussion in the yang-doctors mailing list, Acee noted that
> > > > > IANA probably hasn't yet implemented a procedure for updating YANG
> > > > > modules corresponding to IANA registries
> > > > 
> > > > I think that this is a false alarm.  IANA updates the modules
> > > > according to the process.
> > > > 
> > > > > (such a procedure is
> > > > > specified, e.g., in the IANA Considerations section of RFC 7224). It
> > > > > indeed seems to be the case - for example, a few new interface types
> > > > > have been added recently to
> > > > > 
> > > > > https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib
> > > > > 
> > > > > but the module iana-if-type only exists in revision 2014-05-08.
> > > > 
> > > > See
> > > > https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
> > > > 
> > > > The latest version is iana-if-type@2019-02-08.yang
> > > > 
> > https://www.iana.org/assignments/yang-parameters/iana-if-type@2019-02-08.yang
> > > > 
> > > > 
> > > > > A part of the problem may be that there is AFAIK no authoritative
> > > > > repository for
> > > > > YANG modules where IANA could put the new revisions.
> > > > 
> > > > See
> > > > https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
> > > > 
> > > > This is the authoritative repo.  IANA gets new YANG modules directly
> > > > from the RFC editor before they are formatted into the ascii RFC.
> > > 
> > > Hmm, but then it is kept pretty secret:
> > > 
> > > - RFC 6020 only specifies the new registry "YANG Module Names" and media
> > types
> > > in IANA Considerations, not this authoritative module repository.
> > 
> > RFC 6020 defines the registry.  IANA maintains the registry.  The link
> > above is the link to this registry.  If you go to iana.org and search
> > for "YANG Module Names" this link is the first to be shown.
> 
> According to RFC 6020, it is "a registry for YANG module and submodule names".
> Maybe I am ignorant, but I really didn't know that complete modules can also be
> retrieved. Also, it seems that only the most recent revision of the iana-*
> modules is kept there.

Right.  So the relevant RFC is really RFC 7224, which defines the
initial version of iana-if-type, and the rules for when to update it.

Technically, there's a new IANA registry called "iana-if-type YANG
Module", which is found here:
https://www.iana.org/assignments/iana-if-type/iana-if-type.xhtml


The fact that you can download the other YANG modules is a bonus ;-)


/martin




> 
> > 
> > 
> > > - YANG Catalog doesn't know about the recent revisions of iana-if-type.
> > 
> > That's a completely different issue!
> 
> Of course, but it shows that learning about existing modules & revisions (even
> the standard ones) isn't particularly easy.
> 
> Lada
> 
> > 
> > 
> > /martin
> -- 
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
>