Esko Dijk <esko.d...@iotconsultancy.nl> wrote:
> To be fully complete the URIs that can be discovered should also
> include a port number, as they could be hosted at 5684 or any available
> UDP port - other than 5683.
> coaps://www.example.com:<port>/<est-root-resource>/<short-est>
>
coaps://www.example.com:<port>/<est-root-resource>/ArbitraryLabel/<short-est>
I didn't think that CoAP resource discovery supports port numbers, does it?
There are some issues with this, specifically because it interacts poorly
with the join proxy mechanism. (The proxy always forwards to a single port,
and only listens on a single port)
I supppose that's okay, for that usage can be banned for the zero-touch join
mechanisms that use a join proxy.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
