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

Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 10 March 2020 03:47 UTC

Return-Path: <mjethanandani@gmail.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 6F9483A0ECC for <netconf@ietfa.amsl.com>; Mon, 9 Mar 2020 20:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VZOckDvU7gMy for <netconf@ietfa.amsl.com>; Mon, 9 Mar 2020 20:47:50 -0700 (PDT)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D95F23A0EC7 for <netconf@ietf.org>; Mon, 9 Mar 2020 20:47:29 -0700 (PDT)
Received: by mail-pl1-x62c.google.com with SMTP id f16so2726865plj.4 for <netconf@ietf.org>; Mon, 09 Mar 2020 20:47:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=qHu97nZz0dxntQv713rr3fheRNkAEFj6X39j+CohRSw=; b=USXiG1QEqD2eLmpZuzD2bipz0l/ZVYaecjqrrUaDg//lfdoBi2E8cpcBG+NxPMi/l8 QKw4Z1/XWU0bd+uye/dmXnG4foVZQ8EoWZUVeJpnQIz7j6Mc8zkZFGhadYN/9y0Z7HDV K26qTh+5jcoHya7kOG73/vBY+wAlBY2LiCyGFVGJ8TuoJhvGeqBHLl3kDpjzN30RP0Nf kdGbiharhjv/nW6ZE0UhDACD9WnJdLje+Pba0RjChhSjTEpcrGK0vM/ApChQJ7Zjlf/Z mEGKWdP2q8t06p7QcQtaZH9B5BMpZbH9QAywZMA54hjmmDskhOfuyBd5KJheCi/ASLXq KzHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=qHu97nZz0dxntQv713rr3fheRNkAEFj6X39j+CohRSw=; b=ffSSKTwWaOgft5IlhSUmSdpyaJMhDg33K5XOtkQdHLKxFVckr1FK8koP7GROzxVyot E2xocjhbF8PEp25M7DUbOCZ7K2Xmhz3dhe1t3PNUM/40PyxXu4QBCi/0QPKs/shb+y89 XX/ffpd+A3OXGwIh5/xTIOdP5R7OeFGpHCZuKOXKLcDAAgUeNRPBl0UYakfZbUe5CIAi cPA8rPpPTs+58KH1+gbQ1Dafq/weG2IIjLYqU9QIwsH1VG2nlqynnCRlBeHwDY/frbjE NDYeqWnzAwNFG3b8LmYgCPlQv5tVm48EV2+12Icb5yDoBkvGm+JlxkRf5o/mFkKB9GY6 EUwg==
X-Gm-Message-State: ANhLgQ3hxeZADw9RzOxSDpdjO5eSR5C9YZq/9V3ttiALruN+cbf5ifXu eNu+ojcAm0IkmntrMImX2rMSDjZ2
X-Google-Smtp-Source: ADFU+vvDVrNvhTAR/nwXrTkS1LLcht7fhx3ti3zuwyY+1bOT0jeAAxqNwS/ZMIEbwNbugQQzpSB+Tg==
X-Received: by 2002:a17:90a:bf0c:: with SMTP id c12mr2112962pjs.28.1583812048766; Mon, 09 Mar 2020 20:47:28 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:c66:ef44:8f0b:9230? ([2601:647:5600:5020:c66:ef44:8f0b:9230]) by smtp.gmail.com with ESMTPSA id mt19sm205551pjb.5.2020.03.09.20.47.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Mar 2020 20:47:27 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <53B69FD5-0834-4943-A33A-1596FD3434BD@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5181A0B9-B4D4-4F2B-B195-E6188782F1FC"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 09 Mar 2020 20:47:25 -0700
In-Reply-To: <01000170a78abdde-66112ceb-d466-4c72-ad18-6058ef07ab02-000000@email.amazonses.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Kent Watsen <kent+ietf@watsen.net>
References: <0100017055c347e5-13b624a9-04c0-4ba5-8a53-26a80f079607-000000@email.amazonses.com> <0100017055e833dd-1a2ecac4-53e4-4bb7-aab9-f75516c5fd38-000000@email.amazonses.com> <01000170a78abdde-66112ceb-d466-4c72-ad18-6058ef07ab02-000000@email.amazonses.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/YVMSBSTbiHDqaIHJPOCIJC2MivE>
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: Tue, 10 Mar 2020 03:47:58 -0000

I support the publication of this draft, but would like some of the issues addressed in the document. They are mostly nits that I am hoping can be addressed before sending it to IESG. I reviewed the -12 version of the document.

s 2 Introduction

s/as it part of/as it is part of/
s/Examples include:/Examples include/
s/even to individual/even individual/
s/both in implementation-time/both at implementation-time/

s 2.1 YANG-push Notification Capabilities

OLD:
      to check that capability information provided early, already in
      implementation-time is indeed what the publisher implements (is
      the supplied documentation correct?)

NEW:
      to check that capability information provided earlier, at
      implementation-time is what the publisher has implemented

s 3 Providing System Capability Information

s/already in implementation-time/already at implementation-time/

s 4.2 YANG Module & s 5.2 YANG Module

This section needs to list every draft/RFC referenced in the YANG model.

All imports should carry a reference statement to the draft/RFC they are importing from, e.g. ietf-netconf-acm.

s 7.2 The YANG Module Names Registry

The indentation of the second registry is off.

Finally, have all the examples in the appendix been validated?

Thanks.


> On Mar 4, 2020, at 1:54 PM, Kent Watsen <kent+ietf@watsen.net> wrote:
> 
> 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