[netmod] New top-level URN namespace for enterprise YANG module namespaces

Ing-Wher Chen <ing-wher.chen@ericsson.com> Tue, 17 November 2015 16:06 UTC

Return-Path: <ing-wher.chen@ericsson.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D661AD289 for <netmod@ietfa.amsl.com>; Tue, 17 Nov 2015 08:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 70s0kHzbyzYy for <netmod@ietfa.amsl.com>; Tue, 17 Nov 2015 08:06:28 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20C201AD1A3 for <netmod@ietf.org>; Tue, 17 Nov 2015 08:06:28 -0800 (PST)
X-AuditID: c618062d-f79ef6d000007f54-8f-564aee84585f
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id CE.98.32596.48EEA465; Tue, 17 Nov 2015 10:08:21 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0248.002; Tue, 17 Nov 2015 11:06:26 -0500
From: Ing-Wher Chen <ing-wher.chen@ericsson.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: New top-level URN namespace for enterprise YANG module namespaces
Thread-Index: AdEhUX1B+WwOM6WzT06mEJFjKcBhzw==
Date: Tue, 17 Nov 2015 16:06:26 +0000
Message-ID: <BF6E0BD839774345977891C597F8B50C213BF7C1@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyuXRPrG7rO68wg9cb2S3mX2xkdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxsq5zxkLbrBX9K9Zw9jAuJuti5GTQ0LARGLKx1/sELaYxIV7 64HiXBxCAkcYJZqn72KEcJYzSvzcO58VpIpNwEBiw8ctTCC2iIC6xMyd68EmCQt4SUy+8oUd Ih4o8aVrA5StJ9F5bR9YL4uAqsSU/8+AhnJw8Ar4Stx7kgUSZgRa/P3UGrCRzALiEreezGeC OEhAYsme88wQtqjEy8f/WCFsRYl9/dPZIep1JBbs/sQGYWtLLFv4GqyeV0BQ4uTMJywTGIVn IRk7C0nLLCQts5C0LGBkWcXIUVqcWpabbmSwiREYyMck2HR3MO55aXmIUYCDUYmH12CGV5gQ a2JZcWXuIUYJDmYlEV5OK+8wId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rz7l9wPFRJITyxJzU5N LUgtgskycXBKNTBuNTojrnQo4HNm5AGp9etUN6VI53/Lsr9m8sYosO7jqftxOr3c9wO8rv4v 3B2eve/1LpP0dYEpEezHjBbvuxa5+ONWSZ+AxTZ71hybzfW0LDRNgHHT6tNfut3D/z1fXfSC 8YLjpALPOe+k3mXJr7olXevgpbFuvvdzxu0txjqnVu63nH3o4udsJZbijERDLeai4kQAXsA+ A2ACAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/JQmD8yrUeuAwuHpBnqZV_mcuveU>
Subject: [netmod] New top-level URN namespace for enterprise YANG module namespaces
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Nov 2015 16:06:29 -0000

Hello,

In the netmod meeting during IETF in Yokohama, there was a
discussion on putting in place a guideline and a shortcut to easily
create globally unique URNs as enterprise YANG module namespaces.
For details, please see
<https://www.ietf.org/proceedings/94/slides/slides-94-netmod-5.pdf> or 
<https://datatracker.ietf.org/doc/draft-chen-netmod-enterprise-yang-namespace/> .
The gist of the proposal is to create globally unique enterprise
YANG module namespaces by creating URNs based on registered
domain names (DNS names), in reverse, e.g. urn:com:example:... .

During the meeting, there was a suggestion to create a new top-level
URN namespace, e.g. "rdns", to which reverse DNSnames are appended.

With a brand new top-level URN namespace, the resulting
enterprise YANG module namespace pattern would be something
like "urn:rdns:com:example:...".

For the new top-level URN namespace, are there any objections 
to using "rdns"?

Thanks,
Helen