Hi Linda, all, I fully agree with Diego about the North-South coordinates thing.
Client-facing interface and NSF-facing interface terms are just fine to refer to these interfaces. Cheers, Med De : I2nsf [mailto:i2nsf-boun...@ietf.org] De la part de Diego R. Lopez Envoyé : vendredi 24 juin 2016 07:40 À : Linda Dunbar Cc : I2NSF@ietf.org Objet : Re: [I2nsf] Should we call "South Bound Interface" for the interface between "controller <-> NSF", and "North Bound Interface" for the interface between "Client <-> controller"? Hi Linda, I have always found profoundly wrong the northbound and southbound terms, as they imply an absolute reference system that becomes challenged very soon, and then you have to start qualifying where are you talking north- or southbound. As an example, think on the current drafts dealing with SDN controllers at the “I2NSF southbound” interface, using it as a “SDN northbound”. I find this entirely confusing. So please let’s confine the North-South coordinates to the places where we can not get rid of them just for historical reasons. I’d like to maintain the "service" and “capability” terms, and I do not understand: * Why you say that capabilities of NSFs can be exposed through the service interface. Even if that was the case, the security controller should not expose them as “NSF capabilities” but as “security controller services", as the controller must abstract the underlying NSFs * What you refer with “Event capability”, “Condition capability” and “Action capability”. NSF capabilities should be announced through the registration interface and managed through the capability interface (what you call southbound in your messages) according to the policies expressed in terms of ECA rules, but these rules (or their components) are not part of the capabilities whatsoever… Be goode, On 24 Jun 2016, at 24:31 , Linda Dunbar <linda.dun...@huawei.com<mailto:linda.dun...@huawei.com>> wrote: I2NSF WG: Need your opinion for a good name to represent “Client Facing Interface” and “NSF Facing Interface” of the I2NSF reference model: +-----------------------------------------------------+ | I2NSF Client | | E.g. Overlay Network Mgnt, Enterprise network Mgnt | | another network domain’s mgnt, etc. | +----------+------------------------------------------+ | | Client Facing Interface | +-----+---------------+ |Network Operator mgmt| +-------------+ | Security Controller | < --------- > | Developer’s | +----------+----------+ Registration | Mgnt System | | Interface +-------------+ | | NSF Facing Interface | +----------------------+----------------------------+ | | | | +---+--+ +------+ +------+ +--+---+ + NSF-1+ ------- + NSF-n+ +NSF-1 + ----- +NSF-m + . . . +------+ +------+ +------+ +------+ Vendor A Vendor B During the I2NSF early stage (before the WG was created), "capability interface" was used to represent the interface between controller <-> NSF, and "service interface" was used to represent the interface between the Client <-> controller. As many people use the terminologies loosely, the "Capability Interface" being interchangeably used with "Capability Layer", and "Service Interface" being interchangeably used with "Service Layer". The I2NSF Terminology Draft has defined the "Capability Layer" (independent of which interface to the controller) for exposing the capability of a domain (over Client Facing Interface), or for exposing the capability of a NSF (over the NSF Facing Interface). By this definition, ECA Policy’s "Event" capability can be discovered independently from the "Condition" capability, or "Action" capability. Therefore, continue using the “Capability Interface” can cause more confusion in the future as its sound is too close to the “Capability layer”. Therefore, we are asking people to state which of the following options should be used: 1. Use “Client Facing Interface” for "Client <-> controller"; and “NSF Facing Interface” for "controller <-> NSF", 2. Use “Controller North Bound Interface” for "Client <-> controller"; and “Controller South Bound Interface” for “controller <-> NSF", or Or you can provide a better option. Thanks, Linda _______________________________________________ I2nsf mailing list I2nsf@ietf.org<mailto:I2nsf@ietf.org> 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: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> 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 I2nsf@ietf.org https://www.ietf.org/mailman/listinfo/i2nsf
