
From zachary.zeltsan@alcatel-lucent.com  Mon Oct  8 13:59:36 2012
Return-Path: <zachary.zeltsan@alcatel-lucent.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 ED61D1F0C42 for <scim@ietfa.amsl.com>; Mon,  8 Oct 2012 13:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.249
X-Spam-Level: 
X-Spam-Status: No, score=-8.249 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 lJH4DfkZcmfQ for <scim@ietfa.amsl.com>; Mon,  8 Oct 2012 13:59:36 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9D10A1F0C4A for <scim@ietf.org>; Mon,  8 Oct 2012 13:59:35 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q98KxXMO026177 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <scim@ietf.org>; Mon, 8 Oct 2012 22:59:33 +0200
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 8 Oct 2012 22:59:33 +0200
Received: from US70TWXCHMBA09.zam.alcatel-lucent.com ([169.254.3.198]) by US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id 14.02.0247.003; Mon, 8 Oct 2012 16:59:31 -0400
From: "Zeltsan, Zachary (Zachary)" <zachary.zeltsan@alcatel-lucent.com>
To: "'scim WG'" <scim@ietf.org>
Thread-Topic: New Version Notification for draft-zeltsan-scim-use-cases-00.txt
Thread-Index: AQHNpZb6VPQHw1awRES5p9YTElk465ev4txw
Date: Mon, 8 Oct 2012 20:59:30 +0000
Message-ID: <F5B2863BFA782C4E8866941363AE88E8C6B157@US70TWXCHMBA09.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Subject: [scim] FW: New Version Notification for draft-zeltsan-scim-use-cases-00.txt
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: Mon, 08 Oct 2012 20:59:37 -0000

T24gYmVoYWxmIG9mIHRoZSBjby1hdXRob3JzIEkgaGF2ZSBwb3N0ZWQgdGhlIC0wMCByZXZpc2lv
biBvZiB0aGUgZHJhZnQgb24gU0NJTSB1c2UgY2FzZXMuDQoNClphY2hhcnkNCg0KLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRv
OmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50OiBNb25kYXksIE9jdG9iZXIgMDgsIDIw
MTIgNDo1MyBQTQ0KVG86IFplbHRzYW4sIFphY2hhcnkgKFphY2hhcnkpDQpDYzogdG9ueW5hZEBt
aWNyb3NvZnQuY29tOyB2dW1pcDFAZ21haWwuY29tOyBwaGlsLmh1bnRAb3JhY2xlLmNvbQ0KU3Vi
amVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC16ZWx0c2FuLXNjaW0tdXNl
LWNhc2VzLTAwLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC16ZWx0c2FuLXNj
aW0tdXNlLWNhc2VzLTAwLnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBa
YWNoYXJ5IFplbHRzYW4gYW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCg0KRmls
ZW5hbWU6CSBkcmFmdC16ZWx0c2FuLXNjaW0tdXNlLWNhc2VzDQpSZXZpc2lvbjoJIDAwDQpUaXRs
ZToJCSBTQ0lNIFVzZSBDYXNlcw0KQ3JlYXRpb24gZGF0ZToJIDIwMTItMTAtMDgNCldHIElEOgkJ
IEluZGl2aWR1YWwgU3VibWlzc2lvbg0KTnVtYmVyIG9mIHBhZ2VzOiAxMA0KVVJMOiAgICAgICAg
ICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC16ZWx0c2FuLXNj
aW0tdXNlLWNhc2VzLTAwLnR4dA0KU3RhdHVzOiAgICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIu
aWV0Zi5vcmcvZG9jL2RyYWZ0LXplbHRzYW4tc2NpbS11c2UtY2FzZXMNCkh0bWxpemVkOiAgICAg
ICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtemVsdHNhbi1zY2ltLXVzZS1jYXNl
cy0wMA0KDQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVudCBsaXN0cyB0aGUgdXNlIGNhc2Vz
IG9mIFN5c3RlbSBmb3IgQ3Jvc3MtZG9tYWluIElkZW50aXR5DQogICBNYW5hZ2VtZW50IChTQ0lN
KS4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0
DQoNCg==

From moransar@cisco.com  Wed Oct 10 13:34:30 2012
Return-Path: <moransar@cisco.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 9B26D11E809A for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 13:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 bB13GyvttWLz for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 13:34:30 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 1ACD511E808D for <scim@ietf.org>; Wed, 10 Oct 2012 13:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3683; q=dns/txt; s=iport; t=1349901270; x=1351110870; h=from:to:subject:date:message-id:mime-version; bh=zerp+AJBS9uHBQwVT6ivCXMta2Sh18poPf5eMJDE36U=; b=guZ7OPEmiV8CxvSsvLWSvNGCk9La2He3hYSqa734sGi7n15ZpmwnagEx Ea1ma7kvjJFCPaq29E2DCHT2kupEe3yZ8jyIQwOuqFclCXTWcisol9qbL +Xu0L1SSfN4FvRGF/NGBxIVoo25SB2mDTGw+qtUDLLwF3Dov4uFk+Fg+h 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAIDadVCtJXHA/2dsb2JhbABEgku8Z4EIgiIBBBIBeAEMHlYnBBsah2KWQYEooB2RB2ADpDGBa4Jtghc
X-IronPort-AV: E=Sophos;i="4.80,565,1344211200";  d="scan'208,217";a="130301187"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-2.cisco.com with ESMTP; 10 Oct 2012 20:34:29 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id q9AKYTYs003307 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <scim@ietf.org>; Wed, 10 Oct 2012 20:34:29 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.234]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.001; Wed, 10 Oct 2012 15:34:29 -0500
From: "Morteza Ansari (moransar)" <moransar@cisco.com>
To: "scim@ietf.org" <scim@ietf.org>
Thread-Topic: Proposal to create a design team
Thread-Index: AQHNpyalxIOrHKgYwk66fmTht0qU2A==
Date: Wed, 10 Oct 2012 20:34:29 +0000
Message-ID: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.21.166.40]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19258.000
x-tm-as-result: No--26.673500-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_CA3B67220D628A4780D6FEB31F18A3E32379CB76xmbrcdx08ciscoc_"
MIME-Version: 1.0
Subject: [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: Wed, 10 Oct 2012 20:34:30 -0000

--_000_CA3B67220D628A4780D6FEB31F18A3E32379CB76xmbrcdx08ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Folks,

To expedite getting to a straw man proposal, we propose the creation of a d=
esign team to get the work rolling. We have a few volunteers already signed=
 up:

Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda

If anyone else is interested in joining the design team and contributing pl=
ease let us know. The expectation is that the design team will put a concen=
trated effort into creating the initial straw man proposal for discussions =
by the larger working group.

If anyone is violently opposed to this plan, please say so right now. Silen=
ce counts as acceptance in this case. To learn about the concept
of design teams in the IETF read RFC 2418 (section 6.5).


Cheers,
Morteza & Leif

--_000_CA3B67220D628A4780D6FEB31F18A3E32379CB76xmbrcdx08ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-ID: <50F5458F1D6B9649A403038FA8B6DD01@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Hi Folks,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
To expedite getting to a straw man proposal, we propose the creation of a d=
esign team to get the work rolling. We have a few volunteers already signed=
 up:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
If anyone else is interested in joining the design team and contributing pl=
ease let us know. The expectation is that the design team will put a concen=
trated effort into creating the initial straw man proposal for discussions =
by the larger working group.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div>
<div><font class=3D"Apple-style-span" face=3D"Calibri,sans-serif">If anyone=
 is violently opposed to this plan, please say so right now.&nbsp;</font><s=
pan class=3D"Apple-style-span" style=3D"font-family: Calibri, sans-serif; "=
>Silence counts as acceptance in this case. To
 learn about the concept</span></div>
<div><font class=3D"Apple-style-span" face=3D"Calibri,sans-serif">of design=
 teams in the IETF read RFC 2418 (section 6.5).</font></div>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Cheers,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Morteza &amp; Leif</div>
</div>
</body>
</html>

--_000_CA3B67220D628A4780D6FEB31F18A3E32379CB76xmbrcdx08ciscoc_--

From prvs=9630B53C80=erik.wahlstrom@nexussafe.com  Wed Oct 10 14:09:00 2012
Return-Path: <prvs=9630B53C80=erik.wahlstrom@nexussafe.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 917DC21F8554 for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 14:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 s6MDm+guDZLd for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 14:09:00 -0700 (PDT)
Received: from MailEdge.nexussafe.com (mailedge.nexussafe.com [83.241.133.98]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9D321F8550 for <scim@ietf.org>; Wed, 10 Oct 2012 14:08:59 -0700 (PDT)
Received: from MARVMAILCAS.technxs.com (10.75.28.35) by MailEdge.nexussafe.com (83.241.133.98) with Microsoft SMTP Server (TLS) id 14.1.379.0; Wed, 10 Oct 2012 23:09:01 +0200
Received: from MARVMAILDB.technxs.com ([fe80::153d:18f8:4f37:e551]) by MarvMailCAS.technxs.com ([::1]) with mapi id 14.01.0355.002; Wed, 10 Oct 2012 23:08:53 +0200
From: =?iso-8859-1?Q?Erik_Wahlstr=F6m?= <erik.wahlstrom@nexussafe.com>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
Thread-Topic: [scim] Proposal to create a design team
Thread-Index: AQHNpyalxIOrHKgYwk66fmTht0qU2Jey5xCA
Date: Wed, 10 Oct 2012 21:08:52 +0000
Message-ID: <44C27B49-B4F4-40A0-9CE2-7F293FA148E2@nexussafe.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
In-Reply-To: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Accept-Language: en-US, sv-SE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.75.28.12]
Content-Type: multipart/alternative; boundary="_000_44C27B49B4F440A09CE27F293FA148E2nexussafecom_"
MIME-Version: 1.0
Cc: "scim@ietf.org" <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: Wed, 10 Oct 2012 21:09:00 -0000

--_000_44C27B49B4F440A09CE27F293FA148E2nexussafecom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

If anyone else is interested in joining the design team and contributing pl=
ease let us know.

Sure thing.

Cheers
Erik Wahlstr=F6m



On Oct 10, 2012, at 10:34 PM, Morteza Ansari (moransar) wrote:

Hi Folks,

To expedite getting to a straw man proposal, we propose the creation of a d=
esign team to get the work rolling. We have a few volunteers already signed=
 up:

Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda

If anyone else is interested in joining the design team and contributing pl=
ease let us know. The expectation is that the design team will put a concen=
trated effort into creating the initial straw man proposal for discussions =
by the larger working group.

If anyone is violently opposed to this plan, please say so right now. Silen=
ce counts as acceptance in this case. To learn about the concept
of design teams in the IETF read RFC 2418 (section 6.5).


Cheers,
Morteza & Leif
_______________________________________________
scim mailing list
scim@ietf.org<mailto:scim@ietf.org>
https://www.ietf.org/mailman/listinfo/scim



--_000_44C27B49B4F440A09CE27F293FA148E2nexussafecom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <17FF65EEC51BEA4EB6E336EE8E54845E@nexussafe.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
If anyone else is interested in joining the design team and contributing pl=
ease let us know.&nbsp;</div>
</div>
</div>
</blockquote>
<br>
</div>
Sure thing.
<div><br>
</div>
<div>Cheers</div>
<div>Erik Wahlstr=F6m</div>
<div><br>
</div>
<div><br>
<div><br>
<div>
<div>On Oct 10, 2012, at 10:34 PM, Morteza Ansari (moransar) wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Hi Folks,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
To expedite getting to a straw man proposal, we propose the creation of a d=
esign team to get the work rolling. We have a few volunteers already signed=
 up:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
If anyone else is interested in joining the design team and contributing pl=
ease let us know. The expectation is that the design team will put a concen=
trated effort into creating the initial straw man proposal for discussions =
by the larger working group.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div>
<div><font class=3D"Apple-style-span" face=3D"Calibri,sans-serif">If anyone=
 is violently opposed to this plan, please say so right now.&nbsp;</font><s=
pan class=3D"Apple-style-span" style=3D"font-family: Calibri, sans-serif; "=
>Silence counts as acceptance in this case. To
 learn about the concept</span></div>
<div><font class=3D"Apple-style-span" face=3D"Calibri,sans-serif">of design=
 teams in the IETF read RFC 2418 (section 6.5).</font></div>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Cheers,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; ">
Morteza &amp; Leif</div>
</div>
</div>
_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org">scim@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/scim<br>
</blockquote>
</div>
<br>
</div>
</div>
<div><br>
</div>
</body>
</html>

--_000_44C27B49B4F440A09CE27F293FA148E2nexussafecom_--

From olds@rbcon.com  Wed Oct 10 14:28:38 2012
Return-Path: <olds@rbcon.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 B6EB71F041F for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 14:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 RZjWXunlY0Ig for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 14:28:38 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 340FD1F040A for <scim@ietf.org>; Wed, 10 Oct 2012 14:28:38 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so382335dan.31 for <scim@ietf.org>; Wed, 10 Oct 2012 14:28:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:x-gm-message-state; bh=RxXhpIdcdLAK6rSmHqkUvC2wItCFyX9q4tOc9vhjJSQ=; b=Fe6+HJJBp0s+si+WqdDiCbsxewBvcmRQX9WLJYeHA1Yd0AHg8vWG4gUZ5eU58UmiWA uFg6dQfOCTvvLC01rO978MV9wajfeu+I+MVUN7fchuNmUvcxy2zp15QVDmiqJMGElCtm SyM9ID7w14A1Vbxb1T6GutdXn8klqz43wmIjNDKfPDXyqPSVW1dOTA+kN2jE3rk/l5/K yHRq+zPlHek63yLFtBLsPiJsCnEBiXoKsrKBcuvDAZlE6swt9+MYjXwbg2GDQ5deTHtG 0vyqywkWzRYr32NwQ/kkAk6xqXP3iCADYV3/RUVXGzqq/cmKiUNYj28HHvCTkh8fGGP0 nOJg==
Received: by 10.68.134.99 with SMTP id pj3mr76711242pbb.13.1349904517797; Wed, 10 Oct 2012 14:28:37 -0700 (PDT)
Received: from ?IPv6:2601:9:5800:33:6680:99ff:fe4e:5cc8? ([2601:9:5800:33:6680:99ff:fe4e:5cc8]) by mx.google.com with ESMTPS id pw2sm1558551pbb.59.2012.10.10.14.28.36 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 10 Oct 2012 14:28:37 -0700 (PDT)
Message-ID: <5075E883.5030503@rbcon.com>
Date: Wed, 10 Oct 2012 14:28:35 -0700
From: Dale Olds <olds@rbcon.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: scim@ietf.org
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
In-Reply-To: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Content-Type: multipart/alternative; boundary="------------080606010906010403020708"
X-Gm-Message-State: ALoCoQk0SVaHJW7tLrEtWSScJwdwIf4aTVOC1Qiri5fBfvQZBhhBF0x5wtogwFfS6Ovqtlz+oQH/
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: Wed, 10 Oct 2012 21:28:38 -0000

This is a multi-part message in MIME format.
--------------080606010906010403020708
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I'd like to participate. If nothing else, I can at least argue with Tony 
so everyone else can get work done.

--Dale

On 10/10/2012 01:34 PM, Morteza Ansari (moransar) wrote:
> Hi Folks,
>
> To expedite getting to a straw man proposal, we propose the creation 
> of a design team to get the work rolling. We have a few volunteers 
> already signed up:
>
> Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda
>
> If anyone else is interested in joining the design team and 
> contributing please let us know. The expectation is that the design 
> team will put a concentrated effort into creating the initial straw 
> man proposal for discussions by the larger working group.
>
> If anyone is violently opposed to this plan, please say so right now. 
> Silence counts as acceptance in this case. To learn about the concept
> of design teams in the IETF read RFC 2418 (section 6.5).
>
>
> Cheers,
> Morteza & Leif
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim


--------------080606010906010403020708
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I'd like to participate. If nothing else, I can at least argue with
    Tony so everyone else can get work done. <br>
    <br>
    --Dale<br>
    <br>
    <div class="moz-cite-prefix">On 10/10/2012 01:34 PM, Morteza Ansari
      (moransar) wrote:<br>
    </div>
    <blockquote
cite="mid:CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          Hi Folks,</div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          <br>
        </div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          To expedite getting to a straw man proposal, we propose the
          creation of a design team to get the work rolling. We have a
          few volunteers already signed up:</div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          <br>
        </div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and
          Melinda</div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          <br>
        </div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          If anyone else is interested in joining the design team and
          contributing please let us know. The expectation is that the
          design team will put a concentrated effort into creating the
          initial straw man proposal for discussions by the larger
          working group.</div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          <br>
        </div>
        <div>
          <div><font class="Apple-style-span" face="Calibri,sans-serif">If
              anyone is violently opposed to this plan, please say so
              right now.&nbsp;</font><span class="Apple-style-span"
              style="font-family: Calibri, sans-serif; ">Silence counts
              as acceptance in this case. To learn about the concept</span></div>
          <div><font class="Apple-style-span" face="Calibri,sans-serif">of
              design teams in the IETF read RFC 2418 (section 6.5).</font></div>
        </div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          <br>
        </div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          <br>
        </div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          Cheers,</div>
        <div style="color: rgb(0, 0, 0); font-family: Calibri,
          sans-serif; font-size: 14px; ">
          Morteza &amp; Leif</div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
scim mailing list
<a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080606010906010403020708--

From hasini@wso2.com  Wed Oct 10 16:36:18 2012
Return-Path: <hasini@wso2.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 38FB411E808D for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 16:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 Fh4RBrgqEAE2 for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 16:36:17 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 41E0821F859C for <scim@ietf.org>; Wed, 10 Oct 2012 16:36:17 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so1222816vbb.31 for <scim@ietf.org>; Wed, 10 Oct 2012 16:36:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=YZW2GH9sktZ5l8KAU7AcojpoIRwinhF72xfpDIXIZjE=; b=eVomSe1L1hKUrgdiiLhKZl4nJaMEV85vn0HhRCcjCb5HszMFgsMujXYK5b1ETpKZx0 qxWcnpR32wNQNGK0Dp/UUevJodLPBieceGSDysTaReKhcSj9z0PR2f/08oBSLlaJZ1wy 6cV7jLrcLd9FIVyvWY8h5US5z5JW5ZEmgV0GkHwiTeHbaxhxx15wx/c7vo7mA2L3Y08n RpGwcGeod9sqfuPbNjYpzbnTQjkjBqNcdaNxUGEenFqu3s7H+ZEasmjZrqrgnTnR8B4X oPFfnwjiuAIyZQVsu6tQ6G812jRFTHbQJRIxPMLV8m2cdObwJ0QOAVbaMjNjI6eyobpu ni9A==
MIME-Version: 1.0
Received: by 10.220.148.211 with SMTP id q19mr14912004vcv.55.1349912176557; Wed, 10 Oct 2012 16:36:16 -0700 (PDT)
Received: by 10.58.203.134 with HTTP; Wed, 10 Oct 2012 16:36:16 -0700 (PDT)
In-Reply-To: <44C27B49-B4F4-40A0-9CE2-7F293FA148E2@nexussafe.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <44C27B49-B4F4-40A0-9CE2-7F293FA148E2@nexussafe.com>
Date: Thu, 11 Oct 2012 05:06:16 +0530
Message-ID: <CAOCmpSmBfGebitHYjAxE1voaAp+mgTGe7Wv+61cJKDYHEbFJeg@mail.gmail.com>
From: Hasini Gunasinghe <hasini@wso2.com>
To: =?ISO-8859-1?Q?Erik_Wahlstr=F6m?= <erik.wahlstrom@nexussafe.com>
Content-Type: multipart/alternative; boundary=f46d043bdf16c2fca104cbbceb14
X-Gm-Message-State: ALoCoQn7Ro+79Aa544muAsYQmPFnLrQo/0H4NBmhhVH64HK+ipcECUOxgylI+7lYe/ujVSOoZY47
Cc: "scim@ietf.org" <scim@ietf.org>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>
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: Wed, 10 Oct 2012 23:36:18 -0000

--f46d043bdf16c2fca104cbbceb14
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 11, 2012 at 2:38 AM, Erik Wahlstr=F6m <
erik.wahlstrom@nexussafe.com> wrote:

>    If anyone else is interested in joining the design team and
> contributing please let us know.
>
> +1. I would like to join.

Thanks,
Hasini.

>
>  Sure thing.
>
>  Cheers
> Erik Wahlstr=F6m
>
>
>
>  On Oct 10, 2012, at 10:34 PM, Morteza Ansari (moransar) wrote:
>
>   Hi Folks,
>
>  To expedite getting to a straw man proposal, we propose the creation of
> a design team to get the work rolling. We have a few volunteers already
> signed up:
>
>  Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda
>
>  If anyone else is interested in joining the design team and contributing
> please let us know. The expectation is that the design team will put a
> concentrated effort into creating the initial straw man proposal for
> discussions by the larger working group.
>
>  If anyone is violently opposed to this plan, please say so right now. Si=
lence
> counts as acceptance in this case. To learn about the concept
> of design teams in the IETF read RFC 2418 (section 6.5).
>
>
>  Cheers,
>  Morteza & 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
>
>

--f46d043bdf16c2fca104cbbceb14
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Thu, Oct 11, 2012 at 2:38 AM, Erik Wa=
hlstr=F6m <span dir=3D"ltr">&lt;<a href=3D"mailto:erik.wahlstrom@nexussafe.=
com" target=3D"_blank">erik.wahlstrom@nexussafe.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">




<div style=3D"word-wrap:break-word"><div class=3D"im">
<div>
<blockquote type=3D"cite">
<div style=3D"word-wrap:break-word">
<div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
If anyone else is interested in joining the design team and contributing pl=
ease let us know.=A0</div></div></div></blockquote></div></div></div></bloc=
kquote><div>+1. I would like to join.</div><div><br></div><div>Thanks,</div=
>
<div>Hasini.=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap=
:break-word"><div class=3D"im"><div><blockquote type=3D"cite"><div style=3D=
"word-wrap:break-word">
<div>
</div>
</div>
</blockquote>
<br>
</div></div>
Sure thing.
<div><br>
</div>
<div>Cheers</div>
<div>Erik Wahlstr=F6m</div>
<div><br>
</div>
<div><br>
<div><br>
<div><div><div class=3D"h5">
<div>On Oct 10, 2012, at 10:34 PM, Morteza Ansari (moransar) wrote:</div>
<br>
</div></div><blockquote type=3D"cite"><div><div class=3D"h5">
<div style=3D"word-wrap:break-word">
<div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
Hi Folks,</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
To expedite getting to a straw man proposal, we propose the creation of a d=
esign team to get the work rolling. We have a few volunteers already signed=
 up:</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
If anyone else is interested in joining the design team and contributing pl=
ease let us know. The expectation is that the design team will put a concen=
trated effort into creating the initial straw man proposal for discussions =
by the larger working group.</div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div>
<div><font face=3D"Calibri,sans-serif">If anyone is violently opposed to th=
is plan, please say so right now.=A0</font><span style=3D"font-family:Calib=
ri,sans-serif">Silence counts as acceptance in this case. To
 learn about the concept</span></div>
<div><font face=3D"Calibri,sans-serif">of design teams in the IETF read RFC=
 2418 (section 6.5).</font></div>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
Cheers,</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
Morteza &amp; Leif</div>
</div>
</div></div></div>
_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/scim" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/scim</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<div><br>
</div>
</div>

<br>_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org">scim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/scim" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/scim</a><br>
<br></blockquote></div><br>

--f46d043bdf16c2fca104cbbceb14--

From soohongp@gmail.com  Wed Oct 10 18:00:27 2012
Return-Path: <soohongp@gmail.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 4199B11E80E3 for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 18:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 1tVTLsE9wtu0 for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 18:00:26 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 43E9411E80E1 for <scim@ietf.org>; Wed, 10 Oct 2012 18:00:26 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so641904bkc.31 for <scim@ietf.org>; Wed, 10 Oct 2012 18:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7P5Um7jBtVP6kQZjhC1wwNScAbk5Ombz4hfaupRLQ5g=; b=WQMNxtxO10r5CFXAj5gapH7x0RoUCPcCzC338NS0zC7ozaUeXFIGuYB3IlireT7+nA 3IKvJ1qin6wmkrCiGRQhUYXseDTqXhkYe6zT9XJ5bBLbL0lhjnFJ79G3QGUXVzHPnbyI TMWRaNLPEykpWlUR5/wxhtBZEyEhm4F9lMgEb/BTptYcsyWPxTodjlFjpN/A51ZEzfWh vz3PiDKelc0U+5JlTHpWQ1HxBtM0GgWwYpYhaxKWpeEQl2h1QnfyCNm3IvaIxp06jgNP ZTCZ5nYAsntMlT1ZY+0WZyL8kTZod2X0KSES+1F7xY6f0fPPmUAVanOYyGhAvWoho3KA E1/A==
MIME-Version: 1.0
Received: by 10.205.137.7 with SMTP id im7mr8713325bkc.25.1349917225070; Wed, 10 Oct 2012 18:00:25 -0700 (PDT)
Received: by 10.204.149.85 with HTTP; Wed, 10 Oct 2012 18:00:25 -0700 (PDT)
In-Reply-To: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Date: Thu, 11 Oct 2012 10:00:25 +0900
Message-ID: <CAHSr+v1wuXULByvBXSpkQB6g2_71YYEe+7gEggBjh1gGRH7epg@mail.gmail.com>
From: Daniel Park <soohongp@gmail.com>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
Content-Type: multipart/alternative; boundary=000e0ce03dc2ad2ff504cbbe18df
Cc: "scim@ietf.org" <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, 11 Oct 2012 01:00:27 -0000

--000e0ce03dc2ad2ff504cbbe18df
Content-Type: text/plain; charset=ISO-8859-1

Good to see that activity. If allowed, I would like to join with the device
vendor's perspective in Cloud Service.

Daniel

-- 
*Soohong Daniel Park*
Cloud Computing Lab, Samsung


On Thu, Oct 11, 2012 at 5:34 AM, Morteza Ansari (moransar) <
moransar@cisco.com> wrote:

>   Hi Folks,
>
>  To expedite getting to a straw man proposal, we propose the creation of
> a design team to get the work rolling. We have a few volunteers already
> signed up:
>
>  Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda
>
>  If anyone else is interested in joining the design team and contributing
> please let us know. The expectation is that the design team will put a
> concentrated effort into creating the initial straw man proposal for
> discussions by the larger working group.
>
>  If anyone is violently opposed to this plan, please say so right now. Silence
> counts as acceptance in this case. To learn about the concept
> of design teams in the IETF read RFC 2418 (section 6.5).
>
>
>  Cheers,
>  Morteza & Leif
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>
>

--000e0ce03dc2ad2ff504cbbe18df
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Good to see that activity. If allowed, I would like to join with the d=
evice vendor&#39;s perspective in Cloud Service. </div><div>=A0</div><div>D=
aniel<br><br>-- <br></div><div><div><strong>Soohong Daniel Park</strong><br=
>
Cloud Computing Lab, Samsung</div></div><div><br>=A0</div><div class=3D"gma=
il_quote">On Thu, Oct 11, 2012 at 5:34 AM, Morteza Ansari (moransar) <span =
dir=3D"ltr">&lt;<a href=3D"mailto:moransar@cisco.com" target=3D"_blank">mor=
ansar@cisco.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">



<div style=3D"word-wrap:break-word">
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
Hi Folks,</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
To expedite getting to a straw man proposal, we propose the creation of a d=
esign team to get the work rolling. We have a few volunteers already signed=
 up:</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
If anyone else is interested in joining the design team and contributing pl=
ease let us know. The expectation is that the design team will put a concen=
trated effort into creating the initial straw man proposal for discussions =
by the larger working group.</div>

<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div>
<div><font face=3D"Calibri,sans-serif">If anyone is violently opposed to th=
is plan, please say so right now.=A0</font><span style=3D"font-family:Calib=
ri,sans-serif">Silence counts as acceptance in this case. To
 learn about the concept</span></div>
<div><font face=3D"Calibri,sans-serif">of design teams in the IETF read RFC=
 2418 (section 6.5).</font></div>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
Cheers,</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px">
Morteza &amp; Leif</div>
</div>
</div>

<br>_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org">scim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/scim" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/scim</a><br>
<br></blockquote></div><br><br clear=3D"all"><div>=A0</div><br>

--000e0ce03dc2ad2ff504cbbe18df--

From likepeng@huawei.com  Wed Oct 10 18:22:10 2012
Return-Path: <likepeng@huawei.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 037F521F8606 for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 18:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.841
X-Spam-Level: 
X-Spam-Status: No, score=-2.841 tagged_above=-999 required=5 tests=[AWL=-0.446, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 hdnmTCqUi-0P for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 18:22:09 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 95B9921F84EC for <scim@ietf.org>; Wed, 10 Oct 2012 18:22:07 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKM46154; Thu, 11 Oct 2012 01:22:00 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 11 Oct 2012 02:21:14 +0100
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 11 Oct 2012 02:21:32 +0100
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.168]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Thu, 11 Oct 2012 09:21:28 +0800
From: Likepeng <likepeng@huawei.com>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>, "scim@ietf.org" <scim@ietf.org>
Thread-Topic: Proposal to create a design team
Thread-Index: AQHNpyalxIOrHKgYwk66fmTht0qU2JezTwQg
Date: Thu, 11 Oct 2012 01:21:28 +0000
Message-ID: <34966E97BE8AD64EAE9D3D6E4DEE36F21ED50977@szxeml525-mbx.china.huawei.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
In-Reply-To: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.110.63]
Content-Type: multipart/alternative; boundary="_000_34966E97BE8AD64EAE9D3D6E4DEE36F21ED50977szxeml525mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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, 11 Oct 2012 01:22:10 -0000

--_000_34966E97BE8AD64EAE9D3D6E4DEE36F21ED50977szxeml525mbxchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SSB3b3VsZCBsaWtlIHRvIGpvaW4uDQoNClRoYW5rcywNCktpbmQgUmVnYXJkcw0KS2VwZW5nDQoN
CreivP7Iyzogc2NpbS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86c2NpbS1ib3VuY2VzQGlldGYu
b3JnXSC0+rHtIE1vcnRlemEgQW5zYXJpIChtb3JhbnNhcikNCreiy83KsbzkOiAyMDEyxOoxMNTC
MTHI1SA0OjM0DQrK1bz+yMs6IHNjaW1AaWV0Zi5vcmcNCtb3zOI6IFtzY2ltXSBQcm9wb3NhbCB0
byBjcmVhdGUgYSBkZXNpZ24gdGVhbQ0KDQpIaSBGb2xrcywNCg0KVG8gZXhwZWRpdGUgZ2V0dGlu
ZyB0byBhIHN0cmF3IG1hbiBwcm9wb3NhbCwgd2UgcHJvcG9zZSB0aGUgY3JlYXRpb24gb2YgYSBk
ZXNpZ24gdGVhbSB0byBnZXQgdGhlIHdvcmsgcm9sbGluZy4gV2UgaGF2ZSBhIGZldyB2b2x1bnRl
ZXJzIGFscmVhZHkgc2lnbmVkIHVwOg0KDQpUcmV5IERyYWtlLCBLZWxseSBHcml6emxlLCBQaGls
IEh1bnQsIEFudGhvbnkgTmFkYWxpbiwgYW5kIE1lbGluZGENCg0KSWYgYW55b25lIGVsc2UgaXMg
aW50ZXJlc3RlZCBpbiBqb2luaW5nIHRoZSBkZXNpZ24gdGVhbSBhbmQgY29udHJpYnV0aW5nIHBs
ZWFzZSBsZXQgdXMga25vdy4gVGhlIGV4cGVjdGF0aW9uIGlzIHRoYXQgdGhlIGRlc2lnbiB0ZWFt
IHdpbGwgcHV0IGEgY29uY2VudHJhdGVkIGVmZm9ydCBpbnRvIGNyZWF0aW5nIHRoZSBpbml0aWFs
IHN0cmF3IG1hbiBwcm9wb3NhbCBmb3IgZGlzY3Vzc2lvbnMgYnkgdGhlIGxhcmdlciB3b3JraW5n
IGdyb3VwLg0KDQpJZiBhbnlvbmUgaXMgdmlvbGVudGx5IG9wcG9zZWQgdG8gdGhpcyBwbGFuLCBw
bGVhc2Ugc2F5IHNvIHJpZ2h0IG5vdy4gU2lsZW5jZSBjb3VudHMgYXMgYWNjZXB0YW5jZSBpbiB0
aGlzIGNhc2UuIFRvIGxlYXJuIGFib3V0IHRoZSBjb25jZXB0DQpvZiBkZXNpZ24gdGVhbXMgaW4g
dGhlIElFVEYgcmVhZCBSRkMgMjQxOCAoc2VjdGlvbiA2LjUpLg0KDQoNCkNoZWVycywNCk1vcnRl
emEgJiBMZWlmDQo=

