From cyrus at daboo.name Wed Feb 1 07:02:55 2006 From: cyrus at daboo.name (Cyrus Daboo) Date: Wed Feb 1 07:03:29 2006 Subject: [Ietf-calsify] Small nit in draft-ietf-calsify-rfc2445bis-00.txt In-Reply-To: <6.2.1.2.0.20060131213036.01ebc8e0@mail.comcast.net> References: <6.2.1.2.0.20060121225101.01e89f68@mail.comcast.net> <6B6F861D-B888-4D15-8952-27E2541A9DEC@osafoundation.org> <43D5158C.9040809@Royer.com> <9BACEA7F-4C31-4C04-8469-B6B06D951A03@osafoundation.org> <6.2.1.2.0.20060131213036.01ebc8e0@mail.comcast.net> Message-ID: <8E753F706A8830F9C6FAFF61@Cyrus-Daboo.local> Hi Tim, --On January 31, 2006 9:32:32 PM -0500 Tim Hare wrote: > 6. An implementation MAY truncate a "SUMMARY" property value to 255 > characters. This raises another issue I just spotted with the use of the terms 'octets' and 'characters'. The first thing to note is that a certain number of octets is not necessarily the same number of characters if non-ascii characters are present with utf-8 encoding. So in the above situation, a truncation at 255 characters could actually result in say 1024 octets if each character was a 4-octet utf-8 sequence. I suggest metioning this in Section 4 to clarify the use of 'octets' vs 'characters'. It may be worth adding an example to Section 5.3 showing non-ascii text being split on a proper character boundary. -- Cyrus Daboo From cyrus at daboo.name Wed Feb 1 07:21:50 2006 From: cyrus at daboo.name (Cyrus Daboo) Date: Wed Feb 1 07:21:55 2006 Subject: [Ietf-calsify] Properties and parameters Message-ID: <6F310B9F4D610FC4623148F3@Cyrus-Daboo.local> Hi, 2445bis now mixes properties and parameter definitions within the same sections. I actually find it a lot harder to navigate around to find a particular definition of either a property or parameter now. What would be extremely useful is an index for the definition of each component, property, parameter and value type. The table of contents is not as good for lookup as it was before. -- Cyrus Daboo From Doug at Royer.com Wed Feb 1 08:50:05 2006 From: Doug at Royer.com (Doug Royer) Date: Wed Feb 1 08:50:14 2006 Subject: [Ietf-calsify] Properties and parameters In-Reply-To: <6F310B9F4D610FC4623148F3@Cyrus-Daboo.local> References: <6F310B9F4D610FC4623148F3@Cyrus-Daboo.local> Message-ID: <43E0E6BD.6060100@Royer.com> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4532 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20060201/4af0cded/smime.bin From lisa at osafoundation.org Fri Feb 3 15:02:46 2006 From: lisa at osafoundation.org (Lisa Dusseault) Date: Fri Feb 3 15:02:52 2006 Subject: [Ietf-calsify] Fwd: Internet-Drafts Submission Cutoff Dates for the 65th IETF Meeting in Dallas, TX, USA References: Message-ID: <2117C8A3-AF20-48A8-8EC1-7751CDAF9E26@osafoundation.org> Very important dates for the authors/editors in this WG! I am still hoping we can do better than to just barely hit the dates. Having only one draft out between meetings, and only just before the draft deadline, is not optimal for WG meeting planning and effective agendas. I would encourage the authors/editors to submit works in progress as we're not expecting to see polished, finished results at this time. Lisa Begin forwarded message: > From: ietf-secretariat@ietf.org > Date: February 2, 2006 9:00:01 PM PST > To: ietf-announce@ietf.org > Subject: Internet-Drafts Submission Cutoff Dates for the 65th IETF > Meeting in Dallas, TX, USA > > > There are two (2) Internet-Draft cutoff dates for the 65th > IETF Meeting in Dallas, TX, USA: > > February 27th: Cutoff Date for Initial (i.e., version -00) > Internet-Draft Submissions > > All initial Internet-Drafts (version -00) must be submitted by Monday, > February 27th at 9:00 AM ET. As always, all initial submissions with a > filename beginning with "draft-ietf" must be approved by the > appropriate WG Chair before they can be processed or announced. The > Secretariat would appreciate receiving WG Chair approval by Monday, > February 20th at 9:00 AM ET. > > March 6th: Cutoff Date for Revised (i.e., version -01 and higher) > Internet-Draft Submissions > > All revised Internet-Drafts (version -01 and higher) must be submitted > by Monday, March 6th at 9:00 AM ET. > > Initial and revised Internet-Drafts received after their respective > cutoff dates will not be made available in the Internet-Drafts > directory or announced until on or after Monday, March 20th at 9:00 > AM ET, when Internet-Draft posting resumes. Please do not wait until > the last minute to submit. > > Thank you for your understanding and cooperation. If you have any > questions or concerns, then please send a message to > internet-drafts@ietf.org. > > The IETF Secretariat > > FYI: The Internet-Draft cutoff dates as well as other significant > dates > for the 65th IETF Meeting can be found at http://www.ietf.org/ > meetings/cutoff_dates_65.html. > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20060203/279372b6/attachment.htm From daniele.tiles at gmail.com Sun Feb 12 11:03:56 2006 From: daniele.tiles at gmail.com (Daniele Tiles) Date: Sun Feb 12 11:03:59 2006 Subject: [Ietf-calsify] Most used TZID and Olson Database Message-ID: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> Hi to all, I would like to add a very-basilar support to TimeZone in my Calendar Application...as I read in the RFC, and as I saw working with some iCalendars, the id's of the Olson database seems to be the most used...so, I would like to ask: --Is this actually true? Has anyone got any statistics or something like that? --I'm working on Windows, and what I would REALLY need is a list of the Olson database id's (like Europe/Rome) and they correspondet UTC... Could someone help me? :) Bye Daniele Tiles -- http://remotecalendars.sf.net http://www.icalx.com/html/lasthope/month.php?cal=lasthope.public http://www.universibo.unibo.it -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20060212/09f9407a/attachment.htm From cyrus at daboo.name Sun Feb 12 17:04:31 2006 From: cyrus at daboo.name (Cyrus Daboo) Date: Sun Feb 12 17:04:35 2006 Subject: [Ietf-calsify] Most used TZID and Olson Database In-Reply-To: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> References: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> Message-ID: Hi Daniele, --On February 12, 2006 8:03:56 PM +0100 Daniele Tiles wrote: > I would like to add a very-basilar support to TimeZone in my Calendar > Application...as I read in the RFC, and as I saw working with some > iCalendars, the id's of the Olson database seems to be the most > used...so, I would like to ask: > --Is this actually true? Has anyone got any statistics or something like > that? The Calconnect Timezone questionnaire we did last year did indicate that a majority of respondents used the Olson DB: -- Cyrus Daboo From daniele.tiles at gmail.com Mon Feb 13 10:37:29 2006 From: daniele.tiles at gmail.com (Daniele Tiles) Date: Mon Feb 13 10:37:32 2006 Subject: [Ietf-calsify] Most used TZID and Olson Database In-Reply-To: References: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> Message-ID: <6bd837ee0602131037i4e1e8bb5s1023d5d07234e373@mail.gmail.com> Hi, thank you very much for the quick answer (this somehow helps me...I'm on the right way :))...do you know anything like a simple file containing the Olson Id and the correspondent UTC offset? It would be helpful (it's so annoying that there isn't anything ready under Windows...) Bye Daniele The Calconnect Timezone questionnaire we did last year did indicate that a > majority of respondents used the Olson DB: > > < > http://www.calconnect.org/publications/resultsfromtimezonequestionnairev1.0.pdf > > > > > -- > Cyrus Daboo > > -- http://www.icalx.com/html/lasthope/month.php?cal=lasthope.public http://www.universibo.unibo.it webcal://www.rememberthemilk.com/icalendar/daniele.tiles/121631/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20060213/1171b461/attachment.htm From dmose at mozilla.org Tue Feb 14 13:47:35 2006 From: dmose at mozilla.org (Dan Mosedale) Date: Wed Feb 22 09:22:35 2006 Subject: [Ietf-calsify] calendar apps that generate multiple VALARMs per event? Message-ID: <43F24FF7.4030403@mozilla.org> I'm trying to understand the use of multiple VALARMs per event, and I'm wondering how much, it happens in the real world. Having both an email and an audio alarm on an event seems like a reasonable enough use-case. Do folks know of any calendar apps that generate multiple VALARMs today, or plan to in the future? Dan From helge.hess at opengroupware.org Wed Feb 22 09:34:56 2006 From: helge.hess at opengroupware.org (Helge Hess) Date: Wed Feb 22 09:35:13 2006 Subject: [Ietf-calsify] calendar apps that generate multiple VALARMs per event? In-Reply-To: <43F24FF7.4030403@mozilla.org> References: <43F24FF7.4030403@mozilla.org> Message-ID: <79C3ECD0-1296-470F-8D93-299DD1F56211@opengroupware.org> On 14. Feb 2006, at 22:47 Uhr, Dan Mosedale wrote: > Do folks know of any calendar apps that generate multiple VALARMs > today Apple iCal.app allows to add multiple alarms. Greets, Helge -- http://docs.opengroupware.org/Members/helge/ OpenGroupware.org From reinhold at kainhofer.com Wed Feb 22 09:40:48 2006 From: reinhold at kainhofer.com (Reinhold Kainhofer) Date: Wed Feb 22 09:41:22 2006 Subject: [Ietf-calsify] calendar apps that generate multiple VALARMs per event? In-Reply-To: <43F24FF7.4030403@mozilla.org> References: <43F24FF7.4030403@mozilla.org> Message-ID: <200602221840.49165.reinhold@kainhofer.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Dienstag, 14. Februar 2006 22:47 schrieb Dan Mosedale: > I'm trying to understand the use of multiple VALARMs per event, and I'm > wondering how much, it happens in the real world. Having both an email > and an audio alarm on an event seems like a reasonable enough use-case. > Do folks know of any calendar apps that generate multiple VALARMs today, > or plan to in the future? Yes, KOrganizer does since KDE 3.4 or 3.5. There's an additional tab for all the various alarm settings (relative to start/end of event, type, offset, repeat, etc.): http://www.fam.tuwien.ac.at/~reinhold/KOrganizer/KOrganizer_MultipleAlarms.jpg Cheers, Reinhold - -- - ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: reinhold@kainhofer.com, http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD/KIhTqjEwhXvPN0RArtVAJ48OxdMMrg4/1pzsPiP298sWMQJ7ACg0GMp oCz8D0os4y6VyYPDNTHye6o= =m6Rx -----END PGP SIGNATURE----- From bernard.desruisseaux at oracle.com Wed Feb 22 19:08:46 2006 From: bernard.desruisseaux at oracle.com (Bernard Desruisseaux) Date: Wed Feb 22 19:09:01 2006 Subject: [Ietf-calsify] CalDAV draft Informal Last-Call Message-ID: <43FD273E.3020702@oracle.com> We submitted CalDAV draft -10 to the IETF yesterday. The draft has not been officially announced yet, but it is already available for you to review at the following URL: http://ietf.webdav.org/caldav/draft-dusseault-caldav-10.txt We would like to submit the CalDAV draft for Last Call in time for the 65th IETF Meeting in Dallas (i.e., really soon!). Before we do so, we would like to get as much feedback as possible from the participants of the "ietf-caldav" mailing list as well as from the members of the WebDAV and Calsify Working Groups. Once officially announced the draft should be available at: http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt Previous versions of the draft are available at: http://ietfreport.isoc.org/idref/draft-dusseault-caldav/ Discussion on CalDAV is taking place on the "ietf-caldav" mailing list: mailto:ietf-caldav@osafoundation.org which is archived at: http://lists.osafoundation.org/mailman/listinfo/ietf-caldav Reports on the 4 CalDAV Interoperability Events organized by the Calendaring and Scheduling Consortium (CalConnect) can be found at: http://www.calconnect.org/ioppast.html Finally, additional information on CalDAV can also be found at: http://ietf.webdav.org/caldav/ Please review draft -10 and send us feedback/questions/comments. Thanks for you help! Cheers, Bernard -- C.1. Changes in -10 a. Added new section about support for X- items when storing data. b. Added new precondition to allow servers to reject queries on unsupported X- items, and a new example. c. Added new text about always supporting X- in calendar-data. d. Created new section for PUT, COPY and MOVE preconditions. e. Report examples re-done with full listing of calendar data in Appendix. f. Removed description of using UID, SUMMARY etc as resource name. g. Indicate that calendar object resource may contain only overridden components. h. Add security consideration about not expose details in resource names. i. Add constraint that free-busy-query can only be run on a collection. j. Add preconditions for calendar-timezone property/elements in MKCALENDAR, PROPPATCH and calendar-query REPORT. k. Fix principal-match example. From bernard.desruisseaux at oracle.com Thu Feb 23 06:59:15 2006 From: bernard.desruisseaux at oracle.com (Bernard Desruisseaux) Date: Thu Feb 23 07:01:02 2006 Subject: [Ietf-calsify] Re: CalDAV draft Informal Last-Call In-Reply-To: <43FD6D6F.3030308@gmx.de> References: <43FD273E.3020702@oracle.com> <43FD6D6F.3030308@gmx.de> Message-ID: <43FDCDC3.3000004@oracle.com> Julian, Thanks for your feedback! The idea to do an informal last call is exactly to get this kind of feedback. :-) Lisa, Cyrus and I already discussed about the possibility of making reference to RFC2518bis. We will consider your feedback on this issue. Meanwhile, it would be appreciated if you could elaborate some more on the implication of referencing RFC2518bis instead of RFC2518 in CalDAV. Thanks, Bernard P.S. I have printed rfc2518bis and will take the time to review it! Julian Reschke wrote: > Hm. > > It strikes me as a particularly bad idea to last-call a draft that > builds on top of RFC2518, while, at the same time, RFC2518bis is last > called. > > Reasons: > > - you will likely have to update the spec to refer to rfc2518bis instead > anyway, and this frequently is more work than just updating a single > reference (in particular, the stuff about ETags in section 5.3.4 is > partly in conflict with RFC2616, and likely to be in conflict with the > separate document about ETag handling in HTTP the IETF has decided to > produce). > > - the group of people who can give constructive feedback to CalDAV > definitively overlaps with those who can review RFC2518bis. > > Therefore I strongly suggest not to last-call anything WebDAV related > before RFC2518bis' last call has ended. > > Best regards, Julian > > > Bernard Desruisseaux wrote: > >> >> We submitted CalDAV draft -10 to the IETF yesterday. The draft has >> not been officially announced yet, but it is already available for >> you to review at the following URL: >> >> http://ietf.webdav.org/caldav/draft-dusseault-caldav-10.txt >> >> We would like to submit the CalDAV draft for Last Call in time for >> the 65th IETF Meeting in Dallas (i.e., really soon!). Before we do >> so, we would like to get as much feedback as possible from the >> participants of the "ietf-caldav" mailing list as well as from the >> members of the WebDAV and Calsify Working Groups. >> >> Once officially announced the draft should be available at: >> >> http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt >> >> Previous versions of the draft are available at: >> >> http://ietfreport.isoc.org/idref/draft-dusseault-caldav/ >> >> Discussion on CalDAV is taking place on the "ietf-caldav" mailing list: >> >> mailto:ietf-caldav@osafoundation.org >> >> which is archived at: >> >> http://lists.osafoundation.org/mailman/listinfo/ietf-caldav >> >> Reports on the 4 CalDAV Interoperability Events organized by the >> Calendaring and Scheduling Consortium (CalConnect) can be found at: >> >> http://www.calconnect.org/ioppast.html >> >> Finally, additional information on CalDAV can also be found at: >> >> http://ietf.webdav.org/caldav/ >> >> Please review draft -10 and send us feedback/questions/comments. >> >> Thanks for you help! >> >> Cheers, >> Bernard >> >> -- >> >> C.1. Changes in -10 >> >> a. Added new section about support for X- items when storing data. >> >> b. Added new precondition to allow servers to reject queries on >> unsupported X- items, and a new example. >> >> c. Added new text about always supporting X- in calendar-data. >> >> d. Created new section for PUT, COPY and MOVE preconditions. >> >> e. Report examples re-done with full listing of calendar data in >> Appendix. >> >> f. Removed description of using UID, SUMMARY etc as resource name. >> >> g. Indicate that calendar object resource may contain only >> overridden components. >> >> h. Add security consideration about not expose details in resource >> names. >> >> i. Add constraint that free-busy-query can only be run on a >> collection. >> >> j. Add preconditions for calendar-timezone property/elements in >> MKCALENDAR, PROPPATCH and calendar-query REPORT. >> >> k. Fix principal-match example. >> >> >> >> > > From bernard.desruisseaux at oracle.com Thu Feb 23 19:06:41 2006 From: bernard.desruisseaux at oracle.com (Bernard Desruisseaux) Date: Thu Feb 23 19:06:51 2006 Subject: [Ietf-calsify] [Fwd: I-D ACTION:draft-dusseault-caldav-10.txt] Message-ID: <43FE7841.5040506@oracle.com> -------- Original Message -------- Subject: I-D ACTION:draft-dusseault-caldav-10.txt Date: Thu, 23 Feb 2006 15:50:01 -0500 From: Internet-Drafts@ietf.org Reply-To: internet-drafts@ietf.org To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Calendaring Extensions to WebDAV (CalDAV) Author(s) : L. Dusseault, et al. Filename : draft-dusseault-caldav-10.txt Pages : 94 Date : 2006-2-23 This document specifies a set of methods, headers, message bodies, properties, and reports that define calendar access extensions to the WebDAV protocol. The new protocol elements are intended to make WebDAV-based calendaring and scheduling an interoperable standard that supports calendar access, calendar management, calendar sharing, and calendar publishing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-dusseault-caldav-10.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-dusseault-caldav-10.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. -------------- next part -------------- Skipped content of type message/external-body-------------- next part -------------- _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce From julian.reschke at gmx.de Thu Feb 23 00:08:15 2006 From: julian.reschke at gmx.de (Julian Reschke) Date: Tue Mar 7 14:31:15 2006 Subject: [Ietf-calsify] Re: CalDAV draft Informal Last-Call In-Reply-To: <43FD273E.3020702@oracle.com> References: <43FD273E.3020702@oracle.com> Message-ID: <43FD6D6F.3030308@gmx.de> Hm. It strikes me as a particularly bad idea to last-call a draft that builds on top of RFC2518, while, at the same time, RFC2518bis is last called. Reasons: - you will likely have to update the spec to refer to rfc2518bis instead anyway, and this frequently is more work than just updating a single reference (in particular, the stuff about ETags in section 5.3.4 is partly in conflict with RFC2616, and likely to be in conflict with the separate document about ETag handling in HTTP the IETF has decided to produce). - the group of people who can give constructive feedback to CalDAV definitively overlaps with those who can review RFC2518bis. Therefore I strongly suggest not to last-call anything WebDAV related before RFC2518bis' last call has ended. Best regards, Julian Bernard Desruisseaux wrote: > > We submitted CalDAV draft -10 to the IETF yesterday. The draft has > not been officially announced yet, but it is already available for > you to review at the following URL: > > http://ietf.webdav.org/caldav/draft-dusseault-caldav-10.txt > > We would like to submit the CalDAV draft for Last Call in time for > the 65th IETF Meeting in Dallas (i.e., really soon!). Before we do > so, we would like to get as much feedback as possible from the > participants of the "ietf-caldav" mailing list as well as from the > members of the WebDAV and Calsify Working Groups. > > Once officially announced the draft should be available at: > > http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt > > Previous versions of the draft are available at: > > http://ietfreport.isoc.org/idref/draft-dusseault-caldav/ > > Discussion on CalDAV is taking place on the "ietf-caldav" mailing list: > > mailto:ietf-caldav@osafoundation.org > > which is archived at: > > http://lists.osafoundation.org/mailman/listinfo/ietf-caldav > > Reports on the 4 CalDAV Interoperability Events organized by the > Calendaring and Scheduling Consortium (CalConnect) can be found at: > > http://www.calconnect.org/ioppast.html > > Finally, additional information on CalDAV can also be found at: > > http://ietf.webdav.org/caldav/ > > Please review draft -10 and send us feedback/questions/comments. > > Thanks for you help! > > Cheers, > Bernard > > -- > > C.1. Changes in -10 > > a. Added new section about support for X- items when storing data. > > b. Added new precondition to allow servers to reject queries on > unsupported X- items, and a new example. > > c. Added new text about always supporting X- in calendar-data. > > d. Created new section for PUT, COPY and MOVE preconditions. > > e. Report examples re-done with full listing of calendar data in > Appendix. > > f. Removed description of using UID, SUMMARY etc as resource name. > > g. Indicate that calendar object resource may contain only > overridden components. > > h. Add security consideration about not expose details in resource > names. > > i. Add constraint that free-busy-query can only be run on a > collection. > > j. Add preconditions for calendar-timezone property/elements in > MKCALENDAR, PROPPATCH and calendar-query REPORT. > > k. Fix principal-match example. > > > > -- bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 From julian.reschke at gmx.de Thu Feb 23 07:21:02 2006 From: julian.reschke at gmx.de (Julian Reschke) Date: Tue Mar 7 14:31:16 2006 Subject: [Ietf-calsify] Re: CalDAV draft Informal Last-Call In-Reply-To: <43FDCDC3.3000004@oracle.com> References: <43FD273E.3020702@oracle.com> <43FD6D6F.3030308@gmx.de> <43FDCDC3.3000004@oracle.com> Message-ID: <43FDD2DE.9010005@gmx.de> Bernard Desruisseaux wrote: > > Julian, > > Thanks for your feedback! The idea to do an informal last call is > exactly to get this kind of feedback. :-) > > Lisa, Cyrus and I already discussed about the possibility of making > reference to RFC2518bis. We will consider your feedback on this issue. Well, and that's the problem. To provide that kind of feedback, I'll have to review the spec, and that's the one thing I really don't have time for during RFC2518bis' last call :-) > Meanwhile, it would be appreciated if you could elaborate some more on > the implication of referencing RFC2518bis instead of RFC2518 in CalDAV. > > Thanks, > Bernard > > P.S. I have printed rfc2518bis and will take the time to review it! Great! Best regards, Julian Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 792137F624; Thu, 23 Feb 2006 19:06:48 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 6AC341422B0; Thu, 23 Feb 2006 19:06:48 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21756-05; Thu, 23 Feb 2006 19:06:47 -0800 (PST) Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id AA8761422AC; Thu, 23 Feb 2006 19:06:47 -0800 (PST) Received: from rgmsgw301.us.oracle.com (rgmsgw301.us.oracle.com [138.1.186.50]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k1O36kIO007068; Thu, 23 Feb 2006 21:06:46 -0600 Received: from localhost (localhost [127.0.0.1]) by rgmsgw301.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k1O36jiB010760; Thu, 23 Feb 2006 20:06:45 -0700 Received: from [127.0.0.1] (dhcp-amer-rmdc-csvpn-gw4-141-144-97-75.vpn.oracle.com [141.144.97.75]) by rgmsgw301.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k1O36ar4010721; Thu, 23 Feb 2006 20:06:39 -0700 Message-ID: <43FE7841.5040506@oracle.com> Date: Thu, 23 Feb 2006 22:06:41 -0500 From: Bernard Desruisseaux User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, fr-ca MIME-Version: 1.0 To: CalDAV DevList , Calsify WG , WebDAV WG Content-Type: multipart/mixed; boundary="------------070600070206030600050804" X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-1.2 tagged_above=-50.0 required=4.0 tests=AWL, BAYES_00 X-Spam-Level: Subject: [Ietf-calsify] [Fwd: I-D ACTION:draft-dusseault-caldav-10.txt] X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2006 03:06:48 -0000 This is a multi-part message in MIME format. --------------070600070206030600050804 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit -------- Original Message -------- Subject: I-D ACTION:draft-dusseault-caldav-10.txt Date: Thu, 23 Feb 2006 15:50:01 -0500 From: Internet-Drafts@ietf.org Reply-To: internet-drafts@ietf.org To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Calendaring Extensions to WebDAV (CalDAV) Author(s) : L. Dusseault, et al. Filename : draft-dusseault-caldav-10.txt Pages : 94 Date : 2006-2-23 This document specifies a set of methods, headers, message bodies, properties, and reports that define calendar access extensions to the WebDAV protocol. The new protocol elements are intended to make WebDAV-based calendaring and scheduling an interoperable standard that supports calendar access, calendar management, calendar sharing, and calendar publishing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-dusseault-caldav-10.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-dusseault-caldav-10.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --------------070600070206030600050804 Content-Type: Message/External-body; name="draft-dusseault-caldav-10.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="draft-dusseault-caldav-10.txt" Content-Type: text/plain Content-ID: <2006-2-23145218.I-D@ietf.org> --------------070600070206030600050804 Content-Type: text/plain; name="file:///C|/DOCUME%7E1/BDESRUIS/LOCALS%7E1/TEMP/nsmail-1.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="file:///C|/DOCUME%7E1/BDESRUIS/LOCALS%7E1/TEMP/nsmail-1.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --------------070600070206030600050804-- Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id ED6BF7F521 for ; Thu, 23 Feb 2006 07:22:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id DE25B142264 for ; Thu, 23 Feb 2006 07:22:03 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09475-04 for ; Thu, 23 Feb 2006 07:22:03 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by laweleka.osafoundation.org (Postfix) with SMTP id DF322142275 for ; Thu, 23 Feb 2006 07:22:02 -0800 (PST) Received: (qmail invoked by alias); 23 Feb 2006 15:22:01 -0000 Received: from mail.greenbytes.de (EHLO [192.168.1.40]) [217.91.35.233] by mail.gmx.net (mp031) with SMTP; 23 Feb 2006 16:22:01 +0100 X-Authenticated: #1915285 Message-ID: <43FDD2DE.9010005@gmx.de> Date: Thu, 23 Feb 2006 16:21:02 +0100 From: Julian Reschke User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Bernard Desruisseaux References: <43FD273E.3020702@oracle.com> <43FD6D6F.3030308@gmx.de> <43FDCDC3.3000004@oracle.com> In-Reply-To: <43FDCDC3.3000004@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-1.0 tagged_above=-50.0 required=4.0 tests=AWL, BAYES_00 X-Spam-Level: X-Mailman-Approved-At: Tue, 07 Mar 2006 14:31:14 -0800 Cc: Calsify WG , WebDAV WG , CalDAV DevList Subject: [Ietf-calsify] Re: CalDAV draft Informal Last-Call X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2006 15:22:04 -0000 Bernard Desruisseaux wrote: > > Julian, > > Thanks for your feedback! The idea to do an informal last call is > exactly to get this kind of feedback. :-) > > Lisa, Cyrus and I already discussed about the possibility of making > reference to RFC2518bis. We will consider your feedback on this issue. Well, and that's the problem. To provide that kind of feedback, I'll have to review the spec, and that's the one thing I really don't have time for during RFC2518bis' last call :-) > Meanwhile, it would be appreciated if you could elaborate some more on > the implication of referencing RFC2518bis instead of RFC2518 in CalDAV. > > Thanks, > Bernard > > P.S. I have printed rfc2518bis and will take the time to review it! Great! Best regards, Julian Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id D4E357F645; Thu, 23 Feb 2006 07:01:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id C64651422AA; Thu, 23 Feb 2006 07:01:00 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16825-05; Thu, 23 Feb 2006 07:01:00 -0800 (PST) Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id E1E9A1422A9; Thu, 23 Feb 2006 07:00:59 -0800 (PST) Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.186.49]) by rgminet01.oracle.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id k1NF0swE026961; Thu, 23 Feb 2006 08:00:54 -0700 Received: from localhost (localhost [127.0.0.1]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k1NF0sfS023892; Thu, 23 Feb 2006 08:00:54 -0700 Received: from [10.156.42.83] (bdesruis-ca.ca.oracle.com [10.156.42.83]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k1NF0lbv023847 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 23 Feb 2006 08:00:47 -0700 Message-ID: <43FDCDC3.3000004@oracle.com> Date: Thu, 23 Feb 2006 09:59:15 -0500 From: Bernard Desruisseaux User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Reschke References: <43FD273E.3020702@oracle.com> <43FD6D6F.3030308@gmx.de> In-Reply-To: <43FD6D6F.3030308@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-1.7 tagged_above=-50.0 required=4.0 tests=BAYES_00 X-Spam-Level: Cc: Calsify WG , WebDAV WG , CalDAV DevList Subject: [Ietf-calsify] Re: CalDAV draft Informal Last-Call X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2006 15:01:01 -0000 Julian, Thanks for your feedback! The idea to do an informal last call is exactly to get this kind of feedback. :-) Lisa, Cyrus and I already discussed about the possibility of making reference to RFC2518bis. We will consider your feedback on this issue. Meanwhile, it would be appreciated if you could elaborate some more on the implication of referencing RFC2518bis instead of RFC2518 in CalDAV. Thanks, Bernard P.S. I have printed rfc2518bis and will take the time to review it! Julian Reschke wrote: > Hm. > > It strikes me as a particularly bad idea to last-call a draft that > builds on top of RFC2518, while, at the same time, RFC2518bis is last > called. > > Reasons: > > - you will likely have to update the spec to refer to rfc2518bis instead > anyway, and this frequently is more work than just updating a single > reference (in particular, the stuff about ETags in section 5.3.4 is > partly in conflict with RFC2616, and likely to be in conflict with the > separate document about ETag handling in HTTP the IETF has decided to > produce). > > - the group of people who can give constructive feedback to CalDAV > definitively overlaps with those who can review RFC2518bis. > > Therefore I strongly suggest not to last-call anything WebDAV related > before RFC2518bis' last call has ended. > > Best regards, Julian > > > Bernard Desruisseaux wrote: > >> >> We submitted CalDAV draft -10 to the IETF yesterday. The draft has >> not been officially announced yet, but it is already available for >> you to review at the following URL: >> >> http://ietf.webdav.org/caldav/draft-dusseault-caldav-10.txt >> >> We would like to submit the CalDAV draft for Last Call in time for >> the 65th IETF Meeting in Dallas (i.e., really soon!). Before we do >> so, we would like to get as much feedback as possible from the >> participants of the "ietf-caldav" mailing list as well as from the >> members of the WebDAV and Calsify Working Groups. >> >> Once officially announced the draft should be available at: >> >> http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt >> >> Previous versions of the draft are available at: >> >> http://ietfreport.isoc.org/idref/draft-dusseault-caldav/ >> >> Discussion on CalDAV is taking place on the "ietf-caldav" mailing list: >> >> mailto:ietf-caldav@osafoundation.org >> >> which is archived at: >> >> http://lists.osafoundation.org/mailman/listinfo/ietf-caldav >> >> Reports on the 4 CalDAV Interoperability Events organized by the >> Calendaring and Scheduling Consortium (CalConnect) can be found at: >> >> http://www.calconnect.org/ioppast.html >> >> Finally, additional information on CalDAV can also be found at: >> >> http://ietf.webdav.org/caldav/ >> >> Please review draft -10 and send us feedback/questions/comments. >> >> Thanks for you help! >> >> Cheers, >> Bernard >> >> -- >> >> C.1. Changes in -10 >> >> a. Added new section about support for X- items when storing data. >> >> b. Added new precondition to allow servers to reject queries on >> unsupported X- items, and a new example. >> >> c. Added new text about always supporting X- in calendar-data. >> >> d. Created new section for PUT, COPY and MOVE preconditions. >> >> e. Report examples re-done with full listing of calendar data in >> Appendix. >> >> f. Removed description of using UID, SUMMARY etc as resource name. >> >> g. Indicate that calendar object resource may contain only >> overridden components. >> >> h. Add security consideration about not expose details in resource >> names. >> >> i. Add constraint that free-busy-query can only be run on a >> collection. >> >> j. Add preconditions for calendar-timezone property/elements in >> MKCALENDAR, PROPPATCH and calendar-query REPORT. >> >> k. Fix principal-match example. >> >> >> >> > > Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3271F7F5A8 for ; Thu, 23 Feb 2006 00:09:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2201D142275 for ; Thu, 23 Feb 2006 00:09:07 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09376-05 for ; Thu, 23 Feb 2006 00:09:06 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by laweleka.osafoundation.org (Postfix) with SMTP id D7CEA1422A6 for ; Thu, 23 Feb 2006 00:09:05 -0800 (PST) Received: (qmail invoked by alias); 23 Feb 2006 08:09:04 -0000 Received: from p508FB53A.dip0.t-ipconnect.de (EHLO [192.168.178.21]) [80.143.181.58] by mail.gmx.net (mp029) with SMTP; 23 Feb 2006 09:09:04 +0100 X-Authenticated: #1915285 Message-ID: <43FD6D6F.3030308@gmx.de> Date: Thu, 23 Feb 2006 09:08:15 +0100 From: Julian Reschke User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Bernard Desruisseaux References: <43FD273E.3020702@oracle.com> In-Reply-To: <43FD273E.3020702@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-1.0 tagged_above=-50.0 required=4.0 tests=AWL, BAYES_00 X-Spam-Level: X-Mailman-Approved-At: Tue, 07 Mar 2006 14:31:14 -0800 Cc: Calsify WG , WebDAV WG , CalDAV DevList Subject: [Ietf-calsify] Re: CalDAV draft Informal Last-Call X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2006 08:09:07 -0000 Hm. It strikes me as a particularly bad idea to last-call a draft that builds on top of RFC2518, while, at the same time, RFC2518bis is last called. Reasons: - you will likely have to update the spec to refer to rfc2518bis instead anyway, and this frequently is more work than just updating a single reference (in particular, the stuff about ETags in section 5.3.4 is partly in conflict with RFC2616, and likely to be in conflict with the separate document about ETag handling in HTTP the IETF has decided to produce). - the group of people who can give constructive feedback to CalDAV definitively overlaps with those who can review RFC2518bis. Therefore I strongly suggest not to last-call anything WebDAV related before RFC2518bis' last call has ended. Best regards, Julian Bernard Desruisseaux wrote: > > We submitted CalDAV draft -10 to the IETF yesterday. The draft has > not been officially announced yet, but it is already available for > you to review at the following URL: > > http://ietf.webdav.org/caldav/draft-dusseault-caldav-10.txt > > We would like to submit the CalDAV draft for Last Call in time for > the 65th IETF Meeting in Dallas (i.e., really soon!). Before we do > so, we would like to get as much feedback as possible from the > participants of the "ietf-caldav" mailing list as well as from the > members of the WebDAV and Calsify Working Groups. > > Once officially announced the draft should be available at: > > http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt > > Previous versions of the draft are available at: > > http://ietfreport.isoc.org/idref/draft-dusseault-caldav/ > > Discussion on CalDAV is taking place on the "ietf-caldav" mailing list: > > mailto:ietf-caldav@osafoundation.org > > which is archived at: > > http://lists.osafoundation.org/mailman/listinfo/ietf-caldav > > Reports on the 4 CalDAV Interoperability Events organized by the > Calendaring and Scheduling Consortium (CalConnect) can be found at: > > http://www.calconnect.org/ioppast.html > > Finally, additional information on CalDAV can also be found at: > > http://ietf.webdav.org/caldav/ > > Please review draft -10 and send us feedback/questions/comments. > > Thanks for you help! > > Cheers, > Bernard > > -- > > C.1. Changes in -10 > > a. Added new section about support for X- items when storing data. > > b. Added new precondition to allow servers to reject queries on > unsupported X- items, and a new example. > > c. Added new text about always supporting X- in calendar-data. > > d. Created new section for PUT, COPY and MOVE preconditions. > > e. Report examples re-done with full listing of calendar data in > Appendix. > > f. Removed description of using UID, SUMMARY etc as resource name. > > g. Indicate that calendar object resource may contain only > overridden components. > > h. Add security consideration about not expose details in resource > names. > > i. Add constraint that free-busy-query can only be run on a > collection. > > j. Add preconditions for calendar-timezone property/elements in > MKCALENDAR, PROPPATCH and calendar-query REPORT. > > k. Fix principal-match example. > > > > -- bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id DFB597F530; Wed, 22 Feb 2006 19:08:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D0D6D142285; Wed, 22 Feb 2006 19:08:59 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23255-06; Wed, 22 Feb 2006 19:08:59 -0800 (PST) Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 33EB3142280; Wed, 22 Feb 2006 19:08:59 -0800 (PST) Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.186.49]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k1N38rCL008747; Wed, 22 Feb 2006 21:08:53 -0600 Received: from localhost (localhost [127.0.0.1]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k1N38qet009820; Wed, 22 Feb 2006 20:08:52 -0700 Received: from [127.0.0.1] (dhcp-amer-rmdc-csvpn-gw5-141-144-105-62.vpn.oracle.com [141.144.105.62]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k1N38gnf009762; Wed, 22 Feb 2006 20:08:49 -0700 Message-ID: <43FD273E.3020702@oracle.com> Date: Wed, 22 Feb 2006 22:08:46 -0500 From: Bernard Desruisseaux User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, fr-ca MIME-Version: 1.0 To: CalDAV DevList , Calsify WG , WebDAV WG Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-1.2 tagged_above=-50.0 required=4.0 tests=AWL, BAYES_00 X-Spam-Level: Subject: [Ietf-calsify] CalDAV draft Informal Last-Call X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2006 03:09:00 -0000 We submitted CalDAV draft -10 to the IETF yesterday. The draft has not been officially announced yet, but it is already available for you to review at the following URL: http://ietf.webdav.org/caldav/draft-dusseault-caldav-10.txt We would like to submit the CalDAV draft for Last Call in time for the 65th IETF Meeting in Dallas (i.e., really soon!). Before we do so, we would like to get as much feedback as possible from the participants of the "ietf-caldav" mailing list as well as from the members of the WebDAV and Calsify Working Groups. Once officially announced the draft should be available at: http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt Previous versions of the draft are available at: http://ietfreport.isoc.org/idref/draft-dusseault-caldav/ Discussion on CalDAV is taking place on the "ietf-caldav" mailing list: mailto:ietf-caldav@osafoundation.org which is archived at: http://lists.osafoundation.org/mailman/listinfo/ietf-caldav Reports on the 4 CalDAV Interoperability Events organized by the Calendaring and Scheduling Consortium (CalConnect) can be found at: http://www.calconnect.org/ioppast.html Finally, additional information on CalDAV can also be found at: http://ietf.webdav.org/caldav/ Please review draft -10 and send us feedback/questions/comments. Thanks for you help! Cheers, Bernard -- C.1. Changes in -10 a. Added new section about support for X- items when storing data. b. Added new precondition to allow servers to reject queries on unsupported X- items, and a new example. c. Added new text about always supporting X- in calendar-data. d. Created new section for PUT, COPY and MOVE preconditions. e. Report examples re-done with full listing of calendar data in Appendix. f. Removed description of using UID, SUMMARY etc as resource name. g. Indicate that calendar object resource may contain only overridden components. h. Add security consideration about not expose details in resource names. i. Add constraint that free-busy-query can only be run on a collection. j. Add preconditions for calendar-timezone property/elements in MKCALENDAR, PROPPATCH and calendar-query REPORT. k. Fix principal-match example. Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id BF78A808D3 for ; Wed, 22 Feb 2006 09:41:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B07C81422A6 for ; Wed, 22 Feb 2006 09:41:21 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14519-07 for ; Wed, 22 Feb 2006 09:41:21 -0800 (PST) Received: from doob.fam.tuwien.ac.at (doob.fam.tuwien.ac.at [128.130.51.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 953451422A3 for ; Wed, 22 Feb 2006 09:41:20 -0800 (PST) Received: from curie.fam.tuwien.ac.at (reinhold@curie.fam.tuwien.ac.at [128.130.51.116]) by doob.fam.tuwien.ac.at (8.13.4/8.13.4/Debian-3) with ESMTP id k1MHfDhL011193 for ; Wed, 22 Feb 2006 18:41:15 +0100 From: Reinhold Kainhofer Organization: FAM, Vienna University of Technology To: ietf-calsify@osafoundation.org Subject: Re: [Ietf-calsify] calendar apps that generate multiple VALARMs per event? Date: Wed, 22 Feb 2006 18:40:48 +0100 User-Agent: KMail/1.9.1 References: <43F24FF7.4030403@mozilla.org> In-Reply-To: <43F24FF7.4030403@mozilla.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602221840.49165.reinhold@kainhofer.com> X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-1.3 tagged_above=-50.0 required=4.0 tests=AWL, BAYES_00 X-Spam-Level: X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2006 17:41:21 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Dienstag, 14. Februar 2006 22:47 schrieb Dan Mosedale: > I'm trying to understand the use of multiple VALARMs per event, and I'm > wondering how much, it happens in the real world. Having both an email > and an audio alarm on an event seems like a reasonable enough use-case. > Do folks know of any calendar apps that generate multiple VALARMs today, > or plan to in the future? Yes, KOrganizer does since KDE 3.4 or 3.5. There's an additional tab for all the various alarm settings (relative to start/end of event, type, offset, repeat, etc.): http://www.fam.tuwien.ac.at/~reinhold/KOrganizer/KOrganizer_MultipleAlarms.jpg Cheers, Reinhold - -- - ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: reinhold@kainhofer.com, http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD/KIhTqjEwhXvPN0RArtVAJ48OxdMMrg4/1pzsPiP298sWMQJ7ACg0GMp oCz8D0os4y6VyYPDNTHye6o= =m6Rx -----END PGP SIGNATURE----- Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 00B25808D0 for ; Wed, 22 Feb 2006 09:35:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id E67961422A6 for ; Wed, 22 Feb 2006 09:35:11 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16648-04 for ; Wed, 22 Feb 2006 09:35:11 -0800 (PST) Received: from mail.mdlink.net (medusa.mdlink.de [213.211.192.34]) by laweleka.osafoundation.org (Postfix) with ESMTP id 7A0AD1422A3 for ; Wed, 22 Feb 2006 09:35:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail.mdlink.net (Postfix) with ESMTP id 294B03CB3ED; Wed, 22 Feb 2006 18:29:16 +0100 (CET) Received: from [192.168.1.233] (port-ip-213-211-243-136.reverse.mdcc-fun.de [213.211.243.136]) by mail.mdlink.net (Postfix) with ESMTP id C097F3CD19A; Wed, 22 Feb 2006 18:29:15 +0100 (CET) In-Reply-To: <43F24FF7.4030403@mozilla.org> References: <43F24FF7.4030403@mozilla.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <79C3ECD0-1296-470F-8D93-299DD1F56211@opengroupware.org> Content-Transfer-Encoding: 7bit From: Helge Hess Subject: Re: [Ietf-calsify] calendar apps that generate multiple VALARMs per event? Date: Wed, 22 Feb 2006 18:34:56 +0100 To: Dan Mosedale X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-0.9 tagged_above=-50.0 required=4.0 tests=AWL, BAYES_00, FORGED_RCVD_HELO X-Spam-Level: Cc: ietf-calsify@osafoundation.org X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2006 17:35:12 -0000 On 14. Feb 2006, at 22:47 Uhr, Dan Mosedale wrote: > Do folks know of any calendar apps that generate multiple VALARMs > today Apple iCal.app allows to add multiple alarms. Greets, Helge -- http://docs.opengroupware.org/Members/helge/ OpenGroupware.org Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 5F4DF7F67C for ; Tue, 14 Feb 2006 13:48:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 4889E142294 for ; Tue, 14 Feb 2006 13:48:24 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13802-10 for ; Tue, 14 Feb 2006 13:48:24 -0800 (PST) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by laweleka.osafoundation.org (Postfix) with ESMTP id 20EE214228E for ; Tue, 14 Feb 2006 13:48:24 -0800 (PST) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id k1ELmI5R034854 for ; Tue, 14 Feb 2006 13:48:23 -0800 (PST) (envelope-from dmose@mozilla.org) Received: from [192.168.2.10] (64-121-33-215.c3-0.sfpo-ubr8.sfrn-sfpo.ca.cable.rcn.com [64.121.33.215]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id k1ELlZcP020814 for ; Tue, 14 Feb 2006 13:47:35 -0800 (PST) (envelope-from dmose@mozilla.org) Message-ID: <43F24FF7.4030403@mozilla.org> Date: Tue, 14 Feb 2006 13:47:35 -0800 From: Dan Mosedale User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: ietf-calsify@osafoundation.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests= X-Spam-Level: X-Mailman-Approved-At: Wed, 22 Feb 2006 09:22:33 -0800 Subject: [Ietf-calsify] calendar apps that generate multiple VALARMs per event? X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2006 21:48:25 -0000 I'm trying to understand the use of multiple VALARMs per event, and I'm wondering how much, it happens in the real world. Having both an email and an audio alarm on an event seems like a reasonable enough use-case. Do folks know of any calendar apps that generate multiple VALARMs today, or plan to in the future? Dan Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C07CB7F5AF for ; Mon, 13 Feb 2006 10:37:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B1D7314227C for ; Mon, 13 Feb 2006 10:37:30 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24282-02 for ; Mon, 13 Feb 2006 10:37:30 -0800 (PST) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by laweleka.osafoundation.org (Postfix) with ESMTP id 6795914227B for ; Mon, 13 Feb 2006 10:37:30 -0800 (PST) Received: by zproxy.gmail.com with SMTP id q3so1084264nzb for ; Mon, 13 Feb 2006 10:37:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=EDUh27O5+f4t7Bol5HZtEKMxOMUIDWv1Dt46YYm0k4UdMOsL9k7VjkgJh6xlgKc20isJ9tuBADWxyZNwHylg5n7kBUm2mUhwDV8Qz8mIfqDdMgwAGSnIGwPlk3TtOArBI/fj0hWks+FjddW//IAhtB10fZYYn/TdILzU7pJCQ6A= Received: by 10.65.155.8 with SMTP id h8mr1205342qbo; Mon, 13 Feb 2006 10:37:29 -0800 (PST) Received: by 10.65.95.13 with HTTP; Mon, 13 Feb 2006 10:37:29 -0800 (PST) Message-ID: <6bd837ee0602131037i4e1e8bb5s1023d5d07234e373@mail.gmail.com> Date: Mon, 13 Feb 2006 19:37:29 +0100 From: Daniele Tiles To: ietf-calsify@osafoundation.org Subject: Re: [Ietf-calsify] Most used TZID and Olson Database In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_153_17511501.1139855849207" References: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.5 tagged_above=-50.0 required=4.0 tests=AWL, HTML_40_50, HTML_MESSAGE X-Spam-Level: X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2006 18:37:30 -0000 ------=_Part_153_17511501.1139855849207 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, thank you very much for the quick answer (this somehow helps me...I'm on th= e right way :))...do you know anything like a simple file containing the Olso= n Id and the correspondent UTC offset? It would be helpful (it's so annoying that there isn't anything ready under Windows...) Bye Daniele The Calconnect Timezone questionnaire we did last year did indicate that a > majority of respondents used the Olson DB: > > < > http://www.calconnect.org/publications/resultsfromtimezonequestionnairev1= .0.pdf > > > > > -- > Cyrus Daboo > > -- http://www.icalx.com/html/lasthope/month.php?cal=3Dlasthope.public http://www.universibo.unibo.it webcal://www.rememberthemilk.com/icalendar/daniele.tiles/121631/ ------=_Part_153_17511501.1139855849207 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

Hi,
thank you very much for the quick answer (this somehow= helps me...I'm on the right way :))...do you know anything like a simple f= ile containing the Olson Id and the correspondent UTC offset? It would be h= elpful (it's so annoying that there isn't anything ready under Windows...)
Bye

Daniele

The Calconnect Timezone questionnaire we did last year d= id indicate that a
majority of respondents used the Olson DB:

<= http://www.calconnect.org/publications/resultsfromtimezonequestionnairev1.0= .pdf >


--
Cyrus Daboo




--
http://www.icalx.com/html/lasthope/month.php?cal= =3Dlasthope.public
http://www.universibo.un= ibo.it
webcal://www.rememberthemilk.com/icalendar/daniele.tiles/1216= 31/ ------=_Part_153_17511501.1139855849207-- Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 51EA47F5EF for ; Sun, 12 Feb 2006 17:04:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 4279E1422F8 for ; Sun, 12 Feb 2006 17:04:33 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23777-10 for ; Sun, 12 Feb 2006 17:04:33 -0800 (PST) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by laweleka.osafoundation.org (Postfix) with ESMTP id 1137C1422F1 for ; Sun, 12 Feb 2006 17:04:33 -0800 (PST) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id EF725D33EBD; Sun, 12 Feb 2006 20:04:30 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Sun, 12 Feb 2006 20:04:30 -0500 X-Sasl-enc: R7S+e7Ly0w9HMGQOCF0bPu9UrnIr+phYXz5m0VEacan5 1139792668 Received: from [10.0.1.3] (pool-71-253-43-80.pitbpa.east.verizon.net [71.253.43.80]) by www.fastmail.fm (Postfix) with ESMTP id BC9D157146F; Sun, 12 Feb 2006 20:04:27 -0500 (EST) Date: Sun, 12 Feb 2006 20:04:31 -0500 From: Cyrus Daboo To: Daniele Tiles , ietf-calsify@osafoundation.org Subject: Re: [Ietf-calsify] Most used TZID and Olson Database Message-ID: In-Reply-To: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> References: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> X-Mailer: Mulberry/4.0.4 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=AWL X-Spam-Level: X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2006 01:04:33 -0000 Hi Daniele, --On February 12, 2006 8:03:56 PM +0100 Daniele Tiles wrote: > I would like to add a very-basilar support to TimeZone in my Calendar > Application...as I read in the RFC, and as I saw working with some > iCalendars, the id's of the Olson database seems to be the most > used...so, I would like to ask: > --Is this actually true? Has anyone got any statistics or something like > that? The Calconnect Timezone questionnaire we did last year did indicate that a majority of respondents used the Olson DB: -- Cyrus Daboo Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 219C47F6AA for ; Sun, 12 Feb 2006 11:03:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 1212F1422C9 for ; Sun, 12 Feb 2006 11:03:57 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12540-06 for ; Sun, 12 Feb 2006 11:03:56 -0800 (PST) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by laweleka.osafoundation.org (Postfix) with ESMTP id BC39E1422C8 for ; Sun, 12 Feb 2006 11:03:56 -0800 (PST) Received: by zproxy.gmail.com with SMTP id x7so859672nzc for ; Sun, 12 Feb 2006 11:03:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=qpQLyTsf5i4S4zwLaHUldv1vC7V213RSTjvCFiDxqOFOWzMsZDistPqbLFa9VCvix6eIYbA8J+gvOXxAXev8IFwfSKelWczoToM/lHdaq4pDFzIEUjlKv+oETP7VSjJmi3iainKIwIqMwd1/4Oy2R5SYFrxwnZe4mRgdwRLQQYc= Received: by 10.65.98.9 with SMTP id a9mr649553qbm; Sun, 12 Feb 2006 11:03:56 -0800 (PST) Received: by 10.65.95.13 with HTTP; Sun, 12 Feb 2006 11:03:56 -0800 (PST) Message-ID: <6bd837ee0602121103n780c05b2v39540c00bbb8fec4@mail.gmail.com> Date: Sun, 12 Feb 2006 20:03:56 +0100 From: Daniele Tiles To: ietf-calsify@osafoundation.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1935_21953872.1139771036075" X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.5 tagged_above=-50.0 required=4.0 tests=AWL, HTML_20_30, HTML_MESSAGE X-Spam-Level: Subject: [Ietf-calsify] Most used TZID and Olson Database X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Feb 2006 19:03:57 -0000 ------=_Part_1935_21953872.1139771036075 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi to all, I would like to add a very-basilar support to TimeZone in my Calendar Application...as I read in the RFC, and as I saw working with some iCalendars, the id's of the Olson database seems to be the most used...so, = I would like to ask: --Is this actually true? Has anyone got any statistics or something like that? --I'm working on Windows, and what I would REALLY need is a list of the Olson database id's (like Europe/Rome) and they correspondet UTC... Could someone help me? :) Bye Daniele Tiles -- http://remotecalendars.sf.net http://www.icalx.com/html/lasthope/month.php?cal=3Dlasthope.public http://www.universibo.unibo.it ------=_Part_1935_21953872.1139771036075 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi to all,
I would like to add a very-basilar support to TimeZone in my = Calendar Application...as I read in the RFC, and as I saw working with some= iCalendars, the id's of the Olson database seems to be the most used...so,= I would like to ask:
--Is this actually true? Has anyone got any statistics or something lik= e that?
--I'm working on Windows, and what I would REALLY need is a list= of the Olson database id's (like Europe/Rome) and they correspondet UTC...
Could someone help me? :)
Bye

Daniele Tiles
=
--
http://remotecalendars= .sf.net
http://www.icalx.com/html/lasthope/month.php?cal=3Dlasthope.public
<= a href=3D"http://www.universibo.unibo.it">http://www.universibo.unibo.it

------=_Part_1935_21953872.1139771036075-- Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 15E307F6B2 for ; Fri, 3 Feb 2006 15:02:51 -0800 (PST) Received: from [192.168.1.100] (unknown [198.144.201.116]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 2CB2514228F for ; Fri, 3 Feb 2006 15:02:49 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.2) To: IETF-iCalendar Message-Id: <2117C8A3-AF20-48A8-8EC1-7751CDAF9E26@osafoundation.org> Content-Type: multipart/alternative; boundary=Apple-Mail-5--360706691 References: From: Lisa Dusseault Date: Fri, 3 Feb 2006 15:02:46 -0800 X-Mailer: Apple Mail (2.746.2) Subject: [Ietf-calsify] Fwd: Internet-Drafts Submission Cutoff Dates for the 65th IETF Meeting in Dallas, TX, USA X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2006 23:02:51 -0000 --Apple-Mail-5--360706691 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Very important dates for the authors/editors in this WG! I am still hoping we can do better than to just barely hit the dates. Having only one draft out between meetings, and only just before the draft deadline, is not optimal for WG meeting planning and effective agendas. I would encourage the authors/editors to submit works in progress as we're not expecting to see polished, finished results at this time. Lisa Begin forwarded message: > From: ietf-secretariat@ietf.org > Date: February 2, 2006 9:00:01 PM PST > To: ietf-announce@ietf.org > Subject: Internet-Drafts Submission Cutoff Dates for the 65th IETF > Meeting in Dallas, TX, USA > > > There are two (2) Internet-Draft cutoff dates for the 65th > IETF Meeting in Dallas, TX, USA: > > February 27th: Cutoff Date for Initial (i.e., version -00) > Internet-Draft Submissions > > All initial Internet-Drafts (version -00) must be submitted by Monday, > February 27th at 9:00 AM ET. As always, all initial submissions with a > filename beginning with "draft-ietf" must be approved by the > appropriate WG Chair before they can be processed or announced. The > Secretariat would appreciate receiving WG Chair approval by Monday, > February 20th at 9:00 AM ET. > > March 6th: Cutoff Date for Revised (i.e., version -01 and higher) > Internet-Draft Submissions > > All revised Internet-Drafts (version -01 and higher) must be submitted > by Monday, March 6th at 9:00 AM ET. > > Initial and revised Internet-Drafts received after their respective > cutoff dates will not be made available in the Internet-Drafts > directory or announced until on or after Monday, March 20th at 9:00 > AM ET, when Internet-Draft posting resumes. Please do not wait until > the last minute to submit. > > Thank you for your understanding and cooperation. If you have any > questions or concerns, then please send a message to > internet-drafts@ietf.org. > > The IETF Secretariat > > FYI: The Internet-Draft cutoff dates as well as other significant > dates > for the 65th IETF Meeting can be found at http://www.ietf.org/ > meetings/cutoff_dates_65.html. > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce --Apple-Mail-5--360706691 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 Very important dates for the = authors/editors in this WG!=A0 I am still hoping we can do better than = to just barely hit the dates.=A0 Having only one draft out between = meetings, and only just before the draft deadline, is not optimal for WG = meeting planning and effective agendas.=A0 I would encourage the = authors/editors to submit works in progress as we're not expecting to = see polished, finished results at this time.

