Skip to main content

Liaison statement
IETF Network Management OPerations Working Group LS to TMF on "TMF724A Incident Management API Profile"

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2024-05-07
From Group nmop
From Contact Mohamed Boucadair
To Group TMFORUM
To Contacts liaisons@tmforum.org <liaisons@tmforum.org>
Cc Mahesh Jethanandani <mjethanandani@gmail.com>
Warren Kumari <warren@kumari.net>
Network Management Operations Discussion List <nmop@ietf.org>
Benoît Claise <benoit.claise@huawei.com>
Mohamed Boucadair <mohamed.boucadair@orange.com>
Response Contact Mohamed Boucadair <mohamed.boucadair@orange.com>
Benoît Claise <benoit.claise@huawei.com>
Technical Contact mohamed.boucadair@orange.com
Purpose For action
Deadline 2024-07-15 Action Needed
Attachments PDF version of the LS
Body
The IETF Network Management OPerations Working Group (NMOP WG) [1] was recently
chartered by the IETF to focus on network management operations. The current
topics of focus for the NMOP WG are as follows:

* NETCONF/YANG Push integration with Apache Kafka & time series databases

* Anomaly detection and incident management

* Issues related to deployment/usage of YANG topology modules (e.g., to model a
Digital Map)

* Consider/plan an approach for RFC 3535-next (i.e., collecting updated
operator requirements for IETF network management solutions)

The NMOP WG would like to inform the TMF that the Working Group adopted the
following documents as the basis for continued work and development towards
consensus documents that may be published as RFCs at some time in the future:

* A terminology document for anomaly and incident management [2]

* A YANG model for network incident management [3]

The NMOP WG believes that this work might be relevant to the ongoing "TMF724A
Incident Management API Profile" [4] and would like to coordinate ongoing
efforts in both the IETF and TMF early in the standardization process. Such
coordination is meant to ensure that produced specifications are complementary
and soften overlapping areas (if any).

To that aim, the NMOP WG would appreciate if the TMF can provide a copy of
"TMF724A Incident Management API Profile" specification that can be made
available to the IETF participants.

We look forward fruitful collaboration between TMF and NMOP WG.

Note that the NMOP WG encourages the use of NMOP WG mailing list [5] as the
most effective and expedient way of exchanging information, answering
questions, and clarifying concerns. Also, the NMOP WG is welcoming
presentations from TMF on these matters. Requests for presentations can be sent
to the NMOP Chairs [5].

Following is the schedule of upcoming IETF meetings [6]:

* 20 July 2024 - 26 July 2024, Vancouver Canada (with online participation)

* 02 Nov 2024 - 08 Nov 2024, Dublin Ireland (with online participation)

NMOP Chairs & Area Director

Mohamed Boucadair, Benoît Claise, & Mahesh Jethanandani

References:

[1] https://datatracker.ietf.org/group/nmop/about/

[2] https://datatracker.ietf.org/doc/draft-davis-nmop-incident-terminology/

[3] https://datatracker.ietf.org/doc/draft-feng-nmop-network-incident-yang/

[4]
https://www.tmforum.org/resources/standard/tmf724a-incident-management-api-profile-v1-0-0/

[5] https://www.ietf.org/mailman/listinfo/nmop

[6] https://www.ietf.org/meeting/upcoming/