Re: [netmod] WG adoption poll

Qin Wu <> Tue, 09 October 2018 06:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6D0A113118E; Mon, 8 Oct 2018 23:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YoHK-8K80cNU; Mon, 8 Oct 2018 23:28:19 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E0FA4131182; Mon, 8 Oct 2018 23:28:18 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 842177E8B50BF; Tue, 9 Oct 2018 07:28:15 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 9 Oct 2018 07:28:17 +0100
Received: from ([]) by ([]) with mapi id 14.03.0399.000; Tue, 9 Oct 2018 14:28:11 +0800
From: Qin Wu <>
To: Lou Berger <>, NetMod WG <>
CC: NetMod WG Chairs <>
Thread-Topic: [netmod] WG adoption poll
Thread-Index: AQHUXvuM8WyuPeMdx0Op1BtzAOO3WqUWcKWg
Date: Tue, 09 Oct 2018 06:28:10 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] WG adoption poll
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 09 Oct 2018 06:28:22 -0000

Support adoption of this draft, 
Two quick comments on this draft
1. section 2.5 factory default setting
I would suggest to reference to draft-wu-netconf-restconf-factory-restore in section 2.5.
I think this draft is complementary to draft-wu-netconf-restconf-factory-restore-02, factory datastore can rely on yang instance data file to specify the content of factory datastore.
2. section 2.3 server capability
Server capability in the context of this draft is referred to a set of models and features which can be retrieved from yang library, I see server capability as NETCONF capability. 
I am wondering whether yang data instance file can also be used to specify capability identifiers. Some time I have trouble to understand where the server to get capability 
identifier and exchange it in the hello message.
I understand RFC6470 can advertise the capability change.

发件人: netmod [] 代表 Lou Berger
发送时间: 2018年10月8日 19:39
收件人: NetMod WG
抄送: NetMod WG Chairs
主题: [netmod] WG adoption poll


This is start of a two week poll on making
draft-lengyel-netmod-yang-instance-data-04 a working group document. Please send email to the list indicating "yes/support" or "no/do not support".  If indicating no, please state your reservations with the document.  If yes, please also feel free to provide comments you'd like to see addressed once the document is a WG document.

The poll ends Oct 22.


Lou (and co-chairs)

netmod mailing list