Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Register /.well-known/matrix with IANA #1914

Closed
ara4n opened this issue Mar 5, 2019 · 14 comments
Closed

Register /.well-known/matrix with IANA #1914

ara4n opened this issue Mar 5, 2019 · 14 comments
Assignees
Labels
client-server Client-Server API meta Something that is not a spec change/request and is not related to the build tools s2s Server-to-Server API (federation)

Comments

@ara4n
Copy link
Member

ara4n commented Mar 5, 2019

No description provided.

@jryans
Copy link
Contributor

jryans commented Mar 6, 2019

I have submitted the registration request to the IETF group that reviews them.

@jryans
Copy link
Contributor

jryans commented Mar 8, 2019

The request has been received by IETF mailing list, and now we wait for it to be reviewed, which may take some time.

@turt2live turt2live added s2s Server-to-Server API (federation) client-server Client-Server API meta Something that is not a spec change/request and is not related to the build tools labels Mar 8, 2019
@eskalVAR
Copy link
Contributor

This needs to be addressed within the specification as well. The "/.well-known/matrix/client" to my understanding does not conform to RFC 3986. The /.well-known/ must be segment-nz as specified in RFC 7785. Is the application name just going to be "matrix" then?

@uhoreg
Copy link
Member

uhoreg commented Mar 22, 2019

(I'm assuming you mean 5785 ratherthan 7785) The registered name would just be matrix, and would be a directory. This is similar to some other registered .well-known names that are also defined to be directories, such as acme-challenge or dnt

@eskalVAR
Copy link
Contributor

Yes sorry that was a typo.

@jryans
Copy link
Contributor

jryans commented Mar 22, 2019

Yes, we registered for the name matrix.

@richvdh
Copy link
Member

richvdh commented Mar 22, 2019

@jryans
Copy link
Contributor

jryans commented Apr 9, 2019

The .well-known registry request has been reviewed and broadly looks good, but they are suggesting that we provide a more stable / unchanging URL to the specification documents that explain our .well-known behaviour so that we don't need to update the document URLs in the future.

I had previously offered:

https://matrix.org/docs/spec/client_server/r0.4.0.html#well-known-uri
https://matrix.org/docs/spec/server_server/r0.1.1.html#get-well-known-matrix-server

We could instead provide:

https://matrix.org/docs/spec/client_server/unstable.html#well-known-uri
https://matrix.org/docs/spec/server_server/unstable.html#get-well-known-matrix-server

I am not quite sure how they may feel about the word "unstable" in the URL, though I can try to explain it's just the latest reviewed version.

@ara4n @richvdh @uhoreg Since you've interacted with this issue, are there other URLs you would recommend instead? I suppose it would be possible to craft a separate page that just describes .well-known at an unchanging URL, but I wasn't sure if that would be desirable.

Anyway, if I don't hear any replies here soon, I'll offer the unstable URLs above.

@jcgruenhage
Copy link
Contributor

It would be nice to have a "stable" pointer just like we have "unstable", where stable shows the most recent stable release. Would be really useful here, and I'm sure there's other use cases too

@richvdh
Copy link
Member

richvdh commented Apr 9, 2019

the word you are after is "latest":

https://matrix.org/docs/spec/client_server/latest.html#well-known-uri
https://matrix.org/docs/spec/server_server/latest.html#get-well-known-matrix-server

@jryans
Copy link
Contributor

jryans commented Apr 9, 2019

Aha, thanks all! I will offer the URLs that use latest then.

@jryans
Copy link
Contributor

jryans commented Apr 9, 2019

I have replied with updated spec URLs that use "latest".

@jryans
Copy link
Contributor

jryans commented Apr 15, 2019

The registry experts have approved our request and instructed IANA to add our registration. I'll update this thread once the registration goes live.

@jryans
Copy link
Contributor

jryans commented Apr 16, 2019

IANA has added the registration, so we're all done here. 🎉

@jryans jryans closed this as completed Apr 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API meta Something that is not a spec change/request and is not related to the build tools s2s Server-to-Server API (federation)
Projects
None yet
Development

No branches or pull requests

7 participants