search

SanKumar2015 / EST-coaps

EST over CoAPs IETF draft
1 stars 1 forks source link

Ports in the discovery (Klaus WGLC review 2/27/2019) #144

Closed csosto-pk closed 5 years ago

csosto-pk commented 5 years ago

From Klaus

Discoverable port numbers can be returned in the response payload." -- Now I'm wondering if that's actually permitted by RFC 6690.

csosto-pk commented 5 years ago

I saw http://www.example.com/sensors/t123;anchor="/sensors/temp";rel="describedby in a couple of examples in RFC6690. I also saw it in https://tools.ietf.org/html/draft-ietf-core-resource-directory that shows

"Res: 2.05 Content coap://[2001:db8:3::123]:61616/temp;rt="temperature"; anchor="coap://[2001:db8:3::123]:61616"

Jim suggested the anchor is not needed, but I think the example is OK to include the port.

csosto-pk commented 5 years ago

Klaus is confirming.

I'm not sure. RFC 6690 is really weird. Let me get back to you on this.

csosto-pk commented 5 years ago

From Jim

RFC 6690 references to 3986 for URI-reference RFC 3986 defines the following ABNF URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] hier-part = "//" authority path-abempty / path-absolute / path-rootless / path-empty URI-reference = URI / relative-ref authority = [ userinfo "@" ] host [ ":" port ] Thus yes port is just fine to include

So closing this issue as it looks OK to use the ports.