Re: [scim] Proposal to create a design team

Hannes Tschofenig <hannes.tschofenig@gmx.net> Thu, 18 October 2012 18:49 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 B323421F8835 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 11:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level:
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, 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 QdAAXjMF4tCC for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 11:49:34 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 6F92421F873A for <scim@ietf.org>; Thu, 18 Oct 2012 11:49:34 -0700 (PDT)
Received: (qmail invoked by alias); 18 Oct 2012 18:49:32 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.103]) [88.115.216.191] by mail.gmx.net (mp027) with SMTP; 18 Oct 2012 20:49:32 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX184eOAySz04fFSQcLNOihM3WMT5k15Gn3AvxSVkR5 zhFYv1lRUfzLAi
Date: Thu, 18 Oct 2012 21:49:24 +0300
Message-ID: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: Phil Hunt <phil.hunt@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-Y-GMX-Trusted: 0
Cc: igor.faynberg@alcatel-lucent.com, 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 18:49:35 -0000

Which conference call last Wednesday? I did not see a conference call announcement on the list.

Sent from my ASUS Pad

Phil Hunt <phil.hunt@oracle.com> wrote:

>All these points and more were discussed on the con call last Wednesday.  The chairs did a great job and more importantly they reported back to the WG.
>
>I don't see a problem here.
>
>Phil
>
>@independentid
>www.independentid.com
>phil.hunt@oracle.com
>
>
>
>
>
>On 2012-10-18, at 10:25 AM, Hannes Tschofenig wrote:
>
>> Hi Igor,
>> 
>> I am not sure what you mean. Here is what the IESG says about design teams: http://www.ietf.org/iesg/statement/design-team.html
>> 
>> Ciao
>> Hannes
>> 
>> PS: Btw, although http://www.ietf.org/iesg/statement/design-team.html says that
>> "
>> The key point here is that the output of a design team is input to a working group, not a final document.
>> "
>> I think it is a rather theoretical statement.
>> 
>> I have been involved in about 20 design teams and I have never had the case where the output of the design team was rejected by the group.
>> 
>> On 10/18/2012 08:16 PM, Igor Faynberg wrote:
>>> I tend to stick to Eliot- the-Stick-in-the-Mud's principle on that
>>> issue, but my questions are from the other end of spectrum.
>>> 
>>>   The precedence is such as that a design team can be created either 1)
>>> outside of a working group (as was the case of  the SIN design team 12
>>> years ago) or  2) as part of a working group (what with SIP WG design
>>> teams).
>>> 
>>>  I take it that the proposal is for the case 2, but so far we seem to
>>> have a fairly small group, vis-a-vis that gigantic SIP WG, whose sheer
>>> size necessitated parallelism. And hence question is why a separate
>>> subset group is needed at all.  Of course,  people may have specific
>>> interests, and nothing prevents them from forming a special interest
>>> group, writing drafts and getting them through the WG process.
>>> 
>>> In short, what privileges will the official /design team /have in the
>>> process vs. a typical de-facto design team?
>>> 
>>> Igor
>>> 
>>> On 10/18/2012 11:32 AM, Eliot Lear wrote:
>>>> Leif, Morteza,
>>>> 
>>>> I'm sorry to be a stick in the mud, but I don't understand the
>>>> objective of this design team.  Let's start with an easy question:
>>>> 
>>>>  * What work are they supposed to do?  What issues are they supposed
>>>>    to address?
>>>> 
>>>> Put another way, I was not of the understanding that what is posted is
>>>> a strawman, but based on running code.  If there is running code, it
>>>> seems to me that the onus is on those in the WG to state issues.
>>>> There are a number, as I understand it.  A design team is necessary
>>>> when something needs to be designed. What here needs to be designed
>>>> 
>>>> Now to answer my question in part, there is this dangling reference to
>>>> ServiceProviderConfigs.  Is that needed or should it be removed?
>>>> 
>>>> I guess what I'm asking for is just a bit more scope, please.
>>>> 
>>>> Eliot
>>>> 
>>>> 
>>>> On 10/11/12 11:31 AM, Leif Johansson wrote:
>>>>> On 10/11/2012 09:02 AM, Hannes Tschofenig wrote:
>>>>> > Hi chairs,
>>>>> 
>>>>> > Are we talking about this document:
>>>>> > http://datatracker.ietf.org/doc/draft-ietf-scim-api/
>>>>> 
>>>>> > Looks like a strawman proposal to me already right now.
>>>>> 
>>>>> We are talking about a strawman for the next major revision of
>>>>> that document and the schema document.
>>>>> 
>>>>> It is great to see so many are willing to participate. Please
>>>>> note that participation in a design-team requires active
>>>>> participation and time comittment.
>>>>> 
>>>>>    Best R
>>>>>    Leif
>>>>> 
>>>> >
>>>> _______________________________________________
>>>> 
>>>> > 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
>>> 
>>> 
>>> _______________________________________________
>>> 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
>
>_______________________________________________
>scim mailing list
>scim@ietf.org
>https://www.ietf.org/mailman/listinfo/scim