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

Xiayinben <xiayinben@huawei.com> Tue, 02 June 2015 03:17 UTC

Return-Path: <xiayinben@huawei.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 DB0651A90FD for <ibnemo@ietfa.amsl.com>; Mon, 1 Jun 2015 20:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 WiBX71brV1e8 for <ibnemo@ietfa.amsl.com>; Mon, 1 Jun 2015 20:17:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46B091A909D for <ibnemo@ietf.org>; Mon, 1 Jun 2015 20:17:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTF98892; Tue, 02 Jun 2015 03:17:24 +0000 (GMT)
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 2 Jun 2015 04:17:23 +0100
Received: from NKGEML507-MBS.china.huawei.com ([169.254.6.7]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Tue, 2 Jun 2015 11:17:10 +0800
From: Xiayinben <xiayinben@huawei.com>
To: PEDRO ANDRES ARANDA GUTIERREZ <pedroa.aranda@telefonica.com>, Susan Hares <shares@ndzh.com>, "nfvrg@irtf.org" <nfvrg@irtf.org>
Thread-Topic: [Ibnemo] Defining a Common Model for intent
Thread-Index: AQHQnEuWiYNLyKOVx0mmcojlB5lFfZ2Ygwyw
Date: Tue, 2 Jun 2015 03:17:10 +0000
Message-ID: <5FD31D8EDBF4EC468B36D86F04FDB2E873827068@nkgeml507-mbs.china.huawei.com>
References: <010001d09b13$7b0e19f0$712a4dd0$@ndzh.com> <D191EC7F.1D569%pedroa.aranda@telefonica.com>
In-Reply-To: <D191EC7F.1D569%pedroa.aranda@telefonica.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.53.87]
Content-Type: multipart/alternative; boundary="_000_5FD31D8EDBF4EC468B36D86F04FDB2E873827068nkgeml507mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/yB7FPzfeSYrS0Y4EGuB-FyHQJdQ>
Cc: "draft-xia-ibnemo-icim@tools.ietf.org" <draft-xia-ibnemo-icim@tools.ietf.org>, "ibnemo@ietf.org" <ibnemo@ietf.org>
Subject: [Ibnemo] =?utf-8?b?562U5aSNOiAgRGVmaW5pbmcgYSBDb21tb24gTW9kZWwg?= =?utf-8?q?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: Tue, 02 Jun 2015 03:17:31 -0000

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:ibnemo-bounces@ietf.org] 代表 PEDRO ANDRES ARANDA GUTIERREZ
发送时间: 2015年6月1日 17:15
收件人: Susan Hares; nfvrg@irtf.org
抄送: draft-xia-ibnemo-icim@tools.ietf.org; ibnemo@ietf.org
主题: 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