Re: [Nmop] [Netmo] Initial topics and areas of work

[[e-mail]]

Hi Thomas,

 

thank you for your reply and the information links listed below.

I interpret your response that you are open regarding work on external
exposure and that it could help also in incident management.

 

Currently I am looking into the work being possibly made in other IETF WG
and 

topics that are worked out in other standardization bodies e.g., BBF.

I need to dive into this.

 

 

Best Regards

 

Roland

 

 

Von: [e-mail] <mailto:[e-mail]>
<[e-mail] <mailto:[e-mail]> > 
Gesendet: Donnerstag, 4. Januar 2024 11:45
An: [e-mail] <mailto:[e-mail]> ;
[e-mail] <mailto:[e-mail]> 
Betreff: Re: [Netmo] Initial topics and areas of work

 

Dear Roland,

 

To comment on (3) Anomaly detection and Incident management.

 

The Network Anomaly Detection part relates to the following work being
introduced at ANRW in IETF 117 and at IETF 118 at NMRG and IEPG.

 

https://hal.science/hal-04307611

https://datatracker.ietf.org/meeting/117/materials/slides-117-anrw-sessb-dai
sy-practical-anomaly-detection-in-large-bgpmpls-and-bgpsrv6-vpn-networks-00

https://datatracker.ietf.org/meeting/118/materials/slides-118-nmrg-semantic-
metadata-annotation-for-network-anomaly-detection-01

https://datatracker.ietf.org/doc/html/draft-netana-opsawg-nmrg-network-anoma
ly-semantics

 

We aim to align the ietf-incident-semantic-metadata.yang with
draft-feng-opsawg-incident-management.

 

Regarding (1) YANG Telemetry/Kafka integration. The following two links,
presented at IETF 116 IEPG and throughout side meeting between IETF 115 -
118  give a high level overview. I am working on a document describing the
use case, motivation and the relationship of the various netconf wg related
documents where incremental changes to YANG push and YANG library is being
addressed.

 

http://www.iepg.org/2023-03-26-ietf116/yang.pdf

https://github.com/network-analytics/draft-daisy-kafka-yang-integration/blob
/main/draft-daisy-kafka-yang-integration-05.md

 

Some more details also here:

https://github.com/network-analytics/draft-daisy-kafka-yang-integration/blob
/main/schema-registry-yangkit-integration-01.pdf

https://github.com/network-analytics/draft-daisy-kafka-yang-integration/blob
/main/yang-push-workflow-02.pdf

https://github.com/network-analytics/draft-daisy-kafka-yang-integration/blob
/main/Zhuoyao_final_thesis.pdf

https://github.com/network-analytics/draft-daisy-kafka-yang-integration/blob
/main/INF690_presentation.pdf

 

Regarding (6) An update of operator requirements on Network Mgmt
protocols/modelling within the IETF.  E.g., something like RFC 3535-bis.

https://datatracker.ietf.org/doc/html/draft-boucadair-nmop-rfc3535-20years-l
ater

 

I fully agree with your assessment that we network operators should review
RFC 3535 and assess the conclusions in 2003 when the document was produced
and update it. For me key here is the Data Mesh integration. 20 years ago
there were no requirements that semantics need to be preserved end to end to
enable an automated data processing chain. That's what we try to address
with (1). 

 

I also agree on your assessment that information and service yang modules,
that's what I believe you meant by external exposure, will be very relevant
to integrate network management systems seamlessly and more efficiently.

 

Best wishes

Thomas

 

From: Netmo <[e-mail] <mailto:[e-mail]> > On
Behalf Of [e-mail] <mailto:[e-mail]> 
Sent: Thursday, December 7, 2023 9:20 PM
To: [e-mail] <mailto:[e-mail]> 
Subject: Re: [Netmo] Initial topics and areas of work

 

	
Be aware: This is an external email.

 

Hi Luis, hi all,

 

I like the topic (3) Anomaly detection and Incident management thinking that
it is related to an automated incident management.

Regarding the topic of adding the exposure of network capabilities /
information as candidate topic, I support this idea.

Since the charter is currently under discussion this is a valid option to be
discussed on this list before the charter is finalized.

 

Additionally, I think one can distinguish internal and external exposure.
The mechanisms could be similar. Exposure of information to external 

is in my opinion a mean of network management and operation helping the
customer and its application as well as the network provider.

It could also play a role regarding building an informative digital map (4).

 

Regarding (6) An update of operator requirements on Network Mgmt
protocols/modelling within the IETF, isn't this a task that should be
checked anyway?

I have the impression that operators have requirements for strong automation
and need to run cloud native applications ideally with an autonomous
network.

Concerning this, I think a double check of additional or updated operator
requirements should be part of the work of this group.

 

 

Best Regards

 

Roland