idnits 2.17.1 draft-dawson-vcard-fpi-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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 3 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 (July 1, 1998) is 9430 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 67, but not defined == Unused Reference: 'ISO9070' is defined on line 81, but no explicit reference was found in the text == Unused Reference: 'VCARD' is defined on line 89, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO9070' -- Possible downref: Non-RFC (?) normative reference: ref. 'VCARD' -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 9 errors (**), 0 flaws (~~), 7 warnings (==), 5 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: July 1, 1998 7 vCard v3.0 Formal Public Identifier 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months. Internet-Drafts may be updated, replaced, or made obsolete by 18 other documents at any time. It is not appropriate to use Internet- 19 Drafts as reference material or to cite them other than as a "working 20 draft" or "work in progress". 22 To view the entire list of current Internet-Drafts, please check the 23 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 24 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 25 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 26 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 28 Distribution of this document is unlimited. 30 Copyright (C) The Internet Society 1998. All Rights Reserved. 32 Abstract 34 The IETF has defined a standard format for electronic business card 35 data, called vCard. This format is useful for exchange of personal 36 directory data across the Internet, as well as in non-Internet 37 environments. 39 In a number of environments where the vCard will be used, the format 40 type and version needs to be identified. For example, when 41 registering the vCard as a format for memory-based "clipboard" or 42 "drag/drop" user interface interactions. For these cases, a 43 definitive formal public identifier (FPI) for the vCard will be 44 required. This memo defined the FPI to be used when referring to the 45 version 3.0 of the vCard format. 47 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 48 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and 49 "OPTIONAL" in this document are to be interpreted as described in 50 [RFC 2119]. 52 1. Introduction 54 This memo defines a FPI for the version 3.0 vCard. An FPI is a 55 identifier that is used to uniquely identify an entity. The syntax 56 for a FPI is defined in [ISO 9070]. 58 The FPI defined by this memo can be used to register the version 3.0 59 of the vCard format in an operating system object registry so that 60 the format can be uniquely referenced within that environment. In 61 addition, this FPI can be used to refer to the vCard notation in 62 representation grammars, such as that defined by [XML]. 64 2. vCard v3.0 FPI 66 The public identified defined by this memo is a non-registered FPI, 67 as defined by [ISO 9070]. The FPI is defined by the following text 68 string. 70 "-//IETF//NONSGML vCard version 3.0//EN" 72 This FPI SHOULD be used whereever a reference is needed to the 73 version 3.0 vCard format. 75 3. Security Considerations 77 Security issues are not discussed in this memo. 79 4. References 81 [ISO9070] "Information Technology_SGML Support Facilities_ 82 Registration Procedures for Public Text Owner Identifiers", ISO/IEC 83 9070, Second Edition, International Organization for Standardization, 84 April, 1991. 86 [RFC 2119] "Key words for use in RFCs to Indicate Requirement 87 Levels", RFC 2119, March 1997. 89 [VCARD] F. Dawson and T. Howes, "vCard MIME Directory Profile", , http://www.internic.net/internet-drafts/draft- 91 ietf-asid-mime-vcard-06.txt, April 1998. 93 [XML] "Extensible Markup Language (XML)", Worldwide Web Consortium, 94 http://www.w3.org/TR/PR-xml-971208, December 1997. 96 5. Author's Address 98 The following address information is provided in a vCard v3.0, 99 Electronic Business Card, format. 101 BEGIN:VCARD 102 VERSION:3.0 103 FN:Frank Dawson 104 N:Dawson;Frank 105 ORG:Lotus Development Corporation 106 ADR;WORK;POSTAL;PARCEL:;;6544 Battleford Drive;Raleigh;NC;27613- 107 3502;USA 108 TEL;PREF;WORK;MSG:+1-617-693-8728 109 TEL;WORK;MSG:+1-919-676-9515 110 EMAIL;PREF;INTERNET:Frank_Dawson@Lotus.com 111 EMAIL;INTERNET:fdawson@earthlink.net 112 END:VCARD 114 BEGIN:VCARD 115 VERSION:3.0 116 FN:Paul Hoffman 117 N:Hoffman;Paul 118 ORG:Internet Mail Consortium 119 ADR;WORK;POSTAL;PARCEL:;;127 Segre Place;Santa Cruz;CA;95060;USA 120 TEL;PREF;WORK;MSG:+1-408-426-9827 121 TEL;WORK;MSG:+1-408-426-7301 122 EMAIL;INTERNET:phoffman@imc.org 123 END:VCARD 125 6. Full Copyright Statement 127 "Copyright (C) The Internet Society (1998). All Rights Reserved. 129 This document and translations of it may be copied and furnished to 130 others, and derivative works that comment on or otherwise explain it 131 or assist in its implementation may be prepared, copied, published 132 and distributed, in whole or in part, without restriction of any 133 kind, provided that the above copyright notice and this paragraph are 134 included on all such copies and derivative works. However, this 135 document itself may not be modified in any way, such as by removing 136 the copyright notice or references to the Internet Society or other 137 Internet organizations, except as needed for the purpose of 138 developing Internet standards in which case the procedures for 139 copyrights defined in the Internet Standards process MUST be 140 followed, or as required to translate it into languages other than 141 English. 143 The limited permissions granted above are perpetual and will not be 144 revoked by the Internet Society or its successors or assigns. 146 This document and the information contained herein is provided on an 147 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 148 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 149 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 150 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 151 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.