Re: [scim] Call for support on proposed SCIM/SINS (re)charter

I also support this charter and I'm willing to help produce and review the
resulting documents

On Fri, Sep 10, 2021 at 1:07 PM Mike Kiser <mike.kiser=
40sailpoint.com@dmarc.ietf.org> wrote:

> Nancy -
>
>  Excellent work.
>
>   In favor of this charter, willing to work on revising for fastfed /
> shared events/signals, and HR / PAM extension (a la Grizzle).
>
>   Looking forward to moving SCIM further down the line.
>
>  -Mike
> ------------------------------
> *From:* scim <scim-bounces@ietf.org> on behalf of Nancy Cam-Winget
> (ncamwing) <ncamwing=40cisco.com@dmarc.ietf.org>
> *Sent:* Wednesday, September 8, 2021 19:21
> *To:* scim@ietf.org <scim@ietf.org>
> *Subject:* [scim] Call for support on proposed SCIM/SINS (re)charter
>
>
> Hello SCIM participants,
>
>
>
> After some virtual meetings (thank you Pam for hosting these!) and
> discussion, there is a new proposed charter that addresses the points
> raised at the IETF 111 SINS session.
>
> This is a call for support of the charter defined below, please provide
> your response by Sept. 24, 2021.
>
>
>
> As you respond in support for the charter, please also specify if you are
> willing to produce, review and/or implement the resulting documents.
>
> Otherwise, do provide feedback in the time window if there are concerns or
> issues you see with the charter below:
>
>
> Charter
>
> The System for Cross-domain Identity Management (SCIM) specification is an
> HTTP-based protocol that makes managing identities in multi-domain
> scenarios easier. SCIM was last published in 2015 and has seen growing
> adoption.
>
> One goal for this working group is to shepherd SCIM, currently RFC series
> 7642
> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/rfc7642__;!!MsNKLpFGsw!eTFh5jVfVk7j5EbQi8cR7GP4P6_P3P0XP4CHOXvPG1347jwVSVPPypLTkQ2tqHggOw$>
> , 7643
> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/rfc7643__;!!MsNKLpFGsw!eTFh5jVfVk7j5EbQi8cR7GP4P6_P3P0XP4CHOXvPG1347jwVSVPPypLTkQ2sdvxDOg$>
> , 7644
> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/rfc7644__;!!MsNKLpFGsw!eTFh5jVfVk7j5EbQi8cR7GP4P6_P3P0XP4CHOXvPG1347jwVSVPPypLTkQ09gz3ESg$>,
> through the Internet Standard process. The group will deliver revised
> specifications for the SCIM requirements as Informational, and for the SCIM
> protocol and base schema suitable for consideration as a Standard. This
> work will be based upon the existing RFCs, errata and interoperabilty
> feedback, and incorporate current security and privacy best practices.
>
> In addition to revising the requirements, protocol and base schema RFCs,
> the group will also consider additional specifications as extensions to
> SCIM that have found broad adoption and are ready for standards track. This
> includes profiles and schemas for interoperability in additional scenarios.
> The working group will develop additional Proposed Standard RFCs based on
> outcomes of the following work:
>
>    - Revision of the informational RFC 7642 will:
>       - Focus on Use cases and implementation patterns
>          - Pull vs. Push based use cases
>          - Events and signals use cases
>          - Deletion use cases
>       - New use cases may be added to the revised RFC
>    - Revision of RFC 7643/44 will include:
>       - 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
>    - Document SCIM support for synchronization-related goals between
>    domains focused on:
>       - Handling returning large result sets through paging, based on
>       [draft-hunt-scim-mv-paging-00]
>       - Incremental approaches to synchronization
>    - Support for deletion-related goals including:
>       - Handling Deletes in SCIM Servers that don’t allow Deletes (Soft
>       Deletes) - based on [draft-ansari-scim-soft-delete-00]
>    - Support for advanced automation scenarios such as:
>       - Discovery and negotiation of client credentials
>       - Attribute mapping
>       - Per-attribute schema negotiation
>    - Enhance the existing schema to support exchanging of HR, Enterprise
>    group and privileged access management (using draft-grizzle-scim-pam
>    <https://urldefense.com/v3/__https://tools.ietf.org/id/draft-grizzle-scim-pam-ext-00.html__;!!MsNKLpFGsw!eTFh5jVfVk7j5EbQi8cR7GP4P6_P3P0XP4CHOXvPG1347jwVSVPPypLTkQ2pUlFhPA$> as
>    a base)
>
>
>
> Best, Nancy (as one of the BoF chairs)
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>

-- 

Erik Gustavson

erikgustavson@google.com

Engineering Manager - Google C&C Core

650-451-1372