Re: [netconf] WGLC: draft-ietf-netconf-notification-capabilities-11

"Rob Wilton (rwilton)" <rwilton@cisco.com> Mon, 09 March 2020 18:33 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4713B3A156C; Mon, 9 Mar 2020 11:33:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=mQB4HYzx; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Yu5usHe0
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 Goo6sCeyHcdq; Mon, 9 Mar 2020 11:33:39 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7E3A3A152F; Mon, 9 Mar 2020 11:33:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8474; q=dns/txt; s=iport; t=1583778819; x=1584988419; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=m0C0ZS9VxbB/R/15OQJZ9wdQ655saOCFM2f6WfNFBAQ=; b=mQB4HYzxJHdGOXYRRHe7DupHM4L2yS5M5+cf1dTHrXayE5mSJGGQSDl+ 1slH8HyRpHyVpnkm8Azq+KMADxGHkvsgAn1BEbQ0YdMD7Qv2K31bGSiHw 6thyCfcXUt8c6S7hBAR7n7MkSBm3i3m7Pl7QkctTboyZqxJ3U25xpZEzQ o=;
IronPort-PHdr: =?us-ascii?q?9a23=3A4Z2/2hUMILNsAkSN5cfVz7QgIxHV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSA92J8OpK3uzRta2oGXcN55qMqjgjSNRNTF?= =?us-ascii?q?dE7KdehAk8GIiAAEz/IuTtankgA8VGSFhj13q6KkNSXs35Yg6arw=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DoAQAKi2Ze/5tdJa1mGwEBAQEBAQE?= =?us-ascii?q?FAQEBEQEBAwMBAQGBe4FUUAVsWCAECyqHWwOKbYJfmBWBQoEQA1QJAQEBDAE?= =?us-ascii?q?BGAsKAgQBAYFPgi9FAoIOJDgTAgMBAQsBAQUBAQECAQUEbYVWDIVjAQEBAQM?= =?us-ascii?q?BARAVGQEBKgIIAQIBCwQCAQgRBAEBAQ0hJwsdCAIEAQ0FCBqDBYJKAy4BDp4?= =?us-ascii?q?nAoE5iGKBdDOCfwEBBYUIGIIMAwaBOIwsGoFBP4ERR4JNPoJkAQEDgSgiGoN?= =?us-ascii?q?BgiyWfmWYRQqCPIdSjzCCSYghBY5fgWeOdoh8klUCBAIEBQIOAQEFgWkiKoE?= =?us-ascii?q?ucBUaIYJsUBgNV4Vqh1yDc4UUhUF0gSmNZQEB?=
X-IronPort-AV: E=Sophos;i="5.70,534,1574121600"; d="scan'208";a="649367832"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Mar 2020 18:33:38 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 029IXcU0010259 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Mar 2020 18:33:38 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Mar 2020 13:33:38 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Mar 2020 13:33:37 -0500
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 9 Mar 2020 13:33:37 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; =?utf-8?q?b=3DHVyze16GH69VHy7jn56LyF4cCkyZN/HgtcA4k75anKI1aIfIIUvCtjUOv8by0?= =?utf-8?q?FLNHilHkvzk6+QCLRWXrPQ/9k7espY+/v01nKHc2Q8cnFRFTVCq3/WBKxdG8+reFx?= =?utf-8?q?DqqcrI7ZKNFyezgcbFguSPQE2vsa6hkrnn8bC7KSvYaJPbl4RFgOedGVMZULHbpux?= =?utf-8?q?e/yiNwwFLxh6IXEH0VUXLhY+HCVYFGsjAIXtKDbvIiakx2wKUEIUZ4RHQtrIp4sxR?= =?utf-8?q?GI814RAtNwXCx5GslomAOeIlCh+WPa+ktizTGIk6gLxmN085J4/zeqlWoQkEI78sY?= =?utf-8?q?4oGQWR48sptYVZgqtBu/g=3D=3D?=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; =?utf-8?q?h=3DFrom=3ADate=3ASubject=3AMessage-ID=3ACont?= =?utf-8?q?ent-Type=3AMIME-Version=3AX-MS-Exchange-SenderADCheck=3B?= =?utf-8?q?bh=3Db9y7lhQTeKZxNvrPRwUDlRR5aDyAr3dR5HS/E6aE5tE=3D=3B_b=3DRFUzNv?= =?utf-8?q?BHA9RB22WwwkYzXJcG2Vsl5K0G250kKa/JrNGL6UYWG51HWU2+dLG8+uZ3QxIFUpQ?= =?utf-8?q?k5155Cpy5CNcTep8UAdsc+gl5STFO05FQFNyXJE/zxGR+w8BdbzsDvu0efHzQ8UxK?= =?utf-8?q?d7Rd2s4+rxs/YJwos8TE5isAuAsS5DHyhD3SQp14L7aeu85ho0WJxpunfgHf3yr4b?= =?utf-8?q?FnrXzdfHSH/eVG173ekmL+zXPsJ7Cs17S2ZWrU9VGT5L6ckEUY1UWkSQm0ZEugu3a?= =?utf-8?q?TYR6GhQvszkKwKnzJDL1AnbQSvqVNrRAJDH67MFI8vFiishs0Q0JjFd7zQhRKepyZ?= =?utf-8?q?MYiSg6U5FbQ=3D=3D?=
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; =?utf-8?q?h=3DFrom=3ADate=3ASubject=3AM?= =?utf-8?q?essage-ID=3AContent-Type=3AMIME-Version=3AX-MS-Exchange-SenderADC?= =?utf-8?q?heck=3B_bh=3Db9y7lhQTeKZxNvrPRwUDlRR5aDyAr3dR5HS/E6aE5tE=3D=3B_b?= =?utf-8?q?=3DYu5usHe0XAWva8mrrukN9A9lt4OAZVeocxpG0Iw+nqCvgX7k7d8D2Pb8rUF6bR?= =?utf-8?q?m/rNVDKRFFaGZHY7QW3FwLW04afUNHAqt7su4+9LdbHTnrLHraV94b5qIUYzQRK+m?= =?utf-8?q?Cn+VH6z9v7my1HF1rYJ3xDfL0qSRM8lLX6oEH0vnR0kA=3D?=
Received: from BY5PR11MB4355.namprd11.prod.outlook.com (2603:10b6:a03:1c3::13) by BY5PR11MB4419.namprd11.prod.outlook.com (2603:10b6:a03:1c8::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17; Mon, 9 Mar 2020 18:33:36 +0000
Received: from BY5PR11MB4355.namprd11.prod.outlook.com ([fe80::5434:7127:ff4b:e6f4]) by BY5PR11MB4355.namprd11.prod.outlook.com ([fe80::5434:7127:ff4b:e6f4%4]) with mapi id 15.20.2793.013; Mon, 9 Mar 2020 18:33:36 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: "netconf@ietf.org" <netconf@ietf.org>, =?iso-8859-1?Q?Bal=E1zs_Lengyel?= <balazs.lengyel@ericsson.com>, "draft-ietf-netconf-notification-capabilities@ietf.org" <draft-ietf-netconf-notification-capabilities@ietf.org>
Thread-Topic: [netconf] WGLC: draft-ietf-netconf-notification-capabilities-11
Thread-Index: AQHV5fT97GQMgsC5TEuE1GmMKTxx36ggKT0AgBjpugCAB5/HwA==
Date: Mon, 9 Mar 2020 18:33:36 +0000
Message-ID: =?utf-8?q?=3CBY5PR11MB43554B2EDF3D395D2680D9C1B5FE0=40BY5PR11MB4?= =?utf-8?q?355=2Enamprd11=2Eprod=2Eoutlook=2Ecom=3E?=
References: =?utf-8?q?=3C0100017055c347e5-13b624a9-04c0-4ba5-8a53-26a80f0796?= =?utf-8?q?07-000000=40email=2Eamazonses=2Ecom=3E_=3C0100017055e833dd-1a2eca?= =?utf-8?q?c4-53e4-4bb7-aab9-f75516c5fd38-000000=40email=2Eamazonses=2Ecom?= =?utf-8?q?=3E_=3C01000170a78abdde-66112ceb-d466-4c72-ad18-6058ef07ab02-0000?= =?utf-8?q?00=40email=2Eamazonses=2Ecom=3E?=
In-Reply-To: =?utf-8?q?=3C01000170a78abdde-66112ceb-d466-4c72-ad18-6058ef07a?= =?utf-8?q?b02-000000=40email=2Eamazonses=2Ecom=3E?=
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [2001:420:c0c0:1002::af]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bfeec108-a9fc-443f-8c6e-08d7c4586149
x-ms-traffictypediagnostic: BY5PR11MB4419:
x-microsoft-antispam-prvs: =?utf-8?q?=3CBY5PR11MB44193713A39504CDF29C529BB5F?= =?utf-8?q?E0=40BY5PR11MB4419=2Enamprd11=2Eprod=2Eoutlook=2Ecom=3E?=
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0337AFFE9A
x-forefront-antispam-report: SFV:NSPM; =?utf-8?q?SFS=3A=2810009020=29=284636?= =?utf-8?b?MDA5KSgxMzYwMDMpKDM5NjAwMykoMzc2MDAyKSgzNDYwMDIpKDM2NjAwNCkoMzk4?= =?utf-8?q?60400002=29=28189003=29=28199004=29=2876116006=29=2886362001=29?= =?utf-8?q?=28478600001=29=2866446008=29=2864756008=29=2815650500001=29=2866?= =?utf-8?q?476007=29=2866556008=29=2866946007=29=28110136005=29=285660300002?= =?utf-8?b?KSg1MjUzNjAxNCkoODkzNjAwMikoODExNjYwMDYpKDgxMTU2MDE0KSg4Njc2?= =?utf-8?b?MDAyKSgyOTA2MDAyKSgzMzY1NjAwMikoOTY4NjAwMykoNjUwNjAwNykoNTM1?= =?utf-8?b?NDYwMTEpKDc2OTYwMDUpKDE4NjAwMykoNTUwMTYwMDIpKDQzMjYwMDgpKDMx?= =?utf-8?q?6002=29=28966005=29=2871200400001=29=3B?= DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB4419; H:BY5PR11MB4355.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: =?utf-8?q?wpdrrIOgyfwCmEQ2Rr00veiFTK/jgDY?= =?utf-8?q?HcMyyeThV7TO0eLakzWbo3D6ivKbvmyrAD0FDG4aoWQneFKURNiPQ3yZM3B4defpH?= =?utf-8?q?XJZNePIaA4GEAZvwQAXqGgVzFOA6Y2fx0HV9KkHHmscXNbpiigkmyomXc94ia4hTE?= =?utf-8?q?9ohn6A/axmJT8qSrXtQb8bpFTm5+oF+6xDMyzSI5hqFjsegA4+BG2hL+zdtF/M6+V?= =?utf-8?q?EtgsanqMwMLONmZHD/aOZCswl7YmADbDeRbbIPlE0VdXyxs/rZU+tJbl8xKJag2Ad?= =?utf-8?q?RK0A9peUKgI2sSfd+x216eksSe+YQT3Nyk7Fb4JAOFFTtfH3TURKe0/bVoWmBPSlj?= =?utf-8?q?1m7jmDIo2M0EnyR4jCJSyTlsYS4bmRvPRLRt14NJ6Ebtv69DsujQ01lCkkYBu1RKS?= =?utf-8?q?vtvihazQ0l8rBgAqXg1jUaoM0UXZQaQGQwV+6X0teJz/y2BYjq9C7gOfwgH6VkZFN?= =?utf-8?q?hdgvI5cDU5ML2k4KOxXYvU6NnhY7GjwRV9ltTd96wKTQd3oA=3D=3D?=
x-ms-exchange-antispam-messagedata: =?utf-8?q?cNKJrYafOxldUhY/Ati7m3nHHIME/r?= =?utf-8?q?FhzvhzCobW2tnAc6rweU29TFqQNGYoPpIuzDDEsXlItahUR4wF64orun+Mh/U9RMj?= =?utf-8?q?5PAXrW5DkcACvni9aiwDvxfMZc/jEsmG0Fju+oUDTwUEr5Ei2WpdUqknpk5pw4lF4?= =?utf-8?q?Ngv7wdRe+iw=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bfeec108-a9fc-443f-8c6e-08d7c4586149
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2020 18:33:36.3041 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: =?utf-8?q?tC6hcVGYNCxkBl8x87zE+?= =?utf-8?q?q3sf9+MczBx0RFDsjcotbKp95QdGAALvk5ZXSnnT80JdBL6+x/H/zcfZ5xzZ/cRFA?= =?utf-8?q?=3D=3D?=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4419
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/yE_s6fDOkJQd3ZkBl7p1xPw_aDc>
Subject: Re: [netconf] WGLC: draft-ietf-netconf-notification-capabilities-11
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 18:33:53 -0000

Hi,

Thank you for this work.  I've reviewed this document as an individual contributor and also as an early incoming AD review.


Overall comments:

I support the progression of this work, I think that it is both useful and important, and the document is well written.  I like the split into two separate YANG modules covering system capabilities vs YANG push notifications.  I think that in an ideal world this work would probably be split into two separate documents, one covering system capabilities, and the second for notification capabilities.  In particular, I could imagine the system capabilities evolving over time.  However, I also understand the desire to complete this work, and I don't want to delay it.


Comments on individual sections:


1. Title:
 Perhaps it would be more accurate to name it as 
   "YANG Modules for describing System Capabilities and Yang-Push Notification Capabilities?"
 
2. Abstract
I propose that you rework the text to.
 
 OLD:
 
    This document proposes two YANG modules.  The module ietf-system-
   capabilities provides a structure that can be used to specify any
   YANG related system capability.

   The module ietf-notification-capabilities allows a publisher to
   specify capabilities related to "Subscription to YANG Datastores"
   (YANG-Push).  It proposes to use YANG Instance Data to document this
   information and make it already available at implementation-time, but
   also allow it to be reported at run-time.
   
 NEW:
 
   This document defines two YANG modules:
   
   The module ietf-system-capabilities provides a structure that can be
   used to specify YANG related system capabilities for servers.  The module
   can be used in conjunction with YANG Instance Data to make this information
   available at implementation-time.  The module can also be used to report
   capability information from the server at run-time.

   The module ietf-notification-capabilities augments ietf-system-capabilities
   to specify capabilities related to "Subscription to YANG Datastores"
   (YANG-Push). 


3. Terminology:

- Please add a reference to "instance data" from draft-lengyel-netmod-yang-instance-data

- Add the sentence: "In addition, this document defines the following terms:"

- Perhaps change "On-change Notification Capability" -> "On-change notification capability"?
- Move the definition of on-change notification capability last.

- Implementation-time information and Run-time information.  I think that these definitions should only be defined in terms of "server" and not "publisher", because I think that these considerations apply to all system capabilities, not only notifications.  Perhaps also reference YANG instance data.

E.g.

OLD:

   Implementation-time information: Information about the publisher's or
   server's behavior that is made available during the implementation of
   the publisher/server, available from a source other then a running
   server.

   Run-time information: Information about the publisher's or server's
   behavior that is available from the running server via management
   protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040].

