Hi Maria, > > > > [Lucy] Original subject is about to construct a tenant network > that > > > > contain multiple subnets. > > > > > > This is a complication that is not desirable as it is bad idea to > > have > > > to multiple subnets per VLAN. > > [Lucy] Agree. That is the reason I don't see EVPN fit it and propose > to > > have a new service type. > > Do you say that IPVPN-end-system can be used to construct a tenant > > network that contain multiple subnets? > > You could support multiple subnets in one IPVPN-end-system VPN but this > is a bad network design. As I said, this is like having multiple > subnets per VLAN. [Lucy] Thank you to clarify that again, it is clear to me now. So what you suggest that a good design is to construct several IPVPN-end-system VPNs for a tenant network that contain several subnets. may I understand you correct?
Lucy > > > or you say that for a virtual > > network overlay, there is no need for IP subnet schema. Just use IP > > network address /32 at all tenant systems. > > As I said before, a VM belonging to a subnet is one of configuration > models and should be supported. An IP subnet is a CUG that corresponds > to one VPN. > > Maria _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
