Re: [OPSAWG] Last Call: <draft-ietf-opsawg-model-automation-framework-06.txt> (A Framework for Automating Service and Network Management with YANG) to Informational RFC

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 28 September 2020 22:25 UTC

Return-Path: <brian.e.carpenter@gmail.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 756023A1437; Mon, 28 Sep 2020 15:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level:
X-Spam-Status: No, score=-2.312 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 biFOS9T-cKSa; Mon, 28 Sep 2020 15:25:15 -0700 (PDT)
Received: from mail-pf1-x443.google.com (mail-pf1-x443.google.com [IPv6:2607:f8b0:4864:20::443]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 473383A1434; Mon, 28 Sep 2020 15:25:15 -0700 (PDT)
Received: by mail-pf1-x443.google.com with SMTP id w7so2523622pfi.4; Mon, 28 Sep 2020 15:25:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:references:from:to:cc:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=1p7+1EMhCGpKh+jLu+g3L/fqUrqTcg9jZ3sTf3mViYo=; b=OY2w6VFiTjvkZEUShICoXQukuKhTtznll38Ma0F8PDYGziHrJ7BDPY/v7gpjhcw2UF +1rK/D8n7x+ecXrfdu/XsXdSzNofK/LHRG92TThK+5ePCzan0vjhWzSO5VadNTCcmFSu FxMrfWKemdiN/P9V4g49d3nIOLVKjK0IDjGRoHOH+wdOnehOsqGKxt8MZa5VRixz2ga0 Y8nZdJbqPYlK0VTi9WqpPnlNjXMtF8TBu3lH7DnqCyZA8r0GdO991pheOXpvqbpA/j1V 8KijmITFu5+9ozwjsiu7c7Was+PvSMGnmqlt0RptTXRjQtZBsSzEwZEf5SMsUN6aU6bl pErA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:from:to:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1p7+1EMhCGpKh+jLu+g3L/fqUrqTcg9jZ3sTf3mViYo=; b=FPC27Fmb+1bYmI+G+UPjvl/KsD8O9m84KAuFw+XV/TsZA/P8JVA46co+2SQ+nkKlpE NAG+bSIBBBUE6dDpU+WXOY7Nd07DPYipV1U4Ol7yPZh2oF2UuCWRnr42DJ0fJqNU8+we rJiTiRIIelL7otkXh1oNWrUuOVqety9UtoSQ3Sepjl1KNgXpMtH0044Wpw9nVYhX4mxM 90GhuFFCygxkJaILoLLRKUnCVll4s2avSyAQDb3oPrniNUYJVO3NXnpr6orLeX6/gxC5 SZMuFN4kFUT5OShz9Mp9C/oMnsuGYT/sPT9OaqtLNlGt0UnWo6DWTIQJcBUj+3d4aYUr JZQA==
X-Gm-Message-State: AOAM5327vx0s1FuY99hm7O0XwEwczEo5kvqezfqhjutpA60S/5/3yUQJ mZd8Cpwn4gmlGOSq2wzFxNejlnqkTUTYeg==
X-Google-Smtp-Source: ABdhPJzwwiz4Uvn4dbqu/UDrysFCGLDVGKuNN/a5J/gvZGml81zAlPwjf3rStLMpRoBt5w8utPJyFQ==
X-Received: by 2002:a63:224f:: with SMTP id t15mr927136pgm.251.1601331914419; Mon, 28 Sep 2020 15:25:14 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.138.136]) by smtp.gmail.com with ESMTPSA id t198sm2338695pgb.82.2020.09.28.15.25.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Sep 2020 15:25:13 -0700 (PDT)
References: <160095255684.28293.2595806209469918634@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
To: last-call@ietf.org
Cc: draft-ietf-opsawg-model-automation-framework.all@ietf.org, opsawg@ietf.org
Message-ID: <0ae283b5-1675-9995-757f-d6e6ccbd6d54@gmail.com>
Date: Tue, 29 Sep 2020 11:25:09 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160095255684.28293.2595806209469918634@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/mrpJYJzyHR3LJX1W9LZ2tQXVT8k>
Subject: Re: [OPSAWG] Last Call: <draft-ietf-opsawg-model-automation-framework-06.txt> (A Framework for Automating Service and Network Management with YANG) to Informational RFC
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: Mon, 28 Sep 2020 22:25:16 -0000

Hi,

I have a question for clarification, and then a comment.

First, consider these extracts:

> 5.1.  L2VPN/L3VPN Service Delivery
> 
>    In reference to Figure 5, the following steps are performed to
>    deliver the L3VPN service within the network management automation
>    architecture defined in this document:
> 
>    1.  The Customer requests to create two sites (as per service
>        creation operation in Section 4.2.1)...
...
> 5.2.  VN Lifecycle Management
> 
>    In reference to Figure 7, the following steps are performed to
>    deliver the VN service within the network management automation
>    architecture defined in this document:
> 
>    1.  Customer requests (service exposure operation in Section 4.1.1)
>        to create 'VN' based on Access point...
...
>    3.  The Customer exchanges connectivity-matrix on abstract node and
>        explicit path using TE topology model with the orchestrator...

In those examples, how does the customer "request" or "exchange" data? I assume this is intended to happen by software, rather than by telefax. So what protocol is involved, and which entity on the customer side is doing it?

> 5.3.  Event-based Telemetry in the Device Self Management
> 
>    In reference to Figure 8, the following steps are performed to
>    monitor state changes of managed objects or resources in a network
>    device and provide device self-management within the network
>    management automation architecture defined in this document:
> 
>    1.  To control which state a network device should be in or is
>        allowed to be in at any given time, a set of conditions and
>        actions are defined and correlated with network events (e.g.,
>        allow the NETCONF server to send updates...

Second, this is the first mention of NETCONF in the document, and the only other mention is in the Security Considerations. I suggest that there should be a short description of the role of NETCONF (and RESTCONF) earlier in the document, either in section 3 or more likely in section 4 (Functional Blocks and Interactions).

Regards
   Brian Carpenter