[YANG] extension naming scope
Andy Bierman <ietf@andybierman.com> Sun, 10 February 2008 17:02 UTC
Return-Path: <yang-bounces@ietf.org>
X-Original-To: ietfarch-yang-archive@core3.amsl.com
Delivered-To: ietfarch-yang-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id E977D3A699F;
Sun, 10 Feb 2008 09:02:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.229
X-Spam-Level:
X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[AWL=0.036,
BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from core3.amsl.com ([127.0.0.1])
by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id DPJ3lM4sPsQd; Sun, 10 Feb 2008 09:02:01 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id A00A13A69EE;
Sun, 10 Feb 2008 09:01:04 -0800 (PST)
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 A91663A6985
for <yang@core3.amsl.com>; Sun, 10 Feb 2008 09:01:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id icxiaDTUiRV4 for <yang@core3.amsl.com>;
Sun, 10 Feb 2008 09:01:03 -0800 (PST)
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 315CB3A6992
for <yang@ietf.org>; Sun, 10 Feb 2008 09:00:38 -0800 (PST)
Received: (qmail 61092 invoked from network); 9 Feb 2008 22:15:17 -0000
Received: from unknown (HELO ?192.168.0.10?)
(andybierman@att.net@67.122.137.15 with plain)
by smtp116.sbc.mail.sp1.yahoo.com with SMTP; 9 Feb 2008 22:15:17 -0000
X-YMail-OSG: IR4.xjoVM1l7VrkjzrGss2hBB6ZVSfwGAwM.VbmYGUmyZ3aJ
X-Yahoo-Newman-Property: ymail-3
Message-ID: <47AE266D.4070601@andybierman.com>
Date: Sat, 09 Feb 2008 14:17:17 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: yang <yang@ietf.org>
Subject: [YANG] extension naming scope
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: <http://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: <http://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, I think the extension naming scope needs to be removed, and extensions need to be in the same scope as rpc, notification, and all objects. When converted to YIN, an extension element is in the same XML namespace as the object instances defined in the same module. Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang
- [YANG] extension naming scope Andy Bierman
- Re: [YANG] extension naming scope Martin Bjorklund
- Re: [YANG] extension naming scope Andy Bierman
- Re: [YANG] extension naming scope Martin Bjorklund
- Re: [YANG] extension naming scope Andy Bierman
- Re: [YANG] extension naming scope Martin Bjorklund
- Re: [YANG] extension naming scope Andy Bierman