Re: [scim] Registering SCIM Schema Extension

Phillip Hunt <phil.hunt@independentid.com> Fri, 25 March 2022 19:05 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 E687D3A1770 for <scim@ietfa.amsl.com>; Fri, 25 Mar 2022 12:05:59 -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, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, 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] autolearn=unavailable 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H3eGutozsa7n for <scim@ietfa.amsl.com>; Fri, 25 Mar 2022 12:05:55 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EDB53A1774 for <scim@ietf.org>; Fri, 25 Mar 2022 12:05:54 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id h19so6174312pfv.1 for <scim@ietf.org>; Fri, 25 Mar 2022 12:05:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=hZ4cmx7PhJNAVU5/UjR78FBciYneNFcL3daB+mXadY0=; b=GGw5tierge0du2uFGELo4BlDIYlp0edFTTCgsuMvIhdnwiw+SuZwFGO0f9Z7D3mC5K W1gjP6kwbgw86m85zCkxJjRya1wQXKOl8WjOfWWxCxM2I3e7+WBn3XUikeVmKMMGjRVb 5/1bbYeYYbK5byyxGZFcvFJC3Tzw7wzcbK2P5yBj+u5nOGTyWaX6LqLxujfqsf0Sy4rL B6uJsxCpVjrHSp9TiA38Z8vSEVodpzOi9+NQ2T9VpdpCn8qCUYozR+KF37BoeqirpLSK a6UwvpRAXpaLxo4Vse8evmhJ0bqdl01cbvvdhENa8Ty0TxjjO1FvPMh8tSf6ZsxXGAzz MiTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=hZ4cmx7PhJNAVU5/UjR78FBciYneNFcL3daB+mXadY0=; b=fmtKqDI6n63CgCSWt827DQ+eTu+sXOpuNcHHVdVKCIi5qfBZWbMqWwwooOjaJzeZm3 1b2Fux0Yf9SB/PXIpjre1lFZRQKqijuOA9vnjUqrEE7o1pKnPAwcXn3qd2a/c0GiInk3 94w/iQYcyeBRQI+zyR+hnhtef5ftOW0O9KH3Z7OV7R+CnFLuWUoZ7kuzGoQcaS45HdKZ wgHA1oCVMVRavwLs3Srg8+j7PZBZ6DsiY1fbI4NheW3f2zjBeiqC5twkMK0n0PWpd68d 4j/sEjCDKy4jCx64D3rlWK63hevwsbXA2EbBHt2/CfXDdUx6W6Vr5w4hvJ8b0hAKMzLy ss/Q==
X-Gm-Message-State: AOAM531hVRW4YQV4xcMtkwLUHu4cJlGbcm0KyguVgTfjUuDNMOhvgsog 1hvXGYlZVPeBl4g8sCsoPdpHnOWUxY4DiRMa
X-Google-Smtp-Source: ABdhPJx6qXFBr/bExqNh1ZVWOY/rOzonOhFm2h83oU3iksMDirG8nHUNdvYYKlk9B23CubOOErl1+Q==
X-Received: by 2002:a63:d342:0:b0:381:fd6f:4792 with SMTP id u2-20020a63d342000000b00381fd6f4792mr780945pgi.101.1648235153502; Fri, 25 Mar 2022 12:05:53 -0700 (PDT)
Received: from smtpclient.apple ([2001:569:7316:ae00:7517:415d:9f09:e58a]) by smtp.gmail.com with ESMTPSA id t34-20020a056a0013a200b004faa8346e83sm7924842pfg.2.2022.03.25.12.05.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Mar 2022 12:05:53 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-2832C0FC-BB07-4D88-9A9B-421A30DED48C"
Content-Transfer-Encoding: 7bit
From: Phillip Hunt <phil.hunt@independentid.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 25 Mar 2022 12:05:50 -0700
Message-Id: <EC282948-CE0E-4264-B7FE-B8D432926625@independentid.com>
References: <6AFB8120-57DA-4D65-989A-5FCBF97B73BC@sailpoint.com>
Cc: KATAOKA TOSHIYUKI <toshikataoka@nec.com>, scim@ietf.org
In-Reply-To: <6AFB8120-57DA-4D65-989A-5FCBF97B73BC@sailpoint.com>
To: Kelly Grizzle <kelly.grizzle=40sailpoint.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (19D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/FNXJkYtofjd8LoeJwQHrYtTMj18>
Subject: Re: [scim] Registering SCIM Schema Extension
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 25 Mar 2022 19:06:00 -0000

Yes. At the end of the current rfc7643 there is an IANA registration process described. IANA submitted specs are sent to subject matter experts to review for conflicts etc.  When complete, your schema uri is registered with IANA for anyone to look up. 

As Kelly mentions if you don’t intend wide use, you strictly don’t need to register. 

It is a good idea to bring directly to scim wg if there is substantial overlap and/or widely used claims. For example i think the group will be discussing new authenticator extensions and device/iot schemas going forwards based on discussions at this week’s WG meeting. 

Phil

> On Mar 25, 2022, at 11:43 AM, Kelly Grizzle <kelly.grizzle=40sailpoint.com@dmarc.ietf.org> wrote:
> 
> 
> If you intend it to be a schema that is standardized and shared beyond your organization, then you can register it.  Otherwise, it is not a requirement.
>  
> From: scim <scim-bounces@ietf.org> on behalf of "KATAOKA TOSHIYUKI(片岡 俊幸)" <toshikataoka@nec.com>
> Date: Thursday, March 24, 2022 at 9:47 AM
> To: "scim@ietf.org" <scim@ietf.org>
> Subject: [scim] Registering SCIM Schema Extension
>  
> ZjQcmQRYFpfptBannerStart
> This Message Is From an External Sender
> This message came from outside your organization.
> ZjQcmQRYFpfptBannerEnd
> Hello,
>  
>    We are implementing SCIM protocol in one of our services, and in order to add some new attributes we need a new schema such as: 
>       “urn:ietf:params:scim:schemas:extension:nec:ope:2.0:User”.
>    According to RFC7643 10.3. and scim mailing list archives, I think we need to register a new schema such as above.  Is it correct that we need to send a SCIM schema registration template to this mailing list (scim(at)ietf.org) to register the new schema?
>  
> Regards,
> Toshiyuki Kataoka
>  
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/scim__;!!MsNKLpFGsw!fTbna2L1T2uOxL2iNP12YIvtQbJVf03pZvq768wTTnv9pXl9orLo_7FZR7-_0aefOkHnTuU$ 
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim