On Monday 27 July 2015 07:42:10 ??? wrote: > 3. A stand-alone router could be made very capable without burdening the > IoTivity stack. It would need parts of the CA layer in order to do its job. > Specifically, it would need access to the network adapters and the code > that multiplexes them. (I don??t think it needs RI layer or the upper > layers of CA, as we shall see.) > >> In our design, Routing capabilities are deployed in standalone IoTivity > >> routers. Endpoints just need to add extra destination information once > >> they send request or response. It may be less than 5 lines of source > >> code and we don??t think its burden considering feature it enables.
Please make it so that the endpoints do not know at all that the message is being routed. They should be able to talk to the device without knowing it's proxying or being proxied. > 5. I believe the attempt to handle routing within the > CoAP framework will create problems. Among the problems is that doing so > requires that the routed CoAP messages will need to be decrypted and > encrypted at each gateway. This requires establishing separate trusted > relations with every intermediate node, which adds considerable overhead, > and results in lower overall security, as each intermediate node becomes an > attack surface. > >> A new protocol to transmit the routing adds more problems than using the > >> CoAP framework. We do not think it??s an issue. Agreed, but see above. The endpoints should use CoAP and nothing else, but they should not need to know that the message was proxied or need to request that it be proxied. > 6. Network routing is almost always best handled out-of-band. I don??t think > this needs to be a CoAP issue. While we have agreed that resource messaging > will be handled with CoAP protocol, there is no requirement that all > messaging done by IoTivity use CoAP. (For example, video streaming over > CoAP would be problematical.) > >> Its already out-of band. End nodes doesnot know how the message is > >> transmitted . I agree with "how", but I also insist on "if". -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
