[Ietf-carddav] carddav and corporate directories

Arnaud Quillaud <Arnaud.Quillaud@Sun.COM> Wed, 09 May 2007 16:40 UTC

Return-Path: <Arnaud.Quillaud@Sun.COM>
X-Original-To: ietf-carddav@osafoundation.org
Delivered-To: ietf-carddav@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id E460A7F68F for <ietf-carddav@osafoundation.org>; Wed, 9 May 2007 09:40:11 -0700 (PDT)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id AC7D6142276 for <ietf-carddav@osafoundation.org>; Wed, 9 May 2007 09:39:16 -0700 (PDT)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.297
X-Spam-Level:
X-Spam-Status: No, score=-1.297 tagged_above=-50 required=4 tests=[AWL=1.301, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 6yAwStv-g7Ei for <ietf-carddav@osafoundation.org>; Wed, 9 May 2007 09:39:13 -0700 (PDT)
Received: from gmp-ea-fw-1.sun.com (gmp-ea-fw-1.sun.com [192.18.1.36]) by laweleka.osafoundation.org (Postfix) with ESMTP id 018D814225D for <ietf-carddav@osafoundation.org>; Wed, 9 May 2007 09:39:12 -0700 (PDT)
Received: from d1-emea-09.sun.com (d1-emea-09.sun.com [192.18.2.119]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l49Gd7OX001176 for <ietf-carddav@osafoundation.org>; Wed, 9 May 2007 16:39:07 GMT
Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JHS00K018R1OS00@d1-emea-09.sun.com> (original mail from Arnaud.Quillaud@Sun.COM) for ietf-carddav@osafoundation.org; Wed, 09 May 2007 17:36:31 +0100 (BST)
Received: from KONE-JHY8LIXZ2A.Sun.COM ([129.150.116.246]) by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JHS007QG8STQPC0@d1-emea-09.sun.com> for ietf-carddav@osafoundation.org; Wed, 09 May 2007 17:36:31 +0100 (BST)
Content-return: prohibited
Date: Wed, 09 May 2007 18:36:45 +0200
From: Arnaud Quillaud <Arnaud.Quillaud@Sun.COM>
Sender: Arnaud.Quillaud@Sun.COM
To: ietf-carddav@osafoundation.org
Message-id: <0JHS007QJ8SUQPC0@d1-emea-09.sun.com>
MIME-version: 1.0
X-Mailer: Sun Outlook Connector 7.2.310.1
Content-type: TEXT/PLAIN; CHARSET="ISO-8859-1"
Content-transfer-encoding: 7bit
Subject: [Ietf-carddav] carddav and corporate directories
X-BeenThere: ietf-carddav@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-carddav.osafoundation.org
List-Unsubscribe: <http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-carddav>, <mailto:ietf-carddav-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-carddav>
List-Post: <mailto:ietf-carddav@osafoundation.org>
List-Help: <mailto:ietf-carddav-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-carddav>, <mailto:ietf-carddav-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2007 16:40:12 -0000

Hello,

Although it mentions LDAP in its introduction, the spec does not talk about the link between Corporate Directory access and CardDAV access.

Most PIM or email clients that would benefit from a CardDAV access also offer some access to corporate directories, usually LDAP directories. For an end user, they almost serve the same purpose (e.g. when sending an email, I may select some people from my personal address book and some from my corporate directory).

Nevertheless:
- configuring those clients is usually a real pain: server name and port, ssl or no ssl, base dn, search filter, bind dn, etc...
- each client has to deal with schema translation between the corporate directory schema and the internal representation.

Being able from CardDAV to discover public address books would greatly enhance the user experience. 
Being able to work against one format (vCard) instead of 2 (vCard + some LDAP schema) would ease development of address book enabled applications.


Arnaud Q