[Supa] draft-liu-supa-policy-based-management-framework-01.txt feedback

Benoit Claise <bclaise@cisco.com> Thu, 21 July 2016 17:17 UTC

Return-Path: <bclaise@cisco.com>
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 7E73612D7EE for <supa@ietfa.amsl.com>; Thu, 21 Jul 2016 10:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level:
X-Spam-Status: No, score=-15.807 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_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 7iDFS2usLoIc for <supa@ietfa.amsl.com>; Thu, 21 Jul 2016 10:17:13 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83C3312D7EB for <supa@ietf.org>; Thu, 21 Jul 2016 10:17:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2645; q=dns/txt; s=iport; t=1469121432; x=1470331032; h=from:subject:to:message-id:date:mime-version; bh=e3Z9EG1C5YhgZharqt8HquwBAZp/dzZp8Pj66pV5crQ=; b=Fb68CLg3C8cYiG50058NDda0tydKmYgnLVmyR6/7rYApnL6h0SxmNewX d916CTCReEzVK98jPepUiQSXYn+2wqo5SyDtXJ18CSALD5NfBMLzZoX0e 58lf1DcrjhJV02u/yXK1ujif/LD6Q4taAg4yV7VGO5O9UXgher5PdrRTA s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BzFQDuApFX/xbLJq1dhD+0KIZ/iBcBAQEBAQFmHAtBDgGENnUBDTACSxQNCAEBiCygE49jjVcBAQgCASSGKoF4CIQXhXeCWgWZJo5rgWyHZiOFRZAhVIN1OoVBgj8BAQE
X-IronPort-AV: E=Sophos;i="5.28,400,1464652800"; d="scan'208,217";a="636957500"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jul 2016 17:17:10 +0000
Received: from [10.61.203.51] ([10.61.203.51]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u6LHHAXi002993 for <supa@ietf.org>; Thu, 21 Jul 2016 17:17:10 GMT
From: Benoit Claise <bclaise@cisco.com>
To: "supa@ietf.org" <supa@ietf.org>
Message-ID: <996f62a7-cb53-3049-a1e4-d4623868580a@cisco.com>
Date: Thu, 21 Jul 2016 19:17:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------DD325F57EB98451AE40EF7E9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/supa/h1rSvh33D6_KlNi1b1DjfhLqtLc>
Subject: [Supa] draft-liu-supa-policy-based-management-framework-01.txt feedback
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: Thu, 21 Jul 2016 17:17:14 -0000

Dear all,

Reviewing the abstract

    Simplified Use of Policy Abstractions (SUPA) defines a set of rules
    that define how services are designed, delivered, and operated
    within an operator's environment independent of any one particular
    service or networking device. This document describes the SUPA basic
    architecture, its elements and interfaces.


This document is not about "how services are designed, delivered, and 
operated", but about policies, policies that are could be applied to 
device, technology, and services related
Quote from the charter:

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

I hope that this only an issue with the abstract, and not the draft 
content (I have to admit that I haven't read the draft).
If not, it should be corrected before the WG document adoption IMO.

Regards, Benoit