> -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Thursday, February 26, 2015 12:52 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Host field ignored in findResource > > On Wednesday 25 February 2015 14:02:47 Kesavan, Vijay S wrote: > > We support global discovery (all interfaces, all transports) and host > > discovery (specific host on a specified transport - requires > > identification information for that host eg. IP addr or MAC addr). > > Interface discovery itself might have sub-scenarios and the following > > ones are currently > > supported:
[ ... ] > > What is not supported is selecting the specific interface based on > > transport type. For example, if there are two WiFi interfaces on the > > platform, it is not possible to specify which WiFi interface to use. > > That has to change. > > If I have two IP-based connections, there's no a priori reason why one is > more preferable than than the other. So if I can select one, I should be able > to select the other too. For example, if IoTivity were integrated into a NAT firewall with one Ethernet interface going to the outside world and one (or more) interfaces on the inside network, the firewall would probably only want to find devices by multicast on the inside network, or at least have a different level of trust depending on whether a device is inside or outside the firewall. Bill.
