idnits 2.17.1 draft-jennings-impp-vcard-00.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 (February 21, 2003) is 7707 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: August 22, 2003 February 21, 2003 6 vCard Extensions for IMPP 7 draft-jennings-impp-vcard-00 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 August 22, 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 Editor Note: This is an very early draft to facilitate discussion. 48 Table of Contents 50 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. IMPP Type Definition . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 5. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 56 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 57 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5 58 Normative References . . . . . . . . . . . . . . . . . . . . . . 5 59 Informational References . . . . . . . . . . . . . . . . . . . . 6 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 61 Intellectual Property and Copyright Statements . . . . . . . . . 7 63 1. Overview 65 As more and more people use various IM and presence applications, it 66 becomes important for them to be able to share this contact address 67 information along with the rest of their contact information. RFC 68 2425 [1] and RFC 2426 [2] define a standard format for this 69 exchanging contact information referred to as vCard. This document 70 defines a new type for vCard for representing IMPP URLs. It is very 71 similar to existing types for representing email address and 72 telephone contact information. 74 The type entry to hold this new contact information is an IMPP type. 75 The IMPP entry has a single URI that indicates the address of a 76 service that provides IM, PP, or both. There are also some parameters 77 defined that give hints as to when certain URLs would be appropriate. 78 A given vCard can have multiple IMPP entries but each entry can 79 contain only one URL. Each IMPP entry can contain multiple 80 parameters. Any combination of parameters is valid though the same 81 parameter should occur at most once in a given IMPP entry. 83 The normative definition of this new vCard type is given in Section 2 84 and an informational ABNF is provided in Section 3. 86 2. IMPP Type Definition 88 To: ietf-mime-directory@imc.org 90 Subject: Registration of text/directory MIME type IMPP 92 Type name: IMPP 94 Type purpose: To specify the instant messaging and presence protocol 95 communication with the object the vCard represents. 97 Type encoding: 8bit 99 Type value: A single URL. 101 Type special notes: The type can include the type parameter "TYPE" to 102 specify intended use for the URL. The TYPE parameter values can 103 include: 105 An indication of the type of communications this URI is appropriate 106 for. This can be a value of PERSONAL or BUSINESS. 108 An indication of the location of a device associated with this 109 communications. Values can be HOME, WORK, or MOBILE. 111 An indication of some of the core capabilities of this instant 112 messaging system. Values can be PRES, VIDEO, VOICE, TEXT, SMS, 113 NUMERIC, and BEEP. PRES indicates the system supports some presence 114 protocol. VIDEO, VOICE, and TEXT indicate the system supports voice, 115 video, and text messaging respectively. SMS indicates short text 116 messages. Short is not defined here but something like 160 octets may 117 be a reasonable assumption. NUMERIC indicates that only numeric text 118 messages are allowed, while BEEP indicates that indicates that the 119 information the system can deliver is that a message was sent to the 120 target user. 122 The value STORE indicates that the system can store messages for 123 future delivery to intended user. 125 The value PREF indicates this is a preferred address and has the same 126 semantics as the PREF value in a TEL type. 128 3. Formal Grammar 130 The following ABNF grammar[4] extends the grammar found in RFC 2425 131 and RFC 2426. 133 ;For name="IMPP" 134 param = impp-param ; Only impp parameters are allowed 136 value = uri 138 impp-param = "TYPE" "=" impp-type *("," impp-type) 140 impp-type = "PERSONAL" / "BUSINESS" / ; purpose of communications 141 "HOME" / "WORK" / "MOBILE" / ; useful? 142 "VIDEO" / "VOICE" / "TEXT" / ; core capabilities 143 "SMS" / "NUMERIC" / "BEEP" / "PRES" ; needed??? 144 "STORE" / ; like MSG 145 "PREF" / 146 iana-token / x-name; 147 ; Values are case insensitive 149 4. Example 151 BEGIN:vCard 152 VERSION:3.0 153 FN:John Doe 154 IMPP;TYPE=personal,text,store,pref:im:john@example.com 155 END:vCard 157 5. Open Issues 159 Is this needed at all? Other options include just putting URL for 160 IMPP systems in the TEL type. Using the TEL type is undesirable 161 because the semantics for what you can do with it are confusing in 162 the IMPP case and the parameters are not an excellent fit to IMPP. 164 Are PERSONAL and BUSINESS a conflict in meaning with HOME and WORK? 165 In the TEL type HOME and WORK indicated a location but have slowly 166 come to mean an indicator that personal or business communication is 167 requested. Would a person that had a personal mobile phone and a work 168 mobile phone have HOME,MOBILE and WORK,MOBILE? 170 Is there any need for SMS, NUMERIC, BEEP? This is not a system for 171 negating capabilities and these seem like too fine grain of detail. 172 On the other hand the existing vCard supports pagers and such and 173 these definitions would help users avoid sending large messages to 174 GSM cell phones. 176 Is STORE needed? It mirrors the functionality of MSG in the TEL type 177 and a feature supported by many IM systems. 179 Should PP and IM be treated the same way? Would it be better to have 180 an IM type and a PP type instead of the IMPP type? 182 Is there really an IANA registry for this? RFC 2425 and RFC 2426 183 would imply these types are IANA registered. Help! 185 Convergence issues: Is email just TYPE=text,store with an email URL? 186 Is the TEL type just TYPE=voice with a tel URL? 188 6. IANA Considerations 190 Still to do. Section 2 forms the IANA registration. 192 7. Security Considerations 194 Still to do. Does not introduce additional security issues beyond 195 current vCard specification. Note people may consider their presence 196 information more sensitive than some other address information. 198 8. Acknowledgements 200 Thanks to ... 202 Normative References 204 [1] Howes, T., Smith, M. and F. Dawson, "A MIME Content-Type for 205 Directory Information", RFC 2425, September 1998. 207 [2] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 208 2426, September 1998. 210 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 211 Levels", BCP 14, RFC 2119, March 1997. 213 Informational References 215 [4] Crocker, D. and P. Overell, "Augmented BNF for Syntax 216 Specifications: ABNF", RFC 2234, November 1997. 218 Author's Address 220 Cullen Jennings 221 Cisco Systems 222 170 West Tasman Drive 223 MS: SJC-21/3 224 San Jose, CA 95134 225 USA 227 Phone: +1 408 527-9132 228 EMail: fluffy@cisco.com 230 Intellectual Property Statement 232 The IETF takes no position regarding the validity or scope of any 233 intellectual property or other rights that might be claimed to 234 pertain to the implementation or use of the technology described in 235 this document or the extent to which any license under such rights 236 might or might not be available; neither does it represent that it 237 has made any effort to identify any such rights. Information on the 238 IETF's procedures with respect to rights in standards-track and 239 standards-related documentation can be found in BCP-11. Copies of 240 claims of rights made available for publication and any assurances of 241 licenses to be made available, or the result of an attempt made to 242 obtain a general license or permission for the use of such 243 proprietary rights by implementors or users of this specification can 244 be obtained from the IETF Secretariat. 246 The IETF invites any interested party to bring to its attention any 247 copyrights, patents or patent applications, or other proprietary 248 rights which may cover technology that may be required to practice 249 this standard. Please address the information to the IETF Executive 250 Director. 252 Full Copyright Statement 254 Copyright (C) The Internet Society (2003). All Rights Reserved. 256 This document and translations of it may be copied and furnished to 257 others, and derivative works that comment on or otherwise explain it 258 or assist in its implementation may be prepared, copied, published 259 and distributed, in whole or in part, without restriction of any 260 kind, provided that the above copyright notice and this paragraph are 261 included on all such copies and derivative works. However, this 262 document itself may not be modified in any way, such as by removing 263 the copyright notice or references to the Internet Society or other 264 Internet organizations, except as needed for the purpose of 265 developing Internet standards in which case the procedures for 266 copyrights defined in the Internet Standards process must be 267 followed, or as required to translate it into languages other than 268 English. 270 The limited permissions granted above are perpetual and will not be 271 revoked by the Internet Society or its successors or assignees. 273 This document and the information contained herein is provided on an 274 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 275 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 276 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 277 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 278 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 280 Acknowledgement 282 Funding for the RFC Editor function is currently provided by the 283 Internet Society.