Thomas, 

See  below. I do not agree to the wording.

 And I suggest to change the definition of tenant system, which I identified as 
being perhaps a root cause of confusion.

Lothar

-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im Auftrag von Thomas 
Narten
Gesendet: Freitag, 19. April 2013 20:49
An: Pat Thaler
Cc: [email protected]; Qin Wu
Betreff: Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt

"Pat Thaler" <[email protected]> writes:

> In addition to Thomas's point, we should not restrict the number of
> physical NICs that a tenant system can have. Some tenant systems
> will have more than one physical NIC.

Agreed.

Lothar: Disagree - Given the current definition of tenant system, one would 
have to make a case differentiation throughout the document as follows:

Case A: Tenant System is a VM 
- In this case - which may be the most important one to many - above statement 
is wrong, because then the tenant system has zero physical NICs.

Case B: Tenant System is a bare metal server
- In this case above statement is true

Case C: Tenant System is "according to current definition" a router or 
firewall...
- in this case we start referring to router ports as NICs or pNICs, which may 
further increase confusion.

> We may describe some typical tenant systems as part of examining use
> cases, but NVO3 should define behavior in terms of the network
> interface, i.e. TSI, behavior and should not restrict tenant system
> architecture.

Another way of looking at it is that the TSI is an attachement
point/interface to the TS. The point where the TSI attaches to the TS
has two sides. On the tenant facing side, it appears to be a NIC. It
looks like a NIC, behaves like a NIC, etc. On the side facing away
from the tenant (e.g., the hypervisor in the case of a virtualized
system) we call it a TSI. The TSI side will have attributes that are
specific to NVO3.

Does that make sense?

Thomas

_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to