[OPSAWG] TR: New Version Notification for draft-ietf-opsawg-model-automation-framework-03.txt

mohamed.boucadair@orange.com Fri, 29 May 2020 19:07 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 D87F03A0FDB for <opsawg@ietfa.amsl.com>; Fri, 29 May 2020 12:07:02 -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 WEuMDl8a3_jk for <opsawg@ietfa.amsl.com>; Fri, 29 May 2020 12:07:01 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C8A03A0FDA for <opsawg@ietf.org>; Fri, 29 May 2020 12:07:01 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 49YYw36txjz5vnR; Fri, 29 May 2020 21:06:59 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1590779220; bh=eO3OTRmEMkzl2CwvbKaBrSig2qHZ2YnIGIryzGp9wkY=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=dRky56Agc6lH7Jm0xqfcyFC7sO9XzmrpDSqrkJEhQDD9mPt6dsfbWRTQTvKaJmL+w kvOYe9PjLR6gaflHbJbKxxxH6K0fIJrpa+8KiNKZZjikunN6vsMJPnZMy9UPWV8Yel cmdfeu08svqc5i1DWXQDMd9VZLTOGqu5Wn+0cYzO1/kFsH/jGQwQHF32oY8KwpzuAV NPU00O7/bzte8XiN075ykWGyZ4/NGOwVNAY0TDYtE2Uh5ZSjdlo6S8FElrAuL/v7in 67EtDdMI5VPEyPNu0t0tIvx6ECOgm4LHt08a2d/pm7w0VaoIe8oBhNREBO8g8LFYRN eW9wgRnDew52g==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.92]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 49YYw365RDz3wb8; Fri, 29 May 2020 21:06:59 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-opsawg-model-automation-framework-03.txt
Thread-Index: AQHWNL30QcvC2oia+U6yNVGujjWc3ai/bcCA
Date: Fri, 29 May 2020 19:06:58 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330314D4EE2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <159064934734.16254.9254604963842883997@ietfa.amsl.com>
In-Reply-To: <159064934734.16254.9254604963842883997@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.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/DFUtyNaP6fXC3u4L0X8o3tYOLXw>
Subject: [OPSAWG] TR: New Version Notification for draft-ietf-opsawg-model-automation-framework-03.txt
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: Fri, 29 May 2020 19:07:03 -0000

Hi all,

We updated the draft with many edits to enhance the readability of the document. We also made two major changes:
* Update the security section
* Make it clear what modules are still missing for operating VPN services (see Figure 6) and companion text in particular.   

With these fixes, we think that the draft is ready for the WGLC. 

Cheer,
Med

-----Message d'origine-----
De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Envoyé : jeudi 28 mai 2020 09:02
À : Liang Geng; BOUCADAIR Mohamed TGI/OLN; Diego Lopez; Qin Wu; Diego R. Lopez; Qin WU; Chongfeng Xie
Objet : New Version Notification for draft-ietf-opsawg-model-automation-framework-03.txt


A new version of I-D, draft-ietf-opsawg-model-automation-framework-03.txt
has been successfully submitted by Mohamed Boucadair and posted to the
IETF repository.

Name:		draft-ietf-opsawg-model-automation-framework
Revision:	03
Title:		A Framework for Automating Service and Network Management with YANG
Document date:	2020-05-28
Group:		opsawg
Pages:		38
URL:            https://www.ietf.org/internet-drafts/draft-ietf-opsawg-model-automation-framework-03.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-opsawg-model-automation-framework/
Htmlized:       https://tools.ietf.org/html/draft-ietf-opsawg-model-automation-framework-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-model-automation-framework
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-model-automation-framework-03

Abstract:
   Data models for service and network management provides a
   programmatic approach for representing services or networks and
   deriving (1) configuration information that will be communicated to
   network and service components that are used to build and deliver the
   service and (2) state information that will be monitored and tracked.
   Indeed, data models can be used during various phases of the service
   and network management life cycle, such as service instantiation,
   provisioning, optimization, monitoring, diagnostic, and assurance.
   Also, data models are instrumental in the automation of network
   management.  They also provide closed-loop control for the sake of
   adaptive and deterministic service creation, delivery, and
   maintenance.

   This document describes an architecture for service and network
   management automation that takes advantage of YANG modeling
   technologies.  This architecture is drawn from a network provider
   perspective irrespective of the origin of a data module; it can thus
   accommodate modules that are developed outside the IETF.

   The document aims in particular to exemplify an approach that
   specifies the journey from technology-agnostic services to
   technology-specific actions.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat