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

Here are some review comments on this draft.

1. In the abstract, you mentioned that “SUPA policy can point to device, technology, service specific models”. That means SUPA model could be device policy. But the following words, “Policy rules within an operator’s environment can be used to express high-level, possibly network-wide policies to a network management function” and “Policies are a set of rules that define how services are designed, delivered, and operated within an operator's networking environment.” It seems not consistent on the policy scope. So I just want to know what exactly the SUPA scope is, the device policy or service policy or both.

2. In figure 1, both SUPA Generic and ECA Policy YANG data modules are used directly with resource and service model. I think both of them are base models which need to be extended, for example, specific event, condition and action. And those extension/augment belongs to other WGs or SDOs. Only those specific models can be really used. If so, I think both the figure and related text need to modify.
And this figure may give the impression that YANG data models can only come from IETF. I suspect that various vendors and other organizations (SDOs) may also want to define vendor specific or other SDO standardized YANG data models.

3. The second paragraph of 2.1 is not clear. And what’s “that” stands for. It reads (or can be interpreted) as if no YANG data models exists at all. That is not what you mean. I guess you mean "data models for a specific policy or target, or ??" or "do not exist for everything yet" or some such.  guess you want to explain/state that the GPIM can be extended with new YANG data models that build on GPIM or something like that.

4.In 2.1 the paragraph ”An ECA policy rule is …” is duplicated.

5. Figure 2 mixed the design time and run time process and is not logically right. The SUPA model block describes how to generate data models during the design time. It cannot communicate with the OSS/BSS or the controller. In the run time, OSS/BSS fill the data model and generate model instance, and send the instance to the controller. So I suggest to modify this figure by separating the two stages, and rewrite the corresponding text.

6.Following fig 2, you describe the EPRIM, “This type of Policy Rule explicitly defines the current and desired states of the system being managed.” In ECA policy, event and condition stands for the current state, the action is how to go the desired state. EPRIM does not define the desired states.

7. In 2.4 the paragraph “The YANG module derived from” is duplicated.

8. I think the IM in the process described in 2.4 will make the revision complex. The implementation feedback can just modify the DM if necessary. But this approach also need to modify the IM. 

9. You may want to change the reference [RFC6020bis] into a reference [RFC7950]. 

10. Page 9 states:
       SUPA will provide guidelines for translating the GPIM (or the
       combination of the GPIM and the EPRIM) into concrete YANG data
       models that define how to manage and communicate policies between
       systems.
Firstly, what's the "concrete YANG data models mean"? Do you mean the SUPA Generic and ECA Policy YANG data modules? I think they are base models. Can they be used directly to " manage and communicate policies between systems"?
Secondly, I thought that this WG must also define the SUPA Generic and ECA Policy YANG data models for GPIM and EPRIM from the charter. In fact Strassner and Halpern have already submitted drafts for that. So it is not just guidelines, it is the actual data models I think.

11. The last sentence of this draft is not clear. Cannot understand.

12. The draft only mentioned about the different model abstraction level, e.g. GPIM, EPRIM. But it does not mention functional abstraction in different level, right? For example, service level->network level. The policy may need to translate. Several lower level events will trigger higher level event and then higher level policy. I do not know whether this can be addressed in this document.

Regards，
Tianran

> -----Original Message-----
> From: Supa [mailto:supa-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Tuesday, August 30, 2016 11:11 AM
> 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-manageme
> nt-framework/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-supa-policy-based-management-fr
> amework-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/
> 
> _______________________________________________
> Supa mailing list
> Supa@ietf.org
> https://www.ietf.org/mailman/listinfo/supa