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

Lou Berger <lberger@labn.net> Tue, 28 November 2017 12:00 UTC

Return-Path: <lberger@labn.net>
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 1AA2B126D3F for <netmod@ietfa.amsl.com>; Tue, 28 Nov 2017 04:00:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id siP6wKnBTvbR for <netmod@ietfa.amsl.com>; Tue, 28 Nov 2017 04:00:13 -0800 (PST)
Received: from gproxy8-pub.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) (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 B3563126C2F for <netmod@ietf.org>; Tue, 28 Nov 2017 04:00:13 -0800 (PST)
Received: from cmgw4 (unknown [10.0.90.85]) by gproxy8.mail.unifiedlayer.com (Postfix) with ESMTP id 0D3011AB359 for <netmod@ietf.org>; Tue, 28 Nov 2017 05:00:11 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id fQ061w02T2SSUrH01Q0A8c; Tue, 28 Nov 2017 05:00:11 -0700
X-Authority-Analysis: v=2.2 cv=JNNLi4Cb c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=sC3jslCIGhcA:10 a=u07AKapRAAAA:8 a=wU2YTnxGAAAA:8 a=AqeI_lbacKu6uIOxffkA:9 a=QEXdDO2ut3YA:10 a=SkebfZ6J2Mmvk2rLHZle:22 a=Yz9wTY_ffGCQnEDHKrcv:22
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:Subject: References:In-Reply-To:Message-ID:Date:CC:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=upLYVbimDUG7MiI4J569+Ep+cmiM76DLTxx2wLxuvgs=; b=MTDuUp+mie2EiCbfrOQsSTXWlN da4REYlvg4poAiH14eHiAWOGmpXqNSlrNgdCpvk08JyJtuBmhXbjqYvvTkX9yodz4Q3uIkKjejSHC D8jImONQAFSnp15lqzCinp27K;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:39595 helo=[11.4.0.163]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <lberger@labn.net>) id 1eJeYY-001CEq-C9; Tue, 28 Nov 2017 05:00:06 -0700
From: Lou Berger <lberger@labn.net>
To: Martin Bjorklund <mbj@tail-f.com>
CC: draft-bierman-netmod-yang-data-ext@ietf.org, netmod@ietf.org
Date: Tue, 28 Nov 2017 07:00:03 -0500
Message-ID: <160027f91b8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <20171128.105313.1322848757325572415.mbj@tail-f.com>
References: <a2eb0409-de68-0bcb-31be-c2acf2acb926@labn.net> <20171128.105313.1322848757325572415.mbj@tail-f.com>
User-Agent: AquaMail/1.11.0-568 (build: 101100004)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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-Source-IP: 100.15.86.101
X-Exim-ID: 1eJeYY-001CEq-C9
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([11.4.0.163]) [100.15.86.101]:39595
X-Source-Auth: lberger@labn.net
X-Email-Count: 1
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/R8Myj1f4TPPbTEAb55et0Y2LiyI>
Subject: Re: [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: Tue, 28 Nov 2017 12:00:15 -0000

Hi Martin,

See below.


On November 28, 2017 4:55:17 AM Martin Bjorklund <mbj@tail-f.com> wrote:

> Hi,
>
> Lou Berger <lberger@labn.net> wrote:
>> Hi,
>>
>>     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.
>
> Agreed.  It is intended to replace rc:yang-data.  I have fixed the
> example that used rc:yang-data.  Do you think we need any changes to
> section 1 to clarify this?
>

Only that it should also reflect how the update/deprecation discussed below 
is handled.

>> 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.
>
> I assume this would formally mean that this document would "Update"
> RFC 8040,

Yes, this looks right. although it is a bit subject to how the next point 
is addressed

> and then in the document have text that explains that
> rc:yang-data is deprecated?  Or do you suggest that we actually do a
> 8040bis that formally marks the rc:yang-data extension as
> "deprecated", and instead uses yd:yang-data?
>

This is one option. Another is to just update the rc module with 
rc:yang-data as deprecated.

At this point, since the document is still an individual draft, I suggest 
that the authors propose their preference and that the working group weigh 
in during the acceptance and normal WG processing.

Thanks,

Lou

>
> /martin
>