Re: [scim] Clarification on SCIM schema extension URN naming rules

Phillip Hunt <phil.hunt@independentid.com> Tue, 04 October 2022 15:25 UTC

Return-Path: <phil.hunt@independentid.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F923C14CE2F for <scim@ietfa.amsl.com>; Tue, 4 Oct 2022 08:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKu7WcQ-fO6K for <scim@ietfa.amsl.com>; Tue, 4 Oct 2022 08:25:23 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02873C1522DB for <scim@ietf.org>; Tue, 4 Oct 2022 08:24:52 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id i6so13438349pfb.2 for <scim@ietf.org>; Tue, 04 Oct 2022 08:24:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20210112.gappssmtp.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date; bh=dJSiTJBBBkup/SYgJd1Jd/V4Pfr+KYIwgwV3CZ4TDOA=; b=7XPIeSrUJt20lkQs7yVaK3zxfgHOJqWCTvYfxSyecclo3d/sytE9oPv2XSLcQL3rdl Kj+7Ei5bkqvG6F0/Z/OYAs8tySXX9U/mkiRlmmQKPmih1dWB+LQTVGVjDEaBWVb1aEa9 PDQWv0nUoZ7JEJs2sJYzj2qyKb4hLsuXxqLukHZn0bj68m9ll7TKElNKqDCrT8Jxkgux rAnVSGKIFM3/roQ2eHZVd9gsKahlib5zvc+a4REZvRtyvSz5Sj/3AfVcudK1TcJAKxCI eTFI0NZi/5nZ79NN0SL6TJSshc/q0hEAoxmlL+E8O3R6xIDZ+/sHJJctb1JuhwkQDck6 mwCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date; bh=dJSiTJBBBkup/SYgJd1Jd/V4Pfr+KYIwgwV3CZ4TDOA=; b=TmhOY0OWLjWPQNM2w240AjXC7ArrHXovjVbxkfSKWh6TgnOVKBDBFli+xj+Cl29WRb z5TKoNq/1YI9iHz3frgkMi6NdkwHWcanBJz5Fiuh6PIEPMPhQ02lGHxUvxtQPqVuEu/d FNNtA4LD+9fO9l2KSe4bo8yQ4iZ3w0CKeeLaRItjpjU9tJ1cjWtKfpfYpcSt43xjZR4J IIHYP7ZMS9am6HIPNVamU9JYzCPuAPj+9pJWi/Y8MaLJbJiOgTBeDMghGy78RNnpBr52 bz4UhA/Bscoi3TlFq6pmCtIIjUwPD5yF6h+QP4bpeHY2lKZaNqfhpu5N+ZqBSoVsALhg fs6Q==
X-Gm-Message-State: ACrzQf36XWtzg98U7DA4nCk7oLZRxpAlG+jHiITAd/rqD91x+TvAp9Tb /tfvaxYM8KEs+cJjbaElC/nIJAJmH5Yl4w==
X-Google-Smtp-Source: AMsMyM5Gzj/D6vyBIRbixOHjXg1BzarLh30U0i6q77tOHaPlb7p2c4DBrkMogbIwhURIQnEYHmP7dg==
X-Received: by 2002:a63:1750:0:b0:43a:9392:2676 with SMTP id 16-20020a631750000000b0043a93922676mr23630530pgx.463.1664897091964; Tue, 04 Oct 2022 08:24:51 -0700 (PDT)
Received: from smtpclient.apple (node-1w7jr9plyoqwtktn5waibgx5b.ipv6.telus.net. [2001:569:540c:4900:61ae:e0b5:aa95:1ecf]) by smtp.gmail.com with ESMTPSA id u15-20020a170903124f00b001709b9d292esm9105390plh.268.2022.10.04.08.24.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Oct 2022 08:24:51 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Phillip Hunt <phil.hunt@independentid.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 04 Oct 2022 08:24:51 -0700
Message-Id: <3E25E547-C68D-45A1-8C51-B4676B7164B8@independentid.com>
References: <3250F090-BCCB-4999-9D90-4D428D3100B6@gmail.com>
Cc: scim@ietf.org, Danny Zollner <Danny.Zollner=40microsoft.com@dmarc.ietf.org>, Stanimir Bozhilov <stanimir@audriga.com>
In-Reply-To: <3250F090-BCCB-4999-9D90-4D428D3100B6@gmail.com>
To: Brian Demers <brian.demers@gmail.com>
X-Mailer: iPhone Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/tYnwmpcMsmxuGuyOvdzfojTeQgc>
Subject: Re: [scim] Clarification on SCIM schema extension URN naming rules
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Oct 2022 15:25:27 -0000

