Re: [netconf] WGLC for draft-ietf-netconf-notification-capabilities

Balázs Lengyel <balazs.lengyel@ericsson.com> Wed, 11 September 2019 10:18 UTC

Return-Path: <balazs.lengyel@ericsson.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 5CF8B12085D for <netconf@ietfa.amsl.com>; Wed, 11 Sep 2019 03:18:26 -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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.001, HTML_MESSAGE=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 (1024-bit key) header.d=ericsson.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 MMdRGetlbatv for <netconf@ietfa.amsl.com>; Wed, 11 Sep 2019 03:18:24 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30071.outbound.protection.outlook.com [40.107.3.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5F41120854 for <netconf@ietf.org>; Wed, 11 Sep 2019 03:18:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cgw/SdL2wTnUxzbAOvAOwOfEZbaxftNkcPVxLrSmv6mE+TYPiUN+fZxU6M0e/B0VJb0t8v6W2aqQ7sQ8XiD4jfsA9i1qiRdaBizQCvwtJNRAWxYseWhRnOznFz0oGXHy/CisimDedcHLBO55D2/zypkUHnLelKwH9SDXuyZpaOevGjeuEdaVaELCZJFhGJY6HGhWcyHI9vzgpOjZL3U20/5RBpXbLEErwGuAln6kA8I6Sogqnr7Y3xk2vEqTcMUr5WQUcyB7HigCRxqf5IYZ9xrxMYsITglLR210X040+vrQ/J46YTHGCPgzCS9fb6Wkm278oR6VkZb8RBMixiZMVA==
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=zuY0dRsos3gXi1YkpxDEmyV2alvPE2N2faTKH3n1Yr4=; b=lhvNGRfzx6y3zpl4t2hucXfFEX5KkEPS9Wk+kUJsiHXZJJcF1zKr+EBmrWeXWwYkGbr+b00qmDoU76S94uHjqbqylPvjakwrd3K9MdTWET3JyRfLQD6GGUI6soP1HwvI0Zb2ndDdtzHA/d8+5RXtF5PX3LEfaLkiQPAsYLNc1U5UhgDUem8+3laP8MN3r9pPJ4XA2WAaQi4rF3KQvcWld56L8QTeR080D8iI7sHOfOfpId9ij1GB3MOH7SnOL06W3y8bSs1lH0Vr5viahhjWecCtjywLTJVXmPSImMXboPHHNESWfeBpmRVAPZGY0nKxT0ieSeE6az0MrEC1nVed+Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zuY0dRsos3gXi1YkpxDEmyV2alvPE2N2faTKH3n1Yr4=; b=HlT1l6B/etXDO9XLSQE+ij6RQ/TzHbhpYZo11LliBBFMOGCOC+J3SjsCZnpRFgZOVB2TU/YKE5dI0QVvWV5QbfMdzYDCXGl/xQFo76Xoe5+PY9LfooyVY/pC6AXWZ+Ka4mOpjxZZV6l3ZO2wsbh0aXba2sxbMDWGcTU8BOXoFwE=
Received: from VI1PR0701MB2286.eurprd07.prod.outlook.com (10.169.137.153) by VI1PR0701MB2990.eurprd07.prod.outlook.com (10.173.72.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.6; Wed, 11 Sep 2019 10:18:21 +0000
Received: from VI1PR0701MB2286.eurprd07.prod.outlook.com ([fe80::f44b:854c:51cf:c69f]) by VI1PR0701MB2286.eurprd07.prod.outlook.com ([fe80::f44b:854c:51cf:c69f%7]) with mapi id 15.20.2263.015; Wed, 11 Sep 2019 10:18:21 +0000
From: =?utf-8?B?QmFsw6F6cyBMZW5neWVs?= <balazs.lengyel@ericsson.com>
To: Qin Wu <bill.wu@huawei.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, Netconf <netconf@ietf.org>
Thread-Topic: [netconf] WGLC for draft-ietf-netconf-notification-capabilities
Thread-Index: AdVoPX4GqtZOaS4LR8qYtgUDtxKZ8QAMsgqg
Date: Wed, 11 Sep 2019 10:18:21 +0000
Message-ID: <VI1PR0701MB228658B741BB2E978C318267F0B10@VI1PR0701MB2286.eurprd07.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAA92F6FCF@dggeml511-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA92F6FCF@dggeml511-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=balazs.lengyel@ericsson.com;
x-originating-ip: [89.135.192.225]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cfcfffdf-840e-452d-4359-08d736a15f68
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(49563074)(7193020); SRVR:VI1PR0701MB2990;
x-ms-traffictypediagnostic: VI1PR0701MB2990:
x-microsoft-antispam-prvs: <VI1PR0701MB29906AB7CC1BCCF4A0C3D0CFF0B10@VI1PR0701MB2990.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0157DEB61B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(366004)(396003)(39860400002)(136003)(199004)(189003)(2420400007)(76116006)(15650500001)(478600001)(7696005)(66446008)(64756008)(86362001)(9326002)(606006)(26005)(6246003)(110136005)(229853002)(85182001)(25786009)(99286004)(53546011)(6506007)(8936002)(76176011)(53936002)(7110500001)(7736002)(33656002)(52536014)(74316002)(9686003)(5660300002)(3846002)(6116002)(55016002)(790700001)(236005)(102836004)(54896002)(2906002)(6306002)(85202003)(6436002)(66066001)(446003)(256004)(14444005)(476003)(66616009)(486006)(11346002)(14454004)(71200400001)(66556008)(186003)(71190400001)(316002)(99936001)(81156014)(81166006)(66476007)(8676002)(66946007); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0701MB2990; H:VI1PR0701MB2286.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: P/OPq+PDjDHCwZKy4BfTkmw2aob+rQ+VzPwVBvMVlsId6SwiNiuyA0tPRnwA2/zvLeg1ElI9zaiJUwgAjaOqEM+LkfEzl9HXRAuVV1UJk+yG2L4BtRwjbRh/FtaKDD96MqxkYTVQytlK3EzVv9pbWsK4i0qAJ8VIVU1se/pNnSQfqC1guPimRerQVmITo9F/Fl5kAHmafR6lFFAC1/TnBC0a+Z5o9lOO3ynRF5E9r60bQ0LmbrVnGZgcqxO7ga5MMmbm9S1m8XI7nN8eDW/Qdc0j+xcnFBaS4WajKWQ/FC2NdiZt+jTL79i2yPGF3cIKN2l1NFhqqafV38deLGlOhkUez3AVcJIFtxaf4jgLMEw/sI0vpDj8xID0RZIWWtG21NjywRxj3U7zNUIjpMpXZAbs40HxYwCrgg8jap2Ga/0=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0161_01D5689A.FF2E62E0"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cfcfffdf-840e-452d-4359-08d736a15f68
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Sep 2019 10:18:21.3228 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rQ4Qll9T17JQaJZqrfW5uXr8swj+hpvghoocVL3OVMu4Tpn8ZcFRSkQUL7aCBwYKjhVQVq2ijpe60PzxNQk568pdLfDjSHri86jvtIidniI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2990
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/eZFmnbANP0GY8EksodpE4gipf9o>
Subject: Re: [netconf] WGLC for draft-ietf-netconf-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: Wed, 11 Sep 2019 10:18:26 -0000

Hello Qin,

I did not add module level capabilities because:

In 99% of the cases module level capabilities can be handled  defining per-node-capabilities on one or a few top level containers, lists.   
No one proposed a use-case that could not be handled by the current YAM (Yang Module).
Adding a 4th level beside server/datastore/per-node would make the solution more complex, more difficult to understand.
Regards Balazs

 

From: netconf <netconf-bounces@ietf.org> On Behalf Of Qin Wu
Sent: 2019. szeptember 11., szerda 3:11
To: Mahesh Jethanandani <mjethanandani@gmail.com>om>; Netconf <netconf@ietf.org>
Subject: Re: [netconf] WGLC for draft-ietf-netconf-notification-capabilities

 

Support to move this work forward,  one quick question is 

Since you have datastore level and node level capability, Is there any reason why module level capability is not included?

 

-Qin

发件人: netconf [ <mailto:netconf-bounces@ietf.org> mailto:netconf-bounces@ietf.org] 代表 Mahesh Jethanandani
发送时间: 2019年9月11日 6:39
收件人: Netconf < <mailto:netconf@ietf.org> netconf@ietf.org>
主题: [netconf] WGLC for draft-ietf-netconf-notification-capabilities

 

Authors have published -04 <https://tools.ietf.org/html/draft-ietf-netconf-notification-capabilities-04>  version of the draft, which addresses comments they received in IETF 105. If you provided comments please check to make sure your comments have been addressed. At this point, the authors believe that the document is ready for WGLC.

 

This therefore starts a two week LC, ending on September 24th. Please provide any technical comments you might have on the document. If you believe the document is not ready for LC, please state your reasons.

 

We will issue a IPR poll separately. 

 

Mahesh & Kent (as co-chairs)