Re: [netmod] [Netconf] Summary and AIs from IETF-100 meeting

Alexander Clemm <alexander.clemm@huawei.com> Tue, 28 November 2017 00:34 UTC

Return-Path: <alexander.clemm@huawei.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 40EDD129417; Mon, 27 Nov 2017 16:34:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 FJIrfKk5UqrW; Mon, 27 Nov 2017 16:34:25 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 24757128AA1; Mon, 27 Nov 2017 16:34:25 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 0B1CB9ED4CA6F; Tue, 28 Nov 2017 00:34:21 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 28 Nov 2017 00:34:22 +0000
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.83]) by SJCEML701-CHM.china.huawei.com ([169.254.3.207]) with mapi id 14.03.0361.001; Mon, 27 Nov 2017 16:34:15 -0800
From: Alexander Clemm <alexander.clemm@huawei.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, netconf <netconf@ietf.org>
CC: Jeff Tantsura <jefftant.ietf@gmail.com>, Yingzhen Qu <yingzhen.qu@huawei.com>, Lou Berger <lberger@labn.net>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [Netconf] Summary and AIs from IETF-100 meeting
Thread-Index: AQHTZ9dUHhA1I7Z67kivQ2HOm7SmNqMo7B7Q
Date: Tue, 28 Nov 2017 00:34:15 +0000
Message-ID: <644DA50AFA8C314EA9BDDAC83BD38A2E0EACED10@sjceml521-mbx.china.huawei.com>
References: <4686C139-D0B5-4308-A1B5-2689992B8265@gmail.com>
In-Reply-To: <4686C139-D0B5-4308-A1B5-2689992B8265@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.209.217.14]
Content-Type: multipart/alternative; boundary="_000_644DA50AFA8C314EA9BDDAC83BD38A2E0EACED10sjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/8iFC4BxZNuoISKnI4mMvH6lfhRc>
Subject: Re: [netmod] [Netconf] Summary and AIs from IETF-100 meeting
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, 28 Nov 2017 00:34:27 -0000

Hi,

One other action / question concerns WG adoption of draft-clemm-netconf-nmda-diff-01<https://datatracker.ietf.org/doc/draft-clemm-netconf-nmda-diff/> (Discrepancy detection between NMDA datastores).
The draft received considerable support when the question was asked in the room, but one question that was asked concerns whether this should be in Netconf or perhaps in Netmod instead.  Hence, cc'ing Lou and netmod.

The reason we put this into Netconf concerns the fact that this really defines an RPC, i.e. operations to facilitate interacting with NMDA-compliant servers.  It complements the RESTCONF and NETCONF operations, and the NMDA-extensions to those are also placed in the Netconf WG.  This seemed like another natural extension.  The draft does not really define a traditional YANG data model per se that would be used to manage something, therefore it simply did not occur to us to place it into Netmod, although I can see how one might make a case for that as well.

So, from our (coauthors) perspective, for the stated reasons, perhaps slight preference for Netconf, but really either one (Netconf or Netmod) is fine.  One thing we would not want to do is slow this effort down; since this was presented in Netconf, not in Netmod, if we were moved into Netmod it would hopefully not mean having to go back to square 1.

Thoughts?
--- Alex


From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Mahesh Jethanandani
Sent: Monday, November 27, 2017 3:27 PM
To: netconf <netconf@ietf.org>
Subject: [Netconf] Summary and AIs from IETF-100 meeting

Dear NETCONF WG,

Below is the NETCONF WG session summary and AIs that were taken from the IETF 100 meeting.

This e-mail verifies the discussion that took place in the room. Barring any strong objection, the AIs identified in this summary will be acted upon.

The NETCONF session took place on Thursday, November 16, 2017, between 15:50-17:50 Singapore Time.

The final notes from the meeting (once posted) will be available at:
https://datatracker.ietf.org/doc/minutes-99-netconf/<https://datatracker.ietf.org/doc/minutes-100-netconf/>


  *   rfc6536bis received comments in IESG review. Some last minute updates are being provided to address those comments, and once approved will allow the document to go towards publication. AI for authors to post updated draft before Benoit submits it for publication.
  *   NMDA drafts (YANG Library, NETCONF and RESTCONF) need updates to support features like licensing, and semantic versioning. It also needs to address some bugs. Authors believe the document should be ready for WGLC by end of this year. AI for authors to provide updated draft before the three set of drafts are submitted for LC.
  *   Zerotouch draft went through LC. It received comments during that period, which the author will address. Author believes that once the document is ready, it can be forwarded for publication, currently planned for December. AI for author to provide updated draft.
  *   Keystore draft needs to be updated for issues raised in WGLC and discussion on the mailing list. AI for author(s) to provide updated drafts before LC can be re-initiated.
  *   SSH/TLS NETCONF/RESTCONF Client Server Models also needs updates based on changes in the Keystore draft.  AI for author(s) to provide updated drafts before LC will be re-initated.
  *   YANG Push, Subscribed notifications and NETCONF notification drafts need updates based on discussion in the meeting and on the list. There are still outstanding questions on whether NETCONF notifications draft is needed or its contents can be folded into subscribed-notifications draft.  All these issues need to be discussed and resolved on the mailing list. Co-chairs will initiate WGLC once the issues are resolved. AI for authors to close on open issues and post updated draft.
  *   Notification Message Headers and Bundles and Restconf notifications - These two drafts will be considered for WGLC later. No AI.
  *   UDP Pub Channel draft needs more discussion on the mailing list. A milestone will be added to the NETCONF WG milestones. No other AI planned at this time.
Cheers

Mahesh (and Kent)