--_000_34966E97BE8AD64EAE9D3D6E4DEE36F21ED50977szxeml525mbxchi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: bre=
ak-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I would li=
ke to join.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Kind Regar=
ds<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Kepeng<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:SimSu=
n">=B7=A2=BC=FE=C8=CB<span lang=3D"EN-US">:</span></span></b><span lang=3D"=
EN-US" style=3D"font-size:10.0pt;font-family:SimSun"> scim-bounces@ietf.org=
 [mailto:scim-bounces@ietf.org]
</span><b><span style=3D"font-size:10.0pt;font-family:SimSun">=B4=FA=B1=ED =
</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:SimSu=
n">Morteza Ansari (moransar)<br>
</span><b><span style=3D"font-size:10.0pt;font-family:SimSun">=B7=A2=CB=CD=
=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:SimSun"> 2012</span><span style=3D"font=
-size:10.0pt;font-family:SimSun">=C4=EA<span lang=3D"EN-US">10</span>=D4=C2=
<span lang=3D"EN-US">11</span>=C8=D5<span lang=3D"EN-US">
 4:34<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> scim@ietf.org<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> [scim] Proposal to create a design team<o:p></o:p></span></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Hi Folks,<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">To expedite g=
etting to a straw man proposal, we propose the creation of a design team to=
 get the work rolling. We have a few volunteers already signed
 up:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Trey Drake, K=
elly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">If anyone els=
e is interested in joining the design team and contributing please let us k=
now. The expectation is that the design team will put a concentrated
 effort into creating the initial straw man proposal for discussions by the=
 larger working group.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</=
o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;">If anyone is violently opposed to this pl=
an, please say so right now.&nbsp;<span class=3D"apple-style-span">Silence =
counts as acceptance in this case. To learn about the concept</span></span>=
<span lang=3D"EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;">of design teams in the IETF read RFC 2418=
 (section 6.5).</span><span lang=3D"EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Cheers,<o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Morteza &amp;=
 Leif<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_34966E97BE8AD64EAE9D3D6E4DEE36F21ED50977szxeml525mbxchi_--

From charliemortimore@gmail.com  Wed Oct 10 19:44:04 2012
Return-Path: <charliemortimore@gmail.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 EDE3121F8545 for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 19:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 ruD3+gzTXBzW for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 19:44:03 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE2321F84F2 for <scim@ietf.org>; Wed, 10 Oct 2012 19:44:03 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so1358253pbb.31 for <scim@ietf.org>; Wed, 10 Oct 2012 19:44:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=5RhH3DNjKjYDZmriXP79kLYzU0snW0y6c4Z2XDKsbV4=; b=BK+fvyOeTcOdDfGnzWLTKaKEnJrV49X5JQJMw8onWVqSJXJ11PJY1pBY4im1fMP2np WRyS0QT8fsNEZ1Q0DcPtVp5P3oKNsV8EkK7RurVhrAxBcjSwq9GJzKuAeBxAhZ63Ekdg 1eONt7VO5nOxL/bCLa0P1aynitA3r5Ewue8FSy6nEoBgpv/bP/TmZ3T9z5r3GSLiJFXj FYFNJEW3kLq40kMLGEqgNrdfdMWEDzSkMyaKdpcv2Hnk3ZhYS3qha2Ykhck4IIzmYIIp 0QF2xxxt6DeeY+e5i7kQCWybJsy1YiA/auzKrm3jlSSdXxgTF7rLWFA22UAb43gSaVXI mKPg==
Received: by 10.68.213.138 with SMTP id ns10mr79005799pbc.157.1349923443226; Wed, 10 Oct 2012 19:44:03 -0700 (PDT)
Received: from [10.202.20.146] (mobile-198-228-223-059.mycingular.net. [198.228.223.59]) by mx.google.com with ESMTPS id yi9sm1595321pbc.39.2012.10.10.19.44.01 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 10 Oct 2012 19:44:02 -0700 (PDT)
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
In-Reply-To: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-0E70919F-3A70-47FD-ACA7-30D33A22DF10
Message-Id: <6A420BCF-7B21-4E2A-8042-9FB258AAAFBD@gmail.com>
X-Mailer: iPhone Mail (9B179)
From: Charliemortimore <charliemortimore@gmail.com>
Date: Wed, 10 Oct 2012 19:43:57 -0700
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
Cc: "scim@ietf.org" <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, 11 Oct 2012 02:44:04 -0000

--Apple-Mail-0E70919F-3A70-47FD-ACA7-30D33A22DF10
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I'm in.

- cmort

On Oct 10, 2012, at 1:34 PM, "Morteza Ansari (moransar)" <moransar@cisco.com=
> wrote:

> Hi Folks,
>=20
> To expedite getting to a straw man proposal, we propose the creation of a d=
esign team to get the work rolling. We have a few volunteers already signed u=
p:
>=20
> Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda
>=20
> If anyone else is interested in joining the design team and contributing p=
lease let us know. The expectation is that the design team will put a concen=
trated effort into creating the initial straw man proposal for discussions b=
y the larger working group.
>=20
> If anyone is violently opposed to this plan, please say so right now. Sile=
nce counts as acceptance in this case. To  learn about the concept
> of design teams in the IETF read RFC 2418 (section 6.5).
>=20
>=20
> Cheers,
> Morteza & Leif
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim

--Apple-Mail-0E70919F-3A70-47FD-ACA7-30D33A22DF10
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor="#FFFFFF"><div>I'm in.<br><br>- cmort</div><div><br>On Oct 10, 2012, at 1:34 PM, "Morteza Ansari (moransar)" &lt;<a href="mailto:moransar@cisco.com">moransar@cisco.com</a>&gt; wrote:<br><br></div><div></div><blockquote type="cite"><div>

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">


<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Hi Folks,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
To expedite getting to a straw man proposal, we propose the creation of a design team to get the work rolling. We have a few volunteers already signed up:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
If anyone else is interested in joining the design team and contributing please let us know. The expectation is that the design team will put a concentrated effort into creating the initial straw man proposal for discussions by the larger working group.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div>
<div><font class="Apple-style-span" face="Calibri,sans-serif">If anyone is violently opposed to this plan, please say so right now.&nbsp;</font><span class="Apple-style-span" style="font-family: Calibri, sans-serif; ">Silence counts as acceptance in this case. To
 learn about the concept</span></div>
<div><font class="Apple-style-span" face="Calibri,sans-serif">of design teams in the IETF read RFC 2418 (section 6.5).</font></div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Cheers,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Morteza &amp; Leif</div>
</div>


</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>scim mailing list</span><br><span><a href="mailto:scim@ietf.org">scim@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a></span><br></div></blockquote></body></html>
--Apple-Mail-0E70919F-3A70-47FD-ACA7-30D33A22DF10--

From samuel@erdtman.se  Wed Oct 10 23:12:18 2012
Return-Path: <samuel@erdtman.se>
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 E459E21F8623 for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 23:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.081
X-Spam-Level: 
X-Spam-Status: No, score=-3.081 tagged_above=-999 required=5 tests=[AWL=-0.103, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 6m96UYBWAdUW for <scim@ietfa.amsl.com>; Wed, 10 Oct 2012 23:12:18 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C987A21F8622 for <scim@ietf.org>; Wed, 10 Oct 2012 23:12:17 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so1925919vcb.31 for <scim@ietf.org>; Wed, 10 Oct 2012 23:12:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=lVVm8x/GXW0ohBRxxK7dRh8EGLv8HGaKH7DAExROpH4=; b=dlFY6HB8qIQm+vg3cK5kVr+7llCA/e3VFoWA3ytJSY+1XyKdAMfor9MRwiCDWTPrEi I4+3HtM1GtrrTs0wA1k4qTFD6wYo10pkRnRE4iPS3oeRdkQPYaL2VrIGwG712cnArj/c xWXxqjrsf17brmZGlitAIec6obfMyvuK4jKVd5C120jd4cQSHK3wvyUR09zGOHujg8i1 eW6RhDb8x6jyeBwKAoWYUrTqRC2O4Nu+o/veFVrAShuyN21Vid23XPI8k2P0/rCJ/7rF tuAHnpyQBhJwtHFfTKR3AlI4gJ3SpbE19x+Uk+aRs9Vn2MDBaCGGFzJo1fphUKQhrkiv 6+2g==
MIME-Version: 1.0
Received: by 10.52.64.166 with SMTP id p6mr1630811vds.9.1349935936678; Wed, 10 Oct 2012 23:12:16 -0700 (PDT)
Received: by 10.220.201.2 with HTTP; Wed, 10 Oct 2012 23:12:16 -0700 (PDT)
In-Reply-To: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Date: Thu, 11 Oct 2012 08:12:16 +0200
Message-ID: <CAF2hCbaPZS0NgQSHucDsUHvuTLbDBOcA16=VsrfZYtvdtW74GQ@mail.gmail.com>
From: Samuel Erdtman <samuel@erdtman.se>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQn7NBD52loPToBekwtMFffVanIo9VyTCwBYHquYXnF33qw4bjkEdt4/4wh5dEpSxS1fgfAf
Cc: "scim@ietf.org" <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, 11 Oct 2012 06:12:19 -0000

I'm in.

//Samuel

On Wed, Oct 10, 2012 at 10:34 PM, Morteza Ansari (moransar)
<moransar@cisco.com> wrote:
> Hi Folks,
>
> To expedite getting to a straw man proposal, we propose the creation of a
> design team to get the work rolling. We have a few volunteers already signed
> up:
>
> Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda
>
> If anyone else is interested in joining the design team and contributing
> please let us know. The expectation is that the design team will put a
> concentrated effort into creating the initial straw man proposal for
> discussions by the larger working group.
>
> If anyone is violently opposed to this plan, please say so right now.
> Silence counts as acceptance in this case. To learn about the concept
> of design teams in the IETF read RFC 2418 (section 6.5).
>
>
> Cheers,
> Morteza & Leif
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>

From hannes.tschofenig@gmx.net  Thu Oct 11 00:02:37 2012
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 D920721F8625 for <scim@ietfa.amsl.com>; Thu, 11 Oct 2012 00:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level: 
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=0.179, 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 fX28XpjN8eGG for <scim@ietfa.amsl.com>; Thu, 11 Oct 2012 00:02:33 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id AD34121F85B4 for <scim@ietf.org>; Thu, 11 Oct 2012 00:02:32 -0700 (PDT)
Received: (qmail invoked by alias); 11 Oct 2012 07:02:31 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.216.191] by mail.gmx.net (mp016) with SMTP; 11 Oct 2012 09:02:31 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+0nr5q0su0Omv7BKs49/x/XHqaedhHSCzknwTiuf LdnmvI1C2UJ1bp
Message-ID: <50766F04.6090901@gmx.net>
Date: Thu, 11 Oct 2012 10:02:28 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
In-Reply-To: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "scim@ietf.org" <scim@ietf.org>, hannes.tschofenig@gmx.net
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, 11 Oct 2012 07:02:38 -0000

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.

Ciao
Hannes

On 10/10/2012 11:34 PM, Morteza Ansari (moransar) wrote:
> Hi Folks,
>
> To expedite getting to a straw man proposal, we propose the creation of
> a design team to get the work rolling. We have a few volunteers already
> signed up:
>
> Trey Drake, Kelly Grizzle, Phil Hunt, Anthony Nadalin, and Melinda
>
> If anyone else is interested in joining the design team and contributing
> please let us know. The expectation is that the design team will put a
> concentrated effort into creating the initial straw man proposal for
> discussions by the larger working group.
>
> If anyone is violently opposed to this plan, please say so right now.
> Silence counts as acceptance in this case. To learn about the concept
> of design teams in the IETF read RFC 2418 (section 6.5).
>
>
> Cheers,
> Morteza & Leif
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>


From leifj@mnt.se  Thu Oct 11 02:31:14 2012
Return-Path: <leifj@mnt.se>
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 DE28E21F86D3 for <scim@ietfa.amsl.com>; Thu, 11 Oct 2012 02:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 EVahq4zIFbeN for <scim@ietfa.amsl.com>; Thu, 11 Oct 2012 02:31:14 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id AF80121F862A for <scim@ietf.org>; Thu, 11 Oct 2012 02:31:12 -0700 (PDT)
Received: from [109.105.104.222] (dhcp87.se-tug.nordu.net [109.105.104.222] (may be forged)) (authenticated bits=0) by backup-server.nordu.net (8.14.5/8.14.3) with ESMTP id q9B9V77S021838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <scim@ietf.org>; Thu, 11 Oct 2012 11:31:10 +0200 (CEST)
Message-ID: <507691DB.1050204@mnt.se>
Date: Thu, 11 Oct 2012 11:31:07 +0200
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: scim@ietf.org
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net>
In-Reply-To: <50766F04.6090901@gmx.net>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 11 Oct 2012 09:31:15 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB2kdcACgkQ8Jx8FtbMZnfjXwCggM0XFmq7H8h+GgYIc26kZhwb
kX0AnA0d3fTZTF/qb0IIwyaOUr1GADX5
=SVXo
-----END PGP SIGNATURE-----

From alan.sill@ttu.edu  Mon Oct 15 11:40:18 2012
Return-Path: <alan.sill@ttu.edu>
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 92B6A21F8882 for <scim@ietfa.amsl.com>; Mon, 15 Oct 2012 11:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.001,  BAYES_00=-2.599, GB_I_INVITATION=-2]
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 DdMWlxfAxXMn for <scim@ietfa.amsl.com>; Mon, 15 Oct 2012 11:40:17 -0700 (PDT)
Received: from eurynome.ttu.edu (eurynome.ttu.edu [129.118.1.241]) by ietfa.amsl.com (Postfix) with ESMTP id 634AF21F888F for <scim@ietf.org>; Mon, 15 Oct 2012 11:40:16 -0700 (PDT)
Received: from empusa01.ttu.edu (129.118.201.4) by mxout2.ttu.edu (129.118.1.79) with Microsoft SMTP Server id 8.3.279.5; Mon, 15 Oct 2012 13:40:16 -0500
Received: from CYCLOPS05.ttu.edu ([169.254.2.58]) by empusa01.ttu.edu ([129.118.201.4]) with mapi id 14.02.0318.004; Mon, 15 Oct 2012 13:40:15 -0500
From: "Sill, Alan" <alan.sill@ttu.edu>
To: "cmwg@dmtf.org" <cmwg@dmtf.org>, "occi-wg@ogf.org members" <occi-wg@ogf.org>, "scim@ietf.org" <scim@ietf.org>
Thread-Topic: NIST SAJACC working group meeting Tuesday, Oct. 16 2012, 1:00-2:00 pm EDT
Thread-Index: AQHNqvpRyJdkfM3z6E2+jf90J+GdbA==
Date: Mon, 15 Oct 2012 18:40:15 +0000
Message-ID: <384D0028F888584EB202C371301DDA7F42C1F2@cyclops05.ttu.edu>
References: <384D0028F888584EB202C371301DDA7F42AA96@cyclops05.ttu.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.118.242.5]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <915F0F28A1F7C24FBAA739F6B7E85C9B@default.ttu.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received-SPF: Pass (eurynome.ttu.edu: domain of alan.sill@ttu.edu designates 129.118.201.4 as permitted sender) receiver=eurynome.ttu.edu; client-ip=129.118.201.4; helo=empusa01.ttu.edu;
X-TechMail-Edge-Route: TTU
Cc: "Sill, Alan" <alan.sill@ttu.edu>
Subject: [scim] Fwd: NIST SAJACC working group meeting Tuesday, Oct. 16 2012, 1:00-2:00 pm EDT
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: Mon, 15 Oct 2012 18:40:18 -0000

For this who have not yet been involved in the work of the NIST SAJACC work=
ing group to define and refine definitions of use cases for cloud computing=
 operations suitable for resting, this would be a good time to pay attentio=
n.  This is a direct effort to define use case scenarios that are relevant =
to current software and standards, even those under development, and to inv=
ite community input into this process.

For those who have been involved up to now, thank you, and this is the time=
 to encourage your colleagues to join tomorrow's meeting and help us make p=
rogress against the task of breaking down recently gathered use case docume=
nts into testable pieces, a la the previous successful round of NIST SAJACC=
 efforts, and to define and refine scenarios from these that are amenable t=
o testing and demonstration of applicability of available standards, softwa=
re and implementations.

The previous round was very successful in this regard.  Source code and doc=
umentation of earlier tests are available on the NIST SAJACC page:

	http://collaborate.nist.gov/twiki-cloud-computing/bin/view/CloudComputing/=
SAJACC

You can join the working group lists for this or any of the NIST working gr=
oups on the NIST CC sign-up page:

	http://www.nist.gov/itl/cloud/workinggroups.cfm

We will most likely NOT post further announcements except on the CC_SAJACC =
list, so please be sure to sign up if you want more information.  We are on=
ly posting this notice and reminder as a one-time invitation and announceme=
nt.  (Apologies for the extra traffic if you have already received this not=
ice; we wanted to get the word out about this phase, and believe this work =
is directly related to the output of your working groups.)

Begin forwarded message:

From: "Sill, Alan" <alan.sill@ttu.edu>
Subject: NIST SAJACC working group meeting Tuesday, Oct. 16 2012, 1:00-2:00=
 pm EDT
Date: October 15, 2012 12:27:15 PM CDT
To: "<cc_sajacc@nist.gov>" <cc_sajacc@nist.gov>
Cc: "Sill, Alan" <alan.sill@ttu.edu>, Eugene Luster <eugene.luster@r2ad.com=
>

This is a reminder of the NIST Cloud Computing "SAJACC" use cases definitio=
n and testing meeting.

Purpose: Ongoing SAJACC use case definition and testing efforts meeting ser=
ies. Review of use cases gathered to date and assignment of use case listin=
g review to grop participants.

Time: Tuesday, Oct. 16, 2012: Conference Call, 1:00PM - 2:00PM EDT (deferre=
d from Oct. 2)

Meeting coordinates:
	=95 Phone: (Toll Free) +1 (855) 834-4888
	=95 Conference ID: 73390239
	=95 Web conference chat room tool: http://webconf.soaphub.org/conf/room/sa=
jacc

Coordinators and contacts:
	=95 Alan Sill, Texas Tech U./OGF, Alan.Sill@ttu.edu or afsill@ogf.org, +1-=
806-834-5940
	=95 Eugene Luster, R2AD, Eugene.Luster@r2ad.com, +1-619-917-6289

Register for SAJACC email list and TWiki access: http://www.nist.gov/itl/cl=
oud/workinggroups.cfm

This meeting will be devoted to assessment of completeness of our use case =
example library gathered to date from this meeting series and from the prev=
ious NIST CC Federal Business Use Cases and Stories Subgroup and to compari=
ng these to the previous SAJACC test use case definitions. Relevant meeting=
 materials have been posted on the meeting link:

  http://collaborate.nist.gov/twiki-cloud-computing/bin/view/CloudComputing=
/SAJACCTeleConf26

Please review these before the meeting.  We will be making progress this me=
eting on assigning review to volunteers from the group and in setting deadl=
ines for revision of the use case scenarios prior to the next step, which w=
ill be to make invitations to demonstrate software and standards applicable=
 to the refined scenarios.

Please try to be prompt.

Alan and Eugene



From alan.sill@ttu.edu  Mon Oct 15 11:48:36 2012
Return-Path: <alan.sill@ttu.edu>
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 D2FBB21F86E2 for <scim@ietfa.amsl.com>; Mon, 15 Oct 2012 11:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 mMgPQz0seETq for <scim@ietfa.amsl.com>; Mon, 15 Oct 2012 11:48:36 -0700 (PDT)
Received: from eurymedon.net.ttu.edu (eurymedon.net.ttu.edu [129.118.1.225]) by ietfa.amsl.com (Postfix) with ESMTP id 30A0621F86D3 for <scim@ietf.org>; Mon, 15 Oct 2012 11:48:36 -0700 (PDT)
Received: from empusa10.ttu.edu (129.118.201.68) by tmrc.ttu.edu (129.118.1.179) with Microsoft SMTP Server id 8.3.279.5; Mon, 15 Oct 2012 13:48:35 -0500
Received: from CYCLOPS05.ttu.edu ([169.254.2.58]) by empusa10.ttu.edu ([129.118.201.68]) with mapi id 14.02.0318.004; Mon, 15 Oct 2012 13:48:34 -0500
From: "Sill, Alan" <alan.sill@ttu.edu>
To: "cmwg@dmtf.org" <cmwg@dmtf.org>, "occi-wg@ogf.org members" <occi-wg@ogf.org>, "scim@ietf.org" <scim@ietf.org>
Thread-Topic: NIST SAJACC working group meeting Tuesday, Oct. 16 2012, 1:00-2:00 pm EDT
Thread-Index: AQHNqvpRyJdkfM3z6E2+jf90J+GdbJe7CTgA
Date: Mon, 15 Oct 2012 18:48:34 +0000
Message-ID: <384D0028F888584EB202C371301DDA7F42C2AF@cyclops05.ttu.edu>
References: <384D0028F888584EB202C371301DDA7F42AA96@cyclops05.ttu.edu> <384D0028F888584EB202C371301DDA7F42C1F2@cyclops05.ttu.edu>
In-Reply-To: <384D0028F888584EB202C371301DDA7F42C1F2@cyclops05.ttu.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.118.242.5]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A17578BC96B65B4C92C0C44BE785FECE@default.ttu.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received-SPF: Pass (eurymedon.net.ttu.edu: domain of alan.sill@ttu.edu designates 129.118.201.68 as permitted sender) receiver=eurymedon.net.ttu.edu; client-ip=129.118.201.68; helo=empusa10.ttu.edu;
X-TechMail-Edge-Route: TTU
Cc: "Sill, Alan" <alan.sill@ttu.edu>
Subject: Re: [scim] NIST SAJACC working group meeting Tuesday, Oct. 16 2012, 1:00-2:00 pm EDT
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: Mon, 15 Oct 2012 18:48:36 -0000

Testing!

Alan

On Oct 15, 2012, at 1:40 PM, "Sill, Alan" <alan.sill@ttu.edu>
 wrote:

> suitable for resting


From leifj@sunet.se  Wed Oct 17 08:38:27 2012
Return-Path: <leifj@sunet.se>
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 C410521F86D8 for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 08:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 6l8q3RLtjrBA for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 08:38:27 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id D7B7E21F86CE for <scim@ietf.org>; Wed, 17 Oct 2012 08:38:26 -0700 (PDT)
Received: from [192.168.49.246] ([80.122.97.74]) (authenticated bits=0) by backup-server.nordu.net (8.14.5/8.14.3) with ESMTP id q9HFcIN1008394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <scim@ietf.org>; Wed, 17 Oct 2012 17:38:24 +0200 (CEST)
Message-ID: <507ED0EA.2030101@sunet.se>
Date: Wed, 17 Oct 2012 17:38:18 +0200
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: scim WG <scim@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [scim] issues and issue-tracker
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: Wed, 17 Oct 2012 15:38:28 -0000

Folks,

The chairs have been asked to clarify the policy around the use
of the issue tracker.

Here it is: If you have identified something which you believe
need to be tracked please send a mail to the list and suggest
that an issue be opened.

We will apply a very permissive policy to those emails and if
you don't get a response, please whack us over the head!

	Leif & Morteza

