MIME-Version: 1.0
References: 
 <178854714723.125440.7139796939509885187@dt-datatracker-9769b79f-xztnc>
 <c1b4ae1e-360a-457f-8ca9-f4169938bee7@everything-ops.net>
In-Reply-To: <c1b4ae1e-360a-457f-8ca9-f4169938bee7@everything-ops.net>
From: Jen Linkova <furry13@gmail.com>
Date: Sat, 5 Sep 2026 12:38:22 +1000
Message-ID: 
 <CAFU7BAQ0=XfVhu=yzxX2Qf=Xe15TzvYE7EGtcn_LGkjm-OqR7A@mail.gmail.com>
To: "Benoit@everything-ops.net" <benoit@everything-ops.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: LKSDSFPSMGAQPB3QG7RMQIFY2A2F2JBG
CC: nmop@ietf.org, Mahesh Jethanandani <mjethanandani@gmail.com>,
 Stewart Bryant <stewart.bryant@gmail.com>,
 =?UTF-8?B?TWFsacWhYSBWdcSNaW5pxIc=?= <malisa.vucinic@inria.fr>
Precedence: list
Subject: =?utf-8?q?=5BNMOP=5D_Re=3A_I-D_Action=3A_draft-ietf-nmop-simap-concept-13=2E?=
	=?utf-8?q?txt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/nmop/qaDhuFXfelOSvDS2mrghToFs1oo>

Hi Benoit,

Thank you, the new version does address all my comments except one: I
noticed in my review that neither section 4.1 nor 4.2 use the
normative language (all "should" are lower case), while section 4.3
does use capital case.
The new revision doesn't change that. Could you please confirm it's
intentional and not an oversight?

Thank you!

On Sat, Sep 5, 2026 at 5:26=E2=80=AFAM Benoit@everything-ops.net
<benoit@everything-ops.net> wrote:
>
> Jen, Stewart, Mali=C5=A1a, Mahesh,
>
> This new version addresses the Genart, Opsdir (and the Secdir) directorat=
e reviews.
>
> Regards, Benoit
>
> On 04/09/2026 20:39, internet-drafts@ietf.org wrote:
>
> Internet-Draft draft-ietf-nmop-simap-concept-13.txt is now available. It =
is a
> work item of the Network Management Operations (NMOP) WG of the IETF.
>
>    Title:   SIMAP: Concept, Requirements, and Use Cases
>    Authors: Olga Havel
>             Benoit Claise
>             Oscar Gonzalez de Dios
>             Thomas Graf
>    Name:    draft-ietf-nmop-simap-concept-13.txt
>    Pages:   44
>    Dates:   2026-09-04
>
> Abstract:
>
>    This document defines the concept of Service & Infrastructure Maps
>    (SIMAP) and identifies a set of SIMAP requirements and use cases.
>    The SIMAP was previously known as Digital Map. SIMAP evolves the
>    earlier 'Digital Map' concept by making explicit the ties between
>    service and infrastructure layers, clarifying expected outcomes for
>    operations and automation, and addressing ambiguity associated with
>    the term 'digital.'
>
>    The document intends to be used as a reference for the assessment of
>    the various topology modules to meet SIMAP requirements.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-nmop-simap-concept/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-nmop-simap-concept-13.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-nmop-simap-concept=
-13
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
>


--=20
Cheers, Jen Linkova