> 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 support it also in coaps-est and no additional squatting takes place. Besides support for the well-known URI location, discovery by a client is permitted to find "ace.est" type resources at other places e.g. to get shorter URIs or to get 6lowpan-compressible port numbers, or both.
> I.e. - can the client avoid the round trip to do the discovery? > - does the server have to provide the discovery? > -- if not, what does a client do that performs the discovery and fails? > I've been told it was required. - So it can't be required for the client, is my opinion. - The server must support it (being a good CoAP-citizen) in some way as in the previous email. - If it fails, the client might try another time using the /.well-known/est resource, or retry the discovery later on. (There could be various implementation-specific tactics here. Maybe the IP address of the EST server was configured wrongly; and the process that lead to this IP address can be redone by the client.) Esko _______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