From phil.hunt@oracle.com  Wed Oct 17 09:21:13 2012
Return-Path: <phil.hunt@oracle.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 BCE8521F85A0 for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 09:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.68
X-Spam-Level: 
X-Spam-Status: No, score=-9.68 tagged_above=-999 required=5 tests=[AWL=-0.570,  BAYES_05=-1.11, RCVD_IN_DNSWL_HI=-8]
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 sVB11SC0pn3n for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 09:21:11 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by ietfa.amsl.com (Postfix) with ESMTP id 160CE21F859C for <scim@ietf.org>; Wed, 17 Oct 2012 09:21:10 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9HGL8be026975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <scim@ietf.org>; Wed, 17 Oct 2012 16:21:09 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9HGL8Ej004130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <scim@ietf.org>; Wed, 17 Oct 2012 16:21:08 GMT
Received: from abhmt114.oracle.com (abhmt114.oracle.com [141.146.116.66]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9HGL8kq027638 for <scim@ietf.org>; Wed, 17 Oct 2012 11:21:08 -0500
Received: from [192.168.1.8] (/24.85.226.208) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 17 Oct 2012 09:21:08 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Oct 2012 09:21:07 -0700
Message-Id: <DBF02EBD-970E-4730-8CBE-86F6224407E3@oracle.com>
To: scim WG <scim@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Subject: [scim] Issue: Resource types in Path
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: Wed, 17 Oct 2012 16:21:13 -0000

Leif,

I would add the issue of putting resource types in URL paths.  What =
object types go in this path if any?  If object types are in path how do =
you query for multiple object types (or any type)?

Phil

@independentid
www.independentid.com
phil.hunt@oracle.com






From phil.hunt@oracle.com  Wed Oct 17 09:23:20 2012
Return-Path: <phil.hunt@oracle.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 E060F21F85A1 for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 09:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.31
X-Spam-Level: 
X-Spam-Status: No, score=-10.31 tagged_above=-999 required=5 tests=[AWL=0.289,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 wXDY3dIPWF3s for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 09:23:20 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by ietfa.amsl.com (Postfix) with ESMTP id DDD1021F859C for <scim@ietf.org>; Wed, 17 Oct 2012 09:23:19 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9HGNH6L003209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <scim@ietf.org>; Wed, 17 Oct 2012 16:23:18 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9HGNGaY018114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <scim@ietf.org>; Wed, 17 Oct 2012 16:23:17 GMT
Received: from abhmt114.oracle.com (abhmt114.oracle.com [141.146.116.66]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9HGNG2T029173 for <scim@ietf.org>; Wed, 17 Oct 2012 11:23:16 -0500
Received: from [192.168.1.8] (/24.85.226.208) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 17 Oct 2012 09:23:16 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Oct 2012 09:23:15 -0700
Message-Id: <30E3D7AE-B341-45B4-BECD-148CF670F17F@oracle.com>
To: scim WG <scim@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Subject: [scim] Issue: Patch Operation
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: Wed, 17 Oct 2012 16:23:21 -0000

Leif,

Another issue is to review the patch function to make it more obvious to =
a person reading the operation. I believe this was raised in Vancouver.

Phil

@independentid
www.independentid.com
phil.hunt@oracle.com






From igor.faynberg@alcatel-lucent.com  Wed Oct 17 09:25:15 2012
Return-Path: <igor.faynberg@alcatel-lucent.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 6AB2321F8665 for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 09:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.099
X-Spam-Level: 
X-Spam-Status: No, score=-9.099 tagged_above=-999 required=5 tests=[AWL=1.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 t+X9OBHc3ALp for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 09:25:14 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id B566921F865F for <scim@ietf.org>; Wed, 17 Oct 2012 09:25:14 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q9HGPDIO008568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <scim@ietf.org>; Wed, 17 Oct 2012 11:25:13 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q9HGPDvc030053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <scim@ietf.org>; Wed, 17 Oct 2012 11:25:13 -0500
Received: from [135.244.41.79] (faynberg.lra.lucent.com [135.244.41.79]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q9HGPCPR028445; Wed, 17 Oct 2012 11:25:12 -0500 (CDT)
Message-ID: <507EDBE8.4090207@alcatel-lucent.com>
Date: Wed, 17 Oct 2012 12:25:12 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: scim@ietf.org
References: <30E3D7AE-B341-45B4-BECD-148CF670F17F@oracle.com>
In-Reply-To: <30E3D7AE-B341-45B4-BECD-148CF670F17F@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [scim] Issue: Patch Operation
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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: Wed, 17 Oct 2012 16:25:15 -0000

+1

Igor

On 10/17/2012 12:23 PM, Phil Hunt wrote:
> Leif,
>
> Another issue is to review the patch function to make it more obvious to a person reading the operation. I believe this was raised in Vancouver.
>
> Phil
>
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
>
>
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim

From melinda.shore@gmail.com  Wed Oct 17 12:04:17 2012
Return-Path: <melinda.shore@gmail.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 4972C21F862A for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 12:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.525
X-Spam-Level: 
X-Spam-Status: No, score=-3.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 SjpR1YfdnM-m for <scim@ietfa.amsl.com>; Wed, 17 Oct 2012 12:04:15 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 32AE521F8639 for <scim@ietf.org>; Wed, 17 Oct 2012 12:04:14 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so7459680pbb.31 for <scim@ietf.org>; Wed, 17 Oct 2012 12:04:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Xts1/mL+ajRX8vQsncNaXAxWa7rCQKLQZOj7RaObCSE=; b=YJP3l9jR8agng2HzKm7qJ8HFUOeeIcJC/cHSsZeEOVNgl7grVxh6J5K1YYacOIVh+n 24nKIgg6DfwZ70QcTXdGixX2CtQCVLGDss8TsQBA0lQhEdzimMZEOQ8EsGZEDc12PZ9f 1PysEx9+0byQyz7FGVKeJQVilBkiV7lMPfFwKCDIU+Lc+oL0fzhHq/jEoAnEQFZuO9Uk bs4MN6IkryFc0lPJPTRmsCAGM5qy8wSYS0Evb82orvR5AylXsamhUTbWho4yMICp7hlb T8BjDZUfb1nBSs6nkckS6vZBnYvKaf/zq2BJ1zHQbaIkmSOgd9NQVqC5Z2qVEgpPRbLg b1+g==
Received: by 10.68.235.71 with SMTP id uk7mr59435804pbc.10.1350500651346; Wed, 17 Oct 2012 12:04:11 -0700 (PDT)
Received: from spandex.local (66-230-86-185-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.185]) by mx.google.com with ESMTPS id sa2sm12898568pbc.4.2012.10.17.12.04.08 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Oct 2012 12:04:09 -0700 (PDT)
Message-ID: <507F0127.1010500@gmail.com>
Date: Wed, 17 Oct 2012 11:04:07 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Phil Hunt <phil.hunt@oracle.com>
References: <30E3D7AE-B341-45B4-BECD-148CF670F17F@oracle.com>
In-Reply-To: <30E3D7AE-B341-45B4-BECD-148CF670F17F@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: scim WG <scim@ietf.org>
Subject: Re: [scim] Issue: Patch Operation
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: Wed, 17 Oct 2012 19:04:17 -0000

I've added this and the issue concerning putting resource types
in URL paths to the issue tracker.  For those who aren't aware of
it, we've got an issue tracker at
http://trac.tools.ietf.org/wg/scim/trac/report/1.
Please have a look.

Thanks,

Melinda

From lear@cisco.com  Thu Oct 18 08:32:38 2012
Return-Path: <lear@cisco.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 7D78721F8766 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 08:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.412
X-Spam-Level: 
X-Spam-Status: No, score=-110.412 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 MLipIvKOP4Ab for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 08:32:37 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 8210F21F8751 for <scim@ietf.org>; Thu, 18 Oct 2012 08:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4370; q=dns/txt; s=iport; t=1350574357; x=1351783957; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=Zb7RQThRXhiTFSNWqvVumxIETTcUiivQ3ksA7IhdIIo=; b=aq+fCS0EE4lsg+UcsO74EpTiPXpWSIHj3V/lZ/O+ilzkq4y+Oi5Yt+Pn /0e+OmnG2I6lW3l3WEvm/24u2zmwlBIMSHbQ1Hs+wycPVjeIMAWay8l+O pp2FgpzDhj3fEN1b7tTYZ0ue9olIss3hQeIBAUdy16dbVSM+U64xZJxK/ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIFACUggFCQ/khR/2dsb2JhbABFhhKFX7RQgQiCIAEBAQMBAQEBDwEQSwoBBQsLBBQJFgsCAgkDAgECARUwBg0BBQIBAR6HXAYLnFuNIZMci1iFMIESA5VrgRWNNIFrgnE
X-IronPort-AV: E=Sophos;i="4.80,608,1344211200"; d="scan'208,217";a="8909929"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 18 Oct 2012 15:32:36 +0000
Received: from dhcp-10-55-91-86.cisco.com (dhcp-10-55-91-86.cisco.com [10.55.91.86]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q9IFWZgI001365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Oct 2012 15:32:36 GMT
Message-ID: <50802113.4040805@cisco.com>
Date: Thu, 18 Oct 2012 17:32:35 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Leif Johansson <leifj@mnt.se>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se>
In-Reply-To: <507691DB.1050204@mnt.se>
X-Enigmail-Version: 1.4.5
Content-Type: multipart/alternative; boundary="------------000109050100030801080400"
Cc: 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:32:38 -0000

This is a multi-part message in MIME format.
--------------000109050100030801080400
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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
>
>



--------------000109050100030801080400
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Leif, Morteza,<br>
    <br>
    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:<br>
    <ul>
      <li>What work are they supposed to do?  What issues are they
        supposed to address?</li>
    </ul>
    <p>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</p>
    <p>Now to answer my question in part, there is this dangling
      reference to ServiceProviderConfigs.  Is that needed or should it
      be removed?<br>
    </p>
    <p>I guess what I'm asking for is just a bit more scope, please.<br>
    </p>
    <p>Eliot<br>
    </p>
    <br>
    On 10/11/12 11:31 AM, Leif Johansson wrote:<br>
    <blockquote type="cite">On 10/11/2012 09:02 AM, Hannes Tschofenig
      wrote:<br>
      &gt; Hi chairs,<br>
      <br>
      &gt; Are we talking about this document: <br>
      &gt; <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-scim-api/">http://datatracker.ietf.org/doc/draft-ietf-scim-api/</a><br>
      <br>
      &gt; Looks like a strawman proposal to me already right now.<br>
      <br>
      We are talking about a strawman for the next major revision of<br>
      that document and the schema document.<br>
      <br>
      It is great to see so many are willing to participate. Please<br>
      note that participation in a design-team requires active<br>
      participation and time comittment.<br>
      <br>
          Best R<br>
          Leif<br>
      <br>
    </blockquote>
    <span style="white-space: pre;">&gt;
      _______________________________________________<br>
      &gt; scim mailing list<br>
      &gt; <a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a><br>
      &gt; <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a><br>
      &gt;<br>
      &gt;</span><br>
    <br>
    <br>
  </body>
</html>

--------------000109050100030801080400--

From stpeter@stpeter.im  Thu Oct 18 08:34:19 2012
Return-Path: <stpeter@stpeter.im>
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 4CFA121F8744 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 08:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 EKfwYbK-tEKj for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 08:34:18 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 709A621F8742 for <scim@ietf.org>; Thu, 18 Oct 2012 08:34:18 -0700 (PDT)
Received: from [64.101.72.58] (unknown [64.101.72.58]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id ACEAF40062; Thu, 18 Oct 2012 09:36:58 -0600 (MDT)
Message-ID: <5080217D.7010703@stpeter.im>
Date: Thu, 18 Oct 2012 09:34:21 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com>
In-Reply-To: <50802113.4040805@cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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:34:19 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/18/12 9: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.

And given that half of the semi-active WG participants seem to have
volunteered to be on the design team, we might consider just doing the
work in the WG as a whole. :-)

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCAIX0ACgkQNL8k5A2w/vyvTgCgzjkCMuFsZ3sxUYQGpvcSoJ0S
vdcAnA9ym3jjESmIFUEAuw3WSd3qffTZ
=QhVh
-----END PGP SIGNATURE-----

From hannes.tschofenig@gmx.net  Thu Oct 18 08:54:03 2012
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

----_com.android.email_899299193620332
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SSBoYXZlIHRvIGFncmVlIHdpdGggRWxpb3QuIAoKQSBzdG9yeSBmcm9tIG15IGV4cGVyaWVuY2Ug
aW4gRUNSSVQuIFdoZW4gd2Ugc3RhcnRlZCB0aGUgd29yayBvbiB0aGUgbWFpbiBhcmNoaXRlY3R1
cmUgZG9jdW1lbnQgTWFyYyBhbmQgSSBkZWNpZGVkIHRvIGRvIHRoYXQgd29yayBhcyBwYXJ0IG9m
IGEgZGVzaWduIHRlYW0uIFNpbmNlIHRoZSB3b3JrIHdhcyBzbyBjZW50cmFsIHRvIHRoZSBncm91
cCBpdCB0dXJucyBvdXQgdGhhdCBldmVyeW9uZSBpbiB0aGUgZ3JvdXAgd2FudGVkIHRvIGJlIHBh
cnQgb2YgdGhlIGRlc2lnbiB0ZWFtLiBUaGUgb25seSBiZW5lZml0IGluIGhhdmluZyBhIGRlc2ln
biB0aGVtIChvbmNlIHlvdSBhY2NlcHQgZXZlcnlvbmUsIHdoaWNoIGlzIHdoYXQgd2UgZGlkKSB3
YXMgdGhhdCB3ZSBjb3VsZCBzY2hlZHVsZSBjb25mZXJlbmNlIGNhbGxzLgoKRm9yIHRoZSBTQ0lN
IGRlc2lnbiB0ZWFtIEkgd2FzIHdvbmRlcmluZyB3aGV0aGVyIEkgc2hvdWxkIHJhaXNlIG15IGhh
bmQgYXMgd2VsbCBpbiBvcmRlciB0byBnZXQgdG8ga25vdyB3aGF0IHdvcmsgaXMgZ29pbmcgb24g
aW4gU0NJTSBvbiB0aGUgcHJvdG9jb2wuIE5vdCBiZWluZyBwYXJ0IG9mIHRoZSBkZXNpZ24gdGVh
bSBlc3NlbnRpYWxseSBtZWFucyB0aGF0IHlvdSBhcmUgY3V0IG9mZiBmcm9tIHRoZSBpbmZvcm1h
dGlvbiBmbG93LgoKR2l2ZW4gdGhhdCB0aGUgZ3JvdXAgaGFzIG11Y2ggbW9yZSBhbHJlYWR5IHRo
YW4gYSBwcm90b2NvbCBzcGVjaWZpY2F0aW9uIGJ1dCBhbHJlYWR5IGFuIGludGVyb3BlcmFiaWxp
dHkgdGVzdCBzaXRlIGFuZCB2YXJpb3VzIGludGVyb3BlcmFibGUgaW1wbGVtZW50YXRpb25zIEkg
d29uZGVyIHdoZXRoZXIgdGhlIGRlc2lnbiB0ZWFtIGlkZWEgaXNuJ3QgZ29pbmcgdG8gZGVsYXkg
dGhlIHByb2dyZXNzLgoKU2VudCBmcm9tIG15IEFTVVMgUGFkCgpFbGlvdCBMZWFyIDxsZWFyQGNp
c2NvLmNvbT4gd3JvdGU6Cgo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18KPnNjaW0gbWFpbGluZyBsaXN0Cj5zY2ltQGlldGYub3JnCj5odHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NjaW0K
----_com.android.email_899299193620332
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

SSBoYXZlIHRvIGFncmVlIHdpdGggRWxpb3QuIDxicj48YnI+QSBzdG9yeSBmcm9tIG15IGV4cGVy
aWVuY2UgaW4gRUNSSVQuIFdoZW4gd2Ugc3RhcnRlZCB0aGUgd29yayBvbiB0aGUgbWFpbiBhcmNo
aXRlY3R1cmUgZG9jdW1lbnQgTWFyYyBhbmQgSSBkZWNpZGVkIHRvIGRvIHRoYXQgd29yayBhcyBw
YXJ0IG9mIGEgZGVzaWduIHRlYW0uIFNpbmNlIHRoZSB3b3JrIHdhcyBzbyBjZW50cmFsIHRvIHRo
ZSBncm91cCBpdCB0dXJucyBvdXQgdGhhdCBldmVyeW9uZSBpbiB0aGUgZ3JvdXAgd2FudGVkIHRv
IGJlIHBhcnQgb2YgdGhlIGRlc2lnbiB0ZWFtLiBUaGUgb25seSBiZW5lZml0IGluIGhhdmluZyBh
IGRlc2lnbiB0aGVtIChvbmNlIHlvdSBhY2NlcHQgZXZlcnlvbmUsIHdoaWNoIGlzIHdoYXQgd2Ug
ZGlkKSB3YXMgdGhhdCB3ZSBjb3VsZCBzY2hlZHVsZSBjb25mZXJlbmNlIGNhbGxzLjxicj48YnI+
Rm9yIHRoZSBTQ0lNIGRlc2lnbiB0ZWFtIEkgd2FzIHdvbmRlcmluZyB3aGV0aGVyIEkgc2hvdWxk
IHJhaXNlIG15IGhhbmQgYXMgd2VsbCBpbiBvcmRlciB0byBnZXQgdG8ga25vdyB3aGF0IHdvcmsg
aXMgZ29pbmcgb24gaW4gU0NJTSBvbiB0aGUgcHJvdG9jb2wuIE5vdCBiZWluZyBwYXJ0IG9mIHRo
ZSBkZXNpZ24gdGVhbSBlc3NlbnRpYWxseSBtZWFucyB0aGF0IHlvdSBhcmUgY3V0IG9mZiBmcm9t
IHRoZSBpbmZvcm1hdGlvbiBmbG93Ljxicj48YnI+R2l2ZW4gdGhhdCB0aGUgZ3JvdXAgaGFzIG11
Y2ggbW9yZSBhbHJlYWR5IHRoYW4gYSBwcm90b2NvbCBzcGVjaWZpY2F0aW9uIGJ1dCBhbHJlYWR5
IGFuIGludGVyb3BlcmFiaWxpdHkgdGVzdCBzaXRlIGFuZCB2YXJpb3VzIGludGVyb3BlcmFibGUg
aW1wbGVtZW50YXRpb25zIEkgd29uZGVyIHdoZXRoZXIgdGhlIGRlc2lnbiB0ZWFtIGlkZWEgaXNu
JiMzOTt0IGdvaW5nIHRvIGRlbGF5IHRoZSBwcm9ncmVzcy48YnI+PGJyPlNlbnQgZnJvbSBteSBB
U1VTIFBhZDxicj48YnI+RWxpb3QgTGVhciAmbHQ7bGVhckBjaXNjby5jb20mZ3Q7IHdyb3RlOjxi
cj48YnI+DQogICAgTGVpZiwgTW9ydGV6YSw8YnI+DQogICAgPGJyPg0KICAgIEknbSBzb3JyeSB0
byBiZSBhIHN0aWNrIGluIHRoZSBtdWQsIGJ1dCBJIGRvbid0IHVuZGVyc3RhbmQgdGhlDQogICAg
b2JqZWN0aXZlIG9mIHRoaXMgZGVzaWduIHRlYW0uwqAgTGV0J3Mgc3RhcnQgd2l0aCBhbiBlYXN5
IHF1ZXN0aW9uOjxicj4NCiAgICA8dWw+DQogICAgICA8bGk+V2hhdCB3b3JrIGFyZSB0aGV5IHN1
cHBvc2VkIHRvIGRvP8KgIFdoYXQgaXNzdWVzIGFyZSB0aGV5DQogICAgICAgIHN1cHBvc2VkIHRv
IGFkZHJlc3M/PC9saT4NCiAgICA8L3VsPg0KICAgIDxwPlB1dCBhbm90aGVyIHdheSwgSSB3YXMg
bm90IG9mIHRoZSB1bmRlcnN0YW5kaW5nIHRoYXQgd2hhdCBpcw0KICAgICAgcG9zdGVkIGlzIGEg
c3RyYXdtYW4sIGJ1dCBiYXNlZCBvbiBydW5uaW5nIGNvZGUuwqAgSWYgdGhlcmUgaXMNCiAgICAg
IHJ1bm5pbmcgY29kZSwgaXQgc2VlbXMgdG8gbWUgdGhhdCB0aGUgb251cyBpcyBvbiB0aG9zZSBp
biB0aGUgV0cNCiAgICAgIHRvIHN0YXRlIGlzc3Vlcy7CoCBUaGVyZSBhcmUgYSBudW1iZXIsIGFz
IEkgdW5kZXJzdGFuZCBpdC7CoCBBDQogICAgICBkZXNpZ24gdGVhbSBpcyBuZWNlc3Nhcnkgd2hl
biBzb21ldGhpbmcgbmVlZHMgdG8gYmUgZGVzaWduZWQuwqANCiAgICAgIFdoYXQgaGVyZSBuZWVk
cyB0byBiZSBkZXNpZ25lZDwvcD4NCiAgICA8cD5Ob3cgdG8gYW5zd2VyIG15IHF1ZXN0aW9uIGlu
IHBhcnQsIHRoZXJlIGlzIHRoaXMgZGFuZ2xpbmcNCiAgICAgIHJlZmVyZW5jZSB0byBTZXJ2aWNl
UHJvdmlkZXJDb25maWdzLsKgIElzIHRoYXQgbmVlZGVkIG9yIHNob3VsZCBpdA0KICAgICAgYmUg
cmVtb3ZlZD88YnI+DQogICAgPC9wPg0KICAgIDxwPkkgZ3Vlc3Mgd2hhdCBJJ20gYXNraW5nIGZv
ciBpcyBqdXN0IGEgYml0IG1vcmUgc2NvcGUsIHBsZWFzZS48YnI+DQogICAgPC9wPg0KICAgIDxw
PkVsaW90PGJyPg0KICAgIDwvcD4NCiAgICA8YnI+DQogICAgT24gMTAvMTEvMTIgMTE6MzEgQU0s
IExlaWYgSm9oYW5zc29uIHdyb3RlOjxicj4NCiAgICA8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj5P
biAxMC8xMS8yMDEyIDA5OjAyIEFNLCBIYW5uZXMgVHNjaG9mZW5pZw0KICAgICAgd3JvdGU6PGJy
Pg0KICAgICAgJmd0OyBIaSBjaGFpcnMsPGJyPg0KICAgICAgPGJyPg0KICAgICAgJmd0OyBBcmUg
d2UgdGFsa2luZyBhYm91dCB0aGlzIGRvY3VtZW50OiA8YnI+DQogICAgICAmZ3Q7IDxhIGNsYXNz
PSJtb3otdHh0LWxpbmstZnJlZXRleHQiIGhyZWY9Imh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtaWV0Zi1zY2ltLWFwaS8iPmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtaWV0Zi1zY2ltLWFwaS88L2E+PGJyPg0KICAgICAgPGJyPg0KICAgICAgJmd0OyBM
b29rcyBsaWtlIGEgc3RyYXdtYW4gcHJvcG9zYWwgdG8gbWUgYWxyZWFkeSByaWdodCBub3cuPGJy
Pg0KICAgICAgPGJyPg0KICAgICAgV2UgYXJlIHRhbGtpbmcgYWJvdXQgYSBzdHJhd21hbiBmb3Ig
dGhlIG5leHQgbWFqb3IgcmV2aXNpb24gb2Y8YnI+DQogICAgICB0aGF0IGRvY3VtZW50IGFuZCB0
aGUgc2NoZW1hIGRvY3VtZW50Ljxicj4NCiAgICAgIDxicj4NCiAgICAgIEl0IGlzIGdyZWF0IHRv
IHNlZSBzbyBtYW55IGFyZSB3aWxsaW5nIHRvIHBhcnRpY2lwYXRlLiBQbGVhc2U8YnI+DQogICAg
ICBub3RlIHRoYXQgcGFydGljaXBhdGlvbiBpbiBhIGRlc2lnbi10ZWFtIHJlcXVpcmVzIGFjdGl2
ZTxicj4NCiAgICAgIHBhcnRpY2lwYXRpb24gYW5kIHRpbWUgY29taXR0bWVudC48YnI+DQogICAg
ICA8YnI+DQogICAgICDCoMKgIMKgQmVzdCBSPGJyPg0KICAgICAgwqDCoCDCoExlaWY8YnI+DQog
ICAgICA8YnI+DQogICAgPC9ibG9ja3F1b3RlPg0KICAgIDxzcGFuIHN0eWxlPSJ3aGl0ZS1zcGFj
ZTogcHJlOyI+Jmd0Ow0KICAgICAgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX188YnI+DQogICAgICAmZ3Q7IHNjaW0gbWFpbGluZyBsaXN0PGJyPg0KICAgICAg
Jmd0OyA8YSBjbGFzcz0ibW96LXR4dC1saW5rLWFiYnJldmlhdGVkIiBocmVmPSJtYWlsdG86c2Np
bUBpZXRmLm9yZyI+c2NpbUBpZXRmLm9yZzwvYT48YnI+DQogICAgICAmZ3Q7IDxhIGNsYXNzPSJt
b3otdHh0LWxpbmstZnJlZXRleHQiIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vc2NpbSI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zY2lt
PC9hPjxicj4NCiAgICAgICZndDs8YnI+DQogICAgICAmZ3Q7PC9zcGFuPjxicj4NCiAgICA8YnI+
DQogICAgPGJyPg0KICA=
----_com.android.email_899299193620332--


From melinda.shore@gmail.com  Thu Oct 18 09:37:05 2012
Return-Path: <melinda.shore@gmail.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 4304521F86FE for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 09:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.528
X-Spam-Level: 
X-Spam-Status: No, score=-3.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 946LcGU8To2m for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 09:37:04 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id AE26221F86EC for <scim@ietf.org>; Thu, 18 Oct 2012 09:37:04 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so8424434pad.31 for <scim@ietf.org>; Thu, 18 Oct 2012 09:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=b7201AO2PkQ5+CdjO14reAgzy2AaBtQs5qrwSHmO5Q0=; b=D3Tfue9Cgm95+CCBiMuQ3HnG29HMlHQjBC7miN/oWfDjwZBbSMmW66/AYm7PAxDdSp CfzOTSB69lZ3kE+o6TpjvSq1HxkLoWxB6VnS/q2RmgXH4MUwEm4q9KWsvnodJV6ge6we CHDAPevQPKpToV2GjAw220OzPAQmioAbddfdS0SFpO5HYGLycnReFMtsrTsQK9o06Oo9 gToU0wI4QOcG9Iy9KdZGaL70t1ihrhZmK+rUSe1OXzKEuvKKhnP+QvPLh72ptrlBtxLo fdilZM7oCcbYwxSBl7tGsZUEPD4oqGdJvUr4qSFD8h0LJQZj/psUkr9dVp52aODOT4PL LHyg==
Received: by 10.68.132.165 with SMTP id ov5mr66878859pbb.105.1350578224491; Thu, 18 Oct 2012 09:37:04 -0700 (PDT)
Received: from spandex.local (66-230-86-185-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.185]) by mx.google.com with ESMTPS id sz4sm14473507pbc.22.2012.10.18.09.37.02 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 18 Oct 2012 09:37:03 -0700 (PDT)
Message-ID: <5080302D.5060708@gmail.com>
Date: Thu, 18 Oct 2012 08:37:01 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080217D.7010703@stpeter.im>
In-Reply-To: <5080217D.7010703@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Leif Johansson <leifj@mnt.se>, Eliot Lear <lear@cisco.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 16:37:05 -0000

On 10/18/12 7:34 AM, Peter Saint-Andre wrote:
> And given that half of the semi-active WG participants seem to have
> volunteered to be on the design team, we might consider just doing the
> work in the WG as a whole. :-)

I'd be a little surprised if half the volunteers for the design team
actually do end up writing text, etc.  There's a general problem of how
to progress work in the IETF, since it seems like we're getting less
done between meetings and seem to have morphed into a meeting-driven
organization.  I really don't like interims, since (among
other things) I think reliance on them tends to exclude smaller
companies with crappy travel budgets from the process, and that's not
okay.  Design teams with regular calls can achieve much the same thing
as an interim meeting, and as long as the process is transparent
there's little risk of taking the work in a direction the group would
otherwise not support.  I agree there needs to be clear - and
specific - goals, though.

Melinda


From igor.faynberg@alcatel-lucent.com  Thu Oct 18 10:16:49 2012
Return-Path: <igor.faynberg@alcatel-lucent.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 5C2F121F8745 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 10:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.598
X-Spam-Level: 
X-Spam-Status: No, score=-8.598 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 j-uf1VGD4S1X for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 10:16:48 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 890C721F8724 for <scim@ietf.org>; Thu, 18 Oct 2012 10:16:48 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q9IHGlBM002042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <scim@ietf.org>; Thu, 18 Oct 2012 12:16:47 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q9IHGlM4025024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <scim@ietf.org>; Thu, 18 Oct 2012 12:16:47 -0500
Received: from [135.222.232.243] (USMUYN0L055118.mh.lucent.com [135.222.232.243]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q9IHGjB5020807; Thu, 18 Oct 2012 12:16:46 -0500 (CDT)
Message-ID: <5080397D.4020409@alcatel-lucent.com>
Date: Thu, 18 Oct 2012 13:16:45 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: scim@ietf.org
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>	<50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com>
In-Reply-To: <50802113.4040805@cisco.com>
Content-Type: multipart/alternative; boundary="------------030702040904080401070001"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [scim] Proposal to create a design team
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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 17:16:49 -0000

This is a multi-part message in MIME format.
--------------030702040904080401070001
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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

--------------030702040904080401070001
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    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.  <br>
    <br>
      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). <br>
    <br>
     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.<br>
    <br>
    In short, what privileges will the official <i>design team </i>have
    in the process vs. a typical de-facto design team?<br>
    <br>
    Igor<br>
    <br>
    On 10/18/2012 11:32 AM, Eliot Lear wrote:
    <blockquote cite="mid:50802113.4040805@cisco.com" type="cite">
      <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
      Leif, Morteza,<br>
      <br>
      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:<br>
      <ul>
        <li>What work are they supposed to do?  What issues are they
          supposed to address?</li>
      </ul>
      <p>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</p>
      <p>Now to answer my question in part, there is this dangling
        reference to ServiceProviderConfigs.  Is that needed or should
        it be removed?<br>
      </p>
      <p>I guess what I'm asking for is just a bit more scope, please.<br>
      </p>
      <p>Eliot<br>
      </p>
      <br>
      On 10/11/12 11:31 AM, Leif Johansson wrote:<br>
      <blockquote type="cite">On 10/11/2012 09:02 AM, Hannes Tschofenig
        wrote:<br>
        &gt; Hi chairs,<br>
        <br>
        &gt; Are we talking about this document: <br>
        &gt; <a moz-do-not-send="true" class="moz-txt-link-freetext"
          href="http://datatracker.ietf.org/doc/draft-ietf-scim-api/">http://datatracker.ietf.org/doc/draft-ietf-scim-api/</a><br>
        <br>
        &gt; Looks like a strawman proposal to me already right now.<br>
        <br>
        We are talking about a strawman for the next major revision of<br>
        that document and the schema document.<br>
        <br>
        It is great to see so many are willing to participate. Please<br>
        note that participation in a design-team requires active<br>
        participation and time comittment.<br>
        <br>
            Best R<br>
            Leif<br>
        <br>
      </blockquote>
      <span style="white-space: pre;">&gt;<br>
        _______________________________________________<br>
        <br>
        &gt; scim mailing list<br>
        <br>
        &gt; <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
          href="mailto:scim@ietf.org">scim@ietf.org</a><br>
        <br>
        &gt; <a moz-do-not-send="true" class="moz-txt-link-freetext"
          href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a><br>
        <br>
        &gt;<br>
        <br>
        &gt;</span><br>
      <br>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
scim mailing list
<a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a>
</pre>
    </blockquote>
  </body>
</html>

--------------030702040904080401070001--

From igor.faynberg@alcatel-lucent.com  Thu Oct 18 10:17:54 2012
Return-Path: <igor.faynberg@alcatel-lucent.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 06F3221F8752 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 10:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.599
X-Spam-Level: 
X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 V1abcC8gG4Ve for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 10:17:53 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1082D21F8724 for <scim@ietf.org>; Thu, 18 Oct 2012 10:17:45 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q9IHHjXk012016 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <scim@ietf.org>; Thu, 18 Oct 2012 12:17:45 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q9IHHidV021541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <scim@ietf.org>; Thu, 18 Oct 2012 12:17:45 -0500
Received: from [135.222.232.243] (USMUYN0L055118.mh.lucent.com [135.222.232.243]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q9IHHi99021366; Thu, 18 Oct 2012 12:17:44 -0500 (CDT)
Message-ID: <508039B8.4010403@alcatel-lucent.com>
Date: Thu, 18 Oct 2012 13:17:44 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: scim@ietf.org
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>	<50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se>	<50802113.4040805@cisco.com> <5080217D.7010703@stpeter.im>
In-Reply-To: <5080217D.7010703@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [scim] Proposal to create a design team
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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 17:17:54 -0000

Yes!

Igor

On 10/18/2012 11:34 AM, Peter Saint-Andre wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 10/18/12 9: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.
> And given that half of the semi-active WG participants seem to have
> volunteered to be on the design team, we might consider just doing the
> work in the WG as a whole. :-)
>
> Peter
>
> - -- 
> Peter Saint-Andre
> https://stpeter.im/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>
> iEYEARECAAYFAlCAIX0ACgkQNL8k5A2w/vyvTgCgzjkCMuFsZ3sxUYQGpvcSoJ0S
> vdcAnA9ym3jjESmIFUEAuw3WSd3qffTZ
> =QhVh
> -----END PGP SIGNATURE-----
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim

From hannes.tschofenig@gmx.net  Thu Oct 18 10:25:54 2012
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 22AD121F871D for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 10:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.394
X-Spam-Level: 
X-Spam-Status: No, score=-102.394 tagged_above=-999 required=5 tests=[AWL=0.205, 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 wNv-wklfnmvY for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 10:25:53 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 0886A21F8766 for <scim@ietf.org>; Thu, 18 Oct 2012 10:25:52 -0700 (PDT)
Received: (qmail invoked by alias); 18 Oct 2012 17:25:51 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.216.191] by mail.gmx.net (mp027) with SMTP; 18 Oct 2012 19:25:51 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18awuNLShMaWlAt6AI5m+azCD+mmrWD6CqeCzCOIx ptIb0inIt0P2YO
Message-ID: <50803B9B.2030305@gmx.net>
Date: Thu, 18 Oct 2012 20:25:47 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: igor.faynberg@alcatel-lucent.com
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>	<50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080397D.4020409@alcatel-lucent.com>
In-Reply-To: <5080397D.4020409@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "scim@ietf.org" <scim@ietf.org>, hannes.tschofenig@gmx.net
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 17:25:54 -0000

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
>


From phil.hunt@oracle.com  Thu Oct 18 11:23:22 2012
Return-Path: <phil.hunt@oracle.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 40BE721F8504 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 11:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.393
X-Spam-Level: 
X-Spam-Status: No, score=-10.393 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 LhFjO2eqS4HK for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 11:23:20 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by ietfa.amsl.com (Postfix) with ESMTP id AC64C21F8501 for <scim@ietf.org>; Thu, 18 Oct 2012 11:23:20 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9IINGJe023869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Oct 2012 18:23:16 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9IINFF9012889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Oct 2012 18:23:15 GMT
Received: from abhmt111.oracle.com (abhmt111.oracle.com [141.146.116.63]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9IINEY1019768; Thu, 18 Oct 2012 13:23:14 -0500
Received: from [192.168.1.8] (/24.85.226.208) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 18 Oct 2012 11:23:14 -0700
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <50803B9B.2030305@gmx.net>
Date: Thu, 18 Oct 2012 11:23:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF5A19F6-6A4C-45BB-B982-3F1DE2BB0EBB@oracle.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>	<50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080397D.4020409@alcatel-lucent.com> <50803B9B.2030305@gmx.net>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1283)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: igor.faynberg@alcatel-lucent.com, "scim@ietf.org" <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:23:22 -0000

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,
>=20
> 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
>=20
> Ciao
> Hannes
>=20
> 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.
>=20
> 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.
>=20
> 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.
>>=20
>>   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).
>>=20
>>  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.
>>=20
>> In short, what privileges will the official /design team /have in the
>> process vs. a typical de-facto design team?
>>=20
>> Igor
>>=20
>> On 10/18/2012 11:32 AM, Eliot Lear wrote:
>>> Leif, Morteza,
>>>=20
>>> 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:
>>>=20
>>>  * What work are they supposed to do?  What issues are they supposed
>>>    to address?
>>>=20
>>> 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
>>>=20
>>> Now to answer my question in part, there is this dangling reference =
to
>>> ServiceProviderConfigs.  Is that needed or should it be removed?
>>>=20
>>> I guess what I'm asking for is just a bit more scope, please.
>>>=20
>>> Eliot
>>>=20
>>>=20
>>> On 10/11/12 11:31 AM, Leif Johansson wrote:
>>>> On 10/11/2012 09:02 AM, Hannes Tschofenig wrote:
>>>> > Hi chairs,
>>>>=20
>>>> > Are we talking about this document:
>>>> > http://datatracker.ietf.org/doc/draft-ietf-scim-api/
>>>>=20
>>>> > Looks like a strawman proposal to me already right now.
>>>>=20
>>>> We are talking about a strawman for the next major revision of
>>>> that document and the schema document.
>>>>=20
>>>> 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.
>>>>=20
>>>>    Best R
>>>>    Leif
>>>>=20
>>> >
>>> _______________________________________________
>>>=20
>>> > scim mailing list
>>>=20
>>> > scim@ietf.org
>>>=20
>>> > https://www.ietf.org/mailman/listinfo/scim
>>>=20
>>> >
>>>=20
>>> >
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> scim mailing list
>>> scim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/scim
>>=20
>>=20
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim
>>=20
>=20
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim


From hannes.tschofenig@gmx.net  Thu Oct 18 11:49:35 2012
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

V2hpY2ggY29uZmVyZW5jZSBjYWxsIGxhc3QgV2VkbmVzZGF5PyBJIGRpZCBub3Qgc2VlIGEgY29u
ZmVyZW5jZSBjYWxsIGFubm91bmNlbWVudCBvbiB0aGUgbGlzdC4KClNlbnQgZnJvbSBteSBBU1VT
IFBhZAoKUGhpbCBIdW50IDxwaGlsLmh1bnRAb3JhY2xlLmNvbT4gd3JvdGU6Cgo+QWxsIHRoZXNl
IHBvaW50cyBhbmQgbW9yZSB3ZXJlIGRpc2N1c3NlZCBvbiB0aGUgY29uIGNhbGwgbGFzdCBXZWRu
ZXNkYXkuICBUaGUgY2hhaXJzIGRpZCBhIGdyZWF0IGpvYiBhbmQgbW9yZSBpbXBvcnRhbnRseSB0
aGV5IHJlcG9ydGVkIGJhY2sgdG8gdGhlIFdHLgo+Cj5JIGRvbid0IHNlZSBhIHByb2JsZW0gaGVy
ZS4KPgo+UGhpbAo+Cj5AaW5kZXBlbmRlbnRpZAo+d3d3LmluZGVwZW5kZW50aWQuY29tCj5waGls
Lmh1bnRAb3JhY2xlLmNvbQo+Cj4KPgo+Cj4KPk9uIDIwMTItMTAtMTgsIGF0IDEwOjI1IEFNLCBI
YW5uZXMgVHNjaG9mZW5pZyB3cm90ZToKPgo+PiBIaSBJZ29yLAo+PiAKPj4gSSBhbSBub3Qgc3Vy
ZSB3aGF0IHlvdSBtZWFuLiBIZXJlIGlzIHdoYXQgdGhlIElFU0cgc2F5cyBhYm91dCBkZXNpZ24g
dGVhbXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGVzaWduLXRlYW0uaHRt
bAo+PiAKPj4gQ2lhbwo+PiBIYW5uZXMKPj4gCj4+IFBTOiBCdHcsIGFsdGhvdWdoIGh0dHA6Ly93
d3cuaWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGVzaWduLXRlYW0uaHRtbCBzYXlzIHRoYXQKPj4g
Igo+PiBUaGUga2V5IHBvaW50IGhlcmUgaXMgdGhhdCB0aGUgb3V0cHV0IG9mIGEgZGVzaWduIHRl
YW0gaXMgaW5wdXQgdG8gYSB3b3JraW5nIGdyb3VwLCBub3QgYSBmaW5hbCBkb2N1bWVudC4KPj4g
Igo+PiBJIHRoaW5rIGl0IGlzIGEgcmF0aGVyIHRoZW9yZXRpY2FsIHN0YXRlbWVudC4KPj4gCj4+
IEkgaGF2ZSBiZWVuIGludm9sdmVkIGluIGFib3V0IDIwIGRlc2lnbiB0ZWFtcyBhbmQgSSBoYXZl
IG5ldmVyIGhhZCB0aGUgY2FzZSB3aGVyZSB0aGUgb3V0cHV0IG9mIHRoZSBkZXNpZ24gdGVhbSB3
YXMgcmVqZWN0ZWQgYnkgdGhlIGdyb3VwLgo+PiAKPj4gT24gMTAvMTgvMjAxMiAwODoxNiBQTSwg
SWdvciBGYXluYmVyZyB3cm90ZToKPj4+IEkgdGVuZCB0byBzdGljayB0byBFbGlvdC0gdGhlLVN0
aWNrLWluLXRoZS1NdWQncyBwcmluY2lwbGUgb24gdGhhdAo+Pj4gaXNzdWUsIGJ1dCBteSBxdWVz
dGlvbnMgYXJlIGZyb20gdGhlIG90aGVyIGVuZCBvZiBzcGVjdHJ1bS4KPj4+IAo+Pj4gICBUaGUg
cHJlY2VkZW5jZSBpcyBzdWNoIGFzIHRoYXQgYSBkZXNpZ24gdGVhbSBjYW4gYmUgY3JlYXRlZCBl
aXRoZXIgMSkKPj4+IG91dHNpZGUgb2YgYSB3b3JraW5nIGdyb3VwIChhcyB3YXMgdGhlIGNhc2Ug
b2YgIHRoZSBTSU4gZGVzaWduIHRlYW0gMTIKPj4+IHllYXJzIGFnbykgb3IgIDIpIGFzIHBhcnQg
b2YgYSB3b3JraW5nIGdyb3VwICh3aGF0IHdpdGggU0lQIFdHIGRlc2lnbgo+Pj4gdGVhbXMpLgo+
Pj4gCj4+PiAgSSB0YWtlIGl0IHRoYXQgdGhlIHByb3Bvc2FsIGlzIGZvciB0aGUgY2FzZSAyLCBi
dXQgc28gZmFyIHdlIHNlZW0gdG8KPj4+IGhhdmUgYSBmYWlybHkgc21hbGwgZ3JvdXAsIHZpcy1h
LXZpcyB0aGF0IGdpZ2FudGljIFNJUCBXRywgd2hvc2Ugc2hlZXIKPj4+IHNpemUgbmVjZXNzaXRh
dGVkIHBhcmFsbGVsaXNtLiBBbmQgaGVuY2UgcXVlc3Rpb24gaXMgd2h5IGEgc2VwYXJhdGUKPj4+
IHN1YnNldCBncm91cCBpcyBuZWVkZWQgYXQgYWxsLiAgT2YgY291cnNlLCAgcGVvcGxlIG1heSBo
YXZlIHNwZWNpZmljCj4+PiBpbnRlcmVzdHMsIGFuZCBub3RoaW5nIHByZXZlbnRzIHRoZW0gZnJv
bSBmb3JtaW5nIGEgc3BlY2lhbCBpbnRlcmVzdAo+Pj4gZ3JvdXAsIHdyaXRpbmcgZHJhZnRzIGFu
ZCBnZXR0aW5nIHRoZW0gdGhyb3VnaCB0aGUgV0cgcHJvY2Vzcy4KPj4+IAo+Pj4gSW4gc2hvcnQs
IHdoYXQgcHJpdmlsZWdlcyB3aWxsIHRoZSBvZmZpY2lhbCAvZGVzaWduIHRlYW0gL2hhdmUgaW4g
dGhlCj4+PiBwcm9jZXNzIHZzLiBhIHR5cGljYWwgZGUtZmFjdG8gZGVzaWduIHRlYW0/Cj4+PiAK
Pj4+IElnb3IKPj4+IAo+Pj4gT24gMTAvMTgvMjAxMiAxMTozMiBBTSwgRWxpb3QgTGVhciB3cm90
ZToKPj4+PiBMZWlmLCBNb3J0ZXphLAo+Pj4+IAo+Pj4+IEknbSBzb3JyeSB0byBiZSBhIHN0aWNr
IGluIHRoZSBtdWQsIGJ1dCBJIGRvbid0IHVuZGVyc3RhbmQgdGhlCj4+Pj4gb2JqZWN0aXZlIG9m
IHRoaXMgZGVzaWduIHRlYW0uICBMZXQncyBzdGFydCB3aXRoIGFuIGVhc3kgcXVlc3Rpb246Cj4+
Pj4gCj4+Pj4gICogV2hhdCB3b3JrIGFyZSB0aGV5IHN1cHBvc2VkIHRvIGRvPyAgV2hhdCBpc3N1
ZXMgYXJlIHRoZXkgc3VwcG9zZWQKPj4+PiAgICB0byBhZGRyZXNzPwo+Pj4+IAo+Pj4+IFB1dCBh
bm90aGVyIHdheSwgSSB3YXMgbm90IG9mIHRoZSB1bmRlcnN0YW5kaW5nIHRoYXQgd2hhdCBpcyBw
b3N0ZWQgaXMKPj4+PiBhIHN0cmF3bWFuLCBidXQgYmFzZWQgb24gcnVubmluZyBjb2RlLiAgSWYg
dGhlcmUgaXMgcnVubmluZyBjb2RlLCBpdAo+Pj4+IHNlZW1zIHRvIG1lIHRoYXQgdGhlIG9udXMg
aXMgb24gdGhvc2UgaW4gdGhlIFdHIHRvIHN0YXRlIGlzc3Vlcy4KPj4+PiBUaGVyZSBhcmUgYSBu
dW1iZXIsIGFzIEkgdW5kZXJzdGFuZCBpdC4gIEEgZGVzaWduIHRlYW0gaXMgbmVjZXNzYXJ5Cj4+
Pj4gd2hlbiBzb21ldGhpbmcgbmVlZHMgdG8gYmUgZGVzaWduZWQuIFdoYXQgaGVyZSBuZWVkcyB0
byBiZSBkZXNpZ25lZAo+Pj4+IAo+Pj4+IE5vdyB0byBhbnN3ZXIgbXkgcXVlc3Rpb24gaW4gcGFy
dCwgdGhlcmUgaXMgdGhpcyBkYW5nbGluZyByZWZlcmVuY2UgdG8KPj4+PiBTZXJ2aWNlUHJvdmlk
ZXJDb25maWdzLiAgSXMgdGhhdCBuZWVkZWQgb3Igc2hvdWxkIGl0IGJlIHJlbW92ZWQ/Cj4+Pj4g
Cj4+Pj4gSSBndWVzcyB3aGF0IEknbSBhc2tpbmcgZm9yIGlzIGp1c3QgYSBiaXQgbW9yZSBzY29w
ZSwgcGxlYXNlLgo+Pj4+IAo+Pj4+IEVsaW90Cj4+Pj4gCj4+Pj4gCj4+Pj4gT24gMTAvMTEvMTIg
MTE6MzEgQU0sIExlaWYgSm9oYW5zc29uIHdyb3RlOgo+Pj4+PiBPbiAxMC8xMS8yMDEyIDA5OjAy
IEFNLCBIYW5uZXMgVHNjaG9mZW5pZyB3cm90ZToKPj4+Pj4gPiBIaSBjaGFpcnMsCj4+Pj4+IAo+
Pj4+PiA+IEFyZSB3ZSB0YWxraW5nIGFib3V0IHRoaXMgZG9jdW1lbnQ6Cj4+Pj4+ID4gaHR0cDov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXNjaW0tYXBpLwo+Pj4+PiAKPj4+
Pj4gPiBMb29rcyBsaWtlIGEgc3RyYXdtYW4gcHJvcG9zYWwgdG8gbWUgYWxyZWFkeSByaWdodCBu
b3cuCj4+Pj4+IAo+Pj4+PiBXZSBhcmUgdGFsa2luZyBhYm91dCBhIHN0cmF3bWFuIGZvciB0aGUg
bmV4dCBtYWpvciByZXZpc2lvbiBvZgo+Pj4+PiB0aGF0IGRvY3VtZW50IGFuZCB0aGUgc2NoZW1h
IGRvY3VtZW50Lgo+Pj4+PiAKPj4+Pj4gSXQgaXMgZ3JlYXQgdG8gc2VlIHNvIG1hbnkgYXJlIHdp
bGxpbmcgdG8gcGFydGljaXBhdGUuIFBsZWFzZQo+Pj4+PiBub3RlIHRoYXQgcGFydGljaXBhdGlv
biBpbiBhIGRlc2lnbi10ZWFtIHJlcXVpcmVzIGFjdGl2ZQo+Pj4+PiBwYXJ0aWNpcGF0aW9uIGFu
ZCB0aW1lIGNvbWl0dG1lbnQuCj4+Pj4+IAo+Pj4+PiAgICBCZXN0IFIKPj4+Pj4gICAgTGVpZgo+
Pj4+PiAKPj4+PiA+Cj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18KPj4+PiAKPj4+PiA+IHNjaW0gbWFpbGluZyBsaXN0Cj4+Pj4gCj4+Pj4gPiBzY2lt
QGlldGYub3JnCj4+Pj4gCj4+Pj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL3NjaW0KPj4+PiAKPj4+PiA+Cj4+Pj4gCj4+Pj4gPgo+Pj4+IAo+Pj4+IAo+Pj4+IAo+Pj4+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4+Pj4gc2Np
bSBtYWlsaW5nIGxpc3QKPj4+PiBzY2ltQGlldGYub3JnCj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9zY2ltCj4+PiAKPj4+IAo+Pj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPj4+IHNjaW0gbWFpbGluZyBsaXN0Cj4+PiBz
Y2ltQGlldGYub3JnCj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Nj
aW0KPj4+IAo+PiAKPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18KPj4gc2NpbSBtYWlsaW5nIGxpc3QKPj4gc2NpbUBpZXRmLm9yZwo+PiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NjaW0KPgo+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KPnNjaW0gbWFpbGluZyBsaXN0Cj5zY2ltQGlldGYu
b3JnCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NjaW0K


From igor.faynberg@alcatel-lucent.com  Thu Oct 18 13:03:22 2012
Return-Path: <igor.faynberg@alcatel-lucent.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 3655721F84E6 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 13:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.265
X-Spam-Level: 
X-Spam-Status: No, score=-9.265 tagged_above=-999 required=5 tests=[AWL=1.334,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 wzmL-x8khpBh for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 13:03:21 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 4F12921F84D2 for <scim@ietf.org>; Thu, 18 Oct 2012 13:03:21 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q9IK3DXU022736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 18 Oct 2012 15:03:13 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q9IK3D1O001270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 15:03:13 -0500
Received: from [135.222.232.243] (USMUYN0L055118.mh.lucent.com [135.222.232.243]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q9IK3CVi005003; Thu, 18 Oct 2012 15:03:12 -0500 (CDT)
Message-ID: <50806080.80000@alcatel-lucent.com>
Date: Thu, 18 Oct 2012 16:03:12 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com>
In-Reply-To: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: scim@ietf.org, Phil Hunt <phil.hunt@oracle.com>
Subject: Re: [scim] Proposal to create a design team
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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 20:03:22 -0000

Aha!..

On 10/18/2012 2:49 PM, Hannes Tschofenig wrote:
> 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

From sm@resistor.net  Thu Oct 18 13:19:29 2012
Return-Path: <sm@resistor.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 C847D21F8430 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 13:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, 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 3tLSJcKMPhBW for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 13:19:27 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 97D2021F8513 for <scim@ietf.org>; Thu, 18 Oct 2012 13:19:27 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q9IKJKL9022108 for <scim@ietf.org>; Thu, 18 Oct 2012 13:19:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1350591566; bh=beih8yJHwO9lntFkMNQ1zUAbBIBfjOgFSJsbwyc5eYc=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=JbZjWzaqe+13KHL/nK3u0I1Ye7WDY0d95Mm7nSVItzOXtyhWPiwKQtTjh+hoBhpio aA0L9mLocmobCe4fTTqJpH3XUnwXhble/qbfPhQuRdtfJjAKCpWih1PqFw6TDVCmnJ SxyLZ6Kt/qdR4MmYjGhoNqTv0baKcvTIdOYcrB+o=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1350591566; i=@resistor.net; bh=beih8yJHwO9lntFkMNQ1zUAbBIBfjOgFSJsbwyc5eYc=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=euFCX1R7Jn4x+PSoN9XETi8V9R/s7j0LjurKSUL2lCQTRNTfsgN5BiJ7TcjO1z51c 6gTWGSgN6pfjwDnXFaHAVISmmg4do3+dOJT8lR5ZT3bdofYkdj0CjAJ9SS+nahKmeZ cUVBSKf3xkiklhX+ZzwQBXfeyAdFjXfDW8NPbzoU=
Message-Id: <6.2.5.6.2.20121018130937.0b0cd318@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 18 Oct 2012 13:19:00 -0700
To: scim@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com>
References: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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 20:19:29 -0000

At 11:49 18-10-2012, Hannes Tschofenig wrote:
>Which conference call last Wednesday? I did not see a conference 
>call announcement on the list.

The conference call announcement I saw is at 
http://www.ietf.org/mail-archive/web/scim/current/msg00767.html  Was 
that an IETF activity? :-)

Regards,
-sm 


From igor.faynberg@alcatel-lucent.com  Thu Oct 18 13:20:36 2012
Return-Path: <igor.faynberg@alcatel-lucent.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 3993321F8490 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 13:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level: 
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 ZExlOovbPpHa for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 13:20:35 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 659F021F8430 for <scim@ietf.org>; Thu, 18 Oct 2012 13:20:28 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q9IKKMoU007813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 18 Oct 2012 15:20:26 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q9IKKL3q010392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 15:20:22 -0500
Received: from [135.222.232.243] (USMUYN0L055118.mh.lucent.com [135.222.232.243]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q9IKKLa4017215; Thu, 18 Oct 2012 15:20:21 -0500 (CDT)
Message-ID: <50806485.2060900@alcatel-lucent.com>
Date: Thu, 18 Oct 2012 16:20:21 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com>	<50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080397D.4020409@alcatel-lucent.com> <50803B9B.2030305@gmx.net>
In-Reply-To: <50803B9B.2030305@gmx.net>
Content-Type: multipart/alternative; boundary="------------000408070700050305030206"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: "scim@ietf.org" <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
Reply-To: igor.faynberg@alcatel-lucent.com
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 20:20:36 -0000

This is a multi-part message in MIME format.
--------------000408070700050305030206
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Yes, I am quite familiar with RFC 2418. In fact, I was involved in 
creation of one of the earlier design teams.  I hope then that it is 
clear that I am not agitating against the concept. Nor am I really 
agitating for anything, period.

My point was that design teams make sense either when they exist either 
outside of any WG  or in big groups where several of them tackle 
different matters *in parallel*.  If SCIM has only one design team, this 
situation is indistinguishable to me from the one where there is no 
design team at all.

My only question is : If there is a difference, where is it?

Igor

On 10/18/2012 1:25 PM, 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
>
> ...

--------------000408070700050305030206
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Yes, I am quite familiar with RFC 2418. In fact, I was involved in
    creation of one of the earlier design teams.&nbsp; I hope then that it is
    clear that I am not agitating against the concept. Nor am I really
    agitating for anything, period.<br>
    <br>
    My point was that design teams make sense either when they exist
    either outside of any WG&nbsp; or in big groups where several of them
    tackle different matters <b>in parallel</b>.&nbsp; If SCIM has only one
    design team, this situation is indistinguishable to me from the one
    where there is no design team at all. <br>
    <br>
    My only question is : If there is a difference, where is it?<br>
    <br>
    Igor<br>
    <br>
    On 10/18/2012 1:25 PM, Hannes Tschofenig wrote:
    <blockquote cite="mid:50803B9B.2030305@gmx.net" type="cite">Hi Igor,
      <br>
      <br>
      I am not sure what you mean. Here is what the IESG says about
      design teams: <a class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/statement/design-team.html">http://www.ietf.org/iesg/statement/design-team.html</a>
      <br>
      <br>
      ...<br>
    </blockquote>
  </body>
</html>

--------------000408070700050305030206--

From leifj@mnt.se  Thu Oct 18 23:48:17 2012
Return-Path: <leifj@mnt.se>
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 ED45921F846A for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 4+9Y7qXBpjoX for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:48:16 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7E68821F8620 for <scim@ietf.org>; Thu, 18 Oct 2012 23:48:15 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so105903lam.31 for <scim@ietf.org>; Thu, 18 Oct 2012 23:48:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=3IFr9b/mhgr/usNMmuuikPKQjsk3jVg5Ie4oDemVm/k=; b=omJkkcmLupNFW5oCgjzeDwo/pOExShupjdK1BP8KCcKW4urRu5/swts93+zw/LWr0W ojwZT+LNKhtmcnO+m/9Ot41kozxlOVQnr5wtwjQfk76SJZ/sd5TwpWRSKw+VS6iFiaiz NfRievMvgs/l82d8ewyjLvjas5mb1pwPSzazmb7jUqn7DofIWmPphTfqU1WiIUTSQ2l8 J00uEfNT8tFlZFR9LTVnVE3T9SgpnpHlFw8ywy0rpP22ve71cb/kdKrXWjAm/kbUKDRN Awsw060RITtYJD9kqjGrZuITZsUovVdB7RQ3rcHqDiMT4lbGCBoVdvxSqQzP2TDa7RXL 8pFQ==
Received: by 10.152.105.103 with SMTP id gl7mr307064lab.10.1350629294436; Thu, 18 Oct 2012 23:48:14 -0700 (PDT)
Received: from [10.0.0.232] (ua-83-227-179-169.cust.bredbandsbolaget.se. [83.227.179.169]) by mx.google.com with ESMTPS id j9sm301563lbk.17.2012.10.18.23.48.11 (version=SSLv3 cipher=OTHER); Thu, 18 Oct 2012 23:48:13 -0700 (PDT)
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <50802113.4040805@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-8B5164C5-D365-45AF-941B-0BD78D4AC68E
Content-Transfer-Encoding: 7bit
Message-Id: <E43A1E0C-AAB6-4682-AF26-E6A58F79E48C@mnt.se>
X-Mailer: iPad Mail (10A403)
From: Leif Johansson <leifj@mnt.se>
Date: Fri, 19 Oct 2012 08:48:06 +0200
To: Eliot Lear <lear@cisco.com>
X-Gm-Message-State: ALoCoQnct1OdcRcbCvuC5yAx2Hs/W1MfXFL997fS9nc9VtYZSi8LGP+6crohWwvxPpbZsBZnc/j/
Cc: "scim@ietf.org" <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: Fri, 19 Oct 2012 06:48:17 -0000

--Apple-Mail-8B5164C5-D365-45AF-941B-0BD78D4AC68E
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



18 okt 2012 kl. 17:32 skrev Eliot Lear <lear@cisco.com>:

> Leif, Morteza,
>=20
> I'm sorry to be a stick in the mud, but I don't understand the objective o=
f this design team.  Let's start with an easy question:
> What work are they supposed to do?  What issues are they supposed to addre=
ss?
> Put another way, I was not of the understanding that what is posted is a s=
trawman, but based on running code.  If there is running code, it seems to m=
e that the onus is on those in the WG to state issues.  There are a number, a=
s I understand it.  A design team is necessary when something needs to be de=
signed.  What here needs to be designed
>=20

The chairs believe that the scim comminity see a need for a version 2.0 that=
 involve more than minor incremental changes from what we have now. In our o=
pinion a design team will help the wg start to converge more quickly.=20

The chairs also fully expect the group to be reduced in size very quckly as i=
t was clear on the first call that all who volunteered were not actually abl=
e to spend the time.

In the meantime please continue identifying issues!

> Now to answer my question in part, there is this dangling reference to Ser=
viceProviderConfigs.  Is that needed or should it be removed?
> I guess what I'm asking for is just a bit more scope, please.
> Eliot
>=20
> On 10/11/12 11:31 AM, Leif Johansson wrote:
>> On 10/11/2012 09:02 AM, Hannes Tschofenig wrote:
>> > Hi chairs,
>>=20
>> > Are we talking about this document:=20
>> > http://datatracker.ietf.org/doc/draft-ietf-scim-api/
>>=20
>> > Looks like a strawman proposal to me already right now.
>>=20
>> We are talking about a strawman for the next major revision of
>> that document and the schema document.
>>=20
>> 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.
>>=20
>>     Best R
>>     Leif
> >
>       _______________________________________________
>=20
>       > scim mailing list
>=20
>       > scim@ietf.org
>=20
>       > https://www.ietf.org/mailman/listinfo/scim
>=20
>       >
>=20
>       >
>=20
>=20

--Apple-Mail-8B5164C5-D365-45AF-941B-0BD78D4AC68E
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>18 okt 2012 kl. 17:32 skrev Eliot Lear &lt;<a href="mailto:lear@cisco.com">lear@cisco.com</a>&gt;:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  
  
    Leif, Morteza,<br>
    <br>
    I'm sorry to be a stick in the mud, but I don't understand the
    objective of this design team.&nbsp; Let's start with an easy question:<br>
    <ul>
      <li>What work are they supposed to do?&nbsp; What issues are they
        supposed to address?</li>
    </ul>
    <p>Put another way, I was not of the understanding that what is
      posted is a strawman, but based on running code.&nbsp; If there is
      running code, it seems to me that the onus is on those in the WG
      to state issues.&nbsp; There are a number, as I understand it.&nbsp; A
      design team is necessary when something needs to be designed.&nbsp;
      What here needs to be designed</p></div></blockquote><div><br></div><div>The chairs believe that the scim comminity see a need for a version 2.0 that involve more than minor incremental changes from what we have now. In our opinion a design team will help the wg start to converge more quickly.&nbsp;</div><div><br></div><div>The chairs also fully expect the group to be reduced in size very quckly as it was clear on the first call that all who volunteered were not actually able to spend the time.</div><div><br></div><div>In the meantime please continue identifying issues!</div><br><blockquote type="cite"><div>
    <p>Now to answer my question in part, there is this dangling
      reference to ServiceProviderConfigs.&nbsp; Is that needed or should it
      be removed?<br>
    </p>
    <p>I guess what I'm asking for is just a bit more scope, please.<br>
    </p>
    <p>Eliot<br>
    </p>
    <br>
    On 10/11/12 11:31 AM, Leif Johansson wrote:<br>
    <blockquote type="cite">On 10/11/2012 09:02 AM, Hannes Tschofenig
      wrote:<br>
      &gt; Hi chairs,<br>
      <br>
      &gt; Are we talking about this document: <br>
      &gt; <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-scim-api/">http://datatracker.ietf.org/doc/draft-ietf-scim-api/</a><br>
      <br>
      &gt; Looks like a strawman proposal to me already right now.<br>
      <br>
      We are talking about a strawman for the next major revision of<br>
      that document and the schema document.<br>
      <br>
      It is great to see so many are willing to participate. Please<br>
      note that participation in a design-team requires active<br>
      participation and time comittment.<br>
      <br>
      &nbsp;&nbsp; &nbsp;Best R<br>
      &nbsp;&nbsp; &nbsp;Leif<br>
      <br>
    </blockquote>
    <span style="white-space: pre;">&gt;
      _______________________________________________<br>
      &gt; scim mailing list<br>
      &gt; <a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a><br>
      &gt; <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a><br>
      &gt;<br>
      &gt;</span><br>
    <br>
    <br>
  

</div></blockquote></body></html>
--Apple-Mail-8B5164C5-D365-45AF-941B-0BD78D4AC68E--

From leifj@mnt.se  Thu Oct 18 23:49:54 2012
Return-Path: <leifj@mnt.se>
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 C6F7A21F8630 for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 L7mvM9EJshJM for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:49:53 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8F521F8634 for <scim@ietf.org>; Thu, 18 Oct 2012 23:49:53 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so106742lam.31 for <scim@ietf.org>; Thu, 18 Oct 2012 23:49:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=/ZOnOOzZLuBYGgjQwipEx2oYP3u93WJILahIsWxiXL8=; b=lMwaOoHKr3dqHJ7lnB80b8moKGSTH/WcYLogNhGAqAPIJSdZfdPsWqgOsDx0KW0SJI cuMLwfgZN+w3osw5nfv3ADvXEYDD6uA1pF8y8aeZqXXeK6h1xSPzEhrP7W5q4TwXA0K8 wt/zRqdfcNbUs2E/P6WiBdxSlMOX7AQU4pLVGz71bUzXf7uzNDvRXLIbCvKncHMud5eR Jn3QJMaenMZD7FTHbPRDn0m41w4vJyGJ6AYZjqZ1fYjTBBwbj95OztdHibjOIePfnZBY 6TOeenf/p8pU+oOj4Jovqu5YRfClktW3Ei+2NKwgvx2WPthgxjJMQNOsTl0MnmKxAFXZ I9tg==
Received: by 10.152.162.97 with SMTP id xz1mr269957lab.38.1350629392170; Thu, 18 Oct 2012 23:49:52 -0700 (PDT)
Received: from [10.0.0.232] (ua-83-227-179-169.cust.bredbandsbolaget.se. [83.227.179.169]) by mx.google.com with ESMTPS id e4sm306002lby.12.2012.10.18.23.49.49 (version=SSLv3 cipher=OTHER); Thu, 18 Oct 2012 23:49:51 -0700 (PDT)
References: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <06054233-81BD-42D6-A418-07A3EFA2E922@mnt.se>
X-Mailer: iPad Mail (10A403)
From: Leif Johansson <leifj@mnt.se>
Date: Fri, 19 Oct 2012 08:49:40 +0200
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Gm-Message-State: ALoCoQmwds5UtcJw55UVuDnO2XWkxBk0ynfiLXvCjwVglxWc7jjBPAUcTuXCi0zsJxNDomEnXmFi
Cc: "igor.faynberg@alcatel-lucent.com" <igor.faynberg@alcatel-lucent.com>, "scim@ietf.org" <scim@ietf.org>, Phil Hunt <phil.hunt@oracle.com>
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: Fri, 19 Oct 2012 06:49:54 -0000

18 okt 2012 kl. 20:49 skrev Hannes Tschofenig <hannes.tschofenig@gmx.net>:

> Which conference call last Wednesday? I did not see a conference call anno=
uncement on the list.

Hannes, design teams are allowed to hold private conference calls to organiz=
e work. As long as the bring work back to the wg.

>=20
> Sent from my ASUS Pad
>=20
> Phil Hunt <phil.hunt@oracle.com> wrote:
>=20
>> 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 W=
G.
>>=20
>> I don't see a problem here.
>>=20
>> Phil
>>=20
>> @independentid
>> www.independentid.com
>> phil.hunt@oracle.com
>>=20
>>=20
>>=20
>>=20
>>=20
>> On 2012-10-18, at 10:25 AM, Hannes Tschofenig wrote:
>>=20
>>> Hi Igor,
>>>=20
>>> I am not sure what you mean. Here is what the IESG says about design tea=
ms: http://www.ietf.org/iesg/statement/design-team.html
>>>=20
>>> Ciao
>>> Hannes
>>>=20
>>> PS: Btw, although http://www.ietf.org/iesg/statement/design-team.html sa=
ys that
>>> "
>>> The key point here is that the output of a design team is input to a wor=
king group, not a final document.
>>> "
>>> I think it is a rather theoretical statement.
>>>=20
>>> I have been involved in about 20 design teams and I have never had the c=
ase where the output of the design team was rejected by the group.
>>>=20
>>> 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.
>>>>=20
>>>>  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).
>>>>=20
>>>> 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.
>>>>=20
>>>> In short, what privileges will the official /design team /have in the
>>>> process vs. a typical de-facto design team?
>>>>=20
>>>> Igor
>>>>=20
>>>> On 10/18/2012 11:32 AM, Eliot Lear wrote:
>>>>> Leif, Morteza,
>>>>>=20
>>>>> 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:
>>>>>=20
>>>>> * What work are they supposed to do?  What issues are they supposed
>>>>>   to address?
>>>>>=20
>>>>> 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
>>>>>=20
>>>>> Now to answer my question in part, there is this dangling reference to=

>>>>> ServiceProviderConfigs.  Is that needed or should it be removed?
>>>>>=20
>>>>> I guess what I'm asking for is just a bit more scope, please.
>>>>>=20
>>>>> Eliot
>>>>>=20
>>>>>=20
>>>>> On 10/11/12 11:31 AM, Leif Johansson wrote:
>>>>>> On 10/11/2012 09:02 AM, Hannes Tschofenig wrote:
>>>>>>> Hi chairs,
>>>>>>=20
>>>>>>> Are we talking about this document:
>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-scim-api/
>>>>>>=20
>>>>>>> Looks like a strawman proposal to me already right now.
>>>>>>=20
>>>>>> We are talking about a strawman for the next major revision of
>>>>>> that document and the schema document.
>>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>>   Best R
>>>>>>   Leif
>>>>> _______________________________________________
>>>>>=20
>>>>>> scim mailing list
>>>>>=20
>>>>>> scim@ietf.org
>>>>>=20
>>>>>> https://www.ietf.org/mailman/listinfo/scim
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> scim mailing list
>>>>> scim@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/scim
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> scim mailing list
>>>> scim@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/scim
>>>=20
>>> _______________________________________________
>>> scim mailing list
>>> scim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/scim
>>=20
>> _______________________________________________
>> 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

From leifj@mnt.se  Thu Oct 18 23:50:14 2012
Return-Path: <leifj@mnt.se>
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 2681121F865F for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.335
X-Spam-Level: 
X-Spam-Status: No, score=-2.335 tagged_above=-999 required=5 tests=[AWL=-0.132, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 eEtOzZtAE1eE for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:50:11 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id B856E21F865B for <scim@ietf.org>; Thu, 18 Oct 2012 23:50:07 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so160471lbo.31 for <scim@ietf.org>; Thu, 18 Oct 2012 23:50:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=lcAbjzBcI+kS+n+a084VP1IYPJ7N/C2Sb5IArXB+xao=; b=UtLIMd0MbsA0WTokBPhrGCh0B0uZSnG7/dTzbl/fT8qJEIYJlu10nN6gCFsG+7lgeG kzIvK24TdOqM6yTf8yMWqar9gBzRt4zmrXOYBOq3kLSNFo/DZP/5ffqtPGo5V9Vo3/G6 7j3O/LShhjczF0qV5EkA9tAfbVpTsqytbX8HIFFLe6mpSLlbSiWfZWHclZtPy/y+JzA5 6KVWfR882q/P1KA/Rzhj2bI7eEObzy8hsqmPLX75G/pznjOYxZ7V3veYIjGHHd/szLXd mS2uYTM9+1ganLAT09Qd+UOtzAsMCTWPgZ7Fm9JBkc8w4M9UISIKG0yK6BqlAWUbNTdW D6pQ==
Received: by 10.152.103.243 with SMTP id fz19mr288989lab.27.1350629406631; Thu, 18 Oct 2012 23:50:06 -0700 (PDT)
Received: from [10.0.0.232] (ua-83-227-179-169.cust.bredbandsbolaget.se. [83.227.179.169]) by mx.google.com with ESMTPS id e4sm306002lby.12.2012.10.18.23.50.04 (version=SSLv3 cipher=OTHER); Thu, 18 Oct 2012 23:50:05 -0700 (PDT)
References: <u3xqbbsrre16qpg0gn6uhxya.1350586164138@email.android.com> <6.2.5.6.2.20121018130937.0b0cd318@resistor.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <6.2.5.6.2.20121018130937.0b0cd318@resistor.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7D3C732-8885-4F44-BDC0-A1A028E3594E@mnt.se>
X-Mailer: iPad Mail (10A403)
From: Leif Johansson <leifj@mnt.se>
Date: Fri, 19 Oct 2012 08:50:04 +0200
To: SM <sm@resistor.net>
X-Gm-Message-State: ALoCoQmw5QsxWJrjQQEo4FCWepcDGt/8u2UBaANjOAh0Qj2Z0QHXbxL5rrAuf+DEFHHgHd8bQFnQ
Cc: "scim@ietf.org" <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: Fri, 19 Oct 2012 06:50:14 -0000

18 okt 2012 kl. 22:19 skrev SM <sm@resistor.net>:

> At 11:49 18-10-2012, Hannes Tschofenig wrote:
>> Which conference call last Wednesday? I did not see a conference call ann=
ouncement on the list.
>=20
> The conference call announcement I saw is at http://www.ietf.org/mail-arch=
ive/web/scim/current/msg00767.html  Was that an IETF activity? :-)

No it was not!

>=20
> Regards,
> -sm=20
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim

From leifj@mnt.se  Thu Oct 18 23:59:34 2012
Return-Path: <leifj@mnt.se>
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 673CB21F865E for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085,  BAYES_00=-2.599]
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 LtBGsqHXof-n for <scim@ietfa.amsl.com>; Thu, 18 Oct 2012 23:59:33 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 295E021F8654 for <scim@ietf.org>; Thu, 18 Oct 2012 23:59:32 -0700 (PDT)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.5/8.14.3) with ESMTP id q9J6xKGq015903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Oct 2012 08:59:25 +0200 (CEST)
Message-ID: <5080FA48.40603@mnt.se>
Date: Fri, 19 Oct 2012 08:59:20 +0200
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com>
In-Reply-To: <50802113.4040805@cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Fri, 19 Oct 2012 06:59:34 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/18/2012 05:32 PM, 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
> 


