matrix-spec-proposals
matrix-spec-proposals copied to clipboard
matrix-org
MSC1597: Better spec for matrix identifiers
Rendered: https://github.com/matrix-org/matrix-doc/blob/rav/proposals/id_grammar/proposals/1597-id-grammar.md
A proposal to clarify a bunch of rules about what is and is not allowed in various identifiers.
This is intended to fix matrix-org/matrix-spec#174, matrix-org/matrix-spec#175, matrix-org/matrix-spec#278 and matrix-org/matrix-spec#290.
since the state of this MSC was causing confusion, I have turned this issue into a PR so that it matches the modern system.
I also don't think it has had what would qualify for an FCP nowadays, since it hasn't been implemented; I've updated the labels accordingly.
note that a lot of discussion on this proposal took place on matrix-org/matrix-spec-proposals#1598.
Thoughts on also moving megolm session_id values to being url-safe base64? Same reasoning as excluding the slash from user ids.
Thoughts on also moving megolm session_id values to being url-safe base64? Same reasoning as excluding the slash from user ids.
The reason for user ids is that user IDs appear in the path of REST endpoints, but I don't think the same is true of megolm session IDs?
Megolm session IDs are base64-encoded ed25519 public keys. Base64-encoded ed25519 keys are used a lot in the protocol, and normally don't use url-safe encoding.
Thoughts on also moving megolm session_id values to being url-safe base64? Same reasoning as excluding the slash from user ids.
The reason for user ids is that user IDs appear in the path of REST endpoints, but I don't think the same is true of megolm session IDs?
Megolm session IDs are base64-encoded ed25519 public keys. Base64-encoded ed25519 keys are used a lot in the protocol, and normally don't use url-safe encoding.
They appear in the room_key backup related URLs unfortunately: https://spec.matrix.org/latest/client-server-api/#get_matrixclientv3room_keyskeysroomidsessionid
Thoughts on also moving megolm session_id values to being url-safe base64? Same reasoning as excluding the slash from user ids.
The reason for user ids is that user IDs appear in the path of REST endpoints, but I don't think the same is true of megolm session IDs? Megolm session IDs are base64-encoded ed25519 public keys. Base64-encoded ed25519 keys are used a lot in the protocol, and normally don't use url-safe encoding.
They appear in the room_key backup related URLs unfortunately: https://spec.matrix.org/latest/client-server-api/#get_matrixclientv3room_keyskeysroomidsessionid
Oh hrm, right.
We've got some other changes planned for megolm (cf https://github.com/matrix-org/matrix-spec/issues/1557) so this might be a thing to consider at the same time.