NEW:

   Implementation-time information: Information about the server's
   behavior that is made available during the implementation of
   the server, available from a source other then a running server, such
   as YANG Instance Data [XXXX].

   Run-time information: Information about the server's behavior that is
   available from the running server via management protocols such as
   NETCONF [RFC6241] or RESTCONF [RFC8040].


   
4. Section 2:
Please state that the YANG modules are compliant to NMDA.


5. YANG model:

- Does "minimum-dampening-period" only apply of "on-change-supported" is enabled.  If so, it might be helpful for the description to state this.  I would also put the "on-change-supported" leaf before the "minimum-dampening-period" leaf.

- Does "minimum-dampening-period" only apply if dampening is requested, or does that mean that dampening is always required?  The text may need to be clarified.  Otherwise, I'm concerned about the on-change notification for interface statistics ... that could generate a lot of notifications ;-)

- For both "minimum-dampening-period" and on-change-supported", can probably remove "data store or" from the description.

- Suggest moving "supported-excluded-change-type" above periodic-notifications-supported, to keep all the on-change options together.  I'm also not particularly keen on the negative enumeration values, having them as positive values would seem more normal to me.


6. Section 6 (Security):

Is there a risk that the capabilities information, if available offline and also from a device, could be used to fingerprint the device and gain information about what version of software/hardware is being run?