Lisa

Begin = forwarded message:

Date: February 2, 2006 9:00:01 PM = PST
To: ietf-announce@ietf.org
Subject: Internet-Drafts Submission Cutoff = Dates for the 65th IETF Meeting in Dallas, TX, USA=A0


There are two = (2) Internet-Draft cutoff dates for the 65th=A0
IETF = Meeting in Dallas, TX, USA:

February 27th: Cutoff Date for = Initial (i.e., version -00)=A0
=A0

All initial = Internet-Drafts (version -00) must be submitted by Monday,=A0
February = 27th at 9:00 AM ET. As always, all initial submissions with a=A0
filename = beginning with "draft-ietf" must be approved by the=A0
=A0 The=A0
=A0
February 20th at 9:00 AM ET.

March = 6th: Cutoff Date for Revised (i.e., version -01 and higher)=A0
=A0

All revised = Internet-Drafts (version -01 and higher) must be submitted=A0
by = Monday, March 6th at 9:00 AM ET.

Initial and revised = Internet-Drafts received after their respective=A0
cutoff = dates will not be made available in the Internet-Drafts=A0
=A0
AM ET, when Internet-Draft posting resumes.=A0 Please do not wait until=A0
the last = minute to submit.

Thank you for your understanding and cooperation. If = you have any=A0
questions or concerns, then please send a message = to=A0
internet-drafts@ietf.org.

