Re: [netmod] review of draft-ietf-netmod-schema-mount-08

Lou Berger <lberger@labn.net> Sat, 11 November 2017 03:31 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 1674C1292D3 for <netmod@ietfa.amsl.com>; Fri, 10 Nov 2017 19:31:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.158
X-Spam-Level:
X-Spam-Status: No, score=-3.158 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Icb4_Ig1w2qt for <netmod@ietfa.amsl.com>; Fri, 10 Nov 2017 19:31:30 -0800 (PST)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) (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 500F21270AE for <netmod@ietf.org>; Fri, 10 Nov 2017 19:31:28 -0800 (PST)
Received: from cmgw4 (unknown [10.0.90.85]) by gproxy4.mail.unifiedlayer.com (Postfix) with ESMTP id F3F40176579 for <netmod@ietf.org>; Fri, 10 Nov 2017 20:06:43 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id YT6g1w00S2SSUrH01T6j8s; Fri, 10 Nov 2017 20:06:43 -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=xqWC_Br6kY4A:10 a=sC3jslCIGhcA:10 a=y1sg0DtI7uQ6J5gZwZYA: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:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject: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=+wK0aw0fF00HrZHdAlCqo9ZahsEojvPFitteqiWQHkY=; b=KzX0MAetvHEPigQuppLY8rYOv2 IBt2ocH8U+y5qAN2GB3Imlix4OsoOASERCxWwJb3YSiSSntfq/REoRsCseHn7l65/K8Z/IX7qQpO4 icosx4jEUn26h90j5ph0Gndvg;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:42654 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1eDM80-000AqQ-II; Fri, 10 Nov 2017 20:06:40 -0700
To: Martin Bjorklund <mbj@tail-f.com>, kwatsen@juniper.net
Cc: netmod@ietf.org
References: <F8D5C6D5-1665-43B0-88B6-11381BBFCBB9@juniper.net> <87po8z9x5p.fsf@nic.cz> <D2588141-03D3-43BD-AE39-E98D48052E26@juniper.net> <20171108.095019.1523851923210652414.mbj@tail-f.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <608159e0-f6f4-7918-d0f5-9c0464213ca7@labn.net>
Date: Sat, 11 Nov 2017 00:50:04 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171108.095019.1523851923210652414.mbj@tail-f.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
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: 1eDM80-000AqQ-II
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([IPv6:::1]) [100.15.86.101]:42654
X-Source-Auth: lberger@labn.net
X-Email-Count: 11
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/9LhYLeUPIdNgMat5r_NLkPHMsmI>
Subject: Re: [netmod] review of draft-ietf-netmod-schema-mount-08
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: Sat, 11 Nov 2017 03:31:32 -0000


On 11/8/2017 4:50 PM, Martin Bjorklund wrote:
>>> The "use-schema" case shouldn't pose big problems because it is
>>> essentially an externally specified augment. The "inline" case is
>>> somewhat disturbing though: could the embedded YANG library instances
>>> be different in different datastores?
>> YANG Library is only available in <operational> (it's all config false).
>> I think you mean the embedded YANG Library instances under the mount
>> points.  Yes, you may have a problem here.  Still, this isn't my question,
>> is more about schema-mounting requirements across datastores.  E.g., if
>> a schema-mount exists in <running>, must it existing in <intended> and
>> <operational> as well?  Conversely, if a schema-mount exists in
>> <operational>, must it exist in <running>?  I think this draft should
>> clarify such things.
> I agree that this needs to be clarified.  This issue partly comes from
> the fact that schema mount uses the groupings in the old yang
> library.  I think we need to use the new groupings from rfc7895bis.
> 

We previously discussed this point an chose not to use rfc7895bis as we 
wanted to allow current implementations to add support NIs/LNEs with 
minimal additional work, and specifically not require support for 
rfc7895bis and NMDA to support LNEs/NIs (and consequently schema mount).

I do think it would be good to have rfc7895bis supersede 
ietf-yang-schema-mount by incorporating its functionality, but that 
wouldn't be a change to this document.

Lou