All, The connectivity abstraction currently uses two ports assigned by IANA to CoAP.
* 5693 udp CoAP * 5694 udp CoAp DTLS I have two questions about this. * Are we specifying and committing to sufficient interoperability with CoAP to use the CoAP ports? * Should we apply for our own port assignments to help establish our "brand" and give future flexibility. In addition, we start our unicast server port numbering at 5298. If we can't bind to 5298, we try successive ports (5299, 5300, etc.) until we successfully bind. I believe this is a violation of both the spirit and letter of the port usage RFCs. While testing for usage means that we will run, it also means that once we are successful at binding a port, subsequent attempts to bind by the application that legitimately "owns" that port will fail, and we will be at fault. We don't need a port assignment for Unicast. We should let the OS assign us a number, and everything will work from there. We need to use well-known ports for multicast but not for unicast. We need to address both these issues before we are seen as "bad actors". John Light OTC CSD OIC Development -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150302/6ba4078c/attachment.html>
