Network Working Group C. Joy Internet-Draft Oracle Intended status: Standards Track C. Daboo Expires: June 15, 2012 Apple Inc. M. Douglass RPI December 13, 2011 Mapping of VCard 4 Properties to LDAP objectclasses and attributes draft-daboo-vcard4-ldap-mapping-00 Abstract This specification describes a mapping of standard VCard 4 properties to standard LDAP objectclasses and attributes. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on June 15, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Joy, et al. Expires June 15, 2012 [Page 1] Internet-Draft VCARD4 LDAP Mapping December 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . . 3 3. Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Full Name . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. Kind . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2.1. Mapping of KIND value between LDAP and VCard representations . . . . . . . . . . . . . . . . . . . . 4 3.3. Description . . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Organizational Unit . . . . . . . . . . . . . . . . . . . . 4 3.5. Group Member . . . . . . . . . . . . . . . . . . . . . . . 4 3.6. Calendar URL . . . . . . . . . . . . . . . . . . . . . . . 4 3.7. FreeBusy URL . . . . . . . . . . . . . . . . . . . . . . . 5 3.8. Calendar User Address . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Normative References . . . . . . . . . . . . . . . . . . . . . 5 Joy, et al. Expires June 15, 2012 [Page 2] Internet-Draft VCARD4 LDAP Mapping December 2011 1. Introduction This specification describes a mapping of standard VCard 4 properties defined in vCard Format Specification [RFC6350] to standard LDAP objectclasses and attributes. 2. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Mappings 3.1. Full Name VCard Property: The FN property that specifies the full name of the entity as defined in Section 6.2.1 of [RFC6350]. LDAP Attribute Mapping: The cn attribute as defined in Section 2.3 of [RFC4519]. 3.2. Kind VCard Property: Property KIND that specifies the kind of entity represented, as defined in Section 6.1.4 of [RFC6350]. LDAP Objectclass Mapping: In LDAP, this information can be represented by including the right objectlass. Possible objectclasses are: Person objectclass as defined in Section 3.12 of [RFC4519]. groupOfNames objectclass as defined in Section 3.5 of [RFC4519]. groupOfUniqueNames objectclass as defined in Section 3.6 of [RFC4519]. room objectclass as defined in Section 3.8 of [RFC4524]. organization objectclass as defined in Section 3.8 of [RFC4519]. Joy, et al. Expires June 15, 2012 [Page 3] Internet-Draft VCARD4 LDAP Mapping December 2011 3.2.1. Mapping of KIND value between LDAP and VCard representations KIND Value Mapping Table: +------------------------------------+-------------+ | LDAP Objectclass | VCard Value | +------------------------------------+-------------+ | person | individual | | groupOfNames or groupOfUniqueNames | group | | room | location | | organization | org | +------------------------------------+-------------+ 3.3. Description VCard Property: The NOTE property that can store more information about the entity as defined in Section 6.7.2 of [RFC6350]. LDAP Attribute Mapping: The description attribute as defined in Section 2.5 of [RFC4519]. 3.4. Organizational Unit VCard Property: The ORG property as defined in Section 6.6.4 of [RFC6350]. LDAP Attribute Mapping: The o attribute as defined in Section 2.19 of [RFC4519] or the ou attribute as defined in Section 2.20 of [RFC4519]. 3.5. Group Member VCard Property: The MEMBER property as defined in Section 6.6.5 of [RFC6350]. LDAP Attribute Mapping: The member attribute as defined in Section 2.17 or the uniquemember attribute as defined in Section 2.40 of [RFC4519]. 3.6. Calendar URL VCard Property: Calendar access property CALURI as defined in Section 6.9.3 of [RFC6350]. LDAP Attribute Mapping: Calendar access attribute calCalURI as defined in Section 2.4.4.1 and calOtherCalURIs as defined in Section 2.4.4.5 of [RFC2739] respectively. Joy, et al. Expires June 15, 2012 [Page 4] Internet-Draft VCARD4 LDAP Mapping December 2011 3.7. FreeBusy URL VCard Property: FBURL property as defined in Section 2.3.1 of [RFC2739] and further explained in Section 6.9.1 of [RFC6350]. LDAP Attribute Mapping: Calendar freebusy information access attribute calFBURL as defined in Section 2.4.4.2 and calOtherFBURLs as defined in Section 2.4.4.6 of [RFC2739] respectively. 3.8. Calendar User Address VCard Property: Calendar user address property CALADRURI as defined in Section 2.3.2 [RFC2739] and further explained in Section 6.9.2 of [RFC6350]. LDAP Attribute Mapping: Calendar scheduling Address attribute calCalAdrURI as defined in Section 2.4.4.4 and calOtherCalAdrURIs as defined in Section 2.4.4.8 of [RFC2739] respectively. 4. Security Considerations As this document only defines mapping between VCard 4 properties and parameters to LDAP objectclasses and attributes and does not refer to any actual storage mechanism itself,no special security considerations are required as part of this document. 5. IANA Considerations This document does not request any new IANA registrations. 6. Acknowledgments This specification is a result of discussions that took place within the Calendaring and Scheduling Consortium's Resource Technical Committee. The authors thank the participants of that group. 7. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2739] Small, T., Hennessy, D., and F. Dawson, "Calendar Attributes for vCard and LDAP", RFC 2739, January 2000. [RFC4519] Sciberras, A., "Lightweight Directory Access Protocol (LDAP): Schema for User Applications", RFC 4519, June 2006. Joy, et al. Expires June 15, 2012 [Page 5] Internet-Draft VCARD4 LDAP Mapping December 2011 [RFC4524] Zeilenga, K., "COSINE LDAP/X.500 Schema", RFC 4524, June 2006. [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, August 2011. Authors' Addresses Ciny Joy Oracle Corporation 4210 Network Circle Santa Clara, CA 95054 USA EMail: ciny.joy@oracle.com URI: http://www.oracle.com/ Cyrus Daboo Apple Inc. 1 Infinite Loop Cupertino, CA 95014 USA EMail: cyrus@daboo.name URI: http://www.apple.com/ Michael Douglass Rensselaer Polytechnic Institute 110 8th Street Troy, NY 12180 USA EMail: douglm@rpi.edu URI: http://www.rpi.edu/ Joy, et al. Expires June 15, 2012 [Page 6]