IETF Logo Mail Archive

Re: [netconf] Comment on draft-ietf-notification-capabilities

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Mon, 19 August 2019 22:25 UTC

Return-Path: <rrahman@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 8591B1200EC for <netconf@ietfa.amsl.com>; Mon, 19 Aug 2019 15:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 header.b=ENIaxhoZ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=hSnMguMH
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 d86qmmh5-k4k for <netconf@ietfa.amsl.com>; Mon, 19 Aug 2019 15:25:39 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFE5412008C for <netconf@ietf.org>; Mon, 19 Aug 2019 15:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17547; q=dns/txt; s=iport; t=1566253538; x=1567463138; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=m9zM0LHwAYa4ol6gSGxdn0/BKcBX8BEjIR5Qw5lYrTs=; b=ENIaxhoZmx9EMBrBFCB2RaUPfrDav2klo8MQIxkwpl3pOvMzEi6nlMoj St5bP34E1N08pPLT90krUGuzgSA4F/NYdGBK0m2nlrGp4kUe7P4EiI7XK Zrofnrp1ac6REuGdmq71AlMoqWUWFMRf066mQlcaLWTVil/qR6QpEunTL k=;
IronPort-PHdr: 9a23:9m4g7xdCpsran5CUZIxaNIGvlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dTYzHMFLUndu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0COAADRIFtd/40NJK1mGQEBAQEBAQEBAQEBAQcBAQEBAQGBZ4EWL1ADbVUgBAsqhB+DRwOKeU2BaiWTC4RaglIDVAkBAQEMAQElCAIBAYQ/AheDDyM4EwIFAQEEAQEBAgEGBG2FJwyFSgEBAQEDEhEKEwEBNQMPAgEIEQMBAQEOGgMCAgIwFAkIAgQBEiKDAAGBHU0DHQECDKARAoE4iGFzgTKCegEBBYUCGIIUAwaBNIR0hnUXgUA/gTgME4JMPoJhAQECAYFINg0JglUygiaPFYUPiQKOLwkCgh2GaI1RG5hEjVqHYpApAgQCBAUCDgEBBYFnIYFYcBU7KgGCQYJCg3KFFIU/coEpjVcBAQ
X-IronPort-AV: E=Sophos;i="5.64,406,1559520000"; d="scan'208,217";a="531201663"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Aug 2019 22:25:37 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x7JMPbGR003513 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 19 Aug 2019 22:25:37 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 19 Aug 2019 17:25:36 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 19 Aug 2019 18:25:35 -0400
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 19 Aug 2019 18:25:35 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fOLUPosTUUUPobHU6DlHucfw5oVE4P9WYtu8eCS8QfN4VFa51hTTC5V4eGDqyH6kB4cOvj9XlJrcLYFWTzfHDUodH9h2Bo3WIhFQZ9ZJBkEkUlfSwRQ9NsfgJFb6W6F9UkIsRyTFEkwUtUvwTZHQw4cELIbsHptIXyIo54jytq/1vQcXm94a7XE/MZ9b91Vmvpw6vf6IrTW9LY/f8UwY0kdl2w6JyVfcFfQ5jXQRP8AWUekNU4z/fDYy+2yUhvtUeKWD+nMNYYEqLcincz/1UJZVfAnXx748/B59w8QPxT/xEGmd8wAbeGo8mysXeOo4yN0ckOSOkvdyX3fBFNl1HQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=m9zM0LHwAYa4ol6gSGxdn0/BKcBX8BEjIR5Qw5lYrTs=; b=D6+uM6p2BEB7aKQN5Uf0YEwAVjL4Yhk3UFZKOTilYtA4ztfHm5wdlcjfnmbuxjs25Mzvcvtryn3laPBwk42i5upvzEzVE0/mGzIs7Yk4sWEVhmSKK1jIn0bCb89LAa5BkUbXbcgkwRE7YxCxw7xim0DZFBtOTEu4f5Loj1/lOpzSfYdRICQLT5TFpbyB+x9PzfcB9Z+BlCV7Bwo8AZXuMMY0Yl2+O5iX6EME+34/VuCzXzDVbLlAWUQ5iAc3fIkKXbSRelB2E5IESZ9ScZ7lC0o6z3Glntx5DSopn9aXdsbqJtCmdWcTvOOY2a9ExtGeRRKoxviZJLQ6fCZFhWRujQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=m9zM0LHwAYa4ol6gSGxdn0/BKcBX8BEjIR5Qw5lYrTs=; b=hSnMguMHTIS7pLVmEGrcrX8US8EJDhrOFXfflVGyIs3z9leZrexH7FS9rrKy25DKuxZ/WkTjibFWEiyMYZONT7HBevMjqGweMtkrQTu4ZOSZagjSLyfaELM0n+/9pjjAjSbatuIsOBo670iuAUgVQs5rsrJbhLMqaYREI1D8FIc=
Received: from MN2PR11MB4157.namprd11.prod.outlook.com (20.179.150.223) by MN2PR11MB3776.namprd11.prod.outlook.com (20.178.251.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.21; Mon, 19 Aug 2019 22:25:35 +0000
Received: from MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::80bb:d4b:bc47:7daf]) by MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::80bb:d4b:bc47:7daf%3]) with mapi id 15.20.2178.018; Mon, 19 Aug 2019 22:25:35 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Balázs Lengyel <balazs.lengyel@ericsson.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Comment on draft-ietf-notification-capabilities
Thread-Index: AQHVQZX8ds7lhqEeQECSgTAu48XmQKbYv4YAgCG5xDCACHqDgA==
Date: Mon, 19 Aug 2019 22:25:34 +0000
Message-ID: <67FF4815-A6F2-48CE-8707-DF2DC3D08B43@cisco.com>
References: <A35AA44D-EEFA-4609-8974-5F41FECC98DC@cisco.com> <VI1PR0701MB22863263E6BEA915395089D1F0C70@VI1PR0701MB2286.eurprd07.prod.outlook.com> <VI1PR0701MB228644988825CDC24FCF1863F0AD0@VI1PR0701MB2286.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB228644988825CDC24FCF1863F0AD0@VI1PR0701MB2286.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rrahman@cisco.com;
x-originating-ip: [2001:420:2840:1250:6900:eb73:e481:aee6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b00e1316-7778-4d50-6f07-08d724f4278d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3776;
x-ms-traffictypediagnostic: MN2PR11MB3776:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <MN2PR11MB3776D98BA1F18DAE4A8D945DABA80@MN2PR11MB3776.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0134AD334F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(39860400002)(346002)(376002)(136003)(366004)(189003)(51444003)(199004)(11346002)(236005)(6306002)(606006)(54896002)(6512007)(2420400007)(81166006)(81156014)(71190400001)(966005)(71200400001)(25786009)(6486002)(6246003)(66556008)(7736002)(229853002)(66476007)(15650500001)(53936002)(8936002)(76116006)(36756003)(8676002)(6436002)(64756008)(66446008)(6506007)(53546011)(2501003)(102836004)(58126008)(86362001)(476003)(256004)(66574012)(33656002)(99286004)(14444005)(66946007)(5660300002)(9326002)(316002)(486006)(186003)(2616005)(14454004)(790700001)(6116002)(2906002)(76176011)(46003)(110136005)(7110500001)(478600001)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3776; H:MN2PR11MB4157.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 3fr4jVSnteb+z94dCbszWryMhpMm8RQApnBDSSbHT5NJf2s9nodLx7mdVn9YMczvOfIAi3M7CmZE55iTVuaEqIHjDyPh0MdNbC1M4WFwuq+X71M4uBwoU5ZhMJAwNG18lHb27zIzwdG3NMa0wiRHJpUFshlZoxJbfljlXFCinckKa2YDFpx3Ku+bHryUbCQUbGDkvqn4AoAR7VxHXHRv8sPftR+cMet9G8np+tnyr7qykI/uv8vkkapKPTWENWcphyXKJJxWUWLMG/jDRtyjHjZ2I4zUkCGm8EVYMmGETl1NVzLdfkdeLXepX0Wo1RgnGC/CgUyg174qno8KmF4/cBQY1NZCz2HGG9VAtuIE5XbXiwt0KSho8LVpwkK2ya7bHWtQfsDW+O604zpz7N47HmMt0Lo2EfwwyHGTEq4kRLI=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_67FF4815A6F248CE8707DF2DC3D08B43ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b00e1316-7778-4d50-6f07-08d724f4278d
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2019 22:25:34.8676 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: zsvD4cAh39j6ILNs5YWsqlonhYKpzJmy9ER3ik9xDhXcPDhn8oIDaJEik0sTWXe0bQsJVo7hGAwOGTC97AXIyA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3776
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/KG4P3x_8DgL1wN8QFvLcUynmrHc>
Subject: Re: [netconf] Comment on draft-ietf-notification-capabilities
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: Mon, 19 Aug 2019 22:25:42 -0000

Hi Balazs,

Thanks for adding this text. I think the text is a bit ambiguous, since it’s implementations which support changing capabilities at run-time which should support on-change notifications about the datastore-subscription-capabilities container.
Also it’d be great if one of the examples in Appendix A explicitly mentioned whether capabilities can change at run-time. For instance, the second example has on-change-supported-for-state set to true, so this would imply that the capabilities can change at run-time since there is no entry for the datastore-subscription-capabilities node. You could add the following and state that the on-change capabilities can’t change at run-time.
        <per-node-capabilities>
          <node-selector>
            /inc:datastore-subscription-capabilities</node-selector>
          <on-change-supported>false</on-change-supported>
        </per-node-capabilities>

Regards,
Reshad.

From: Balázs Lengyel <balazs.lengyel@ericsson.com>
Date: Wednesday, August 14, 2019 at 5:01 AM
To: Balázs Lengyel <balazs.lengyel@ericsson.com>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "netconf@ietf.org" <netconf@ietf.org>
Subject: RE: Comment on draft-ietf-notification-capabilities

Hello Reshad,
https://tools.ietf.org/html/draft-ietf-netconf-notification-capabilities-03#section-3 includes the text:

For the run-time use-case: It SHALL be available via NETCONF

      [RFC6241<https://tools.ietf.org/html/rfc6241>] or RESTCONF [RFC8040<https://tools.ietf.org/html/rfc8040>] from the live server during

      runtime.



      As these capabilities might change during run-time,

      implementations that support the YANG-Push on-change feature,

      SHOULD support sending on-change notifications about this module.

I think that should cover your comment. Or is it something else you want?
Regards Balazs

From: Balázs Lengyel <balazs.lengyel@ericsson.com>
Sent: 2019. július 23., kedd 23:56
To: Reshad Rahman (rrahman) <rrahman@cisco.com>; netconf@ietf.org
Subject: RE: Comment on draft-ietf-notification-capabilities

OK, will add it.  Balazs

From: Reshad Rahman (rrahman) <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Sent: 2019. július 23., kedd 16:34
To: Balázs Lengyel <balazs.lengyel@ericsson.com<mailto:balazs.lengyel@ericsson.com>>; netconf@ietf.org<mailto:netconf@ietf.org>
Subject: Comment on draft-ietf-notification-capabilities

Hi Balazs,

Section 2 mentions that the capabilities could change at run-time. For those implementations which support this, there would be value if the datastore-subscription-capabilities container is on-change capable?
This should be indicated with an entry for that node in the on-change-notification-capability list (for the operational datastore)? Could we have some text in the draft for this?

Regards,
Reshad.

v2.15.0 | Report a Bug | By Email