I would take a look at the IANA section of RFC7643. It details the namespace and registration process for SCIM urns. 

Phil

> On Oct 4, 2022, at 7:33 AM, Brian Demers <brian.demers@gmail.com> wrote:
> 
> Same question here!
> 
> I gave a SCIM talk yesterday, and Iglossed over this topic, because it was not clear to me.
> The spec states the URN prefix for the IANA registered schema.
> But that may suggest that non-registered schema should avoid that prefix? 🤷
> 
> -Brian
> 
>>> On Oct 4, 2022, at 9:13 AM, Stanimir Bozhilov <stanimir@audriga.com> wrote:
>>> 
>>> On 2022-09-30 07:37, Danny Zollner wrote:
>>> Hi SCIM-ers,
>>> In RFC 7643, as best I can tell, all of the examples of schemas for
>>> SCIM resources begin with the prefix of
>>> urn:ietf:params:scim:schemas:…, with the sole exception of the text
>>> on page 29 that refers to the schema for the ResourceType resource.
>>> This text describing the schema for the ResourceType resource contains
>>> the following:
>>> schemaExtensions
>>>     A list of URIs of the resource type's schema extensions.
>>>     OPTIONAL.
>>>     schema  The URI of an extended schema, e.g.,
>>> "urn:edu:2.0:Staff".
>>>        This MUST be equal to the "id" attribute of a "Schema"
>>>        resource.  REQUIRED.
>>> This example uses urn:edu:2.0:Staff as the example for an extension
>>> schema, but all other examples of schemas in RFC 7643 that I could
>>> find use the ietf namespace. In a discussion I was having with a
>>> colleague of mine a few months ago, it was stated that the only schema
>>> URNs that should be using the urn:ietf:.. namespace are ones contained
>>> in IETF-managed drafts or RFCs. I've worked with dozens of SCIM
>>> service provider implementers in the past few years, and possibly
>>> without exception all implementers that have custom schema extensions
>>> do something equivalent to
>>> urn:ietf:params:scim:schemas:extension:CompanyName:2.0:User.
>>> I'd like to get input from others in the working group - is it correct
>>> that for non-IETF managed schemas - such as those that are custom to a
>>> single SCIM implementation - that a schema extension URN should not
>>> begin with urn:ietf:… but instead virtually anything else - i.e.:
>>> urn:foo:bar, or the example above of urn:edu:2.0:Staff?
>>> If it is the case, then I've got the following questions:
>>>   * Does improper schema URN naming(improper usage of urn:ietf:.. )
>>> have any negative impact?
>>>   * For future guidance on this topic as part of the SCIM 2.0 standard,
>>> should any consideration be given to the fact that the overwhelming
>>> majority of SCIM 2.0 implementers have implemented their extensions
>>> starting with urn:ietf:..?
>>>   * If a future version increase of SCIM happens - 2.1, 3.0, etc -
>>> should clearer guidance on proper versus improper schema URN naming be
>>> given, including explicit guidance that urn:ietf:… is reserved?
>>> Thanks,
>>> Danny Zollner
>>> _______________________________________________
>>> scim mailing list
>>> scim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/scim
>> 
>> 
>> Hi Danny,
>> 
>> We're currently facing the same issue where it's not completely clear how one is supposed to define the URN of new resources or extensions in SCIM.
>> 
>> For the time being, we took the approach where we have the "urn:ietf:..." prefix and at the end of the URN we have "CompanyName:2.0:SomeResourceType". However, we weren't really sure whether this was actually proper naming and so we could easily change the URN naming in case it turns out that this is not the right way to go about naming new resources and/or schema extensions.
>> Regarding this matter, we'd also be particularly interested in feedback and official guidance on how such naming should be done in general.
>> 
>> Best regards,
>> Stanimir Bozhilov
>> 
>> -- 
>> Stanimir Bozhilov
>> Tel: +49 721 170293 16
>> Fax: +49 721 170293 179
>> 
>> http://www.audriga.com | http://www.twitter.com/audriga
>> 
>> --------------------------------------------------------------------------
>> audriga GmbH |  Alter Schlachthof 57  | 76137 Karlsruhe
>> Sitz der Gesellschaft: Karlsruhe - Amtsgericht Mannheim - HRB 713034
>> Geschäftsführer: Dr. Frank Dengler, Dr.-Ing. Hans-Jörg Happel
>> --------------------------------------------------------------------------
>> 
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim
> 
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim