Re: [NGO] external module properties

Andy Bierman <ietf@andybierman.com> Tue, 29 April 2008 00:10 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 BF7F53A6B13; Mon, 28 Apr 2008 17:10:19 -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 03EF628C220 for <ngo@core3.amsl.com>; Mon, 28 Apr 2008 17:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.116
X-Spam-Level:
X-Spam-Status: No, score=-2.116 tagged_above=-999 required=5 tests=[AWL=0.149, 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 yycGgcRwD0Kc for <ngo@core3.amsl.com>; Mon, 28 Apr 2008 17:10:12 -0700 (PDT)
Received: from smtp120.sbc.mail.sp1.yahoo.com (smtp120.sbc.mail.sp1.yahoo.com [69.147.64.93]) by core3.amsl.com (Postfix) with SMTP id DFBE83A6CDC for <ngo@ietf.org>; Mon, 28 Apr 2008 17:10:03 -0700 (PDT)
Received: (qmail 26432 invoked from network); 29 Apr 2008 00:10:06 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.126.241.42 with plain) by smtp120.sbc.mail.sp1.yahoo.com with SMTP; 29 Apr 2008 00:10:05 -0000
X-YMail-OSG: 3kPZeh8VM1mSfv.tXTAEsxpo3MIkG3g0dz41sI4pUT11wUJ2ekRMNRGD9KiuxMv.kRhFd4Lh125PCOe8cZOsQr2BosE691hcD_TjgGOM6HYyov4Y33ufzX4eKG80nLxOQpY-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4816675C.6060000@andybierman.com>
Date: Mon, 28 Apr 2008 17:10:04 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Martin Bjorklund <mbj@tail-f.com>
References: <48137444.6070802@andybierman.com> <sdr6cq83d2.fsf@wes.hardakers.net> <4815EA5E.60607@andybierman.com> <20080428.211816.17535040.mbj@tail-f.com>
In-Reply-To: <20080428.211816.17535040.mbj@tail-f.com>
Cc: ngo@ietf.org
Subject: Re: [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

Martin Bjorklund wrote:
> Hi,
> 
> While I agree with Juergen about the general idea that YANG should not
> try to enforce arbitrary rules on the user, in the case of 'revision'
> I think it falls into the same category as 'namespace' and 'prefix'.
> Neither is strictly speaking not required in all cases - a namespace
> is not needed if the module is a type library such as yang-types; a
> prefix is not needed if there are no local references in the module.
> 
> And I also agree that the revision might be needed for proper schema
> discovery.
> 
> I think I'd rather see all three mandatory than all three optional.
> 

agreed.

The easy part (if there is one) is having a standard version ID.

The hard part is determining what changes are allowed without
updating the version, and what changes are never allowed, even
if the version is updated.

This is where MUST for standards and SHOULD for vendors is needed.

> 
> /martin

Andy

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