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

[Xiayinben <[e-mail]>]

For example,
A user’s intent is creating a connection from Boston office to Denver office;
BD(Business Designer) of Service Provider’s intent is creating user’s connection on demand and providing higher SLA guarantee to user’s flow than background flow(such as sync or backup flow)
Network administrator’s intent is monitoring physical connection’s utilization, when utilization over 80%, some background flows should be moved to other lower utilization  path.

In this example, providing higher SLA to user’s flow is BD’s intent but not user’s intent, because user doesn’t care about it.  Moving background flow to other path is network admin’s intent but not BD’s intent. How to move flow to other path is implementation detail in SDN controller but not network admin’s intent.

Use this example, I hope to express that a intent interface is related with a group of user’s role and what they are cared is what their intent elements.

Tianran started a thread for role based intent, we can combine discussion to there.

Yinben
发件人: Susan Hares [mailto:[e-mail]]
发送时间: 2015年6月3日 5:37
收件人: Xiayinben; 'PEDRO ANDRES ARANDA GUTIERREZ'; [e-mail]
抄送: [e-mail]; [e-mail]; Lifengkai (Fengkai)
主题: RE: [Nfvrg] 答复: [Ibnemo] Defining a Common Model for intent

Yinben and Pedro:

I agree you that the role of the user is more accurate than layer, but could you provide examples at lower layers.  At the user level, a user can signal intent to create a connection from Boston Office to Denver office across the whole network.

Sue

From: Nfvrg [mailto:[e-mail]] On Behalf Of Xiayinben
Sent: Monday, June 01, 2015 11:17 PM
To: PEDRO ANDRES ARANDA GUTIERREZ; Susan Hares; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; Lifengkai (Fengkai)
Subject: [Nfvrg] 答复: [Ibnemo] Defining a Common Model for intent

Pedro,

Agree with you.
According to your example, I think ‘intent’ should be classified by user’s role  more accuracy than by layer.
Sometime users’s role have layer relationship, but not always same layer relationship.

Best regards,
Yinben

发件人: Ibnemo [mailto:[e-mail]] 代表 PEDRO ANDRES ARANDA GUTIERREZ
发送时间: 2015年6月1日 17:15
收件人: Susan Hares; [e-mail]<mailto:[e-mail]>
抄送: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
主题: Re: [Ibnemo] Defining a Common Model for intent

Hi,

A small clarification proposal for draft 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