Re: [NGO] external module properties

Phil Shafer <phil@juniper.net> Tue, 29 April 2008 15:42 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 C6E773A6920; Tue, 29 Apr 2008 08:42:06 -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 C8B623A6920 for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 08:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bTc-fwKLV8Dt for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 08:42:02 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by core3.amsl.com (Postfix) with ESMTP id 2EB1B3A67CC for <ngo@ietf.org>; Tue, 29 Apr 2008 08:42:01 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP; Tue, 29 Apr 2008 08:41:27 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 29 Apr 2008 08:41:57 -0700
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m3TFfux39856; Tue, 29 Apr 2008 08:41:56 -0700 (PDT) (envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m3TFeJCa088074; Tue, 29 Apr 2008 15:40:19 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200804291540.m3TFeJCa088074@idle.juniper.net>
To: Andy Bierman <ietf@andybierman.com>
In-reply-to: <48173E9B.5000404@andybierman.com>
Date: Tue, 29 Apr 2008 11:40:19 -0400
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 29 Apr 2008 15:41:57.0794 (UTC) FILETIME=[8ED9F820:01C8AA0F]
Cc: NETCONF Goes On <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

Andy Bierman writes:
>The YANG spec is silent on finding the module associated
>with an import or include.  That doesn't mean a robust,
>interoperable, standards-based CM system can be silent on the issue.

This was intentional, in the same manner that the ANSI C spec doesn't
tell you about /usr/include, /usr/local/include, or the -I flag.
The language spec should be defining the language and the model of
operation.  Your tool set will dictate where and how it searches
for files.

Heck, my tool set may not even use files.

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