[NMOP] Re: SIMAP Issue 94: Italo Busi, Sergio Belotti- REQ-BASIC-MODEL-SUPPORT
Olga Havel <olga.havel@huawei.com> Fri, 13 February 2026 16:57 UTC
Return-Path: <olga.havel@huawei.com>
X-Original-To: nmop@mail2.ietf.org
Delivered-To: nmop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E70E4B707F0B for <nmop@mail2.ietf.org>; Fri, 13 Feb 2026 08:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.195
X-Spam-Level:
X-Spam-Status: No, score=-4.195 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 p-RDpr0Y6PXh for <nmop@mail2.ietf.org>; Fri, 13 Feb 2026 08:57:53 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 90CCFB707F03 for <nmop@ietf.org>; Fri, 13 Feb 2026 08:57:53 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.224.83]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4fCJHy0gwFzHnGds; Sat, 14 Feb 2026 00:57:34 +0800 (CST)
Received: from frapema500004.china.huawei.com (unknown [7.182.19.21]) by mail.maildlp.com (Postfix) with ESMTPS id AC36040569; Sat, 14 Feb 2026 00:57:52 +0800 (CST)
Received: from frapema500007.china.huawei.com (7.182.19.81) by frapema500004.china.huawei.com (7.182.19.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 13 Feb 2026 17:57:52 +0100
Received: from frapema500007.china.huawei.com ([7.182.19.81]) by frapema500007.china.huawei.com ([7.182.19.81]) with mapi id 15.02.1544.011; Fri, 13 Feb 2026 17:57:52 +0100
From: Olga Havel <olga.havel@huawei.com>
To: Italo Busi <Italo.Busi@huawei.com>, "Belotti, Sergio (Nokia - IT)" <sergio.belotti@nokia.com>, "nmop@ietf.org" <nmop@ietf.org>
Thread-Topic: SIMAP Issue 94: Italo Busi, Sergio Belotti- REQ-BASIC-MODEL-SUPPORT
Thread-Index: AdyVFEA939MYmbsFRPia3PQB558K+QBragoQAZGTG0A=
Date: Fri, 13 Feb 2026 16:57:52 +0000
Message-ID: <130f8cb6baf84fc89454e79ffa5205d8@huawei.com>
References: <b10867c382294ac5a2e9b022982403c6@huawei.com> <dcbdcdc4e20d41bf949281ce7302ac3a@huawei.com>
In-Reply-To: <dcbdcdc4e20d41bf949281ce7302ac3a@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.206.138.9]
Content-Type: multipart/alternative; boundary="_000_130f8cb6baf84fc89454e79ffa5205d8huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: CIAWEPJOWOPAH2JKVEUQR3EOML3QTF2R
X-Message-ID-Hash: CIAWEPJOWOPAH2JKVEUQR3EOML3QTF2R
X-MailFrom: olga.havel@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [NMOP] Re: SIMAP Issue 94: Italo Busi, Sergio Belotti- REQ-BASIC-MODEL-SUPPORT
List-Id: "Network Management Operations (NMOP) Working Group" <nmop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmop/sSgl0HLSygMiOYWCRsQTisFv1OM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmop>
List-Help: <mailto:nmop-request@ietf.org?subject=help>
List-Owner: <mailto:nmop-owner@ietf.org>
List-Post: <mailto:nmop@ietf.org>
List-Subscribe: <mailto:nmop-join@ietf.org>
List-Unsubscribe: <mailto:nmop-leave@ietf.org>
Hi all, I updated as follows: OLD: REQ-BASIC-MODEL-SUPPORT: : Basic model with network, node, link, and termination point entity types. This means that users of SIMAP must be able to understand a topology model at any layer via these core concepts only, without having to go to the details of the specific augmentations to understand the topology. NEW: REQ-BASIC-MODEL-SUPPORT: : Basic model with network, node, link, and termination point entity types. This means that users of SIMAP must be able to reconstruct a topology at any layer in an unambiguous manner via these core concepts only, without the need to understand layer or technology specific information. I closed the Issue https://github.com/ietf-wg-nmop/draft-ietf-nmop-digital-map-concept/issues/94 via pull request https://github.com/ietf-wg-nmop/draft-ietf-nmop-digital-map-concept/pull/165 Best Regards, Olga From: Italo Busi <Italo.Busi@huawei.com> Sent: Thursday, February 5, 2026 5:11 PM To: Olga Havel <olga.havel@huawei.com>; Belotti, Sergio (Nokia - IT) <sergio.belotti@nokia.com>; nmop@ietf.org Subject: RE: SIMAP Issue 94: Italo Busi, Sergio Belotti- REQ-BASIC-MODEL-SUPPORT Hi Olga, I changes in NEW are fine for me I am wondering whether the term "augmentation" might not be understood as too constrained (e.g., YANG-specific). What about "without the need to understand layer (or technology) specific information" or just remove since the "via these core concepts only" seems clear enough to me My 2 cents Italo From: Olga Havel <olga.havel@huawei.com<mailto:olga.havel@huawei.com>> Sent: martedì 3 febbraio 2026 14:54 To: Italo Busi <Italo.Busi@huawei.com<mailto:Italo.Busi@huawei.com>>; Belotti, Sergio (Nokia - IT) <sergio.belotti@nokia.com<mailto:sergio.belotti@nokia.com>>; nmop@ietf.org<mailto:nmop@ietf.org> Subject: SIMAP Issue 94: Italo Busi, Sergio Belotti- REQ-BASIC-MODEL-SUPPORT Italo, Sergio, We addressed the core topology entities definition and closed this issue. You both have concern about what 'understand the topology model' means. What about the following change, based on the agreed definition of the core topology that we added based on the comment from both of you: OLD: REQ-BASIC-MODEL-SUPPORT: : Basic model with network, node, link, and termination point entity types. This means that users of SIMAP must be able to understand a topology model at any layer via these core concepts only, without having to go to the details of the specific augmentations to understand the topology. NEW: REQ-BASIC-MODEL-SUPPORT: : Basic model with network, node, link, and termination point entity types. This means that users of SIMAP must be able to reconstruct a topology at any layer in an unambiguous manner via these core concepts only, without having to go to the details of the specific augmentations to understand the topology. Best Regards, Olga