From internet-drafts@ietf.org Thu Jul 4 14:55:26 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F59021F9BC0; Thu, 4 Jul 2013 14:55:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.506 X-Spam-Level: X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZG+tEN8scXsS; Thu, 4 Jul 2013 14:55:24 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 908A611E80D3; Thu, 4 Jul 2013 14:55:20 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130704215520.28179.4034.idtracker@ietfa.amsl.com> Date: Thu, 04 Jul 2013 14:55:20 -0700 Cc: netmod@ietf.org Subject: [netmod] I-D Action: draft-ietf-netmod-iana-if-type-07.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 21:55:26 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the NETCONF Data Modeling Language Working Gr= oup of the IETF. Title : IANA Interface Type YANG Module Author(s) : Martin Bjorklund Filename : draft-ietf-netmod-iana-if-type-07.txt Pages : 40 Date : 2013-07-04 Abstract: This document defines the initial version of the iana-if-type YANG module. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-iana-if-type There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-netmod-iana-if-type-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netmod-iana-if-type-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Thu Jul 4 14:58:19 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C718D11E81FA; Thu, 4 Jul 2013 14:58:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.504 X-Spam-Level: X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f4vlE65THqMI; Thu, 4 Jul 2013 14:58:19 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D86F011E81DB; Thu, 4 Jul 2013 14:58:16 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130704215816.30530.64711.idtracker@ietfa.amsl.com> Date: Thu, 04 Jul 2013 14:58:16 -0700 Cc: netmod@ietf.org Subject: [netmod] I-D Action: draft-ietf-netmod-interfaces-cfg-12.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 21:58:19 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the NETCONF Data Modeling Language Working Gr= oup of the IETF. Title : A YANG Data Model for Interface Management Author(s) : Martin Bjorklund Filename : draft-ietf-netmod-interfaces-cfg-12.txt Pages : 44 Date : 2013-07-04 Abstract: This document defines a YANG data model for the management of network interfaces. It is expected that interface type specific data models augment the generic interfaces data model defined in this document. The data model includes configuration data, state data and counters for the collection of statistics. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-interfaces-cfg There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-netmod-interfaces-cfg-12 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netmod-interfaces-cfg-12 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Thu Jul 4 15:00:29 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1F1E21F9F97; Thu, 4 Jul 2013 15:00:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.501 X-Spam-Level: X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWGrsEgMBcsQ; Thu, 4 Jul 2013 15:00:29 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E14611E819D; Thu, 4 Jul 2013 15:00:28 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130704220028.3429.78697.idtracker@ietfa.amsl.com> Date: Thu, 04 Jul 2013 15:00:28 -0700 Cc: netmod@ietf.org Subject: [netmod] I-D Action: draft-ietf-netmod-system-mgmt-08.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 22:00:30 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the NETCONF Data Modeling Language Working Gr= oup of the IETF. Title : YANG Data Model for System Management Author(s) : Andy Bierman Martin Bjorklund Filename : draft-ietf-netmod-system-mgmt-08.txt Pages : 37 Date : 2013-07-04 Abstract: This document defines a YANG data model for the configuration and identification of some common system properties within a device containing a NETCONF server. This includes data node definitions for system identification, time-of-day management, user management, DNS resolver configuration, and some protocol operations for system management. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-netmod-system-mgmt-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netmod-system-mgmt-08 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From mbj@tail-f.com Thu Jul 4 15:04:58 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C63E11E80F5 for ; Thu, 4 Jul 2013 15:04:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iF5rX-yKYHQ6 for ; Thu, 4 Jul 2013 15:04:52 -0700 (PDT) Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id 2E62A21F9A18 for ; Thu, 4 Jul 2013 15:04:52 -0700 (PDT) Received: from localhost (213-65-182-102-no181.tbcn.telia.com [213.65.182.102]) by mail.tail-f.com (Postfix) with ESMTPSA id 53C001200D00 for ; Fri, 5 Jul 2013 00:04:50 +0200 (CEST) Date: Fri, 05 Jul 2013 00:04:49 +0200 (CEST) Message-Id: <20130705.000449.417733125.mbj@tail-f.com> To: netmod@ietf.org From: Martin Bjorklund In-Reply-To: <20130704215520.28179.4034.idtracker@ietfa.amsl.com> References: <20130704215520.28179.4034.idtracker@ietfa.amsl.com> X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [netmod] I-D Action: draft-ietf-netmod-iana-if-type-07.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 22:04:58 -0000 Hi, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the NETCONF Data Modeling Language > Working Group of the IETF. > > Title : IANA Interface Type YANG Module > Author(s) : Martin Bjorklund > Filename : draft-ietf-netmod-iana-if-type-07.txt > Pages : 40 > Date : 2013-07-04 > > Abstract: > This document defines the initial version of the iana-if-type YANG > module. We stumbled upon some problems with the AFN and SAFI IANA registries, and in order to not delay the interfaces document, the AFN and SAFI module has been moved to a separate document (uploaded, but awaiting approval). draft-ietf-netmod-iana-if-type-07 now contains the iana-if-type module only. /martin From internet-drafts@ietf.org Thu Jul 4 23:52:51 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E93911E8257; Thu, 4 Jul 2013 23:52:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.506 X-Spam-Level: X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rfvJz3RB5qQi; Thu, 4 Jul 2013 23:52:50 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3D6011E811D; Thu, 4 Jul 2013 23:52:49 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130705065249.7603.79975.idtracker@ietfa.amsl.com> Date: Thu, 04 Jul 2013 23:52:49 -0700 Cc: netmod@ietf.org Subject: [netmod] I-D Action: draft-ietf-netmod-iana-afn-safi-00.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jul 2013 06:52:51 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the NETCONF Data Modeling Language Working Gr= oup of the IETF. Title : IANA Address Family Numbers and Subsequent Address Famil= y Identifiers YANG Module Author(s) : Martin Bjorklund Filename : draft-ietf-netmod-iana-afn-safi-00.txt Pages : 20 Date : 2013-07-04 Abstract: This document defines the initial version of the iana-afn-safi YANG module. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-iana-afn-safi There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-netmod-iana-afn-safi-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From j.schoenwaelder@jacobs-university.de Fri Jul 5 05:28:36 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903F811E82BE for ; Fri, 5 Jul 2013 05:28:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.95 X-Spam-Level: X-Spam-Status: No, score=-101.95 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XNf7cHkJGjRX for ; Fri, 5 Jul 2013 05:28:32 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 159A111E82BD for ; Fri, 5 Jul 2013 05:28:31 -0700 (PDT) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 550B120BE6; Fri, 5 Jul 2013 14:28:30 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 5zC1WKC9WNPg; Fri, 5 Jul 2013 14:28:30 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id DD03D20BE1; Fri, 5 Jul 2013 14:28:29 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 9ED4F2727FBE; Fri, 5 Jul 2013 14:28:27 +0200 (CEST) Date: Fri, 5 Jul 2013 14:28:27 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130705122827.GA47431@elstar.local> Mail-Followup-To: netmod@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [netmod] WG Last Call draft-ietf-netmod-system-mgmt-08 (until 2013-07-22) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jul 2013 12:28:36 -0000 Hi, I hereby like to start a WG last call for the document "YANG Data Model for System Management": http://tools.ietf.org/html/draft-ietf-netmod-system-mgmt-08 Please indicate your support by Monday July 22nd. We are not only interested in receiving defect reports, we are equally interested in statements of the form: "I have reviewed I-D XYZ and I found no issues" "I have implemented the data model in I-D XYZ" "I am implementing the data model in I-D XYZ" "I am considering to implement the data model in I-D XYZ" This is the 2nd WG last call. The 1st WG last call took place in March 2013 and uncovered a number of issues that resulted in the current version of the I-D. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From j.schoenwaelder@jacobs-university.de Fri Jul 5 05:29:08 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD4311E82BF for ; Fri, 5 Jul 2013 05:29:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhTMqiSdj9IG for ; Fri, 5 Jul 2013 05:29:03 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE6311E82BD for ; Fri, 5 Jul 2013 05:29:03 -0700 (PDT) Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id F0B1A20BE6; Fri, 5 Jul 2013 14:29:02 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id fACc6xN8sqt9; Fri, 5 Jul 2013 14:29:02 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 848FB20BE1; Fri, 5 Jul 2013 14:29:02 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 423792727FE1; Fri, 5 Jul 2013 14:29:01 +0200 (CEST) Date: Fri, 5 Jul 2013 14:29:01 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130705122901.GB47431@elstar.local> Mail-Followup-To: netmod@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [netmod] WG Last Call draft-ietf-netmod-interfaces-cfg-12 (until 2013-07-22) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jul 2013 12:29:08 -0000 Hi, I hereby like to start a WG last call for the document "A YANG Data Model for Interface Management": http://tools.ietf.org/html/draft-ietf-netmod-interfaces-cfg-12 Please indicate your support by Monday July 22nd. We are not only interested in receiving defect reports, we are equally interested in statements of the form: "I have reviewed I-D XYZ and I found no issues" "I have implemented the data model in I-D XYZ" "I am implementing the data model in I-D XYZ" "I am considering to implement the data model in I-D XYZ" This document already had two WG last calls and it subsequently went through IETF last call. Several issues were raised during IETF last call and some of them required to be explicit how we deal with the separation of configuration state and operational state. This version of the I-D is believed to address the issues that were raised. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From j.schoenwaelder@jacobs-university.de Fri Jul 5 05:29:33 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D68621F942B for ; Fri, 5 Jul 2013 05:29:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.816 X-Spam-Level: X-Spam-Status: No, score=-102.816 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0v4MEA0hzVY for ; Fri, 5 Jul 2013 05:29:28 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 90EAA21F9307 for ; Fri, 5 Jul 2013 05:29:28 -0700 (PDT) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0216220BE6; Fri, 5 Jul 2013 14:29:28 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id FAibSUS3XAh6; Fri, 5 Jul 2013 14:29:27 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8B58F20BE1; Fri, 5 Jul 2013 14:29:27 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 48C852727FFE; Fri, 5 Jul 2013 14:29:26 +0200 (CEST) Date: Fri, 5 Jul 2013 14:29:26 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130705122926.GC47431@elstar.local> Mail-Followup-To: netmod@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [netmod] WG Last Call draft-ietf-netmod-interfaces-cfg-12 (until 2013-07-22) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jul 2013 12:29:33 -0000 Hi, I hereby like to start a WG last call for the document "IANA Interface Type YANG Module": http://tools.ietf.org/html/draft-ietf-netmod-iana-if-type-07 Please indicate your support by Monday July 22nd. We are not only interested in receiving defect reports, we are equally interested in statements of the form: "I have reviewed I-D XYZ and I found no issues" "I have implemented the data model in I-D XYZ" "I am implementing the data model in I-D XYZ" "I am considering to implement the data model in I-D XYZ" This document already had two WG last calls and it subsequently went through IETF last call. No technical issues were raised for this I-D but we decided to move the address family registry (which is only used by the routing document so far) into a separate document so that things can progress independently. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From j.schoenwaelder@jacobs-university.de Fri Jul 5 05:30:12 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 106FA11E82BC for ; Fri, 5 Jul 2013 05:30:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.816 X-Spam-Level: X-Spam-Status: No, score=-102.816 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1cKlS-6ke-Ta for ; Fri, 5 Jul 2013 05:30:11 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id C372B21F955A for ; Fri, 5 Jul 2013 05:30:11 -0700 (PDT) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 337B320BE6; Fri, 5 Jul 2013 14:30:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id kHCw6js-G-og; Fri, 5 Jul 2013 14:30:11 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id C5BDF20BE1; Fri, 5 Jul 2013 14:30:10 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 7BB812728037; Fri, 5 Jul 2013 14:30:09 +0200 (CEST) Date: Fri, 5 Jul 2013 14:30:09 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130705123009.GD47431@elstar.local> Mail-Followup-To: netmod@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [netmod] WG Last Call draft-ietf-netmod-iana-if-type-07 (until 2013-07-22) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jul 2013 12:30:12 -0000 Hi, I hereby like to start a WG last call for the document "IANA Interface Type YANG Module": http://tools.ietf.org/html/draft-ietf-netmod-iana-if-type-07 Please indicate your support by Monday July 22nd. We are not only interested in receiving defect reports, we are equally interested in statements of the form: "I have reviewed I-D XYZ and I found no issues" "I have implemented the data model in I-D XYZ" "I am implementing the data model in I-D XYZ" "I am considering to implement the data model in I-D XYZ" This document already had two WG last calls and it subsequently went through IETF last call. No technical issues were raised for this I-D but we decided to move the address family registry (which is only used by the routing document so far) into a separate document so that things can progress independently. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From j.schoenwaelder@jacobs-university.de Fri Jul 5 05:39:03 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D2311E82BD for ; Fri, 5 Jul 2013 05:39:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.924 X-Spam-Level: X-Spam-Status: No, score=-102.924 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ewe8ZLmocQKc for ; Fri, 5 Jul 2013 05:38:59 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 01F8E11E82BF for ; Fri, 5 Jul 2013 05:38:59 -0700 (PDT) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6781320BE6; Fri, 5 Jul 2013 14:38:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id uOW1_b3qlwQw; Fri, 5 Jul 2013 14:38:58 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id F415020A6D; Fri, 5 Jul 2013 14:38:57 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id D5A64272812A; Fri, 5 Jul 2013 14:38:55 +0200 (CEST) Date: Fri, 5 Jul 2013 14:38:55 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130705123855.GA47547@elstar.local> Mail-Followup-To: netmod@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [netmod] WG Last Call draft-ietf-netmod-iana-timezones-00 (until 2013-07-22) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jul 2013 12:39:03 -0000 Hi, I hereby like to start a WG last call for the document "IANA Timezone Database YANG Module": http://tools.ietf.org/html/draft-ietf-netmod-iana-timezones-00 Please indicate your support by Monday July 22nd. We are not only interested in receiving defect reports, we are equally interested in statements of the form: "I have reviewed I-D XYZ and I found no issues" "I have implemented the data model in I-D XYZ" "I am implementing the data model in I-D XYZ" "I am considering to implement the data model in I-D XYZ" This is the 1st WG last call on this document. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From j.schoenwaelder@jacobs-university.de Fri Jul 5 05:53:05 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA8611E82CC for ; Fri, 5 Jul 2013 05:53:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.989 X-Spam-Level: X-Spam-Status: No, score=-102.989 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUG5yYyuNTdu for ; Fri, 5 Jul 2013 05:53:00 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6875A11E82C8 for ; Fri, 5 Jul 2013 05:52:59 -0700 (PDT) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id CBFA920BEE; Fri, 5 Jul 2013 14:52:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id n8JDV1kVHN6C; Fri, 5 Jul 2013 14:52:58 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 59D4A20BE6; Fri, 5 Jul 2013 14:52:58 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id EFFD727282BB; Fri, 5 Jul 2013 14:52:56 +0200 (CEST) Date: Fri, 5 Jul 2013 14:52:56 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130705125256.GA47658@elstar.local> Mail-Followup-To: netmod@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [netmod] draft agenda ietf meeting berlin X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jul 2013 12:53:05 -0000 Hi, I have posted a very first draft agenda for the IETF meeting in Berlin. http://www.ietf.org/proceedings/87/agenda/agenda-87-netmod If you want agenda time, please contact the chairs. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From lhotka@nic.cz Wed Jul 10 01:41:54 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE3021F9D7C for ; Wed, 10 Jul 2013 01:41:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.182 X-Spam-Level: X-Spam-Status: No, score=-1.182 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, HOST_EQ_CZ=0.904, J_CHICKENPOX_23=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9Dbb9AjvxN3 for ; Wed, 10 Jul 2013 01:41:50 -0700 (PDT) Received: from trail.lhotka.name (nat-5.bravonet.cz [77.48.224.5]) by ietfa.amsl.com (Postfix) with ESMTP id A1DC821F9D68 for ; Wed, 10 Jul 2013 01:41:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by trail.lhotka.name (Postfix) with ESMTP id 62008540208 for ; Wed, 10 Jul 2013 10:41:46 +0200 (CEST) Received: from trail.lhotka.name ([127.0.0.1]) by localhost (trail.lhotka.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zdqywUE6xI2K for ; Wed, 10 Jul 2013 10:41:39 +0200 (CEST) Received: from localhost (unknown [172.29.2.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by trail.lhotka.name (Postfix) with ESMTPSA id BA1085401FC for ; Wed, 10 Jul 2013 10:41:34 +0200 (CEST) From: Ladislav Lhotka To: netmod@ietf.org In-Reply-To: <20130705125256.GA47658@elstar.local> References: <20130705125256.GA47658@elstar.local> User-Agent: Notmuch/0.15.2 (http://notmuchmail.org) Emacs/23.4.1 (x86_64-apple-darwin12.3.0) Mail-Followup-To: netmod@ietf.org Date: Wed, 10 Jul 2013 10:41:32 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [netmod] draft agenda ietf meeting berlin X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 08:41:54 -0000 Hi, I think Martin can cover draft-ietf-netmod-iana-afn-safi-00 together with iana-if-type-07. The only thing to talk about it to explain the reason for splitting the documents. Lada Juergen Schoenwaelder writes: > Hi, > > I have posted a very first draft agenda for the IETF meeting in > Berlin. > > http://www.ietf.org/proceedings/87/agenda/agenda-87-netmod > > If you want agenda time, please contact the chairs. > > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C From andy@yumaworks.com Fri Jul 12 13:47:37 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33A3D21F9F23 for ; Fri, 12 Jul 2013 13:47:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.224 X-Spam-Level: X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORzeTCNUB3EZ for ; Fri, 12 Jul 2013 13:47:32 -0700 (PDT) Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4D54621F9F21 for ; Fri, 12 Jul 2013 13:47:32 -0700 (PDT) Received: by mail-pd0-f172.google.com with SMTP id z10so8914657pdj.31 for ; Fri, 12 Jul 2013 13:47:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=+kl3GgQmrPKFfxcslE7zcnDUmsXy78q9yLkwL+fYz/o=; b=C4ZdIXZFxP6TMZWiAluKvl/6AP5EJWZUTOrqLu9OktCvorDKv+MjAfooHKi339xo0b t0A8Qw6/WTylVFZByT0iPhgAuZHC2qFoKJkMUKG8JxBgvm4sEPYvRJlXnRmuLazxDDfz 2t2YtoQPBViMAaZLbamYIoTxmfR21TzMRbvFao5d5qYFJIh1JFKNquiDvKw6UQ3XLdsd 6Pe1Yx3rTd3Qpq16eXMpDcJLRPePHT86iscW1NqUQohKa7e0uzGy3HigtYznwKKcnjR9 0k2SOIM+NzC7b0pzMEo82QKhaMFGeayCAb/wGPjjNAPJHeMuVxpN4brDjxjJ6vlorI0a dpkw== MIME-Version: 1.0 X-Received: by 10.66.252.194 with SMTP id zu2mr45334993pac.71.1373662044262; Fri, 12 Jul 2013 13:47:24 -0700 (PDT) Received: by 10.70.12.161 with HTTP; Fri, 12 Jul 2013 13:47:23 -0700 (PDT) Date: Fri, 12 Jul 2013 13:47:23 -0700 Message-ID: From: Andy Bierman To: netmod@ietf.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlnszHIWuwKJg3fU8kZz0rC9qmazozM0H4XZyP6lsmSsfgCl0ipSeHoYD3seGrwhiLcHqrj Subject: [netmod] YANG Cheat Sheet X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jul 2013 20:47:37 -0000 Hi, I created a 1 page PDF file with most of YANG syntax represented. (Still learning gimp so v1.0 graphics are not too good). http://www.netconfcentral.org/papers/yang-cheat-sheet-v1.pdf I wanted something easier to read than the ABNF in RFC 6020, so I tried to create a template for most YANG statements. Let me know if you find errors, or have ideas to get more info onto 1 page (I had to leave out type-stmt). Andy From internet-drafts@ietf.org Sat Jul 13 01:07:14 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6957911E819A; Sat, 13 Jul 2013 01:07:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.54 X-Spam-Level: X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJWh5Bhld+Mk; Sat, 13 Jul 2013 01:07:14 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0453111E8196; Sat, 13 Jul 2013 01:07:14 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130713080713.23472.19742.idtracker@ietfa.amsl.com> Date: Sat, 13 Jul 2013 01:07:13 -0700 Cc: netmod@ietf.org Subject: [netmod] I-D Action: draft-ietf-netmod-routing-cfg-10.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jul 2013 08:07:14 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the NETCONF Data Modeling Language Working Gr= oup of the IETF. Title : A YANG Data Model for Routing Management Author(s) : Ladislav Lhotka Filename : draft-ietf-netmod-routing-cfg-10.txt Pages : 82 Date : 2013-07-13 Abstract: This document contains a specification of three YANG modules. Together they form the core routing data model which serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for individual routing protocols and other related functions. The core routing data model provides common building blocks for such extensions - router instances, routes, routing tables, routing protocols and route filters. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-netmod-routing-cfg-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netmod-routing-cfg-10 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From lhotka@nic.cz Sat Jul 13 01:13:35 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC66D21E80D6 for ; Sat, 13 Jul 2013 01:13:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_23=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CDVJPRpg6614 for ; Sat, 13 Jul 2013 01:13:33 -0700 (PDT) Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) by ietfa.amsl.com (Postfix) with ESMTP id C0E0D11E818A for ; Sat, 13 Jul 2013 01:13:24 -0700 (PDT) Received: from [172.29.2.202] (nat-5.bravonet.cz [77.48.224.5]) by mail.nic.cz (Postfix) with ESMTPSA id 849C413F991 for ; Sat, 13 Jul 2013 10:13:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1373703203; bh=WWg4ZA/VUzbNr+/igOQLJrFo8wz07a54BUXQQDhHW0U=; h=From:Content-Type:Content-Transfer-Encoding:Subject:Date: References:To:Message-Id:Mime-Version; b=g0E5I0sq3l083uxgaYRmPtL0YmIGANA2CGgT+iWySRp5nEkrTypCUQ/4M6r2ERDHn gYyUH+ootug+qZJH2DWLPQ7l0fk/WYWqUoLNnJacKi8J+d1qNi5SiCYFAfzMU6pkzL 0ja/rgQULytjTPaAy52QeNeive3paekD0jEC1qto= From: Ladislav Lhotka Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 13 Jul 2013 10:13:23 +0200 References: <20130713080714.23472.51827.idtracker@ietfa.amsl.com> To: netmod@ietf.org Message-Id: <3275514D-43CB-4B3A-9FCA-77AF8D24E3BC@nic.cz> Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-Virus-Scanned: clamav-milter 0.97.8 at mail X-Virus-Status: Clean Subject: [netmod] Fwd: New Version Notification for draft-ietf-netmod-routing-cfg-10.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jul 2013 08:13:35 -0000 Hi, main changes in this revision are: 1. A separate subtree for operational state data. 2. Terms "system-controlled" and "user-controlled" are introduced for = classifying entries of "config false" lists. 3. New feature "user-defined-routing-tables" considerably simplifies the = data model for implementations that do not support user-defined routing = tables. Lada Begin forwarded message: > From: internet-drafts@ietf.org > Subject: New Version Notification for = draft-ietf-netmod-routing-cfg-10.txt > Date: July 13, 2013 10:07:14 AM GMT+02:00 > To: Ladislav Lhotka >=20 >=20 > A new version of I-D, draft-ietf-netmod-routing-cfg-10.txt > has been successfully submitted by Ladislav Lhotka and posted to the > IETF repository. >=20 > Filename: draft-ietf-netmod-routing-cfg > Revision: 10 > Title: A YANG Data Model for Routing Management > Creation date: 2013-07-13 > Group: netmod > Number of pages: 82 > URL: = http://www.ietf.org/internet-drafts/draft-ietf-netmod-routing-cfg-10.txt > Status: = http://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg > Htmlized: = http://tools.ietf.org/html/draft-ietf-netmod-routing-cfg-10 > Diff: = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netmod-routing-cfg-10 >=20 > Abstract: > This document contains a specification of three YANG modules. > Together they form the core routing data model which serves as a > framework for configuring and managing a routing subsystem. It is > expected that these modules will be augmented by additional YANG > modules defining data models for individual routing protocols and > other related functions. The core routing data model provides = common > building blocks for such extensions - router instances, routes, > routing tables, routing protocols and route filters. >=20 >=20 >=20 >=20 > The IETF Secretariat >=20 -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C From j.schoenwaelder@jacobs-university.de Wed Jul 17 23:50:56 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C44EB21E8094 for ; Wed, 17 Jul 2013 23:50:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.142 X-Spam-Level: X-Spam-Status: No, score=-103.142 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVBZEwV104rM for ; Wed, 17 Jul 2013 23:50:52 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 360A621E8095 for ; Wed, 17 Jul 2013 23:50:52 -0700 (PDT) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3860320BF8; Thu, 18 Jul 2013 08:50:51 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id KrPO8x6_pJNQ; Thu, 18 Jul 2013 08:50:51 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id BD2A720BF4; Thu, 18 Jul 2013 08:50:50 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 46A3F2741007; Thu, 18 Jul 2013 08:50:46 +0200 (CEST) Date: Thu, 18 Jul 2013 08:50:46 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130718065046.GA89409@elstar.local> Mail-Followup-To: netmod@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [netmod] wg last call reminder X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 06:50:57 -0000 Hi, This is a gentle reminder that the following I-Ds are in WG last call: http://tools.ietf.org/html/draft-ietf-netmod-system-mgmt-08 http://tools.ietf.org/html/draft-ietf-netmod-interfaces-cfg-12 http://tools.ietf.org/html/draft-ietf-netmod-iana-if-type-07 http://tools.ietf.org/html/draft-ietf-netmod-iana-timezones-00 Please indicate your support by Monday July 22nd. We are not only interested in receiving defect reports, we are equally interested in statements of the form: "I have reviewed I-D XYZ and I found no issues" "I have implemented the data model in I-D XYZ" "I am implementing the data model in I-D XYZ" "I am considering to implement the data model in I-D XYZ" /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From fengchongllly@gmail.com Thu Jul 18 02:19:00 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEA0A21E80A8 for ; Thu, 18 Jul 2013 02:19:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETN92FGtf62O for ; Thu, 18 Jul 2013 02:19:00 -0700 (PDT) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E98C921E80AF for ; Thu, 18 Jul 2013 02:18:58 -0700 (PDT) Received: by mail-qc0-f173.google.com with SMTP id l10so1592064qcy.18 for ; Thu, 18 Jul 2013 02:18:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=n4DRjTUDQXdburWi84iYIEWhevX4QJCINXTdGkg/vUQ=; b=fMEixXzX0w6wDCC1RpToCbJzloIRloWoP1Gotoa5VYytoTvDNTBI/r66F3oQIJc3w9 XPB/j4cdFSaYUyB6U5EsflD1qnch6SldM64s8TBIw8OF5zzqq0tIqGiePrc8hq8XJ/Ou h85ltvyMQrX44mpholtqyR+IiBf0FHWEY1SHjzhFuZhbT4VyXuij1eSQO5B9a9T8ocUt BX88MwEBZ0O9NtviZgNHTw0YD4qmDBRysTl5EwJxIRH3L3BcUzSU/vCyjtBkT/m9dXo3 XXp4r0XWEg1ASENQdHO3GfMsUHvnRH9E0DBIpDD32A1V15Ca6ZpLH+eGdHc0KpZVkFCu g7iA== MIME-Version: 1.0 X-Received: by 10.49.59.228 with SMTP id c4mr11703141qer.15.1374139138380; Thu, 18 Jul 2013 02:18:58 -0700 (PDT) Received: by 10.229.102.96 with HTTP; Thu, 18 Jul 2013 02:18:58 -0700 (PDT) Date: Thu, 18 Jul 2013 17:18:58 +0800 Message-ID: From: chong feng To: netmod@ietf.org Content-Type: multipart/alternative; boundary=047d7b6d8a0e37255804e1c5b33b Subject: [netmod] how to use 'mandatory' node X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 09:19:01 -0000 --047d7b6d8a0e37255804e1c5b33b Content-Type: text/plain; charset=ISO-8859-1 hello everyone: I'm developing our own NETCONF agent. when i received a netconf request to delete a instance of list, a mandatory node was defined in this list. Should this mandatory node be included to this request? I think this node should not be included in netconf request,but there is no explicit description in RFC 6020. --047d7b6d8a0e37255804e1c5b33b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hello everyone:
I'm developing our own NETCONF age= nt. when i received a netconf request to delete a instance of list, a manda= tory node was defined in this list. Should=A0this mandatory node be include= d to this request?
I think this node should not be included in netconf request,but there = is no explicit description in RFC 6020.
--047d7b6d8a0e37255804e1c5b33b-- From j.schoenwaelder@jacobs-university.de Mon Jul 22 13:22:36 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B73111E814F for ; Mon, 22 Jul 2013 13:22:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.249 X-Spam-Level: X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V3-i3dhmmjSn for ; Mon, 22 Jul 2013 13:22:31 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 3832711E813F for ; Mon, 22 Jul 2013 13:22:30 -0700 (PDT) Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5868A20AFA; Mon, 22 Jul 2013 22:22:25 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id nutggghhuZ7i; Mon, 22 Jul 2013 22:22:25 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id C7B9220B6C; Mon, 22 Jul 2013 22:22:24 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id BBBA8274C780; Mon, 22 Jul 2013 22:22:20 +0200 (CEST) Date: Mon, 22 Jul 2013 22:22:20 +0200 From: Juergen Schoenwaelder To: netmod@ietf.org Message-ID: <20130722202220.GA1746@elstar.local> Mail-Followup-To: netmod@ietf.org References: <20130718065046.GA89409@elstar.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130718065046.GA89409@elstar.local> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [netmod] wg last call reminder X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 20:22:36 -0000 Hi, another gentle reminder - note that reviews during WG last calls are crucial and important to move I-Ds towards RFCs. /js On Thu, Jul 18, 2013 at 08:50:46AM +0200, Juergen Schoenwaelder wrote: > Hi, > > This is a gentle reminder that the following I-Ds are in WG last > call: > > http://tools.ietf.org/html/draft-ietf-netmod-system-mgmt-08 > http://tools.ietf.org/html/draft-ietf-netmod-interfaces-cfg-12 > http://tools.ietf.org/html/draft-ietf-netmod-iana-if-type-07 > http://tools.ietf.org/html/draft-ietf-netmod-iana-timezones-00 > > Please indicate your support by Monday July 22nd. We are not only > interested in receiving defect reports, we are equally interested > in statements of the form: > > "I have reviewed I-D XYZ and I found no issues" > "I have implemented the data model in I-D XYZ" > "I am implementing the data model in I-D XYZ" > "I am considering to implement the data model in I-D XYZ" /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From balazs.lengyel@ericsson.com Tue Jul 23 02:26:16 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 230C611E80DC for ; Tue, 23 Jul 2013 02:26:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.695 X-Spam-Level: X-Spam-Status: No, score=-3.695 tagged_above=-999 required=5 tests=[AWL=1.096, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3CIrf-UC-Z-H for ; Tue, 23 Jul 2013 02:26:09 -0700 (PDT) Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC9121F9E88 for ; Tue, 23 Jul 2013 02:26:08 -0700 (PDT) X-AuditID: c1b4fb25-b7f826d000001766-d1-51ee4c2f200b Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 03.6D.05990.F2C4EE15; Tue, 23 Jul 2013 11:26:07 +0200 (CEST) Received: from [159.107.196.192] (153.88.183.19) by smtp.internal.ericsson.com (153.88.183.68) with Microsoft SMTP Server id 14.2.328.9; Tue, 23 Jul 2013 11:26:06 +0200 Message-ID: <51EE4C2E.3010509@ericsson.com> Date: Tue, 23 Jul 2013 11:26:06 +0200 From: Balazs Lengyel User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: "netmod@ietf.org" References: <9904FB1B0159DA42B0B887B7FA8119CA1287A840@AZ-FFEXMB04.global.avaya.com> In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA1287A840@AZ-FFEXMB04.global.avaya.com> X-Forwarded-Message-Id: <9904FB1B0159DA42B0B887B7FA8119CA1287A840@AZ-FFEXMB04.global.avaya.com> Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFJMWRmVeSWpSXmKPExsUyM+Jvra6+z7tAg84PChbzLzayOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4+TJJ4wF790qrr6Yw9jA2G3RxcjJISFgInH26GI2CFtM4sK9 9WC2kMBhRoljc/S6GLmA7DWMEj+OvWQGSfAKaEu8aXzOCmKzCKhKvHrwC6yBTcBIYmr/eRYQ W1QgSqK1dypUvaDEyZlPwOIiAuoSM3dCLBAWcJfYsvscO8SyYImO6VvBZnIKhEg8vr6HBeKg eImFPTeZQGxmAV2JC/+nsEDY8hLb385hhujVkHh44S/rBEbBWUjWzULSMgtJywJG5lWM7LmJ mTnp5UabGIHhd3DLb9UdjHfOiRxilOZgURLn3ax3JlBIID2xJDU7NbUgtSi+qDQntfgQIxMH p1QDY+iNHImo/DUPJl2NFa/obpTxiXJoeHUsUINdLHbTVn2HexMsP3Rm/UoIqr7+13vbdN5v FsumTCp/de6OcuEyhn++18+Gz19/bGblTY41rznlZy02vipV1tvIc/fDx7wDpSH7hBQ/JV0r 2r00u2LWnp2Lze8ty1x/aEnqz02hqb8WyV2cXVWoeU6JpTgj0VCLuag4EQCOX3S6DQIAAA== Subject: [netmod] Fwd: Re: [YANG] Usage of rpc under container or list statement X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2013 09:26:16 -0000 Hello Kedar,
This was planned, but never maid it to the RFC. However both Tail-F and Ericsson is using such a thing. We are considering writing an RFC about it at some point.
regards balazs

