Re: [netmod] moving forward with schema mount

Christian Hopps <chopps@chopps.org> Wed, 24 January 2018 12:37 UTC

Return-Path: <chopps@chopps.org>
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 55734120726 for <netmod@ietfa.amsl.com>; Wed, 24 Jan 2018 04:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.461
X-Spam-Level:
X-Spam-Status: No, score=-0.461 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BRBL_LASTEXT=1.449, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 KIYSyB6a-qjJ for <netmod@ietfa.amsl.com>; Wed, 24 Jan 2018 04:37:36 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id BDD54120227 for <netmod@ietf.org>; Wed, 24 Jan 2018 04:37:36 -0800 (PST)
Received: from dap.chopps.org (24-247-65-170.dhcp.trcy.mi.charter.com [24.247.65.170]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 20A9262A03; Wed, 24 Jan 2018 12:37:36 +0000 (UTC)
References: <BF9C1543-4471-4CB3-9A26-451F45A2E4B6@juniper.net>
User-agent: mu4e 1.0-alpha2; emacs 25.3.1
From: Christian Hopps <chopps@chopps.org>
To: Kent Watsen <kwatsen@juniper.net>
Cc: "netmod@ietf.org" <netmod@ietf.org>
In-reply-to: <BF9C1543-4471-4CB3-9A26-451F45A2E4B6@juniper.net>
Date: Wed, 24 Jan 2018 07:37:35 -0500
Message-ID: <87vafrl9f4.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/KRiSz-xKbRPBYBNPtKRRSJrUfDE>
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 12:37:38 -0000

Great news.

Thanks,
Chris.

Kent Watsen <kwatsen@juniper.net> writes:

> 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