From owner-ietf-calendar@mail.imc.org Fri Dec 1 06:47:27 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA03994 for ; Fri, 1 Dec 2000 06:47:27 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id DAA14540 for ietf-calendar-bks; Fri, 1 Dec 2000 03:27:07 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id DAA14533 for ; Fri, 1 Dec 2000 03:27:05 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22985; Fri, 1 Dec 2000 06:28:44 -0500 (EST) Message-Id: <200012011128.GAA22985@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-calendar@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-calsch-cap-03.txt Date: Fri, 01 Dec 2000 06:28:43 -0500 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --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 Working Group of the IETF. Title : Calendar Access Protocol (CAP) Author(s) : S. Mansour, D. Royer, G. Babics, P. Hill Filename : draft-ietf-calsch-cap-03.txt Pages : 65 Date : 30-Nov-00 The Calendar Access Protocol (CAP)is an Internet protocol that permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an [RFC2445] based Calendar Store (CS). This memo defines the CAP specification. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-calsch-cap-03.txt 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-ietf-calsch-cap-03.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-ietf-calsch-cap-03.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20001130114116.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-calsch-cap-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-calsch-cap-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001130114116.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-calendar@mail.imc.org Fri Dec 1 10:08:20 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19879 for ; Fri, 1 Dec 2000 10:08:19 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA29720 for ietf-calendar-bks; Fri, 1 Dec 2000 06:52:26 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA29715 for ; Fri, 1 Dec 2000 06:52:25 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eB1EwAA03452 for ; Fri, 1 Dec 2000 09:58:10 -0500 Message-ID: <3A27BC82.4834A60A@ecal.com> Date: Fri, 01 Dec 2000 09:58:10 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Agenda for CALSCH at IETF meeting - San Diego References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Eric Busboom wrote: > Will we have any other (informal) meetings during the week? We generally meet for a semi-working dinner on Monday night; and, last time, we had a working lunch or two. -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |In the country of the blind, the one-eyed man is| |francis@ecal.com|in therapy. | \=================================================================/ From owner-ietf-calendar@mail.imc.org Fri Dec 1 10:12:26 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA20005 for ; Fri, 1 Dec 2000 10:12:26 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA29602 for ietf-calendar-bks; Fri, 1 Dec 2000 06:51:06 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA29597 for ; Fri, 1 Dec 2000 06:51:05 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eB1EulA03444 for ; Fri, 1 Dec 2000 09:56:47 -0500 Message-ID: <3A27BC2E.6A10813B@ecal.com> Date: Fri, 01 Dec 2000 09:56:47 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: CalSched IETF Subject: Re: iTIP updates References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Bruce_Kahn@iris.com wrote: > Ok, besides the obvious "Its gonna happen because email is not > 100%" kind of answer Ill reiterate my original response in a > different way to be clearer. I (still) see no compelling > reason to rev SEQUENCE for this (and restart the workflow > process) when sending out a message with a newer DTSTAMP will > achieve the desired results. Simply put, if Pat and I have an > ongoing weekly meeting we both have accepted and I want to add > Steve to it; why do I have to invalidate Pats current status > and make her reACCEPT all the affected entries Maybe Pat doesn't want to come if Steve is there? (No, I'm not implying anything. :-) -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |"What now, Brain?" "We should flee in terror.| |francis@ecal.com|Yes, that would be the wisest course." | \==============================================================/ From owner-ietf-calendar@mail.imc.org Sun Dec 3 03:30:14 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA06468 for ; Sun, 3 Dec 2000 03:30:14 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA19895 for ietf-calendar-bks; Sat, 2 Dec 2000 23:58:27 -0800 (PST) Received: from royer.com (royer.com [207.177.146.80]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA19885 for ; Sat, 2 Dec 2000 23:58:25 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA10830 for ietf-calendar@imc.org; Sun, 3 Dec 2000 00:00:03 -0800 (PST) Date: Sun, 3 Dec 2000 00:00:03 -0800 (PST) From: Doug Royer Message-Id: <200012030800.AAA10830@royer.com> X-Authentication-Warning: royer.com: doug set sender to Doug@Royer.Com using -r To: ietf-calendar@imc.org Subject: CALSCH Action Items Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a list of action items for the CALSCH Working Group. This list will be sent out once a week and updated as often as practical (That means if I am not available it may take an extra week or two before you see your changes). Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM . There are three parts to this action list: (W) Working group action items. (C) CAP editor action items. (I) iCalendar action items (Frank Dawson) Each action item will be assigned a unique ID that will aid in tracking the items. ------------------------------------------------------------------------------ Working Group Action Items Where Resolution is one of: U - undecided. Y - Chair determined consensus is in favor of the proposal. N - Chair determined consensus is NOT in favor of the proposal. D - Dropped. Chair has decided that it may never reach consensus. The following are a list of proposals and their status in the WG: WG Action Item Resolution -------------- ---------- W-1 CAP Use HTTP as transport N W-2 CAP If all booked and scheduled Y appointments are in same table W-3 CAP Use SASL as authentication method Y W-4 Add UID and COUNTER to VFREEBUSY N W-5 CAP Should CAPABILITY reply be sent N as result of successful AUTHENTICATE and IDENTITY W-6 Do we need to handle 'unscheduled event' as described by the SKI project? N (In CAP - 'N', SKI to be a seperate project/draft as it will effect RFC2445,6,7) W-7 CAP Auto-logout Timer issues Do we need one? Y How long? Can the server decide not to do this? Y W-8 CAP Bounded Latency Issues D W-9 CAP MOVE method. Issues with VCARs. Y [see note in CAP 7.2.1.5] W-10 CAP Text mandatory in all response N codes W-11 CAP Text optional in response codes Y (some response codes may have mandatory data that follows) W-12 CAP Should parts of response code be Y separated by ';' W-13 CAP Store Schema Y W-14 CAP VEVENT Schema Y W-15 CAP VTODO Schema Y W-16 CAP VJOURNAL Schema Y W-17 CAP VCAR Schema Y W-18 CAP UPN definition, including anonymous Y user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and Y static and how groups are used in VCARs. Policy definitions, in a VCAR format. W-20 Associating UPN values with CREATED N and LAST-MODIFIED properties. W-21 CAP Get/Set calendar user properties N W-22 VTIMEZONE and IANA Y in process W-23 CAP Calendar property to allow/disallow N overlapped booking OPAQUE entries? W-24 CAP Calendar CHARSET property issues Y W-25 Remove MUST from UID in 4.8.4.7 Y W-26 Write/Submit information draft/rfc Y W-27 How a query can specify if the recurrence Y rules are to be expanded by the CS. W-28 Cal-Props - PATH N (CAP-00 - 12.2) Will there need to be one? N Optional? N W-29 Import/Export Y - sync only W-30 Transport protocol name (transport vs Y application layer) W-31 NOOP command? Y W-32 NOOP advisory only? Y W-33 Should DISCONNECT be called QUIT? U W-34 Format following error codes. Are Y they well defined? If not they need to be machine determinable. W-35 Move DNS and SLP to seperate draft? Y ------------------------------------------------------------------------------ The following are a list of action items for the draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex Y text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug D C-4 VCAR examples Doug? Y C-5 PUBLISH text Y C-6 REQUEST text Y C-7 REPLY text Y C-8 ADD text Y C-9 CANCEL text Y C-10 REFRESH text Y C-11 COUNTER text Y C-12 DECLINECOUNTER Text Y C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS Y and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property Y C-16 (2.11) Query Schema Y C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Y Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS D Format? Text needs to be written. C-20 (13.) Security Considerations Y See editors note - more text. C-21 Resubmit REQUIREMENTS draft. Y C-22 Document MAXSIZE and MAXRESULT N C-23 Document METHOD is stored in CS database N Only one 'CREATE' per UID. Multple non-CREATE per UID. C-24 Fix the RESPONSE's to be consistant. N and multiple components, one for each TARGET. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: (iCal, iTIP, iMIP) Draft Action Item Who Done (Y/N) ----------------- --- ---------- I-1 MIME alternate/related Frank ? MUST be supported. I-2 Remove ordering of properties and Frank ? parameters in draft. I-3 S/MIME and RFC1847. U [CAP] 2.2.3 I-4 Add ALARMID to VALARM! I-5 iTIP error. VJOURNAL should be 0 (not 0+) for CANCEL ------------------------------------------------------------------------------ Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM -------------------------------------------------------------------------- Work: Doug.Royer@Software.com Home 801 Woodside Rd #14-244 530 E. Montecito St. Office: Redwood City, CA 94061 Santa Barbara, CA 93103 805-957-1790 x541 Personal Email: Doug@Royer.com Tuesday discussion: DONE Section 2.4.3 - editor note: Change with new paragraph; Groups may be in a directory with its own ACL model and CAP should use the directory service to expand a UPN subject to the directory service access control model for the authenticated entity. DONE Section 2.4.4.1 - editor note: Your access is a union of all your grants minus a union of all your denies. (We still need to discuss ordering - allow or not. We may not want to fool with it). DONE Section 2.4.4.2 - editor note: We need an example (Steve/Doug) - Paul needs to read this note an example). Section 2.6 CALID - need to define that relative CALID must be consistent with the scheme specific part of URI as defined in RFC xxx. - Steve Section 2.9 Will be discussed earlier in draft - remove altogether. Section 7.1.3 Need to get IANA registration Section 7.1.3 Delete editors note about blank on examples. Need to add an unsuccessful login. Delete all lines except the line that starts with "The following...." - (* Who will do this example) DONE Section 7.2.1.1.1 Get rid of whole paragraph (pargraph above). If you want to generate unique relative CALids, use the GENERATE UID command and use the result as the relative CALid. (we need to make sure that the results are characters that are compatible with our definition of calids) Section 7.2.1.3. The result needs to be consistent with CALID character rules (i.e. no spaces). The example needs one more line with a dot. Steve will do this. DONE Section 7.2.1.5 This issue goes away because we are not doing heirarchial. Remove editors note Section 7.2.1.7 Add an example of a partial result - we want to get something that matches some things, and on the ones you don't have access, you don't have rights to some of the components. George will write up something. Section 7.2.2 Need restriction tables. Some are CAP - for the rest of them use iTIP tables (Steve/Doug) we all need to review the text DONE Section 7.2.3.2 Pull editors note - fix applied Section 8.0 Response codes. Need to make sure response codes in all drafts - iCal, iMip and iTip and examples. Error numbers need to be the same. Put text about error codes in comments below the examples (so that people don't look at them as being required in their text). Pat will look at the codes. Section 11.0 DTN, DTSTAMP, etc are implementations that may need to be considered. Restrictions tables may resolve these issues. Section 12.0 Leave as is until we get people to agree. On version shipped after last call, this is what we are going to enhance this section. It does not make sense to do this until working group last call. Updates to iCalendar need to be written and will not be submitted to IANA until last call to WG. Doug Section 13.0 This section is not ready for prime time. Need Paul Hill. Need an editors note. Section 14.0 Needs to be reformatted - Doug will make sure it is consistent. George will do 14 DONE Section 15.1.1. Steve - additions or changes to the CAP schema (replaces Define the Entity). Word entity needs to be removed and replaced throughout the document). Section 15.1.4 Submit entity for approval - John submitted to list. Need to find. Get John's text and add back into CAP draft. John submitted as a separate draft document. Use the MIME appeal verbage with John's additional text. Point WG at John's draft and say it should be included in the draft. We need to also submit to April Marine as well. DONE Section 16.0 Remove reference to vCard - - - - - - Assignment list: Section 2.4.4.2 - VCAR example (Steve/Doug) Sectoin 2.6 - Steve will research Section 7.1.3 - IANA registration (Pat) Section 7.1.3 - example of unsuccessful login (Who) Section 7.2.1.1. - look at Calid characters (Doug) Section 7.2.1.3 - example line (Steve) Section 7.2.1.7 - George will write some verbage and we need to add an example of partial results (Steve/Doug) Section 7.2.2. - Restriction tables (Steve/Doug) Section 8.0 - look at consistency of Response code in all drafts (Pat) Section 12.0 - needs work. Check for consistency - Doug Section 13.0 - Paul Hill Section 14.0 - George Section 15.1.1 - replace text (Pat) Section 15.1.4 - add John's text to doc and put on list to look at proposal. - - - - - Work on Restriction table Editor note: Remove references to VDATA (mistake) Editor note: GENERATE UID is not a method. It's wrong in section 7.1.2.3 Ditto with NOOP - Section 7.2.1.6 From owner-ietf-calendar@mail.imc.org Sun Dec 3 08:51:37 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA26087 for ; Sun, 3 Dec 2000 08:51:37 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id FAA27529 for ietf-calendar-bks; Sun, 3 Dec 2000 05:32:33 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id FAA27523 for ; Sun, 3 Dec 2000 05:32:31 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA28846; Sun, 3 Dec 00 08:35:41 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id IAA00708; Sun, 3 Dec 2000 08:34:11 -0500 (EST) Received: from [216.254.65.45] (widget.bobmah.com [216.254.65.45]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id IAA03763; Sun, 3 Dec 2000 08:34:10 -0500 (EST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Sun, 3 Dec 2000 08:34:42 -0500 To: Eric Busboom From: Bob Mahoney Subject: Re: Agenda for CALSCH at IETF meeting - San Diego Cc: pregen@egenconsulting.com, ietf-calendar@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: >Will we have any other (informal) meetings during the week? Two hours does >not seem like much time. In addition to the now-traditional Monday dinners, calsch folks do tend to grab a few social/working meals together as their schedules permit . It's pretty common to get together several times during the week to work on ideas and try to improve text. I'd encourage you to try and make the Monday dinner, anyway. It really helps to put faces to names... -Bob From owner-ietf-calendar@mail.imc.org Sun Dec 3 18:48:53 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22634 for ; Sun, 3 Dec 2000 18:48:52 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id PAA08478 for ietf-calendar-bks; Sun, 3 Dec 2000 15:31:59 -0800 (PST) Received: from chemms.chem.pku.edu.cn (chemms.chem.pku.edu.cn [162.105.153.150]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id PAA08448; Sun, 3 Dec 2000 15:31:41 -0800 (PST) From: bn1bn2@yahoo.com Received: from 5zfYc8uFT (1cust13.tnt21.lax3.da.uu.net) by chemms.chem.pku.edu.cn with SMTP (5.67b8/1.2-eef) id AA16095; Mon, 4 Dec 2000 07:26:24 -0800 Date: 03 Dec 00 3:36:33 PM Message-Id: Subject: Holiday Special: Don't miss the savings! Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hurry!!! Time is running out. Thinking of getting a laptop computer for the holidays, or any occasions... Brand new name brand notebooks at up to 35% savings, compare around than call us 1-800-644-9584. We have thousands Notebook PC, PDAs, Digital Cameras, Parts and Accessories in stock for the holiday, anything you need, we can get you the lower prices. C o m p a q ================================================== Compaq Armada M700 $2199 Intel PIII 650 MHz, 128MB, 12.0GB, 14.1in TFT, 24X CD-ROM, 56 Kbps, 10/100 Ethernet Card, Windows NT 4.0 Compaq Presario 1200-XL125 $1379 AMD K6-2 533 MHz, 64MB , 6.0GB, 13.3in TFT, 8X DVD-ROM, 56Kbps , WIN98se Compaq Presario 1200-XL300 $1095 Intel Celeron 600 MHz, 64MB, 6.0GB, 13in HPA, 24X CD-ROM, 56K , Windows ME Compaq Presario 1200-XL325 $1499 Intel PIII 650 MHz, 64MB, 6.0GB, 13.3in TFT, 8X DVD-ROM, 56K , Windows ME Compaq Presario 1700-XL360 $1799 Intel PIII 600 MHz, 64MB, 10.0GB, 14.1in TFT, 8X DVD-ROM, 56K , Windows ME H P ==================================================== HP Omni Book 6000 $3499 Intel PIII 850MHz , 128 MB , 20GB, 15.1in TFT, 8X DVD-ROM, 56Kbps, Windows 2000 HP Pavilion N5150 $1499 Intel PIII 600 MHz, 64MB, 10.0GB , 13.3in TFT, 8X DVD-ROM, 56Kbps, Windows Millennium Edition HP Pavilion N5170 $1599 Intel PIII 600 MHz , 64MB, 7.0GB , 14.1in TFT, 8X DVD-ROM, 56Kbps, 10/100 Ethernet, Windows Millennium Edition HP Pavilion N5195 $2199 Intel PIII 700 MHz , 128MB , 20.0GB , 15.1in TFT, 8X DVD-ROM, 56Kbps, 10/100 Ethernet, Windows Millennium Edition S O N Y ==================================================== Sony VAIO PCG-F580 Notebook $2099 Intel PIII 650 MHz, 64MB, 12.0GB, 15.0in TFT, 8X DVD-ROM, 56K, Windows 98se Sony VAIO PCG-F650 Notebook $1889 Intel PIII 600 MHz, 64MB, 12.0GB, 14.1in TFT, 8X DVD-ROM, 56Kbps, Windows ME For more info or to place an order call: 1-800-644-9584 To Visit Our Site http://www.laptopland.com to find out more detail This message is being sent to you in compliance with the proposed Federal legislation for commercial e-mail (S.1618 - SECTION 301)."Pursuant to Section 301, Paragraph (a)(2)(C) of S. 1618, further transmissions to you by the sender of this e-mail may be stopped at no cost to you by submitting a request to be removed. INSTRUCTIONS- click here mailto:member9288@computerassociation.com?subject=removelist134 to be removed. From owner-ietf-calendar@mail.imc.org Tue Dec 5 00:19:22 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19603 for ; Tue, 5 Dec 2000 00:19:21 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id UAA15032 for ietf-calendar-bks; Mon, 4 Dec 2000 20:52:35 -0800 (PST) Received: from server1.egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA15023 for ; Mon, 4 Dec 2000 20:52:33 -0800 (PST) From: pregen@egenconsulting.com To: John Stracke Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: iTIP updates X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 Message-ID: Date: Mon, 4 Dec 2000 23:54:15 -0500 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 12/04/2000 11:54:28 PM, Serialize complete at 12/04/2000 11:54:28 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 001995E1852569AC_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 001995E1852569AC_= Content-Type: text/plain; charset="us-ascii" Hm, attending meetings with multiple vendors in attendance is ALWAYS interesting. Not a problem. 8-) ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 John Stracke Sent by: owner-ietf-calendar@mail.imc.org 12/01/00 09:56 AM To: CalSched IETF cc: Subject: Re: iTIP updates Bruce_Kahn@iris.com wrote: > Ok, besides the obvious "Its gonna happen because email is not > 100%" kind of answer Ill reiterate my original response in a > different way to be clearer. I (still) see no compelling > reason to rev SEQUENCE for this (and restart the workflow > process) when sending out a message with a newer DTSTAMP will > achieve the desired results. Simply put, if Pat and I have an > ongoing weekly meeting we both have accepted and I want to add > Steve to it; why do I have to invalidate Pats current status > and make her reACCEPT all the affected entries Maybe Pat doesn't want to come if Steve is there? (No, I'm not implying anything. :-) -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |"What now, Brain?" "We should flee in terror.| |francis@ecal.com|Yes, that would be the wisest course." | \==============================================================/ --=_alternative 001995E1852569AC_= Content-Type: text/html; charset="us-ascii"
Hm, attending meetings with multiple vendors in attendance is ALWAYS interesting. Not a problem.   8-)
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


John Stracke <francis@ecal.com>
Sent by: owner-ietf-calendar@mail.imc.org

