From ietf-calsify-bounces@osafoundation.org Mon Feb 1 09:02:41 2010 Return-Path: X-Original-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8322C28C133 for ; Mon, 1 Feb 2010 09:02:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.334 X-Spam-Level: X-Spam-Status: No, score=-102.334 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAfdx8xYUZU0 for ; Mon, 1 Feb 2010 09:02:38 -0800 (PST) Received: from leka.osafoundation.org (leka.osafoundation.org [149.20.54.96]) by core3.amsl.com (Postfix) with ESMTP id 42B3028C14A for ; Mon, 1 Feb 2010 09:02:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 11E3C7841FC; Mon, 1 Feb 2010 09:03:10 -0800 (PST) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMMCTEDR182h; Mon, 1 Feb 2010 09:03:09 -0800 (PST) Received: from leka.osafoundation.org (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 91E9977D709; Mon, 1 Feb 2010 09:03:04 -0800 (PST) X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id E016577D709 for ; Mon, 1 Feb 2010 09:00:48 -0800 (PST) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7aAC5S7l4WCg for ; Mon, 1 Feb 2010 09:00:44 -0800 (PST) Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by leka.osafoundation.org (Postfix) with ESMTP id 8F00577D704 for ; Mon, 1 Feb 2010 09:00:37 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 0) id 3776B28C180; Mon, 1 Feb 2010 09:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100201170002.3776B28C180@core3.amsl.com> Date: Mon, 1 Feb 2010 09:00:02 -0800 (PST) Cc: ietf-calsify@osafoundation.org Subject: [ietf-calsify] I-D ACTION:draft-ietf-calsify-rfc2447bis-08.txt X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RFC2445, 2446 and 2447 Discusions" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ietf-calsify-bounces@osafoundation.org Errors-To: ietf-calsify-bounces@osafoundation.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Calendaring and Scheduling Standards Simplification Working Group of the IETF. Title : iCalendar Message-Based Interoperability Protocol (iMIP) Author(s) : A. Melnikov Filename : draft-ietf-calsify-rfc2447bis-08.txt Pages : 22 Date : 2010-1-30 This document, iCalendar Message-Based Interoperability Protocol (iMIP), specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322, RFC 2045, RFC 2046, RFC 2047 and RFC 2049, and then transported over SMTP. This document is a product of the Calendaring and Scheduling Standards Simplification (calsify) working group. More information about the IETF CALSIFY working group activities can be found on the IETF web site at . The issue tracker for the Calsify WG is located at: A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-calsify-rfc2447bis-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-calsify-rfc2447bis-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-2-1084906.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ietf-calsify mailing list ietf-calsify@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/ietf-calsify --NextPart-- From ietf-calsify-bounces@osafoundation.org Wed Feb 10 12:48:02 2010 Return-Path: X-Original-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CBC928C248 for ; Wed, 10 Feb 2010 12:48:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_65=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYHQb6R+Xg5a for ; Wed, 10 Feb 2010 12:48:01 -0800 (PST) Received: from leka.osafoundation.org (leka.osafoundation.org [149.20.54.96]) by core3.amsl.com (Postfix) with ESMTP id 0306828C293 for ; Wed, 10 Feb 2010 12:48:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 75F0E77D721; Wed, 10 Feb 2010 12:49:12 -0800 (PST) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v4veiq5Ex1fe; Wed, 10 Feb 2010 12:49:12 -0800 (PST) Received: from leka.osafoundation.org (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id BCD1D77D71C; Wed, 10 Feb 2010 12:49:08 -0800 (PST) X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 8DA1A77D71C for ; Wed, 10 Feb 2010 12:49:05 -0800 (PST) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZT1wqsVG69e for ; Wed, 10 Feb 2010 12:49:00 -0800 (PST) Received: from acsinet11.oracle.com (acsinet11.oracle.com [141.146.126.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by leka.osafoundation.org (Postfix) with ESMTP id 47CE977D71B for ; Wed, 10 Feb 2010 12:48:59 -0800 (PST) Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by acsinet11.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o1AKmn9T021094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 10 Feb 2010 20:48:50 GMT Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o1AKml7K021412; Wed, 10 Feb 2010 20:48:48 GMT Received: from hqdfmt01.oracle.com by acsmt355.oracle.com with ESMTP id 21541271265834914; Wed, 10 Feb 2010 12:48:34 -0800 Received: from [10.156.43.80] (/10.156.43.80) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 10 Feb 2010 12:48:33 -0800 Message-ID: <4B731B9B.2010203@oracle.com> Date: Wed, 10 Feb 2010 15:48:27 -0500 From: Bernard Desruisseaux User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: RFC Errata System References: <20100210201830.B92D9E06CC@rfc-editor.org> In-Reply-To: <20100210201830.B92D9E06CC@rfc-editor.org> X-Source-IP: acsmt354.oracle.com [141.146.40.154] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090207.4B731BB0.0197:SCFMA4539814,ss=1,fgs=0 Cc: ietf-calsify@osafoundation.org, arnouten@bzzt.net Subject: Re: [ietf-calsify] [Technical Errata Reported] RFC5545 (2039) X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RFC2445, 2446 and 2447 Discusions" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-calsify-bounces@osafoundation.org Errors-To: ietf-calsify-bounces@osafoundation.org ADs should approve this errata. Thanks, Bernard RFC Errata System wrote: > The following errata report has been submitted for RFC5545, > "Internet Calendaring and Scheduling Core Object Specification (iCalendar)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5545&eid=2039 > > -------------------------------------- > Type: Technical > Reported by: Arnout Engelen > > Section: 4 > > Original Text > ------------- > BEGIN:VALARM > ACTION:AUDIO > TRIGGER:19980403T120000Z > ATTACH;FMTTYPE=audio/basic:http://example.com/pub/audio- > files/ssbanner.aud > REPEAT:4 > DURATION:PT1H > END:VALARM > > > Corrected Text > -------------- > BEGIN:VALARM > ACTION:AUDIO > TRIGGER;VALUE=DATE-TIME:19980403T120000Z > ATTACH;FMTTYPE=audio/basic:http://example.com/pub/audio- > files/ssbanner.aud > REPEAT:4 > DURATION:PT1H > END:VALARM > > > Notes > ----- > The trigger is presented as a DATE-TIME, but the default type of this field is DURATION (3.8.6.3). Either the type must be specified (as per my corrected text), or specified in DURATION format. > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5545 (draft-ietf-calsify-rfc2445bis-10) > -------------------------------------- > Title : Internet Calendaring and Scheduling Core Object Specification (iCalendar) > Publication Date : September 2009 > Author(s) : B. Desruisseaux, Ed. > Category : PROPOSED STANDARD > Source : Calendaring and Scheduling Standards Simplification > Area : Applications > Stream : IETF > Verifying Party : IESG > _______________________________________________ ietf-calsify mailing list ietf-calsify@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/ietf-calsify From ietf-calsify-bounces@osafoundation.org Wed Feb 10 12:48:26 2010 Return-Path: X-Original-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 233EF28C164 for ; Wed, 10 Feb 2010 12:48:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JprsdztTgvE5 for ; Wed, 10 Feb 2010 12:48:25 -0800 (PST) Received: from leka.osafoundation.org (leka.osafoundation.org [149.20.54.96]) by core3.amsl.com (Postfix) with ESMTP id 1CD1D28C0D0 for ; Wed, 10 Feb 2010 12:48:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id EC70E77D72B; Wed, 10 Feb 2010 12:49:35 -0800 (PST) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08acCCgT4O5m; Wed, 10 Feb 2010 12:49:29 -0800 (PST) Received: from leka.osafoundation.org (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 36EFC77D724; Wed, 10 Feb 2010 12:49:28 -0800 (PST) X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id B126D77D726 for ; Wed, 10 Feb 2010 12:49:25 -0800 (PST) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lH3kyNHVIfEx for ; Wed, 10 Feb 2010 12:49:20 -0800 (PST) Received: from acsinet11.oracle.com (acsinet11.oracle.com [141.146.126.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by leka.osafoundation.org (Postfix) with ESMTP id 1274477D724 for ; Wed, 10 Feb 2010 12:49:19 -0800 (PST) Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by acsinet11.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o1AKmp0H021254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 10 Feb 2010 20:48:52 GMT Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o19NmQ7i016356; Wed, 10 Feb 2010 20:48:50 GMT Received: from hqdfmt01.oracle.com by acsmt354.oracle.com with ESMTP id 21540771265834896; Wed, 10 Feb 2010 12:48:16 -0800 Received: from [10.156.43.80] (/10.156.43.80) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 10 Feb 2010 12:48:15 -0800 Message-ID: <4B731B8B.60601@oracle.com> Date: Wed, 10 Feb 2010 15:48:11 -0500 From: Bernard Desruisseaux User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: RFC Errata System References: <20100210195000.CD6A1E06CC@rfc-editor.org> In-Reply-To: <20100210195000.CD6A1E06CC@rfc-editor.org> X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090202.4B731BB3.006A:SCFMA4539814,ss=1,fgs=0 Cc: ietf-calsify@osafoundation.org, arnouten@bzzt.net Subject: Re: [ietf-calsify] [Editorial Errata Reported] RFC5545 (2038) X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RFC2445, 2446 and 2447 Discusions" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-calsify-bounces@osafoundation.org Errors-To: ietf-calsify-bounces@osafoundation.org ADs should approve this errata. Thanks, Bernard RFC Errata System wrote: > The following errata report has been submitted for RFC5545, > "Internet Calendaring and Scheduling Core Object Specification (iCalendar)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5545&eid=2038 > > -------------------------------------- > Type: Editorial > Reported by: Arnout Engelen > > Section: Appendix A > > Original Text > ------------- > 5. The "DURATION" property can no longer appear in "VFREEBUSY" > components. > > A.2. Restrictions Removed > > > > Corrected Text > -------------- > 5. The "DURATION" property can no longer appear in "VFREEBUSY" > components. > > 6. Use of the "charset" Content-Type parameter in MIME transports > is now mandatory. > > A.2. Restrictions Removed > > > > Notes > ----- > > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5545 (draft-ietf-calsify-rfc2445bis-10) > -------------------------------------- > Title : Internet Calendaring and Scheduling Core Object Specification (iCalendar) > Publication Date : September 2009 > Author(s) : B. Desruisseaux, Ed. > Category : PROPOSED STANDARD > Source : Calendaring and Scheduling Standards Simplification > Area : Applications > Stream : IETF > Verifying Party : IESG > _______________________________________________ ietf-calsify mailing list ietf-calsify@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/ietf-calsify From gren.elliot@scalix.com Fri Feb 26 06:04:36 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65B1028C0ED for ; Fri, 26 Feb 2010 06:04:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxiJVi3NclDS for ; Fri, 26 Feb 2010 06:04:35 -0800 (PST) Received: from mail.uk.scalix.com (mail.uk.scalix.com [82.111.253.243]) by core3.amsl.com (Postfix) with ESMTP id 156E428C0E4 for ; Fri, 26 Feb 2010 06:04:27 -0800 (PST) Received: from mail.uk.scalix.com (localhost.localdomain [127.0.0.1]) by mail.uk.scalix.com (8.13.8/8.13.8) with ESMTP id o1QE6ZMc012506 for ; Fri, 26 Feb 2010 14:06:35 GMT Received: from copper.uk.scalix.com (copper.uk.scalix.com [10.11.108.128]) by mail.uk.scalix.com (Scalix SMTP Relay 11.5.0.14001) via ESMTP; Fri, 26 Feb 2010 14:06:34 +0000 (GMT) Date: Fri, 26 Feb 2010 14:06:33 +0000 From: Gren Elliot To: calsify@ietf.org Message-ID: <4B87D569.2080305@scalix.com> x-scalix-Hops: 1 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.8) Gecko/20100216 Lightning/1.0b1 Thunderbird/3.0.2 X-SMP-CT-RefID: str=0001.0A0B0206.4B87D56A.0154,ss=1,fgs=0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------020805000009080902020600" Subject: [calsify] VTIMEZONES with onset times in the future of appointments X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2010 14:04:36 -0000 --------------020805000009080902020600 Content-Type: text/plain; charset="US-ASCII"; format="flowed" Hi, I'm starting to see ICAL appearing in the wild from a well known mobile phone provider's devices with VEVENT dates referencing a VTIMEZONE component whose rules' onset times are in the future of the actual appointment. Any views on how these should be treated? The libical library we use assumes (not unreasonably IMHO) that such times are UTC - which is clearly at odds with the actual intent. For example, the following contains a VTIMEZONE with only 2 rules that first apply from 14th March (DST) or 17th Nov (Standard) this year, but the appointment is on 17th February this year... ... BEGIN:VTIMEZONE TZID:US/Central BEGIN:DAYLIGHT DTSTART:20100314T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:CDT TZOFFSETFROM:-0600 TZOFFSETTO:-0500 END:DAYLIGHT BEGIN:STANDARD DTSTART:20101107T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:CST TZOFFSETFROM:-0500 TZOFFSETTO:-0600 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ... DTSTART;TZID=US/Central:20100217T170000 DTEND;TZID=US/Central:20100217T180000 ... Regards, Gren. -- Gren Elliot Senior Software Engineer *Scalix* gren.elliot@scalix.com Tel: +44 1344 381812 www.scalix.com --------------020805000009080902020600 Content-Type: text/html; charset="US-ASCII" Hi,

I'm starting to see ICAL appearing in the wild from a well known mobile phone provider's devices with VEVENT dates referencing a VTIMEZONE component whose rules' onset times are in the future of the actual appointment.  Any views on how these should be treated?  The libical library we use assumes (not unreasonably IMHO) that such times are UTC - which is clearly at odds with the actual intent.

For example, the following contains a VTIMEZONE with only 2 rules that first apply from 14th March (DST) or 17th Nov (Standard) this year, but the appointment is on 17th February this year...
...
BEGIN:VTIMEZONE
TZID:US/Central
BEGIN:DAYLIGHT
DTSTART:20100314T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20101107T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
...
DTSTART;TZID=US/Central:20100217T170000
DTEND;TZID=US/Central:20100217T180000
...
Regards,
Gren.
-- 
Gren Elliot
Senior Software Engineer
*Scalix*
gren.elliot@scalix.com
Tel: +44 1344 381812
www.scalix.com
--------------020805000009080902020600-- From calsify-bounces@ietf.org Fri Feb 26 06:04:37 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 999513A87BC; Fri, 26 Feb 2010 06:04:37 -0800 (PST) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65B1028C0ED for ; Fri, 26 Feb 2010 06:04:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxiJVi3NclDS for ; Fri, 26 Feb 2010 06:04:35 -0800 (PST) Received: from mail.uk.scalix.com (mail.uk.scalix.com [82.111.253.243]) by core3.amsl.com (Postfix) with ESMTP id 156E428C0E4 for ; Fri, 26 Feb 2010 06:04:27 -0800 (PST) Received: from mail.uk.scalix.com (localhost.localdomain [127.0.0.1]) by mail.uk.scalix.com (8.13.8/8.13.8) with ESMTP id o1QE6ZMc012506 for ; Fri, 26 Feb 2010 14:06:35 GMT Received: from copper.uk.scalix.com (copper.uk.scalix.com [10.11.108.128]) by mail.uk.scalix.com (Scalix SMTP Relay 11.5.0.14001) via ESMTP; Fri, 26 Feb 2010 14:06:34 +0000 (GMT) Date: Fri, 26 Feb 2010 14:06:33 +0000 From: Gren Elliot To: calsify@ietf.org Message-ID: <4B87D569.2080305@scalix.com> x-scalix-Hops: 1 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.8) Gecko/20100216 Lightning/1.0b1 Thunderbird/3.0.2 X-SMP-CT-RefID: str=0001.0A0B0206.4B87D56A.0154,ss=1,fgs=0 MIME-Version: 1.0 Subject: [calsify] VTIMEZONES with onset times in the future of appointments X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0226993561==" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org --===============0226993561== Content-Type: multipart/alternative; boundary="------------020805000009080902020600" --------------020805000009080902020600 Content-Type: text/plain; charset="US-ASCII"; format="flowed" Hi, I'm starting to see ICAL appearing in the wild from a well known mobile phone provider's devices with VEVENT dates referencing a VTIMEZONE component whose rules' onset times are in the future of the actual appointment. Any views on how these should be treated? The libical library we use assumes (not unreasonably IMHO) that such times are UTC - which is clearly at odds with the actual intent. For example, the following contains a VTIMEZONE with only 2 rules that first apply from 14th March (DST) or 17th Nov (Standard) this year, but the appointment is on 17th February this year... ... BEGIN:VTIMEZONE TZID:US/Central BEGIN:DAYLIGHT DTSTART:20100314T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:CDT TZOFFSETFROM:-0600 TZOFFSETTO:-0500 END:DAYLIGHT BEGIN:STANDARD DTSTART:20101107T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:CST TZOFFSETFROM:-0500 TZOFFSETTO:-0600 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ... DTSTART;TZID=US/Central:20100217T170000 DTEND;TZID=US/Central:20100217T180000 ... Regards, Gren. -- Gren Elliot Senior Software Engineer *Scalix* gren.elliot@scalix.com Tel: +44 1344 381812 www.scalix.com --------------020805000009080902020600 Content-Type: text/html; charset="US-ASCII" Hi,

I'm starting to see ICAL appearing in the wild from a well known mobile phone provider's devices with VEVENT dates referencing a VTIMEZONE component whose rules' onset times are in the future of the actual appointment.  Any views on how these should be treated?  The libical library we use assumes (not unreasonably IMHO) that such times are UTC - which is clearly at odds with the actual intent.

For example, the following contains a VTIMEZONE with only 2 rules that first apply from 14th March (DST) or 17th Nov (Standard) this year, but the appointment is on 17th February this year...
...
BEGIN:VTIMEZONE
TZID:US/Central
BEGIN:DAYLIGHT
DTSTART:20100314T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20101107T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
...
DTSTART;TZID=US/Central:20100217T170000
DTEND;TZID=US/Central:20100217T180000
...
Regards,
Gren.
-- 
Gren Elliot
Senior Software Engineer
*Scalix*
gren.elliot@scalix.com
Tel: +44 1344 381812
www.scalix.com
--------------020805000009080902020600-- --===============0226993561== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify --===============0226993561==-- From cyrus@daboo.name Fri Feb 26 07:02:59 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48BA628C14C for ; Fri, 26 Feb 2010 07:02:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaEpEgicQNNS for ; Fri, 26 Feb 2010 07:02:58 -0800 (PST) Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id A5E3528C128 for ; Fri, 26 Feb 2010 07:02:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 54EF4E3E22AF; Fri, 26 Feb 2010 10:05:11 -0500 (EST) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PD24g-wec2-J; Fri, 26 Feb 2010 10:05:10 -0500 (EST) Received: from caldav.corp.apple.com (caldav.corp.apple.com [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id B6CCEE3E22A4; Fri, 26 Feb 2010 10:05:09 -0500 (EST) Date: Fri, 26 Feb 2010 10:05:04 -0500 From: Cyrus Daboo To: Gren Elliot , calsify@ietf.org Message-ID: <4923AE1FFEA8307F842F12B8@caldav.corp.apple.com> In-Reply-To: <4B87D569.2080305@scalix.com> References: <4B87D569.2080305@scalix.com> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1522 Subject: Re: [calsify] VTIMEZONES with onset times in the future of appointments X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2010 15:02:59 -0000 Hi Gren, --On February 26, 2010 2:06:33 PM +0000 Gren Elliot wrote: > I'm starting to see ICAL appearing in the wild from a well known mobile > phone provider's devices with VEVENT dates referencing a VTIMEZONE > component whose rules' onset times are in the future of the actual > appointment. Any views on how these should be treated? The libical > library we use assumes (not unreasonably IMHO) that such times are UTC - > which is clearly at odds with the actual intent. > > For example, the following contains a VTIMEZONE with only 2 rules that > first apply from 14th March (DST) or 17th Nov (Standard) this year, but > the appointment is on 17th February this year... If the timezone id is "well known" you could simply map the client's timezone to one your server has stashed (and which is complete) and just substitute that. Our server does that - we use the Olson db and parse that on startup to cache timezone ids. Then whenever a new id is seen the calendar library loads the timezone definition from our cache rather than use the one in the data provided. Of course this is risky in that it assumes the same timezone id is really being used the same way by both client and server - but at this point I think we have to reasonably make that assumption. One day we will have a standard timezone registry so there would be a guarantee that ids always represent the same set of timezone rules. This is a perfect example of why such a registry is needed! -- Cyrus Daboo From calsify-bounces@ietf.org Fri Feb 26 07:03:00 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E05D28C182; Fri, 26 Feb 2010 07:03:00 -0800 (PST) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48BA628C14C for ; Fri, 26 Feb 2010 07:02:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaEpEgicQNNS for ; Fri, 26 Feb 2010 07:02:58 -0800 (PST) Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id A5E3528C128 for ; Fri, 26 Feb 2010 07:02:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 54EF4E3E22AF; Fri, 26 Feb 2010 10:05:11 -0500 (EST) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PD24g-wec2-J; Fri, 26 Feb 2010 10:05:10 -0500 (EST) Received: from caldav.corp.apple.com (caldav.corp.apple.com [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id B6CCEE3E22A4; Fri, 26 Feb 2010 10:05:09 -0500 (EST) Date: Fri, 26 Feb 2010 10:05:04 -0500 From: Cyrus Daboo To: Gren Elliot , calsify@ietf.org Message-ID: <4923AE1FFEA8307F842F12B8@caldav.corp.apple.com> In-Reply-To: <4B87D569.2080305@scalix.com> References: <4B87D569.2080305@scalix.com> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Disposition: inline; size=1522 Subject: Re: [calsify] VTIMEZONES with onset times in the future of appointments X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org Hi Gren, --On February 26, 2010 2:06:33 PM +0000 Gren Elliot wrote: > I'm starting to see ICAL appearing in the wild from a well known mobile > phone provider's devices with VEVENT dates referencing a VTIMEZONE > component whose rules' onset times are in the future of the actual > appointment. Any views on how these should be treated? The libical > library we use assumes (not unreasonably IMHO) that such times are UTC - > which is clearly at odds with the actual intent. > > For example, the following contains a VTIMEZONE with only 2 rules that > first apply from 14th March (DST) or 17th Nov (Standard) this year, but > the appointment is on 17th February this year... If the timezone id is "well known" you could simply map the client's timezone to one your server has stashed (and which is complete) and just substitute that. Our server does that - we use the Olson db and parse that on startup to cache timezone ids. Then whenever a new id is seen the calendar library loads the timezone definition from our cache rather than use the one in the data provided. Of course this is risky in that it assumes the same timezone id is really being used the same way by both client and server - but at this point I think we have to reasonably make that assumption. One day we will have a standard timezone registry so there would be a guarantee that ids always represent the same set of timezone rules. This is a perfect example of why such a registry is needed! -- Cyrus Daboo _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From calsify-bounces@ietf.org Fri Feb 26 07:51:36 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63DAB3A87A2; Fri, 26 Feb 2010 07:51:36 -0800 (PST) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 430D13A87A2 for ; Fri, 26 Feb 2010 07:51:35 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Duplicate header field: "References" X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihh2IXw16zyc for ; Fri, 26 Feb 2010 07:51:34 -0800 (PST) Received: from mail.uk.scalix.com (mail.uk.scalix.com [82.111.253.243]) by core3.amsl.com (Postfix) with ESMTP id 1AB2B3A86A2 for ; Fri, 26 Feb 2010 07:51:33 -0800 (PST) Received: from mail.uk.scalix.com (localhost.localdomain [127.0.0.1]) by mail.uk.scalix.com (8.13.8/8.13.8) with ESMTP id o1QFrgvB003327; Fri, 26 Feb 2010 15:53:42 GMT Received: from copper.uk.scalix.com (copper.uk.scalix.com [10.11.108.128]) by mail.uk.scalix.com (Scalix SMTP Relay 11.5.0.14001) via ESMTP; Fri, 26 Feb 2010 15:53:41 +0000 (GMT) Date: Fri, 26 Feb 2010 15:53:41 +0000 From: Gren Elliot To: Rick DeNatale , calsify@ietf.org Message-ID: <4B87EE85.3070203@scalix.com> In-Reply-To: References: <4B87D569.2080305@scalix.com> References: x-scalix-Hops: 1 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.8) Gecko/20100216 Lightning/1.0b1 Thunderbird/3.0.2 X-SMP-CT-RefID: str=0001.0A0B0208.4B87EE85.026B,ss=1,fgs=0 MIME-Version: 1.0 Subject: Re: [calsify] VTIMEZONES with onset times in the future of appointments X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org On 26/02/2010 15:14, Rick DeNatale wrote: > As I understand it, in the case of an event time prior to the event > time with a timezone, you should use the UTC offset specified in the > TZOFFSETFROM property of the earliest DAYLIGHT or STANDARD period of > that time zone, which would be the DAYLIGHT period starting at > 20100314T020000, so the offset would be -0600, > > Note that each DAYLIGHT/STANDARD period carries not only the offset to > be applied during that period, but also the offset applied for the > previous period. > > This allows for dealing with times before a given timezone existed, or > more to the point before daylight savings time was introduced to a > given timezone. > Good point - I hadn't thought of that aspect. In which case the problem isn't as bad as I had thought it was. Cyrus's suggestion on using the system timezone definitions in preference also has a lot of merits. I'll probably end up with fixes based on some mix of the 2 ideas (as not all TZIDs may be known on the system). Thanks to you both, Regards, Gren. _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From gren.elliot@scalix.com Fri Feb 26 07:51:35 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 430D13A87A2 for ; Fri, 26 Feb 2010 07:51:35 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Duplicate header field: "References" X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihh2IXw16zyc for ; Fri, 26 Feb 2010 07:51:34 -0800 (PST) Received: from mail.uk.scalix.com (mail.uk.scalix.com [82.111.253.243]) by core3.amsl.com (Postfix) with ESMTP id 1AB2B3A86A2 for ; Fri, 26 Feb 2010 07:51:33 -0800 (PST) Received: from mail.uk.scalix.com (localhost.localdomain [127.0.0.1]) by mail.uk.scalix.com (8.13.8/8.13.8) with ESMTP id o1QFrgvB003327; Fri, 26 Feb 2010 15:53:42 GMT Received: from copper.uk.scalix.com (copper.uk.scalix.com [10.11.108.128]) by mail.uk.scalix.com (Scalix SMTP Relay 11.5.0.14001) via ESMTP; Fri, 26 Feb 2010 15:53:41 +0000 (GMT) Date: Fri, 26 Feb 2010 15:53:41 +0000 From: Gren Elliot To: Rick DeNatale , calsify@ietf.org Message-ID: <4B87EE85.3070203@scalix.com> In-Reply-To: References: <4B87D569.2080305@scalix.com> References: x-scalix-Hops: 1 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.8) Gecko/20100216 Lightning/1.0b1 Thunderbird/3.0.2 X-SMP-CT-RefID: str=0001.0A0B0208.4B87EE85.026B,ss=1,fgs=0 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII"; format="flowed" Subject: Re: [calsify] VTIMEZONES with onset times in the future of appointments X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2010 15:51:35 -0000 On 26/02/2010 15:14, Rick DeNatale wrote: > As I understand it, in the case of an event time prior to the event > time with a timezone, you should use the UTC offset specified in the > TZOFFSETFROM property of the earliest DAYLIGHT or STANDARD period of > that time zone, which would be the DAYLIGHT period starting at > 20100314T020000, so the offset would be -0600, > > Note that each DAYLIGHT/STANDARD period carries not only the offset to > be applied during that period, but also the offset applied for the > previous period. > > This allows for dealing with times before a given timezone existed, or > more to the point before daylight savings time was introduced to a > given timezone. > Good point - I hadn't thought of that aspect. In which case the problem isn't as bad as I had thought it was. Cyrus's suggestion on using the system timezone definitions in preference also has a lot of merits. I'll probably end up with fixes based on some mix of the 2 ideas (as not all TZIDs may be known on the system). Thanks to you both, Regards, Gren. From cyrus@daboo.name Fri Feb 26 12:05:22 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06BF23A883F for ; Fri, 26 Feb 2010 12:05:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.562 X-Spam-Level: X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xfK9Oar-MY0C for ; Fri, 26 Feb 2010 12:05:21 -0800 (PST) Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 0892C3A883E for ; Fri, 26 Feb 2010 12:05:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id D18D4E3E3EE4 for ; Fri, 26 Feb 2010 15:07:36 -0500 (EST) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TsCdav0GBXDx for ; Fri, 26 Feb 2010 15:07:36 -0500 (EST) Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 144F0E3E3ED9 for ; Fri, 26 Feb 2010 15:07:35 -0500 (EST) Date: Fri, 26 Feb 2010 15:07:32 -0500 From: Cyrus Daboo To: calsify@ietf.org Message-ID: X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=364 Subject: [calsify] Individual submission: new iCalendar properties X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2010 20:05:22 -0000 Hi folks, I have just uploaded a new draft that defines some new iCalendar properties (). Several of these are ones that have various X- variants floating around, so this draft is an attempt to standardise the name and usage as per our new IANA registry process. Comments welcome. -- Cyrus Daboo From calsify-bounces@ietf.org Fri Feb 26 12:05:23 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7662C3A883E; Fri, 26 Feb 2010 12:05:23 -0800 (PST) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06BF23A883F for ; Fri, 26 Feb 2010 12:05:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.562 X-Spam-Level: X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xfK9Oar-MY0C for ; Fri, 26 Feb 2010 12:05:21 -0800 (PST) Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 0892C3A883E for ; Fri, 26 Feb 2010 12:05:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id D18D4E3E3EE4 for ; Fri, 26 Feb 2010 15:07:36 -0500 (EST) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TsCdav0GBXDx for ; Fri, 26 Feb 2010 15:07:36 -0500 (EST) Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 144F0E3E3ED9 for ; Fri, 26 Feb 2010 15:07:35 -0500 (EST) Date: Fri, 26 Feb 2010 15:07:32 -0500 From: Cyrus Daboo To: calsify@ietf.org Message-ID: X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Disposition: inline; size=364 Subject: [calsify] Individual submission: new iCalendar properties X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org Hi folks, I have just uploaded a new draft that defines some new iCalendar properties (). Several of these are ones that have various X- variants floating around, so this draft is an attempt to standardise the name and usage as per our new IANA registry process. Comments welcome. -- Cyrus Daboo _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify