draft-ietf-vcarddav-oma-cab-extensions-03.txt   rfc6715.txt 
vcarddav D. Cauchie Internet Engineering Task Force (IETF) D. Cauchie
Internet-Draft France Telecom - Orange Request for Comments: 6715 France Telecom - Orange
Intended status: Standards Track B. Leiba Category: Standards Track B. Leiba
Expires: December 20, 2012 K. Li ISSN: 2070-1721 K. Li
Huawei Technologies Huawei Technologies
June 18, 2012 August 2012
vCard Format extension : represent vCard extensions defined by the Open vCard Format Extensions: Representing vCard Extensions Defined by the
Mobile Alliance (OMA) Converged Address Book (CAB) group Open Mobile Alliance (OMA) Converged Address Book (CAB) Group
draft-ietf-vcarddav-oma-cab-extensions-03
Abstract Abstract
This document defines extensions to the vCard data format for This document defines extensions to the vCard data format for
representing and exchanging certain contact information. The representing and exchanging certain contact information. The
properties covered here have been defined by the Open Mobile Alliance properties covered here have been defined by the Open Mobile Alliance
Converged Address Book group, in order to synchronize, using OMA Data (OMA) Converged Address Book group, in order to synchronize, using
Synchronization, contact fields that were not already defined in the OMA Data Synchronization, contact fields that were not already
base vCard 4.0 specification. defined in the base vCard 4.0 specification.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on December 20, 2012. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6715.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
1.1. A Brief Introduction to the Converged Address Book . . . . . 3 1.1. A Brief Introduction to the Converged Address Book .........2
1.2. Terminology Used in This Document . . . . . . . . . . . . . 3 1.2. Terminology Used in This Document ..........................3
2. vCard Extensions: Properties ....................................3
2. vCard Extensions : Properties . . . . . . . . . . . . . . . 4 2.1. Property: EXPERTISE ........................................3
2.1. Property : EXPERTISE . . . . . . . . . . . . . . . . . . . . 4 2.2. Property: HOBBY ............................................4
2.2. Property : HOBBY . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Property: INTEREST .........................................5
2.3. Property : INTEREST . . . . . . . . . . . . . . . . . . . . 6 2.4. Property: ORG-DIRECTORY ....................................6
2.4. Property : ORG-DIRECTORY . . . . . . . . . . . . . . . . . . 7 3. vCard Extensions: Parameters ....................................7
3.1. Parameter: INDEX ...........................................7
3. vCard extensions : Parameters . . . . . . . . . . . . . . . 8 3.2. Parameter: LEVEL ...........................................8
3.1. Parameter : INDEX . . . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations .........................................8
3.2. Parameter : LEVEL . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations .............................................9
6. Acknowledgments .................................................9
4. Security Considerations . . . . . . . . . . . . . . . . . . 10 7. References .....................................................10
7.1. Normative References ......................................10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10 7.2. Informative References ....................................10
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Synchronization of an Open Mobile Alliance Converged Address Book Synchronization of an Open Mobile Alliance Converged Address Book
[OMA-CAB], using Open Mobile Alliance Data Synchronization [OMA-DS], [OMA-CAB], using Open Mobile Alliance Data Synchronization [OMA-DS],
commonly uses vCard as an exchange format between the DS Server and commonly uses vCard as an exchange format between the DS Server and
the DS Client. In order to properly perform synchronization of an the DS Client. In order to properly perform synchronization of an
OMA-CAB, the CAB specification defines some CAB contact fields not OMA-CAB, the CAB specification defines some CAB contact fields not
already defined in the vCard base specification. This document re- already defined in the vCard base specification. This document
uses the definitions found in the OMA-CAB specification and describes reuses the definitions found in the OMA-CAB specification and
them as vCard extensions. The following sections define the describes them as vCard extensions. The following sections define
necessary Properties and Parameters. the necessary Properties and Parameters.
1.1. A Brief Introduction to the Converged Address Book 1.1. A Brief Introduction to the Converged Address Book
The Converged Address Book (CAB) Enabler provides consistent The Converged Address Book (CAB) Enabler provides consistent
mechanisms to manage contact information both in user-facing mechanisms to manage contact information both in user-facing
applications and in support of network-facing activities. At the applications and in support of network-facing activities. At the
core of this enabler is a network-based contact repository in which a core of this enabler is a network-based contact repository in which a
user can store contact information. That information can be user can store contact information. That information can be
retrieved by any CAB-enabled device. The network-based repository is retrieved by any CAB-enabled device. The network-based repository is
also able to provide specific contact information to other users and also able to provide specific contact information to other users and
to keep their copies up to date whenever the information is changed. to keep their copies up to date whenever the information is changed.
The CAB Enabler provides synchronization of the contact information The CAB Enabler provides synchronization of the contact information
available in the user device(s) with the network-based contact available in the user device(s) with the network-based contact
repository. repository.
The CAB Enabler also manages the distribution of a user's own contact The CAB Enabler also manages the distribution of a user's own contact
information. In essence, a user fills out a Personal Contact Card, information. In essence, a user fills out a Personal Contact Card,
which includes all the information a user wishes to store about him which includes all the information a user wishes to store about
or herself. himself or herself.
Because systems that are supporting the CAB Enabler are likely Because systems that are supporting the CAB Enabler are likely
supporting multiple users, the CAB Enabler also defines a search supporting multiple users, the CAB Enabler also defines a search
paradigm that permits other users to query those systems to locate paradigm that permits other users to query those systems to locate
information about the available users. information about the available users.
The CAB Enabler supports many different types of information. It, The CAB Enabler supports many different types of information. It
therefore, has a data model that is flexible and extensible. It therefore has a data model that is flexible and extensible. It
manages traditional types of contact information (such as name, manages traditional types of contact information (such as name,
address, email, phone number, mobile number) as well as new types of address, email, phone number, mobile number) as well as new types of
information (such as websites, blogs, presence subscription information (such as websites, blogs, presence subscription
references). references).
1.2. Terminology Used in This Document 1.2. Terminology Used in This Document
Syntax specifications shown here use the augmented Backus-Naur Form Syntax specifications shown here use the augmented Backus-Naur Form
(ABNF) as described in [RFC5234], and are specified as in the base (ABNF) as described in [RFC5234] and are specified as in the base
vcard specification [RFC6350]. vCard specification [RFC6350].
2. vCard Extensions : Properties 2. vCard Extensions: Properties
The following sections define the CAB Properties. The following sections define the CAB Properties.
Note: Note:
Some string-value vCard properties are defined herein for which no Some string-value vCard properties are defined herein for which no
specific list of allowed strings is specified. For those properties, specific list of allowed strings is specified. For those properties,
it is intended that de-facto taxonomies might develop. One vCard it is intended that de facto taxonomies might develop. One vCard
can, for example, specify a hobby of "philately", while another uses can, for example, specify a hobby of "philately", while another uses
"stamp collecting", and a third has "old postage stamps". Usage, not "stamp collecting", and a third has "old postage stamps". Usage, not
specification, may lead to a preference over time for a single term. specification, may lead to a preference over time for a single term.
In general, these are meant to be understood by humans, rather than In general, these are meant to be understood by humans, rather than
to be used for automated categorization that might require standard to be used for automated categorization that might require standard
terms and registries. terms and registries.
2.1. Property : EXPERTISE 2.1. Property: EXPERTISE
Namespace: Namespace:
Property name: EXPERTISE Property name: EXPERTISE
Purpose: To specify a field of expertise for the object that the Purpose: To specify a field of expertise for the object to which the
vCard refers to. vCard refers.
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
Property parameters: LEVEL (possible values : "beginner", "average", Property parameters: LEVEL (possible values: "beginner", "average",
"expert"), INDEX "expert"), INDEX
Description: This is intended to be a free-form naming of fields of Description: This is intended to be a free-form naming of fields of
expertise, meant for human consumption, and no specific expertise expertise, meant for human consumption, and no specific
fields are defined. See the note at the beginning of Section 2. expertise fields are defined. See the note at the
beginning of Section 2.
Format definition: Format definition:
EXPERTISE-param = LEVEL-param / INDEX-param / language-param / EXPERTISE-param = LEVEL-param / INDEX-param / language-param /
pref-param / altid-param / type-param / any-param pref-param / altid-param / type-param /
any-param
EXPERTISE-value = text EXPERTISE-value = text
Examples: Examples:
EXPERTISE;LEVEL=beginner;INDEX=2:chinese literature EXPERTISE;LEVEL=beginner;INDEX=2:chinese literature
EXPERTISE;INDEX=1;LEVEL=expert:chemistry EXPERTISE;INDEX=1;LEVEL=expert:chemistry
2.2. Property : HOBBY 2.2. Property: HOBBY
Namespace: Namespace:
Property name: HOBBY Property name: HOBBY
Purpose: To specify the hobbies of the object that the vCard refers Purpose: To specify the hobbies of the object to which the vCard
to. refers.
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
Property parameters: LEVEL (possible values : "high", "medium", Property parameters: LEVEL (possible values: "high", "medium",
"low"), INDEX "low"), INDEX
Description: This is intended to be a free-form naming of hobbies, Description: This is intended to be a free-form naming of hobbies,
meant for human consumption, and no specific hobbies are defined. meant for human consumption, and no specific hobbies
See the note at the beginning of Section 2. are defined. See the note at the beginning of
Section 2.
A hobby, as opposed to an interest (see Section 2.3) is an A hobby, as opposed to an interest (see Section 2.3),
activity that one actively engages in for entertainment, is an activity that one actively engages in for
intellectual stimulation, creative expression, or the like. entertainment, intellectual stimulation, creative
expression, or the like.
* "Art" might be a hobby if one actively sculpts or paints. * "Art" might be a hobby if one actively sculpts or paints.
* "Tennis" might be a hobby if one enjoys playing, rather than * "Tennis" might be a hobby if one enjoys playing, rather than
just watching matches. just watching, matches.
Format definition: Format definition:
HOBBY-param = LEVEL-param / INDEX-param / language-param / pref- HOBBY-param = LEVEL-param / INDEX-param / language-param /
param / altid-param / type-param / any-param pref-param / altid-param / type-param / any-param
HOBBY-value = text HOBBY-value = text
Examples: Examples:
HOBBY;INDEX=1;LEVEL=high:reading HOBBY;INDEX=1;LEVEL=high:reading
HOBBY;INDEX=2;LEVEL=high:sewing HOBBY;INDEX=2;LEVEL=high:sewing
2.3. Property : INTEREST 2.3. Property: INTEREST
Namespace: Namespace:
Property name: INTEREST Property name: INTEREST
Purpose: To specify the interest(s) of the object that the vCard Purpose: To specify the interest(s) of the object to which the vCard
refers to. refers.
Value type: A single text value Value type: A single text value
Cardinality: * Cardinality: *
Property parameters: LEVEL (possible values : "high", "medium", Property parameters: LEVEL (possible values: "high", "medium",
"low"), INDEX "low"), INDEX
Description: This is intended to be a free-form naming of interests, Description: This is intended to be a free-form naming of interests,
meant for human consumption, and no specific interests are meant for human consumption, and no specific interests
defined. See the note at the beginning of Section 2. are defined. See the note at the beginning of
Section 2.
An interest, as opposed to a hobby (see Section 2.2) is an An interest, as opposed to a hobby (see Section 2.2),
activity or topic that one finds interesting, but doesn't is an activity or topic that one finds interesting but
necessarily actively engage in. doesn't necessarily actively engage in.
* "Art" might be an interest if one likes looking at art, but * "Art" might be an interest if one likes looking at art but
doesn't create art. doesn't create art.
* "Tennis" might be an interest if one enjoys watching matches, * "Tennis" might be an interest if one enjoys watching matches
but doesn't play. but doesn't play.
Format definition: Format definition:
INTEREST-param = LEVEL-param / INDEX-param / language-param / INTEREST-param = LEVEL-param / INDEX-param / language-param /
pref-param / altid-param / type-param / any-param pref-param / altid-param / type-param /
any-param
INTEREST-value = text INTEREST-value = text
Examples: Examples:
INTEREST;INDEX=1;LEVEL=medium:r&b music INTEREST;INDEX=1;LEVEL=medium:r&b music
INTEREST;INDEX=2;LEVEL=high:rock'n roll music INTEREST;INDEX=2;LEVEL=high:rock 'n' roll music
2.4. Property : ORG-DIRECTORY 2.4. Property: ORG-DIRECTORY
Namespace: Namespace:
Property name: ORG-DIRECTORY Property name: ORG-DIRECTORY
Purpose: To specify a directory of an organization the vCard's Purpose: To specify a directory of an organization to which the
entity belongs to. vCard's entity belongs.
Value type: A single URI value. Value type: A single URI value.
Cardinality: * Cardinality: *
Property parameters: PREF, INDEX Property parameters: PREF, INDEX
Description: This is intended to be a URI that can be used to do an Description: This is intended to be a URI that can be used to do an
organization-directory lookup. Presumably, the entity the vCard organization-directory lookup. Presumably, the entity
represents would be found in the directory, though that isn't the vCard represents would be found in the directory,
required. This might be used to make it easier to find someone's though that isn't required. This might be used to make
co-workers, management chain, and so on, in a company or it easier to find someone's coworkers, management
organizational directory. chain, and so on, in a company or organizational
directory.
How the lookup is done depends upon the URI scheme, and no How the lookup is done depends upon the URI scheme, and
attempt is made here to specify details of the lookup mechanism. no attempt is made here to specify details of the
An HTTP URI might, for example, lead to a web form that's lookup mechanism. An HTTP URI might, for example, lead
intended for manual lookup in a browser -- thus, this URI might to a web form that's intended for manual lookup in a
or might not be useable for automated lookup or searching. browser; thus, this URI might or might not be usable
for automated lookup or searching.
Format definition: Format definition:
ORG-DIRECTORY-param = pref-param / INDEX-param / language-param ORG-DIRECTORY-param = pref-param / INDEX-param / language-param
/ pid-param / pref-param / altid-param / type-param / / pid-param / pref-param / altid-param /
any-param type-param / any-param
ORG-DIRECTORY-value= uri ORG-DIRECTORY-value= uri
Examples: Examples:
ORG-DIRECTORY;INDEX=1:http://directory.mycompany.example.com ORG-DIRECTORY;INDEX=1:http://directory.mycompany.example.com
ORG-DIRECTORY;PREF=1:ldap://ldap.tech.example/ ORG-DIRECTORY;PREF=1:ldap://ldap.tech.example/
o=Example%20Tech,ou=Engineering o=Example%20Tech,ou=Engineering
3. vCard extensions : Parameters 3. vCard Extensions: Parameters
The following sections define Parameters used within Properties The following sections define Parameters used within Properties
definitions. definitions.
3.1. Parameter : INDEX 3.1. Parameter: INDEX
Namespace: Namespace:
Parameter name: INDEX Parameter name: INDEX
Purpose: Used in a multi-valued property to indicate the position of Purpose: Used in a multi-valued property to indicate the position of
this value within the set of values. this value within the set of values.
Description: When a property is multi-valued, INDEX can be used to Description: When a property is multi-valued, INDEX can be used to
indicate an ordering or sequence of the values. INDEX values indicate an ordering or sequence of the values. INDEX
MUST be strictly positive. Zero is not allowed. values must be strictly positive. Zero is not allowed.
Format definition: Format definition:
INDEX-param = "INDEX=" INDEX-value INDEX-param = "INDEX=" INDEX-value
INDEX-value = integer INDEX-value = integer
Examples: Examples:
ORG-URI;INDEX=1:http://mycompany.example1.com ORG-URI;INDEX=1:http://mycompany.example1.com
ORG-URI;PREF=1;INDEX=2:http://mycompany.example2.com ORG-URI;PREF=1;INDEX=2:http://mycompany.example2.com
3.2. Parameter : LEVEL 3.2. Parameter: LEVEL
Namespace: Namespace:
Parameter name: LEVEL Parameter name: LEVEL
Purpose: Used to indicate a level of expertise, hobby or interest Purpose: Used to indicate a level of expertise, hobby, or interest
attained by the object the vCard represents. attained by the object the vCard represents.
Description: Allowable values: Description: Allowable values:
* "beginner", "average", "expert" when used with EXPERTISE * "beginner", "average", "expert" when used with EXPERTISE
* "high", "medium", "low" when used with HOBBY or INTEREST * "high", "medium", "low" when used with HOBBY or INTEREST
Format definition: Format definition:
LEVEL-param = "LEVEL=" LEVEL-value LEVEL-param = "LEVEL=" LEVEL-value
LEVEL-value = "beginner" / "average" / "expert" / "high" / LEVEL-value = "beginner" / "average" / "expert" / "high" /
"medium" / "low" "medium" / "low"
Examples: Examples:
EXPERTISE;LEVEL=beginner:chinese literature EXPERTISE;LEVEL=beginner:chinese literature
HOBBY;LEVEL=high:reading HOBBY;LEVEL=high:reading
INTEREST;LEVEL=medium:r&b music INTEREST;LEVEL=medium:r&b music
4. Security Considerations 4. Security Considerations
This document presents no security considerations beyond those in This document presents no security considerations beyond those in
section 9 of the base vcard specification [RFC6350]. Section 9 of the base vCard specification [RFC6350].
5. IANA Considerations 5. IANA Considerations
IANA is requested to add the following entries to the vCard IANA has added the following entries to the "vCard Properties"
Properties registry, defined in [RFC6350] section 10.3.1. registry, defined in [RFC6350] Section 10.3.1.
+-------+---------------------------+-------------------+ +-------+------------------------+------------------------+
| Name | | | | Name- | | |
| space | Property | Reference | | space | Property | Reference |
+-------+---------------------------+-------------------+ +-------+------------------------+------------------------+
| | EXPERTISE | RFCXXXX, sec 2.1 | | | EXPERTISE | RFC 6715, Section 2.1 |
| | HOBBY | RFCXXXX, sec 2.2 | | | HOBBY | RFC 6715, Section 2.2 |
| | INTEREST | RFCXXXX, sec 2.3 | | | INTEREST | RFC 6715, Section 2.3 |
| | ORG-URI | RFCXXXX, sec 2.4 | | | ORG-URI | RFC 6715, Section 2.4 |
+-------+---------------------------+-------------------+ +-------+------------------------+------------------------+
IANA is requested to add the following entries to the vCard IANA has added the following entries to the "vCard Parameters"
Parameters registry, defined in [RFC6350] section 10.3.2. registry, defined in [RFC6350] Section 10.3.2.
+-------+---------------------------+-------------------+ +-------+------------------------+------------------------+
| Name | | | | Name- | | |
| space | Parameter | Reference | | space | Parameter | Reference |
+-------+---------------------------+-------------------+ +-------+------------------------+------------------------+
| | INDEX | RFCXXXX, sec 3.1 | | | INDEX | RFC 6715, Section 3.1 |
| | LEVEL | RFCXXXX, sec 3.2 | | | LEVEL | RFC 6715, Section 3.2 |
+-------+---------------------------+-------------------+ +-------+------------------------+------------------------+
IANA is requested to add the following entries to the vCard Values IANA has added the following entries to the "vCard Parameter Values"
registry, defined in [RFC6350] section 10.3.4. registry, defined in [RFC6350] Section 10.3.4.
+-----------+-----------+---------------+-------------------+ +-----------+-----------+---------------+------------------------+
| Property | Parameter | Value | Reference | | Property | Parameter | Value | Reference |
+-----------+-----------+---------------+-------------------+ +-----------+-----------+---------------+------------------------+
| EXPERTISE | LEVEL | beginner | RFCXXXX, sec 3.2 | | EXPERTISE | LEVEL | beginner | RFC 6715, Section 3.2 |
| EXPERTISE | LEVEL | average | RFCXXXX, sec 3.2 | | EXPERTISE | LEVEL | average | RFC 6715, Section 3.2 |
| EXPERTISE | LEVEL | expert | RFCXXXX, sec 3.2 | | EXPERTISE | LEVEL | expert | RFC 6715, Section 3.2 |
| HOBBY | LEVEL | high | RFCXXXX, sec 3.2 | | HOBBY | LEVEL | high | RFC 6715, Section 3.2 |
| HOBBY | LEVEL | medium | RFCXXXX, sec 3.2 | | HOBBY | LEVEL | medium | RFC 6715, Section 3.2 |
| HOBBY | LEVEL | low | RFCXXXX, sec 3.2 | | HOBBY | LEVEL | low | RFC 6715, Section 3.2 |
| INTEREST | LEVEL | high | RFCXXXX, sec 3.2 | | INTEREST | LEVEL | high | RFC 6715, Section 3.2 |
| INTEREST | LEVEL | medium | RFCXXXX, sec 3.2 | | INTEREST | LEVEL | medium | RFC 6715, Section 3.2 |
| INTEREST | LEVEL | low | RFCXXXX, sec 3.2 | | INTEREST | LEVEL | low | RFC 6715, Section 3.2 |
+-----------+---------------------------+-------------------+ +-----------+---------------------------+------------------------+
6. Acknowledgments 6. Acknowledgments
Thanks to Simon Perreault, Peter Saint-Andre, Cyrus Daboo, and Chris Thanks to Simon Perreault, Peter Saint-Andre, Cyrus Daboo, and Chris
Newman for particularly thorough reviews, which led to a much cleaner Newman for particularly thorough reviews, which led to a much cleaner
submission to the working group. submission to the working group.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Specifications: ABNF", STD 68, RFC 5234, January 2008. Syntax Specifications: ABNF", STD 68, RFC 5234,
January 2008.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011. August 2011.
7.2. Informative References 7.2. Informative References
[OMA-CAB] Open Mobile Alliance, "Converged Address Book (CAB) [OMA-CAB] Open Mobile Alliance, "Converged Address Book (CAB)
Specification", October 2010, <http:// Specification", October 2010, <http://
www.openmobilealliance.org/Technical/release_program/docs/ www.openmobilealliance.org/Technical/release_program/docs/
CopyrightClick.aspx?pck=CAB&file=V1_0-20101019-C/ CopyrightClick.aspx?pck=CAB&file=V1_0-20101019-C/
OMA-TS-CAB-V1_0-20101019-C.pdf>. OMA-TS-CAB-V1_0-20101019-C.pdf>.
Candidate Version 1.0, OMA-TS-CAB-V1_0-20101019-C Candidate Version 1.0, OMA-TS-CAB-V1_0-20101019-C
[OMA-DS] Open Mobile Alliance, "Data Synchronization Protocol", [OMA-DS] Open Mobile Alliance, "DS Protocol", March 2009, <http://
March 2009, <http://www.openmobilealliance.org/Technical/ www.openmobilealliance.org/Technical/release_program/docs/
release_program/docs/
copyrightclick.aspx?pck=DS&file=V1_2_2-20090319-A/ copyrightclick.aspx?pck=DS&file=V1_2_2-20090319-A/
OMA-TS-DS_Protocol-V1_2_2-20090319-A.pdf>. OMA-TS-DS_Protocol-V1_2_2-20090319-A.pdf>.
Candidate Version 1.2.2, OMA-TS-DS_Protocol-V1_2_2-
20090319-A
Authors' Addresses Authors' Addresses
Dany Cauchie Dany Cauchie
France Telecom - Orange France Telecom - Orange
2 Avenue Pierre Marzin 2 Avenue Pierre Marzin
Lannion 22307 Lannion 22307
France France
Phone: +33 2 96 05 31 16 Phone: +33 2 96 05 31 16
Email: dany.cauchie@orange.com EMail: dany.cauchie@orange.com
Barry Leiba Barry Leiba
Huawei Technologies Huawei Technologies
Phone: +1 646 827 0648 Phone: +1 646 827 0648
Email: barryleiba@computer.org EMail: barryleiba@computer.org
URI: http://internetmessagingtechnology.org/ URI: http://internetmessagingtechnology.org/
Kepeng Li Kepeng Li
Huawei Technologies Huawei Technologies
Phone: +86 755 28974289 Phone: +86 755 28974289
Email: likepeng@huawei.com EMail: likepeng@huawei.com
 End of changes. 61 change blocks. 
166 lines changed or deleted 160 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/