Re: [netconf] RtgDir review: draft-ietf-netconf-netconf-event-notifications-17

"Eric Voit (evoit)" <evoit@cisco.com> Thu, 09 May 2019 20:47 UTC

Return-Path: <evoit@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 7743E1200DE; Thu, 9 May 2019 13:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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
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 fEPEZsopt7QG; Thu, 9 May 2019 13:47:40 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDCE612009C; Thu, 9 May 2019 13:47:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5014; q=dns/txt; s=iport; t=1557434859; x=1558644459; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=fe08GN/4ONqB/3ECqbgrx3gPLg19ykkOYX6Zmmxzo1I=; b=VlySrsFguTO/kQNZNqL4x8wKU/lXtBuWJVx7u1KexTyNS1ywtr+TTQOB GBLcSDENfjpFTDT2dmn5VGgZ2PN0EXv4yC5f0rBsAN1ZY9YE9mCx+bgRX 0L0Q3EUO23MQU2tgoRaPKP9XpnQYaAjdQWNEOetob+z9AJje5Jqwai6Bd s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DAAADokNRc/5JdJa1kHAEBAQQBAQc?= =?us-ascii?q?EAQGBVAQBAQsBgWYqgT0wKAqEB5Uemk4JAQEBDAEBLwEBhEACF4FxIzcGDgE?= =?us-ascii?q?DAQEEAQECAQRtKIVKAQEBAwEjEUMCBQsCAQgVAwICCR0CAgIwFRACBA4FCIJ?= =?us-ascii?q?PS4F8D603gS+KMoELJwGLTheBQD+EIz6ESzOCUIJYBIsZA4IPLJluCQKCCZJ?= =?us-ascii?q?MI4IQhkYFjH6DG4ork1YCERWBMDUigVdwFYMnkFFBMY5egSEBAQ?=
X-IronPort-AV: E=Sophos;i="5.60,450,1549929600"; d="scan'208";a="557414181"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 May 2019 20:47:38 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x49Klcsp005052 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 9 May 2019 20:47:38 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 9 May 2019 16:47:37 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1473.003; Thu, 9 May 2019 16:47:37 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
CC: Kent Watsen <kent+ietf@watsen.net>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-netconf-netconf-event-notifications.all@ietf.org" <draft-ietf-netconf-netconf-event-notifications.all@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, Dhruv Dhody <dhruv.dhody@huawei.com>, "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>
Thread-Topic: RtgDir review: draft-ietf-netconf-netconf-event-notifications-17
Thread-Index: AQHU/xC8WbWTXSPvekeZmlnK7/xOtqZU7OSwgAI1bICACP37sIAAYi6AgACOyoCAAFnN8IABEe2AgADU50A=
Date: Thu, 9 May 2019 20:47:37 +0000
Message-ID: <e68ea032d2c04a6383f9291080f33256@XCH-RTP-013.cisco.com>
References: <CAB75xn4HiqYqeWu2tiOsfDwU4ePc+-6ym+4EpowqZ-YMgkRRMA@mail.gmail.com> <7395d7e5db4b48e1ba582c9c48c29913@XCH-RTP-013.cisco.com> <0100016a758d3dec-7b7a305f-30f6-4234-b66e-d48960cddef6-000000@email.amazonses.com> <1cf686e76a314553842305bc97baeb3d@XCH-RTP-013.cisco.com> <0100016a944613e1-766a1ada-f1a1-44a3-bced-4ed28baa8797-000000@email.amazonses.com> <CAB75xn4vcHcu3pNBCntWjhw9s6RkgspsfWkQuW4AF3=P8v16cw@mail.gmail.com> <e488c7df0d8049b8aed02b3d240ebe35@XCH-RTP-013.cisco.com> <CAB75xn4it5rABU362p6--wECsc2NVvZqu-4Np1ZhLD72DB_s3Q@mail.gmail.com>
In-Reply-To: <CAB75xn4it5rABU362p6--wECsc2NVvZqu-4Np1ZhLD72DB_s3Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.226]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.155, xch-rtp-015.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/AQhwry4VimNzt1D0jaMIc0e-F2M>
Subject: Re: [netconf] RtgDir review: draft-ietf-netconf-netconf-event-notifications-17
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: Thu, 09 May 2019 20:47:42 -0000

Hi Dhruv,

> From: Dhruv Dhody, May 9, 2019 12:03 AM
> 
> Hi Eric,
> 
> Thanks for the update. I see one minor comment that is not handled.
> Maybe you missed it? Or you disagree, that some more text is required?
> 
> > Minor Issues:
> > -------------
> > (1) Abstract & Introduction, It is not clear what does the 'binding'
> > mean and who are the parties to this binding? If this is the document that
> mentions 'binding'
> > first, so please add some more clarifying text.

This is not the first document which mentions 'binding'  first.  The document which does this first is draft-ietf-netconf-subscribed-notifications.   In the abstract of this document, that draft is not explicitly listed by reference (as I understood we are not supposed to use references in abstracts).  But it is listed in the Introduction.

To make this clearer for you in this document, perhaps "transport binding" instead of "binding"?   I really don't have many alternatives I can think of which also keeps the text brief.   This particular text has been frequently tweaked in the past.

Thanks.
Eric

 
> Thanks!
> Dhruv> 
> On Wed, May 8, 2019 at 9:14 PM Eric Voit (evoit) <evoit@cisco.com>; wrote:
> >
> > Update posted as -v20.   With the corresponding change to draft-ietf-netconf-
> subscribed-notifications posted as -v25.
> >
> > Eric
> >
> > > From: Dhruv Dhody, May 8, 2019 2:21 AM
> > >
> > > Hi Kent, Eric,
> > >
> > > Fine with me!
> > >
> > > Thanks!
> > > Dhruv
> > >
> > > On Wed, May 8, 2019 at 3:19 AM Kent Watsen <kent+ietf@watsen.net>;
> wrote:
> > > >
> > > >
> > > >
> > > > <eric> Based on my reading of your process suggestions Kent, I
> > > > like best the
> > > “mention” approach which you used for RFC-8071, Section 1.4.
> > > >
> > > > What I think could be done to cover this is:
> > > >
> > > > (A)  Remove Section 11: Notes to the RFC Editor
> > > >
> > > > (B)  Per Kent’s desire to also cover
> > > > draft-ietf-netconf-restconf-notif, place the
> > > following statement into draft-ietf-netconf-subscribed-notifications
> > > directly after Figure 10
> > > >
> > > > [RFC-5277] Section 2.2.1 states that a notification message is to
> > > > be sent to a
> > > subscriber which initiated a "create-subscription".   With this specification,
> this
> > > RFC-5277 statement should be more broadly interpreted to mean that
> > > notification messages can also be sent to a subscriber which
> > > initiated an "establish-subscription", or a configured receiver
> > > which has been sent a “subscription-started”.
> > > >
> > > > Does this work for both of you?
> > > >
> > > >
> > > > Works for me.
> > > >
> > > >
> > > >
> > > > The issue isn't consistency so much as meeting expectations, per
> > > > `xml2rfc`, the
> > > document should have something like the following in the References
> > > section, which then auto-expands to the correct reference text, as
> > > well as defining the anchor "I-D.ietf-netconf-subscribed-notifications":
> > > >
> > > >         <?rfc
> > > > include="reference.I-D.ietf-netconf-subscribed-notifications"?>
> > > >
> > > > <Eric> That definitely makes things easier than what I have been
> > > > doing.  I am
> > > hitting an xml2rfc error trying this right now, but I will get there.
> > > >
> > > >
> > > > Yes, it was an eye-opener when I figured it out.   Be aware that, though
> some
> > > external sources (e.g., ITU standards) are supported, many are not,
> > > and so hand- coding the <reference> is still sometimes required...
> > > >
> > > >
> > > > Kent // shepherd
> > > >
> > > >
> > > >