[scim] Re: [Technical Errata Reported] RFC7643 (8362)

[Phil Hunt <[e-mail]>]

REJECTED

Resource types are referenced by their ID. ALWAYS.

It often occurs that name and id are the same.  The scenario you describe would not occur because it would point by ID.

Phil Hunt
[e-mail]



> On Mar 31, 2025, at 9:11 AM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC7643,
> "System for Cross-domain Identity Management: Core Schema".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8362
> 
> --------------------------------------
> Type: Technical
> Reported by: Matthias Winter <[e-mail]>
> 
> Section: 6
> 
> Original Text
> -------------
>   id
>      The resource type's server unique id.  This is often the same
>      value as the "name" attribute.  OPTIONAL.
> 
>   name
>      The resource type name.  When applicable, service providers MUST
>      specify the name, e.g., "User" or "Group".  This name is
>      referenced by the "meta.resourceType" attribute in all resources.
>      REQUIRED.
> 
> 
> Corrected Text
> --------------
>   id
>      The resource type's server unique id.  This is often the same
>      value as the "name" attribute.  OPTIONAL.
> 
>   name
>      The resource type name.  When applicable, service providers MUST
>      specify the name, e.g., "User" or "Group".  This name is
>      referenced by the "meta.resourceType" attribute in all resources.
>      REQUIRED. The resource type name must be unique within the server.
> 
> 
> Notes
> -----
> ResourceTypes are not referenced by their "id" in the meta.resourceType attribute, but by their "name".
> Section 3.3 states:
>   In order to determine which URI value in the "schemas" attribute is
>   the base schema and which is an extended schema for any given
>   resource, the resource's "resourceType" attribute value MAY be used
>   to retrieve the resource's "ResourceType" schema (see Section 6).
> 
> This would not work if there were numerous ResourceType resources with the same name. The name must therefore be unique within the server.
> 
> This also applies to the schema definition in section 8.7.2 where it should be defined with "uniqueness": "server" instead of "none".
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC7643 (draft-ietf-scim-core-schema-22)
> --------------------------------------
> Title               : System for Cross-domain Identity Management: Core Schema
> Publication Date    : September 2015
> Author(s)           : P. Hunt, Ed., K. Grizzle, E. Wahlstroem, C. Mortimore
> Category            : PROPOSED STANDARD
> Source              : System for Cross-domain Identity Management
> Stream              : IETF
> Verifying Party     : IESG