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

Dhruv Dhody <dhruv.ietf@gmail.com> Thu, 09 May 2019 04:03 UTC

Return-Path: <dhruv.ietf@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 D42AF12025B; Wed, 8 May 2019 21:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 fNuDIR3eFOO2; Wed, 8 May 2019 21:03:13 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 53DA0120264; Wed, 8 May 2019 21:03:13 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id z4so566335iol.0; Wed, 08 May 2019 21:03:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=5QQMZ929+wacsGBuhjCLfY+y7FGKryJPsvoIVE7BVKc=; b=DIvqaj/27Hc6foVZLdLEAxPRnW4R3LDEbUA+V1so5P9p1Ypuhgg4CxqI3vHmNntL2w Kknnv9nn3vukuq2Lrp7GComb1BnzQgYUQrqLBWr5T9CTAPTaWgVWvJbsmtjWTLZOgnee cZP8QwWCU3qdC/3mp+zlX+rwZxMFIbZMyDBZdhm5HqTrnQ0LF6JLffoEGX72JJOr1RZX jABuPbI7I2eFcq7061vy+MX909ILjmRYlzqbf4geR2i+mgF8MNddfNCkgEHfOy0MkVQV LUK9M8w8VYsS/3WqfSJw2OU9HwlHUm+2As2gItGfRPeIlcotlmU70Pesi12M0kHt6Fmr xglg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=5QQMZ929+wacsGBuhjCLfY+y7FGKryJPsvoIVE7BVKc=; b=npMCgAt3hKcgjprmJ1eKUPVBNkNUrBpj+EgzEVDprmmeg/9rhRX3igpPfqUGMDfMzs OUgEGLzzcd1kVpCREFDkyPUYR8Km9RCMSNEF6DUYiz7yaU4R7c+skQtiMixGX+d3yGyY bj3C+f19N642u1KxANIL4fT6l4qA50W5OD54ftvZcHhE6a6D+39OER2Fqv0On5Ise04X QsO7GHZF4dv3leFIyZGFYBTwJUbWuJWhqDlnD/FLty0Zv8Z7I3VpRgBrVrLKEng4CDzQ I00YRRUsne7Y3mORKpDHPaS4EebgLeqdC2c5RI+yhb+bhSWPGtTA7b8MpbE9wGDfuAt+ dRjg==
X-Gm-Message-State: APjAAAVISKX9t4lYgVO/Hkw0UAjmfn/5M51aeQvVxSSBIiMAci91bYyo Yg2iU7VnuNN3Eb4BZFGj6uZm1MriEHGyAuXsJiY=
X-Google-Smtp-Source: APXvYqzNvnT75htL2kMUWtBDvKorKkLcw1qkb07ca6t7U+tkNUAJhXiIHPD1HjqZJSL1yNpTrK7urWk67KHJloNrIdc=
X-Received: by 2002:a5e:9b05:: with SMTP id j5mr1113170iok.158.1557374592410; Wed, 08 May 2019 21:03:12 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <e488c7df0d8049b8aed02b3d240ebe35@XCH-RTP-013.cisco.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 9 May 2019 09:32:35 +0530
Message-ID: <CAB75xn4it5rABU362p6--wECsc2NVvZqu-4Np1ZhLD72DB_s3Q@mail.gmail.com>
To: "Eric Voit (evoit)" <evoit@cisco.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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/pfpa405vI2GdPYyco36dA6XLnRk>
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 04:03:16 -0000

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.

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
> > >
> > >
> > >