[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01

Network Working Group                               Frank Dawson, Lotus
Internet Draft                                        Paul Hoffman, IMC
<draft-ietf-calsch-icalfpi-01.txt>
Expires six months after:                                 April 1, 1999


                   iCalendar Formal Public Identifier

Status of this Memo

   This memo is an Internet-Draft and is in full conformance with all
   provisions of Section 10 of RFC 2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   Distribution of this document is unlimited.

   Copyright (C) The Internet Society 1999. All Rights Reserved.

Abstract

   The IETF has defined a standard format for exchanging calendaring and
   scheduling data, called iCalendar. This format is useful for exchange
   of personal calendar data across the Internet, as well as in non-
   Internet environments.

   In a number of environments where the iCalendar will be used, the
   format type and version needs to be identified. For example, when
   registering the iCalendar as a format for memory-based "clipboard" or
   "drag/drop" user interface interactions. For these cases, a
   definitive formal public identifier (FPI) for the iCalendar will be
   required. This memo defined the FPI to be used when referring to the
   version 2.0 (the value in the "VERSION" property) of the iCalendar
   format.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC 2119].

1.      Introduction

   This memo defines a FPI for iCalendar. The format corresponds to the
   version defined by the [RFC 2445] specification and identified in an


Dawson/Hoffman                     1               Expires October 1999


Internet Draft               iCalendar FPI                April 1, 1999


   iCalendar object by the "VERSION:2.0" property:value pair. An FPI is
   an identifier that is used to uniquely identify an entity. The syntax
   for a FPI is defined in [ISO 9070].

   The FPI defined by this memo can be used to register the version 2.0
   of the iCalendar format in an operating system object registry so
   that the format can be uniquely referenced within that environment.
   In addition, this FPI can be used to refer to the iCalendar notation
   in representation grammars, such as that defined by [XML].

2.      iCalendar v2.0 FPI

   The public identified defined by this memo is a non-registered FPI,
   as defined by [ISO 9070]. The FPI is defined by the following text
   string.

        "-//IETF//NOTATION RFC 2445/iCalendar//EN"

   This FPI SHOULD be used where ever a reference is needed to the
   standard iCalendar format defined by [RFC 2445]. For example, the
   following shows how it would be used in an XML notation declaration:

        <!NOTATION iCalendar PUBLIC
        "-//IETF//NOTATION RFC 2445/iCalendar//EN">

3.      Security Considerations

   There are no security issues in the material discussed in this memo.

4.      References

   [ISO 9070] "Information Technology_SGML Support Facilities_
   Registration Procedures for Public Text Owner Identifiers", ISO/IEC
   9070, Second Edition, International Organization for Standardization,
   April, 1991.

   [RFC 2119] "Key words for use in RFCs to Indicate Requirement
   Levels", RFC 2119, March 1997.

   [RFC 2445]  F. Dawson and D. Stenerson, "Internet Calendaring and
   Scheduling Core Object Specification (iCalendar)", RFC 2445,
   http://www.internic.net/rfc/rfc2445.txt, November 1998.

   [XML] "Extensible Markup Language (XML)", Worldwide Web Consortium,
   http://www.w3.org/TR/1998/REC-xml-19980210, February 1998.

5.      Author's Address

   The following address information is provided in a vCard v3.0,
   Electronic Business Card, format.


   BEGIN:VCARD
   VERSION:3.0


Dawson/Hoffman                     2               Expires October 1999


Internet Draft               iCalendar FPI                April 1, 1999


   FN:Frank Dawson
   N:Dawson;Frank
   ORG:Lotus Development Corporation
   ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive;Raleigh;NC;27613
    -3502;USA
   TEL;TYPE=PREF,WORK,MSG:+1-617-693-8728
   TEL;TYPE=WORK,MSG:+1-919-676-9515
   EMAIL;TYPE=PREF,INTERNET:Frank_Dawson@Lotus.com
   EMAIL;TYPE=INTERNET:fdawson@earthlink.net
   END:VCARD


   BEGIN:VCARD
   VERSION:3.0
   FN:Paul Hoffman
   N:Hoffman;Paul
   ORG:Internet Mail Consortium
   ADR;TYPE=WORK,POSTAL,PARCEL:;;127 Segre Place;Santa
    Cruz;CA;95060;USA
   TEL;TYPE=PREF,WORK,MSG:+1-831-426-9827
   TEL;TYPE=WORK,FAX:+1-831-426-7301
   EMAIL;TYPE=INTERNET:phoffman@imc.org
   END:VCARD

   This memo is a result of the work of the Internet Engineering Task
   Force Calendaring and scheduling Working Group. The chairmen of that
   working group are:

   BEGIN:VCARD
   VERSION:3.0
   N:Moskowitz;Robert
   FN:Robert Moskowitz
   EMAIL;TYPE=INTERNET:rgm-ietf@htt-consult.com
   END:VCARD

   BEGIN:VCARD
   VERSION:3.0
   N:Egen;Pat
   FN:Pat Egen
   ORG:Egen Consulting, Inc..
   ADR;TYPE=WORK,POSTAL,PARCEL:;;803 Creek Overlook;
    Chattanooga;TN;37415
   TEL;TYPE=WORK,MSG:+1-423-875-2652
   TEL;TYPE=WORK,FAX:+1-423-875-2017
   EMAIL;TYPE=INTERNET:pregen@egenconsulting.com
   END:VCARD

6.      Full Copyright Statement

   Copyright (C) The Internet Society (1999). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published


Dawson/Hoffman                     3               Expires October 1999


Internet Draft               iCalendar FPI                April 1, 1999


   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process MUST be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.




































Dawson/Hoffman                     4               Expires October 1999


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/