Re: [Supa] supa framework review
"Liushucheng (Will Liu)" <liushucheng@huawei.com> Mon, 03 July 2017 14:02 UTC
Return-Path: <liushucheng@huawei.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 C1FCE131648 for <supa@ietfa.amsl.com>; Mon, 3 Jul 2017 07:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tuVNeVLizJOh for <supa@ietfa.amsl.com>; Mon, 3 Jul 2017 07:02:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A513131638 for <supa@ietf.org>; Mon, 3 Jul 2017 07:02:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJQ76141; Mon, 03 Jul 2017 14:02:17 +0000 (GMT)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 3 Jul 2017 15:02:16 +0100
Received: from DGGEML510-MBX.china.huawei.com ([169.254.2.202]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0301.000; Mon, 3 Jul 2017 22:02:09 +0800
From: "Liushucheng (Will Liu)" <liushucheng@huawei.com>
To: Gunter Wang <gunter.wang@ericsson.com>
CC: "supa@ietf.org" <supa@ietf.org>
Thread-Topic: supa framework review
Thread-Index: AdLW2HYlX7EHN3QaQsKi96TSuuMNmgdGjHyQ
Date: Mon, 03 Jul 2017 14:02:08 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB8A32B237@dggeml510-mbx.china.huawei.com>
References: <AMSPR07MB2303A327F5938199B22B62587FD0@AMSPR07MB230.eurprd07.prod.outlook.com>
In-Reply-To: <AMSPR07MB2303A327F5938199B22B62587FD0@AMSPR07MB230.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.79.69]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB8A32B237dggeml510mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.595A4E6A.012F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.202, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: eaadbde84d1dcd539b4a4586eb50cdfb
Archived-At: <https://mailarchive.ietf.org/arch/msg/supa/RiBgzaJ51Bq8rk_tJg1Z5el7FTA>
Subject: Re: [Supa] supa framework review
X-BeenThere: supa@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 03 Jul 2017 14:02:29 -0000
Dear Gunter, Many thanks for your detailed comments. We’ve just updated the draft using all of them. Please have a look at the new version and let us know if there is anything missing. Regards, / 致礼! Will LIU / 刘树成 From: SUPA [mailto:supa-bounces@ietf.org] On Behalf Of Gunter Wang Sent: Saturday, May 27, 2017 7:01 PM To: supa@ietf.org Subject: [Supa] supa framework review Hi, all After reviewing the supa architecture draft, I give some of the comments as follows, * Section 1, page 2: > The rapid growth in the variety and importance of traffic flowing over increasingly complex enterprise and service provider network architectures makes the task of network operations and management applications deploying new services much more difficult. In addition, network operators want to deploy new services quickly and efficiently. It sounds like that the growth of importance of ... makes the task more difficult. It doesn't make sense. Traffic flow over increasingly complex enterprise and service provider network becomes more and more important. Meanwhile, the rapid growth of the variety makes the task of network operations and management applications deploying new services much more difficult, Moreover, network operators want to deploy new services quickly and efficiently. * Section 3.1, page 4: >Note that YANG models may not exist. In this case, the SUPA generic policy YANG data modules serve as an extensible basis to develop new YANG data models for the Service Interface Logic to create appropriate input mechanisms for the operator to define policies. This transfers the work specified by the Resource and Service YANG data models specified in IETF into the Service Interface Logic, which is then translated to configuration snippets. already explained in above paragraph, delete it? Too long to understand Change to Note that YANG models may not exist. In this case, the SUPA generic policy YANG data modules serve as an extensible basis to develop new YANG data models for the Service Interface Logic This transfers the work specified by the Resource and Service YANG data models specified in IETF into the Service Interface Logic. ** Editorial ** Section 1, page 3 >The ECA Policy Rule Information Model (EPRIM) [I-D.ietf-supa-generic-policyinfo- model] extends the GPIM to define how to build policy rules according to the event-condition-action paradigm. Please change to "The ECA Policy Rule Information Model (EPRIM) [I-D.ietf-supa-generic-policyinfo- model] extends the GPIM by defining how to build policy rules according to the event-condition-action paradigm. * Section 2, page 3: >EPRIM: ECA Policy Rule Information Model, which extends the GPIM to define how to build policy rules according to the event-conditionaction paradigm. Change to EPRIM: ECA Policy Rule Information Model, which extends the GPIM by defining how to build policy rules according to the event-conditionaction paradigm. * Section 2 and page 3: >GPDM: Generic Policy Data Models [I-D.ietf-supa-generic-policy-datamodel], are created from the GPIM. These YANG data model policies are used to control the configuration of network elements that model the service(s) to be managed using policy. Change to GPDM: Generic Policy Data Models [I-D.ietf-supa-generic-policy-datamodel], are created from the GPIM. These YANG data model policies are used to control the configuration of network elements that model the service(s) to be managed. * Section 3.1 and page 5: >Figure 1 is exemplary. The Operator actor shown in Figure 1 can interact with SUPA in other ways not shown in Figure 1. Change to Figure 1 is exemplary. The Operator actor can interact with SUPA in other ways not shown in Figure 1. * Section 3.1 and page 6: >A set of Generic Policy Data Models (GPDM) are then created from the GPIM. These YANG data model policies are then used to control the configuration of network elements that model the service(s) to be managed using policy. Change to A set of Generic Policy Data Models (GPDM) are then created from the GPIM. These YANG data model policies are then used to control the configuration of network elements that model the service(s) to be managed. * Section 3.1 and page 7: >ECA Policy Rule Data Model: a model of policy rules, derived from EPRIM, that consist of an event clause, a condition clause, and an action clause. Change to ECA Policy Rule Data Model: a model of policy rules, derived from EPRIM, while each policy rule consists of an event clause, a condition clause, and an action clause. * Section 3.1 and page 8: >Line (1) and (2) connecting policy to resource and policy to service are same, and line (3) connecting resource to service is different as it’s navigable only from resource to service. Change to Line (1) and (2) connecting policy to resource and policy to service are the same, and line (3) connecting resource to service is different as it’s navigable only from resource to service. * Section 3.3 and page 8: >The GPIM provides a common vocabulary for representing concepts that are common to expressing different types of policy, but which are independent of language, protocol, repository, and level of abstraction. Change to The GPIM provides a common vocabulary for representing concepts that are common to different types of policy, but which are independent of language, protocol, repository, and level of abstraction. * Section 3.3 and page 9: >The GPIM provides a common vocabulary for representing concepts that are common to expressing different types of policy, change to The GPIM provides a common vocabulary for representing concepts that are common to different types of policy, * Section 3.4 and page 10: >The YANG module derived from the GPIM contains concepts and terminology for the common operation and administration of policy- based systems, as well as an extensible structure for policy rules of different paradigms. The YANG module derived from the EPRIM extends the generic nature of the GPIM to represent policies using an event- condition-action structure. The above sequence allows for the addition of new, as well as the editing of existing model elements in the GPIM and EPRIM. In practice, the implementation sequence may be much simpler. Specifically, it is unlikely that the GPIM will need to be changed. In addition, changes to the EPRIM will likely be focused on fine- tuning the behavior offered by a specific set of model elements. Change to The YANG module derived from the GPIM contains concepts and terminology for the common operation and administration of policy- based systems, as well as an extensible structure for policy rules of different paradigms. The YANG module derived from the EPRIM extends the generic nature of the GPIM by representing policies using an event condition-action structure. The above sequence allows for the addition of new, as well as the editing of existing model elements in the GPIM and EPRIM. In practice, the implementation sequence may be much simpler. Specifically, it is unlikely that the GPIM will need to be changed. Changes to the EPRIM will likely be focused on fine- tuning the behavior offered by a specific set of model elements. BR/Gunter
- [Supa] supa framework review Gunter Wang
- Re: [Supa] supa framework review Liushucheng (Will Liu)