Subject: Re: [scim] Draft BOF charter

From: Trey Drake <[email-masked]>
Date: Fri, 10 Feb 2012 07:26:21 -0600

They are not.  Paul M. owns the SAML AI, but we owe him feedback on the latest proposal (see mailing list).  

I've had an open action item for months to kickstart the LDAP binding.  I'll sketch next week.

Thanks,
Trey 

On Feb 8, 2012, at 10:16 AM, Samuel Erdtman wrote:

> Are the SAML and LDAP binding done?
> 
> Regards
> //Samuel
> 
> 
> On Wed, Jan 25, 2012 at 10:06 AM, Morteza Ansari (moransar)
> <[email-masked]> wrote:
>> Sorry folks, but I didn’t get a chance to get this out sooner. Attached is
>> the strawman proposal for the BOF charter. Let’s review this on the call
>> tomorrow and we can continue to work on it on the list.
>> 
>> 
>> 
>> 
>> 
>> Cheers,
>> 
>> Morteza
>> 
>> 
>> 
>> 
>> 
>> Simplified Cloud Identity Management (SCIM)
>> 
>> --------------------------------------------------------
>> 
>> 
>> 
>> Charter
>> 
>> 
>> 
>> Current Status: BOF Request
>> 
>> 
>> 
>> Chair(s):
>> 
>>      TBD1
>> 
>>      TBD2
>> 
>> 
>> 
>> Applications Area Director(s):
>> 
>>     Pete Resnick <[email-masked]>
>> 
>>      Peter Saint-Andre <[email-masked]>
>> 
>> 
>> 
>> Mailing Lists:
>> 
>>      General Discussion: [email-masked]
>> 
>>      To Subscribe:     https://www.ietf.org/mailman/listinfo/scim
>> 
>>      Archive:
>>     http://www.ietf.org/mail-archive/web/scim/current/maillist.html
>> 
>> 
>> 
>> Description of Working Group:
>> 
>> 
>> 
>> The Simple Cloud Identity Management (SCIM) specification is designed to
>> make managing user identity lifecycle in cloud based applications and
>> services easier.
>> 
>> 
>> 
>> The specification suite seeks to build upon experience with existing schemas
>> and deployments, placing specific emphasis on simplicity of development and
>> integration, while applying existing authentication, authorization, and
>> privacy models. Its intent is to reduce the cost and complexity of user
>> management operations by providing a common user schema and extension model,
>> as well as binding documents to provide patterns for exchanging this schema
>> using standard protocols.
>> 
>> 
>> 
>> The group will work to adapt the SCIM 1.0 specification (produced under the
>> Open Web Foundation framework) as an IETF technology for management of user
>> identities in cloud-based applications.
>> 
>> 
>> 
>> SCIM 1.0 consists of:
>> 
>> ·         Schema definition for identity related objects
>> 
>> ·         Protocol definition for accessing and managing the identity
>> objects
>> 
>> ·         Binding of SCIM schema to Security Assertion Markup Language
>> (SAML) messages and assertions
>> 
>> ·         Binding of SCIM schema to Lightweight Directory Access Protocol
>> (LDAP) schema (RFC4519)
>> 
>> 
>> 
>> The Working Group will produce one or more documents suitable for
>> consideration as a Proposed Standard that will:
>> 
>> ·         Improve the terminology used
>> 
>> ·         Embody good security practices, document gaps in its capabilities,
>> and propose a path forward for addressing the gaps
>> 
>> ·         Promote interoperability
>> 
>> ·         Provide guidelines for extensibility
>> 
>> 
>> 
>> SCIM 1.0 will be used as the starting point. The working group will strive
>> to retain backward compatibility with the 1.0 specification. Changes that
>> are not backwards compatible may be accepted if the group determines changes
>> are required to meet the group's technical objectives and the group clearly
>> documents the reasons for making them.
>> 
>> 
>> 
>> The Working Group should consider:
>> 
>> ·         Implementer experience
>> 
>> ·         The end-user experience, including internationalization
>> 
>> ·         Existing uses of SCIM
>> 
>> ·         Ability to achieve broad implementation
>> 
>> ·         Ability to address broader use cases than those considered by the
>> original authors
>> 
>> ·         Additional functions or extensions that are needed to address key
>> security concerns, cross-area review, and implementer feedback
>> 
>> 
>> 
>> The working group will focus on adapting the core technology first but work
>> on extensions will be considered after the core work is well in hand.