From: yang-bounces@ietf.org [mailto:yang-bounces@ietf.org] On Behalf Of Kedar Gaonkar
Sent: Wednesday, July 17, 2013 11:49 PM
To: yang@ietf.org
Subject: [YANG] Usage of rpc under container or list statement

 

Greetings,

 

Can I have an rpc statement under a container or a list? RFC 6020 doesn’t mention ‘rpc’ under section 7.5.2 (container substatements) or 7.8.1 (list substatements).

 

In my data model, I have a list defined for access points. The key for this list is the mac-address of access point. Along with all the leaves, I wanted to define an rpc under this list that enables or disables the LED of access-point. Since this rpc has meaning only for access-points, I was wondering if I could logically group it under the list, or is it mandatory that all rpcs have to be defined globally outside of containers?

 

container access_point {

                config false; 

                list ap {

                                key “mac_address”;

                                leaf mac_address  { type yang:mac-address; }

 

                                <some-other-leaves..>

 

                                rpc set_led {

                                                config false;

                                                input {

                                                                leaf on { type boolean; }

                                                }

                                }

                }

}

 

Thanks,

Kedar


-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
System Manager
ECN: 831 7320                        Tel: +36-1-437-7320
Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com


From andy@yumaworks.com Tue Jul 23 08:48:55 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCABA21E8085 for ; Tue, 23 Jul 2013 08:48:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.202 X-Spam-Level: X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ErIt1ls14512 for ; Tue, 23 Jul 2013 08:48:51 -0700 (PDT) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0946821E80AF for ; Tue, 23 Jul 2013 08:48:49 -0700 (PDT) Received: by mail-pa0-f51.google.com with SMTP id lf11so97392pab.24 for ; Tue, 23 Jul 2013 08:48:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=SqTWNR4svaqUzY4QkceSu8v7xB7ibk+jbT/vI3wXeVE=; b=OcMELiDDvvlvvxDlLE72hkYr9hdwnV4MloL+s0Uu35Kl0cLCb1FESOH69byL6gpqrS c7PcSdhV7Op2Qeeri+MMuN91AVYDw9p6XG30Re2kcz2Pc3etEjc9MLPebAWHZHDisiqv u8yllXSVQAsqOgzUy5l4qR1vt/c55XuINpwYTVfqIHKu7EQ+jyIn8WPXaBuu4kVLjuWb dR9YJhIQN/SUWTnJ38Yil7WDeNXeEb/CdX6SdrXe7zFRi1IiJzhkGd1MiP68p7psee5S Kys0XjmIDnlgIFmhhxsB/7QUZG7tFk8lhnwYLGgeQgNuw1lfl685/ACvCgJiX6yQX2Cs ExIg== X-Received: by 10.68.196.231 with SMTP id ip7mr37395266pbc.18.1374594528732; Tue, 23 Jul 2013 08:48:48 -0700 (PDT) Received: from [10.101.224.168] (mobile-198-228-209-085.mycingular.net. [198.228.209.85]) by mx.google.com with ESMTPSA id eq5sm42525378pbc.15.2013.07.23.08.48.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 23 Jul 2013 08:48:48 -0700 (PDT) References: <9904FB1B0159DA42B0B887B7FA8119CA1287A840@AZ-FFEXMB04.global.avaya.com> <51EE4C2E.3010509@ericsson.com> Mime-Version: 1.0 (1.0) In-Reply-To: <51EE4C2E.3010509@ericsson.com> Content-Type: multipart/alternative; boundary=Apple-Mail-BE0CC2FF-3B68-42FC-8B15-C5831687EA29 Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: iPhone Mail (10B329) From: Andy Bierman Date: Tue, 23 Jul 2013 08:48:37 -0700 To: Balazs Lengyel X-Gm-Message-State: ALoCoQme5CROHHX0qU2M7ZJ5MxiEetODodPVhxb3isxh+j9NSFIX54mko5QVeIipCInyblkReUcV Cc: "netmod@ietf.org" Subject: Re: [netmod] Fwd: Re: [YANG] Usage of rpc under container or list statement X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2013 15:48:56 -0000 --Apple-Mail-BE0CC2FF-3B68-42FC-8B15-C5831687EA29 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I think it didn't make it in because YANG is not OO. Placing an rpc inside a= data node does not change that. Andy Sent from my iPhone On Jul 23, 2013, at 2:26, Balazs Lengyel wrote= : > Hello Kedar, > This was planned, but never maid it to the RFC. However both Tail-F and Er= icsson is using such a thing. We are considering writing an RFC about it at s= ome point. > regards balazs >=20 >=20 > From: yang-bounces@ietf.org [mailto:yang-bounces@ietf.org] On Behalf Of Ke= dar Gaonkar > Sent: Wednesday, July 17, 2013 11:49 PM > To: yang@ietf.org > Subject: [YANG] Usage of rpc under container or list statement >=20 > =20 >=20 > Greetings, >=20 > =20 >=20 > Can I have an rpc statement under a container or a list? RFC 6020 doesn=E2= =80=99t mention =E2=80=98rpc=E2=80=99 under section 7.5.2 (container substat= ements) or 7.8.1 (list substatements). >=20 > =20 >=20 > In my data model, I have a list defined for access points. The key for thi= s list is the mac-address of access point. Along with all the leaves, I want= ed to define an rpc under this list that enables or disables the LED of acce= ss-point. Since this rpc has meaning only for access-points, I was wondering= if I could logically group it under the list, or is it mandatory that all r= pcs have to be defined globally outside of containers? >=20 > =20 >=20 > container access_point { >=20 > config false;=20 >=20 > list ap { >=20 > key =E2=80=9Cmac_address=E2=80=9D; >=20 > leaf mac_address { type yang:mac-address;= } >=20 > =20 >=20 > >=20 > =20 >=20 > rpc set_led { >=20 > config false; >=20 > input { >=20 > = leaf on { type boolean; } >=20 > } >=20 > } >=20 > } >=20 > } >=20 > =20 >=20 > Thanks, >=20 > Kedar >=20 >=20 > --=20 > Balazs Lengyel Ericsson Hungary Ltd. > System Manager > ECN: 831 7320 Tel: +36-1-437-7320 > Mobile: +36-70-330-7909 email: Balazs.Lengyel@ericsson.com=20= >=20 >=20 > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod --Apple-Mail-BE0CC2FF-3B68-42FC-8B15-C5831687EA29 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I think it didn't make it in because Y= ANG is not OO. Placing an rpc inside a data node does not change that.
=

Andy

Sent from my iPhone

On Jul 23,= 2013, at 2:26, Balazs Lengyel <balazs.lengyel@ericsson.com> wrote:

=20 =20 =20 Hello Kedar,
This was planned, but never maid it to the RFC. However both Tail-F and Ericsson is using such a thing. We are considering writing an RFC about it at some point.
regards balazs

From: yang-bounces@ietf.org [mailto:yang-bounces@ietf.org] On Behalf Of Kedar Gaonkar
Sent: Wednesday, July 17, 2013 11:49 PM
To: yang@ietf.org
Subject: [YANG] Usage of rpc under container or list statement

 

Greetings,

 

Can I have an rpc statement under a container or a list? RFC 6020 doesn=E2=80=99t mention =E2=80=98rpc=E2=80=99 under secti= on 7.5.2 (container substatements) or 7.8.1 (list substatements).

 

In my data model, I have a list defined for access points. The key for this list is the mac-address of access point. Along with all the leaves, I wanted to define an rpc under this list that enables or disables the LED of access-point. Since this rpc has meaning only for access-points, I was wondering if I could logically group it under the list, or is it mandatory that all rpcs have to be defined globally outside of containers?

 

container access_point {

         &n= bsp;      config false; 

         &n= bsp;      list ap {

         &n= bsp;            =           key =E2=80=9Cmac_address=E2=80=9D;

         &n= bsp;                &n= bsp;     leaf mac_address  { type yang:mac-address;= }

 

         &n= bsp;                &n= bsp;     <some-other-leaves..>

 

         &n= bsp;                &n= bsp;     rpc set_led {

         &n= bsp;            =             &nbs= p;             config false;

         &n= bsp;            =             &nbs= p;             input {

         &n= bsp;            =             &nbs= p;            &n= bsp;            =     leaf on { type boolean; }

         &n= bsp;            =             &nbs= p;             }

         &n= bsp;            =           }

         &n= bsp;      }

}

 

