Re: [netconf] More capabilities for ietf-notification-capabilities (WGLC)

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 11 October 2019 12:46 UTC

Return-Path: <rwilton@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 D3EE3120073 for <netconf@ietfa.amsl.com>; Fri, 11 Oct 2019 05:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.4
X-Spam-Level:
X-Spam-Status: No, score=-14.4 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, TRACKER_ID=0.1, 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=bwMAYajJ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=LvrG7+Et
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 Nf9NAI-Msoht for <netconf@ietfa.amsl.com>; Fri, 11 Oct 2019 05:46:06 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 591C1120019 for <netconf@ietf.org>; Fri, 11 Oct 2019 05:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9913; q=dns/txt; s=iport; t=1570797966; x=1572007566; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=IctBamhOrakugnlZ9BGMjsuNzvCVv9AZnd1ioj5tbI0=; b=bwMAYajJOBtJW3ARbxtCmgv6IZJ61sCuEt9KRpxwFPyYCIBwtFwKSsPb CgGms++hmur8+DbCt7/6doaOt33Xj0hjUuHmERCotO29P+CTJYhHdxigR Ky27TU5ajkJ7lklIgMTgU7RNyhJQF3VOxg/iP3Lns/pWbG0OxGrOJgM7b g=;
IronPort-PHdr: =?us-ascii?q?9a23=3AdscuthB7mA4xAVXAmrhIUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qs13kTRU9Dd7PRJw6rNvqbsVHZIwK7JsWtKMfkuHw?= =?us-ascii?q?QAld1QmgUhBMCfDkiuNuHrazA9GuxJVURu+DewNk0GUMs=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0APAADPeKBd/49dJa1mGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYFnBQEBAQELAYEbLyQsBWxWIAQLKgqHYAOEWIV?= =?us-ascii?q?vTYIPkxyEYYEuFIEQA1QJAQEBDAEBIwoCAQGEQAKCXiM0CQ4CAwkBAQQBAQE?= =?us-ascii?q?CAQUEbYUtDIVLAQEBBBIbEwEBNQMPAgEIEQQBASgHMhQJCAEBBAESCBqDAYF?= =?us-ascii?q?5TQMuAQIMpwQCgTiIYYIngn0BAQWFCxiCFwMGgTQBhRWGeBiBQD+BEUaCTD6?= =?us-ascii?q?CYQEBAgGBKwESAQkYKwmDCoIsjRKIFIEEiCqOcwqCIoYkZI4smUCOLYgikRU?= =?us-ascii?q?CBAIEBQIOAQEFgVI5Z3FwFTuCbFAQFIFPg3OFFIU/dAGBKI1jgSIBgSIBAQ?=
X-IronPort-AV: E=Sophos;i="5.67,284,1566864000"; d="scan'208,217";a="646009688"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Oct 2019 12:46:03 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x9BCk3L5002176 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 11 Oct 2019 12:46:03 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 11 Oct 2019 07:46:03 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 11 Oct 2019 07:46:02 -0500
Received: from NAM03-BY2-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; Fri, 11 Oct 2019 08:46:02 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fi6TANMoE+eciNiZ087TDP6f/YU0Oiu0T8Up7gd6Z5PoEbOYL91v2EK3D6KF4bA6uyxCzpOUgTgGl3oIVjTnoMe9qzzfH+XDLcw2+tNNvwAFQGjW1I1FhRkFh0HQy2Mq9yNB/NeOPZBSc8aVpr5nq+B5sbL8IDAqp+nUBXTLVVx4oJQMCQIs9qaL9hfSDSIUHjZlmtIb99rdRFACcU+HPlVWRh5tj8J0c8niNde/XDnXMtwRxN9v9Sg6A93D/1KiUWezzHn/f83YSm+0tdJ2DguseNj7RvPvYLi5mAb1dw+nNE3DkVNkA8r33n6GziBJiEvAxvXf0lwGdEvyDS4QCA==
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=HlvHewO7nqyQeqbRQNJPh70sbx51AMsjTTHVmBku1+s=; b=i98XtsxE/gVISjHr9T1bDGnlmYhKCIJT0MqXNx/jJFWev3aM2f0n2L3cgRG9Mu+NuWol167RR4DfMSrgtxHMomQRoy3AkqQPCGrhHAnYrgUSN7FlMAdKU/Fb3ZAKYiZxuD+Zws85JMIMdxacZ13WGBSYOhSkVGdoGDX+7u2r6ZGMYrNGhyOlKQj8obio1pjhbPQwkD/iFx3V3+MctHmRyotD1EkDpOzkVAN64fef93RH7AKF3OqaTU3Lyth/tymF4JHo6zuk+oIE4RJHKY2FbsXW27mtbyYln2CQ3BFGtoDKSxmpDOUQ7rKax5zOPrJYxKv6Obs5UZeeTokaGsB/Jg==
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=HlvHewO7nqyQeqbRQNJPh70sbx51AMsjTTHVmBku1+s=; b=LvrG7+Et3/BUGaHfOeB3ZgNEtl59D4Bl3Y4yd/YWvIBwtxwuaUS6G/lH0wsXqr9S/VXlXV2mLxuY85Mvo3Jq33acuAvrYDslIjKPsULLYFRp7MKyZyl2tnp4Q5qP0UNk7FFH/Hx3MBpJdznyb5abvsb2t20UXtpoevM/ytQS6ys=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB3886.namprd11.prod.outlook.com (20.179.150.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.16; Fri, 11 Oct 2019 12:46:01 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::cca:41bd:b0bb:c549]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::cca:41bd:b0bb:c549%2]) with mapi id 15.20.2327.026; Fri, 11 Oct 2019 12:46:01 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: =?iso-8859-1?Q?Bal=E1zs_Lengyel?= <balazs.lengyel@ericsson.com>, Netconf <netconf@ietf.org>, Alexander Clemm <ludwig@clemm.org>, "Eric Voit (evoit)" <evoit@cisco.com>
Thread-Topic: More capabilities for ietf-notification-capabilities (WGLC)
Thread-Index: AdV+rn5v2Ucx0GJ9Tj2SEjVbMpaBTABgwrdg
Date: Fri, 11 Oct 2019 12:46:01 +0000
Message-ID: <MN2PR11MB43669E19CC3B19C503C3D539B5970@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <VI1PR0701MB22868DD351B416462CE90CEDF0950@VI1PR0701MB2286.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB22868DD351B416462CE90CEDF0950@VI1PR0701MB2286.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.41]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 989248c4-ac7d-4bd5-2476-08d74e48f8ab
x-ms-traffictypediagnostic: MN2PR11MB3886:
x-ms-exchange-purlcount: 1
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MN2PR11MB3886714F02815F549396B485B5970@MN2PR11MB3886.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0187F3EA14
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(4636009)(376002)(136003)(39860400002)(346002)(366004)(396003)(199004)(189003)(51444003)(74316002)(99286004)(229853002)(52536014)(7696005)(5660300002)(966005)(6306002)(54896002)(9686003)(236005)(478600001)(55016002)(7736002)(606006)(6436002)(6636002)(25786009)(66574012)(14454004)(64756008)(66556008)(6246003)(66476007)(33656002)(86362001)(66946007)(66446008)(76116006)(6506007)(2906002)(3846002)(6116002)(790700001)(15650500001)(7110500001)(2420400007)(110136005)(316002)(71200400001)(71190400001)(81156014)(81166006)(8676002)(26005)(186003)(102836004)(66066001)(53546011)(446003)(76176011)(11346002)(14444005)(486006)(476003)(8936002)(256004)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3886; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +FujwLJMPhM02BFEnvmg7IvHIzPiwNuGDSD61tWR4K4AncFgKPQE5noh5axGRW/x7QC2Q9+CRnhc8faPIlRQCnBAmfpFDP0X1ZBsM0WZDhrQKvR51Jtp4VrLwG17j92qRQIkLt4FjQSNvUqaF9K27dn4VxuGdgNuLBqm+kTPNTLt+Qw9sNn1MOBKNgTaWPGLFmyx+dTkeopwOu0UNPS4VVmogBGMX2wAUtj101eV38pVcupdRBvyIs2qpLrDYaA1akIuHZLdPA0YV6BwZBgFIV+/48UVycKrVNVRm7pr+qoCxuoYGqq0we2UdtCtmPQYJRHW1AIw4Zpn7cOVa/KLx92NuIxLY7WLjHMFRjvn92XGHCwSDUVHvm0aQ7FCpX8XVJHeEu9lVkNbB4aNHzuabhnWXjCBl/olRV6oSmklxXkiLglrlYPMs9KW7LYZDFgBOC0KHQ/Jp5QrnDlhejtZEA==
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB43669E19CC3B19C503C3D539B5970MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 989248c4-ac7d-4bd5-2476-08d74e48f8ab
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Oct 2019 12:46:01.0893 (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: JfJPH5cyAOV4h7pd423U6GjY7U2VuEOEeUsUzV1vKStd06c6PzN0nd1x7RZYu7uZX/+sWc2wtusMup/BhfVKDQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3886
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/tqUy_CUfoU1wduOR331I_A97osw>
Subject: Re: [netconf] More capabilities for ietf-notification-capabilities (WGLC)
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: Fri, 11 Oct 2019 12:46:09 -0000

I support adding these.

I think that it is plausible that a server may not support periodic subscriptions on either "candidate" or "startup" datastores, hence the ability to clearly express this in the capabilities model is important.

I think that it also has the benefit of making the model slightly more regular.

Thanks,
Rob


From: Balázs Lengyel <balazs.lengyel@ericsson.com>;
Sent: 09 October 2019 15:33
To: Netconf <netconf@ietf.org>;; Alexander Clemm <ludwig@clemm.org>;; Eric Voit (evoit) <evoit@cisco.com>;; Rob Wilton (rwilton) <rwilton@cisco.com>;
Subject: More capabilities for ietf-notification-capabilities (WGLC)

Hello,
During WGLC it was asked that  we could/should add some more capabilities to the ietf-notification-capabilities model.
In https://tools.ietf.org/html/rfc8641#appendix-A.1 there are two more error conditions mentioned.
cant-exclude
datastore-not-subscribable

The publisher might be able to declare which change types can be used in the  leaf-list excluded-change
The publisher might want to declare that not even periodic subscriptions are supported for a specific datastore. Some people stated that supporting periodic subscriptions is mandatory if RFC8641 (Yang-Push) is supported, so we should not add this capability. But is it really mandatory to support periodic subscriptions for e.g. the start-up datastore?

I intend to add these 2 to the model.

Opinions?

Regards Balazs


--
Balazs Lengyel                    Senior Specialist                       Ericsson Hungary Ltd.
Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com<mailto:Balazs.Lengyel@ericsson.com>