[scim] May 2022: Update on status of SCIM Schema and Protocol revision work

[Danny Zollner <[e-mail]>]

Hi everyone,
 
Ahead of our interim meeting today, Janelle and I as editors for the SCIM Schema and Protocol (RFC 7643/7644) revision work would like to share the following:
 
. We've converted the SCIM 2.0 schema and protocol RFCs into Markdown/Kramdown in order to facilitate easier editing in the future. There are still some formatting problems remaining, as well as the editor and reference information needing to be added in the right format, but the bulk of the reformatting work is done.
	o These Kramdown files can be found in the api and core-schema repos at https://github.com/ietf-scim-wg
	o These Markdown/Kramdown files can be converted via tooling at https://github.com/cabo/kramdown-rfc from KD -> XML -> RFC-formatted TXT file
	o If anyone is interested in helping with finishing off the formatting issues related to XML -> MD conversion, it would be greatly appreciated
. We'll work on processing various errata and clarifications to the spec into a newer version of the SCIM 2.0 schema and protocol
	o We're still working on figuring out what the end state looks like in terms of versioning (reissue 2.0/2.1/3.0/etc..)  - but we're going to put that to the side for now and focus on content and solving problems instead.
	o Major introductions of new features will be drafted as independent extensions to SCIM 2.0 to start with
 
Now on to specific agenda items:
 
Items that we have clear thoughts on next steps on:
 
. Updates to account state for capturing context of the state or change in state of the users account
	o Janelle has been working on this - the current idea is a proposal to expand the "active" attribute on the user resource to be complex rather than a boolean, and to include other contextual information such as reason for enablement/disablement. 
	o Janelle has a session at Identiverse in June where she'll be speaking on this topic
. Multi-Value Query Filtering and Paging
	o draft-hunt-scim-mv-paging is the best starting point for this and we should work towards getting any necessary changes made and adopting it
. Define a method for coordinating resources between domains - Security Event Tokens
	o draft-hunt-scim-events addresses this and folks should review this and provide feedback
. Support for deletion-related goals including handling deletes in SCIM servers that don't allow deletes
	o Would like to combine into account state expansion above, and use elements from draft-ansari-scim-soft-delete as appropriate
. Support for advance automation scenarios - new schemas:
	o Going to work on initial drafts for HR and Enterprise Group schemas
 
 
Items that we haven't given much thought to yet:
 
. Profiling SCIM relationships with other identity-centric protocols such as OAuth 2.0, OpenID Connect, Shared Signals, and Fastfed
. Updates to the evolution of the externalid usage
. Define a method for coordinating resources between domains
	o Synchronization/Delta Change Detection
. Support for advanced automation scenarios such as:
	o Discovery and negotiation of client credentials
	o Attribute mapping
	o Per-attribute schema negotiation
	o PAM schema
 
For any of the above items, if anyone is interested in collaborating on these for initial drafts prior to submission/sharing with the mailing list and the IETF data tracker, please reach out. As we make progress we'll start posting basic drafts to the GitHub repos and soliciting feedback as well.

Thanks,

Danny Zollner

[e-mail]