[netconf] Re: Status update of draft-ietf-netconf-adaptive-subscription-05
Thomas.Graf@swisscom.com Fri, 19 July 2024 14:39 UTC
Return-Path: <Thomas.Graf@swisscom.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 18C2AC14F60B; Fri, 19 Jul 2024 07:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.393
X-Spam-Level:
X-Spam-Status: No, score=-4.393 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=swisscom.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o_Khtj5RH6D9; Fri, 19 Jul 2024 07:39:28 -0700 (PDT)
Received: from mail.swisscom.com (mailout110.swisscom.com [138.188.166.110]) (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 7A4EDC14F619; Fri, 19 Jul 2024 07:39:27 -0700 (PDT)
Received: by mail.swisscom.com; Fri, 19 Jul 2024 16:39:20 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=swisscom.com; s=iscm; t=1721399960; bh=YW7BvZyftal13/bt/Mm9U3hcrslcTxnG7XGbpdSxhKA=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=ibfwpYWiiEZjVgMIf1Ly9Y+2XJ8FHvHy6LyTZL4O/unzihY8LHAmk9zmYDJ3i1RXy nf9CkMozkBqb/E58T1OCsazBh0+tkOzP6G90/VehNb7TiI9hp6Ad9Qpwo0oDBe9CxC gDVaSSBjDe6zG3XXE1Ez66tGT/AcxWy2ziW5jYD5dwcTPwd51eRHkGu9BgDIpU9J7k 3uHY579yEM1l4Sf6xGvHSNJyk7kUxiTKqVhuhoKYJuV35gik957zPTgHiioBI6cmzG 5fel4KW0cQO/gFJriuley/9afrasGsA+gkRc/m5T43IiSqZnAqo29GtYy9T8qw66zR rXmYWdalKz3Pw==
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----=_Part_333822_264856792.1721399959641"
X-Mailer: Totemo_TrustMail_(Notification)
From: Thomas.Graf@swisscom.com
To: maqiufang1@huawei.com, netconf@ietf.org
Thread-Topic: Status update of draft-ietf-netconf-adaptive-subscription-05
Thread-Index: AdrY2XlRjtaXyhOTQEmeKd3yTveCfwAQAIawABsiFwAAGEtaIA==
Date: Fri, 19 Jul 2024 14:39:17 +0000
Message-ID: <ce9fa01e5b8e454b8b496bb434a631d2@swisscom.com>
References: <21854d6e65f14dd9b05dbb0309e160f2@huawei.com> <3b6b9a540fbb4ff4a58db8668d7cd4ed@swisscom.com> <620fc56adbca4b799bd5bd8ca00a6b0e@huawei.com>
In-Reply-To: <620fc56adbca4b799bd5bd8ca00a6b0e@huawei.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ActionId=6f368d50-9021-4dc7-a4cd-1897ac1adbdf;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ContentBits=0;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Enabled=true;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Method=Standard;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Name=C2 Internal;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SetDate=2024-07-19T14:23:14Z;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SiteId=364e5b87-c1c7-420d-9bee-c35d19b557a1;
x-originating-ip: [138.188.161.184]
X-CFilter-Loop: Reflected
X-Trustmail: processed
Message-ID-Hash: NRFLULQD4RLU57Y3UTR3Y2YBTQR46YOW
X-Message-ID-Hash: NRFLULQD4RLU57Y3UTR3Y2YBTQR46YOW
X-MailFrom: Thomas.Graf@swisscom.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: netconf-chairs@ietf.org, draft-ietf-netconf-adaptive-subscription@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] Re: Status update of draft-ietf-netconf-adaptive-subscription-05
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/jdNYNlm8oHnpuqCwPdIfu5svD8w>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>
Dear Qiufang, Thanks a lot for the feedback and sharing the details on the IETF 113 hackathon project. This is exemplary. Qiufang> Would you suggest us to add an "implementation status" section to document related information in the draft? That would be nice. Especially with a link to a repository where an interested implementer can look at the running code. Qiufang> personally I think it would be good if it could be validated using your implementation. We did implement this mechanism as demos and also in our products, however, I am unsure currently if we are able to open source it and if our existing implementation can completely fit into your project. Let me check internally, and I will get back to you then. I appreciate that. We have already published (https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/120/Hackathon/yp-test-suite.tar.gz) a python script which creates YANG-Push subscriptions based on ietf-subscribed-notifications and captures the ietf-yang-push notifications. See https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/120/Hackathon/yp_test_suite_report_20240709_152636.log and https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/120/Hackathon/yp-test-20240709-152636.pcap. We also published a network telemetry test automation https://github.com/pmacct/pmacct/pull/774 recently. It covers also the data collection transformation into Apache Kafka message broker. Currently we are supporting BMP and IPFIX. We plan to start working on YANG-Push integration as well. I would love to have a brief conversation with you and Benoit on this. The aim of these activities is to improve the quality of the documents, its implementations and make it accessible to vendors, operators and universities equally. Best wishes Thomas From: maqiufang (A) <maqiufang1@huawei.com> Sent: Friday, July 19, 2024 1:39 AM To: Graf Thomas, INI-NET-VNC-HCS <Thomas.Graf@swisscom.com>; netconf@ietf.org Cc: netconf-chairs@ietf.org; draft-ietf-netconf-adaptive-subscription@ietf.org Subject: RE: Status update of draft-ietf-netconf-adaptive-subscription-05 Be aware: This is an external email. Hi, Thomas, Thanks a lot for the valuable comments, please see inline. From: Thomas.Graf@swisscom.com<mailto:Thomas.Graf@swisscom.com> [mailto:Thomas.Graf@swisscom.com] Sent: Thursday, July 18, 2024 10:08 PM To: maqiufang (A) <maqiufang1@huawei.com<mailto:maqiufang1@huawei.com>>; netconf@ietf.org<mailto:netconf@ietf.org> Cc: netconf-chairs@ietf.org<mailto:netconf-chairs@ietf.org>; draft-ietf-netconf-adaptive-subscription@ietf.org<mailto:draft-ietf-netconf-adaptive-subscription@ietf.org> Subject: RE: Status update of draft-ietf-netconf-adaptive-subscription-05 Dear Qiufang, Thanks a lot for the update. I agree that the document is in a very good shape and addresses network operators needs for on demand fine grained network telemetry data. [Qiufang] Thanks, glad to know;-) I reviewed the document and have two comments. Editorial: I suggest to change "Applying adaptive subscription allows publishers to automatically adjust the period and volume of telemetry data sent to receivers." to "Applying adaptive subscription allows publishers to automatically adjust the subscription period dynamically based on pre-defined threshold for finer grained network telemetry data sent to receivers." [Qiufang] Sure, the proposed text looks good to me. In https://datatracker.ietf.org/doc/html/draft-ietf-netconf-adaptive-subscription-05#section-2.2 you are mentioning "Note that the adaptive subscription may not be supported by every YANG datastore node." I suggest to augment ietf-notification-capabilities as defined in https://datatracker.ietf.org/doc/html/rfc9196#section-5 to describe which YANG nodes this can be applied to. From a workflow perspective, that matches what we described in https://datatracker.ietf.org/doc/html/draft-ietf-nmop-yang-message-broker-integration-03#section-4.1. [Qiufang] This makes sense to me, and good point! Will augment the "per-node-capabilities" in the system-capabilities yang module with the support of adaptive-subscription. I see that the document is missing a implementation status section (https://datatracker.ietf.org/doc/html/rfc7942) nor in the data tracker has under "additional resources" a "related implementations" link. [Qiufang] Actually we used to have a hackathon project on this work around more than two years ago, we were targeting a real campus network scenario where gRPC based adaptive telemetry is used to collect data from AP devices, it turns out that adaptive subscription can analyze the WIFI degradation events with the minimum amount of push data, and you might want to refer to the presentation slides for some more details: https://github.com/IETF-Hackathon/ietf113-project-presentations/blob/main/ietf-hackathon-adaptive-subscription.pdf. And demo implementation results and learned experience were also brought back to the WG to better refine the document. Would you suggest us to add an "implementation status" section to document related information in the draft? We will consider adding this in the next revision. I encourage to provide an open-source reference implementation and would support and contribute in its validation as part of our "Validate Configured Subscription YANG-Push Publisher Implementations" activities at the IETF hackathon (https://wiki.ietf.org/en/meeting/120/hackathon) I believe this helps to improve the quality of the described standard. [Qiufang] Happy to know your continued hackathon project on yang-push notification validation, it looks good! We've defined a new "adaptive-period-update" state change notification in the draft, personally I think it would be good if it could be validated using your implementation. We did implement this mechanism as demos and also in our products, however, I am unsure currently if we are able to open source it and if our existing implementation can completely fit into your project. Let me check internally, and I will get back to you then. Best wishes Thomas Best Regards, Qiufang From: maqiufang (A) <maqiufang1=40huawei.com@dmarc.ietf.org<mailto:maqiufang1=40huawei.com@dmarc.ietf.org>> Sent: Wednesday, July 17, 2024 11:38 PM To: netconf@ietf.org<mailto:netconf@ietf.org> Cc: netconf-chairs@ietf.org<mailto:netconf-chairs@ietf.org>; draft-ietf-netconf-adaptive-subscription@ietf.org<mailto:draft-ietf-netconf-adaptive-subscription@ietf.org> Subject: [netconf] Status update of draft-ietf-netconf-adaptive-subscription-05 Be aware: This is an external email. Hi, all, As adaptive-subscription document is not going to be presented in this IETF NETCONF session and authors of WG documents are requested to provide a status update to the WG, this email is to give a status-update of this work. The authors have submitted -05 before the submission window, and the main updates are as follows: * Move use cases for adaptive subscription into a separate appendix section; * Define adaptive-subscription specific RFC errors for "modify-subscription" RPC, in addition to the existing ones for "establish-subscription"; * Add "Subscription State Change Notifications" new section to align with the YANG module definition; * Use the security considerations template described in rfc8407bis; * Other editorial updates. There are not known open issues currently and the authors feel this document is close to WGLC, but would really appreciate any feedback from the WG. Thanks a lot! Best Regards, Qiufang // on behalf of authors
- [netconf] Status update of draft-ietf-netconf-ada… maqiufang (A)
- [netconf] Re: Status update of draft-ietf-netconf… Thomas.Graf
- [netconf] Re: Status update of draft-ietf-netconf… maqiufang (A)
- [netconf] Re: Status update of draft-ietf-netconf… Thomas.Graf