I see. Two cases: 1) if the oracle is on NVE, the control plane between the NVE and the oracle is just internal API. You will need the control plane between the oracles. 2) if the oracle is not on NVE, the control plane between the NVE and the oracle need some protocols. You may still need the control plane between the oracles if there are multiple.
Logical centralized means no one-on-one mapping between NVE and oracle, right? Lucy > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Larry Kreeger (kreeger) > Sent: Wednesday, April 10, 2013 2:37 PM > To: Lucy yong; Fedyk, Donald (Don); Lou Berger; Linda Dunbar > Cc: Truman Boyes; [email protected] > Subject: Re: [nvo3] NVO3 Terminology changes > > Lucy, > > We are discussing a single name that covers both a centralized and a > distributed model for the oracle. The control plane between the NVE > and > the oracle would not be different if the oracle is centralized vs > distributed. That is why we have been saying that the oracle is > "logically centralized". This is where an Architecture document would > be > useful to clarify these things. > > - Larry > > On 4/10/13 12:23 PM, "Lucy yong" <[email protected]> wrote: > > >Hi Larry, > > > >I am fine with NVC name. > > > >One clarification question: does this mean that we will work out both > NV > >controller based NVo3 solution and Control Plane based NVo3 solution? > The > >latter is in "distributed mode". > > > >Cheers, > >Lucy > > > >> -----Original Message----- > >> From: [email protected] [mailto:[email protected]] On Behalf > Of > >> Fedyk, Donald (Don) > >> Sent: Wednesday, April 10, 2013 2:11 PM > >> To: Lou Berger; Linda Dunbar > >> Cc: Truman Boyes; [email protected]; Larry Kreeger (kreeger) > >> Subject: Re: [nvo3] NVO3 Terminology changes > >> > >> I'd vote for NVC > >> > >> PS. Most Layer 2 Ethernet technologies are full of V's (VLANs, VLAN > >> Ids). > >> > >> -----Original Message----- > >> From: [email protected] [mailto:[email protected]] On Behalf > Of > >> Lou Berger > >> Sent: Wednesday, April 10, 2013 1:04 PM > >> To: Linda Dunbar > >> Cc: Truman Boyes; [email protected]; Larry Kreeger (kreeger) > >> Subject: Re: [nvo3] NVO3 Terminology changes > >> > >> > >> > >> On 4/10/2013 12:22 PM, Linda Dunbar wrote: > >> >>> We are talking about an entity that has information on inner- > outer > >> >>> address mapping, and potentially other host (VMs or Servers) > >> >>> location information. This entity is orthogonal to > ³virtualization². > >> >> > >> >> Do I understand your point correctly, that you're suggesting that > >> >> this discussion is orthogonal to the "V" in technologies such as > >> >> L3VPN, L2VPN/EVPN, NVGRE, VXLAN, ...? > >> > > >> > [Linda] and TRILL, and PBB ... > >> > >> So how do you feel about the name of the WG? > >> (Particularly, the "V" and "O3" parts...) > >> > >> Lou > >> > >> > > >> >> > >> >> Lou > >> >> > >> >>> > >> >>> > >> >>> > >> >>> Therefore, I think ³Network Mapping Authority² or ³Host Location > >> >>> Information Service² is more accurate. > >> >>> > >> > _______________________________________________ > >> > nvo3 mailing list > >> > [email protected] > >> > https://www.ietf.org/mailman/listinfo/nvo3 > >> > > >> _______________________________________________ > >> nvo3 mailing list > >> [email protected] > >> https://www.ietf.org/mailman/listinfo/nvo3 > >> _______________________________________________ > >> nvo3 mailing list > >> [email protected] > >> https://www.ietf.org/mailman/listinfo/nvo3 > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
