Re: [scim] Moving towards the next IETF Meeting

Audrei Drummond <adrummond@slack-corp.com> Tue, 06 October 2020 16:51 UTC

Return-Path: <adrummond@slack-corp.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 782003A0CEC for <scim@ietfa.amsl.com>; Tue, 6 Oct 2020 09:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=slack-corp.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 6QkaOzPWb1iA for <scim@ietfa.amsl.com>; Tue, 6 Oct 2020 09:51:41 -0700 (PDT)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 3D0FD3A0CE3 for <scim@ietf.org>; Tue, 6 Oct 2020 09:51:41 -0700 (PDT)
Received: by mail-il1-x12a.google.com with SMTP id l16so11578264ilt.13 for <scim@ietf.org>; Tue, 06 Oct 2020 09:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=slack-corp.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=7UBPLP0sDUuKGd1eAX8eAIcgPqUmbTsBk4klZcbSPak=; b=jSSLE6UTwajKoEc7NeCOLlARbHV3NJZlCR+t48brXKICTM2cKbx2aQcFGX7C57nhjm TmJUTawUZ8Byzu2jJK9IrxoWiitSJH++1WSXXYL5XBLC8H08Ah8DeLHVfTwKUdHOas4s Y1jj7iIggJk14tBNuVPmIRT6zM7/jbb/ubWiQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7UBPLP0sDUuKGd1eAX8eAIcgPqUmbTsBk4klZcbSPak=; b=DvWv9FF+SAfetKc7vfrXFuf0KdGFoRGCXe9EA/ZiLExz+KWJgx6gNrFjtztdWWOqdl SMZXUy+UbwHfQBBwE3/M/VpDeb7BOvU2I1k4hV6HOc7Hcf6ZjGkzjAxvff88D2bGLaLv u4ibsF80Vd42Epmvvx/apanR8v9wcmUETBFEmEsgARZPiYGA0DBGwtE/tdMJjS3x1QQz VCq12mK+3kvinSUkFMBEI+k0Pl5/9ZnszLtGVi3mj6iGp10XROdU8dmE15pwy6+TxJpx IszRvt36lfVHLpjdoZAaENdNtykX+8ZTu57qeCtHlxcgEt+Dza7ejAJd9eHfQEW9aKNq Rcyg==
X-Gm-Message-State: AOAM53399nf/A84tevUN2uvARkg4UzdTzF5oD5qeOMFLnLWUowHsNRGZ /b/J2Vk2i2m+9N+Hk/EbeGU3YwRUOs+AxU/1BHWjMZoBWJg=
X-Google-Smtp-Source: ABdhPJxP/T9ecpsP6QxDos96+HOssqfmjpathxVtK0czQFEsRK564Q3vpxz+hRzEBpyCJjOGy5pxeGLpW57G8gUiS6Y=
X-Received: by 2002:a92:1589:: with SMTP id 9mr4431843ilv.292.1602003100028; Tue, 06 Oct 2020 09:51:40 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.2601.1599667404.7978.scim@ietf.org>
In-Reply-To: <mailman.2601.1599667404.7978.scim@ietf.org>
From: Audrei Drummond <adrummond@slack-corp.com>
Date: Tue, 6 Oct 2020 12:51:29 -0400
Message-ID: <CA+0cy9Fe2F3NYRhnJVigCagC+sd3BxrnmXSj+7AJTNHBMVirOA@mail.gmail.com>
To: scim@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b5013805b10369cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/F3LnzIjvb7q8xKNJbcK1pwm4Y6o>
Subject: Re: [scim] Moving towards the next IETF Meeting
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: Tue, 06 Oct 2020 16:51:43 -0000

+1, I'm also interested

On Wed, Sep 9, 2020 at 12:03 PM <scim-request@ietf.org> wrote:

