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

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 08 May 2019 06:21 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 6A06112014A; Tue, 7 May 2019 23:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 zKKjeAJQMW8j; Tue, 7 May 2019 23:21:23 -0700 (PDT)
Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 0A2C6120134; Tue, 7 May 2019 23:21:23 -0700 (PDT)
Received: by mail-it1-x130.google.com with SMTP id g71so2152237ita.5; Tue, 07 May 2019 23:21:22 -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=4j58fOYHrClmYK94QGDLpjLQ7AmsI03YqKwjVGMeaZo=; b=end91jnoC15BoLGesk297OPobhrOGxVMW8XSQ/jaSAPG8gNwCcDVfXQrUFA0664Ec8 geuZSSgkOassi3i9GuLLbPrENL/2SCxaiRbWN+eGjtvTW9gqCD9aYDAyAMcr9Kt9s8pv /s47rfoltgk74n6cKjGFrMqZtYYNwJW+v4QhahR1s5+TyVuYycNdb11f/iXT9P07xYu6 gd934nUauT0tbEmfI+f3bGpsdqaqYRABiezWOMQPJqC8GvaAzTtViEpq3WkazmOMzIGQ Goi5V4nwNRBIL16rT4WJULRqLYwuGnT4FSt8g/o393jU77ALc11M5eUinvslwqy2QcS0 fzNw==
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=4j58fOYHrClmYK94QGDLpjLQ7AmsI03YqKwjVGMeaZo=; b=YN7twdQ0ArejB21Xkwo/SkRjX5HMAquP/ZymUH/Ukm2kFspv2ZtSj0g9Dg212ThIxn Pi5jTlrKWDcZZaXpQXUz4mBIix6pxZlDW8PMmhEBcSSyoDHs2wEnxKceYHmN9YXqjKM1 SY/VP3XTOBRdDyOFgIZwuNOHxXGfFbpeRo9ZPzfnVX77LYmQNaknY5iuNsHh896TG6Ir w8srxvrVlN+tLWMwrrFahhGCarEBSPHllL0s5hYtvbmAf8tz0RHY+lCEz7bgQRsGglmK R2W79GBe5z1+/5T8/ojV1p2+QzTCiTMYNzUdYegBDIQXQ2Nu1UA/GzYUBgNIyOYRNqjd lH1A==
X-Gm-Message-State: APjAAAUV2k6tKkAwHac4iCXyqYE/kpCiZdQVg7Nxfo7myLNpojFxOtLY EUvlwO4BJMLqAW6N/Ss4vNZdBS3mq0pgyGeHl2s=
X-Google-Smtp-Source: APXvYqyZ9mlpYlrerT2VPxlbORQe7EwJrU3z4S4eYSo60R7UjFSQbCAq8dsV2yYmdqoBDaZix7/5ZC4Bjwm/CL6mAXE=
X-Received: by 2002:a24:cd82:: with SMTP id l124mr2157139itg.164.1557296482202; Tue, 07 May 2019 23:21:22 -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>
In-Reply-To: <0100016a944613e1-766a1ada-f1a1-44a3-bced-4ed28baa8797-000000@email.amazonses.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 8 May 2019 11:50:45 +0530
Message-ID: <CAB75xn4vcHcu3pNBCntWjhw9s6RkgspsfWkQuW4AF3=P8v16cw@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: "Eric Voit (evoit)" <evoit@cisco.com>, "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/PxqB5EERyKVsgd8tGYd2p4RNc8o>
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: Wed, 08 May 2019 06:21:24 -0000

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