Re: [netmod] IANA modules

Ladislav Lhotka <lhotka@nic.cz> Wed, 10 April 2019 13:04 UTC

Return-Path: <lhotka@nic.cz>
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 CA9F0120399 for <netmod@ietfa.amsl.com>; Wed, 10 Apr 2019 06:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 g_d_SWqOR3rZ for <netmod@ietfa.amsl.com>; Wed, 10 Apr 2019 06:04:37 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C09112012A for <netmod@ietf.org>; Wed, 10 Apr 2019 06:04:31 -0700 (PDT)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:9c6b:9bff:fee6:6583]) by mail.nic.cz (Postfix) with ESMTPSA id 7ECD3605AC; Wed, 10 Apr 2019 15:04:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1554901469; bh=yEaRkM9Zt4sswBXzlTWYlPdUzxSy3+wCo+MKZb3lTeo=; h=From:To:Date; b=QJALJ7KbtjW889BEI3ZFwjIAQazbT2ldnYB0UmstIEF/8vJ4s2/DdBzYKsbtyoCph JBH19qE/fmtL/r7uEQQUDrIw9sKDEONhXju29U9XFLowOpfo/e6stYB0aL3VJaXrMN KXfGuIzmZghtQ6B4/EpBx9cfFFnL3HgIPEjzNcs8=
Message-ID: <b0f4f047f70aaea32265ed51ec709855254a2758.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: netmod@ietf.org
Date: Wed, 10 Apr 2019 15:04:29 +0200
In-Reply-To: <20190410.142635.1128497654710441973.mbj@tail-f.com>
References: <b5666afbedc60cc53cb57f312563f2d1e1ee1e68.camel@nic.cz> <20190410.142635.1128497654710441973.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.0
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/TcvqfZL06bwYFNNLljixcpEifuI>
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 13:04:46 -0000

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.

- YANG Catalog doesn't know about the recent revisions of iana-if-type.

Lada

> 
> 
> 
> /martin
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67