[nmrg] Notes of the NMRG meeting @ IM 2017, May 11th 2017

Lisandro Zambenedetti Granville <granville@inf.ufrgs.br> Fri, 12 May 2017 22:03 UTC

Return-Path: <granville@inf.ufrgs.br>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53AE612941C for <nmrg@ietfa.amsl.com>; Fri, 12 May 2017 15:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.303
X-Spam-Level:
X-Spam-Status: No, score=-2.303 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nS5NA7VLe6K for <nmrg@ietfa.amsl.com>; Fri, 12 May 2017 15:03:20 -0700 (PDT)
Received: from smtp.inf.ufrgs.br (smtp.inf.ufrgs.br [143.54.11.23]) by ietfa.amsl.com (Postfix) with ESMTP id 7A111129438 for <nmrg@irtf.org>; Fri, 12 May 2017 14:59:06 -0700 (PDT)
Received: from [10.5.1.204] (unknown [201.140.212.141]) by smtp.inf.ufrgs.br (Postfix) with ESMTPSA id E8FF4120705 for <nmrg@irtf.org>; Fri, 12 May 2017 18:59:02 -0300 (BRT)
From: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 12 May 2017 22:58:30 +0100
References: <16DFD8DA-7E59-47BA-9F0A-9624018B1D6C@inf.ufrgs.br>
To: nmrg@irtf.org
In-Reply-To: <16DFD8DA-7E59-47BA-9F0A-9624018B1D6C@inf.ufrgs.br>
Message-Id: <4B46753A-E371-4513-B9AA-E600C7AA5F6E@inf.ufrgs.br>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/jXWrJlTaAzW4oz0gGjA9lWQWb-c>
Subject: [nmrg] Notes of the NMRG meeting @ IM 2017, May 11th 2017
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 May 2017 22:03:22 -0000

Dear NMRG subscribers,

Please find below the notes from the NMRG meeting at IM 2017.

Best regards,

Laurent and Lisandro

-------------------------------------------------------------

NMRG meeting @ IM 2017

May 11th 2017
Room Milão I - 12:30 ~ 14:00

Attendees: 
- Marc-Olivier Pahl, TUM
- Joe Betes, Aerospace
- Mohamed Faten Zhani, ÉTS Montreal
- Imen Grida Benyahia, Orange
- Roberto Riggio, CREATE-NET
- Alexander Clemm, Huawei
- Atay Ozgovde, Galatasaray Univ.
- Laurent Ciavaglia, Nokia - Bell labs
- Lisandro Zambenedetti Granville, UFRGS
- (remote) Ali Hamidian, Huawei

---

. Laurent mentions two initial working topics, to discuss:
 - Intent-Based Networking (IBN)
 - Autonomic networking (AN)

...

. Alex
 - A position document, to put the concepts of IBN, PBNM (policy-based
   network management), and service management in perspective, is important
   to clarify these concepts and their relationship with each other

. Imen
 - What’s the requirements to realize IBN?
 - What’s the relationship with autonomic management?
 - A second outcome should be so to address these two questions too 

. Atay - Examples of IBN would be beneficial to clarify the concept

. Roberto - E.g., a taxonomy of intents

. Laurent - Take into account that the SCOPE of IBN is sensitive because 
   it can be either too broad (and people can get lost) or too narrow (which
   addresses too specific details)
. Alex - Refer to the classical data model x information model NMRG RFC as an
   example of a good outcome that put, in the past, concepts in perspective
   with each other
. Faten - Clarifications are important because different terms (possibly from
   different communities) would be map to terms that an NMRG outcome should
   define/consolidate
. Several people/Imen - The “requirements” document should include also open 
   questions and research challenges on IBN

. So far, 2 outcomes are then expected: 
 - 1 document for clarifying IBN/PBNM/Serv.Mgmt./AN
 - 1 document for IBN requirements, open questions, and research challenges

...

. Laurent/Alex/Lisandro - We need autonomics "beyond and above ANIMA” 
 - 3rd outcome, to report on the autonomics landscape

. Marc-Olivier/several - How AN relates to IoT, for example? That leads to the
 observation (Laurent) that a 4th document is important, in the future,

 addressing a study of the applicability of autonomic networking

 specifications to constrained environments.

...

Action points:
. Alex will take the first step towards the “Concepts” outcome

. Imen will take the first step towards the “Requirements” outcome

. Laurent will take the first step towards the “revised RFC 7575 7576”/“beyond
 and above ANIMA” outcome

---

Additional future topics to be considered in next NMRG interactions:
- Laurent - Management of virtualized infrastructures
- Roberto - Lightweight solution for the management and orchestration of
           distributed infrastructures (e.g.,MANO)
 . Imen - Orchestrators’ requirements and management functions “placement"
- Laurent - Network slicing
- Imen - Management of hybrid (virtualized and non virtualized) networks