idnits 2.17.1 draft-dawson-ical-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 9425 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 70, but not defined == Unused Reference: 'ISO9070' is defined on line 84, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO9070' -- Possible downref: Non-RFC (?) normative reference: ref. 'ICAL' -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 9 errors (**), 0 flaws (~~), 6 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 iCalendar v2.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 exchanging calendaring and 35 scheduling data, called iCalendar. This format is useful for exchange 36 of personal calendar data across the Internet, as well as in non- 37 Internet environments. 39 In a number of environments where the iCalendar will be used, the 40 format type and version needs to be identified. For example, when 41 registering the iCalendar 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 iCalendar will be 44 required. This memo defined the FPI to be used when referring to the 45 version 2.0 (the value in the "VERSION" property) of the iCalendar 46 format. 48 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 49 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and 50 "OPTIONAL" in this document are to be interpreted as described in 51 [RFC 2119]. 53 1. Introduction 55 This memo defines a FPI for iCalendar. The format corresponds to the 56 version defined by the [ICAL] specification and identified in an 57 iCalendar object by the "VERSION:2.0" property:value pair. An FPI is 58 an identifier that is used to uniquely identify an entity. The syntax 59 for a FPI is defined in [ISO 9070]. 61 The FPI defined by this memo can be used to register the version 2.0 62 of the iCalendar format in an operating system object registry so 63 that the format can be uniquely referenced within that environment. 64 In addition, this FPI can be used to refer to the iCalendar notation 65 in representation grammars, such as that defined by [XML]. 67 2. iCalendar v2.0 FPI 69 The public identified defined by this memo is a non-registered FPI, 70 as defined by [ISO 9070]. The FPI is defined by the following text 71 string. 73 "-//IETF//NONSGML iCalendar version 2.0//EN" 75 This FPI SHOULD be used whereever a reference is needed to the 76 version 2.0 iCalendar format. 78 3. Security Considerations 80 Security issues are not discussed in this memo. 82 4. References 84 [ISO9070] "Information Technology_SGML Support Facilities_ 85 Registration Procedures for Public Text Owner Identifiers", ISO/IEC 86 9070, Second Edition, International Organization for Standardization, 87 April, 1991. 89 [RFC 2119] "Key words for use in RFCs to Indicate Requirement 90 Levels", RFC 2119, March 1997. 92 [ICAL] F. Dawson and D. Stenerson, "Internet Calendaring and 93 Scheduling Core Object Specification (iCalendar)", , http://www.internic.net/internet-drafts/draft-ietf-calsch- 95 ical-08.txt, June 1998. 97 [XML] "Extensible Markup Language (XML)", Worldwide Web Consortium, 98 http://www.w3.org/TR/PR-xml-971208, December 1997. 100 5. Author's Address 102 The following address information is provided in a vCard v3.0, 103 Electronic Business Card, format. 105 BEGIN:VCARD 106 VERSION:3.0 107 FN:Frank Dawson 108 N:Dawson;Frank 109 ORG:Lotus Development Corporation 110 ADR;WORK;POSTAL;PARCEL:;;6544 Battleford Drive;Raleigh;NC;27613- 111 3502;USA 112 TEL;PREF;WORK;MSG:+1-617-693-8728 113 TEL;WORK;MSG:+1-919-676-9515 114 EMAIL;PREF;INTERNET:Frank_Dawson@Lotus.com 115 EMAIL;INTERNET:fdawson@earthlink.net 116 END:VCARD 118 BEGIN:VCARD 119 VERSION:3.0 120 FN:Paul Hoffman 121 N:Hoffman;Paul 122 ORG:Internet Mail Consortium 123 ADR;WORK;POSTAL;PARCEL:;;127 Segre Place;Santa Cruz;CA;95060;USA 124 TEL;PREF;WORK;MSG:+1-408-426-9827 125 TEL;WORK;MSG:+1-408-426-7301 126 EMAIL;INTERNET:phoffman@imc.org 127 END:VCARD 129 6. Full Copyright Statement 131 "Copyright (C) The Internet Society (1998). All Rights Reserved. 133 This document and translations of it may be copied and furnished to 134 others, and derivative works that comment on or otherwise explain it 135 or assist in its implementation may be prepared, copied, published 136 and distributed, in whole or in part, without restriction of any 137 kind, provided that the above copyright notice and this paragraph are 138 included on all such copies and derivative works. However, this 139 document itself may not be modified in any way, such as by removing 140 the copyright notice or references to the Internet Society or other 141 Internet organizations, except as needed for the purpose of 142 developing Internet standards in which case the procedures for 143 copyrights defined in the Internet Standards process MUST be 144 followed, or as required to translate it into languages other than 145 English. 147 The limited permissions granted above are perpetual and will not be 148 revoked by the Internet Society or its successors or assigns. 150 This document and the information contained herein is provided on an 151 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 152 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 153 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 154 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 155 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.