Re: [OPSAWG] Éric Vyncke's No Objection on draft-ietf-opsawg-model-automation-framework-07: (with COMMENT)

mohamed.boucadair@orange.com Tue, 20 October 2020 06:10 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FFDA3A0FF6; Mon, 19 Oct 2020 23:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 UIw10RRBzk8t; Mon, 19 Oct 2020 23:10:19 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3F843A0FF7; Mon, 19 Oct 2020 23:10:18 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 4CFjsP1D9ZzCtnm; Tue, 20 Oct 2020 08:10:17 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1603174217; bh=gSYoc8mDn8/j4m6ED6harlU/f2GE0tzMLWvN5rfFA0E=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=ireiMj56530HGrb5Kj/iz/HgXMjDOIf+jlub0MDYfcDWodK5Rr07GOgAnhKiNZHM9 s+SQd2tGuyW05qh4pwaTRWGAhXIkWQQDAw6NtkwoleboAeyd1W2sNTJfWE8wGCfgl6 qSXV6ApmtjDiaQZjOsRYvrRHDNQ13FEaHySKI1G3Sza78cwimTajAHpoFTfz47c9UY 8ZjaleqABWzjb9qwUzrpKXKIGAl8luKusW2dp0xnZrfVxlfnDtzHnNORon1cyEn/mD 3MHxf9OtzaX9qMVPZrNNhxRmRG0Q+fCKHlsKFEbsqgLW318K7XSTxYBIYy4/JNPgrw oyfsRnpWOWtBg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.57]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 4CFjsN74Clz1xpY; Tue, 20 Oct 2020 08:10:16 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: =?utf-8?B?w4lyaWMgVnluY2tl?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>
CC: "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-ietf-opsawg-model-automation-framework@ietf.org" <draft-ietf-opsawg-model-automation-framework@ietf.org>
Thread-Topic: =?utf-8?B?W09QU0FXR10gw4lyaWMgVnluY2tlJ3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0?= =?utf-8?B?LWlldGYtb3BzYXdnLW1vZGVsLWF1dG9tYXRpb24tZnJhbWV3b3JrLTA3OiAo?= =?utf-8?Q?with_COMMENT)?=
Thread-Index: AQHWphXNGo5e/w9iikqSBy92czeWoamf8z8A
Date: Tue, 20 Oct 2020 06:10:16 +0000
Message-ID: <13218_1603174217_5F8E7F49_13218_23_1_787AE7BB302AE849A7480A190F8B933031563194@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <160311155243.3413.8258578749909771073@ietfa.amsl.com>
In-Reply-To: <160311155243.3413.8258578749909771073@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/RlwOlU8q-kPLgdxRlSejbDspqCY>
Subject: Re: [OPSAWG] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-opsawg-model-automation-framework-07=3A_=28with_COMMENT=29?=
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 06:10:21 -0000

Hi Eric, 

