IETF Logo Mail Archive

Re: [scim] Proposal to create a design team

Hannes Tschofenig <hannes.tschofenig@gmx.net> Thu, 18 October 2012 15:54 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 0406821F858F for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 08:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.39
X-Spam-Level:
X-Spam-Status: No, score=-102.39 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3GqZIzXHQ5xW for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 08:54:02 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id F0DA521F85C0 for <scim@ietf.org>; Thu, 18 Oct 2012 08:54:01 -0700 (PDT)
Received: (qmail invoked by alias); 18 Oct 2012 15:54:00 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.100]) [88.115.216.191] by mail.gmx.net (mp032) with SMTP; 18 Oct 2012 17:54:00 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19QG7oL17ZQR1gev3fVqASyTUXcswdFZ7LSc7rbMr X+M4WLTSM0U1M2
Date: Thu, 18 Oct 2012 18:53:50 +0300
Message-ID: <um7k6oax2axi1qqfj80629hl.1350575630439@email.android.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: Eliot Lear <lear@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_899299193620332"
X-Y-GMX-Trusted: 0
Cc: Leif Johansson <leifj@mnt.se>, scim@ietf.org
Subject: Re: [scim] Proposal to create a design team
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 18 Oct 2012 15:54:03 -0000

I have to agree with Eliot. 

A story from my experience in ECRIT. When we started the work on the main architecture document Marc and I decided to do that work as part of a design team. Since the work was so central to the group it turns out that everyone in the group wanted to be part of the design team. The only benefit in having a design them (once you accept everyone, which is what we did) was that we could schedule conference calls.

For the SCIM design team I was wondering whether I should raise my hand as well in order to get to know what work is going on in SCIM on the protocol. Not being part of the design team essentially means that you are cut off from the information flow.

Given that the group has much more already than a protocol specification but already an interoperability test site and various interoperable implementations I wonder whether the design team idea isn't going to delay the progress.

Sent from my ASUS Pad

Eliot Lear <lear@cisco.com> wrote:

>_______________________________________________
>scim mailing list
>scim@ietf.org
>https://www.ietf.org/mailman/listinfo/scim

v2.23.0 | Report a Bug | By Email