RE: Last Call: <draft-ietf-netmod-yang-metadata-04.txt> (Defining and Using Metadata with YANG) to Proposed Standard

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 09 March 2016 16:10 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5275D12DF9E; Wed, 9 Mar 2016 08:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K-rtNNgSaHSw; Wed, 9 Mar 2016 08:10:17 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAAD612E0F2; Wed, 9 Mar 2016 08:02:23 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2AGAgD+qt9W/xUHmMZcGQEBAQEPAQEBAYJfK4E/BrhKghMBDYFphg8CgUE4FAEBAQEBAQFkHAuEQQEBAQECARIoNAsFBwQCAQgNBAQBAQsUBQQHMhQJCAIEDgUIGod6CAGlMpl4AQEBAQEBAQMBAQEBAQEBAQEBARWGGIRBhDqDK4EPBZcrAY9ThESDGYU6jloeAQFCgjCBNGqIRiUWAX0BAQE
X-IPAS-Result: A2AGAgD+qt9W/xUHmMZcGQEBAQEPAQEBAYJfK4E/BrhKghMBDYFphg8CgUE4FAEBAQEBAQFkHAuEQQEBAQECARIoNAsFBwQCAQgNBAQBAQsUBQQHMhQJCAIEDgUIGod6CAGlMpl4AQEBAQEBAQMBAQEBAQEBAQEBARWGGIRBhDqDK4EPBZcrAY9ThESDGYU6jloeAQFCgjCBNGqIRiUWAX0BAQE
X-IronPort-AV: E=Sophos;i="5.24,310,1454994000"; d="scan'208";a="146006384"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Mar 2016 11:02:20 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 09 Mar 2016 11:02:19 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 9 Mar 2016 17:02:18 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-netmod-yang-metadata-04.txt> (Defining and Using Metadata with YANG) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-netmod-yang-metadata-04.txt> (Defining and Using Metadata with YANG) to Proposed Standard
Thread-Index: AQHRbw42QO6jzW2l30iNn8jwXjUBNp9RW4UQ
Date: Wed, 9 Mar 2016 16:02:16 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BF85B79@AZ-FFEXMB04.global.avaya.com>
References: <20160224141730.8516.29327.idtracker@ietfa.amsl.com>
In-Reply-To: <20160224141730.8516.29327.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.47]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zmPu0dpZqQgEpYw9scpUoX9pljI>
Cc: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "kwatsen@juniper.net" <kwatsen@juniper.net>, "draft-ietf-netmod-yang-metadata@ietf.org" <draft-ietf-netmod-yang-metadata@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2016 16:10:20 -0000

This documents looks fine to me. 

I have one comment though. 

In Section 6: 

>    [RFC6110] defines the standard mapping of YANG data models to
   Document Schema Definition Languages (DSDL) [ISO.19757-1].  This
   section specifies the mapping for the extension statement
   "md:annotation" (Section 7), which enables validation of XML instance
   documents containing metadata annotations.

>   The first step of the DSDL mapping procedure, i.e., the
   transformation of the YANG data model to the hybrid schema (see
   sec. 6 in [RFC6110]), is modified as follows:

...

Does not this mean that the document updated RFC 6110 and this should be mentioned in the header? 

Regards,

Dan


> -----Original Message-----
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: Wednesday, February 24, 2016 4:18 PM
> To: IETF-Announce
> Cc: bclaise@cisco.com; netmod-chairs@ietf.org; draft-ietf-netmod-yang-
> metadata@ietf.org; kwatsen@juniper.net; netmod@ietf.org
> Subject: Last Call: <draft-ietf-netmod-yang-metadata-04.txt> (Defining and
> Using Metadata with YANG) to Proposed Standard
> 
> 
> The IESG has received a request from the NETCONF Data Modeling Language
> WG (netmod) to consider the following document:
> - 'Defining and Using Metadata with YANG'
>   <draft-ietf-netmod-yang-metadata-04.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2016-03-09. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the beginning of
> the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document defines a YANG extension statement that allows for
>    defining metadata annotations in YANG modules.  The document also
>    specifies XML and JSON encoding of annotations and other rules for
>    annotating instances of YANG data nodes.
> 
> 
>