[Ibnemo] 答复: 答复: 答复: How to group/reuse definitions

["zhangyali (D)" <[e-mail]>]

Thanks Pedro. I think our understanding for “connection” and “connect/connectivity” is different. This topic has been discussed in our team many times. It’s really helpful for us to listen your views.

First of all, I want to clarify the meaning of connection. It refers to a kind of resources to allow the communication.  It’s not a physical link, but a abstraction of objects depended on communication. For example, a tunnel can be seen as a connection. For each of connection, user could assign bandwidth on it or not.

In your expression, “connect” refers to “connectivity” which specifies the communication rules or logic connection rather than resources depended on. (Please point it out if my understanding is wrong.)

In fact, we have considered if we need a new keyword to express connectivity, but there are some questions we need further consideration.

1.       If connection does not have bandwidth parameter, do the connection and connectivity have the same meaning?

2.       If the keyword of connectivity exists, when use the connectivity and when use connection?

3.       If user have to express connection before expressing connectivity? If not, do users know there are resources supporting for the connectivity?

Looking forward to your opinions.

Yali
发件人: PEDRO ANDRES ARANDA GUTIERREZ [mailto:[e-mail]]
发送时间: 2015年11月13日 19:31
收件人: zhangyali (D); Zhoutianran; Bert Wijnen (IETF); [e-mail]
主题: Re: 答复: 答复: [Ibnemo] How to group/reuse definitions

Comments inline

De: "zhangyali (D)" <[e-mail]<mailto:[e-mail]>>
Fecha: viernes, 13 de noviembre de 2015, 10:59
Para: paag <[e-mail]<mailto:[e-mail]>>, Zhoutianran <[e-mail]<mailto:[e-mail]>>, "Bert Wijnen (IETF)" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Asunto: 答复: 答复: [Ibnemo] How to group/reuse definitions


[Yali] Our expressions of new DMZ are similar, except you omit parameter lists. And firewall and l2-group(L2Switch in your expression, I think) are predefined node types, so I omit them.

    A key point/difference is how to express the connection/connectivity between the two nodes. I think resource is a essential element to allow the communication between nodes no matter where it is, that is, if there is not "real" connection between nodes, they will not be connected.

Sorry, but I would distinguish a ‘logical patch panel’ implemented in an Open VirtualSwitch inside a server blade or even inside a data centre supporting SDN, NFV, etc. from a real link (i..e. my second example). Why? Because these connections have no specific characteristics, while a "connection over a cable” has characteristics like Bandwidth etc.


    And what if user wants to assign a bandwidth in this connection? So I am not sure if the "Connect" includes enough information.

The Connect is used when I have no specific requirements. In an example related more to ETSI/NFV, I could see the Connect as the logical connection between Virtual Network Function Components (VNFCs) inside a VNF.

My .02 cents, /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/ Zurbarán,12
28010 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