I'm not sure if the email I send from my ipad is getting through so
forgive me if this (approximate) reply appears twice on the list.

The chairs believe that the SCIM WG are having trouble getting
started because there is a perceived need for non-trivial changes
in a "SCIM 2.0" relative to what we have in the current published
documents.

The purpose of a design team is to help the WG start that discussion
more quickly.

The chairs expect the design team to "right-size" itself very quickly
since on the first call (which was *NOT* an IETF activity) it became
clear that many who volunteered did not expect to be called on to do
actual work.

As with all design teams the intent is to produce a draft and present
it to the WG for discussion.

The chairs are there to make sure this happens.

I hope this helps to clear things up.

	Leif




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCA+kQACgkQ8Jx8FtbMZnfH9gCgnxxndl0bN0hKLO9gfh8nx6M8
AYkAnjRC9l0MTGSpQzVHIPXw/OZ8tziF
=PyWd
-----END PGP SIGNATURE-----

From leifj@mnt.se  Fri Oct 19 00:07:04 2012
Return-Path: <leifj@mnt.se>
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 7081521F8667 for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 00:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599]
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 WVkIjHDjK4MJ for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 00:07:03 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 07B5F21F86DA for <scim@ietf.org>; Fri, 19 Oct 2012 00:07:02 -0700 (PDT)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.5/8.14.3) with ESMTP id q9J76q0S013373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Oct 2012 09:06:56 +0200 (CEST)
Message-ID: <5080FC0C.8050801@mnt.se>
Date: Fri, 19 Oct 2012 09:06:52 +0200
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080217D.7010703@stpeter.im>
In-Reply-To: <5080217D.7010703@stpeter.im>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: scim@ietf.org, Eliot Lear <lear@cisco.com>
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: Fri, 19 Oct 2012 07:07:04 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/18/2012 05:34 PM, Peter Saint-Andre wrote:
> On 10/18/12 9: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.
> 
> And given that half of the semi-active WG participants seem to
> have volunteered to be on the design team, we might consider just
> doing the work in the WG as a whole. :-)

