Re: [netmod] schema mount and YANG library

Lou Berger <lberger@labn.net> Wed, 17 January 2018 19:10 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 9F93C12E858 for <netmod@ietfa.amsl.com>; Wed, 17 Jan 2018 11:10:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 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=-0.001, 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 SDy6u6U1rqrO for <netmod@ietfa.amsl.com>; Wed, 17 Jan 2018 11:10:07 -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 718491270AE for <netmod@ietf.org>; Wed, 17 Jan 2018 11:10:07 -0800 (PST)
Received: from cmgw3 (unknown [10.0.90.84]) by gproxy4.mail.unifiedlayer.com (Postfix) with ESMTP id 18D56176010 for <netmod@ietf.org>; Wed, 17 Jan 2018 12:10:07 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id zXA41w0042SSUrH01XA7pM; Wed, 17 Jan 2018 12:10:07 -0700
X-Authority-Analysis: v=2.2 cv=XM9AcUpE c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=RgaUWeydRksA:10 a=IQTN1rbPY9PPOIutjD8A: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=fuBE2O7mtJe7IBMTVCdb5FnhzPCIZ8N/9zzJjrN3uaA=; b=PEjaQo8bfO3RjjDMTVKYAcmFgY Sc0gNKv4rBLqIUbzc7AKPxuKlr4VD4PnN7UT8vCiZCfvKp5murnINlUGWIAaF02HHqjRPSAHeCZHv tFj8tbQskoY3/NDSmlbrpkg3R;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:52548 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 1ebt63-0047pj-SP; Wed, 17 Jan 2018 12:10:03 -0700
To: Ladislav Lhotka <lhotka@nic.cz>, Martin Bjorklund <mbj@tail-f.com>
Cc: netmod@ietf.org
References: <754a4ce8-a3de-ad0b-03a4-0edc500f9cf3@labn.net> <20180117.092002.464472752076487902.mbj@tail-f.com> <e3d5c195-a737-057a-5911-daa50a06c4bd@labn.net> <20180117.154205.449528767667713089.mbj@tail-f.com> <16104ca0948.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <1516206380.1388.62.camel@nic.cz>
From: Lou Berger <lberger@labn.net>
Message-ID: <75f62f7e-6561-6d16-c638-ab36daa888bc@labn.net>
Date: Wed, 17 Jan 2018 14:10:01 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <1516206380.1388.62.camel@nic.cz>
Content-Type: text/plain; charset="utf-8"; format="flowed"
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-Source-IP: 100.15.86.101
X-Exim-ID: 1ebt63-0047pj-SP
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]:52548
X-Source-Auth: lberger@labn.net
X-Email-Count: 6
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ZAaoO5N4yHfXkmN8GuHASjcKLOg>
Subject: Re: [netmod] schema mount and YANG library
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: Wed, 17 Jan 2018 19:10:17 -0000


On 1/17/2018 11:26 AM, Ladislav Lhotka wrote:
>>>> But when we discussed this the last time having inline schema
>>>> available at the top level (in the SM module), the general consensus
>>>> was that having YL under inline was the preferred approach.
>>> What is new now is that we have an indirection; each instance has its
>>> own pointer to the schema at the top level.  In the previous
>>> discussion, having the schema at the top level implied that all
>>> instances shared the same schema, and*that*  was rejected.
>>>
>> Indirection was possible at the previous time and is part of the current
>> scheme Mount definition. Yes, you need to use different mount points to
>> reference different schema, but take a look at the ni document that's
>> exactly what we are doing there. So I don't believe this is the point that
> What Martin and I are talking about is a mount point that is a list node of the
> "use-schema" type. There is no way how different entries of this list could have
> different schemas.
>
> The same applies to a container mount point that is inside a list. Then you can
> also have multiple*instances*  of the mount point, and with "use-schema" there
> is no way how these instances could have different schemas.
umm, if a server knows enough to use the right metadata indirection (per 
current proposal), it would have also know enough to use the right mount 
point and use-schema (in the old proposal).  Again, the latter is what 
we're doing to solve this *exact* problem for the non-inline case in the 
NI draft.

The only thing new in the proposal is how to encode the indirection, it 
doesn't change the fundamental points/discussion from when we decided on 
the current solution.

Lou
> Lada
>