Re: [Supa] BRIEF comments on draft-liu-supa-policy-based-management-framework-01

"Liushucheng (Will)" <liushucheng@huawei.com> Tue, 19 July 2016 22:41 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 909E412D951 for <supa@ietfa.amsl.com>; Tue, 19 Jul 2016 15:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.507
X-Spam-Level:
X-Spam-Status: No, score=-5.507 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=-1.287, SPF_PASS=-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 O98eBRGiOBtj for <supa@ietfa.amsl.com>; Tue, 19 Jul 2016 15:41:50 -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 10DD312B025 for <supa@ietf.org>; Tue, 19 Jul 2016 15:41:49 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CNY64887; Tue, 19 Jul 2016 22:41:47 +0000 (GMT)
Received: from SZXEMA411-HUB.china.huawei.com (10.82.72.70) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 19 Jul 2016 23:41:44 +0100
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.215]) by szxema411-hub.china.huawei.com ([10.82.72.70]) with mapi id 14.03.0235.001; Wed, 20 Jul 2016 06:41:37 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: John Strassner <strazpdj@gmail.com>, "supa@ietf.org" <supa@ietf.org>
Thread-Topic: BRIEF comments on draft-liu-supa-policy-based-management-framework-01
Thread-Index: AQHR4dOLR8LS88SoMk2G8z3nxwnNmKAgVIgg
Date: Tue, 19 Jul 2016 22:41:37 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB897C33E2@SZXEMA509-MBS.china.huawei.com>
References: <CAJwYUrHgt2Qv89pbHa3cZYmH_NqZQGSg7TxGBCxK_1cdv99JUw@mail.gmail.com>
In-Reply-To: <CAJwYUrHgt2Qv89pbHa3cZYmH_NqZQGSg7TxGBCxK_1cdv99JUw@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.218.122]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB897C33E2SZXEMA509MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.578EACAC.0072, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.215, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 4db2c4d3e55673b364649cbdc1e578aa
Archived-At: <https://mailarchive.ietf.org/arch/msg/supa/Tjm5Gv2MPE8LhEwtqZtOoIk4eJU>
Subject: Re: [Supa] BRIEF comments on draft-liu-supa-policy-based-management-framework-01
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: Tue, 19 Jul 2016 22:41:53 -0000

Dear John,

Many thx for your review and helpful comments. Inline.


From: John Strassner [mailto:strazpdj@gmail.com]
Sent: Tuesday, July 19, 2016 5:38 PM
To: supa@ietf.org
Cc: Liushucheng (Will)
Subject: BRIEF comments on draft-liu-supa-policy-based-management-framework-01

Hi Will,

here are some brief comments on the above draft for your consideration:

Technical Changes
Page 8:
   (1) policy relies on and is able to adjust service
<jcs> policy manages and can adjust service behavior as necessary </jcs>

   (2) policy relies on network ability provided by resource and is
   able to adjust resource
<jcs> policy manages and can adjust resource behavior as necessary </jcs>

   (3) resource relies on network ability and is able to reserve and
   consume/occupy resource
<jcs> resource hosts service; changing resources may change service behavior as necessary </jcs>
[Will] Thanks for help. I understand what you mean here and will use your sentences in next version. However, there are still some concepts might need to express:

1)     policy need the parameters provided by service/resource, or maybe we can use other way to express the concept of “relies on”(policy need to know there is service created/resource exists before it manages service/resource?)

2)     policy is service-crossing/resource-crossing, in other words, one policy can manage multiple services/resources (1:N relationship)

3)     service is resource-crossing, in other words, one service can use multiple resources (1:M relationship)


Maybe some of they are not necessary to be fully written here. If some should, would you please help to add some words into your sentences?

Page 10

(1)=>(2)=>(3)=>(4)=>(3')=>(2')=>(1')

   Where, (1)=GPIM; (2)=EPRIM; (3)=YANG data models; (4)=
   Implementation; (3')= update of YANG data models; (2')=update of
   EPRIM; (1') = update of GPIM

   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.

<jcs>
I suggest the following additional text:
   The above sequence allows for the addition of new, as well as 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.
</jcs>
[Will] Agree, will add.

NITS!
Page 3
Please update [SUPA-info-model] to point to draft-ietf-supa-generic-policy-info-model-01
Should we update [] to point to draft-ietf-netmod-rfc6020bis-14
[Will] Yes, will update.

Pages 3-4
I offer to redraw the figure, there are lines that are past the character limit
[Will] Great! Many thanks!

Cheers,
Will (Shucheng LIU)