Re: [i2rs] [Supa] FW: New Version Notification for draft-hares-i2rs-bnp-eca-data-model-03.txt
John Strassner <strazpdj@gmail.com> Wed, 06 January 2016 03:27 UTC
Return-Path: <strazpdj@gmail.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 148C91A8AD1; Tue, 5 Jan 2016 19:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 FThLQjltJsR1; Tue, 5 Jan 2016 19:27:47 -0800 (PST)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 0CB221A8AC8; Tue, 5 Jan 2016 19:27:47 -0800 (PST)
Received: by mail-lf0-x22a.google.com with SMTP id c192so129524375lfe.2; Tue, 05 Jan 2016 19:27:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O/hutANSbakogS0d9e3FD1igoweRHjzqM037hqpTKAE=; b=yBoVAPjvvsssgwbC17EAubvGK28yuCRuDKUOFPvWpT42emxXaQLCgmyaXHmSuAJqvl TBBOHA1CkIrEhngcZCWfblFKIdmJpja7Gbe7p7sbjgCsUT5rvRcR+PEd6YRBzDJzlqfb 3BwsyecYY8RHa+hra0TAL7AGJ8eIHzWXRs5LSggULcv14hjk0cTrBJ5FMvE3gZZXL392 mV4/5Y1j9NZlDsADT5s4IRVj5LLSX07ruKzff8Eqmlt/hvtUGOA+6gTYmKpB7JM+Vax0 mNac9AYUcRS42TSiBiD2EFRVd51Mbo7oti9oL0gDbwXdOPutEBSnel6yfxHOkLQzwcis ThDw==
MIME-Version: 1.0
X-Received: by 10.25.145.14 with SMTP id t14mr18797351lfd.100.1452050865264; Tue, 05 Jan 2016 19:27:45 -0800 (PST)
Received: by 10.25.89.12 with HTTP; Tue, 5 Jan 2016 19:27:45 -0800 (PST)
In-Reply-To: <00b501d1473f$fef22990$fcd67cb0$@ndzh.com>
References: <20160104170330.13929.73845.idtracker@ietfa.amsl.com> <006701d14722$616c6950$24453bf0$@ndzh.com> <568ADBE7.3030101@joelhalpern.com> <00b501d1473f$fef22990$fcd67cb0$@ndzh.com>
Date: Tue, 05 Jan 2016 19:27:45 -0800
Message-ID: <CAJwYUrHc=ynpL5-BS=_xMn-4L0B2mEO4RDRPnkyGQp5CEZzgXA@mail.gmail.com>
From: John Strassner <strazpdj@gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="001a11401eb20522780528a1f064"
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/k-2l4DwFoJ9Qs3EdaXA0ba6eW4Q>
X-Mailman-Approved-At: Tue, 12 Jan 2016 13:06:31 -0800
Cc: i2rs@ietf.org, "Joel M. Halpern" <jmh@joelhalpern.com>, "supa@ietf.org" <supa@ietf.org>, netmod@ietf.org, John Strassner <strazpdj@gmail.com>
Subject: Re: [i2rs] [Supa] FW: New Version Notification for draft-hares-i2rs-bnp-eca-data-model-03.txt
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 03:27:51 -0000
Sue, > On #1) the dependency between I2RS Filter-based RIB (FB-RIB) and > ECA, please see draft-kini-i2rs-fb-rib-info-model-02.txt. In section 1.1, > it gives the definition of the FB-RIB. Sorry, it does NOT do this. To quote from this section: A Filter Based RIB uses Event-Condition-Action policy. A Filter- based RIB entry specifies matches on fields in a packet (which may include layer 2 fields, IP header fields, transport or application fields) or size of the packet or interface received on. The matches are contained in an ordered list of filters which contain pairs of match condition-action (aka event-condition-action). Please tell me WHERE the event is in the above definition. All I see is a condition-action rule. (BTW, the analysis of PCIM and PCIMe is also not quite correct in your draft). > In section 1.2, it links this to an event-condition-action model. Sorry, it does NOT do this. First, this section simply says, and I quote: "The filter based-RIB uses event-condition-action policy (ECA) rules." That is a tautology at best. Second, in Section 2, under the definition of FB-Route, the draft says: "The policy rules in the filter-based RIB are prescriptive of the Event-Condition-Action form which is often represented by if Condition then action." Please note that this definition is incorrect, and in conflict with SUPA. The whole point of an EVENT-condition-action policy rule is to define a rule of the form: IF <event_clause> evaluates to TRUE IF <condition_clause evaluates to TRUE THEN execute actions in <action_clause> ENDIF ENDIF This definition has been established in the industry and academia for at least 2 decades. Variations of the above have been defined and published (e.g., FOCALE has an alternate set of actions to execute if the condition clause evaluated to FALSE; this has NOT been proposed for SUPA at this time). There have also been extensions to handle sets and groups, as well as specific ordering (DEN-ng, SID, FOCALE). Therefore, I would suggest that you change your drafts to use a condition-action policy rule, OR update the drafts (I would be happy to help) to use a correct definition of an ECA policy rule. regards, John On Mon, Jan 4, 2016 at 2:33 PM, Susan Hares <shares@ndzh.com> wrote: > Joel: > > > > On #1) the dependency between I2RS Filter-based RIB (FB-RIB) and ECA, > please see draft-kini-i2rs-fb-rib-info-model-02.txt. In section 1.1, it > gives the definition of the FB-RIB. In section 1.2, it links this to an > event-condition-action model. If you disagree with the definition of I2RS > FB-RIB, then we should probably restrict this conversation to the I2RS mail > list. Any feedback on the Info-model or data-model would be helpful. The > authors hoped to go to a WG adoption call at the end of this week. > > > > One challenge for the ephemeral I2RS FB-RIB, is there is no definition of > the non-ephemeral FB-RIB. If you think there should be a non-ephemeral > FB-RIB – that discussion may be useful between I2RS, Netmod and SUPA. > > > > On #2) SUPA ECA model, I agree that we should be able to have a common > draft. At IETF 94, I raised issues regarding the SUPA versus my ECA > definition. > > > > Cheerily, > > > > Sue > > > > -----Original Message----- > From: Joel M. Halpern [mailto:jmh@joelhalpern.com] > Sent: Monday, January 04, 2016 3:54 PM > To: Susan Hares; i2rs@ietf.org; netmod@ietf.org; supa@ietf.org > Subject: Re: [i2rs] FW: New Version Notification for > draft-hares-i2rs-bnp-eca-data-model-03.txt > > > > I think there are two issues here. > > > > 1) It is not clear to me why there is any dependence of the fb-rib data > model on an eca data model. While supa does allow for policy model to be > sent directly to the router, it also allows many other cases. > > > > 2) The approach with the supa eca data model is still under development. > > Having said that, the material in there is intended to be very general. > From what I understand, there should be no difficulty in refining the > action side of that model to actions which affect the fb-rib in ways that > are consistent with the fb-dib data model. > > > > Yours, > > Joel > > > > On 1/4/16 2:01 PM, Susan Hares wrote: > > > This model provides a Event-Condition-Action (ECA) policy model. > > > The I2RS FB-RIB yang data model utilizes this model, but to my > > > knowledge the Netmod or netconf has not adopted an ECA policy model to > > > parallel the ACL model. > > > > > > Chen and co-authors have created the model: > > > > > > draft-chen-supa-eca-data-model-05.txt > > > > > > But it does not align with this yang model or seem sufficient to > > > support the FB-RIB information model. At IETF 94, > > > I presented a discussion of the issues I found with the > > > draft-chen-supa-eca-data-model-05.txt, but it has not been updated. > > > We would appreciate feedback on this version of yang model. > > > > > > <i2rs Chair hat on> > > > In my role as I2RS chair, I2RS needs to make progress soon on the > > > I2RS FB-RIB data model. We would appreciate your aid. > > > <i2rs chair hat off> > > > > > > Sue > > > > > > -----Original Message----- > > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org > <internet-drafts@ietf.org>] > > > Sent: Monday, January 04, 2016 12:04 PM > > > To: Susan Hares; Qin Wu; Russ White > > > Subject: New Version Notification for > > > draft-hares-i2rs-bnp-eca-data-model-03.txt > > > > > > > > > A new version of I-D, draft-hares-i2rs-bnp-eca-data-model-03.txt > > > has been successfully submitted by Susan Hares and posted to the IETF > repository. > > > > > > Name: draft-hares-i2rs-bnp-eca-data-model > > > Revision: 03 > > > Title: An Information Model for Basic Network Policy > and Filter Rules > > > Document date: 2016-01-04 > > > Group: Individual Submission > > > Pages: 30 > > > URL: > https://www.ietf.org/internet-drafts/draft-hares-i2rs-bnp-eca-data-model-03.txt > > > Status: > https://datatracker.ietf.org/doc/draft-hares-i2rs-bnp-eca-data-model/ > > > Htmlized: > https://tools.ietf.org/html/draft-hares-i2rs-bnp-eca-data-model-03 > > > Diff: > https://www.ietf.org/rfcdiff?url2=draft-hares-i2rs-bnp-eca-data-model-03 > > > > > > Abstract: > > > This document contains the Basic Network Policy and Filters (BNP IM) > > > Data Model which provides a policy model that support an ordered list > > > of match-condition-action (aka event-condition-action (ECA)) for > > > multiple layers (interface, L1-L4, application) and other factors > > > (size of packet, time of day). The actions allow for setting actions > > > (QOS and other), decapsulation, encapsulation, plus forwarding > > > actions. The policy model can be used with the I2RS filter-based > > > RIB. > > > > > > > > > > > > > > > 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. > > > > > > The IETF Secretariat > > > > > > > > > _______________________________________________ > > > i2rs mailing list > > > i2rs@ietf.org > > > https://www.ietf.org/mailman/listinfo/i2rs > > > > > _______________________________________________ > Supa mailing list > Supa@ietf.org > https://www.ietf.org/mailman/listinfo/supa > > -- regards, John
- [i2rs] FW: New Version Notification for draft-har… Susan Hares
- Re: [i2rs] FW: New Version Notification for draft… Joel M. Halpern
- Re: [i2rs] FW: New Version Notification for draft… Susan Hares
- Re: [i2rs] FW: New Version Notification for draft… Joel M. Halpern
- Re: [i2rs] FW: New Version Notification for draft… Susan Hares
- Re: [i2rs] FW: New Version Notification for draft… Joel M. Halpern
- Re: [i2rs] FW: New Version Notification for draft… Susan Hares
- Re: [i2rs] [Supa] FW: New Version Notification fo… Susan Hares
- Re: [i2rs] [Supa] FW: New Version Notification fo… Susan Hares
- Re: [i2rs] [Supa] FW: New Version Notification fo… John Strassner
- Re: [i2rs] [netmod] [Supa] FW: New Version Notifi… John Strassner
- Re: [i2rs] [Supa] FW: New Version Notification fo… John Strassner
- Re: [i2rs] [Supa] FW: New Version Notification fo… John Strassner