Re: [Supa] I-D Action: draft-ietf-supa-policy-based-management-framework-00.txt

"Jonathan Hansford" <jonathan@hansfords.net> Wed, 31 August 2016 17:49 UTC

Return-Path: <jonathan@hansfords.net>
X-Original-To: supa@ietfa.amsl.com
Delivered-To: supa@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8A712D5AF for <supa@ietfa.amsl.com>; Wed, 31 Aug 2016 10:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hansfords.net
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 PxJ4FNVSyp3w for <supa@ietfa.amsl.com>; Wed, 31 Aug 2016 10:49:56 -0700 (PDT)
Received: from server.myfast.site (server.myfast.site [212.113.130.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1582F12D5B7 for <supa@ietf.org>; Wed, 31 Aug 2016 10:49:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=hansfords.net; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=A3C6Av1U4u9er5soAJFDOkUshVWrEyxKp1wHeQMuHjw=; b=ToxN/mFa4i4s3P/9dO+kXeXJ9u 5Obp6seswABm5DHDQOvkAPaLhAJVLQJy2EUKvF4PA718S4IOO09v805MtE9j9Z4t5OMplDjxviuHb 3F4KQyO8H6qoM4nKoDpb9W0Zdk0eOXfYINSfI3LGtrOrKxLISvlHiGyedFWJcSwpAeNQjWdzjDBES aUNiTmrbrzeD9y5EO812mAlH9B/APPSwAzzT1YgYy7n5OS7kJxrpkAnr+Em4VDK0C+vC4nczaREuq xR6TVgQS9SLgsvG2xqR1fDotCLjOPogMVJ9/81eq/XBFfb30LktCistA7vqf2eCLO2C9vS2NR2+My MM4x3VCg==;
Received: from hansfords.plus.com ([84.92.116.209]:37381 helo=Vanguard) by server.myfast.site with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from <jonathan@hansfords.net>) id 1bf9e5-001TTl-4R for supa@ietf.org; Wed, 31 Aug 2016 18:49:53 +0100
From: Jonathan Hansford <jonathan@hansfords.net>
To: supa@ietf.org
Date: Wed, 31 Aug 2016 18:49:55 +0100
Message-ID: <01a901d203b0$158411f0$408c35d0$@hansfords.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AA_01D203B8.774A4EB0"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdIDsBRF+swVj4/+QgS9HqW74nSkdw==
Content-Language: en-gb
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.myfast.site
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - hansfords.net
X-Get-Message-Sender-Via: server.myfast.site: authenticated_id: jonathan@hansfords.net
X-Authenticated-Sender: server.myfast.site: jonathan@hansfords.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/supa/93r29PjHQrck3Pu6fbFRhwsTygA>
Subject: Re: [Supa] I-D Action: draft-ietf-supa-policy-based-management-framework-00.txt
X-BeenThere: supa@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This list is to discuss SUPA \(Simplified Use of Policy Abstractions\) related issues." <supa.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/supa>, <mailto:supa-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/supa/>
List-Post: <mailto:supa@ietf.org>
List-Help: <mailto:supa-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/supa>, <mailto:supa-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 17:50:00 -0000

Some review comments:

 

*         General

o   The phrase "the GPIM (or the combination of the GPIM and the EPRIM)" or
its equivalent appears a number of times throughout this document so clearly
it is important but, coming to SUPA cold, I failed to understand its
importance. If there is a need to constantly repeat this phrase, could it
not do with further explanation?

*         Page 2

o   1. Introduction

*  "the task of network operations and management applications and deploying
new services" - is that one task and, if so, what is it? Should that read
"the task of network operations and management applications and deploying
new services"?

*         Page 3

o   1. Introduction

*  s/indepednent/independent

*  What is the term "snippet" intended to imply? Should it be defined
somewhere?

o   2.1 Overview

*  "The GPIM, as well as the combination of the  GPIM and EPRIM, are
converted to generic YANG data modules." Shouldn't that be either The GPIM,
as well as the combination of the  GPIM and EPRIM, is converted ." or "The
GPIM and the combination of the  GPIM and EPRIM are converted ."?

*         Page 4

o   2.1 Overview

*  For consistency with capitalisation, either e.g. "SUPA Generic & ECA
Policy YANG Data modules" or "SUPA generic policy YANG data modules"

*         Page 7

o   2.1 Overview

*  None of the arrows with Ds appear to be double-headed and not all of the
arrows with Cs

*  Since lower down we have "ECA Policy Rule Information Data Model
(EPRIM):" for consistency should we not also have "Generic Policy
Information Model (GPIM):"?

*  "query, and implementation languages, and protocol" (appears twice) -
should that be "query, and implementation languages, and protocol"?

*  "policy rules for that are" - should that be ""policy rules for that
are"?

*  "dependent of" - should that be "independent of" or "dependent on"?

*  "policy rules derived from EPRIM, consist" - should that be "policy
rules, derived from EPRIM, that consist"?

*         Page 8

o   2.1 Overview

*  "Relationship among Policy, Service and Resource" (appears twice) -
should that be "Relationship between Policy, Service and Resource"?

*  Should the caption for Figure 3 end with "models"?

o   2.2 Operation

*  "the goals to achieve" - would "the goals to be achieved" be better?

*         Page 9

o   2.3 The GPIM and the EPRIM

*  The structure of this section feels a little odd. Item (1) appears to
repeat a little of what is in the first two paragraphs and I wonder whether
the section would be better structured if those two paragraphs were
incorporated into item (1).

*         Page 10

o   2.4 Creation of Generic YANG Modules

*  "the addition of new, as well as editing of existing model elements" -
should that be "the addition of new, as well as the editing of existing
model elements"?

o   Pagination fails on the PDF version of this Internet-Draft. Is this page
too long?

 

Jonathan

 

 

> -----Original Message-----

> From: Supa [mailto:supa-bounces@ietf.org] On Behalf Of internet-

> drafts@ietf.org

> Sent: 30 August 2016 04:11

> To: i-d-announce@ietf.org

> Cc: supa@ietf.org

> Subject: [Supa] I-D Action: draft-ietf-supa-policy-based-management-

> framework-00.txt

> 

> 

> A New Internet-Draft is available from the on-line Internet-Drafts
directories.

> This draft is a work item of the Simplified Use of Policy Abstractions of
the

> IETF.

> 

>         Title           : SUPA policy-based management framework

>         Authors         : Will(Shucheng) Liu

>                           John Strassner

>                           Georgios Karagiannis

>                           Maxim Klyus

>                           Jun Bi

>                           Chongfeng Xie

>             Filename        : draft-ietf-supa-policy-based-management-

> framework-00.txt

>             Pages           : 14

>             Date            : 2016-08-29

> 

> Abstract:

>    Simplified Use of Policy Abstractions (SUPA) defines base YANG data

>    models to encode policy, which will point to device-, technology-,

>    and service-specific YANG models developed in other working groups.

>    Policy rules within an operator's environment can be used to express

>    high-level, possibly network-wide policies to a network management

>    function (within a controller, an orchestrator, or a network element).

>    The network management function can then control the configuration

>    and/or monitoring of network elements and services. This document

>    describes the SUPA basic framework, its elements and interfaces.

> 

> 

> The IETF datatracker status page for this draft is:

>
<https://datatracker.ietf.org/doc/draft-ietf-supa-policy-based-management-fr
amework/>
https://datatracker.ietf.org/doc/draft-ietf-supa-policy-based-management-

 
<https://datatracker.ietf.org/doc/draft-ietf-supa-policy-based-management-fr
amework/> > framework/

> 

> There's also a htmlized version available at:

>
<https://tools.ietf.org/html/draft-ietf-supa-policy-based-management-framewo
rk-00> https://tools.ietf.org/html/draft-ietf-supa-policy-based-management-

 
<https://tools.ietf.org/html/draft-ietf-supa-policy-based-management-framewo
rk-00> > framework-00

> 

> 

> 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.

> 

> Internet-Drafts are also available by anonymous FTP at:

>  <ftp://ftp.ietf.org/internet-drafts/> ftp://ftp.ietf.org/internet-drafts/

> 

> _______________________________________________

> Supa mailing list

>  <mailto:Supa@ietf.org> Supa@ietf.org

>  <https://www.ietf.org/mailman/listinfo/supa>
https://www.ietf.org/mailman/listinfo/supa