Re: [Netmo] Initial topics and areas of work

Thomas.Graf@swisscom.com Wed, 22 November 2023 06:52 UTC

Return-Path: <Thomas.Graf@swisscom.com>
X-Original-To: netmo@ietfa.amsl.com
Delivered-To: netmo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89044C14CE4A; Tue, 21 Nov 2023 22:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 CLyiBBk7JSEI; Tue, 21 Nov 2023 22:52:02 -0800 (PST)
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 AFA68C14CE3F; Tue, 21 Nov 2023 22:52:00 -0800 (PST)
Received: by mail.swisscom.com; Wed, 22 Nov 2023 07:51:57 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=swisscom.com; s=iscm; t=1700635917; bh=yRmgjbW7xbjYHkf0vAAw8on7OXfesZqFQ6oun6AQlug=; h=From:To:Subject:Date:References:In-Reply-To; b=stGUGg11zQWVo/nQzFOpaI5NRzX2u1BFiLBsa9QTpIeErnBhdwW2V0dSa6UhAw+j4 TR+Xi+fRIZbztwneJn4mH3+wph8xuPoYGG9TFnbSA+KfSblGGT/Ld8wRf2Iz6/woQb gEI+TkOprZDLj31YdO355N1L0RUiF2qIfLO6qTSBtM7RgtTtxrTenbooHHR0O8aMgO 7aJhcS28vK0HTIzsoi3dAyuvoGHEljaMGuRvOBufRC848m6quLX/A+xEouvJqPO+s2 SDugxjGngx3Mrx/eh/tp1kT+pC5wtaTcTIdSMD5WdABRgc+qFYYE05l7UE5T1jOtmc b0RvI+EaSEJVg==
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----=_Part_61011_249617744.1700635917127"
From: Thomas.Graf@swisscom.com
To: rwilton=40cisco.com@dmarc.ietf.org, netmo@ietf.org
Thread-Topic: Initial topics and areas of work
Thread-Index: AdoZRUZyn3d381y3R22nWwHOxFxMVADyUfmQ
Date: Wed, 22 Nov 2023 06:51:54 +0000
Message-ID: <b98743858c3441ceabf9af0be9ecee42@swisscom.com>
References: <BY5PR11MB41960A04DBEF203F811881BEB5B7A@BY5PR11MB4196.namprd11.prod.outlook.com>
In-Reply-To: <BY5PR11MB41960A04DBEF203F811881BEB5B7A@BY5PR11MB4196.namprd11.prod.outlook.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=d49e3854-f4a6-4f70-b4b5-d1cc74fd9f09; 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=2023-11-22T06:38:51Z; 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-Mailer: Totemo_TrustMail_(Notification)
X-Trustmail: processed
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmo/LQsmP58CXu1ux5nRiTXIjOrXWkY>
Subject: Re: [Netmo] Initial topics and areas of work
X-BeenThere: netmo@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Management Operations <netmo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmo>, <mailto:netmo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmo/>
List-Post: <mailto:netmo@ietf.org>
List-Help: <mailto:netmo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmo>, <mailto:netmo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2023 06:52:06 -0000

Dear colleagues,

Thanks a lot Rob for putting the list together. 

(1) YANG Telemetry/Kafka integration
    => You are correct that we progressed here already quiet far we have a cross functional team working on implementation and identifying and addressing gaps as we go along. As suggested by Med to Alex, I intend to write a requirement document similar to the one pager here https://github.com/network-analytics/draft-daisy-kafka-yang-integration/blob/main/draft-daisy-kafka-yang-integration-05.md and what Jan did here https://datatracker.ietf.org/doc/html/draft-lindblad-tlm-philatelist with all the references to the existing draft documents in netconf for IETF 119. That will help to have overall overview and how these existing documents are related. 

(3) Anomaly detection and Incident management
    => You are correct that we are in incubation state. We showed at IEPG and NMRG the first document and an example application in the hackathon this IETF. We will continue and update the document by IETF 119 and possibly by IETF 120. latest 121 having an open-source implementation validating the proposal. The work relates to the Network Anomaly Detection paper presented at the ANRW at IETF 117, https://anrw23.hotcrp.com/doc/anrw23-paper8.pdf and is going to be extended and submit to IEEE Transactions on Network and Service Management to gain more traction.

Regarding Network Connectivity Service SLI/SLO analytics use case. With draft-ietf-ippm-pam and draft-clemm-opsawg-pam-ipfix, IPPM and OPSAWG has already documents describing the implementation aspect. What I miss is a requirement document describe the operator needs. At Swisscom I already have architecture documents describing requirements and how the Network Connectivity Service SLI/SLO use cases can be implemented and what operational network telemetry metrics are needed. Where the Network Anomaly Detection use case focuses on state change without having an intend, SLI would be the state of a Network Connectivity Service and SLO the state objective. Network Connectivity Service SLI/SLO complement the efforts in the Digital Map. I would love to present at IETF 119 my view on this topic and get feedback from other network operators and possibly working by IETF 121 on a requirement document. 

Best wishes
Thomas

-----Original Message-----
From: Netmo <netmo-bounces@ietf.org> On Behalf Of Rob Wilton (rwilton)
Sent: Friday, November 17, 2023 12:53 PM
To: netmo@ietf.org
Subject: [Netmo] Initial topics and areas of work

Hi,

As per my introduction email, it would be helpful to have list of initial topics and work that this WG will focus on progressing.  This doesn't mean that all agenda time and presentations need to be focussed solely on these topics, but it means which areas the WG intends to primary concentrate on (e.g., if it adopts drafts).

Ideally, I think that I'm looking for the top three topics for the WG to focus on, but could be more or less, depending on feedback.

Based on the recent side meetings, and other topics that have come up in discussion, I think that some potential topics could be:

(1) YANG Telemetry/Kafka integration
(2) Issues related to mapping configuration, and agreement on north bound interfaces from the device (protocol and model families)
(3) Anomaly detection and Incident management
(4) Issues related to deployment/usage of YANG topology modules (e.g., digital map)
(5) Controller architectures for management of pluggable optics (there are several drafts currently in CCAMP)
(6) An update of operator requirements on Network Mgmt protocols/modelling within the IETF.  E.g., something like RFC 3535-bis.

Are there other topics that the operators are interested in the near term, and which of these topics are most important to focus on?

Regards,
Rob

-- 
Netmo mailing list
Netmo@ietf.org
https://www.ietf.org/mailman/listinfo/netmo