PP10: Extending LDAP schemas in support of Applications

Lisa Dusseault <lisa@osafoundation.org> Fri, 18 January 2008 19:42 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFx6W-00068Y-8V; Fri, 18 Jan 2008 14:42:16 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1JFx6U-00068S-Q5 for discuss-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 14:42:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFx6U-00068K-B2 for discuss@apps.ietf.org; Fri, 18 Jan 2008 14:42:14 -0500
Received: from laweleka.osafoundation.org ([204.152.186.98]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFx6S-0002bK-El for discuss@apps.ietf.org; Fri, 18 Jan 2008 14:42:14 -0500
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 601D6142254 for <discuss@apps.ietf.org>; Fri, 18 Jan 2008 11:42:14 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OBm2sNdHNQBR for <discuss@apps.ietf.org>; Fri, 18 Jan 2008 11:42:08 -0800 (PST)
Received: from [192.168.1.101] (unknown [74.95.2.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 065AD142203 for <discuss@apps.ietf.org>; Fri, 18 Jan 2008 11:42:08 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.3)
To: Apps Discuss <discuss@apps.ietf.org>
Message-Id: <5DAA4297-0D1D-4B71-A587-F8C702BE9296@osafoundation.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-4--960174947
References: <1625A315-9B63-4FA8-B042-8BF4F8B0A64B@Isode.com>
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: PP10: Extending LDAP schemas in support of Applications
Date: Fri, 18 Jan 2008 11:42:04 -0800
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

	

Begin forwarded message:

> From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
> Date: January 18, 2008 11:33:45 AM PST
> To: Lisa Dusseault <lisa@osafoundation.org>
> Subject: Re: Directory Position
>
> Here's a bit more...  -- Kurt
>
>
> LDAP directory systems are in wide spread use as repositories for  
> information used in providing Internet services, including Email  
> services (SMTP, IMAP, POP, SIEVE, MANAGESIEVE), instant messaging  
> and presence services (XMPP, SIP), and calendaring and scheduling  
> (CALDAV).  Despite this wide spread use, schema used in  
> representing Internet service information is rarely standardized.   
> This hinders interoperability.
>
> To improve interoperability, the IETF should engineer standards,  
> where appropriate, of LDAP schema used for representing information  
> used in providing Internet services.  This engineering would  
> include specification of generalized schema elements, such as for  
> representing Internet users and their credentials, and  
> specification of service-specific elements, such as representing  
> objects in support of Email services.
>
> Example generalized schema elements include:
>
> - Define schema to represent a user of Internet services.
> - Define schema to represent a user's authorization to utilize  
> Internet services.
>
> Example service-specific schema elements include:
>
> - Define email service schema in support of SMTP, IMAP, POP, SIEVE,  
> MANAGESIEVE, etc.  This would not be limited to just routing (as  
> LASER is), but also represent things such as the user's current  
> SIEVE script.
>
> The generalized elements would aide one in deploying multiple  
> different services using components provided by different vendors  
> (for instance an Isode email solution with an Apple calendaring  
> solution).   The service-specific elements would aide one in  
> deploying within a single service, such as email, components from  
> different vendors (for instance, Sendmail incoming SMTP servers,  
> Postfix outing SMTP, Apple submission SMTP, and an Isode IMAP server).
>
>
>