[netmod] explicit mount

Martin Bjorklund <mbj@tail-f.com> Tue, 23 February 2016 15:08 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2021B315E for <netmod@ietfa.amsl.com>; Tue, 23 Feb 2016 07:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham
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 4TaK8Sbvmsrl for <netmod@ietfa.amsl.com>; Tue, 23 Feb 2016 07:08:04 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 264551B3156 for <netmod@ietf.org>; Tue, 23 Feb 2016 07:08:04 -0800 (PST)
Received: from localhost (unknown [173.38.220.38]) by mail.tail-f.com (Postfix) with ESMTPSA id 1FE751AE035B for <netmod@ietf.org>; Tue, 23 Feb 2016 16:08:02 +0100 (CET)
Date: Tue, 23 Feb 2016 16:08:06 +0100
Message-Id: <20160223.160806.696185201696745163.mbj@tail-f.com>
To: netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/FM2bbR4we2Sljms8dI-y74x-N00>
Subject: [netmod] explicit mount
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 23 Feb 2016 15:08:05 -0000

Hi,

In yesterday's meeting, Lou (I think?) mentioned a use case for mount
that is not documented in draft-rtgyangdt-rtgwg-device-model; the need
for being able to specify modules to mount directly in the schema.
Something like this:

  container root {
    ymnt:mount-point "lne" {
      ymnt:mount-module "ietf-interfaces";
    }
  }

It would be useful if the use case for this could be described in more
details.  Is it a requirement to be able to specify this in the
schema, or could it be done (as Chris mentioned) in the RFC text?

The reason I ask is that it is probably not as simple as the example
above.  First, you probably need to specify a revision of the module
to be mounted.  Or a min-revision.  Then probably a set of features
that must be enabled.  And so on.  It turns out that there is already
a proposal for specifying such a "conformance profile" - YANG Packages
(see draft-bierman-netmod-yang-package).  Maybe it would be better to
re-use packages?


/martin