Skip to content

Conversation

@sandhose
Copy link
Member

@sandhose sandhose commented Sep 12, 2024

Rendered

Implementions:

To do:

  • Update references to MSC3861 as it has been accepted
  • Add clarification about being the replacement for delete devices API endpoints when using OAuth 2.0 API
  • Check for consistency with MSC3824

In line with matrix-org/matrix-spec#1700, the following disclosure applies:

I am a Software Engineer at Element. This proposal was written and published as an Element employee.


SCT Stuff:

FCP tickyboxes

MSC checklist

@turt2live turt2live added proposal A matrix spec change proposal client-server Client-Server API kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Sep 12, 2024
@hughns hughns marked this pull request as ready for review September 17, 2025 17:04
@hughns hughns changed the title MSC4191: Account management deep-linking MSC4191: Account management deep-linking for OAuth 2.0 API Sep 17, 2025
@github-project-automation github-project-automation bot moved this to Tracking for review in Spec Core Team Workflow Sep 17, 2025
@turt2live turt2live added the matrix-2.0 Required for Matrix 2.0 label Sep 17, 2025
@turt2live turt2live moved this from Tracking for review to Proposed for FCP readiness in Spec Core Team Workflow Sep 17, 2025
@hughns hughns changed the title MSC4191: Account management deep-linking for OAuth 2.0 API MSC4191: Account management for OAuth 2.0 API Sep 23, 2025
@turt2live
Copy link
Member

@mscbot fcp merge
@mscbot concern Pending preliminary approval from oauth-ext-review to use the new names - https://mailarchive.ietf.org/arch/msg/oauth-ext-review/6RQXusbqFTy-XZCGwLSW-RIa9Dg/

@mscbot
Copy link
Collaborator

mscbot commented Sep 24, 2025

Team member @mscbot has proposed to merge this. The next step is review by the rest of the tagged people:

Concerns:

Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for information about what commands tagged team members can give me.

@mscbot mscbot added proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. disposition-merge unresolved-concerns This proposal has at least one outstanding concern labels Sep 24, 2025
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
hughns and others added 2 commits October 20, 2025 10:56
Co-authored-by: Johannes Marbach <n0-0ne+github@mailbox.org>
Added a reference to MSC4312 for cross-signing reset details.
Copy link
Contributor

@tonkku107 tonkku107 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

org.matrix.session_end was renamed to org.matrix.device_delete but the rest of the proposal didn't follow

Co-authored-by: Tonkku <contact@tonkku.me>
@turt2live
Copy link
Member

Per recent emails sent to oauth-ext-review on our thread, it seems possible to allow this MSC to go through without formal registration. When we get to the spec PR, we should verbosely describe the fields so we can point to them in a more complete registration application.

@mscbot resolve Pending preliminary approval from oauth-ext-review to use the new names - https://mailarchive.ietf.org/arch/msg/oauth-ext-review/6RQXusbqFTy-XZCGwLSW-RIa9Dg/

@mscbot
Copy link
Collaborator

mscbot commented Nov 18, 2025

🔔 This is now entering its final comment period, as per the review above. 🔔

@mscbot mscbot added final-comment-period This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days. and removed proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. unresolved-concerns This proposal has at least one outstanding concern labels Nov 18, 2025
@turt2live turt2live removed the 00-weekly-pings Tracking for weekly pings in the SCT office. 00 to make it first in the labels list. label Nov 18, 2025
@turt2live turt2live moved this from Ready for FCP ticks to In FCP in Spec Core Team Workflow Nov 18, 2025
@mscbot
Copy link
Collaborator

mscbot commented Nov 23, 2025

The final comment period, with a disposition to merge, as per the review above, is now complete.

@mscbot mscbot added finished-final-comment-period and removed disposition-merge final-comment-period This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days. labels Nov 23, 2025
@turt2live turt2live merged commit 2b6da16 into main Nov 24, 2025
1 check passed
@turt2live turt2live added spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec and removed finished-final-comment-period labels Nov 24, 2025
@turt2live turt2live moved this from In FCP to Requires spec writing in Spec Core Team Workflow Nov 24, 2025
@zecakeh
Copy link
Contributor

zecakeh commented Dec 16, 2025

Spec PR: matrix-org/matrix-spec#2270

@turt2live turt2live added spec-pr-in-review A proposal which has been PR'd against the spec and is in review and removed spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec labels Dec 16, 2025
@turt2live turt2live moved this from Requires spec writing to Requires spec PR review in Spec Core Team Workflow Dec 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client-server Client-Server API kind:core MSC which is critical to the protocol's success matrix-2.0 Required for Matrix 2.0 proposal A matrix spec change proposal spec-pr-in-review A proposal which has been PR'd against the spec and is in review

Projects

Status: Requires spec PR review

Development

Successfully merging this pull request may close these issues.