Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-05.txt

Lou Berger <lberger@labn.net> Thu, 18 May 2017 12:22 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 C1AA4129C34 for <netmod@ietfa.amsl.com>; Thu, 18 May 2017 05:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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 pQcL-cJ4S1qL for <netmod@ietfa.amsl.com>; Thu, 18 May 2017 05:22:28 -0700 (PDT)
Received: from outbound-ss-1812.hostmonster.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) (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 46106129C59 for <netmod@ietf.org>; Thu, 18 May 2017 05:17:29 -0700 (PDT)
Received: from cmgw4 (cmgw5 [10.0.90.85]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id 13DA7176068 for <netmod@ietf.org>; Thu, 18 May 2017 06:17:28 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id MoHQ1v0072SSUrH01oHTAF; Thu, 18 May 2017 06:17:28 -0600
X-Authority-Analysis: v=2.2 cv=QdwWhoTv c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=xqWC_Br6kY4A:10 a=tJ8p9aeEuA8A:10 a=r77TgQKjGQsHNAKrUKIA:9 a=8NcDGvkTCyg4cpWR7GkA:9 a=pILNOxqGKmIA:10 a=u07AKapRAAAA:8 a=jcSiR2zVKJmlRU7KT50A:9 a=u7xDNrcMcA4Ze7kp:21 a=_W_S_7VecoQA:10 a=SkebfZ6J2Mmvk2rLHZle:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc: References:To:Subject:Sender:Reply-To:Content-Transfer-Encoding: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=E3E7W9D2hYwTP7QQVSoRyuTYimnUJ2Vys8wduC9wplo=; b=VZ2QxDHCABPO8lywC09UP1mK6Y YANkvFe2nFlMtIBNlpHcgK4Rv/VMROrfs9Xxsvr5STMScHuqEcisp/0FeBAzQiFHRzmxMqgCllcQ0 tuZV2JU18nzQlnV72inovWi5h;
Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:38578 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1dBKMu-0007Aq-2g; Thu, 18 May 2017 06:17:24 -0600
To: Martin Bjorklund <mbj@tail-f.com>, andy@yumaworks.com
References: <149493700012.11951.17167734464796184887@ietfa.amsl.com> <20170516.142434.78646315149686396.mbj@tail-f.com> <CABCOCHSBp3v29k2S9HthUVx4GRBnYm4apeuXB6XrZBqeD1s0xQ@mail.gmail.com> <20170517.094657.1191825685767676391.mbj@tail-f.com>
Cc: netmod@ietf.org
From: Lou Berger <lberger@labn.net>
Message-ID: <6ffcbc1a-3715-01de-361f-318f17aaddce@labn.net>
Date: Thu, 18 May 2017 08:17:18 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170517.094657.1191825685767676391.mbj@tail-f.com>
Content-Type: multipart/alternative; boundary="------------05E8B5B5D1F4194EF591AB41"
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.84.20
X-Exim-ID: 1dBKMu-0007Aq-2g
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:38578
X-Source-Auth: lberger@labn.net
X-Email-Count: 6
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/KyXrhrcRwDnmYLZjosR90P8zh9Q>
Subject: Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-05.txt
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: Thu, 18 May 2017 12:22:30 -0000


On 5/17/2017 3:46 AM, Martin Bjorklund wrote:
>> Also open issue B.3 says design time mounts are not supported yet but
>> sec 1 (Intro) says they are out of scope:
>>
>>    The schema mount mechanism defined in this document provides support
>>    only for the latter two cases because design-time definition of the
>>    mounted schema doesn't play well with the existing YANG modularity
>>    mechanisms.  For example, it would be impossible to augment the
>>    mounted data model.
>>
>>
>> I agree with sec 1. Leave them out of scope.
> I also agree.  This is open until we have WG consensus.

(As contributor)
I'm fine with leaving such support out of scope for this document, but
disagree with the text.  How about just keeping it simple and say:

  The schema mount mechanism defined in this document provides support
   only for the latter two cases, i.e., design-time mounts are not specified by this document.

Lou