idnits 2.17.1 draft-dawson-vcard-fpi-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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 4 longer pages, the longest (page 1) being 62 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([RFC2119]), 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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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 (April 1, 1999) is 9156 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) == Missing Reference: 'ISO 9070' is mentioned on line 71, but not defined == Unused Reference: 'ISO9070' is defined on line 89, but no explicit reference was found in the text == Unused Reference: 'VCARD' is defined on line 97, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO9070' ** Obsolete normative reference: RFC 2426 (ref. 'VCARD') (Obsoleted by RFC 6350) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 6 errors (**), 0 flaws (~~), 7 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Frank Dawson, Lotus 3 Internet Draft Paul Hoffman, IMC 4 5 Expires six months after: April 1, 1999 7 vCard v3.0 Formal Public Identifier 9 Status of this Memo 11 This memo is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC 2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- 22 Drafts as reference material or to cite them other than as "work 23 in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Distribution of this document is unlimited. 33 Copyright (C) The Internet Society 1999. All Rights Reserved. 35 Abstract 37 The IETF has defined a standard format for electronic business 38 card data, called vCard. This format is useful for exchange of 39 personal directory data across the Internet, as well as in non- 40 Internet environments. 42 In a number of environments where the vCard will be used, the 43 format type and version needs to be identified. For example, when 44 registering the vCard as a format for memory-based "clipboard" or 45 "drag/drop" user interface interactions. For these cases, a 46 definitive formal public identifier (FPI) for the vCard will be 47 required. This memo defined the FPI to be used when referring to 48 the version 3.0 of the vCard format. 50 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 51 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", 52 "MAY" and "OPTIONAL" in this document are to be interpreted as 53 described in [RFC 2119]. 55 1. Introduction 57 This memo defines a FPI for the version 3.0 vCard. An FPI is a 58 identifier that is used to uniquely identify an entity. The 59 syntax for a FPI is defined in [ISO 9070]. 61 The FPI defined by this memo can be used to register the version 62 3.0 of the vCard format in an operating system object registry so 63 that the format can be uniquely referenced within that 64 environment. In addition, this FPI can be used to refer to the 65 vCard notation in representation grammars, such as that defined 66 by [XML]. 68 2. vCard v3.0 FPI 70 The public identified defined by this memo is a non-registered 71 FPI, as defined by [ISO 9070]. The FPI is defined by the 72 following text string. 74 "-//IETF//NOTATION RFC 2426/vCard//EN" 76 This FPI SHOULD be used where ever a reference is needed to the 77 version 3.0 vCard format. For example, the following shows how it 78 would be used in an XML notation declaration: 80 83 3. Security Considerations 85 Security issues are not discussed in this memo. 87 4. References 89 [ISO9070] "Information Technology_SGML Support Facilities_ 90 Registration Procedures for Public Text Owner Identifiers", 91 ISO/IEC 9070, Second Edition, International Organization for 92 Standardization, April, 1991. 94 [RFC 2119] "Key words for use in RFCs to Indicate Requirement 95 Levels", RFC 2119, March 1997. 97 [VCARD] F. Dawson and T. Howes, "vCard MIME Directory Profile", 98 RFC 2426, http://www.ietf.org/rfc/rfc2426.txt, September 1998. 100 [XML] "Extensible Markup Language (XML)", Worldwide Web 101 Consortium, http://www.w3.org/TR/1998/REC-xml-19980210, February 102 1998. 104 5. Author's Address 106 The following address information is provided in a vCard v3.0, 107 Electronic Business Card, format. 109 BEGIN:VCARD 110 VERSION:3.0 111 FN:Frank Dawson 112 N:Dawson;Frank 113 ORG:Lotus Development Corporation 114 ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive;Raleigh; 115 NC;27613-3502;USA 116 TEL;TYPE=PREF,WORK,MSG:+1-617-693-8728 117 TEL;TYPE=WORK,MSG:+1-919-676-9515 118 EMAIL;TYPE=PREF,INTERNET:Frank_Dawson@Lotus.com 119 EMAIL;TYPE=INTERNET:fdawson@earthlink.net 120 END:VCARD 122 BEGIN:VCARD 123 VERSION:3.0 124 FN:Paul Hoffman 125 N:Hoffman;Paul 126 ORG:Internet Mail Consortium 127 ADR;TYPE=WORK,POSTAL,PARCEL:;;127 Segre Place;Santa Cruz; 128 CA;95060;USA 129 TEL;TYPE=PREF,WORK,MSG:+1-831-426-9827 130 TEL;TYPE=WORK,MSG:+1-831-426-7301 131 EMAIL;TYPE=INTERNET:phoffman@imc.org 132 END:VCARD 134 6. 136 Full Copyright Statement 138 "Copyright (C) The Internet Society (1999). All Rights Reserved. 140 This document and translations of it may be copied and furnished 141 to others, and derivative works that comment on or otherwise 142 explain it or assist in its implementation may be prepared, 143 copied, published and distributed, in whole or in part, without 144 restriction of any kind, provided that the above copyright notice 145 and this paragraph are included on all such copies and derivative 146 works. However, this document itself may not be modified in any 147 way, such as by removing the copyright notice or references to 148 the Internet Society or other Internet organizations, except as 149 needed for the purpose of developing Internet standards in which 150 case the procedures for copyrights defined in the Internet 151 Standards process MUST be followed, or as required to translate 152 it into languages other than English. 154 The limited permissions granted above are perpetual and will not 155 be revoked by the Internet Society or its successors or assigns. 157 This document and the information contained herein is provided on 158 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 159 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 160 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 161 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 162 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 163 PURPOSE.