As I said in an other mail just now: I don't expect the design team
to stay this size. If it did then you'd have a very good point.

	MVH leifj
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCA/AwACgkQ8Jx8FtbMZnfEuQCfYAeDWS1b/Vv+uk+35JLtUlwA
NLkAoLFfJsLqVTqJImN67IeNRJVgTstc
=M7p0
-----END PGP SIGNATURE-----

From hannes.tschofenig@gmx.net  Fri Oct 19 00:48:27 2012
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 18FA721F87D7 for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 00:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 vj4ZDi9MFyb1 for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 00:48:26 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id B887821F87EC for <scim@ietf.org>; Fri, 19 Oct 2012 00:48:25 -0700 (PDT)
Received: (qmail invoked by alias); 19 Oct 2012 07:48:22 -0000
Received: from unknown (EHLO [10.255.131.34]) [194.251.119.201] by mail.gmx.net (mp001) with SMTP; 19 Oct 2012 09:48:22 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18oMFY93aQoJCGjyPUqkGNxkfXzUJk1tPkwdyKI7B EFNjLhF4y6dFaK
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <5080FA48.40603@mnt.se>
Date: Fri, 19 Oct 2012 10:48:09 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se>
To: Leif Johansson <leifj@mnt.se>
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
Cc: scim@ietf.org, Hannes Tschofenig <hannes.tschofenig@gmx.net>, Eliot Lear <lear@cisco.com>
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: Fri, 19 Oct 2012 07:48:27 -0000

I would like to be part of the design team.=20
Without being on the design team it seems impossible to get to know what =
is going on.=20

On Oct 19, 2012, at 9:59 AM, Leif Johansson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 10/18/2012 05:32 PM, Eliot Lear wrote:
>> Leif, Morteza,
>>=20
>> I'm sorry to be a stick in the mud, but I don't understand the=20
>> objective of this design team.  Let's start with an easy question:
>>=20
>> * What work are they supposed to do?  What issues are they
>> supposed to address?
>>=20
>> 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
>>=20
>=20
>=20
> I'm not sure if the email I send from my ipad is getting through so
> forgive me if this (approximate) reply appears twice on the list.
>=20
> The chairs believe that the SCIM WG are having trouble getting
> started because there is a perceived need for non-trivial changes
> in a "SCIM 2.0" relative to what we have in the current published
> documents.
>=20
> The purpose of a design team is to help the WG start that discussion
> more quickly.
>=20
> The chairs expect the design team to "right-size" itself very quickly
> since on the first call (which was *NOT* an IETF activity) it became
> clear that many who volunteered did not expect to be called on to do
> actual work.
>=20
> As with all design teams the intent is to produce a draft and present
> it to the WG for discussion.
>=20
> The chairs are there to make sure this happens.
>=20
> I hope this helps to clear things up.
>=20
> 	Leif
>=20
>=20
>=20
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>=20
> iEYEARECAAYFAlCA+kQACgkQ8Jx8FtbMZnfH9gCgnxxndl0bN0hKLO9gfh8nx6M8
> AYkAnjRC9l0MTGSpQzVHIPXw/OZ8tziF
> =3DPyWd
> -----END PGP SIGNATURE-----
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim


From leifj@mnt.se  Fri Oct 19 00:51:31 2012
Return-Path: <leifj@mnt.se>
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 E33D921F8461 for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 00:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.295
X-Spam-Level: 
X-Spam-Status: No, score=-0.295 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1]
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 l6DFmxcRayzR for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 00:51:31 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12A9321F841F for <scim@ietf.org>; Fri, 19 Oct 2012 00:51:29 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so141769lam.31 for <scim@ietf.org>; Fri, 19 Oct 2012 00:51:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=5tuW4GA3zwQQQUeczps6X0z2w2ge5MgB1Yo4C4RBplo=; b=L//20P2l5DDOaXDvNDQGoaL4jblfRxpzmpfBlFwSb95oR/6eXUGpQXv87qBr5tISQB BcbnBwYM3FTYHf21RXnkUnKsrR+XBLgw7F/QeQFOqFEAJ9Fl8j4DRMUqhTgMD2KArIAw sO+8QI5D5LVdhEVXiRhYU3kWDDW/GuFmId0uvHhVnqJu1pWCGvzAfg2rA5gdImNatuH4 05nBHNAstmVhPAXgjl2pG3Wbm5jC79vZqVItqKylbiCoN9a2uRfyj373ksyLiTNa984Z b27kZtFyRZHHdNBA4EFoHRZAKTfnL+XxLZj0QMZ6L45UZmv+cy0J8YkU/aqufJVumzUn /W0Q==
Received: by 10.112.44.132 with SMTP id e4mr292627lbm.101.1350633088934; Fri, 19 Oct 2012 00:51:28 -0700 (PDT)
Received: from [2.66.41.40] (2.66.41.40.mobile.tre.se. [2.66.41.40]) by mx.google.com with ESMTPS id nr2sm276995lab.5.2012.10.19.00.51.24 (version=SSLv3 cipher=OTHER); Fri, 19 Oct 2012 00:51:25 -0700 (PDT)
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se> <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se>
X-Mailer: iPhone Mail (10A403)
From: Leif Johansson <leifj@mnt.se>
Date: Fri, 19 Oct 2012 09:51:21 +0200
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Gm-Message-State: ALoCoQnJJ1LKIBzbgSOXsARhO9cGboCi+KN9coR4RcofoRvxwbc1j+P4cnfsVNvOEVoXvLS5zCVF
Cc: "scim@ietf.org" <scim@ietf.org>, Eliot Lear <lear@cisco.com>
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: Fri, 19 Oct 2012 07:51:32 -0000

fine, are you willing and able to put in a substantive effort involving a fe=
w hrs work per week?

19 okt 2012 kl. 09:48 skrev Hannes Tschofenig <hannes.tschofenig@gmx.net>:

> I would like to be part of the design team.=20
> Without being on the design team it seems impossible to get to know what i=
s going on.=20
>=20
> On Oct 19, 2012, at 9:59 AM, Leif Johansson wrote:
>=20
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>=20
>> On 10/18/2012 05:32 PM, Eliot Lear wrote:
>>> Leif, Morteza,
>>>=20
>>> I'm sorry to be a stick in the mud, but I don't understand the=20
>>> objective of this design team.  Let's start with an easy question:
>>>=20
>>> * What work are they supposed to do?  What issues are they
>>> supposed to address?
>>>=20
>>> 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
>>=20
>>=20
>> I'm not sure if the email I send from my ipad is getting through so
>> forgive me if this (approximate) reply appears twice on the list.
>>=20
>> The chairs believe that the SCIM WG are having trouble getting
>> started because there is a perceived need for non-trivial changes
>> in a "SCIM 2.0" relative to what we have in the current published
>> documents.
>>=20
>> The purpose of a design team is to help the WG start that discussion
>> more quickly.
>>=20
>> The chairs expect the design team to "right-size" itself very quickly
>> since on the first call (which was *NOT* an IETF activity) it became
>> clear that many who volunteered did not expect to be called on to do
>> actual work.
>>=20
>> As with all design teams the intent is to produce a draft and present
>> it to the WG for discussion.
>>=20
>> The chairs are there to make sure this happens.
>>=20
>> I hope this helps to clear things up.
>>=20
>>    Leif
>>=20
>>=20
>>=20
>>=20
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>>=20
>> iEYEARECAAYFAlCA+kQACgkQ8Jx8FtbMZnfH9gCgnxxndl0bN0hKLO9gfh8nx6M8
>> AYkAnjRC9l0MTGSpQzVHIPXw/OZ8tziF
>> =3DPyWd
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim
>=20

From michael.hammer@yaanatech.com  Fri Oct 19 06:11:22 2012
Return-Path: <michael.hammer@yaanatech.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 B053C21F85ED for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 06:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.962
X-Spam-Level: 
X-Spam-Status: No, score=-1.962 tagged_above=-999 required=5 tests=[AWL=0.637,  BAYES_00=-2.599]
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 0u9IBL-gwM09 for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 06:11:21 -0700 (PDT)
Received: from email1.corp.yaanatech.com (email1.corp.yaanatech.com [205.140.198.134]) by ietfa.amsl.com (Postfix) with ESMTP id BD7F121F85E7 for <scim@ietf.org>; Fri, 19 Oct 2012 06:11:21 -0700 (PDT)
Received: from EX2K10MB2.corp.yaanatech.com ([fe80::5d11:66a1:e508:6871]) by ex2k10hub1.corp.yaanatech.com ([::1]) with mapi id 14.01.0218.012; Fri, 19 Oct 2012 06:11:21 -0700
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "leifj@mnt.se" <leifj@mnt.se>, "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>
Thread-Topic: [scim] Proposal to create a design team
Thread-Index: AQHNpyalxIOrHKgYwk66fmTht0qU2Je0I8sAgAApiICAC2VQgIABAu4AgAANpICAAADlgP//49TQ
Date: Fri, 19 Oct 2012 13:11:20 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB32EBE9D72@ex2k10mb2.corp.yaanatech.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se> <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net> <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se>
In-Reply-To: <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.17.88.2]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0000_01CDADD9.B331B460"
MIME-Version: 1.0
Cc: "scim@ietf.org" <scim@ietf.org>, "lear@cisco.com" <lear@cisco.com>
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: Fri, 19 Oct 2012 13:11:22 -0000

------=_NextPart_000_0000_01CDADD9.B331B460
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Leif,

If you knew Hannes, you would know how funny that question sounds.
I don't think I know anyone more prolific.

Mike


-----Original Message-----
From: scim-bounces@ietf.org [mailto:scim-bounces@ietf.org] On Behalf Of Leif
Johansson
Sent: Friday, October 19, 2012 3:51 AM
To: Hannes Tschofenig
Cc: scim@ietf.org; Eliot Lear
Subject: Re: [scim] Proposal to create a design team

fine, are you willing and able to put in a substantive effort involving a
few hrs work per week?

19 okt 2012 kl. 09:48 skrev Hannes Tschofenig <hannes.tschofenig@gmx.net>:

> I would like to be part of the design team. 
> Without being on the design team it seems impossible to get to know what
is going on. 
> 
> On Oct 19, 2012, at 9:59 AM, Leif Johansson wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> On 10/18/2012 05:32 PM, 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
>> 
>> 
>> I'm not sure if the email I send from my ipad is getting through so 
>> forgive me if this (approximate) reply appears twice on the list.
>> 
>> The chairs believe that the SCIM WG are having trouble getting 
>> started because there is a perceived need for non-trivial changes in 
>> a "SCIM 2.0" relative to what we have in the current published 
>> documents.
>> 
>> The purpose of a design team is to help the WG start that discussion 
>> more quickly.
>> 
>> The chairs expect the design team to "right-size" itself very quickly 
>> since on the first call (which was *NOT* an IETF activity) it became 
>> clear that many who volunteered did not expect to be called on to do 
>> actual work.
>> 
>> As with all design teams the intent is to produce a draft and present 
>> it to the WG for discussion.
>> 
>> The chairs are there to make sure this happens.
>> 
>> I hope this helps to clear things up.
>> 
>>    Leif
>> 
>> 
>> 
>> 
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>> 
>> iEYEARECAAYFAlCA+kQACgkQ8Jx8FtbMZnfH9gCgnxxndl0bN0hKLO9gfh8nx6M8
>> AYkAnjRC9l0MTGSpQzVHIPXw/OZ8tziF
>> =PyWd
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> 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

------=_NextPart_000_0000_01CDADD9.B331B460
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIP6zCCBBow
ggMCAhEAi1t1VoRUhQsAz684SM6xpDANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNOTkxMDAxMDAwMDAwWhcNMzYwNzE2MjM1OTU5WjCByjELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk
IHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IC0gRzMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDd
hNS5tPmn2PMEeJzePdxsExbZet0kUWbAxyZZDawGCMKU0TMf8IM1H24byN6qbhVOVCfvxG0a7Avj
DvBEpVfHQFgeo0cfcexg9m2UyBg57f5CGFbf5ExJEHhOAXY1YxI23Wa8AQQ2o1Vo1aI2CayrISZU
Bq0/yhTgrMqtBh2V4vid8eBg/8J/dStMzNr+h5kh6rr+PlTX0ll42zxuz6ATABq4J6HkvmeWyqDF
s5zdyXWe6zCaX6PN2a54GT8j6VzbKb2tVcgbVIxj9uim6sc3ElyjKR4C2dsfO7TXD1ZHgRUESq+D
J9HFWIjB3faqp6MY2miqbRFR4b9la5+WdtE9AgMBAAEwDQYJKoZIhvcNAQEFBQADggEBAKtmjdez
useatuZV0AXxnzGNWqrZqkYmD3Htpa1TVmIBRypE6f4/dAsTm7n0TRuy0V+yttKIXLOfzcvUp9lg
lYQ6+ME3HWHK57DF5ZHaVKasMYGul97NCKy4wJeAf25ypOdpE5VlH8STPP15jwTUPk/q957OzWd8
T2UC/5GFVHPH/zb3hi3s0F5P/xGfcgbWuBrxTA0mZeJEgB7Hn+Pd6Ara7KUggGlooU9+4WvPB0H6
g468ON2wLhGxa7JCzJq8+UgieUoZD7IcPiB02WrDvvIoeBNWeU9tUOobsLVXsTdmWCPz3A/fCofE
74YF1TgUYJmjS94GlnEs8tu2H6TvP+4wggTXMIIDv6ADAgECAhBcX1ns/Jl/DtI19/BXCcuBMA0G
CSqGSIb3DQEBBQUAMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAd
BgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBo
dHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBW
YWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVy
IENBIC0gRzMwHhcNMTIwNDAzMDAwMDAwWhcNMTMwNDAzMjM1OTU5WjCCAR4xFzAVBgNVBAoTDlZl
cmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13
d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChj
KTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNDAyBgNVBAsTK0RpZ2l0YWwgSUQg
Q2xhc3MgMSAtIE1pY3Jvc29mdCBGdWxsIFNlcnZpY2UxFzAVBgNVBAMUDk1pY2hhZWwgSGFtbWVy
MSswKQYJKoZIhvcNAQkBFhxtaWNoYWVsLmhhbW1lckB5YWFuYXRlY2guY29tMIGfMA0GCSqGSIb3
DQEBAQUAA4GNADCBiQKBgQDoKTk9rP/4lG6CLqIR4++IFTuOSLF6bmhDr6eiSahqU0VNP+H/LbiD
MAZsK9GQoBYPKQdKzy/gM+fl3Gm6VOdjKl8M3GB6LGgAK8d3ETN5dyKe5CAG7EEbKg9wxHWcuXW7
KYd052ven5Ec+Xj++v3HsE423O5q2mNh1Q8FNsnlXQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYD
VR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2ln
bi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYD
VR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20v
SW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQA8rhDezFsw7OlR3+mZOZ39
SCKWNJ4gMlQEe31NNtvs6BUzE1uN+fJeZrJ5zjTdJWeG1NgVugcuzQfdv/m5BYbhgJvNfW6ElqZh
cye6imOUx8diekkeHXKYSLnEvCdJItXsC1h/huIT9e83WksM92qI/TFyCq6u39cGf9PaBYbcKcZk
jHjNi3SPnGifMC6opGiiyK/vB1lituoBRcJ13Y7XoXA8T0kSR8Dtmqvo1JudcFAbS1srytG1QX1H
XTsPkTDKHlwv2ZfmCSKK3sWHDrZfpRglxvcX2OwibcKVkKBJRRw36UuJOIj/u0WYABcYtusAb2+0
nqoGmOEYARnrseTZMIIG7jCCBdagAwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUF
ADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZv
ciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQ
cmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkw
NDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP
6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYH
r54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50
ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yx
BF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ
6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CG
SAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYI
KwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6Al
hiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYI
KwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQ
UjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1Ud
EQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EI
Qf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4
BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkx
RTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB
dXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZ
gbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v
8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM6
1a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/
XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4
VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggS4MIIEtAIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTsw
OQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykw
OTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFz
cyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczAhBcX1ns/Jl/DtI19/BXCcuBMAkGBSsO
AwIaBQCgggMbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMTAx
OTEzMTExOFowIwYJKoZIhvcNAQkEMRYEFO0P0mInorgaOtf7PNanlz/nJl2IMIGrBgkqhkiG9w0B
CQ8xgZ0wgZowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBFjAKBggqhkiG9w0DBzALBglghkgBZQME
AQIwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEo
MAcGBSsOAwIaMAsGCWCGSAFlAwQCAzALBglghkgBZQMEAgIwCwYJYIZIAWUDBAIBMIIBAwYJKwYB
BAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAd
BgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBo
dHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBW
YWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVy
IENBIC0gRzMCEFxfWez8mX8O0jX38FcJy4EwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkG
A1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVz
dCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24u
Y29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5W
ZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczAhBcX1ns/Jl/DtI1
9/BXCcuBMA0GCSqGSIb3DQEBAQUABIGAppU9SYJzJwnhyLZhEdk1gfHnliATELpDi54FSZguhO+J
4dUynSGyfyKJmV830sytD5Kd/4O0HDb/k8TQovMMCh4poGhSru6XCFOnab871IY/XmHJlj6+mxHd
ZolXgA93KBP3sB36s2LEslLcSj+BVQcLo++zSaMTAZHccbt+Q1YAAAAAAAA=

------=_NextPart_000_0000_01CDADD9.B331B460--

From leifj@mnt.se  Fri Oct 19 06:46:24 2012
Return-Path: <leifj@mnt.se>
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 7F69421F86B0 for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 06:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 sr5Aml4N9S4Z for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 06:46:23 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA1121F86A1 for <scim@ietf.org>; Fri, 19 Oct 2012 06:46:23 -0700 (PDT)
Received: from [109.105.104.224] (dhcp89.se-tug.nordu.net [109.105.104.224] (may be forged)) (authenticated bits=0) by backup-server.nordu.net (8.14.5/8.14.3) with ESMTP id q9JDkIdW003378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <scim@ietf.org>; Fri, 19 Oct 2012 15:46:21 +0200 (CEST)
Message-ID: <508159AA.4080809@mnt.se>
Date: Fri, 19 Oct 2012 15:46:18 +0200
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: scim@ietf.org
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se> <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net> <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se> <00C069FD01E0324C9FFCADF539701DB32EBE9D72@ex2k10mb2.corp.yaanatech.com>
In-Reply-To: <00C069FD01E0324C9FFCADF539701DB32EBE9D72@ex2k10mb2.corp.yaanatech.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Fri, 19 Oct 2012 13:46:24 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/19/2012 03:11 PM, Michael Hammer wrote:
> Leif,
> 
> If you knew Hannes, you would know how funny that question sounds. 
> I don't think I know anyone more prolific.

Me and Hannes know each other well :-)

The question however was not made in jest. Knowing just how much
time Hannes spends I'm curious about his ability to spend more.

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCBWakACgkQ8Jx8FtbMZnfH+QCguS6aqfRqgTattU3q1cmXUwH1
LEQAn0DVwLCOQqN5Js5q8MnrRkACz5pG
=lNAp
-----END PGP SIGNATURE-----

From pdingle@pingidentity.com  Fri Oct 19 12:49:57 2012
Return-Path: <pdingle@pingidentity.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 2271921F878B for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 12:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.976
X-Spam-Level: 
X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 BbvRPeGzRtfl for <scim@ietfa.amsl.com>; Fri, 19 Oct 2012 12:49:55 -0700 (PDT)
Received: from na3sys009aog124.obsmtp.com (na3sys009aog124.obsmtp.com [74.125.149.151]) by ietfa.amsl.com (Postfix) with ESMTP id 21A4421F878C for <scim@ietf.org>; Fri, 19 Oct 2012 12:49:55 -0700 (PDT)
Received: from mail-wg0-f70.google.com ([74.125.82.70]) (using TLSv1) by na3sys009aob124.postini.com ([74.125.148.12]) with SMTP ID DSNKUIGu4bl/8A3jEcrh8cg2wQ3UBATt0KqP@postini.com; Fri, 19 Oct 2012 12:49:55 PDT
Received: by mail-wg0-f70.google.com with SMTP id dt14so721655wgb.1 for <scim@ietf.org>; Fri, 19 Oct 2012 12:49:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=SOGyTzW+0i93DGIyn0XT0LCG+Ocm0VhpW/OgaPkqZh8=; b=cT/8lJEoYp+ZuhTYZqeXjidRQ6Qj6e3eqbqhdmAR9fnv2CqSdGsHGgOyjOtQ2xZs3p f8UdGb7XxCZcRFC7NiFcu+WAn4Db2N244N9VDOy+BhNmaL7UYpxkf5bm4vTe7oUicvGO wYRjXj7tCJbOB/gJrEuTtFhQKXZVXR4fwKsY/AWx7q4AQFAJ4ZO28dYUq96ND6mW5dAZ zKoslbF/lGS2pHA/F5HwcVMllM/x7u2Nng8x/NoEUhZLEmL2vdn4WNSBFvz2NZhZSGB4 IRJBXmyPrx96dK2lYeAlBK0Ubx5ZMpFXRWbirwpBvUEBZ7behMoB3mHXFw6GNoJciHPw h7cA==
Received: by 10.14.4.201 with SMTP id 49mr3498732eej.0.1350676191731; Fri, 19 Oct 2012 12:49:51 -0700 (PDT)
Received: by 10.14.4.201 with SMTP id 49mr3498722eej.0.1350676191598; Fri, 19 Oct 2012 12:49:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.218.135 with HTTP; Fri, 19 Oct 2012 12:49:31 -0700 (PDT)
In-Reply-To: <508159AA.4080809@mnt.se>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se> <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net> <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se> <00C069FD01E0324C9FFCADF539701DB32EBE9D72@ex2k10mb2.corp.yaanatech.com> <508159AA.4080809@mnt.se>
From: Pam Dingle <pdingle@pingidentity.com>
Date: Fri, 19 Oct 2012 12:49:31 -0700
Message-ID: <CANBMvsD63J4jALe6ULKREtzTZfdoebEXnvNUpQ=boJuUeqw6Fw@mail.gmail.com>
To: Leif Johansson <leifj@mnt.se>
Content-Type: multipart/alternative; boundary=047d7b66f1cd9b58d104cc6ece03
X-Gm-Message-State: ALoCoQmuKVUOk40xxpR6l2dMp5UH3Is4ZrCq8KC9ecpx9DggghmJl1a7hU9tZwElqtm1NxWevK1i41T3urC0HKx517O0IAv8PLhZgk2RSFmk8vHlrF0iRr/hywTqnn0CxwpqjWY5sdn0
Cc: 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: Fri, 19 Oct 2012 19:49:57 -0000

--047d7b66f1cd9b58d104cc6ece03
Content-Type: text/plain; charset=ISO-8859-1

As someone who tracks this WG solely through the mailing list, I am
confused. In going through the mailing list archives, I do not see a
documented set of conversations that would directly lead me to the
conclusion that this working group as a whole has perceived that
significant changes must be made prior to a 2.0 SCIM release. It seems like
these decisions were made on a conference call, but I don't see any notes
from that conference call, assuming the call happened recently.

Could somebody just catch us up and start a new thread with a brief summary
of what exact non-trivial work has been identified as necessary prior to a
2.0 release?

My apologies if this is crystal clear to everybody else.

Thanks,

Pamela


On Fri, Oct 19, 2012 at 6:46 AM, Leif Johansson <leifj@mnt.se> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 10/19/2012 03:11 PM, Michael Hammer wrote:
> > Leif,
> >
> > If you knew Hannes, you would know how funny that question sounds.
> > I don't think I know anyone more prolific.
>
> Me and Hannes know each other well :-)
>
> The question however was not made in jest. Knowing just how much
> time Hannes spends I'm curious about his ability to spend more.
>
>         Cheers Leif
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>
> iEYEARECAAYFAlCBWakACgkQ8Jx8FtbMZnfH+QCguS6aqfRqgTattU3q1cmXUwH1
> LEQAn0DVwLCOQqN5Js5q8MnrRkACz5pG
> =lNAp
> -----END PGP SIGNATURE-----
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>



-- 
*Pamela Dingle*  |  Sr. Technical Architect
*Ping**Identity*  |   www.pingidentity.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
*O:* 303-999-5890   *M:* 303-999-5890
*Email:* pdingle@pingidentity.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
*Connect with Ping*
Twitter: @pingidentity
LinkedIn Group: Ping's Identity Cloud
Facebook.com/pingidentitypage
*Connect with me*
Twitter: @pamelarosiedee

--047d7b66f1cd9b58d104cc6ece03
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

As someone who tracks this WG solely through the mailing list, I am confuse=
d. In going through the mailing list archives, I do not see a documented se=
t of conversations that would directly lead me to the conclusion that this =
working group as a whole has perceived that significant changes must be mad=
e=A0prior to a 2.0 SCIM release. It seems like these decisions were made on=
 a conference call, but I don&#39;t see any notes from that conference call=
, assuming the call happened recently.=A0<div>


<br></div><div>Could somebody just catch us up and start a new thread with =
a brief summary of what exact non-trivial work has been identified as neces=
sary prior to a 2.0 release? =A0</div><div><br></div><div>My apologies if t=
his is crystal clear to everybody else. =A0</div>


<div><br></div><div>Thanks,</div><div><br></div><div>Pamela</div><div><br><=
/div><div><br><div class=3D"gmail_quote">On Fri, Oct 19, 2012 at 6:46 AM, L=
eif Johansson <span dir=3D"ltr">&lt;<a href=3D"mailto:leifj@mnt.se" target=
=3D"_blank">leifj@mnt.se</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div>On 10/19/2012 03:11 PM, Michael Hammer wrote:<br>
&gt; Leif,<br>
&gt;<br>
&gt; If you knew Hannes, you would know how funny that question sounds.<br>
&gt; I don&#39;t think I know anyone more prolific.<br>
<br>
</div>Me and Hannes know each other well :-)<br>
<br>
The question however was not made in jest. Knowing just how much<br>
time Hannes spends I&#39;m curious about his ability to spend more.<br>
<br>
=A0 =A0 =A0 =A0 Cheers Leif<br>
<div>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href=3D"http://www.enigmail.net/" ta=
rget=3D"_blank">http://www.enigmail.net/</a><br>
<br>
</div>iEYEARECAAYFAlCBWakACgkQ8Jx8FtbMZnfH+QCguS6aqfRqgTattU3q1cmXUwH1<br>
LEQAn0DVwLCOQqN5Js5q8MnrRkACz5pG<br>
=3DlNAp<br>
<div><div>-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/scim" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/scim</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<span style=3D"font-family:&#39;Lucida Grande&#39;,Tahoma,Arial,Verdana,san=
s-serif;font-size:10px;color:rgb(42,42,42)"><font color=3D"#343634" face=3D=
"Tahoma" style=3D"color:rgb(52,54,52);font-size:12px"><strong><span>Pamela =
Dingle</span></strong>=A0=A0|=A0=A0<span>Sr. Technical Architect</span></fo=
nt><br>


<font face=3D"Arial" style=3D"font-size:11px"><font color=3D"#343634" face=
=3D"Tahoma"><strong>Ping</strong></font><font color=3D"#E71939" face=3D"Tah=
oma"><strong>Identity</strong></font>=A0=A0|=A0=A0 <a href=3D"http://www.pi=
ngidentity.com" target=3D"_blank">www.pingidentity.com</a><br>


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -=
 - -<br><font color=3D"#005568"><strong>O:</strong></font>=A0<font color=3D=
"#343634"><span><a href=3D"tel:303-999-5890" value=3D"+13039995890" target=
=3D"_blank">303-999-5890</a></span></font>=A0=A0=A0<font color=3D"#005568">=
<strong>M:</strong></font>=A0<font color=3D"#343634"><span><a href=3D"tel:3=
03-999-5890" value=3D"+13039995890" target=3D"_blank">303-999-5890</a></spa=
n></font><br>


<font color=3D"#005568"><strong>Email:</strong></font>=A0<span><a href=3D"m=
ailto:pdingle@pingidentity.com" target=3D"_blank">pdingle@pingidentity.com<=
/a></span><br>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -=
 - - - - - - - - -<br>


<table cellpadding=3D"0" cellspacing=3D"0"><tbody><tr valign=3D"top"><td no=
wrap><div style=3D"float:left"><font face=3D"Arial" style=3D"font-size:11px=
"><font color=3D"#005568"><strong>Connect with Ping</strong></font><br><fon=
t color=3D"#000000">Twitter: @pingidentity</font><br>


<font color=3D"#000000">LinkedIn Group: Ping&#39;s Identity Cloud</font>=A0=
=A0 =A0<br><font color=3D"#000000">Facebook.com/pingidentitypage</font></fo=
nt></div></td><td nowrap><div style=3D"margin-left:20px"><font face=3D"Aria=
l" style=3D"font-size:11px"><font color=3D"#005568"><strong><span>Connect w=
ith me</span></strong></font><br>


<font color=3D"#000000"><span>Twitter: @pamelarosiedee</span></font><br><fo=
nt color=3D"#000000"><span></span></font></font></div></td></tr></tbody></t=
able></font></span><br>
</div>

--047d7b66f1cd9b58d104cc6ece03--

From leifj@mnt.se  Sat Oct 20 05:07:59 2012
Return-Path: <leifj@mnt.se>
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 EF5B521F889F for <scim@ietfa.amsl.com>; Sat, 20 Oct 2012 05:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.294
X-Spam-Level: 
X-Spam-Status: No, score=-0.294 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1]
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 XZjyT83Zd3AM for <scim@ietfa.amsl.com>; Sat, 20 Oct 2012 05:07:58 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 770A321F8562 for <scim@ietf.org>; Sat, 20 Oct 2012 05:07:57 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so975214lbo.31 for <scim@ietf.org>; Sat, 20 Oct 2012 05:07:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=Zfi1YlrfyY94jupoLaSyzyy1wqBXbfbAnZEjsWEgcG0=; b=DwEzwwST4D4Ut/ANJO8XhuRZTPh0zXtxn3bJo5ouQxP7fOrfJKhElcD8kezi51suxj IWvCcd+Q/+bjKO3S7jG2EL4ElxXgMQsgKcNh6cLtGesW9eyvO396pVK5eov1SE8paCqX QqkOms3NiOd3bCfYrCtqRiEOB2QDCGXeqyv8/wUAxBM97d7TCkiFAAJAj5qqLR3rtN/j RCFu+VZtbyNKlxegW1CJzU7KfEdWZ9ZqYXMJfWOF101fbtHo8bDAEOXys4IcLShUEGO9 JDVpfKoTaQeVRpXnxJEPfkdIKw9RkrcZzxW+nzktjdstmeleIle9ynssJr7xRVJ/hV6H xLtQ==
Received: by 10.152.108.197 with SMTP id hm5mr3498416lab.45.1350734876141; Sat, 20 Oct 2012 05:07:56 -0700 (PDT)
Received: from [2.64.227.177] (2.64.227.177.mobile.tre.se. [2.64.227.177]) by mx.google.com with ESMTPS id ps11sm1286983lab.12.2012.10.20.05.07.53 (version=SSLv3 cipher=OTHER); Sat, 20 Oct 2012 05:07:55 -0700 (PDT)
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se> <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net> <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se> <00C069FD01E0324C9FFCADF539701DB32EBE9D72@ex2k10mb2.corp.yaanatech.com> <508159AA.4080809@mnt.se> <CANBMvsD63J4jALe6ULKREtzTZfdoebEXnvNUpQ=boJuUeqw6Fw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CANBMvsD63J4jALe6ULKREtzTZfdoebEXnvNUpQ=boJuUeqw6Fw@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1744E3AB-1CFC-489B-B63D-A32EBF81BAAC
Content-Transfer-Encoding: 7bit
Message-Id: <6199A469-707B-4647-AFE7-B0BE1855242C@mnt.se>
X-Mailer: iPhone Mail (10A403)
From: Leif Johansson <leifj@mnt.se>
Date: Sat, 20 Oct 2012 14:07:49 +0200
To: Pam Dingle <pdingle@pingidentity.com>
X-Gm-Message-State: ALoCoQmW2VS54TI1yVcB1DiAxHhbTzXaTwT0kq9ZVhClaq7JnI8CtfM0/X/+Xc9tF4je07ZpqQUN
Cc: "scim@ietf.org" <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: Sat, 20 Oct 2012 12:07:59 -0000

--Apple-Mail-1744E3AB-1CFC-489B-B63D-A32EBF81BAAC
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



19 okt 2012 kl. 21:49 skrev Pam Dingle <pdingle@pingidentity.com>:

> As someone who tracks this WG solely through the mailing list, I am confus=
ed. In going through the mailing list archives, I do not see a documented se=
t of conversations that would directly lead me to the conclusion that this w=
orking group as a whole has perceived that significant changes must be made p=
rior to a 2.0 SCIM release. It seems like these decisions were made on a con=
ference call, but I don't see any notes from that conference call, assuming t=
he call happened recently.=20

Those discussions happened at the first
wg meeting (at the last IETF).

Like any group or individual who decide
to propose something to a wg, this design
ream will produce I-Ds that the wg will
choose to adopt or not.

The purpose of this exercise is to get a
focused technical discussion started, not
to end or preempt one.

>=20
> Could somebody just catch us up and start a new thread with a brief summar=
y of what exact non-trivial work has been identified as necessary prior to a=
 2.0 release? =20

There is some good starting points in the
presentations that Phil and Kelly made=20
in Vancouver.=20

>=20
> My apologies if this is crystal clear to everybody else. =20
>=20
> Thanks,

My appologies for clearly not beeing clear
enough on this issue.

Leif

>=20
> Pamela
>=20
>=20
> On Fri, Oct 19, 2012 at 6:46 AM, Leif Johansson <leifj@mnt.se> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>=20
>> On 10/19/2012 03:11 PM, Michael Hammer wrote:
>> > Leif,
>> >
>> > If you knew Hannes, you would know how funny that question sounds.
>> > I don't think I know anyone more prolific.
>>=20
>> Me and Hannes know each other well :-)
>>=20
>> The question however was not made in jest. Knowing just how much
>> time Hannes spends I'm curious about his ability to spend more.
>>=20
>>         Cheers Leif
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>>=20
>> iEYEARECAAYFAlCBWakACgkQ8Jx8FtbMZnfH+QCguS6aqfRqgTattU3q1cmXUwH1
>> LEQAn0DVwLCOQqN5Js5q8MnrRkACz5pG
>> =3DlNAp
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim
>=20
>=20
>=20
> --=20
> Pamela Dingle  |  Sr. Technical Architect
> PingIdentity  |   www.pingidentity.com
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -=
 - -
> O: 303-999-5890   M: 303-999-5890
> Email: pdingle@pingidentity.com
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -=
 - -
> Connect with Ping
> Twitter: @pingidentity
> LinkedIn Group: Ping's Identity Cloud   =20
> Facebook.com/pingidentitypage=09
> Connect with me
> Twitter: @pamelarosiedee
>=20

--Apple-Mail-1744E3AB-1CFC-489B-B63D-A32EBF81BAAC
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><br><br>19 okt 2012 kl. 21:49 skrev Pa=
m Dingle &lt;<a href=3D"mailto:pdingle@pingidentity.com">pdingle@pingidentit=
y.com</a>&gt;:<br><br></div><blockquote type=3D"cite"><div>As someone who tr=
acks this WG solely through the mailing list, I am confused. In going throug=
h the mailing list archives, I do not see a documented set of conversations t=
hat would directly lead me to the conclusion that this working group as a wh=
ole has perceived that significant changes must be made&nbsp;prior to a 2.0 S=
CIM release. It seems like these decisions were made on a conference call, b=
ut I don't see any notes from that conference call, assuming the call happen=
ed recently.&nbsp;</div></blockquote><div><br></div><div>Those discussions h=
appened at the first</div><div>wg meeting (at the last IETF).</div><div><br>=
</div><div>Like any group or individual who decide</div><div>to propose some=
thing to a wg, this design</div><div>ream will produce I-Ds that the wg will=
</div><div>choose to adopt or not.</div><div><br></div><div>The purpose of t=
his exercise is to get a</div><div>focused technical discussion started, not=
</div><div>to end or preempt one.</div><br><blockquote type=3D"cite"><div><d=
iv>


<br></div><div>Could somebody just catch us up and start a new thread with a=
 brief summary of what exact non-trivial work has been identified as necessa=
ry prior to a 2.0 release? &nbsp;</div></div></blockquote><div><br></div><di=
v>There is some good starting points in the</div><div>presentations that Phi=
l and Kelly made&nbsp;</div><div>in Vancouver.&nbsp;</div><div><br></div><bl=
ockquote type=3D"cite"><div><div><br></div><div>My apologies if this is crys=
tal clear to everybody else. &nbsp;</div>


<div><br></div><div>Thanks,</div></div></blockquote><div><br></div><div>My a=
ppologies for clearly not beeing clear</div><div>enough on this issue.</div>=
<div><br></div><div>Leif</div><br><blockquote type=3D"cite"><div><div><br></=
div><div>Pamela</div><div><br></div><div><br><div class=3D"gmail_quote">On Fri=
, Oct 19, 2012 at 6:46 AM, Leif Johansson <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:leifj@mnt.se" target=3D"_blank">leifj@mnt.se</a>&gt;</span> wrote:<br>=



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><div>-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div>On 10/19/2012 03:11 PM, Michael Hammer wrote:<br>
&gt; Leif,<br>
&gt;<br>
&gt; If you knew Hannes, you would know how funny that question sounds.<br>
&gt; I don't think I know anyone more prolific.<br>
<br>
</div>Me and Hannes know each other well :-)<br>
<br>
The question however was not made in jest. Knowing just how much<br>
time Hannes spends I'm curious about his ability to spend more.<br>
<br>
&nbsp; &nbsp; &nbsp; &nbsp; Cheers Leif<br>
<div>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href=3D"http://www.enigmail.net/" tar=
get=3D"_blank">http://www.enigmail.net/</a><br>
<br>
</div>iEYEARECAAYFAlCBWakACgkQ8Jx8FtbMZnfH+QCguS6aqfRqgTattU3q1cmXUwH1<br>
LEQAn0DVwLCOQqN5Js5q8MnrRkACz5pG<br>
=3DlNAp<br>
<div><div>-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/scim" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/scim</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><=
span style=3D"font-family:'Lucida Grande',Tahoma,Arial,Verdana,sans-serif;fo=
nt-size:10px;color:rgb(42,42,42)"><font color=3D"#343634" face=3D"Tahoma" st=
yle=3D"color:rgb(52,54,52);font-size:12px"><strong><span>Pamela Dingle</span=
></strong>&nbsp;&nbsp;|&nbsp;&nbsp;<span>Sr. Technical Architect</span></fon=
t><br>


<font face=3D"Arial" style=3D"font-size:11px"><font color=3D"#343634" face=3D=
"Tahoma"><strong>Ping</strong></font><font color=3D"#E71939" face=3D"Tahoma"=
><strong>Identity</strong></font>&nbsp;&nbsp;|&nbsp;&nbsp; <a href=3D"http:/=
/www.pingidentity.com" target=3D"_blank">www.pingidentity.com</a><br>


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -=
 -<br><font color=3D"#005568"><strong>O:</strong></font>&nbsp;<font color=3D=
"#343634"><span><a href=3D"tel:303-999-5890" value=3D"+13039995890" target=3D=
"_blank">303-999-5890</a></span></font>&nbsp;&nbsp;&nbsp;<font color=3D"#005=
568"><strong>M:</strong></font>&nbsp;<font color=3D"#343634"><span><a href=3D=
"tel:303-999-5890" value=3D"+13039995890" target=3D"_blank">303-999-5890</a>=
</span></font><br>


<font color=3D"#005568"><strong>Email:</strong></font>&nbsp;<span><a href=3D=
"mailto:pdingle@pingidentity.com" target=3D"_blank">pdingle@pingidentity.com=
</a></span><br>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -=
 - - - - - - - - -<br>


<table cellpadding=3D"0" cellspacing=3D"0"><tbody><tr valign=3D"top"><td now=
rap=3D""><div style=3D"float:left"><font face=3D"Arial" style=3D"font-size:1=
1px"><font color=3D"#005568"><strong>Connect with Ping</strong></font><br><f=
ont color=3D"#000000">Twitter: @pingidentity</font><br>


<font color=3D"#000000">LinkedIn Group: Ping's Identity Cloud</font>&nbsp;&n=
bsp; &nbsp;<br><font color=3D"#000000"><a href=3D"http://Facebook.com/pingid=
entitypage">Facebook.com/pingidentitypage</a></font></font></div></td><td no=
wrap=3D""><div style=3D"margin-left:20px"><font face=3D"Arial" style=3D"font=
-size:11px"><font color=3D"#005568"><strong><span>Connect with me</span></st=
rong></font><br>


<font color=3D"#000000"><span>Twitter: @pamelarosiedee</span></font><br><fon=
t color=3D"#000000"><span></span></font></font></div></td></tr></tbody></tab=
le></font></span><br>
</div>
</div></blockquote></body></html>=

--Apple-Mail-1744E3AB-1CFC-489B-B63D-A32EBF81BAAC--

From lear@cisco.com  Sun Oct 21 01:54:02 2012
Return-Path: <lear@cisco.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 B92FC21F8A52 for <scim@ietfa.amsl.com>; Sun, 21 Oct 2012 01:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.741
X-Spam-Level: 
X-Spam-Status: No, score=-110.741 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 4oaPPzPwuwXx for <scim@ietfa.amsl.com>; Sun, 21 Oct 2012 01:54:01 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id D250C21F89C2 for <scim@ietf.org>; Sun, 21 Oct 2012 01:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6341; q=dns/txt; s=iport; t=1350809642; x=1352019242; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=NVL0wNkxbSoc8AD5bdfS+qb/dTiToS7mMj8P2wgx94s=; b=SY/76yATdLkT7wOWlhEUNWKmwH8UJkMn+Sp7OM3E4hQ89KclTF3N6haf odovPVuOib6eLGgh6An8meraLkByWTuTP5xra53t/et0FvkPq+ShA1EEp BG1xLWiTeBGYM0qGJHH/cqoNeDb01y423HBBzQdQECYca+ZPenv+sl5Wv o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskFAOa3g1CrRDoG/2dsb2JhbABEhhSFX7UcgQiCIAEBAQMBEgEQVQEFCwshFgsCAgkDAgECAUUGDQEHAQEeh1wFm16NIZFfkTyBEgOVcY5OgWuCcQ
X-IronPort-AV: E=Sophos;i="4.80,625,1344211200"; d="scan'208,217";a="61896475"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 21 Oct 2012 08:53:53 +0000
Received: from elear-mac.local ([10.21.74.215]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q9L8rqvN017247; Sun, 21 Oct 2012 08:53:52 GMT
Message-ID: <5083B820.8070604@cisco.com>
Date: Sun, 21 Oct 2012 10:53:52 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Leif Johansson <leifj@mnt.se>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se> <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net> <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se> <00C069FD01E0324C9FFCADF539701DB32EBE9D72@ex2k10mb2.corp.yaanatech.com> <508159AA.4080809@mnt.se> <CANBMvsD63J4jALe6ULKREtzTZfdoebEXnvNUpQ=boJuUeqw6Fw@mail.gmail.com> <6199A469-707B-4647-AFE7-B0BE1855242C@mnt.se>
In-Reply-To: <6199A469-707B-4647-AFE7-B0BE1855242C@mnt.se>
X-Enigmail-Version: 1.4.5
Content-Type: multipart/alternative; boundary="------------050202090204020007050108"
Cc: Pam Dingle <pdingle@pingidentity.com>, "scim@ietf.org" <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: Sun, 21 Oct 2012 08:54:02 -0000

This is a multi-part message in MIME format.
--------------050202090204020007050108
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Leif,

Now I am even MORE confused.  Please see below:

On 10/20/12 2:07 PM, Leif Johansson wrote:

> Like any group or individual who decide
> to propose something to a wg, this design
> ream will produce I-Ds that the wg will
> choose to adopt or not.

I don't understand.  How would such drafts relate to the existing wg drafts?

>
> The purpose of this exercise is to get a
> focused technical discussion started, not
> to end or preempt one.
>
>>
>> Could somebody just catch us up and start a new thread with a brief
summary of what exact non-trivial work has been identified as necessary
prior to a 2.0 release?
>
> There is some good starting points in the
> presentations that Phil and Kelly made
> in Vancouver.

Again (and again), could you kindly be more specific?  I looked at those
presentations and the minutes and saw nothing in Kelly's presentation
that seemed like a question.  Phil has identified issues, but they seem
incremental.  I don't see Phil's presentation posted, and what I see
from the minutes is this:

> . should directories evolve to support scim? Also, directory vendors
>   getting requests for rest interfaces.  Will scim be the next
>   *directory* interface?
>
> . things impacting path uris: tenancy, targeting, "users" is too
>   general, object types ay expand, ability to query for any object
>   under /
>
> . the current search is under 'get' only - security concerns.  ability
>   to query using post?
>
> . rest "minimum" profile
>
> . add and replace - why not combine in put?  minor difference is
>   resource identifier
>
> . why not rework post to accommodate query and bulk?  What's classic
>   REST?

And then a few items from others:
> Jon Bradley: PUT and POST are not the same.  we should probably try to
> fix the semantics rather than bend them.  keep the rest semantics
> clear.  
>
> Kent Watson: idempotence.
>
> Tony Nadalin:  agree on resource type.  shouldn't be in the uri.
> Looking at spec, don't see how to do multitenancy correctly with the
> urn path that's in there.  Okay place to start but shouldn't rush to
> put out 1.1 lest people adhere to that


And then the biggie raised by multiple people, but most notably Hannes
and Paul:
> axe xml[...]

So... are these issues the scope for the design team?  And it would seem
to me that their output should be a bunch of proposals to change the
existing drafts, right?

Eliot





--------------050202090204020007050108
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Leif,<br>
    <br>
    Now I am even MORE confused.  Please see below:<br>
    <br>
    On 10/20/12 2:07 PM, Leif Johansson wrote:<br>
    <span style="white-space: pre;"><br>
      &gt; Like any group or individual who decide<br>
      &gt; to propose something to a wg, this design<br>
      &gt; ream will produce I-Ds that the wg will<br>
      &gt; choose to adopt or not.<br>
    </span><br>
    I don't understand.  How would such drafts relate to the existing wg
    drafts?<br>
    <br>
    <span style="white-space: pre;">&gt;<br>
      &gt; The purpose of this exercise is to get a<br>
      &gt; focused technical discussion started, not<br>
      &gt; to end or preempt one.<br>
      &gt;<br>
      &gt;&gt;<br>
      &gt;&gt; Could somebody just catch us up and start a new thread
      with a brief summary of what exact non-trivial work has been
      identified as necessary prior to a 2.0 release? <br>
      &gt;<br>
      &gt; There is some good starting points in the<br>
      &gt; presentations that Phil and Kelly made <br>
      &gt; in Vancouver. <br>
    </span><br>
    Again (and again), could you kindly be more specific?  I looked at
    those presentations and the minutes and saw nothing in Kelly's
    presentation that seemed like a question.  Phil has identified
    issues, but they seem incremental.  I don't see Phil's presentation
    posted, and what I see from the minutes is this:<br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre>. should directories evolve to support scim? Also, directory vendors
  getting requests for rest interfaces.  Will scim be the next
  *directory* interface?

. things impacting path uris: tenancy, targeting, "users" is too
  general, object types ay expand, ability to query for any object
  under /

. the current search is under 'get' only - security concerns.  ability
  to query using post?

. rest "minimum" profile

. add and replace - why not combine in put?  minor difference is
  resource identifier

. why not rework post to accommodate query and bulk?  What's classic
  REST?</pre>
    </blockquote>
    <br>
    And then a few items from others:<br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre>Jon Bradley: PUT and POST are not the same.  we should probably try to
fix the semantics rather than bend them.  keep the rest semantics
clear.  

Kent Watson: idempotence.

Tony Nadalin:  agree on resource type.  shouldn't be in the uri.
Looking at spec, don't see how to do multitenancy correctly with the
urn path that's in there.  Okay place to start but shouldn't rush to
put out 1.1 lest people adhere to that</pre>
    </blockquote>
    <br>
    <br>
    And then the biggie raised by multiple people, but most notably
    Hannes and Paul:<br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre>axe xml[...]</pre>
    </blockquote>
    <br>
    So... are these issues the scope for the design team?  And it would
    seem to me that their output should be a bunch of proposals to
    change the existing drafts, right?<br>
    <br>
    Eliot<br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------050202090204020007050108--

From leifj@mnt.se  Sun Oct 21 03:57:26 2012
Return-Path: <leifj@mnt.se>
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 B539821F897D for <scim@ietfa.amsl.com>; Sun, 21 Oct 2012 03:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 NlBQQPsIicaf for <scim@ietfa.amsl.com>; Sun, 21 Oct 2012 03:57:25 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 59E4621F8915 for <scim@ietf.org>; Sun, 21 Oct 2012 03:57:25 -0700 (PDT)
Received: from [10.33.1.163] ([212.247.15.226]) (authenticated bits=0) by backup-server.nordu.net (8.14.5/8.14.3) with ESMTP id q9LAvCLa013900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Oct 2012 12:57:16 +0200 (CEST)
Message-ID: <5083D508.8050505@mnt.se>
Date: Sun, 21 Oct 2012 12:57:12 +0200
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <CA3B67220D628A4780D6FEB31F18A3E32379CB76@xmb-rcd-x08.cisco.com> <50766F04.6090901@gmx.net> <507691DB.1050204@mnt.se> <50802113.4040805@cisco.com> <5080FA48.40603@mnt.se> <97295FA4-5F5F-4E1B-BFF1-D5740BE93478@gmx.net> <98D0FB76-3CD2-4651-A315-9780D71B00A7@mnt.se> <00C069FD01E0324C9FFCADF539701DB32EBE9D72@ex2k10mb2.corp.yaanatech.com> <508159AA.4080809@mnt.se> <CANBMvsD63J4jALe6ULKREtzTZfdoebEXnvNUpQ=boJuUeqw6Fw@mail.gmail.com> <6199A469-707B-4647-AFE7-B0BE1855242C@mnt.se> <5083B820.8070604@cisco.com>
In-Reply-To: <5083B820.8070604@cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pam Dingle <pdingle@pingidentity.com>, "scim@ietf.org" <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: Sun, 21 Oct 2012 10:57:26 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> I don't understand.  How would such drafts relate to the existing
> wg drafts?

Ok bad choice of words.

What I meant to say was that the output of a design team doesn't
automatically get adopted by a WG.

_If_ they choose to write an I-D (say an I-D summarizing some
proposed changes) as input to the WG then that I-D doesn't
automatically get adopted.

I'm sorry if that was confusing.


> 
>> 
>> The purpose of this exercise is to get a focused technical
>> discussion started, not to end or preempt one.
>> 
>>> 
>>> Could somebody just catch us up and start a new thread with a
>>> brief
> summary of what exact non-trivial work has been identified as
> necessary prior to a 2.0 release?
>> 
>> There is some good starting points in the presentations that Phil
>> and Kelly made in Vancouver.
> 
> Again (and again), could you kindly be more specific?  I looked at
> those presentations and the minutes and saw nothing in Kelly's
> presentation that seemed like a question.  Phil has identified
> issues, but they seem incremental.  I don't see Phil's presentation
> posted, and what I see from the minutes is this:

Fair points but they should be answered by Kelly and Phil and others
who raised issues at the mic in Vancouver.

> 
>> . should directories evolve to support scim? Also, directory
>> vendors getting requests for rest interfaces.  Will scim be the
>> next *directory* interface?
>> 
>> . things impacting path uris: tenancy, targeting, "users" is too 
>> general, object types ay expand, ability to query for any object 
>> under /
>> 
>> . the current search is under 'get' only - security concerns.
>> ability to query using post?
>> 
>> . rest "minimum" profile
>> 
>> . add and replace - why not combine in put?  minor difference is 
>> resource identifier
>> 
>> . why not rework post to accommodate query and bulk?  What's
>> classic REST?
> 
> And then a few items from others:
>> Jon Bradley: PUT and POST are not the same.  we should probably
>> try to fix the semantics rather than bend them.  keep the rest
>> semantics clear.
>> 
>> Kent Watson: idempotence.
>> 
>> Tony Nadalin:  agree on resource type.  shouldn't be in the uri. 
>> Looking at spec, don't see how to do multitenancy correctly with
>> the urn path that's in there.  Okay place to start but shouldn't
>> rush to put out 1.1 lest people adhere to that
> 

This issue is an example of something that actually _may_ require a bit
of redesign.

> 
> And then the biggie raised by multiple people, but most notably
> Hannes and Paul:
>> axe xml[...]

as is this...

This list is a pretty good summary of what has been raised so far.

> 
> So... are these issues the scope for the design team?  And it would
> seem to me that their output should be a bunch of proposals to
> change the existing drafts, right?

I hope so.

	Cheers Leif

	

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCD1QgACgkQ8Jx8FtbMZnf0mQCfbGGB7VjEZtzCGTeCYtDuvtsB
sCIAoI/l8mdjyo402Ij2XJG0aHLtIJnr
=MDM2
-----END PGP SIGNATURE-----

From laszlo.hordos@gmail.com  Sun Oct 28 03:57:46 2012
Return-Path: <laszlo.hordos@gmail.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 2A18E21F84FC for <scim@ietfa.amsl.com>; Sun, 28 Oct 2012 03:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.398
X-Spam-Level: 
X-Spam-Status: No, score=-0.398 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_LOW=-1]
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 RQZMS2Zu6pdE for <scim@ietfa.amsl.com>; Sun, 28 Oct 2012 03:57:45 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2135B21F85CB for <scim@ietf.org>; Sun, 28 Oct 2012 03:57:41 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so2180580wgb.13 for <scim@ietf.org>; Sun, 28 Oct 2012 03:57:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; bh=Jnb+RPMpqZbdmpHzKgP2KwrmZva1xvUGrI4prBSA9Y4=; b=wKTUlnbYbBK/qiv5Vp3ALTlYFUPiDSbel6p5lZP3MO1fha1Ha/0eEdncBMPusdNL7R OUOZrv+ziZI98c8O+jdC8kw5ebIceu0qSxyQbcyjDa58jhcl6X6fSIOqEYk7TY13LMIZ pTo/StlCv7KIaXzvanmdC022uehJ2+3vfC3Djo8ksAal6lZqDSrwDlgAGwwYiY68zsa+ sKGwdINAvgq0A5PXMYsx+688q2Ahn5gWjitKgUhGhU0GoFdBImY5+yRTf++MvkC8YGgB H+cScfV3fS+jkxlzFmMHFfjxaAf+92V4kq/COvtED2HfWLHVJZqYpZLAUdvjursQkRUu w78A==
Received: by 10.216.203.1 with SMTP id e1mr15783730weo.103.1351421860838; Sun, 28 Oct 2012 03:57:40 -0700 (PDT)
Received: from [172.16.2.30] (83.229.6.109.rev.sfr.net. [109.6.229.83]) by mx.google.com with ESMTPS id bn7sm6313491wib.8.2012.10.28.03.57.37 (version=SSLv3 cipher=OTHER); Sun, 28 Oct 2012 03:57:39 -0700 (PDT)
From: Laszlo Hordos <laszlo.hordos@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-75--547501003
Date: Sun, 28 Oct 2012 11:57:33 +0100
In-Reply-To: <mailman.68.1350846031.12905.scim@ietf.org>
To: scim@ietf.org
References: <mailman.68.1350846031.12905.scim@ietf.org>
Message-Id: <743A5B7F-47C0-4EE6-9CFA-5A0E90832BEC@gmail.com>
X-Mailer: Apple Mail (2.1085)
Subject: [scim] Filtering and the missing NOT operator
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: Sun, 28 Oct 2012 10:57:46 -0000

--Apple-Mail-75--547501003
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all!

I'm reading the 3.2.2.1. Filtering section in the API specification and =
I have some questions because I miss some filter operators. I noticed =
the priority is not on the filtering now and the specifications states =
"Providers MAY support additional filter operations if they choose." so =
It's all fine but what I miss is the way to negate.

There is a way for Boolean expressions:

[attributeName|required] [standard or custom attribute =
operator|required] [value|optional]

There is a way for the two logical AND, OR operators

[expression|required] [logical AND, OR operator|required] =
[expression|required]

I can not figure out any way to negate the filter condition. Have a =
negative boolean operator for each standard operator does not solves the =
problem of logical operator.=20

eq (equal) =3D> neq (not equal) =20
co (contains) =3D> nco (not contains)
etc.

How about negating? How to find all active user who is not Employee or =
Contractor?

active eq true and not(userType eq "Employee"  or userType eq =
"Contractor")

If I may suggest I'd like to see the not as part of the core =
specification because then the missing operators can follow the same =
patterns.

Regards,
Laszlo Hordos=20



--Apple-Mail-75--547501003
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi all!<div><br></div><div>I'm =
reading the&nbsp;<a =
href=3D"http://tools.ietf.org/id/draft-ietf-scim-api-00.html#rfc.section.3=
.2.2.1">3.2.2.1.&nbsp;Filtering</a>&nbsp;section in the API =
specification and I have some questions because I miss some filter =
operators. I noticed the priority is not on the filtering now and the =
specifications states "Providers MAY support additional filter =
operations if they choose." so It's all fine but what I miss is the way =
to negate.</div><div><br></div><div>There is a way for Boolean =
expressions:</div><div><br></div><div>[attributeName|required] [standard =
or custom attribute operator|required] =
[value|optional]</div><div><br></div><div>There is a way for the two =
logical AND, OR operators</div><div><br></div><div>[expression|required] =
[logical AND, OR =
operator|required]&nbsp;[expression|required]</div><div><br></div><div>I =
can not figure out any way to negate the filter condition. Have a =
negative boolean operator for each standard operator does not solves the =
problem of logical operator.&nbsp;</div><div><br></div><div>eq (equal) =
=3D&gt; neq (not equal) &nbsp;</div><div>co (contains) =3D&gt; nco (not =
contains)</div><div>etc.</div><div><br></div><div>How about negating? =
How to find all active user who is not Employee or =
Contractor?</div><div><br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;"><div><div><i>active eq true and <b>not</b>(userType =
eq "Employee"&nbsp;&nbsp;or userType eq =
"Contractor")</i></div></div></blockquote><div><br></div><div>If I may =
suggest I'd like to see the <b>not</b> as part of the core specification =
because then the missing operators can follow the same =
patterns.</div><div><br></div><div>Regards,</div><div>Laszlo =
Hordos&nbsp;</div><div><br></div><div><br></div></body></html>=

--Apple-Mail-75--547501003--

From trey.drake@unboundid.com  Mon Oct 29 08:43:40 2012
Return-Path: <trey.drake@unboundid.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 A903A21F86E1 for <scim@ietfa.amsl.com>; Mon, 29 Oct 2012 08:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 W3r6cfSxDGeE for <scim@ietfa.amsl.com>; Mon, 29 Oct 2012 08:43:40 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id DBB5121F862D for <scim@ietf.org>; Mon, 29 Oct 2012 08:43:39 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so5322531obq.31 for <scim@ietf.org>; Mon, 29 Oct 2012 08:43:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version:x-mailer :x-gm-message-state; bh=kKrHuSHhJ1OwvjarICw2Y9KOZwkvUMANm6wmxsWZHkQ=; b=gMDlAdZvUA6m6kLtLX8lr9U/nETdPRPK6fDlJEi8j49cxHh6JjPdRxaewfhRTSG4lx EoFO7oEcBGw5fU1dwN0Ul3YXurwm7ngtpwgHkSXxOSZGsnKhvG1QfhCjb9LwrO2fa/z2 6bGNdIbZJhFhumorLYiTqG2yYQp0v4II7pzNTXco+FBMbkocX4qnxEDxpp+GLP9iHTay Kc1YcDSo3BKpF+v5WF0BACDwRw7/M8aDSePxEcbv0gVJYXr2wnp0O/tA9kqXBr+j2EA5 gAgS43USLYcAefcqOWv6KmrmNYr0jE6xTnZx33TQLBwOYexrNOEoUWVW1LrcmIUjeimu W6Aw==
Received: by 10.182.38.69 with SMTP id e5mr25463809obk.79.1351525419517; Mon, 29 Oct 2012 08:43:39 -0700 (PDT)
Received: from [192.168.241.44] (24-155-184-100.static.grandenetworks.net. [24.155.184.100]) by mx.google.com with ESMTPS id z10sm7635447oed.12.2012.10.29.08.43.37 (version=SSLv3 cipher=OTHER); Mon, 29 Oct 2012 08:43:38 -0700 (PDT)
From: Trey Drake <trey.drake@unboundid.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0EC965FD-2AF6-4892-B609-11EAC1A42A61"
Message-Id: <50D435B3-766A-4473-A4A6-E09B27BACFBB@unboundid.com>
Date: Mon, 29 Oct 2012 10:43:37 -0500
To: "scim@ietf.org Management" <scim@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQnOXO9Rlb1D5WMwU503hWWrYqSnyDwrLyCmtAPv8HTQ6xR9S109/Ytn/X1qkNKVbgIZ82qt
Subject: [scim] Design Team Status
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: Mon, 29 Oct 2012 15:43:40 -0000

--Apple-Mail=_0EC965FD-2AF6-4892-B609-11EAC1A42A61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

The design team has identified and is actively working the following =
issues:

Schema:
- Object relationship (children objects?)
- Keep existing info model or adopt other.  vCard is in the running.  =
Key consideration is extensibility.
- Remove XML data model. Spec JSON only?
- Metadata on each attribute (possibly on each value). Provides the =
ability to set meta-data describing an attribute's: creation date , =
expiry date, source,  if verified, etc.=20
- Attribute value case preservation (e.g. ExternalID). Must the service =
provider respect the consumer case sensitivity?  Problematic w.r.t. =
indexing, et al.=20
- Entitlements =96 remove from spec and make it extension or define =
basic model

API:
- Re-visit the API.  Should we further elaborate the API/response so =
that it is more Graph like a la oData? For example, embed Group/user =
relationship/references? =20
- Multi-Tenancy clarifications
- REST pattern (URL modeling, filter semantics, object naming rules)
- Patch improvements/cleanup
- Query/filter semantics improvements: return only values that match the =
query (not all values =96 ex. Search for groups with member foo, but =
only return member foo and not all members), negation
- Search query parameters via GET URL vs. post?  If POST there is a case =
to be made to introduce a search operation; e.g., X-SEARCH vs GET =
overloading
- Password management and policy =96 should this be spec'd now, later or =
simply handle as an extension?

Thanks,
Trey=

--Apple-Mail=_0EC965FD-2AF6-4892-B609-11EAC1A42A61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; ">The design =
team has identified and is actively working the following =
issues:</div><div style=3D"font-family: Calibri, sans-serif; font-size: =
14px; "><br></div><div style=3D"font-family: Calibri, sans-serif; =
font-size: 14px; ">Schema:</div><div style=3D"font-family: Calibri, =
sans-serif; font-size: 14px; ">- Object relationship (children =
objects?)</div><div style=3D"font-family: Calibri, sans-serif; =
font-size: 14px; "><div>- Keep existing info model or adopt other. =
&nbsp;vCard is in the running. &nbsp;Key consideration is =
extensibility.</div><div>- Remove XML data model. Spec JSON =
only?</div><div>- Metadata on each attribute (possibly on each value). =
Provides the ability to set meta-data describing an attribute's: =
creation date , expiry date, source, &nbsp;if verified, =
etc.&nbsp;</div><div>- Attribute value case preservation (e.g. =
ExternalID). Must the service provider respect the consumer case =
sensitivity? &nbsp;Problematic w.r.t. indexing, et al.&nbsp;</div><div>- =
Entitlements =96 remove from spec and make it extension or define basic =
model</div></div><div style=3D"font-family: Calibri, sans-serif; =
font-size: 14px; "><br></div><div style=3D"font-family: Calibri, =
sans-serif; font-size: 14px; ">API:</div><div style=3D"font-family: =
Calibri, sans-serif; font-size: 14px; "><div>- Re-visit the API. =
&nbsp;Should we further elaborate the API/response so that it is more =
Graph like a la oData? For example, embed Group/user =
relationship/references? &nbsp;</div><div>- Multi-Tenancy =
clarifications</div></div><div style=3D"font-family: Calibri, =
sans-serif; font-size: 14px; ">- REST pattern (URL modeling, filter =
semantics, object naming rules)</div><div style=3D"font-family: Calibri, =
sans-serif; font-size: 14px; ">- Patch improvements/cleanup</div><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; ">- =
Query/filter semantics improvements:&nbsp;return only values that match =
the query (not all values =96 ex. Search for groups with member foo, but =
only return member foo and not all members), negation</div><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; "><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; "></span>- Search =
query parameters via GET URL vs. post?&nbsp; If POST there is a case to =
be made to introduce a search operation; e.g., X-SEARCH vs GET =
overloading</div><div style=3D"font-family: Calibri, sans-serif; =
font-size: 14px; ">- Password management and policy =96 should this be =
spec'd now, later or simply handle as an extension?</div><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
"><br></div><div style=3D"font-family: Calibri, sans-serif; font-size: =
14px; ">Thanks,</div><div style=3D"font-family: Calibri, sans-serif; =
font-size: 14px; ">Trey</div></body></html>=

--Apple-Mail=_0EC965FD-2AF6-4892-B609-11EAC1A42A61--

From bjorn.aannestad@unboundid.com  Mon Oct 29 16:00:23 2012
Return-Path: <bjorn.aannestad@unboundid.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 2B22521F8562 for <scim@ietfa.amsl.com>; Mon, 29 Oct 2012 16:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 JRKVaI4CI3q5 for <scim@ietfa.amsl.com>; Mon, 29 Oct 2012 16:00:22 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE4221F865B for <scim@ietf.org>; Mon, 29 Oct 2012 16:00:22 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n5so5869280oag.31 for <scim@ietf.org>; Mon, 29 Oct 2012 16:00:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-forwarded-message-id:content-type:x-gm-message-state; bh=baD1AJAPHGpq+g66c8q6KaRJMv4xQbZpM6BTU68AsE0=; b=oXRkanZPb8crxwzTnby/xPOGgCc+0gp8RJEbHFPF2186TjfbNsLAS3Vrb2frYze2Kh Rkf/gOrP0U4pTsmlYxPQQ8AX5/CEujebe4gDcLEOlSpInlqQpbe40A7rHyi4TPYoc1B6 yzraEeZGoqGRf2uS8kczGfzEwDo/vhgNG//YKTsNG2ZfZxg4yS5ACzIegpG9d+W8QwXW pPWEVQtpsxBtR+wuWvpR1JuP9znNqc9h51dBrRfujtpqVZQl4svJ35SqXZQpn0WQYurV P7RiMcFYoCie4BJijlz3LFoLiVzWVwNmMv6YVPc97gR38+Gh0lkf90MhhqIdqYT3OTm1 Fkjg==
Received: by 10.182.64.114 with SMTP id n18mr14132258obs.95.1351551621618; Mon, 29 Oct 2012 16:00:21 -0700 (PDT)
Received: from [10.8.1.253] (24-155-184-100.static.grandenetworks.net. [24.155.184.100]) by mx.google.com with ESMTPS id bd5sm10941557obb.5.2012.10.29.16.00.19 (version=SSLv3 cipher=OTHER); Mon, 29 Oct 2012 16:00:20 -0700 (PDT)
Message-ID: <508F0A80.40004@unboundid.com>
Date: Mon, 29 Oct 2012 18:00:16 -0500
From: Bjorn Aannestad <bjorn.aannestad@unboundid.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: scim WG <scim@ietf.org>
References: <508EB590.6020706@unboundid.com>
In-Reply-To: <508EB590.6020706@unboundid.com>
X-Forwarded-Message-Id: <508EB590.6020706@unboundid.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms000209050806050904090100"
X-Gm-Message-State: ALoCoQkc5QQ2gYfQ4gZQAQNJMQXLEZ+fGiRgX+f5yq2Rw9WWTy2DzqHzIrN7YnnanXWu+w1mWpBE
Subject: Re: [scim] Design Team Status
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: Mon, 29 Oct 2012 23:00:23 -0000

This is a cryptographically signed message in MIME format.

--------------ms000209050806050904090100
Content-Type: multipart/mixed;
 boundary="------------030701090100080900010707"

This is a multi-part message in MIME format.
--------------030701090100080900010707
Content-Type: multipart/alternative;
 boundary="------------040305080202020500000003"


--------------040305080202020500000003
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable



Here's my attempt to turn these into new, specific items for the issues=20
tracker.   Take this as a proposal for issue titles.  Then, the=20
discussions on the merits and details of each can proceed.

Object relationships:
- Should the spec define how to create and traverse parent-child=20
relationships and/or arbitrary relationships, or stay as-is?

Keep existing info model or adopt other.
- Should the spec adopt the vCard  model?
- Should the spec define a "human person" resource, and then define and=20
allow "user" and other derived types?
- Should the spec define an "application" resource, for use e.g. with=20
OAuth client provisioning?

Entitlements:
- Should the spec define a basic model for entitlements?  If so, define=20
it (existing Issue #11).

Meta-data:
- Should the spec define metadata on each attribute?  If so what is=20
standard and what is extended?

Query improvements
- Define support for a negation operator in queries
- Define a method for retrieving a resource when its type is not known,=20
only its id
- Allow queries to return only values that match the query (Search for=20
groups with member foo, but only return member foo and not all members)

Passwords  (overlaps existing issue #14)
- Should there be an extension for Password Management and Policies?  If =
so,
     - Method for retrieving machine-readable password rules defined by=20
the provider?
     - Define attributes of "User" for password & log in metadata
     - Method(s) for password expiration flows (both pre- and=20
post-expiration)?
     - Method for requiring and sending current password with a password =

reset
     - Method for verifying that a new or changed password matches rules =

defined by the provider
     - Method for checking that a client-supplied password matches the=20
one stored by the provider


Other
- After group approval, remove requirement to support XML
- Propose text to address case preservation
- Propose text to clarify the spec position on multi-tenancy
- Propose text to improve/clean up PATCH operation (existing issue #18)
- Propose text to resolve search query parameters via GET URL or POST


REST pattern (URL modeling, filter semantics, object naming rules)
- I'm not sure what the specific issues are in this one.

-Bjorn

On 10/29/2012 10:43, Trey Drake wrote:
> The design team has identified and is actively working the following=20
> issues:
>
> Schema:
> - Object relationship (children objects?)
> - Keep existing info model or adopt other.  vCard is in the running.=20
>  Key consideration is extensibility.
> - Remove XML data model. Spec JSON only?
> - Metadata on each attribute (possibly on each value). Provides the=20
> ability to set meta-data describing an attribute's: creation date ,=20
> expiry date, source,  if verified, etc.
> - Attribute value case preservation (e.g. ExternalID). Must the=20
> service provider respect the consumer case sensitivity?  Problematic=20
> w.r.t. indexing, et al.
> - Entitlements =E2=80=93 remove from spec and make it extension or defi=
ne=20
> basic model
>
> API:
> - Re-visit the API.  Should we further elaborate the API/response so=20
> that it is more Graph like a la oData? For example, embed Group/user=20
> relationship/references?
> - Multi-Tenancy clarifications
> - REST pattern (URL modeling, filter semantics, object naming rules)
> - Patch improvements/cleanup
> - Query/filter semantics improvements: return only values that match=20
> the query (not all values =E2=80=93 ex. Search for groups with member f=
oo, but=20
> only return member foo and not all members), negation
> - Search query parameters via GET URL vs. post?  If POST there is a=20
> case to be made to introduce a search operation; e.g., X-SEARCH vs GET =

> overloading
> - Password management and policy =E2=80=93 should this be spec'd now, l=
ater or=20
> simply handle as an extension?
>
> Thanks,
> Trey
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim


--=20
__________________________________________________________
Bjorn Aannestad | Dir, Product Management | UnboundID Corp
mailto:bjorn@unboundid.com  | 512-769-6461





--------------040305080202020500000003
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    <div class=3D"moz-forward-container"><br>
      <div class=3D"moz-cite-prefix"> Here's my attempt to turn these int=
o
        new, specific items for the issues tracker. =C2=A0 Take this as a=

        proposal for issue titles.=C2=A0 Then, the discussions on the mer=
its
        and details of each can proceed.<br>
        <br>
        Object relationships:=C2=A0 <br>
        - Should the spec define how to create and traverse parent-child
        relationships and/or arbitrary relationships, or stay as-is?<br>
        <br>
        Keep existing info model or adopt other. <br>
        - Should the spec adopt the vCard=C2=A0 model?<br>
        - Should the spec define a "human person" resource, and then
        define and allow "user" and other derived types? <br>
        - Should the spec define an "application" resource, for use e.g.
        with OAuth client provisioning?<br>
        <br>
        Entitlements:<br>
        - Should the spec define a basic model for entitlements?=C2=A0 If=
 so,
        define it (existing Issue #11).<br>
        <br>
        Meta-data:<br>
        - Should the spec define metadata on each attribute?=C2=A0 If so =
what
        is standard and what is extended?=C2=A0 <br>
        <br>
        Query improvements<br>
        - Define support for a negation operator in queries<br>
        - Define a method for retrieving a resource when its type is not
        known, only its id<br>
        - Allow queries to return only values that match the query
        (Search for groups with member foo, but only return member foo
        and not all members)<br>
        <br>
        Passwords=C2=A0 (overlaps existing issue #14)<br>
        - Should there be an extension for Password Management and
        Policies?=C2=A0 If so,<br>
        =C2=A0=C2=A0=C2=A0 - Method for retrieving machine-readable passw=
ord rules
        defined by the provider? <br>
        =C2=A0=C2=A0=C2=A0 - Define attributes of "User" for password &am=
p; log in
        metadata<br>
        =C2=A0=C2=A0=C2=A0 - Method(s) for password expiration flows (bot=
h pre- and
        post-expiration)?<br>
        =C2=A0=C2=A0=C2=A0 - Method for requiring and sending current pas=
sword with a
        password reset<br>
        =C2=A0=C2=A0=C2=A0 - Method for verifying that a new or changed p=
assword
        matches rules defined by the provider<br>
        =C2=A0=C2=A0=C2=A0 - Method for checking that a client-supplied p=
assword
        matches the one stored by the provider <br>
        <br>
        <br>
        Other<br>
        - After group approval, remove requirement to support XML<br>
        - Propose text to address case preservation<br>
        - Propose text to clarify the spec position on multi-tenancy<br>
        - Propose text to improve/clean up PATCH operation (existing
        issue #18)<br>
        - Propose text to resolve search query parameters via GET URL or
        POST<br>
        <br>
        <br>
        REST pattern (URL modeling, filter semantics, object naming
        rules)<br>
        - I'm not sure what the specific issues are in this one.<br>
        <br>
        -Bjorn<br>
        <br>
        On 10/29/2012 10:43, Trey Drake wrote:<br>
      </div>
      <blockquote
        cite=3D"mid:50D435B3-766A-4473-A4A6-E09B27BACFBB@unboundid.com"
        type=3D"cite">
        <meta http-equiv=3D"Content-Type" content=3D"text/html;
          charset=3DUTF-8">
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">The

          design team has identified and is actively working the
          following issues:</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
"><br>
        </div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">Schema:</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">-
          Object relationship (children objects?)</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">
          <div>- Keep existing info model or adopt other. =C2=A0vCard is =
in
            the running. =C2=A0Key consideration is extensibility.</div>
          <div>- Remove XML data model. Spec JSON only?</div>
          <div>- Metadata on each attribute (possibly on each value).
            Provides the ability to set meta-data describing an
            attribute's: creation date , expiry date, source, =C2=A0if
            verified, etc.=C2=A0</div>
          <div>- Attribute value case preservation (e.g. ExternalID).
            Must the service provider respect the consumer case
            sensitivity? =C2=A0Problematic w.r.t. indexing, et al.=C2=A0<=
/div>
          <div>- Entitlements =E2=80=93 remove from spec and make it exte=
nsion
            or define basic model</div>
        </div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
"><br>
        </div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">API:</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">
          <div>- Re-visit the API. =C2=A0Should we further elaborate the
            API/response so that it is more Graph like a la oData? For
            example, embed Group/user relationship/references? =C2=A0</di=
v>
          <div>- Multi-Tenancy clarifications</div>
        </div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">-
          REST pattern (URL modeling, filter semantics, object naming
          rules)</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">-
          Patch improvements/cleanup</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">-
          Query/filter semantics improvements:=C2=A0return only values th=
at
          match the query (not all values =E2=80=93 ex. Search for groups=
 with
          member foo, but only return member foo and not all members),
          negation</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
"><span
            class=3D"Apple-tab-span" style=3D"white-space: pre; "></span>=
-
          Search query parameters via GET URL vs. post?=C2=A0 If POST the=
re
          is a case to be made to introduce a search operation; e.g.,
          X-SEARCH vs GET overloading</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">-
          Password management and policy =E2=80=93 should this be spec'd =
now,
          later or simply handle as an extension?</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
"><br>
        </div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">Thanks,</div>
        <div style=3D"font-family: Calibri, sans-serif; font-size: 14px; =
">Trey</div>
        <br>
        <fieldset class=3D"mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap=3D"">_______________________________________________
scim mailing list
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:scim@ietf.org">scim@ietf.org</a>
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" href=3D"https=
://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listi=
nfo/scim</a>
</pre>
      </blockquote>
      <br>
      <br>
      <pre class=3D"moz-signature" cols=3D"72">--=20
__________________________________________________________
Bjorn Aannestad | Dir, Product Management | UnboundID Corp
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" href=3D"mailt=
o:bjorn@unboundid.com">mailto:bjorn@unboundid.com</a> | 512-769-6461</pre=
>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------040305080202020500000003--

--------------030701090100080900010707
Content-Type: text/x-vcard; charset=utf-8;
 name="bjorn_aannestad.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="bjorn_aannestad.vcf"

YmVnaW46dmNhcmQNCmZuOkJqb3JuIEFhbm5lc3RhZA0KbjpBYW5uZXN0YWQ7Qmpvcm4NCm9y
ZzpVbmJvdW5kSUQNCmVtYWlsO2ludGVybmV0OmJqb3JuQHVuYm91bmRpZC5jb20NCnRpdGxl
OkRpcmVjdG9yLCBQcm9kdWN0IE1hbmFnZW1lbnQNCnRlbDt3b3JrOjUxMiA2MDAgNzc1Mw0K
dGVsO2NlbGw6NTEyIDc2OSA2NDYxDQpub3RlOnNreXBlOiBiam9ybl9hYW5uZXN0YWQNCnZl
cnNpb246Mi4xDQplbmQ6dmNhcmQNCg0K
--------------030701090100080900010707--

--------------ms000209050806050904090100
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMUjCC
BVwwggREoAMCAQICECStp7X80wzNJ6GfICadV/cwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz
aWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG
A1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAe
Fw0xMjAyMjMwMDAwMDBaFw0xMzAyMjIyMzU5NTlaMIIBHzEXMBUGA1UEChMOVmVyaVNpZ24s
IEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52
ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMp
OTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJ
RCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMRgwFgYDVQQDFA9Cam9ybiBBYW5u
ZXN0YWQxLDAqBgkqhkiG9w0BCQEWHWJqb3JuLmFhbm5lc3RhZEB1bmJvdW5kaWQuY29tMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw+4r+Le4uODrErBgJsA7UoexcjH/r2Ds
62wKyDCY5CQfOFMROnynV9GWWXp8zmCj7/N9I2hOU7poaqR4kkJjoiKiNHQdVfyM1yFZTurW
AV5PCT5NouiqlruJDM6s2HV3B7mSRhtHFOSfhiDP+/kHf/JEdFJ7zEPaP0Kuy8XKpPR5nVCz
k4zFKPBc4T9+HAlXeGY1PnwOsxPEevZlHOTThF9RunZu5Z/uaObR2JplM6KxXDfXNRjSkmK7
6kW8wFC1C0GleHKfM85nQTvVicuSK4GbbvhMjqovMtUIR1SNG8vsmTvU4PY9G/WkDM4Ge/97
phIcQIm9W/DXjC78wBfa/QIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5Bgtg
hkgBhvhFAQcXATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBh
MAsGA1UdDwQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkw
RzBFoEOgQYY/aHR0cDovL2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5k
QzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQC345zS3026vrJVysBCE3TN
BhQ4VlqRtwj5AcAXhhF2c3krlbgJRLV6STYky+/i7YRdezIZYgY2eo693dlIQUnkZMb6D2PL
dRs1Lgw4NJKB+WGLGkmyV8YqqKrTm/ZbPdl/+Y4Pc88DLcYEmr0OsEDel8LqLPpongUDnGU5
2wxAvaHn9sZ4nyDa3bAy9RyqrAdWhsfRttlgAbvMeHSXhvDa63AbdGdZbzBfqGpBTYZJqrA/
fzcbVZQIw7ULW0YRpUNx8bmmgxFd5ovdDVZnfiKNd7QHy+BcTQgfxLYsBYZhICz1ud1QKn88
pW944VjwHTzxyErX43AGoPYoZKA8b3XXMIIG7jCCBdagAwIBAgIQcRVmBUrkkSFN6bxE+azT
3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMTk5
OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxW
ZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5
IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5W
ZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6
ZYggCxET6ZvgSU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f
0jGyVBlzRmoZQhHsEnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Iba
k2f4MwOuGjxraXj2wCyO4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+
wbaULZeQLSfSux7pg2qE9sSyriMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ
6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBn
MGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNv
bS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTA0BgNV
HR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNV
HQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1hZ2UvZ2lmMCEwHzAH
BgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28udmVyaXNpZ24u
Y29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRlTGFiZWw0
LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHpMIHm
oYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWdu
LCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItb
dVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSo
WufYbAlMJBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6
jhmND0OojPKvYLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvi
d+zoK2Q1ds262uDRyxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5l
UkL7DojS7Uodv0vj+Mxy+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaM
xmgD5yKocwuxvKDaUljdCg5/wYIxggT5MIIE9QIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3Jw
YSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczAhAkrae1/NMMzSeh
nyAmnVf3MAkGBSsOAwIaBQCgggLbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEyMTAyOTIzMDAxNlowIwYJKoZIhvcNAQkEMRYEFNuBhXwbbzeAXF6OMx8B
hVcVJi5zMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICASgwggEDBgkrBgEEAYI3EAQxgfUwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkG
A1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMp
MDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMwIQJK2ntfzTDM0noZ8gJp1X
9zCCAQUGCyqGSIb3DQEJEAILMYH1oIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy
aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsT
MlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4w
HAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNz
IDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCECStp7X80wzNJ6GfICadV/cwDQYJ
KoZIhvcNAQEBBQAEggEAmP5tKNfcfRo41AxyC+iO9nMrxTCjETEauktUEF67WnZDZAJAx4H5
oJs3i3AoOFs57CPDMaoFxT33A9aHeN1T/9ike9K5SqA3UInMmmWy3uVjiIA1M4WWqGEKa2/7
4XUW7rRrk4pFUTRwAaVRIMJ6osTD0O06x+3uZWjRjJ8dRALi4qHi3hw5swH9tY0mXNtjMx6b
x0rO8BXBw0izvQ1+u9UnrAxlTPG4PKICyFdN5BW+ctUaOMIrrpKNMR9uHhLYGBOTgk5dQ0cz
LZGwv2J+1tMBPCbzGesFmeEIfQePYAnfoBvI5MKmhBX2jbIv6r31cdrRGTlVqrm1Z2xag4ej
VwAAAAAAAA==
--------------ms000209050806050904090100--

From melinda.shore@gmail.com  Mon Oct 29 16:50:00 2012
Return-Path: <melinda.shore@gmail.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 9031321F8678 for <scim@ietfa.amsl.com>; Mon, 29 Oct 2012 16:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 S7GpxF2k++Ia for <scim@ietfa.amsl.com>; Mon, 29 Oct 2012 16:50:00 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0872921F8650 for <scim@ietf.org>; Mon, 29 Oct 2012 16:50:00 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so4517785pbb.31 for <scim@ietf.org>; Mon, 29 Oct 2012 16:49:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=JPbOTjGYskixEZkZEYAlHNCAcPuf75St5nNAhlaDF9I=; b=J0b15pT7hN3JawpjhJB+NzHPoK9tT0gXWKZAmzCEwM+reeO46QDZyAyNpk/5AfUbHp 7BPNKGRGY36uDp3qCrJmni7xRnrTVYxQO1wHF2YtufE8a5wOZLTZGi1ybsjre0bj0iXU 9AvcQykUfye5UstQ3AwzHMQHiOMukX/4nGfUt6zAeF0P0qUEdiCFuYNQOmu781sX+Rnx r5X0vBCpoWMfhvgE6aVrY8IWGsct9arDAw3WsGf1z6mFZCSlwGc4qWdA+cwqUxqul13f jJKdIdDbez9HSCLCL8d+0VF9O5RrggfikLXJFpXeNOG0dhit5mEb7meyoFvf1EcCqtRD JBoQ==
Received: by 10.68.209.170 with SMTP id mn10mr97878863pbc.11.1351554599778; Mon, 29 Oct 2012 16:49:59 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id sf4sm6700437pbc.75.2012.10.29.16.49.58 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Oct 2012 16:49:58 -0700 (PDT)
Message-ID: <508F1624.3060205@gmail.com>
Date: Mon, 29 Oct 2012 15:49:56 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: scim@ietf.org
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com>
In-Reply-To: <508F0A80.40004@unboundid.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [scim] Design Team Status
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: Mon, 29 Oct 2012 23:50:00 -0000

On 10/29/12 3:00 PM, Bjorn Aannestad wrote:
> Here's my attempt to turn these into new, specific items for the issues
> tracker.   Take this as a proposal for issue titles.  Then, the
> discussions on the merits and details of each can proceed.

As a matter of process, anybody with an account can create tickets or
edit existing ones (not sure about closing them).  Allow me to suggest
that it's more productive to go ahead and create tickets than it is
to debate them first.  On the other hand, it's not a good thing to
get lost in a sea of tickets.

More generally, I'm not sure that having high-level design questions
in the ticket tracker is that productive - they should probably be
specific and on point.  "Remove requirement to support XML" is a good
ticket subject.  "Should the spec define how to create and traverse
parent-child relationships and/or arbitrary relationships, or stay
as-is?" is probably not great, but once a decision is made and if
it requires a change to the spec, "write text defining the creation and
traversal of parent-child relationships" is something that can be
done and be closed.

Melinda


From leifj@mnt.se  Tue Oct 30 03:10:18 2012
Return-Path: <leifj@mnt.se>
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 05F0721F8502 for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 03:10:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 dGCc8I6n-3PV for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 03:10:17 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 81E4221F8506 for <scim@ietf.org>; Tue, 30 Oct 2012 03:10:16 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so91609lbo.31 for <scim@ietf.org>; Tue, 30 Oct 2012 03:10:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=FEHUBq9iIa3FcGJPGqeRejuxZhgsAW4IdczX7GkmHVA=; b=cjy72mcsvOSpa6Qvpz6XefX1sF263sG2HRpPbzQVTRZnGnvrY7lcC1hrUGHAfMUZcb O4OcD8DLC+5A3OG3KtrfFMFELQyG+OBMvVC5m0DXpYa1k8OP2gR+Jqm8lO0t74QR6Kh+ PUHE7zwTVU0kYw6l43dmz+lEwPvZ55unXld20PaTVQE9jQVmNOwru0jmR0UDZkvbjr6v vHjhfyTDxPG+8mB1aCZ8cC1rKcxizkyTLMq6mZZGfkWEQPdjW5Kcbpgz7fPIiqMhBkwi FA8kQ15EM5ZtNTQIXkeKy1SAIFv/riDECY1MiVCxd4npHzAmFlrhjXZOuHB5g7E5Jh+T R26Q==
Received: by 10.112.37.41 with SMTP id v9mr4182137lbj.97.1351591815417; Tue, 30 Oct 2012 03:10:15 -0700 (PDT)
Received: from ?IPv6:2001:6b0:7:0:9d7a:1761:ad39:5305? ([2001:6b0:7:0:9d7a:1761:ad39:5305]) by mx.google.com with ESMTPS id nr2sm134815lab.5.2012.10.30.03.10.13 (version=SSLv3 cipher=OTHER); Tue, 30 Oct 2012 03:10:14 -0700 (PDT)
Message-ID: <508FA781.2060501@mnt.se>
Date: Tue, 30 Oct 2012 11:10:09 +0100
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: scim@ietf.org
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com>
In-Reply-To: <508F1624.3060205@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQmpGWvoRtnx5nkR7EfMDGBxMG1APPyNm95OfDyP7NMIuILlZKHSv50BrCoRqKRgVAtVQp0x
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 10:10:18 -0000

On 10/30/2012 12:49 AM, Melinda Shore wrote:
> On 10/29/12 3:00 PM, Bjorn Aannestad wrote:
>> Here's my attempt to turn these into new, specific items for the issues
>> tracker.   Take this as a proposal for issue titles.  Then, the
>> discussions on the merits and details of each can proceed.
> As a matter of process, anybody with an account can create tickets or
> edit existing ones (not sure about closing them).  Allow me to suggest
> that it's more productive to go ahead and create tickets than it is
> to debate them first.  On the other hand, it's not a good thing to
> get lost in a sea of tickets.
>
> More generally, I'm not sure that having high-level design questions
> in the ticket tracker is that productive - they should probably be
> specific and on point.  "Remove requirement to support XML" is a good
> ticket subject.  "Should the spec define how to create and traverse
> parent-child relationships and/or arbitrary relationships, or stay
> as-is?" is probably not great, but once a decision is made and if
> it requires a change to the spec, "write text defining the creation and
> traversal of parent-child relationships" is something that can be
> done and be closed.
>

Those are very good points. Lets make the tickets actionable!

From bjorn.aannestad@unboundid.com  Tue Oct 30 08:06:08 2012
Return-Path: <bjorn.aannestad@unboundid.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 1AF6F21F857C for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 08:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 wFHfAN76gWop for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 08:06:07 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7323721F8526 for <scim@ietf.org>; Tue, 30 Oct 2012 08:06:07 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n5so403497oag.31 for <scim@ietf.org>; Tue, 30 Oct 2012 08:06:07 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=NH6A/48IjW6P6/rCnlchHAAVIq7hSHwJWoBPfsBkAhQ=; b=UpRJ2qQjrvQf5XAR95ukm3pPrRq9who/T8cg/VxFsFc7hwCfQyv1GdkwOdJg00u1eY i7ByjlZoNaAzshiYrPKfckfaKBtBx63HnAiD0Cxti6CftdLDccB7/NbHLtmeRGb7/IuM 5JaxdqVBUFMbBLzs2hEMyvN/X0yO+EEz5OobJ8MOswPMbySRnKkgC6nc631qIR3EMAAI Lev08a+Z5GhGIKheNTuKRFRa86kScV15hXb09RkHFS++YL1p+L5gIwWIJkRv3UxCN8Dq WqrzWCRqhwDURuNRRgQP0F3IfeTn4DzQdg95ybHwsRWfRUMim/ZkmA4Lh6+kPkSuCVZ/ +EbQ==
Received: by 10.182.18.165 with SMTP id x5mr28412422obd.73.1351609566853; Tue, 30 Oct 2012 08:06:06 -0700 (PDT)
Received: from [10.8.1.249] (24-155-184-100.static.grandenetworks.net. [24.155.184.100]) by mx.google.com with ESMTPS id k8sm596446oee.11.2012.10.30.08.06.05 (version=SSLv3 cipher=OTHER); Tue, 30 Oct 2012 08:06:05 -0700 (PDT)
Message-ID: <508FECD8.7000008@unboundid.com>
Date: Tue, 30 Oct 2012 10:06:00 -0500
From: Bjorn Aannestad <bjorn.aannestad@unboundid.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com>
In-Reply-To: <508F1624.3060205@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030602010808000504030304"
X-Gm-Message-State: ALoCoQkjhSyszH6347Pr/Ol8jhiHJPmquPu1eGBuyz3E3Xqx5ccHZFfJUqcq9JOKd13tMTiRCnHV
Cc: scim@ietf.org
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 15:06:08 -0000

This is a cryptographically signed message in MIME format.

--------------ms030602010808000504030304
Content-Type: multipart/mixed;
 boundary="------------070101020008080409080407"

This is a multi-part message in MIME format.
--------------070101020008080409080407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable


Thanks for the guidance, Melinda -- that works for me.   Is there a=20
consensus on which items are ticket-worthy?  I'm happy to create some or =

all of them, as needed.

-Bjorn

On 10/29/2012 18:49, Melinda Shore wrote:
> On 10/29/12 3:00 PM, Bjorn Aannestad wrote:
>> Here's my attempt to turn these into new, specific items for the issue=
s
>> tracker.   Take this as a proposal for issue titles.  Then, the
>> discussions on the merits and details of each can proceed.
> As a matter of process, anybody with an account can create tickets or
> edit existing ones (not sure about closing them).  Allow me to suggest
> that it's more productive to go ahead and create tickets than it is
> to debate them first.  On the other hand, it's not a good thing to
> get lost in a sea of tickets.
>
> More generally, I'm not sure that having high-level design questions
> in the ticket tracker is that productive - they should probably be
> specific and on point.  "Remove requirement to support XML" is a good
> ticket subject.  "Should the spec define how to create and traverse
> parent-child relationships and/or arbitrary relationships, or stay
> as-is?" is probably not great, but once a decision is made and if
> it requires a change to the spec, "write text defining the creation and=

> traversal of parent-child relationships" is something that can be
> done and be closed.
>
> Melinda
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim


--=20
__________________________________________________________
Bjorn Aannestad | Dir, Product Management | UnboundID Corp
mailto:bjorn@unboundid.com | 512-769-6461


--------------070101020008080409080407
Content-Type: text/x-vcard; charset=utf-8;
 name="bjorn_aannestad.vcf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="bjorn_aannestad.vcf"

begin:vcard
fn:Bjorn Aannestad
n:Aannestad;Bjorn
org:UnboundID
email;internet:bjorn@unboundid.com
title:Director, Product Management
tel;work:512 600 7753
tel;cell:512 769 6461
note:skype: bjorn_aannestad
version:2.1
end:vcard


--------------070101020008080409080407--

--------------ms030602010808000504030304
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMUjCC
BVwwggREoAMCAQICECStp7X80wzNJ6GfICadV/cwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz
aWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG
A1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAe
Fw0xMjAyMjMwMDAwMDBaFw0xMzAyMjIyMzU5NTlaMIIBHzEXMBUGA1UEChMOVmVyaVNpZ24s
IEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52
ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMp
OTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJ
RCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMRgwFgYDVQQDFA9Cam9ybiBBYW5u
ZXN0YWQxLDAqBgkqhkiG9w0BCQEWHWJqb3JuLmFhbm5lc3RhZEB1bmJvdW5kaWQuY29tMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw+4r+Le4uODrErBgJsA7UoexcjH/r2Ds
62wKyDCY5CQfOFMROnynV9GWWXp8zmCj7/N9I2hOU7poaqR4kkJjoiKiNHQdVfyM1yFZTurW
AV5PCT5NouiqlruJDM6s2HV3B7mSRhtHFOSfhiDP+/kHf/JEdFJ7zEPaP0Kuy8XKpPR5nVCz
k4zFKPBc4T9+HAlXeGY1PnwOsxPEevZlHOTThF9RunZu5Z/uaObR2JplM6KxXDfXNRjSkmK7
6kW8wFC1C0GleHKfM85nQTvVicuSK4GbbvhMjqovMtUIR1SNG8vsmTvU4PY9G/WkDM4Ge/97
phIcQIm9W/DXjC78wBfa/QIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5Bgtg
hkgBhvhFAQcXATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBh
MAsGA1UdDwQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkw
RzBFoEOgQYY/aHR0cDovL2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5k
QzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQC345zS3026vrJVysBCE3TN
BhQ4VlqRtwj5AcAXhhF2c3krlbgJRLV6STYky+/i7YRdezIZYgY2eo693dlIQUnkZMb6D2PL
dRs1Lgw4NJKB+WGLGkmyV8YqqKrTm/ZbPdl/+Y4Pc88DLcYEmr0OsEDel8LqLPpongUDnGU5
2wxAvaHn9sZ4nyDa3bAy9RyqrAdWhsfRttlgAbvMeHSXhvDa63AbdGdZbzBfqGpBTYZJqrA/
fzcbVZQIw7ULW0YRpUNx8bmmgxFd5ovdDVZnfiKNd7QHy+BcTQgfxLYsBYZhICz1ud1QKn88
pW944VjwHTzxyErX43AGoPYoZKA8b3XXMIIG7jCCBdagAwIBAgIQcRVmBUrkkSFN6bxE+azT
3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMTk5
OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxW
ZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5
IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5W
ZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6
ZYggCxET6ZvgSU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f
0jGyVBlzRmoZQhHsEnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Iba
k2f4MwOuGjxraXj2wCyO4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+
wbaULZeQLSfSux7pg2qE9sSyriMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ
6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBn
MGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNv
bS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTA0BgNV
HR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNV
HQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1hZ2UvZ2lmMCEwHzAH
BgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28udmVyaXNpZ24u
Y29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRlTGFiZWw0
LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHpMIHm
oYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWdu
LCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItb
dVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSo
WufYbAlMJBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6
jhmND0OojPKvYLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvi
d+zoK2Q1ds262uDRyxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5l
UkL7DojS7Uodv0vj+Mxy+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaM
xmgD5yKocwuxvKDaUljdCg5/wYIxggT5MIIE9QIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3Jw
YSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczAhAkrae1/NMMzSeh
nyAmnVf3MAkGBSsOAwIaBQCgggLbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEyMTAzMDE1MDYwMFowIwYJKoZIhvcNAQkEMRYEFLX4rEes3p7OJBYapYYj
n2DUh/nHMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICASgwggEDBgkrBgEEAYI3EAQxgfUwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkG
A1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMp
MDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMwIQJK2ntfzTDM0noZ8gJp1X
9zCCAQUGCyqGSIb3DQEJEAILMYH1oIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy
aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsT
MlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4w
HAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNz
IDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCECStp7X80wzNJ6GfICadV/cwDQYJ
KoZIhvcNAQEBBQAEggEADjmS0GMb778GqOavKXNB7I7fcCsXouXki9wLQNLLQoAX2KDV6j+5
jHmDSPnfm4TFImlZORXaTjQLEG8l3NbNEEgA1iCcNTVAd2KyCklkuCj561V7LXzGk2Ji6thF
EkNVIFIPkWJtsFSE/ua0dncOxtE1mfZpRi8XacBpNsfMhM4ZxQQf6TtfI3g0ssScV6mFnYK/
mViqZADyEnnAgUWFEbee8TDwhgxZZMyf38oqXe/aRegiOrZbhYjAcFxQxfvIIjjlYVPALzP+
S7oH0J2j0YReoNhPYztS50fi27vx35fRTDPbAcfkRZJ47YTa9qTvocdnEZrjvELy37zALVcm
4gAAAAAAAA==
--------------ms030602010808000504030304--

From lear@cisco.com  Tue Oct 30 08:09:01 2012
Return-Path: <lear@cisco.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 5B12621F85A7 for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 08:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 M2ogiVC-dd0E for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 08:09:00 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 2A49B21F8526 for <scim@ietf.org>; Tue, 30 Oct 2012 08:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5720; q=dns/txt; s=iport; t=1351609740; x=1352819340; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=DTJruw0BDeK+xomPcC1VtqtlmwJ8t5zq2lqB5vBIZu8=; b=jMJGzacPbxf0ea5XScLIS2iz9WB+/687JFE4XVB2lGgZJ7gqA4kN1VLJ bbM4BrZvvmwv2x4LmI5fwhcxf3yC5NHRnrTupsPv0jDD5a1D1jltCJ0k8 0EDVjcM0rqi8Re5oDcLzzLKzoA8dPgUsGIKuX9RUa1swcs36DiNXvG5dN U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnMFAMvsj1CQ/khM/2dsb2JhbABEhhiFX7dRgQiCHgEBAQQBAQEPARBLBAYBEAsYCQwKCwICCQMCAQIBFTAGDQEFAgEBHodkC50AjSyCO5A5BIt3JIMJgh2BEwOVdY5XgWuCcA
X-IronPort-AV: E=Sophos;i="4.80,679,1344211200"; d="scan'208,217";a="9215497"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 30 Oct 2012 15:08:59 +0000
Received: from dhcp-10-55-90-162.cisco.com (dhcp-10-55-90-162.cisco.com [10.55.90.162]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q9UF8wa3023068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2012 15:08:58 GMT
Message-ID: <508FED8A.5040608@cisco.com>
Date: Tue, 30 Oct 2012 16:08:58 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Bjorn Aannestad <bjorn.aannestad@unboundid.com>
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com> <508FECD8.7000008@unboundid.com>
In-Reply-To: <508FECD8.7000008@unboundid.com>
X-Enigmail-Version: 1.4.5
Content-Type: multipart/alternative; boundary="------------030606030106000006040209"
Cc: scim@ietf.org, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 15:09:01 -0000

This is a multi-part message in MIME format.
--------------030606030106000006040209
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I think Melinda said that anyone can create tickets, so how about
shooting first and asking questions later?

;-)

Eliot
On 10/30/12 4:06 PM, Bjorn Aannestad wrote:
>
> Thanks for the guidance, Melinda -- that works for me.   Is there a
> consensus on which items are ticket-worthy?  I'm happy to create some
> or all of them, as needed.
>
> -Bjorn
>
> On 10/29/2012 18:49, Melinda Shore wrote:
>> On 10/29/12 3:00 PM, Bjorn Aannestad wrote:
>>> Here's my attempt to turn these into new, specific items for the issues
>>> tracker.   Take this as a proposal for issue titles.  Then, the
>>> discussions on the merits and details of each can proceed.
>> As a matter of process, anybody with an account can create tickets or
>> edit existing ones (not sure about closing them).  Allow me to suggest
>> that it's more productive to go ahead and create tickets than it is
>> to debate them first.  On the other hand, it's not a good thing to
>> get lost in a sea of tickets.
>>
>> More generally, I'm not sure that having high-level design questions
>> in the ticket tracker is that productive - they should probably be
>> specific and on point.  "Remove requirement to support XML" is a good
>> ticket subject.  "Should the spec define how to create and traverse
>> parent-child relationships and/or arbitrary relationships, or stay
>> as-is?" is probably not great, but once a decision is made and if
>> it requires a change to the spec, "write text defining the creation and
>> traversal of parent-child relationships" is something that can be
>> done and be closed.
>>
>> Melinda
>>
>> _______________________________________________
>> 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


--------------030606030106000006040209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I think Melinda said that anyone can create tickets, so how about
    shooting first and asking questions later?<br>
    <br>
    ;-)<br>
    <br>
    Eliot<br>
    <div class="moz-cite-prefix">On 10/30/12 4:06 PM, Bjorn Aannestad
      wrote:<br>
    </div>
    <blockquote cite="mid:508FECD8.7000008@unboundid.com" type="cite">
      <br>
      Thanks for the guidance, Melinda -- that works for me.   Is there
      a consensus on which items are ticket-worthy?  I'm happy to create
      some or all of them, as needed.
      <br>
      <br>
      -Bjorn
      <br>
      <br>
      On 10/29/2012 18:49, Melinda Shore wrote:
      <br>
      <blockquote type="cite">On 10/29/12 3:00 PM, Bjorn Aannestad
        wrote:
        <br>
        <blockquote type="cite">Here's my attempt to turn these into
          new, specific items for the issues
          <br>
          tracker.   Take this as a proposal for issue titles.  Then,
          the
          <br>
          discussions on the merits and details of each can proceed.
          <br>
        </blockquote>
        As a matter of process, anybody with an account can create
        tickets or
        <br>
        edit existing ones (not sure about closing them).  Allow me to
        suggest
        <br>
        that it's more productive to go ahead and create tickets than it
        is
        <br>
        to debate them first.  On the other hand, it's not a good thing
        to
        <br>
        get lost in a sea of tickets.
        <br>
        <br>
        More generally, I'm not sure that having high-level design
        questions
        <br>
        in the ticket tracker is that productive - they should probably
        be
        <br>
        specific and on point.  "Remove requirement to support XML" is a
        good
        <br>
        ticket subject.  "Should the spec define how to create and
        traverse
        <br>
        parent-child relationships and/or arbitrary relationships, or
        stay
        <br>
        as-is?" is probably not great, but once a decision is made and
        if
        <br>
        it requires a change to the spec, "write text defining the
        creation and
        <br>
        traversal of parent-child relationships" is something that can
        be
        <br>
        done and be closed.
        <br>
        <br>
        Melinda
        <br>
        <br>
        _______________________________________________
        <br>
        scim mailing list
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a>
        <br>
        <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a>
        <br>
      </blockquote>
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
scim mailing list
<a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030606030106000006040209--

From phil.hunt@oracle.com  Tue Oct 30 09:16:08 2012
Return-Path: <phil.hunt@oracle.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 356B721F86F1 for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 09:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 RbH9OxSL9hLe for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 09:16:07 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4C921F85EB for <scim@ietf.org>; Tue, 30 Oct 2012 09:16:07 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9UGG53X020130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 30 Oct 2012 16:16:06 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9UGG5Lo021863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2012 16:16:05 GMT
Received: from abhmt114.oracle.com (abhmt114.oracle.com [141.146.116.66]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9UGG4aK030474; Tue, 30 Oct 2012 11:16:04 -0500
Received: from [192.168.1.125] (/24.85.226.208) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 30 Oct 2012 09:16:04 -0700
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com> <508FECD8.7000008@unboundid.com> <508FED8A.5040608@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <508FED8A.5040608@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-9DAE24E2-0A44-4B68-A8D2-0B47083A37F4
Content-Transfer-Encoding: 7bit
Message-Id: <F1D2B4EE-581B-4A08-BD31-DC7CCFFF21E6@oracle.com>
X-Mailer: iPhone Mail (10A403)
From: Phil Hunt <phil.hunt@oracle.com>
Date: Tue, 30 Oct 2012 09:16:03 -0700
To: Eliot Lear <lear@cisco.com>
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: "scim@ietf.org" <scim@ietf.org>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 16:16:08 -0000

--Apple-Mail-9DAE24E2-0A44-4B68-A8D2-0B47083A37F4
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I believe Morteza had some updates from iiw. Not sure if he has already appl=
ied them or still pending.=20

Phil

On 2012-10-30, at 8:08, Eliot Lear <lear@cisco.com> wrote:

> I think Melinda said that anyone can create tickets, so how about shooting=
 first and asking questions later?
>=20
> ;-)
>=20
> Eliot
> On 10/30/12 4:06 PM, Bjorn Aannestad wrote:
>>=20
>> Thanks for the guidance, Melinda -- that works for me.   Is there a conse=
nsus on which items are ticket-worthy?  I'm happy to create some or all of t=
hem, as needed.=20
>>=20
>> -Bjorn=20
>>=20
>> On 10/29/2012 18:49, Melinda Shore wrote:=20
>>> On 10/29/12 3:00 PM, Bjorn Aannestad wrote:=20
>>>> Here's my attempt to turn these into new, specific items for the issues=
=20
>>>> tracker.   Take this as a proposal for issue titles.  Then, the=20
>>>> discussions on the merits and details of each can proceed.
>>> As a matter of process, anybody with an account can create tickets or=20=

>>> edit existing ones (not sure about closing them).  Allow me to suggest  =
      =20
>>> that it's more productive to go ahead and create tickets than it is=20
>>> to debate them first.  On the other hand, it's not a good thing to=20
>>> get lost in a sea of tickets.=20
>>>=20
>>> More generally, I'm not sure that having high-level design questions=20
>>> in the ticket tracker is that productive - they should probably be=20
>>> specific and on point.  "Remove requirement to support XML" is a good=20=

>>> ticket subject.  "Should the spec define how to create and traverse=20
>>> parent-child relationships and/or arbitrary relationships, or stay=20
>>> as-is?" is probably not great, but once a decision is made and if=20
>>> it requires a change to the spec, "write text defining the creation and =
       =20
>>> traversal of parent-child relationships" is something that can         b=
e=20
>>> done and be closed.=20
>>>=20
>>> Melinda=20
>>>=20
>>> _______________________________________________=20
>>> scim mailing list=20
>>> scim@ietf.org=20
>>> https://www.ietf.org/mailman/listinfo/scim
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim
>=20
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim

--Apple-Mail-9DAE24E2-0A44-4B68-A8D2-0B47083A37F4
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I believe Morteza had some updates from iiw. Not sure if he has already applied them or still pending.&nbsp;<br><br>Phil</div><div><br>On 2012-10-30, at 8:08, Eliot Lear &lt;<a href="mailto:lear@cisco.com">lear@cisco.com</a>&gt; wrote:<br><br></div><div><span></span></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  
  
    I think Melinda said that anyone can create tickets, so how about
    shooting first and asking questions later?<br>
    <br>
    ;-)<br>
    <br>
    Eliot<br>
    <div class="moz-cite-prefix">On 10/30/12 4:06 PM, Bjorn Aannestad
      wrote:<br>
    </div>
    <blockquote cite="mid:508FECD8.7000008@unboundid.com" type="cite">
      <br>
      Thanks for the guidance, Melinda -- that works for me.&nbsp;&nbsp; Is there
      a consensus on which items are ticket-worthy?&nbsp; I'm happy to create
      some or all of them, as needed.
      <br>
      <br>
      -Bjorn
      <br>
      <br>
      On 10/29/2012 18:49, Melinda Shore wrote:
      <br>
      <blockquote type="cite">On 10/29/12 3:00 PM, Bjorn Aannestad
        wrote:
        <br>
        <blockquote type="cite">Here's my attempt to turn these into
          new, specific items for the issues
          <br>
          tracker.&nbsp;&nbsp; Take this as a proposal for issue titles.&nbsp; Then,
          the
          <br>
          discussions on the merits and details of each can proceed.
          <br>
        </blockquote>
        As a matter of process, anybody with an account can create
        tickets or
        <br>
        edit existing ones (not sure about closing them).&nbsp; Allow me to
        suggest
        <br>
        that it's more productive to go ahead and create tickets than it
        is
        <br>
        to debate them first.&nbsp; On the other hand, it's not a good thing
        to
        <br>
        get lost in a sea of tickets.
        <br>
        <br>
        More generally, I'm not sure that having high-level design
        questions
        <br>
        in the ticket tracker is that productive - they should probably
        be
        <br>
        specific and on point.&nbsp; "Remove requirement to support XML" is a
        good
        <br>
        ticket subject.&nbsp; "Should the spec define how to create and
        traverse
        <br>
        parent-child relationships and/or arbitrary relationships, or
        stay
        <br>
        as-is?" is probably not great, but once a decision is made and
        if
        <br>
        it requires a change to the spec, "write text defining the
        creation and
        <br>
        traversal of parent-child relationships" is something that can
        be
        <br>
        done and be closed.
        <br>
        <br>
        Melinda
        <br>
        <br>
        _______________________________________________
        <br>
        scim mailing list
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a>
        <br>
        <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a>
        <br>
      </blockquote>
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
scim mailing list
<a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a>
</pre>
    </blockquote>
    <br>
  

</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>scim mailing list</span><br><span><a href="mailto:scim@ietf.org">scim@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/scim">https://www.ietf.org/mailman/listinfo/scim</a></span><br></div></blockquote></body></html>
--Apple-Mail-9DAE24E2-0A44-4B68-A8D2-0B47083A37F4--

From melinda.shore@gmail.com  Tue Oct 30 10:06:18 2012
Return-Path: <melinda.shore@gmail.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 2641921F8708 for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 10:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 GtonDe9GJpY7 for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 10:06:17 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id BBE2C21F8458 for <scim@ietf.org>; Tue, 30 Oct 2012 10:06:17 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so317017pad.31 for <scim@ietf.org>; Tue, 30 Oct 2012 10:06:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=L1gYQCMwD3v/q3g7X5sA0aO6Efz+1aPlPekIdf7b5O0=; b=B33Kl5RUgQlHgH3PbwY6XINYx7V7dVvIY3kzOg7arZggK9kMwHxzSrQJoEsg590HjZ gByLRaY70h9kYkVc2GT/5Rbr4N1VWRdFkPYGNKglwQ5k4wWAyxStAquGYx7y9ME6TQXU M+rmwgDeBsQ7FbFCFV0OpRjDpxVoNDzeByA/uEC/JlBLkUEcXj/cCfsARaEafnub0g4V pS3KTIfYlMa+Vut8h7SySXtfM3Ji+TgSDd8/1UHP9tT/SZ5qIIRphsX2cAWG45Rqx1jd 70wjq4B8FuFshqdt2zGq1+P78Q2b1MUfgcvbO9uDvMq5d+owknBmxIeHbtvBQktC3XVw CeRw==
Received: by 10.66.85.69 with SMTP id f5mr80125661paz.50.1351616777596; Tue, 30 Oct 2012 10:06:17 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id nu8sm810408pbc.45.2012.10.30.10.06.15 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Oct 2012 10:06:16 -0700 (PDT)
Message-ID: <50900906.1010403@gmail.com>
Date: Tue, 30 Oct 2012 09:06:14 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com> <508FECD8.7000008@unboundid.com> <508FED8A.5040608@cisco.com>
In-Reply-To: <508FED8A.5040608@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: scim@ietf.org
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 17:06:18 -0000

On 10/30/12 7:08 AM, Eliot Lear wrote:
> I think Melinda said that anyone can create tickets, so how about
> shooting first and asking questions later?

I think this is reasonable, but should not be taken as a license
to create tickets for things which have not been mentioned on the
list.  If things get out of hand or there's clear misbehavior we can
put access controls on the issue tracker, but for the time being
there seems to be more benefit than not to having it open.

Melinda


From melinda.shore@gmail.com  Tue Oct 30 11:10:16 2012
Return-Path: <melinda.shore@gmail.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 2512521F866D for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 11:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
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 e6LBllGfiNEC for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 11:10:15 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id AEEBA21F866B for <scim@ietf.org>; Tue, 30 Oct 2012 11:10:15 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so356361pad.31 for <scim@ietf.org>; Tue, 30 Oct 2012 11:10:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=qs69O2vdHD+cEJLkmK9zpr+ds9cLNmfQ1Gu3sg6L0fE=; b=On9to/gYBTf1uyg6Uwv7NmLLnEdtSiEjRJVSf6r8D7mtxCjXWlfHmFe9ngnKyRvYZi IAVjxnbuBrYgW+9YDosR7qwyTHHc30WOKnJRNO+z8D4mqP25PeoDm54Yz1g4ZXN9xpeM 5EDxxeR6yL7evrt2vxHdyOUuYPoFfyNfaEBHGuVsC2TCGDwTwQzlIMWBjIj507LnHGPB wfOhuEHTtyA4LcvTzaOOdoNh2y7N5kZ/HtULwv4HWdKn8L+ACWWRpUzK8HVM6atxYgDJ /B2JqnMums6Q/oVT7bZKIsn8KYLBg64tM1a5w9dazbMZBO6z3meWpAjRC9OCAPk8JmXB mWEg==
Received: by 10.66.72.134 with SMTP id d6mr94628074pav.13.1351620615538; Tue, 30 Oct 2012 11:10:15 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id o5sm741779paz.32.2012.10.30.11.10.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Oct 2012 11:10:14 -0700 (PDT)
Message-ID: <50901804.2000009@gmail.com>
Date: Tue, 30 Oct 2012 10:10:12 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "scim@ietf.org" <scim@ietf.org>
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com> <508FECD8.7000008@unboundid.com> <508FED8A.5040608@cisco.com> <F1D2B4EE-581B-4A08-BD31-DC7CCFFF21E6@oracle.com>
In-Reply-To: <F1D2B4EE-581B-4A08-BD31-DC7CCFFF21E6@oracle.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 18:10:16 -0000

Speaking of the issue tracker, this might be a good time to start
going through the tickets and closing the easy ones.  I think most
of them require some effort but a few do not, particularly.  For
example, #7 ("The Canonical types for groups attribute begins with
capital letter, but all other are lowercase") appears to be just
editorial.

Melinda

From kelly.grizzle@sailpoint.com  Tue Oct 30 12:05:01 2012
Return-Path: <kelly.grizzle@sailpoint.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 C53AC21F85D4 for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 12:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
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 34j6Rgnj1rZE for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 12:05:00 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD1321F85B8 for <scim@ietf.org>; Tue, 30 Oct 2012 12:05:00 -0700 (PDT)
Received: from mail177-va3-R.bigfish.com (10.7.14.239) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 14.1.225.23; Tue, 30 Oct 2012 19:04:59 +0000
Received: from mail177-va3 (localhost [127.0.0.1])	by mail177-va3-R.bigfish.com (Postfix) with ESMTP id C3A962C0132; Tue, 30 Oct 2012 19:04:59 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.85; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0410HT004.namprd04.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: PS-26(zz9371I542Mzz1202h1d1ah1d2ahzz1033IL8275dhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received-SPF: pass (mail177-va3: domain of sailpoint.com designates 157.56.236.85 as permitted sender) client-ip=157.56.236.85; envelope-from=kelly.grizzle@sailpoint.com; helo=BY2PRD0410HT004.namprd04.prod.outlook.com ; .outlook.com ; 
Received: from mail177-va3 (localhost.localdomain [127.0.0.1]) by mail177-va3 (MessageSwitch) id 1351623897686534_27167; Tue, 30 Oct 2012 19:04:57 +0000 (UTC)
Received: from VA3EHSMHS046.bigfish.com (unknown [10.7.14.249])	by mail177-va3.bigfish.com (Postfix) with ESMTP id 961312A010D; Tue, 30 Oct 2012 19:04:57 +0000 (UTC)
Received: from BY2PRD0410HT004.namprd04.prod.outlook.com (157.56.236.85) by VA3EHSMHS046.bigfish.com (10.7.99.56) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 30 Oct 2012 19:04:51 +0000
Received: from BY2PRD0410MB354.namprd04.prod.outlook.com ([169.254.11.81]) by BY2PRD0410HT004.namprd04.prod.outlook.com ([10.255.83.39]) with mapi id 14.16.0233.002; Tue, 30 Oct 2012 19:04:47 +0000
From: Kelly Grizzle <kelly.grizzle@sailpoint.com>
To: Melinda Shore <melinda.shore@gmail.com>, "scim@ietf.org" <scim@ietf.org>
Thread-Topic: [scim] Design Team Status
Thread-Index: AQHNtikoLyZ2vo9LwEiRpmmaIrCnWZfQ898AgAD/8wCAAADUAIAAEr6AgAAf5QCAAAShgA==
Date: Tue, 30 Oct 2012 19:04:47 +0000
Message-ID: <56C3C758F9D6534CA3778EAA1E0C34373E7F02EA@BY2PRD0410MB354.namprd04.prod.outlook.com>
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com> <508FECD8.7000008@unboundid.com> <508FED8A.5040608@cisco.com> <F1D2B4EE-581B-4A08-BD31-DC7CCFFF21E6@oracle.com> <50901804.2000009@gmail.com>
In-Reply-To: <50901804.2000009@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-vipre-scanned: 5D5BF81E0035B45D5BF96B
x-originating-ip: [173.226.147.242]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: sailpoint.com
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 19:05:01 -0000

The nice thing about capital types for the members attribute on the Group r=
esource is that the type value corresponds to the resource name.  In other =
words, given a group you could traverse the object relationship to the memb=
er.  Something like this:

    resource =3D GET /Schemas?name eq {member.type}
    GET {resource.endpoint}/{member.value}

Of course, with a lowercase name you could just upper case the first letter=
.  To me it is a little more apparent with the upper-case letter.

On the other hand, this might become a moot point depending on how we addre=
ss this: "Should the spec define how to create and traverse parent-child re=
lationships and/or arbitrary relationships, or stay as-is?".

--Kelly

-----Original Message-----
From: scim-bounces@ietf.org [mailto:scim-bounces@ietf.org] On Behalf Of Mel=
inda Shore
Sent: Tuesday, October 30, 2012 1:10 PM
To: scim@ietf.org
Subject: Re: [scim] Design Team Status

Speaking of the issue tracker, this might be a good time to start going thr=
ough the tickets and closing the easy ones.  I think most of them require s=
ome effort but a few do not, particularly.  For example, #7 ("The Canonical=
 types for groups attribute begins with capital letter, but all other are l=
owercase") appears to be just editorial.

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



From leifj@mnt.se  Tue Oct 30 14:54:27 2012
Return-Path: <leifj@mnt.se>
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 C23F221F85F0 for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 14:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 L9P-Gc3xkcWK for <scim@ietfa.amsl.com>; Tue, 30 Oct 2012 14:54:26 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5C58321F85E1 for <scim@ietf.org>; Tue, 30 Oct 2012 14:54:25 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so641132lbo.31 for <scim@ietf.org>; Tue, 30 Oct 2012 14:54:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:x-gm-message-state; bh=Q0TbO6KghNcnPr7tDKS3EguDh9VvWzmOJ3cyqkjNLcc=; b=N3YGmviIFy79+YErvjPXZzAOMyPReCAG2Znti6wJqT5Rq6MWtJzjjo3hCUGtrZNggj v2c+a+p3vmMfQHf4pLKUKsId/27SJ+C3Y2+KRDXAwfn+LA6DeWvruCsEAkk83I0+A+kc YwBwXBX6BGULwXxH+hmYHGc6+FN3q9Rgw1orFpKjDyov3xgNzWynGzSwr/0PZ1bw7z8k vL1QsxyNLOS+ZCOIU0aFGPY4l4vtqoqn1XOFGfvfjvwptUUZ3vPv0qsFdB8GzAnEEDKp pF/K0lCR20qhaWR6S13OGrhnvfKta3VGU7e/QCH65i/cxBzQ+mmmbaBC3fVXbqAclEq8 P0cg==
Received: by 10.112.29.71 with SMTP id i7mr3818684lbh.85.1351634064261; Tue, 30 Oct 2012 14:54:24 -0700 (PDT)
Received: from [10.0.0.244] (ua-83-227-179-169.cust.bredbandsbolaget.se. [83.227.179.169]) by mx.google.com with ESMTPS id i7sm802245lbg.13.2012.10.30.14.54.21 (version=SSLv3 cipher=OTHER); Tue, 30 Oct 2012 14:54:22 -0700 (PDT)
Message-ID: <50904C8C.2030602@mnt.se>
Date: Tue, 30 Oct 2012 22:54:20 +0100
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: scim@ietf.org
References: <508EB590.6020706@unboundid.com> <508F0A80.40004@unboundid.com> <508F1624.3060205@gmail.com> <508FECD8.7000008@unboundid.com> <508FED8A.5040608@cisco.com>
In-Reply-To: <508FED8A.5040608@cisco.com>
Content-Type: multipart/alternative; boundary="------------080608000407030509000509"
X-Gm-Message-State: ALoCoQls72bumV6St7QpE5R1uaS/IGdGqnP7nCwOoYuE8Im0q81eELYW/cbH1gssXreRazSsSauO
Subject: Re: [scim] Design Team Status
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: Tue, 30 Oct 2012 21:54:27 -0000

This is a multi-part message in MIME format.
--------------080608000407030509000509
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 10/30/2012 04:08 PM, Eliot Lear wrote:
> I think Melinda said that anyone can create tickets, so how about
> shooting first and asking questions later?

As chair I'd rather have actionable issues than no issues. But I'd
_love_ to have both :-)


--------------080608000407030509000509
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 10/30/2012 04:08 PM, Eliot Lear
      wrote:<br>
    </div>
    <blockquote cite="mid:508FED8A.5040608@cisco.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      I think Melinda said that anyone can create tickets, so how about
      shooting first and asking questions later?<br>
    </blockquote>
    <br>
    As chair I'd rather have actionable issues than no issues. But I'd
    _love_ to have both :-)<br>
    <br>
  </body>
</html>

--------------080608000407030509000509--

From phil.hunt@oracle.com  Wed Oct 31 09:08:41 2012
Return-Path: <phil.hunt@oracle.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 0202521F8671 for <scim@ietfa.amsl.com>; Wed, 31 Oct 2012 09:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=0.699,  BAYES_00=-2.599]
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 pzbpuzvlU6EX for <scim@ietfa.amsl.com>; Wed, 31 Oct 2012 09:08:40 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 6340221F84D2 for <scim@ietf.org>; Wed, 31 Oct 2012 09:08:40 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9VG8dHk004170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <scim@ietf.org>; Wed, 31 Oct 2012 16:08:39 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9VG8cCN000602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <scim@ietf.org>; Wed, 31 Oct 2012 16:08:39 GMT
Received: from abhmt118.oracle.com (abhmt118.oracle.com [141.146.116.70]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9VG8cAM030120 for <scim@ietf.org>; Wed, 31 Oct 2012 11:08:38 -0500
Received: from [192.168.1.131] (/24.85.226.208) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 31 Oct 2012 09:08:38 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 31 Oct 2012 09:08:38 -0700
Message-Id: <71CCC0EB-6C91-4EE2-9621-20008E75E7B7@oracle.com>
To: "scim@ietf.org WG" <scim@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Subject: [scim] schemas question - clarification on use
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: Wed, 31 Oct 2012 16:08:41 -0000

I was just looking at the "schemas" attribute definition (in =
core-schema-00) and was wondering whether it is meant to indicate =
whether the SP's resource "has" a particular schema extension, or =
whether it means the current JSON structure has the extension schema =
present? =20

For example, if a SP returns a User resource that internally has the =
Enterprise extension but no enterprise schema attributes were requested, =
then what should schemas say?

IMHO. I think having schemas always return what is available is always =
useful. If the client didn't request all attributes, then it already =
knows whether to look for extended attributes or not.

I just mention this because I believe we have an ticket to review =
schemas in order to define how we indicate what resource type a json =
structure represents.   Also, should schemas be part of the "meta" =
attribute?

Phil

@independentid
www.independentid.com
phil.hunt@oracle.com






From kelly.grizzle@sailpoint.com  Wed Oct 31 17:40:07 2012
Return-Path: <kelly.grizzle@sailpoint.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 7D3A821F8889 for <scim@ietfa.amsl.com>; Wed, 31 Oct 2012 17:40:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 krJ0YVBOkPMr for <scim@ietfa.amsl.com>; Wed, 31 Oct 2012 17:40:05 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe006.messaging.microsoft.com [216.32.181.186]) by ietfa.amsl.com (Postfix) with ESMTP id 6F67321F8887 for <scim@ietf.org>; Wed, 31 Oct 2012 17:40:05 -0700 (PDT)
Received: from mail33-ch1-R.bigfish.com (10.43.68.233) by CH1EHSOBE014.bigfish.com (10.43.70.64) with Microsoft SMTP Server id 14.1.225.23; Thu, 1 Nov 2012 00:40:04 +0000
Received: from mail33-ch1 (localhost [127.0.0.1])	by mail33-ch1-R.bigfish.com (Postfix) with ESMTP id 693FCC00A6; Thu,  1 Nov 2012 00:40:04 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.85; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0410HT004.namprd04.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(zz98dI9371I1432Izz1202h1d1ah1d2ahzz1033IL8275bh8275dhz2fh2a8h668h839h944hd25he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received-SPF: pass (mail33-ch1: domain of sailpoint.com designates 157.56.236.85 as permitted sender) client-ip=157.56.236.85; envelope-from=kelly.grizzle@sailpoint.com; helo=BY2PRD0410HT004.namprd04.prod.outlook.com ; .outlook.com ; 
Received: from mail33-ch1 (localhost.localdomain [127.0.0.1]) by mail33-ch1 (MessageSwitch) id 1351730401539156_30284; Thu,  1 Nov 2012 00:40:01 +0000 (UTC)
Received: from CH1EHSMHS026.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.231])	by mail33-ch1.bigfish.com (Postfix) with ESMTP id 80EFD1C006F;	Thu,  1 Nov 2012 00:40:01 +0000 (UTC)
Received: from BY2PRD0410HT004.namprd04.prod.outlook.com (157.56.236.85) by CH1EHSMHS026.bigfish.com (10.43.70.26) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 1 Nov 2012 00:40:01 +0000
Received: from BY2PRD0410MB354.namprd04.prod.outlook.com ([169.254.11.81]) by BY2PRD0410HT004.namprd04.prod.outlook.com ([10.255.83.39]) with mapi id 14.16.0233.002; Thu, 1 Nov 2012 00:39:45 +0000
From: Kelly Grizzle <kelly.grizzle@sailpoint.com>
To: Phil Hunt <phil.hunt@oracle.com>
Thread-Topic: [scim] schemas question - clarification on use
Thread-Index: AQHNt4IBnglSJpfq6E6TP9BveiBlcZfUI8I4
Date: Thu, 1 Nov 2012 00:39:44 +0000
Message-ID: <7598A6D7-63B3-4396-B1F3-8AF3DBF2E07E@sailpoint.com>
References: <71CCC0EB-6C91-4EE2-9621-20008E75E7B7@oracle.com>
In-Reply-To: <71CCC0EB-6C91-4EE2-9621-20008E75E7B7@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [72.182.10.254]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: sailpoint.com
Cc: "scim@ietf.org WG" <scim@ietf.org>
Subject: Re: [scim] schemas question - clarification on use
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, 01 Nov 2012 00:40:07 -0000

> IMHO. I think having schemas always return what is available is always us=
eful.

Agreed.  This would be similar to the objectclass attribute in LDAP.

--Kelly

On Oct 31, 2012, at 11:08 AM, "Phil Hunt" <phil.hunt@oracle.com> wrote:

> I was just looking at the "schemas" attribute definition (in core-schema-=
00) and was wondering whether it is meant to indicate whether the SP's reso=
urce "has" a particular schema extension, or whether it means the current J=
SON structure has the extension schema present? =20
>=20
> For example, if a SP returns a User resource that internally has the Ente=
rprise extension but no enterprise schema attributes were requested, then w=
hat should schemas say?
>=20
> IMHO. I think having schemas always return what is available is always us=
eful. If the client didn't request all attributes, then it already knows wh=
ether to look for extended attributes or not.
>=20
> I just mention this because I believe we have an ticket to review schemas=
 in order to define how we indicate what resource type a json structure rep=
resents.   Also, should schemas be part of the "meta" attribute?
> Phil
>=20
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>=20

