Re: [netmod] moving forward with schema mount

Lou Berger <lberger@labn.net> Wed, 24 January 2018 15:42 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 200F0126CD6 for <netmod@ietfa.amsl.com>; Wed, 24 Jan 2018 07:42:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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 DT-0I0kFoZPG for <netmod@ietfa.amsl.com>; Wed, 24 Jan 2018 07:42:32 -0800 (PST)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) (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 A6138126C3D for <netmod@ietf.org>; Wed, 24 Jan 2018 07:42:30 -0800 (PST)
Received: from CMOut01 (unknown [10.0.90.82]) by gproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id DDFE54186E for <netmod@ietf.org>; Wed, 24 Jan 2018 08:20:12 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id 2FL81x01P2SSUrH01FLB6G; Wed, 24 Jan 2018 08:20:12 -0700
X-Authority-Analysis: v=2.2 cv=Rf/gMxlv c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=RgaUWeydRksA:10 a=Scm6ppW0Vsq7PnY0iGgA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: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=lKtFt5O3z5UtzHhGjKdliqymD6yA7cCsCmutmHFtP68=; b=uXLaKM3Jwh40b+7rPb3EIHih+S TDpTCZuIZg2H73nO2JLAdTdx1IaG8LkQDVWr6TBP1TL43akCtymFvlVygX8GIX+ByVbYP82R2ByNx ILAlSaco1mOCUHeOrIDJ+WxE5;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:60938 helo=fs2.dc.labn.net) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_1) (envelope-from <lberger@labn.net>) id 1eeMqO-000ybh-Nu; Wed, 24 Jan 2018 08:20:08 -0700
To: Kent Watsen <kwatsen@juniper.net>, "netmod@ietf.org" <netmod@ietf.org>
References: <BF9C1543-4471-4CB3-9A26-451F45A2E4B6@juniper.net> <20180123202610.vhclqrsfshevtbj3@elstar.local>
From: Lou Berger <lberger@labn.net>
Message-ID: <87b0d5ed-52d9-7bb2-e83b-89241baa35bc@labn.net>
Date: Wed, 24 Jan 2018 10:20:07 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <20180123202610.vhclqrsfshevtbj3@elstar.local>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
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.86.101
X-Exim-ID: 1eeMqO-000ybh-Nu
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net (fs2.dc.labn.net) [100.15.86.101]:60938
X-Source-Auth: lberger@labn.net
X-Email-Count: 3
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/lgcifeCF8IbIHRw1Y-dB_xp5jh8>
Subject: Re: [netmod] moving forward with schema mount
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: Wed, 24 Jan 2018 15:42:36 -0000

On 01/23/2018 03:26 PM, Juergen Schoenwaelder wrote:
> On Mon, Jan 22, 2018 at 08:05:54PM +0000, Kent Watsen wrote:
>>
>> Thank you all for the important discussion since the completion of WGLC on Nov 6th.
>>
>> Per normal process, drafts typically progress once LC comments are address unless significant faults are found.  Post LC comments have been made, which needed consideration, notably the relationship with NMDA and rfc7895bis and an alternate representation of inline schema.  These have been considered respecting their impact on the last call consensus and it is the position of the chairs that it is best to advance the existing schema-mount document at this time.
>>
> 
> If we take the formal road, then you may want to read again Robert
> Wilton's email posted on November 2nd (Thu, 2 Nov 2017 17:06:34 +0000)
> again. He does talk about YANG library alignment - so YANG library
> alignment is not just post LC comments. (I personally prefer to have
> technical discussion than formal discussions but if it is necessary to
> g there...)

Focusing a moment on the future and the technical, it would be most
helpful to have a document that describes SM with NMDA and YL-bis.  This
would at least be a starting point for WG discussion.  It might even
help show if the current plan is flawed.

I, personally, suspect that a proposal that changes basic approach, or
revisits past arguments, will end up in another round of very long
discussions based on what each party thinks is optimal. Therefore, I
hope that the initial proposed solution would take a minimalistic change
approach in order to garner widest support.  This consensus foundation
could then provide a foundation for further optimization to the degree
supported by WG consensus.

Lou


> 
> /js
>