[NMOP] Re: SIMAP Issue 102: REQ-BIDIR

Italo Busi <Italo.Busi@huawei.com> Mon, 02 February 2026 10:38 UTC

From: Italo Busi <Italo.Busi@huawei.com>
To: "Benoit@everything-ops.net" <benoit@everything-ops.net>
Thread-Topic: SIMAP Issue 102: REQ-BIDIR
Thread-Index: AQHckgh92s8xRbMCyUqo2fxQxxcG3rVvO91g
Date: Mon, 02 Feb 2026 10:38:09 +0000
Message-ID: <428f0da502384308b8da114376c70d9e@huawei.com>
References: <a7d293e8-ad99-435d-971a-04050d587f1d@everything-ops.net>
In-Reply-To: <a7d293e8-ad99-435d-971a-04050d587f1d@everything-ops.net>
Accept-Language: it-IT, en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_428f0da502384308b8da114376c70d9ehuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: PUB2G7ZE3XYU7RBIRQKMESXJYTEZST3F
CC: "nmop@ietf.org" <nmop@ietf.org>
Precedence: list
Subject: [NMOP] Re: SIMAP Issue 102: REQ-BIDIR
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmop/r-FAl4w2WsU-qGWlpkZpkWCwlwA>

Hi Benoit,

I am fine with the updated text

Thanks, Italo

From: Benoit@everything-ops.net <benoit@everything-ops.net>
Sent: venerdì 30 gennaio 2026 17:50
To: Italo Busi <Italo.Busi@huawei.com>
Cc: nmop@ietf.org
Subject: SIMAP Issue 102: REQ-BIDIR

Italo,

Thanks for your feedback.
Regarding this issue https://github.com/ietf-wg-nmop/draft-ietf-nmop-digital-map-concept/issues/102
REQ-BIDIR
The term "simplified service layer topology" needs further qualification on the "simplification".
I do agree on the requirement to show how a bidirectional link in the client layer (or higher abstraction view) can be supported by two unidirectional links in the server layer (or lower abstraction view).
We must understand that "simplified service layer topology" as the fact that not all SIMAP users/applications want to see the two unidirectional; under some circumstances/for a specific service layer topolgoy, a bidir is sufficient. Even from a pure display point of view, this is a simplified view.
Let's simplify :-) the text

OLD:

 REQ-BIDIR:  SIMAP must provide a mechanism to model bidirectional

      links.  While data flows are unidirectional, the bidirectional

      links are also common in networking.  Examples are Ethernet

      cables, bidirectional SONET rings, socket connection to the

      server, etc.  There is also the requirement for simplified Service

      layer topology, where a link is modeled as bidirectional in order

      to be supported by unidirectional links at the lower layer.
NEW:

 REQ-BIDIR:  SIMAP must provide a mechanism to model bidirectional

      links.  While data flows are unidirectional, the bidirectional

      links are also common in networking.  Examples are Ethernet

      cables, bidirectional SONET rings, socket connection to the

      server, etc., where a link is modeled as bidirectional, which in turn

      might be supported as unidirectional links at the lower layer.

This change is applied via https://github.com/ietf-wg-nmop/draft-ietf-nmop-digital-map-concept/pull/160

Regards, Benoit

[NMOP] SIMAP Issue 102: REQ-BIDIR Benoit@everything-ops.net
[NMOP] Re: SIMAP Issue 102: REQ-BIDIR Italo Busi