Re: [Supa] Fwd: I-D Action: draft-halpern-supa-generic-policy-data-model-01.txt

[Andy Bierman <[e-mail]>]

Hi,

Here is the object tree that pyang generates.
Looks fairly complex. How many of these 168 objects does one
usually need to provide for a typical policy?

It would be helpful to see examples to understand how this YANG module is
used.

I read this framework draft:
http://www.ietf.org/id/draft-liu-supa-policy-based-management-framework-00.txt

It is still difficult to understand how they relate to each other and
how a SUPA controller would provide a standards-based solution.


Andy



On Fri, Apr 15, 2016 at 1:32 PM, Joel Halpern <[e-mail]> wrote:

> We have revised the data model draft to fix the extraction and YANG errors.
> It has been checked with a YANG 1.1 validator, which says it works.
>
> The must clauses on the instance-identifiers now indicate the target class
> (including subclasses) of the association.  As I noted in BA, for
> associations with properties, the two end-points both point to the
> association class, which points to both end-points.
>
> We will be doing the YANG tree, better descriptions, and text about the
> mapping from IM to DM.
>
> Please review either the IM or the DM (using the IM descriptions) to see
> whether this model represents what the WG wants to see.
>
> Yours,
> Joel
>
>
> -------- Forwarded Message --------
> Subject: I-D Action: draft-halpern-supa-generic-policy-data-model-01.txt
> Date: Fri, 15 Apr 2016 13:06:32 -0700
> From: [e-mail]
> Reply-To: [e-mail]
> To: [e-mail]
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : Generic Policy Data Model for Simplified Use of
> Policy Abstractions (SUPA)
>         Authors         : Joel Halpern
>                           John Strassner
>         Filename        :
> draft-halpern-supa-generic-policy-data-model-01.txt
>         Pages           : 48
>         Date            : 2016-04-15
>
> Abstract:
>    This document defines two YANG policy data models. The first is a
>    generic policy model that is meant to be extended on an application-
>    specific basis. The second is an exemplary extension of the first
>    generic policy model, and defines rules as event-condition-action
>    policies. Both models are independent of the level of abstraction of
>    the content and meaning of a policy.
>
>
>
> The IETF datatracker status page for this draft is:
>
> https://datatracker.ietf.org/doc/draft-halpern-supa-generic-policy-data-model/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-halpern-supa-generic-policy-data-model-01
>
> A diff from the previous version is available at:
>
> https://www.ietf.org/rfcdiff?url2=draft-halpern-supa-generic-policy-data-model-01
>
>
> 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/
>
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>
> _______________________________________________
> Supa mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/supa
>