Re: [netmod] "iana" in yang modules' name/namespace/prefix

Benoit Claise <bclaise@cisco.com> Sun, 22 July 2018 13:54 UTC

Return-Path: <bclaise@cisco.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 D04A5130F29 for <netmod@ietfa.amsl.com>; Sun, 22 Jul 2018 06:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 0PIqUSbA2HXu for <netmod@ietfa.amsl.com>; Sun, 22 Jul 2018 06:54:22 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA17130E1D for <netmod@ietf.org>; Sun, 22 Jul 2018 06:54:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1522; q=dns/txt; s=iport; t=1532267661; x=1533477261; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=O/4g06ghRRj4rM6EHRW6Ql3wmDDeuFAY9FnqQjgqqu8=; b=gtioXSVcKKBEBPFNulYLetmw718dXyTYze+h2H9C9DYXI7GRGV6OAYUb OrN0wuz0/C8OFK2fngThRJ2V9QHVDPDHL4axEIt5x4v7a62lFQ6oz1cQ7 PTRSM2y3AA0Y8OwNIBCFYXFaEd4JXCOOqXC9uW1TJkNZX9th5wS9lsoPY Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A9BAAvi1Rb/5RdJa1cGwEBAQEDAQE?= =?us-ascii?q?BCQEBAYNNY38og36UNoFglWmBegsYC4QDRgKDDCE1FwECAQECAQECbRwMhTc?= =?us-ascii?q?CAQMBASEPAQU2GwsaAiYCAicwBgEMBgIBAYMcAYF/D65vgS6EXYVsBYELh3e?= =?us-ascii?q?BVz+BESeCaoMbAQGEYYJVAoxcjRAJjyoGiCCFUoxMhVWBQwE1gVIzGggbFTu?= =?us-ascii?q?CaYsVhVojMAGPEwEB?=
X-IronPort-AV: E=Sophos;i="5.51,389,1526342400"; d="scan'208";a="146588548"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jul 2018 13:54:21 +0000
Received: from [10.86.252.240] ([10.86.252.240]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTP id w6MDsKPq027365; Sun, 22 Jul 2018 13:54:20 GMT
To: Martin Vigoureux <martin.vigoureux@nokia.com>, netmod@ietf.org
References: <98a58631-0c57-7ed8-5277-5dcb3ee9dd86@nokia.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <0a82c50c-5cec-362d-208e-67d2c136a4bb@cisco.com>
Date: Sun, 22 Jul 2018 09:54:20 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <98a58631-0c57-7ed8-5277-5dcb3ee9dd86@nokia.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Outbound-SMTP-Client: 10.86.252.240, [10.86.252.240]
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/YarTXlzsfmv_ITLKmOfZ0oL2-DI>
Subject: Re: [netmod] "iana" in yang modules' name/namespace/prefix
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 22 Jul 2018 13:54:24 -0000

Martin,

I'm wonder whether this is really an important optimization, worth 
changing now, in the hypothetical case that IANA is not called IANA any 
longer in the future?
Right now, "iana" n the YANG module name correctly states what this is about
https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
     => "maintained by IANA"
I agree with Jürgen that documenting this in 6087bis is the right way 
forward.

Regards, Benoit.
> Hello
>
> As part of a recent IESG review (of draft-bfd-yang) a point came up on 
> the use of "iana" in yang modules' name/namespace/prefix.
> This is typically used in the case where the module refers to an IANA 
> maintained registry. However, the point raised was that the name of 
> the registry operator might not always be IANA, and that using that 
> name might not put modules on the most stable deployment footing under 
> all possible circumstances.
>
> On top of that, as far as I can tell, the use of "iana" is an 
> undocumented convention.
>
> So, I wanted to collect views:
> on whether a convention should be documented,
> and, with regards to the point raised in IESG, on whether that keyword 
> should be changed going forward. In that context, what about "reg" 
> (for registry) or "regop" (for registry operator)? Other proposals are 
> welcome.
>
> Thanks
> -m
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> .
>