Hi, :
Sorry, my figure is filtered out. So I send it again.
Regards!
-Qin
发件人: Larry Kreeger (kreeger) [mailto:[email protected]]
发送时间: 2013年4月18日 0:56
收件人: Qin Wu; Anoop Ghanwani; Black, David
抄送: [email protected]; Reith, Lothar
主题: Re: [nvo3] 答复: 答复: 答复: 答复: NVO3 Terminology changes
>Hi Qin,
>A VM is one possible implementation of a Tenant System. I have not seen anyone
>suggesting that a Tenant System get more granular than that.
[Qin]: Okay, I should agree with you since I didn’t see more granularity either
and still doubt about that.
>Regarding what defines a TSI, someone could choose any branch in the tree
>below to define as the TSI. I was assuming that the TSI would be at point A
>below in the tree. However, point B would correspond the
>VAP. Pat had mentioned having the TSI at point D. I think if we were to
>define the TSI to be either point C or point D, then it would depend on the
>service being given (L2 or L3). I would prefer it to be at point A or B.
>>>>
VNIC-+-VN-+-MAC-+-IP
^ | | +-IP ...
| | |
| | +-MAC-+-IP
| | +-IP ...
| |
| +-VN-+-MAC-+-IP
| ^ | +-IP ...
| | |
| | +-MAC-+-IP
| | ^ +-IP ...
| | | ^
| | | |
A B C D
>>>>
[Qin]:Firstly I agree with Pat about having TSI at point D, In the meanwhile I
think we could also having TSI at point B.
Point C doesn't make sense to me since each VNIC only MUST be assigned one
unique MAC address based on my understanding, when VNIC connects multiple VNs,
you can not use one MAC address to distinct different TSI.
Point A is also having problem, as I mentioned earlier below, , if we regard
vNIC as TSI, you may have case to associate one TSI with multiple NVEs when
vNIC connect to multiple VNs.
Secondly, VNIC Containment Relationship in the figure you described above
introduces a little bit confusing, since you didn't distinguish the entity or
objects from identifiers since vNIC and VN are both objects while MAC address
and IP address are both identifier. So I proposed to change the figure you
described above as follows:
+---------------------+
| |
| VM (Tenant System) |
| |
+-+--------+--------+-+
| | |
| | |
| | |
+ + ...... +
vNIC1/pNIC1 vNIC2 vNICx
|
|
|--------+------+------+
| | | |
| | | |
VN1 VN2 VN3 Non-VN
Tenant System Interfaces(TSI):
TSIa [VNID1,MAC1,IP addr1]corresponding to vNIC
TSIb [VNID2,MAC1,IP addr2]corresponding to vNIC
TSIc [VNID3,MAC1,IP addr3]corresponding to vNIC
TSId [ ,MAC1,IP add4] corresponding to pNIC
You don’t need to care about the relation between vNIC and TSI is 1:1 or 1: N.
Each TSI is identifier by combination of VNID, MAC address of vNIC, IP address
of vNIC,
when going to pNIC, TSI can be identified by only combination of MAC address
and IP address, not necessary adding VNID.
Note that for one vNIC, it uses the same MAC address for all the TSIs belonging
to the same vNIC.
For L2 and L3 service distinction, you can add additional identifier to [VNID,
MAC address, IP address], e.g., VLAN Tag to distinct L2 from L3.
I think this proposed change above also considers both NIC and vNIC and address
the concerns what we discussed on this list and is also still getting in line
with what pat observed.
>> - Larry
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
