[nmrg] Re: IRSG ballot issued: <draft-irtf-nmrg-ai-challenges-06.txt> to Informational RFC

["Dikshit, Saumya" <[e-mail]>]

[Updating the To, CC to authors of draft and nmrg ]

Hi all,
Not sure, if responding here is the right context for the review with “IRSG ballot issued”. If not kindly point me the right way.

I am from AIOPs group with Aruba networks, HPE. And warming up to nmrg ai leads with this read.

Since I work with lots of telemetry from networking devices (switches, WLAN, gateways), my observations are driven accordingly.

A few observations:

1) Section 6.2 covers data collection well but stops at IPFIX and SDN-based monitoring.
    Two frameworks that are now standardized and directly relevant to the ML input challenges in Section 6.1 needs more than a mention:

  *
YANG-Push (RFC 8641) for subscription-based datastore streaming,
  *
 and BMP (RFC 7854) for continuous routing-state observation.

   Both produce the structured, schema-validated streams Section 6.1 is asking for. A sentence each would close the gap.

2) Section 4 and Sections 5-7 use "challenge" for two different things: high-level adoption obstacles in Section 4,  and specific research sub-challenges with numbered headings in 5-7.
   Expert readers will track it, but a one-sentence bridge at the end of Section 4 might be of some help
   "The following sections decompose these obstacles into research-level sub-challenges" and would help readers new to the NMRG framing.
  As a reader/implementer I got stuck with this.

3) Section 9.3 covers out-of-bounds AI outputs (bandwidth exceeding link capacity) but not the adjacent failure mode:

  *
logically valid outputs that are operationally dangerous in context, like a correct route computation that induces a forwarding loop.

   This is distinct from adversarial ML (Section 9.2) and deserves explicit mention with a pointer to the verification/sandbox work already present in Section 5.5.

I support publication.

Best regards,
Saumya
From: IESG Secretary <[e-mail]>
Date: Thursday, 13 August 2026 at 1:18 PM
To: The IRSG <[e-mail]>
Cc: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Subject: [nmrg] IRSG ballot issued: <draft-irtf-nmrg-ai-challenges-06.txt> to Informational RFC

Evaluation for <draft-irtf-nmrg-ai-challenges-06.txt> can be found at
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-irtf-nmrg-ai-challenges/__;!!NpxR!mb3Lq7TV_7_wrRLrHAd5eiXR_lb53t4A3IhxZCYjJjICMMcnOUs8o2W5oeyWyPfCnY5IrWj3GKmMN1KLkJiIhl6DzQ$

Ballot expires on: 2026-08-27 00:00 PDT

Needs a YES.



_______________________________________________
nmrg mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]