7. Could you please add a brief section to thank folks who have contributed and reviewed this work.
- I think that it easier to get reviews, if the time/effort spent in the review is acknowledged.


8. Appendix A:
- Your examples look like they probably have some introduced line wrapping (e.g. for the description, node-selector, and others).  Perhaps we should be using the artwork draft for this, or alternatively add a comment that linespaces have been introduced in various fields to improve readability.

- Perhaps:

OLD:

 The following example is instance-data describing the notification
   capabilities of a hypothetical "acme-switch" ...
   
NEW:

 The following instance-data example describes the notification
   capabilities of a hypothetical "acme-switch" ...

- First example:
  "        </datastore-capabilities>" should be outdented at two spaces after first block.

- I would normally expect candidate/running to be listed before operational, although there is obviously no harm in having it the other way.

 
9. Appendix B:
 - Please add a note to ask the RFC Editor to remove this section on publication.
 
Nits:
 - Please check for full stops (e.g. terminology)

Thanks,
Rob


> -----Original Message-----
> From: netconf <netconf-bounces@ietf.org> On Behalf Of Kent Watsen
> Sent: 04 March 2020 21:54
> To: netconf@ietf.org
> Subject: Re: [netconf] WGLC: draft-ietf-netconf-notification-capabilities-
> 11
> 
> Dear All,
> 
> This WGLC has received zero responses, which is insufficient to progress
> the document at this time.  The chairs have therefore decided to extend
> the WGLC for another two weeks, now ending March 18th.
> 
> Again, positive comments, e.g., "I've reviewed this document and believe
> it is ready for publication", are welcomed.  This is useful and important,
> even from authors.  Objections, concerns, and suggestions are also
> welcomed at this time.
> 
> The NETCONF Chairs
> 
> 
> 
> 
> > On Feb 17, 2020, at 8:27 PM, Kent Watsen <kent+ietf@watsen.net> wrote:
> >
> > FWIW, this is WGLC #2, after the major updates resulting from WGLC #1
> (in October).
> >
> > K.
> >
> >
> >> On Feb 17, 2020, at 7:47 PM, Kent Watsen <kent+ietf@watsen.net> wrote:
> >>
> >> This message begins a two-week WGLC for draft-ietf-netconf-
> notification-capabilities-11 ending on March 2nd (a week before the IETF
> 107 submission cutoff deadline).  Here is a direct link to the HTML
> version of the draft:
> >>
> >> 	https://tools.ietf.org/html/draft-ietf-netconf-notification-
> capabilities-11
> >>
> >> Positive comments, e.g., "I've reviewed this document and believe it is
> ready for publication", are welcome!  This is useful and important, even
> from authors.  Objections, concerns, and suggestions are also welcomed at
> this time.
> >>
> >> Thank you,
> >> NETCONF Chairs
> >> _______________________________________________
> >> netconf mailing list
> >> netconf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/netconf
> >
> > _______________________________________________
> > netconf mailing list
> > netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf