Re: [Ibnemo] Defining a Common Model for intent

"Susan Hares" <shares@ndzh.com> Mon, 01 June 2015 21:33 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 159671A0063 for <ibnemo@ietfa.amsl.com>; Mon, 1 Jun 2015 14:33:11 -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 GbKTSQmapvF2 for <ibnemo@ietfa.amsl.com>; Mon, 1 Jun 2015 14:33:09 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id F1ADE1A005C for <ibnemo@ietf.org>; Mon, 1 Jun 2015 14:33:08 -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: "'PEDRO ANDRES ARANDA GUTIERREZ'" <pedroa.aranda@telefonica.com>, <nfvrg@irtf.org>
References: <010001d09b13$7b0e19f0$712a4dd0$@ndzh.com> <D191EC7F.1D569%pedroa.aranda@telefonica.com>
In-Reply-To: <D191EC7F.1D569%pedroa.aranda@telefonica.com>
Date: Mon, 1 Jun 2015 17:32:50 -0400
Message-ID: <022801d09cb2$88c41d10$9a4c5730$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0229_01D09C91.01B58A50"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFmUXpwBxWy/ToZog2PwFtky8zSWAILX45CnlxmiOA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/acyLV4TAT-RRHYFf1FQ2HdhjVrE>
Cc: draft-xia-ibnemo-icim@tools.ietf.org, ibnemo@ietf.org
Subject: Re: [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: Mon, 01 Jun 2015 21:33:11 -0000

Pedro:

 

I like this addition to the draft.   Does the “new-sue” editorial addition is included to “smooth” the English. 

 

Sue 

 

 

 

For network administrators, <new-sue> an example of intent<new-sue> can be <new>defining a network topology like a router connected to a firewall, connected to a load balancer and this to two L2 networks where WWW servers sit or specifying the</new> operations on a set of devices such as configuring IP addresses on network servers in a data center.

 

 

From: PEDRO ANDRES ARANDA GUTIERREZ [mailto:pedroa.aranda@telefonica.com] 
Sent: Monday, June 01, 2015 5:15 AM
To: Susan Hares; nfvrg@irtf.org
Cc: draft-xia-ibnemo-icim@tools.ietf.org; ibnemo@ietf.org
Subject: Re: [Ibnemo] Defining a Common Model for intent

 

Hi,

 

A small clarification proposal for draft  <https://datatracker.ietf.org/doc/draft-xia-ibnemo-icim/> https://datatracker.ietf.org/doc/draft-xia-ibnemo-icim/ .

 

In section 2.4, I would leave the following as a paragraph

For example, in the network area the intent of end-users could be
safe connectivity between two sites which a technology independent
and device independent requirement. For business-based network
designers, the network connectivity can be selected which is device-
independent but technology specific. An example of the business-based
technology is the L3VPN. 
And change:
For network administrators, intent can be
specific operations on a set of devices such as configuring IP
addresses on network servers in a data center.

To

 

For network administrators, intent can be <new>defining a network topology like a router connected to a firewall, connected to a load balancer and this to two L2 networks where WWW servers sit or specifying the</new> operations on a set of devices such as configuring IP addresses on network servers in a data center.
 
Rationale behind this is again, that intent should be anything that is invariant and that expresses what a network operator/administrator may need to do, as opposed to how he would do that, i.e. The router is a HW device from vendor X or a virtual machine running a specific routing daemon over a given data-path implementation.
Best, /PA

---

Dr. Pedro A. Aranda Gutiérrez

 

Technology Exploration -

Network Innovation & Virtualisation

email: pedroa d0t aranda At telefonica d0t com

Telefónica, Investigación y Desarrollo

C/ D. Ramón de la Cruz,84

28006 Madrid, Spain

 

Fragen sind nicht da, um beantwortet zu werden.

Fragen sind da, um gestellt zu werden.

Georg Kreisler

 

  _____  


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