The IETF = Secretariat

FYI: The Internet-Draft cutoff dates as well as = other significant dates
for the 65th = IETF Meeting can be found at http://www.ietf= .org/meetings/cutoff_dates_65.html.

IETF-Announce mailing list
https://www1= .ietf.org/mailman/listinfo/ietf-announce
=

= --Apple-Mail-5--360706691-- Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C65DF7F5F1 for ; Wed, 1 Feb 2006 08:50:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B4C5D142287 for ; Wed, 1 Feb 2006 08:50:12 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19933-03 for ; Wed, 1 Feb 2006 08:50:12 -0800 (PST) Received: from pjag.com (Intellical.net [217.160.241.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 32827142285 for ; Wed, 1 Feb 2006 08:50:12 -0800 (PST) Received: (qmail 9693 invoked from network); 1 Feb 2006 11:50:10 -0500 Received: from localhost (HELO ?192.168.168.10?) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Feb 2006 11:50:10 -0500 Message-ID: <43E0E6BD.6060100@Royer.com> Date: Wed, 01 Feb 2006 09:50:05 -0700 From: Doug Royer Organization: IntelliCal.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calsify@osafoundation.org Subject: Re: [Ietf-calsify] Properties and parameters References: <6F310B9F4D610FC4623148F3@Cyrus-Daboo.local> In-Reply-To: <6F310B9F4D610FC4623148F3@Cyrus-Daboo.local> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030406050800080908020108" X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=AWL X-Spam-Level: X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf-calsify@osafoundation.org List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 16:50:12 -0000 This is a cryptographically signed message in MIME format. --------------ms030406050800080908020108 Content-Type: multipart/mixed; boundary="------------050402000001000508070601" This is a multi-part message in MIME format. --------------050402000001000508070601 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The table of contents calls 'parameters' 'properties'. And the TOC only calls the parameter "VALUE" value types parameters. Many of the parameters are not listed in the TOC at all The section 12 TOC 'Property Parameters' is empty Cyrus Daboo wrote: > Hi, > 2445bis now mixes properties and parameter definitions within the same > sections. I actually find it a lot harder to navigate around to find a > particular definition of either a property or parameter now. What would > be extremely useful is an index for the definition of each component, > property, parameter and value type. The table of contents is not as good > for lookup as it was before. > -- Doug Royer | http://INET-Consulting.com -------------------------------|----------------------------- We Do Standards - You Need Standards --------------050402000001000508070601 Content-Type: text/x-vcard; charset=utf-8; name="Doug.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Doug.vcf" begin:vcard fn:Doug Royer n:Royer;Doug org:INET-Consulting.com adr:;;;;;;U.S.A email;internet:Doug@Royer.com title:CEO tel;work:866-594-8574 tel;fax:866-594-8574 note;quoted-printable:AOL: SupportUnix=0D=0A= MSN: Support@INET-Consulting.com=0D=0A= Yahoo: Help4Unix x-mozilla-html:FALSE url:http://Royer.com version:2.1 end:vcard --------------050402000001000508070601-- --------------ms030406050800080908020108 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMzDCC A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4 MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0 ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+ i+P7FTCCBK8wggQYoAMCAQICEFsGSvEntexpo94qqcjJuhAwDQYJKoZIhvcNAQEFBQAwgcwx FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3 b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDUwOTE4MDAw MDAwWhcNMDYwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3 DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDZ BFhLbROJ3gBYIeuP8+vR6G9dT4K3lXeeK+a9TO0qfqkxm6B3RDcXyhjd000rAUjGGRvVkyBX 6EjXkqCILRMAkbU5Zvk8nMyh0a27CzZH5JPHgw9bUutozhECZSDn/F5GRB/nwlOS3ip2Q+30 AvwX7x2h/12yyjyO9op9HIZLnpKXqgJETp/fmiOgfPg7xu8OBrwch1k9f48As0/8YCstHjka 32q/jEqWboVtE40sk48ROWca6KMLXli3HfVdj/NIZkYc8UFjK6Y5ojZ8hCYUo6H6hZanIyqd ptDd5T5/TuQHcJH7M6kq/BUgTzDJgRXdQEPxISfZGCRj7NckF5zXAgMBAAGjgcswgcgwCQYD VR0TBAIwADBEBgNVHSAEPTA7MDkGC2CGSAGG+EUBBxcDMCowKAYIKwYBBQUHAgEWHGh0dHBz Oi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwCwYDVR0PBAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUF BwMEBggrBgEFBQcDAjAUBgpghkgBhvhFAQYHBAYWBE5vbmUwMwYDVR0fBCwwKjAooCagJIYi aHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQUFAAOBgQBT 5VLp42EyzXxqDBuVNmtAkVqt6U3GOY9gWKUUzBSRtlepDPiR3yF+I+GfeEZ8087H9QKcBrrU eXQlQ68hFm/nH1XVTVGdQ3wZOSnC/6JrZUvlurzw9bjjXXaUx2xKI/vH7PFBoa2bfMAxSfGO UEBY2wBeWT4QhxxV3TuDSI3NgzCCBK8wggQYoAMCAQICEFsGSvEntexpo94qqcjJuhAwDQYJ KoZIhvcNAQEFBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0 ZWQwHhcNMDUwOTE4MDAwMDAwWhcNMDYwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlT aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13 d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxU RChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0 YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBS b3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUA A4IBDwAwggEKAoIBAQDZBFhLbROJ3gBYIeuP8+vR6G9dT4K3lXeeK+a9TO0qfqkxm6B3RDcX yhjd000rAUjGGRvVkyBX6EjXkqCILRMAkbU5Zvk8nMyh0a27CzZH5JPHgw9bUutozhECZSDn /F5GRB/nwlOS3ip2Q+30AvwX7x2h/12yyjyO9op9HIZLnpKXqgJETp/fmiOgfPg7xu8OBrwc h1k9f48As0/8YCstHjka32q/jEqWboVtE40sk48ROWca6KMLXli3HfVdj/NIZkYc8UFjK6Y5 ojZ8hCYUo6H6hZanIyqdptDd5T5/TuQHcJH7M6kq/BUgTzDJgRXdQEPxISfZGCRj7NckF5zX AgMBAAGjgcswgcgwCQYDVR0TBAIwADBEBgNVHSAEPTA7MDkGC2CGSAGG+EUBBxcDMCowKAYI KwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwCwYDVR0PBAQDAgWgMB0G A1UdJQQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjAUBgpghkgBhvhFAQYHBAYWBE5vbmUwMwYD VR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkq hkiG9w0BAQUFAAOBgQBT5VLp42EyzXxqDBuVNmtAkVqt6U3GOY9gWKUUzBSRtlepDPiR3yF+ I+GfeEZ8087H9QKcBrrUeXQlQ68hFm/nH1XVTVGdQ3wZOSnC/6JrZUvlurzw9bjjXXaUx2xK I/vH7PFBoa2bfMAxSfGOUEBY2wBeWT4QhxxV3TuDSI3NgzGCBKowggSmAgEBMIHhMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhBbBkrxJ7XsaaPeKqnI yboQMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTA2MDIwMTE2NTAwNVowIwYJKoZIhvcNAQkEMRYEFJivP6E+DopE7tLuPGHo3B7e Nf+rMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqG SIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEEAYI3EAQxgeQwgeEw gcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO ZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29y cC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENB IEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEFsGSvEntexp o94qqcjJuhAwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwg SW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZl cmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5 ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXIt UGVyc29uYSBOb3QgVmFsaWRhdGVkAhBbBkrxJ7XsaaPeKqnIyboQMA0GCSqGSIb3DQEBAQUA BIIBANHtB3S3Z3l7Fl+TFW4kASH+BWM3zWmdkNUNK47fgD3CzurNTEmj7BpowA19UdxYBsNO sT8OTaWmQE175mzv+WyjFGBBon1GWfzRy2dWh/GQT1K+ijYMtpVd9PAoS1AETpmgtP58h1NV OSg5FruIjmikJjsf+Y0nS2k/6Yh6cx8rNIsDqlv6bb9/dqFTfmQRdNqJAzdtxAerpSUYog3w xUznJFGLNqbldgE/VvNBQ5e5pXw6zZsO5MZ4LzIOlCa6938cCTLyTwJz6IsENqH9287ZyoWv KnXCXzU9H1MbSEFOTNu05381/MkKNgTM+AfwEnQL618uxYiehHlNhmPiyzgAAAAAAAA= --------------ms030406050800080908020108-- Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 7D6BD7F612 for ; Wed, 1 Feb 2006 07:21:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 68653142275 for ; Wed, 1 Feb 2006 07:21:54 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02327-08 for ; Wed, 1 Feb 2006 07:21:54 -0800 (PST) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by laweleka.osafoundation.org (Postfix) with ESMTP id 11C2F14226C for ; Wed, 1 Feb 2006 07:21:54 -0800 (PST) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id E4F56D333A7 for ; Wed, 1 Feb 2006 10:21:52 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Wed, 01 Feb 2006 10:21:52 -0500 X-Sasl-enc: FAMPwZqAV+LhzRKROzPx6iVlABxCm7jr6RJ9RKL5sTji 1138807312 Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id EFA32571513 for ; Wed, 1 Feb 2006 10:21:51 -0500 (EST) Date: Wed, 01 Feb 2006 10:21:50 -0500 From: Cyrus Daboo To: ietf-calsify@osafoundation.org Message-ID: <6F310B9F4D610FC4623148F3@Cyrus-Daboo.local> X-Mailer: Mulberry/4.0.4 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL X-Spam-Level: Subject: [Ietf-calsify] Properties and parameters X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 15:21:54 -0000 Hi, 2445bis now mixes properties and parameter definitions within the same sections. I actually find it a lot harder to navigate around to find a particular definition of either a property or parameter now. What would be extremely useful is an index for the definition of each component, property, parameter and value type. The table of contents is not as good for lookup as it was before. -- Cyrus Daboo Return-Path: X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 271257F611 for ; Wed, 1 Feb 2006 07:03:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 1445414225B for ; Wed, 1 Feb 2006 07:03:27 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04125-02 for ; Wed, 1 Feb 2006 07:03:26 -0800 (PST) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by laweleka.osafoundation.org (Postfix) with ESMTP id D1C3414225A for ; Wed, 1 Feb 2006 07:03:26 -0800 (PST) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 407B7D33995; Wed, 1 Feb 2006 10:03:25 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Wed, 01 Feb 2006 10:03:25 -0500 X-Sasl-enc: 8GwJKmSoZfYSXJoyhFbcuDY5rsexisNDH1ifDE5Gz73d 1138806201 Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 9FF4B571503; Wed, 1 Feb 2006 10:03:18 -0500 (EST) Date: Wed, 01 Feb 2006 10:02:55 -0500 From: Cyrus Daboo To: Tim Hare , ietf-calsify@osafoundation.org Subject: Re: [Ietf-calsify] Small nit in draft-ietf-calsify-rfc2445bis-00.txt Message-ID: <8E753F706A8830F9C6FAFF61@Cyrus-Daboo.local> In-Reply-To: <6.2.1.2.0.20060131213036.01ebc8e0@mail.comcast.net> References: <6.2.1.2.0.20060121225101.01e89f68@mail.comcast.net> <6B6F861D-B888-4D15-8952-27E2541A9DEC@osafoundation.org> <43D5158C.9040809@Royer.com> <9BACEA7F-4C31-4C04-8469-B6B06D951A03@osafoundation.org> <6.2.1.2.0.20060131213036.01ebc8e0@mail.comcast.net> X-Mailer: Mulberry/4.0.4 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL X-Spam-Level: X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-calsify.osafoundation.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 15:03:27 -0000 Hi Tim, --On January 31, 2006 9:32:32 PM -0500 Tim Hare wrote: > 6. An implementation MAY truncate a "SUMMARY" property value to 255 > characters. This raises another issue I just spotted with the use of the terms 'octets' and 'characters'. The first thing to note is that a certain number of octets is not necessarily the same number of characters if non-ascii characters are present with utf-8 encoding. So in the above situation, a truncation at 255 characters could actually result in say 1024 octets if each character was a 4-octet utf-8 sequence. I suggest metioning this in Section 4 to clarify the use of 'octets' vs 'characters'. It may be worth adding an example to Section 5.3 showing non-ascii text being split on a proper character boundary. -- Cyrus Daboo