From mailman-bounces@core3.amsl.com Fri Feb 1 05:04:38 2008 Return-Path: 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 57BFA28CE9D for ; Fri, 1 Feb 2008 05:04:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.587 X-Spam-Level: X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQFg6lPHkOWB for ; Fri, 1 Feb 2008 05:04:37 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E93228C522 for ; Fri, 1 Feb 2008 05:00:50 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: yang-archive@optimus.ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Feb 2008 05:00:26 -0800 Precedence: bulk X-BeenThere: mailman@core3.amsl.com X-Mailman-Version: 2.1.9 List-Id: X-List-Administrivia: yes Sender: mailman-bounces@core3.amsl.com Errors-To: mailman-bounces@core3.amsl.com This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! http://www.ietf.org/mailman/options/yang/yang-archive%40optimus.ietf.org From mailman-bounces@core3.amsl.com Fri Feb 1 05:04:41 2008 Return-Path: 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 C95E7293CFF for ; Fri, 1 Feb 2008 05:04:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.587 X-Spam-Level: X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u52nYqZwK80o for ; Fri, 1 Feb 2008 05:04:41 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD40B28C24C for ; Fri, 1 Feb 2008 05:00:50 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: yang-archive@optimus.ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Feb 2008 05:00:26 -0800 Precedence: bulk X-BeenThere: mailman@core3.amsl.com X-Mailman-Version: 2.1.9 List-Id: X-List-Administrivia: yes Sender: mailman-bounces@core3.amsl.com Errors-To: mailman-bounces@core3.amsl.com This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! http://www.ietf.org/mailman/options/yang/yang-archive%40optimus.ietf.org From yang-bounces@ietf.org Sat Feb 2 09:17:44 2008 Return-Path: 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 61B8A28C6B1; Sat, 2 Feb 2008 09:17:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.452 X-Spam-Level: X-Spam-Status: No, score=-0.452 tagged_above=-999 required=5 tests=[AWL=0.324, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b4cEDbAv+duF; Sat, 2 Feb 2008 09:17:43 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B53343A6841; Sat, 2 Feb 2008 09:17:43 -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 96A2E28C560 for ; Sat, 2 Feb 2008 09:17:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzqerwdjIZS6 for ; Sat, 2 Feb 2008 09:17:41 -0800 (PST) Received: from smtp117.sbc.mail.sp1.yahoo.com (smtp117.sbc.mail.sp1.yahoo.com [69.147.64.90]) by core3.amsl.com (Postfix) with SMTP id E8B743A6A2A for ; Sat, 2 Feb 2008 09:17:41 -0800 (PST) Received: (qmail 97772 invoked from network); 2 Feb 2008 17:19:18 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@68.120.83.0 with plain) by smtp117.sbc.mail.sp1.yahoo.com with SMTP; 2 Feb 2008 17:19:18 -0000 X-YMail-OSG: 2Tpg8SMVM1llNbMbxLSf7t5Q9zdsXnJ_vBI4L6yRTlENgWMJg3E.e3mmuf5IJoAVicBdsmOWXUs2reMn8Etmj5UQ X-Yahoo-Newman-Property: ymail-3 Message-ID: <47A4A62A.8070502@andybierman.com> Date: Sat, 02 Feb 2008 09:19:38 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang Subject: [YANG] new draft not found X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-01.txt Is anybody else getting a '404 not found' error for this URL? Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sat Feb 2 10:09:11 2008 Return-Path: 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 1D4203A6A6A; Sat, 2 Feb 2008 10:09:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.196 X-Spam-Level: X-Spam-Status: No, score=0.196 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_40=-0.185, IP_NOT_FRIENDLY=0.334] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KsZ-Zz0qFxo; Sat, 2 Feb 2008 10:09:11 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21A013A6A70; Sat, 2 Feb 2008 10:04:56 -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 176923A6AB2 for ; Sat, 2 Feb 2008 10:04:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSQ+J5aQkJsN for ; Sat, 2 Feb 2008 10:04:54 -0800 (PST) Received: from smtp117.sbc.mail.sp1.yahoo.com (smtp117.sbc.mail.sp1.yahoo.com [69.147.64.90]) by core3.amsl.com (Postfix) with SMTP id B9E493A6A70 for ; Sat, 2 Feb 2008 10:00:06 -0800 (PST) Received: (qmail 65203 invoked from network); 2 Feb 2008 18:00:44 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@68.120.83.0 with plain) by smtp117.sbc.mail.sp1.yahoo.com with SMTP; 2 Feb 2008 18:00:44 -0000 X-YMail-OSG: 2RBV4kEVM1mrAZz0wHcPRc6mcfhFT3cxlIO8dWP.79jwLz31 X-Yahoo-Newman-Property: ymail-3 Message-ID: <47A4AFE0.5030002@andybierman.com> Date: Sat, 02 Feb 2008 10:01:04 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang Subject: [YANG] config-stmt missing for choice construct X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, It seems the 'config true/false' clause is missing from the choice-stmt data definition statement. Without it, there is no way to declare a top-level non-config choice. It should be legal to declare a non-config choice nested within a config node. Also, 7.17.1, para 2 (config statement) needs to add text that the 'config' property for the following nodes is hardwired into the NETCONF architecture: rpc/input -- config true; non-config nodes MUST NOT appear under rpc/input rpc/output -- config false; config nodes MUST NOT appear under rpc/output notification -- config false; config nodes MUST NOT appear within a notification All other nodes follow the rules already defined in this section. A top-level RPC method node cannot have config true/false set, but what about an optional classification field like (config, exec, monitor, debug, other)? IMO, this is useful for operators and access control. Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sat Feb 2 10:14:15 2008 Return-Path: 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 0D87F3A6A88; Sat, 2 Feb 2008 10:14:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.021 X-Spam-Level: X-Spam-Status: No, score=-1.021 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWla6i7JMf5Z; Sat, 2 Feb 2008 10:14:14 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64DA43A6A74; Sat, 2 Feb 2008 10:14:14 -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 8A85B3A6A74 for ; Sat, 2 Feb 2008 10:14:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9M9IwnCUsQL for ; Sat, 2 Feb 2008 10:14:12 -0800 (PST) Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id AA5C83A6A6A for ; Sat, 2 Feb 2008 10:14:12 -0800 (PST) Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id F1A0F1B80C8; Sat, 2 Feb 2008 19:15:47 +0100 (CET) Date: Sat, 02 Feb 2008 19:15:42 +0100 (CET) Message-Id: <20080202.191542.202841592.mbj@tail-f.com> To: andy@andybierman.com From: Martin Bjorklund In-Reply-To: <47A4A62A.8070502@andybierman.com> References: <47A4A62A.8070502@andybierman.com> X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Cc: yang@ietf.org Subject: Re: [YANG] new draft not found X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Andy Bierman wrote: > Hi, > > > http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-01.txt > > Is anybody else getting a '404 not found' error for this URL? Yep. I've sent a mail to the ietf support. /martin _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sat Feb 2 10:58:48 2008 Return-Path: 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 13D733A6AC5; Sat, 2 Feb 2008 10:58:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.001 X-Spam-Level: * X-Spam-Status: No, score=1.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=1] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXD+mRyRHk+0; Sat, 2 Feb 2008 10:58:47 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 536C43A67EB; Sat, 2 Feb 2008 10:58:47 -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 4B08D3A6A46 for ; Sat, 2 Feb 2008 10:58:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id orlcZT83kQHV for ; Sat, 2 Feb 2008 10:58:45 -0800 (PST) Received: from web27804.mail.ukl.yahoo.com (web27804.mail.ukl.yahoo.com [217.146.182.9]) by core3.amsl.com (Postfix) with SMTP id A67A43A67EB for ; Sat, 2 Feb 2008 10:58:44 -0800 (PST) Received: (qmail 40083 invoked by uid 60001); 2 Feb 2008 18:53:40 -0000 X-YMail-OSG: DCk5knQVM1kWbb6U21zIZM1FZ5QLYJSGl3JSv6diqhdBsg9o6uEHOpkxH2JtCqnrYa4MoOWzUqC2HT2.MMj0H46cLI3apHIjgMO4z80rcMMhGoACV_tQBTl3OLM- Received: from [217.115.75.232] by web27804.mail.ukl.yahoo.com via HTTP; Sat, 02 Feb 2008 18:53:40 GMT X-Mailer: YahooMailRC/818.31 YahooMailWebService/0.7.162 Date: Sat, 2 Feb 2008 18:53:40 +0000 (GMT) From: Mehmet Ersue To: YANG , andy@andybierman.com MIME-Version: 1.0 Message-ID: <485011.39944.qm@web27804.mail.ukl.yahoo.com> Subject: Re: [YANG] new draft not found X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0741597090==" Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org --===============0741597090== Content-Type: multipart/alternative; boundary="0-903630378-1201978420=:39944" --0-903630378-1201978420=:39944 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =0AHi Andy,=0A=0Athere is no -01 draft yet. The correct URL is:=0A=0Ahttp:/= /www.ietf.org/internet-drafts/draft-linowski-netconf-dml-requirements-00.tx= t=0A=0ACheers, =0AMehmet =0A =0A=0A> -----Original Message-----=0A> From: y= ang-bounces@ietf.org [mailto:yang-bounces@ietf.org] On =0A> Behalf Of ext A= ndy Bierman=0A> Sent: Saturday, February 02, 2008 6:20 PM=0A> To: yang=0A> = Subject: [YANG] new draft not found=0A> =0A> Hi,=0A> =0A> =0A> http://www.i= etf.org/internet-drafts/draft-bjorklund-netconf-ya=0A> ng-01.txt=0A> =0A> I= s anybody else getting a '404 not found' error for this URL?=0A> =0A> =0A> = Andy=0A> =0A=0A=0A> =0A=0A> =0A=0A=0A> =0A=0A> ____________________________= ___________________=0A> YANG mailing list=0A> YANG@ietf.org=0A> http://www.= ietf.org/mailman/listinfo/yang=0A> =0A=0A=0A=0A=0A Heute schon einen B= lick in die Zukunft von E-Mails wagen? Versuchen Sie=C2=B4s mit dem neuen Y= ahoo! Mail. www.yahoo.de/mail --0-903630378-1201978420=:39944 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi Andy,

there is no -01 draft yet. The correct URL is:<= br>
http://www.ietf.org/inte= rnet-drafts/draft-linowski-netconf-dml-requirements-00.txt
Cheers,
Mehmet
 

> -----Original Message-----
&= gt; From: yang-bounces@ietf.org [mailto:yang-bounces@ietf.org] On
> = Behalf Of ext Andy Bierman
> Sent: Saturday, February 02, 2008 6:20 P= M
> To: yang
> Subject: [YANG] new draft not found
>
= > Hi,
>
>
> http://www.ietf.= org/internet-drafts/draft-bjorklund-netconf-ya
> ng-01.txt
>
> Is anybody else getting a '404 not found' error= for this URL?
>
>
> Andy
>
=0A=0A>
= =0A>
=0A=0A>
=0A> ________________________________________= _______
> YANG mailing list
> YANG@ietf.org
> http://w= ww.ietf.org/mailman/listinfo/yang
>

= =0A
Lesen Sie Ihre E-Mails jetzt einfach von unterwegs mi= t =0A =0AYahoo! Go= . =0A --0-903630378-1201978420=:39944-- --===============0741597090== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang --===============0741597090==-- From yang-bounces@ietf.org Sat Feb 2 13:06:55 2008 Return-Path: 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 E0C593A6A96; Sat, 2 Feb 2008 13:06:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.104 X-Spam-Level: X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, HELO_EQ_DE=0.35] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rB5wzPD1PNqK; Sat, 2 Feb 2008 13:06:55 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28DEF3A6841; Sat, 2 Feb 2008 13:06:55 -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 BCA243A6841 for ; Sat, 2 Feb 2008 13:06:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAR+uVbIkjse for ; Sat, 2 Feb 2008 13:06:53 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 9D4663A696F for ; Sat, 2 Feb 2008 13:06:53 -0800 (PST) Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id C249B889D9; Sat, 2 Feb 2008 22:08:28 +0100 (CET) Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 19125-05; Sat, 2 Feb 2008 22:08:24 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 206AF8A220; Sat, 2 Feb 2008 22:08:23 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 4D3B449BC31; Sat, 2 Feb 2008 22:08:20 +0100 (CET) Date: Sat, 2 Feb 2008 22:08:20 +0100 From: Juergen Schoenwaelder To: Andy Bierman Message-ID: <20080202210820.GA9868@elstar.local> Mail-Followup-To: Andy Bierman , yang References: <47A4AFE0.5030002@andybierman.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <47A4AFE0.5030002@andybierman.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de Cc: yang Subject: Re: [YANG] config-stmt missing for choice construct X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: j.schoenwaelder@jacobs-university.de List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org On Sat, Feb 02, 2008 at 10:01:04AM -0800, Andy Bierman wrote: > Also, 7.17.1, para 2 (config statement) needs to add text that > the 'config' property for the following nodes is hardwired into > the NETCONF architecture: > > rpc/input -- config true; > non-config nodes MUST NOT appear under rpc/input > > rpc/output -- config false; > config nodes MUST NOT appear under rpc/output > > notification -- config false; > config nodes MUST NOT appear within a notification > > All other nodes follow the rules already defined in this section. Why is rpc/input config? /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sat Feb 2 13:45:27 2008 Return-Path: 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 8F16E3A6A87; Sat, 2 Feb 2008 13:45:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.104 X-Spam-Level: X-Spam-Status: No, score=-1.104 tagged_above=-999 required=5 tests=[AWL=1.161, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ouPvGyqm3HW7; Sat, 2 Feb 2008 13:45:26 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4EB73A6ABA; Sat, 2 Feb 2008 13:45:26 -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 91CF33A6A6A for ; Sat, 2 Feb 2008 13:45:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBFjSiOQ4LVg for ; Sat, 2 Feb 2008 13:45:25 -0800 (PST) Received: from smtp117.sbc.mail.sp1.yahoo.com (smtp117.sbc.mail.sp1.yahoo.com [69.147.64.90]) by core3.amsl.com (Postfix) with SMTP id ED7DC3A6A87 for ; Sat, 2 Feb 2008 13:45:24 -0800 (PST) Received: (qmail 87950 invoked from network); 2 Feb 2008 21:47:01 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@68.120.83.0 with plain) by smtp117.sbc.mail.sp1.yahoo.com with SMTP; 2 Feb 2008 21:47:00 -0000 X-YMail-OSG: .rG4PcYVM1m4W_gomCRKerQTlURTf4K.CTQlQtrgSjTr1J0q X-Yahoo-Newman-Property: ymail-3 Message-ID: <47A4E4E9.8060901@andybierman.com> Date: Sat, 02 Feb 2008 13:47:21 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Andy Bierman , yang References: <47A4AFE0.5030002@andybierman.com> <20080202210820.GA9868@elstar.local> In-Reply-To: <20080202210820.GA9868@elstar.local> Subject: Re: [YANG] config-stmt missing for choice construct X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Juergen Schoenwaelder wrote: > On Sat, Feb 02, 2008 at 10:01:04AM -0800, Andy Bierman wrote: > >> Also, 7.17.1, para 2 (config statement) needs to add text that >> the 'config' property for the following nodes is hardwired into >> the NETCONF architecture: >> >> rpc/input -- config true; >> non-config nodes MUST NOT appear under rpc/input >> >> rpc/output -- config false; >> config nodes MUST NOT appear under rpc/output >> >> notification -- config false; >> config nodes MUST NOT appear within a notification >> >> All other nodes follow the rules already defined in this section. > > Why is rpc/input config? > Well, all the input parameters are writable. In YANG, 'config false' is the closest thing to 'max-access read-only'. Either we should say the config-stmt is ignored for rpc and notifications, or explicitly define its meaning for these things. > /js > Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sat Feb 2 14:16:18 2008 Return-Path: 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 E24C13A6AB7; Sat, 2 Feb 2008 14:16:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.125 X-Spam-Level: X-Spam-Status: No, score=-2.125 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, HELO_EQ_DE=0.35] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gI5x2lu-ET-n; Sat, 2 Feb 2008 14:16:18 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E20A3A6934; Sat, 2 Feb 2008 14:16:18 -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 CD1BC3A6A8F for ; Sat, 2 Feb 2008 14:16:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77pSWPtPFhNL for ; Sat, 2 Feb 2008 14:16:16 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id DC0F43A6934 for ; Sat, 2 Feb 2008 14:16:15 -0800 (PST) Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0210D8A220; Sat, 2 Feb 2008 23:17:52 +0100 (CET) Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 22682-09; Sat, 2 Feb 2008 23:17:47 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 767338A21F; Sat, 2 Feb 2008 23:17:47 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id E56ED49BDDC; Sat, 2 Feb 2008 23:17:43 +0100 (CET) Date: Sat, 2 Feb 2008 23:17:43 +0100 From: Juergen Schoenwaelder To: Andy Bierman Message-ID: <20080202221743.GA10056@elstar.local> Mail-Followup-To: Andy Bierman , yang References: <47A4AFE0.5030002@andybierman.com> <20080202210820.GA9868@elstar.local> <47A4E4E9.8060901@andybierman.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <47A4E4E9.8060901@andybierman.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de Cc: yang Subject: Re: [YANG] config-stmt missing for choice construct X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: j.schoenwaelder@jacobs-university.de List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org On Sat, Feb 02, 2008 at 01:47:21PM -0800, Andy Bierman wrote: > Well, all the input parameters are writable. > In YANG, 'config false' is the closest thing to 'max-access read-only'. > Either we should say the config-stmt is ignored for rpc and notifications, > or explicitly define its meaning for these things. I think it should be ignored. My understanding of 'config true' is that it marks data items that belong to the configuration state and 'config false' says data items belongs to the operational state. The in/out/(error) parameters of operations are in general something different. And I think the same argument can be made for notifications. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Mon Feb 4 00:03:31 2008 Return-Path: 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 2BC5A3A6E0A; Mon, 4 Feb 2008 00:03:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x3N+CGGfmPET; Mon, 4 Feb 2008 00:03:30 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99FCC3A6DDA; Mon, 4 Feb 2008 00:03:27 -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 26FBF3A6BC3 for ; Mon, 4 Feb 2008 00:03:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rfShoEKl5E7c for ; Mon, 4 Feb 2008 00:03:25 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 5674B3A686B for ; Mon, 4 Feb 2008 00:03:06 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 1513A20957; Mon, 4 Feb 2008 09:04:37 +0100 (CET) X-AuditID: c1b4fb3c-a8ae9bb0000007e0-94-47a6c715f85c Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 01A2B20575; Mon, 4 Feb 2008 09:04:37 +0100 (CET) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Feb 2008 09:04:36 +0100 Received: from [159.107.197.224] ([159.107.197.224]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Feb 2008 09:04:36 +0100 Message-ID: <47A6C713.6040306@ericsson.com> Date: Mon, 04 Feb 2008 09:04:35 +0100 From: Balazs Lengyel User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: Andy Bierman References: <47A4A62A.8070502@andybierman.com> In-Reply-To: <47A4A62A.8070502@andybierman.com> X-OriginalArrivalTime: 04 Feb 2008 08:04:36.0420 (UTC) FILETIME=[9567D840:01C86704] X-Brightmail-Tracker: AAAAAA== Cc: yang Subject: Re: [YANG] new draft not found X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org I get the same. Balazs Andy Bierman wrote: > Hi, > > > http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-01.txt > > Is anybody else getting a '404 not found' error for this URL? > > > Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Mon Feb 4 00:54:38 2008 Return-Path: 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 04C543A6E0A; Mon, 4 Feb 2008 00:54:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.47 X-Spam-Level: X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IKpDMhWQe3w4; Mon, 4 Feb 2008 00:54:37 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EAAC3A6E0F; Mon, 4 Feb 2008 00:54:37 -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 086673A6E0A for ; Mon, 4 Feb 2008 00:54:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1FgHzNmh-6GL for ; Mon, 4 Feb 2008 00:54:32 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 279953A6DC2 for ; Mon, 4 Feb 2008 00:54:32 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.25,301,1199682000"; d="scan'208";a="97387714" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 04 Feb 2008 03:56:06 -0500 X-IronPort-AV: E=Sophos;i="4.25,301,1199682000"; d="scan'208";a="150508306" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 04 Feb 2008 03:56:05 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 4 Feb 2008 09:55:57 +0100 Message-ID: In-Reply-To: <47A6C713.6040306@ericsson.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [YANG] new draft not found Thread-Index: AchnBTmDeHpyJ7UcQg+MO5Pdh1ywQAABmw2w References: <47A4A62A.8070502@andybierman.com> <47A6C713.6040306@ericsson.com> From: "Romascanu, Dan (Dan)" To: "Balazs Lengyel" , "Andy Bierman" Cc: yang Subject: Re: [YANG] new draft not found X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org This may be related to the transition of the secretariat services which was completed last week. Dan > -----Original Message----- > From: yang-bounces@ietf.org [mailto:yang-bounces@ietf.org] On > Behalf Of Balazs Lengyel > Sent: Monday, February 04, 2008 10:05 AM > To: Andy Bierman > Cc: yang > Subject: Re: [YANG] new draft not found > > I get the same. > Balazs > > Andy Bierman wrote: > > Hi, > > > > > > > http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-01.tx > > t > > > > Is anybody else getting a '404 not found' error for this URL? > > > > > > Andy > _______________________________________________ > YANG mailing list > YANG@ietf.org > http://www.ietf.org/mailman/listinfo/yang > _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Mon Feb 4 10:16:14 2008 Return-Path: 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 92D7E3A6DB0; Mon, 4 Feb 2008 10:16:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.369 X-Spam-Level: X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8mZ675x+UCg; Mon, 4 Feb 2008 10:16:13 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C81FC3A6D33; Mon, 4 Feb 2008 10:16:13 -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 700413A6D4B for ; Mon, 4 Feb 2008 10:16:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSAGUZw0ASiO for ; Mon, 4 Feb 2008 10:16:11 -0800 (PST) Received: from smtp104.sbc.mail.mud.yahoo.com (smtp104.sbc.mail.mud.yahoo.com [68.142.198.203]) by core3.amsl.com (Postfix) with SMTP id A167A3A6D33 for ; Mon, 4 Feb 2008 10:16:11 -0800 (PST) Received: (qmail 96394 invoked from network); 4 Feb 2008 18:17:45 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.122.136.212 with plain) by smtp104.sbc.mail.mud.yahoo.com with SMTP; 4 Feb 2008 18:17:45 -0000 X-YMail-OSG: K0EGf1UVM1nisNe_DGBaCubCE1UOsWXgs_wdTOmg.gxn4fo_ X-Yahoo-Newman-Property: ymail-3 Message-ID: <47A756C9.8000401@andybierman.com> Date: Mon, 04 Feb 2008 10:17:45 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang Subject: [YANG] mandatory empty X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, What does this mean exactly? leaf foo { type empty; mandatory true; } Does this translate to: The empty data type can be modeled in XSD as an empty complexType: Can it be modeled as a simpleType? If mandatory means that the manager must supply a value, then the leaf 'foo' can never be missing. Even if it means the agent must supply a value, it still seems strange. Perhaps more text is needed about the empty data type. IMO, 'mandatory' and 'units' are not applicable to built-in type 'empty'. Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Mon Feb 4 11:47:49 2008 Return-Path: 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 293923A7139; Mon, 4 Feb 2008 11:47:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.675 X-Spam-Level: X-Spam-Status: No, score=-1.675 tagged_above=-999 required=5 tests=[AWL=0.924, BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Re5NjzlWdoxR; Mon, 4 Feb 2008 11:47:49 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F5223A70F8; Mon, 4 Feb 2008 11:47:40 -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 815973A6ECE for ; Mon, 4 Feb 2008 11:47:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LaKf0C93cW6O for ; Mon, 4 Feb 2008 11:47:37 -0800 (PST) Received: from mail.tail-f.com (mail.tail-f.com [213.180.94.158]) by core3.amsl.com (Postfix) with ESMTP id A27773A6FFE for ; Mon, 4 Feb 2008 11:45:32 -0800 (PST) Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id 224D81B80CF; Mon, 4 Feb 2008 20:47:06 +0100 (CET) Date: Mon, 04 Feb 2008 20:46:56 +0100 (CET) Message-Id: <20080204.204656.247665076.mbj@tail-f.com> To: ietf@andybierman.com From: Martin Bjorklund In-Reply-To: <47A756C9.8000401@andybierman.com> References: <47A756C9.8000401@andybierman.com> X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Cc: yang@ietf.org Subject: Re: [YANG] mandatory empty X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Andy Bierman wrote: > Hi, > > What does this mean exactly? > > leaf foo { > type empty; > mandatory true; > } > > Does this translate to: > > No, b/c the default type in XSD is anyType, which means any xml. And if it's mandatory, it should be minOccurs='1' (which is the default). But it depends on what your XSD is supposed to validate - a NETCONF PDU or the datastore. I translate this into: > The empty data type can be modeled in XSD as an empty complexType: > > Yes. > Can it be modeled as a simpleType? > > > > > > I don't know. Maybe? > If mandatory means that the manager must supply a value, > then the leaf 'foo' can never be missing. > > Even if it means the agent must supply a value, > it still seems strange. Perhaps more text is needed > about the empty data type. > > IMO, 'mandatory' and 'units' are not applicable to built-in type 'empty'. I agree that units on a type empty seems weird. mandatory true on type empty also seems weird, since a type empty leaf provides a single bit of information (in its existance). So if it always has to be there, what is the point? I don't know if we have to make this an error though. /martin _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Tue Feb 5 23:53:09 2008 Return-Path: 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 C58643A6A91; Tue, 5 Feb 2008 23:53:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 pjRNkPI0cy1j; Tue, 5 Feb 2008 23:53:09 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26D453A6A40; Tue, 5 Feb 2008 23:53:09 -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 2DD913A694F for ; Tue, 5 Feb 2008 23:53:08 -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 OtC0CxlDfvYm for ; Tue, 5 Feb 2008 23:53:07 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 107A83A6A07 for ; Tue, 5 Feb 2008 23:53:04 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 02BF02150B for ; Wed, 6 Feb 2008 08:54:34 +0100 (CET) X-AuditID: c1b4fb3e-ac5ebbb0000007e1-4f-47a967b95728 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id DA90B2150A for ; Wed, 6 Feb 2008 08:54:33 +0100 (CET) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Feb 2008 08:54:33 +0100 Received: from selic023.lmera.ericsson.se ([150.132.89.214]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Feb 2008 08:54:33 +0100 From: David Partain Organization: Ericsson AB To: yang@ietf.org Date: Wed, 6 Feb 2008 08:54:32 +0100 User-Agent: KMail/1.9.8 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200802060854.32971.david.partain@ericsson.com> X-OriginalArrivalTime: 06 Feb 2008 07:54:33.0418 (UTC) FILETIME=[82D08AA0:01C86895] X-Brightmail-Tracker: AAAAAA== Subject: [YANG] New revision of the YANG draft X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, There is a new version of the YANG draft in the I-D repository. http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-02.txt Cheers, David _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 6 00:08:27 2008 Return-Path: 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 CBC7F3A6AAF; Wed, 6 Feb 2008 00:08:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.495 X-Spam-Level: X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] 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 SEuYmZghsZNY; Wed, 6 Feb 2008 00:08:27 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24A6B3A69FE; Wed, 6 Feb 2008 00:08:27 -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 B90DC3A6A2E for ; Wed, 6 Feb 2008 00:08:25 -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 n6PHCnbV13wj for ; Wed, 6 Feb 2008 00:08:25 -0800 (PST) Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id E19923A6899 for ; Wed, 6 Feb 2008 00:08:24 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTP id D34C41B80C4 for ; Wed, 6 Feb 2008 09:09:54 +0100 (CET) Date: Wed, 06 Feb 2008 09:11:47 +0100 (CET) Message-Id: <20080206.091147.119060343.mbj@tail-f.com> To: yang@ietf.org From: Martin Bjorklund In-Reply-To: <200802060854.32971.david.partain@ericsson.com> References: <200802060854.32971.david.partain@ericsson.com> X-Mailer: Mew version 5.1.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Subject: Re: [YANG] New revision of the YANG draft X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, FYI: In case you wonder about the 00 to 02 jump - 01 was submitted but got lost in the transition of the secretariat tasks. 02 is the same as 01, with some ABNF grammar bugfixes. /martin David Partain wrote: > Hi, > > There is a new version of the YANG draft in the I-D repository. > > http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-02.txt > > Cheers, > > David > _______________________________________________ > YANG mailing list > YANG@ietf.org > http://www.ietf.org/mailman/listinfo/yang > _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 6 00:39:01 2008 Return-Path: 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 AF33F3A6A01; Wed, 6 Feb 2008 00:39:01 -0800 (PST) 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 core3.amsl.com ([127.0.0.1]) by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xjiDBB8Eimzp; Wed, 6 Feb 2008 00:39:00 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E448C3A6ACE; Wed, 6 Feb 2008 00:39:00 -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 468E13A6B1A for ; Wed, 6 Feb 2008 00:38:59 -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 l4MTmISAlQZT for ; Wed, 6 Feb 2008 00:38:58 -0800 (PST) Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id 4E8C83A6A01 for ; Wed, 6 Feb 2008 00:38:54 -0800 (PST) Received: from source ([66.129.224.36]) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP; Wed, 06 Feb 2008 00:40:26 PST Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Feb 2008 00:32:41 -0800 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 m168Wcq31525; Wed, 6 Feb 2008 00:32:38 -0800 (PST) (envelope-from phil@idle.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 m168WMXH018271; Wed, 6 Feb 2008 08:32:23 GMT (envelope-from phil@idle.juniper.net) Message-Id: <200802060832.m168WMXH018271@idle.juniper.net> To: Balazs Lengyel In-reply-to: <47A829D9.903@ericsson.com> Date: Wed, 06 Feb 2008 03:32:22 -0500 From: Phil Shafer X-OriginalArrivalTime: 06 Feb 2008 08:32:41.0525 (UTC) FILETIME=[D6A1F650:01C8689A] Cc: yang@ietf.org Subject: Re: [YANG] mandatory empty X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Balazs Lengyel writes: >I agree units and mandatory on empty is useless, but they are not dangerous. They won't >cause >subtle problems, so I don't see a need for the little rule. The need is to avoid pointless YANG specs, where the user is asking for something that makes no sense. If we allow it, we allow nonsense, which is nonsensical. Thanks, Phil _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Fri Feb 8 15:09:58 2008 Return-Path: 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 4BF0328C6E9; Fri, 8 Feb 2008 15:09:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.265 X-Spam-Level: X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[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 s8vppUzjWFEN; Fri, 8 Feb 2008 15:09:57 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3469E28C714; Fri, 8 Feb 2008 15:09:55 -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 A6B1328C70E for ; Fri, 8 Feb 2008 15:09:54 -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 r37x0O6Iuekl for ; Fri, 8 Feb 2008 15:09:54 -0800 (PST) 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 A172428C746 for ; Fri, 8 Feb 2008 15:09:31 -0800 (PST) Received: (qmail 70910 invoked from network); 8 Feb 2008 23:11:00 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.121.105.87 with plain) by smtp120.sbc.mail.sp1.yahoo.com with SMTP; 8 Feb 2008 23:11:00 -0000 X-YMail-OSG: PLFKf5UVM1nNdvHq_ReHfXFsYnS6ECvr8Rj6_0Q8apAMfshm X-Yahoo-Newman-Property: ymail-3 Message-ID: <47ACE183.5070708@andybierman.com> Date: Fri, 08 Feb 2008 15:10:59 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang Subject: [YANG] module version field X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, The [sub]module version field is kind of important, and there is none in YANG. SMIv2 has LAST-UPDATED. I like 'version'. It is CLI and XSD friendly. IMO, the version string should not be coupled to the LAST-UPDATED timestamp. What if the vendor has a totally different numbering scheme? An explicit version field could be a CLR -- just something to match up to some other string somewhere else, or it could be extra semantics. The current syntax only allows 1 version per day, which is not good enough in every development environment. I think we should consider adding an optional version field to meta-stmts. If missing, then the most recent revision date is used, and if no revision statements are present, then the vendor can use whatever they want (including no version). Whatever we use, there needs to be exactly one inter-operable field that can be used in schema discovery, that matches a version field in YANG/XSD/RNG files. The namespace URI should not be used for this purpose. For protocol features, like the capability URIs, a version field in the URI is OK because it doesn't change very often, and NETCONF supports extensions. YANG module versions should be separate from the module namespace URI. Once we work on change control rules, the important CLRs will get defined ;-) Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sun Feb 10 09:02:06 2008 Return-Path: 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 ; 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 ; 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 ; 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 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From yang-bounces@ietf.org Sun Feb 10 13:04:10 2008 Return-Path: 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 C6B9E3A68F5; Sun, 10 Feb 2008 13:04:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.657 X-Spam-Level: X-Spam-Status: No, score=-0.657 tagged_above=-999 required=5 tests=[AWL=-0.162, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] 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 IhvZiuiys1Jm; Sun, 10 Feb 2008 13:04:10 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 138253A68AE; Sun, 10 Feb 2008 13:04:10 -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 5EBEE3A6854 for ; Sun, 10 Feb 2008 13:04:09 -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 l2b+tUXBkfuf for ; Sun, 10 Feb 2008 13:04:08 -0800 (PST) Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id 8753B3A6834 for ; Sun, 10 Feb 2008 13:04:08 -0800 (PST) Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id 432F21B80C3; Sun, 10 Feb 2008 22:05:33 +0100 (CET) Date: Sun, 10 Feb 2008 22:05:08 +0100 (CET) Message-Id: <20080210.220508.149362842.mbj@tail-f.com> To: ietf@andybierman.com From: Martin Bjorklund In-Reply-To: <47AE266D.4070601@andybierman.com> References: <47AE266D.4070601@andybierman.com> X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Cc: yang@ietf.org Subject: Re: [YANG] extension naming scope X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Andy Bierman wrote: > 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. I don't think this is a problem. The same thing is done in XSD, where e.g. simpleTypes and elements have different naming scopes. In XSD, there can be a simpleType named 'foo' and an element named 'foo' and a group named 'foo' at the same time. /martin _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sun Feb 10 13:22:57 2008 Return-Path: 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 E575A3A67A6; Sun, 10 Feb 2008 13:22:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.265 X-Spam-Level: X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[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 UxDGsm2NlF6X; Sun, 10 Feb 2008 13:22:57 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA3423A695E; Sun, 10 Feb 2008 13:22:42 -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 6C90F3A68F8 for ; Sun, 10 Feb 2008 13:22:41 -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 51Ki8kMN1hYo for ; Sun, 10 Feb 2008 13:22:35 -0800 (PST) Received: from smtp122.sbc.mail.sp1.yahoo.com (smtp122.sbc.mail.sp1.yahoo.com [69.147.64.95]) by core3.amsl.com (Postfix) with SMTP id 13C773A68FE for ; Sun, 10 Feb 2008 13:22:11 -0800 (PST) Received: (qmail 73388 invoked from network); 10 Feb 2008 21:23:38 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.126.128.21 with plain) by smtp122.sbc.mail.sp1.yahoo.com with SMTP; 10 Feb 2008 21:23:38 -0000 X-YMail-OSG: gQUf4L0VM1nVkGzAay99Cp3i26S.yjbzlYEqERLIzltzoTp0 X-Yahoo-Newman-Property: ymail-3 Message-ID: <47AF6B58.6080204@andybierman.com> Date: Sun, 10 Feb 2008 13:23:36 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Martin Bjorklund References: <47AE266D.4070601@andybierman.com> <20080210.220508.149362842.mbj@tail-f.com> In-Reply-To: <20080210.220508.149362842.mbj@tail-f.com> Cc: yang@ietf.org Subject: Re: [YANG] extension naming scope X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Martin Bjorklund wrote: > Andy Bierman wrote: >> 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. > > I don't think this is a problem. The same thing is done in XSD, where > e.g. simpleTypes and elements have different naming scopes. In XSD, > there can be a simpleType named 'foo' and an element named 'foo' and a > group named 'foo' at the same time. > I disagree. leaf foo { type int16; } extension foo { argument bar { yin-element false; } } These are both defined in the same XML namespace. 17 The > /martin > > > Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sun Feb 10 14:11:45 2008 Return-Path: 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 C7CFF3A6A27; Sun, 10 Feb 2008 14:11:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.128 X-Spam-Level: X-Spam-Status: No, score=0.128 tagged_above=-999 required=5 tests=[AWL=-0.635, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_13=0.6, J_CHICKENPOX_14=0.6, RDNS_NONE=0.1] 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 cwQdd0mtKu29; Sun, 10 Feb 2008 14:11:40 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 149983A6A49; Sun, 10 Feb 2008 14:08:26 -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 8D9173A6854 for ; Sun, 10 Feb 2008 14:08:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 Qjmm0UGjWbvN for ; Sun, 10 Feb 2008 14:08:23 -0800 (PST) Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id 5539D3A6A27 for ; Sun, 10 Feb 2008 13:51:18 -0800 (PST) Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id A69131B80C3; Sun, 10 Feb 2008 22:52:43 +0100 (CET) Date: Sun, 10 Feb 2008 22:52:18 +0100 (CET) Message-Id: <20080210.225218.154558934.mbj@tail-f.com> To: ietf@andybierman.com From: Martin Bjorklund In-Reply-To: <47AF7015.3000102@andybierman.com> References: <47AF6B58.6080204@andybierman.com> <20080210.223104.132979664.mbj@tail-f.com> <47AF7015.3000102@andybierman.com> X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Cc: yang@ietf.org Subject: Re: [YANG] extension naming scope X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Andy Bierman wrote: > Well, how about this one? > > module x { > ... > prefix x; > ... > > leaf foo { > type int16; > x:foo "some string"; > } > > x:foo "another string"; > > extension foo { > argument bar { > yin-element false; > } > } > } I'm sorry, I don't see the problem. leaf foo and extension foo are different entities. The YIN translations looks like this: $ ./pyang.py x.yang -f yin /martin _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sun Feb 10 14:15:18 2008 Return-Path: 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 435C53A695D; Sun, 10 Feb 2008 14:15:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.024 X-Spam-Level: X-Spam-Status: No, score=-1.024 tagged_above=-999 required=5 tests=[AWL=-1.187, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1] 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 RokdjcTD1bJv; Sun, 10 Feb 2008 14:15:17 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E26D3A69DE; Sun, 10 Feb 2008 14:14:18 -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 15C353A69DE for ; Sun, 10 Feb 2008 14:14:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 LPPJrj4tw0Jl for ; Sun, 10 Feb 2008 14:14:16 -0800 (PST) Received: from smtp109.sbc.mail.mud.yahoo.com (smtp109.sbc.mail.mud.yahoo.com [68.142.198.208]) by core3.amsl.com (Postfix) with SMTP id A28013A69CB for ; Sun, 10 Feb 2008 13:42:24 -0800 (PST) Received: (qmail 28569 invoked from network); 10 Feb 2008 21:43:51 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.126.128.21 with plain) by smtp109.sbc.mail.mud.yahoo.com with SMTP; 10 Feb 2008 21:43:50 -0000 X-YMail-OSG: NETbfvEVM1k6EZKeG2nHPYYe9MW5Qel4bCBamUq4N.bHjing X-Yahoo-Newman-Property: ymail-3 Message-ID: <47AF7015.3000102@andybierman.com> Date: Sun, 10 Feb 2008 13:43:49 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Martin Bjorklund References: <47AE266D.4070601@andybierman.com> <20080210.220508.149362842.mbj@tail-f.com> <47AF6B58.6080204@andybierman.com> <20080210.223104.132979664.mbj@tail-f.com> In-Reply-To: <20080210.223104.132979664.mbj@tail-f.com> Cc: yang@ietf.org Subject: Re: [YANG] extension naming scope X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Martin Bjorklund wrote: > Andy Bierman wrote: >> Martin Bjorklund wrote: >>> Andy Bierman wrote: >>>> 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. >>> I don't think this is a problem. The same thing is done in XSD, where >>> e.g. simpleTypes and elements have different naming scopes. In XSD, >>> there can be a simpleType named 'foo' and an element named 'foo' and a >>> group named 'foo' at the same time. >>> >> I disagree. >> >> leaf foo { type int16; } >> >> >> extension foo { >> argument bar { >> yin-element false; >> } >> } >> >> These are both defined in the same XML namespace. >> >> 17 >> >> >> >> The > as the one generated for the leaf. > > The YIN version of this is: > > > > > > > > > > > Maybe you didn't mean YIN, but XSD? > Well, how about this one? module x { ... prefix x; ... leaf foo { type int16; x:foo "some string"; } x:foo "another string"; extension foo { argument bar { yin-element false; } } } > > /martin > > > Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sun Feb 10 14:24:30 2008 Return-Path: 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 97EA03A699E; Sun, 10 Feb 2008 14:24:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.436 X-Spam-Level: X-Spam-Status: No, score=-0.436 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 k5KeoKOfhSls; Sun, 10 Feb 2008 14:24:29 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C00E3A69AC; Sun, 10 Feb 2008 14:24:22 -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 0A0113A69BF for ; Sun, 10 Feb 2008 14:24:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 I3ZPkfZBUXiC for ; Sun, 10 Feb 2008 14:24:20 -0800 (PST) Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id 38AA63A69AC for ; Sun, 10 Feb 2008 13:30:03 -0800 (PST) Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id 4ACC81B80C3; Sun, 10 Feb 2008 22:31:29 +0100 (CET) Date: Sun, 10 Feb 2008 22:31:04 +0100 (CET) Message-Id: <20080210.223104.132979664.mbj@tail-f.com> To: ietf@andybierman.com From: Martin Bjorklund In-Reply-To: <47AF6B58.6080204@andybierman.com> References: <47AE266D.4070601@andybierman.com> <20080210.220508.149362842.mbj@tail-f.com> <47AF6B58.6080204@andybierman.com> X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Cc: yang@ietf.org Subject: Re: [YANG] extension naming scope X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Andy Bierman wrote: > Martin Bjorklund wrote: > > Andy Bierman wrote: > >> 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. > > I don't think this is a problem. The same thing is done in XSD, where > > e.g. simpleTypes and elements have different naming scopes. In XSD, > > there can be a simpleType named 'foo' and an element named 'foo' and a > > group named 'foo' at the same time. > > > > I disagree. > > leaf foo { type int16; } > > > extension foo { > argument bar { > yin-element false; > } > } > > These are both defined in the same XML namespace. > > 17 > > > > The as the one generated for the leaf. The YIN version of this is: Maybe you didn't mean YIN, but XSD? /martin _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Sun Feb 10 15:39:45 2008 Return-Path: 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 C956C3A696F; Sun, 10 Feb 2008 15:39:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.105 X-Spam-Level: X-Spam-Status: No, score=-0.105 tagged_above=-999 required=5 tests=[AWL=-0.868, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_13=0.6, J_CHICKENPOX_14=0.6, RDNS_NONE=0.1] 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 Pb9evDONVtmZ; Sun, 10 Feb 2008 15:39:45 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24FFB3A6907; Sun, 10 Feb 2008 15:39:45 -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 6FBF63A6907 for ; Sun, 10 Feb 2008 15:39:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 0OJ0SQ7ROl+M for ; Sun, 10 Feb 2008 15:39:43 -0800 (PST) Received: from smtp122.sbc.mail.sp1.yahoo.com (smtp122.sbc.mail.sp1.yahoo.com [69.147.64.95]) by core3.amsl.com (Postfix) with SMTP id BC8A23A6865 for ; Sun, 10 Feb 2008 15:39:41 -0800 (PST) Received: (qmail 10305 invoked from network); 10 Feb 2008 23:41:08 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.126.128.21 with plain) by smtp122.sbc.mail.sp1.yahoo.com with SMTP; 10 Feb 2008 23:41:08 -0000 X-YMail-OSG: 79ScstgVM1kLO5WSHyt7Bisbxuo9bmA8M4POS0SbLBuMz4HU X-Yahoo-Newman-Property: ymail-3 Message-ID: <47AF8B93.4020609@andybierman.com> Date: Sun, 10 Feb 2008 15:41:07 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Martin Bjorklund References: <47AF6B58.6080204@andybierman.com> <20080210.223104.132979664.mbj@tail-f.com> <47AF7015.3000102@andybierman.com> <20080210.225218.154558934.mbj@tail-f.com> In-Reply-To: <20080210.225218.154558934.mbj@tail-f.com> Cc: yang@ietf.org Subject: Re: [YANG] extension naming scope X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Martin Bjorklund wrote: > Andy Bierman wrote: >> Well, how about this one? >> >> module x { >> ... >> prefix x; >> ... >> >> leaf foo { >> type int16; >> x:foo "some string"; >> } >> >> x:foo "another string"; >> >> extension foo { >> argument bar { >> yin-element false; >> } >> } >> } > > I'm sorry, I don't see the problem. leaf foo and extension foo are > different entities. The YIN translations looks like this: > okay -- if you imported x into the YIN document, then it would be correct. I forget everything including the values in in the YIN namespace. > $ ./pyang.py x.yang -f yin > > name="x"> > > > > > > > > > > > > > > > > /martin > > > Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 13 06:00:45 2008 Return-Path: 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 CADDA28C85D; Wed, 13 Feb 2008 06:00:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.698 X-Spam-Level: X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[AWL=-0.261, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 joVdn11KmsIB; Wed, 13 Feb 2008 06:00:41 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C13E428C77B; Wed, 13 Feb 2008 06:00:41 -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 ED6A03A6A24 for ; Wed, 13 Feb 2008 06:00:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 Z6f-bxEcxMTv for ; Wed, 13 Feb 2008 06:00:38 -0800 (PST) Received: from smtp101.sbc.mail.mud.yahoo.com (smtp101.sbc.mail.mud.yahoo.com [68.142.198.200]) by core3.amsl.com (Postfix) with SMTP id 737143A6E79 for ; Wed, 13 Feb 2008 06:00:38 -0800 (PST) Received: (qmail 402 invoked from network); 13 Feb 2008 14:02:01 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@68.120.85.9 with plain) by smtp101.sbc.mail.mud.yahoo.com with SMTP; 13 Feb 2008 14:02:01 -0000 X-YMail-OSG: jLput2UVM1mt0TtjxIBhqZZUTWcsa_oSQSYouXAEwwMMngGw X-Yahoo-Newman-Property: ymail-3 Message-ID: <47B2F858.2080309@andybierman.com> Date: Wed, 13 Feb 2008 06:02:00 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang , NETCONF Goes On Subject: [YANG] reusable types and groupings X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, There are some important CANMOD requirements that are not agreed upon, including deep keys, and perhaps reusable complex structures. There is a difference between a reusable container on the wire and a conceptual set of sibling nodes defined in an off-line document. A container can be processed by shared code that knows the syntax and semantics of that container. (Any C programmer knows the difference between 'typedef struct foo_t' and '#define FOO_ITEMS'.) The IETF needs the ability to define standard NETCONF models which include reusable containers (conceptual and on-the-wire), and the ability to use leafs from those containers in the key for a list. The examples that keep coming up are quire relevant to networking, like address/zone index, address/port, etc. The YANG draft specifies that instances of lists are reordered on-the-wire so all the leaf nodes are encoded first (instead of where they belong based on document order), para 2 and 3 below: 7.8.5. XML Encoding Rules A list is encoded as a series of XML elements, one for each entry in the list. Each element's name is the list's identifier, and its XML namespace is the module's XML namespace. The list's key nodes are encoded as subelements to the list's identifier element, in the same order as they are defined within the key statement. The rest of the list's child nodes are encoded as subelements to the list element, after the keys, in the same order as they are defined within the list statement. There is no explanation in the draft why this done, or considered a feature. It would obviously never work with deep keys, since removing them from the sub-tree changes their identity (/name is not the same as /foo/name). Even if the same grouping is used in 2 different lists, or in a container, it won't be a reusable container on the wire at all. grouping stats_entry { leaf src_addr { type smi:InetAddress; } leaf dst_addr { type smi:InetAddress; } leaf octets { type smi:Counter32; } leaf packets { type smi:Counter32; } leaf last_active_time { type smi:DateAndTime' } } container A { uses stats_entry; } list B { key "src_addr dst_addr"; uses stats_entry; } list C { key "dst_addr src_addr"; uses stats_entry; } list D { key "last_active_time"; uses stats_entry; } Only 'container A' and 'list B' will be encoded on the wire in document order. Even worse, there is no way to model the real intent, which is to have one real stats list, and different ways of sorting the entries. Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 13 11:29:22 2008 Return-Path: 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 3C8383A6873; Wed, 13 Feb 2008 11:29:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.291 X-Spam-Level: X-Spam-Status: No, score=-1.291 tagged_above=-999 required=5 tests=[AWL=-0.854, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 d80T1jUyVvfh; Wed, 13 Feb 2008 11:29:20 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB5CB3A6839; Wed, 13 Feb 2008 11:29:20 -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 4019D3A6873 for ; Wed, 13 Feb 2008 11:29:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 KMCGKNcAWZL0 for ; Wed, 13 Feb 2008 11:29:18 -0800 (PST) Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id EE0CC3A68DF for ; Wed, 13 Feb 2008 11:28:59 -0800 (PST) Received: from OMTA12.westchester.pa.mail.comcast.net ([76.96.62.44]) by QMTA01.westchester.pa.mail.comcast.net with comcast id p7PA1Y00P0xGWP85102o00; Wed, 13 Feb 2008 19:30:10 +0000 Received: from Harrington73653 ([24.128.66.199]) by OMTA12.westchester.pa.mail.comcast.net with comcast id p7WF1Y00K4HwxpC3Y00000; Wed, 13 Feb 2008 19:30:21 +0000 X-Authority-Analysis: v=1.0 c=1 a=48vgC7mUAAAA:8 a=pN97noSpMnYpo8LAzDEA:9 a=PrGIxpRL7ESBDKpO4vIA:7 a=MXgra5dG5e5eZ4cl7k4y5DrTbScA:4 a=lZB815dzVvQA:10 a=50e4U0PicR4A:10 From: "David Harrington" To: "'Andy Bierman'" , "'yang'" , "'NETCONF Goes On'" References: <47B2F858.2080309@andybierman.com> Date: Wed, 13 Feb 2008 14:30:15 -0500 Message-ID: <035301c86e76$dcf06f00$0600a8c0@china.huawei.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AchuSRJfhtyigohRRPK/+aVkAw/9RAAHiXag In-Reply-To: <47B2F858.2080309@andybierman.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Subject: Re: [YANG] [NGO] reusable types and groupings X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, Like Andy, I'm a bit concerned about the reordering requirements. I have three concerns. 1) In RFC3535, operators said they don't want data arbitrarily reordered: 10. It is highly desirable that text processing tools such as diff, and version management tools such as RCS or CVS, can be used to process configurations, which implies that devices should not arbitrarily reorder data such as access control lists. YANG supports "system ordering", which seems counter to the requirements expressed by operators. 7.7.4.1. ordered-by system The entries in the list are sorted according to an unspecified order. Thus an implementation is free to sort the entries in the most appropriate order. An implementation SHOULD use the same order for the same data, regardless of how the data were created. Using a deterministic order will makes comparisons possible using simple tools like "diff". This is the default order. This seems totally counter to the operators' requests. A deterministic order for making comparisons should be defined by a vendor-independent interoperable standard that specifies the order, not a "system" order defined by each vendor. 2) Simplicity YANG supports user-ordered lists: In the other style of lists, the order of list entries matters for the implementation of the list's configuration and the user is responsible for ordering the entries, while the device maintains that order. YANG calls this style of list "user ordered" and they are indicated with the statement "ordered-by user". For example, the order in which firewall filters entries are applied to incoming traffic may affect how that traffic is filtered. The user would need to decide if the filter entry that discards all TCP traffic should be applied before or after the filter entry that allows all traffic from trusted interfaces. The choice of order would be crucial. In an "ordered-by user" leaf-list, the attributes "insert" and "value" in the YANG namespace (Section 5.4.1) can be used to control where in the leaf-list the entry is inserted. These can be used during "create" operations to insert a new leaf-list entry, or during "merge" or "replace" operations to insert a new leaf-list entry or move an existing one. This strikes me as being too oriented toward a specific implementation strategy, and I have a concern that a managed node needs to keep a lot of meta-information about the sort order to be able to return data in a user-specified order based on a user-ordered linked-list approach. I think this adds much complexity on the device with little benefit, compared to defining the data order as part of a standard data model. Is this something that operators have requested? I didn't see this requirement in RFC3535. 3) Keep the agent simple Traditionally, the IETF Management Framework has kept complexity off the managed device. Where complex functionality is needed, such as reordering data or deriving values from other values, it is done by the NMS, not by the managed device. I want my routers routing and my switches switching, not spending a lot of time reordering buffers of data (or calculating standard deviations, or mean values, or whatever). Sorting the data into whatever order I want depends on the the specific task I am working on, off the device. I can have my NMS application on my PC reorder the data, where I typically do not have network-operations-critical processing occurring, and where I typically have lots of resources available. dbh > -----Original Message----- > From: ngo-bounces@ietf.org [mailto:ngo-bounces@ietf.org] On > Behalf Of Andy Bierman > Sent: Wednesday, February 13, 2008 9:02 AM > To: yang; NETCONF Goes On > Subject: [NGO] reusable types and groupings > > Hi, > > There are some important CANMOD requirements that are not > agreed upon, including deep keys, and perhaps reusable complex > structures. > > There is a difference between a reusable container on the wire > and a conceptual set of sibling nodes defined in an off-line document. > A container can be processed by shared code that knows > the syntax and semantics of that container. > (Any C programmer knows the difference between 'typedef struct foo_t' > and '#define FOO_ITEMS'.) > > The IETF needs the ability to define standard NETCONF models > which include reusable containers (conceptual and on-the-wire), > and the ability to use leafs from those containers in the key > for a list. > The examples that keep coming up are quire relevant to networking, > like address/zone index, address/port, etc. > > The YANG draft specifies that instances of lists are > reordered on-the-wire > so all the leaf nodes are encoded first (instead of where they belong > based on document order), para 2 and 3 below: > > 7.8.5. XML Encoding Rules > > A list is encoded as a series of XML elements, one for > each entry in > the list. Each element's name is the list's > identifier, and its XML > namespace is the module's XML namespace. > > The list's key nodes are encoded as subelements to the list's > identifier element, in the same order as they are > defined within the > key statement. > > The rest of the list's child nodes are encoded as > subelements to the > list element, after the keys, in the same order as > they are defined > within the list statement. > > There is no explanation in the draft why this done, or > considered a feature. > It would obviously never work with deep keys, since removing them > from the sub-tree changes their identity (/name is not the > same as /foo/name). > > Even if the same grouping is used in 2 different lists, or > in a container, it won't be a reusable container on the wire at all. > > grouping stats_entry { > leaf src_addr { type smi:InetAddress; } > leaf dst_addr { type smi:InetAddress; } > leaf octets { type smi:Counter32; } > leaf packets { type smi:Counter32; } > leaf last_active_time { type smi:DateAndTime' } > } > > container A { > uses stats_entry; > } > > list B { > key "src_addr dst_addr"; > uses stats_entry; > } > > list C { > key "dst_addr src_addr"; > uses stats_entry; > } > > list D { > key "last_active_time"; > uses stats_entry; > } > > > Only 'container A' and 'list B' will be encoded on the wire > in document order. > Even worse, there is no way to model the real intent, which > is to have one real stats list, and different ways of sorting > the entries. > > > > Andy > > _______________________________________________ > NGO mailing list > NGO@ietf.org > http://www.ietf.org/mailman/listinfo/ngo > _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 13 11:36:25 2008 Return-Path: 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 3679E3A6FB5; Wed, 13 Feb 2008 11:36:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.004 X-Spam-Level: X-Spam-Status: No, score=-1.004 tagged_above=-999 required=5 tests=[AWL=-0.567, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 vmtjyTRaljge; Wed, 13 Feb 2008 11:36:24 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D2133A6844; Wed, 13 Feb 2008 11:36:23 -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 E819F3A67A2; Wed, 13 Feb 2008 11:36:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 nBQeZ1f2dYNs; Wed, 13 Feb 2008 11:36:20 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 999F23A6804; Wed, 13 Feb 2008 11:36:20 -0800 (PST) Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 978C68AEC5; Wed, 13 Feb 2008 20:37:42 +0100 (CET) Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 30455-05-3; Wed, 13 Feb 2008 20:37:37 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 41DCE8AF9C; Wed, 13 Feb 2008 20:37:37 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 180924B0CAA; Wed, 13 Feb 2008 20:37:36 +0100 (CET) Date: Wed, 13 Feb 2008 20:37:35 +0100 From: Juergen Schoenwaelder To: David Harrington Message-ID: <20080213193735.GB775@elstar.local> Mail-Followup-To: David Harrington , 'Andy Bierman' , 'yang' , 'NETCONF Goes On' References: <47B2F858.2080309@andybierman.com> <035301c86e76$dcf06f00$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <035301c86e76$dcf06f00$0600a8c0@china.huawei.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de Cc: 'yang' , 'NETCONF Goes On' Subject: Re: [YANG] [NGO] reusable types and groupings X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: j.schoenwaelder@jacobs-university.de List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org On Wed, Feb 13, 2008 at 02:30:15PM -0500, David Harrington wrote: > Like Andy, I'm a bit concerned about the reordering requirements. I > have three concerns. > > 1) In RFC3535, operators said they don't want data arbitrarily > reordered: > > 10. It is highly desirable that text processing tools such as diff, > and version management tools such as RCS or CVS, can be used to > process configurations, which implies that devices should not > arbitrarily reorder data such as access control lists. > > YANG supports "system ordering", which seems counter to the > requirements expressed by operators. It simply depends on the data. For some data, people are used that the system puts it into a canonical order, regardless in which order it was created. A typical example is an IP forwarding table which is typically ordered by the prefixes. > 7.7.4.1. ordered-by system > > The entries in the list are sorted according to an unspecified > order. > Thus an implementation is free to sort the entries in the most > appropriate order. An implementation SHOULD use the same order for > the same data, regardless of how the data were created. Using a > deterministic order will makes comparisons possible using simple > tools like "diff". > > This is the default order. > > This seems totally counter to the operators' requests. > A deterministic order for making comparisons should be defined by a > vendor-independent interoperable standard that specifies the order, > not a "system" order defined by each vendor. This ordered-by system tells us simply that the order is maintained by the system. It is up to the writer of the description clause to specify what the order is if there is a commonly used and agreeable order for things (like in the IP forwarding table case). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 13 12:10:59 2008 Return-Path: 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 C57CC3A6913; Wed, 13 Feb 2008 12:10:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.724 X-Spam-Level: X-Spam-Status: No, score=-0.724 tagged_above=-999 required=5 tests=[AWL=-0.287, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 GFy0OFw5iePb; Wed, 13 Feb 2008 12:10:58 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 943DC3A683B; Wed, 13 Feb 2008 12:10:58 -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 92CBD3A6814 for ; Wed, 13 Feb 2008 12:10:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 eZJLo+GtiZ8W for ; Wed, 13 Feb 2008 12:10:56 -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 5A1D23A6864 for ; Wed, 13 Feb 2008 12:10:56 -0800 (PST) Received: (qmail 98899 invoked from network); 13 Feb 2008 20:12:19 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@68.120.85.9 with plain) by smtp116.sbc.mail.sp1.yahoo.com with SMTP; 13 Feb 2008 20:12:18 -0000 X-YMail-OSG: IXNgdAcVM1lvNH2WoeDaHbE8r6dgqKYZxMEMtEFFaK3zwrww8Q.M7cls55TIYYzQr96HaYcAjUAxOJd96hhWo1jN X-Yahoo-Newman-Property: ymail-3 Message-ID: <47B34F22.3020400@andybierman.com> Date: Wed, 13 Feb 2008 12:12:18 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: David Harrington References: <47B2F858.2080309@andybierman.com> <035301c86e76$dcf06f00$0600a8c0@china.huawei.com> In-Reply-To: <035301c86e76$dcf06f00$0600a8c0@china.huawei.com> Cc: 'yang' , 'NETCONF Goes On' Subject: Re: [YANG] [NGO] reusable types and groupings X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org David Harrington wrote: > Hi, > > Like Andy, I'm a bit concerned about the reordering requirements. I > have three concerns. > This issue with the XML encoding of 'list' is different than the 'insert' and 'key' XML attribute extensions to the NETCONF protocol. Those extensions to the operation support the use case in which the DM writer does not want to use a key, but still keep a specific sort order, provided by the user. Data structures like access control lists could be modeled with 'line numbers' as the index for each rule, or simply managed by the user instead without numbering each rule. This is a more elegant solution than the SNMP 'arbitrary INTEGER index', and ever requires renumbering the rules. The purpose of moving the key leafs from their document order is to favor agent implementations that do not want to buffer the incoming NETCONF PDU. By providing all the naming information in the first N leafs, the agent can direct the request to a sub-agent more efficiently, similar to an AGENTX master agent that may look into a varbind (which always contains all the naming information for each leaf -- very redundant encoding but useful for sub-agent dispatching). IMO, NETCONF PDUs represent such a small percentage of the bandwidth and memory resources needed by an agent, and the 'special case' impact on manager applications is not worth the memory resources on the agent needed to receive an entire PDU before processing it completely. The 'key leaf within a container' issue could be considered separate, but it is related to this PDU buffering issue. I would rather have a blatant CLR that says key leafs MUST be the first nodes defined in a list, rather than some weird XML encoding rules just for YANG lists. Andy > 1) In RFC3535, operators said they don't want data arbitrarily > reordered: > > 10. It is highly desirable that text processing tools such as diff, > and version management tools such as RCS or CVS, can be used to > process configurations, which implies that devices should not > arbitrarily reorder data such as access control lists. > > YANG supports "system ordering", which seems counter to the > requirements expressed by operators. > > 7.7.4.1. ordered-by system > > The entries in the list are sorted according to an unspecified > order. > Thus an implementation is free to sort the entries in the most > appropriate order. An implementation SHOULD use the same order for > the same data, regardless of how the data were created. Using a > deterministic order will makes comparisons possible using simple > tools like "diff". > > This is the default order. > > This seems totally counter to the operators' requests. > A deterministic order for making comparisons should be defined by a > vendor-independent interoperable standard that specifies the order, > not a "system" order defined by each vendor. > > 2) Simplicity > > YANG supports user-ordered lists: > > In the other style of lists, the order of list entries matters > for > the implementation of the list's configuration and the user is > responsible for ordering the entries, while the device maintains > that > order. YANG calls this style of list "user ordered" and they are > indicated with the statement "ordered-by user". > > For example, the order in which firewall filters entries are > applied > to incoming traffic may affect how that traffic is filtered. The > user would need to decide if the filter entry that discards all TCP > traffic should be applied before or after the filter entry that > allows all traffic from trusted interfaces. The choice of order > would be crucial. > > In an "ordered-by user" leaf-list, the attributes "insert" and > "value" in the YANG namespace (Section 5.4.1) can be used to > control > where in the leaf-list the entry is inserted. These can be used > during "create" operations to insert a new leaf-list entry, or > during > "merge" or "replace" operations to insert a new leaf-list entry or > move an existing one. > > This strikes me as being too oriented toward a specific implementation > strategy, and I have a concern that a managed node needs to keep a lot > of meta-information about the sort order to be able to return data in > a user-specified order based on a user-ordered linked-list approach. I > think this adds much complexity on the device with little benefit, > compared to defining the data order as part of a standard data model. > > Is this something that operators have requested? I didn't see this > requirement in RFC3535. > > > 3) Keep the agent simple > > Traditionally, the IETF Management Framework has kept complexity off > the managed device. Where complex functionality is needed, such as > reordering data or deriving values from other values, it is done by > the NMS, not by the managed device. I want my routers routing and my > switches switching, not spending a lot of time reordering buffers of > data (or calculating standard deviations, or mean values, or > whatever). Sorting the data into whatever order I want depends on the > the specific task I am working on, off the device. I can have my NMS > application on my PC reorder the data, where I typically do not have > network-operations-critical processing occurring, and where I > typically have lots of resources available. > > dbh > >> -----Original Message----- >> From: ngo-bounces@ietf.org [mailto:ngo-bounces@ietf.org] On >> Behalf Of Andy Bierman >> Sent: Wednesday, February 13, 2008 9:02 AM >> To: yang; NETCONF Goes On >> Subject: [NGO] reusable types and groupings >> >> Hi, >> >> There are some important CANMOD requirements that are not >> agreed upon, including deep keys, and perhaps reusable complex >> structures. >> >> There is a difference between a reusable container on the wire >> and a conceptual set of sibling nodes defined in an off-line > document. >> A container can be processed by shared code that knows >> the syntax and semantics of that container. >> (Any C programmer knows the difference between 'typedef struct > foo_t' >> and '#define FOO_ITEMS'.) >> >> The IETF needs the ability to define standard NETCONF models >> which include reusable containers (conceptual and on-the-wire), >> and the ability to use leafs from those containers in the key >> for a list. >> The examples that keep coming up are quire relevant to networking, >> like address/zone index, address/port, etc. >> >> The YANG draft specifies that instances of lists are >> reordered on-the-wire >> so all the leaf nodes are encoded first (instead of where they > belong >> based on document order), para 2 and 3 below: >> >> 7.8.5. XML Encoding Rules >> >> A list is encoded as a series of XML elements, one for >> each entry in >> the list. Each element's name is the list's >> identifier, and its XML >> namespace is the module's XML namespace. >> >> The list's key nodes are encoded as subelements to the list's >> identifier element, in the same order as they are >> defined within the >> key statement. >> >> The rest of the list's child nodes are encoded as >> subelements to the >> list element, after the keys, in the same order as >> they are defined >> within the list statement. >> >> There is no explanation in the draft why this done, or >> considered a feature. >> It would obviously never work with deep keys, since removing them >> from the sub-tree changes their identity (/name is not the >> same as /foo/name). >> >> Even if the same grouping is used in 2 different lists, or >> in a container, it won't be a reusable container on the wire at all. >> >> grouping stats_entry { >> leaf src_addr { type smi:InetAddress; } >> leaf dst_addr { type smi:InetAddress; } >> leaf octets { type smi:Counter32; } >> leaf packets { type smi:Counter32; } >> leaf last_active_time { type smi:DateAndTime' } >> } >> >> container A { >> uses stats_entry; >> } >> >> list B { >> key "src_addr dst_addr"; >> uses stats_entry; >> } >> >> list C { >> key "dst_addr src_addr"; >> uses stats_entry; >> } >> >> list D { >> key "last_active_time"; >> uses stats_entry; >> } >> >> >> Only 'container A' and 'list B' will be encoded on the wire >> in document order. >> Even worse, there is no way to model the real intent, which >> is to have one real stats list, and different ways of sorting >> the entries. >> >> >> >> Andy >> >> _______________________________________________ >> NGO mailing list >> NGO@ietf.org >> http://www.ietf.org/mailman/listinfo/ngo >> > > > > > _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 13 12:56:30 2008 Return-Path: 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 53A883A6FAC; Wed, 13 Feb 2008 12:56:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[AWL=-1.459, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 l1HXrvtSRCWn; Wed, 13 Feb 2008 12:56:29 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C6323A6942; Wed, 13 Feb 2008 12:56:28 -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 60A813A67A2; Wed, 13 Feb 2008 12:56:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 h-OEBUpaYqF8; Wed, 13 Feb 2008 12:56:24 -0800 (PST) Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id 273643A67CF; Wed, 13 Feb 2008 12:56:23 -0800 (PST) Received: from source ([66.129.224.36]) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP; Wed, 13 Feb 2008 12:57:32 PST Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 13 Feb 2008 12:57:09 -0800 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 m1DKvBq02638; Wed, 13 Feb 2008 12:57:11 -0800 (PST) (envelope-from phil@idle.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 m1DKumDY087360; Wed, 13 Feb 2008 20:56:48 GMT (envelope-from phil@idle.juniper.net) Message-Id: <200802132056.m1DKumDY087360@idle.juniper.net> To: "David Harrington" In-reply-to: <035301c86e76$dcf06f00$0600a8c0@china.huawei.com> Date: Wed, 13 Feb 2008 15:56:48 -0500 From: Phil Shafer X-OriginalArrivalTime: 13 Feb 2008 20:57:09.0210 (UTC) FILETIME=[FF8A0BA0:01C86E82] Cc: 'yang' , 'NETCONF Goes On' Subject: Re: [YANG] [NGO] reusable types and groupings X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org "David Harrington" writes: > 10. It is highly desirable that text processing tools such as diff, > and version management tools such as RCS or CVS, can be used to > process configurations, which implies that devices should not > arbitrarily reorder data such as access control lists. > >YANG supports "system ordering", which seems counter to the >requirements expressed by operators. "ordered-by system" means the system defines the rules for ordering (such as alphabetically), not that the order is arbitrary. As such, the order should be consistent as config is fetched over time, enhancing the ability of text-based tools to work with configurations. >This strikes me as being too oriented toward a specific implementation >strategy, and I have a concern that a managed node needs to keep a lot >of meta-information about the sort order to be able to return data in >a user-specified order based on a user-ordered linked-list approach. I >think this adds much complexity on the device with little benefit, >compared to defining the data order as part of a standard data model. It has less to do with the implementation than the nature of the data being modeled. If I'm modeling login names, the order is unimportant, but if I'm modeling actions performed inside a firewall filter, the order of those actions affects the ability to perform the required filtering. >I want my routers routing and my >switches switching, not spending a lot of time reordering buffers of >data (or calculating standard deviations, or mean values, or >whatever). Sorting the data into whatever order I want depends on the >the specific task I am working on, off the device. In YANG, the order is either important to the data, in which case the user/application is responsible for dictating the order, or it is not important, in which case the system is allowed to sort it in a natural order. The order will often be detailed in the description statement of the list, but will not be arbitrary, random, or based on nonsense such as standard deviations or mean values. If your application requires such specific sorting, you are free to perform this sort after (or as) the data is downloaded from the device. Thanks, Phil _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Thu Feb 14 00:46:50 2008 Return-Path: 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 7655128C7EA; Thu, 14 Feb 2008 00:46:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.452 X-Spam-Level: X-Spam-Status: No, score=-1.452 tagged_above=-999 required=5 tests=[AWL=-1.015, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 mCExnngSM86Z; Thu, 14 Feb 2008 00:46:49 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE0583A7064; Thu, 14 Feb 2008 00:46:48 -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 6FF363A682B; Thu, 14 Feb 2008 00:46:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 opeH3ssj1L-g; Thu, 14 Feb 2008 00:46:46 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 460A13A705B; Thu, 14 Feb 2008 00:46:45 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id E14E121426; Thu, 14 Feb 2008 09:48:06 +0100 (CET) X-AuditID: c1b4fb3e-a89fbbb000000b15-6d-47b40046da4c Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id CC18B20159; Thu, 14 Feb 2008 09:48:06 +0100 (CET) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 14 Feb 2008 09:48:05 +0100 Received: from [159.107.197.224] ([159.107.197.224]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 14 Feb 2008 09:48:04 +0100 Message-ID: <47B40044.2000109@ericsson.com> Date: Thu, 14 Feb 2008 09:48:04 +0100 From: Balazs Lengyel User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: Andy Bierman References: <47B2F858.2080309@andybierman.com> In-Reply-To: <47B2F858.2080309@andybierman.com> X-OriginalArrivalTime: 14 Feb 2008 08:48:05.0012 (UTC) FILETIME=[5060E540:01C86EE6] X-Brightmail-Tracker: AAAAAA== Cc: yang , NETCONF Goes On Subject: Re: [YANG] [NGO] reusable types and groupings X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org If we would allow putting the key inside the grouping that would avoid the reordering problem as the keys would have a fixed place. I had a very similar problem recently. I want to use the containers/groupings as managed objects (just like the Siemens/Nokia guys). However I am not allowed to put the "key" statement inside a grouping which is a problem. It is clearly part of an objects definition/sematics to identify which piece of data is the key. Balazs Andy Bierman wrote: > Hi, > > There are some important CANMOD requirements that are not > agreed upon, including deep keys, and perhaps reusable complex > structures. > > There is a difference between a reusable container on the wire > and a conceptual set of sibling nodes defined in an off-line document. > A container can be processed by shared code that knows > the syntax and semantics of that container. > (Any C programmer knows the difference between 'typedef struct foo_t' > and '#define FOO_ITEMS'.) > > The IETF needs the ability to define standard NETCONF models > which include reusable containers (conceptual and on-the-wire), > and the ability to use leafs from those containers in the key for a list. > The examples that keep coming up are quire relevant to networking, > like address/zone index, address/port, etc. > > > Even if the same grouping is used in 2 different lists, or > in a container, it won't be a reusable container on the wire at all. > > grouping stats_entry { > leaf src_addr { type smi:InetAddress; } > leaf dst_addr { type smi:InetAddress; } > leaf octets { type smi:Counter32; } > leaf packets { type smi:Counter32; } > leaf last_active_time { type smi:DateAndTime' } > } > > container A { > uses stats_entry; > } > > list B { > key "src_addr dst_addr"; > uses stats_entry; > } > ... > list D { > key "last_active_time"; > uses stats_entry; > } > _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Thu Feb 21 00:44:57 2008 Return-Path: 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 9FC5028C9A2; Thu, 21 Feb 2008 00:44:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.023 X-Spam-Level: X-Spam-Status: No, score=-1.023 tagged_above=-999 required=5 tests=[AWL=-0.586, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 D8DcUaOmhA7S; Thu, 21 Feb 2008 00:44:56 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF45828C806; Thu, 21 Feb 2008 00:44:56 -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 342F628C806 for ; Thu, 21 Feb 2008 00:44:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 7BnyQlkSmsN6 for ; Thu, 21 Feb 2008 00:44:54 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 5AA2E28C74A for ; Thu, 21 Feb 2008 00:44:54 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id B103B21159 for ; Thu, 21 Feb 2008 09:44:20 +0100 (CET) X-AuditID: c1b4fb3e-a79f9bb000000b15-56-47bd39e4a5a3 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id A1D4521146 for ; Thu, 21 Feb 2008 09:44:20 +0100 (CET) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Feb 2008 09:41:01 +0100 Received: from [159.107.197.224] ([159.107.197.224]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Feb 2008 09:41:01 +0100 Message-ID: <47BD391D.3080005@ericsson.com> Date: Thu, 21 Feb 2008 09:41:01 +0100 From: Balazs Lengyel User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: yang@ietf.org X-OriginalArrivalTime: 21 Feb 2008 08:41:01.0560 (UTC) FILETIME=[7CDF7F80:01C87465] X-Brightmail-Tracker: AAAAAA== Subject: [YANG] Status and containment X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Is it allowed to have a current child in a deprecated or obsolete container/list/choice/rpc/notification/etc. I think no. I would add to 7.17.2. The status Statement "If a containing element in a model has the status obsolete, all it's sub-statements are also obsolete. If a containing element in a model has the status deprecated, all it's sub-statements are also deprecated, unless they are explicitly stated as obsolete." Shall I check this in? Balazs _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Thu Feb 21 11:20:17 2008 Return-Path: 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 8F40028C9DE; Thu, 21 Feb 2008 11:20:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.25 X-Spam-Level: X-Spam-Status: No, score=-0.25 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RCVD_IN_SORBS_WEB=0.619, RDNS_NONE=0.1] 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 A3safFCtrpc3; Thu, 21 Feb 2008 11:20:16 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C522B28C67F; Thu, 21 Feb 2008 11:20:16 -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 BB4AC28C67F for ; Thu, 21 Feb 2008 11:20:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 qeCwPN-hif6I for ; Thu, 21 Feb 2008 11:20:10 -0800 (PST) Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id BF09B28C611 for ; Thu, 21 Feb 2008 11:20:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=bG6fbW14CtZihAkhqiot36FkDdyUUGQqE3KF6oWNcTpsXFvVn8UH8qbkEx5/1pYC; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.203.55] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1JSGxh-0006Wt-NS for yang@ietf.org; Thu, 21 Feb 2008 14:20:06 -0500 Message-ID: <004101c874be$e6d0a1e0$6801a8c0@oemcomputer> From: "Randy Presuhn" To: References: <47BD391D.3080005@ericsson.com> Date: Thu, 21 Feb 2008 11:21:03 -0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc89117b3115e22e04a142edea0bcefdcb42c6b350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.203.55 Subject: Re: [YANG] Status and containment X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi - > From: "Balazs Lengyel" > To: > Sent: Thursday, February 21, 2008 12:41 AM > Subject: [YANG] Status and containment > > Is it allowed to have a current child in a deprecated or obsolete > container/list/choice/rpc/notification/etc. I think no. > > I would add to 7.17.2. The status Statement > > "If a containing element in a model has the status obsolete, all it's sub-statements are also > obsolete. > > If a containing element in a model has the status deprecated, all it's sub-statements are also > deprecated, unless they are explicitly stated as obsolete." ... How would this affect modules that re-use of any of those children? Randy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Fri Feb 22 10:38:10 2008 Return-Path: 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 3A85328C345; Fri, 22 Feb 2008 10:38:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.006 X-Spam-Level: X-Spam-Status: No, score=-1.006 tagged_above=-999 required=5 tests=[AWL=-1.169, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_63=0.6, RDNS_NONE=0.1] 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 QU3Z608LvH4F; Fri, 22 Feb 2008 10:38:09 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D4B13A68CD; Fri, 22 Feb 2008 10:38:09 -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 104B13A6806 for ; Fri, 22 Feb 2008 10:38:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 phB9XqraVkD4 for ; Fri, 22 Feb 2008 10:38:07 -0800 (PST) Received: from smtp119.sbc.mail.sp1.yahoo.com (smtp119.sbc.mail.sp1.yahoo.com [69.147.64.92]) by core3.amsl.com (Postfix) with SMTP id 3BAE63A68CD for ; Fri, 22 Feb 2008 10:38:07 -0800 (PST) Received: (qmail 65811 invoked from network); 22 Feb 2008 18:38:03 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.127.172.9 with plain) by smtp119.sbc.mail.sp1.yahoo.com with SMTP; 22 Feb 2008 18:38:02 -0000 X-YMail-OSG: ba4PDkgVM1lKXH1gW9elLh4gm7IuBLW63e1QqfeYbyWDkbcM X-Yahoo-Newman-Property: ymail-3 Message-ID: <47BF167B.8060709@andybierman.com> Date: Fri, 22 Feb 2008 10:37:47 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang Subject: [YANG] Identifiers X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 know I brought this up a year ago, but there is still a problem with definition identifiers. (There are not defined.) There are 3 types of identifiers in YANG/NETCONF. Applications may need to use all 3 types: 1) Instance Identifier 2) Object Identifier 3) Definition Identifier (1) An instance identifier is an Xpath expression which is defined with the instance-identifier built-in type. It represents one conceptual instance of an object. It can contain prefixes, which are XML namespace prefixes, not module prefixes. It never includes meta-nodes (e.g., input, output, choice, case), only real nodes, in the config: /if:interfaces/if:interface[if:name='eth0']/if:ifInOctets (2) An object identifier is an Xpath expression that specifies one conceptual object within a module, and it can contain module prefixes (e.g., augment target). Meta-nodes such input, output, choice-identifier, case-identifier, are included in the Xpath expression. A missing prefix indicates the current module, not the prefix of the parent node. Key values are never included in the Xpath expression. /interfaces/interface/ifInOctets /interface/interface/acme:acme-choice1/acme:case1/acme:acme-knob1 /interface/interface/acme:acme-choice1/acme:case2/acme:acme-knob1-alt (3) A definition identifier is the unambiguous string that identifies any particular user-defined object construct. Unlike an object identifier, it must be context-free, and cannot include any prefixes, which must be evaluated within the context of a specific module. YANG has several different naming scopes for objects (objects/rpcs/notifications, and groupings), so some conventions are needed to prevent naming collisions. Sometimes it is useful to distinguish between the 'foo-knob' defined in the 'foo' grouping, and a 'foo-knob' leaf expanded from a 'uses foo;' statement. The definition identifier must account for nested groupings, objects, and augments. I came up with the following hack (relying on the fact that the first char in an identifier cannot be '.') - the full [sub]module name is used as the starting prefix and must be present. - the parent module is used if none is specified in a node - a different module can only appear if a top-level augment in a different module added nodes within the first module. - grouping names are prefixed with '.' (in the identifier only) - uses and augments are transparent -- only the outcome of the expansion is specified within a definition identifier - otherwise the string follows object identifier syntax ifmib:interfaces/interface/acme-defs:acme-choice1/case1/acme-knob1 Consider the following simple example (from the 'foomod' module): grouping bar { leaf baz { type int32; } grouping bar2 { leaf bar2 { type string; } } container bar2 { uses bar2; } } container goo { uses bar; } A 'baz' object within the 'bar' grouping within the 'goo' container would look like: foomod:goo/.bar/baz The baz object used within the goo container would not have the grouping in the string: foomod:goo/baz The full set of definition identifiers: foomod:.bar foomod:.bar/baz foomod:.bar/.bar2 foomod:.bar/.bar2/bar2 foomod:.bar/bar2 foomod:.bar/bar2/bar2 foomod:goo foomod:goo/baz foomod:goo/bar2 foomod:goo/bar2/bar2 To complete (and complicate things), a definition identifier can terminate with a 'revision-suffix', to indicate the definition from a specific version of the [sub]module. A missing suffix implies the most current version: foomod:.bar/.bar2/bar2?2008-01-14 foomod:goo/bar2?2008-02-22 Definition identifiers could be considered an application implementation detail, or they could be considered part of the standard. Comments? Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Fri Feb 22 10:52:19 2008 Return-Path: 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 8871D28C965; Fri, 22 Feb 2008 10:52:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.634 X-Spam-Level: X-Spam-Status: No, score=-1.634 tagged_above=-999 required=5 tests=[AWL=-1.197, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 D9D8uDhQY4Eu; Fri, 22 Feb 2008 10:52:18 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A9E328CB22; Fri, 22 Feb 2008 10:51:38 -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 9705B28CB19 for ; Fri, 22 Feb 2008 10:51:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 Z0acARU2mvyK for ; Fri, 22 Feb 2008 10:51:35 -0800 (PST) Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id 8926028CB51 for ; Fri, 22 Feb 2008 10:48:34 -0800 (PST) Received: from source ([66.129.224.36]) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP; Fri, 22 Feb 2008 10:48:29 PST Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 22 Feb 2008 10:48:09 -0800 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 m1MIm8q10864; Fri, 22 Feb 2008 10:48:08 -0800 (PST) (envelope-from phil@idle.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 m1MIlbkj055131; Fri, 22 Feb 2008 18:47:37 GMT (envelope-from phil@idle.juniper.net) Message-Id: <200802221847.m1MIlbkj055131@idle.juniper.net> To: Andy Bierman In-reply-to: <47BF167B.8060709@andybierman.com> Date: Fri, 22 Feb 2008 13:47:37 -0500 From: Phil Shafer X-OriginalArrivalTime: 22 Feb 2008 18:48:09.0231 (UTC) FILETIME=[77DEB9F0:01C87583] Cc: yang Subject: Re: [YANG] Identifiers X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Andy Bierman writes: >Definition identifiers could be considered an application implementation >detail, or they could be considered part of the standard. Comments? I'm slow, but I don't follow you. What problem does "definition identifiers" attempt to solve? Do you have a couple of real-world use cases? Thanks, Phil _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Fri Feb 22 11:03:02 2008 Return-Path: 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 9144428C406; Fri, 22 Feb 2008 11:03:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.194 X-Spam-Level: X-Spam-Status: No, score=-1.194 tagged_above=-999 required=5 tests=[AWL=-0.757, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 KujNZwPkz24o; Fri, 22 Feb 2008 11:03:01 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F0C128C348; Fri, 22 Feb 2008 11:03:01 -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 65F0B3A6CD6 for ; Fri, 22 Feb 2008 11:02:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 b2lSKALA8VJT for ; Fri, 22 Feb 2008 11:02:58 -0800 (PST) Received: from smtp101.sbc.mail.mud.yahoo.com (smtp101.sbc.mail.mud.yahoo.com [68.142.198.200]) by core3.amsl.com (Postfix) with SMTP id 5D8CF28C4BE for ; Fri, 22 Feb 2008 11:02:21 -0800 (PST) Received: (qmail 12549 invoked from network); 22 Feb 2008 19:02:16 -0000 Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.127.172.9 with plain) by smtp101.sbc.mail.mud.yahoo.com with SMTP; 22 Feb 2008 19:02:16 -0000 X-YMail-OSG: RP8kyT0VM1kwvEKFgOkW.IDlLNoHf0LBDaieS_OktWR7amhe X-Yahoo-Newman-Property: ymail-3 Message-ID: <47BF1C28.3070109@andybierman.com> Date: Fri, 22 Feb 2008 11:02:00 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Phil Shafer References: <200802221847.m1MIlbkj055131@idle.juniper.net> In-Reply-To: <200802221847.m1MIlbkj055131@idle.juniper.net> Cc: yang Subject: Re: [YANG] Identifiers X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Phil Shafer wrote: > Andy Bierman writes: >> Definition identifiers could be considered an application implementation >> detail, or they could be considered part of the standard. Comments? > > I'm slow, but I don't follow you. What problem does "definition > identifiers" attempt to solve? Do you have a couple of real-world > use cases? > One use would be an application to auto-assist editing and diffing of YANG objects, track changes over time, etc. Since the 'uses' can refine and augment inner nodes, they will not always be the same as the grouping. Another use is an unambiguous reference within documents, but outside of YANG modules. This is more in line with standards, but does not need the grouping IDs, just context-free and version-specific. > Thanks, > Phil > > > Andy _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Mon Feb 25 09:09:36 2008 Return-Path: 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 A44BF3A6CD1; Mon, 25 Feb 2008 09:09:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.066 X-Spam-Level: X-Spam-Status: No, score=-1.066 tagged_above=-999 required=5 tests=[AWL=-0.629, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 I26mL98+6XF7; Mon, 25 Feb 2008 09:09:35 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98DBE28C7D8; Mon, 25 Feb 2008 09:07: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 0533E3A6D09 for ; Mon, 25 Feb 2008 08:59:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 3ynyaIgUfIyj for ; Mon, 25 Feb 2008 08:59:24 -0800 (PST) Received: from mx06.uni-tuebingen.de (mx06.uni-tuebingen.de [134.2.3.3]) by core3.amsl.com (Postfix) with ESMTP id C908A3A6D34 for ; Mon, 25 Feb 2008 08:59:23 -0800 (PST) Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138]) by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id m1PGxES8013521; Mon, 25 Feb 2008 17:59:15 +0100 Message-ID: <47C2F3E3.9020001@informatik.uni-tuebingen.de> Date: Mon, 25 Feb 2008 17:59:15 +0100 From: Gerhard Muenz User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: yang@ietf.org X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.6.0.67; VDF: 7.0.2.189; host: mx06) X-Mailman-Approved-At: Mon, 25 Feb 2008 09:07:04 -0800 Cc: Benoit Claise Subject: [YANG] IPFIX/PSAMP configuration data model X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1194754879==" Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org This is a cryptographically signed message in MIME format. --===============1194754879== Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030005040702000007000403" This is a cryptographically signed message in MIME format. --------------ms030005040702000007000403 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear YANGsters, As an author of the draft on IPFIX/PSAMP configuration, I would like to advise you of the new draft revision which makes use of YANG for specifying the configuration data model: http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-04.tx= t Before, we were using XML Schema which made it difficult to ensure compatibility with the Netconf protocol. Martin Bjorklund has helped to convert our specification into YANG. If you have time to have a look at the draft, I would very much appreciate additional feedback from you as experts in Netconf and YANG. Kind regards, Gerhard=09 --=20 Dipl.-Ing. Gerhard M=FCnz Computer Networks and Internet Wilhelm Schickard Institute for Computer Science University of Tuebingen Sand 13 (Room B309), D-72076 Tuebingen, Germany Phone: +49 7071 29-70534 Fax: +49 7071 29-5220 E-mail: muenz@informatik.uni-tuebingen.de WWW: http://net.informatik.uni-tuebingen.de/~muenz --------------ms030005040702000007000403 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJdTCC AxUwggJ+oAMCAQICED9aGsYWkMr+s4zmyODhB+IwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDIxMzE1MTUxN1oX DTA5MDIxMjE1MTUxN1owbDEOMAwGA1UEBBMFTXVlbnoxEDAOBgNVBCoTB0dlcmhhcmQxFjAU BgNVBAMTDUdlcmhhcmQgTXVlbnoxMDAuBgkqhkiG9w0BCQEWIW11ZW56QGluZm9ybWF0aWsu dW5pLXR1ZWJpbmdlbi5kZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMZex/Sq sAxkzTVvKP/YAgkaeXA+ngH59Aa0bbRPsKOWzAndGqty5EKcEzrnKqEJ27qHFvoF/pHp88U2 7SJI/xbqkgWeV2jRaldipZQYlnjYLQcmb4cewIFuGRRSVrm3BquzX38aYazuE4+DVH2Z3a8z n0FcdMXhA1NR2Ma1rh4G7SIeZ+hC7czbvNRPraBliGdQhs8J/6yP/iL8aNYAl9c7CL4ofRj8 Y9orMOV/4vtWTq76/VQUVdbhUMiv0D8aHqI1ZvGskhRRvmITgQRVbbn8N8WTpZ0UCgMDjxPP 9i5IhLfp6oBtsKl4OZ0RXvSLZrbJTkBX3vnEutcyxDvyNgMCAwEAAaM+MDwwLAYDVR0RBCUw I4EhbXVlbnpAaW5mb3JtYXRpay51bmktdHVlYmluZ2VuLmRlMAwGA1UdEwEB/wQCMAAwDQYJ KoZIhvcNAQEFBQADgYEAX5SiD6epJePwBjJumOsTF6wzeuZRDLYlN+fOpXwd2C0Yx6i8iIZ9 l/J/nGaE1YpJPfX5oJDE+tOk1vYh2E9ThLOj9kJ3buZmgOCdVu90qtCWhfhli7RCYcJ+G9M3 FCnqbrzI/waPPXGB8/DY1HKgPj5G+oKPUK+GD2aE1Q3PYGowggMVMIICfqADAgECAhA/WhrG FpDK/rOM5sjg4QfiMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wODAyMTMxNTE1MTdaFw0wOTAyMTIxNTE1MTdaMGwx DjAMBgNVBAQTBU11ZW56MRAwDgYDVQQqEwdHZXJoYXJkMRYwFAYDVQQDEw1HZXJoYXJkIE11 ZW56MTAwLgYJKoZIhvcNAQkBFiFtdWVuekBpbmZvcm1hdGlrLnVuaS10dWViaW5nZW4uZGUw ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDGXsf0qrAMZM01byj/2AIJGnlwPp4B +fQGtG20T7CjlswJ3RqrcuRCnBM65yqhCdu6hxb6Bf6R6fPFNu0iSP8W6pIFnldo0WpXYqWU GJZ42C0HJm+HHsCBbhkUUla5twars19/GmGs7hOPg1R9md2vM59BXHTF4QNTUdjGta4eBu0i HmfoQu3M27zUT62gZYhnUIbPCf+sj/4i/GjWAJfXOwi+KH0Y/GPaKzDlf+L7Vk6u+v1UFFXW 4VDIr9A/Gh6iNWbxrJIUUb5iE4EEVW25/DfFk6WdFAoDA48Tz/YuSIS36eqAbbCpeDmdEV70 i2a2yU5AV975xLrXMsQ78jYDAgMBAAGjPjA8MCwGA1UdEQQlMCOBIW11ZW56QGluZm9ybWF0 aWsudW5pLXR1ZWJpbmdlbi5kZTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBAF+U og+nqSXj8AYybpjrExesM3rmUQy2JTfnzqV8HdgtGMeovIiGfZfyf5xmhNWKST31+aCQxPrT pNb2IdhPU4Szo/ZCd27mZoDgnVbvdKrQloX4ZYu0QmHCfhvTNxQp6m68yP8Gjz1xgfPw2NRy oD4+RvqCj1Cvhg9mhNUNz2BqMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/ cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8 YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4 oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4 Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEB MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0 ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhA/WhrG FpDK/rOM5sjg4QfiMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw HAYJKoZIhvcNAQkFMQ8XDTA4MDIyNTE2NTkxNVowIwYJKoZIhvcNAQkEMRYEFACaH0qny3Og kar8BMQ2lYJgjOBIMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3 EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ P1oaxhaQyv6zjObI4OEH4jCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUg UGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQP1oaxhaQyv6zjObI4OEH4jANBgkqhkiG 9w0BAQEFAASCAQAGRhzpaRZTkoYuL1dFIoUfsUr9dIZq6wKVPKQnqxQ/amounuFge/i5K0+E X4Hk2ke+zV2ekSflNbClncLKEydkN3R9pAQsgU13E0yJUoUNcnn9Wpq1/K/Qc2MqcbiFObj2 I3y1NF/8eAD6RwFCOygCov3Lt7HwJcQqHlodx7Y2+8YUioz/8BYnWp+KKZjToc9YAEL0zq1V Hqn1B5nWh5Ujq2yuY0yciLMUjofoXS9eQjrIFkp7SDXQ9AUpqvlLQN9Llw12jj7V7tofi1nz TN9n/Fq0210T+ibjLWUSengIzb1ppr+3pMrbiKqC9r3vrrOwi+buAWwwi3HonrbUELoTAAAA AAAA --------------ms030005040702000007000403-- --===============1194754879== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang --===============1194754879==-- From yang-bounces@ietf.org Tue Feb 26 08:18:35 2008 Return-Path: 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 8733928C508; Tue, 26 Feb 2008 08:18:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.464 X-Spam-Level: X-Spam-Status: No, score=-1.464 tagged_above=-999 required=5 tests=[AWL=-1.027, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 vYMzvClwQY9q; Tue, 26 Feb 2008 08:18:31 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E70EF28C3E5; Tue, 26 Feb 2008 08:18:30 -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 AB5FF28C32E; Tue, 26 Feb 2008 08:18:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 boFoMl6VB-jZ; Tue, 26 Feb 2008 08:18:28 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 78E7D28C1BA; Tue, 26 Feb 2008 08:18:28 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3FE3A20399; Tue, 26 Feb 2008 17:04:44 +0100 (CET) X-AuditID: c1b4fb3e-a91fcbb000000b15-5c-47c4389c0f2f Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 352072006D; Tue, 26 Feb 2008 17:04:44 +0100 (CET) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Feb 2008 17:04:43 +0100 Received: from selic023.lmera.ericsson.se ([150.132.89.214]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Feb 2008 17:02:54 +0100 From: David Partain Organization: Ericsson AB To: ngo@ietf.org, yang@ietf.org Date: Tue, 26 Feb 2008 17:02:52 +0100 User-Agent: KMail/1.9.9 References: <47B2F858.2080309@andybierman.com> <47B40044.2000109@ericsson.com> In-Reply-To: <47B40044.2000109@ericsson.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200802261702.53133.david.partain@ericsson.com> X-OriginalArrivalTime: 26 Feb 2008 16:02:54.0091 (UTC) FILETIME=[0BA36DB0:01C87891] X-Brightmail-Tracker: AAAAAA== Subject: [YANG] Question about a YANG meeting in Philly X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi all, Please forgive the cross-posting. Please strip ngo from any public responses and we'll take followup on the YANG list. Since many of those who are interested in the modeling for NETCONF question in general and YANG in particular, the YANG gang thinks it'd be a good idea to spend some time doing some YANG-related work during the upcoming IETF. Some ideas: 1. A tutorial on YANG with the latest updates since the last IETF? 2. A modeling session? It might be that people (like IPFIX and DNS have already started doing) want to use YANG for modeling their configuration problem.... 3. A CLR sweep? Go through YANG to get rid of unnecessary crappy little rules... 4. Discussion of specific technical questions? (we'll use yang-central.org to build the list of questions, in that case) Could be things like deep keys, actions/operations, etc.. Our ideas may be great, but it'd be far better if those who want to come tell us what they want the meeting to be about! As such, if you'd like to be there, please respond directly to me and tell me that you'd like to come and what you'd like the meeting to address in some kind of prioritized list. We don't know yet when this will be. Best guess at this point is Monday evening. No, this is _not_ official IETF business. It's just those of us who are interested getting together to work because we're all in the same place. Cheers, David _______________________________________________ YANG mailing list YANG@ietf.org http://www.ietf.org/mailman/listinfo/yang From yang-bounces@ietf.org Wed Feb 27 05:31:40 2008 Return-Path: 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 3A9CB28C2A0; Wed, 27 Feb 2008 05:31:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.638 X-Spam-Level: X-Spam-Status: No, score=-0.638 tagged_above=-999 required=5 tests=[AWL=-0.201, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] 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 NkUGPttZYRUc; Wed, 27 Feb 2008 05:31:39 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 279663A6A80; Wed, 27 Feb 2008 05:31:39 -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 0EF6D3A6A1A for ; Wed, 27 Feb 2008 05:31:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 BPcyL-fbzimP for ; Wed, 27 Feb 2008 05:31:32 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 49BA53A6A80 for ; Wed, 27 Feb 2008 05:31:32 -0800 (PST) Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id DD4358A6A2 for ; Wed, 27 Feb 2008 14:31:24 +0100 (CET) Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 23661-02-42; Wed, 27 Feb 2008 14:31:19 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id A89F28A78F; Wed, 27 Feb 2008 14:29:08 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id A6E664D30E6; Wed, 27 Feb 2008 14:29:07 +0100 (CET) Date: Wed, 27 Feb 2008 14:29:07 +0100 From: Juergen Schoenwaelder To: yang@ietf.org Message-ID: <20080227132907.GC5680@elstar.local> Mail-Followup-To: yang@ietf.org MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de Subject: [YANG] [j.schoenwaelder@jacobs-university.de: libsmi 0.4.6 released] X-BeenThere: yang@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: j.schoenwaelder@jacobs-university.de List-Id: YANG modeling Language for NETCONF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: yang-bounces@ietf.org Errors-To: yang-bounces@ietf.org Hi, this might be of interest to some people here... /js ----- Forwarded message from Juergen Schoenwaelder ----- Date: Wed, 27 Feb 2008 13:14:47 +0100 From: Juergen Schoenwaelder To: libsmi@ibr.cs.tu-bs.de Subject: libsmi 0.4.6 released Reply-To: j.schoenwaelder@jacobs-university.de Mail-Followup-To: libsmi@ibr.cs.tu-bs.de User-Agent: Mutt/1.5.17 (2007-11-01) Hi, we have just released version 0.4.6 of libsmi. Despite the usual number of bug fixes, this release contains some new code: - An implementation of RFC 3780 (the SMIng core) replacing the now historic SMIng parser together with an extended API to support SMIng. - An smidump backend which turns SMIv1/SMIv2 modules into YANG modules. It might take some while until package maintainers switch to the new version. As usual, you can get the source from ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/libsmi-0.4.6.tar.gz or the subversion directory directly. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 ----- End forwarded message ----- _______________________________________________ YANG mailing list YANG@ietf.org https://www.ietf.org/mailman/listinfo/yang