From owner-ietf-calendar@imc.org Wed Mar 1 15:59:53 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12984 for ; Wed, 1 Mar 2000 15:59:50 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA08239 for ietf-calendar-bks; Wed, 1 Mar 2000 12:30:20 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA08235 for ; Wed, 1 Mar 2000 12:30:19 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id MAA24826 for ietf-calendar@imc.org; Wed, 1 Mar 2000 12:30:26 -0800 (PST) Date: Wed, 1 Mar 2000 12:30:26 -0800 (PST) From: ietf-calendar@imc.org Message-Id: <200003012030.MAA24826@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@imc.org Thu Mar 2 12:49:54 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20814 for ; Thu, 2 Mar 2000 12:49:53 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA27288 for ietf-calendar-bks; Thu, 2 Mar 2000 09:22:14 -0800 (PST) Received: from mailgw2.netvision.net.il (mailgw2.netvision.net.il [194.90.1.9]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA27283 for ; Thu, 2 Mar 2000 09:22:03 -0800 (PST) Received: from sendout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65]) by mailgw2.netvision.net.il (8.9.3/8.9.3) with ESMTP id TAA14490 for ; Thu, 2 Mar 2000 19:22:05 +0200 (IST) Received: from unity-mail.icomverse.com (unity-mail.icomverse.com [89.119.41.3]) by sendout.icomverse.com (8.9.3/8.8.7) with ESMTP id TAA14496 for ; Thu, 2 Mar 2000 19:22:41 +0200 Received: by unity-mail.icomverse.com with Internet Mail Service (5.5.2650.21) id <10G20W1L>; Thu, 2 Mar 2000 19:20:20 +0200 Message-ID: <5B34AF33D291D311A06D0004AC1509D7AAEBB3@unity-mail.icomverse.com> From: "Aloni, Eran" To: "'ietf-calendar@imc.org'" Subject: A utility for handling schedules and recurrences Date: Thu, 2 Mar 2000 19:20:19 +0200 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@imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I'm looking for a utility (preferably C++ code) that can parse and "understand" the iCalendar schedule and recurrent schedule format. "Understanding" means, matching the schedule with a specific date and time and computing the next time that matches the schedule. Thanks. Eran From owner-ietf-calendar@imc.org Thu Mar 2 13:45:06 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22560 for ; Thu, 2 Mar 2000 13:45:05 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA28619 for ietf-calendar-bks; Thu, 2 Mar 2000 10:23:43 -0800 (PST) Received: from egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA28615 for ; Thu, 2 Mar 2000 10:23:42 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Cc: andre@cst.ca, Frank_Dawson@lotus.com, sman@netscape.com, doug@royer.com, pbh@mit.edu, dmadeo@ms.com Subject: CalConnect - Interoperability test X-Mailer: Lotus Notes Release 5.0.1a August 17, 1999 Message-ID: Date: Thu, 2 Mar 2000 13:23:39 -0500 X-Priority: 3 (Normal) X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.1a|August 17, 1999) at 03/02/2000 01:23:52 PM, Serialize complete at 03/02/2000 01:23:52 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0064E8A585256896_=" Sender: owner-ietf-calendar@imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0064E8A585256896_= Content-Type: text/plain; charset="us-ascii" We are planning an iCalendar CalConnect Interoperability test for April 10-11 in Boston. MIT will helping by providing room space for our testing. The fee will be $1000 which will allow 2 people access to the testing. Food will be included as well as access to an Internet connection. We are working on the logistics of a mail server and connectivity. Please contact Pat Egen before 3/31/00 if you are interested in participating. I will be updating the list with available hotels in the area, time schedules, etc. as soon as we know how many companies will be participating ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 0064E8A585256896_= Content-Type: text/html; charset="us-ascii"
We are planning an iCalendar CalConnect Interoperability test for April 10-11 in Boston.  MIT will helping by providing room space for our testing.  The fee will be $1000 which will allow 2 people access to the testing.  Food will be included as well as access to an Internet connection.  We are working on the logistics of a mail server and connectivity.  Please contact Pat Egen before 3/31/00 if you are interested in participating.  I will be updating the list with available hotels in the area, time schedules, etc. as soon as we know how many companies will be participating
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 0064E8A585256896_=-- From owner-ietf-calendar@imc.org Thu Mar 2 15:51:02 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26495 for ; Thu, 2 Mar 2000 15:51:01 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA00412 for ietf-calendar-bks; Thu, 2 Mar 2000 12:27:52 -0800 (PST) Received: from egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA00408 for ; Thu, 2 Mar 2000 12:27:50 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Subject: Reminder - 3/10 deadline for draft X-Mailer: Lotus Notes Release 5.0.1a August 17, 1999 Message-ID: Date: Thu, 2 Mar 2000 15:27:59 -0500 X-Priority: 3 (Normal) X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.1a|August 17, 1999) at 03/02/2000 03:28:01 PM, Serialize complete at 03/02/2000 03:28:01 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 00704C8885256896_=" Sender: owner-ietf-calendar@imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 00704C8885256896_= Content-Type: text/plain; charset="us-ascii" Just a friendly reminder that the CAP draft needs to be posted by 3/10 in order to be on the agenda in Adelaide. Thanks. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 00704C8885256896_= Content-Type: text/html; charset="us-ascii"
Just a friendly reminder that the CAP draft needs to be posted by 3/10 in order to be on the agenda in Adelaide.  Thanks.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 00704C8885256896_=-- From owner-ietf-calendar@imc.org Fri Mar 3 01:41:40 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10805 for ; Fri, 3 Mar 2000 01:41:39 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id WAA22056 for ietf-calendar-bks; Thu, 2 Mar 2000 22:17:29 -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 WAA22052 for ; Thu, 2 Mar 2000 22:17:28 -0800 (PST) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id WAA28480 for ; Thu, 2 Mar 2000 22:12:59 -0800 (PST) Received: from netscape.com ([198.93.95.223]) by dredd.mcom.com (Netscape Messaging Server 4.1 Aug 9 1999 18:28:31) with ESMTP id FQU1GO00.V7D; Thu, 2 Mar 2000 22:17:12 -0800 Message-ID: <38BF58D4.9A7F33A6@netscape.com> Date: Thu, 02 Mar 2000 22:16:52 -0800 From: sman@netscape.com (Steve Mansour) X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: pregen@egenconsulting.com CC: ietf-calendar@imc.org, andre@cst.ca, Frank_Dawson@lotus.com, doug@royer.com, pbh@mit.edu, dmadeo@ms.com Subject: Re: CalConnect - Interoperability test References: Content-Type: multipart/mixed; boundary="------------86087B603234BD35E42807A3" Sender: owner-ietf-calendar@imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------86087B603234BD35E42807A3 Content-Type: multipart/alternative; boundary="------------CF8FAA5DCE6D9321AF4EBFDD" --------------CF8FAA5DCE6D9321AF4EBFDD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I don't suppose there would be any chance of moving this to later in the week? 12-13? I lose a day getting out there. So little time to spend with the family. Hate to lose a weekend day. -Steve pregen@egenconsulting.com wrote: > > We are planning an iCalendar CalConnect Interoperability test for > April 10-11 in Boston. MIT will helping by providing room space for > our testing. The fee will be $1000 which will allow 2 people access > to the testing. Food will be included as well as access to an > Internet connection. We are working on the logistics of a mail server > and connectivity. Please contact Pat Egen before 3/31/00 if you are > interested in participating. I will be updating the list with > available hotels in the area, time schedules, etc. as soon as we know > how many companies will be participating > ___________________ > Patricia Egen Consulting > www.egenconsulting.com > 423-875-2652 --------------CF8FAA5DCE6D9321AF4EBFDD Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I don't suppose there would be any chance of moving this to later in the week?  12-13?  I lose a day getting out there. So little time to spend with the family. Hate to lose a weekend day.
-Steve

pregen@egenconsulting.com wrote:

 
We are planning an iCalendar CalConnect Interoperability test for April 10-11 in Boston.  MIT will helping by providing room space for our testing.  The fee will be $1000 which will allow 2 people access to the testing.  Food will be included as well as access to an Internet connection.  We are working on the logistics of a mail server and connectivity.  Please contact Pat Egen before 3/31/00 if you are interested in participating.  I will be updating the list with available hotels in the area, time schedules, etc. as soon as we know how many companies will be participating
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652
--------------CF8FAA5DCE6D9321AF4EBFDD-- --------------86087B603234BD35E42807A3 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;fax:650-937-2103 tel;work:650-937-2378 x-mozilla-html:FALSE org:Netscape version:2.1 email;internet:sman@netscape.com title:Judge, Jury, and Executioner adr;quoted-printable:;;501 East Middlefield Road=0D=0AMS: MV-054;Mountain View;CA;94043; x-mozilla-cpt:;-10552 fn:Steve Mansour end:vcard --------------86087B603234BD35E42807A3-- From owner-ietf-calendar@mail.imc.org Sat Mar 4 02:12:58 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29280 for ; Sat, 4 Mar 2000 02:12:57 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id WAA02036 for ietf-calendar-bks; Fri, 3 Mar 2000 22:44:31 -0800 (PST) Received: from egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA02013 for ; Fri, 3 Mar 2000 22:44:20 -0800 (PST) From: pregen@egenconsulting.com To: sman@netscape.com (Steve Mansour) Cc: andre@cst.ca, dmadeo@ms.com, doug@royer.com, Frank_Dawson@lotus.com, ietf-calendar@imc.org, pbh@mit.edu, Bob Mahoney Subject: Re: CalConnect - Interoperability test X-Mailer: Lotus Notes Release 5.0.1a August 17, 1999 Message-ID: Date: Sat, 4 Mar 2000 01:44:11 -0500 X-Priority: 3 (Normal) X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.1a|August 17, 1999) at 03/04/2000 01:44:42 AM MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_mixed 0024FF1185256898_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --=_mixed 0024FF1185256898_= Content-Type: multipart/alternative; boundary="=_alternative 0024FF1185256898_=" --=_alternative 0024FF1185256898_= Content-Type: text/plain; charset="us-ascii" Actually, I think so. Someone else asked for later in the week, so if we can get MIT space ( and I think the week is ok) then I think we can move it. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 sman@netscape.com (Steve Mansour) 03/03/00 01:16 AM To: pregen@egenconsulting.com cc: ietf-calendar@imc.org, andre@cst.ca, Frank_Dawson@lotus.com, doug@royer.com, pbh@mit.edu, dmadeo@ms.com Subject: Re: CalConnect - Interoperability test I don't suppose there would be any chance of moving this to later in the week? 12-13? I lose a day getting out there. So little time to spend with the family. Hate to lose a weekend day. -Steve pregen@egenconsulting.com wrote: We are planning an iCalendar CalConnect Interoperability test for April 10-11 in Boston. MIT will helping by providing room space for our testing. The fee will be $1000 which will allow 2 people access to the testing. Food will be included as well as access to an Internet connection. We are working on the logistics of a mail server and connectivity. Please contact Pat Egen before 3/31/00 if you are interested in participating. I will be updating the list with available hotels in the area, time schedules, etc. as soon as we know how many companies will be participating ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 0024FF1185256898_= Content-Type: text/html; charset="us-ascii"
Actually, I think so.  Someone else asked for later in the week, so if we can get MIT  space ( and I think the week is ok) then I think we can move it.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


sman@netscape.com (Steve Mansour)

03/03/00 01:16 AM

       
        To:        pregen@egenconsulting.com
        cc:        ietf-calendar@imc.org, andre@cst.ca, Frank_Dawson@lotus.com, doug@royer.com, pbh@mit.edu, dmadeo@ms.com
        Subject:        Re: CalConnect - Interoperability test


I don't suppose there would be any chance of moving this to later in the week?  12-13?  I lose a day getting out there. So little time to spend with the family. Hate to lose a weekend day.
-Steve

pregen@egenconsulting.com wrote:
 
We are planning an iCalendar CalConnect Interoperability test for April 10-11 in Boston.  MIT will helping by providing room space for our testing.  The fee will be $1000 which will allow 2 people access to the testing.  Food will be included as well as access to an Internet connection.  We are working on the logistics of a mail server and connectivity.  Please contact Pat Egen before 3/31/00 if you are interested in participating.  I will be updating the list with available hotels in the area, time schedules, etc. as soon as we know how many companies will be participating
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652