12/01/00 09:56 AM

       
        To:        CalSched IETF <ietf-calendar@imc.org>
        cc:        
        Subject:        Re: iTIP updates



Bruce_Kahn@iris.com wrote:

> Ok, besides the obvious "Its gonna happen because email is not
> 100%" kind of answer Ill reiterate my original response in a
> different way to be clearer.  I (still) see no compelling
> reason to rev SEQUENCE for this (and restart the workflow
> process) when sending out a message with a newer DTSTAMP will
> achieve the desired results.  Simply put, if Pat and I have an
> ongoing weekly meeting we both have accepted and I want to add
> Steve to it; why do I have to invalidate Pats current status
> and make her reACCEPT all the affected entries

Maybe Pat doesn't want to come if Steve is there?

(No, I'm not implying anything.  :-)

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |"What now, Brain?" "We should flee in terror.|
|francis@ecal.com|Yes, that would be the wisest course."       |
\==============================================================/

--=_alternative 001995E1852569AC_=-- From owner-ietf-calendar@mail.imc.org Tue Dec 5 11:33:15 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA02476 for ; Tue, 5 Dec 2000 11:33:14 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA29065 for ietf-calendar-bks; Tue, 5 Dec 2000 08:14:04 -0800 (PST) Received: from e-smith.net (mail.e-smith.com [64.26.145.90]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id IAA29048 for ; Tue, 5 Dec 2000 08:13:51 -0800 (PST) Received: (qmail 12704 invoked from network); 5 Dec 2000 16:15:11 -0000 Received: from unknown (HELO e-smith.com) (192.168.16.20) by 192.168.14.2 with SMTP; 5 Dec 2000 16:15:11 -0000 Received: (qmail 13715 invoked from network); 5 Dec 2000 16:15:11 -0000 Received: from unknown (HELO infotrope.net) (192.168.16.110) by 192.168.16.20 with SMTP; 5 Dec 2000 16:15:11 -0000 Message-ID: <3A2D148E.39609211@infotrope.net> Date: Tue, 05 Dec 2000 11:15:10 -0500 From: Kirrily Robert X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: XML DTD information Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Greetings, I've recently joined this list, and have been going through the archives. I see a lot of traffic on the topic of an XML DTD and/or schema to describe iCalendar data. Is there a site where I can find further information on this? Thanks in advance, K. -- Kirrily "Skud" Robert skud@e-smith.com (work) skud@infotrope.net (home) From owner-ietf-calendar@mail.imc.org Tue Dec 5 12:01:11 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10648 for ; Tue, 5 Dec 2000 12:01:10 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA01279 for ietf-calendar-bks; Tue, 5 Dec 2000 08:38:52 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA01271 for ; Tue, 5 Dec 2000 08:38:50 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eB5Gj1O19237 for ; Tue, 5 Dec 2000 11:45:01 -0500 Message-ID: <3A2D1B8D.3BA1CEEA@ecal.com> Date: Tue, 05 Dec 2000 11:45:01 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: XML DTD information References: <3A2D148E.39609211@infotrope.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Kirrily Robert wrote: > I see a lot of traffic on the topic of an XML DTD and/or schema to > describe iCalendar data. Is there a site where I can find further > information on this? No, it didn't really go anywhere. The Internet-Draft seems to have expired by now. -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |But how do we know destroying the Van Allen belt| |francis@ecal.com|will kill all life on Earth if we don't try it? | \=================================================================/ From owner-ietf-calendar@mail.imc.org Wed Dec 6 09:30:51 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20105 for ; Wed, 6 Dec 2000 09:30:51 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id GAA03031 for ietf-calendar-bks; Wed, 6 Dec 2000 06:01:51 -0800 (PST) Received: from ljudo.shortlist.se (IDENT:postfix@ljudo.shortlist.se [193.14.119.253]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA03026 for ; Wed, 6 Dec 2000 06:01:49 -0800 (PST) Received: from gregs (unknown [193.14.119.6]) by ljudo.shortlist.se (Postfix) with SMTP id 0A776B34FE; Wed, 6 Dec 2000 15:03:53 +0100 (CET) From: "Greg FitzPatrick" To: "Kirrily Robert" , Cc: "Surendra Reddy" , "Lisa Lippert (Dusseault) (Exchange)" Subject: SV: XML DTD information Date: Wed, 6 Dec 2000 15:04:12 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <3A2D148E.39609211@infotrope.net> Importance: Normal Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: X-MIME-Autoconverted: from 8bit to quoted-printable by ns.secondary.com id GAA03031 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA20105 Yes the XML question was sometimes quite heatedly discussed. Here is Frank's draft - out of date but not forgotten. http://www.globecom.net/ietf/draft/draft-dawson-ical-xml-dtd-01.html The XML issue had a lot to do with loss of interoperability as well as the diverging product strategies of the parent companies of several of the CALSCH WG participants. When the XML question was raised, I believe first by Surendra Reddy from Oracle, iCal had already reached a relatively high level of interoperability, counting several major application providers amongst its implementers. There were fears that embracing XML would lead to dis-interoperability. It will be obvious to any software engineer, when given a choice, that an infostructure technology that allows nesting, name-spaces and schemas is a better vehicle for their creative ideas than a flat infostructure technology that doesn't do much more than get along well with the current mail protocol standards. Don't get me wrong though, when this came up, iCal and vCard objects were alive and well on millions of peoples computers, XML was a great idea with almost no existing applications and entrenched in a lot of controversy to boot. If I remember correctly from Oslo - one side wanted a totally one2one mapping of 2445 into a DTD and the other side wanted to get started right away with "improving" things. Furthermore CAP was already taking up a lot of delegates energy and the thinking was; let us just get CAP under our belts and then we can turn our attention to XML (and SKiCal for that matter) As a sideline I can say that we have developed SKiCal in both mime-directory and dtd/schema forms from the beginning of our work almost three years ago. (We actually began with Dublin Core metatags.) Last Christmas I wrote a mail to some of the members of this list and some W3C people. I proposed a joint IETF/W3C working group (á digital signatures) to develop an XML iCal schema. Though I received support from W3C folks (Tim Berners-Lee and Dan Connolly among others) there was less enthusiasm from the IETF side. After a short flurry of email - the last I heard of this was in a conversation with Scott Bradner here in Stockholm. "We are talking about it", he said. But then things just died down. If you are interested, there is a RDF model of iCal/SKiCal in the W3C archives (written by Jonas Liljegren) as well as a review of iCal which Tim BL wrote (I don't think he read 2445 very carefully) considering iCal/SKiCal as a candidate for RDF-isation. I am CC:ing this to Surendra and Lisa who where part of the original XML thrust and no longer populate this list to see if they want to set the record straight for historical purposes my version is of course is sheer MHO. Lastly, here is a pointer to a short tutorial comparing "flat" and "nested" object publishing. http://www.metamatrix.se/presentationer/html/tutorial/chap1.htm If you will be in San Diego, I will gladly elaborate. Greg Greetings, I've recently joined this list, and have been going through the archives. I see a lot of traffic on the topic of an XML DTD and/or schema to describe iCalendar data. Is there a site where I can find further information on this? Thanks in advance, K. -- Kirrily "Skud" Robert skud@e-smith.com (work) skud@infotrope.net (home) From owner-ietf-calendar@mail.imc.org Thu Dec 7 06:19:18 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA29574 for ; Thu, 7 Dec 2000 06:19:18 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id DAA10664 for ietf-calendar-bks; Thu, 7 Dec 2000 03:04:03 -0800 (PST) Received: from mgw-dax2.ext.nokia.com ([63.78.179.217]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id DAA10659 for ; Thu, 7 Dec 2000 03:04:01 -0800 (PST) From: Frank.Dawson@nokia.com Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86]) by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id eB7B68615300 for ; Thu, 7 Dec 2000 05:06:09 -0600 (CST) Received: from daebh01nok.americas.nokia.com (unverified) by davir03nok.americas.nokia.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Thu, 7 Dec 2000 05:05:31 -0600 Received: by daebh01nok with Internet Mail Service (5.5.2652.78) id ; Thu, 7 Dec 2000 05:01:04 -0600 Message-ID: <30F2DED23724D311902D0008C7EABAFB0301E0B0@daeis06nok> To: greg.fitzpatrick@metamatrix.se, ietf-calendar@imc.org Subject: RE: XML DTD information Date: Thu, 7 Dec 2000 04:59:42 -0600 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Greg FitzPatrick wrote: >If I remember correctly from Oslo - one side wanted a totally one2one >mapping of 2445 into a DTD and the other side wanted to get started right >away with "improving" things. The instructions we have _always_ had from our area directors, wg chair and the general consensus of the wg participants has been to have ONE AND ONLY ONE definition of calendaring semantics, called iCalendar. The XML DTD was to only be an alternative syntax for that work. It certainly helps to be reminded about this fact, when ever this discussion comes up. -- Frank From owner-ietf-calendar@mail.imc.org Thu Dec 7 14:47:58 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23553 for ; Thu, 7 Dec 2000 14:47:55 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id LAA20389 for ietf-calendar-bks; Thu, 7 Dec 2000 11:18:57 -0800 (PST) Received: from ljudo.shortlist.se (IDENT:postfix@ljudo.shortlist.se [193.14.119.253]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA20380 for ; Thu, 7 Dec 2000 11:18:54 -0800 (PST) Received: from gregs (unknown [193.14.119.6]) by ljudo.shortlist.se (Postfix) with SMTP id BB0D9B34FE; Thu, 7 Dec 2000 20:21:04 +0100 (CET) From: "Greg FitzPatrick" To: , Subject: SV: XML DTD information Date: Thu, 7 Dec 2000 20:21:25 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <30F2DED23724D311902D0008C7EABAFB0301E0B0@daeis06nok> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Hi Frank Congratulations to your new working address. Perhaps we will see you up here in the polar circle soon. Surely Nokia calendar implementation will be iCal compliant any day now, now that you are on board. Otherwise, I hope it is clear that I was just trying to relate history. I was trying my best not to be partial. I have always had respect for both sides of this issue. And needless to say - this is water under the bridge - time marches on. Frank wrote: The instructions we have _always_ had from our area directors, wg chair and the general consensus of the wg participants has been to have ONE AND ONLY ONE definition of calendaring semantics, called iCalendar. The XML DTD was to only be an alternative syntax for that work. It certainly helps to be reminded about this fact, when ever this discussion comes up. From owner-ietf-calendar@mail.imc.org Fri Dec 8 11:04:32 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03281 for ; Fri, 8 Dec 2000 11:04:31 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id HAA13327 for ietf-calendar-bks; Fri, 8 Dec 2000 07:30:06 -0800 (PST) Received: from ljudo.shortlist.se (IDENT:postfix@ljudo.shortlist.se [193.14.119.253]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA13321 for ; Fri, 8 Dec 2000 07:30:04 -0800 (PST) Received: from real (unknown [193.14.119.80]) by ljudo.shortlist.se (Postfix) with SMTP id 2879AB3502; Fri, 8 Dec 2000 16:32:20 +0100 (CET) From: "Greg FitzPatrick" To: "Bob Mahoney" , "Eric Busboom" Cc: , Subject: SV: Agenda for CALSCH at IETF meeting - San Diego Date: Fri, 8 Dec 2000 16:32:18 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Where is the traditional monday dinner to be eaten? Greg >Will we have any other (informal) meetings during the week? Two hours does >not seem like much time. In addition to the now-traditional Monday dinners, calsch folks do tend to grab a few social/working meals together as their schedules permit . It's pretty common to get together several times during the week to work on ideas and try to improve text. I'd encourage you to try and make the Monday dinner, anyway. It really helps to put faces to names... -Bob From owner-ietf-calendar@mail.imc.org Sat Dec 9 12:45:47 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA27453 for ; Sat, 9 Dec 2000 12:45:46 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA17651 for ietf-calendar-bks; Sat, 9 Dec 2000 09:12:10 -0800 (PST) Received: from nt1.rocori.k12.mn.us (nt1.rocori.k12.mn.us [207.229.251.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA17647; Sat, 9 Dec 2000 09:12:08 -0800 (PST) Message-Id: <200012091712.JAA17647@ns.secondary.com> From: Mail Sender To: ietf-announce-request@ietf.org CC: ietf-calendar@imc.org, ietf-calendar-request@imc.org, ietf-cat-wg@lists.stanford.edu, ietf-cat-wg-request@lists.stanford.edu, ietf-dav-versioning@w3.org Subject: Russian Goods and Service from Moscow Reply-To: mailsender@mailsender.ru Date: 09.12.2000 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: www.rusgoods.com www.rusgoods.ru ================================================================ We present you the production of the 1-st Moscow Watch Factory "Poljot" (Flying). From the simple mechanical watch of the series 2609 till unique, composite and precise mechanical o'clock - Marine timer . It is unique factory in Russia, which makes mechanical hours with the Swiss quality. Factory, which makes watches for the Russian Air Forces , Russian Naval Forces. All mechanical watch which we offer to you, will be delivered to you directly from the factory. If it isn't in the warehouse of the factory, we will place your order directly at the 1-st Moscow Watch Factory without any middlemans. The submarine "Kursk" had on board mechanical marine hronometr 6MX. =============================================================== The "table" of orders. Here you can to order, to find, to know almost everything, than the Russia is rich, everything that does not contradict Russian Federation laws. Here you can receive or order: The information about any enterprise, firm, organization, or person in Russia The production or any goods of Russian manufactories, and other things if it is possible. =============================================================== www.rusgoods.com www.rusgoods.ru From owner-ietf-calendar@mail.imc.org Sun Dec 10 03:22:25 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02510 for ; Sun, 10 Dec 2000 03:22:25 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA05472 for ietf-calendar-bks; Sat, 9 Dec 2000 23:57:52 -0800 (PST) Received: from royer.com (royer.com [207.177.146.80]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA05468 for ; Sat, 9 Dec 2000 23:57:50 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA17377 for ietf-calendar@imc.org; Sun, 10 Dec 2000 00:00:03 -0800 (PST) Date: Sun, 10 Dec 2000 00:00:03 -0800 (PST) From: Doug Royer Message-Id: <200012100800.AAA17377@royer.com> X-Authentication-Warning: royer.com: doug set sender to Doug@Royer.Com using -r To: ietf-calendar@imc.org Subject: CALSCH Action Items Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a list of action items for the CALSCH Working Group. This list will be sent out once a week and updated as often as practical (That means if I am not available it may take an extra week or two before you see your changes). Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM . There are three parts to this action list: (W) Working group action items. (C) CAP editor action items. (I) iCalendar action items (Frank Dawson) Each action item will be assigned a unique ID that will aid in tracking the items. ------------------------------------------------------------------------------ Working Group Action Items Where Resolution is one of: U - undecided. Y - Chair determined consensus is in favor of the proposal. N - Chair determined consensus is NOT in favor of the proposal. D - Dropped. Chair has decided that it may never reach consensus. The following are a list of proposals and their status in the WG: WG Action Item Resolution -------------- ---------- W-1 CAP Use HTTP as transport N W-2 CAP If all booked and scheduled Y appointments are in same table W-3 CAP Use SASL as authentication method Y W-4 Add UID and COUNTER to VFREEBUSY N W-5 CAP Should CAPABILITY reply be sent N as result of successful AUTHENTICATE and IDENTITY W-6 Do we need to handle 'unscheduled event' as described by the SKI project? N (In CAP - 'N', SKI to be a seperate project/draft as it will effect RFC2445,6,7) W-7 CAP Auto-logout Timer issues Do we need one? Y How long? Can the server decide not to do this? Y W-8 CAP Bounded Latency Issues D W-9 CAP MOVE method. Issues with VCARs. Y [see note in CAP 7.2.1.5] W-10 CAP Text mandatory in all response N codes W-11 CAP Text optional in response codes Y (some response codes may have mandatory data that follows) W-12 CAP Should parts of response code be Y separated by ';' W-13 CAP Store Schema Y W-14 CAP VEVENT Schema Y W-15 CAP VTODO Schema Y W-16 CAP VJOURNAL Schema Y W-17 CAP VCAR Schema Y W-18 CAP UPN definition, including anonymous Y user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and Y static and how groups are used in VCARs. Policy definitions, in a VCAR format. W-20 Associating UPN values with CREATED N and LAST-MODIFIED properties. W-21 CAP Get/Set calendar user properties N W-22 VTIMEZONE and IANA Y in process W-23 CAP Calendar property to allow/disallow N overlapped booking OPAQUE entries? W-24 CAP Calendar CHARSET property issues Y W-25 Remove MUST from UID in 4.8.4.7 Y W-26 Write/Submit information draft/rfc Y W-27 How a query can specify if the recurrence Y rules are to be expanded by the CS. W-28 Cal-Props - PATH N (CAP-00 - 12.2) Will there need to be one? N Optional? N W-29 Import/Export Y - sync only W-30 Transport protocol name (transport vs Y application layer) W-31 NOOP command? Y W-32 NOOP advisory only? Y W-33 Should DISCONNECT be called QUIT? U W-34 Format following error codes. Are Y they well defined? If not they need to be machine determinable. W-35 Move DNS and SLP to seperate draft? Y ------------------------------------------------------------------------------ The following are a list of action items for the draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex Y text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug D C-4 VCAR examples Doug? Y C-5 PUBLISH text Y C-6 REQUEST text Y C-7 REPLY text Y C-8 ADD text Y C-9 CANCEL text Y C-10 REFRESH text Y C-11 COUNTER text Y C-12 DECLINECOUNTER Text Y C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS Y and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property Y C-16 (2.11) Query Schema Y C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Y Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS D Format? Text needs to be written. C-20 (13.) Security Considerations Y See editors note - more text. C-21 Resubmit REQUIREMENTS draft. Y C-22 Document MAXSIZE and MAXRESULT N C-23 Document METHOD is stored in CS database N Only one 'CREATE' per UID. Multple non-CREATE per UID. C-24 Fix the RESPONSE's to be consistant. N and multiple components, one for each TARGET. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: (iCal, iTIP, iMIP) Draft Action Item Who Done (Y/N) ----------------- --- ---------- I-1 MIME alternate/related Frank ? MUST be supported. I-2 Remove ordering of properties and Frank ? parameters in draft. I-3 S/MIME and RFC1847. U [CAP] 2.2.3 I-4 Add ALARMID to VALARM! I-5 iTIP error. VJOURNAL should be 0 (not 0+) for CANCEL ------------------------------------------------------------------------------ Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM -------------------------------------------------------------------------- Work: Doug.Royer@Software.com Home 801 Woodside Rd #14-244 530 E. Montecito St. Office: Redwood City, CA 94061 Santa Barbara, CA 93103 805-957-1790 x541 Personal Email: Doug@Royer.com Tuesday discussion: DONE Section 2.4.3 - editor note: Change with new paragraph; Groups may be in a directory with its own ACL model and CAP should use the directory service to expand a UPN subject to the directory service access control model for the authenticated entity. DONE Section 2.4.4.1 - editor note: Your access is a union of all your grants minus a union of all your denies. (We still need to discuss ordering - allow or not. We may not want to fool with it). DONE Section 2.4.4.2 - editor note: We need an example (Steve/Doug) - Paul needs to read this note an example). Section 2.6 CALID - need to define that relative CALID must be consistent with the scheme specific part of URI as defined in RFC xxx. - Steve Section 2.9 Will be discussed earlier in draft - remove altogether. Section 7.1.3 Need to get IANA registration Section 7.1.3 Delete editors note about blank on examples. Need to add an unsuccessful login. Delete all lines except the line that starts with "The following...." - (* Who will do this example) DONE Section 7.2.1.1.1 Get rid of whole paragraph (pargraph above). If you want to generate unique relative CALids, use the GENERATE UID command and use the result as the relative CALid. (we need to make sure that the results are characters that are compatible with our definition of calids) Section 7.2.1.3. The result needs to be consistent with CALID character rules (i.e. no spaces). The example needs one more line with a dot. Steve will do this. DONE Section 7.2.1.5 This issue goes away because we are not doing heirarchial. Remove editors note Section 7.2.1.7 Add an example of a partial result - we want to get something that matches some things, and on the ones you don't have access, you don't have rights to some of the components. George will write up something. Section 7.2.2 Need restriction tables. Some are CAP - for the rest of them use iTIP tables (Steve/Doug) we all need to review the text DONE Section 7.2.3.2 Pull editors note - fix applied Section 8.0 Response codes. Need to make sure response codes in all drafts - iCal, iMip and iTip and examples. Error numbers need to be the same. Put text about error codes in comments below the examples (so that people don't look at them as being required in their text). Pat will look at the codes. Section 11.0 DTN, DTSTAMP, etc are implementations that may need to be considered. Restrictions tables may resolve these issues. Section 12.0 Leave as is until we get people to agree. On version shipped after last call, this is what we are going to enhance this section. It does not make sense to do this until working group last call. Updates to iCalendar need to be written and will not be submitted to IANA until last call to WG. Doug Section 13.0 This section is not ready for prime time. Need Paul Hill. Need an editors note. Section 14.0 Needs to be reformatted - Doug will make sure it is consistent. George will do 14 DONE Section 15.1.1. Steve - additions or changes to the CAP schema (replaces Define the Entity). Word entity needs to be removed and replaced throughout the document). Section 15.1.4 Submit entity for approval - John submitted to list. Need to find. Get John's text and add back into CAP draft. John submitted as a separate draft document. Use the MIME appeal verbage with John's additional text. Point WG at John's draft and say it should be included in the draft. We need to also submit to April Marine as well. DONE Section 16.0 Remove reference to vCard - - - - - - Assignment list: Section 2.4.4.2 - VCAR example (Steve/Doug) Sectoin 2.6 - Steve will research Section 7.1.3 - IANA registration (Pat) Section 7.1.3 - example of unsuccessful login (Who) Section 7.2.1.1. - look at Calid characters (Doug) Section 7.2.1.3 - example line (Steve) Section 7.2.1.7 - George will write some verbage and we need to add an example of partial results (Steve/Doug) Section 7.2.2. - Restriction tables (Steve/Doug) Section 8.0 - look at consistency of Response code in all drafts (Pat) Section 12.0 - needs work. Check for consistency - Doug Section 13.0 - Paul Hill Section 14.0 - George Section 15.1.1 - replace text (Pat) Section 15.1.4 - add John's text to doc and put on list to look at proposal. - - - - - Work on Restriction table Editor note: Remove references to VDATA (mistake) Editor note: GENERATE UID is not a method. It's wrong in section 7.1.2.3 Ditto with NOOP - Section 7.2.1.6 From owner-ietf-calendar@mail.imc.org Sun Dec 10 09:00:58 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA22544 for ; Sun, 10 Dec 2000 09:00:57 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id FAA19757 for ietf-calendar-bks; Sun, 10 Dec 2000 05:41:44 -0800 (PST) Received: from smtp1.atcominfo.com ([199.106.231.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id FAA19753 for ; Sun, 10 Dec 2000 05:41:43 -0800 (PST) From: pregen@egenconsulting.com Received: from TP770e ([63.95.215.5]) by smtp1.atcominfo.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Sat, 9 Dec 2000 14:23:58 -0800 To: ietf-calendar@imc.org Subject: Monday dinner at IETF meeting X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 Message-ID: Date: Sat, 9 Dec 2000 17:20:17 -0500 X-MIMETrack: Serialize by Notes Client on Pat R Egen/Egen Consulting/01(Release 5.0.2a |November 23, 1999) at 12/09/2000 05:20:17 PM, Serialize complete at 12/09/2000 05:20:17 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 007AB4CB852569B0_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 007AB4CB852569B0_= Content-Type: text/plain; charset="us-ascii" As usual, we are going to try to meet in the lobby of the conference hotel (i.e. the Sheraton) at around 7:00 pm on Monday, 12/11. Please gather there if you are interested in coming to dinner. We'll have a better idea that day of good places to dine and chat. Hope to see you there. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 007AB4CB852569B0_= Content-Type: text/html; charset="us-ascii"
As usual, we are going to try to meet in the lobby of the conference hotel (i.e. the Sheraton) at around 7:00 pm on Monday, 12/11.  Please gather there if you are interested in coming to dinner.  We'll have a better idea that day of good places to dine and chat.  Hope to see you there.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 007AB4CB852569B0_=-- From owner-ietf-calendar@mail.imc.org Sun Dec 10 11:45:09 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27858 for ; Sun, 10 Dec 2000 11:45:08 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA26522 for ietf-calendar-bks; Sun, 10 Dec 2000 08:24:23 -0800 (PST) Received: from smtp1.atcominfo.com ([199.106.231.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA26516 for ; Sun, 10 Dec 2000 08:24:21 -0800 (PST) Received: from localhost.localdomain ([63.219.39.36]) by smtp1.atcominfo.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Sun, 10 Dec 2000 08:21:08 -0800 Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBAGM7607745 for ; Sun, 10 Dec 2000 11:22:08 -0500 Message-ID: <3A33ADAE.B04ACE66@ecal.com> Date: Sun, 10 Dec 2000 11:22:06 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Monday dinner at IETF meeting References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit pregen@egenconsulting.com wrote: > As usual, we are going to try to meet in the lobby of the > conference hotel (i.e. the Sheraton) East Tower or West? (The East Tower lobby seems to be the main lobby, where they send you to register, so I'd suggest that, since it's the one people are likely to default to.) -- /===============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |==============================================| |eCal Corp. |A computer without Windows is like a chocolate| |francis@ecal.com|cake without mustard. | \===============================================================/ From owner-ietf-calendar@mail.imc.org Sun Dec 10 14:11:42 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA00847 for ; Sun, 10 Dec 2000 14:11:42 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id KAA28762 for ietf-calendar-bks; Sun, 10 Dec 2000 10:48:15 -0800 (PST) Received: from smtp1.atcominfo.com ([199.106.231.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA28757 for ; Sun, 10 Dec 2000 10:48:14 -0800 (PST) From: pregen@egenconsulting.com Received: from TP770e ([63.95.215.4]) by smtp1.atcominfo.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Sun, 10 Dec 2000 10:54:00 -0800 To: John Stracke Cc: ietf-calendar@imc.org Subject: Re: Monday dinner at IETF meeting X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 Message-ID: Date: Sun, 10 Dec 2000 13:50:16 -0500 X-MIMETrack: Serialize by Notes Client on Pat R Egen/Egen Consulting/01(Release 5.0.2a |November 23, 1999) at 12/10/2000 01:50:16 PM, Serialize complete at 12/10/2000 01:50:16 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 00677A7B852569B1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 00677A7B852569B1_= Content-Type: text/plain; charset="us-ascii" Thanks John, good suggestion. East tower it is. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 John Stracke Sent by: owner-ietf-calendar@mail.imc.org 12/10/00 11:22 AM To: ietf-calendar@imc.org cc: Subject: Re: Monday dinner at IETF meeting pregen@egenconsulting.com wrote: > As usual, we are going to try to meet in the lobby of the > conference hotel (i.e. the Sheraton) East Tower or West? (The East Tower lobby seems to be the main lobby, where they send you to register, so I'd suggest that, since it's the one people are likely to default to.) -- /===============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |==============================================| |eCal Corp. |A computer without Windows is like a chocolate| |francis@ecal.com|cake without mustard. | \===============================================================/ --=_alternative 00677A7B852569B1_= Content-Type: text/html; charset="us-ascii"
Thanks John, good suggestion.  East tower it is.  
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


John Stracke <francis@ecal.com>
Sent by: owner-ietf-calendar@mail.imc.org

12/10/00 11:22 AM

       
        To:        ietf-calendar@imc.org
        cc:        
        Subject:        Re: Monday dinner at IETF meeting



pregen@egenconsulting.com wrote:

> As usual, we are going to try to meet in the lobby of the
> conference hotel (i.e. the Sheraton)

East Tower or West?

(The East Tower lobby seems to be the main lobby, where they send
you to register, so I'd suggest that, since it's the one people
are likely to default to.)

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |A computer without Windows is like a chocolate|
|francis@ecal.com|cake without mustard.                         |
\===============================================================/

--=_alternative 00677A7B852569B1_=-- From owner-ietf-calendar@mail.imc.org Mon Dec 11 19:44:17 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16393 for ; Mon, 11 Dec 2000 19:44:16 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id QAA09719 for ietf-calendar-bks; Mon, 11 Dec 2000 16:01:54 -0800 (PST) Received: from agony.busboom.org (24-25-200-53.san.rr.com [24.25.200.53]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA09713 for ; Mon, 11 Dec 2000 16:01:52 -0800 (PST) Received: from localhost (eric@localhost) by agony.busboom.org (8.9.3/8.9.3) with ESMTP id QAA08004 for ; Mon, 11 Dec 2000 16:04:04 -0800 X-Authentication-Warning: agony.busboom.org: eric owned process doing -bs Date: Mon, 11 Dec 2000 16:04:02 -0800 (PST) From: Eric Busboom X-Sender: eric@agony.busboom.org To: ietf-calendar@imc.org Subject: RFC 2445 Issues List Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463809014-1069117017-976579310=:22782" Content-ID: Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1463809014-1069117017-976579310=:22782 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: The latest version of the RFC2445 Issues list is available online at: http://softwarestudio.org/iCal/2445Issues.html You can also get the list as a CSV file ( without all the spiffy hypertext links ) at: http://www.softwarestudio.org/iCal/Issues.csv An abbreviated version is also attached to this message. This list is being kept to track errors and omissions to RFC2445. Please review the list, and contribute to it by responding to the mail I send out regarding the issues. If the issue is not listed as a typo, we need your input to close it out. eric. ---1463809014-1069117017-976579310=:22782 Content-Type: TEXT/PLAIN; NAME="Issues.txt" Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="Issues.txt" Content-Transfer-Encoding: BASE64 UkZDMjQ0NSBJc3N1ZXMgTGlzdA0KDQpUaGlzIGlzIGEgc3VtbWFyeSB2ZXJz aW9uIG9mIHRoZSBSRkMyNDQ1IGlzc3VlcyBsaXN0LiBQbGVhc2Ugc2VlIHRo ZQ0KaHRtbCB2ZXJzaW9uICggZmlsZTovLy9ob21lL2VyaWMvZG9jdW1lbnRz L2lDYWwvSXNzdWVzLmh0bWwgKSBmb3INCmNvbXBsZXRlIGRldGFpbHMuDQoN Cg0KMCAgRGlzcG9zaXRpb24gVHlwZSAgIFN1bW1hcnkNCjEgIFJlamVjdGVk IElDUiAgICBTcGVjaWZ5IEZpbGUgbmFtZSBpbiBBVFRBQ0g/DQoyICBSZWpl Y3RlZCBJQ1IgICAgQllEQVkgdGVybWlub2xvZ3kgaXMgQ29uZnVzaW5nLiAN CjMgIERpc2N1c3MgIEVSUiAgICBEQVRFIERUU1RBUlQgYW5kIFJFQ1VSUkVO Q0UtSUQNCjQgIE9wZW4gICAgIFR5cG8gICBPcmRlcmluZyBvZiBQYXJhbWV0 ZXJzIGluIEFCTkYNCjUgIERpc2N1c3MgIEVSUiAgICBNdWx0aXBsZSBBVFRF TkRFRSB3aXRoIFNhbWUgVmFsdWUNCjYgIE9wZW4gICAgIElDUiAgICBNaXhl ZCBEQVRFIGFuZCBEQVRFLVRJTUUNCjcgIE9wZW4gICAgIElDUiAgICBJbmNv bnNpc3RlbmNleSBpbiBVSUQgcHJvcA0KOCAgUmVqZWN0ZWQgSUNSICAgIFNw ZWNpZnkgRmlsZSBuYW1lIGluIEFUVEFDSD8NCjkgIE9wZW4gICAgIEVSUiAg ICBXZWVrbnVtYmVyIGluZGVwZW5kZW50IG9mIHN0YXJ0IG9mIHdlZWs/DQox MCBPcGVuICAgICBUeXBvICAgQ29uZmxpY3QgaW4gTXVsdGlwbGUgb2NjdXJy ZW5jZSBvZiBERVNDUklQVElPTg0KMTEgT3BlbiAgICAgVHlwbyAgIE5lZWQg Q1JMRiBpbiBUUklHR0VSIHNwZWMNCjEyIE9wZW4gICAgIFR5cG8gICBUeXBv IGluIDQuOC4xLjcNCjEzIE9wZW4gICAgIEVSUiAgICBQVUJMSVNIICYgTm8g T3JnYW5pemVyIGluIE5vbi1ncm91cCBzY2hlZHVsZWQNCgkJICAgbWVldGlu Z3MNCjE0IE9wZW4gICAgIFR5cG8gICBGaXggZXJyb3JzIGluIGV4YW1wbGVz DQoxNSBEaXNjdXNzICBJQ1IgICAgUmVzdHJpY3Rpb25zIG9uIFJFQ1VSIHJ1 bGVzDQoxNiBPcGVuICAgICBSZWplY3RlZCAgV2h5IGlzIFVOVElMIG9ubHkg VVRDPw0KMTcgT3BlbiAgICAgQ1IgICAgIENoYW5nZXMgdG8gUkVRVUVTVC1T VEFUVVMNCjE4IE9wZW4gICAgIENSICAgICBOZXcgVFJBTlNQIFZhbHVlcyBm b3IgQ0FQDQoxOSBPcGVuICAgICBDUiAgICAgTmV3IEdFT19CT1VORFMgcHJv cGVydHkNCjIwIE9wZW4gICAgIENSICAgICBBZGQgTmV3IENBUCBjb21wb25l bnRzIHRvIHNwZWMNCjIxIE9wZW4gICAgIFR5cG8gICA0LjIuMTggIFNlbnQg QnkgZXhhbXBsZTogdXNlID0gaW5zdGVhZCBvZiA6DQoyMiBPcGVuICAgICBJ Q1IgICAgIEFCTkYgZG9lc24ndCBjdXJyZW50bHkgYWxsb3cgcmVnaXN0ZXJl ZCBleHRlbnNpb25zDQoyMyBPcGVuICAgICBJQ1IgICAgRGlzYWxsb3cgUkVD VVJSRU5DRS1JRCBvZiBEQVRFIGZvciA+MSBvY2N1cmVuY2VzIHBlcg0KCQkg ICBkYXkNCjI0IE9wZW4gICAgIFR5cG8gICBQYWdlIDE0LCBzZWN0aW9uIDQu MSwgeC10b2tlbiB0byB4LW5hbWUNCjI1IE9wZW4gICAgIFR5cG8gICBQYWdl IDIxLCBzZWN0aW9uIDQuMi40LCB1c2VzIHRvIHVzZXJzDQoyNiBPcGVuICAg ICBUeXBvICAgUGFnZSAyMiwgc2VjdGlvbiA0LjIuNiwgdmFsdWVzIHRvIHZh bHVlDQoyNyBPcGVuICAgICBUeXBvICAgUGFnZSAyMiwgc2VjdGlvbiA0LjIu NiwgTVVTVCBlYWNoIGJlIHNwZWNpZmllZCB0bw0KCQkgICBNVVNUIGJlIHNw ZWNpZmllZA0KMjggT3BlbiAgICAgVHlwbyAgIFBhZ2UgMjIsIHNlY3Rpb24g NC4yLjYsIFRoZSBpbmRpdmlkdWFsIFVSSSB0byBUaGUNCgkJICAgVVJJDQoy OSBPcGVuICAgICBUeXBvICAgUGFnZSA0NSwgc2VjdGlvbiA0LjMuMTEsIEVT Q0FQRUQtQ0hBUiA9ICB0bw0KCQkgICBFU0NBUEVELUNIQVIgPSAoDQozMCBP cGVuICAgICBUeXBvICAgUGFnZSA0Niwgc2VjdGlvbiA0LjMuMTEsIC8gJXgz Qy01QiB0byAvICV4M0MtNUIgLw0KMzEgT3BlbiAgICAgVHlwbyAgIFBhZ2Ug NTIsIHNlY3Rpb24gNC42LCBmcmVlYnVzeWMgLyB0byBmcmVlYnVzeWMNCjMy IE9wZW4gICAgIFR5cG8gICBQYWdlIDg0LCBzZWN0aW9uIDQuOC4xLjcsIEYx MjMsIHRvIEYxMjNcLA0KMzMgT3BlbiAgICAgVHlwbyAgIFBhZ2UgODgsIHNl Y3Rpb24gNC44LjEuMTEsIHN0YXRwYXJhbV0gdG8gc3RhdHBhcmFtDQozNCBP cGVuICAgICBUeXBvICAgUGFnZSAxMTAsIHNlY3Rpb24gNC44LjQuNSwgY2Fu Y2VsZWQgdG8gY2FuY2VsbGVkIGZvcg0KCQkgICBjb25zaXN0ZW5jeQ0KMzUg T3BlbiAgICAgVHlwbyAgIFBhZ2UgMTEwLCBzZWN0aW9uIDQuOC40LjUsIFty ZWxwYXJhbV0gdG8gcmVscGFyYW0NCjM2IE9wZW4gICAgIFR5cG8gICBQYWdl IDExMCwgc2VjdGlvbiA0LjguNC41LCB4cGFybSB0byB4cGFyYW0NCjM3IE9w ZW4gICAgIFR5cG8gICBQYWdlIDEyOCwgc2VjdGlvbiA0LjguNi4zLCAvIHRy aWdhYnMpIHRvIC8gdHJpZ2FicykNCgkJICAgQ1JMRg0KMzggT3BlbiAgICAg VHlwbyAgIFBhZ2UgMTM4LCBzZWN0aW9uIDUsIHRleHQvY2FsZW5kYXIgdG8N CgkJICAgdGV4dC9jYWxlbmRhcjtNRVRIT0Q9eHl6O0NPTVBPTkVOVA0KCQkg ICA9VkVWRU5UDQozOSBPcGVuICAgICBUeXBvICAgUGFnZSAxMzgsIHNlY3Rp b24gNSwgVFJJR0dFUjoxOTk4MDQwM1QxMjAwMDAgdG8NCgkJICAgVFJJR0dF UjoxOTk4MDQwM1QxMjAwMDBaDQo0MCBPcGVuICAgICBUeXBvICAgUGFnZSAx NDMsIHNlY3Rpb24gNy4yLjQsIC4uaXMgYXBwb2ludGVkIHRvIHRoZS4uIHRv DQoJCSAgIC4uaXMgYXBwb2ludGVkIGJ5IHRoZS4uDQo0MSBPcGVuICAgICBU eXBvICAgQWRqdXN0IEFCTkYgdG8gYWNjb21tb2RhdGUgZXh0ZW5zaW9uDQo0 MiBPcGVuICAgICBUeXBvICAgVHlwb3MgaW4gZXhhbXBsZXMNCjQzIE9wZW4g ICAgIFR5cG8gICBSZWYgdG8gNC4xLjEwLjExIGluIHNlYyA0LjYuNSBzaG91 bGQgYmUgNC4zLjEyDQo0NCBPcGVuICAgICBJQ1IgICAgIFJlY3VycmVuY2Ug VU5USUwvUkRBVEUvRVhEQVRFIHByb3BlcnRpZXMgd2l0aCBEQVRFDQoJCSAg IHZhbHVlcyAgICANCg== ---1463809014-1069117017-976579310=:22782-- From owner-ietf-calendar@mail.imc.org Tue Dec 12 02:37:47 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA02242 for ; Tue, 12 Dec 2000 02:37:47 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id XAA21124 for ietf-calendar-bks; Mon, 11 Dec 2000 23:09:02 -0800 (PST) Received: from agony.busboom.org (24-25-200-53.san.rr.com [24.25.200.53]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA21113 for ; Mon, 11 Dec 2000 23:09:01 -0800 (PST) Received: from localhost (eric@localhost) by agony.busboom.org (8.9.3/8.9.3) with ESMTP id XAA16598 for ; Mon, 11 Dec 2000 23:11:14 -0800 X-Authentication-Warning: agony.busboom.org: eric owned process doing -bs Date: Mon, 11 Dec 2000 23:11:14 -0800 (PST) From: Eric Busboom X-Sender: eric@agony.busboom.org To: ietf-calendar@imc.org Subject: Recurrence Rules Issue Summary Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Here are the recorded issues with recurrence rules and some proposed text. eric. (1) In a YEARLY frequency with BYMONTH and/or BYWEEKNO set, does the BYDAY modifier apply to the year day, the month day, or the week day? (2) The BYYEARDAY part, for a given year, effectively specifies the month, day of month, and week number, so other BYXX rule parts for month, day of month and week number may conflict. (3) BYWEEKNO implies a month, conflicting with BYMONTH (4) MONTHLY recurrences (FREQ=MONTHLY) conflict with BYYEARDAY and BYWEEKNO. (5) WEEKLY recurrences (FREQ=WEEKLY) conflict with BYMONTHDAY and BYYEARDAY. (6) BYSETPOS is limited to 366 positive values or 366*2 positive and negative values in a sufficiently large set. A complete expansion for every second in every day of the year would result in much larger sets. ( Do we need BYSETPOS? ) (7) The algorithm to calculate the first week in the year may be awkward, since some people/countries may be used to other numbering schemes. Maybe there should be a choice of a few schemes for this. (8) What do you do with a WEEKLY recurrence if it has BYDAY=2TU ? Some proposed text, an addition to RFC2445, section 4.3.10. Numbers in parenthesis refer to the problems listed above. ---------------------------------------------------------------------- There are two types of BYxxx rules; date BYxxx rule parts that specify time periods equal to or longer than a day, and time BYxxx rule parts that specify the time periods less than a day. The day BYxxx rule parts are : BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY and BYDAY. The time BYxxx rule parts are BYHOUR, BYMINUTE, and BYSECOND. BYSETPOS is neither a date rule part nor time rule part. Not all date BYxxx rule parts can appear simultaneously in a single recurrence rule. Date BYxxx rule part restrictions are: [a] If the BYYEARDAY part appears in a rule , no other date rule part may appear. (2) [b] BYWEEKNO and BYMONTH rule parts may not both appear. (3) [ except when week covers two months?] Furthermore, not all date rule parts may be used with all recurrence intervals. [c] For MONTHLY recurrences neither BYYEARDAY nor BYWEEKNO may appear. (4) [d] For WEEKLY recurrences neither BYMONTHDAY nor BYYEARDAY may appear. (5) There are no restrictions regarding combinations of date rule parts and time rule parts. There are no restrictions with using any combination of time rule part. For FREQ=WEEKLY, BYDAY rule parts MUST have integer values of 1, or the integer value MUST be omitted. "FREQ=WEEKLY;BYDAY=TU" is valid, but "FREQ=WEEKLY;BYDAY=2TU" is not. (8) -------------------------------------------------------------------------- The text does not address (1), (6) and (7) From owner-ietf-calendar@mail.imc.org Tue Dec 12 12:00:44 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23643 for ; Tue, 12 Dec 2000 12:00:44 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA27894 for ietf-calendar-bks; Tue, 12 Dec 2000 08:37:40 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.73.83.tx.verio.net [207.137.73.83]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA27887 for ; Tue, 12 Dec 2000 08:37:38 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBCGibP25928 for ; Tue, 12 Dec 2000 11:44:37 -0500 Message-ID: <3A3655F4.F84A5B8B@ecal.com> Date: Tue, 12 Dec 2000 11:44:36 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Recurrence Rules Issue Summary References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Eric Busboom wrote: > Some proposed text, an addition to RFC2445, section 4.3.10. Numbers in > parenthesis refer to the problems listed above. The proposed text looks good; we might also want to consider recommending what to do if you get a noncompliant iCalendar that contains a conflict. You could just flag the error, of course. If you don't, though, it might be useful to have a rule of thumb like "if two specifiers conflict, then the one that refers to a larger unit of time takes precedence". So, for example, BYYEARDAY takes precedence over BYMONTH. This would mean that, if I send out a noncompliant iCalendar to N people, at least they'll all agree on what it means--there can still be confusion, but less than if each of them interprets it differently. -- /================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |===============================================| |eCal Corp. |"Lollygaggers will be shot on sight!" "I didn't| |francis@ecal.com|say that!" "I was paraphrasing." | \================================================================/ From owner-ietf-calendar@mail.imc.org Tue Dec 12 12:08:33 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25904 for ; Tue, 12 Dec 2000 12:08:33 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA28567 for ietf-calendar-bks; Tue, 12 Dec 2000 08:50:03 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.73.83.tx.verio.net [207.137.73.83]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA28563 for ; Tue, 12 Dec 2000 08:50:02 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBCGv1P25982 for ; Tue, 12 Dec 2000 11:57:01 -0500 Message-ID: <3A3658DA.7D50F022@ecal.com> Date: Tue, 12 Dec 2000 11:56:58 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: Photos from IETF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit My manager wanted me to make some sort of report to the team so they'd understand what I did at IETF. I figured pictures would help, so I brought my camera. Here's a couple of pictures of calsch people at lunch and dinner yesterday. I'll try to get time to label them so people can put names to faces. http://www.thibault.org/calsch/ietf49/ -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |Speak softly and carry an Illudium Q-32 | |francis@ecal.com|Explosive Space Disintegrator. | \==============================================================/ From owner-ietf-calendar@mail.imc.org Tue Dec 12 12:24:12 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29289 for ; Tue, 12 Dec 2000 12:24:12 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA29237 for ietf-calendar-bks; Tue, 12 Dec 2000 09:04:01 -0800 (PST) Received: from arista.iris.com (arista.iris.com [198.112.211.42]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA29233 for ; Tue, 12 Dec 2000 09:03:59 -0800 (PST) From: Bruce_Kahn@iris.com To: John Stracke Cc: ietf-calendar@imc.org Subject: Re: Recurrence Rules Issue Summary MIME-Version: 1.0 X-Mailer: Lotus Notes Build V60_12042000 December 04, 2000 Message-ID: Date: Tue, 12 Dec 2000 12:06:28 -0500 X-MIMETrack: Serialize by Router on Arista/Iris(Build V505_07112000 |July 11, 2000) at 12/12/2000 12:06:37 PM, Serialize complete at 12/12/2000 12:06:37 PM Content-Type: multipart/alternative; boundary="=_alternative 0063381E852569B3_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0063381E852569B3_= Content-Type: text/plain; charset="us-ascii" John proposed: >If you don't, though, it might be >useful to have a rule of thumb like "if two specifiers conflict, then the one >that refers to a larger unit of time takes precedence". So, for example, >BYYEARDAY takes precedence over BYMONTH. I agree that we should add some text to codify the proper behaviour in these cases. However I would recommend that we use the same order of evaluation that we described in the RFC. This is roughly what John suggested (we did it by time scale mostly) but its "more consistant" with how correct iCalendar is evaluated. Bruce =========================================================================== Bruce Kahn INet: Bruce_Kahn@iris.com Iris Associates Phone: 978.392.5335 Westford, MA, USA 01886 FAX: and nothing but the FAX... Standard disclaimers apply, even where prohibited by law... --=_alternative 0063381E852569B3_= Content-Type: text/html; charset="us-ascii"
John proposed:
>If you don't, though, it might be
>useful to have a rule of thumb like "if two specifiers conflict, then the one
>that refers to a larger unit of time takes precedence".  So, for example,
>BYYEARDAY takes precedence over BYMONTH.

I agree that we should add some text to codify the proper behaviour in these cases.  However I would recommend that we use the same order of evaluation that we described in the RFC.  This is roughly what John suggested (we did it by time scale mostly) but its "more consistant" with how correct iCalendar is evaluated.

Bruce
===========================================================================
Bruce Kahn                                INet: Bruce_Kahn@iris.com
Iris Associates                          Phone: 978.392.5335
Westford, MA, USA 01886                    FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law... --=_alternative 0063381E852569B3_=-- From owner-ietf-calendar@mail.imc.org Tue Dec 12 12:36:58 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA02059 for ; Tue, 12 Dec 2000 12:36:57 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA29428 for ietf-calendar-bks; Tue, 12 Dec 2000 09:14:17 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.73.83.tx.verio.net [207.137.73.83]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA29424 for ; Tue, 12 Dec 2000 09:14:16 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBCHLDP28315 for ; Tue, 12 Dec 2000 12:21:15 -0500 Message-ID: <3A365E87.3E2052D6@ecal.com> Date: Tue, 12 Dec 2000 12:21:12 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Recurrence Rules Issue Summary References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Bruce_Kahn@iris.com wrote: > John proposed: > >If you don't, though, it might be > >useful to have a rule of thumb like "if two specifiers > conflict, then the one > > I agree that we should add some text to codify the proper > behaviour in these cases. However I would recommend that we > use the same order of evaluation that we described in the RFC. > This is roughly what John suggested (we did it by time scale > mostly) but its "more consistant" with how correct iCalendar is > evaluated. OK, fine by me. -- /================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |===============================================| |eCal Corp. |Don't anthropomorphize computers. We don't like| |francis@ecal.com|it. | \================================================================/ From owner-ietf-calendar@mail.imc.org Tue Dec 12 15:08:22 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA03290 for ; Tue, 12 Dec 2000 15:08:21 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id LAA10765 for ietf-calendar-bks; Tue, 12 Dec 2000 11:42:57 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.73.186.tx.verio.net [207.137.73.186]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA10761 for ; Tue, 12 Dec 2000 11:42:55 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBCJntb11411 for ; Tue, 12 Dec 2000 14:49:55 -0500 Message-ID: <3A36787A.7ADFC72A@ecal.com> Date: Tue, 12 Dec 2000 14:11:55 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: Opposite of CRISP (humor) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit I'm reviewing the CAP draft, and it just occurred to me: hypothetically, someone could create a CAP server with no iTIP support--it would just do calendaring, not scheduling. Products without scheduling exist, of course, and it's conceivable that someone could want to see such a calendar with a CAP client. So what would such a subset be called? Well, it'd be the inverse of CRISP, so, of course, it'd have to be called SOGGY. :-) (Um...Scheduling Omitted, Good for Goats and Yaks? Goats and yaks don't need scheduling, after all.) -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |Campbell's has it wrong--it's "Never | |francis@ecal.com|underestimate the power of *chocolate*". | \==============================================================/ From owner-ietf-calendar@mail.imc.org Tue Dec 12 15:10:09 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA03498 for ; Tue, 12 Dec 2000 15:10:09 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id LAA10757 for ietf-calendar-bks; Tue, 12 Dec 2000 11:42:55 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.73.186.tx.verio.net [207.137.73.186]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA10753 for ; Tue, 12 Dec 2000 11:42:53 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBCJnqb11399 for ; Tue, 12 Dec 2000 14:49:52 -0500 Message-ID: <3A366A8C.7B7D28CA@ecal.com> Date: Tue, 12 Dec 2000 13:12:29 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: Proposal to make CAP able to be CRISP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Back in August, I proposed CRISP, a profile of CAP which plays the same role as the now-defunct iRIP. (See draft-stracke-calsch-crisp-01.txt.) A CRISP server is a CAP server which supports only iTIP operations. This means, among other things, that its capabilities include: * CAR=NONE * QUERYLEVEL=NONE ...neither of which is legal in the current CAP draft. I propose adding NONE to the list of legal values for CAR and QUERYLEVEL in section 7.1.5 of draft-ietf-calsch-cap-03.txt. Comments? -- /================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |===============================================| |eCal Corp. |Yes, sir, we've graphed the data. It's a smiley| |francis@ecal.com|face, sir. | \================================================================/ From owner-ietf-calendar@mail.imc.org Tue Dec 12 15:31:07 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06040 for ; Tue, 12 Dec 2000 15:31:06 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA12352 for ietf-calendar-bks; Tue, 12 Dec 2000 12:08:12 -0800 (PST) Received: from amadeus.spin.com.mx (root@amadeus.spin.com.mx [200.12.165.19]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA12346 for ; Tue, 12 Dec 2000 12:08:11 -0800 (PST) Received: from guanabana.helixcode.com (foobar@master18.spin.com.mx [200.13.80.141]) by amadeus.spin.com.mx (8.9.3/8.9.0) with ESMTP id OAA10155; Tue, 12 Dec 2000 14:16:01 -0600 (CST) Received: (from federico@localhost) by guanabana.helixcode.com (8.9.3/8.9.3) id OAA17328; Tue, 12 Dec 2000 14:18:55 -0600 Date: Tue, 12 Dec 2000 14:18:55 -0600 Message-Id: <200012122018.OAA17328@guanabana.helixcode.com> X-Authentication-Warning: guanabana.helixcode.com: federico set sender to federico@helixcode.com using -f From: Federico Mena Quintero X-Palindrome: Step on no pets. To: John Stracke Cc: ietf-calendar@imc.org Subject: Re: Recurrence Rules Issue Summary References: <3A3655F4.F84A5B8B@ecal.com> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: John Stracke writes: > The proposed text looks good; we might also want to consider recommending > what to do if you get a noncompliant iCalendar that contains a conflict. You > could just flag the error, of course. If you don't, though, it might be > useful to have a rule of thumb like "if two specifiers conflict, then the one > that refers to a larger unit of time takes precedence". So, for example, > BYYEARDAY takes precedence over BYMONTH. This would mean that, if I send out > a noncompliant iCalendar to N people, at least they'll all agree on what it > means--there can still be confusion, but less than if each of them interprets > it differently. Is it not just easier to mark it as an invalid component and ignore it, warning the user about it? It seems to me that trying to fix up broken components on the fly will lead to implementations that do different things in badly inconsistent ways. Federico From owner-ietf-calendar@mail.imc.org Tue Dec 12 16:39:06 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA14996 for ; Tue, 12 Dec 2000 16:39:06 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA15389 for ietf-calendar-bks; Tue, 12 Dec 2000 13:17:02 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.74.67.tx.verio.net [207.137.74.67]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA15385 for ; Tue, 12 Dec 2000 13:17:01 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBCLHlK11892 for ; Tue, 12 Dec 2000 16:20:28 -0500 Message-ID: <3A3695F8.40934B03@ecal.com> Date: Tue, 12 Dec 2000 16:17:44 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Recurrence Rules Issue Summary References: <3A3655F4.F84A5B8B@ecal.com> <200012122018.OAA17328@guanabana.helixcode.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Federico Mena Quintero wrote: > John Stracke writes: > > > The proposed text looks good; we might also want to consider recommending > > what to do if you get a noncompliant iCalendar that contains a conflict. > > Is it not just easier to mark it as an invalid component and ignore > it, warning the user about it? Usually. This is mostly for edge cases--for example, if the user is a robot, and can't talk the problem over with the sender. -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |I'm a zygote, he's a zygote, she's a zygote, | |francis@ecal.com|wouldn't you like to be a zygote, too? | \==============================================================/ From owner-ietf-calendar@mail.imc.org Tue Dec 12 20:09:15 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA21936 for ; Tue, 12 Dec 2000 20:09:14 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id QAA21634 for ietf-calendar-bks; Tue, 12 Dec 2000 16:34:51 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.72.172.tx.verio.net [207.137.72.172]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA21630 for ; Tue, 12 Dec 2000 16:34:49 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBD0fpE12964 for ; Tue, 12 Dec 2000 19:41:51 -0500 Message-ID: <3A36C123.4B5699AD@ecal.com> Date: Tue, 12 Dec 2000 19:21:56 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: Bunch of CAP comments Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit I just reviewed the CAP draft for the first time in a while, so I have a bunch of comments. I grouped all the typo-level stuff together at the end. "The hierarchical calendar feature is not a storage relationship of the calendars within the CS." -- perhaps "not necessarily"? Storage is, of course, an implementation issue, and an implementation might choose to use hierarchical storage for hierarchical calendars. "A CU's UPN MUST never be deliverable to a different person." -- this is not an appropriate MUST for CAP, since (a) it has nothing to do with CAP interoperability and (b) it's unenforceable anyway. "For Calendaring and Scheduling Systems that are integrated with a directory system, the CS MUST support the ability to configure which schema attribute stores the UPN. The CS MAY allow one or more attributes to be searched for the UPN." -- again, this strikes me as an odd requirement; I can't see how it's relevant to achieving interop. "CAP implementations MUST support anonymous authentication," -- admins may want to be able to turn this off. Given that, implementors may want to leave it out altogether, if none of their customers use it. "VCARs specified in a calendar or a sub-calendar override all inherited VCARs." -- does this mean that there is no attempt to merge them at all, so that, if a subcalendar specifies any VCAR, no inheritance occurs? " is the Calendar Store ID. It is the network address of the computer on which the CAP server is running." -- or hostname, right? " [...] is an arbitrary string of 7 bit ASCII characters." -- except that it can't contain any character which is not legal in a URI. cap://calendar.example.com/user1 ://calendar.example.com/user1 user1 All these are equivalent. Do we really want this level of flexibility? It's not like HTML, where there's a need for relative URLs so that documents can be moved around together. CAP is strictly an on-the-wire protocol, generated and consumed by software, not humans. The more options there are, the more opportunity there is to get things wrong. Once the STARTTLS command has been successfully executed from either the Connected or Authenticated state, it must not be executed again. If an AUTHENTICATE command is successful, the connection enters the Authenticated state and then immediately goes to the IDENTIFIED state. So, if the connection moves immediately from Authenticated to Identified, how can STARTTLS be used in the Authenticated state? Come to that, what *is* the Authenticated state if you leave it as soon as you enter it? When the server is unable to complete the command in the maximum latency time, it issues an appropriate reply code and waits for the CUA to tell it how to proceed. Does "wait" mean it suspends working on the request? Also, it strikes me that supporting these latency limits may turn out to be very difficult for some styles of implementation (e.g., one single-threaded process per connection); can we get a capability to let the CUA know that latency limits will be ignored? "When a timeout occurs, the server drops the connection to the CUA." -- perhaps there should be some way of telling the CUA that it's hit the idle timeout, so it can distinguish between a timeout and a server crash? (3) There is no ORDERBY. Sorting will take place in the order the columns are supplied in the command. (4) The CS MUST sort at least the first column. The CS MAY sort additional columns. What if the CUA doesn't need sorting on some of those columns? I don't want to waste CS computrons on sorting that won't help anybody. QUERY:SELECT UID,SUMMARY,DESCRIPTION FROM VEVENT WHERE VALARM.TRIGGER >= '20000101T030405Z' AND VALARM.TRIGGER <= '20001231T235959Z' This syntax looks like it would have trouble with events that have multiple VALARMs (permitted in iCalendar: see Section 4.5.1 of RFC-2445). I don't think it's a legal subset of SQL, either, since you're using VALARM.TRIGGER although you aren't selecting FROM VALARM. (I could be wrong about that, though; my SQL knowledge is somewhat narrow.) responseCode [sep transportDescr sep [applicationDescr]] CRLF "." CRLF I think you left out the ABNF for the body of the response. If CMDID is not supplied then the fist command that is still pending is aborted. (a) "first", not "fist" (b) If there was one command pending, and ABORT reached the server after that command was already completed, then the "the first command that is still pending" will be the ABORT itself. The ABORT will be aborted, and no response will be sent. This in itself is kind of a silly objection, but it does point up: (c) If there was more than one command pending, and the CUA wanted to cancel the earliest one, it can't safely use ABORT without a CMDID, because the earliest one might complete before the ABORT reaches the server, in which case it'll cancel the wrong one. For this reason, I believe that ABORT without a CMDID should be disallowed; its results are too unpredictable to be safe. The CUA may not issue the "AUTHENTICATE" command multiple times, even if the first attempt was aborted. If a CUA attempts to do this the CS must terminate the session. Does this mean that, if AUTHENTICATE is aborted, the session must be terminated immediately? S: BEGIN:VCALENDAR S: PRODID:-//ACME/CAPserver//EN S: VERSION:2.1 S: IDENTITY=bill@example.com S: CAPVERSION=1.0 S: ITIPVERSION=1.0 S: AUTH=KERBEROS_V4 S: AUTH=DIGEST_MD5 S: CAR=CAR-FULL-1 S: MINDATE=19700101T000000Z S: MAXDATE=20370201T000000Z S: END:VCALENDAR Um...those "FOO=bar" lines don't look like iCalendar to me. Should they be "FOO:bar", maybe? C: CALIDEXPAND cap://cal.example.com/calid14 S: 2.0 cap://cal.example.com/calid14 S: cap://cal.example.com/calid2 S: cap://cal.example.com/calid5 S: cap://cal.example.com/calid66 S: . The response doesn't seem to be properly terminated; 4.3 seems to say that there should be two more . sequences, on every response. C: CALIDEXPAND cap://cal.example.com/calid76 S: 2.0 cap://cal.example.com/calid76 S: cap://cal.example.com/calid3 S: cap://cal.example.com/calid12 S: cap://cal.example.com/calid21 S: cap://cal.example.com/calid33 S: 2.3 Expansion resulted in too much data S: . This is using a syntax which doesn't seem to meet 4.3: inserting an extra status code later in the response. It's not clear how the CUA is meant to recognize it as a status code rather than part of the arguments. BEGIN:VCOMMAND [VQUERY] OLD-VALUES NEW-VALUES END:VCOMMAND Why is OLD-VALUES needed? What if I want to change a bunch of events (selected by the VQUERY), but the OLD-VALUES are different for each one? [EDITORS NOTE: This section needs to be completed by adding the restriction tables for each of these iTIP methods. The basis for the text is to be taken from [iTIP].] Wouldn't it be better just to reference iTIP? 7.2.2.2. PUBLISH [...] This method is used to move a calendar within the CS's hierarchy of calendars. If the CU wishes to keep the I think you have a copy-and-paste error; this is the same text as MOVE. the list or elsewhere have not been addressed. The Method Reviewers decision to reject a proposal can be appealed by the proposer to the IESG, or the objections raised can be addressed by the proposer and the proposal resubmitted. [EDITORS NOTE: John Stracke to review any updates] I think this suffers the same bug as the iCalendar text: the Method Reviewer has the power to accept any proposal without possibility of appeal. Editorial nits: "In it's simplest form it looks like" -- "its", not "it's". "In this mo del, VSCHEDULE" -- "model". ">From RFC-2459, section 4.1.2.6 (Subject):" -- you sent this by email, didn't you? :-) Delete the ">". Also, I would indent the block quotation which follows; it's hard to tell where it ends. "The CS SHOULD not preserve UG expansions across operations." -- SHOULD NOT. The examples of user groups at the end of 2.4.3 appear again at the end of 2.4.5, where they make rather less sense. "The CUA may have issued the SENDATA command" -- left out a D in "SENDDATA". "This section describes CAPs selecting" -- left out the apostrophe in "CAP's". This query selects the entire contents of every booked VEVENT that has an instance less than or equal to July 31st, 2000 23:59:59 Z and greater than or equal to July 1st, 2000 00:00:00 Z BEGIN:VQUERY EXPAND:TRUE QUERY:SELECT * FROM VEVENT WHERE RECURRENCE-ID >= '20000801T000000Z' AND RECURRENCE-ID <= '20000831T235959Z' AND METHOD = 'CREATE' END:VQUERY Should that be "August" rather than "July"? "In the examples below, lines preceded with "S:" refer to the sender and lines preceded with "R:" refer to the receiver." -- in the actual examples, "S:" seems to mark lines from the server, while "C:" marks lines from the client. "5 TLS not supported" -- looks like that should be "6.5". -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |I will not buy this .signature, it is scratched.| |francis@ecal.com| | \=================================================================/ From owner-ietf-calendar@mail.imc.org Wed Dec 13 12:32:15 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17447 for ; Wed, 13 Dec 2000 12:32:14 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA05430 for ietf-calendar-bks; Wed, 13 Dec 2000 09:06:48 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.75.240.tx.verio.net [207.137.75.240]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA05425 for ; Wed, 13 Dec 2000 09:06:46 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBDHDq816091 for ; Wed, 13 Dec 2000 12:13:52 -0500 Message-ID: <3A37AE50.DA1F5DDD@ecal.com> Date: Wed, 13 Dec 2000 12:13:52 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: Re: Proposal to make CAP able to be CRISP References: <3A366A8C.7B7D28CA@ecal.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit John Stracke wrote: > I propose > adding NONE to the list of legal values for CAR and QUERYLEVEL in > section 7.1.5 of draft-ietf-calsch-cap-03.txt. For what it's worth, I just brought this up in the WG meeting, and nobody objected. (On the other hand, nobody said anything at all. :-) -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |"If there's anything The Flintstones have taught| |francis@ecal.com|us, it's that pelicans can be used to mix | | |cement." -- Homer Simpson | \=================================================================/ From owner-ietf-calendar@mail.imc.org Wed Dec 13 13:07:45 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA23345 for ; Wed, 13 Dec 2000 13:07:44 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA07020 for ietf-calendar-bks; Wed, 13 Dec 2000 09:48:18 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.73.164.tx.verio.net [207.137.73.164]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA07016 for ; Wed, 13 Dec 2000 09:48:17 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBDHtMU16326; Wed, 13 Dec 2000 12:55:22 -0500 Message-ID: <3A37B806.494DDB55@ecal.com> Date: Wed, 13 Dec 2000 12:55:18 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: Email Effects Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Somebody in the meeting just mentioned Email Effects, a drawing program that generates ASCII art. The URL is . Mac and Windows only (of course, Unix people don't need it; we can use pbmtoascii :-). -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |"If there's anything The Flintstones have taught| |francis@ecal.com|us, it's that pelicans can be used to mix | | |cement." -- Homer Simpson | \=================================================================/ From owner-ietf-calendar@mail.imc.org Wed Dec 13 16:38:47 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA26415 for ; Wed, 13 Dec 2000 16:38:46 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA21178 for ietf-calendar-bks; Wed, 13 Dec 2000 13:16:39 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.72.168.tx.verio.net [207.137.72.168]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA21174 for ; Wed, 13 Dec 2000 13:16:38 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBDLNgk16692 for ; Wed, 13 Dec 2000 16:23:42 -0500 Message-ID: <3A37E8D4.1404F024@ecal.com> Date: Wed, 13 Dec 2000 16:23:33 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: CAP point: implicit VCARs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit A point that came up over lunch that we need to resolve: in CAP, can the CUA query to get a list of the decreed VCARs? -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |"If there's anything The Flintstones have taught| |francis@ecal.com|us, it's that pelicans can be used to mix | | |cement." -- Homer Simpson | \=================================================================/ From owner-ietf-calendar@mail.imc.org Wed Dec 13 16:59:36 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA29193 for ; Wed, 13 Dec 2000 16:59:35 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA21608 for ietf-calendar-bks; Wed, 13 Dec 2000 13:36:17 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.75.181.tx.verio.net [207.137.75.181]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA21604 for ; Wed, 13 Dec 2000 13:36:16 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBDLhIF17035 for ; Wed, 13 Dec 2000 16:43:18 -0500 Message-ID: <3A37ED71.52C0B301@ecal.com> Date: Wed, 13 Dec 2000 16:43:13 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: calsch WG Subject: Re: Photos from IETF References: <3A3658DA.7D50F022@ecal.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit John Stracke wrote: > Here's a couple of pictures of > calsch people at lunch and dinner yesterday. There's now one from the actual meeting, too. > http://www.thibault.org/calsch/ietf49/ -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |"If there's anything The Flintstones have taught| |francis@ecal.com|us, it's that pelicans can be used to mix | | |cement." -- Homer Simpson | \=================================================================/ From owner-ietf-calendar@mail.imc.org Thu Dec 14 03:29:06 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA26091 for ; Thu, 14 Dec 2000 03:29:05 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id AAA25292 for ietf-calendar-bks; Thu, 14 Dec 2000 00:05:00 -0800 (PST) Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id AAA25288 for ; Thu, 14 Dec 2000 00:04:58 -0800 (PST) From: Frank.Dawson@nokia.com Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86]) by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id eBE88E609866 for ; Thu, 14 Dec 2000 02:08:24 -0600 (CST) Received: from daebh01nok.americas.nokia.com (unverified) by davir03nok.americas.nokia.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Thu, 14 Dec 2000 02:07:32 -0600 Received: by daebh01nok with Internet Mail Service (5.5.2652.78) id ; Thu, 14 Dec 2000 02:03:00 -0600 Message-ID: <30F2DED23724D311902D0008C7EABAFB0301E0D3@daeis06nok> To: francis@ecal.com, ietf-calendar@imc.org Subject: RE: Photos from IETF Date: Thu, 14 Dec 2000 02:01:36 -0600 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: John: Great photos. By all the "smiles" I gather that you all had a very productive meeting. My regrets on being at the WAP Forum meeting instead! All my best to the WG members. I hope the next IETF meeting isn't scheduled against the WAP Forum again :-( -- Frank From owner-ietf-calendar@mail.imc.org Thu Dec 14 12:32:53 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04999 for ; Thu, 14 Dec 2000 12:32:53 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA01793 for ietf-calendar-bks; Thu, 14 Dec 2000 09:13:21 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.70.17.tx.verio.net [207.137.70.17]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA01789 for ; Thu, 14 Dec 2000 09:13:19 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBEHKS219217 for ; Thu, 14 Dec 2000 12:20:29 -0500 Message-ID: <3A390154.3DD5E521@ecal.com> Date: Thu, 14 Dec 2000 12:20:21 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Photos from IETF References: <30F2DED23724D311902D0008C7EABAFB0301E0D3@daeis06nok> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Frank.Dawson@nokia.com wrote: > Great photos. By all the "smiles" I gather that you all had a very > productive meeting. Yeah, actually, it went well. > All my best to the WG members. I hope the next IETF meeting isn't scheduled > against the WAP Forum again :-( Given the reception the WAP speaker got in Adelaide, I can just imagine how the IETF membership would react to a proposal that the IETF schedule around WAP meetings. ;-) (Yeah, that's an extreme way of putting it--the two groups could just cooperate--but you *know* that's how some people would insist on interpreting it.) -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |For the life of me, I've never understood why | |francis@ecal.com|people dismiss the importance of "semantics" in | | |communication. After all, if semantics had no | | |purpleness, you'd slitheringly go bold at by-sit| | |it I'm climbing. -- Tangwystyl | \=================================================================/ From owner-ietf-calendar@mail.imc.org Thu Dec 14 14:00:09 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA16647 for ; Thu, 14 Dec 2000 14:00:09 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA07051 for ietf-calendar-bks; Thu, 14 Dec 2000 10:39:53 -0800 (PST) Received: from elysium.uwa.edu.au (root@elysium.uwa.edu.au [130.95.128.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA07038 for ; Thu, 14 Dec 2000 10:39:36 -0800 (PST) Received: from tartarus.uwa.edu.au (mtearle@tartarus.uwa.edu.au [130.95.128.3]) by elysium.uwa.edu.au (8.11.1/8.10.2) with ESMTP id eBEIgHi26493 for ; Fri, 15 Dec 2000 02:42:18 +0800 (WST) Date: Fri, 15 Dec 2000 01:43:27 +0800 (WST) From: Mark Tearle X-Sender: mtearle@tartarus.uwa.edu.au To: ietf-calendar@ietf.org Subject: JetSpeed - Java implementation of RFC2445 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all Whilst randomly web surfing tonight came upon Jetspeed, I don't think I've heard it mentioned here before but they appear to have implemented some java classes for RFC2445 http://java.apache.org/jetspeed Yours Mark -- Mark Tearle - mark@tearle.com "You howl and listen Listen and wait for the Echoes of angels who won't return" From owner-ietf-calendar@mail.imc.org Thu Dec 14 15:26:41 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06686 for ; Thu, 14 Dec 2000 15:26:40 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA11994 for ietf-calendar-bks; Thu, 14 Dec 2000 12:09:11 -0800 (PST) Received: from mail12.svr.pol.co.uk (mail12.svr.pol.co.uk [195.92.193.215]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA11990 for ; Thu, 14 Dec 2000 12:09:09 -0800 (PST) Received: from modem-217.flagfin-angel.dialup.pol.co.uk ([62.137.12.217] helo=helixcode.com) by mail12.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 146ejM-0002wD-00 for ietf-calendar@imc.org; Thu, 14 Dec 2000 20:11:56 +0000 Message-ID: <3A39295B.AA1BF085@helixcode.com> Date: Thu, 14 Dec 2000 20:11:07 +0000 From: Damon Chaplin X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: converting Olson timezone database to VTIMEZONEs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Hi, Has anyone converted the Olson timezone database to VTIMEZONE format? I'm thinking of having a go, but don't want to repeat work already done. Damon From owner-ietf-calendar@mail.imc.org Thu Dec 14 18:07:32 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA07418 for ; Thu, 14 Dec 2000 18:07:32 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id OAA19234 for ietf-calendar-bks; Thu, 14 Dec 2000 14:54:10 -0800 (PST) Received: from imb.uq.edu.au (mail.imb.uq.edu.au [130.102.118.20]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id OAA19230 for ; Thu, 14 Dec 2000 14:54:07 -0800 (PST) Received: from [130.102.4.80] ([130.102.4.80] verified) by imb.uq.edu.au (CommuniGate Pro SMTP 3.3) with SMTP id 391549 for ietf-calendar@imc.org; Fri, 15 Dec 2000 09:00:38 +1000 X-Sender: Vthomas@pop3.vthrc.uq.edu.au Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 15 Dec 2000 08:56:52 +1000 To: ietf-calendar@imc.org From: D.Thomas@imb.uq.edu.au (Danny Thomas) Subject: seeking iCalendar resources, including client/server list Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I know requests to this list are discouraged, but I can't seem to find a good source for iCalendar material, eg a list of clients as is available for vCalendar - searching the archive of this list as a 14M text file is rather daunting. I think my main question is fair enough - is there a good resource page for iCalendar, eg with an faq describing differences to vCalendar, along with a list of known servers & clients. Maybe my search attempts have missed the obvious, but I would be expecting something by now - the initial rfc has been out for two years. Somebody might care to offer some advice & suggestions for our needs we're a research institute of around 350 people, mainly Mac but with some Windows & SGI/Unix users, so we're looking for a cross-platform personal, group & resource calendaring/scheduling system. In the medium term, we expect to migrate most Macs to MacOS X which amongst other things will offer a much better java implementation (so says Apple) A web-solution would work for most of our users, but we also require 1) the calendar should be available off-line so a travelling person can see their dairy when not net-connected, and can also makes changes which get synced to the server when they go back on-line. 2) While it's not an immediate issue, syncing with PDA's will also be important. Maybe the PDA's are getting smarter and can directly sync with the iCalendar server? We are aware of MeetingMaker, but the licensing is around US$100 for each calendar in the system. The jetspeed apache project has recently produced an iCalendar server (http://java.apache.org/jetspeed/site/iCalendar.html), which we could run, but we probably need (java?) clients to address points (1) & (2). We'd be grateful for any advice cheers, Danny Thomas From owner-ietf-calendar@mail.imc.org Thu Dec 14 18:47:57 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19727 for ; Thu, 14 Dec 2000 18:47:57 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id PAA20262 for ietf-calendar-bks; Thu, 14 Dec 2000 15:33:05 -0800 (PST) Received: from localhost.localdomain (ietf.207.137.72.59.tx.verio.net [207.137.72.59]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA20258 for ; Thu, 14 Dec 2000 15:33:04 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eBENeIO19609 for ; Thu, 14 Dec 2000 18:40:18 -0500 Message-ID: <3A395A62.EF6720DB@ecal.com> Date: Thu, 14 Dec 2000 18:40:18 -0500 From: John Stracke X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en, de, es MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: seeking iCalendar resources, including client/server list References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Danny Thomas wrote: > I know requests to this list are discouraged, but I can't seem to find a > good source for iCalendar material, eg a list of clients as is available Pat & Bob said at the meeting that they would make such a list available on (hosted by MIT), once that site is active (Bob says "within 3 weeks"). (I would just wait for Pat or Bob to answer, but I think they're both in the air today.) -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |World domination should never be left to chance.| |francis@ecal.com| | \=================================================================/ From owner-ietf-calendar@mail.imc.org Thu Dec 14 19:13:41 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27766 for ; Thu, 14 Dec 2000 19:13:41 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id PAA20991 for ietf-calendar-bks; Thu, 14 Dec 2000 15:58:00 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id PAA20984 for ; Thu, 14 Dec 2000 15:57:58 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA28731; Thu, 14 Dec 00 19:02:17 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id TAA28615; Thu, 14 Dec 2000 19:00:41 -0500 (EST) Received: from [207.137.73.25] (ietf.207.137.73.25.tx.verio.net [207.137.73.25]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id TAA25174; Thu, 14 Dec 2000 19:00:27 -0500 (EST) Mime-Version: 1.0 Message-Id: In-Reply-To: <3A395A62.EF6720DB@ecal.com> References: <3A395A62.EF6720DB@ecal.com> Date: Thu, 14 Dec 2000 19:00:17 -0500 To: John Stracke From: Bob Mahoney Subject: Re: seeking iCalendar resources, including client/server list Cc: ietf-calendar@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I'm still safely on the ground... :-) We don't yet have this registered (today, I hope), so please don't publicize this address. An announcement will go to the list when it's ready, and I still stand by my 30week guess. That said, we do intend to answer the sort of questions Danny posed with these pages. -Bob At 6:40 PM -0500 12/14/00, John Stracke wrote: >Danny Thomas wrote: > >> I know requests to this list are discouraged, but I can't seem to find a >> good source for iCalendar material, eg a list of clients as is available > >Pat & Bob said at the meeting that they would make such a list available on > (hosted by MIT), once that site is active (Bob says >"within 3 weeks"). > >(I would just wait for Pat or Bob to answer, but I think they're both in the >air today.) > >-- >/=================================================================\ >|John Stracke | http://www.ecal.com |My opinions are my own. | >|Chief Scientist |================================================| >|eCal Corp. |World domination should never be left to chance.| >|francis@ecal.com| | >\=================================================================/ From owner-ietf-calendar@mail.imc.org Thu Dec 14 19:26:31 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA01109 for ; Thu, 14 Dec 2000 19:26:30 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id QAA21317 for ietf-calendar-bks; Thu, 14 Dec 2000 16:14:31 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id QAA21312 for ; Thu, 14 Dec 2000 16:14:29 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA21803; Thu, 14 Dec 00 19:16:24 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id TAA00568 for ; Thu, 14 Dec 2000 19:13:06 -0500 (EST) Received: from [207.137.73.25] (ietf.207.137.73.25.tx.verio.net [207.137.73.25]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id TAA27102 for ; Thu, 14 Dec 2000 19:13:06 -0500 (EST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: <3A395A62.EF6720DB@ecal.com> Date: Thu, 14 Dec 2000 19:12:53 -0500 To: ietf-calendar@imc.org From: Bob Mahoney Subject: Re: seeking iCalendar resources, including client/server list Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 7:00 PM -0500 12/14/00, Bob Mahoney wrote: > >I still stand by my 30week guess. Ok, before anyone asks, that's supposed to read "3-week"... :-) -Bob From owner-ietf-calendar@mail.imc.org Thu Dec 14 20:32:26 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20491 for ; Thu, 14 Dec 2000 20:32:25 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id RAA22689 for ietf-calendar-bks; Thu, 14 Dec 2000 17:15:03 -0800 (PST) Received: from toiir01adm.transitions.com ([195.7.37.110]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id RAA22685 for ; Thu, 14 Dec 2000 17:15:00 -0800 (PST) From: 67Z29IMJa@mail.i-net.co.id Received: FROM Zw2XlDB1C BY toiir01adm.transitions.com ; Fri Dec 15 01:18:25 2000 0000 DATE: 14 Dec 00 8:12:42 PM Message-ID: SUBJECT: web hosting Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Thu Dec 14 21:01:02 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA00247 for ; Thu, 14 Dec 2000 21:01:01 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id RAA23247 for ietf-calendar-bks; Thu, 14 Dec 2000 17:44:42 -0800 (PST) Received: from home.se (smtphost3.home.se [195.66.35.199]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA23243 for ; Thu, 14 Dec 2000 17:44:40 -0800 (PST) Received: from metaacer [207.137.75.156] by home.se with Novonyx SMTP Server $Revision: 2.71 $; Fri, 15 Dec 2000 02:46:04 +0100 (ECTD) From: "Greg FitzPatrick" To: , , Subject: SV: Photos from IETF Date: Fri, 15 Dec 2000 02:47:21 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <30F2DED23724D311902D0008C7EABAFB0301E0D3@daeis06nok> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: X-MIME-Autoconverted: from 8bit to quoted-printable by ns.secondary.com id RAA23247 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA00247 Frank Missed seeing you here. Pat asked me to get the (an) XML DTD/Schema resubmitted. Of course she means the one2one, totally flat, no thrills version. I was thinking of checking out your work (which I have bragged that Niclas and I found 63 parse errors in) and check it over and then send it in. So I want to get your reaction to that and so forth.... or if you want to do that yourself??? Greg -----Ursprungligt meddelande----- Från: owner-ietf-calendar@mail.imc.org [mailto:owner-ietf-calendar@mail.imc.org]För Frank.Dawson@nokia.com Skickat: den 14 december 2000 09:02 Till: francis@ecal.com; ietf-calendar@imc.org Ämne: RE: Photos from IETF Prioritet: Hög John: Great photos. By all the "smiles" I gather that you all had a very productive meeting. My regrets on being at the WAP Forum meeting instead! All my best to the WG members. I hope the next IETF meeting isn't scheduled against the WAP Forum again :-( -- Frank From owner-ietf-calendar@mail.imc.org Fri Dec 15 23:17:19 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA02957 for ; Fri, 15 Dec 2000 23:17:19 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id TAA24605 for ietf-calendar-bks; Fri, 15 Dec 2000 19:52:27 -0800 (PST) Received: from server1.egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA24597 for ; Fri, 15 Dec 2000 19:52:15 -0800 (PST) From: pregen@egenconsulting.com To: Bob Mahoney Cc: John Stracke , ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: seeking iCalendar resources, including client/server list X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Sat, 16 Dec 2000 03:55:07 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 12/15/2000 10:55:20 PM, Serialize complete at 12/15/2000 10:55:20 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 007E100B802569B6_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 007E100B802569B6_= Content-Type: text/plain; charset="us-ascii" Bob Mahoney Sent by: owner-ietf-calendar@mail.imc.org 12/15/00 12:00 AM To: John Stracke cc: ietf-calendar@imc.org Subject: Re: seeking iCalendar resources, including client/server list Bob said: We don't yet have this registered (today, I hope), so please don't publicize this address. An announcement will go to the list when it's ready, and I still stand by my 30week guess. >> I don't think it will take that long (30 weeks). Several of the pages are ready to go. I can host them on my site, but MIT has lots more bandwidth and has generously offered to host this site. Danny, it will be exactly what you are looking for. It's information I have gleaned as well as input from others interested in Calendaring and Scheduling (and not just on the Net). After the pages are up and the site is posted, I would appreciate anyone sending products that are missing. Use the link below to look at the pages that are "waiting" on the MIT website. Thought you might be interested so we can "wet your appetite." http://www.egenconsulting.com/ietf/website/calsch.html -Bob At 6:40 PM -0500 12/14/00, John Stracke wrote: >Danny Thomas wrote: > >> I know requests to this list are discouraged, but I can't seem to find a >> good source for iCalendar material, eg a list of clients as is available > >Pat & Bob said at the meeting that they would make such a list available on > (hosted by MIT), once that site is active (Bob says >"within 3 weeks"). > >(I would just wait for Pat or Bob to answer, but I think they're both in the >air today.) > >-- >/=================================================================\ >|John Stracke | http://www.ecal.com |My opinions are my own. | >|Chief Scientist |================================================| >|eCal Corp. |World domination should never be left to chance.| >|francis@ecal.com| | >\=================================================================/ --=_alternative 007E100B802569B6_= Content-Type: text/html; charset="us-ascii"


Bob Mahoney <bobmah@mit.edu>
Sent by: owner-ietf-calendar@mail.imc.org

12/15/00 12:00 AM

       
        To:        John Stracke <francis@ecal.com>
        cc:        ietf-calendar@imc.org
        Subject:        Re: seeking iCalendar resources, including client/server list



Bob said:
We don't yet have this registered (today, I hope), so please don't
publicize this address.  An announcement will go to the list when
it's ready, and I still stand by my 30week guess.
>> I don't think it will take that long (30 weeks).  Several of the pages are ready to go.  I can host them on my site, but MIT has lots more bandwidth and has generously offered to host this site.  Danny, it will be exactly what you are looking for.  It's information I have gleaned as well as input from others interested in Calendaring and Scheduling (and not just on the Net).  After the pages are up and the site is posted, I would appreciate anyone sending products that are missing.  

Use the link below to look at the pages that are "waiting" on the MIT website.  Thought you might be interested so we can "wet your appetite."

http://www.egenconsulting.com/ietf/website/calsch.html


-Bob

At 6:40 PM -0500 12/14/00, John Stracke wrote:
>Danny Thomas wrote:
>
>>  I know requests to this list are discouraged, but I can't seem to find a
>>  good source for iCalendar material, eg a list of clients as is available
>
>Pat & Bob said at the meeting that they would make such a list available on
><http://www.calsched.org> (hosted by MIT), once that site is active (Bob says
>"within 3 weeks").
>
>(I would just wait for Pat or Bob to answer, but I think they're both in the
>air today.)
>
>--
>/=================================================================\
>|John Stracke    | http://www.ecal.com |My opinions are my own.   |
>|Chief Scientist |================================================|
>|eCal Corp.      |World domination should never be left to chance.|
>|francis@ecal.com|                                                |
>\=================================================================/

--=_alternative 007E100B802569B6_=-- From owner-ietf-calendar@mail.imc.org Sat Dec 16 23:11:03 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA12601 for ; Sat, 16 Dec 2000 23:11:03 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id TAA21048 for ietf-calendar-bks; Sat, 16 Dec 2000 19:54:24 -0800 (PST) Received: from exchange.animenation.org ([209.109.142.132]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA21042 for ; Sat, 16 Dec 2000 19:54:17 -0800 (PST) From: adhausdhuas@server1.fata.ru To: Date: Sat, 16 Dec 2000 19:16:20 Message-Id: <404.249469.747046@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Sun Dec 17 00:39:32 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA14057 for ; Sun, 17 Dec 2000 00:39:31 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA22351 for ietf-calendar-bks; Sat, 16 Dec 2000 20:46:46 -0800 (PST) Received: from arista.iris.com (arista.iris.com [198.112.211.42]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA22347 for ; Sat, 16 Dec 2000 20:46:44 -0800 (PST) From: Bruce_Kahn@iris.com To: Damon Chaplin Cc: "ietf-calendar@imc.org" Subject: Re: converting Olson timezone database to VTIMEZONEs MIME-Version: 1.0 X-Mailer: Lotus Notes Build V60_12042000 December 04, 2000 Message-ID: Date: Sat, 16 Dec 2000 23:49:32 -0500 X-MIMETrack: Serialize by Router on Arista/Iris(Build V505_07112000 |July 11, 2000) at 12/16/2000 11:49:45 PM, Serialize complete at 12/16/2000 11:49:46 PM, Serialize by Router on Arista/Iris(Build V505_07112000 |July 11, 2000) at 12/16/2000 11:49:46 PM Content-Type: multipart/alternative; boundary="=_alternative 001EF925852569B8_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 001EF925852569B8_= Content-Type: text/plain; charset="us-ascii" Damon asked: >Has anyone converted the Olson timezone database to VTIMEZONE format? Doug Royer worked on a LEX/YACC convertor program a while back. I dont think I got a copy to help with or not so Id recommend you look around ftp://ftp.royer.com/ and see if you can find it still or not. Bruce =========================================================================== Bruce Kahn INet: Bruce_Kahn@iris.com Iris Associates Phone: 978.392.5335 Westford, MA, USA 01886 FAX: and nothing but the FAX... Standard disclaimers apply, even where prohibited by law... --=_alternative 001EF925852569B8_= Content-Type: text/html; charset="us-ascii"
Damon asked:
>Has anyone converted the Olson timezone database to VTIMEZONE format?
Doug Royer worked on a LEX/YACC convertor program a while back.  I dont think I got a copy to help with or not so Id recommend you look around ftp://ftp.royer.com/ and see if you can find it still or not.

Bruce
===========================================================================
Bruce Kahn                                INet: Bruce_Kahn@iris.com
Iris Associates                          Phone: 978.392.5335
Westford, MA, USA 01886                    FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law... --=_alternative 001EF925852569B8_=-- From owner-ietf-calendar@mail.imc.org Sun Dec 17 03:18:56 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA06647 for ; Sun, 17 Dec 2000 03:18:56 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA08737 for ietf-calendar-bks; Sat, 16 Dec 2000 23:57:17 -0800 (PST) Received: from royer.com (royer.com [207.177.146.80]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA08728 for ; Sat, 16 Dec 2000 23:57:15 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA07021 for ietf-calendar@imc.org; Sun, 17 Dec 2000 00:00:03 -0800 (PST) Date: Sun, 17 Dec 2000 00:00:03 -0800 (PST) From: Doug Royer Message-Id: <200012170800.AAA07021@royer.com> X-Authentication-Warning: royer.com: doug set sender to Doug@Royer.Com using -r To: ietf-calendar@imc.org Subject: CALSCH Action Items Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a list of action items for the CALSCH Working Group. This list will be sent out once a week and updated as often as practical (That means if I am not available it may take an extra week or two before you see your changes). Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM . There are three parts to this action list: (W) Working group action items. (C) CAP editor action items. (I) iCalendar action items (Frank Dawson) Each action item will be assigned a unique ID that will aid in tracking the items. ------------------------------------------------------------------------------ Working Group Action Items Where Resolution is one of: U - undecided. Y - Chair determined consensus is in favor of the proposal. N - Chair determined consensus is NOT in favor of the proposal. D - Dropped. Chair has decided that it may never reach consensus. The following are a list of proposals and their status in the WG: WG Action Item Resolution -------------- ---------- W-1 CAP Use HTTP as transport N W-2 CAP If all booked and scheduled Y appointments are in same table W-3 CAP Use SASL as authentication method Y W-4 Add UID and COUNTER to VFREEBUSY N W-5 CAP Should CAPABILITY reply be sent N as result of successful AUTHENTICATE and IDENTITY W-6 Do we need to handle 'unscheduled event' as described by the SKI project? N (In CAP - 'N', SKI to be a seperate project/draft as it will effect RFC2445,6,7) W-7 CAP Auto-logout Timer issues Do we need one? Y How long? Can the server decide not to do this? Y W-8 CAP Bounded Latency Issues D W-9 CAP MOVE method. Issues with VCARs. Y [see note in CAP 7.2.1.5] W-10 CAP Text mandatory in all response N codes W-11 CAP Text optional in response codes Y (some response codes may have mandatory data that follows) W-12 CAP Should parts of response code be Y separated by ';' W-13 CAP Store Schema Y W-14 CAP VEVENT Schema Y W-15 CAP VTODO Schema Y W-16 CAP VJOURNAL Schema Y W-17 CAP VCAR Schema Y W-18 CAP UPN definition, including anonymous Y user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and Y static and how groups are used in VCARs. Policy definitions, in a VCAR format. W-20 Associating UPN values with CREATED N and LAST-MODIFIED properties. W-21 CAP Get/Set calendar user properties N W-22 VTIMEZONE and IANA Y in process W-23 CAP Calendar property to allow/disallow N overlapped booking OPAQUE entries? W-24 CAP Calendar CHARSET property issues Y W-25 Remove MUST from UID in 4.8.4.7 Y W-26 Write/Submit information draft/rfc Y W-27 How a query can specify if the recurrence Y rules are to be expanded by the CS. W-28 Cal-Props - PATH N (CAP-00 - 12.2) Will there need to be one? N Optional? N W-29 Import/Export Y - sync only W-30 Transport protocol name (transport vs Y application layer) W-31 NOOP command? Y W-32 NOOP advisory only? Y W-33 Should DISCONNECT be called QUIT? U W-34 Format following error codes. Are Y they well defined? If not they need to be machine determinable. W-35 Move DNS and SLP to seperate draft? Y ------------------------------------------------------------------------------ The following are a list of action items for the draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex Y text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug D C-4 VCAR examples Doug? Y C-5 PUBLISH text Y C-6 REQUEST text Y C-7 REPLY text Y C-8 ADD text Y C-9 CANCEL text Y C-10 REFRESH text Y C-11 COUNTER text Y C-12 DECLINECOUNTER Text Y C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS Y and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property Y C-16 (2.11) Query Schema Y C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Y Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS D Format? Text needs to be written. C-20 (13.) Security Considerations Y See editors note - more text. C-21 Resubmit REQUIREMENTS draft. Y C-22 Document MAXSIZE and MAXRESULT N C-23 Document METHOD is stored in CS database N Only one 'CREATE' per UID. Multple non-CREATE per UID. C-24 Fix the RESPONSE's to be consistant. N and multiple components, one for each TARGET. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: (iCal, iTIP, iMIP) Draft Action Item Who Done (Y/N) ----------------- --- ---------- I-1 MIME alternate/related Frank ? MUST be supported. I-2 Remove ordering of properties and Frank ? parameters in draft. I-3 S/MIME and RFC1847. U [CAP] 2.2.3 I-4 Add ALARMID to VALARM! I-5 iTIP error. VJOURNAL should be 0 (not 0+) for CANCEL ------------------------------------------------------------------------------ Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM -------------------------------------------------------------------------- Work: Doug.Royer@Software.com Home 801 Woodside Rd #14-244 530 E. Montecito St. Office: Redwood City, CA 94061 Santa Barbara, CA 93103 805-957-1790 x541 Personal Email: Doug@Royer.com Tuesday discussion: DONE Section 2.4.3 - editor note: Change with new paragraph; Groups may be in a directory with its own ACL model and CAP should use the directory service to expand a UPN subject to the directory service access control model for the authenticated entity. DONE Section 2.4.4.1 - editor note: Your access is a union of all your grants minus a union of all your denies. (We still need to discuss ordering - allow or not. We may not want to fool with it). DONE Section 2.4.4.2 - editor note: We need an example (Steve/Doug) - Paul needs to read this note an example). Section 2.6 CALID - need to define that relative CALID must be consistent with the scheme specific part of URI as defined in RFC xxx. - Steve Section 2.9 Will be discussed earlier in draft - remove altogether. Section 7.1.3 Need to get IANA registration Section 7.1.3 Delete editors note about blank on examples. Need to add an unsuccessful login. Delete all lines except the line that starts with "The following...." - (* Who will do this example) DONE Section 7.2.1.1.1 Get rid of whole paragraph (pargraph above). If you want to generate unique relative CALids, use the GENERATE UID command and use the result as the relative CALid. (we need to make sure that the results are characters that are compatible with our definition of calids) Section 7.2.1.3. The result needs to be consistent with CALID character rules (i.e. no spaces). The example needs one more line with a dot. Steve will do this. DONE Section 7.2.1.5 This issue goes away because we are not doing heirarchial. Remove editors note Section 7.2.1.7 Add an example of a partial result - we want to get something that matches some things, and on the ones you don't have access, you don't have rights to some of the components. George will write up something. Section 7.2.2 Need restriction tables. Some are CAP - for the rest of them use iTIP tables (Steve/Doug) we all need to review the text DONE Section 7.2.3.2 Pull editors note - fix applied Section 8.0 Response codes. Need to make sure response codes in all drafts - iCal, iMip and iTip and examples. Error numbers need to be the same. Put text about error codes in comments below the examples (so that people don't look at them as being required in their text). Pat will look at the codes. Section 11.0 DTN, DTSTAMP, etc are implementations that may need to be considered. Restrictions tables may resolve these issues. Section 12.0 Leave as is until we get people to agree. On version shipped after last call, this is what we are going to enhance this section. It does not make sense to do this until working group last call. Updates to iCalendar need to be written and will not be submitted to IANA until last call to WG. Doug Section 13.0 This section is not ready for prime time. Need Paul Hill. Need an editors note. Section 14.0 Needs to be reformatted - Doug will make sure it is consistent. George will do 14 DONE Section 15.1.1. Steve - additions or changes to the CAP schema (replaces Define the Entity). Word entity needs to be removed and replaced throughout the document). Section 15.1.4 Submit entity for approval - John submitted to list. Need to find. Get John's text and add back into CAP draft. John submitted as a separate draft document. Use the MIME appeal verbage with John's additional text. Point WG at John's draft and say it should be included in the draft. We need to also submit to April Marine as well. DONE Section 16.0 Remove reference to vCard - - - - - - Assignment list: Section 2.4.4.2 - VCAR example (Steve/Doug) Sectoin 2.6 - Steve will research Section 7.1.3 - IANA registration (Pat) Section 7.1.3 - example of unsuccessful login (Who) Section 7.2.1.1. - look at Calid characters (Doug) Section 7.2.1.3 - example line (Steve) Section 7.2.1.7 - George will write some verbage and we need to add an example of partial results (Steve/Doug) Section 7.2.2. - Restriction tables (Steve/Doug) Section 8.0 - look at consistency of Response code in all drafts (Pat) Section 12.0 - needs work. Check for consistency - Doug Section 13.0 - Paul Hill Section 14.0 - George Section 15.1.1 - replace text (Pat) Section 15.1.4 - add John's text to doc and put on list to look at proposal. - - - - - Work on Restriction table Editor note: Remove references to VDATA (mistake) Editor note: GENERATE UID is not a method. It's wrong in section 7.1.2.3 Ditto with NOOP - Section 7.2.1.6 From owner-ietf-calendar@mail.imc.org Sun Dec 17 07:42:32 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA12995 for ; Sun, 17 Dec 2000 07:42:32 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id EAA06244 for ietf-calendar-bks; Sun, 17 Dec 2000 04:17:22 -0800 (PST) Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id EAA06239 for ; Sun, 17 Dec 2000 04:17:20 -0800 (PST) Received: from HALVESTR-8KCDT.alvestrand.no (localhost [127.0.0.1]) by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id NAA30521; Sun, 17 Dec 2000 13:20:10 +0100 Message-Id: <4.3.2.7.2.20001216200152.07cd6d50@127.0.0.1> X-Sender: hta@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 16 Dec 2000 20:04:03 -0800 To: John Stracke , ietf-calendar@imc.org From: Harald Alvestrand Subject: WAP scheduling (Re: Photos from IETF) In-Reply-To: <3A390154.3DD5E521@ecal.com> References: <30F2DED23724D311902D0008C7EABAFB0301E0D3@daeis06nok> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 12:20 14/12/2000 -0500, John Stracke wrote: >Given the reception the WAP speaker got in Adelaide, I can just imagine how >the IETF membership would react to a proposal that the IETF schedule around >WAP meetings. ;-) (Yeah, that's an extreme way of putting it--the two groups >could just cooperate--but you *know* that's how some people would insist on >interpreting it.) if anyone here knows the persons who schedule WAP meetings, they might want to notify them that there is a mailing list called "meeting-planning@ietf.org" (I think it has the usual -request convention) where quite a few organizations send notifications of events. The schedules might be better synchronized if they send notifications there (and listen to the ones coming out). Harald -- Harald Tveit Alvestrand, alvestrand@cisco.com +47 41 44 29 94 Personal email: Harald@Alvestrand.no From owner-ietf-calendar@mail.imc.org Sun Dec 17 13:50:19 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20767 for ; Sun, 17 Dec 2000 13:50:19 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA00614 for ietf-calendar-bks; Sun, 17 Dec 2000 10:24:06 -0800 (PST) Received: from galactica.it (mail5.galactica.it [212.41.208.22] (may be forged)) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA00610 for ; Sun, 17 Dec 2000 10:24:05 -0800 (PST) Received: from gb1 ([213.167.205.78]) by galactica.it with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 17 Dec 2000 19:27:39 +0100 From: SicilyWEB E-cards Date: Sun, 17 Dec 2000 19:30:14 Subject: A Postcard for you from Sicily - Una Cartolian per te dalla Sicilia Message-ID: <0ffb439271811c0MAIL5@galactica.it> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Ciao, Giambattista ti ha spedito una cartolina dalla Sicilia. La puoi visionare andando al seguente indirizzo: http://sicilyweb.com/card-25122000-set234598.htm Verra' cancellata dal server in 15 giorni. ------------------------------------------------------- Hi, Giambattista sent you a postcard from SICILY. You can pick it going at this address: http://sicilyweb.com/card-25122000-set234598.htm We will delete it from server in 15 days. -------------------------------------------- ARE YOU LOOKING FOR SOMETHING IN SICILY? http://www.sicilyweb.com From owner-ietf-calendar@mail.imc.org Mon Dec 18 01:48:50 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA28026 for ; Mon, 18 Dec 2000 01:48:50 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id WAA23635 for ietf-calendar-bks; Sun, 17 Dec 2000 22:27:07 -0800 (PST) Received: from aomswin1.allenovery.com (mail1.allenovery.com [194.129.43.121]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA23622 for ; Sun, 17 Dec 2000 22:27:05 -0800 (PST) Received: from mail.mindspring.com (unverified) by aomswin1.allenovery.com (Content Technologies SMTPRS 4.1.5) with SMTP id for ; Mon, 18 Dec 2000 06:19:24 +0000 From: To: Date: Mon, 18 Dec 2000 02:20:59 Message-Id: <556.776215.713523@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Mon Dec 18 01:49:47 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA28166 for ; Mon, 18 Dec 2000 01:49:46 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id WAA23641 for ietf-calendar-bks; Sun, 17 Dec 2000 22:27:07 -0800 (PST) Received: from aomswin1.allenovery.com (mail1.allenovery.com [194.129.43.121]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA23629 for ; Sun, 17 Dec 2000 22:27:06 -0800 (PST) Received: from mail.mindspring.com (unverified) by aomswin1.allenovery.com (Content Technologies SMTPRS 4.1.5) with SMTP id for ; Mon, 18 Dec 2000 06:05:18 +0000 From: To: Date: Mon, 18 Dec 2000 02:35:05 Message-Id: <493.786073.790496@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Mon Dec 18 23:55:24 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA24276 for ; Mon, 18 Dec 2000 23:55:24 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA09174 for ietf-calendar-bks; Mon, 18 Dec 2000 20:38:28 -0800 (PST) Received: from craven-college.ac.uk ([212.219.3.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA09162 for ; Mon, 18 Dec 2000 20:38:26 -0800 (PST) From: asdasdha@mail.world-of-mac.de Received: from mail.mindspring.com by craven-college.ac.uk (8.9.3+Sun/SMI-SVR4) id EAA26269; Tue, 19 Dec 2000 04:39:56 GMT To: Date: Mon, 18 Dec 2000 20:00:46 Message-Id: <342.727110.639348@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Tue Dec 19 05:50:19 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA10486 for ; Tue, 19 Dec 2000 05:50:19 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id CAA16058 for ietf-calendar-bks; Tue, 19 Dec 2000 02:28:18 -0800 (PST) Received: from craven-college.ac.uk ([212.219.3.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id CAA16052 for ; Tue, 19 Dec 2000 02:28:16 -0800 (PST) From: ASDLPASD@postman.itw.fr Received: from mail.mindspring.com by craven-college.ac.uk (8.9.3+Sun/SMI-SVR4) id KAA22223; Tue, 19 Dec 2000 10:29:47 GMT To: Date: Tue, 19 Dec 2000 01:50:37 Message-Id: <501.387599.466987@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Tue Dec 19 08:33:22 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA13249 for ; Tue, 19 Dec 2000 08:33:22 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id FAA00313 for ietf-calendar-bks; Tue, 19 Dec 2000 05:15:32 -0800 (PST) Received: from craven-college.ac.uk ([212.219.3.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id FAA00301 for ; Tue, 19 Dec 2000 05:15:15 -0800 (PST) From: adaskdjas@mail.kraft-s.ru Received: from mail.mindspring.com by craven-college.ac.uk (8.9.3+Sun/SMI-SVR4) id NAA01114; Tue, 19 Dec 2000 13:16:47 GMT To: Date: Tue, 19 Dec 2000 04:37:36 Message-Id: <789.2575.701107@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Wed Dec 20 07:37:37 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA21394 for ; Wed, 20 Dec 2000 07:37:37 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id EAA22190 for ietf-calendar-bks; Wed, 20 Dec 2000 04:12:11 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id EAA22186 for ; Wed, 20 Dec 2000 04:12:10 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20413; Wed, 20 Dec 2000 07:15:25 -0500 (EST) Message-Id: <200012201215.HAA20413@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-calendar@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-calsch-crisp-00.txt Date: Wed, 20 Dec 2000 07:15:25 -0500 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --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 Working Group of the IETF. Title : CAP Realtime iTIP-based Scheduling Profile (CRISP) Author(s) : J. Stracke Filename : draft-ietf-calsch-crisp-00.txt Pages : 4 Date : 19-Dec-00 This document sets forth a restricted profile of [CAP], one which supports no operations beyond the scheduling functionality of [iTIP]. The motivation is to permit use of CAP's real-time iTIP functionality without exposing the calendar access functionality (which may require stricter security controls than iTIP). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-calsch-crisp-00.txt 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-ietf-calsch-crisp-00.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-ietf-calsch-crisp-00.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20001219130515.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-calsch-crisp-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-calsch-crisp-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001219130515.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-calendar@mail.imc.org Wed Dec 20 09:13:36 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25172 for ; Wed, 20 Dec 2000 09:13:35 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id FAA28489 for ietf-calendar-bks; Wed, 20 Dec 2000 05:44:14 -0800 (PST) Received: from ljudo.shortlist.se (IDENT:postfix@ljudo.shortlist.se [193.14.119.253]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id FAA28484 for ; Wed, 20 Dec 2000 05:44:12 -0800 (PST) Received: from metamatrix.se (dublin.metamatrix.se [193.14.119.156]) by ljudo.shortlist.se (Postfix) with ESMTP id 5598AB3570 for ; Wed, 20 Dec 2000 15:47:22 +0100 (CET) Message-ID: <3A40B869.D4B0EB4E@metamatrix.se> Date: Wed, 20 Dec 2000 14:47:21 +0100 From: =?iso-8859-1?Q?P=E4r=20Lanner=F6?= Organization: Metamatrix AB X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: writing RFC-style documents Content-Type: text/plain; charset=iso-8859-1 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: X-MIME-Autoconverted: from 8bit to quoted-printable by ns.secondary.com id FAA28489 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA25172 Hi At the recent meeting in San Diego there was some talk about a software package for writing Internet-Drafts using XML. As I have tried it out while working with the SKICal draft you might be interested to know my opinion about it. At least those of you who intend to write new Internet-Drafts. (Converting existing draft documents into XML may not be worthwile.) One good thing about editing the draft in one "source" XML document is that from this document you can automatically generate both a nice-looking HTML document an appropriately formatted ascii text file for submission to the RFC Editor. Another advantage is that the process is actually published as an informational RFC. (RFC-2629) In this document there is a DTD which you can use. Thirdly the software to convert the source document into .html and .txt is free and open source. It is a tcl script which you can find at http://xml.resource.org/authoring/xml2rfc.tar.gz Table of contents, reference linking etc. is generated automatically by this conversion software written by Marshall T. Rose. Even though I would have preferred an XSL transform to a tcl script I think this is a much better method than using the Word conversion software which requires that you print and process .prn files. It certainly is superior to doing raw text editing. Never tried the nroff stuff though. I have found only one bug in the tcl software: you cannot refer to a document in the reference list from inside a element (this element is used for including preformatted text such as sample code). If anybody on the list is a tcl hacker you might want to help fix this. Another item on my whishlist is an XSL-fo stylesheet to render printer-friendly PDF output. If I can find time I will do this myself. /Pär -- Pär Lannerö, Infostructure developer, Metamatrix AB, Stockholm Mail: Cellphone: +46 739 44 20 43 Work web: www.metamatrix.se Personal web: www.lannero.com/p/ From owner-ietf-calendar@mail.imc.org Wed Dec 20 12:05:04 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03913 for ; Wed, 20 Dec 2000 12:05:04 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA11099 for ietf-calendar-bks; Wed, 20 Dec 2000 08:24:46 -0800 (PST) Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA11091 for ; Wed, 20 Dec 2000 08:24:44 -0800 (PST) From: Frank.Dawson@nokia.com Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86]) by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id eBKGSb614878 for ; Wed, 20 Dec 2000 10:28:47 -0600 (CST) Received: from daebh01nok.americas.nokia.com (unverified) by davir03nok.americas.nokia.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Wed, 20 Dec 2000 10:27:49 -0600 Received: by daebh01nok with Internet Mail Service (5.5.2652.78) id ; Wed, 20 Dec 2000 10:23:13 -0600 Message-ID: <30F2DED23724D311902D0008C7EABAFB0301E156@daeis06nok> To: par.lannero@metamatrix.se, ietf-calendar@imc.org Subject: RE: writing RFC-style documents Date: Wed, 20 Dec 2000 10:21:47 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Another short-coming is the lack of WYSIWYG editing. For large documents, this greatly improves performance. -- Frank From owner-ietf-calendar@mail.imc.org Wed Dec 20 23:03:35 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA25266 for ; Wed, 20 Dec 2000 23:03:34 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id TAA06104 for ietf-calendar-bks; Wed, 20 Dec 2000 19:44:54 -0800 (PST) Received: from guanabana.helixcode.com (IDENT:root@cs2-13.modems.unam.mx [132.248.10.183]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA06100 for ; Wed, 20 Dec 2000 19:44:51 -0800 (PST) Received: (from federico@localhost) by guanabana.helixcode.com (8.9.3/8.9.3) id VAA09970; Wed, 20 Dec 2000 21:56:21 -0600 Date: Wed, 20 Dec 2000 21:56:21 -0600 Message-Id: <200012210356.VAA09970@guanabana.helixcode.com> X-Authentication-Warning: guanabana.helixcode.com: federico set sender to federico@helixcode.com using -f From: Federico Mena Quintero To: Pär Lannerö Cc: ietf-calendar@imc.org Subject: Re: writing RFC-style documents References: <3A40B869.D4B0EB4E@metamatrix.se> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Pär Lannerö writes: > At the recent meeting in San Diego there was some talk about a software > package for writing Internet-Drafts using XML. As I have tried it out > while working with the SKICal draft you might be interested to know my > opinion about it. At least those of you who intend to write new > Internet-Drafts. (Converting existing draft documents into XML may not > be worthwile.) > > One good thing about editing the draft in one "source" XML document is > that from this document you can automatically generate both a > nice-looking HTML document an appropriately formatted ascii text file > for submission to the RFC Editor. Ummm, what is wrong with just using DocBook, instead of defining yet another DTD and stylesheets? You can even use the newer DocBook/XML. It is what everyone[1] seems to be using for formal documents these days, and it is actually very nice to use. [1] Free software people, at least. Federico From owner-ietf-calendar@mail.imc.org Thu Dec 21 05:10:56 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA14222 for ; Thu, 21 Dec 2000 05:10:55 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id BAA07840 for ietf-calendar-bks; Thu, 21 Dec 2000 01:55:04 -0800 (PST) Received: from ljudo.shortlist.se (IDENT:postfix@ljudo.shortlist.se [193.14.119.253]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id BAA07833 for ; Thu, 21 Dec 2000 01:55:02 -0800 (PST) Received: from metamatrix.se (dublin.metamatrix.se [193.14.119.156]) by ljudo.shortlist.se (Postfix) with ESMTP id 6EC03B3570; Thu, 21 Dec 2000 11:58:21 +0100 (CET) Message-ID: <3A41D43C.17B89186@metamatrix.se> Date: Thu, 21 Dec 2000 10:58:20 +0100 From: =?iso-8859-1?Q?P=E4r=20Lanner=F6?= Organization: Metamatrix AB X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Federico Mena Quintero Cc: ietf-calendar@imc.org Subject: Re: writing RFC-style documents References: <3A40B869.D4B0EB4E@metamatrix.se> <200012210356.VAA09970@guanabana.helixcode.com> Content-Type: text/plain; charset=iso-8859-1 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: X-MIME-Autoconverted: from 8bit to quoted-printable by ns.secondary.com id BAA07840 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA14222 Federico Mena Quintero wrote: > > One good thing about editing the draft in one "source" XML document is > > that from this document you can automatically generate both a > > nice-looking HTML document an appropriately formatted ascii text file > > for submission to the RFC Editor. > > Ummm, what is wrong with just using DocBook, instead of defining yet > another DTD and stylesheets? You can even use the newer DocBook/XML. That would be nice, but is there a stylesheet to generate RFC style text documents formatted according to RFC-2223? (Limited to 72 characters per line and 58 lines per page, followed by a formfeed character....) I cannot find any such information on the Oasis docbook site. /Pär From owner-ietf-calendar@mail.imc.org Thu Dec 21 06:08:47 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA14672 for ; Thu, 21 Dec 2000 06:08:46 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id CAA11072 for ietf-calendar-bks; Thu, 21 Dec 2000 02:43:46 -0800 (PST) Received: from ljudo.shortlist.se (IDENT:postfix@ljudo.shortlist.se [193.14.119.253]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id CAA11068 for ; Thu, 21 Dec 2000 02:43:44 -0800 (PST) Received: from gregs (unknown [193.14.119.6]) by ljudo.shortlist.se (Postfix) with SMTP id 03778B3570 for ; Thu, 21 Dec 2000 12:47:04 +0100 (CET) From: "Greg FitzPatrick" To: Subject: SV: writing RFC-style documents Date: Thu, 21 Dec 2000 11:47:33 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <30F2DED23724D311902D0008C7EABAFB0301E156@daeis06nok> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Frank wrote: >Another short-coming is the lack of WYSIWYG editing. For large documents, >this greatly improves performance. I work in XML-SPY, mostly using the text-editing page, of course that wont give you WYSIWYG but on the other hand you can do a validation against the DTD for every change you make and that is very helpful. Greg From owner-ietf-calendar@mail.imc.org Thu Dec 21 11:37:51 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA23645 for ; Thu, 21 Dec 2000 11:37:50 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA04329 for ietf-calendar-bks; Thu, 21 Dec 2000 08:04:15 -0800 (PST) Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA04324 for ; Thu, 21 Dec 2000 08:04:13 -0800 (PST) From: Frank.Dawson@nokia.com Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84]) by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id eBLG8O627114 for ; Thu, 21 Dec 2000 10:08:24 -0600 (CST) Received: from daebh01nok.americas.nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Thu, 21 Dec 2000 10:07:34 -0600 Received: by daebh01nok with Internet Mail Service (5.5.2652.78) id ; Thu, 21 Dec 2000 10:02:57 -0600 Message-ID: <30F2DED23724D311902D0008C7EABAFB0301E174@daeis06nok> To: greg.fitzpatrick@metamatrix.se, ietf-calendar@imc.org Subject: RE: writing RFC-style documents Date: Thu, 21 Dec 2000 10:01:30 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > I work in XML-SPY, mostly using the text-editing page, of > course that wont > give you WYSIWYG but on the other hand you can do a > validation against the > DTD for every change you make and that is very helpful. > We used this for the SyncML work, also. I agree, not a bad tool. However, as you point out it doesn't provide a WYSIWYG capability. It is just a DTD design tool. We were talking about editing a document instance, not the template. From owner-ietf-calendar@mail.imc.org Thu Dec 21 13:43:52 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27102 for ; Thu, 21 Dec 2000 13:43:51 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA11860 for ietf-calendar-bks; Thu, 21 Dec 2000 10:20:58 -0800 (PST) Received: from ljudo.shortlist.se (IDENT:postfix@ljudo.shortlist.se [193.14.119.253]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA11851 for ; Thu, 21 Dec 2000 10:20:56 -0800 (PST) Received: from gregs (unknown [193.14.119.6]) by ljudo.shortlist.se (Postfix) with SMTP id ACE3BB3570; Thu, 21 Dec 2000 20:24:17 +0100 (CET) From: "Greg FitzPatrick" To: , Cc: "Niklas Hjelm" Subject: SV: writing RFC-style documents Date: Thu, 21 Dec 2000 19:24:46 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <30F2DED23724D311902D0008C7EABAFB0301E174@daeis06nok> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: X-MIME-Autoconverted: from 8bit to quoted-printable by ns.secondary.com id KAA11860 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA27102 Niklas has just offered (offlist) to do a style sheet :-) -----Ursprungligt meddelande----- Från: Frank.Dawson@nokia.com [mailto:Frank.Dawson@nokia.com] Skickat: den 21 december 2000 17:01 Till: greg.fitzpatrick@metamatrix.se; ietf-calendar@imc.org Ämne: RE: writing RFC-style documents > I work in XML-SPY, mostly using the text-editing page, of > course that wont > give you WYSIWYG but on the other hand you can do a > validation against the > DTD for every change you make and that is very helpful. > We used this for the SyncML work, also. I agree, not a bad tool. However, as you point out it doesn't provide a WYSIWYG capability. It is just a DTD design tool. We were talking about editing a document instance, not the template. From owner-ietf-calendar@mail.imc.org Fri Dec 22 19:46:09 2000 Received: from ns.secondary.com (ns.secondary2.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16685 for ; Fri, 22 Dec 2000 19:46:09 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id QAA22827 for ietf-calendar-bks; Fri, 22 Dec 2000 16:25:15 -0800 (PST) Received: from [213.56.213.1] ([213.56.213.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA22823 for ; Fri, 22 Dec 2000 16:25:13 -0800 (PST) Received: from MAIL.MINDSPRING.COM by [213.56.213.1] with SMTP (QuickMail Pro Server for Mac 2.0.1); 22-Dec-2000 07:15:01 +0100 From: To: Date: Fri, 22 Dec 2000 02:25:24 Message-Id: <392.105615.647522@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 if you are outside the USA, please fax 240 337 8325 Webhosting International From owner-ietf-calendar@mail.imc.org Sun Dec 24 03:24:00 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02528 for ; Sun, 24 Dec 2000 03:23:59 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA06736 for ietf-calendar-bks; Sat, 23 Dec 2000 23:56:42 -0800 (PST) Received: from royer.com (royer.com [207.177.146.80]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA06728 for ; Sat, 23 Dec 2000 23:56:39 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA17582 for ietf-calendar@imc.org; Sun, 24 Dec 2000 00:00:03 -0800 (PST) Date: Sun, 24 Dec 2000 00:00:03 -0800 (PST) From: Doug Royer Message-Id: <200012240800.AAA17582@royer.com> X-Authentication-Warning: royer.com: doug set sender to Doug@Royer.Com using -r To: ietf-calendar@imc.org Subject: CALSCH Action Items Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a list of action items for the CALSCH Working Group. This list will be sent out once a week and updated as often as practical (That means if I am not available it may take an extra week or two before you see your changes). Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM . There are three parts to this action list: (W) Working group action items. (C) CAP editor action items. (I) iCalendar action items (Frank Dawson) Each action item will be assigned a unique ID that will aid in tracking the items. ------------------------------------------------------------------------------ Working Group Action Items Where Resolution is one of: U - undecided. Y - Chair determined consensus is in favor of the proposal. N - Chair determined consensus is NOT in favor of the proposal. D - Dropped. Chair has decided that it may never reach consensus. The following are a list of proposals and their status in the WG: WG Action Item Resolution -------------- ---------- W-1 CAP Use HTTP as transport N W-2 CAP If all booked and scheduled Y appointments are in same table W-3 CAP Use SASL as authentication method Y W-4 Add UID and COUNTER to VFREEBUSY N W-5 CAP Should CAPABILITY reply be sent N as result of successful AUTHENTICATE and IDENTITY W-6 Do we need to handle 'unscheduled event' as described by the SKI project? N (In CAP - 'N', SKI to be a seperate project/draft as it will effect RFC2445,6,7) W-7 CAP Auto-logout Timer issues Do we need one? Y How long? Can the server decide not to do this? Y W-8 CAP Bounded Latency Issues D W-9 CAP MOVE method. Issues with VCARs. Y [see note in CAP 7.2.1.5] W-10 CAP Text mandatory in all response N codes W-11 CAP Text optional in response codes Y (some response codes may have mandatory data that follows) W-12 CAP Should parts of response code be Y separated by ';' W-13 CAP Store Schema Y W-14 CAP VEVENT Schema Y W-15 CAP VTODO Schema Y W-16 CAP VJOURNAL Schema Y W-17 CAP VCAR Schema Y W-18 CAP UPN definition, including anonymous Y user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and Y static and how groups are used in VCARs. Policy definitions, in a VCAR format. W-20 Associating UPN values with CREATED N and LAST-MODIFIED properties. W-21 CAP Get/Set calendar user properties N W-22 VTIMEZONE and IANA Y in process W-23 CAP Calendar property to allow/disallow N overlapped booking OPAQUE entries? W-24 CAP Calendar CHARSET property issues Y W-25 Remove MUST from UID in 4.8.4.7 Y W-26 Write/Submit information draft/rfc Y W-27 How a query can specify if the recurrence Y rules are to be expanded by the CS. W-28 Cal-Props - PATH N (CAP-00 - 12.2) Will there need to be one? N Optional? N W-29 Import/Export Y - sync only W-30 Transport protocol name (transport vs Y application layer) W-31 NOOP command? Y W-32 NOOP advisory only? Y W-33 Should DISCONNECT be called QUIT? U W-34 Format following error codes. Are Y they well defined? If not they need to be machine determinable. W-35 Move DNS and SLP to seperate draft? Y ------------------------------------------------------------------------------ The following are a list of action items for the draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex Y text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug D C-4 VCAR examples Doug? Y C-5 PUBLISH text Y C-6 REQUEST text Y C-7 REPLY text Y C-8 ADD text Y C-9 CANCEL text Y C-10 REFRESH text Y C-11 COUNTER text Y C-12 DECLINECOUNTER Text Y C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS Y and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property Y C-16 (2.11) Query Schema Y C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Y Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS D Format? Text needs to be written. C-20 (13.) Security Considerations Y See editors note - more text. C-21 Resubmit REQUIREMENTS draft. Y C-22 Document MAXSIZE and MAXRESULT N C-23 Document METHOD is stored in CS database N Only one 'CREATE' per UID. Multple non-CREATE per UID. C-24 Fix the RESPONSE's to be consistant. N and multiple components, one for each TARGET. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: (iCal, iTIP, iMIP) Draft Action Item Who Done (Y/N) ----------------- --- ---------- I-1 MIME alternate/related Frank ? MUST be supported. I-2 Remove ordering of properties and Frank ? parameters in draft. I-3 S/MIME and RFC1847. U [CAP] 2.2.3 I-4 Add ALARMID to VALARM! I-5 iTIP error. VJOURNAL should be 0 (not 0+) for CANCEL ------------------------------------------------------------------------------ Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM -------------------------------------------------------------------------- Work: Doug.Royer@Software.com Home 801 Woodside Rd #14-244 530 E. Montecito St. Office: Redwood City, CA 94061 Santa Barbara, CA 93103 805-957-1790 x541 Personal Email: Doug@Royer.com Tuesday discussion: DONE Section 2.4.3 - editor note: Change with new paragraph; Groups may be in a directory with its own ACL model and CAP should use the directory service to expand a UPN subject to the directory service access control model for the authenticated entity. DONE Section 2.4.4.1 - editor note: Your access is a union of all your grants minus a union of all your denies. (We still need to discuss ordering - allow or not. We may not want to fool with it). DONE Section 2.4.4.2 - editor note: We need an example (Steve/Doug) - Paul needs to read this note an example). Section 2.6 CALID - need to define that relative CALID must be consistent with the scheme specific part of URI as defined in RFC xxx. - Steve Section 2.9 Will be discussed earlier in draft - remove altogether. Section 7.1.3 Need to get IANA registration Section 7.1.3 Delete editors note about blank on examples. Need to add an unsuccessful login. Delete all lines except the line that starts with "The following...." - (* Who will do this example) DONE Section 7.2.1.1.1 Get rid of whole paragraph (pargraph above). If you want to generate unique relative CALids, use the GENERATE UID command and use the result as the relative CALid. (we need to make sure that the results are characters that are compatible with our definition of calids) Section 7.2.1.3. The result needs to be consistent with CALID character rules (i.e. no spaces). The example needs one more line with a dot. Steve will do this. DONE Section 7.2.1.5 This issue goes away because we are not doing heirarchial. Remove editors note Section 7.2.1.7 Add an example of a partial result - we want to get something that matches some things, and on the ones you don't have access, you don't have rights to some of the components. George will write up something. Section 7.2.2 Need restriction tables. Some are CAP - for the rest of them use iTIP tables (Steve/Doug) we all need to review the text DONE Section 7.2.3.2 Pull editors note - fix applied Section 8.0 Response codes. Need to make sure response codes in all drafts - iCal, iMip and iTip and examples. Error numbers need to be the same. Put text about error codes in comments below the examples (so that people don't look at them as being required in their text). Pat will look at the codes. Section 11.0 DTN, DTSTAMP, etc are implementations that may need to be considered. Restrictions tables may resolve these issues. Section 12.0 Leave as is until we get people to agree. On version shipped after last call, this is what we are going to enhance this section. It does not make sense to do this until working group last call. Updates to iCalendar need to be written and will not be submitted to IANA until last call to WG. Doug Section 13.0 This section is not ready for prime time. Need Paul Hill. Need an editors note. Section 14.0 Needs to be reformatted - Doug will make sure it is consistent. George will do 14 DONE Section 15.1.1. Steve - additions or changes to the CAP schema (replaces Define the Entity). Word entity needs to be removed and replaced throughout the document). Section 15.1.4 Submit entity for approval - John submitted to list. Need to find. Get John's text and add back into CAP draft. John submitted as a separate draft document. Use the MIME appeal verbage with John's additional text. Point WG at John's draft and say it should be included in the draft. We need to also submit to April Marine as well. DONE Section 16.0 Remove reference to vCard - - - - - - Assignment list: Section 2.4.4.2 - VCAR example (Steve/Doug) Sectoin 2.6 - Steve will research Section 7.1.3 - IANA registration (Pat) Section 7.1.3 - example of unsuccessful login (Who) Section 7.2.1.1. - look at Calid characters (Doug) Section 7.2.1.3 - example line (Steve) Section 7.2.1.7 - George will write some verbage and we need to add an example of partial results (Steve/Doug) Section 7.2.2. - Restriction tables (Steve/Doug) Section 8.0 - look at consistency of Response code in all drafts (Pat) Section 12.0 - needs work. Check for consistency - Doug Section 13.0 - Paul Hill Section 14.0 - George Section 15.1.1 - replace text (Pat) Section 15.1.4 - add John's text to doc and put on list to look at proposal. - - - - - Work on Restriction table Editor note: Remove references to VDATA (mistake) Editor note: GENERATE UID is not a method. It's wrong in section 7.1.2.3 Ditto with NOOP - Section 7.2.1.6 From owner-ietf-calendar@mail.imc.org Sun Dec 31 03:22:55 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02628 for ; Sun, 31 Dec 2000 03:22:55 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA14306 for ietf-calendar-bks; Sat, 30 Dec 2000 23:56:06 -0800 (PST) Received: from royer.com (royer.com [207.177.146.80]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA14298 for ; Sat, 30 Dec 2000 23:56:04 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA02592 for ietf-calendar@imc.org; Sun, 31 Dec 2000 00:00:04 -0800 (PST) Date: Sun, 31 Dec 2000 00:00:04 -0800 (PST) From: Doug Royer Message-Id: <200012310800.AAA02592@royer.com> X-Authentication-Warning: royer.com: doug set sender to Doug@Royer.Com using -r To: ietf-calendar@imc.org Subject: CALSCH Action Items Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a list of action items for the CALSCH Working Group. This list will be sent out once a week and updated as often as practical (That means if I am not available it may take an extra week or two before you see your changes). Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM . There are three parts to this action list: (W) Working group action items. (C) CAP editor action items. (I) iCalendar action items (Frank Dawson) Each action item will be assigned a unique ID that will aid in tracking the items. ------------------------------------------------------------------------------ Working Group Action Items Where Resolution is one of: U - undecided. Y - Chair determined consensus is in favor of the proposal. N - Chair determined consensus is NOT in favor of the proposal. D - Dropped. Chair has decided that it may never reach consensus. The following are a list of proposals and their status in the WG: WG Action Item Resolution -------------- ---------- W-1 CAP Use HTTP as transport N W-2 CAP If all booked and scheduled Y appointments are in same table W-3 CAP Use SASL as authentication method Y W-4 Add UID and COUNTER to VFREEBUSY N W-5 CAP Should CAPABILITY reply be sent N as result of successful AUTHENTICATE and IDENTITY W-6 Do we need to handle 'unscheduled event' as described by the SKI project? N (In CAP - 'N', SKI to be a seperate project/draft as it will effect RFC2445,6,7) W-7 CAP Auto-logout Timer issues Do we need one? Y How long? Can the server decide not to do this? Y W-8 CAP Bounded Latency Issues D W-9 CAP MOVE method. Issues with VCARs. Y [see note in CAP 7.2.1.5] W-10 CAP Text mandatory in all response N codes W-11 CAP Text optional in response codes Y (some response codes may have mandatory data that follows) W-12 CAP Should parts of response code be Y separated by ';' W-13 CAP Store Schema Y W-14 CAP VEVENT Schema Y W-15 CAP VTODO Schema Y W-16 CAP VJOURNAL Schema Y W-17 CAP VCAR Schema Y W-18 CAP UPN definition, including anonymous Y user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and Y static and how groups are used in VCARs. Policy definitions, in a VCAR format. W-20 Associating UPN values with CREATED N and LAST-MODIFIED properties. W-21 CAP Get/Set calendar user properties N W-22 VTIMEZONE and IANA Y in process W-23 CAP Calendar property to allow/disallow N overlapped booking OPAQUE entries? W-24 CAP Calendar CHARSET property issues Y W-25 Remove MUST from UID in 4.8.4.7 Y W-26 Write/Submit information draft/rfc Y W-27 How a query can specify if the recurrence Y rules are to be expanded by the CS. W-28 Cal-Props - PATH N (CAP-00 - 12.2) Will there need to be one? N Optional? N W-29 Import/Export Y - sync only W-30 Transport protocol name (transport vs Y application layer) W-31 NOOP command? Y W-32 NOOP advisory only? Y W-33 Should DISCONNECT be called QUIT? U W-34 Format following error codes. Are Y they well defined? If not they need to be machine determinable. W-35 Move DNS and SLP to seperate draft? Y ------------------------------------------------------------------------------ The following are a list of action items for the draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex Y text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug D C-4 VCAR examples Doug? Y C-5 PUBLISH text Y C-6 REQUEST text Y C-7 REPLY text Y C-8 ADD text Y C-9 CANCEL text Y C-10 REFRESH text Y C-11 COUNTER text Y C-12 DECLINECOUNTER Text Y C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS Y and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property Y C-16 (2.11) Query Schema Y C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Y Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS D Format? Text needs to be written. C-20 (13.) Security Considerations Y See editors note - more text. C-21 Resubmit REQUIREMENTS draft. Y C-22 Document MAXSIZE and MAXRESULT N C-23 Document METHOD is stored in CS database N Only one 'CREATE' per UID. Multple non-CREATE per UID. C-24 Fix the RESPONSE's to be consistant. N and multiple components, one for each TARGET. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: (iCal, iTIP, iMIP) Draft Action Item Who Done (Y/N) ----------------- --- ---------- I-1 MIME alternate/related Frank ? MUST be supported. I-2 Remove ordering of properties and Frank ? parameters in draft. I-3 S/MIME and RFC1847. U [CAP] 2.2.3 I-4 Add ALARMID to VALARM! I-5 iTIP error. VJOURNAL should be 0 (not 0+) for CANCEL ------------------------------------------------------------------------------ Updates should be sent to mailto:ietf-calendar@imc.org or to myself mailto:Doug.Royer@Software.COM -------------------------------------------------------------------------- Work: Doug.Royer@Software.com Home 801 Woodside Rd #14-244 530 E. Montecito St. Office: Redwood City, CA 94061 Santa Barbara, CA 93103 805-957-1790 x541 Personal Email: Doug@Royer.com Tuesday discussion: DONE Section 2.4.3 - editor note: Change with new paragraph; Groups may be in a directory with its own ACL model and CAP should use the directory service to expand a UPN subject to the directory service access control model for the authenticated entity. DONE Section 2.4.4.1 - editor note: Your access is a union of all your grants minus a union of all your denies. (We still need to discuss ordering - allow or not. We may not want to fool with it). DONE Section 2.4.4.2 - editor note: We need an example (Steve/Doug) - Paul needs to read this note an example). Section 2.6 CALID - need to define that relative CALID must be consistent with the scheme specific part of URI as defined in RFC xxx. - Steve Section 2.9 Will be discussed earlier in draft - remove altogether. Section 7.1.3 Need to get IANA registration Section 7.1.3 Delete editors note about blank on examples. Need to add an unsuccessful login. Delete all lines except the line that starts with "The following...." - (* Who will do this example) DONE Section 7.2.1.1.1 Get rid of whole paragraph (pargraph above). If you want to generate unique relative CALids, use the GENERATE UID command and use the result as the relative CALid. (we need to make sure that the results are characters that are compatible with our definition of calids) Section 7.2.1.3. The result needs to be consistent with CALID character rules (i.e. no spaces). The example needs one more line with a dot. Steve will do this. DONE Section 7.2.1.5 This issue goes away because we are not doing heirarchial. Remove editors note Section 7.2.1.7 Add an example of a partial result - we want to get something that matches some things, and on the ones you don't have access, you don't have rights to some of the components. George will write up something. Section 7.2.2 Need restriction tables. Some are CAP - for the rest of them use iTIP tables (Steve/Doug) we all need to review the text DONE Section 7.2.3.2 Pull editors note - fix applied Section 8.0 Response codes. Need to make sure response codes in all drafts - iCal, iMip and iTip and examples. Error numbers need to be the same. Put text about error codes in comments below the examples (so that people don't look at them as being required in their text). Pat will look at the codes. Section 11.0 DTN, DTSTAMP, etc are implementations that may need to be considered. Restrictions tables may resolve these issues. Section 12.0 Leave as is until we get people to agree. On version shipped after last call, this is what we are going to enhance this section. It does not make sense to do this until working group last call. Updates to iCalendar need to be written and will not be submitted to IANA until last call to WG. Doug Section 13.0 This section is not ready for prime time. Need Paul Hill. Need an editors note. Section 14.0 Needs to be reformatted - Doug will make sure it is consistent. George will do 14 DONE Section 15.1.1. Steve - additions or changes to the CAP schema (replaces Define the Entity). Word entity needs to be removed and replaced throughout the document). Section 15.1.4 Submit entity for approval - John submitted to list. Need to find. Get John's text and add back into CAP draft. John submitted as a separate draft document. Use the MIME appeal verbage with John's additional text. Point WG at John's draft and say it should be included in the draft. We need to also submit to April Marine as well. DONE Section 16.0 Remove reference to vCard - - - - - - Assignment list: Section 2.4.4.2 - VCAR example (Steve/Doug) Sectoin 2.6 - Steve will research Section 7.1.3 - IANA registration (Pat) Section 7.1.3 - example of unsuccessful login (Who) Section 7.2.1.1. - look at Calid characters (Doug) Section 7.2.1.3 - example line (Steve) Section 7.2.1.7 - George will write some verbage and we need to add an example of partial results (Steve/Doug) Section 7.2.2. - Restriction tables (Steve/Doug) Section 8.0 - look at consistency of Response code in all drafts (Pat) Section 12.0 - needs work. Check for consistency - Doug Section 13.0 - Paul Hill Section 14.0 - George Section 15.1.1 - replace text (Pat) Section 15.1.4 - add John's text to doc and put on list to look at proposal. - - - - - Work on Restriction table Editor note: Remove references to VDATA (mistake) Editor note: GENERATE UID is not a method. It's wrong in section 7.1.2.3 Ditto with NOOP - Section 7.2.1.6