[NGO] external module properties

Andy Bierman <ietf@andybierman.com> Sat, 26 April 2008 18:28 UTC

Return-Path: <ngo-bounces@ietf.org>
X-Original-To: ngo-archive@optimus.ietf.org
Delivered-To: ietfarch-ngo-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CF7A3A6D72; Sat, 26 Apr 2008 11:28:22 -0700 (PDT)
X-Original-To: ngo@core3.amsl.com
Delivered-To: ngo@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A08383A6D72 for <ngo@core3.amsl.com>; Sat, 26 Apr 2008 11:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level:
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[AWL=0.527, 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 5eVpnESQe89c for <ngo@core3.amsl.com>; Sat, 26 Apr 2008 11:28:19 -0700 (PDT)
Received: from smtp123.sbc.mail.sp1.yahoo.com (smtp123.sbc.mail.sp1.yahoo.com [69.147.64.96]) by core3.amsl.com (Postfix) with SMTP id 7D1FE3A6841 for <ngo@ietf.org>; Sat, 26 Apr 2008 11:28:19 -0700 (PDT)
Received: (qmail 58735 invoked from network); 26 Apr 2008 18:28:24 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.126.241.42 with plain) by smtp123.sbc.mail.sp1.yahoo.com with SMTP; 26 Apr 2008 18:28:22 -0000
X-YMail-OSG: GyME63sVM1mJBlbeG5JLZqvc2i3FsQVulXIwyMUcu62uPkaHzT9z54959tn.9xY0B82s0d_91JxFpOB89v3OfOQajznrKegQiMpr951bVVOgIoB.M1YjbK7X5EzABRfP6PA-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <48137444.6070802@andybierman.com>
Date: Sat, 26 Apr 2008 11:28:20 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: NETCONF Goes On <ngo@ietf.org>
Subject: [NGO] external module properties
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

Hi,

There is so much focus on the contents of a NETCONF data module,
that little attention has been paid to the 'external' properties.
I have already brought up module/submodule name uniqueness.

YANG does not have a concept of a module version, which is a mistake.
SMIv2 has LAST-UPDATED.  IMO, all YANG modules should have at
least 3 standard external properties:

   - name (matches import or include directive)
   - version (derived from most recent 'revision')
   - authoritative online module repository location

This implies that at least one revision-stmt MUST be present.
IMO, especially thinking for the long-term, it is not acceptable
to use ad-hoc non-standard mechanisms to identify the actual
module version.  LAST-UPDATED and REVISION are optional in SMIv2.
This is a mistake that should be fixed in YANG.

Another controversial external module property is 'schemaLocation' ;-)


Andy

_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo