idnits 2.17.1 draft-saintandre-vcarddav-thing-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 10, 2011) is 4668 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Saint-Andre 3 Internet-Draft Cisco 4 Intended status: Standards Track July 10, 2011 5 Expires: January 11, 2012 7 vCard KIND:application 8 draft-saintandre-vcarddav-thing-02 10 Abstract 12 This document defines a value of "application" for the vCard KIND 13 property so that vCards can be used to represent software 14 applications. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 11, 2012. 33 Copyright Notice 35 Copyright (c) 2011 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 54 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 55 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 56 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 57 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 58 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 1. Introduction 63 Version 4 of the vCard specification [VCARD] defines a new "KIND" 64 property to specify the type of entity that a vCard represents. 65 During its work on the base vCard4 specification, the VCARDDAV 66 Working Group defined values of "individual", "organization", 67 "group", and "location" for the KIND property. The working group 68 considered but then removed a value of "thing" to represent any type 69 of physical entity, machine, software application, etc., with the 70 expectation that such a value might be defined in a vCard extension. 71 This document does not define a generic "thing" value, but instead 72 defines a more narrow "application" value so that vCards can be used 73 to represent software applications. 75 2. Meaning 77 When the KIND property has a value of "application", the vCard 78 represents a software application such as a server, an online service 79 (e.g., a chatroom), or an automated software bot. More formally, an 80 "application" is functionally equivalent to the 'applicationProcess' 81 object class used in the Lightweight Directory Access Protocol 82 [RFC4519] and derived from the Open Systems Interconnection model 83 [X.521] and [X.200]. As one example of the "application" KIND, 84 vCards are currently used in the Extensible Messaging and Presence 85 Protocol [RFC6120] to represent instant messaging servers that are 86 deployed on the network. 88 The properties included in an application's vCard apply to one of the 89 following: 91 o The application itself (e.g., the FN property might represent the 92 friendly name of an application service, the URL property might 93 represent a website that contains further information about the 94 service, and the ADR, GEO, and TZ properties might represent the 95 physical address, geographical location, and timezone of the 96 machine where the service is hosted). 98 o An organization or person that makes the application available on 99 the network (e.g., the LOGO property might represent the corporate 100 logo of a service provider). 102 o A person or role that maintains the application (e.g., the TEL, 103 EMAIL, and IMPP properties might represent ways to contact a 104 server administrator). 106 Because software applications do not have work places and personal 107 lives, it makes no sense to include the "work" and "home" values of 108 the TYPE parameter in an application's vCard (see Section 5.6 of 109 [VCARD]). 111 The following base properties make sense for vCards that represent 112 software applications (this list is not exhaustive, and other 113 properties might be applicable as well): 115 o ADR 116 o EMAIL 117 o FN 118 o GEO 119 o IMPP 120 o KEY 121 o KIND 122 o LANG 123 o LOGO 124 o NOTE 125 o ORG 126 o PHOTO 127 o REV 128 o SOURCE 129 o TEL 130 o TZ 131 o URL 133 Although it might be desirable to define a more fine-grained taxonomy 134 of applications (e.g., a KIND of "application" with a subtype of 135 "server" or "IM server"), such a taxonomy is out of scope for this 136 document. 138 3. Example 140 The following example of an XMPP server is borrowed from [XEP-0292] 141 and uses the XML representation of vCard described in [VCARDXML]. 143 144 jabber.org IM service 145 http://www.jabber.org/ 146 147 1 148 en 149 150 xmpp@jabber.org 151 xmpp:jabber.org 152 http://www.jabber.org/images/logo.png 153 geo:42.25,-91.05 154 America/Chicago 155 xmpp:jabber.org?vcard 156 19990104T122100Z 157 application 158 160 4. IANA Considerations 162 The IANA is requested to add "application" to the registry of 163 property values for vCard4. In conformance with Section 10.2.6 of 164 [VCARD], the registration is as follows, where the reference is to 165 RFCXXXX. 167 Value: application 168 Purpose: The entity represented by the vCard is a software 169 application (e.g., a server, an online service such as a chatroom, 170 or an automated software bot). 171 Conformance: This value can be used with the "KIND" property. 172 Example: See Section 3 of RFCXXXX. 174 [[NOTE TO RFC EDITOR: Please change XXXX to the number assigned to 175 this specification, and remove this paragraph on publication.]] 177 5. Security Considerations 179 Use of vCards to represent physical objects and software applications 180 is not envisioned to introduce security considerations beyond those 181 specified for vCards in [VCARD]. 183 6. Acknowledgements 185 Thanks to Cyrus Daboo, Barry Leiba, Kepeng Li, and Simon Perreault 186 for their feedback. 188 7. References 190 7.1. Normative References 192 [VCARD] Perreault, S., "vCard Format Specification", 193 draft-ietf-vcarddav-vcardrev-22 (work in progress), 194 May 2011. 196 7.2. Informative References 198 [RFC4519] Sciberras, A., "Lightweight Directory Access Protocol 199 (LDAP): Schema for User Applications", RFC 4519, 200 June 2006. 202 [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence 203 Protocol (XMPP): Core", RFC 6120, March 2011. 205 [VCARDXML] 206 Perreault, S., "vCard XML Representation", 207 draft-ietf-vcarddav-vcardxml-11 (work in progress), 208 May 2011. 210 [X.200] International Telecommunications Union, "Information 211 Technology - Open Systems Interconnection - Basic 212 Reference Model: The Basic Model", ITU-T Recommendation 213 X.521, ISO Standard 9594-7, February 2001. 215 [X.521] International Telecommunications Union, "Information 216 Technology - Open Systems Interconnection - The Directory: 217 Selected Object Classes", ITU-T Recommendation X.200, 218 ISO Standard 7498-1, July 1994. 220 [XEP-0292] 221 Saint-Andre, P. and S. Mizzi, "vCard4 over XMPP", XSF 222 XEP 0292, July 2011. 224 Author's Address 226 Peter Saint-Andre 227 Cisco 228 1899 Wyknoop Street, Suite 600 229 Denver, CO 80202 230 USA 232 Phone: +1-303-308-3282 233 Email: psaintan@cisco.com