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

"Eric Voit (evoit)" <evoit@cisco.com> Wed, 08 May 2019 15:44 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 D9A6512013C; Wed, 8 May 2019 08:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, 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
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 aluGz2cHVDc8; Wed, 8 May 2019 08:44:30 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CEA5120136; Wed, 8 May 2019 08:44:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2928; q=dns/txt; s=iport; t=1557330269; x=1558539869; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=r477+/v9Fjr/1wZqh4zPAZFRSKPiAJSC6FGSKVQC9BY=; b=Uxa2vdMYB74KiF1dl7Eq76EvRAkMqAMZbsCYPOO3itx+7QPgiUowetEf DaVfPv0GlxL4/Gh6FsfNS1Ug6XUKpXbVGCRE/towKeX+DOh6IQhZ48X3o uhZqnCcqo7Fqq5aSsmZ/fOK9GYx8MfEbcELAZZ7fLZ1YKIXvrjcwXBKwu g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AnAABA+NJc/5ldJa1kHAEBAQQBAQc?= =?us-ascii?q?EAQGBUQcBAQsBgWYqgT0wKAqEBogcjQKYUoF7CQcBAS+EPwIXgXEjNAkOAQM?= =?us-ascii?q?BAQQBAQIBBG0ohUoBAQEDASMRQwIFCwIBCBUDAgIJHQICAjAVEAIEAQ0FCIJ?= =?us-ascii?q?PS4F8D60jgS+KKoELJwGLTReBQD+EIz6ESzOCUIJYBI0qLJlsCQKCCZJHI4I?= =?us-ascii?q?Qk0eDG4kJgSGTVQIRFYEwHziBVnAVgyeQUUExj26BIQEB?=
X-IronPort-AV: E=Sophos;i="5.60,446,1549929600"; d="scan'208";a="268935471"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 May 2019 15:44:28 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x48FiR7f000383 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 May 2019 15:44:27 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 8 May 2019 11:44:26 -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; Wed, 8 May 2019 11:44:26 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, Kent Watsen <kent+ietf@watsen.net>
CC: "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/xOtqZU7OSwgAI1bICACP37sIAAYi6AgACOyoCAAFnN8A==
Date: Wed, 8 May 2019 15:44:26 +0000
Message-ID: <e488c7df0d8049b8aed02b3d240ebe35@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>
In-Reply-To: <CAB75xn4vcHcu3pNBCntWjhw9s6RkgspsfWkQuW4AF3=P8v16cw@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.233]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.153, xch-rtp-013.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/j82KRyjk9e_Ij2o-i0E0ikL_TzQ>
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 15:44:32 -0000

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