Introduce a .well-known discovery endpoint and DNS SRV records

[glpatcern]

Following today's discussions, would this be enough? Maybe complemented with some details in the README.md file?

[mickenordin]

Looks good!

[DanScharon]

wonderful!
Is this intended to enable the discovery of a user's federated instance?
For example I would enter the email address of a person I wish to share with (person1@example.com) and my instance would look up https://example.com/.well-known/ocm which would point to https://cloud-storage.example.com and my instance would ask https://cloud-storage.example.com whether it has a user with the email address person1@example.com that I could share with?

[glpatcern]

wonderful! Is this intended to enable the discovery of a user's federated instance?

@DanScharon that's precisely the idea, assuming that the vendors will implement that mechanism in Nextcloud, OCIS, etc.

I intend to include that workflow in the README.md, possibly coupled with the other idea that emerged at the CS3 workshop, that is the DNS SRV record.

[DanScharon]

wonderful! Is this intended to enable the discovery of a user's federated instance?

@DanScharon that's precisely the idea, assuming that the vendors will implement that mechanism in Nextcloud, OCIS, etc.

I intend to include that workflow in the README.md, possibly coupled with the other idea that emerged at the CS3 workshop, that is the DNS SRV record.

Excellent! Thank you for including this in the spec!

[glpatcern]

I'd love a second read of the paragraph I added to the README.md, @mickenordin would you please have a look? Thanks!

[mickenordin]

I think this is a fine addition.

We should probably extract relevent information from this discussion and add it to the spec text it self: #37 (comment)

But I dont think it needs to happen in this pr, we can do it separately.

[glpatcern]

We should probably extract relevent information from this discussion and add it to the spec text it self: #37 (comment)

That's true, this comment is even referenced "as is" but it would be good to get more up to date information about current issues with .well-known. Agreed that it's for another PR.

And otherwise, with @labkode we better defined how to use DNS SRV records, which is a much more viable solution than assuming that an organization can deploy https://example.com/.well-known/ocm sort of URLs: the latter are typically not under the control of the EFSS team.

[glpatcern]

@DanScharon we slightly modified the logic for discovery: the goal is the same, but typically a https://example.com/.well-known/ocm address is hard to be maintained by the cloud storage team as it "belongs" to the institutional web site and its auth system. Instead, a DNS query can do it, see the new description.