[netmod] comment on draft-bierman-netmod-yang-data-ext

Lou Berger <lberger@labn.net> Mon, 27 November 2017 21:59 UTC

Return-Path: <lberger@labn.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BA699124D6C for <netmod@ietfa.amsl.com>; Mon, 27 Nov 2017 13:59:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jWM13XsXyveG for <netmod@ietfa.amsl.com>; Mon, 27 Nov 2017 13:59:11 -0800 (PST)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACF7D1200C5 for <netmod@ietf.org>; Mon, 27 Nov 2017 13:59:11 -0800 (PST)
Received: from cmgw2 (unknown []) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 3DDC21E17C1 for <netmod@ietf.org>; Mon, 27 Nov 2017 14:59:11 -0700 (MST)
Received: from box313.bluehost.com ([]) by cmgw2 with id f9z81w0042SSUrH019zBwb; Mon, 27 Nov 2017 14:59:11 -0700
X-Authority-Analysis: v=2.2 cv=dZfw5Tfe c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=sC3jslCIGhcA:10 a=imFlxykSS6GNyt6sfbMA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:To:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=tW9kML1zSq0O2AusEgh17oR2Sz8jTns6nxd7IXHR9Tk=; b=xxhGoirxkYxQPkT5vcUKiJqzuH 55my0rYCkLYQA2gC+8v59dUP7J245h1WHllLKF6pKpGazT/GVX1hjLmepMS2lS0hzA0Mdltel8ke7 tfOL7sn8JaB1OmibAPSRerEw+;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([]:39522 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <lberger@labn.net>) id 1eJRQh-002rfm-Rv; Mon, 27 Nov 2017 14:59:07 -0700
To: draft-bierman-netmod-yang-data-ext@ietf.org, NetMod WG <netmod@ietf.org>
From: Lou Berger <lberger@labn.net>
Message-ID: <a2eb0409-de68-0bcb-31be-c2acf2acb926@labn.net>
Date: Mon, 27 Nov 2017 16:59:08 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Exim-ID: 1eJRQh-002rfm-Rv
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([IPv6:::1]) []:39522
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/omrO6Bv4vMW4_U7V2AvCZA8KuVU>
Subject: [netmod] comment on draft-bierman-netmod-yang-data-ext
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Nov 2017 21:59:13 -0000


    I was looking at how yd:yang-data (this draft) relates to
rc:yang-data (rfc8040).  The document seems to imply that this draft's
extension is a replacement in one place (see abstract) , is supplemental
in another (sec 1, plus augment-yang-data example) and perhaps
orthogonal in a final (that rc:yang-data is still used/referenced at
all).  I think the document should be clear as to it's objective with
respect to  rc:yang-data. 

As rc:yang-data is currently defined in a protocol specific way, I (with
any/all hats) would prefer to see a definition of yang-data that would
work for any protocol that encodes and transports yang.  I also
generally think that having two definitions for basically the same
mechanism isn't beneficial to implementors of IETF RFCs, so this leads
me to suggest that if this document becomes a WG document it should
deprecate rc:yang-data.