The Scope Creep Automated reviews of new AI-related working group submissions

Meeting · IETF 127

SCIM WG at IETF 127

San Francisco, US · November 14 to 20, 2026

3 drafts on the agenda, 3 reviewed here. Reviewed drafts have a short summary and a link to the full review. The rest show the draft's own abstract. Official agenda, revision 03 →

Agenda as of November 16, 2026. It can change before the meeting.

Agenda 5 slots

  • Chairs intro and agenda gardening

    5 min
  • SCIM 2.0 Interoperability Profile

    Danny · 20 min

    draft-zollner-scim-interop-profile -02

    SCIM 2.0 Interoperability Profile

    SCIM's optionality is the product of a many-to-many market, and it makes every integration bespoke.

    One identity provider provisions into hundreds of SaaS applications. Each of those applications accepts connections from dozens of identity providers. RFC 7643 and RFC 7644 leave PATCH syntax, pagination, filtering, case sensitivity, and error handling open enough that two conformant implementations routinely fail to talk to each other. The result is that every IdP maintains per-application quirk configuration, and every application maintains per-IdP quirk handling.

  • SCIM Group Membership Resource Type Extension

    Danny · 20 min

    draft-zollner-scim-group-membership -00

    SCIM Group Membership Resource Type

    A group with a million members does not fit in one HTTP response.

    RFC 7643 stores membership as a multi-valued members attribute on the Group. SCIM paginates resources, not values inside a resource. The draft puts a million-member Group at roughly 200MB (Section 2). Some service providers have stopped returning members at all. Some clients exclude it on every request, so they can push changes but never read back the real state.

  • SCIM User Supersession and Identity Resolution Correction Events

    Vivek · 15 min

    draft-vivek-scim-user-supersession -00

    SCIM Events for Merged and Unmerged Users

    A SCIM service provider finds that two User resources are the same person. It keeps one and retires the other.

    Today the only signal a downstream receiver gets is a delete event for the retired User. Nothing says which User replaced it. Anything the receiver keyed to the old id is orphaned.

  • Rechartering Discussion

    30 min