Re: [NGO] external module properties

Andy Bierman <ietf@andybierman.com> Sun, 27 April 2008 13:21 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 12E333A6B94; Sun, 27 Apr 2008 06:21:34 -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 247393A6C95 for <ngo@core3.amsl.com>; Sun, 27 Apr 2008 06:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.964
X-Spam-Level:
X-Spam-Status: No, score=-1.964 tagged_above=-999 required=5 tests=[AWL=0.301, 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 KRMopBeePRh7 for <ngo@core3.amsl.com>; Sun, 27 Apr 2008 06:21:32 -0700 (PDT)
Received: from smtp116.sbc.mail.sp1.yahoo.com (smtp116.sbc.mail.sp1.yahoo.com [69.147.64.89]) by core3.amsl.com (Postfix) with SMTP id 719543A6C6C for <ngo@ietf.org>; Sun, 27 Apr 2008 06:21:32 -0700 (PDT)
Received: (qmail 75481 invoked from network); 27 Apr 2008 13:21:36 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.126.241.42 with plain) by smtp116.sbc.mail.sp1.yahoo.com with SMTP; 27 Apr 2008 13:21:35 -0000
X-YMail-OSG: IvWTUv4VM1nBMnsYKNmblLHaWZRCeUdUzJOqsYZTJ268OQBEFl0UEDgPufQu.hhBwp2llo98FrKqLM65Efp5P6YHdYcuDMSqERiK4keWO7c5_82hUcOrfnk1MLlWgg8H2pM-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <48147DDD.9060203@andybierman.com>
Date: Sun, 27 Apr 2008 06:21:33 -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: <4813A0EC.50209@andybierman.com> <20080427061550.GB22643@elstar.local> <48145349.2030602@andybierman.com> <20080427.131919.130156558.mbj@tail-f.com>
In-Reply-To: <20080427.131919.130156558.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:
> Andy Bierman <ietf@andybierman.com> wrote:
>>> Namespace information is needed for parsers to work properly in case
>>> of identifier clashes. And I am sure the IETF will require that
>>> revision clauses are present in YANG modules. But this is not a
>>> technical requirement of the language itself; it is a usage guideline
>>> requirement. I believe this distinction is worthwhile to make.
>>
>> no -- the prefix is needed for the language parser.
>> The namespace URI string isn't used anywhere in YANG.
> 
> It is needed in the NETCONF data that YANG defines.  Thus it is an
> essential property in a YANG module.
> 

not really.  I don't think RFC 4741 says so.
YANG does not need to make it mandatory.
YANG is arbitrarily enforcing a CLR outside
the language for the module namespace, but not for module version.


> 
> /martin
> 

Andy



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