From owner-ietf-calendar@mail.imc.org Sun Jan 7 03:29:38 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03477 for ; Sun, 7 Jan 2001 03:29:38 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA07569 for ietf-calendar-bks; Sat, 6 Jan 2001 23:55:32 -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 XAA07561 for ; Sat, 6 Jan 2001 23:55:29 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA15677 for ietf-calendar@imc.org; Sun, 7 Jan 2001 00:00:04 -0800 (PST) Date: Sun, 7 Jan 2001 00:00:04 -0800 (PST) From: Doug Royer Message-Id: <200101070800.AAA15677@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 Mon Jan 8 02:38:01 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA28241 for ; Mon, 8 Jan 2001 02:38:00 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id XAA21099 for ietf-calendar-bks; Sun, 7 Jan 2001 23:13:12 -0800 (PST) Received: from tor-exchange.goldfarbconsultants.com (mail.goldfarbconsultants.com [204.101.222.194]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA21089 for ; Sun, 7 Jan 2001 23:13:10 -0800 (PST) Received: from shieldsmtp.goldfarbconsultants.com (SHIELDSMTP [151.51.192.28]) by tor-exchange.goldfarbconsultants.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id Z5MVNLKJ; Mon, 8 Jan 2001 02:13:31 -0500 Received: FROM mail.mindspring.com BY shieldsmtp.goldfarbconsultants.com ; Sat Jan 06 06:16:43 2001 -0500 From: To: Date: Sat, 6 Jan 2001 02:35:55 Message-Id: <494.59726.422867@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 Thu Jan 11 13:21:20 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11712 for ; Thu, 11 Jan 2001 13:21:20 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA14492 for ietf-calendar-bks; Thu, 11 Jan 2001 10:03:49 -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 KAA14486 for ; Thu, 11 Jan 2001 10:03:47 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Subject: Minneapolis meeting X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Thu, 11 Jan 2001 18:08:52 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 01/11/2001 01:08:54 PM, Serialize complete at 01/11/2001 01:08:54 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 004861F0802569D1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 004861F0802569D1_= Content-Type: text/plain; charset="us-ascii" We are being asked for timeslots for the Minneapolis meeting of the IETF. Please post preferences for times and days and note any working groups which we should avoid scheduling against. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 004861F0802569D1_= Content-Type: text/html; charset="us-ascii"
We are being asked for timeslots for the Minneapolis meeting of the IETF.  Please post preferences for times and days and note any working groups which we should avoid scheduling against.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 004861F0802569D1_=-- From owner-ietf-calendar@mail.imc.org Thu Jan 11 13:28:14 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11809 for ; Thu, 11 Jan 2001 13:28:13 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id KAA15075 for ietf-calendar-bks; Thu, 11 Jan 2001 10:10:53 -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 KAA15066 for ; Thu, 11 Jan 2001 10:10:45 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Subject: CalConnect Number 2 X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Thu, 11 Jan 2001 18:15:49 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 01/11/2001 01:15:52 PM, Serialize complete at 01/11/2001 01:15:52 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 004904D7802569D1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 004904D7802569D1_= Content-Type: text/plain; charset="us-ascii" We are finalizing the information on our next interoperability testing. It will occur the week of 2/19. We will have a firm date with in the next week. The location will be the Palo Alto area. I will post a URL link to information on requirements to participate, hotels in the area, maps to the site, etc. As soon as I resolve where the actual interop will take place (it's between two sites right now), I will provide the URL. I am posting the note to give the developers a heads up on the timeframe for the meeting. This will be a two day session and will probably occur the Thursday and Friday of the 2/19 week. Again, that will be further resolved when we finalize the location. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 004904D7802569D1_= Content-Type: text/html; charset="us-ascii"
We are finalizing the information on our next interoperability testing.  It will occur the week of 2/19.  We will have a firm date with in the next week.  The location will be the Palo Alto area.  I will post a URL link to information on requirements to participate, hotels in the area, maps to the site, etc.  As soon as I resolve where the actual interop will take place (it's between two sites right now), I will provide the URL.  I am posting the note to give the developers a heads up on the timeframe for the meeting.

This will be a two day session and will probably occur the Thursday and Friday of the 2/19 week.  Again, that will be further resolved when we finalize the location.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 004904D7802569D1_=-- From owner-ietf-calendar@mail.imc.org Thu Jan 11 13:59:35 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12403 for ; Thu, 11 Jan 2001 13:59:35 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id KAA15976 for ietf-calendar-bks; Thu, 11 Jan 2001 10:33:56 -0800 (PST) Received: from ledig.paf.se (c193.150.248.34.cm-upc.chello.se [193.150.248.34]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA15972 for ; Thu, 11 Jan 2001 10:33:54 -0800 (PST) Received: from [192.168.1.11] (dhcp-11.paf.se [192.168.1.11]) by ledig.paf.se (8.9.3/8.9.3) with ESMTP id TAA70460; Thu, 11 Jan 2001 19:38:45 +0100 (CET) (envelope-from paf@cisco.com) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: References: Date: Thu, 11 Jan 2001 19:38:27 +0100 To: pregen@egenconsulting.com, ietf-calendar@imc.org From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: Re: Minneapolis meeting Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 KAA15976 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA12403 At 18.08 +0000 01-01-11, pregen@egenconsulting.com wrote: > Please post preferences for times and days and note any working >groups which we should avoid scheduling against. Important are the wg's and eventual bof's you know about which you want to NOT collide with. Selections of days have very low priority when sheduling, and moving things around do happen regularly. Just to let you know where priorities are when we do scheduling. paf -- Patrik Fältström Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC From owner-ietf-calendar@mail.imc.org Thu Jan 11 15:27:08 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA13985 for ; Thu, 11 Jan 2001 15:27:08 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id MAA22931 for ietf-calendar-bks; Thu, 11 Jan 2001 12:06:39 -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 MAA22926 for ; Thu, 11 Jan 2001 12:06:36 -0800 (PST) From: pregen@egenconsulting.com To: Patrik =?iso-8859-1?q?F=E4ltstr=F6m?= Cc: ietf-calendar@imc.org Subject: Re: Minneapolis meeting X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Thu, 11 Jan 2001 20:11:43 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 01/11/2001 03:11:43 PM, Serialize complete at 01/11/2001 03:11:43 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0053A15E802569D1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0053A15E802569D1_= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you Patrik for the clarification. =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Patricia Egen Consulting www.egenconsulting.com 423-875-2652 Patrik F=E4ltstr=F6m 01/11/01 06:38 PM =20 To: pregen@egenconsulting.com, ietf-calendar@imc.org cc:=20 Subject: Re: Minneapolis meeting At 18.08 +0000 01-01-11, pregen@egenconsulting.com wrote: > Please post preferences for times and days and note any working=20 >groups which we should avoid scheduling against. Important are the wg's and eventual bof's you know about which you=20 want to NOT collide with. Selections of days have very low priority when sheduling, and moving=20 things around do happen regularly. Just to let you know where priorities are when we do scheduling. paf --=20 Patrik F=E4ltstr=F6m Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC --=_alternative 0053A15E802569D1_= Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Thank you Patrik for the clarificati= on.
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


Patrik F=E4ltstr=F6m <paf@cisc= o.com>

01/11/01 06:38 PM

       
        To: &nbs= p;      pregen@egenconsulting.com, ietf-calendar@imc.org
        cc: &nbs= p;      
        Subject:=        Re: Minneapolis meeting



At 18.08 +0000 01-01-11, pregen@egenconsulting.com w= rote:
>   Please post preferences for times and days and note any working=
>groups which we should avoid scheduling against.

Important are the wg's and eventual bof's you know about which you
want to NOT collide with.

Selections of days have very low priority when sheduling, and moving
things around do happen regularly.

Just to let you know where priorities are when we do scheduling.

  paf


--
Patrik F=E4ltstr=F6m <paf@cisco.com>       Internet En= gineering Task Force
Area Director, Applications Area             =       http://www.ietf.org
Phone: (Stockholm) +46-8-4494212            (= San Jose) +1-408-525-0940
       PGP: 2DFC AAF6 16F0 F276 7843  2DC1 BC79 5= 1D9 7D25 B8DC

--=_alternative 0053A15E802569D1_=-- From owner-ietf-calendar@mail.imc.org Sat Jan 13 12:49:46 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA19096 for ; Sat, 13 Jan 2001 12:49:45 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA06532 for ietf-calendar-bks; Sat, 13 Jan 2001 09:25:48 -0800 (PST) Received: from passnotes.share.org (passnotes.share.org [192.111.120.12]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id JAA06524 for ; Sat, 13 Jan 2001 09:25:46 -0800 (PST) From: Pat_R_Egen@mail.share.org Received: by passnotes.share.org(Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) id 862569D3.00603AC0 ; Sat, 13 Jan 2001 11:31:05 -0600 X-Lotus-FromDomain: SHARE INC To: Damon Chaplin cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Message-ID: <862569D3.00603778.00@passnotes.share.org> Date: Sat, 13 Jan 2001 11:30:47 -0600 Subject: Re: converting Olson timezone database to VTIMEZONEs Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=y9djq3ju5rJhuhYYpyQTJNlp1hIYKtYHuQmz4Q6u8jcOWuMZMJrqA36I" Content-Disposition: inline Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --0__=y9djq3ju5rJhuhYYpyQTJNlp1hIYKtYHuQmz4Q6u8jcOWuMZMJrqA36I Content-type: text/plain; charset=us-ascii Content-Disposition: inline Hi Damon. --0__=y9djq3ju5rJhuhYYpyQTJNlp1hIYKtYHuQmz4Q6u8jcOWuMZMJrqA36I Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0Doug Royer did just that. =A0He also sent a note to IANA to register= what he had done. =A0In talking with CS&T at the IETF this week, they s= aid they have found some missing timezones from the Olson database. =A0They have= a more comprehensive database. =A0Let me see if I can find out where Doug has = the database. =A0He is out on medical leave and it may take me a few days. = =A0However, we would really like to have someone besides Doug working on the timezo= ne effort. =A0So, I think it would be excellent that you get involved as w= ell. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 |-------------------------+-------------------------+------------------= -------| | | Damon Chaplin | = | | | | =A0 =A0 =A0 =A0= To: | | | Sent by: | "ietf-calendar@= imc.org| | | owner-ietf-calendar@ma| " = | | | il.imc.org | = | | | 12/14/00 03:11 PM | =A0 =A0 =A0 =A0= cc: | | | | =A0 =A0 =A0 =A0= Subject: | | | | converting Olso= n | | | | timezone databa= se to | | | | VTIMEZONEs = | |-------------------------+-------------------------+------------------= -------| 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 = --0__=y9djq3ju5rJhuhYYpyQTJNlp1hIYKtYHuQmz4Q6u8jcOWuMZMJrqA36I-- From owner-ietf-calendar@mail.imc.org Sun Jan 14 03:24:04 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02698 for ; Sun, 14 Jan 2001 03:24:03 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA07628 for ietf-calendar-bks; Sat, 13 Jan 2001 23:54:56 -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 XAA07618 for ; Sat, 13 Jan 2001 23:54:53 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA29955 for ietf-calendar@imc.org; Sun, 14 Jan 2001 00:00:03 -0800 (PST) Date: Sun, 14 Jan 2001 00:00:03 -0800 (PST) From: Doug Royer Message-Id: <200101140800.AAA29955@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 Jan 14 13:45:41 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09856 for ; Sun, 14 Jan 2001 13:45:41 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA20629 for ietf-calendar-bks; Sun, 14 Jan 2001 10:15:35 -0800 (PST) Received: from exchange.parex.co.nz ([203.167.234.98]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA20620 for ; Sun, 14 Jan 2001 10:15:27 -0800 (PST) From: dsadlp@fmcc.se To: Date: Sun, 14 Jan 2001 09:36:09 Message-Id: <82.418166.590458@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 150 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 Jan 16 09:40:17 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA13199 for ; Tue, 16 Jan 2001 09:40:17 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA00408 for ietf-calendar-bks; Tue, 16 Jan 2001 06:12:22 -0800 (PST) Received: from mail6.svr.pol.co.uk (mail6.svr.pol.co.uk [195.92.193.212]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA00403 for ; Tue, 16 Jan 2001 06:12:19 -0800 (PST) Received: from modem-90.heniochus.dialup.pol.co.uk ([62.137.26.90] helo=ximian.com) by mail6.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14IWvm-0005Em-00 for ietf-calendar@imc.org; Tue, 16 Jan 2001 14:17:50 +0000 Message-ID: <3A6449C9.64B2D023@ximian.com> Date: Tue, 16 Jan 2001 13:16:57 +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: Re: converting Olson timezone database to VTIMEZONEs References: <862569D3.00603778.00@passnotes.share.org> 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 first go at the Olson -> VTIMEZONE conversion app is here: http://www.karuna.freeserve.co.uk/vzic.tgz The VTIMEZONE output is here: http://www.karuna.freeserve.co.uk/vtimezones.tgz Don't rely on the output too much yet! I haven't checked it at all. Comments welcome. Damon From owner-ietf-calendar@mail.imc.org Wed Jan 17 00:37:29 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA00727 for ; Wed, 17 Jan 2001 00:37:29 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id VAA13998 for ietf-calendar-bks; Tue, 16 Jan 2001 21:13:31 -0800 (PST) Received: from zeus.amt.co.kr ([203.248.62.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id VAA13994 for ; Tue, 16 Jan 2001 21:13:29 -0800 (PST) From: bk12bk27@yahoo.com Received: from max1-34.losangeles.corecomm.net by zeus.amt.co.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id DDA0T52D; Wed, 17 Jan 2001 11:41:29 +0900 DATE: 16 Jan 01 6:45:28 PM Message-ID: SUBJECT: RE; THANK YOU Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Dear Friend and Partner, Think of all the things you could do if you had more free time and money wasn't an object What kind of car would you be driving? Where would you live? Where would you go on vacation? Now, for a limited time, 300+ money making and saving secrets can be yours for less than $10.00. Click here http://www.300moneysecrets.com/ and ORDER NOW!!!!!!!!!!!!!! Get information now, that could make you millions!!!! ** REMOVE ** REMOVE ** REMOVE ** REMOVE ** REMOVE ** To be removed from our mailing list, please email sandywho1212@yahoo.com All REMOVE requests AUTOMATICALLY honored upon receipt. PLEASE understand that any effort to disrupt, close or block this REMOVE account can only result in difficulties for others wanting to be removed from our mailing list as it will be impossible to take anyone off the list if the remove instruction can not be received. From owner-ietf-calendar@mail.imc.org Fri Jan 19 00:58:23 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA12229 for ; Fri, 19 Jan 2001 00:58:23 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id VAA23976 for ietf-calendar-bks; Thu, 18 Jan 2001 21:24:53 -0800 (PST) Received: from teapot21.domain3.bigpond.com (teapot21.domain3.bigpond.com [139.134.5.159]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id VAA23972 for ; Thu, 18 Jan 2001 21:24:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by teapot21.domain3.bigpond.com (NTMail 3.02.13) with ESMTP id ya381340 for ; Fri, 19 Jan 2001 15:18:50 +1000 Received: from LDIP-T-009-p-63-76.tmns.net.au ([203.54.63.76]) by mail3.bigpond.com (Claudes-Bashful-MailRouter V2.9c 5/282033); 19 Jan 2001 15:18:49 Reply-To: From: "Simon Mackay" To: "Ietf-Calendar (E-mail)" Subject: vCalendar and iCalendar support Date: Fri, 19 Jan 2001 15:54:42 +1100 Message-ID: <004e01c081d7$b8241ca0$4c3f36cb@simonmac> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01C08233.EBACFEA0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_004F_01C08233.EBACFEA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi everyone! Does anyone know which programs or hardware PDAs other than Microsoft Outlook do support vCalendar or iCalendar whether natively or through the use of a plugin? Also has anyone bothered to distribute VB or C++ source code for people to integrate basic vCalendar / iCalendar support in their programs? With regards, Simon Mackay ------=_NextPart_000_004F_01C08233.EBACFEA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=20 everyone!
 
Does = anyone know=20 which programs or hardware PDAs other than Microsoft Outlook=20 do support vCalendar or iCalendar whether natively or through = the use=20 of a plugin? Also has anyone bothered to distribute VB or C++ source = code for=20 people to integrate basic vCalendar / iCalendar support in their=20 programs?
 
With=20 regards,
 
Simon=20 Mackay
------=_NextPart_000_004F_01C08233.EBACFEA0-- From owner-ietf-calendar@mail.imc.org Fri Jan 19 02:22:16 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA25646 for ; Fri, 19 Jan 2001 02:22:15 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id WAA26940 for ietf-calendar-bks; Thu, 18 Jan 2001 22:58:03 -0800 (PST) Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA26923 for ; Thu, 18 Jan 2001 22:58:00 -0800 (PST) From: Frank.Dawson@nokia.com Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87]) by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f0J73gR23117 for ; Fri, 19 Jan 2001 01:03:47 -0600 (CST) Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Fri, 19 Jan 2001 01:03:39 -0600 Received: by daebh02nok with Internet Mail Service (5.5.2652.78) id ; Fri, 19 Jan 2001 01:03:39 -0600 Message-ID: <30F2DED23724D311902D0008C7EABAFB0361F87B@daeis06nok> To: Simon_Mackay@bigpond.com, ietf-calendar@imc.org Subject: RE: vCalendar and iCalendar support Date: Fri, 19 Jan 2001 00:57:07 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C081E5.09663140" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C081E5.09663140 Content-Type: text/plain; charset="iso-8859-1" Simon, Hei! Of course vCard and vCalendar has widespread support in the mobile phone/handset community. Nokia GSM phones leverage vCard and vCalendar for exchange of phone book and calendar information. Please refer to the SmartMessaging specification found in the http://www.forum.nokia.com website for details on the open and free SmartMessaging license. -- Frank Does anyone know which programs or hardware PDAs other than Microsoft Outlook do support vCalendar or iCalendar whether natively or through the use of a plugin? Also has anyone bothered to distribute VB or C++ source code for people to integrate basic vCalendar / iCalendar support in their programs? ------_=_NextPart_001_01C081E5.09663140 Content-Type: text/html; charset="iso-8859-1"
Simon, Hei!
 
Of course vCard and vCalendar has widespread support in the mobile phone/handset community. Nokia GSM phones leverage vCard and vCalendar for exchange of phone book and calendar information. Please refer to the SmartMessaging specification found in the http://www.forum.nokia.com website for details on the open and free SmartMessaging license.
 
-- Frank
Does anyone know which programs or hardware PDAs other than Microsoft Outlook do support vCalendar or iCalendar whether natively or through the use of a plugin? Also has anyone bothered to distribute VB or C++ source code for people to integrate basic vCalendar / iCalendar support in their programs? 
------_=_NextPart_001_01C081E5.09663140-- From owner-ietf-calendar@mail.imc.org Fri Jan 19 05:34:20 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA26882 for ; Fri, 19 Jan 2001 05:34:19 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id CAA26888 for ietf-calendar-bks; Fri, 19 Jan 2001 02:09:24 -0800 (PST) Received: from obilonpxy.onboardinfo.lan ([62.189.17.22]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id CAA26883 for ; Fri, 19 Jan 2001 02:09:21 -0800 (PST) Received: FROM obilonmsx01.onboardinfo.com BY obilonpxy.onboardinfo.lan ; Fri Jan 19 10:08:49 2001 0000 Received: by obilonmsx01.onboardinfo.com with Internet Mail Service (5.5.2650.21) id ; Fri, 19 Jan 2001 10:09:57 -0000 Message-ID: <218AEB5F048FD411B97000B0D03EAC2E27BE55@obilonmsx01.onboardinfo.com> From: Isaac Hepworth To: "'Simon_Mackay@bigpond.com'" , "'Ietf-Calendar (E-mail)'" Subject: RE: vCalendar and iCalendar support Date: Fri, 19 Jan 2001 10:09:49 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > Does anyone know which programs or hardware PDAs > other than Microsoft Outlook do support vCalendar Try http://www.imc.org/pdi/pdiprodslist.html > Also has anyone bothered to distribute VB or C++ source > code for people to integrate basic vCalendar / iCalendar support There's an SDK here http://www.imc.org/pdi/pdiproddev.html -----Original Message----- From: Simon Mackay [mailto:Simon_Mackay@bigpond.com] Sent: 19 January 2001 04:55 To: Ietf-Calendar (E-mail) Subject: vCalendar and iCalendar support Hi everyone! Does anyone know which programs or hardware PDAs other than Microsoft Outlook do support vCalendar or iCalendar whether natively or through the use of a plugin? Also has anyone bothered to distribute VB or C++ source code for people to integrate basic vCalendar / iCalendar support in their programs? With regards, Simon Mackay From owner-ietf-calendar@mail.imc.org Fri Jan 19 09:07:22 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29297 for ; Fri, 19 Jan 2001 09:07:20 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id FAA14856 for ietf-calendar-bks; Fri, 19 Jan 2001 05:39:44 -0800 (PST) Received: from teapot28.domain6.bigpond.com (teapot28.domain6.bigpond.com [139.134.5.197]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id FAA14851 for ; Fri, 19 Jan 2001 05:39:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by teapot28.domain6.bigpond.com (NTMail 3.02.13) with ESMTP id wa599270 for ; Fri, 19 Jan 2001 23:36:24 +1000 Received: from LDIP-T-011-p-65-208.tmns.net.au ([203.54.65.208]) by mail6.bigpond.com (Claudes-Eccentric-MailRouter V2.9c 11/421878); 19 Jan 2001 23:36:23 Reply-To: From: "Simon Mackay" To: "Ietf-Calendar (E-mail)" Subject: A very noticeable omission for software support Date: Fri, 19 Jan 2001 22:39:09 +1100 Message-ID: <000b01c0821d$3acc3da0$d04136cb@simonmac> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C08279.6E65E880" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C08279.6E65E880 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi everyone! I had looked at the list of software that supports vCalendar and iCalendar and there is one noticeable omission regarding the support of these technologies, whether natively or through a plug-in. It happens to be Lotus Notes. This program is often favoured in a lot of mainstream corporations as a "workflow" program and also ends up being used as a desktop PDA program on these sites. Are there going to be any plug-ins available that allow Lotus Notes users to import and export vCard and vCalendar data so that they can easily exchange contact and appointment details with people who use other PDA programs that use these standards? With regards, Simon Mackay ------=_NextPart_000_000C_01C08279.6E65E880 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=20 everyone!
 
I had = looked at the=20 list of software that supports vCalendar and iCalendar and there is one=20 noticeable omission regarding the support of these technologies, whether = natively or through a plug-in. It happens to be Lotus Notes. This = program is=20 often favoured in a lot of mainstream corporations as a "workflow" = program and=20 also ends up being used as a desktop PDA program on these sites.=20
 
Are = there going to=20 be any plug-ins available that allow Lotus Notes users to import and = export=20 vCard and vCalendar data so that they can easily exchange contact and=20 appointment details with people who use other PDA programs = that use=20 these standards?
 
With=20 regards,
 
Simon=20 Mackay 
------=_NextPart_000_000C_01C08279.6E65E880-- From owner-ietf-calendar@mail.imc.org Fri Jan 19 09:48:11 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29811 for ; Fri, 19 Jan 2001 09:48:10 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA17208 for ietf-calendar-bks; Fri, 19 Jan 2001 06:19:50 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA17203 for ; Fri, 19 Jan 2001 06:19:48 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f0JEUme13595 for ; Fri, 19 Jan 2001 09:30:49 -0500 Message-ID: <3A684F95.2C36EACB@ecal.com> Date: Fri, 19 Jan 2001 09:30:45 -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 (E-mail)" Subject: Re: vCalendar and iCalendar support References: <004e01c081d7$b8241ca0$4c3f36cb@simonmac> 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 Simon Mackay wrote: > Also has anyone bothered to distribute VB or C++ source code > for people to integrate basic vCalendar / iCalendar support in > their programs? http://www.softwarestudio.org/libical/ -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |If God had meant us to be in the Army, we | |francis@ecal.com|would've been born with green, baggy skin. | \==============================================================/ From owner-ietf-calendar@mail.imc.org Fri Jan 19 10:00:12 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA00059 for ; Fri, 19 Jan 2001 10:00:12 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA18154 for ietf-calendar-bks; Fri, 19 Jan 2001 06:32:37 -0800 (PST) Received: from prd116.cs.ctc (mail.cantire.com [207.61.17.3] (may be forged)) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA18149 for ; Fri, 19 Jan 2001 06:32:36 -0800 (PST) From: brian.capstick@cantire.com Received: from admin1.cs.ctc ([42.2.30.59]) by prd116.cs.ctc (Lotus Domino Release 5.0.3) with ESMTP id 2001011909364830:2362 ; Fri, 19 Jan 2001 09:36:48 -0500 Subject: Re: A very noticeable omission for software support To: ietf-calendar@imc.org Cc: Simon_Mackay@bigpond.com X-Mailer: Lotus Notes Release 5.0.3 March 21, 2000 Message-ID: Date: Fri, 19 Jan 2001 09:37:31 -0500 MIME-Version: 1.0 X-MIMETrack: Serialize by Router on ADMIN1/H/CTR/CTC(Release 5.0.5 |September 22, 2000) at 01/19/2001 09:38:06 AM, Itemize by SMTP Server on SMTP1/M/CTR/CTC(Release 5.0.3 |March 21, 2000) at 01/19/2001 09:36:48 AM, Serialize by Router on SMTP1/M/CTR/CTC(Release 5.0.3 |March 21, 2000) at 01/19/2001 09:37:24 AM, Serialize complete at 01/19/2001 09:37:24 AM Content-type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from quoted-printable to 8bit by ns.secondary.com id GAA18150 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 GAA18154 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA00059 vCard exists for Lotus Notes now. If you go to the website http://www.notes.net and enter the 'Iris Sandbox' you will see a download there called vCard. Once installed it gives you the ability to process vCards from within Notes. I have not seen or heard from Lotus whether this will be added natively to their product. Brian Capstick "Simon Mackay" Sent by: cc: owner-ietf-calendar@ma Subject: A very noticeable omission for software il.imc.org support 01/19/2001 06:39 AM Please respond to Simon_Mackay Hi everyone! I had looked at the list of software that supports vCalendar and iCalendar and there is one noticeable omission regarding the support of these technologies, whether natively or through a plug-in. It happens to be Lotus Notes. This program is often favoured in a lot of mainstream corporations as a "workflow" program and also ends up being used as a desktop PDA program on these sites. Are there going to be any plug-ins available that allow Lotus Notes users to import and export vCard and vCalendar data so that they can easily exchange contact and appointment details with people who use other PDA programs that use these standards? With regards, Simon Mackay From owner-ietf-calendar@mail.imc.org Fri Jan 19 11:30:39 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01707 for ; Fri, 19 Jan 2001 11:30:38 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA26719 for ietf-calendar-bks; Fri, 19 Jan 2001 08:04:21 -0800 (PST) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA26714 for ; Fri, 19 Jan 2001 08:04:20 -0800 (PST) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.10.0/8.10.0) with ESMTP id f0JG9ZG23847 for ; Fri, 19 Jan 2001 08:09:35 -0800 (PST) Received: from netscape.com ([198.93.95.152]) by dredd.mcom.com (Netscape Messaging Server 4.15 dredd Jun 22 2000 16:29:39) with ESMTP id G7F3JZ00.CZS; Fri, 19 Jan 2001 08:09:35 -0800 Message-ID: <3A6866F3.43061A35@netscape.com> Date: Fri, 19 Jan 2001 08:10:27 -0800 From: sman@netscape.com (Steve Mansour) X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Simon_Mackay@bigpond.com CC: "Ietf-Calendar (E-mail)" Subject: Re: vCalendar and iCalendar support References: <004e01c081d7$b8241ca0$4c3f36cb@simonmac> Content-Type: multipart/mixed; boundary="------------0EC6F972B2674787946E1E3D" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------0EC6F972B2674787946E1E3D Content-Type: multipart/alternative; boundary="------------7823D8D098DC1240B4F5C640" --------------7823D8D098DC1240B4F5C640 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, iPlanet's calendar server supports iCalendar and a subset of iTIP and iMIP. Check out http://docs.iplanet.com/docs/manuals/calendar.html -Steve Simon Mackay wrote: > Hi everyone!Does anyone know which programs or hardware PDAs other > than Microsoft Outlook do support vCalendar or iCalendar whether > natively or through the use of a plugin? Also has anyone bothered to > distribute VB or C++ source code for people to integrate basic > vCalendar / iCalendar support in their programs?With regards,Simon > Mackay --------------7823D8D098DC1240B4F5C640 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

iPlanet's calendar server supports iCalendar and a subset of iTIP and iMIP.  Check out http://docs.iplanet.com/docs/manuals/calendar.html

-Steve

Simon Mackay wrote:

 Hi everyone!Does anyone know which programs or hardware PDAs other than Microsoft Outlook do support vCalendar or iCalendar whether natively or through the use of a plugin? Also has anyone bothered to distribute VB or C++ source code for people to integrate basic vCalendar / iCalendar support in their programs?With regards,Simon Mackay
--------------7823D8D098DC1240B4F5C640-- --------------0EC6F972B2674787946E1E3D Content-Type: text/x-vcard; charset=us-ascii; name="sman.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Steve Mansour Content-Disposition: attachment; filename="sman.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Mansour;Steve tel;work:408-276-4268 x-mozilla-html:FALSE org:;Netscape adr:;;;;;; version:2.1 email;internet:sman@netscape.com title:Judge, Jury, and Executioner fn:Steve Mansour end:vcard --------------0EC6F972B2674787946E1E3D-- From owner-ietf-calendar@mail.imc.org Fri Jan 19 12:00:13 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA02347 for ; Fri, 19 Jan 2001 12:00:13 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA28189 for ietf-calendar-bks; Fri, 19 Jan 2001 08:33:05 -0800 (PST) Received: from guanabana.helixcode.com (IDENT:root@[132.248.10.190]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA28185 for ; Fri, 19 Jan 2001 08:33:02 -0800 (PST) Received: (from federico@localhost) by guanabana.helixcode.com (8.9.3/8.9.3) id KAA20545; Fri, 19 Jan 2001 10:47:13 -0600 Date: Fri, 19 Jan 2001 10:47:13 -0600 Message-Id: <200101191647.KAA20545@guanabana.helixcode.com> X-Authentication-Warning: guanabana.helixcode.com: federico set sender to federico@ximian.com using -f From: Federico Mena Quintero X-perience: what you needed right before obtaining it To: Cc: "Ietf-Calendar (E-mail)" Subject: Re: vCalendar and iCalendar support References: <004e01c081d7$b8241ca0$4c3f36cb@simonmac> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: "Simon Mackay" writes: > Does anyone know which programs or hardware PDAs other than Microsoft > Outlook do support vCalendar or iCalendar whether natively or through the > use of a plugin? Also has anyone bothered to distribute VB or C++ source > code for people to integrate basic vCalendar / iCalendar support in their > programs? The calendar in the Evolution groupware suite uses iCalendar. We will support importing vCalendar data in the future; it actually used vCalendar from when the Evolution calendar was the Gnomecal program, but we upgraded it to use iCalendar instead. It uses Eric Busboom's libical for its backend stuff. Federico From owner-ietf-calendar@mail.imc.org Sun Jan 21 03:28:15 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03262 for ; Sun, 21 Jan 2001 03:28:15 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA20368 for ietf-calendar-bks; Sat, 20 Jan 2001 23:54:22 -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 XAA20352 for ; Sat, 20 Jan 2001 23:54:19 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA10424 for ietf-calendar@imc.org; Sun, 21 Jan 2001 00:00:03 -0800 (PST) Date: Sun, 21 Jan 2001 00:00:03 -0800 (PST) From: Doug Royer Message-Id: <200101210800.AAA10424@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 Mon Jan 22 11:05:21 2001 Received: from ns.secondary.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07392 for ; Mon, 22 Jan 2001 11:05:20 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id HAA22879 for ietf-calendar-bks; Mon, 22 Jan 2001 07:34:57 -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 HAA22867 for ; Mon, 22 Jan 2001 07:34:44 -0800 (PST) From: pregen@egenconsulting.com To: brian.capstick@cantire.com Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org, Simon_Mackay@bigpond.com Subject: Re: A very noticeable omission for software support X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Mon, 22 Jan 2001 15:40:40 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 01/22/2001 10:40:55 AM, Serialize complete at 01/22/2001 10:40:55 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 003AE395802569DC_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 003AE395802569DC_= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At Lotusphere last week, Lotus announced iCalendar support for Notes=20 R"Next" due sometime in the future (hopefully this year). =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Patricia Egen Consulting www.egenconsulting.com 423-875-2652 brian.capstick@cantire.com Sent by: owner-ietf-calendar@mail.imc.org 01/19/01 02:37 PM =20 To: ietf-calendar@imc.org cc: Simon=5FMackay@bigpond.com Subject: Re: A very noticeable omission for software support vCard exists for Lotus Notes now. If you go to the website http://www.notes.net and enter the 'Iris Sandbox' you will see a download there called vCard. Once installed it gives you the ability to process vCards from within Notes. I have not seen or heard from Lotus whether this will be added natively to their product. Brian Capstick =20 "Simon Mackay" =20 = =20 Sent by: cc: =20 owner-ietf-calendar@ma Subject: A very=20 noticeable omission for software=20 il.imc.org support =20 =20 =20 01/19/2001 06:39 AM =20 Please respond to =20 Simon=5FMackay =20 =20 =20 Hi everyone! I had looked at the list of software that supports vCalendar and=20 iCalendar and there is one noticeable omission regarding the support of these technologies, whether natively or through a plug-in. It happens to be Lotus Notes. This program is often favoured in a lot of mainstream corporations as a "workflow" program and also ends up being used as a desktop PDA program on these sites. Are there going to be any plug-ins available that allow Lotus Notes users to import and export vCard and vCalendar data so that they can easily exchange contact and appointment details with=A0people who use other PDA=A0programs that use these standards? With regards, Simon Mackay --=_alternative 003AE395802569DC_= Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
At Lotusphere last week, Lotus annou= nced iCalendar support for Notes R"Next" due sometime in the futu= re (hopefully this year).
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


brian.capstick@cantire.com
Sent by: owner-ietf-calendar@mail.im= c.org

01/19/01 02:37 PM

       
        To: &nbs= p;      ietf-calendar@imc.org
        cc: &nbs= p;      Simon=5FMackay@bigpond.com
        Subject:=        Re: A very noticeable omission for software sup= port




vCard exists for Lotus Notes now. If you go to the website
http://www.notes.net and enter the 'Iris Sandbox' you will see a download there called vCard. Once installed it gives you the ability to process
vCards from within Notes. I have not seen or heard from Lotus whether this<= br> will be added natively to their product.

Brian Capstick



                    &nbs= p;                     &n= bsp;                     =                      = ;                
                   "= ;Simon Mackay"                =                     &nbs= p;                     &n= bsp;        
                   <S= imon=5FMackay@bigpond.        To:     "I= etf-Calendar (E-mail)"              = ;      
                   com&g= t;                     &n= bsp;    <ietf-calendar@imc.org>        =                     &nbs= p;
                   Sent = by:                     &= nbsp;cc:                   &nb= sp;                     &= nbsp;        
                   owner= -ietf-calendar@ma        Subject:     A very = noticeable omission for software
                   il.im= c.org                    = support                   &nbs= p;                     &n= bsp;    
                    &nbs= p;                     &n= bsp;                     =                      = ;                
                    &nbs= p;                     &n= bsp;                     =                      = ;                
                   01/19= /2001 06:39 AM                 &nbs= p;                     &n= bsp;                     =    
                   Pleas= e respond to                  =                     &nbs= p;                     &n= bsp;    
                   Simon= =5FMackay                   &n= bsp;                     =                      = ;        
                    &nbs= p;                     &n= bsp;                     =                      = ;                
                    &nbs= p;                     &n= bsp;                     =                      = ;                





Hi  everyone!

I had looked at the  list of software that supports vCalendar and iCal= endar
and there is one  noticeable omission regarding the support of these technologies, whether  natively or through a plug-in. It happens to be=
Lotus Notes. This program is  often favoured in a lot of mainstream
corporations as a "workflow" program and  also ends up being= used as a
desktop PDA program on these sites.

Are there going to  be any plug-ins available that allow Lotus Notes u= sers
to import and export  vCard and vCalendar data so that they can easily=
exchange contact and  appointment details with=A0people who use other<= br> PDA=A0programs that use  these standards?

With  regards,

Simon  Mackay

--=_alternative 003AE395802569DC_=-- From owner-ietf-calendar@mail.imc.org Thu Jan 25 01:10:50 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA08726 for ; Thu, 25 Jan 2001 01:10:49 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id VAA06980 for ietf-calendar-bks; Wed, 24 Jan 2001 21:41:41 -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 VAA06973 for ; Wed, 24 Jan 2001 21:41:34 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Subject: IPTEL spec and iCalendar X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Thu, 25 Jan 2001 05:47:36 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 01/25/2001 12:47:52 AM, Serialize complete at 01/25/2001 12:47:52 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 00049CC5802569DF_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 00049CC5802569DF_= Content-Type: text/plain; charset="us-ascii" The IESG is reviewing the draft-ietf-iptel-cpl draft, which uses iCal time spec for occurances of events. They use a subset of the iCal specification and we need to know if this is valid. Basically, if the phone people have problems with the spec, we in the calendar group also should have problems. We need to have people on the list go look at the draft "draft-ietf-iptel-cpl" and see if we see potential problems/issues. We have been asked if we handled recurrence rules during interoperability testing. I told our AD that this was not done in the first pass. WE know recurrence rules are going to be a challenge. Here's probably yet another one as well. Also, if anyone can provide a brief description of what part of recurrence rules must be implented to be compliant with ical, it would be helpful. I'll forward that on to the iptel people. Thanks for your help. --=_alternative 00049CC5802569DF_= Content-Type: text/html; charset="us-ascii"
The IESG is reviewing the draft-ietf-iptel-cpl draft, which uses iCal time spec for occurances of events. They use a subset of the iCal specification and we need to know if this is valid. Basically, if the phone people have problems with the spec, we in the calendar group also should have problems.

We need to have people on the list go look at the draft "draft-ietf-iptel-cpl" and see if we see potential problems/issues.

We have been asked if we handled recurrence rules during interoperability testing.  I told our AD that this was not done in the first pass.  WE know recurrence rules are going to be a challenge.  Here's probably yet another one as well.

Also, if anyone can provide a brief description of what part of recurrence rules must be implented to be compliant with ical, it would be helpful.  I'll forward that on to the iptel people.

Thanks for your help.
 --=_alternative 00049CC5802569DF_=-- From owner-ietf-calendar@mail.imc.org Thu Jan 25 02:33:01 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21700 for ; Thu, 25 Jan 2001 02:33:00 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id XAA14754 for ietf-calendar-bks; Wed, 24 Jan 2001 23:11:59 -0800 (PST) Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id XAA14746 for ; Wed, 24 Jan 2001 23:11:58 -0800 (PST) Received: from sj-msg-av-2.cisco.com (sj-msg-av-2.cisco.com [171.71.163.110]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id XAA08545; Wed, 24 Jan 2001 23:17:55 -0800 (PST) Received: from mailman.cisco.com (localhost [127.0.0.1]) by sj-msg-av-2.cisco.com (8.10.1/8.10.1) with ESMTP id f0P7Hem28196; Wed, 24 Jan 2001 23:17:40 -0800 (PST) Received: from [193.0.4.72] (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id XAA15262; Wed, 24 Jan 2001 23:17:37 -0800 (PST) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: References: Date: Thu, 25 Jan 2001 08:16:14 +0100 To: pregen@egenconsulting.com, ietf-calendar@imc.org From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: Re: IPTEL spec and iCalendar Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 XAA14754 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA21700 At 05.47 +0000 01-01-25, pregen@egenconsulting.com wrote: >We need to have people on the list go look at the draft >"draft-ietf-iptel-cpl" and see if we see potential problems/issues. It is extremely important that this is done in a timely fashion. The document has passed last call in the IETF, and I as AD was suprised that noone from this wg did send in any comments. The spec do use your specification, and you should have _some_ comments I thought. Anyway, because of this, I personally blocked the document in the IESG until I get comments from you in this wg. I expect comments no later than tuesday next week, or I have to make a decision that "no comments" from this wg during last call really means that you don't feel we might end up in interoperability problems in the future between ical and cpl applications. Patrik -- Patrik Fältström Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC From owner-ietf-calendar@mail.imc.org Thu Jan 25 10:59:36 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA02403 for ; Thu, 25 Jan 2001 10:59:34 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id HAA05046 for ietf-calendar-bks; Thu, 25 Jan 2001 07:37:11 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA05041 for ; Thu, 25 Jan 2001 07:37:09 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f0PFmoW04626 for ; Thu, 25 Jan 2001 10:48:50 -0500 Message-ID: <3A704AE0.FD8F4C21@ecal.com> Date: Thu, 25 Jan 2001 10:48:48 -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: IPTEL spec and iCalendar References: 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 HAA05046 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA02403 Patrik Fältström wrote: > It is extremely important that this is done in a timely fashion. The > document has passed last call in the IETF, and I as AD was suprised > that noone from this wg did send in any comments. Was there a mechanism to tell us that it used iCalendar? Near as I can tell, it was not mentioned on the calsch list; and I don't think the I-D announcements mention what specs the draft references. So, to catch everything that references iCalendar, we'd have to read all the I-Ds that come out; I don't think any of us has time for that. I don't mean to be argumentative; I will go and read it now. I just don't think it's surprising that we didn't catch it earlier. -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |"The Elliot 903 was the first portable I ever | |francis@ecal.com|used, though it needed a furniture van to *make*| | |it portable." --Will Rose | \=================================================================/ From owner-ietf-calendar@mail.imc.org Thu Jan 25 11:39:03 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03477 for ; Thu, 25 Jan 2001 11:39:03 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA08397 for ietf-calendar-bks; Thu, 25 Jan 2001 08:17:24 -0800 (PST) Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA08390 for ; Thu, 25 Jan 2001 08:17:23 -0800 (PST) Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com [171.69.2.19]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id IAA15593; Thu, 25 Jan 2001 08:23:24 -0800 (PST) Received: from mailman.cisco.com (localhost [127.0.0.1]) by sj-msg-av-3.cisco.com (8.10.1/8.10.1) with ESMTP id f0PGNAh19879; Thu, 25 Jan 2001 08:23:10 -0800 (PST) Received: from [193.0.4.72] (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id IAA24829; Thu, 25 Jan 2001 08:23:01 -0800 (PST) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: <3A704AE0.FD8F4C21@ecal.com> References: <3A704AE0.FD8F4C21@ecal.com> Date: Thu, 25 Jan 2001 17:15:25 +0100 To: John Stracke , ietf-calendar@imc.org From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: Re: IPTEL spec and iCalendar Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 IAA08397 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA03477 At 10.48 -0500 01-01-25, John Stracke wrote: >Was there a mechanism to tell us that it used iCalendar? Near as I can >tell, it was not mentioned on the calsch list; and I don't think the I-D >announcements mention what specs the draft references. So, to catch >everything that references iCalendar, we'd have to read all the I-Ds that >come out; I don't think any of us has time for that. Grep is your friend. You (in the most undefined way possible) is a wg which defined Calendar properties for use on the Internet. If I were you, I would check all different wg's and I-D's for any kind of references to the definitions you use, or where what you have done could be used. There are reasons we have an IETF wide last call. Who should else do it? >I don't mean to be argumentative; I will go and read it now. Thanks. paf -- Patrik Fältström Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC From owner-ietf-calendar@mail.imc.org Thu Jan 25 12:07:05 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04233 for ; Thu, 25 Jan 2001 12:07:05 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA09136 for ietf-calendar-bks; Thu, 25 Jan 2001 08:32:47 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA09131 for ; Thu, 25 Jan 2001 08:32:45 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f0PGiQW04750 for ; Thu, 25 Jan 2001 11:44:26 -0500 Message-ID: <3A7057EA.F6D43876@ecal.com> Date: Thu, 25 Jan 2001 11:44:26 -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: IPTEL spec and iCalendar References: <3A704AE0.FD8F4C21@ecal.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 IAA09136 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA04233 Patrik Fältström wrote: > At 10.48 -0500 01-01-25, John Stracke wrote: > >Was there a mechanism to tell us that it used iCalendar? > > Grep is your friend. Point taken. :-) I'll dust off the procmail manpage. -- /=================================================================\ |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 Jan 25 12:07:11 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04234 for ; Thu, 25 Jan 2001 12:07:05 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id IAA09123 for ietf-calendar-bks; Thu, 25 Jan 2001 08:32:04 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA09118 for ; Thu, 25 Jan 2001 08:32:02 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f0PGhhW04746 for ; Thu, 25 Jan 2001 11:43:43 -0500 Message-ID: <3A7057BB.61B60245@ecal.com> Date: Thu, 25 Jan 2001 11:43:39 -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: IPTEL spec and iCalendar 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: > The IESG is reviewing the draft-ietf-iptel-cpl draft, which > uses iCal time spec for occurances of events. They use a subset > of the iCal specification and we need to know if this is valid. > Basically, if the phone people have problems with the spec, we > in the calendar group also should have problems. OK, some points: * They use DATE-TIME values in their "time nodes", but specify that they may not contain the timezone, since the timezone is specified at a higher level. I think this is probably OK. * They do not actually reference the iCalendar recurrence rule spec; they define their own which imitates it, except: o In order to make sure that no two instances of an event overlap, they: + forbid the duration of a repeating event to be greater than 24 hours, + forbid "freq" to be "secondly", "minutely", or "hourly", + do not support "bysecond", "byminute", "byhour". o In order to make sure they can evaluate the expression in O(1) time, they do not support "count" or "bysetpos". + The problem is that, in order to apply count or bysetpos, you have to expand the recurrence set, which could take an arbitrary length of time. I think these changes may be reasonable for the problem domain they were trying to solve, but it is certainly not compatible with iCalendar. > Also, if anyone can provide a brief description of what part of > recurrence rules must be implented to be compliant with ical, > it would be helpful. Um...it's all of them, isn't it? This is potentially a problem. The motivation they give for using the iCalendar model is: This allows CPLs to be generated automatically from calendar books. It also allows us to re-use the extensive existing work specifying time intervals. Clearly, if they don't support the full RRULE syntax, they can't meet the first goal. Forbidding the sub-day recurrences may be OK (they're unlikely to be used often), but count and bysetpos are likely to be used regularly. To translate such a repeating event into a CPL, one would have to enumerate all the instances. On the other hand, for code that's meant to run in telephony switches, that may be better than supporting rules that take O(N) time to evaluate. But what they *could* do is support count and bysetpos, and enumerate the instances once, when the CPL is loaded, rather than each time it's executed. In the reverse direction--CPLs being turned into iCalendar objects--I don't see a problem; it's a subset. However, there will be a problem if they go from iCalendar to CPL and back; if the original iCalendar object uses count or bysetpos, then the one generated from the CPL will be expanded with a long list of RDATEs rather than being the original rule. This means that, if you want to use something that manipulates iCalendar to edit your CPLs, things are going to work sort of OK when you first create the CPL, but get messy when you go back and edit it. Also, one nit: they keep referring to iCalendar as "iCal". Not important--certainly not important enough to hold up the Draft on its own--but it'd be nice to change if other changes are going to be made anyway. -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |Do not suspect that I am not human. | |francis@ecal.com| | \==============================================================/ From owner-ietf-calendar@mail.imc.org Thu Jan 25 13:16:46 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05415 for ; Thu, 25 Jan 2001 13:16:45 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA15720 for ietf-calendar-bks; Thu, 25 Jan 2001 09:56:39 -0800 (PST) Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA15714 for ; Thu, 25 Jan 2001 09:56:38 -0800 (PST) Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com [171.69.2.19]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id KAA23083; Thu, 25 Jan 2001 10:02:40 -0800 (PST) Received: from mailman.cisco.com (localhost [127.0.0.1]) by sj-msg-av-3.cisco.com (8.10.1/8.10.1) with ESMTP id f0PI2Ox07752; Thu, 25 Jan 2001 10:02:24 -0800 (PST) Received: from [193.0.4.72] (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id KAA14100; Thu, 25 Jan 2001 10:02:17 -0800 (PST) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: <3A7057BB.61B60245@ecal.com> References: <3A7057BB.61B60245@ecal.com> Date: Thu, 25 Jan 2001 18:38:32 +0100 To: John Stracke , ietf-calendar@imc.org From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: Re: IPTEL spec and iCalendar Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 JAA15720 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA05415 At 11.43 -0500 01-01-25, John Stracke wrote: >Also, one nit: they keep referring to iCalendar as "iCal". Not >important--certainly not important enough to hold up the Draft on >its own--but it'd be nice to change if other changes are going to >be made anyway. This is easy. Changes like this I can request at the RFC Editor. Remember: Don't filter what you think is needed changed or not. Let me know everything you want changed, why, and of course with weights. The rest I don't comment on. I let you on the list think about it. Good comments, and exactly what I found :-) paf -- Patrik Fältström Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC From owner-ietf-calendar@mail.imc.org Thu Jan 25 13:17:49 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05432 for ; Thu, 25 Jan 2001 13:17:48 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA15708 for ietf-calendar-bks; Thu, 25 Jan 2001 09:56:36 -0800 (PST) Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA15701 for ; Thu, 25 Jan 2001 09:56:35 -0800 (PST) Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com [171.69.2.19]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id KAA22939; Thu, 25 Jan 2001 10:02:33 -0800 (PST) Received: from mailman.cisco.com (localhost [127.0.0.1]) by sj-msg-av-3.cisco.com (8.10.1/8.10.1) with ESMTP id f0PI2ET07543; Thu, 25 Jan 2001 10:02:14 -0800 (PST) Received: from [193.0.4.72] (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id KAA14037; Thu, 25 Jan 2001 10:02:06 -0800 (PST) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: <3A7057EA.F6D43876@ecal.com> References: <3A704AE0.FD8F4C21@ecal.com> <3A7057EA.F6D43876@ecal.com> Date: Thu, 25 Jan 2001 18:28:23 +0100 To: John Stracke , ietf-calendar@imc.org From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: Re: IPTEL spec and iCalendar Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 JAA15708 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA05432 At 11.44 -0500 01-01-25, John Stracke wrote: >Patrik Fältström wrote: > >> At 10.48 -0500 01-01-25, John Stracke wrote: >> >Was there a mechanism to tell us that it used iCalendar? >> >> Grep is your friend. > >Point taken. :-) I'll dust off the procmail manpage. Sorry I forgot the smiley. I am partly serious and partly very laid-back as you seem to understand. We all have some kind of responsibility of reviewing things that ends up as RFC's. Yes, I am the last line of defence (against publicing stupid things) together with the other individuals in the IESG, but I am very scared if you all trust me. All Area Directors are humans (even if I understand you sometimes ask if that is the case...). If nothing else, you should know by now that I don't know everything!!! ;-) I even appreciate if you send me a note IF you review something, just anything, send me a mail with the name of the I-D, and specifics you think, and ALSO if you like it. You don't even have to do it during last call! paf From owner-ietf-calendar@mail.imc.org Thu Jan 25 17:55:07 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10559 for ; Thu, 25 Jan 2001 17:55:06 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id OAA06616 for ietf-calendar-bks; Thu, 25 Jan 2001 14:33:25 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id OAA06612 for ; Thu, 25 Jan 2001 14:33:23 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f0PMj5W05635 for ; Thu, 25 Jan 2001 17:45:05 -0500 Message-ID: <3A70AC71.7CDB9D69@ecal.com> Date: Thu, 25 Jan 2001 17:45:05 -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: IPTEL spec and iCalendar References: <3A704AE0.FD8F4C21@ecal.com> <3A7057EA.F6D43876@ecal.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 OAA06616 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA10559 John Stracke wrote: > Patrik Fältström wrote: > > > At 10.48 -0500 01-01-25, John Stracke wrote: > > >Was there a mechanism to tell us that it used iCalendar? > > > > Grep is your friend. > > Point taken. :-) I'll dust off the procmail manpage. Tonight or tomorrow, I'm going to set up a tool to monitor the I-D announcements and look for interesting ones. I'm thinking of having the calsch-related ones it finds go to the calsch list. Anybody object? -- /=================================================================\ |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 Thu Jan 25 19:00:58 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA11906 for ; Thu, 25 Jan 2001 19:00:58 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id PAA11321 for ietf-calendar-bks; Thu, 25 Jan 2001 15:39:03 -0800 (PST) Received: from office.jigzaw.com ([63.144.102.109]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA11317 for ; Thu, 25 Jan 2001 15:39:02 -0800 (PST) Received: from colatz ([10.0.0.14]) by office.jigzaw.com (8.9.3/8.9.3) with ESMTP id RAA11192 for ; Thu, 25 Jan 2001 17:24:23 -0600 From: "Shannon J. Clark" To: Subject: RE: IPTEL spec and iCalendar Date: Thu, 25 Jan 2001 17:44:17 -0600 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) Importance: Normal In-Reply-To: <3A70AC71.7CDB9D69@ecal.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 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 PAA11321 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA11906 It seems to me that monitoring the announcements and passing along important ones would be a useful tool, might want to be shared with other working groups as well - if this problem is occurring with the iCalendar standard, I have to assume that other standards have and are having the same problem, different groups using or modifying a standard without reference back to the standards groups. Just a thought on my part. Shannon Shannon J. Clark CEO - JigZaw, Inc 1.800.4.JIGZAW (454.4929) shannon@jigzaw.com www.jigzaw.com -----Original Message----- From: owner-ietf-calendar@mail.imc.org [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke Sent: Thursday, January 25, 2001 4:45 PM To: ietf-calendar@imc.org Subject: Re: IPTEL spec and iCalendar Importance: High John Stracke wrote: > Patrik Fältström wrote: > > > At 10.48 -0500 01-01-25, John Stracke wrote: > > >Was there a mechanism to tell us that it used iCalendar? > > > > Grep is your friend. > > Point taken. :-) I'll dust off the procmail manpage. Tonight or tomorrow, I'm going to set up a tool to monitor the I-D announcements and look for interesting ones. I'm thinking of having the calsch-related ones it finds go to the calsch list. Anybody object? -- /=================================================================\ |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 Jan 26 10:19:41 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12204 for ; Fri, 26 Jan 2001 10:19:41 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA15870 for ietf-calendar-bks; Fri, 26 Jan 2001 06:41:10 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA15864 for ; Fri, 26 Jan 2001 06:41:07 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f0QEqs107126 for ; Fri, 26 Jan 2001 09:52:54 -0500 Message-ID: <3A718F44.C7A5317C@ecal.com> Date: Fri, 26 Jan 2001 09:52: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: ietf-calendar@imc.org Subject: Re: IPTEL spec and iCalendar 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 "Shannon J. Clark" wrote: > It seems to me that monitoring the announcements and passing along important > ones would be a useful tool, might want to be shared with other working > groups as well That did occur to me, but I don't want to have to keep the tool running for everybody in the world. I'll probably ask my boss's permission to release the tool under the GPL. -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |This space intentionally not left blank. | |francis@ecal.com| | \==============================================================/ From owner-ietf-calendar@mail.imc.org Fri Jan 26 10:49:19 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12621 for ; Fri, 26 Jan 2001 10:49:17 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id HAA19820 for ietf-calendar-bks; Fri, 26 Jan 2001 07:29:00 -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 HAA19793 for ; Fri, 26 Jan 2001 07:28:56 -0800 (PST) From: pregen@egenconsulting.com To: John Stracke Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: IPTEL spec and iCalendar X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Fri, 26 Jan 2001 15:35:13 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 01/26/2001 10:35:16 AM, Serialize complete at 01/26/2001 10:35:16 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 003A6CF8802569E0_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 003A6CF8802569E0_= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable John, excellent idea. Not sure you can help with missing notes. We sent=20 out one a bit earlier looking for comments on the IPTEL spec and I can't=20 find it in the archive. I know it left my mail engine. I've had comments = that it has happened in the past as well. I got so busy that I did not=20 look to see if the note "returned" to my inbasket from the maillist. Now=20 that kind of tool would be wonderful. Again, thanks for doing this. =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Patricia Egen Consulting www.egenconsulting.com 423-875-2652 John Stracke Sent by: owner-ietf-calendar@mail.imc.org 01/25/01 10:45 PM =20 To: ietf-calendar@imc.org cc:=20 Subject: Re: IPTEL spec and iCalendar John Stracke wrote: > Patrik F=E4ltstr=F6m wrote: > > > At 10.48 -0500 01-01-25, John Stracke wrote: > > >Was there a mechanism to tell us that it used iCalendar? > > > > Grep is your friend. > > Point taken. :-) I'll dust off the procmail manpage. Tonight or tomorrow, I'm going to set up a tool to monitor the I-D announcements and look for interesting ones. I'm thinking of having the calsch-related ones it finds go to the calsch list. Anybody object? -- /=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D| |eCal Corp. |In the country of the blind, the one-eyed man is| |francis@ecal.com|in therapy. | \=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/ --=_alternative 003A6CF8802569E0_= Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
John, excellent idea.  Not sure= you can help with missing notes.  We sent out one a bit earlier looki= ng for comments on the IPTEL spec and I can't find it in the archive.  = ;I know it left my mail engine.  I've had comments that it has happene= d in the past as well.  I got so busy that I did not look to see if th= e note "returned" to my inbasket from the maillist.  Now tha= t kind of tool would be wonderful.  Again, thanks for doing this.
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


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

01/25/01 10:45 PM

       
        To: &nbs= p;      ietf-calendar@imc.org
        cc: &nbs= p;      
        Subject:=        Re: IPTEL spec and iCalendar



John Stracke wrote:

> Patrik F=E4ltstr=F6m wrote:
>
> > At 10.48 -0500 01-01-25, John Stracke wrote:
> > >Was there a mechanism to tell us that it used iCalendar?
> >
> > Grep is your friend.
>
> Point taken.  :-) I'll dust off the procmail manpage.

Tonight or tomorrow, I'm going to set up a tool to monitor the I-D
announcements and look for interesting ones.  I'm thinking of having the calsch-related ones it finds go to the calsch list.  Anybody
object?

--
/=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\
|John Stracke    | http://www.ecal.com |My opinions are my own. &= nbsp; |
|Chief Scientist |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D|
|eCal Corp.      |In the country of the blind, the one-eyed = man is|
|francis@ecal.com|in therapy.             &nb= sp;                     &= nbsp; |
\=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/

--=_alternative 003A6CF8802569E0_=-- From owner-ietf-calendar@mail.imc.org Fri Jan 26 11:02:35 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12839 for ; Fri, 26 Jan 2001 11:02:34 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id HAA20600 for ietf-calendar-bks; Fri, 26 Jan 2001 07:32:44 -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 HAA20592 for ; Fri, 26 Jan 2001 07:32:42 -0800 (PST) From: pregen@egenconsulting.com To: "Shannon J. Clark" Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: RE: IPTEL spec and iCalendar X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: Date: Fri, 26 Jan 2001 15:38:58 +0000 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.5 |September 22, 2000) at 01/26/2001 10:39:02 AM, Serialize complete at 01/26/2001 10:39:02 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 003AC4FD802569E0_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 003AC4FD802569E0_= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Shannon, you are correct. I can't even imagine how all the working groups=20 keep track of what is called in a spec. When you think about the POP,=20 IMAP and LDAP items that are used extensively, how do those groups keep up = with other drafts and specifications that use their protocols? This is=20 much bigger than it appears on the surface. I think John's idea is a good = one and something similar for working on other groups would be particulary = helpful. =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Patricia Egen Consulting www.egenconsulting.com 423-875-2652 "Shannon J. Clark" Sent by: owner-ietf-calendar@mail.imc.org 01/25/01 11:44 PM =20 To: cc:=20 Subject: RE: IPTEL spec and iCalendar It seems to me that monitoring the announcements and passing along=20 important ones would be a useful tool, might want to be shared with other working groups as well - if this problem is occurring with the iCalendar standard, = I have to assume that other standards have and are having the same problem, different groups using or modifying a standard without reference back to=20 the standards groups. Just a thought on my part. Shannon Shannon J. Clark CEO - JigZaw, Inc 1.800.4.JIGZAW (454.4929) shannon@jigzaw.com www.jigzaw.com -----Original Message----- From: owner-ietf-calendar@mail.imc.org [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke Sent: Thursday, January 25, 2001 4:45 PM To: ietf-calendar@imc.org Subject: Re: IPTEL spec and iCalendar Importance: High John Stracke wrote: > Patrik F=E4ltstr=F6m wrote: > > > At 10.48 -0500 01-01-25, John Stracke wrote: > > >Was there a mechanism to tell us that it used iCalendar? > > > > Grep is your friend. > > Point taken. :-) I'll dust off the procmail manpage. Tonight or tomorrow, I'm going to set up a tool to monitor the I-D announcements and look for interesting ones. I'm thinking of having the calsch-related ones it finds go to the calsch list. Anybody object? -- /=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D| |eCal Corp. |In the country of the blind, the one-eyed man is| |francis@ecal.com|in therapy. | \=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/ --=_alternative 003AC4FD802569E0_= Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Shannon, you are correct. I can't ev= en imagine how all the working groups keep track of what is called in a spe= c.  When you think about the POP, IMAP and LDAP items that are used ex= tensively, how do those groups keep up with other drafts and specifications= that use their protocols?  This is much bigger than it appears on the= surface.  I think John's idea is a good one and something similar for= working on other groups would be particulary helpful.
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


"Shannon J. Clark" <= shannon@jigzaw.com>
Sent by: owner-ietf-calendar@mail.im= c.org

01/25/01 11:44 PM

       
        To: &nbs= p;      <ietf-calendar@imc.org>
        cc: &nbs= p;      
        Subject:=        RE: IPTEL spec and iCalendar



It seems to me that monitoring the announcements and= passing along important
ones would be a useful tool, might want to be shared with other working
groups as well - if this problem is occurring with the iCalendar standard, = I
have to assume that other standards have and are having the same problem, different groups using or modifying a standard without reference back to th= e
standards groups.

Just a thought on my part.

Shannon

Shannon J. Clark
CEO - JigZaw, Inc
1.800.4.JIGZAW (454.4929)
shannon@jigzaw.com
www.jigzaw.com

-----Original Message-----
From: owner-ietf-calendar@mail.imc.org
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke
Sent: Thursday, January 25, 2001 4:45 PM
To: ietf-calendar@imc.org
Subject: Re: IPTEL spec and iCalendar
Importance: High


John Stracke wrote:

> Patrik F=E4ltstr=F6m wrote:
>
> > At 10.48 -0500 01-01-25, John Stracke wrote:
> > >Was there a mechanism to tell us that it used iCalendar?
> >
> > Grep is your friend.
>
> Point taken.  :-) I'll dust off the procmail manpage.

Tonight or tomorrow, I'm going to set up a tool to monitor the I-D
announcements and look for interesting ones.  I'm thinking of having the calsch-related ones it finds go to the calsch list.  Anybody
object?

--
/=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\
|John Stracke    | http://www.ecal.com |My opinions are my own. &= nbsp; |
|Chief Scientist |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D|
|eCal Corp.      |In the country of the blind, the one-eyed = man is|
|francis@ecal.com|in therapy.             &nb= sp;                     &= nbsp; |
\=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/

--=_alternative 003AC4FD802569E0_=-- From owner-ietf-calendar@mail.imc.org Fri Jan 26 13:05:29 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA16470 for ; Fri, 26 Jan 2001 13:05:29 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA02604 for ietf-calendar-bks; Fri, 26 Jan 2001 09:44:32 -0800 (PST) Received: from office.jigzaw.com ([63.144.102.109]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA02597 for ; Fri, 26 Jan 2001 09:44:30 -0800 (PST) Received: from colatz ([10.0.0.14]) by office.jigzaw.com (8.9.3/8.9.3) with ESMTP id LAA12703 for ; Fri, 26 Jan 2001 11:29:34 -0600 From: "Shannon J. Clark" To: Subject: RE: IPTEL spec and iCalendar Date: Fri, 26 Jan 2001 11:49:51 -0600 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) In-reply-to: <3A718F44.C7A5317C@ecal.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit John, It seems to me that such a tool might be a good thing to have running directly at the IETF and/or IMC main mailing list servers - basically what I am envisioning is a tool that for each group that is currently set up, and for all future groups that are created a set of defining terms is created: For the Calendaring and Scheduling group this could be a list such as: iCalendar, iCal, vCalendar, vCal, CAP, iMip, iTip, iRip, and the specific RFC #'s that we cover. Each group would then maintain this list as a list of "What our topics are/ What needs to be addressed by us" The software would then monitor the following items - announcements of new RFC's and drafts (including a mechanism to probably scan the documents themselves as well as the announcements w/links?). Potentially this same software could watch the other group mailing lists for discussions that touch upon this group's interests (along the line of - hey should we use the iCalendar standard in our work...) - the actions taken by the application could differ depending on the mailing list it is monitoring - Perhaps announcements and other drafts that reference one of this group's areas of responsibility could be immediately brought to the attention of this group, discussions of our standards on other groups might just be brought to certain individuals? It feels like a tool that once created the various groups won't know how they worked before it was available. Shannon -----Original Message----- From: owner-ietf-calendar@mail.imc.org [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke Sent: Friday, January 26, 2001 8:53 AM To: ietf-calendar@imc.org Subject: Re: IPTEL spec and iCalendar "Shannon J. Clark" wrote: > It seems to me that monitoring the announcements and passing along important > ones would be a useful tool, might want to be shared with other working > groups as well That did occur to me, but I don't want to have to keep the tool running for everybody in the world. I'll probably ask my boss's permission to release the tool under the GPL. -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |This space intentionally not left blank. | |francis@ecal.com| | \==============================================================/ From owner-ietf-calendar@mail.imc.org Fri Jan 26 13:41:54 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17593 for ; Fri, 26 Jan 2001 13:41:54 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA04390 for ietf-calendar-bks; Fri, 26 Jan 2001 10:11:53 -0800 (PST) Received: from localhost.localdomain ([216.52.68.3]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA04381 for ; Fri, 26 Jan 2001 10:11:50 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f0QINb107663 for ; Fri, 26 Jan 2001 13:23:37 -0500 Message-ID: <3A71C0A9.B532C2D0@ecal.com> Date: Fri, 26 Jan 2001 13:23:37 -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: IPTEL spec and iCalendar 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 "Shannon J. Clark" wrote: > It seems to me that such a tool might be a good thing to have running > directly at the IETF and/or IMC main mailing list servers Perhaps, but it's not up to me. I'm going to write the tool to be extensible like this (even for my own use, I want to watch for more than just iCalendar); but I don't know if it either the IETF or the IMC has the spare computrons to have it watch for N+1 different patterns. -- /==============================================================\ |John Stracke | http://www.ecal.com |My opinions are my own.| |Chief Scientist |=============================================| |eCal Corp. |Solipsists have all the fun. | |francis@ecal.com| | \==============================================================/ From owner-ietf-calendar@mail.imc.org Fri Jan 26 17:01:10 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23135 for ; Fri, 26 Jan 2001 17:01:09 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA15879 for ietf-calendar-bks; Fri, 26 Jan 2001 13:34:29 -0800 (PST) Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA15869; Fri, 26 Jan 2001 13:34:27 -0800 (PST) Received: from sj-msg-av-2.cisco.com (sj-msg-av-2.cisco.com [171.71.163.110]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id NAA20266; Fri, 26 Jan 2001 13:39:36 -0800 (PST) Received: from mailman.cisco.com (localhost [127.0.0.1]) by sj-msg-av-2.cisco.com (8.10.1/8.10.1) with ESMTP id f0QLdWN01882; Fri, 26 Jan 2001 13:39:32 -0800 (PST) Received: from [193.0.4.72] (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id NAA20002; Fri, 26 Jan 2001 13:39:18 -0800 (PST) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: References: Date: Fri, 26 Jan 2001 22:36:20 +0100 To: pregen@egenconsulting.com, "Shannon J. Clark" From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: RE: IPTEL spec and iCalendar Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 NAA15879 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA23135 At 15.38 +0000 01-01-26, pregen@egenconsulting.com wrote: >When you think about the POP, IMAP and LDAP items that are used >extensively, how do those groups keep up with other drafts and >specifications that use their protocols? Rule number one is that the group of people creating the _new_ thing should contact the group which have standardized whatever they are inheriting. This we must trust people doing. But, we also have a review process, and the review process is supposed to check that rule number one really has been fulfilled. The formal steps we have is the IETF Last Call, and the review by members of the IESG. I don't want this to be more formal than this -- because all formalities take time. On the IESG, myself and Ned as Apps AD's do catch most such things (I can not remember a single one I have missed), but unfortunately when we find one we need responses fast -- as the IESG can not have one paper on our table for so long time. We get about 10 new I-D's on our plate a week. So, it is _my_ job to do this stuff, but, I apreciate all help I can get as you are the ones which know the details. Patrik -- Patrik Fältström Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC From owner-ietf-calendar@mail.imc.org Fri Jan 26 17:01:51 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23147 for ; Fri, 26 Jan 2001 17:01:50 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA15837 for ietf-calendar-bks; Fri, 26 Jan 2001 13:33:54 -0800 (PST) Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA15831 for ; Fri, 26 Jan 2001 13:33:53 -0800 (PST) Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com [171.69.2.19]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id NAA01137; Fri, 26 Jan 2001 13:39:58 -0800 (PST) Received: from mailman.cisco.com (localhost [127.0.0.1]) by sj-msg-av-3.cisco.com (8.10.1/8.10.1) with ESMTP id f0QLdkV04616; Fri, 26 Jan 2001 13:39:46 -0800 (PST) Received: from [193.0.4.72] (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id NAA20149; Fri, 26 Jan 2001 13:39:39 -0800 (PST) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: <3A71C0A9.B532C2D0@ecal.com> References: <3A71C0A9.B532C2D0@ecal.com> Date: Fri, 26 Jan 2001 22:37:36 +0100 To: John Stracke , ietf-calendar@imc.org From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: Re: IPTEL spec and iCalendar Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 NAA15837 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA23147 At 13.23 -0500 01-01-26, John Stracke wrote: >"Shannon J. Clark" wrote: > >> It seems to me that such a tool might be a good thing to have running >> directly at the IETF and/or IMC main mailing list servers > >Perhaps, but it's not up to me. I'm going to write the tool to be >extensible like >this (even for my own use, I want to watch for more than just >iCalendar); but I >don't know if it either the IETF or the IMC has the spare computrons >to have it >watch for N+1 different patterns. Don't forget to resolve the issue with the cpl document though. Pat, can you see that a dialogue starts between your people and the cpl people so this gets resolved? I.e. it all started with the cpl people was told by me to contact you. paf -- Patrik Fältström Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC From owner-ietf-calendar@mail.imc.org Sun Jan 28 03:24:29 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02802 for ; Sun, 28 Jan 2001 03:24:28 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA08184 for ietf-calendar-bks; Sat, 27 Jan 2001 23:53:45 -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 XAA08172 for ; Sat, 27 Jan 2001 23:53:43 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA03718 for ietf-calendar@imc.org; Sun, 28 Jan 2001 00:00:03 -0800 (PST) Date: Sun, 28 Jan 2001 00:00:03 -0800 (PST) From: Doug Royer Message-Id: <200101280800.AAA03718@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 Jan 28 16:42:27 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10531 for ; Sun, 28 Jan 2001 16:42:27 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA18542 for ietf-calendar-bks; Sun, 28 Jan 2001 13:23:08 -0800 (PST) Received: from plexus.cst.ca (plexus.CST.CA [207.139.176.42]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA18533 for ; Sun, 28 Jan 2001 13:23:06 -0800 (PST) Received: from apollo.cst.ca (apollo.cst.ca [193.77.49.44]) by plexus.cst.ca (8.9.3/1.0.1) with ESMTP id QAA03330; Sun, 28 Jan 2001 16:29:01 -0500 Received: from steltor.com (host2.vpn.cst.ca [192.168.6.2]) by apollo.cst.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id D4NRZ3ZG; Sun, 28 Jan 2001 16:28:20 -0500 Message-ID: <3A748F57.FBBF0A58@steltor.com> Date: Sun, 28 Jan 2001 16:29:59 -0500 From: George Babics X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: pregen@egenconsulting.com CC: ietf-calendar@imc.org Subject: Re: IPTEL spec and iCalendar 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: > > The IESG is reviewing the draft-ietf-iptel-cpl draft, which uses iCal > time spec for occurances of events. They use a subset of the iCal > specification and we need to know if this is valid. Basically, if the > phone people have problems with the spec, we in the calendar group > also should have problems. > > We need to have people on the list go look at the draft > "draft-ietf-iptel-cpl" and see if we see potential problems/issues. - They recommend using the Olson database on timezones. However, it should be noted that it is incomplete. - iCalendar does not have a notion of "floating" times for recurrence rules. A local time zone must be specified. This is the only inconsistency that I found with iCal. For their purposes they need not be consistent, however they may want to note this difference. > > We have been asked if we handled recurrence rules during > interoperability testing. I told our AD that this was not done in the > first pass. WE know recurrence rules are going to be a challenge. > Here's probably yet another one as well. We still have some unresolved issues with recurrence rules. Eric has a list of iCalendar issues at: http://www.softwarestudio.org/iCal/2445Issues.html Having a quick glance at the list revealed that CPL may also encounter issues with the "BYXXX" parameters. > > Also, if anyone can provide a brief description of what part of > recurrence rules must be implented to be compliant with ical, it would > be helpful. I'll forward that on to the iptel people. One must implement all parts of recurrence rules to be compliant with iCalendar. There are no different levels of support. > > Thanks for your help. From owner-ietf-calendar@mail.imc.org Sun Jan 28 22:22:48 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12523 for ; Sun, 28 Jan 2001 22:22:48 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id TAA26396 for ietf-calendar-bks; Sun, 28 Jan 2001 19:03:05 -0800 (PST) Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA26392 for ; Sun, 28 Jan 2001 19:03:03 -0800 (PST) Received: from sj-msg-av-2.cisco.com (sj-msg-av-2.cisco.com [171.71.163.110]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id TAA21049; Sun, 28 Jan 2001 19:09:09 -0800 (PST) Received: from mailman.cisco.com (localhost [127.0.0.1]) by sj-msg-av-2.cisco.com (8.10.1/8.10.1) with ESMTP id f0T38sW23540; Sun, 28 Jan 2001 19:08:54 -0800 (PST) Received: from [10.0.1.29] (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id TAA18724; Sun, 28 Jan 2001 19:08:43 -0800 (PST) Mime-Version: 1.0 X-Sender: pfaltstr@127.0.0.1 Message-Id: In-Reply-To: <3A748F57.FBBF0A58@steltor.com> References: <3A748F57.FBBF0A58@steltor.com> Date: Mon, 29 Jan 2001 04:05:55 +0100 To: George Babics , pregen@egenconsulting.com From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= Subject: Re: IPTEL spec and iCalendar Cc: ietf-calendar@imc.org Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" 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 TAA26396 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA12523 At 16.29 -0500 01-01-28, George Babics wrote: > > We need to have people on the list go look at the draft > > "draft-ietf-iptel-cpl" and see if we see potential problems/issues. > > - They recommend using the Olson database on timezones. However, it > should be noted that it is incomplete. > > - iCalendar does not have a notion of "floating" times for recurrence > rules. A local time zone must be specified. This is the only >inconsistency > that I found with iCal. For their purposes they need not be >consistent, > however they may want to note this difference. I would like to see them reference the spec _you_ do in this wg, full stop. Is it possible to negotiate (or whatever) to a situation when that is possible? Has anyone contacted the cpl guys (Pat?)? paf -- Patrik Fältström Internet Engineering Task Force Area Director, Applications Area http://www.ietf.org Phone: (Stockholm) +46-8-4494212 (San Jose) +1-408-525-0940 PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC From owner-ietf-calendar@mail.imc.org Mon Jan 29 06:12:49 2001 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA28946 for ; Mon, 29 Jan 2001 06:12:49 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id CAA05713 for ietf-calendar-bks; Mon, 29 Jan 2001 02:45:19 -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 CAA05706 for ; Mon, 29 Jan 2001 02:45:16 -0800 (PST) Received: from metaacer (unknown [193.14.119.80]) by ljudo.shortlist.se (Postfix) with SMTP id 5B2C0B34F9; Mon, 29 Jan 2001 11:51:47 +0100 (CET) From: "Greg FitzPatrick" To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= , , "Shannon J. Clark" Cc: , Subject: SV: IPTEL spec and iCalendar Date: Mon, 29 Jan 2001 11:46:30 +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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: 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 CAA05713 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA28946 I can relate to this from a SkiCal angle. Though SkiCal is an extension of iCal and CPL a “call processing language” using XML syntax, two quite divergent efforts, the authors of both drafts have tried to reuse previous work and not reinvent when possible. CPL uses XML syntax. ( Though I wonder if they took a good look at RDF, which might have suited their purposes even better.) In §2.4 XML Structure they equate “nodes” and “outputs” with “XML tags” (I believe they should have used the term “Elements”) and “parameters” with “XML tag Attributes”. (again – skip the tag!) so I believe the map is… (CPL Nodes & Outputs) eqv. (Mime-directory Component Properties) eqv. (XML Elements) (CPL Parameters) eqv. (Mime-directory Property Properties) eqv. (XML Attributes) I am not sure where this puts Calendar Components – but they are not part of the deal here so that is irrelevant. For reference here is the Map that Frank Dawson did in his iCal DTD from 19990220 (Mime Directory Calendar Components) eqv. (XML Elements) (Mime Directory Calendar Properties) eqv. (XML Attributes) (Mime Directory Component Properties) eqv. (XML Elements) (Mime Directory Property Parameters) eqv. (XML Attributes) (Mime Directory Value Types) eqv. (XML Value Types) In § 5.3 Time switches, the CPL authors reference first tzid and tzurl, and then dtstart, dtend/duration using the term “parameters”. Actually in 2445 TZID and TZURL are Properties but tzid is also confusingly a general property parameter. Other names referred to as parameters are: dtstart dtend duration all of which are Component Properties in 2445 freq interval which are value type components of the Recurrence Rules value type: RECUR in 2445 and processed first and independently from… until byday bymonthday byyearday byweekno bymonth wkst which are also value type components of the Recurrence Rules and not properties and not parameters either.. In other words there is a bit of a term muddle here which should be worked out. If Properties, property parameters and property values are all going to turn into parameters - be careful about it. At least be careful if some sort of interoperability with iCal applications is intended. I also would caution against using attributes to qualify their sibling attributes rather than their parent element as the authors have done. This is not good ER. One solution would be to nest;