> Send scim mailing list submissions to
>         scim@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/scim
> or, via email, send a message with subject or body 'help' to
>         scim-request@ietf.org
>
> You can reach the person managing the list at
>         scim-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of scim digest..."
> Today's Topics:
>
>    1. Moving towards the next IETF Meeting (Pamela Dingle)
>    2. PRECIS questions (Sarah Mundy)
>    3. Re: Moving towards the next IETF Meeting (Paul Lanzi)
>    4. Re: Moving towards the next IETF Meeting (Darran Rolls)
>
>
>
> ---------- Forwarded message ----------
> From: Pamela Dingle <Pamela.Dingle@microsoft.com>
> To: "scim@ietf.org" <scim@ietf.org>
> Cc:
> Bcc:
> Date: Wed, 9 Sep 2020 15:34:59 +0000
> Subject: [scim] Moving towards the next IETF Meeting
> Hi SCIM working group,
>
> I would like to propose we get together to do three things:
>
> 1) Share each of our goals for where SCIM can go
>
> 2) Find the commonalities
>
> 3) Create a roadmap for the time between now and the next IETF meeting to
> achieve those goals
>
> I will find a time, is there interest?
>
>
>
> ---------- Forwarded message ----------
> From: Sarah Mundy <the.sarah.mundy@gmail.com>
> To: scim@ietf.org
> Cc:
> Bcc:
> Date: Mon, 31 Aug 2020 08:22:03 -0700
> Subject: [scim] PRECIS questions
> Hi all,
>
> A couple of questions about PRECIS string comparison for SCIM 2.0:
>
> 1. The SCIM 2.0 spec references RFCs 7564 and 7613, which are obsolete
> drafts of PRECIS. Are folks instead using the final versions, RFCs 8264 and
> 8265?
>
> 2. Can anyone point me to a stable, open-source library of PRECIS tools,
> preferably in Java? What are other server implementers using? I haven't
> been able to find anything but maybe I am not using the right keywords in
> my searches.
>
> Thanks,
> Sarah
>
>
>
> ---------- Forwarded message ----------
> From: Paul Lanzi <paul@remediant.com>
> To: Pamela Dingle <Pamela.Dingle=40microsoft.com@dmarc.ietf.org>
> Cc: "scim@ietf.org" <scim@ietf.org>
> Bcc:
> Date: Wed, 9 Sep 2020 08:39:28 -0700
> Subject: Re: [scim] Moving towards the next IETF Meeting
> Hi Pam - certainly would be interested.
>
> --Paul
> ᐧ
>
> On Wed, Sep 9, 2020 at 8:37 AM Pamela Dingle <Pamela.Dingle=
> 40microsoft.com@dmarc.ietf.org> wrote:
>
>> Hi SCIM working group,
>>
>> I would like to propose we get together to do three things:
>>
>> 1) Share each of our goals for where SCIM can go
>>
>> 2) Find the commonalities
>>
>> 3) Create a roadmap for the time between now and the next IETF meeting to
>> achieve those goals
>>
>> I will find a time, is there interest?
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim
>>
>
>
>
> ---------- Forwarded message ----------
> From: Darran Rolls <me@darranrolls.com>
> To: Paul Lanzi <paul@remediant.com>om>, Pamela Dingle <Pamela.Dingle=
> 40microsoft.com@dmarc.ietf.org>
> Cc: "scim@ietf.org" <scim@ietf.org>
> Bcc:
> Date: Wed, 9 Sep 2020 16:03:16 +0000
> Subject: Re: [scim] Moving towards the next IETF Meeting
>
> Me2.
>
>
>
> I’ve not shared the results of our “I’m interested to contribute here”
> analysis – I’ll do that now – that’s a key input into this process.  In
> summary there are gaps but commonality and lots to do…
>
>
>
> Darran
>
>
>
> *From: *scim <scim-bounces@ietf.org> on behalf of Paul Lanzi <
> paul@remediant.com>
> *Date: *Wednesday, September 9, 2020 at 10:55 AM
> *To: *Pamela Dingle <Pamela.Dingle=40microsoft.com@dmarc.ietf.org>
> *Cc: *"scim@ietf.org" <scim@ietf.org>
> *Subject: *Re: [scim] Moving towards the next IETF Meeting
>
>
>
> Hi Pam - certainly would be interested.
>
>
>
> --Paul
>
> [image: Image removed by sender.]ᐧ
>
>
>
> On Wed, Sep 9, 2020 at 8:37 AM Pamela Dingle <Pamela.Dingle=
> 40microsoft.com@dmarc.ietf.org> wrote:
>
> Hi SCIM working group,
>
>
>
> I would like to propose we get together to do three things:
>
>
>
> 1) Share each of our goals for where SCIM can go
>
>
>
> 2) Find the commonalities
>
>
>
> 3) Create a roadmap for the time between now and the next IETF meeting to
> achieve those goals
>
>
>
> I will find a time, is there interest?
>
> _______________________________________________
> 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
>