[YANG] [sub]module name uniqueness

Andy Bierman <ietf@andybierman.com> Fri, 04 April 2008 22:13 UTC

Return-Path: <yang-bounces@ietf.org>
X-Original-To: yang-archive@optimus.ietf.org
Delivered-To: ietfarch-yang-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 170C93A6A00; Fri, 4 Apr 2008 15:13:58 -0700 (PDT)
X-Original-To: yang@core3.amsl.com
Delivered-To: yang@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A57A3A6CF4 for <yang@core3.amsl.com>; Fri, 4 Apr 2008 15:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gh8y0RuQTzjY for <yang@core3.amsl.com>; Fri, 4 Apr 2008 15:13:56 -0700 (PDT)
Received: from smtp119.sbc.mail.sp1.yahoo.com (smtp119.sbc.mail.sp1.yahoo.com [69.147.64.92]) by core3.amsl.com (Postfix) with SMTP id C2D9B3A68AA for <yang@ietf.org>; Fri, 4 Apr 2008 15:13:56 -0700 (PDT)
Received: (qmail 95505 invoked from network); 4 Apr 2008 22:14:03 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.125.158.234 with plain) by smtp119.sbc.mail.sp1.yahoo.com with SMTP; 4 Apr 2008 22:14:02 -0000
X-YMail-OSG: _eEjaU8VM1lx7HVBZCE1dm_bYN2luBryZg0s.CrVwuhEjVwY
X-Yahoo-Newman-Property: ymail-3
Message-ID: <47F6A7F2.9050006@andybierman.com>
Date: Fri, 04 Apr 2008 15:13:06 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: yang <yang@ietf.org>
Subject: [YANG] [sub]module name uniqueness
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: yang-bounces@ietf.org
Errors-To: yang-bounces@ietf.org

Hi,

Sec 4.2.1 is silent on the requirement for module and sub-module
names to be unique, across some naming scope.  This is needed
for interoperability.

There are 3 options for processing import or include statements:

  1) modules and sub-module names are globally unique, and there can
     only 1 file that corresponds to a given import or include statement.

  2) there is some proprietary mechanism to determine which file
     is requested when more than 1 corresponds to the import or include
     statement value.

  3) there is some standard mechanism to determine which file
     is requested when more than 1 corresponds to the import or include
     statement value.

IMO, modules and submodules need to share the
same naming scope, and be globally unique.
All SMIv2 module names should also be considered part
of this naming scope, so that SMIv2 modules translated to YANG do
not conflict with new modules written in YANG.


Andy

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www.ietf.org/mailman/listinfo/yang