Re: [Netconf] bug in ietf-netconf-monitoring.yang

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 27 June 2010 10:12 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A1883A68BB for <netconf@core3.amsl.com>; Sun, 27 Jun 2010 03:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[AWL=0.712, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dPYFgqLBcxvv for <netconf@core3.amsl.com>; Sun, 27 Jun 2010 03:12:25 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 8DD773A68A0 for <netconf@ietf.org>; Sun, 27 Jun 2010 03:12:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,491,1272859200"; d="scan'208";a="225122135"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 27 Jun 2010 06:12:34 -0400
X-IronPort-AV: E=Sophos;i="4.53,491,1272859200"; d="scan'208";a="476333367"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 27 Jun 2010 06:12:34 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 27 Jun 2010 12:12:12 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F39A5@307622ANEX5.global.avaya.com>
In-Reply-To: <4C250371.50302@iwl.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Netconf] bug in ietf-netconf-monitoring.yang
Thread-Index: AcsUnJfZOir0xaiHSZievtZThZ54yQBRGNcQ
References: <4C250371.50302@iwl.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: andyb@iwl.com, NETCONF <netconf@ietf.org>
Subject: Re: [Netconf] bug in ietf-netconf-monitoring.yang
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jun 2010 10:12:27 -0000

Should this edit be included in the RFC Editor notes? 

Were all the other current RFC Editor notes made redundant by the new
version and can they be deleted? 

(Questions for the editors and document shepherd)

Dan
 

> -----Original Message-----
> From: netconf-bounces@ietf.org 
> [mailto:netconf-bounces@ietf.org] On Behalf Of Andy Bierman
> Sent: Friday, June 25, 2010 10:29 PM
> To: NETCONF
> Subject: [Netconf] bug in ietf-netconf-monitoring.yang
> 
> Hi,
> 
> Please use the correct data type from ietf-yang-types, since 
> that module is already imported anyway:
> 
> /netconf-state/datastores/datastore/locks/lock-type/partial-lo
> cks/partial-locks/select
> 
>       leaf-list select {
>          type string;
>               ^^^^^^
>          min-elements 1;
>           description
>             "The xpath expression which was used to request
>              the lock.  The select expression indicates the
>              original intended scope of the lock.";
>          }
> 
> 
> s/string/yang:xpath1.0/
> 
> Tools need to be aware of QNames in the content.
> 
> 
> 
> Andy
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>