Re: [Ibnemo] [Nfvrg] 答复: 答复: Defining a Common Model for intent

"Gember-Jacobson, Aaron" <agember@cs.wisc.edu> Fri, 05 June 2015 17:41 UTC

Return-Path: <agember@cs.wisc.edu>
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 015CD1A00B0 for <ibnemo@ietfa.amsl.com>; Fri, 5 Jun 2015 10:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level:
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 B7PpuXiCU9PW for <ibnemo@ietfa.amsl.com>; Fri, 5 Jun 2015 10:41:43 -0700 (PDT)
Received: from sabe.cs.wisc.edu (sabe.cs.wisc.edu [128.105.6.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78F451A00F7 for <ibnemo@ietf.org>; Fri, 5 Jun 2015 10:41:41 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) (authenticated bits=0) by sabe.cs.wisc.edu (8.14.1/8.14.1) with ESMTP id t55Hfbxb023780 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <ibnemo@ietf.org>; Fri, 5 Jun 2015 12:41:39 -0500
Received: by lbbqq2 with SMTP id qq2so50277403lbb.3 for <ibnemo@ietf.org>; Fri, 05 Jun 2015 10:41:32 -0700 (PDT)
X-Gm-Message-State: ALoCoQljE7VqWHJxf55/px6cPubCWzL9WkgURztFCc1poFxBFzUrOCCfEeAXhdI+3JM2gqiDDPxi
X-Received: by 10.112.119.198 with SMTP id kw6mr4288702lbb.97.1433526092024; Fri, 05 Jun 2015 10:41:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.199.231 with HTTP; Fri, 5 Jun 2015 10:41:00 -0700 (PDT)
In-Reply-To: <01f901d09fb3$20be9e30$623bda90$@ndzh.com>
References: <D19315B6.1D624%pedroa.aranda@telefonica.com> <014801d09d86$46b6d4b0$d4247e10$@ndzh.com> <D19460A3.1D73F%pedroa.aranda@telefonica.com> <A747A0713F56294D8FBE33E5C6B8F581295121C3@szxeml513-mbx.china.huawei.com> <01d501d09efd$2b05f6b0$8111e410$@ndzh.com> <83E20623-51AE-4384-B41C-1F4A84B362C4@telefonica.com> <01f901d09fb3$20be9e30$623bda90$@ndzh.com>
From: "Gember-Jacobson, Aaron" <agember@cs.wisc.edu>
Date: Fri, 5 Jun 2015 12:41:00 -0500
Message-ID: <CAD+Ke9c6XXt4qNBBgPb9tDUF6sFM4O32w0Bb3eozE0Uib2iXLQ@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary=047d7ba9701e7e10a00517c8cd72
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/hUDLPJNXh2FAQyNSgEHR6I95wVk>
X-Mailman-Approved-At: Fri, 05 Jun 2015 12:34:59 -0700
Cc: "zhangyali \(D\)" <zhangyali369@huawei.com>, ibnemo@ietf.org, nfvrg@irtf.org, draft-xia-ibnemo-icim@tools.ietf.org
Subject: Re: [Ibnemo] =?utf-8?b?W05mdnJnXSAg562U5aSNOiDnrZTlpI06IERlZmluaW5n?= =?utf-8?q?_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: Fri, 05 Jun 2015 17:41:45 -0000

Flowlog is a "network SQL" for SDN (
https://www.usenix.org/conference/nsdi14/technical-sessions/presentation/nelson).
There's also NDlog (
http://www.cis.upenn.edu/~boonloo/papers/declarenet_cacm09.pdf). However, I
think the level of abstraction provided by both Flowlog and NDlog is lower
on the policy continuum than many expressions of intent. Nonetheless, these
works may be a valuable starting point for a declarative language for
intent.

Aaron

On Fri, Jun 5, 2015 at 12:14 PM, Susan Hares <shares@ndzh.com> wrote:

> Diego:
>
>
>
> I 100% agree with your goals on creating a “network SQL that is a
> declarative language.
>
>
>
> Sue
>
>
>
> *From:* DIEGO LOPEZ GARCIA [mailto:diego.r.lopez@telefonica.com]
> *Sent:* Thursday, June 04, 2015 4:17 PM
> *To:* Susan Hares
> *Cc:* zhangyali (D); PEDRO ANDRES ARANDA GUTIERREZ; nfvrg@irtf.org;
> draft-xia-ibnemo-icim@tools.ietf.org; ibnemo@ietf.org
> *Subject:* Re: [Ibnemo] [Nfvrg] 答复: 答复: Defining a Common Model for intent
>
>
>
> Hi,
>
>
>
> Let me try to bring a new view on this (hence no quotation of previous
> exchanges) in the hope it helps to get to a common understanding.
>
>
>
> Those of you who know me have probably heard me saying that to complete
> the promise of SDN we need something like a "network SQL": a declarative
> language based on a formal network model that would allow both defining
> network properties and manipulating network behavior, and, what is of
> capital importance in my view, support the seamless integration of these
> definitions and manipulations within general-purpose applications. This is
> my hope for intent-based networking, and that is my understanding of an
> intent expression.
>
>
>
> An intent model would precisely define this formal network model on which
> to base the declarative language. Different models would support different
> views (or roles?) and therefore translate into different declarative
> languages, the same way we have several mechanisms to manipulate data that
> are not necessarily SQL.
>
>
>
> Be goode,
>
>
>
> --
>
> "Esta vez no fallaremos, Doctor Infierno"
>
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
>
> e-mail: diego.r.lopez@telefonica.com
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> ----------------------------------
>
>
>
>
> ------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
>
> _______________________________________________
> Nfvrg mailing list
> Nfvrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nfvrg
>
>