Re: [netmod] moving forward with schema mount

Martin Bjorklund <mbj@tail-f.com> Tue, 23 January 2018 08:24 UTC

Return-Path: <mbj@tail-f.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 3BD931243FE for <netmod@ietfa.amsl.com>; Tue, 23 Jan 2018 00:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 aoZ6hmn1hX7Y for <netmod@ietfa.amsl.com>; Tue, 23 Jan 2018 00:24:27 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 36CD0120726 for <netmod@ietf.org>; Tue, 23 Jan 2018 00:24:27 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 1B3771AE02BE; Tue, 23 Jan 2018 09:24:26 +0100 (CET)
Date: Tue, 23 Jan 2018 09:24:25 +0100
Message-Id: <20180123.092425.1788188537428313683.mbj@tail-f.com>
To: kwatsen@juniper.net
Cc: netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <BF9C1543-4471-4CB3-9A26-451F45A2E4B6@juniper.net>
References: <BF9C1543-4471-4CB3-9A26-451F45A2E4B6@juniper.net>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/QfPP4G6fI6_tZtZBENIRh2L7oX8>
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: Tue, 23 Jan 2018 08:24:29 -0000

Hi,

So do you believe that this decision reflects rough consensus in the
WG?

I hope that the document writeup will show that the WG is divided on
this issue.

For the record, if this means that using Schema Mount *with* NMDA gets
delayed, I strongly object to this decision.

Assuming this document now moves forward as-is, can we assume that we
can start to work on the bis document immediately?  What is needed?

  1.  a new individual draft
  2.  some time until this becomes WG draft
  3.  some time before WGLC

Do we have to go through all these steps?

This new draft would immediately obsolete the current SM document,
right?  And it would mark the current SM YANG nodes as deprecated.

Maybe we can send both the original document and the bis document to
the IESG at the same time ;-)


/martin


Kent Watsen <kwatsen@juniper.net> 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.
> 
> Given that there are significant concerns for how the solution proposed in this draft operates with NMDA, we do think it reasonable to add an applicability statement to the draft that covers its operation in NMDA implementations. We do not believe that such a statement substantively alters the draft nor would it impact drafts that normatively reference the current draft.
> 
> In addition to resolving the remaining open thread [1], we also agree with the recently made comment that the schema mount draft should allow the use of rfc7895bis (i.e., not reference /modules-state), thereby enabling the draft's use (though not ideal) on servers supporting rfc7895bis.
> 
> The chairs will propose specific text for the updates mentioned in this message to be reviewed by the WG for correctness before final submission and advancement. 
> 
> [1] https://www.ietf.org/mail-archive/web/netmod/current/msg20049.html
> 
> Thanks,
> Kent, Lou, and Joel
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>