IETF Logo Mail Archive

Re: [netmod] IANA modules

tom petch <ietfc@btconnect.com> Fri, 12 April 2019 11:57 UTC

Return-Path: <ietfc@btconnect.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 488931201AF for <netmod@ietfa.amsl.com>; Fri, 12 Apr 2019 04:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 uPuX8mF6daJs for <netmod@ietfa.amsl.com>; Fri, 12 Apr 2019 04:57:31 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140100.outbound.protection.outlook.com [40.107.14.100]) (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 31E57120657 for <netmod@ietf.org>; Fri, 12 Apr 2019 04:57:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ri9/j7WGG8854GGLPnh7HpDWAtNhjP42GFF1N8MtI64=; b=Z1iIP4g3IY/xv5070h0WhhzqII6vaI58+nD7pkTobfR2abDTN2H18KGRnEYNgaI6XOY3eCpYoJ5uaOXKTCb8pjwcQaPh3WGfvRtQRYH2ofIIUN9czSuU4NKMsONht+xuv8gP5drhc0NxMDjG1ic9Aq25IpOeQmKgjebmzy655Rk=
Received: from DB7PR07MB5562.eurprd07.prod.outlook.com (20.178.46.212) by DB7PR07MB5690.eurprd07.prod.outlook.com (20.178.104.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1813.9; Fri, 12 Apr 2019 11:57:27 +0000
Received: from DB7PR07MB5562.eurprd07.prod.outlook.com ([fe80::89bf:8194:3f8c:ff65]) by DB7PR07MB5562.eurprd07.prod.outlook.com ([fe80::89bf:8194:3f8c:ff65%6]) with mapi id 15.20.1813.009; Fri, 12 Apr 2019 11:57:27 +0000
From: tom petch <ietfc@btconnect.com>
To: "lhotka@nic.cz" <lhotka@nic.cz>, Martin Bjorklund <mbj@tail-f.com>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] IANA modules
Thread-Index: AQHU8SbmQKl8JNYBnEKEMQy5H3Qumw==
Date: Fri, 12 Apr 2019 11:57:27 +0000
Message-ID: <05a701d4f126$7afded60$4001a8c0@gateway.2wire.net>
References: <b5666afbedc60cc53cb57f312563f2d1e1ee1e68.camel@nic.cz> <20190410.142635.1128497654710441973.mbj@tail-f.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0115.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:c::31) To DB7PR07MB5562.eurprd07.prod.outlook.com (2603:10a6:10:7b::20)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 616bc915-48d6-4c2b-735c-08d6bf3e0872
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:DB7PR07MB5690;
x-ms-traffictypediagnostic: DB7PR07MB5690:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <DB7PR07MB569005DD7D0DDB5064FEB624A0280@DB7PR07MB5690.eurprd07.prod.outlook.com>
x-forefront-prvs: 0005B05917
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(376002)(366004)(136003)(346002)(396003)(199004)(189003)(51444003)(13464003)(186003)(256004)(97736004)(106356001)(26005)(6506007)(386003)(81686011)(81816011)(105586002)(110136005)(102836004)(61296003)(316002)(476003)(76176011)(486006)(99286004)(52116002)(6116002)(2501003)(5660300002)(68736007)(446003)(3846002)(305945005)(4720700003)(229853002)(86362001)(1556002)(71190400001)(71200400001)(81156014)(53936002)(9686003)(6436002)(7736002)(8936002)(8676002)(44716002)(81166006)(62236002)(6246003)(2906002)(6306002)(6512007)(4326008)(86152003)(84392002)(14454004)(966005)(66066001)(50226002)(6486002)(44736005)(478600001)(14496001)(25786009)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB5690; H:DB7PR07MB5562.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 0PX+WmSMqTKOjEY/rHIwlCkaHXCP+GSVhZwcaqPS3r3NmBHAPKb/tb5rH2BOmuLN8DORa+jfs5cEmK73K/A+duE0df2ntvIbNMHDgTHgbzXy0WsTCFp+uQwAtsHYhEoAzQ25qHmLVnu18yae50973MCJjgwwHA0QLAdlBEy1GdiE28LCtV8F/U0ClXhnifCSmDrZ9oGWW117WUsTSCynC9K9tFOBeQqd4wQ+Tv7o+46Qyf8OeWbU2y/9ioxj2AKZ2/wGr02yRo66ZTk689wK6cREl3nNGuBnwcd6J4Kc/xkFB0zBAWyA6NSAjsEfffj5XIlRobRCQ3F/WBjEbz76wTT49ZKZS/eXwW5zbulq7jdcZqUntBFBct6EIG08VqekrX+BbfPp1b9rlfhHgPtGvhCZynujr2gON+bu56UFF9k=
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B11940F6039B12499DCD999210F0BB0B@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 616bc915-48d6-4c2b-735c-08d6bf3e0872
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2019 11:57:27.6434 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5690
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/RWAKdAR1I6AUhyZcpzZJ-zkN9SA>
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: Fri, 12 Apr 2019 11:57:34 -0000

I think that there is another issue at least for ifType.

Somewhere there is a discussion on

>  Title           : Guidelines and Registration Procedures for
Interface Types
>  Authors      : David Thaler
>                      Dan Romascanu
> Filename       : draft-thaler-iftype-reg-01.txt
> Pages           : 9
> Date            : 2019-03-05
>
> Abstract:
>    The registration and use of interface types ("ifType" values)
>    predated the use of IANA Considerations sections and YANG modules,
>    and so confusion has arisen about the interface type allocation
>    process.  This document provides updated guidelines for the
>    definition of new interface types, for consideration by those who
are
>    defining, registering, or evaluating those definitions

from which I sort of get a flavour of 'These OAM people have been
messing up our beautiful register of ifType with their untidy MIB and
YANG modules and it is time to take back control'!

I did ask on the Netconf list if anyone knew where it was being
discussed and got no reply.

Tom Petch


----- Original Message -----
From: "Martin Bjorklund" <mbj@tail-f.com>
To: <lhotka@nic.cz>
Cc: <netmod@ietf.org>
Sent: Wednesday, April 10, 2019 1:26 PM
Subject: Re: [netmod] IANA modules


> 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.
>
>
>
> /martin
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

v2.23.0 | Report a Bug | By Email