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

Andy Bierman <andy@yumaworks.com> Sat, 16 April 2016 17:56 UTC

Return-Path: <andy@yumaworks.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 22FB412E27C for <supa@ietfa.amsl.com>; Sat, 16 Apr 2016 10:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 Hh5RioLvjEuC for <supa@ietfa.amsl.com>; Sat, 16 Apr 2016 10:56:37 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CEBD12E274 for <supa@ietf.org>; Sat, 16 Apr 2016 10:56:37 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id e190so177547792lfe.0 for <supa@ietf.org>; Sat, 16 Apr 2016 10:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=4kZNp9TzJz+F3eOgZIuv+qU8RcfwqajHQX2cVNqYiTs=; b=kmGBXBKMB+O6WyyZFyGlX+RSW3WM7k1WVLQTQ4nMwNQkH+QBlFvpg6hbngUmJ/Js2/ lALF5XcARXdqUImckFGaCEv8h3iHykBozCQuAPzGJJyY9lzrcyjWOEWuIUEO9dezb1eG O7NHWFnMAdafv4/bXtrH+yHGFb3libeWe/5RRIoDxMD/UvlWPWzTI4QtVrTfynO8s/Ra EaKnideoz1KIKLgYNwdtErc2Q0dbkS+DXBDC1h792IvcOBBTfRTTPCmYH5ZMFVoZICtX Qkl9Q9f1Bz+3ngqwHyUkO6jRlCCMV3nq/B7uxZMcFwfEbxItTRGbxkHohTk7oa5U7COR NdHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=4kZNp9TzJz+F3eOgZIuv+qU8RcfwqajHQX2cVNqYiTs=; b=KAo+WMvhEhigfow03ux8HNwSJgviCZULTbkrJVQ1d3Ic3th4MMCIJNniz7eTDlG5Qn u04lQZXkIh1SwoUice3baDD8U03Y2u9H796qjMkoHAHRTpfJZlT+D0s7edKEVQHchbFo ifuUalEAVDZHojeokB2HBgHuZa3vm/6Hss/5Pekmoro+OuN8eech75A1sB5Vo/pmQf+U GNDumNPBp1wVWtSY2LZ6G9U79We704p4Icr2BgB87PshzlzG5i1uQbgskdmexf2hOBPd 1UPwoCzidmXh291vBBhJmYgoCrPVNgbD/tnLnivv/Uc8xOqS7L0wIWfWqzZKakNPTTb/ hUnA==
X-Gm-Message-State: AOPr4FWCMNRCeQIYADvNE+VRfNJp63XbPITP61hQAt9fJhbOiOQ+CGLCY+2+hQnAqZjka3zZSUd7L+jhtviXFA==
MIME-Version: 1.0
X-Received: by 10.112.56.43 with SMTP id x11mr11389020lbp.145.1460829395089; Sat, 16 Apr 2016 10:56:35 -0700 (PDT)
Received: by 10.112.198.70 with HTTP; Sat, 16 Apr 2016 10:56:34 -0700 (PDT)
In-Reply-To: <57114FD4.8000709@joelhalpern.com>
References: <20160415200632.17497.79135.idtracker@ietfa.amsl.com> <57114FD4.8000709@joelhalpern.com>
Date: Sat, 16 Apr 2016 10:56:34 -0700
Message-ID: <CABCOCHSx+=HXehVv5qrtiBGgUBmZ_9wLQ1RJzx-nhjpn9T+Zjg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Joel Halpern <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary="001a1133a9ea2c18ca05309dd9ed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/supa/a0lVnPwijv9iZAjj9Chsb1z6wGs>
Cc: SUPA list <supa@ietf.org>
Subject: Re: [Supa] Fwd: I-D Action: draft-halpern-supa-generic-policy-data-model-01.txt
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: Sat, 16 Apr 2016 17:56:40 -0000

Hi,

I would like to see an example of SUPA in use.
I thought Juergen has a clear maybe-not-simple use-case with SNMP:


Event: example-interface-up notification received
Task: Extract NE ID and interface ID

Condition: Determine if NE,interface is an edge interface to an untrusted
network
Task: examine topology database?  Out of scope?

Action: install an ACL on this NE, interface to deny incoming and outbound
packets on port 161, 162
Task: Determine how ACLs done on NE and send proper configuration changes

What parts will SUPA provide and how are they done?
What parts will the domain-specific models provide and how do
they integrate with this module?  What parts are left
as implementation details and out of scope for SUPA?

I am far from convinced this approach is simpler than a controller level
data model.
E.g.,  a network-wide ACL that blocks SNMP from entering or exiting the
administrative
domain can implement this policy, and all the ECA configuration and
execution details
are hidden within implementation details.



Andy



On Fri, Apr 15, 2016 at 1:32 PM, Joel Halpern <jmh@joelhalpern.com> 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: internet-drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
>
>
> 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
> I-D-Announce@ietf.org
> 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
> Supa@ietf.org
> https://www.ietf.org/mailman/listinfo/supa
>