IETF Logo Mail Archive

Re: [netmod] Design-Time schema mount

Balazs Lengyel <balazs.lengyel@ericsson.com> Thu, 28 July 2016 14:37 UTC

Return-Path: <balazs.lengyel@ericsson.com>
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 9376312D788 for <netmod@ietfa.amsl.com>; Thu, 28 Jul 2016 07:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.497
X-Spam-Level:
X-Spam-Status: No, score=-3.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 B_8m_5DxYJFs for <netmod@ietfa.amsl.com>; Thu, 28 Jul 2016 07:37:27 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 018D512D77B for <netmod@ietf.org>; Thu, 28 Jul 2016 07:37:26 -0700 (PDT)
X-AuditID: c1b4fb25-6efff70000000bbb-97-579a18a4cdd9
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by (Symantec Mail Security) with SMTP id 88.52.03003.4A81A975; Thu, 28 Jul 2016 16:37:25 +0200 (CEST)
Received: from [159.107.198.13] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.92) with Microsoft SMTP Server id 14.3.301.0; Thu, 28 Jul 2016 16:37:24 +0200
To: Ladislav Lhotka <lhotka@nic.cz>
References: <6d87e060-3c52-38f6-e499-da3d7c20a783@ericsson.com> <m2a8h1c3r3.fsf@birdie.labs.nic.cz> <b7f89965-f240-3909-dc49-8555c0eace57@ericsson.com> <6C7B9426-DB44-40B0-9AEE-1A7A0D51D1D0@nic.cz>
From: Balazs Lengyel <balazs.lengyel@ericsson.com>
Message-ID: <a8a448f5-46e1-56ff-e168-280e0e5213d1@ericsson.com>
Date: Thu, 28 Jul 2016 16:37:24 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <6C7B9426-DB44-40B0-9AEE-1A7A0D51D1D0@nic.cz>
Content-Type: text/html; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM2J7lO5SiVnhBk0/pS0urJrLZjH/YiOr A5PHkiU/mTw2Xb7DGMAUxWWTkpqTWZZapG+XwJXxaMd2toJb/BW3vvUyNTB+5+5i5OSQEDCR uDitj72LkYtDSGA9o8Ty18tYIZw1jBLL2nqYQKqEBfQk7n3ZB2aLCChLXJzwkwXEFhI4zShx 7acPiM0soC5x59RjNhCbTcBIYmr/eaAaDg5eAXuJ7e84QMIsAqoSzy9MZQcJiwrESKzvSwAJ 8woISpyc+QRsIqeAlcTN9jtsEBP1Ja7fuc8KYctLNG+dzQyxVUPi4YW/rBMYBWYhaZ+FpGUW kpYFjMyrGEWLU4uTctONjPVSizKTi4vz8/TyUks2MQKD8uCW36o7GC+/cTzEKMDBqMTDu+Db jHAh1sSy4srcQ4wSHMxKIryTRWeFC/GmJFZWpRblxxeV5qQWH2KU5mBREuf1f6kYLiSQnliS mp2aWpBaBJNl4uCUamBU/P1YVlzzbsiHB1FlrD1ZMRO5pO0Ea3uaV/jKH//3L3dT776WV32P Jyoc9Qj64b9c8ZeZr17C+jIu+UlTJKtM72t5rdq05+rZO9VdItZc79Sf1v2czr1OcpEt5/1N xk/e/Dpq5K19zOZYfrvk8mlTM/qaDkf9Xqxo46B5OGyKh/w2o7nMe5YosRRnJBpqMRcVJwIA m+IsVkYCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/_ilRByNRrpEAV9tqO9X7as-uNv0>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] Design-Time schema mount
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 28 Jul 2016 14:37:28 -0000

Hello Lada,

I want a formal way to define mount data. I want tools to understand it, so RFC text or an unspecified file  is a not a good solution.

We could have described any data model in plain English. The whole point of YANG is to have a formal definition. If containing one container in another is described in a formal way why is containing a full module in a container less important?

My solution would only use standard YANG files with a well specified content. I need the same level of precision from any alternative.

Balazs


On 2016-07-28 16:14, Ladislav Lhotka wrote:
Solution: My problem is that the specific data in the yang-library or in ietf-yang-schema-mount is only defined and available in run-time, so I don't understand how it could solve the design-time schema-mount requirement. IMHO whatever the solution, it needs to be in a file.

YANG library data can appear in the RFC text, in a file, or elsewhere off line.

We could do the same with "mount-points" data as defined in draft-ietf-netmod-schema-mount-02 but only with one level of mounts. 



-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
Senior Specialist
Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com

v2.23.0 | Report a Bug | By Email