Looks good, and I agree that Gateway is more clear.
On Apr 17, 2013, at 5:38 PM, Thomas Narten <[email protected]> wrote: > Hi Qin. > > Thanks for the suggested text. It helps clarify the concerns you > have. From your proposal, you seem to be raising the following: > > 1) We use the term "router" to refer to the device that relays traffic > between devices connected to two different VNs, as well as for > relaying traffic between devices A and B, where A is attached to a VN, > while B is a conventional device not connected to a VN at all (e.g., > it could be out on the Internet or on the DCN). > > You use the term "edge device" for this, but I think that is even less > clear. I used the term "router" because it is acting much like a > traditional router. It supports IP, and it it relays traffic between > devices connected to different IP subnets. > > Maybe the term "gateway" would be better? > > 2) you've added some text, but I'm having difficulty seeing what it is > trying to clarify. > > That said, how about I reword the first paragraph to say: > > OLD: > > Another problem area relates to the routing of traffic into and > out of a virtual network. A virtual network may have two routers > for traffic to/from other VNs or external to all VNs, and the > optimal choice of router may depend on where the VM is > located. The two routers may not be equally "close" to a given > VM. The issue appears both when a VM is initially instantiated on > a virtual network or when a VM migrates or is moved to a different > location. After a migration, the VM's closest router for such > traffic may change, i.e., the VM may get better service by > switching to the "closer" router, and this may improve the > utilization of network resources. > > New: > > > Another problem area relates to the optimal forwarding of traffic > between peers that are not connected to the same virtual network. > Such forwarding happens when a host on a virtual network > communicates with a host not on any virtual network (e.g., an > Internet host) as well as when a host on a virtual network > communicates with a host on a different virtual network. A > virtual network may have two (or more) gateways for forwarding > traffic onto and off of the virtual network and the optimal choice > of which gateway to use may depend on the the set of available > paths between the communicating peers. The set of available > gateways may not be equally "close" to a given destination. The > issue appears both when a VM is initially instantiated on a > virtual network or when a VM migrates or is moved to a different > location. After a migration, for instance, a VM's best-choice > gateway for such traffic may change, i.e., the VM may get better > service by switching to the "closer" gateway, and this may improve > the utilization of network resources. > > Does that help? > > 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
