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

"Susan Hares" <shares@ndzh.com> Fri, 05 June 2015 17:56 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 51B1E1A0045 for <ibnemo@ietfa.amsl.com>; Fri, 5 Jun 2015 10:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.754
X-Spam-Level:
X-Spam-Status: No, score=-98.754 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 mt_Cv2YeK-b6 for <ibnemo@ietfa.amsl.com>; Fri, 5 Jun 2015 10:56:27 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id E39351A005F for <ibnemo@ietf.org>; Fri, 5 Jun 2015 10:56:26 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.80.157;
From: "Susan Hares" <shares@ndzh.com>
To: "'Natale, Bob'" <RNATALE@mitre.org>, "'DIEGO LOPEZ GARCIA'" <diego.r.lopez@telefonica.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> <CY1PR09MB09228415B704C5C0372FB229A8B20@CY1PR09MB0922.namprd09.prod.outlook.com>
In-Reply-To: <CY1PR09MB09228415B704C5C0372FB229A8B20@CY1PR09MB0922.namprd09.prod.outlook.com>
Date: Fri, 5 Jun 2015 13:56:25 -0400
Message-ID: <024101d09fb8$f10945e0$d31bd1a0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0242_01D09F97.69FC39C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIyszWq5a5j3lzymrlGmCaVlNwkHQHyOFyyAiYPs3QCCna0QQGbdYxcAKUWXW0A8i9pV5yPXu0Q
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/f3EHfWierRrkYX9X0kG0hKm_dyo>
Cc: nfvrg@irtf.org, draft-xia-ibnemo-icim@tools.ietf.org, "'zhangyali \(D\)'" <zhangyali369@huawei.com>, ibnemo@ietf.org
Subject: Re: [Ibnemo] =?utf-8?b?W05mdnJnXSAgIOetlOWkjTogIOetlOWkjTogIERlZmlu?= =?utf-8?q?ing_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:56:29 -0000

Bob: 

+1 on Diego’s statement of need. 

+1 on your comment to start with the business user and funnel through SLAs/Service offerings. 

 

BGP provider roles I described are really business roles that get cast into BGP identities.  We should stay with business policies first.  I tried to provide this email previous to this one. 

 

Sue 

 

From: Natale, Bob [mailto:RNATALE@mitre.org] 
Sent: Friday, June 05, 2015 12:02 AM
To: DIEGO LOPEZ GARCIA; Susan Hares
Cc: nfvrg@irtf.org; PEDRO ANDRES ARANDA GUTIERREZ; draft-xia-ibnemo-icim@tools.ietf.org; zhangyali (D); ibnemo@ietf.org
Subject: RE: [Nfvrg] [Ibnemo] 答复: 答复: Defining a Common Model for intent

 

Major +1 from me Diego’s statement of the need … absolutely on the mark, in my judgment.

 

Two things I have found confusing in the threads on this topic:

 

- Use of “role” (and I think Diego may be questioning this too) … I think I understand the usage, but that term carries a certain specificity that is too rigid in the context of understanding the levels of translation usually modeled into policy-based management solutions … “views” or “perspectives” or something like that is more common.

 

- The targeting of “user” intent in this discussion … other than where “user” is proxy for “operator” or “provider” or something like that (and I think Bert might have touched on that too), I don’t think we should focus on user intents yet. I would agree that user intents will ultimately be addressed via successful intent-based policy management solutions but that’s too aggressive for where we are now … better to assume that user intents come into the service provider business model at the top and are mediated by that business model (e.g., via service offerings, SLAs, etc.) and represented in the intents that the service provider/network operator use to control network behavior on behalf the their users.

 

Avanti,

BobN

 

From: Nfvrg [mailto:nfvrg-bounces@irtf.org] On Behalf Of DIEGO LOPEZ GARCIA
Sent: Thursday, June 04, 2015 4:17 PM
To: Susan Hares
Cc: nfvrg@irtf.org; PEDRO ANDRES ARANDA GUTIERREZ; draft-xia-ibnemo-icim@tools.ietf.org; zhangyali (D); ibnemo@ietf.org
Subject: Re: [Nfvrg] [Ibnemo] 答复: 答复: 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