Thank you for the comments. 

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : OPSAWG [mailto:opsawg-bounces@ietf.org] De la part de Éric
> Vyncke via Datatracker
> Envoyé : lundi 19 octobre 2020 14:46
> À : The IESG <iesg@ietf.org>
> Cc : opsawg-chairs@ietf.org; opsawg@ietf.org; draft-ietf-opsawg-
> model-automation-framework@ietf.org
> Objet : [OPSAWG] Éric Vyncke's No Objection on draft-ietf-opsawg-
> model-automation-framework-07: (with COMMENT)
> 
> Éric Vyncke has entered the following ballot position for
> draft-ietf-opsawg-model-automation-framework-07: No Objection
> 
> When responding, please keep the subject line intact and reply to
> all email addresses included in the To and CC lines. (Feel free to
> cut this introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-
> criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-model-automation-
> framework/
> 
> 
> 
> --------------------------------------------------------------------
> --
> COMMENT:
> --------------------------------------------------------------------
> --
> 
> Thank you for the work put into this document.
> 
> Please find below a couple of non-blocking COMMENT points and nits.
> I hope that this helps to improve the document,
> 
> Regards,
> 
> -éric
> 
> == COMMENTS ==
> 
> A generic comment: it hurts my eyes 

[Med] It shouldn't :-)

to see several occurrences of
> "NAT" as a service in an IETF document in 2020...

[Med] Will double check. But, please note that from a YANG standpoint, the NAT module is not only about NAT44, but covers also NAT64, CLAT, SIIT, EAM, NPTv6. 

> 
> Should there be a reference to
> draft-claise-opsawg-service-assurance-architecture (albeit not yet
> an adopted
> document) ?

[Med] We could consider adding it as another example under Section 5 if we had a volunteer to provide the text explaining the mapping with the arch in the document.  

> 
> There are a lot of detailed service creations with a good
> decomposition of all the required steps; but, little is written on
> the importance of YANG models (as opposed to any standard data
> exchange), so, the current title seems a little misleading.

[Med] The important of YANG is described in the intro, e.g., 

   o  Allow for vendor-agnostic interfaces to manage a service and the
      underlying network.

   o  Move from deployment schemes where vendor-specific network
      managers are required to a scheme where the entities that are
      responsible for orchestrating and controlling services and network
      resources provided by multi-vendor devices are unified.

   o  Ease data inheritance and reusability among the various
      architecture layers promoting thus a network-wise provisioning
      instead of device-specific configuration.

   o  Dynamically fed a decision-making process (e.g., Controllers,
      Orchestrators) with notifications that will trigger appropriate
      actions allowing thus to continuously adjust a network (and thus
      involved resources) to comply the intended service to deliver.

> 
> -- Abstract --
> To be honest, I fail to understand why data models can be used to
> 'derive'
> configuration information. Did the authors mean 'describe' or
> 'specify' ?
> 

[Med] We meant "derive". Think about a service model (L3SM, for example), it does not specify the configuration that will be put into effect in a network, but will be used to derive a network model (L3NM), that will be used to derive the actual device configuration models. 

> Later "This document describes an architecture" while the title of
> this document if "framework" ? Slight semantic difference ;-)
> 

[Med] Will be fixed. 

> And later "accommodate modules that", is it 'YANG modules' or 'data
> models' ?

[Med] YANG modules. 

> 
> -- Section 4 --
> The complex figure 4 would benefit from some textual introduction
> referring to the subsections. Also, the meaning of the arrow would
> gain if specified. E.g., why "Service Diagnosis" does not have a
> loop back to optimization or assurance ?

[Med] Point Taken. Will add more text. 

> 
> -- Section 4.2.2 --
> If not mistaken, this is the first appearance of the notation
> "<intended>". Do the angle brackets have a specific meaning?

[Med] Yes, https://tools.ietf.org/html/rfc8342#section-5.1.4. We can add a pointer. 

> 
> -- Section 4.2.3 --
> Suggestion to use the figure 4 wording as the title esp. since the
> wording of MDT is not really used in the sub-section.

[Med] Fair point. Will be fixed. Thanks.

> 
> -- Section 6 --
> Is it required/useful to have the 'standard YANG security
> considerations" in this document that does not contain any YANG
> module?

[Med] The document is about manipulating YANG, hence the need to include the text. 

> 
> -- Section 10.1 --
> Most of the references should probably be informational only.

[Med] Most of the RFCs that are cited there are required because of the security section. 

> 
> == NITS ==
> 
> Generic nit, I found the use of capitalized "Service Model" or
> "Network Models"
> a little disturbing.

[Med] OK. 

> 
> -- Section 1 --
> "how different layer YANG data models" is rather difficult to parse,
> suggest to rephrase it.

[Med] Changed to " YANG data models at different layers "

> 
> -- Section 4.4 --
> Is it "service decomposing" or "service decomposition" ?
> 

[Med] Yes. Will be updated.  


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.