[Ibnemo] Defining a Common Model for intent

"Susan Hares" <shares@ndzh.com> Sat, 30 May 2015 20:02 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: ibnemo@ietfa.amsl.com
Delivered-To: ibnemo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C25AB1ACCEE for <ibnemo@ietfa.amsl.com>; Sat, 30 May 2015 13:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=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 RTvpeXckU86m for <ibnemo@ietfa.amsl.com>; Sat, 30 May 2015 13:02:01 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id DB6681ACCF3 for <ibnemo@ietf.org>; Sat, 30 May 2015 13:02:00 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.178.112;
From: "Susan Hares" <shares@ndzh.com>
To: <nfvrg@irtf.org>
Date: Sat, 30 May 2015 16:01:55 -0400
Message-ID: <010001d09b13$7b0e19f0$712a4dd0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0101_01D09AF1.F3FE0090"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCbEqAyuT71NsUGRiqkUn3qIW+SrQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/_08_kVUTgYt08j3TLEwBQymfcDU>
Cc: draft-xia-ibnemo-icim@tools.ietf.org, ibnemo@ietf.org
Subject: [Ibnemo] Defining a Common Model for intent
X-BeenThere: ibnemo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of Nemo, an intent-based North Bound \(NB\) interface consisting of an application protocol running over HTTP \(RESTful interfaces\) to exchange intent-based primitives between applications and meta-controllers controlling virtual network resources \(networks, storage, CPU\)." <ibnemo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ibnemo>, <mailto:ibnemo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ibnemo/>
List-Help: <mailto:ibnemo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ibnemo>, <mailto:ibnemo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 May 2015 20:02:02 -0000

On the post
http://www.ietf.org/mail-archive/web/nfvrg/current/msg00208.html, I suggest
that any discussion about use cases or models for Intent needs to define
intent before examining use cases or models.  In the current forums
examining Intent (ODL NIC, ODL Nemo, OF NBI and Keystone, OPNFV Movie,
OpenStack) there is a realization that Intent occurs at multiple layers.
However, there is no clear definition or model across all these forums for
Intent. 

 

The authors of draft-xia-ibnemo-icim have created unified model for defining
intent across many layers, and ask feedback on the concepts in the draft.
The model suggest that:

1)      A user has a intent that is expressed in a context.

2)      Intent (usually) involves an object with a result, and optionally
includes operations toward that result. 

3)      Operations conditions perform actions within/modified by
constraints. 

 

We believe this defines clearly what others are calling "pure intent"
(objects + results) versus "constrained intent" (objects + operations +
constraints).   The draft can be found at:
https://datatracker.ietf.org/doc/draft-xia-ibnemo-icim/ .   We would
appreciate any feedback on this common information model for intent. 

 

Sue Hares 

shares@ndzh.com