Thanks,

Kedar 


--=20
Balazs Lengyel                       Ericsson Hungary Ltd.
System Manager
ECN: 831 7320                        Tel: +36-1-437-7320
Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.co=
m=20


=20
____________________= ___________________________
netmod mailing list
netmod@ietf.org
<= a href=3D"https://www.ietf.org/mailman/listinfo/netmod">https://www.ietf.org= /mailman/listinfo/netmod
= --Apple-Mail-BE0CC2FF-3B68-42FC-8B15-C5831687EA29-- From mbj@tail-f.com Tue Jul 23 14:45:48 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74C4011E8392 for ; Tue, 23 Jul 2013 14:45:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.746 X-Spam-Level: X-Spam-Status: No, score=-1.746 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_73=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpz537lik6ad for ; Tue, 23 Jul 2013 14:45:39 -0700 (PDT) Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id 1952111E8383 for ; Tue, 23 Jul 2013 14:45:28 -0700 (PDT) Received: from localhost (213-65-182-102-no181.tbcn.telia.com [213.65.182.102]) by mail.tail-f.com (Postfix) with ESMTPSA id 3035D1200A39; Tue, 23 Jul 2013 23:45:21 +0200 (CEST) Date: Tue, 23 Jul 2013 23:45:20 +0200 (CEST) Message-Id: <20130723.234520.378400633.mbj@tail-f.com> To: fengchongllly@gmail.com From: Martin Bjorklund In-Reply-To: References: X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netmod@ietf.org Subject: Re: [netmod] how to use 'mandatory' node X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2013 21:45:48 -0000 Hi, chong feng wrote: > hello everyone: > I'm developing our own NETCONF agent. when i received a netconf > request to > delete a instance of list, a mandatory node was defined in this list. > Should this mandatory node be included to this request? > I think this node should not be included in netconf request,but there > is no > explicit description in RFC 6020. In general, if you do: the entire subtree under "foo" is deleted. There is no need to explicitly delete nodes underneath "foo". /martin From fengchongllly@gmail.com Wed Jul 24 07:37:59 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAB8D11E80F7 for ; Wed, 24 Jul 2013 07:37:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, J_CHICKENPOX_73=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yctgkcd5xoI8 for ; Wed, 24 Jul 2013 07:37:59 -0700 (PDT) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB7321F9DED for ; Wed, 24 Jul 2013 07:37:47 -0700 (PDT) Received: by mail-qc0-f178.google.com with SMTP id b11so323016qcw.37 for ; Wed, 24 Jul 2013 07:37:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cWN1qC4kxHc+axeYkhHnInrmB9XF3VqcFqgfvqANL1s=; b=LwbnqwwQ+SpijpOC4C4lgf79/fD8I6UoEzgY1LqoZmMsQUYAR0AosYf2a5FYaNJz8G ky9+2htNh3Lh1UHV2sqgg1BaG0GJskgXaZ/3iR1Y7VgqkE7ugtDdXijV4cu3E1I2isJH yXQnY46ElxiV61JJSVNUFDZd5zEUg9YMMsOpSkSa8xGTvQBFAEqEMASAgObXU9aTIJEQ gJ9IqCQ6HIDeqWpLXifjyDKragtbXCzaiNGa6yiEWr0R1W76LVii96HPxh5Yh0oVJS4c RoJus45Iij5IKdpWPRoczUE6mhItk1ztNFL8zIl7+7BazZRxeUezCQ/+qU7ubQas+bGa batw== MIME-Version: 1.0 X-Received: by 10.49.12.202 with SMTP id a10mr43500915qec.91.1374676623917; Wed, 24 Jul 2013 07:37:03 -0700 (PDT) Received: by 10.229.177.74 with HTTP; Wed, 24 Jul 2013 07:37:03 -0700 (PDT) In-Reply-To: <20130723.234520.378400633.mbj@tail-f.com> References: <20130723.234520.378400633.mbj@tail-f.com> Date: Wed, 24 Jul 2013 22:37:03 +0800 Message-ID: From: chong feng To: Martin Bjorklund Content-Type: multipart/alternative; boundary=047d7b67794cd986c104e242d79d Cc: netmod@ietf.org Subject: Re: [netmod] how to use 'mandatory' node X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2013 14:37:59 -0000 --047d7b67794cd986c104e242d79d Content-Type: text/plain; charset=ISO-8859-1 Hi, If I want to modify one leaf's value, should mandatory nodes be included in request? for example, lista---- |---key1 |---key2 |---mandatory-node |---leaf1 If I want to modify leaf1's value,the netconf request should be 1 2 3 4 or 1 2 4 ? 2013/7/24 Martin Bjorklund > Hi, > > chong feng wrote: > > hello everyone: > > I'm developing our own NETCONF agent. when i received a netconf > > request to > > delete a instance of list, a mandatory node was defined in this list. > > Should this mandatory node be included to this request? > > I think this node should not be included in netconf request,but there > > is no > > explicit description in RFC 6020. > > In general, if you do: > > > > the entire subtree under "foo" is deleted. There is no need to > explicitly delete nodes underneath "foo". > > > /martin > --047d7b67794cd986c104e242d79d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
If I want to modify one leaf's value, should m= andatory nodes be included in request?
for example,
lis= ta----
=A0 =A0 |---key1
=A0 =A0 |---key2
=A0 = =A0 |---mandatory-node
=A0 =A0 |---leaf1
If I want to modify leaf1's value,the = netconf request should be
=A0 =A0<lista operation=3D "mer= ge">
=A0 =A0 =A0 =A0<key1>1</key1>
= =A0 =A0 =A0 =A0<key2>2</key2>
=A0 =A0 =A0 =A0<mandatory-node>3</mandatory-node>
=A0 =A0 =A0 =A0<leaf1>4</leaf1>
=A0 </lista><= /div>
=A0
or=A0
=A0=A0<lista operation=3D &= quot;merge">
=A0 =A0 =A0 =A0<key1>1</key1>
=A0 =A0 =A0 =A0<= ;key2>2</key2>
=A0 =A0 =A0 =A0<leaf1>4</leaf1&g= t;
=A0 </lista>
?

