> -----Original Message-----
> From: Ace <ace-boun...@ietf.org> On Behalf Of Michael Richardson
> Sent: Monday, September 24, 2018 9:27 AM
> To: consulta...@vanderstok.org
> Cc: Esko Dijk <esko.d...@iotconsultancy.nl>; Panos Kampanakis (pkampana)
> <pkamp...@cisco.com>; ace@ietf.org
> Subject: Re: [Ace] ace-coap-est: unclear definition of /.well-known/est
URI
>
>
> Peter van der Stok <stokc...@bbhmail.nl> wrote:
> > What do I read? when you do GET coap://example.com/.well-known/core
> > The discovery is on port 5683. When you do GET
> > coaps://example.com/.well-known/core the discovery port is 5684.
>
> yes, the question is, when you ask:
>
> coap://example.com/.well-known/core?rt=ace.est
>
> do you expect to get back a pointer to:
>
> coaps://example.com/est
>
> > RFC 7030 does not ask a port number from IANA. And a search through
> > IANA port numbers on "est" does not yield anything.
>
> It does not.
> a) it doesn't do discovery, but just uses /.well-known directly.
> b) it assumes https://
Is there any reason to assume that you need a different port from the
default pair of coap ports? Knowing what the protocol and host name will
point it to the correct location and you have the URI path to go to the
correct resource on that server.
Jim
>
> --
> ] Never tell me the odds! | ipv6 mesh
networks [
> ] Michael Richardson, Sandelman Software Works | network
architect [
> ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails
[
_______________________________________________
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
