draft-ietf-vcarddav-kind-app-00.txt   rfc6473.txt 
Network Working Group P. Saint-Andre Internet Engineering Task Force (IETF) P. Saint-Andre
Internet-Draft Cisco Request for Comments: 6473 Cisco
Intended status: Standards Track July 27, 2011 Category: Standards Track December 2011
Expires: January 28, 2012 ISSN: 2070-1721
vCard KIND:application vCard KIND:application
draft-ietf-vcarddav-kind-app-00
Abstract Abstract
This document defines a value of "application" for the vCard KIND This document defines a value of "application" for the vCard KIND
property so that vCards can be used to represent software property so that vCards can be used to represent software
applications. applications.
Status of this Memo 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 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 January 28, 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/rfc6473.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
2. Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Meaning .........................................................2
3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Example .........................................................4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations .............................................4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations .........................................4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements ................................................5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References ......................................................5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References .......................................5
7.2. Informative References . . . . . . . . . . . . . . . . . . 6 7.2. Informative References .....................................5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
Version 4 of the vCard specification [VCARD] defines a new "KIND" Version 4 of the vCard specification [RFC6350] defines a new KIND
property to specify the type of entity that a vCard represents. property to specify the type of entity that a vCard represents.
During its work on the base vCard4 specification, the VCARDDAV During its work on the base vCard4 specification, the VCARDDAV
Working Group defined values of "individual", "organization", Working Group defined values of "individual", "organization",
"group", and "location" for the KIND property. The working group "group", and "location" for the KIND property. The working group
considered but then removed a value of "thing" to represent any type considered but then removed a value of "thing" to represent any type
of physical entity, machine, software application, etc., with the of physical entity, machine, software application, etc., with the
expectation that such a value might be defined in a vCard extension. expectation that such a value might be defined in a vCard extension.
This document does not define a generic "thing" value, but instead This document does not define a generic "thing" value but instead
defines a more narrow "application" value so that vCards can be used defines a more narrow "application" value so that vCards can be used
to represent software applications. to represent software applications.
2. Meaning 2. Meaning
When the KIND property has a value of "application", the vCard When the KIND property has a value of "application", the vCard
represents a software application such as a server, an online service represents a software application such as a server, an online service
(e.g., a chatroom), or an automated software bot. More formally, an (e.g., a chat room), or an automated software bot. More formally, an
"application" is functionally equivalent to the 'applicationProcess' "application" is functionally equivalent to the 'applicationProcess'
object class used in the Lightweight Directory Access Protocol object class used in the Lightweight Directory Access Protocol
[RFC4519] as derived from the Open Systems Interconnection model [RFC4519] as derived from the Open Systems Interconnection model
[X.521] and [X.200]. As one example of the "application" KIND, [X.521] [X.200]. As one example of the "application" KIND, vCards
vCards are currently used in the Extensible Messaging and Presence are currently used in the Extensible Messaging and Presence Protocol
Protocol [RFC6120] to represent instant messaging servers that are [RFC6120] to represent instant messaging servers that are deployed on
deployed on the network. the network.
The properties included in an application's vCard apply to one of the The properties included in an application's vCard apply to one of the
following: following:
o The application itself (e.g., the FN property might represent the o The application itself (e.g., the FN property might represent the
friendly name of an application service, the URL property might friendly name of an application service, the URL property might
represent a website that contains further information about the represent a website that contains further information about the
service, and the ADR, GEO, and TZ properties might represent the service, and the ADR, GEO, and TZ properties might represent the
physical address, geographical location, and timezone of the physical address, geographical location, and time zone of the
machine where the service is hosted). machine where the service is hosted).
o An organization or person that makes the application available on o An organization or person that makes the application available on
the network (e.g., the LOGO property might represent the corporate the network (e.g., the LOGO property might represent the corporate
logo of a service provider). logo of a service provider).
o A person or role that maintains the application (e.g., the TEL, o A person or role that maintains the application (e.g., the TEL,
EMAIL, and IMPP properties might represent ways to contact a EMAIL, and IMPP properties might represent ways to contact a
server administrator). server administrator).
When a property represents some aspect of the application itself, it When a property represents some aspect of the application itself, it
makes no sense to include the "work" and "home" values of the TYPE makes no sense to include the "work" and "home" values of the TYPE
parameter since software applications do not have work places and parameter since software applications do not have work places and
personal lives (see the definition of the TYPE parameter in Section personal lives (see the definition of the TYPE parameter in Section
5.6 of [VCARD]). When a property represents information about an 5.6 of [RFC6350]). When a property represents information about an
individual associated with the application (e.g., an individual individual associated with the application (e.g., an individual
service administrator as opposed to a generic service administrator service administrator as opposed to a generic service administrator
role or an associated organization), inclusion of the "work" and role or an associated organization), inclusion of the "work" and
"home" values can be appropriate. "home" values can be appropriate.
The following base properties make sense for vCards that represent The following base properties make sense for vCards that represent
software applications (this list is not exhaustive, and other software applications (this list is not exhaustive, and other
properties might be applicable as well): properties might be applicable as well):
o ADR o ADR
skipping to change at page 4, line 36 skipping to change at page 3, line 47
o ORG o ORG
o PHOTO o PHOTO
o REV o REV
o SOURCE o SOURCE
o TEL o TEL
o TZ o TZ
o URL o URL
Although it might be desirable to define a more fine-grained taxonomy Although it might be desirable to define a more fine-grained taxonomy
of applications (e.g., a KIND of "application" with a subtype of of applications (e.g., a KIND of "application" with a subtype of
"server" or "IM server"), such a taxonomy is out of scope for this "server" or "IM server"), such a taxonomy is out of the scope of this
document. document.
3. Example 3. Example
The following example of an XMPP server is borrowed from [XEP-0292] The following example of an Extensible Messaging and Presence
and uses the XML representation of vCard described in [VCARDXML]. Protocol (XMPP) server is borrowed from [XEP-0292]. The XML
representation of the vCard is described in [RFC6351], which allows
for the use of the new "application" value using the "iana-token"
production defined in [RFC6350].
<vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<fn><text>jabber.org IM service</text></fn> <fn><text>jabber.org IM service</text></fn>
<url><uri>http://www.jabber.org/</uri></url> <url><uri>http://www.jabber.org/</uri></url>
<lang> <lang>
<parameters><pref>1</pref></parameters> <parameters><pref><integer>1</integer></pref></parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<email><text>xmpp@jabber.org</text></email> <email><text>xmpp@jabber.org</text></email>
<impp><uri>xmpp:jabber.org</uri></impp> <impp><uri>xmpp:jabber.org</uri></impp>
<logo><uri>http://www.jabber.org/images/logo.png</uri></logo> <logo><uri>http://www.jabber.org/images/logo.png</uri></logo>
<geo><uri>geo:42.25,-91.05</uri></geo> <geo><uri>geo:42.25,-91.05</uri></geo>
<tz><text>America/Chicago</text></tz> <tz><text>America/Chicago</text></tz>
<source><uri>xmpp:jabber.org?vcard</uri></source> <source><uri>xmpp:jabber.org?vcard</uri></source>
<rev><timestamp>19990104T122100Z</timestamp></rev> <rev><timestamp>19990104T122100Z</timestamp></rev>
<kind><text>application</text></kind> <kind><text>application</text></kind>
</vcard> </vcard>
4. IANA Considerations 4. IANA Considerations
The IANA is requested to add "application" to the registry of IANA has added "application" to the registry of property values for
property values for vCard4. In conformance with Section 10.2.6 of vCard4. In conformance with Section 10.2.6 of [RFC6350], the
[VCARD], the registration is as follows, where the reference is to registration is as follows, where the reference is to RFC 6473.
RFCXXXX.
Value: application Value: application
Purpose: The entity represented by the vCard is a software Purpose: The entity represented by the vCard is a software
application (e.g., a server, an online service such as a chatroom, application (e.g., a server, an online service such as a chat
or an automated software bot). room, or an automated software bot).
Conformance: This value can be used with the "KIND" property.
Example: See Section 3 of RFCXXXX.
[[NOTE TO RFC EDITOR: Please change XXXX to the number assigned to Conformance: This value can be used with the KIND property.
this specification, and remove this paragraph on publication.]]
Example: See Section 3 of RFC 6473.
5. Security Considerations 5. Security Considerations
Use of vCards to represent software applications is not envisioned to Use of vCards to represent software applications is not envisioned to
introduce security considerations beyond those specified for vCards introduce security considerations beyond those specified for vCards
in general as described in [VCARD]. in general as described in [RFC6350].
6. Acknowledgements 6. Acknowledgements
Thanks to Cyrus Daboo, Barry Leiba, Kepeng Li, and Simon Perreault Thanks to Cyrus Daboo, Barry Leiba, Kepeng Li, and Simon Perreault
for their feedback. for their feedback.
7. References 7. References
7.1. Normative References 7.1. Normative References
[VCARD] Perreault, S., "vCard Format Specification", [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
draft-ietf-vcarddav-vcardrev-22 (work in progress), August 2011.
May 2011.
7.2. Informative References 7.2. Informative References
[RFC4519] Sciberras, A., "Lightweight Directory Access Protocol [RFC4519] Sciberras, A., "Lightweight Directory Access Protocol
(LDAP): Schema for User Applications", RFC 4519, (LDAP): Schema for User Applications", RFC 4519,
June 2006. June 2006.
[RFC6120] Saint-Andre, P., "Extensible Messaging and Presence [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Core", RFC 6120, March 2011. Protocol (XMPP): Core", RFC 6120, March 2011.
[VCARDXML] [RFC6351] Perreault, S., "xCard: vCard XML Representation",
Perreault, S., "vCard XML Representation", RFC 6351, August 2011.
draft-ietf-vcarddav-vcardxml-11 (work in progress),
May 2011.
[X.200] International Telecommunications Union, "Information [X.200] International Telecommunications Union, "Information
Technology - Open Systems Interconnection - Basic Technology - Open Systems Interconnection - Basic
Reference Model: The Basic Model", ITU-T Recommendation Reference Model: The Basic Model", ITU-T Recommendation
X.521, ISO Standard 9594-7, February 2001. X.200, ISO Standard 7498-1, July 1994.
[X.521] International Telecommunications Union, "Information [X.521] International Telecommunications Union, "Information
Technology - Open Systems Interconnection - The Directory: Technology - Open Systems Interconnection - The
Selected Object Classes", ITU-T Recommendation X.200, Directory: Selected Object Classes", ITU-T Recommendation
ISO Standard 7498-1, July 1994. X.521, ISO Standard 9594-7, November 2008.
[XEP-0292] [XEP-0292] Saint-Andre, P. and S. Mizzi, "vCard4 over XMPP", XSF
Saint-Andre, P. and S. Mizzi, "vCard4 over XMPP", XSF XEP 0292, October 2011.
XEP 0292, July 2011.
Author's Address Author's Address
Peter Saint-Andre Peter Saint-Andre
Cisco Cisco
1899 Wyknoop Street, Suite 600 1899 Wynkoop Street, Suite 600
Denver, CO 80202 Denver, CO 80202
USA USA
Phone: +1-303-308-3282 Phone: +1-303-308-3282
Email: psaintan@cisco.com EMail: psaintan@cisco.com
 End of changes. 30 change blocks. 
76 lines changed or deleted 69 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/