=


2013/7/24 Martin Bjorklund <mbj@tail-f.com= >
Hi,

chong feng <fengchongllly@gma= il.com> wrote:
> hello everyone:
> I'm developing our own NETCONF agent. when i received a netconf > request to
> delete a instance of list, a mandatory node was defined in this list.<= br> > Should this mandatory node be included to this request?
> I think this node should not be included in netconf request,but there<= br> > is no
> explicit description in RFC 6020.

In general, if you do:

=A0 <foo nc:operation=3D"delete"/>

the entire subtree under "foo" is deleted. =A0There is no need to=
explicitly delete nodes underneath "foo".


/martin

--047d7b67794cd986c104e242d79d-- From andy@yumaworks.com Wed Jul 24 08:12:44 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8614211E80D3 for ; Wed, 24 Jul 2013 08:12:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.777 X-Spam-Level: X-Spam-Status: No, score=-1.777 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_53=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_65=0.6, J_CHICKENPOX_73=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CWaC1sjrB+mI for ; Wed, 24 Jul 2013 08:12:40 -0700 (PDT) Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2FF11E80CC for ; Wed, 24 Jul 2013 08:11:32 -0700 (PDT) Received: by mail-pb0-f46.google.com with SMTP id rq8so1342034pbb.5 for ; Wed, 24 Jul 2013 08:11:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=4Ns0KW/HCg96adRjbb3hFGTI2+lGa8e84WmxTYnwgEo=; b=pgn7lOrumHitqW2bwiceHYsBV2345Gl/7dAFgK7rmAPnGs2oi1qZeVPpWxUfvxC3+F 9YhbRihLJWThPdJaCOXdsRqPl3KEeluhyfedqB0kdmGkW7v0yAX2Jwc4yBblu6TdIf6T LnUurHk3cyIWY4oigCCDXwBOFpUaIEw5P+pCDz1MG2+qwaH9BzpQqgjLoCMz4zPazgyQ Tk1W/kuw9JxaCdpZpdi0Wzo/FhX3Zbm0hINF+wz2p47S1PO7yVHRB7Y+1luyw5HICA9n 2sDmT/7u4AGIn76OJnGIOsg+KnBpcnhi/R5rnBFUuwTK9idRhhLEfZyLjU9sUQeT/uPF XlyQ== MIME-Version: 1.0 X-Received: by 10.68.201.98 with SMTP id jz2mr42784803pbc.56.1374678689446; Wed, 24 Jul 2013 08:11:29 -0700 (PDT) Received: by 10.70.12.161 with HTTP; Wed, 24 Jul 2013 08:11:29 -0700 (PDT) In-Reply-To: References: <20130723.234520.378400633.mbj@tail-f.com> Date: Wed, 24 Jul 2013 08:11:29 -0700 Message-ID: From: Andy Bierman To: chong feng Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkk6rvcAiUixCzf7e+ZtDA3RoesosvWD56w82V849BYwMVzDuB494xFQi8hG6+DJDlWcrlv Cc: netmod@ietf.org Subject: Re: [netmod] how to use 'mandatory' node X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2013 15:12:44 -0000 On Wed, Jul 24, 2013 at 7:37 AM, chong feng wrote: > Hi, > If I want to modify one leaf's value, should mandatory nodes be included in > request? > for example, > lista---- > |---key1 > |---key2 > |---mandatory-node > |---leaf1 > If I want to modify leaf1's value,the netconf request should be > > 1 > 2 > 3 > 4 > > > or > > 1 > 2 > 4 > > ? > The 2nd one. For config=true data nodes, mandatory means the running config must contain the data node to be valid. Sec. 3.1 appears to indicate that config=false nodes can be mandatory, but sec. 7.6.5 applies only to config=true data nodes. This definition applies to config=true data nodes and rpc input nodes. A mandatory config=false data node, rpc output node or notification node means that it must appear in the protocol message. This implies that non-mandatory nodes in these messages are optional to implement, but this is not correct. YANG conformance is only affected by the "if-feature" stmt. Andy > > > > 2013/7/24 Martin Bjorklund >> >> Hi, >> >> chong feng wrote: >> > hello everyone: >> > I'm developing our own NETCONF agent. when i received a netconf >> > request to >> > delete a instance of list, a mandatory node was defined in this list. >> > Should this mandatory node be included to this request? >> > I think this node should not be included in netconf request,but there >> > is no >> > explicit description in RFC 6020. >> >> In general, if you do: >> >> >> >> the entire subtree under "foo" is deleted. There is no need to >> explicitly delete nodes underneath "foo". >> >> >> /martin > > > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod > From fengchongllly@gmail.com Wed Jul 24 23:16:36 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77EDF21F9976 for ; Wed, 24 Jul 2013 23:16:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_65=0.6, J_CHICKENPOX_73=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sDqBj-wuhEQq for ; Wed, 24 Jul 2013 23:16:35 -0700 (PDT) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFCD21F85E6 for ; Wed, 24 Jul 2013 23:16:33 -0700 (PDT) Received: by mail-qc0-f170.google.com with SMTP id s1so763461qcw.1 for ; Wed, 24 Jul 2013 23:16:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pVN3e53mv1lg/wxvRh8phLblgbJHdKa3tpnwyKNXPmM=; b=DobveGq+Ca2bVNR5Qujjc+0LlHr+9gghEEZO5Zoo+UWytaLuNMCC2s2izlf7+IgAO/ oQKLD5gLSMgl4xPAs+3LsY0asS/UhUmiC5Yyy5nv8LB0XmI5G6ju3NKGGORxaeg5FD5a SjeyrEonVwvxP6sVdMCRxMHWXjElFlR6wp2UxXwRPED7ygSYp7faYOED9V3VGkIf7FBa 6nuKlOxokjo2R49PiVYATNLwkNuBJ3XrsahPVpmNhDM48Bkoy0dUrD8hf6MDC3fBWfP9 henpwAmyEva1vvt1P1MyqGCwxELdhIAOXx7u2H6IycMICXgNtr/8EzqJXrXZIcn6VdEi lnfA== MIME-Version: 1.0 X-Received: by 10.224.97.66 with SMTP id k2mr26318675qan.109.1374732991937; Wed, 24 Jul 2013 23:16:31 -0700 (PDT) Received: by 10.229.177.74 with HTTP; Wed, 24 Jul 2013 23:16:31 -0700 (PDT) In-Reply-To: References: <20130723.234520.378400633.mbj@tail-f.com> Date: Thu, 25 Jul 2013 14:16:31 +0800 Message-ID: From: chong feng To: Andy Bierman Content-Type: multipart/alternative; boundary=001a11c3ef46a5400f04e24ff74c Cc: netmod@ietf.org Subject: Re: [netmod] how to use 'mandatory' node X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 06:16:36 -0000 --001a11c3ef46a5400f04e24ff74c Content-Type: text/plain; charset=ISO-8859-1 Hi: If I want to create a instance of lista, should mandatory node be included ? But, you know, operation "merge" can be used to create a instance if the instance is not exists. When I received the netconf request with operation "merge", should I check whether the instance is exist? 2013/7/24 Andy Bierman > On Wed, Jul 24, 2013 at 7:37 AM, chong feng > wrote: > > Hi, > > If I want to modify one leaf's value, should mandatory nodes be included > in > > request? > > for example, > > lista---- > > |---key1 > > |---key2 > > |---mandatory-node > > |---leaf1 > > If I want to modify leaf1's value,the netconf request should be > > > > 1 > > 2 > > 3 > > 4 > > > > > > or > > > > 1 > > 2 > > 4 > > > > ? > > > > The 2nd one. > For config=true data nodes, mandatory means the running config > must contain the data node to be valid. > > Sec. 3.1 appears to indicate that config=false nodes can be mandatory, > but sec. 7.6.5 applies only to config=true data nodes. This definition > applies to config=true data nodes and rpc input nodes. > > A mandatory config=false data node, rpc output node or > notification node means that it must appear in the protocol message. > This implies that non-mandatory nodes in these messages are optional > to implement, but this is not correct. YANG conformance is only affected > by the "if-feature" stmt. > > > Andy > > > > > > > > > 2013/7/24 Martin Bjorklund > >> > >> Hi, > >> > >> chong feng wrote: > >> > hello everyone: > >> > I'm developing our own NETCONF agent. when i received a netconf > >> > request to > >> > delete a instance of list, a mandatory node was defined in this list. > >> > Should this mandatory node be included to this request? > >> > I think this node should not be included in netconf request,but there > >> > is no > >> > explicit description in RFC 6020. > >> > >> In general, if you do: > >> > >> > >> > >> the entire subtree under "foo" is deleted. There is no need to > >> explicitly delete nodes underneath "foo". > >> > >> > >> /martin > > > > > > > > _______________________________________________ > > netmod mailing list > > netmod@ietf.org > > https://www.ietf.org/mailman/listinfo/netmod > > > --001a11c3ef46a5400f04e24ff74c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi:
=A0 =A0If I want to create a instance of lista, sh= ould mandatory node be included ?
=A0 =A0
=A0 =A0But, y= ou know, operation "merge" can be used to create a instance if th= e instance is not exists.
=A0 =A0When I received the netconf request with operation "merge&= quot;, should I check whether the instance
=A0 =A0is exist?=A0


2013/7/24 An= dy Bierman <andy@yumaworks.com>
On Wed, Jul 24, 2013 at 7:= 37 AM, chong feng <fengchongl= lly@gmail.com> wrote:
> Hi,
> If I want to modify one leaf's value, should mandatory nodes be in= cluded in
> request?
> for example,
> lista----
> =A0 =A0 |---key1
> =A0 =A0 |---key2
> =A0 =A0 |---mandatory-node
> =A0 =A0 |---leaf1
> If I want to modify leaf1's value,the netconf request should be > =A0 =A0<lista operation=3D "merge">
> =A0 =A0 =A0 =A0<key1>1</key1>
> =A0 =A0 =A0 =A0<key2>2</key2>
> =A0 =A0 =A0 =A0<mandatory-node>3</mandatory-node>
> =A0 =A0 =A0 =A0<leaf1>4</leaf1>
> =A0 </lista>
>
> or
> =A0 <lista operation=3D "merge">
> =A0 =A0 =A0 =A0<key1>1</key1>
> =A0 =A0 =A0 =A0<key2>2</key2>
> =A0 =A0 =A0 =A0<leaf1>4</leaf1>
> =A0 </lista>
> ?
>

The 2nd one.
For config=3Dtrue data nodes, mandatory means the running config
must contain the data node to be valid.

Sec. 3.1 appears to indicate that config=3Dfalse nodes can be mandatory, but sec. 7.6.5 applies only to config=3Dtrue data nodes. =A0This definition=
applies to config=3Dtrue data nodes and rpc input nodes.

A mandatory config=3Dfalse data node, rpc output node or
notification node means that it must appear in the protocol message.
This implies that non-mandatory nodes in these messages are optional
to implement, but this is not correct. =A0YANG conformance is only affected=
by the "if-feature" stmt.


Andy

>
>
>
> 2013/7/24 Martin Bjorklund <mbj@t= ail-f.com>
>>
>> Hi,
>>
>> chong feng <fengchon= gllly@gmail.com> wrote:
>> > hello everyone:
>> > I'm developing our own NETCONF agent. when i received a n= etconf
>> > request to
>> > delete a instance of list, a mandatory node was defined in th= is list.
>> > Should this mandatory node be included to this request?
>> > I think this node should not be included in netconf request,b= ut there
>> > is no
>> > explicit description in RFC 6020.
>>
>> In general, if you do:
>>
>> =A0 <foo nc:operation=3D"delete"/>
>>
>> the entire subtree under "foo" is deleted. =A0There is n= o need to
>> explicitly delete nodes underneath "foo".
>>
>>
>> /martin
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>

