> -Original Message-
> From: Ace On Behalf Of Michael Richardson
> Sent: Monday, September 24, 2018 9:27 AM
> To: consulta...@vanderstok.org
> Cc: Esko Dijk ; Panos Kampanakis (pkampana)
> ; ace@ietf.org
> Subject: Re: [Ace] ace-coap-est: unclear definition of
Peter van der Stok 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/co
: [Ace] ace-coap-est: unclear definition of /.well-known/est URI
Hi,
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.
I agree that we did not assign a port to coaps
Hi,
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.
I agree that we did not assign a port to coaps://example.com/est for
that matter,
and as such the example is inco
Sorry folks,
But you confuse me.
discovery is about /.well-known/core.
I don't understand where /.well-known/est comes in for discovery.
Peter.
Esko Dijk schreef op 2018-09-21 10:24:
>> I've asked if discovery is always required, permitted, or encouraged.
>
> Normally it is always encouraged to
> I've asked if discovery is always required, permitted, or encouraged.
Normally it is always encouraged to use discovery in favour of fixed URIs at
the server, to avoid specs squatting the URI namespace. But in our case the
/.well-known/est space is already assigned (RFC 7030) so we have to sup
> I've seen it just return , but I guess if you want to return the
> port number, you have to return the hostname... <:61616/est> won't do?
The closest thing valid according to the ABNF definitions would be
But unfortunately CoAP by its RFC 7252 URI definition forbids using an empty
host (reg
Esko Dijk wrote:
> @Michael:
> Since the EST resource is always present on the fixed port 5684 on URI
> /.well-known/est - if a fixed port is needed e.g. for a join proxy, use
> 5684 and the well-known URI. No discovery needed.
I've asked if discovery is always required, permitt
Esko Dijk wrote:
> Indeed, and the ace-coap-est examples use port 61616 mostly. The
> discovery Link Format is quite inefficient when returning results on
> *different* endpoints. Example:
> REQ: GET coap://[2001:db8::2:1]/.well-known/core?rt=ace.est
> RES: 2.05 Content
Esko
From: Peter van der Stok
Sent: Thursday, September 20, 2018 16:56
To: Michael Richardson
Cc: Esko Dijk ; Panos Kampanakis (pkampana)
; ace@ietf.org
Subject: Re: [Ace] ace-coap-est: unclear definition of /.well-known/est URI
Michael Richardson schreef op 2018-09-20 16:51:
I didn't
Michael Richardson schreef op 2018-09-20 16:51:
> I didn't think that CoAP resource discovery supports port numbers, does it?
>
> It does; at least for the 3rd party registration, but also examples in the RD
> show return of port___
Ace mailing list
Ac
Esko Dijk 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://
>
coaps://www.example.com://ArbitraryLabel/
I didn'
en though it is kind of self-explanatory.
I hope it makes sense.
Panos
From: Ace [mailto:ace-boun...@ietf.org] On Behalf Of Esko Dijk
Sent: Wednesday, September 12, 2018 11:10 AM
To: mailto:ace@ietf.org
Subject: [Ace] ace-coap-est: unclear definition of /.well-known/est URI
Dear all/authors
12, 2018 11:10 AM
To: mailto:ace@ietf.org
Subject: [Ace] ace-coap-est: unclear definition of /.well-known/est URI
Dear all/authors of ace-coap-est,
Section 5 of ace-coap-est-05 indicates URI discovery is possible to find the
EST functions entry point URI. Also a well-known URI is defined:
coap
to specify that the labl should be as short as
possible, even though it is kind of self-explanatory.
I hope it makes sense.
Panos
From: Ace [mailto:ace-boun...@ietf.org] On Behalf Of Esko Dijk
Sent: Wednesday, September 12, 2018 11:10 AM
To: mailto:ace@ietf.org
Subject: [Ace] ace-coap-est: unclea
hope it makes sense.
>
> Panos
>
> FROM: Ace [mailto:ace-boun...@ietf.org] ON BEHALF OF Esko Dijk
> SENT: Wednesday, September 12, 2018 11:10 AM
> TO: ace@ietf.org
> SUBJECT: [Ace] ace-coap-est: unclear definition of /.well-known/est URI
>
> Dear all/authors of ace-c
possible, even though it is kind of self-explanatory.
I hope it makes sense.
Panos
From: Ace [mailto:ace-boun...@ietf.org] On Behalf Of Esko Dijk
Sent: Wednesday, September 12, 2018 11:10 AM
To: ace@ietf.org
Subject: [Ace] ace-coap-est: unclear definition of /.well-known/est URI
Dear all
Dear all/authors of ace-coap-est,
Section 5 of ace-coap-est-05 indicates URI discovery is possible to find the
EST functions entry point URI. Also a well-known URI is defined:
coaps://www.example.com/.well-known/est/ArbitraryLabel/.
This URI seems more complicated than needed? What if we simply
18 matches
Mail list logo
