idnits 2.17.1 draft-jennings-impp-vcard-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([3]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 28, 2003) is 7607 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) ** Obsolete normative reference: RFC 2425 (ref. '1') (Obsoleted by RFC 6350) ** Obsolete normative reference: RFC 2426 (ref. '2') (Obsoleted by RFC 6350) -- Obsolete informational reference (is this intentional?): RFC 2234 (ref. '4') (Obsoleted by RFC 4234) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IMPP C. Jennings 3 Internet-Draft Cisco Systems 4 Expires: December 27, 2003 June 28, 2003 6 vCard Extensions for IMPP 7 draft-jennings-impp-vcard-01 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at http:// 24 www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This Internet-Draft will expire on December 27, 2003. 31 Copyright Notice 33 Copyright (C) The Internet Society (2003). All Rights Reserved. 35 Abstract 37 This draft describes an extension to vCard to support Instant 38 Messaging (IM) and Presence Protocol (PP) applications. It allows a 39 URL that is associated with IM or PP to be specified inside of a 40 vCard. 42 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 43 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 44 document are to be interpreted as described in RFC 2119 [3]. 46 1. Overview 48 As more and more people use various instant messaging (IM) and 49 presence protocol (PP) applications, it becomes important for them to 50 be able to share this contact address information along with the rest 51 of their contact information. RFC 2425 [1] and RFC 2426 [2] define a 52 standard format for this information which is referred to as vCard. 53 This document defines a new type in a vCard for representing IMPP 54 URLs. It is very similar to existing types for representing email 55 address and telephone contact information. 57 The type entry to hold this new contact information is an IMPP type. 58 The IMPP entry has a single URI that indicates the address of a 59 service that provides IM, PP, or both. Also defined are some 60 parameters that give hints as to when certain URLs would be 61 appropriate. A given vCard can have multiple IMPP entries but each 62 entry can contain only one URL. Each IMPP entry can contain multiple 63 parameters. Any combination of parameters is valid, though a 64 parameter should occur at most once in a given IMPP entry. 66 The normative definition of this new vCard type is given in Section 2 67 and an informational ABNF is provided in Section 3. 69 2. IMPP Type Definition 71 To: ietf-mime-directory@imc.org 73 Subject: Registration of text/directory MIME type IMPP 75 Type name: IMPP 77 Type purpose: To specify the URL for instant messaging and presence 78 protocol communication with the object the vCard represents. 80 Type encoding: 8bit 82 Type value: A single URL. 84 Type special notes: The type can include the type parameter "TYPE" to 85 specify an intended use for the URL. The TYPE parameter values can 86 include: 88 An indication of the type of communication for which this URL is 89 appropriate. This can be a value of PERSONAL or BUSINESS. 91 An indication of the location of a device associated with this URL. 92 Values can be HOME, WORK, or MOBILE. 94 An indication of some of the core capabilities of this instant 95 messaging system. Values can be PRES, VIDEO, VOICE, TEXT, SMS, 96 NUMERIC, and BEEP. PRES indicates the system supports some presence 97 protocol. VIDEO, VOICE, and TEXT indicate the system supports voice, 98 video, and text messaging respectively. SMS indicates short text 99 messages. Short is not defined here but something like 160 octets may 100 be a reasonable assumption. NUMERIC indicates that only numeric text 101 messages are allowed. BEEP indicates that the only information the 102 system can deliver is that a message was sent to the target user. 104 The value STORE indicates that the system can store messages for 105 future delivery to intended the intended user. 107 The value PREF indicates this is a preferred address and has the same 108 semantics as the PREF value in a TEL type. 110 3. Formal Grammar 112 The following ABNF grammar[4] extends the grammar found in RFC 2425 113 [1] and RFC 2426 [2]. 115 ;For name="IMPP" 116 param = impp-param ; Only impp parameters are allowed 118 value = uri 120 impp-param = "TYPE" "=" impp-type *("," impp-type) 122 impp-type = "PERSONAL" / "BUSINESS" / ; purpose of communications 123 "HOME" / "WORK" / "MOBILE" / ; useful? 124 "VIDEO" / "VOICE" / "TEXT" / ; core capabilities 125 "SMS" / "NUMERIC" / "BEEP" / "PRES" ; needed??? 126 "STORE" / ; like MSG 127 "PREF" / 128 iana-token / x-name; 129 ; Values are case insensitive 131 4. Example 133 BEGIN:vCard 134 VERSION:3.0 135 FN:John Doe 136 IMPP;TYPE=personal,text,store,pref:im:john@example.com 137 END:vCard 139 5. IANA Considerations 141 Section 2 forms the IANA registration. 143 6. Security Considerations 145 This does not introduce additional security issues beyond current 146 vCard specification. It is worth noting that many people consider 147 their presence information more sensitive than some other address 148 information. Any system that stores or transfers vCards needs to 149 carefully consider the privacy issues around this information. 151 Normative References 153 [1] Howes, T., Smith, M. and F. Dawson, "A MIME Content-Type for 154 Directory Information", RFC 2425, September 1998. 156 [2] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 157 2426, September 1998. 159 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 160 Levels", BCP 14, RFC 2119, March 1997. 162 Informational References 164 [4] Crocker, D. and P. Overell, "Augmented BNF for Syntax 165 Specifications: ABNF", RFC 2234, November 1997. 167 Author's Address 169 Cullen Jennings 170 Cisco Systems 171 170 West Tasman Drive 172 MS: SJC-21/3 173 San Jose, CA 95134 174 USA 176 Phone: +1 408 527-9132 177 EMail: fluffy@cisco.com 179 Intellectual Property Statement 181 The IETF takes no position regarding the validity or scope of any 182 intellectual property or other rights that might be claimed to 183 pertain to the implementation or use of the technology described in 184 this document or the extent to which any license under such rights 185 might or might not be available; neither does it represent that it 186 has made any effort to identify any such rights. Information on the 187 IETF's procedures with respect to rights in standards-track and 188 standards-related documentation can be found in BCP-11. Copies of 189 claims of rights made available for publication and any assurances of 190 licenses to be made available, or the result of an attempt made to 191 obtain a general license or permission for the use of such 192 proprietary rights by implementors or users of this specification can 193 be obtained from the IETF Secretariat. 195 The IETF invites any interested party to bring to its attention any 196 copyrights, patents or patent applications, or other proprietary 197 rights which may cover technology that may be required to practice 198 this standard. Please address the information to the IETF Executive 199 Director. 201 Full Copyright Statement 203 Copyright (C) The Internet Society (2003). All Rights Reserved. 205 This document and translations of it may be copied and furnished to 206 others, and derivative works that comment on or otherwise explain it 207 or assist in its implementation may be prepared, copied, published 208 and distributed, in whole or in part, without restriction of any 209 kind, provided that the above copyright notice and this paragraph are 210 included on all such copies and derivative works. However, this 211 document itself may not be modified in any way, such as by removing 212 the copyright notice or references to the Internet Society or other 213 Internet organizations, except as needed for the purpose of 214 developing Internet standards in which case the procedures for 215 copyrights defined in the Internet Standards process must be 216 followed, or as required to translate it into languages other than 217 English. 219 The limited permissions granted above are perpetual and will not be 220 revoked by the Internet Society or its successors or assignees. 222 This document and the information contained herein is provided on an 223 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 224 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 225 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 226 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 227 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 229 Acknowledgement 231 Funding for the RFC Editor function is currently provided by the 232 Internet Society.