Return-Path: X-Original-To: nmrg@mail2.ietf.org Delivered-To: nmrg@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0CFE411C2063F for ; Wed, 22 Jul 2026 03:22:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784715743; bh=jA19gbCXSZ7kTffJuW2OwXT/AbR7vY3uay7Ov8tJ0wo=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=elR49GTONHli3f6MwMdbDY8U/hW0Q4fzjjn8+WUxHeNotp2Jijk6gP0fQib/EZatM 67DMyM7inkq1eIzZQEI8bg3ZGWNMALQbhj8fup6tyIE6j8G8Wtd11tEZN+4uRiL/c+ QpQlHlISaS31PYbkpBYL0B73hSYhpm4KBKzvG3mI= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cs.fau.de Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vf9JWAXtGmrE for ; Wed, 22 Jul 2026 03:22:21 -0700 (PDT) Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 45FE011C20527 for ; Wed, 22 Jul 2026 03:22:18 -0700 (PDT) Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4h4r0F4ym7z1RDZ5; Wed, 22 Jul 2026 12:22:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.fau.de; s=r20250630-faui40; t=1784715731; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vtWuQi5ih2ps78DcjS/lcmE7i/WrAd4M7YKVeohwOXE=; b=dkK5T78UubS9pMhbFkr8BGo0cLYyw/Pivzkr/3Sg6Nm+ozhBmmjkGjFAMhiIkqHSBa7FR7 AWaNntWrRbn/UYwC2AYmx95otGO9u10t88mR5FSJj9gSavIu6cF+3umLWPGBtC2Aveyx3n DjIgKm0djJI0EjO8n5WIIg6IPhW7U5oaVjVOzjcaUpHLr2/RKrjgHxVe+pI+8pRU/CVCkH W3WkiisuBnOUzr62WgbOcOctYRrDOQm7ZoV5UgP1wty5mUylIGVagOODRxcH8/sBbQxXZH tf1ELWFa6EIkhz/wDQ2FvlUXSZzOf1lggpVDZ+VPvQKCpsw/MFdfo4Ux+3dmjw== Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4h4r0H2cCgzl4TN; Wed, 22 Jul 2026 12:22:07 +0200 (CEST) Date: Wed, 22 Jul 2026 12:22:07 +0200 From: Toerless Eckert To: Mahesh Jethanandani Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: Message-ID-Hash: 3J3CKLXQOOAOXV3SDKTBSHEVJEIPXNV2 X-Message-ID-Hash: 3J3CKLXQOOAOXV3SDKTBSHEVJEIPXNV2 X-MailFrom: eckert@i4.informatik.uni-erlangen.de X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nmrg.irtf.org-0; header-match-nmrg.irtf.org-1; header-match-nmrg.irtf.org-2; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Roland.Schott@telekom.de, danvoyerwork@gmail.com, ainetops@ietf.org, nmop@ietf.org, opsawg@ietf.org, nmrg@irtf.org X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Bnmrg=5D_Re=3A_=5BOPSAWG=5DRe=3A_=5Bainetops=5D_Re=3A_AIOPS_Side?= =?utf-8?q?_Meeting_=5BWas_Re=3A_Agenda_for_the_Side_Meeting=3A_AI-Driven_Ne?= =?utf-8?q?twork_Operations_=E2=80=94_IETF_126=2C_Fri_24_Jul=2C_08=3A00_CEST?= =?utf-8?q?=5D?= List-Id: Network Management Research Group discussion list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: [adding NMRG] Thanks, Mahesh Yes, indeed, NMRG meeting starting at 9AM, so lets try to get the most out = of the first hour of our side-meeting at 8AM. There are a couple of documents proposed/discussed for the NMRG meeting including yours truly dr= aft-cxxx-nmrg-ai4ibn-00 that should be also of interest to folks interested in AINETOPS. Even more so, similar to how NMRG work product (RFCs) was a justification = in support of chartering ANIMA (by Benoit back then), such work in NMRG could equally support justifying AINETOPS - or help it to scope. And that's definitely al= so a question i would like to raise in NMRG: "which of the stuff here in NMRG do you see of interest to you (when you ar= e an operator specifically) to be brought to the IETF, specifically a group scoped such = as proposed for AINETOPS". So maybe we'll get even more time and interest in the topic, even if some of of it will be in NMRG on friday. But there are a lot of operator participan= ts in there. Cheers Toerless =20 On Wed, Jul 22, 2026 at 12:02:17PM +0200, Mahesh Jethanandani wrote: > Hi Dan, et al,

Based on talking to quite a f= ew of you, there is clearly a lot of interest in having the meeting. We wil= l therefore go ahead and have the meeting.

A few h= ave indicated a conflict starting at 9 am. I expect that we will start losi= ng the quorum by that time. So participants, should plan on getting a few c= ore things sorted out in the first hour itself. I will hang around after th= e first hour.

Look forward to seeing you all on Fr= iday.

Cheers.

Mahesh Jethanandani
mjethanandani@gma= il.com

On Jul 22,= 2026, at 9:31=E2=80=AFAM, Roland.Schott@telekom.de wrote:

=EF=BB=BF >=20 > >=20 >=20 >
> Hi Dan,
>
>
>
>
> I want to meet with Mahesh to clarify, if I can support.
>
>
>
>
> In case community has interest we will find a way to run it.
>
>
>
>
> Best Regards
>
>
>
>
> Roland 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Von: Dan Voyer IETF <danvoyerwork@gmail.com>
> Gesendet: Mittwoch, Juli 22, 2026 9:26 AM
> An: Mahesh Jethanandani <mjethanandani@gmail.com>
> Cc: ainetops@ietf.org <ainetops@ietf.org>; nmop@ietf.org <= ;nmop@ietf.org>; opsawg <opsawg@ietf.org>
> Betreff: [ainetops] Re: [OPSAWG]AIOPS Side Meeting [Was Re: Agenda= for the Side Meeting: AI-Driven Network Operations =E2=80=94 IETF 126, Fri= 24 Jul, 08:00 CEST] >
 
>
>
H Mahesh,
>

>
>
Is the side-meeting going or did you shut it down since = no one took charge ?
>

>
>
And, perhaps since you proposed that side-meeting, is th= ere any possibility that you run it ? 
>

>
>
Dan
>
>
On Sun, Jul 19, 2026 at 9:08=E2=80= =AFPM Mahesh Jethanandani <mj= ethanandani@gmail.com> wrote:
>
>
Hi All,
>

>
>
When I proposed the AIOPS side meeting, I aske= d if anyone was willing to step up and fill the roles needed to run it. To = date, no one has volunteered for any of them. I understand the turnaround h= as been short, but without these roles > filled, the meeting has no one driving it and won't be worth holding. >

>
>
If you're a would-be proponent and want to see= AIOPS work happen in the IETF, this is the moment to step up:
>

>
>
Take charge of the agenda
>
Work the draft of a problem statement
>
Own the pen on the charter text
>
Show up and demonstrate real interest
>

>
>
If a core group hasn't formed by Wednesday, Ju= ly 22, I will cancel the side meeting.
>

>
>
Cheers,
>

>
>
>
On Jul 13, 2026, at 9:16=E2=80=AFPM, Mahesh Je= thanandani <mjethanandani@gmail.com> wrote:
>

>
>
> Volunteers needed to help run the meeting
>
> ------------------------------------------
>
> A few operational roles are still open for running this session - separat= e
>
> from chairing the proposed working group itself. Room capacity is limited= ;
>
> preference for in-room seating will be given to those who take one of >
> these on:
>
>
>
>
>   - Co-chair (checklist owner): tracks the Part B checklist live so = the
>
>     co-chair can stay focused on the room
>
>   - Co-chair (clock & consensus): runs the clock at each agenda-= block
>
>     boundary and calls rough consensus alongside the co-chair >
>   - Notes-pad owner: opens a shared pad before the meeting and captu= res
>
>     the roll call, deliverables, and objections live
>
>   - Jabber/WebEx monitor: relays remote comments and hands into the = room
>
>     queue
>
>   - Breakout group leads (4 needed): one each for YANG data models,<= /div> >
>     protocol extensions, MCP, and BCP/governance, to keep the 0= 9:10
>
>     deliverables breakout focused and report back
>
>   - Charter text owners (2 needed): own the charter text draft and >
>     drive it toward consensus, on-list before the next meeting = and through
>
>     to a final version after
>
>

>
>
>
> Mahesh Jethanandani
>
> mjethanandan= i@gmail.com
>
>
>
>
>
>
>
>
>
>

>
>
>

>
>
______________________________________________= _
> OPSAWG mailing list -- opsawg@ietf.org
> To unsubscribe send an email to > opsawg-leave@ietf.org
>
>
>
>=20 >=20 >
> _______________________________________________ > OPSAWG mailing list -- opsawg@ietf.org > To unsubscribe send an email to opsawg-leave@ietf.org --=20 --- tte@cs.fau.de