[netmod] Differentiating the types of Mount

"Eric Voit (evoit)" <evoit@cisco.com> Wed, 16 March 2016 03:59 UTC

Return-Path: <evoit@cisco.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 561DB12D810 for <netmod@ietfa.amsl.com>; Tue, 15 Mar 2016 20:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 k60cxkY4RVs8 for <netmod@ietfa.amsl.com>; Tue, 15 Mar 2016 20:59:54 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 274B212D7D2 for <netmod@ietf.org>; Tue, 15 Mar 2016 20:59:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2145; q=dns/txt; s=iport; t=1458100794; x=1459310394; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=5UlK2GkzhrzZzlIArKuoorUkp96XrCvqMIyg0ZLaUUc=; b=OxBqvRhyMrXYp4OQSwAKKwzsnXujl2REZly37umCcSl+eHpHK4dPf5HQ IKf8aWx6Glxh1KhqatKo+noVZtZEKNcK+ShN2bBLdF1J0UwC68eX5hhV6 efAXOqhafy+zA4jytK/SVp+8oQ9NRrWuRzSvPjw5ibF7yzfHw8DbkSTjd A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CmBACP2ehW/xbLJq1ehQ68F4gaAQEBAQEBZSeESIELAYEAJgEEARqIH78EAQEBBwEBAQEchhqNNwWHYIYSiV0BjXmPDI5+AWKDZYoUJRZ+AQEB
X-IronPort-AV: E=Sophos;i="5.24,342,1454976000"; d="scan'208";a="634474440"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Mar 2016 03:59:52 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u2G3xpwb008868 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 16 Mar 2016 03:59:51 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 15 Mar 2016 23:59:50 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1104.009; Tue, 15 Mar 2016 23:59:50 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "netmod@ietf.org" <netmod@ietf.org>, "Martin Bjorklund (mbjorklu)" <mbjorklu@cisco.com>, Lou Berger <lberger@labn.net>, "lhotka@nic.cz" <lhotka@nic.cz>, "Acee Lindem (acee)" <acee@cisco.com>, "Alexander Clemm (alex)" <alex@cisco.com>, "Ambika Prasad Tripathy (ambtripa)" <ambtripa@cisco.com>
Thread-Topic: Differentiating the types of Mount
Thread-Index: AdF/OD2NJ3Cq4cCSQLyujReGzdHIoQ==
Date: Wed, 16 Mar 2016 03:59:50 +0000
Message-ID: <84d0c3c5331c4b5e9d0883f890a87a40@XCH-RTP-013.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.231]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/vtWQrDRZu_voiogCFW3EBya8CGQ>
Subject: [netmod] Differentiating the types of 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: Wed, 16 Mar 2016 03:59:56 -0000

To help differentiate between concepts and drafts, below are strawman definitions for the various types of Mount which we have been discussing over the last year in Netmod.   Thoughts/suggestions?

YANG Mount
----------------  
Definition: An abstracted term for a mechanism that a parent YANG model can use to link in YANG information defined or located elsewhere.  
Purpose: Provides model flexibility by enabling the growth of YANG trees via an explicit reference to other YANG information and structures. 

Schema Mount
-------------------
Definition: A type of YANG Mount where a new YANG Schema is constructed by inserting any existing YANG schema under a parent model within a local datastore.   Objects populated into the mounted schema are only instantiated as part of the parent's hierarchy.  
Purpose: This allows reuse of existing model definitions to facilitate implementation of alternative model structures in multiple contexts.  In effect, it allows to define models which reuse other model definitions as if they had been defined as a special kind of grouping.  

Alias Mount
---------------
Definition: A type of YANG Mount which allows to provide an alternative path to local objects of YANG data.  
Purpose: Enables multiple concurrent context specific object models without replicating instance data.  This allows programmers access common objects via the hierarchies that best make sense to them. (E.g. Symbolic link in a file system.)

Peer Mount
--------------
Definition: A type of YANG Mount which enables access to remote objects as if they were contained within a local datastore dynamically.
Purpose: Provides an on-demand virtual federated datastore that provides visibility and location transparency of YANG-data across device boundaries.  Retains clear authoritative ownership.  Eliminates many tasks otherwise needed to synchronize, reconcile aggregate, validate information replicated across these devices. (E.g. File share to remote host in a file system.)

Thanks, 
Eric