--=_alternative 0024FF1185256898_=-- --=_mixed 0024FF1185256898_= Content-Type: application/octet-stream; name="ATTA2EKM" Content-Disposition: attachment; filename="ATTA2EKM" Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 YmVnaW46dmNhcmQgDQpuOk1hbnNvdXI7U3RldmUNCnRlbDtmYXg6NjUwLTkzNy0yMTAzDQp0ZWw7 d29yazo2NTAtOTM3LTIzNzgNCngtbW96aWxsYS1odG1sOkZBTFNFDQpvcmc6TmV0c2NhcGUNCnZl cnNpb246Mi4xDQplbWFpbDtpbnRlcm5ldDpzbWFuQG5ldHNjYXBlLmNvbQ0KdGl0bGU6SnVkZ2Us IEp1cnksIGFuZCBFeGVjdXRpb25lcg0KYWRyO3F1b3RlZC1wcmludGFibGU6Ozs1MDEgRWFzdCBN aWRkbGVmaWVsZCBSb2FkPTBEPTBBTVM6IE1WLTA1NDtNb3VudGFpbiBWaWV3O0NBOzk0MDQzOw0K eC1tb3ppbGxhLWNwdDo7LTEwNTUyDQpmbjpTdGV2ZSBNYW5zb3VyDQplbmQ6dmNhcmQNCg== --=_mixed 0024FF1185256898_=-- From owner-ietf-calendar@mail.imc.org Sun Mar 5 03:24:07 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02024 for ; Sun, 5 Mar 2000 03:24:06 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA20782 for ietf-calendar-bks; Sat, 4 Mar 2000 23:59:53 -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 XAA20778 for ; Sat, 4 Mar 2000 23:59:51 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA17697 for ietf-calendar@imc.org; Sun, 5 Mar 2000 00:00:04 -0800 (PST) Date: Sun, 5 Mar 2000 00:00:04 -0800 (PST) From: Doug Royer Message-Id: <200003050800.AAA17697@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 U user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and U 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 CAP draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex N text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug N C-4 VCAR examples Doug? N C-5 PUBLISH text C-6 REQUEST text C-7 REPLY text C-8 ADD text C-9 CANCEL text C-10 REFRESH text C-11 COUNTER text C-12 DECLINECOUNTER Text C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property C-16 (2.11) Query Schema I'll send this out next week. C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS Format? Text needs to be written. C-20 (13.) Security Considerations See editors note - more text. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: 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 ------------------------------------------------------------------------------ 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 From owner-ietf-calendar@mail.imc.org Mon Mar 6 22:40:44 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13959 for ; Mon, 6 Mar 2000 22:40:43 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id TAA19269 for ietf-calendar-bks; Mon, 6 Mar 2000 19:21:03 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA19262 for ; Mon, 6 Mar 2000 19:21:02 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id TAA29974 for ietf-calendar@imc.org; Mon, 6 Mar 2000 19:21:28 -0800 (PST) Date: Mon, 6 Mar 2000 19:21:28 -0800 (PST) From: ietf-calendar@imc.org Message-Id: <200003070321.TAA29974@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Mon Mar 6 23:33:24 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22631 for ; Mon, 6 Mar 2000 23:33:24 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA22841 for ietf-calendar-bks; Mon, 6 Mar 2000 20:17:01 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA22834 for ; Mon, 6 Mar 2000 20:16:58 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id UAA00200 for ietf-calendar@imc.org; Mon, 6 Mar 2000 20:17:32 -0800 (PST) Date: Mon, 6 Mar 2000 20:17:32 -0800 (PST) From: ietf-calendar@imc.org Message-Id: <200003070417.UAA00200@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Mon Mar 6 23:34:34 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22801 for ; Mon, 6 Mar 2000 23:34:33 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA23098 for ietf-calendar-bks; Mon, 6 Mar 2000 20:21:40 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA23092 for ; Mon, 6 Mar 2000 20:21:40 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id UAA00267 for ietf-calendar@imc.org; Mon, 6 Mar 2000 20:22:14 -0800 (PST) Date: Mon, 6 Mar 2000 20:22:14 -0800 (PST) From: ietf-calendar@imc.org Message-Id: <200003070422.UAA00267@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Mon Mar 6 23:43:21 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23940 for ; Mon, 6 Mar 2000 23:43:21 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA23452 for ietf-calendar-bks; Mon, 6 Mar 2000 20:25:30 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA23448 for ; Mon, 6 Mar 2000 20:25:30 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id UAA00314 for ietf-calendar@imc.org; Mon, 6 Mar 2000 20:26:03 -0800 (PST) Date: Mon, 6 Mar 2000 20:26:03 -0800 (PST) From: ietf-calendar@imc.org Message-Id: <200003070426.UAA00314@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Tue Mar 7 11:19:04 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03248 for ; Tue, 7 Mar 2000 11:19:03 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA17245 for ietf-calendar-bks; Tue, 7 Mar 2000 08:02:03 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id IAA17241 for ; Tue, 7 Mar 2000 08:02:02 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA10358; Tue, 7 Mar 00 11:04:04 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id LAA00682; Tue, 7 Mar 2000 11:02:35 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id LAA23458; Tue, 7 Mar 2000 11:02:28 -0500 (EST) Message-Id: <4.2.0.58.20000307105529.01f18258@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 07 Mar 2000 10:57:56 -0500 To: Doug@royer.com From: "Paul B. Hill" Subject: Re: Small typo in UPN text? Cc: ietf-calendar@imc.org In-Reply-To: <38B98BF3.C273CE49@home.royer.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, At 12:41 PM 2/27/2000 -0800, Doug Royer wrote: >In: > > 2.5.1. UPNs and Certificates > > > Note: If a server is validating data received via iMIP, if the > "ORGANIZER" or "ATTENDEE" property said (e.g.) "ATTENDEE;CN=Joe Random > :juser@example.com" then the "juser@example.com" part should be > checked against the altSubjectName field of the certificate, and the > "Joe Random User" part should be checked against the CN component of > the altSubjectName DN. This is so the "ATTENDEE" property couldn't be > munged to something misleading like "ATTENDEE;CN=Joe Rictus > juser@example.com" and have it pass validation. This validation > will also defeat other attempts at confusion. > >Had the ATTENDEE line had "User:" in the ATTENDEE lines: > > "ATTENDEE;CN=Joe Random:User:juser@example.com" Actually the typo is in "Joe Random:User:" it should have been "Joe Random User:", in retrospect this is confusing since "User" is also a key word. I'll change the examples in this section and others where the same problem occurs. > "User:Joe Random User" > > >As "User:" is not part of ATTENDEE, I assumed that was a typo and >I removed "User:". > >-Doug From owner-ietf-calendar@mail.imc.org Tue Mar 7 16:17:56 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16160 for ; Tue, 7 Mar 2000 16:17:49 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA22421 for ietf-calendar-bks; Tue, 7 Mar 2000 13:01:05 -0800 (PST) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA22417 for ; Tue, 7 Mar 2000 13:01:04 -0800 (PST) Received: from kaipara.live.com (mg-20425427-109.ricochet.net [204.254.27.109]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id NAA13075 for ; Tue, 7 Mar 2000 13:00:14 -0800 (PST) Message-Id: <4.3.1.20000307125649.00b572a0@shell7.ba.best.com> X-Sender: rsf@shell7.ba.best.com X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 07 Mar 2000 12:59:47 -0800 To: ietf-calendar@imc.org From: Ross Finlayson Subject: Progress of the Olsen timezone -> VTIMEZONE conversion? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: A few weeks ago there was some discussion of converting the Olsen timezone database into iCalendar VTIMEZONE format. How is this work progressing. Does anyone now have a set of VTIMEZONE-format descriptions online that we can access? Ross. From owner-ietf-calendar@mail.imc.org Tue Mar 7 20:19:40 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26353 for ; Tue, 7 Mar 2000 20:19:40 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id QAA26695 for ietf-calendar-bks; Tue, 7 Mar 2000 16:58:35 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id QAA26690 for ; Tue, 7 Mar 2000 16:58:33 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA18543; Tue, 7 Mar 00 19:59:02 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id TAA06569; Tue, 7 Mar 2000 19:59:03 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id TAA23520; Tue, 7 Mar 2000 19:59:02 -0500 (EST) Message-Id: <4.2.0.58.20000307192814.01c50dc8@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 07 Mar 2000 19:54:29 -0500 To: Doug Royer , rans@netscape.com From: "Paul B. Hill" Subject: Re: Small typo in UPN text? Cc: ietf-calendar@imc.org In-Reply-To: <200003072103.NAA03278@royer.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 01:03 PM 3/7/2000 -0800, Doug Royer wrote: > > Paul, > > > > The IDENTIFY command is still in the CAP draft. Can you explain to Doug > why we > > don't need this command anymore. > >I don't need an explanation, the list does. It has not seen one. Hi, (Note the IDENTIFY command is currently in section 2.6.2) During the interim meeting there was discussion about removing the IDENTIFY command because SASL implementations should enable CUAs to specify an authorization identity (UPN) distinct from the authentication identity asserted by the client's (user's) credentials. I was probably the major proponent of its removal. I've changed my mind. But request that the last paragraph of the current 2.6.2 section be modified. If you are interested please read on. In general I think re-authenticating and using SASL's authorization identifier should be the preferred practice. However, in the case of server-to-server communications the removal of the IDENTIFY command from CAP would cause us to run into performance problems. The initiating server would have to constantly go back to the disconnected state, reconnect and re-authenticate. This is neither practical nor desirable. Furthermore, there does not appear to be a requirement that every SASL implementation support a separate and distinct authorization identity. This means that CAP should have the capability in order to maximize interoperability. I am still very worried about implementations that might abuse this feature. In general I don't think CUAs that typical end users have on their desktops should make this feature easily available. What I really don't like about the current text of 2.6.2 is the last paragraph and the examples: The "IDENTIFY" command provides for a weak group implementation. By allowing multiple sets of authentication credentials belonging to different users to identify as the same UPN, that UPN essentially identifies a group of people, and may be used for group calendar ownership, or the granting of access rights to a group. I don't think that this is a good path to go down. I would much rather see the last paragraph changed to: The "IDENTIFY" command potentially provides for a weak group implementation. An implementation might enable multiple sets of authentication credentials belonging to different users to identify as the same UPN. Implementations SHOULD NOT use the IDENTIFY command to provide a group mechanism. Paul From owner-ietf-calendar@mail.imc.org Tue Mar 7 20:33:56 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01838 for ; Tue, 7 Mar 2000 20:33:55 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id RAA26857 for ietf-calendar-bks; Tue, 7 Mar 2000 17:14:16 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id RAA26852 for ; Tue, 7 Mar 2000 17:14:15 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA14205; Tue, 7 Mar 00 20:16:23 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id UAA08901 for ; Tue, 7 Mar 2000 20:14:54 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id UAA26190 for ; Tue, 7 Mar 2000 20:14:53 -0500 (EST) Message-Id: <4.2.0.58.20000307195832.01c6def8@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 07 Mar 2000 20:10:23 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: section duplication and confusion Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, The topic of Access Rights is still very scattered. Section 2.4.4 "Access Rights" introduces the concept. This is under the Security Model section, which sounds like the correct place for the text. Section 2.4.4.1 "VCalendar Access Right (VCAR)", still under the security model section starts going into a little more detail. Section 2.4.4.2 - 2.4.4.4 are also related. OK so far? Section 2.10 "VCalendar Access Rights (VCARs), almost duplicates the text from section 2.4.4. I think this section should be deleted. I suspect it is just left over from some recent cut-and-paste jobs. Sections 6, 6.1, and 6.2 revisit access control and VCARs. Most of the text is descriptive or explanatory and should therefore be moved to the security model section (2.4.4.x). Other closely related sections are 14.2 "RIGHTS Value Type" and 14.3 VCAR Calendar Component. I do think these are in the correct area of the document. Paul From owner-ietf-calendar@mail.imc.org Tue Mar 7 20:35:52 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02468 for ; Tue, 7 Mar 2000 20:35:51 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id RAA26917 for ietf-calendar-bks; Tue, 7 Mar 2000 17:19:45 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id RAA26913 for ; Tue, 7 Mar 2000 17:19:44 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA15500; Tue, 7 Mar 00 20:21:53 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id UAA09845 for ; Tue, 7 Mar 2000 20:20:23 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id UAA27185 for ; Tue, 7 Mar 2000 20:20:22 -0500 (EST) Message-Id: <4.2.0.58.20000307201317.01d0bcb8@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 07 Mar 2000 20:15:48 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: sections 2.6 and 2.6.1 are obsolete Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, Section 2.6 "Calendar User" and section 2.6.1 "UPNs and Certificates" are old text and should be removed from the document. The newer text appears in sections 2.4.2 "Calendar User and UPNs" and in section 2.4.2.1 "UPNs and Certificates". (I'm looking at the March 6, 2000 version of the document.) Paul From owner-ietf-calendar@mail.imc.org Wed Mar 8 00:01:23 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00251 for ; Wed, 8 Mar 2000 00:01:22 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA12637 for ietf-calendar-bks; Tue, 7 Mar 2000 20:36:09 -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 UAA12632 for ; Tue, 7 Mar 2000 20:36:09 -0800 (PST) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id UAA10888 for ; Tue, 7 Mar 2000 20:31:55 -0800 (PST) Received: from netscape.com ([198.93.95.223]) by dredd.mcom.com (Netscape Messaging Server 4.1 Aug 9 1999 18:28:31) with ESMTP id FR364I00.7X4; Tue, 7 Mar 2000 20:36:18 -0800 Message-ID: <38C5D893.25EC8C4B@netscape.com> Date: Tue, 07 Mar 2000 20:35:32 -0800 From: sman@netscape.com (Steve Mansour) X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Paul B. Hill" CC: ietf-calendar@imc.org Subject: Re: sections 2.6 and 2.6.1 are obsolete References: <4.2.0.58.20000307201317.01d0bcb8@po12.mit.edu> Content-Type: multipart/mixed; boundary="------------BE1E5E9F264658371B1C0247" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------BE1E5E9F264658371B1C0247 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Done. I missed that last night when I was making the updates. -Steve "Paul B. Hill" wrote: > Hi, > > Section 2.6 "Calendar User" and section 2.6.1 "UPNs and Certificates" are > old text and should be removed from the document. The newer text appears in > sections 2.4.2 "Calendar User and UPNs" and in section 2.4.2.1 "UPNs and > Certificates". > > (I'm looking at the March 6, 2000 version of the document.) > > Paul --------------BE1E5E9F264658371B1C0247 Content-Type: text/x-vcard; charset=us-ascii; name="sman.vcf" Content-Description: Card for Steve Mansour Content-Disposition: attachment; filename="sman.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Mansour;Steve tel;fax:650-937-2103 tel;work:650-937-2378 x-mozilla-html:FALSE org:Netscape version:2.1 email;internet:sman@netscape.com title:Judge, Jury, and Executioner adr;quoted-printable:;;501 East Middlefield Road=0D=0AMS: MV-054;Mountain View;CA;94043; x-mozilla-cpt:;-10552 fn:Steve Mansour end:vcard --------------BE1E5E9F264658371B1C0247-- From owner-ietf-calendar@mail.imc.org Wed Mar 8 14:28:33 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07620 for ; Wed, 8 Mar 2000 14:28:32 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id LAA17389 for ietf-calendar-bks; Wed, 8 Mar 2000 11:10:59 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id LAA17380 for ; Wed, 8 Mar 2000 11:10:57 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA21457; Wed, 8 Mar 00 14:11:37 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id OAA06799 for ; Wed, 8 Mar 2000 14:09:35 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id OAA19894 for ; Wed, 8 Mar 2000 14:09:34 -0500 (EST) Message-Id: <4.2.0.58.20000308102901.01d1c258@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 08 Mar 2000 10:37:43 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: proposed revision to section 2.4.2.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, I'd like to 2.4.2.2 so that it reads as follows: ---------------------- 2.4.2.2. Anonymous Users and Authentication Anonymous access is often desirable. For example an organization may publish calendar information that does not require any access control for viewing or login. Conversely, a user may wish to view unrestricted calendar information without revealing their identity. CAP implementations MUST support anonymous authentication, as defined in section . CAP implementations MAY support anonymous authentication with TLS, as defined in section . ---------------------- The last two short paragraphs are new. The previous version contained the sentence: "For detailed syntax information on anonymous authentication please refer to the AUTHENTICATE command in section 7.1.3." This is now redundant and incomplete. Paul From owner-ietf-calendar@mail.imc.org Wed Mar 8 14:28:37 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07655 for ; Wed, 8 Mar 2000 14:28:36 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id LAA17391 for ietf-calendar-bks; Wed, 8 Mar 2000 11:11:07 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id LAA17381 for ; Wed, 8 Mar 2000 11:10:57 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA21461; Wed, 8 Mar 00 14:11:37 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id OAA06805 for ; Wed, 8 Mar 2000 14:09:35 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id OAA19902 for ; Wed, 8 Mar 2000 14:09:35 -0500 (EST) Message-Id: <4.2.0.58.20000308120916.01cf1ee8@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 08 Mar 2000 12:11:33 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: modfication to Start TLS section Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, I think the following sentence should be removed from the Start TLS section: ---------- If an authentication id was determined during TLS negotiations it MUST NOT be used for the purpose of granting a CAP session identity unless the CUA authenticates using the SASL external mechanism. --------- This is the last sentence of the 2nd paragraph. Paul From owner-ietf-calendar@mail.imc.org Wed Mar 8 15:50:03 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01368 for ; Wed, 8 Mar 2000 15:50:02 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA18576 for ietf-calendar-bks; Wed, 8 Mar 2000 12:29:51 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA18572 for ; Wed, 8 Mar 2000 12:29:49 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id MAA02297 for ietf-calendar@imc.org; Wed, 8 Mar 2000 12:30:31 -0800 (PST) Date: Wed, 8 Mar 2000 12:30:31 -0800 (PST) From: ietf-calendar@imc.org Message-Id: <200003082030.MAA02297@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Wed Mar 8 16:01:43 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05548 for ; Wed, 8 Mar 2000 16:01:42 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA18767 for ietf-calendar-bks; Wed, 8 Mar 2000 12:44:42 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id MAA18755 for ; Wed, 8 Mar 2000 12:44:38 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA29101; Wed, 8 Mar 00 15:46:50 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id PAA07936 for ; Wed, 8 Mar 2000 15:42:42 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id PAA25601 for ; Wed, 8 Mar 2000 15:42:41 -0500 (EST) Message-Id: <4.2.0.58.20000308105925.01d1c258@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 08 Mar 2000 11:01:09 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: proposed section on TLS Ciphersuites Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, I propose a new section that describes which TLS Ciphersuites are appropriate for use with CAP. 2.4.2.4 TLS Ciphersuites The following ciphersuites defined in [RFC 2246] MUST NOT be used for confidentiality protection of passwords or data: TLS_NULL_WITH_NULL_NULL TLS_RSA_WITH_NULL_MD5 TLS_RSA_WITH_NULL_SHA The following ciphersuites defined in [RFC 2246] can be cracked easily (less than a week of CPU time on a standard CPU in 1997). The client and server SHOULD carefully consider the value of the password or data being protected before using these ciphersuites: TLS_RSA_EXPORT_WITH_RC4_40_MD5 TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_DH_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DH_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA The following ciphersuites are vulnerable to man-in-the-middle attacks, and SHOULD NOT be used to protect passwords or sensitive data, unless the network configuration is such that the danger of a man-in-the-middle attack is tolerable: TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 TLS_DH_anon_WITH_RC4_128_MD5 TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_3DES_EDE_CBC_SHA A client or server that supports TLS MUST support at least TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA. From owner-ietf-calendar@mail.imc.org Wed Mar 8 16:01:46 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05577 for ; Wed, 8 Mar 2000 16:01:45 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA18758 for ietf-calendar-bks; Wed, 8 Mar 2000 12:44:38 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id MAA18752 for ; Wed, 8 Mar 2000 12:44:37 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA27949; Wed, 8 Mar 00 15:45:18 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id PAA07844 for ; Wed, 8 Mar 2000 15:42:20 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id PAA25509 for ; Wed, 8 Mar 2000 15:42:19 -0500 (EST) Message-Id: <4.2.0.58.20000308104713.01d1c258@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 08 Mar 2000 15:38:02 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: proposed new section 2.4.2.3 Required Security Mechanisms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, I have a proposed new section, 2.4.2.3 Required Security Mechanisms. This section, in conjunction with revisions to the section "AUTHETICATE Command" should eliminate the errors that were noticed in earlier revisions of the draft. 2.4.2.3 Required Security Mechanisms The following implementation conformance requirements are in place: (1) For a read-only, public CS, anonymous authentication, described in section , can be used. (2) Implementations providing password-based authenticated access MUST support authentication using Digest, as described in section . This provides client authentication with protection against passive eavesdropping attacks, but does not provide protection against active intermediary attacks. (3) For a CS needing session protection and authentication, the Start TLS extended operation, and either the simple authentication choice or the SASL EXTERNAL mechanism, are to be used together. Implementations SHOULD support authentication with a password as described in section , and SHOULD support authentication with a certificate as described in section . Together, these can provide integrity and disclosure protection of transmitted data, and authentication of client and server, including protection against active intermediary attacks. From owner-ietf-calendar@mail.imc.org Wed Mar 8 16:02:46 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05885 for ; Wed, 8 Mar 2000 16:02:45 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id MAA18773 for ietf-calendar-bks; Wed, 8 Mar 2000 12:44:43 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id MAA18761 for ; Wed, 8 Mar 2000 12:44:41 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA29132; Wed, 8 Mar 00 15:46:53 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id PAA07479 for ; Wed, 8 Mar 2000 15:40:52 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id PAA25058 for ; Wed, 8 Mar 2000 15:40:51 -0500 (EST) Message-Id: <4.2.0.58.20000308110408.01d1c258@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 08 Mar 2000 15:36:33 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: proposed revised AUTHENTICATE command section Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, I'd like to revise the AUTHENTICATE command to the version that I have included below. This version eliminates the earlier text that seemed to be a splice of two different sentences that talked about Digest-MD5, DES, and 3DES. It also eliminates other SASL mechanism specific text that did not belong in this section. ------------------------- 7.1.3. AUTHENTICATE Command Arguments: [] Data: continuation data may be requested Result: 2.0 - Authenticate completed, now in authenticated state. 6.0 - Failed authentication. 6.1 - Authorization identity refused. 6.2 - Sender aborted authentication, authentication exchange cancelled. 6.3 - Unsupported Authentication Mechanism. 6.x - Temporary failure (back end authentication server down). 6.x - Authentication exchange cancelled. 6.x - Authentication mechanism too weak. 6.x - Encryption required. 6.x - Pass phrase expired. The pass phrase was correct but expired. The user will have to contact a pass phrase change server prior to authenticating. 6.x - The user is valid but the server does not have an entry in the authentication database for the requested mechanism (e.g., DIGEST- MD5). If the user successfully authenticates using a plain text password, then the back end back end entry will be updated. Note that if the client chooses to fall back to plain text password authentication it should enable an encryption layer or get user-con- firmation that a one-time transition is ac- ceptable. 6.x - User account disabled. The user will have to contact the system administrator to get the account re-enabled. 9.1 - Unexpected command. The capabilities of the CS in the authenticated state are reported in the response from the CS. These may be different than the capabilities in the Connected, but unauthenticated state. The AUTHENTICATE command is used by the CUA to identify the user to the CS. CAP supports a number of authentication methods, the [SASL] specification for authentication is the preferred method. If STARTTLS is negotiated prior to the AUTHENTICATE command, the client MUST discard all information about the CS capabilities fetched prior to the TLS negotiation. In particular, the value of supported SASL Mechanisms MAY be different after TLS has been negotiated. If a SASL security layer is negotiated, the client MUST discard all information about the CS capabilities fetched prior to SASL. In particular, if the client is configured to support multiple SASL mechanisms, it SHOULD fetch supported SASL Mechanisms both before and after the SASL security layer is negotiated and verify that the value has not changed after the SASL security layer was negotiated. This detects active attacks which remove supported SASL mechanisms from the supported SASL Mechanisms list. is an optional parameter which can be used for mechanisms which require an initial response from the CUA. The AUTHENTICATE command is followed by an authentication protocol exchange, in the form of a series of CS challenges and CUA responses, per the relevant RFC that describes the specific SASL mechanism being used. Cancelling the authentication process during its negotiation is implementation specific and not within scope of the CAP specification. If a security layer was negotiated it comes into effect for the CS starting with the first octet transmitted after the CRLF which follows the 2.0 reply code, and for the CUA starting with the first octet after the CRLF of its last response in the authentication exchange. Encrypted data is transmitted as described in [SASL]. The service name specified by this protocol's profile of SASL is "cap". [Note: this must be registered with IANA, has anyone done this yet?] The result of the AUTHENTICATE command includes data indicating the identity which has been assigned to the session, derived from the supplied authentication credentials, and/or authorization identifier. A CAP session does not have an identity until the CUA has issued the "AUTHENTICATE" command. The CUA may not issue the "AUTHENTICATE" command multiple times, even if the first attempt was aborted. If a CUA attempts to do this the CS must terminate the session. Data returned in response to a successful login is: The following examples illustrate the various possibilities for an authentication protocol exchange. Here are examples of a successful authentication: C: AUTHENTICATE KERBEROS_V4 S: AmFYig== C: BAcAQU5EUkVXLkNNVS5FRFUAOCAsho84kLN3/IJmrMG+25a4DT S: or//EoAADZI= C: DiAF5A4gA+oOIALuBkAAmw== S: 2.0 S: . S: Content-Type:text/calendar; method=REQUEST; charset=US-ASCII S: Content-Transfer-Encoding: 7bit S: S: BEGIN:VCALENDAR S: PRODID:-//ACME/CAPserver//EN S: VERSION:2.1 S: IDENTITY=bill@example.com S: CAPVERSION=1.0 S: ITIPVERSION=1.0 S: AUTH=KERBEROS_V4 S: AUTH=DIGEST_MD5 S: CAR=CAR-FULL-1 S: MINDATE=19700101T000000Z S: MAXDATE=20370201T000000Z S: END:VCALENDAR S: . This example shows a failed authentication: C: AUTHENTICATE KERBEROS_V4 S: AmFYig== C: BAcAQU5EUkVXLkNNVS5FRFUAOCAsho84kLN3/IJmrMG+25a4DT S: . S: 6.0 S: . S: . From owner-ietf-calendar@mail.imc.org Wed Mar 8 18:50:00 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19089 for ; Wed, 8 Mar 2000 18:50:00 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id PAA21227 for ietf-calendar-bks; Wed, 8 Mar 2000 15:36:16 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id PAA21223 for ; Wed, 8 Mar 2000 15:36:15 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA27395; Wed, 8 Mar 00 18:36:56 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id SAA28072; Wed, 8 Mar 2000 18:36:57 -0500 (EST) Received: from [18.177.0.98] (WINGNUT.MIT.EDU [18.177.0.98]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id SAA24002; Wed, 8 Mar 2000 18:36:56 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@po12.mit.edu Message-Id: In-Reply-To: References: Date: Wed, 8 Mar 2000 18:36:48 -0500 To: Frank_Dawson@lotus.com From: Bob Mahoney Subject: Re: Participation In CAP Cc: , pregen@egenconsulting.com, bobmah@mit.edu, paf@swip.net Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Frank- I'm very sorry to see you leave the CAP effort. Your input and leadership will be sorely missed. It would be very helpful to know exactly what aspects of the CAP technical direction you feel might be off-track- it's not apparent to me where your concerns lie. Even if you will be unable to participate in their resolution, it would be very useful if you could explain where you think we have fundamental problems. I personally believe that if CAP is worth doing, it is probably only worth doing with standards-track as the goal. As long as there are interested people willing to work on the problem, and the ADs feel we can be useful as a WG, I'd like to see the work completed. -Bob From owner-ietf-calendar@mail.imc.org Wed Mar 8 18:51:14 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19507 for ; Wed, 8 Mar 2000 18:51:13 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id PAA21140 for ietf-calendar-bks; Wed, 8 Mar 2000 15:33:01 -0800 (PST) Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA21136 for ; Wed, 8 Mar 2000 15:32:59 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id SAA13623 for ; Wed, 8 Mar 2000 18:49:31 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id SAA13925 for ; Wed, 8 Mar 2000 18:33:12 -0500 (EST) Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id PAA28595; Wed, 8 Mar 2000 15:58:22 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id PAA25951; Wed, 8 Mar 2000 15:42:03 -0500 (EST) X-Mailer: Lotus Notes Release 5.0.2b December 16, 1999 MIME-Version: 1.0 Subject: Participation In CAP Cc: pregen@egenconsulting.com, bobmah@mit.edu, paf@swip.net To: Message-ID: Date: Wed, 8 Mar 2000 18:31:21 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/08/2000 06:31:45 PM Content-type: text/plain; charset=us-ascii Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Folks: After some lengthly and careful thought, I would like to ask that my name be removed as an editor for the current Calendar Access Protocol specification. This is not a reflection on the other editors for this I-D. They remain some of the most forward thinking experts on C&S in the industry and hopefully, still my friends and colleagues! However, it is apparent to me that the current CAP work effort is not proceeding in the technical direction or with the schedule that I had expected. The current draft is making presumptions about the technical direction and the priority of features that ought to be included in the initial version CAP. I disagree with these current directions and priorities. In addition, I believe this current effort is draining the resources and focus that SHOULD BE applied to iCalendar/iTIP/iMIP interoperability testing. I think that the current effort should be published as an Internet-Draft but is not suitable for publication as an RFC. I personally (and with Corporate sponsorship) remain _ever_ committed to my responsibilities as editor for the iCalendar (RFC 2445), iTIP (RFC 2446) and iMIP (RFC 2447) drafts and also the whole heartedly support the current renewed focus on demonstrating interoperability between iCalendar/iTIP/iMIP implementations and the progress of these three drafts within the IETF document process. Letting go of this responsibility will allow me to focus on what I believe ought to be a higher C&S industry priority. -- Frank Dawson From owner-ietf-calendar@mail.imc.org Wed Mar 8 19:27:05 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29278 for ; Wed, 8 Mar 2000 19:27:05 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id QAA22529 for ietf-calendar-bks; Wed, 8 Mar 2000 16:10:03 -0800 (PST) Received: from mta2biz.bizmailsrvcs.net (mta2.bizmailsrvcs.net [206.46.164.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA22521 for ; Wed, 8 Mar 2000 16:10:01 -0800 (PST) Received: from Software.com ([207.175.94.157]) by mta2biz.bizmailsrvcs.net with ESMTP id <20000309000958.BKWL943.mta2biz.bizmailsrvcs.net@Software.com>; Wed, 8 Mar 2000 18:09:58 -0600 Message-ID: <38C6EAE0.CB8FB75D@Software.com> Date: Wed, 08 Mar 2000 16:05:52 -0800 From: Doug Royer Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Frank_Dawson@lotus.com CC: ietf-calendar@imc.org, pregen@egenconsulting.com, bobmah@mit.edu, paf@swip.net Subject: Re: Participation In CAP References: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms132DDAA0F0156D43FA184737" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a cryptographically signed message in MIME format. --------------ms132DDAA0F0156D43FA184737 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Frank_Dawson@lotus.com wrote: > > Folks: > > After some lengthly and careful thought, I would like to ask that my name > be removed as an editor for the current Calendar Access Protocol > specification. Ouch! > This is not a reflection on the other editors for this I-D. > They remain some of the most forward thinking experts on C&S in the > industry and hopefully, still my friends and colleagues! > However, it is apparent to me that the current CAP work effort is not > proceeding in the technical direction or with the schedule that I had > expected. The speed if CAP is of concern to many of us. I do however think we are making some progress and the pace is picking up. > The current draft is making presumptions about the technical > direction and the priority of features that ought to be included in the > initial version CAP. I disagree with these current directions and > priorities. I assume you have been busy lately - we missed your input. > In addition, I believe this current effort is draining the > resources and focus that SHOULD BE applied to iCalendar/iTIP/iMIP > interoperability testing. I do not see that CAP is slowing down iCalendar/iTIP/iMIP testing. I see CAP as the reason that the vendors are starting to be concerned about interoperability testing as CAP can't work if iCalendar/iTIP/iMIP is not working. > I think that the current effort should be published as an Internet-Draft > but is not suitable for publication as an RFC. Why? -Doug --------------ms132DDAA0F0156D43FA184737 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIKKgYJKoZIhvcNAQcCoIIKGzCCChcCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC CCIwggTsMIIEVaADAgECAhA2tOutfntkPZeWwhSMC60VMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDExNzAwMDAw MFoXDTAwMTAxMzIzNTk1OVowggEZMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0RvdWdsYXMgTSBSb3llcjEmMCQGCSqG SIb3DQEJARYXZG91Zy5yb3llckBzb2Z0d2FyZS5jb20wXDANBgkqhkiG9w0BAQEFAANLADBI AkEA8b+/7AusCQc89McoXWlPBDcEaOyt/e2NdL+lPypsoauWxoLohWrk708y93xfziOVZ/Jh 3yF9Dq43K9rW9m8SewIDAQABo4IBwTCCAb0wCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5Mjk4 NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjIxNDFi ZWFkYjJiZDJlODkyMWZhODZiZjFkMTExNDk5ZmEzYmE0N2ZkZjNlYTQ1MDYwMAYKYIZIAYb4 RQEGBwQiFiA2NWVlMGM5M2RkNDY2OGJjNGViOGM2OWNiMDliZWYxNzAzBgNVHR8ELDAqMCig JqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEBBAUA A4GBAIfiBv6wsXfERKczHkNCZ3zPRgSs/eOEutA2lnTtejz+sHTm3XWcEEx0zcEkYafFIOCK GFgFsy6cR4czApnWlILPzDAyT+FcDsAqTtSGDL8jTVMo/7MW6CHReAc0oSzGtapMxWcLgaMh /D0lM5vSddVM7EgNhGLWQPoAvxKe4PExMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqglXa/u DXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ bmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0 aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZl cmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQL Ez13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFC LkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vi c2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ AoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI 4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqO f2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIBBjBH BgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5j b20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZI hvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoPuUmF pJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11YGkk8 kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggHQMIIBzAIBATCB4TCBzDEXMBUG A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQNrTrrX57ZD2XlsIUjAut FTAJBgUrDgMCGgUAoIGGMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF MQ8XDTAwMDMwOTAwMDU1M1owIwYJKoZIhvcNAQkEMRYEFGw8iOkhLVpvQENdnTLIbnVL/x/Z MCcGCSqGSIb3DQEJDzEaMBgwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEB BQAEQH9PYlhHyxgn3taaL+4SQvO0RsiSdPRlp06YGgKGhmqZftBQfhSSueuYu3Lbq27M54y6 F2rngkEg9Q+aHdFVLdU= --------------ms132DDAA0F0156D43FA184737-- From owner-ietf-calendar@mail.imc.org Thu Mar 9 00:55:52 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10793 for ; Thu, 9 Mar 2000 00:55:51 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id VAA11774 for ietf-calendar-bks; Wed, 8 Mar 2000 21:31:50 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id VAA11770 for ; Wed, 8 Mar 2000 21:31:48 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id VAA03042 for ietf-calendar@imc.org; Wed, 8 Mar 2000 21:32:32 -0800 (PST) Date: Wed, 8 Mar 2000 21:32:32 -0800 (PST) From: Steve Mansour (sman@Netscape.com) Message-Id: <200003090532.VAA03042@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Thu Mar 9 06:49:53 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01615 for ; Thu, 9 Mar 2000 06:49:52 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id DAA26475 for ietf-calendar-bks; Thu, 9 Mar 2000 03:30:53 -0800 (PST) Received: from hotmail.com (f92.law7.hotmail.com [216.33.237.92]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id DAA26471 for ; Thu, 9 Mar 2000 03:30:52 -0800 (PST) Received: (qmail 14060 invoked by uid 0); 9 Mar 2000 11:31:09 -0000 Message-ID: <20000309113109.14059.qmail@hotmail.com> Received: from 202.54.42.182 by www.hotmail.com with HTTP; Thu, 09 Mar 2000 03:31:09 PST X-Originating-IP: [202.54.42.182] From: "Nitin Shingne" To: ietf-calendar@imc.org Cc: n_shingne@hotmail.com Subject: problem reconciling CAP Methods Date: Thu, 09 Mar 2000 03:31:09 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Greetings !!! What would be the sequence of commands to create a new entry for an Event in a Calendar. The event has some attendees. The draft gives an example to create an entry as ... C: SENDDATA C: Content-Type:text/calendar; method=CREATE; charset=US-ASCII C: Content-Transfer-Encoding:7bit C: C: BEGIN:VCALENDAR C: VERSION:2.1 C: CMDID:abcde C: METHOD:CREATE C: TARGET:cap://cal.foo.com/relcal1 C: TARGET:relcal2 C: BEGIN:VEVENT ........... ........... so on.... Now with the method specified as "CREATE", where would the scheduling method "REQUEST" go? Also BTW, What is CMDID? I could not find the definition in the draft or RFC's 2446 & 2445. thanks & regards, nitin ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From owner-ietf-calendar@mail.imc.org Thu Mar 9 11:52:58 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06068 for ; Thu, 9 Mar 2000 11:52:57 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id IAA04816 for ietf-calendar-bks; Thu, 9 Mar 2000 08:27:01 -0800 (PST) Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA04812 for ; Thu, 9 Mar 2000 08:27:00 -0800 (PST) Received: from Software.com ([207.175.94.86]) by mta1biz.bizmailsrvcs.net with ESMTP id <20000309162711.CCJH895.mta1biz.bizmailsrvcs.net@Software.com>; Thu, 9 Mar 2000 10:27:11 -0600 Message-ID: <38C7CFE5.C0217CA3@Software.com> Date: Thu, 09 Mar 2000 08:23:01 -0800 From: Doug Royer Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Nitin Shingne , ietf-calendar@imc.org CC: ietf-calendar@imc.org Subject: Re: problem reconciling CAP Methods References: <20000309113109.14059.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Nitin Shingne wrote: > > Greetings !!! > > What would be the sequence of commands to create a new entry for an Event in > a Calendar. The event has some attendees. > > The draft gives an example to create an entry as ... > C: SENDDATA > C: Content-Type:text/calendar; method=CREATE; charset=US-ASCII > C: Content-Transfer-Encoding:7bit > C: > C: BEGIN:VCALENDAR > C: VERSION:2.1 > C: CMDID:abcde > C: METHOD:CREATE > C: TARGET:cap://cal.foo.com/relcal1 > C: TARGET:relcal2 > C: BEGIN:VEVENT > ........... > ........... so on.... > > Now with the method specified as "CREATE", where would the scheduling method > "REQUEST" go? A CS does two things for you: (1) Calendaring - Get this months appointments. - Place this appointment into my calendar. (The example you gave above). (2) Scheduling - METHOD: REQUEST, REPLY, COUNTER, DECLINE-... So there needs to be a way for a CUA to say "just drop this into my calendar as I (the CU) have already determined I want this on my calendar". A CS would CREATE a new VEVENT in the store with the characteristics that followed in the same command. If the CREATEed VEVENT had METHOD:REQUEST, then the CS would deposit the REQUEST VEVENT into the calendar along with the other properties in the VEVENT. This is where we still need more text in CAP. The CS would look at the ORGANIZER: Is the ORGANIZER the CU that deposited the VEVNET (with METHOD:REQUEST in the VEVENT)? Yes - Process it as an iTIP scheduling request. Send out email or CAP connect to the ATTENDEEs sending them a METHOD:REQUEST. This is a CU requesting a scheduling with the ATTENDEEs via METHOD:REQUEST and CAP. No - This is a CU depositing a REQUEST (possibly from iMIP) into the CU's (not ORGANIZER's) store. Just drop the VEVENT into the store as the CU/CUA wants to keep the VEVENT data. Later a CUA/CU would look for all non-booked appointments (text already in CAP or soon to be), find this one and ask the CU if they wanted to attend the event: Yes - Change the METHOD:REQUST to METHOD:CREATE in the store. It is now 'booked' in the CU's store. Possibly RSVP with a YES. Possibly sending a METHOD:REPLY to the ORGANIZER. Probably deleting the entry from the store. No - Possibly RSVP with a NO. Possibly sending a METHOD:REPLY to the ORGANIZER. Probably deleting the entry from the store. We need more discussion on this, it looks to be the same as iTIP and I suspect it is exactly the same. I also suspect that anything that we find that is not like iTIP, will be a bug in iTIP that will also need to be fixed. It is just that CAP also needs to just be able to deposit and fetch appointments for a CUA. ALSO - we need a CAP restriction table, much like the iTIP restriction table. I suspect that the above CAP example will not be valid as I suspect a METHOD will be a MUST (As I think you are pointing out). -Doug > Also BTW, What is CMDID? I could not find the definition in the draft or > RFC's 2446 & 2445. iCalendar is extendable. CMDID missing from CAP. Thanks! It is simply a TAG to match a command to a response for overlapped commands. > thanks & regards, > nitin From owner-ietf-calendar@mail.imc.org Thu Mar 9 12:32:50 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18975 for ; Thu, 9 Mar 2000 12:32:49 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA05447 for ietf-calendar-bks; Thu, 9 Mar 2000 09:09:42 -0800 (PST) Received: from mta2biz.bizmailsrvcs.net (mta2.bizmailsrvcs.net [206.46.164.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA05443 for ; Thu, 9 Mar 2000 09:09:40 -0800 (PST) Received: from Software.com ([207.175.94.86]) by mta2biz.bizmailsrvcs.net with ESMTP id <20000309170957.BRNC943.mta2biz.bizmailsrvcs.net@Software.com>; Thu, 9 Mar 2000 11:09:57 -0600 Message-ID: <38C7D9EB.830F1CCC@Software.com> Date: Thu, 09 Mar 2000 09:05:47 -0800 From: Doug Royer Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Nitin Shingne , ietf-calendar@imc.org Subject: Re: problem reconciling CAP Methods References: <20000309113109.14059.qmail@hotmail.com> <38C7CFE5.C0217CA3@Software.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Doug Royer wrote: oops! > Is the ORGANIZER the CU that deposited the VEVNET (with METHOD:REQUEST > in the VEVENT)? > ... > Yes - Change the METHOD:REQUST to METHOD:CREATE > in the store. It is now 'booked' in the > CU's store. > > Possibly RSVP with a YES. > > Possibly sending a METHOD:REPLY to the > ORGANIZER. The next line I sent is bogus. > Probably deleting the entry from the store. From owner-ietf-calendar@mail.imc.org Thu Mar 9 20:40:59 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13761 for ; Thu, 9 Mar 2000 20:40:58 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id RAA12696 for ietf-calendar-bks; Thu, 9 Mar 2000 17:21:42 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id RAA12691 for ; Thu, 9 Mar 2000 17:21:41 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA13225; Thu, 9 Mar 00 20:24:00 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id UAA14961 for ; Thu, 9 Mar 2000 20:22:29 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id UAA22869 for ; Thu, 9 Mar 2000 20:22:28 -0500 (EST) Message-Id: <4.2.0.58.20000309195755.01c82a90@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 09 Mar 2000 20:17:52 -0500 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: section 2.4.3 User Groups comments Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, The last sentence of the 1st paragraph of section User Groups (2.4.3) states, "The CUA cannot distinguish between CUs and UGs." Is this clear enough? Or should it read, "The CUA cannot distinguish between a UPN that represents a CU or a UG"? Paul From owner-ietf-calendar@mail.imc.org Thu Mar 9 21:06:22 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20156 for ; Thu, 9 Mar 2000 21:06:21 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id RAA12974 for ietf-calendar-bks; Thu, 9 Mar 2000 17:51:54 -0800 (PST) Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA12970 for ; Thu, 9 Mar 2000 17:51:52 -0800 (PST) Received: from Software.com ([207.175.94.86]) by mta1biz.bizmailsrvcs.net with ESMTP id <20000310015205.CONR895.mta1biz.bizmailsrvcs.net@Software.com>; Thu, 9 Mar 2000 19:52:05 -0600 Message-ID: <38C85447.462B1CB@Software.com> Date: Thu, 09 Mar 2000 17:47:51 -0800 From: Doug Royer Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Paul B. Hill" CC: ietf-calendar@imc.org Subject: Re: section 2.4.3 User Groups comments References: <4.2.0.58.20000309195755.01c82a90@po12.mit.edu> 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 "Paul B. Hill" wrote: > > Hi, > > The last sentence of the 1st paragraph of section User Groups (2.4.3) > states, "The CUA cannot distinguish between CUs and UGs." Is this clear > enough? Or should it read, "The CUA cannot distinguish between a UPN that > represents a CU or a UG"? > > Paul #2 seems more clear to me. I remember reading that one twice the first time. -Doug From owner-ietf-calendar@mail.imc.org Thu Mar 9 21:38:00 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00453 for ; Thu, 9 Mar 2000 21:37:59 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id SAA14536 for ietf-calendar-bks; Thu, 9 Mar 2000 18:14:29 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id SAA14527 for ; Thu, 9 Mar 2000 18:14:27 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA17431; Thu, 9 Mar 00 21:15:10 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id VAA20900; Thu, 9 Mar 2000 21:15:12 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id VAA29624; Thu, 9 Mar 2000 21:15:11 -0500 (EST) Message-Id: <4.2.0.58.20000309202417.01dd5c20@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 09 Mar 2000 21:10:37 -0500 To: Doug@royer.com From: "Paul B. Hill" Subject: Re: UPN + GROUP + UPNEXPAND question. Cc: ietf-calendar@imc.org In-Reply-To: <38B9729A.A29AEB8F@home.royer.com> References: <38B441CC.120DFA7D@netscape.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 10:53 AM 2/27/2000 -0800, Doug Royer wrote: >Within the context of groups, when do you get MULTIPLE UPNs? I don't think you do. The UPNEXPAND examples show multiple CSIDs being returned but not multiple UPNs. Section 2.4.3, User Groups, has a misleading paragraph: UGs are expanded as necessary by the CS. The CS MUST accept a CUA request for UG expansion, although the CS may be configured to restrict some responses. The CS MAY expand a UG (including nested UGs) to obtain a list of unique CUs. Duplicate UPNs are filtered during expansion. Incomplete expansion should be treated as a failure. At first I thought that "Duplicate UPNs are filtered during expansion." should be changed to "Duplicate CSIDs are filtered during expansion." Now I am not so sure. Maybe the UPNEXPAND examples are incorrect? Was the intent actually to allow a CU via a CUA determine what users were members of a user group? >There was talk that you MUST do a UPNEXPAND each time you >authenticate? I must have misfiled some messages I can't find a message that indicates that anyone proposed this. >Seems a silly to have an extra round trip. I agree. >Why not do it as part of the authentication reply? I don't see why it should be needed as part the authentication reply either. >Then I still do NOT know what you do with them. At what point >does the CUA ever pass them back to the CS? If never, then >what's the point? I don't think that a CUA would ever pass the result of UPNEXPAND back to the CS. That would seem to be going down the road of using CAP to administer groups which I thought was out of scope by consensus of the group. >Perhaps those of you that understand UPN's can send some text or >email describing when you get them? The current CAP draft and >the text from Paul (I think it was from Paul) does not seem to say. A UPN is the result of authentication to the CS with the possibility of a few well understood transformations. Normally the user asserts their UPN offers sufficient proof to the CS that it is believed. Not that we would do this, but as an example: UPN=pbh@mit.edu PASSWORD=foo. Or a certificate could be presented, verified, and the UPN read out of the certificate. A SASL implementation could also authenticate the user, and present the authorization id as defined in the SASL RFC and the authorization id would be the UPN. Finally after the initial authentication, the IDENTITY command could be used. I don't see the CS forcing the UPN upon the user. I don't see the CUA asserting a list of UPNs during a transaction to be subsequently used by other operations. (You may see a CUA putting a list of UPNs on the wire as part of a VCAR definition.) >I think Bruce says they comeback as part of the authentication reply? That would be a misunderstanding. I must have said something the was confusing at some point and later it got asserted as fact. My apologies to Bruce. >Yet no one that proposed any new text has replied to that question. >And I can't find any text that says that. >There was no proposed changes to the ABNF or any text, or any example >in CAP-draft that shows when you get them, other than UPNEXPAND. I don't think the draft needs to go into them any further, if everybody agrees with what I have said up to this point :) >As I understoon groups of calendars, it was meant to be something like: >If you happen (at run time) to be part of group-A, and there is >a calendar that has modify permission to cal-group-a, then you >can modify that calendar. That's what I thought too. >So why does the CUA ever need to know >the UPN of group-A ? 'user' has or does not have permission >to modify cal-group-a. Why does the CUA care what the value >of the UPN property is that allowd that? Why can't it just >work, or you get permission denied? I don't think the CUA cares :) I think someone thinks the user might care. :) I may be confused but I think someone tried to sneak the equivalent of SMTP's EPN into CAP. >Would it be something like: small modification below > C: AUTHENTICATE [ no in a username password case change the above to: ] C: AUTHENTICATE > S: 2.0 > S: . > S: Content-Type:text/calendar; method=REQUEST; charset=US-ASCII > S: Content-Transfer-Encoding: 7bit > S: > S: BEGIN:VCALENDAR > S: PRODID:-//ACME/CAPserver//EN > S: VERSION:2.1 > S: CAPVERSION=1.0 > S: ITIPVERSION=1.0 > S: AUTH=KERBEROS_V4 > S: AUTH=DIGEST_MD5 > S: CAR=CAR-FULL-1 > S: MINDATE=19700101T000000Z > S: MAXDATE=20370201T000000Z Remember that you actually connect as part of CAP, but the time that we use AUTHENTICATE we actually dive into SASL, which possibly takes us into other transactions over the wire, then we pop back into CAP. The normal C: S: .... notation doesn't really accurately reflect what might be going on. Treat SASL as a bit of black box. Does this help? Paul From owner-ietf-calendar@mail.imc.org Thu Mar 9 21:44:16 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02690 for ; Thu, 9 Mar 2000 21:44:15 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id SAA15253 for ietf-calendar-bks; Thu, 9 Mar 2000 18:25:03 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id SAA15249 for ; Thu, 9 Mar 2000 18:25:02 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA24414; Thu, 9 Mar 00 21:27:19 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id VAA21945; Thu, 9 Mar 2000 21:25:48 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id VAA00819; Thu, 9 Mar 2000 21:25:48 -0500 (EST) Message-Id: <4.2.0.58.20000309212003.01ca9a58@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 09 Mar 2000 21:21:14 -0500 To: Doug@royer.com From: "Paul B. Hill" Subject: Re: UPN + GROUP + UPNEXPAND question. Cc: ietf-calendar@imc.org In-Reply-To: <4.2.0.58.20000309202417.01dd5c20@po12.mit.edu> References: <38B9729A.A29AEB8F@home.royer.com> <38B441CC.120DFA7D@netscape.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 09:10 PM 3/9/2000 -0500, Paul B. Hill wrote: >I may be confused but I think someone tried to sneak the equivalent of >SMTP's EPN into CAP. Oops, EPN should have been EXPN. From owner-ietf-calendar@mail.imc.org Thu Mar 9 22:15:37 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13443 for ; Thu, 9 Mar 2000 22:15:37 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id SAA17568 for ietf-calendar-bks; Thu, 9 Mar 2000 18:59:09 -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 SAA17561 for ; Thu, 9 Mar 2000 18:59:08 -0800 (PST) Received: from royer.com (royer.com [207.177.146.80]) by royer.com (8.9.1/8.9.1) with SMTP id SAA13892 for ; Thu, 9 Mar 2000 18:59:56 -0800 (PST) Message-Id: <200003100259.SAA13892@royer.com> Date: Thu, 9 Mar 2000 18:59:56 -0800 (PST) From: Doug Royer Reply-To: ietf-calendar@imc.org Subject: Re: UPN + GROUP + UPNEXPAND question. To: ietf-calendar@imc.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: Um81V5T50CUmBl87GZunHA== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4c sparc Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > From: "Paul B. Hill" > Subject: Re: UPN + GROUP + UPNEXPAND question. > Cc: ietf-calendar@imc.org > > At 09:10 PM 3/9/2000 -0500, Paul B. Hill wrote: > >I may be confused but I think someone tried to sneak the equivalent of > >SMTP's EPN into CAP. > > Oops, EPN should have been EXPN. Okay. So, other than debuging - why do we want it (UPNEXPAND)? With SMTP's EXPN, I think it is only used for debugging. I don't think MUA's use EXPN. The reason that I think that, is that may MTA's do not allow VRFY or EXPN, they return unimplemented. I would suspect the same for UPNEXPAND. Many will NOT want to give out membership lists to spammers. And I do not see any benifit for UPNEXPAND - other than debugging. And it would not be used from a CUA, or at least it would not be reliable from a CUA as it can be turned off at the CS. If I am correct, I would make a motion to remove UPNEXPAND. -Doug From owner-ietf-calendar@mail.imc.org Thu Mar 9 22:42:06 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23065 for ; Thu, 9 Mar 2000 22:42:05 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id TAA19399 for ietf-calendar-bks; Thu, 9 Mar 2000 19:27:13 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id TAA19395 for ; Thu, 9 Mar 2000 19:27:11 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA05612; Thu, 9 Mar 00 22:29:31 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id WAA29185 for ; Thu, 9 Mar 2000 22:28:00 -0500 (EST) Received: from miles-davis (MUCKLEY-FOURTEEN.MIT.EDU [18.172.5.14]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id WAA08892; Thu, 9 Mar 2000 22:27:59 -0500 (EST) Message-Id: <4.2.0.58.20000309221928.01c68a68@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 09 Mar 2000 22:23:25 -0500 To: ietf-calendar@imc.org, ietf-calendar@imc.org From: "Paul B. Hill" Subject: Re: UPN + GROUP + UPNEXPAND question. In-Reply-To: <200003100259.SAA13892@royer.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 06:59 PM 3/9/2000 -0800, Doug Royer wrote: >The reason that I think that, is that >may MTA's do not allow VRFY or EXPN, they return unimplemented. >I would suspect the same for UPNEXPAND. Many will NOT want >to give out membership lists to spammers. And I do not see >any benifit for UPNEXPAND - other than debugging. And >it would not be used from a CUA, or at least it would not >be reliable from a CUA as it can be turned off at the CS. SMTP is unauthenticated, CAP is not. A CS could have authorizations that determine which users are allowed to use UPNEXPAND. It becomes more important when we consider the CS to CS usage of CAP. In this case the CSs might not share a common group definition. The UPNs that represent groups must be expanded prior to moving the data across a security context boundary so that a consistent evaluation can take place. Paul From owner-ietf-calendar@mail.imc.org Thu Mar 9 23:26:01 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07492 for ; Thu, 9 Mar 2000 23:26:01 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA21042 for ietf-calendar-bks; Thu, 9 Mar 2000 20:07:01 -0800 (PST) Received: from hqvsbh1.ms.com (hqvsbh1.ms.com [205.228.12.103]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA21036 for ; Thu, 9 Mar 2000 20:07:00 -0800 (PST) Received: (from uucp@localhost) by hqvsbh1.ms.com (8.9.3/fw v1.30) id XAA20117; Thu, 9 Mar 2000 23:07:48 -0500 (EST) Received: from localhost(127.0.0.1) by hqvsbh1 via smap (4.1) id sma.9526612661.020088; Thu, 9 Mar 00 23:07:46 -0500 Received: (from uucp@localhost) by hqvsbh1.ms.com (8.9.3/8.9.3(vs)) id XAA20085; Thu, 9 Mar 2000 23:07:46 -0500 (EST) X-Authentication-Warning: hqvsbh1.ms.com: Processed from queue /var/spool/mqueue-vs X-Authentication-Warning: hqvsbh1.ms.com: Processed by uucp with -C /etc/mail/sendmail.vs.cf Received: from sasmh4.ms.com(144.14.193.5) by hqvsbh1 via smap (4.1) id sma.9526612631.020078; Thu, 9 Mar 00 23:07:43 -0500 Received: from msdw.com (hqdsl26.morgan.com [205.228.1.26]) by sasmh4.ms.com (8.8.5/imap+ldap v2.4) with ESMTP id XAA10875; Thu, 9 Mar 2000 23:07:43 -0500 (EST) Message-ID: <38C87510.4F3810C@msdw.com> Date: Thu, 09 Mar 2000 23:07:44 -0500 From: David Madeo Reply-To: David.Madeo@msdw.com Organization: Morgan Stanley Dean Witter & Co. X-Mailer: Mozilla 4.51 [en]C-CCK-MCD (WinNT; U) X-Accept-Language: en,ja MIME-Version: 1.0 To: "Paul B. Hill" CC: ietf-calendar@imc.org Subject: Re: UPN + GROUP + UPNEXPAND question. References: <4.2.0.58.20000309221928.01c68a68@po12.mit.edu> Content-Type: multipart/mixed; boundary="------------64B8F5A2496ED3BFCE25412B" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------64B8F5A2496ED3BFCE25412B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Paul B. Hill" wrote: > At 06:59 PM 3/9/2000 -0800, Doug Royer wrote: > >The reason that I think that, is that > >may MTA's do not allow VRFY or EXPN, they return unimplemented. > >I would suspect the same for UPNEXPAND. Many will NOT want > >to give out membership lists to spammers. And I do not see > >any benifit for UPNEXPAND - other than debugging. And > >it would not be used from a CUA, or at least it would not > >be reliable from a CUA as it can be turned off at the CS. > > SMTP is unauthenticated, CAP is not. A CS could have authorizations that > determine which users are allowed to use UPNEXPAND. > > It becomes more important when we consider the CS to CS usage of CAP. In > this case the CSs might not share a common group definition. The UPNs that > represent groups must be expanded prior to moving the data across a > security context boundary so that a consistent evaluation can take place. Even the CUA to CS model might have the CUA and CS having different user/group directories. The CUA needs to be able to ask the CS to expand the UPN for it. Especially on thin clients. dmadeo --------------64B8F5A2496ED3BFCE25412B Content-Type: text/x-vcard; charset=us-ascii; name="David.Madeo.vcf" Content-Description: Card for David Madeo Content-Disposition: attachment; filename="David.Madeo.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Madeo;David tel;fax:212-762-1009 tel;work:212-762-2348 x-mozilla-html:FALSE url:www.ms.com org:Morgan Stanley Dean Witter and Discover;Information Technology version:2.1 email;internet:dmadeo@ms.com adr;quoted-printable:;;750 Seventh Ave=0D=0A;NY;NY;10019;USA x-mozilla-cpt:;0 fn:David Madeo end:vcard --------------64B8F5A2496ED3BFCE25412B-- From owner-ietf-calendar@mail.imc.org Thu Mar 9 23:39:20 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12223 for ; Thu, 9 Mar 2000 23:39:19 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA21729 for ietf-calendar-bks; Thu, 9 Mar 2000 20:15:59 -0800 (PST) Received: from mauve.innosoft.com (mauve.innosoft.com [192.160.253.247]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA21725 for ; Thu, 9 Mar 2000 20:15:57 -0800 (PST) From: ned.freed@innosoft.com Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.0-20 #35243) id <01JMUAN0P0OW000NQ8@MAUVE.INNOSOFT.COM> for ietf-calendar@imc.org; Thu, 09 Mar 2000 20:16:23 -0800 (PST) Date: Thu, 09 Mar 2000 20:13:20 -0800 (PST) Subject: Re: UPN + GROUP + UPNEXPAND question. In-reply-to: "Your message dated Thu, 09 Mar 2000 22:23:25 -0500" <4.2.0.58.20000309221928.01c68a68@po12.mit.edu> To: "Paul B. Hill" Cc: ietf-calendar@imc.org Message-id: <01JMUB6NLH6S000NQ8@MAUVE.INNOSOFT.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed References: <200003100259.SAA13892@royer.com> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > At 06:59 PM 3/9/2000 -0800, Doug Royer wrote: > >The reason that I think that, is that > >may MTA's do not allow VRFY or EXPN, they return unimplemented. > >I would suspect the same for UPNEXPAND. Many will NOT want > >to give out membership lists to spammers. And I do not see > >any benifit for UPNEXPAND - other than debugging. And > >it would not be used from a CUA, or at least it would not > >be reliable from a CUA as it can be turned off at the CS. An MTA that returns unimplemented for VRFY is in technical violation of the SMTP specification. > SMTP is unauthenticated, CAP is not. A CS could have authorizations that > determine which users are allowed to use UPNEXPAND. On the contrary, SMTP has authentication facilities. They are optional but they are there. In fact deployment of them is happening pretty rapidly as they are often used as part of a spam control strategy. And they can be used to enable/disable use of EXPN. Ned From owner-ietf-calendar@mail.imc.org Fri Mar 10 03:19:04 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00845 for ; Fri, 10 Mar 2000 03:18:58 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id XAA29945 for ietf-calendar-bks; Thu, 9 Mar 2000 23:56:00 -0800 (PST) Received: from hotmail.com (f254.law7.hotmail.com [216.33.236.132]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id XAA29941 for ; Thu, 9 Mar 2000 23:55:58 -0800 (PST) Received: (qmail 43771 invoked by uid 0); 10 Mar 2000 07:56:19 -0000 Message-ID: <20000310075619.43770.qmail@hotmail.com> Received: from 202.54.42.183 by www.hotmail.com with HTTP; Thu, 09 Mar 2000 23:56:19 PST X-Originating-IP: [202.54.42.183] From: "Nitin Shingne" To: ietf-calendar@imc.org Cc: n_shingne@hotmail.com Subject: Discrepancy between RFC 2445 & RFC 2446 Date: Thu, 09 Mar 2000 23:56:19 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Please refer to description of Organizer in RFC 2445. 4.8.4.3 Organizer ... Conformance: ....This property MUST NOT be specified in an iCalendar object ... or that defines calendar entities that are not group scheduled entities,but are entities only on a single user's calendar. Now, does this mean that PUBLISH on an Event should not have an Organizer? But see what RFC 2446 PUBLISH for an Event [section 3.2.1] says... Organizer is a MUST. So is the case for PUBLISH methods for ToDo and Journal objects. please help me in understanding this. thanks & regards, nitin ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From owner-ietf-calendar@mail.imc.org Fri Mar 10 11:24:02 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07651 for ; Fri, 10 Mar 2000 11:23:54 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id HAA22761 for ietf-calendar-bks; Fri, 10 Mar 2000 07:58:38 -0800 (PST) Received: from mail.chronolabs.de (qmailr@mail.chronolabs.de [62.154.158.51]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id HAA22757 for ; Fri, 10 Mar 2000 07:58:36 -0800 (PST) Received: (qmail 5572 invoked from network); 10 Mar 2000 15:52:43 -0000 Received: from unknown (HELO holger.chronolabs.de) (62.154.158.50) by mail.chronolabs.de with SMTP; 10 Mar 2000 15:52:43 -0000 Message-Id: <4.3.0.20000310163915.00a9caa0@mail.chronolabs.de> X-Sender: clbhs01@mail.chronolabs.de X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Fri, 10 Mar 2000 16:52:41 +0100 To: ietf-calendar@imc.org From: Holger Schmidt Subject: typo in CAP draft Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: 7.1.3.1. AUTHENTICATE ANONYMOUS FC-2245 defines the Anonymous SASL mechanism. This RFC states that "the mechanism consists of a single message from the client to the server. ... Should probably start with _R_FC-2245 Who should receive notices like this in the future ? H. Schmidt -- Holger Schmidt - email: hschmidt@chronolabs.de phone: ++4989 55869988 - fax: ++4989 55869966 Chronolabs GmbH - Landwehrstr. 5 - 80336 Munich From owner-ietf-calendar@mail.imc.org Fri Mar 10 11:52:05 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17917 for ; Fri, 10 Mar 2000 11:52:04 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA23090 for ietf-calendar-bks; Fri, 10 Mar 2000 08:17:18 -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 IAA23084 for ; Fri, 10 Mar 2000 08:17:13 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id IAA22327 for ; Fri, 10 Mar 2000 08:13:07 -0800 (PST) Received: from netscape.com ([198.93.95.223]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FR7RXA00.I1E; Fri, 10 Mar 2000 08:17:34 -0800 Message-ID: <38C91FE2.1480F793@netscape.com> Date: Fri, 10 Mar 2000 08:16:34 -0800 From: Steve Mansour X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Holger Schmidt , CalSched IETF Subject: Re: typo in CAP draft References: <4.3.0.20000310163915.00a9caa0@mail.chronolabs.de> 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 Holger Schmidt wrote: > 7.1.3.1. AUTHENTICATE ANONYMOUS > > FC-2245 defines the Anonymous SASL mechanism. This RFC states that "the > mechanism consists of a single message from the client to the server. > ... fixed. thanks for reporting this. > Should probably start with _R_FC-2245 > > Who should receive notices like this in the future ? You can send them to the list. Reduces the chance of people reporting it twice :-) -Steve From owner-ietf-calendar@mail.imc.org Fri Mar 10 12:12:14 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24987 for ; Fri, 10 Mar 2000 12:12:13 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA23641 for ietf-calendar-bks; Fri, 10 Mar 2000 08:49:55 -0800 (PST) Received: from mumrik.nada.kth.se (mumrik.nada.kth.se [130.237.226.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA23634 for ; Fri, 10 Mar 2000 08:49:53 -0800 (PST) Received: from localhost (d92-pla@localhost) by mumrik.nada.kth.se (8.8.7/8.8.7) with ESMTP id RAA22283 for ; Fri, 10 Mar 2000 17:50:43 +0100 (MET) Date: Fri, 10 Mar 2000 17:50:43 +0100 (MET) From: =?ISO-8859-1?Q?P=E4r_Lanner=F6?= To: ietf-calendar@imc.org Subject: SKICal applications Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="----=_NextPart_000_0004_01BF8AAC.B78F67E0" Content-ID: Content-Transfer-Encoding: 8bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ------=_NextPart_000_0004_01BF8AAC.B78F67E0 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1 Content-ID: Content-Transfer-Encoding: 8BIT CALSCH friends We would like to let you know that there is a bunch of SKiCal applications up and running on the Internet (at least in Sweden) and we hope that everyone has a chance to take a look. If we can in any way participate in the interoperability tests from a distance - let us know. The largest municipalities in Sweden have committed themselves to SKiCal and Stockholm town is the first implementer. The InfoStructure which we are building for Stockholm has a central node - Stockholm's information Service - SIS - at http://www.stockholmtown.com/events/9/index.asp you can click on "advanced" search to try out some Geo searches. If you pick any event you will be able to download it to your desktop calendar. The SKiCal extensions are all X-ed so they should not disturb interoperability - but then of course you cannot to see the skical-specific information. Several major newspapers will boost their events calendars by regularly collecting event information contained in the SKICal file generated by calling SIS webserver at http://www.stockholmtown.com/events/9/skical.vcs?since=2000-03-08 (The particular example retrieves all events edited or published since March 8.) There are a few similar URLs from which event information can be harvested, but this one is by far the richest one available today. The Swedish tourist council distributes an application for creating and editing SKICal (and iCalendar) files, for those who do not have their information in a database already. It is a Java application and can be retrieved from http://195.163.30.82/qscwdv/skicalgen.zip Sorry, the interface is only in Swedish so far. For those of you unfamiliar with the SKiCal extensions - the draft is here: http://www.ietf.org/internet-drafts/draft-many-ical-ski-01.txt More information about the SKICal initiative can be found at http://www.skical.org/ Greetings from Pär Lannerö and Greg FitzPatrick ------=_NextPart_000_0004_01BF8AAC.B78F67E0-- From owner-ietf-calendar@mail.imc.org Fri Mar 10 13:57:12 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01280 for ; Fri, 10 Mar 2000 13:57:10 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA25094 for ietf-calendar-bks; Fri, 10 Mar 2000 10:35:29 -0800 (PST) Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA25090 for ; Fri, 10 Mar 2000 10:35:28 -0800 (PST) Received: from Software.com ([207.175.94.55]) by mta1biz.bizmailsrvcs.net with ESMTP id <20000310183544.DAIE895.mta1biz.bizmailsrvcs.net@Software.com>; Fri, 10 Mar 2000 12:35:44 -0600 Message-ID: <38C93F78.5E764E93@Software.com> Date: Fri, 10 Mar 2000 10:31:20 -0800 From: Doug Royer Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: 520 cap.txt downloads! 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 It looks as if having the CAP.TXT file available via FTP is popular. There have been 520 downloads since it was first setup for download! -Doug From owner-ietf-calendar@mail.imc.org Fri Mar 10 13:58:35 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01754 for ; Fri, 10 Mar 2000 13:58:33 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA25178 for ietf-calendar-bks; Fri, 10 Mar 2000 10:39:45 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA25174 for ; Fri, 10 Mar 2000 10:39:42 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id KAA06835 for ietf-calendar@imc.org; Fri, 10 Mar 2000 10:40:31 -0800 (PST) Date: Fri, 10 Mar 2000 10:40:31 -0800 (PST) From: Steve Mansour (sman@Netscape.com) Message-Id: <200003101840.KAA06835@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Fri Mar 10 14:05:49 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04906 for ; Fri, 10 Mar 2000 14:05:47 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA25347 for ietf-calendar-bks; Fri, 10 Mar 2000 10:45:51 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA25342 for ; Fri, 10 Mar 2000 10:45:49 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id KAA06869 for ietf-calendar@imc.org; Fri, 10 Mar 2000 10:46:39 -0800 (PST) Date: Fri, 10 Mar 2000 10:46:39 -0800 (PST) From: Steve Mansour (sman@Netscape.com) Message-Id: <200003101846.KAA06869@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Fri Mar 10 14:13:21 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08107 for ; Fri, 10 Mar 2000 14:13:20 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA25458 for ietf-calendar-bks; Fri, 10 Mar 2000 10:55:38 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id KAA25454 for ; Fri, 10 Mar 2000 10:55:36 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA10005; Fri, 10 Mar 00 13:57:59 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id NAA21970; Fri, 10 Mar 2000 13:53:19 -0500 (EST) Received: from [18.177.0.98] (WINGNUT.MIT.EDU [18.177.0.98]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id NAA21831; Fri, 10 Mar 2000 13:53:19 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: In-Reply-To: <38C93F78.5E764E93@Software.com> References: <38C93F78.5E764E93@Software.com> Date: Fri, 10 Mar 2000 13:52:43 -0500 To: Doug Royer From: Bob Mahoney Subject: Re: 520 cap.txt downloads! Cc: ietf-calendar@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 10:31 AM -0800 3/10/00, Doug Royer wrote: >It looks as if having the CAP.TXT file available via FTP is popular. >There have been 520 downloads since it was first setup for download! Very cool. Thanks for all your work making this readily available! -Bob From owner-ietf-calendar@mail.imc.org Fri Mar 10 16:12:57 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19694 for ; Fri, 10 Mar 2000 16:12:56 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA26823 for ietf-calendar-bks; Fri, 10 Mar 2000 12:44:23 -0800 (PST) Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA26819 for ; Fri, 10 Mar 2000 12:44:22 -0800 (PST) Received: from Software.com ([207.175.94.55]) by mta1biz.bizmailsrvcs.net with ESMTP id <20000310204439.DDER895.mta1biz.bizmailsrvcs.net@Software.com> for ; Fri, 10 Mar 2000 14:44:39 -0600 Message-ID: <38C95DF8.1874B9BA@Software.com> Date: Fri, 10 Mar 2000 12:41:28 -0800 From: Doug Royer Reply-To: ietf-calendar@imc.org Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: UPN + GROUP + UPNEXPAND question. References: <200003100259.SAA13892@royer.com> <01JMUB6NLH6S000NQ8@MAUVE.INNOSOFT.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit ned.freed@innosoft.com wrote: > > > At 06:59 PM 3/9/2000 -0800, Doug Royer wrote: > > >The reason that I think that, is that > > >may MTA's do not allow VRFY or EXPN, they return unimplemented. > > >I would suspect the same for UPNEXPAND. Many will NOT want > > >to give out membership lists to spammers. And I do not see > > >any benifit for UPNEXPAND - other than debugging. And > > >it would not be used from a CUA, or at least it would not > > >be reliable from a CUA as it can be turned off at the CS. > > An MTA that returns unimplemented for VRFY is in technical violation of > the SMTP specification. Right - I meant to say - EXPN returns "no I will not", which I think is not a violation. From owner-ietf-calendar@mail.imc.org Fri Mar 10 16:41:36 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29900 for ; Fri, 10 Mar 2000 16:41:35 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA27208 for ietf-calendar-bks; Fri, 10 Mar 2000 13:14:20 -0800 (PST) Received: from mauve.innosoft.com (mauve.innosoft.com [192.160.253.247]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA27204 for ; Fri, 10 Mar 2000 13:14:19 -0800 (PST) From: ned.freed@innosoft.com Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.0-20 #35243) id <01JMV6JQLBGG000OXK@MAUVE.INNOSOFT.COM> for ietf-calendar@imc.org; Fri, 10 Mar 2000 13:14:54 -0800 (PST) Date: Fri, 10 Mar 2000 13:14:02 -0800 (PST) Subject: Re: UPN + GROUP + UPNEXPAND question. In-reply-to: "Your message dated Fri, 10 Mar 2000 12:41:28 -0800" <38C95DF8.1874B9BA@Software.com> To: Doug Royer Cc: ietf-calendar@imc.org Message-id: <01JMVARFEV10000OXK@MAUVE.INNOSOFT.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii References: <200003100259.SAA13892@royer.com> <01JMUB6NLH6S000NQ8@MAUVE.INNOSOFT.COM> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > ned.freed@innosoft.com wrote: > > > > > At 06:59 PM 3/9/2000 -0800, Doug Royer wrote: > > > >The reason that I think that, is that > > > >may MTA's do not allow VRFY or EXPN, they return unimplemented. > > > >I would suspect the same for UPNEXPAND. Many will NOT want > > > >to give out membership lists to spammers. And I do not see > > > >any benifit for UPNEXPAND - other than debugging. And > > > >it would not be used from a CUA, or at least it would not > > > >be reliable from a CUA as it can be turned off at the CS. > > > > An MTA that returns unimplemented for VRFY is in technical violation of > > the SMTP specification. > Right - I meant to say - EXPN returns "no I will not", which > I think is not a violation. Correct. Unfortunately, this sort of minutiae actually matters in practice, since it affects what commands a client can expect to use. And there are some very strange clients out there... Ned From owner-ietf-calendar@mail.imc.org Fri Mar 10 22:34:45 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24837 for ; Fri, 10 Mar 2000 22:34:44 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id TAA06991 for ietf-calendar-bks; Fri, 10 Mar 2000 19:16:46 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA06985 for ; Fri, 10 Mar 2000 19:16:45 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id TAA07517 for ietf-calendar@imc.org; Fri, 10 Mar 2000 19:17:28 -0800 (PST) Date: Fri, 10 Mar 2000 19:17:28 -0800 (PST) From: Steve Mansour (sman@Netscape.com) Message-Id: <200003110317.TAA07517@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Sat Mar 11 15:42:06 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23428 for ; Sat, 11 Mar 2000 15:42:05 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA04540 for ietf-calendar-bks; Sat, 11 Mar 2000 12:29:36 -0800 (PST) Received: from home.royer.com (adsl-63-195-80-50.dsl.snfc21.pacbell.net [63.195.80.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA04536 for ; Sat, 11 Mar 2000 12:29:35 -0800 (PST) Received: (from sman@localhost) by home.royer.com (8.9.1/8.9.1) id MAA09837 for ietf-calendar@imc.org; Sat, 11 Mar 2000 12:30:32 -0800 (PST) Date: Sat, 11 Mar 2000 12:30:32 -0800 (PST) From: Steve Mansour (sman@Netscape.com) Message-Id: <200003112030.MAA09837@home.royer.com> To: ietf-calendar@imc.org Subject: CAP draft update Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The CAP draft files have been updated on: ftp://royer.com/pub/CALSCH The current cap drafit is: ftp://royer.com/pub/CALSCH/cap.txt.gz Nroff and other source files including cap.txt: ftp://royer.com/pub/CALSCH/sources.tar.gz From owner-ietf-calendar@mail.imc.org Sun Mar 12 03:26:31 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04674 for ; Sun, 12 Mar 2000 03:26:31 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA23024 for ietf-calendar-bks; Sat, 11 Mar 2000 23:59:19 -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 XAA23020 for ; Sat, 11 Mar 2000 23:59:17 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA23375 for ietf-calendar@imc.org; Sun, 12 Mar 2000 00:00:06 -0800 (PST) Date: Sun, 12 Mar 2000 00:00:06 -0800 (PST) From: Doug Royer Message-Id: <200003120800.AAA23375@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 U user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and U 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 CAP draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex N text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug N C-4 VCAR examples Doug? N C-5 PUBLISH text C-6 REQUEST text C-7 REPLY text C-8 ADD text C-9 CANCEL text C-10 REFRESH text C-11 COUNTER text C-12 DECLINECOUNTER Text C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property C-16 (2.11) Query Schema I'll send this out next week. C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS Format? Text needs to be written. C-20 (13.) Security Considerations See editors note - more text. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: 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 ------------------------------------------------------------------------------ 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 From owner-ietf-calendar@mail.imc.org Mon Mar 13 10:56:32 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28784 for ; Mon, 13 Mar 2000 10:56:30 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id HAA15911 for ietf-calendar-bks; Mon, 13 Mar 2000 07:22:15 -0800 (PST) Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA15907 for ; Mon, 13 Mar 2000 07:22:08 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id KAA19915; Mon, 13 Mar 2000 10:39:06 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id KAA21319; Mon, 13 Mar 2000 10:22:39 -0500 (EST) To: =?iso-8859-1?q?P=E4r_Lanner=F6?= Cc: ietf-calendar@imc.org Subject: Re: SKICal applications X-Mailer: Lotus Notes Release 5.0.2b December 16, 1999 Message-ID: Date: Mon, 13 Mar 2000 10:20:51 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/13/2000 10:20:56 AM, Serialize complete at 03/13/2000 10:20:56 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 004C3EA6852568A1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 004C3EA6852568A1_= Content-Type: text/plain; charset="us-ascii" Are these different implementations (i.e., different code bases)? -- Frank --=_alternative 004C3EA6852568A1_= Content-Type: text/html; charset="us-ascii"
Are these different implementations (i.e., different code bases)?

-- Frank --=_alternative 004C3EA6852568A1_=-- From owner-ietf-calendar@mail.imc.org Mon Mar 13 11:02:07 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01344 for ; Mon, 13 Mar 2000 11:02:05 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id HAA16191 for ietf-calendar-bks; Mon, 13 Mar 2000 07:38:50 -0800 (PST) Received: from mumrik.nada.kth.se (mumrik.nada.kth.se [130.237.226.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA16120 for ; Mon, 13 Mar 2000 07:34:13 -0800 (PST) Received: from localhost (d92-pla@localhost) by mumrik.nada.kth.se (8.8.7/8.8.7) with ESMTP id QAA01641 for ; Mon, 13 Mar 2000 16:34:44 +0100 (MET) Date: Mon, 13 Mar 2000 16:34:44 +0100 (MET) From: =?ISO-8859-1?Q?P=E4r_Lanner=F6?= To: ietf-calendar@imc.org Subject: Re: SKICal applications In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8BIT On Mon, 13 Mar 2000 Frank_Dawson@lotus.com wrote: > Are these different implementations (i.e., different code bases)? Yes. They are even written in different programming languages. They implement different functionality, even though all are applications centered around SKICal. 1. A graphical search interface making use of GEO information etc, written as a Java applet: http://www.stockholmtown.com/events/9/index.asp you can click on "advanced" search to try out some Geo searches. 2. SKICal output from database, written in VBscript: http://www.stockholmtown.com/events/9/skical.vcs?since=2000-03-08 3. An application for creating and editing SKICal (and iCalendar) files, for those who do not have their information in a database already. It is a Java standalone application and can be retrieved from http://195.163.30.82/qscwdv/skicalgen.zip There is also a SKICal parser written in C which is not available as a web resource, and a SKICal emitter written as a Perl cgi script. Regards Pär Lannerö -Pär-Lannerö---------------------------------------------------------- mailto:par.lannero@metamatrix.se jobb:+46(0)8337785 http://www.d.kth.se/~d92-pla/ hem:+46(0)853039951 icq:306436 gsm:+46(0)708/826888 ---------------------------------------------------------------------- - anpassar databaser till Internetĺldern From owner-ietf-calendar@mail.imc.org Mon Mar 13 12:06:02 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26138 for ; Mon, 13 Mar 2000 12:06:01 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id IAA17090 for ietf-calendar-bks; Mon, 13 Mar 2000 08:41:49 -0800 (PST) Received: from mumrik.nada.kth.se (mumrik.nada.kth.se [130.237.226.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA17086 for ; Mon, 13 Mar 2000 08:41:46 -0800 (PST) Received: from localhost (d92-pla@localhost) by mumrik.nada.kth.se (8.8.7/8.8.7) with ESMTP id QAA01641 for ; Mon, 13 Mar 2000 16:34:44 +0100 (MET) Date: Mon, 13 Mar 2000 16:34:44 +0100 (MET) From: =?ISO-8859-1?Q?P=E4r_Lanner=F6?= To: ietf-calendar@imc.org Subject: Re: SKICal applications In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8BIT On Mon, 13 Mar 2000 Frank_Dawson@lotus.com wrote: > Are these different implementations (i.e., different code bases)? Yes. They are even written in different programming languages. They implement different functionality, even though all are applications centered around SKICal. 1. A graphical search interface making use of GEO information etc, written as a Java applet: http://www.stockholmtown.com/events/9/index.asp you can click on "advanced" search to try out some Geo searches. 2. SKICal output from database, written in VBscript: http://www.stockholmtown.com/events/9/skical.vcs?since=2000-03-08 3. An application for creating and editing SKICal (and iCalendar) files, for those who do not have their information in a database already. It is a Java standalone application and can be retrieved from http://195.163.30.82/qscwdv/skicalgen.zip There is also a SKICal parser written in C which is not available as a web resource, and a SKICal emitter written as a Perl cgi script. Regards Pär Lannerö -Pär-Lannerö---------------------------------------------------------- mailto:par.lannero@metamatrix.se jobb:+46(0)8337785 http://www.d.kth.se/~d92-pla/ hem:+46(0)853039951 icq:306436 gsm:+46(0)708/826888 ---------------------------------------------------------------------- - anpassar databaser till Internetĺldern From owner-ietf-calendar@mail.imc.org Mon Mar 13 13:28:30 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00265 for ; Mon, 13 Mar 2000 13:28:29 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA18486 for ietf-calendar-bks; Mon, 13 Mar 2000 10:09:14 -0800 (PST) Received: from diablo.cisco.com (diablo.cisco.com [171.68.224.210]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA18482 for ; Mon, 13 Mar 2000 10:09:12 -0800 (PST) Received: from jschnizl1-pc (jschnizl-isdn2.cisco.com [171.68.12.75]) by diablo.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id KAA28728 for ; Mon, 13 Mar 2000 10:09:47 -0800 (PST) Message-Id: <4.1.20000313125709.00aea300@diablo.cisco.com> X-Sender: jschnizl@diablo.cisco.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 13 Mar 2000 13:01:07 -0500 To: ietf-calendar@imc.org From: John Schnizlein Subject: time period format incompatibility Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Looking for guidance from the Calendar WG. John }From: remoore@us.ibm.com } }Let me explain what happened. } }Since there has been no suggestion that the current encodings }for these fields don't work, the authors of the draft decided }that their lack of alignment with the RFC 2445 encodings is a }second-order problem. If the WG as a whole thinks this }alignment is important, we can certainly change the draft. }But so far I haven't heard even one other person second your }motion to make this change. } ... }To: Robert Moore/Raleigh/IBM@IBMUS, policy@raleigh.ibm.com }Subject: Re: Summary of changes in -04 draft of the PCIM } }Am I the only person who sees a problem in that the Policy Framework }draft is proposing a format for time-dates and periods of them that is }incompatible with Standard-track RFC 2445? } }I expected that my answers to Bob's questions last month regarding }changing the draft would lead to compatibility. What is the compelling }reason to introduce time format translations for any attempt to }interoperate between Internet-standard scheduling and Policy? } }John } }draft-ietf-policy-core-info-model-04.txt } 6.5.1. The Property "TimePeriod" } } This property identifies an overall range of calendar dates and times } over which a policy rule is valid. It is formatted as a string } consisting of a start date and time, then a colon (':'), and followed } by an end date and time. The first date indicates the beginning of } the range, while the second date indicates the end. Thus, the second } date and time must be later than the first. Dates are expressed as } substrings of the form "yyyymmddhhmmss". For example: } } 19990101080000:19990131120000 } } }RFC 2445: } The iCalendar format is suitable as an exchange format between } applications or systems. The format is defined in terms of a MIME } content type. This will enable the object to be exchanged using } several transports, including but not limited to SMTP, HTTP, ... } }4.3.4 Date } Example: The following represents July 14, 1997: } 19970714 }4.3.5 Date-Time } For example, the following represents January 19, 1998, at 0700 UTC: } DTSTART:19980119T070000Z }4.3.9 Period of Time } Example: The period starting at 18:00:00 UTC, on January 1, 1997 and } ending at 07:00:00 UTC on January 2, 1997 would be: } 19970101T180000Z/19970102T070000Z } From owner-ietf-calendar@mail.imc.org Mon Mar 13 16:33:32 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13183 for ; Mon, 13 Mar 2000 16:33:31 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA23689 for ietf-calendar-bks; Mon, 13 Mar 2000 12:59:32 -0800 (PST) Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA23685 for ; Mon, 13 Mar 2000 12:59:30 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id QAA12601; Mon, 13 Mar 2000 16:16:20 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id PAA22712; Mon, 13 Mar 2000 15:59:54 -0500 (EST) To: John Schnizlein Cc: ietf-calendar@imc.org Subject: Re: time period format incompatibility X-Mailer: Lotus Notes Release 5.0.2b December 16, 1999 Message-ID: Date: Mon, 13 Mar 2000 15:58:09 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/13/2000 03:58:10 PM, Serialize complete at 03/13/2000 03:58:10 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0073B712852568A1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0073B712852568A1_= Content-Type: text/plain; charset="us-ascii" John: This just isn't a draft-ietf-policy-core-info-model-04.txt versus RFC 2445. The iCalendar format is based on an accepted International Standard, ISO 8601. There doesn't seem to be a good reason to intentionally do something different for a period format. Push back again! -- Frank --=_alternative 0073B712852568A1_= Content-Type: text/html; charset="us-ascii"
John:

This just isn't a draft-ietf-policy-core-info-model-04.txt versus RFC 2445. The iCalendar format is based on an accepted International Standard, ISO 8601.

There doesn't seem to be a good reason to intentionally do something different for a period format.

Push back again!

-- Frank --=_alternative 0073B712852568A1_=-- From owner-ietf-calendar@mail.imc.org Mon Mar 13 18:45:24 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00192 for ; Mon, 13 Mar 2000 18:45:20 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id PAA27048 for ietf-calendar-bks; Mon, 13 Mar 2000 15:29:45 -0800 (PST) Received: from rodent.crp.com.au (rodent.ringtail.com.au [203.13.222.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA27043 for ; Mon, 13 Mar 2000 15:29:40 -0800 (PST) Received: from gnome (richard.ringtail.com.au [203.13.222.9]) by rodent.crp.com.au (8.9.3/8.9.3) with SMTP id KAA49359 for ; Tue, 14 Mar 2000 10:40:33 +1100 (EST) (envelope-from richard@ringtail.com.au) Message-ID: <006001bf8d4c$5dc7f680$09de0dcb@ringtail.com.au> From: "Richard Antill" To: Subject: Implementations of vToDo items Date: Tue, 14 Mar 2000 10:29:31 +1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_005D_01BF8DA0.2F4C5A40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_005D_01BF8DA0.2F4C5A40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all I came across the work of this group for the first time last week and = think it is brilliant. Consequently, we are now in the midst of adding = iCalendar functionality to our web application. I have a question in relation to the vTODO items. It seems that Outlook = currently does not support vToDO items, at least my version of Outlook = 2000 doesn't (although it does support ics files and vEvents). Can anyone tell me where I can find out what mail clients currently = support or intend to support vToDo items. cheers Richard ------=_NextPart_000_005D_01BF8DA0.2F4C5A40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi all
 
I came across the work of this group = for the first=20 time last week and think it is brilliant. Consequently, we are now in = the midst=20 of adding iCalendar functionality to our web application.
 
I have a question in relation to the = vTODO items.=20 It seems that Outlook currently does not support vToDO items, at least = my=20 version of Outlook 2000 doesn't (although it does support ics files and=20 vEvents).
 
Can anyone tell me where I can find out = what mail=20 clients currently support or intend to support vToDo items.
 
cheers
 
Richard
------=_NextPart_000_005D_01BF8DA0.2F4C5A40-- From owner-ietf-calendar@mail.imc.org Mon Mar 13 19:12:47 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11002 for ; Mon, 13 Mar 2000 19:12:46 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id PAA27453 for ietf-calendar-bks; Mon, 13 Mar 2000 15:56:26 -0800 (PST) Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA27449; Mon, 13 Mar 2000 15:56:25 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id TAA27149; Mon, 13 Mar 2000 19:13:26 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id SAA10091; Mon, 13 Mar 2000 18:57:01 -0500 (EST) To: "Richard Antill" Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: Implementations of vToDo items X-Mailer: Lotus Notes Release 5.0.2b December 16, 1999 Message-ID: Date: Mon, 13 Mar 2000 18:55:15 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/13/2000 06:55:16 PM, Serialize complete at 03/13/2000 06:55:16 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 000017B0852568A2_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 000017B0852568A2_= Content-Type: text/plain; charset="us-ascii" Richard: The VTODO object is support both by Lotus Organizer v6.0 and also by the prototype iCalendar support for Lotus Notes r5, found on the www.notes.net website (search for "Notes iCalendar Support"). -- Frank --=_alternative 000017B0852568A2_= Content-Type: text/html; charset="us-ascii"
Richard:

The VTODO object is support both by Lotus Organizer v6.0 and also by the prototype iCalendar support for Lotus Notes r5, found on the www.notes.net website (search for "Notes iCalendar Support").

-- Frank

--=_alternative 000017B0852568A2_=-- From owner-ietf-calendar@mail.imc.org Mon Mar 13 23:27:31 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11177 for ; Mon, 13 Mar 2000 23:27:31 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA09111 for ietf-calendar-bks; Mon, 13 Mar 2000 20:09:48 -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 UAA09105 for ; Mon, 13 Mar 2000 20:09:47 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id UAA12432 for ; Mon, 13 Mar 2000 20:05:54 -0800 (PST) Received: from netscape.com ([198.93.95.223]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FRE8XE00.CI3; Mon, 13 Mar 2000 20:10:26 -0800 Message-ID: <38CDBB65.51A40097@netscape.com> Date: Mon, 13 Mar 2000 20:09:09 -0800 From: Steve Mansour X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Richard Antill CC: ietf-calendar@imc.org Subject: Re: Implementations of vToDo items References: <006001bf8d4c$5dc7f680$09de0dcb@ringtail.com.au> Content-Type: multipart/mixed; boundary="------------3F2F8E198E2035FF84B4A79F" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------3F2F8E198E2035FF84B4A79F Content-Type: multipart/alternative; boundary="------------F65682918CE61F8BDDC628E5" --------------F65682918CE61F8BDDC628E5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit iPlanet Calendar Server 2.x comes with a web client that supports sending VTODOs by email. -Steve Richard Antill wrote: > Hi all I came across the work of this group for the first time last > week and think it is brilliant. Consequently, we are now in the midst > of adding iCalendar functionality to our web application. I have a > question in relation to the vTODO items. It seems that Outlook > currently does not support vToDO items, at least my version of Outlook > 2000 doesn't (although it does support ics files and vEvents). Can > anyone tell me where I can find out what mail clients currently > support or intend to support vToDo items. cheers Richard --------------F65682918CE61F8BDDC628E5 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit iPlanet Calendar Server 2.x comes with a web client that supports sending VTODOs by email.
-Steve

Richard Antill wrote:

Hi all I came across the work of this group for the first time last week and think it is brilliant. Consequently, we are now in the midst of adding iCalendar functionality to our web application. I have a question in relation to the vTODO items. It seems that Outlook currently does not support vToDO items, at least my version of Outlook 2000 doesn't (although it does support ics files and vEvents). Can anyone tell me where I can find out what mail clients currently support or intend to support vToDo items. cheers Richard
--------------F65682918CE61F8BDDC628E5-- --------------3F2F8E198E2035FF84B4A79F 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;fax:650-937-2103 tel;work:650-937-2378 x-mozilla-html:FALSE org:Netscape version:2.1 email;internet:sman@netscape.com title:Judge, Jury, and Executioner adr;quoted-printable:;;501 East Middlefield Road=0D=0AMS: MV-054;Mountain View;CA;94043; x-mozilla-cpt:;-10552 fn:Steve Mansour end:vcard --------------3F2F8E198E2035FF84B4A79F-- From owner-ietf-calendar@mail.imc.org Wed Mar 15 06:47:14 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07933 for ; Wed, 15 Mar 2000 06:47:13 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id DAA26248 for ietf-calendar-bks; Wed, 15 Mar 2000 03:20:14 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id DAA26244 for ; Wed, 15 Mar 2000 03:20:12 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27917; Wed, 15 Mar 2000 06:21:26 -0500 (EST) Message-Id: <200003151121.GAA27917@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-calendar@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-calsch-cap-02.txt Date: Wed, 15 Mar 2000 06:21:25 -0500 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Calendaring and Scheduling Working Group of the IETF. Title : Calendar Access Protocol (CAP) Author(s) : S. Mansour, F. Dawson, D. Royer, A. Taler, P. Hill Filename : draft-ietf-calsch-cap-02.txt Pages : 101 Date : 14-Mar-00 The Calendar Access Protocol (CAP)is an Internet protocol that permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an [RFC2445] based Calendar Store (CS). This memo defines the CAP specification. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-calsch-cap-02.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-calsch-cap-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-calsch-cap-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000314132318.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-calsch-cap-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-calsch-cap-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000314132318.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-calendar@mail.imc.org Fri Mar 17 14:11:21 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14035 for ; Fri, 17 Mar 2000 14:11:20 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA19728 for ietf-calendar-bks; Fri, 17 Mar 2000 10:46:26 -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 KAA19724 for ; Fri, 17 Mar 2000 10:46:24 -0800 (PST) Received: from tintin.mcom.com (tintin.mcom.com [205.217.233.42]) by netscape.com (8.8.5/8.8.5) with ESMTP id KAA16928 for ; Fri, 17 Mar 2000 10:42:42 -0800 (PST) Received: from netscape.com ([207.1.151.176]) by tintin.mcom.com (Netscape Messaging Server 4.1) with ESMTP id FRKXIY00.2ZF for ; Fri, 17 Mar 2000 10:47:22 -0800 Message-ID: <38D27D5D.F606004@netscape.com> Date: Fri, 17 Mar 2000 10:45:49 -0800 From: rans@netscape.com (Richard Shusterman) Organization: Netscape Communications Corp. X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47 (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Sun/Netscape Alliance supports CAP References: Content-Type: multipart/alternative; boundary="------------7F39756298EF32FC8FA6E54E" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --------------7F39756298EF32FC8FA6E54E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sometimes silence is not golden :) This is to re-iterate the Sun/Netscape Alliance commitment to implementing and offering, in all our calendar products, support for all IETF Calendar and Scheduling WG standards, including iCalendar/iTIP/iMIP and the "soon to be finished" CAP. We will also participate in the upcoming CalConnect and in future CAP testing with any/all implementors who want to demonstrate interoperability in these standards. Steve Mansour and I will be attending the upcoming IETF Calendar and Scheduling WG meetings in Adelaide, Australia and we are prepared and willing to discuss how to finish CAP as soon as possible. If anyone questions our willingness to implement/offer standards support, they should download/test our iPlanet Calendar Server product, which was released in Oct 1999 and which supports iCalendar/iTIP/iMIP. We will also implement/offer CAP support when it's a standard. --------------7F39756298EF32FC8FA6E54E Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Sometimes silence is not golden :)

This is to re-iterate the Sun/Netscape Alliance commitment to implementing and offering, in all our calendar products, support for all IETF Calendar and Scheduling WG standards, including iCalendar/iTIP/iMIP and the "soon to be finished" CAP. We will also participate in the upcoming CalConnect and in future CAP testing with any/all implementors who want to demonstrate interoperability in these standards.

Steve Mansour and I will be attending the upcoming IETF Calendar and Scheduling WG meetings in Adelaide, Australia and we are prepared and willing to discuss how to finish CAP as soon as possible. If anyone questions our willingness to implement/offer standards support, they should download/test our iPlanet Calendar Server product, which was released in Oct 1999 and which supports iCalendar/iTIP/iMIP. We will also implement/offer CAP support when it's a standard.
 
  --------------7F39756298EF32FC8FA6E54E-- From owner-ietf-calendar@mail.imc.org Sun Mar 19 03:21:37 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08009 for ; Sun, 19 Mar 2000 03:21:36 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA16377 for ietf-calendar-bks; Sat, 18 Mar 2000 23:58:44 -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 XAA16373 for ; Sat, 18 Mar 2000 23:58:43 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA28484 for ietf-calendar@imc.org; Sun, 19 Mar 2000 00:00:07 -0800 (PST) Date: Sun, 19 Mar 2000 00:00:07 -0800 (PST) From: Doug Royer Message-Id: <200003190800.AAA28484@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 U user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and U 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 CAP draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex N text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug N C-4 VCAR examples Doug? N C-5 PUBLISH text C-6 REQUEST text C-7 REPLY text C-8 ADD text C-9 CANCEL text C-10 REFRESH text C-11 COUNTER text C-12 DECLINECOUNTER Text C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property C-16 (2.11) Query Schema I'll send this out next week. C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS Format? Text needs to be written. C-20 (13.) Security Considerations See editors note - more text. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: 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 ------------------------------------------------------------------------------ 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 From owner-ietf-calendar@mail.imc.org Sun Mar 19 12:15:24 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11543 for ; Sun, 19 Mar 2000 12:15:23 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id IAA27349 for ietf-calendar-bks; Sun, 19 Mar 2000 08:51:12 -0800 (PST) Received: from egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA27345 for ; Sun, 19 Mar 2000 08:51:10 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Subject: CalConnect Details X-Mailer: Lotus Notes Release 5.0.1a August 17, 1999 Message-ID: Date: Sun, 19 Mar 2000 11:52:37 -0500 X-Priority: 3 (Normal) X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.1a|August 17, 1999) at 03/19/2000 11:52:39 AM, Serialize complete at 03/19/2000 11:52:39 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 005CAEDC852568A7_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 005CAEDC852568A7_= Content-Type: text/plain; charset="us-ascii" This is the final information on the CalConnect Interoperability Testing. Dates: ------------------- The official dates for the CalConnect testing are April 11 - 12. These will be two full days of testing so participants should allow for travel on Monday, 4/10 and Thursday, 4/13. Testing will be held at MIT in Cambridge. The exact room name will be provided right before the day of the meeting. Testing Schedule and rules: -------------------------------------------- The preliminary schedule is as follows. Continental breakfast, Lunch and breaks will be provided. In addition, dinner on Tuesday, 4/11 will be provided on site. Tuesday, April 11 8:30 - Breakfast, setup, introductions and coordination 9:30 - 12:00 - Testing 12:00 - lunch served (buffet - sandwiches) 1:00 - until - Testing Around 6:00 dinner will be brought in - participants can eat at their leisure Wednesday, April 12 8:30 - breakfast 9:00 - 12:00 - Testing 12:00 - lunch 1:00 - 4:30 - Testing 4:30 on - Review and shut down Hotel Accommodations: Testing rules: ----------------------- Participants bring their own equipment and software. Ethernet connectivity and networking will be provided as well as a mail server and access to the Internet. Testing of applications and code is open. This means there are no set steps or processes involved. You will have a list of participants and will know what each vendor or representative wants to test. It is every recipients responsibility to find other participants to test applications. This effort will test everything we can on iCalendar, iTIP and iMIP. The major emphasis will be on the iCalendar protocol. The chairs will provide a matrix of all MUST, CAN and SHOULD statements that can be used to help "check off" what is working and what is not. Each participant is expected to detail what works and what does not and expected plans for fixing or not fixing sections that do not work. If nothing will happen on a specific item and participants do not plan to fix or make pieces work, those items must be removed from the draft. The key rule is "What happens during testing remains in the room." It is expected that participants will honor this rule. No press is allowed and for the participants, please do not bring Marketing staff. The chairs of the CALSCH working group will publish the results and further the movement of the RFC towards Standard activation. Hotel Accommodations: ------------------------------------ A reduced rate for visitors to MIT is available at the Hyatt Regency, Marriott, and Sonesta hotels in Cambridge and at several Boston hotels, depending on the season. Visitors must request the MIT rate when reserving a room and when registering. Marriott information: 2 Cambridge Center, Phone: 617-494-6600 Hyatt information: 575 Memorial Drive, Phone: 617 492 1234 Sonesta information: 5 Cambridge Parkway, Phone: 617-806-4200 Directions: Getting to MIT from Logan Airport: ----------------------------------------------------------------- Taxi. Taxi fare from the airport is about $15. Under normal traffic conditions the taxi ride will take about 15 minutes. Subway. The subway ride from Logan involves several transfers. From any terminal at Logan airport, take the airport shuttle bus to the Blue Line subway station. Take the Blue Line to the Government Center station and go upstairs to and take the Green Line trolley to Park Street. At the Park Street station, go downstairs and take the Red Line subway to Kendall/MIT (take the outbound train toward Alewife). Under normal conditions the ride will take about one-half hour. Car. The drive from Logan airport can be rather nasty, depending on traffic conditions. Take the main exit from the airport (not the Ted Williams Tunnel) and follow the signs toward Boston via the Sumner Tunnel. The tunnel toll is US $1. As you exit the tunnel, turn right onto the expressway (93 North). Take the second exit, marked 'Storrow Drive West'. Immediately take the right fork of the road to a stoplight. Turn left, then immediately turn right and drive over the Charles River. The Boston Museum of Science will be on your left. Turn left at the next stoplight onto Memorial Drive. Follow Memorial Drive for about a half mile and MIT will be on your right side. Additional information and a map can be found at: http://whereis.mit.edu/doc/getting-to-mit.html --=_alternative 005CAEDC852568A7_= Content-Type: text/html; charset="us-ascii"
This is the final information on the CalConnect Interoperability Testing.

Dates:
-------------------
The official dates for the CalConnect testing are April 11 - 12. These will be two full days of testing so participants should allow for travel on Monday, 4/10  and Thursday, 4/13.  Testing will be held at MIT in Cambridge.  The exact room name will be provided right before the day of the meeting.

Testing Schedule and rules:
--------------------------------------------
The preliminary schedule is as follows. Continental breakfast, Lunch and breaks will be provided.  In addition, dinner on Tuesday, 4/11 will be provided on site.

Tuesday, April 11
8:30 - Breakfast, setup, introductions and coordination
9:30 - 12:00 - Testing
12:00 - lunch served (buffet - sandwiches)
1:00 - until - Testing
Around 6:00 dinner will be brought in - participants can eat at their leisure

Wednesday, April 12
8:30 - breakfast
9:00 - 12:00 - Testing
12:00 - lunch
1:00 - 4:30 - Testing
4:30 on - Review and shut down
Hotel Accommodations:

Testing rules:
-----------------------
Participants bring their own equipment and software.  Ethernet connectivity and networking will be provided as well as a mail server and access to the Internet.  Testing of applications and code is open.  This means there are no set steps or processes involved.  You will have a list of participants and will know what each vendor or representative wants to test. It is every recipients responsibility to find other participants to test applications.

This effort will test everything we can on iCalendar, iTIP and iMIP.  The major emphasis will be on the iCalendar protocol.  The chairs will provide a matrix of all MUST, CAN and SHOULD statements that can be used to help "check off" what is working and what is not.  Each participant is expected to detail what works and what does not and expected plans for fixing or not fixing sections that do not work.  If nothing will happen on a specific item and participants do not plan to fix or make pieces work, those items must be removed from the draft.

The key rule is "What happens during testing remains in the room."  It is expected that participants will honor this rule.  No press is allowed and for the participants, please do not bring Marketing staff.

The chairs of the CALSCH working group will publish the results and further the movement of the RFC towards Standard activation.

Hotel Accommodations:
------------------------------------
A reduced rate for visitors to MIT is available at the Hyatt Regency, Marriott, and Sonesta hotels in Cambridge and at several Boston hotels, depending on the season. Visitors must request the MIT rate when reserving a room and when registering.

Marriott information:          2 Cambridge Center,  Phone: 617-494-6600
Hyatt information:         575 Memorial Drive,   Phone: 617 492 1234
Sonesta information:        5 Cambridge Parkway, Phone: 617-806-4200

Directions: Getting to MIT from Logan Airport:
-----------------------------------------------------------------
Taxi. Taxi fare from the airport is about $15. Under normal traffic conditions the taxi ride will take about 15 minutes.

Subway. The subway ride from Logan involves several transfers. From any terminal at Logan airport, take the airport shuttle bus to the Blue Line subway station. Take the Blue Line to the Government Center station and go upstairs to and take the Green Line trolley to Park Street. At the Park Street station, go downstairs and take the Red Line subway to Kendall/MIT (take the outbound train toward Alewife). Under normal conditions the ride will take about one-half hour.

Car. The drive from Logan airport can be rather nasty, depending on traffic conditions. Take the main exit from the airport (not the Ted Williams Tunnel) and follow the signs toward Boston via the Sumner Tunnel. The tunnel toll is US $1. As you exit the tunnel, turn right onto the expressway (93 North). Take the second exit, marked 'Storrow Drive West'. Immediately take the right fork of the road to a stoplight. Turn left, then immediately turn right and drive over the Charles River. The Boston Museum of Science will be on your left. Turn left at the next stoplight onto Memorial Drive. Follow Memorial Drive for about a half mile and MIT will be on your right side.

Additional information and a map can be found at: http://whereis.mit.edu/doc/getting-to-mit.html --=_alternative 005CAEDC852568A7_=-- From owner-ietf-calendar@mail.imc.org Sun Mar 19 13:08:16 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04018 for ; Sun, 19 Mar 2000 13:08:14 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA27826 for ietf-calendar-bks; Sun, 19 Mar 2000 09:48:19 -0800 (PST) Received: from mail.chronolabs.de (qmailr@mail.chronolabs.de [62.154.158.51]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id JAA27822 for ; Sun, 19 Mar 2000 09:48:17 -0800 (PST) Received: (qmail 19755 invoked from network); 19 Mar 2000 17:49:52 -0000 Received: from unknown (HELO holger.openical.org) (62.154.158.50) by mail.chronolabs.de with SMTP; 19 Mar 2000 17:49:52 -0000 Message-Id: <4.3.0.20000319184407.00a84ae0@mail.chronolabs.de> X-Sender: oichs01@mail.openical.org X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Sun, 19 Mar 2000 18:49:46 +0100 To: ietf-calendar@imc.org From: Holger Schmidt Subject: CAP Draft - 4.3. Response Format Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: <---> 4.3. Response Format Server responses consist of a response code and any parameters: [response args] [; debug text ; more text] . [] . <---> if there is no application data, should it end with .. ? or should be [response args] [; debug text ; more text] . [ .] H. Schmidt From owner-ietf-calendar@mail.imc.org Wed Mar 22 00:15:49 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05147 for ; Wed, 22 Mar 2000 00:15:48 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA23108 for ietf-calendar-bks; Tue, 21 Mar 2000 20:41:43 -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 UAA23103 for ; Tue, 21 Mar 2000 20:41:42 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id UAA03499 for ; Tue, 21 Mar 2000 20:38:14 -0800 (PST) Received: from netscape.com ([198.93.95.223]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FRT3RQ02.M0C for ; Tue, 21 Mar 2000 20:43:02 -0800 Message-ID: <38D84F90.C73CF82C@netscape.com> Date: Tue, 21 Mar 2000 20:44:00 -0800 From: Steve Mansour X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: CalSched IETF Subject: CalConnect participants? Content-Type: multipart/mixed; boundary="------------D760248D6212F13989CC0C74" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------D760248D6212F13989CC0C74 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I never saw a list of participants for cal-connect. Sun/Netscape will be there. Which companies plan to be at cal-connect? -Steve --------------D760248D6212F13989CC0C74 Content-Type: text/x-vcard; charset=us-ascii; name="sman.vcf" Content-Description: Card for Steve Mansour Content-Disposition: attachment; filename="sman.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Mansour;Steve tel;fax:650-937-2103 tel;work:650-937-2378 x-mozilla-html:FALSE org:Netscape version:2.1 email;internet:sman@netscape.com title:Judge, Jury, and Executioner adr;quoted-printable:;;501 East Middlefield Road=0D=0AMS: MV-054;Mountain View;CA;94043; x-mozilla-cpt:;-10552 fn:Steve Mansour end:vcard --------------D760248D6212F13989CC0C74-- From owner-ietf-calendar@mail.imc.org Wed Mar 22 00:57:31 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22807 for ; Wed, 22 Mar 2000 00:57:29 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id VAA24800 for ietf-calendar-bks; Tue, 21 Mar 2000 21:29:51 -0800 (PST) Received: from lotus.lotus.com (lotus.lotus.com [192.233.136.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id VAA24796 for ; Tue, 21 Mar 2000 21:29:49 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus.lotus.com (8.9.3/8.9.3) with ESMTP id AAA01196; Wed, 22 Mar 2000 00:22:50 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id AAA02324; Wed, 22 Mar 2000 00:31:07 -0500 (EST) To: Steve Mansour Cc: ietf-calendar@imc.org Subject: Re: CalConnect participants? X-Mailer: Lotus Notes Release 5.0.2c February 2, 2000 Message-ID: Date: Wed, 22 Mar 2000 00:28:51 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/22/2000 12:28:52 AM, Serialize complete at 03/22/2000 12:28:52 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 001ECD83852568AA_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 001ECD83852568AA_= Content-Type: text/plain; charset="us-ascii" Better yet...When is it. We need at least 2 weeks notice! --=_alternative 001ECD83852568AA_= Content-Type: text/html; charset="us-ascii"
Better yet...When is it. We need at least 2 weeks notice! --=_alternative 001ECD83852568AA_=-- From owner-ietf-calendar@mail.imc.org Wed Mar 22 01:07:05 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26669 for ; Wed, 22 Mar 2000 01:07:04 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id VAA25062 for ietf-calendar-bks; Tue, 21 Mar 2000 21:44:17 -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 VAA25058 for ; Tue, 21 Mar 2000 21:44:16 -0800 (PST) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id VAA06893 for ; Tue, 21 Mar 2000 21:40:48 -0800 (PST) Received: from netscape.com ([198.93.95.152]) by dredd.mcom.com (Netscape Messaging Server 4.1 Aug 9 1999 18:28:31) with ESMTP id FRT6O000.7EA; Tue, 21 Mar 2000 21:45:36 -0800 Message-ID: <38D85DE5.8F640B7E@netscape.com> Date: Tue, 21 Mar 2000 21:45:10 -0800 From: sman@netscape.com (Steve Mansour) X-Mailer: Mozilla 4.73b1 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Frank_Dawson@lotus.com CC: ietf-calendar@imc.org Subject: Re: CalConnect participants? References: Content-Type: multipart/mixed; boundary="------------ADF6E04954F134AF265C9EE7" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------ADF6E04954F134AF265C9EE7 Content-Type: multipart/alternative; boundary="------------1291ACA672934ED0FDF481D2" --------------1291ACA672934ED0FDF481D2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Pat sent out the details: http://www.imc.org/ietf-calendar/mail-archive/msg04064.html -Steve Frank_Dawson@lotus.com wrote: > > Better yet...When is it. We need at least 2 weeks notice! --------------1291ACA672934ED0FDF481D2 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Pat sent out the details:  http://www.imc.org/ietf-calendar/mail-archive/msg04064.html

-Steve

Frank_Dawson@lotus.com wrote:

 
Better yet...When is it. We need at least 2 weeks notice!
--------------1291ACA672934ED0FDF481D2-- --------------ADF6E04954F134AF265C9EE7 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 x-mozilla-html:FALSE adr:;;;;;; version:2.1 email;internet:sman@netscape.com title:Judge, Jury, and Executioner fn:Steve Mansour end:vcard --------------ADF6E04954F134AF265C9EE7-- From owner-ietf-calendar@mail.imc.org Wed Mar 22 07:24:57 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23234 for ; Wed, 22 Mar 2000 07:24:56 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id EAA14650 for ietf-calendar-bks; Wed, 22 Mar 2000 04:02:29 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id EAA14644 for ; Wed, 22 Mar 2000 04:02:28 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA23805; Wed, 22 Mar 00 07:04:04 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id HAA22304; Wed, 22 Mar 2000 07:04:04 -0500 (EST) Received: from [18.177.1.27] (bobmah-2.dsl.speakeasy.net [216.254.65.44]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id HAA16269; Wed, 22 Mar 2000 07:03:52 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: In-Reply-To: <38D85DE5.8F640B7E@netscape.com> References: <38D85DE5.8F640B7E@netscape.com> Date: Wed, 22 Mar 2000 07:03:48 -0500 To: sman@netscape.com (Steve Mansour) From: Bob Mahoney Subject: Re: CalConnect participants? Cc: Frank_Dawson@lotus.com, ietf-calendar@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 9:45 PM -0800 3/21/00, Steve Mansour wrote: >Pat sent out the details: >http://www.imc.org/ietf-calendar/mail-archive/msg04064.html If people can drop Pat and I a note with the number of participants from their company/group, I'd appreciate it. Please also indicate any dietary restrictions. -Bob From owner-ietf-calendar@mail.imc.org Wed Mar 22 10:09:06 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20681 for ; Wed, 22 Mar 2000 10:09:05 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA19150 for ietf-calendar-bks; Wed, 22 Mar 2000 06:45:40 -0800 (PST) Received: from lotus.lotus.com (lotus.lotus.com [192.233.136.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA19145; Wed, 22 Mar 2000 06:45:39 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet1.lotus.com (internet1 [9.95.4.235]) by lotus.lotus.com (8.9.3/8.9.3) with ESMTP id JAA17209; Wed, 22 Mar 2000 09:38:38 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet1.lotus.com (8.9.3/8.9.3) with ESMTP id JAA26387; Wed, 22 Mar 2000 09:24:48 -0500 (EST) To: Bob Mahoney Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org, sman@netscape.com (Steve Mansour) Subject: Re: CalConnect participants? X-Mailer: Lotus Notes Release 5.0.2c February 2, 2000 Message-ID: Date: Wed, 22 Mar 2000 09:22:27 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/22/2000 09:22:34 AM, Serialize complete at 03/22/2000 09:22:34 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 004FC655852568AA_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 004FC655852568AA_= Content-Type: text/plain; charset="us-ascii" Bob: Thanks! I missed this Sunday posting. Appreciate you reposting it. Information is good. However, the toll is now $2 for the tunnel! Who is developing the matrix of MUST/SHOULD/NOT? We actually need three. One for RFC2425, RFC2426 and RFC2427. Why not also test vCard support? There is a companion RFC for carrying C&S info in vCard. We should be testing this also. -- Frank --=_alternative 004FC655852568AA_= Content-Type: text/html; charset="us-ascii"
Bob:

Thanks! I missed this Sunday posting. Appreciate you reposting it.

Information is good. However, the toll is now $2 for the tunnel!

Who is developing the matrix of MUST/SHOULD/NOT? We actually need three. One for RFC2425, RFC2426 and RFC2427.

Why not also test vCard support? There is a companion RFC for carrying C&S info in vCard. We should be testing this also.

-- Frank --=_alternative 004FC655852568AA_=-- From owner-ietf-calendar@mail.imc.org Wed Mar 22 10:18:19 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24421 for ; Wed, 22 Mar 2000 10:18:18 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA19304 for ietf-calendar-bks; Wed, 22 Mar 2000 06:53:30 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id GAA19300 for ; Wed, 22 Mar 2000 06:53:28 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA09462; Wed, 22 Mar 00 09:56:46 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id JAA16367; Wed, 22 Mar 2000 09:55:07 -0500 (EST) Received: from [18.177.1.27] (bobmah-2.dsl.speakeasy.net [216.254.65.44]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id JAA12182; Wed, 22 Mar 2000 09:55:07 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: In-Reply-To: References: Date: Wed, 22 Mar 2000 09:55:03 -0500 To: , Pat Egen From: Bob Mahoney Subject: Re: CalConnect participants? Cc: Bob Mahoney , ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org, sman@netscape.com (Steve Mansour) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I'm travelling today, but Pat and I began working on the matrix. (We're just pulling this from the document) We will have this done in time. We'll probably be working on this by mail during the meeting. I guess I don't have a strong opinion on the vCard testing... Pat? Sorry about that tunnel thing- you'd be astonished how many of my suggestions the government simply ignores... ;^) -Bob At 9:22 AM -0500 3/22/00, Frank_Dawson@lotus.com wrote: >Bob: > >Thanks! I missed this Sunday posting. Appreciate you reposting it. > >Information is good. However, the toll is now $2 for the tunnel! > >Who is developing the matrix of MUST/SHOULD/NOT? We actually need >three. One for RFC2425, RFC2426 and RFC2427. > >Why not also test vCard support? There is a companion RFC for >carrying C&S info in vCard. We should be testing this also. > >-- Frank From owner-ietf-calendar@mail.imc.org Wed Mar 22 10:19:49 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25037 for ; Wed, 22 Mar 2000 10:19:49 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id GAA19316 for ietf-calendar-bks; Wed, 22 Mar 2000 06:53:40 -0800 (PST) Received: from egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA19312 for ; Wed, 22 Mar 2000 06:53:39 -0800 (PST) From: pregen@egenconsulting.com To: Frank_Dawson@lotus.com Cc: ietf-calendar@imc.org, sman@netscape.com Subject: Re: CalConnect participants? X-Mailer: Lotus Notes Release 5.0.1a August 17, 1999 Message-ID: Date: Wed, 22 Mar 2000 09:55:38 -0500 X-Priority: 3 (Normal) X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.1a|August 17, 1999) at 03/22/2000 09:55:22 AM, Serialize complete at 03/22/2000 09:55:22 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0051DDFB852568AA_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0051DDFB852568AA_= Content-Type: text/plain; charset="us-ascii" Frank, we posted the dates a month ago. In fact, we changed the date to start on 4/11, Tuesday, at your request. You asked if we move it to a Tuesday so you could spend some time with your family. I checked with other participants and they said OK to date change. Monday I sent the particulars to the list, (including starting times, hotel information, etc. ) Please check your email inbasket. Participants who have responded were: Lotus Netscape Doug Royer Eric Busboom (open source work) There are two additional parties that we are waiting on confirmation. Hope that helps. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 0051DDFB852568AA_= Content-Type: text/html; charset="us-ascii"
Frank, we posted the dates a month ago.  In fact, we changed the date to start on 4/11, Tuesday, at your request.  You asked if we move it to a Tuesday so you could spend some time with your family.  I checked with other participants and they said OK to date change. Monday I sent the particulars to the list, (including starting times, hotel information, etc. ) Please check your email inbasket.

Participants who have responded were:

Lotus
Netscape
Doug Royer
Eric Busboom (open source work)

There are two additional parties that we are waiting on confirmation.

Hope that helps.

___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 0051DDFB852568AA_=-- From owner-ietf-calendar@mail.imc.org Wed Mar 22 15:27:03 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16449 for ; Wed, 22 Mar 2000 15:27:02 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA25306 for ietf-calendar-bks; Wed, 22 Mar 2000 12:02:25 -0800 (PST) Received: from egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA25302 for ; Wed, 22 Mar 2000 12:02:23 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Subject: Additional Info on CalConnect X-Mailer: Lotus Notes Release 5.0.1a August 17, 1999 Message-ID: Date: Wed, 22 Mar 2000 15:04:35 -0500 X-Priority: 3 (Normal) X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.1a|August 17, 1999) at 03/22/2000 03:04:07 PM, Serialize complete at 03/22/2000 03:04:07 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 006E26EE852568AA_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 006E26EE852568AA_= Content-Type: text/plain; charset="us-ascii" This is an additional note to provide a few more details. These were noted earlier, but I want to provide the info again. The cost of participation at CalConnect is $1000. You are allowed two participants. If you are going to bring more, the cost is $500 per person and we must know in advance. Payment can be by check or Master Charge or Visa. The following is a link to CalConnect details, including the testing Matrixes (still under final proofing). http://www.egenconsulting.com/calconnect1.html ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 006E26EE852568AA_= Content-Type: text/html; charset="us-ascii"
This is an additional note to provide a few more details.  These were noted earlier, but I want to provide the info again.

The cost of participation at CalConnect is $1000.  You are allowed two participants.  If you are going to bring more, the cost is $500 per person and we must know in advance.

Payment can be by check or Master Charge or Visa.

The following is a link to CalConnect details, including the testing Matrixes (still under final proofing). http://www.egenconsulting.com/calconnect1.html

___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 006E26EE852568AA_=-- From owner-ietf-calendar@mail.imc.org Thu Mar 23 14:13:06 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09580 for ; Thu, 23 Mar 2000 14:13:04 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA15021 for ietf-calendar-bks; Thu, 23 Mar 2000 10:46:35 -0800 (PST) Received: from lotus.lotus.com (lotus.lotus.com [192.233.136.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA15016 for ; Thu, 23 Mar 2000 10:46:33 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus.lotus.com (8.9.3/8.9.3) with ESMTP id NAA28856; Thu, 23 Mar 2000 13:39:23 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id NAA23136; Thu, 23 Mar 2000 13:47:39 -0500 (EST) To: pregen@egenconsulting.com, bobmah@mit.edu Cc: ietf-calendar@imc.org Subject: CalConnect Payment X-Mailer: Lotus Notes Release 5.0.2c February 2, 2000 Message-ID: Date: Thu, 23 Mar 2000 13:45:17 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/23/2000 01:45:20 PM, Serialize complete at 03/23/2000 01:45:20 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0067DEF2852568AB_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0067DEF2852568AB_= Content-Type: text/plain; charset="us-ascii" Pat and Bob: Didn't see that AMEX listed as a payment option, so I guess an old fashion check will have to do. If we want a company check cut, we need a name, address, phone info for the process. Can you please post this info for us. Thanks. -- Frank --=_alternative 0067DEF2852568AB_= Content-Type: text/html; charset="us-ascii"
Pat and Bob:

Didn't see that AMEX listed as a payment option, so I guess an old fashion check will have to do.

If we want a company check cut, we need a name, address, phone info for the process. Can you please post this info for us. Thanks.

-- Frank

--=_alternative 0067DEF2852568AB_=-- From owner-ietf-calendar@mail.imc.org Sun Mar 26 03:24:12 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02937 for ; Sun, 26 Mar 2000 03:24:09 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id XAA15987 for ietf-calendar-bks; Sat, 25 Mar 2000 23:58:09 -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 XAA15983 for ; Sat, 25 Mar 2000 23:58:07 -0800 (PST) Received: (from doug@localhost) by royer.com (8.9.1/8.9.1) id AAA04108 for ietf-calendar@imc.org; Sun, 26 Mar 2000 00:00:06 -0800 (PST) Date: Sun, 26 Mar 2000 00:00:06 -0800 (PST) From: Doug Royer Message-Id: <200003260800.AAA04108@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 U user and how UPN's are used in LDAP and certificates. W-19 CAP Group definitions, dynamic and U 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 CAP draft editors: Draft Action Item Who Done (Y/N) ----------------- --- ---------- C-1 Remove unused definitions N C-2 Fix up changes in authentication Alex N text as commented on the list Paul C-3 Text for 2.7 [Finding CAP Servers] Doug N C-4 VCAR examples Doug? N C-5 PUBLISH text C-6 REQUEST text C-7 REPLY text C-8 ADD text C-9 CANCEL text C-10 REFRESH text C-11 COUNTER text C-12 DECLINECOUNTER Text C-13 Post CAP-00.txt Y C-14 Redo state diagram to include STARTTLS and IDENTIFY command. C-15 Document the 'CALMASTER' calendar property C-16 (2.11) Query Schema I'll send this out next week. C-17 (7.2.1.5) MOVE Method More text needed - Who? C-18 (12.1) Calendar Store Properties Editors note. (Per W-27) C-19 (12.2) SCHEDULABLE-HOURS Format? Text needs to be written. C-20 (13.) Security Considerations See editors note - more text. ------------------------------------------------------------------------------ The following are a list of action items for the iCalendar-2 draft: 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 ------------------------------------------------------------------------------ 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 From owner-ietf-calendar@mail.imc.org Sun Mar 26 03:26:54 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04570 for ; Sun, 26 Mar 2000 03:26:53 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id AAA16406 for ietf-calendar-bks; Sun, 26 Mar 2000 00:12:30 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id AAA16401 for ; Sun, 26 Mar 2000 00:12:28 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA28248; Sun, 26 Mar 00 03:16:17 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id DAA01838; Sun, 26 Mar 2000 03:14:36 -0500 (EST) Received: from [169.208.192.18] (dhcp-192-18.ietf.connect.com.au [169.208.192.18]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id DAA03069; Sun, 26 Mar 2000 03:14:31 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: In-Reply-To: References: Date: Sun, 26 Mar 2000 17:44:23 +0930 To: From: Bob Mahoney Subject: Re: CalConnect Payment Cc: pregen@egenconsulting.com, bobmah@mit.edu, ietf-calendar@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Frank- Unfortunately, the credit card process I had hoped would be in place is not yet ready, so we're left with checks. Checks should be made out to: "MIT" And should be mailed to me: Bob Mahoney MIT E40-327 77 Massachusetts Avenue Cambridge, MA 02139 (617) 253-0774 (Note that I am in Adelaide at the moment, so calling me in Cambridge isn't very useful. If this is a problem for anyone's check-cutting department, I can try and convince someone in Cambridge to take calls on this, although you can always have your money folks leave messages for me at the Stamford Plaza here... :-) -Bob At 1:45 PM -0500 3/23/00, Frank_Dawson@lotus.com wrote: >Pat and Bob: > >Didn't see that AMEX listed as a payment option, so I guess an old >fashion check will have to do. > >If we want a company check cut, we need a name, address, phone info >for the process. Can you please post this info for us. Thanks. > >-- Frank From owner-ietf-calendar@mail.imc.org Mon Mar 27 20:08:32 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28310 for ; Mon, 27 Mar 2000 20:08:31 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id QAA19517 for ietf-calendar-bks; Mon, 27 Mar 2000 16:36:01 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id QAA19511 for ; Mon, 27 Mar 2000 16:35:59 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA28213; Mon, 27 Mar 00 19:38:11 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id TAA25839 for ; Mon, 27 Mar 2000 19:38:17 -0500 (EST) Received: from [169.208.192.18] (dhcp-192-18.ietf.connect.com.au [169.208.192.18]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id TAA23443 for ; Mon, 27 Mar 2000 19:38:13 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: Date: Tue, 28 Mar 2000 10:08:17 +0930 To: ietf-calendar@imc.org From: Bob Mahoney Subject: Casual CalSch dinner tonight Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: If any of the calsch folks in Adelaide would like to catch up for a casual dinner tonight, some of us will be meeting near the Conference Center registration desk tonight at 6:00. Come and talk calendars while we eat! -Bob From owner-ietf-calendar@mail.imc.org Mon Mar 27 22:55:40 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02892 for ; Mon, 27 Mar 2000 22:55:39 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id TAA29898 for ietf-calendar-bks; Mon, 27 Mar 2000 19:34:50 -0800 (PST) Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA29892 for ; Mon, 27 Mar 2000 19:34:48 -0800 (PST) Received: from Software.com ([169.208.192.208]) by mta1biz.bizmailsrvcs.net with ESMTP id <20000328033621.GENC851310.mta1biz.bizmailsrvcs.net@Software.com>; Mon, 27 Mar 2000 21:36:21 -0600 Message-ID: <38E027CF.1DD997E1@Software.com> Date: Mon, 27 Mar 2000 19:32:31 -0800 From: Doug Royer Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Bob Mahoney CC: ietf-calendar@imc.org Subject: Re: Casual CalSch dinner tonight 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 Bob Mahoney wrote: > > If any of the calsch folks in Adelaide would like to catch up for a > casual dinner tonight, some of us will be meeting near the Conference > Center registration desk tonight at 6:00. Come and talk calendars > while we eat! > > -Bob This is also an INFORMAL social. The paperwork is being passed out now. Do we just want to attend that? Tue Mar 28 - after 6pm Stamford Grand Hotel - Beach side Pub Moeseley Square, Glenelg, SA I do not care ether way - just trying to keep informed of our options. -Doug From owner-ietf-calendar@mail.imc.org Mon Mar 27 23:40:08 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04039 for ; Mon, 27 Mar 2000 23:40:07 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA03309 for ietf-calendar-bks; Mon, 27 Mar 2000 20:18:23 -0800 (PST) Received: from elysium.uwa.edu.au (root@elysium.uwa.edu.au [130.95.128.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA03299 for ; Mon, 27 Mar 2000 20:18:20 -0800 (PST) Received: from tartarus.uwa.edu.au (mtearle@tartarus.uwa.edu.au [130.95.128.3]) by elysium.uwa.edu.au (8.8.7/8.8.0) with ESMTP id MAA31632; Tue, 28 Mar 2000 12:20:31 +0800 (WST) Date: Tue, 28 Mar 2000 12:20:31 +0800 (WST) From: Mark Tearle To: Doug Royer cc: ietf-calendar@imc.org Subject: Re: Casual CalSch dinner tonight In-Reply-To: <38E027CF.1DD997E1@Software.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Mon, 27 Mar 2000, Doug Royer wrote: > Bob Mahoney wrote: > > > > If any of the calsch folks in Adelaide would like to catch up for a > > casual dinner tonight, some of us will be meeting near the Conference > > Center registration desk tonight at 6:00. Come and talk calendars > > while we eat! > > > > -Bob > > This is also an INFORMAL social. The paperwork is being passed out > now. Do we just want to attend that? > > Tue Mar 28 - after 6pm > > Stamford Grand Hotel - Beach side Pub > Moeseley Square, Glenelg, SA > > I do not care ether way - just trying to keep informed of our > options. > > -Doug > Bugger, wrong damn part of .au - are any of the Calsch crowd visiting Western Australia whilst they are over here? Yours Mark -- Mark Tearle - mtearle@tartarus.uwa.edu.au "We are all in the gutter, but some of us are looking at the stars." -- Oscar Wilde From owner-ietf-calendar@mail.imc.org Tue Mar 28 16:01:24 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26552 for ; Tue, 28 Mar 2000 16:01:24 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id MAA09051 for ietf-calendar-bks; Tue, 28 Mar 2000 12:28:26 -0800 (PST) Received: from arista.iris.com (arista.iris.com [198.112.211.42]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA09047 for ; Tue, 28 Mar 2000 12:28:24 -0800 (PST) From: Bruce_Kahn@iris.com Importance: High X-Priority: 1 (High) To: ietf-calendar@imc.org Subject: RFC 2445 Errors X-Mailer: Lotus Notes Build V60_03232000 March 23, 2000 Message-ID: Date: Tue, 28 Mar 2000 15:30:14 -0500 X-MIMETrack: S/MIME Sign by Notes Client on Bruce Kahn/Iris(Build V60_03232000|March 23, 2000) at 03/28/2000 03:31:05 PM, Serialize by Notes Client on Bruce Kahn/Iris(Build V60_03232000|March 23, 2000) at 03/28/2000 03:31:05 PM, Serialize complete at 03/28/2000 03:31:05 PM, Itemize by Notes Client on Bruce Kahn/Iris(Build V60_03232000|March 23, 2000) at 03/28/2000 03:31:06 PM, S/MIME Sign complete at 03/28/2000 03:31:06 PM, Serialize by Router on Arista/Iris(Build V503_03082000 |March 8, 2000) at 03/28/2000 03:32:29 PM, Serialize complete at 03/28/2000 03:32:29 PM MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z01886_boundary_sign Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is an S/MIME signed message. ---------z01886_boundary_sign Content-Type: text/plain; charset="us-ascii" In the RFC 2445 there are some problems with the examples: Under 5 iCalendar Object Examples there are lots of problems: 1: The 1st example is incorrectly formatted. There are no CRLFs at the end of the property values... (Not sure if we caught this already so Im including for completeness.) 2: The 2nd example has an embedded vTimeZone and vEvent but no METHOD: 3: The 3rd example has a non-2445 standard METHOD value: METHOD:xyz . It should be REQUEST or something standard. 4: The vToDo example has no METHOD: property. 5: Neither does the vJournal example that follows it. 6: The vFreeBusy example also lacks METHOD: Also, the vTimeZone in the 2nd example is a bit odd/misleading: BEGIN:VTIMEZONE TZID:US-Eastern BEGIN:STANDARD DTSTART:19981025T020000 RDATE:19981025T020000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:EST END:STANDARD BEGIN:DAYLIGHT DTSTART:19990404T020000 RDATE:19990404T020000 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 TZNAME:EDT END:DAYLIGHT END:VTIMEZONE The vDaylight has dates in 1994 but the others are 1998 (including the example ones). The RDATEs should be the following year, not the same one. It would be better if there were RRULEs intstead but thats just a nit compared to the rest of it. Bruce =========================================================================== Bruce Kahn INet: Bruce_Kahn@iris.com Iris Associates Phone: 978.392.5335 Westford, MA, USA 01886 FAX: and nothing but the FAX... Standard disclaimers apply, even where prohibited by law... ---------z01886_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggHZMIIBg6ADAgECAiBgUF6eflpWh6h9PfgYD7sAlMCM8enGl8RXOcIo9uhg ezANBgkqhkiG9w0BAQQFADBGMQswCQYDVQQGEwJVUzENMAsGA1UECBMETUFTUzEN MAsGA1UEChMESXJpczEZMBcGA1UEAxMQSXJpcyBJbnRlcm5ldCBDQTAeFw05OTEx MTcxOTEzMjdaFw0wMTExMTYxOTEyNTNaMEgxDTALBgNVBAoTBElyaXMxEzARBgNV BAMTCkJydWNlIEthaG4xIjAgBgkqhkiG9w0BCQEWE0JydWNlX0thaG5AaXJpcy5j b20wWzANBgkqhkiG9w0BAQEFAANKADBHAkEA495S/vcTouExtWuNrF33Q28Lcjjk 4lj2W6ERZ3MhEBR5vHL3wTaXoRWVhPeoDaUcCc54oig8YQlC/hwSp3YF4QICQlGj PDA6MBEGA1UdDgQKBAhG2i3x0db2dzAPBgNVHQ8BAf8EBQMDB7AAMBQGC2CGSAGG +A4CAgMCBAUDAweAADANBgkqhkiG9w0BAQQFAANBAJnY7BPUuh9G4grcCnmNPlMH JsE0/KULlvaqMab5uWQd0nFkZg64TIWwlYMLrwKqzenyrEkVF4QO6yjiShaej/Aw ggF+MIIBKKADAgECAgQ2PhKnMA0GCSqGSIb3DQEBBAUAMEYxCzAJBgNVBAYTAlVT MQ0wCwYDVQQIEwRNQVNTMQ0wCwYDVQQKEwRJcmlzMRkwFwYDVQQDExBJcmlzIElu dGVybmV0IENBMB4XDTk4MTEwMjA4MTQwMFoXDTA4MTAzMDA4MTQwMFowRjELMAkG A1UEBhMCVVMxDTALBgNVBAgTBE1BU1MxDTALBgNVBAoTBElyaXMxGTAXBgNVBAMT EElyaXMgSW50ZXJuZXQgQ0EwXDANBgkqhkiG9w0BAQEFAANLADBIAkEAw+BjK0cg xCxC13brFzl7eB4j2cat+s6ZSd2flxlTuJGg1dtyQHwKYRsDODiEpqUC5oI5yBLD j5LDYXUEwBm4YQIDAQABMA0GCSqGSIb3DQEBBAUAA0EASQ/WFnGO4okdcxMtJrwz cO3Ltq2HlXm3akcNDZ0cltVk60oXJyKq+LVXR/Twj+ZI/Zsr5qfhb5JALi7C+/wi ngAAMYAwggF5AgEBMGowRjELMAkGA1UEBhMCVVMxDTALBgNVBAgTBE1BU1MxDTAL BgNVBAoTBElyaXMxGTAXBgNVBAMTEElyaXMgSW50ZXJuZXQgQ0ECIGBQXp5+WlaH qH09+BgPuwCUwIzx6caXxFc5wij26GB7MAkGBSsOAwIaBQCggaswGAYJKoZIhvcN AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDAwMzI4MjAzMTA1WjAj BgkqhkiG9w0BCQQxFgQU1a+51FzEa5ppK7w/Uybg9eiMi0EwTAYJKoZIhvcNAQkP MT8wPTAHBgUrDgMCHTAOBggqhkiG9w0DAgICAIAwCgYIKoZIhvcNAwcwBwYFKw4D AgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEQNtZUiAzyMYD8Y2qq6Is TDVukr4Fqh5sTuJH39oNkPOTa4KPv7UXJzagC6t3YucFjz4G+xnXB3CZ3I22rBY7 uL8AAAAAAAAAAA== ---------z01886_boundary_sign-- From owner-ietf-calendar@mail.imc.org Tue Mar 28 19:43:33 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00514 for ; Tue, 28 Mar 2000 19:43:30 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id QAA12144 for ietf-calendar-bks; Tue, 28 Mar 2000 16:10:37 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id QAA12140 for ; Tue, 28 Mar 2000 16:10:34 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA08110; Tue, 28 Mar 00 19:14:40 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id TAA12906 for ; Tue, 28 Mar 2000 19:12:57 -0500 (EST) Received: from [169.208.192.18] (dhcp-192-18.ietf.connect.com.au [169.208.192.18]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id TAA12763 for ; Tue, 28 Mar 2000 19:12:54 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: Date: Wed, 29 Mar 2000 09:42:45 +0930 To: ietf-calendar@imc.org From: Bob Mahoney Subject: Adeliade meeting minutes Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: (These minutes are being submitted to the proceedings. Thanks to Richard for acting as scribe! -Bob) Minutes from 47th IETF meeting of the Calendar and Scheduling Workgroup in Adelaide, Australia March 28, 2000 Bob Mahoney, CALSCH co-chair presiding (bobmah@mit.edu) Reported by Richard Shusterman (rans@netscape.com) Approximatly 25+ people in attendance 1. Guide to Implementors (5 minutes) Discussion lead by Bob Mahoney (co-author) Bob: This draft needs to be rev'd soon; it is about to expire. The authors will work on posting an updated draft in the near future. We need input from developers that are reading the calendar documents. Please send in your "war stories". There were no comments or questions from the crowd. 2. CAP draft discussion (15 minutes) Discussion lead by Bob Mahoney, with presentations by Paul Hill (co-author) and Steve Mansour (co-author), with help from Doug Royer (co-author) Bob: The latest draft, draft-ietf-calsch-cap-02.txt, was posted on March 10, 2000. We are making good progress; there has been discussion on the mailing list that is reflected in this draft. There was one interim meeting scheduled this past January in Boston that was sparsely attended, probably due to the snow storm. Bob: What is our timeframe? Soon. Bob: What features are our priorities? There is no one feature that is prioritized above another feature. However, some features have had more discussion on the mailing list than other features. Recently there has been a lot of discussion in 2 areas, security and groups, which will now be presented by Paul and Steve. 2A. Security - presented by Paul Hill Security Model The requirements are very similar to the authentication and access control requirements of LDAP. The current language is very closely aligned with the LDAP authentication draft. User Principal Name (UPN) An identifier that denotes a unique CU. A UPN is an RFC 822 compliant email address, with exceptions listed below, and in most cases it is deliverable to the CU. In some cases it is identical to the CU's well known email address. A CU's UPN MUST never be deliverable to a different person. It consists of a realm in the form of a valid, unique DNS domain name and a unique username. UPN may be the authentication ID used by the authentication method. UPN may also be the optional SASL authentication ID. CAP IDENTIFY command may also be used to assert the UPN. Question: Is a UPN independent of the authentication method? Paul: Yes, it is the same ID regardless of the authentication method used by the CU. The same UPN is used by VCARs. UPN and Certificates When using X.509 certificates for purposes of CAP authentication, the UPN should appear in the certificate. Unfortunately there is no single correct guideline for which field should contain the UPN. Since no single method of including the UPN in the certificate will work in all cases, CAP implementations MUST support the ability to configure what the mapping will be by the CS administrator. Implementations MAY support multiple mapping definitions, for example, the UPN may be found in either the subject alternative name field, or the UPN may be embedded in the subject distinquished name as an EmailAddress attribute. Question: Is there a preferred field? Paul: Yes, a preferred field is specified in the draft. TLS Ciphersuites Section 2.4.2.4 mentions which ciphersuites may be appropriate. This is aligned with the LDAP access control draft. 2B. Groups - presented by Steve Mansour Usage For VCARs (UPNEXPAND) To invite groups of individuals to an event/todo (CALIDEXPAND) Example Why do groups need to be expanded? An example diagram was presented, showing 2 CS, coach.com and publicIsp.com that are connected together using CAP. The CS coach.com has an embedded directory with group and calendar "baseball team", and current members bill, joe, and bob, each with their own calendar. The scenario is for the "coach" to setup a team calendar in coach.com with a VCAR definition that only allows the members of his team to access this calendar. Any changes to the membership of his team will automatically be enforced by this VCAR definition. If the "coach" would like to invite the calendars for each member of his team to a meeting, his CUA can use CALIDEXPAND to retrieve the list of CALIDs. "joe" would like to view the current members of his team. His CUA, connected to publicIsp.com, can attempt to use UPNEXPAND to retrieve the list of UPNs. Since the definition of his team is embedded in coach.com, this request will be fanned out to coach.com by publicIsp.com and if allowed, the list will be returned. "joe" would now like to invite his team to a meeting. His CUA, creates an event with his team as the only attendee. In order to track the responses of each member, publicIsp.com can use CALIDEXPAND to retrieve the list of CALIDs from coach.com before fanning this request out. Paul: The current draft has a mistake showing CALIDs being returned by UPNEXPAND. This should be UPNs. 2C. iCalendar enhancements in CAP Bob: Do these belong in CAP? Should iCalendar be revised or should these be treated as IANA extensions? There were no comments or questions from the crowd. Doug: There are also bugs in iCalendar that need to be fixed. 3. iMIP security (2 minutes) Bob: RFC 1847 vs RFC 2633 (PGP vs S/MIME) S/MIME is excluded because it doesn't support multipart/encrypted, thus not being RFC 1847-compliant. This was not the WG intent. iCalendar was written before S/MIME RFC was ready. This issue should be addressed in iCalendar. Bob: Does anyone know if S/MIME will ever support multipart/encrypted? There were no comments or questions from the crowd. 4. CalConnect (2 minutes) April 11-12, Cambridge, MA (MIT) Question: How many participants? Bob: Potentially 4-5 vendors, and hopefully 1 open source. Cost is $1K and you can send 2 participants. Other comments and questions from the crowd Question: What's left to be done on the draft? Steve: Examples that show multipart responses and groups. Also, restriction tables, i.e., what commands are allowed and where. This is very tedious work but it was found to be a key part of iTIP. These examples and tables should come out in the next few weeks and any input from the mailing list is welcome. Doug: We need more examples. Question: Have all the issues on searching, raised by Lisa Lippert, been addressed? Paul: Since Lisa has not been participating lately on the mailing list, there has been no further discussion (or apparent interest) on these issues. Question: What's the interest level in CAP? Doug: So far, there have been 570 downloads of the CAP draft, many from the same individuals, which also reflects the multiple revisions of the draft since the ftp site was setup. Bob: Editors are available for discussion after this meeting. We are all --working towards finishing up this work, which the AD's appreciate. Meeting was adjourned From owner-ietf-calendar@mail.imc.org Tue Mar 28 20:15:03 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00872 for ; Tue, 28 Mar 2000 20:15:00 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id QAA12878 for ietf-calendar-bks; Tue, 28 Mar 2000 16:50:11 -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 QAA12874 for ; Tue, 28 Mar 2000 16:50:10 -0800 (PST) Received: from royer.com (royer.com [207.177.146.80]) by royer.com (8.9.1/8.9.1) with SMTP id QAA23232 for ; Tue, 28 Mar 2000 16:52:33 -0800 (PST) Message-Id: <200003290052.QAA23232@royer.com> Date: Tue, 28 Mar 2000 16:52:33 -0800 (PST) From: Doug Royer Reply-To: Doug Royer Subject: cap requirements To: ietf-calendar@imc.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: b7QgiKEsxJ15fTcMxan9IQ== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4c sparc Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I have noticed that cap requirements has expired. I think we should resubmit it - perhaps with updates. While looking at the old doc, I noticed some things we did not address. I'll send separate email on that. I just asked Bob if we should resent the requirements doc. I do not know of any reason not to do that. WG input please. -Doug ------------------------------------------------------------------- Doug@Royer@.COM http://Royer.com/People/Doug.html 801 W. El Camino #131 Work: (650)786-7599 Mountain View, CA 94040 Ham Radio: N6AAW, Aviation: PP-ASEL From owner-ietf-calendar@mail.imc.org Wed Mar 29 00:15:07 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04818 for ; Wed, 29 Mar 2000 00:15:06 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA00408 for ietf-calendar-bks; Tue, 28 Mar 2000 20:57:31 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id UAA00403 for ; Tue, 28 Mar 2000 20:57:30 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA14470; Tue, 28 Mar 00 23:59:47 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id XAA00439 for ; Tue, 28 Mar 2000 23:59:54 -0500 (EST) Received: from [169.208.192.18] (dhcp-192-18.ietf.connect.com.au [169.208.192.18]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id XAA05095 for ; Tue, 28 Mar 2000 23:59:51 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: Date: Wed, 29 Mar 2000 14:29:40 +0930 To: ietf-calendar@imc.org From: Bob Mahoney Subject: CAP Extensions Revised draft vs. IANA? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: There was a brief discussion after the meeting yesterday about how to handle iCalendar enhancements, in CAP or as IANA extensions. (We have had some errors in the iCalendar document recently come to light- these will need to be revised in any event.) Harald Alvestrand was still in the room, and had some good thoughts along the lines of "do both". The feeling was that we should use the IANA process, as there is value in exercising that. But it is also useful for future developers to be able to find the relevant information in the mainline documents as much as possible. -Bob From owner-ietf-calendar@mail.imc.org Wed Mar 29 00:15:10 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04829 for ; Wed, 29 Mar 2000 00:15:09 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id UAA00492 for ietf-calendar-bks; Tue, 28 Mar 2000 20:59:42 -0800 (PST) Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id UAA00484 for ; Tue, 28 Mar 2000 20:59:39 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA11083; Wed, 29 Mar 00 00:03:47 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id AAA00756 for ; Wed, 29 Mar 2000 00:02:05 -0500 (EST) Received: from [169.208.192.18] (dhcp-192-18.ietf.connect.com.au [169.208.192.18]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id AAA05441 for ; Wed, 29 Mar 2000 00:02:02 -0500 (EST) Mime-Version: 1.0 X-Sender: bobmah@18.69.0.43 Message-Id: In-Reply-To: References: Date: Wed, 29 Mar 2000 14:31:54 +0930 To: ietf-calendar@imc.org From: Bob Mahoney Subject: Re: Adelaide meeting minutes Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: It was pointed out to me that all instances of "co-author" should be "co-editor". (*blush*) -Bob From owner-ietf-calendar@mail.imc.org Wed Mar 29 08:01:38 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20524 for ; Wed, 29 Mar 2000 08:01:38 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id EAA26779 for ietf-calendar-bks; Wed, 29 Mar 2000 04:43:49 -0800 (PST) Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id EAA26775; Wed, 29 Mar 2000 04:43:48 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id IAA11342; Wed, 29 Mar 2000 08:02:29 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id HAA01698; Wed, 29 Mar 2000 07:45:43 -0500 (EST) To: Bob Mahoney Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: CAP Extensions Revised draft vs. IANA? X-Mailer: Lotus Notes Release 5.0.2c February 2, 2000 Message-ID: Date: Wed, 29 Mar 2000 07:43:01 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/29/2000 07:43:03 AM, Serialize complete at 03/29/2000 07:43:03 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0034E1B9852568B1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0034E1B9852568B1_= Content-Type: text/plain; charset="us-ascii" The errors should be reported so we can correct them in a revised iCalendar draft, if they are new errors. A number of typos were already reported and corrected in a past iCalendar draft update. I agree with Harald that the extensions to iCalendar for CAP should follow the IANA registration process defined in RFC 2445. -- Frank --=_alternative 0034E1B9852568B1_= Content-Type: text/html; charset="us-ascii"
The errors should be reported so we can correct them in a revised iCalendar draft, if they are new errors. A number of typos were already reported and corrected in a past iCalendar draft update.

I agree with Harald that the extensions to iCalendar for CAP should follow the IANA registration process defined in RFC 2445.

-- Frank --=_alternative 0034E1B9852568B1_=-- From owner-ietf-calendar@mail.imc.org Wed Mar 29 08:08:31 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20576 for ; Wed, 29 Mar 2000 08:08:31 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id EAA27020 for ietf-calendar-bks; Wed, 29 Mar 2000 04:54:15 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id EAA27016 for ; Wed, 29 Mar 2000 04:54:14 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA18313; Wed, 29 Mar 00 07:56:33 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id HAA01564; Wed, 29 Mar 2000 07:56:40 -0500 (EST) Received: from miles-davis (dhcp-192-103.ietf.connect.com.au [169.208.192.103]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id HAA05983; Wed, 29 Mar 2000 07:56:34 -0500 (EST) Message-Id: <4.2.0.58.20000329075431.0159a9a0@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 29 Mar 2000 07:56:27 -0500 To: Frank_Dawson@lotus.com From: "Paul B. Hill" Subject: Re: CAP Extensions Revised draft vs. IANA? Cc: ietf-calendar@imc.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: At 07:43 AM 3/29/2000 -0500, Frank_Dawson@lotus.com wrote: >I agree with Harald that the extensions to iCalendar for CAP should follow >the IANA registration process defined in RFC 2445. Does this mean that you do not agree with Harald that the extensions to iCalendar for CAP should also be incorporated into a revised iCalendar as long as we are also revising iCalendar to fix some errors? Paul From owner-ietf-calendar@mail.imc.org Wed Mar 29 10:53:43 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22104 for ; Wed, 29 Mar 2000 10:53:43 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id HAA29892 for ietf-calendar-bks; Wed, 29 Mar 2000 07:24:42 -0800 (PST) Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA29887 for ; Wed, 29 Mar 2000 07:24:41 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id KAA11002; Wed, 29 Mar 2000 10:43:24 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id JAA28442; Wed, 29 Mar 2000 09:58:37 -0500 (EST) To: "Paul B. Hill" Cc: ietf-calendar@imc.org Subject: Re: CAP Extensions Revised draft vs. IANA? X-Mailer: Lotus Notes Release 5.0.2c February 2, 2000 Message-ID: Date: Wed, 29 Mar 2000 09:55:54 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/29/2000 09:55:57 AM, Serialize complete at 03/29/2000 09:55:57 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0052ACAB852568B1_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0052ACAB852568B1_= Content-Type: text/plain; charset="us-ascii" Paul Hill wrote: >Does this mean that you do not agree with Harald that the extensions to >iCalendar for CAP should also be incorporated into a revised iCalendar as >long as we are also revising iCalendar to fix some errors? If they are "approved" iCalendar extensions, then they will have used the iCalendar extension procedure specified in RFC 2445. That means that IANA gets notified of the approved extensions. If that IANA notification mechanism is via the publication of a CAP RFC or via a revision to the iCalendar RFC ... I am just a humble document editor. Let me know what the mailing list consensus mechanism ends up being. -- Frank --=_alternative 0052ACAB852568B1_= Content-Type: text/html; charset="us-ascii"
Paul Hill wrote:

>Does this mean that you do not agree with Harald that the extensions to
>iCalendar for CAP should also be incorporated into a revised iCalendar as
>long as we are also revising iCalendar to fix some errors?

If they are "approved" iCalendar extensions, then they will have used the iCalendar extension procedure specified in RFC 2445. That means that IANA gets notified of the approved extensions. If that IANA notification mechanism is via the publication of a CAP RFC or via a revision to the iCalendar RFC ... I am just a humble document editor.

Let me know what the mailing list consensus mechanism ends up being.

-- Frank

--=_alternative 0052ACAB852568B1_=-- From owner-ietf-calendar@mail.imc.org Wed Mar 29 16:29:23 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24551 for ; Wed, 29 Mar 2000 16:29:22 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id MAA06908 for ietf-calendar-bks; Wed, 29 Mar 2000 12:56:04 -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 MAA06904 for ; Wed, 29 Mar 2000 12:56:03 -0800 (PST) From: andrec@cst.ca 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 PAA08433; Wed, 29 Mar 2000 15:57:58 -0500 Received: by apollo.CST.CA with Internet Mail Service (5.5.2650.21) id ; Wed, 29 Mar 2000 15:57:58 -0500 Message-ID: To: doug@royer.com Cc: ietf-calendar@imc.org Subject: RE: cap requirements Date: Wed, 29 Mar 2000 15:57:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ns.secondary.com id MAA06905 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8bit Doug, I think its important to keep the requirement document active and on hand. It is a very good guiding light. André -----Original Message----- From: Doug Royer [mailto:doug@royer.com] Sent: Tuesday, March 28, 2000 7:53 PM To: ietf-calendar@imc.org Subject: cap requirements I have noticed that cap requirements has expired. I think we should resubmit it - perhaps with updates. While looking at the old doc, I noticed some things we did not address. I'll send separate email on that. I just asked Bob if we should resent the requirements doc. I do not know of any reason not to do that. WG input please. -Doug ------------------------------------------------------------------- Doug@Royer@.COM http://Royer.com/People/Doug.html 801 W. El Camino #131 Work: (650)786-7599 Mountain View, CA 94040 Ham Radio: N6AAW, Aviation: PP-ASEL From owner-ietf-calendar@mail.imc.org Wed Mar 29 20:52:54 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26909 for ; Wed, 29 Mar 2000 20:52:53 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id RAA10874 for ietf-calendar-bks; Wed, 29 Mar 2000 17:22:32 -0800 (PST) Received: from localhost.localdomain (dhcp-32-162.ietf.connect.com.au [169.208.32.162]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA10870 for ; Wed, 29 Mar 2000 17:22:30 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA08096 for ; Thu, 30 Mar 2000 10:54:03 +0930 Message-ID: <38E2ACAF.93D166EC@ecal.com> Date: Thu, 30 Mar 2000 10:53:59 +0930 From: John Stracke X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: CAP Extensions Revised draft vs. IANA? 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 Frank_Dawson@lotus.com wrote: > I agree with Harald that the extensions to iCalendar for CAP > should follow the IANA registration process defined in RFC > 2445. We should fix the registration process first, though. (Reminder: the problem is that the Method Reviewer's decision to accept an extension cannot be appealed. Decisions to reject can be appealed; but, if the MR's decision to accept is final, then a single person has the power to define new extensions unilaterally.) -- /================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |===============================================| |eCal Corp. |Almost no one has ever wanted a 1/4" drill bit;| |francis@ecal.com|all they ever wanted was a 1/4" hole. | \================================================================/ From owner-ietf-calendar@mail.imc.org Wed Mar 29 21:26:33 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27323 for ; Wed, 29 Mar 2000 21:26:32 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id RAA11303 for ietf-calendar-bks; Wed, 29 Mar 2000 17:57:43 -0800 (PST) Received: from localhost.localdomain (dhcp-32-162.ietf.connect.com.au [169.208.32.162]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA11296 for ; Wed, 29 Mar 2000 17:57:41 -0800 (PST) Received: from ecal.com (localhost [127.0.0.1]) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id LAA08415; Thu, 30 Mar 2000 11:29:16 +0930 Message-ID: <38E2B4F4.A35EE955@ecal.com> Date: Thu, 30 Mar 2000 11:29:16 +0930 From: John Stracke X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586) X-Accept-Language: en MIME-Version: 1.0 To: calsch WG Subject: draft-stracke-calsch-ical-reviewer-00 Content-Type: multipart/mixed; boundary="------------2EB41CAEF49C43E3BE412D21" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------2EB41CAEF49C43E3BE412D21 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Attached is an I-D I just wrote, proposing a fix to the Method Reviewer process. (Yes, this is basically what I promised to do back in Oslo.) I've submitted this I-D already, but of course it won't be published for a while. -- /================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |===============================================| |eCal Corp. |Almost no one has ever wanted a 1/4" drill bit;| |francis@ecal.com|all they ever wanted was a 1/4" hole. | \================================================================/ --------------2EB41CAEF49C43E3BE412D21 Content-Type: text/plain; charset=us-ascii; name="draft-stracke-calsch-ical-reviewer-00.txt" Content-Disposition: inline; filename="draft-stracke-calsch-ical-reviewer-00.txt" Content-Transfer-Encoding: 7bit Network Working Group J. Stracke, eCal Corp. INTERNET DRAFT Expires September, 2000 March 30, 2000 Fixing the iCalendar Registration Process 1 Status of this Document This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as ``work in progress.'' The list of current Internet-Drafts can be accessed at The list of Internet-Draft Shadow Directories can be accessed at Distribution of this document is unlimited. Please send comments to francis@ecal.com or to the impp@iastate.edu discussion list. 2 Abstract This document discusses a problem with the [ICALENDAR] registration process, which gives the Method Reviewer too much power, and proposes a fix. 3 Introduction This document discusses a problem with the [ICALENDAR] registration process, which gives the Method Reviewer too much power, and proposes a fix. Section 7.2 of [ICALENDAR] defines a process for defining new iCalendar properties. This process seems to be modeled on the [MIME] registration procedures, but with some subtle changes: a decision from the Method Reviewer to accept a proposal cannot be appealed. Decisions to reject can be appealed, but only by the original proposer. In the first place, the IETF simply does not grant any single person the power to extend a standard unilaterally. Consider what happens if an unscrupulous MR gets appointed: they can propose, and accept, a slew of extensions to further their employer's agenda. In the second place, the unilateral power to accept can be used to make the review of rejections meaningless. If the MR sees a proposal Stracke [Page 1] INTERNET-DRAFT iCalendar Registration Fix March 30, 2000 which they want to reject, they can propose, and accept, a different proposal which conflicts with the rejected proposal (e.g., by using the same type names). The appeal of the rejection would then be more or less foredoomed. In the third place, it may be a bad idea to state that only the original proposer can appeal the MR's decisions. For example, suppose the MR rejects a proposal, and the original proposer cannot afford the time for a formal appeal; it may well be desirable to permit a third party to make the appeal (as is possible in [MIME]). Finally, it is not made explicit that the MR can be removed; the Applications Area Director(s) appoint the MR, but an argument could be made that they do not have the power to remove the MR. Granted, it would be a pretty weak argument; but better to avoid the problem in the first place. 4 Proposed fix The proposed fix is to modify the registration process so that all decisions of the Method Reviewer can be appealed to the IESG, by any party, and so that the Area Director(s) can remove the Method Reviewer at any time. 5 References [MIME-FORMAT] N. Freed, J. Klensin, J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures." RFC-2048. Innosoft, MCI, ISI. November, 1996. [ICALENDAR] F. Dawson, D. Stenerson, "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC-2445. Lotus, Microsoft. November, 1998. 6 Author's Address J. Stracke eCal Corp. 234 N. Columbus Blvd., 2nd Floor Philadelphia, PA 94043 francis@ecal.com Stracke [Page 2] --------------2EB41CAEF49C43E3BE412D21-- From owner-ietf-calendar@mail.imc.org Wed Mar 29 23:57:09 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01039 for ; Wed, 29 Mar 2000 23:57:08 -0500 (EST) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id UAA22629 for ietf-calendar-bks; Wed, 29 Mar 2000 20:23:32 -0800 (PST) Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA22624 for ; Wed, 29 Mar 2000 20:23:30 -0800 (PST) Received: from Software.com ([169.208.34.62]) by mta1biz.bizmailsrvcs.net with ESMTP id <20000330042514.IFJX851310.mta1biz.bizmailsrvcs.net@Software.com>; Wed, 29 Mar 2000 22:25:14 -0600 Message-ID: <38E2D640.AAB6634E@Software.com> Date: Wed, 29 Mar 2000 20:21:20 -0800 From: Doug Royer Organization: Software.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: John Stracke CC: ietf-calendar@imc.org Subject: Re: CAP Extensions Revised draft vs. IANA? References: <38E2ACAF.93D166EC@ecal.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msD446116A51EF58640AA3EDD2" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a cryptographically signed message in MIME format. --------------msD446116A51EF58640AA3EDD2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Yes. I think the WG already agreed to this. -Doug John Stracke wrote: > > Frank_Dawson@lotus.com wrote: > > > I agree with Harald that the extensions to iCalendar for CAP > > should follow the IANA registration process defined in RFC > > 2445. > > We should fix the registration process first, though. (Reminder: > the problem is that the Method Reviewer's decision to accept an > extension cannot be appealed. Decisions to reject can be > appealed; but, if the MR's decision to accept is final, then a > single person has the power to define new extensions > unilaterally.) --------------msD446116A51EF58640AA3EDD2 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIKKgYJKoZIhvcNAQcCoIIKGzCCChcCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC CCIwggTsMIIEVaADAgECAhA2tOutfntkPZeWwhSMC60VMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDExNzAwMDAw MFoXDTAwMTAxMzIzNTk1OVowggEZMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0RvdWdsYXMgTSBSb3llcjEmMCQGCSqG SIb3DQEJARYXZG91Zy5yb3llckBzb2Z0d2FyZS5jb20wXDANBgkqhkiG9w0BAQEFAANLADBI AkEA8b+/7AusCQc89McoXWlPBDcEaOyt/e2NdL+lPypsoauWxoLohWrk708y93xfziOVZ/Jh 3yF9Dq43K9rW9m8SewIDAQABo4IBwTCCAb0wCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5Mjk4 NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjIxNDFi ZWFkYjJiZDJlODkyMWZhODZiZjFkMTExNDk5ZmEzYmE0N2ZkZjNlYTQ1MDYwMAYKYIZIAYb4 RQEGBwQiFiA2NWVlMGM5M2RkNDY2OGJjNGViOGM2OWNiMDliZWYxNzAzBgNVHR8ELDAqMCig JqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEBBAUA A4GBAIfiBv6wsXfERKczHkNCZ3zPRgSs/eOEutA2lnTtejz+sHTm3XWcEEx0zcEkYafFIOCK GFgFsy6cR4czApnWlILPzDAyT+FcDsAqTtSGDL8jTVMo/7MW6CHReAc0oSzGtapMxWcLgaMh /D0lM5vSddVM7EgNhGLWQPoAvxKe4PExMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqglXa/u DXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ bmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0 aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZl cmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQL Ez13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFC LkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vi c2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ AoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI 4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqO f2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIBBjBH BgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5j b20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZI hvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoPuUmF pJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11YGkk8 kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggHQMIIBzAIBATCB4TCBzDEXMBUG A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQNrTrrX57ZD2XlsIUjAut FTAJBgUrDgMCGgUAoIGGMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF MQ8XDTAwMDMzMDA0MjEyMVowIwYJKoZIhvcNAQkEMRYEFBvxcEgcwskub3/YJFDPFr1z1H9f MCcGCSqGSIb3DQEJDzEaMBgwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEB BQAEQDUuIXlcUan1DjYzQ0d98aKnb3S1WF5RoTgabGzpmq+bhId13JRmYv4r4FcK3sCoUtl7 JPWExqVgS/PJ96+zN0E= --------------msD446116A51EF58640AA3EDD2-- From owner-ietf-calendar@mail.imc.org Thu Mar 30 01:53:17 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05032 for ; Thu, 30 Mar 2000 01:53:16 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id WAA27265 for ietf-calendar-bks; Wed, 29 Mar 2000 22:27:40 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id WAA27261 for ; Wed, 29 Mar 2000 22:27:38 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA08442; Thu, 30 Mar 00 01:30:00 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id BAA24631 for ; Thu, 30 Mar 2000 01:27:48 -0500 (EST) Received: from miles-davis (dhcp-192-103.ietf.connect.com.au [169.208.192.103]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id BAA02187 for ; Thu, 30 Mar 2000 01:27:45 -0500 (EST) Message-Id: <4.2.0.58.20000330155232.01c3a150@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 30 Mar 2000 15:57:39 +0930 To: ietf-calendar@imc.org From: "Paul B. Hill" Subject: Some notes on SASL Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, After the working group meeting RL Bob Morgan mentioned some open security issues to me. Some are relevant to CAP if we want CAP to be useful to ISP or portal companies that wish to host virtual hosts for C&S system. I'll try to get some text about this ready for the next revision. In the meantime Bob talked about some of these issues at the Adelaide BLOCKS BOF. His slides are available at Paul From owner-ietf-calendar@mail.imc.org Thu Mar 30 10:54:31 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17237 for ; Thu, 30 Mar 2000 10:54:31 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id HAA20595 for ietf-calendar-bks; Thu, 30 Mar 2000 07:24:45 -0800 (PST) Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA20591; Thu, 30 Mar 2000 07:24:43 -0800 (PST) From: Frank_Dawson@lotus.com Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id KAA24410; Thu, 30 Mar 2000 10:43:31 -0500 (EST) Received: from cammail06.lotus.com (Cammail06.lotus.com [9.95.5.18]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id KAA22339; Thu, 30 Mar 2000 10:26:43 -0500 (EST) To: "Paul B. Hill" Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: Some notes on SASL X-Mailer: Lotus Notes Release 5.0.2c February 2, 2000 Message-ID: Date: Thu, 30 Mar 2000 10:23:56 -0500 X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/30/2000 10:23:58 AM, Serialize complete at 03/30/2000 10:23:58 AM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 00445162852568B2_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 00445162852568B2_= Content-Type: text/plain; charset="us-ascii" Paul: Why would you just add undiscussed text into the CAP draft? Shouldn't we discuss this suggested addition, first, on the mailing list? Why don't you append your suggested text here first. -- Frank --=_alternative 00445162852568B2_= Content-Type: text/html; charset="us-ascii"
Paul:

Why would you just add undiscussed text into the CAP draft? Shouldn't we discuss this suggested addition, first, on the mailing list? Why don't you append your suggested text here first.

-- Frank --=_alternative 00445162852568B2_=-- From owner-ietf-calendar@mail.imc.org Thu Mar 30 16:54:30 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22053 for ; Thu, 30 Mar 2000 16:54:29 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id NAA27647 for ietf-calendar-bks; Thu, 30 Mar 2000 13:34:23 -0800 (PST) Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id NAA27642 for ; Thu, 30 Mar 2000 13:34:21 -0800 (PST) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA16461; Thu, 30 Mar 00 16:36:45 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id QAA25130; Thu, 30 Mar 2000 16:36:52 -0500 (EST) Received: from miles-davis (dhcp-192-103.ietf.connect.com.au [169.208.192.103]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id QAA22445; Thu, 30 Mar 2000 16:36:44 -0500 (EST) Message-Id: <4.2.0.58.20000331070400.01d3a268@po12.mit.edu> X-Sender: pbh@po12.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 31 Mar 2000 07:06:35 +0930 To: From: "Paul B. Hill" Subject: Re: Some notes on SASL Cc: ietf-calendar@imc.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: HI Frank, Actually I would send the text to the list and get it into the unofficial copy of the draft that people can get via ftp so that they could see the wider context if they so desired. If there was dissension on the topic it would be removed. Be very careful about throwing rocks. Paul At 10:23 AM 3/30/2000 -0500, Frank_Dawson@lotus.com wrote: >Paul: > >Why would you just add undiscussed text into the CAP draft? Shouldn't we >discuss this suggested addition, first, on the mailing list? Why don't you >append your suggested text here first. > >-- Frank From owner-ietf-calendar@mail.imc.org Fri Mar 31 13:02:30 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16894 for ; Fri, 31 Mar 2000 13:02:30 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA19855 for ietf-calendar-bks; Fri, 31 Mar 2000 09:33:30 -0800 (PST) Received: from egenconsulting.com (www.egenconsulting.com [207.244.42.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA19851 for ; Fri, 31 Mar 2000 09:33:22 -0800 (PST) From: pregen@egenconsulting.com To: ietf-calendar@imc.org Subject: Interoperability Testing X-Mailer: Lotus Notes Release 5.0.1a August 17, 1999 Message-ID: Date: Fri, 31 Mar 2000 12:35:39 -0500 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.2a |November 23, 1999) at 03/31/2000 12:36:06 PM, Serialize complete at 03/31/2000 12:36:06 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 00607F82852568B3_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 00607F82852568B3_= Content-Type: text/plain; charset="us-ascii" For everyone attending the interoperability testing, we have just confirmed that American Express, Visa and Master Charge credit cards will be accepted, as well as checks. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 00607F82852568B3_= Content-Type: text/html; charset="us-ascii"
For everyone attending the interoperability testing, we have just confirmed that American Express, Visa and Master Charge credit cards will be accepted, as well as checks.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 00607F82852568B3_=--