--001a11c3ef46a5400f04e24ff74c-- From mbj@tail-f.com Thu Jul 25 02:25:38 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1008121F8EDF for ; Thu, 25 Jul 2013 02:25:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.786 X-Spam-Level: X-Spam-Status: No, score=-0.786 tagged_above=-999 required=5 tests=[AWL=-1.140, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_53=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_65=0.6, J_CHICKENPOX_73=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSathbSLSyP4 for ; Thu, 25 Jul 2013 02:25:33 -0700 (PDT) Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id 7279921F8DDD for ; Thu, 25 Jul 2013 02:25:25 -0700 (PDT) Received: from localhost (213-65-182-102-no181.tbcn.telia.com [213.65.182.102]) by mail.tail-f.com (Postfix) with ESMTPSA id 59F301200A3B; Thu, 25 Jul 2013 11:25:23 +0200 (CEST) Date: Thu, 25 Jul 2013 11:25:22 +0200 (CEST) Message-Id: <20130725.112522.506079812.mbj@tail-f.com> To: fengchongllly@gmail.com From: Martin Bjorklund In-Reply-To: References: X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netmod@ietf.org Subject: Re: [netmod] how to use 'mandatory' node X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 09:25:38 -0000 Hi, chong feng wrote: > Hi: > If I want to create a instance of lista, should mandatory node be > included ? mandatory means that the node MUST be there in a valid configuration. If you create the list entry in the candidate, the mandatory nodes does not have to be there. But if you try to commit this candidate, commit will fail b/c the mandatory node is missing. See section 8 of RFC 6030. /martin > But, you know, operation "merge" can be used to create a instance if > the > instance is not exists. > When I received the netconf request with operation "merge", should I > check whether the instance > is exist? > > > 2013/7/24 Andy Bierman > > > On Wed, Jul 24, 2013 at 7:37 AM, chong feng > > wrote: > > > Hi, > > > If I want to modify one leaf's value, should mandatory nodes be > > > included > > in > > > request? > > > for example, > > > lista---- > > > |---key1 > > > |---key2 > > > |---mandatory-node > > > |---leaf1 > > > If I want to modify leaf1's value,the netconf request should be > > > > > > 1 > > > 2 > > > 3 > > > 4 > > > > > > > > > or > > > > > > 1 > > > 2 > > > 4 > > > > > > ? > > > > > > > The 2nd one. > > For config=true data nodes, mandatory means the running config > > must contain the data node to be valid. > > > > Sec. 3.1 appears to indicate that config=false nodes can be mandatory, > > but sec. 7.6.5 applies only to config=true data nodes. This > > definition > > applies to config=true data nodes and rpc input nodes. > > > > A mandatory config=false data node, rpc output node or > > notification node means that it must appear in the protocol message. > > This implies that non-mandatory nodes in these messages are optional > > to implement, but this is not correct. YANG conformance is only > > affected > > by the "if-feature" stmt. > > > > > > Andy > > > > > > > > > > > > > > 2013/7/24 Martin Bjorklund > > >> > > >> Hi, > > >> > > >> chong feng wrote: > > >> > hello everyone: > > >> > I'm developing our own NETCONF agent. when i received a netconf > > >> > request to > > >> > delete a instance of list, a mandatory node was defined in this list. > > >> > Should this mandatory node be included to this request? > > >> > I think this node should not be included in netconf request,but there > > >> > is no > > >> > explicit description in RFC 6020. > > >> > > >> In general, if you do: > > >> > > >> > > >> > > >> the entire subtree under "foo" is deleted. There is no need to > > >> explicitly delete nodes underneath "foo". > > >> > > >> > > >> /martin > > > > > > > > > > > > _______________________________________________ > > > netmod mailing list > > > netmod@ietf.org > > > https://www.ietf.org/mailman/listinfo/netmod > > > > > From kedargaonkar@gmail.com Sun Jul 21 15:20:07 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7B121F9D56 for ; Sun, 21 Jul 2013 15:20:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2BV45du5i2ag for ; Sun, 21 Jul 2013 15:20:06 -0700 (PDT) Received: from mail-ea0-x232.google.com (mail-ea0-x232.google.com [IPv6:2a00:1450:4013:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE2821F9D17 for ; Sun, 21 Jul 2013 15:20:06 -0700 (PDT) Received: by mail-ea0-f178.google.com with SMTP id l15so3412219eak.37 for ; Sun, 21 Jul 2013 15:20:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=QKwPLHgxMKjNJg0Tk5ektSxvWUPizuLBDiiHB7lKM3A=; b=EDb/pdx0IqVPbYMDzPEGAUNoSJpbSDSD1fu0Xw0Ohz/IJe4Sb47tMlXFEPH/vahJgm lCC8ftb2VYgRyM6IBqUf5QTps//RxXwbkB++/DfoscwoWqe3xIidUJ71x54Cdtg+Blvf pE9y+4l34zlcgmtmEGZzu/iO/VPlmT4mQXTYLPvdZHr2QG5Txs7Tje6K6Ca1Vqfsc694 6yOa8W8z+/vgJakXA3wLQSjGcKlZmxfv9eStahMWiPv30baTu/Ap5mM6wQqlGKpIrJOa QJ5wUI1ccaRC7ADufxCa23AeqjuqivjgxDGdUDqOBrpcekkbh3ZYkMrKoR7R9YB93/rX AgTA== MIME-Version: 1.0 X-Received: by 10.14.115.132 with SMTP id e4mr24923390eeh.54.1374445205495; Sun, 21 Jul 2013 15:20:05 -0700 (PDT) Received: by 10.14.199.196 with HTTP; Sun, 21 Jul 2013 15:20:05 -0700 (PDT) Date: Sun, 21 Jul 2013 15:20:05 -0700 Message-ID: From: Kedar Gaonkar To: netmod@ietf.org Content-Type: multipart/alternative; boundary=001a11c29a683cc3f004e20cf611 X-Mailman-Approved-At: Fri, 26 Jul 2013 23:47:27 -0700 Subject: [netmod] Usage of rpc under container or list statement X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jul 2013 22:20:07 -0000 --001a11c29a683cc3f004e20cf611 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Greetings, Can I have an rpc statement under a container or a list? RFC 6020 doesn=92t mention =91rpc=92 under section 7.5.2 (container substatements) or 7.8.1 (l= ist substatements). In my data model, I have a list defined for access points. The key for this list is the mac-address of access point. Along with all the leaves, I wanted to define an rpc under this list that enables or disables the LED of access-point. Since this rpc has meaning only for access-points, I was wondering if I could logically group it under the list, or is it mandatory that all rpcs have to be defined globally outside of containers? container access_point { config false; list ap { key =93mac_address=94; leaf mac_address { type yang:mac-address; = } rpc set_led { config false; input { leaf on { type boolean; } } } } } Thanks, Kedar --001a11c29a683cc3f004e20cf611 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

G= reetings,


<= /p>

Can I have an r= pc statement under a container or a list? RFC 6020 doesn=92t mention =91rpc= =92 under section 7.5.2 (container substatements) or 7.8.1 (list substateme= nts).


In my data model, I have a= list defined for access points. The key for this list is the mac-address o= f access point. Along with all the leaves, I wanted to define an rpc under = this list that enables or disables the LED of access-point. Since this rpc = has meaning only for access-points, I was wondering if I could logically gr= oup it under the list, or is it mandatory that all rpcs have to be defined = globally outside of containers?

=A0

container access_point {

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 config false;=A0

=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0 list ap {

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 key =93mac_address=94;

=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 l= eaf mac_address =A0{ type yang:mac-address; }

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <some-other-leaves..&g= t;

=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 r= pc set_led {

= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 config f= alse;

=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 input {

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 leaf on { type boolean; }

=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 }

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 }

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 }

}


Thanks,
Kedar
--001a11c29a683cc3f004e20cf611-- From wwwrun@rfc-editor.org Wed Jul 31 07:17:26 2013 Return-Path: X-Original-To: netmod@ietfa.amsl.com Delivered-To: netmod@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2649F21F9FCF; Wed, 31 Jul 2013 07:17:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.016 X-Spam-Level: X-Spam-Status: No, score=-102.016 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GoTn1CrtjjIn; Wed, 31 Jul 2013 07:17:25 -0700 (PDT) Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB2521F99CE; Wed, 31 Jul 2013 07:17:25 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id E17E46212E; Wed, 31 Jul 2013 07:13:56 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20130731141356.E17E46212E@rfc-editor.org> Date: Wed, 31 Jul 2013 07:13:56 -0700 (PDT) Cc: drafts-update-ref@iana.org, netmod@ietf.org, rfc-editor@rfc-editor.org Subject: [netmod] RFC 6991 on Common YANG Data Types X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 14:17:26 -0000 A new Request for Comments is now available in online RFC libraries. RFC 6991 Title: Common YANG Data Types Author: J. Schoenwaelder, Ed. Status: Standards Track Stream: IETF Date: July 2013 Mailbox: j.schoenwaelder@jacobs-university.de Pages: 30 Characters: 60242 Obsoletes: RFC6021 I-D Tag: draft-ietf-netmod-rfc6021-bis-03.txt URL: http://www.rfc-editor.org/rfc/rfc6991.txt This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. This document is a product of the NETCONF Data Modeling Language Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php For downloading RFCs, see http://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC