In Section 3.2, we described two data path designs. Assuming IP addresses are assigned to waypoints, the in-bound connectivity achieved by each design is as follows. For the regular data path design without support for multi-homing:
With multi-homing support, since port or identifier numbers are used for connection demultiplexing, the following additional restriction is imposed:
Thus, as long as is greater than the average number of simultaneous sessions to non-IP hosts opened by a typical IP initiator, say , in-bound connectivity can be restored to a high level.
To summarize AVES's deployability, waypoints can be independently deployed; NAT gateways need to be extended, however this is necessary and acceptable because their operators have the right incentives to perform the upgrade. To deploy AVES for an intranet, upgrading the local DNS server software will provide the best performance. However, even when it is impossible to upgrade existing DNS servers, the delayed binding technique can be used at the expense of lowered performance. In all cases, no existing IP hosts or IP network routers need to be modified.