Hi, Not exactly. We could say that we have two type of I2NSF clients:
* I2NSF applications, sending inquiry/request for Flow Security Policy to a controller (which controls a security domain) * I2NSF controllers, that collect and expose NSF capabilities, and send Flow Security Policy to individual NSFs within a security domain (Note the use of the term “security domain” rather than “network”) Be goode, On 21 Jun 2016, at 14:02 , Linda Dunbar <[email protected]<mailto:[email protected]>> wrote: Diego, Do you mean that we should abandon the general “I2NSF Client” term, instead having the following two separate definitions? Controller Client: I2NSF applications that send inquiry/request for Flow Security Policy to a controller (who controls a network). For example: an overlay network controller sending inquiry/request for Flow Security Policy to an underlay network controller NSF Client: I2NSF controllers that send Flow Security Policy to individual NSFs Linda From: DIEGO LOPEZ GARCIA [mailto:[email protected]] Sent: Monday, June 20, 2016 4:46 AM To: Linda Dunbar Cc: John Strassner; Xialiang (Frank); Susan Hares; [email protected]<mailto:[email protected]> Subject: Re: [I2nsf] I2NSF Terminology draft : Is it better to have two distinct terminologies to differentiate the “Client to controller” from the “Client to NSFs”? Hi Linda, The obvious suggestion that comes to my mind is to use the SDN analogy, and call the clients of type 1 “I2NSF applications” and those of type 2 “I2NSF controllers” Be goode, On 18 Jun 2016, at 23:08 , Linda Dunbar <[email protected]<mailto:[email protected]>> wrote: Dear authors of the I2NSF terminology draft: I2NSF framework has two different types of clients: 1. One type of client sending inquiry/request for Flow Security Policy to a controller (who controls a network). For example: an overlay network controller sending inquiry/request for Flow Security Policy to an underlay network controller. 2. Another type of client is the controller sending Flow Security Policy to individual NSFs. Simply put, the client described in 1) is making request to the (I2NSF) Controller (i.e. the controller’s North Bound Interface); and the “client” described in 2) is making request to the NSFs ( i.e. the controller’s South Bound Interface). It seems to me that the “I2NSF Client” described in the current I2NSF Terminology draft is performing the “controller” function, and the “I2NSF Agent” is residing in the NSF for receiving the flow security policies from the “Controller”. Is it better to have two distinct terminologies to differentiate the “Client to controller” from the “Client to NSFs”? Any suggestions? Linda _______________________________________________ I2nsf mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/i2nsf -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D http://people.tid.es/diego.lopez/ e-mail: [email protected]<mailto:[email protected]> 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 -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D http://people.tid.es/diego.lopez/ e-mail: [email protected] 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
_______________________________________________ I2nsf mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2nsf
