search

Domain-Connect / spec

Domain Connect Specification
MIT License
73 stars 34 forks source link

Discovery TXT record contents #103

Open TheEnbyperor opened 3 months ago

TheEnbyperor commented 3 months ago

It is currently unclear in the specification if the contents of the _domainconnect TXT record is a FQDN, or a partial URI. That is can the record contain a path element; example.net/connect being valid as well as example.net.

From poking at iCloud's implementation they seem to treat it as partial URI and not an FQDN. I'm unsure what other current implementations do.

As for my opinion on this I think it should be a partial URI, and not just an FQDN.

pawel-kow commented 3 months ago

Excellent question! The specification is obviously not specific enough about it. I would rather opt for partial URI interpretation - this is at least what can be derived from the text how the URL to /settings REST API is built. The fact that the spec is now silent about it and all examples actually use FQDN may be indeed misleading.

greenreader9 commented 3 months ago

I agree with @TheEnbyperor, in that a FQDN should not be required, but a partial URI should be allowed.

Since the service provider just makes a request to the endpoint suffixed with the required paths and parameters, the DNS provider should be allowed to do their own versioning within paths (such as "dnsprovider.tld/api/v1/domainConnect/".

As long as a valid URI is provided, I don't see a reason why paths should not be allowed.