The I2NSF framework currently uses “client-facing –interface”.
Either “Tenant-facing-interface” or “User-facing-interface” would be equivalent.

From: Diego R. Lopez []
Sent: Monday, October 17, 2016 4:36 PM
To: Linda Dunbar <>
Cc: John Strassner <>;
Subject: Re: [I2nsf] Definition for "Consumer" in I2NSF terminology , in the 
context of "Client Facing Interface"

And what about “tenant or “user" rather than “customer”?

Be goode,

On 17 Oct 2016, at 22:28 , Linda Dunbar 
<<>> wrote:


Maybe we should call it “customer-facing-interface” instead of 


From: I2nsf [] On Behalf Of Linda Dunbar
Sent: Monday, October 17, 2016 3:23 PM
To: John Strassner <<>>
Subject: [I2nsf] Definition for "Consumer" in I2NSF terminology , in the 
context of "Client Facing Interface"


There are two types of interface described in I2NSF framework:
-        one is NSF facing interface, over which  rules  or policies can be 
expressed based on ports/IP addresses for packets traversing through a NSF;
-        another is the interface for Clients, users, tenants, to express/query 
rules that are expressed in users own ID, address domains, etc. Commonly called 
“Client facing interface”.

You have suggested to use “Consumer facing Interface”. But the definition of 
“Consumer” in I2NSF Terminology -01, doesn’t really reflect the idea of rules 
being expressed from the perspective of clients or users.

If we use this terminology, “Consumer” interface can also face NSFs as well.

  Consumer:  A Consumer is a Role that is assigned to an I2NSF
      Component that can receive information from another I2NSF
      Component.  See also:  Provider, Role.

Can you clarify ?

Thanks, Linda
I2nsf mailing list<>

"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

Tel:    +34 913 129 041
Mobile: +34 682 051 091

I2nsf mailing list

Reply via email to