[netmod] Fwd: Re: YANG schema mount - any early implementations?

Hayden Brown <Hayden.Brown@Aviatnet.com> Mon, 30 July 2018 23:27 UTC

Return-Path: <Hayden.Brown@Aviatnet.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 A5E0613114F for <netmod@ietfa.amsl.com>; Mon, 30 Jul 2018 16:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aviatus.onmicrosoft.com
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 TV29lUD5cIjX for <netmod@ietfa.amsl.com>; Mon, 30 Jul 2018 16:27:35 -0700 (PDT)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700075.outbound.protection.outlook.com [40.107.70.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E786E1311C4 for <netmod@ietf.org>; Mon, 30 Jul 2018 16:27:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aviatus.onmicrosoft.com; s=selector1-aviatnet-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9LCZWuLEiJIAlktZNa7P+C+yn64qYX2LJtKZToUbPvA=; b=Fk31VtAKh9d1CQ8tTwZlGPRfTyWEPiNOGhtbrQc0vVuo54YcK/GGAn/hyqGdCWVaUrNueeA5qEz9ceRC23iR3axbRQlZZy+MkoosngNaFDF8Ix1aQv1fVbhl4+PpDVqmEq3KJ2BeBlEeS0GIEXnq6R1W+MaZND+hl6WFrbwQapc=
Received: from DM5PR08CA0037.namprd08.prod.outlook.com (2603:10b6:4:60::26) by BN1PR08MB155.namprd08.prod.outlook.com (2a01:111:e400:40d::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.995.19; Mon, 30 Jul 2018 23:27:29 +0000
Received: from DM3NAM03FT030.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e49::201) by DM5PR08CA0037.outlook.office365.com (2603:10b6:4:60::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.995.17 via Frontend Transport; Mon, 30 Jul 2018 23:27:29 +0000
Authentication-Results: spf=pass (sender IP is 192.147.115.52) smtp.mailfrom=Aviatnet.com; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=bestguesspass action=none header.from=Aviatnet.com;
Received-SPF: Pass (protection.outlook.com: domain of Aviatnet.com designates 192.147.115.52 as permitted sender) receiver=protection.outlook.com; client-ip=192.147.115.52; helo=mail-send.aviatnet.com;
Received: from mail-send.aviatnet.com (192.147.115.52) by DM3NAM03FT030.mail.protection.outlook.com (10.152.82.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1038.3 via Frontend Transport; Mon, 30 Jul 2018 23:27:28 +0000
From: Hayden Brown <Hayden.Brown@Aviatnet.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: Fwd: Re: [netmod] YANG schema mount - any early implementations?
Thread-Index: AdQoXL4JL5BXFoDLT6iNrQ7jsBoYyA==
Date: Mon, 30 Jul 2018 23:27:26 +0000
Message-ID: <5df7eb40589d4631a33c704358bc8f8e@USP-EXCHPROD01.GNET.global.vpn>
Accept-Language: en-NZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.15.6.9]
Content-Type: multipart/alternative; boundary="_000_5df7eb40589d4631a33c704358bc8f8eUSPEXCHPROD01GNETglobal_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:192.147.115.52; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(376002)(346002)(39850400004)(136003)(396003)(2980300002)(438002)(53754006)(199004)(189003)(5660300001)(2906002)(5024004)(6306002)(9686003)(2473003)(6512007)(229853002)(336012)(260700001)(24736004)(36736006)(102836004)(108616005)(316002)(106002)(186003)(26005)(606006)(6916009)(53546011)(16586007)(6116002)(54896002)(118246002)(126002)(84326002)(86362001)(790700001)(236005)(2351001)(561944003)(7636002)(246002)(7596002)(8676002)(7736002)(356003)(53416004)(966005)(478600001)(72206003)(476003)(3846002)(956004)(5640700003)(6486002)(486006)(2501003)(25786009)(8936002)(1730700003)(106466001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN1PR08MB155; H:mail-send.aviatnet.com; FPR:; SPF:Pass; LANG:en; PTR:mail-send.aviatnet.com; A:1; MX:1;
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM03FT030; 1:DswMjwPFdTRQkYGSRrvwN78owRPEjBgHC5zeXEgSWBuNVcSz08PP/NRPhDXI+d69bccMXx6j+kNMFmsx/svIGhle9SnymxxFwPbADrAlvjDgQ1HkMZYRTG7WA6IN4gjZ
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 5ac2d3e5-8478-43af-c750-08d5f6740431
X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600074)(711020)(4608076)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:BN1PR08MB155;
X-Microsoft-Exchange-Diagnostics: 1; BN1PR08MB155; 3:aeXWLM4OFESghuuyozDFiDpNkLLuCphnU5efSkHYphYBx9y5nZKCo4JxBa2vMwWzV8ALBiTymGG1zO+wxouSqPrt+ib09Zlp75d4uC4liNXPEv+N6mN2kCxx0W6g2oj7gzwaG/+pF+ZHW057DYxKNQqhVoAKVITLwRMzdQ9jbFNNVRzY0LTeMZRm/oomS8cdYgEZOabpT0JkGIT6BcO2DvDYFzRKICldwO6xNAMEaAuf+36YbeJu1PMN0dpPZKGiATc2iDjhI2eoSwL5ZCz74A5YVxzIS4gYkRiXoFWr0jOgfMGstwfEh8tIuXFUXJppHAnHxO0mnmF7zMqHYdJzIpIr+8KRqNz6RHq/i83YL9g=; 25:i9M32Roj1D1XIcKOnaH0tCoLeUz5OGaTpLRjLKvztKgezGCu2o77HFgVMV1yQBYdn8OX4gYOyAEAAsttb52v301hGvjLvRI9pONCNERIcmt2TgkiOcluSc2CiHp9hmuWvOJk+TeDR0B/ExOqdnCXhXheDG2r7Zlgo/evF7C+i0OVQUeY1phiXP380nUlPmurd2Tv6wqUcpOya8tNP3b2sJqX7x9X91Z/Mb3iKyrqk3t6qabyoY4stXWV7V+41iz5lME5WPpP0prJl//PM7TiM0Kizvnw3W85DT1OD43Nc+KWy7L7VoPUM5JKzsxOXOa2ZuA91BTPdj8mMjeST3LeKQ==
X-MS-TrafficTypeDiagnostic: BN1PR08MB155:
X-Microsoft-Exchange-Diagnostics: 1; BN1PR08MB155; 31:aL8lwwqYbI5BDwygqGWn61zsDSLYTvefW5VykVYpE6oMQPv2Q23QQDLXD6FhF+VibFuj+wGEqrDnq/tLXQy6WUDmhh9hX0ARfrTDqcU0+FYPfqINmauB84LET/cNkyc4SIelRLRFNpiSG5MO8tXm9q6knUunZc90a6YQCEaH/A+Zo+h7t6K8i1+pcGzPiKaWOoP44IPJww+RL1PjYwStGU0Y0PkynU2ws+UD+Wxu9kE=; 20:hAr3WS1cZsXFjTABEhQ0IQpk1Vr74CribTGEF2Li2CjiM/alWny+JkRAAradezFgxaISWloFzS2020d2l1Og1KyrRwqD8dqy6J1s9pmBIZ4M7bwIrv+mUCxSetxzEoIcYl48RI1LGJ2k8JTsEai2TFBJhEIldbWFAWBuZ6uR7LmTQEOESFGZtU5HYfVwOd8XHdcDk/hEldVUiTBo2w/n63C8UG06MaXS+hPdekdvVVlP7yixrBw/H+bot4h3QptnuMj/A+I43aPkMjAvD/f2R//IF4mNI24Y4iMRDgHfuTxLgwKjq6758XHqQ9omLtWcNoAruUoCV4D+9ohdrDbO6XzDru7LSiDw7+Q1wtVETGfpscyfdjOHIosOg5UWfGXAMnoqvdsJtCoAT0ML1SQnzr8unnNaqHWYqOxtpgnYxWb6jBZAdqiJTi31BCWpESWIE7OXKfNsWhmUqqzjvPX1krnQgxHQrfdyKoi8kFN/8a+6qiKia/glFHmTBlJGIGLr
X-Microsoft-Antispam-PRVS: <BN1PR08MB1556EE8DB26192D0E366E0BF62F0@BN1PR08MB155.namprd08.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(28532068793085)(158342451672863)(120809045254105)(21748063052155);
X-MS-Exchange-SenderADCheck: 1
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231311)(944501410)(52105095)(93006095)(93004095)(3002001)(10201501046)(149027)(150027)(6041310)(20161123558120)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:BN1PR08MB155; BCL:0; PCL:0; RULEID:; SRVR:BN1PR08MB155;
X-Microsoft-Exchange-Diagnostics: 1; BN1PR08MB155; 4:uOUmBMoeSoAYmT1dmvEHEetrIh/DYB/ZqQaZAz2p3efE1/omtitxnU8Gb+aA7AT8smuWfyzzAtT/fRBswkZO2it811OrF9M/nJVkZhx//U1AojENdniUehM2b9Y1cmIIyU2kzYkpNp5PQ4iq9Z5c2Rcf/FGiz/ICn0PmFaDKtt90rZw5CuefTLKG8Y0NlBiTzuLqn0X+zJCHltEEI0k+odM67HzSbvgIgH0+cVFKXEUYyAMZJWerpsi01JpGjLQBr23GjBmEKDlcRDDUj4TG8zRvFrDNT9Wm5q816kd7ZAmX6QcYfvYvpTFBuNKi0caUBwC/LiL9SoTuGCoJDg9Y7HRnEIMyYUo8EN1SnRyIPx7aephNIUku5KIk70zXPSmx23aEV5mLn1drcjVISZ/A6QueZRhFXUGsXaWvpZt+eCY=
X-Forefront-PRVS: 0749DC2CE6
X-Microsoft-Exchange-Diagnostics: 1; BN1PR08MB155; 23:TlQnOgscmbHL61cmp8p5qd148MitSOctWC1+YF947CX8l5mpOobaE6KT4V8SeWxf8AgiJkMc1tR0T9XfIhlL79t8DDjKesHzfC1bUwz3BvBJYKn5BDNFOrWaC+L7zrVr1iIK0J/CyXYtwp12oLu8M6VVVMcRyKWAe5GNmQVpHgifgjVo1NuQBrSvZPGSrf3mTxNdQWCSIfgOdayUP/O4hE+SOH5CjqT2/YkA0kdxjGxPKQwpPvObeYDMmIBCegrzN5WcGDDtsp42V4xVz9BX3eha1I1nVbA9lthy9eoCgTk35K9XQ9RqLexTa7n9afCY3yEahyX4UIsmstEuRURWadM7vp+aiP1R3Obr5Ki0qnXMXfcHmsF1TfjgAvbE0zEawcewVmcZiy5FwgbhjM+WAC8xqxLYq8zveYgXqtqY94LhiBo4pM+3/tMASTGIJRHcYscQME5bCfVUnVC+rtNf3JqVXV34ColQUMt3lGZliaxynB5UdXJKFD2OaDd7AWNEw79jX7AiUkbor08NGlw58i6kX3SnlyOWH26+11glpFzbGJXx+cSSrfdiVsqs+Am31wlSPfiEmm9gkaJ0tyy8MWN8G6BUSyYiMes9WlS8H74PhQSEzJhe7nrhDMPFv5TqFW5GcMyHwwUvoPcMl5Ih7WY9RAyNttwlyum02Bf2CGY6aE6aV++W0ns5BL3bbE2E4yfM37XAzVOh6ej5+b6Ln4lfRoq5A8L296esVzIMYBcJDc3nhltI5zuGYD6XunZGEQG/BZKaQL91Dv8dfJeemt8RrpSn3r7EH4A+fGSjXBUFEtDexGwblDmHC4RzoWZSCg8gzsFLjDZK6l5Qz5NeEu5YkaPMLAyfOdTWKh0FLjBWpJWSdc2Vb16TjkY+i3mvfXUvxxzcWeis91D17JoU6MFfD+Qv/K4n4WLltjsTopbuRL3nLJOLrS2KFl4WnxZf4EwhgBAxdGxqjvw3jsCAnkeC/9A+cTeekhUVI+SMInQvbpTvlAVR0CWhPmlYLLqreAk4P+i8hLNsioS/uu1D5hMsoav5wUVOGs6TWaaxwmCRPoYxUAgJqTeNnR+AXKtnpkxaDtQ/SW6mDoyzLOg4WvgZSoj/4Wzn8WAcEOgVsEgjCsnvTyYlHF8GGR8B+7TKY7/XQhiEEYALQZ+cxspqalkvn2BT2FQPGlRw0/0tKn6VFrLPNJdghTyXgEmTu2GBsAsW1lsXCf1G+eKoBN45rnlTqURFS1Hvqe3uVE0qU76fUjhjecc//+Te70F9GmuWXHVIlTbXeuQ8eAoe18WkrppYAJsjh5HBRSBOWkVs1A4dPPJfFJo4/TbdKxFsUc42+aoUPXpybyNAo7KCEAk9qQ==
X-Microsoft-Antispam-Message-Info: bODlYnpIRn3APTTo793Yv7olB0y8LWNn8my5UWkTLAZt08JvLoOOP+OR7kz5c6ojDzfewQNoldNtG3zeWrgqzG1XAAfDSRNHv8mWmO4G1J6jALVsSdocZ7Dj9B7mvWihHdaCo/cclOZiI3NqmK+GexCJTSzXis0ZYxPBfMEHi3ycdOziP/4YKCy2zT4LdGL+iGfXvth7BwZM+YL04Ns76xD9AXlxYaWSRHXIaCiXVcGCtJKNwgYi7SQXu+zqqHEPYsmh4wGm2JMntO0zomUz6pjncQop35OOHZmCVzQxQLfdhcTpfreCaMacVr73HywSAXnLR/ELvpqsxXc/6ce+f0tVe7kYhsnJ/6DnCeYx7/k=
X-Microsoft-Exchange-Diagnostics: 1; BN1PR08MB155; 6:tPEXmAGK9XFsPoONUIwm2jcEKdDJVAjHynbiyxTgLfICwQtDxsMZf2hoA9BNJWexbmwlkAKfOhTv1WnDmd7dewM9D1zckrf6FqFvvIGJaHi++ZIdp/AHnAvVOGtpV+Qbm96MMrsCU0xAYCI21TqCaM7izgpEJpwZ/9u+0/M0Q5JlCnDbblEDYIk9JVsFHhiR0EUZOXR52i7+XU6ajsFl6VNHz7q23VUeMUxBcb/kIY6r9p2beziehiVg8dKllAf6iiUyn2gaeyVtl8Xo9omn2kBszL84QvzRfLPUelynJhfPA9rxVeAUHIr1IVM5RgSR89bDHZPH3fPQZVmbVMKNsCM+r52EmcrgFxzZJT+nrwxielht7nbdvgbTktAIRRlsBxyB/lLzXD4/1G56g6h5YWSoH18k8c8enh46L3SLNbEliVy6ijPbul9i5KuBS1UEkXmf9e6qnMdEOgj0tg8R6w==; 5:6bfxflRya+WJEvbshoM9nYKj5ZmqUWbKSr5g/aSMfhkGftoYiTQPjxXxu0I8NiXwmyj3x3/zqApQPk/lAjXWVoTKDe6zP+yzgrGTlRdIaAUIaSBRbuR5FuLPVygHc0I1mPKB9ULB+GEkmF7ZkrE/f+wgPxMZbkMRNv5FXeKrONE=; 7:D/BwEmlLLuReWtkXAIA7ehK3BYPgDvSLIj4Q2PLqEKCjadjC6NndH2XW2tdij2KjdeSAfSjm364kkcM14hoyz2progZBC3VIh4f9YIzOADJzBFIATS5wQNyLouxIB1N0Pdazps83y/Id+++xJFCvcFBRDKvWOonEChMq5riGlvGM9kiabOOZHgYSGiiawkGbR+pbIT5HLNDBQrwe3Gio8niJxFwBnHxdrXCzQZv+bufGjnule4eRxeV6IOpRQCsO
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: aviatnet.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Jul 2018 23:27:28.5272 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 5ac2d3e5-8478-43af-c750-08d5f6740431
X-MS-Exchange-CrossTenant-Id: 8d7d22b9-3890-4eef-95a6-a226e64151be
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=8d7d22b9-3890-4eef-95a6-a226e64151be; Ip=[192.147.115.52]; Helo=[mail-send.aviatnet.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR08MB155
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/2CKTkBB1Dhjxgf9daT8_4YfAdJk>
Subject: [netmod] Fwd: Re: YANG schema mount - any early implementations?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.27
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, 30 Jul 2018 23:27:49 -0000

Hi everyone,

I just wanted to ask if it would be possible to clarify the intentions around some of the wording of the draft schema mount standard (Rev-10). In particular, regarding entries of the /schema-mounts/mount-points list.

My interpretation is that the intended use of the /schema-mounts/mount-points list entries are to specify the parent modules that contain a mount point. Following on from this, the client should use the YANG library instance to determine which schema options can be mounted at the root of a mount point. This seems consistent with the examples of Appendix A of the draft standard.

In this email I wanted to highlight the following sections of the draft RFC below. In my view they seem to me to be somewhat ambiguous, in implying that the mount-point list entries specify the *child* module (sub-schema):


>From https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/?include_text=1
Section 3.3 - Page 7
> The "/schema-mounts" container has the "mount-point" list as one of its children. Every entry of this list refers through its key to a mount point and specifies the mounted schema.

Section 3.3 - Page 8
> An entry of the "mount-point" list can specify the mounted schema in two different ways, "inline" or "shared-schema".


Section 9 - Page 13
> A mount point defines a place in the node hierarchy where other data models may be attached. A server that implements a module with a mount point populates the /schema-mounts/mount-point list with detailed information on which data models are mounted at each mount point.

Section 9 - Page 14
list mount-point {
    key "module label";
    description
    "Each entry of this list specifies a schema for a particular mount point.


The wording makes me wonder if these passages might actually just be "left-over" context from earlier revisions of the draft standard (Revision 8 and prior) -- effectively referring back to the schema-mount 'use-schema' list.


I do of course acknowledge that it is entirely possible that I've misinterpreted the wording of the passages above, however if that is the case, I suspect I may not be the only one in future.
Many thanks for your time on this matter.

Best regards,
Hayden







On 20/07/2018 8:09 PM, Juergen Schoenwaelder wrote:

On Wed, Jul 11, 2018 at 09:43:32AM +1200, hayden wrote:



I understand that the schema mount proposal is still effectively in a

state of flux, but are there any publicly visible implementations or

deployments of a NETCONF or RESTCONF server that those interested could

experiment with (e.g. to aid in client development)?



State of flux? It is past WG last call and IETF last call.



https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/history/



/js