Proxy discovery Sample Clauses
Proxy discovery. Proxies will be used in CoAP networks for at least two major reasons:
1. Http/coap proxy.
2. Proxy of service on battery-less device. The first proxy is probably implemented as forward proxy, while the latter is probably implemented as backward proxy. The battery-less device will only rarely (i.e. when it is not sleeping) and during installation, answer the GET /.well-known/core request. The return data is used by the installation tool to make the proxy device return the same resource names on /.well-known/core as is returned by the sleeping device. An installation tool installs on the proxy all the resources of the sleeping device for which the proxy is assumed to answer. Consequently, the proxy is discovered as a multi-server host with as many path names as the proxies sleeping servers. The servers on sleeping devices should not be discoverable via DNS-SD. However, AAAA records are generated for the sleeping device host name. This host name is used by the proxy to subscribe to the "sporadic" services of the sleeping device. Figure 15 represents the network architecture with heterogeneous devices. The CoAP gateway connects one link with two legacy devices with the wireless CoAP network composed of three CoAP hosts. The CoAP hosts can freely exchange data representations according to the CoAP protocol over the wireless 6LoWPAN network. The host can send data representations to the CoAP gateway which passes them on to the specified legacy host. The legacy device returns data to the requesting CoAP host via the same gateway. The CoAP hosts can address the legacy devices behind the gateway in at least 4 ways: All devices of legacy network share the URI with the CoAP gateway. Every legacy device is a resource for the gateway as seen from the CoAP host. Consequently, the CoAP host sends the message to the IP address of the gateway and the gateway parses the URI-Path to determine the specified legacy device. All devices of legacy network have IP addresses different from the IP address of the gateway. Consequently, a CoAP host sends the message to the IP address of the specified device. The routing protocol on the CoAP network makes the message arrive at the CoAP gateway. The gateway determines the specified legacy device from the destination IP address. All devices of legacy network have different authorities. The authorities of the legacy device resolve to an IP address of the gateway. This means that the possibly lengthy authority names need to be transm...
