From owner-ietf-calendar@mail.imc.org Mon Jul 1 16:43:12 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02108 for ; Mon, 1 Jul 2002 16:43:12 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g61KWJW14048 for ietf-calendar-bks; Mon, 1 Jul 2002 13:32:19 -0700 (PDT) Received: from server1.egenconsulting.com ([208.31.106.94]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g61KWHw14043 for ; Mon, 1 Jul 2002 13:32:17 -0700 (PDT) To: George Babics Cc: ietf-calendar@imc.org Subject: Re: CAP draft MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: pregen@egenconsulting.com Date: Mon, 1 Jul 2002 16:32:28 -0400 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.9a |January 7, 2002) at 07/01/2002 04:32:21 PM, Serialize complete at 07/01/2002 04:32:21 PM Content-Type: multipart/alternative; boundary="=_alternative 0070D63185256BE9_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0070D63185256BE9_= Content-Type: text/plain; charset="us-ascii" Hey George, submitting the draft to the IETF does not make it cast in stone. It allows other people to review it and make comments as well. I know some of the Steltor folks said there were items in the draft that were not discussed. Doug posted his comments on what he thought might have been new. I have seen no other comments from any other sources saying there are items in the draft that were not discussed on the list. Can you help us by pointing out what changes were not on the list. We can't find "many" changes. We can see a couple - but not "many." If you feel there are a lot, please point them out so we can fix them if need be. And other people on the list, if you see items, please make comments on the list. thanks. George Babics 06/28/2002 18:22 To: pregen@egenconsulting.com cc: ietf-calendar@imc.org Subject: Re: CAP draft Isn't it a bit too early to submit the draft? I think there were many changes done recently in Doug's working document that were not discussed nor agreed to on the list, should we take the time to review, comment and adjust them? If I am not mistaken, before posting a new draft the chairs should ask or declare consensus for each one the proposed changes. Was that done for these changes? George pregen@egenconsulting.com wrote: > > Has everyone responded to the list regarding CAP changes? We would like to submit the draft so it can be reviewed by everyone in the IETF. Now is your chance - if you object, say so. If you do not > have objections or we do not hear on the list, we're submitting the draft. Thanks. > ___________________ > Patricia Egen Consulting > www.egenconsulting.com > 423-875-2652 --=_alternative 0070D63185256BE9_= Content-Type: text/html; charset="us-ascii"
Hey George, submitting the draft to the IETF does not make it cast in stone.  It allows other people to review it and make comments as well.  I know some of the Steltor folks said there were items in the draft that were not discussed.  Doug posted his comments on what he thought might have been new.  I have seen no other comments from any other sources saying there are items in the draft that were not discussed on the list.  Can you help us by pointing out what changes were not on the list.  We can't find "many" changes.  We can see a couple - but not "many."  If you feel there are a lot, please point them out so we can fix them if need be.  And other people on the list, if you see items, please make comments on the list.  thanks.


George Babics <georgeb@steltor.com>

06/28/2002 18:22

       
        To:        pregen@egenconsulting.com
        cc:        ietf-calendar@imc.org
        Subject:        Re: CAP draft



 
 Isn't it a bit too early to submit the draft?

 I think there were many changes done recently in Doug's working
document that were not discussed nor agreed to on the list, should
we take the time to review, comment and adjust them? If I am not
mistaken, before posting a new draft the chairs should ask or
declare consensus for each one the proposed changes. Was that done
for these changes?

George

pregen@egenconsulting.com wrote:
>
> Has everyone responded to the list regarding CAP changes? We would like to submit the draft so it can be reviewed by everyone in the IETF.  Now is your chance - if you object, say so.  If you do not
> have objections or we do not hear on the list, we're submitting the draft.  Thanks.
> ___________________
> Patricia Egen Consulting
> www.egenconsulting.com
> 423-875-2652

--=_alternative 0070D63185256BE9_=-- From owner-ietf-calendar@mail.imc.org Fri Jul 5 06:42:21 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18082 for ; Fri, 5 Jul 2002 06:42:20 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g65AXhE29842 for ietf-calendar-bks; Fri, 5 Jul 2002 03:33:43 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g65AXhw29838 for ; Fri, 5 Jul 2002 03:33:43 -0700 (PDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16856; Fri, 5 Jul 2002 06:32:53 -0400 (EDT) Message-Id: <200207051032.GAA16856@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-08.txt Date: Fri, 05 Jul 2002 06:32:53 -0400 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) : D. Royer, G. Babics, P. Hill, S. Mansour Filename : draft-ietf-calsch-cap-08.txt Pages : 133 Date : 03-Jul-02 The Calendar Access Protocol (CAP) is an Internet protocol described in this memo that permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an [iCAL] based Calendar Store (CS). The CAP definition is based on requirements identified by the Internet Engineering Task Force (IETF) Calendaring and Scheduling (CALSCH) Working Group. More information about the IETF CALSCH Working Group activities can be found on the IMC web site at http:// www.imc.org/ietf-calendar and at the IETF web site at http:// www.ietf.org/html.charters/calsch-charter.html [1]. Refer to the references within this memo for further information on how to access these various documents. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-calsch-cap-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-08.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-08.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: <20020703135251.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-calsch-cap-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-calsch-cap-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020703135251.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-calendar@mail.imc.org Fri Jul 5 12:39:40 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03392 for ; Fri, 5 Jul 2002 12:39:40 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g65GVIW29964 for ietf-calendar-bks; Fri, 5 Jul 2002 09:31:18 -0700 (PDT) Received: from mail.samsungcontact.com ([195.89.159.51]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g65GVGw29959 for ; Fri, 5 Jul 2002 09:31:16 -0700 (PDT) Received: from mail.samsungcontact.com (root@localhost) by mail.samsungcontact.com (8.11.6/8.11.6) with ESMTP id g65GVCP03394 for ; Fri, 5 Jul 2002 17:31:12 +0100 Received: from samsungcontact.com (host195-89-159-62.uk.regusnet.com 195.89.159.62) by mail.samsungcontact.com (Samsung Contact SMTP Relay 7.1.0) via ESMTP; Fri, 05 Jul 2002 17:31:12 +0100 (BST) Message-ID: <3D25C9CD.9000702@samsungcontact.com> Date: Fri, 05 Jul 2002 17:31:09 +0100 From: Mark Davidson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Security considerations in cap-08 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit In the security considerations (section 13) of the new draft it says: 'Although service provisioning is a policy matter, at a minimum, all implementations must provide the following tuning profiles:' I think the must in this line should be either a MUST or a SHOULD. I would prefer if it was a SHOULD as some countries might have problems (legally) with specific security technologies. So could the line be changed to: 'Although service provisioning is a policy matter, at a minimum, all implementations SHOULD provide the following tuning profiles:' Mark Davidson From owner-ietf-calendar@mail.imc.org Fri Jul 5 13:16:46 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04940 for ; Fri, 5 Jul 2002 13:16:46 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g65HAV603624 for ietf-calendar-bks; Fri, 5 Jul 2002 10:10:31 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g65HAUw03620 for ; Fri, 5 Jul 2002 10:10:30 -0700 (PDT) Received: from Royer.com (blackhole.dtdocs.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g65HATRb015652 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Fri, 5 Jul 2002 10:10:31 -0700 Message-ID: <3D25D08C.6487BD55@Royer.com> Date: Fri, 05 Jul 2002 10:59:56 -0600 From: Doug Royer Reply-To: "ietf-calendar@imc.org" Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: Security considerations in cap-08 References: <3D25C9CD.9000702@samsungcontact.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms628F257538DABD82B565FC81" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a cryptographically signed message in MIME format. --------------ms628F257538DABD82B565FC81 Content-Type: multipart/mixed; boundary="------------0DA3C7ED38BCE54C3B088B04" This is a multi-part message in MIME format. --------------0DA3C7ED38BCE54C3B088B04 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Davidson wrote: > > In the security considerations (section 13) of the new draft it says: > > 'Although service provisioning is a policy matter, at a minimum, all > implementations must provide the following tuning profiles:' > > I think the must in this line should be either a MUST or a SHOULD. > > I would prefer if it was a SHOULD as some countries might have problems > (legally) with specific security technologies. > > So could the line be changed to: > 'Although service provisioning is a policy matter, at a minimum, all > implementations SHOULD provide the following tuning profiles:' > > Mark Davidson We must have a minimum set of authentication requirements or we will not have interoperability. So the is section can only be a MUST. The correct thing to do is to make sure it is the correct set of 'MUST'. In the past, Paul Hill took on this responsibility and he consulted the security experts (for which I call him an expert), and they concluded that DIGEST-MD5 was the correct 'MUST' to use for authentication. And I seem to recall that they concluded that triple DES with SHA was also the correct minimum for TLS and certificates. Paul? - is this correct? -Doug --------------0DA3C7ED38BCE54C3B088B04 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------0DA3C7ED38BCE54C3B088B04-- --------------ms628F257538DABD82B565FC81 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIKQwYJKoZIhvcNAQcCoIIKNDCCCjACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B88wggSZMIIEAqADAgECAhA85nVyQ1LlncKock/RLC9dMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDEyMjAwMDAw MFoXDTAyMTAxMjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0B CQEWDmRvdWdAcm95ZXIuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7uTPDnj/U t/EKae6vnKPIWpCI2HoHAl3n5uSf/gIwD4Z+j3gewsR0Dm70bjAcWxwps6FNphsMUBolBwKo L73DGK8NNSz+G8fvzMrDa6SA+Pv/hv0IhkqqmCkEdgawKzzs3i3t3qQy8zOVhXNQSkhUvzlu TDNi0FS2bsCepU7hwwIDAQABo4IBODCCATQwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDAGCmCGSAGG+EUBBgcEIhYgMTgwNjlhZjY3YjMyNzNhNTAyMzQw MWRjMjU3MWY3NjQwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20v Y2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQAirjMwaw74Gbr3M61qm+BnzaNOeTMvriFN twfq1XDwgW4VBGhP1jHFL1bg6TJwEonPLJepixj0Y6/SahwkG1QUo86aCyJSyrB7qWl5q4PI XvjcGvN3jgVLlM5CYcXIyEXL9sGm8hxdxPB15yKd519QNkzNp+sd5QU8Ww5DM0AYczCCAy4w ggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYT AlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1 MTIyMzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5 L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24g Q2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVk MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xU v7zodyqdufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbaw NkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQAB o3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsG CCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYB Af8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEe kmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPH vhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWi kK5uMYICPDCCAjgCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW YWxpZGF0ZWQCEDzmdXJDUuWdwqhyT9EsL10wCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMjA3MDUxNjU5NTlaMCMGCSqGSIb3DQEJ BDEWBBRsEyeUDkPGHq+uGEV4W7+qkje3BzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIB KDANBgkqhkiG9w0BAQEFAASBgDXsFCOFHepvMKQLUuyWonB3ny0H/jgYr6ulLMuEF2bPRtaT DWYHzT2p0o0uC0RdHibhoIF0SesFnmcvtSgNM+/a64lvy3m4KYV4yIrI4507z230NsOr9JTr aUd3nL9ofz1fDnc08wdf7Ad8rpqe90+uajVdO66VRockQqa+8GSk --------------ms628F257538DABD82B565FC81-- From owner-ietf-calendar@mail.imc.org Sun Jul 7 17:25:03 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06341 for ; Sun, 7 Jul 2002 17:25:02 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g67LFKh21641 for ietf-calendar-bks; Sun, 7 Jul 2002 14:15:20 -0700 (PDT) Received: from codd.miraclefish.com (host217-34-103-41.in-addr.btopenworld.com [217.34.103.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g67LFIw21628 for ; Sun, 7 Jul 2002 14:15:18 -0700 (PDT) Received: (qmail 24684 invoked from network); 7 Jul 2002 21:29:40 -0000 Received: from user-0c8gh2q.cable.mindspring.com (HELO russellsharpe.com) (24.136.68.90) by 0 with SMTP; 7 Jul 2002 21:29:40 -0000 Message-ID: <3D28AF4C.79D27CC4@russellsharpe.com> Date: Sun, 07 Jul 2002 14:14:52 -0700 From: Paul Sharpe Organization: Russell Sharpe Limited X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en, ja, pdf MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Schudling an event 'asap' 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 How can I use iCalendar to schedule an event 'as soon as possible' i.e. as soon as there's an available slot in a calendar? Looking at RFC 2445, the only approach I can see is to use a non-standard property e.g. X-DTSTART: ASAP. Cheers, paul -- Paul Sharpe - Technical Director Tel: +44 (0)1483 894158 Russell Sharpe Ltd. Fax: +44 (0)1483 898932 The Tannery, Tannery Lane mailto:paul@russellsharpe.com Bramley, Surrey GU5 0AJ, UK From owner-ietf-calendar@mail.imc.org Sun Jul 7 18:47:42 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09408 for ; Sun, 7 Jul 2002 18:47:41 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g67MeJ828543 for ietf-calendar-bks; Sun, 7 Jul 2002 15:40:19 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g67MeIw28534 for ; Sun, 7 Jul 2002 15:40:18 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g67Me9Rb022470 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 7 Jul 2002 15:40:21 -0700 Message-ID: <3D28C0B8.A4031A11@Royer.com> Date: Sun, 07 Jul 2002 16:29:12 -0600 From: Doug Royer Reply-To: "ietf-calendar@imc.org" Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org CC: Paul Sharpe Subject: Re: Schudling an event 'asap' References: <3D28AF4C.79D27CC4@russellsharpe.com> Content-Type: multipart/mixed; boundary="------------70DB79475B2BF15FEFC11301" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------70DB79475B2BF15FEFC11301 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Paul Sharpe wrote: > > How can I use iCalendar to schedule an event 'as soon as possible' i.e. > as soon as there's an available slot in a calendar? Looking at RFC > 2445, the only approach I can see is to use a non-standard property e.g. > X-DTSTART: ASAP. You have to get the calendars BUSY (VFREEBUSY) time and then do an iTIP (RFC 2446) METHOD:REQUEST for the time slot. There is no 'notification' in 2445, 2446, 2447, or CAP. There would be some issues that would have to be worked out to make such a request. Interesting add-on idea. -Doug --------------70DB79475B2BF15FEFC11301 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------70DB79475B2BF15FEFC11301-- From owner-ietf-calendar@mail.imc.org Mon Jul 8 13:25:46 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26467 for ; Mon, 8 Jul 2002 13:25:46 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g68HJB516432 for ietf-calendar-bks; Mon, 8 Jul 2002 10:19:11 -0700 (PDT) Received: from netscape.com (c3po.netscape.com [205.217.237.46]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g68HJ9w16428 for ; Mon, 8 Jul 2002 10:19:09 -0700 (PDT) Received: from dredd.mcom.com (dredd.nscp.aoltw.net [10.169.8.48]) by netscape.com (8.10.0/8.10.0) with ESMTP id g68HJ4m03809 for ; Mon, 8 Jul 2002 10:19:04 -0700 (PDT) Received: from netscape.com ([10.169.59.254]) by dredd.mcom.com (Netscape Messaging Server 4.15) with ESMTP id GYXXFT00.L1A; Mon, 8 Jul 2002 10:19:05 -0700 Message-ID: <3D29C88F.52027E87@netscape.com> Date: Mon, 08 Jul 2002 10:14:55 -0700 From: sman@netscape.com (Steve Mansour) X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Paul Sharpe CC: ietf-calendar@imc.org Subject: Re: Schudling an event 'asap' References: <3D28AF4C.79D27CC4@russellsharpe.com> Content-Type: multipart/mixed; boundary="------------2B0C2AAAE68F2808DC37F06E" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------2B0C2AAAE68F2808DC37F06E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Paul, RFC 2445 does not address your problem. It is simply a schema. Your problem is specific to scheduling. I believe it would fall more in the CAP domain (and possibly iTIP) than the iCalendar domain. I think what you're trying to do will turn out to be a client feature rather than something we build into a protocol RFC. We do need to make sure you have the raw functionality to build this feature, and I believe that functionality is present. -Steve Paul Sharpe wrote: > How can I use iCalendar to schedule an event 'as soon as possible' i.e. > as soon as there's an available slot in a calendar? Looking at RFC > 2445, the only approach I can see is to use a non-standard property e.g. > X-DTSTART: ASAP. > > Cheers, > > paul > > -- > Paul Sharpe - Technical Director Tel: +44 (0)1483 894158 > Russell Sharpe Ltd. Fax: +44 (0)1483 898932 > The Tannery, Tannery Lane mailto:paul@russellsharpe.com > Bramley, Surrey GU5 0AJ, UK --------------2B0C2AAAE68F2808DC37F06E 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;work:650.937.3351 x-mozilla-html:FALSE org:AOL / Netscape adr:;;;;;; version:2.1 title:Director of Engineering fn:Steve Mansour end:vcard --------------2B0C2AAAE68F2808DC37F06E-- From owner-ietf-calendar@mail.imc.org Mon Jul 8 18:23:47 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14428 for ; Mon, 8 Jul 2002 18:23:46 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g68MFhi10643 for ietf-calendar-bks; Mon, 8 Jul 2002 15:15:43 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g68MFgw10639 for ; Mon, 8 Jul 2002 15:15:42 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g68MFfRb031053 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 8 Jul 2002 15:15:44 -0700 Message-ID: <3D2A0C71.648A42D1@Royer.com> Date: Mon, 08 Jul 2002 16:04:33 -0600 From: Doug Royer Reply-To: "ietf-calendar@imc.org" Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: [Fwd: RFC 3283 on Guide to Internet Calendaring] Content-Type: multipart/mixed; boundary="------------C6ADC21BDDABF6CB7E79E697" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------C6ADC21BDDABF6CB7E79E697 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit WAY TO GO! -------- Original Message -------- Subject: RFC 3283 on Guide to Internet Calendaring Date: Mon, 08 Jul 2002 14:20:01 -0700 From: rfc-editor@rfc-editor.org To: IETF-Announce: ; CC: rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 3283 Title: Guide to Internet Calendaring Author(s): B. Mahoney, G. Babics, A. Taler Status: Informational Date: June 2002 Mailbox: bobmah@mit.edu, georgeb@steltor.com, alex@0--0.org Pages: 16 Characters: 31768 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-calsch-inetcal-guide-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3283.txt This document describes the various Internet calendaring and scheduling standards and works in progress, and the relationships between them. Its intent is to provide a context for these documents, assist in their understanding, and potentially aid in the design of standards-based calendaring and scheduling systems. The standards addressed are RFC 2445 (iCalendar), RFC 2446 (iTIP), and RFC 2447 (iMIP). The work in progress addressed is "Calendar Access Protocol" (CAP). This document also describes issues and problems that are not solved by these protocols, and that could be targets for future work. This document is a product of the Calendaring and Scheduling Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --------------C6ADC21BDDABF6CB7E79E697 Content-Type: Message/External-body; name="rfc3283.txt" Content-Disposition: inline; filename="rfc3283.txt" Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <020708141924.RFC@RFC-EDITOR.ORG> --------------C6ADC21BDDABF6CB7E79E697 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------C6ADC21BDDABF6CB7E79E697-- From owner-ietf-calendar@mail.imc.org Tue Jul 9 13:55:58 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05160 for ; Tue, 9 Jul 2002 13:55:57 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g69HljT26448 for ietf-calendar-bks; Tue, 9 Jul 2002 10:47:45 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g69Hlhw26442 for ; Tue, 9 Jul 2002 10:47:44 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 56B0615533; Tue, 9 Jul 2002 19:47:44 +0200 (CEST) Date: Tue, 9 Jul 2002 19:47:44 +0200 From: Andrea Campi To: ietf-calendar@imc.org Subject: Examples in latest draft Message-ID: <20020709174743.GH98336@inet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I've been following this wg list for just a couple of months so bear with me if this has already been discussed. While reading the draft I noticed the following (after definition of CREATE): S: Content-Type: text/calendar S: S: BEGIN:VCALENDAR S: VERSION:2.0 S: CMD;ID=creation01:REPLY S: TARGET:cal.example.com S: BEGIN:REPLY <- Reply for 1st calendar create S: CALID:relcalz1 S: REQUEST-STATUS:2.0 S: END:REPLY S: BEGIN:VREPLY <- Reply for 2nd calendar create S: CALID:relcalz2 S: REQUEST-STATUS:2.0 S: END:VREPLY S: END:VCALENDAR The VCALENDAR is missing the PRODID property. Moreover, VREPLY is mispelled as REPLY. In addition, part of the exhanges are labeled with C: and S:, and part with I: and L:. Bye, andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Tue Jul 9 14:36:10 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06697 for ; Tue, 9 Jul 2002 14:36:09 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g69IQYF29944 for ietf-calendar-bks; Tue, 9 Jul 2002 11:26:34 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g69IQXw29940 for ; Tue, 9 Jul 2002 11:26:33 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g69IQWRb005783 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 9 Jul 2002 11:26:35 -0700 Message-ID: <3D2B2833.8E0FCB62@Royer.com> Date: Tue, 09 Jul 2002 12:15:15 -0600 From: Doug Royer Reply-To: ietf-calendar@imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: Examples in latest draft References: <20020709174743.GH98336@inet.it> 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 Andrea Campi wrote: > > Hi all, > > I've been following this wg list for just a couple of months so > bear with me if this has already been discussed. While reading the > draft I noticed the following (after definition of CREATE): > ... > > The VCALENDAR is missing the PRODID property. Moreover, VREPLY is > mispelled as REPLY. Thanks, I just edited in those fixes. > In addition, part of the exhanges are labeled with C: and S:, and > part with I: and L:. This refers to the BEEP Initiator and Listener. GET-CAPABILITY can be initiated by the CUA or CS. 3.3.1 Use of BEEP, MIME and iCalendar ... This example tells the CS to generate and return 10 UIDs to be used by the CUA. (Note throughout this memo, 'C:' refers to what the CUA sends, 'S:' refers to what the CS sends, 'I:' refers to what the initiator sends, and 'L:' refers to what the listener sends. Where initiator and responder are used as defined in [BEEP].) -Doug From owner-ietf-calendar@mail.imc.org Tue Jul 9 15:32:58 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14278 for ; Tue, 9 Jul 2002 15:32:57 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g69JPWW04241 for ietf-calendar-bks; Tue, 9 Jul 2002 12:25:32 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g69JPVw04237 for ; Tue, 9 Jul 2002 12:25:31 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 4D59615533; Tue, 9 Jul 2002 21:25:33 +0200 (CEST) Date: Tue, 9 Jul 2002 21:25:33 +0200 From: Andrea Campi To: ietf-calendar@imc.org Subject: Re: Examples in latest draft Message-ID: <20020709192533.GM98336@inet.it> References: <20020709174743.GH98336@inet.it> <3D2B2833.8E0FCB62@Royer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D2B2833.8E0FCB62@Royer.com> Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Tue, Jul 09, 2002 at 12:15:15PM -0600, Doug Royer wrote: > > Andrea Campi wrote: > > > > The VCALENDAR is missing the PRODID property. Moreover, VREPLY is > > mispelled as REPLY. > > Thanks, I just edited in those fixes. Great, thanks. By the way, I only mentioned CREATE as an example, but it wasn't the only one missing PRODID... > > > In addition, part of the exhanges are labeled with C: and S:, and > > part with I: and L:. > > This refers to the BEEP Initiator and Listener. GET-CAPABILITY > can be initiated by the CUA or CS. > Right, I see it now. > > -Doug Bye, Andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Fri Jul 12 05:32:17 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13523 for ; Fri, 12 Jul 2002 05:32:16 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6C99aq01413 for ietf-calendar-bks; Fri, 12 Jul 2002 02:09:36 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6C99Yw01409 for ; Fri, 12 Jul 2002 02:09:35 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 8164615538; Fri, 12 Jul 2002 11:09:33 +0200 (CEST) Date: Fri, 12 Jul 2002 11:09:33 +0200 From: Andrea Campi To: ietf-calendar@imc.org Subject: QUERY-LEVEL vs CAR-LEVEL Message-ID: <20020712090933.GF46205@inet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, looking at section 9.3, definition of CS properties: QUERY-LEVEL can take values CAL-QL-1 or NONE CAR-LEVEL can take CAR-NONE, CAR-MIN, CAR-FULL-1. This doesn't sound logical, exp. given that they are related (QUERY-LEVEL:NONE imply CAR-LEVEL:CAR-NONE). I propose we change NONE to CAL-QL-NONE. Bye, Andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Fri Jul 12 10:13:51 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23731 for ; Fri, 12 Jul 2002 10:13:50 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6CE5A204025 for ietf-calendar-bks; Fri, 12 Jul 2002 07:05:10 -0700 (PDT) Received: from CarWash.IncentiveSystems.com (CarWash.IncentiveSystems.com [66.152.247.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g6CE59w04020 for ; Fri, 12 Jul 2002 07:05:09 -0700 (PDT) Received: from minglewood.incentivesystems.com ([172.16.0.25]) by CarWash.IncentiveSystems.com (NAVGW 2.5.2.11) with SMTP id M2002071210103830768 for ; Fri, 12 Jul 2002 10:10:38 -0400 Received: from incentivesystems.com ([10.10.48.190]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 12 Jul 2002 10:03:34 -0400 Message-ID: <3D2EE1B6.5050606@incentivesystems.com> Date: Fri, 12 Jul 2002 10:03:34 -0400 From: John Stracke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: QUERY-LEVEL vs CAR-LEVEL References: <20020712090933.GF46205@inet.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Jul 2002 14:03:35.0009 (UTC) FILETIME=[E999F510:01C229AC] Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Andrea Campi wrote: >This doesn't sound logical, exp. given that they are related >(QUERY-LEVEL:NONE imply CAR-LEVEL:CAR-NONE). > I don't think it does, actually; it would probably be possible to have the ability to submit iTIP messages subject to access controls. >I propose we change NONE to CAL-QL-NONE. > > As the person who came up with NONE in the first place (for CRISP...which I need to update...), I don't have a problem with this. -- /========================================================\ |John Stracke |Principal Engineer | |jstracke@incentivesystems.com |Incentive Systems, Inc.| |http://www.incentivesystems.com |My opinions are my own.| |========================================================| |This is the .sig that says... Ni! | \========================================================/ From owner-ietf-calendar@mail.imc.org Fri Jul 12 11:58:33 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29650 for ; Fri, 12 Jul 2002 11:58:32 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6CFpuw17095 for ietf-calendar-bks; Fri, 12 Jul 2002 08:51:56 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6CFptw17091 for ; Fri, 12 Jul 2002 08:51:55 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 738881555E; Fri, 12 Jul 2002 17:51:55 +0200 (CEST) Date: Fri, 12 Jul 2002 17:51:54 +0200 From: Andrea Campi To: John Stracke Cc: ietf-calendar@imc.org Subject: Re: QUERY-LEVEL vs CAR-LEVEL Message-ID: <20020712155154.GL46205@inet.it> References: <20020712090933.GF46205@inet.it> <3D2EE1B6.5050606@incentivesystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D2EE1B6.5050606@incentivesystems.com> Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Fri, Jul 12, 2002 at 10:03:34AM -0400, John Stracke wrote: > > Andrea Campi wrote: > > >This doesn't sound logical, exp. given that they are related > >(QUERY-LEVEL:NONE imply CAR-LEVEL:CAR-NONE). > > > I don't think it does, actually; it would probably be possible to have > the ability to submit iTIP messages subject to access controls. Well, the draft says: QUERY-LEVEL 1 Indicates level of SQL support. CAL-QL-1 or NONE. (NONE is for CS's that allow ITIP methods only to be deposited and nothing else). If set to NONE, then the 'car' capability MUST BE set to NONE. The rational for this would be that VCAR are specified using a query (the SCOPE property), so if you don't understand CAL-QL you can't understand a full VCAR. On the other hand, I can imagine a server could have at least DEFAULT-VCARS without necessarily using CAL-QL. So yes, I agree with you and think that period should be reviewed. Bye, Andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Sun Jul 14 16:06:15 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15549 for ; Sun, 14 Jul 2002 16:06:14 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6EJtE711262 for ietf-calendar-bks; Sun, 14 Jul 2002 12:55:14 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6EJtDw11255 for ; Sun, 14 Jul 2002 12:55:14 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6EJsqM9006497 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 14 Jul 2002 12:55:05 -0700 Message-ID: <3D31D3D3.440E3B69@Royer.com> Date: Sun, 14 Jul 2002 13:41:07 -0600 From: Doug Royer Reply-To: ietf-calendar@imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: QUERY-LEVEL vs CAR-LEVEL References: <20020712090933.GF46205@inet.it> <3D2EE1B6.5050606@incentivesystems.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit John Stracke wrote: > > Andrea Campi wrote: > >I propose we change NONE to CAL-QL-NONE. > > > > > As the person who came up with NONE in the first place (for > CRISP...which I need to update...), I don't have a problem with this. If there are no objections, I'll change it to CAL-QL-NONE From owner-ietf-calendar@mail.imc.org Mon Jul 15 09:52:30 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04569 for ; Mon, 15 Jul 2002 09:52:30 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6FDjvc14327 for ietf-calendar-bks; Mon, 15 Jul 2002 06:45:57 -0700 (PDT) Received: from mail.samsungcontact.com ([195.89.159.51]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6FDjtw14323 for ; Mon, 15 Jul 2002 06:45:55 -0700 (PDT) Received: from mail.samsungcontact.com (root@localhost) by mail.samsungcontact.com (8.11.6/8.11.6) with ESMTP id g6FDjpg28371; Mon, 15 Jul 2002 14:45:52 +0100 Received: from samsungcontact.com (host195-89-159-62.uk.regusnet.com 195.89.159.62) by mail.samsungcontact.com (Samsung Contact SMTP Relay 7.1.0) via ESMTP; Mon, 15 Jul 2002 14:45:53 +0100 (BST) Message-ID: <3D32D20D.2000902@samsungcontact.com> Date: Mon, 15 Jul 2002 14:45:49 +0100 From: Mark Davidson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "ietf-calendar@imc.org" CC: Doug Royer Subject: CREATE command definition in draft-08 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit In section 9.1.4 create-vreply = "BEGIN" ":" "VREPLY" CRLF created-id request-status *(x-prop) "END" ":" "VREPLY" CRLF ; Where the id is appropriate for the ; type of object created: ; ; VAGENDA = calid ; VCAR = carid ; VEVENT, VFREEBUSY, VJOURNAL, VTODO = uid ; VQUERY = queryid ; ALARM = sequence ; x-component = x-id ; I think the comments should be as I don't think you can create ALARMS with CREATE, you would use MODIFY (If I am wrong about creating ALARMS, then some different changes need to be made around what a TARGET can be): ; VAGENDA = calid ; VCAR = carid ; VEVENT, VFREEBUSY, VJOURNAL, VTODO = uid ; VQUERY = queryid ; VTIMEZONE = tzid ; x-component = x-id Just under that: created-id = ( calid / carid / uid / uid dtstamp / queryid / tzid / sequence / x-id) When would "uid timestamp" be used? Is it "uid" space "timestamp"? A bit further down in this section: create-reply = "BEGIN" ":" "VCALENDAR" CRLF calprops *(iana-prop) *(x-prop) 1*(create-comp-vreply) "END" ":" "VCALENDAR" CRLF create-comp-vreply is not defined. I am also unsure of what the restrictions table for a create reply is telling me, that the Responce: section did not (apart from it is possible to send an iTIP response). Also a small typo in the same section (page 95) The CS would sends the REPLY in separate MIME objects, one per TARGET. Should be: The CS would send the REPLY in separate MIME objects, one per TARGET. Mark Davidson From owner-ietf-calendar@mail.imc.org Mon Jul 15 21:01:13 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22262 for ; Mon, 15 Jul 2002 21:01:12 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6G0qdH12982 for ietf-calendar-bks; Mon, 15 Jul 2002 17:52:39 -0700 (PDT) Received: from rockpub2.rockliffe.com (rockpub2.rockliffe.com [147.208.187.183]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6G0qcw12974 for ; Mon, 15 Jul 2002 17:52:38 -0700 (PDT) Received: from mars (peluzo-sdsl-141.istep.com [209.133.115.141]) by rockliffe.com (Rockliffe SMTPRA 5.2.4) with ESMTP id for ; Mon, 15 Jul 2002 17:52:44 -0700 Message-ID: <001b01c22c63$3e298c90$8d7385d1@mars> From: "Mike Hixson" To: Subject: target property in draft-08 Date: Mon, 15 Jul 2002 17:53:46 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C22C28.9168E580" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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_0018_01C22C28.9168E580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, In section 2 (Additions to iCalendar) it says that the "target" property = is optional, but must not occur more than once. However on page 93 and = 94 there is some discussion and an example using multiple "target" = properties. Can someone please clarify? Is there a typo in section 2? Regards, Mike = Fact - Over 85% of viruses enter networks via e-mail. This message has been scanned for viruses and delivered by Rockliffe Mail= Site. http://www.rockliffe.com/products/av= ------=_NextPart_000_0018_01C22C28.9168E580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
In section 2 (Additions to iCalendar) = it says that=20 the "target" property is optional, but must not occur more than once. = However on=20 page 93 and 94 there is some discussion and an example using = multiple=20 "target" properties. Can someone please clarify? Is there a typo in = section=20 2?
 
Regards,
Mike
=
Fact - Over 85% of = viruses enter networks via e-mail.
This message has been scanned for viruses and delivered by Rockliffe Mail= Site.
http://www.rockliffe.co= m/products/av/= ------=_NextPart_000_0018_01C22C28.9168E580-- From owner-ietf-calendar@mail.imc.org Mon Jul 15 22:12:18 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24572 for ; Mon, 15 Jul 2002 22:12:18 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6G25hY14819 for ietf-calendar-bks; Mon, 15 Jul 2002 19:05:43 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6G25gw14815 for ; Mon, 15 Jul 2002 19:05:42 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6G25hM9016851 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 15 Jul 2002 19:05:45 -0700 Message-ID: <3D337C2F.5B2AE27A@Royer.com> Date: Mon, 15 Jul 2002 19:51:43 -0600 From: Doug Royer Reply-To: "ietf-calendar@imc.org" Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: target property in draft-08 References: <001b01c22c63$3e298c90$8d7385d1@mars> Content-Type: multipart/mixed; boundary="------------9D328586478197A771CEFEB4" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------9D328586478197A771CEFEB4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Mike Hixson wrote: > > Hi, > > In section 2 (Additions to iCalendar) it says that the "target" > property is optional, but must not occur more than once. However on > page 93 and 94 there is some discussion and an example using multiple > "target" properties. Can someone please clarify? Is there a typo in > section 2? Your right - thanks. It should be: calprops = 2*( ; 'prodid' and 'version' are both REQUIRED, ; but MUST NOT occur more than once. ; prodid /version / ; These are optional, but MUST NOT occur ; more than once. ; calscale / method / iana-prop / cmd / ; These are optional, and may occur more ; than once. ; target / x-prop --------------9D328586478197A771CEFEB4 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------9D328586478197A771CEFEB4-- From owner-ietf-calendar@mail.imc.org Tue Jul 16 13:24:41 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24823 for ; Tue, 16 Jul 2002 13:24:41 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6GHEHw19916 for ietf-calendar-bks; Tue, 16 Jul 2002 10:14:17 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6GHEGw19912 for ; Tue, 16 Jul 2002 10:14:16 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 3D84D15511; Tue, 16 Jul 2002 19:14:17 +0200 (CEST) Date: Tue, 16 Jul 2002 19:14:17 +0200 From: Andrea Campi To: ietf-calendar@imc.org Subject: CAL-QUERY definition Message-ID: <20020716171417.GJ67602@inet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, there's something I don't understand in the definition of CAL-QUERY. - cauprops and capcprops are used but not defined anywhere. They look like they have no purpose either; maybe they are leftovers from a previous revision? - uprop-list and cprop-list are defined but not used? - cap-local, what purpose does it serve? Its description mentions cap-using but that's not defined anywhere. - cap-colval is the only thing which can appear on the left side of a cap-oper, but it doesn't include STATE() etc. This doesn't look right and goes against the examples (or I am missing something). In addition, it accepts cap-ucolq which isn't defined. - cap-factor = cap-colval SP cap-oper SP col-value / cap-colval SP "NOT LIKE" SP col-value / cap-colval SP "LIKE" SP col-value / cap-colval SP "IS NULL" / cap-colval SP "IS NOT NULL" / col-value SP "NOT IN" cap-colval" / col-value SP "IN" cap-colval" There are extra double quotes at end of the last two lines. - [NOT] OWNER() is not allowed anywhere - should it be, or should it just be moved to UPN-FILTER? Also, I don't think the definition allows for component.property syntax (but I might be completely wrong here). A couple of suggestions: - it could be a good idea to explicitely state that AND, OR etc are case sensitive and MUST be spelled in capital letters. This is apparent from the draft but we all know the devil is in the details... - PARAM() could use at least a short paragraph like the other functions - literal-data definition talks about value types, but I think it could be beneficial to state that enumerated types are equivalent to strings. Otherwise you wouldn't be able to say: TRANSP='OPAQUE' A final note: I hate the mismatch between '=' and '!='. It should either be '=' and '<>' as in SQL, or '==' and '!=' as in C. Bye, Andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Tue Jul 16 15:46:08 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28313 for ; Tue, 16 Jul 2002 15:46:08 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6GJcU729153 for ietf-calendar-bks; Tue, 16 Jul 2002 12:38:30 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6GJcTw29147 for ; Tue, 16 Jul 2002 12:38:29 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6GJcTM9023192 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 16 Jul 2002 12:38:31 -0700 Message-ID: <3D3472E4.8800C360@Royer.com> Date: Tue, 16 Jul 2002 13:24:20 -0600 From: Doug Royer Reply-To: ietf-calendar@imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: CAL-QUERY definition References: <20020716171417.GJ67602@inet.it> Content-Type: multipart/mixed; boundary="------------2525223DBB23363E45FADC06" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------2525223DBB23363E45FADC06 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Andrea Campi wrote: > > Hi all, > > there's something I don't understand in the definition of CAL-QUERY. > > - cauprops and capcprops are used but not defined anywhere. They > look like they have no purpose either; maybe they are leftovers > from a previous revision? > > - uprop-list and cprop-list are defined but not used? > > - cap-local, what purpose does it serve? Its description mentions > cap-using but that's not defined anywhere. They may have been left over from a previous edit - thanks - looking. > - cap-colval is the only thing which can appear on the left side > of a cap-oper, but it doesn't include STATE() etc. This doesn't > look right and goes against the examples (or I am missing something). > In addition, it accepts cap-ucolq which isn't defined. Looks as if this needs more editing :-) I'll spend some time this weekend and go through that in detail and send the new section to the list for editorial review. > / col-value SP "NOT IN" cap-colval" > / col-value SP "IN" cap-colval" > > There are extra double quotes at end of the last two lines. Thanks I just remove them. > - [NOT] OWNER() is not allowed anywhere - should it be, or should > it just be moved to UPN-FILTER? No, it should also be allowed in the query as in, SELECT * FROM vevent WHERE ORGANIZER = OWNER() I'll update the ABNF, thanks for finding that. > Also, I don't think the definition allows for component.property > syntax (but I might be completely wrong here). > > A couple of suggestions: > > - it could be a good idea to explicitely state that AND, OR etc > are case sensitive and MUST be spelled in capital letters. This is > apparent from the draft but we all know the devil is in the details... They are not case sensitive - all of iCalendar is case in-sensitive. Do we need to add a note to CAP for this? Or is that it is already defined in 2445 sufficient? > - PARAM() could use at least a short paragraph like the other > functions Yep - I'll add a section. > - literal-data definition talks about value types, but I think it > could be beneficial to state that enumerated types are equivalent > to strings. Otherwise you wouldn't be able to say: > > TRANSP='OPAQUE' Another great find - thanks. > A final note: I hate the mismatch between '=' and '!='. It should > either be '=' and '<>' as in SQL, or '==' and '!=' as in C. Good point, if there are no objections, I'll change any '!=' to '<>'. --------------2525223DBB23363E45FADC06 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------2525223DBB23363E45FADC06-- From owner-ietf-calendar@mail.imc.org Tue Jul 16 16:08:12 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28656 for ; Tue, 16 Jul 2002 16:08:11 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6GK1vC00881 for ietf-calendar-bks; Tue, 16 Jul 2002 13:01:57 -0700 (PDT) Received: from CarWash.IncentiveSystems.com (CarWash.IncentiveSystems.com [66.152.247.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g6GK1uw00874 for ; Tue, 16 Jul 2002 13:01:56 -0700 (PDT) Received: from minglewood.incentivesystems.com ([172.16.0.25]) by CarWash.IncentiveSystems.com (NAVGW 2.5.2.11) with SMTP id M2002071616072419334 for ; Tue, 16 Jul 2002 16:07:24 -0400 Received: from incentivesystems.com ([10.10.48.190]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.2966); Tue, 16 Jul 2002 16:00:22 -0400 Message-ID: <3D347B56.70107@incentivesystems.com> Date: Tue, 16 Jul 2002 16:00:22 -0400 From: John Stracke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: CAL-QUERY definition References: <20020716171417.GJ67602@inet.it> <3D3472E4.8800C360@Royer.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Jul 2002 20:00:22.0165 (UTC) FILETIME=[6AE9BC50:01C22D03] Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Doug Royer wrote: >They are not case sensitive - all of iCalendar is case in-sensitive. > Actually, no, it's not. From 2445: All names of properties, property parameters, enumerated property values and property parameter values are case-insensitive. However, all other property values are case-sensitive, unless otherwise stated. -- /========================================================\ |John Stracke |Principal Engineer | |jstracke@incentivesystems.com |Incentive Systems, Inc.| |http://www.incentivesystems.com |My opinions are my own.| |========================================================| |This is the .sig that says... Ni! | \========================================================/ From owner-ietf-calendar@mail.imc.org Tue Jul 16 18:49:06 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01826 for ; Tue, 16 Jul 2002 18:49:05 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6GMgc405399 for ietf-calendar-bks; Tue, 16 Jul 2002 15:42:38 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6GMgbw05395 for ; Tue, 16 Jul 2002 15:42:37 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6GMgbM9024268 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 16 Jul 2002 15:42:40 -0700 Message-ID: <3D349E0B.D4D9A787@Royer.com> Date: Tue, 16 Jul 2002 16:28:27 -0600 From: Doug Royer Reply-To: "ietf-calendar@imc.org" Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: CAP draft typos: bibliography/references 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 "G. Barnes" wrote: > > While reading the latest CAP draft, I noticed the bibliography > didn't match completely with the references in the text. This isn't > surprising in a draft, so I did a little work which hopefully someone > can use to make the bibliography/references more useful. > > Here are my notes, which hopefully are self-explanatory: > ... VERY helpful - THANKS! -Doug From owner-ietf-calendar@mail.imc.org Tue Jul 16 19:14:05 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02303 for ; Tue, 16 Jul 2002 19:14:04 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6GMAlm03794 for ietf-calendar-bks; Tue, 16 Jul 2002 15:10:47 -0700 (PDT) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6GMAkw03790 for ; Tue, 16 Jul 2002 15:10:46 -0700 (PDT) Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6GMAiS4003617 for ; Tue, 16 Jul 2002 15:10:49 -0700 Received: FROM mead1.u.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Jul 16 15:10:43 2002 -0700 Received: from localhost (gsbarnes@localhost) by mead1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g6GMAg5x028962 for ; Tue, 16 Jul 2002 15:10:43 -0700 Date: Tue, 16 Jul 2002 15:10:42 -0700 (PDT) From: "G. Barnes" To: "ietf-calendar@imc.org" Subject: CAP draft typos: bibliography/references In-Reply-To: <3D3472E4.8800C360@Royer.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: While reading the latest CAP draft, I noticed the bibliography didn't match completely with the references in the text. This isn't surprising in a draft, so I did a little work which hopefully someone can use to make the bibliography/references more useful. Here are my notes, which hopefully are self-explanatory: -------------------------------------------------------- Text abbreviation different from bibliographic abbreviation In text: [BEEP] (numerous places) In bibliography: [RFC3080] text: [MIME] (numerous places) bib: [RFC2045] text: [BEEPTCP] (p21) bib: [RFC3081] text: [SASL] (p23) bib: [RFC2222] text: [SQL92] (p32) bib: [SQL] text: [RFC396] (p9) bib: [RFC2396] Note: 2396 is correct -------------------------------------------------------- in text, but not in bibliography [GUIDE] (p5) --- I think this is RFC 3283, Guide to Internet Calendaring [RFC2718] (p9) --- Guidelines for new URL Schemes [RFC 2459] (p24) --- Internet X.509 Public Key Infrastructure Certificate and CRL Profile (obsoleted by RFC3280) [RFC 2278] (p57) --- IANA Charset Registration Procedures (obsoleted by RFC 2978) [RFC 2277] (p58) --- IETF Policy on Character Sets and Languages -------------------------------------------------------- in bibliography, but not in text: [RFC1521] Borenstein, N., Freed, N., "Specifying and Describing the Format of Internet Message Bodies", RFC 1521, September 1993 ftp://ftp.isi.edu/in-notes/rfc1521.txt [RFC2246] Dierks, T. and Allen, C., "The TLS Protocol Version 1.0", RFC 2246, January 1999 ftp://ftp.isi.edu/in-notes/rfc2246.txt [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource Locators", RFC 2392, August 1998 ftp://ftp.isi.edu/in-notes/rfc2392.txt [UNICODE] The Unicode Consortium, "The Unicode Standard, Version 3.1" http://www.unicode.org/unicode/standard/standard.html [US-ASCII] Coded Character Set -- 7-bit American Standard Code for Information Interchange, ANSI X3.4-1986. [CharEncoding] "Worldwide Character Encoding -- Version 1.0", Addison-Wesley, Volume 1, 1991, Volume 2, 1992. UTF-8 is described in Unicode Technical Report #4. -------------------------------------------------------- Greg Barnes Computing and Communications, University of Washington gsbarnes@cac.washington.edu (206) 685-3295 From owner-ietf-calendar@mail.imc.org Wed Jul 17 03:56:48 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09121 for ; Wed, 17 Jul 2002 03:56:48 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6H7oFj04349 for ietf-calendar-bks; Wed, 17 Jul 2002 00:50:15 -0700 (PDT) Received: from rockpub2.rockliffe.com (rockpub2.rockliffe.com [147.208.187.183]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6H7oEw04342 for ; Wed, 17 Jul 2002 00:50:14 -0700 (PDT) Received: from mars (peluzo-sdsl-141.istep.com [209.133.115.141]) by rockliffe.com (Rockliffe SMTPRA 5.2.4) with ESMTP id for ; Wed, 17 Jul 2002 00:50:03 -0700 Message-ID: <000c01c22d66$b3e94ac0$8d7385d1@mars> From: "Mike Hixson" To: Subject: Text value data type in iCal Date: Wed, 17 Jul 2002 00:51:04 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01C22D2C.0734B1A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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_0009_01C22D2C.0734B1A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi All, Anyone know if the text value data type in iCal has been updated to = include a requirement for the equals sign to be escaped? The reason I = ask is because I don't see how to distinguish between a property that = has a structured value and one that just has a regular value -- both of = which are defined as valid TEXT types. For example: Property with a text value as a structured value (I don't know of a real = text property that uses structured values so I made one up): MYPROP:FREQ=3DYEARLY Property with a regular text value: DESCRIPTION:MONKEY=3DFUN If the second example were like the following there would be no problem: DESCRIPTION:MONKEY\=3DFUN Also, anyone know where I can find the ABNF or more info for a = structured value? Specifically, I'm looking for the valid characters for = the TEXT and VALUE parts of a structured value. Only discussion about = structured values in iCal is: 4.1.1 Some property values are defined in terms of multiple parts. These structured property values MUST have their value parts separated by a SEMICOLON character (US-ASCII decimal 59). 4.3.11 The "TEXT" property values may also contain special characters that are used to signify delimiters, such as a COMMA character for lists of values or a SEMICOLON character for structured values. Regards, Mike = Fact - Over 85% of viruses enter networks via e-mail. This message has been scanned for viruses and delivered by Rockliffe Mail= Site. http://www.rockliffe.com/products/av= ------=_NextPart_000_0009_01C22D2C.0734B1A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi All,
 
Anyone know if the text value data type = in iCal has=20 been updated to include a requirement for the equals sign to be escaped? = The=20 reason I ask is because I don't see how to distinguish between a = property that=20 has a structured value and one that just has a regular value -- both of = which=20 are defined as valid TEXT types. For example:
 
Property with a text value as a = structured value (I=20 don't know of a real text property that uses structured values so I made = one=20 up):
MYPROP:FREQ=3DYEARLY
 
Property with a regular text = value:
DESCRIPTION:MONKEY=3DFUN
 
If the second example were like the = following there=20 would be no problem:
DESCRIPTION:MONKEY\=3DFUN
 
Also, anyone know where I can find the = ABNF or more=20 info for a structured value? Specifically, I'm looking for the valid = characters=20 for the TEXT and VALUE parts of a structured value. Only discussion = about=20 structured values in iCal is:
 
4.1.1
   Some property values are defined in terms of multiple = parts.=20 These
   structured property values MUST have their value = parts=20 separated by a
   SEMICOLON character (US-ASCII decimal = 59).
 
4.3.11
   The "TEXT" property values may also contain special = characters=20 that
   are used to signify delimiters, such as a COMMA = character=20 for lists
   of values or a SEMICOLON character for = structured=20 values.
 
Regards,
Mike
=
Fact - Over 85% of = viruses enter networks via e-mail.
This message has been scanned for viruses and delivered by Rockliffe Mail= Site.
http://www.rockliffe.co= m/products/av/= ------=_NextPart_000_0009_01C22D2C.0734B1A0-- From owner-ietf-calendar@mail.imc.org Wed Jul 17 04:15:15 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09468 for ; Wed, 17 Jul 2002 04:15:15 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6H89rj09027 for ietf-calendar-bks; Wed, 17 Jul 2002 01:09:53 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6H89qw09016 for ; Wed, 17 Jul 2002 01:09:52 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id CB02A15510; Wed, 17 Jul 2002 10:09:51 +0200 (CEST) Date: Wed, 17 Jul 2002 10:09:51 +0200 From: Andrea Campi To: ietf-calendar@imc.org Subject: Re: CAL-QUERY definition Message-ID: <20020717080951.GA19507@inet.it> References: <20020716171417.GJ67602@inet.it> <3D3472E4.8800C360@Royer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D3472E4.8800C360@Royer.com> Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Tue, Jul 16, 2002 at 01:24:20PM -0600, Doug Royer wrote: > Andrea Campi wrote: > > > > Hi all, > > > > there's something I don't understand in the definition of CAL-QUERY. > > [...] > They may have been left over from a previous edit - thanks - looking. > [...] Great, thanks. While I was writing the text below, I noticed formal definitions for ENABLE Parameter (6.2.1) and LOCAL Parameter (6.2.2) are incorrect (copy and past-o :-?). Also, there's a typo (Format Definition instead of Formal) all over the draft. Also, ALLOW-CONFLICT property doesn't specify the default in case no ALLOW-CONFLICT is present. I'd like to suggest a couple of parameters for QUERYID (I am open to suggestions for the names): NAMESPACE Parameter Parameter Name: NAMESPACE Purpose: This parameter qualifies the QUERYID as belonging to a particular namespace. Value Type: TEXT Conformance: This property MAY be specified in the "QUERID" properties. Description: CAP server implementation may choose to qualify queries as belonging to a namespace. Namespaces are completely separated from one another, so that queries with the same name but different names can coexist. This allows a client to install stored queries in a server without worrying about name conflicts. This parameter is less useful for non-stored queries but may be specified for documentation purpose. Formal Definition: The parameter is defined by the following notation: namespace = "NAMESPACE" ":" text Example: The following is an example of two different stored queries with the same QUERYID in the same namespace. They could both exist in the same CAP server as they don't conflict with each other. BEGIN:VQUERY QUERYID;NAMESPACE=example.net:A query END:VQUERY BEGIN:VQUERY QUERYID;NAMESPACE=example.com:A query END:VQUERY NATIVE Parameter Parameter Name: NATIVE Purpose: This parameter qualifies the QUERY as having an implementation known only to the server and not necessarily mappable to a CAL-QL-1. Value Type: BOOLEAN Conformance: This property MAY be specified in the "QUERID" properties for stored queries. Description: A server may choose to implement some stored queries in the most efficient way, which may not be easy to express in CAL-QL-1. A server may also choose to do this in order to avoid having to parse and compile CAL-QL-1 queries in its native query language. This parameter allows a server to mark queries as having a native implementation, so a client can't expect to know how the query works. However, the client can still ask the server to run the query if it knows what it returns. This can be thought as the equivalence of encapsulation in object oriented parlance. The parameter defaults to FALSE Formal Definition: The parameter is defined by the following notation: native = "NATIVE" ":" boolean I also propose to change VQUERY to allow a VERSION property. This allows a future draft to define extensions to the query language while keeping backward and forward compatibility. If you agree to this, then I think we should discuss whether or not the QUERY-LEVEL should allow for a list. To give you an example of what I'm talking about, let's say a future draft defines substitution parameters in stored queries, so that for instance it's possible to store (this is just an example!): BEGIN:VQUERY QUERYID;NAMESPACE=example.com:foo(date) QUERY:SELECT * FROM VEVENT WHERE DTSTART = ?date? END:VQUERY which would be then invoked as: BEGIN:VCALENDAR VERSION:2.0 CMD:QUERY TARGET:relcal1 BEGIN:VQUERY QUERYID;NAMESPACE=example.com:foo('20020708T000000Z') END:VQUERY This could be name CAL-QL-EXT1. At a later time a new draft could specify CAL-QL-EXT2, which doesn't imply CAL-QL-EXT1. It would be most useful to be able to say: ... BEGIN:VREPLY ... QUERY-LEVEL:CAL-QL-1,CAL-QL-EXT2,my-extensions ... END:VREPLY Wow, it's a lot of proposals at a time! What do you say? Bye, andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Wed Jul 17 05:33:17 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10933 for ; Wed, 17 Jul 2002 05:33:16 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6H9QFA18443 for ietf-calendar-bks; Wed, 17 Jul 2002 02:26:15 -0700 (PDT) Received: from rockpub2.rockliffe.com (rockpub2.rockliffe.com [147.208.187.183]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6H9QEw18438 for ; Wed, 17 Jul 2002 02:26:14 -0700 (PDT) Received: from mars (peluzo-sdsl-141.istep.com [209.133.115.141]) by rockliffe.com (Rockliffe SMTPRA 5.2.4) with ESMTP id ; Wed, 17 Jul 2002 02:26:17 -0700 Message-ID: <004101c22d74$252393a0$8d7385d1@mars> From: "Mike Hixson" To: Cc: "Andrea Campi" References: <000c01c22d66$b3e94ac0$8d7385d1@mars> <20020717085518.GB19507@inet.it> Subject: Re: Text value data type in iCal Date: Wed, 17 Jul 2002 02:27:17 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit > Uhm... it's my understanding that structured types are expressed > using parameters, so that your example would become something like: > > MYPROP;FREQ=YEARLY:value > > DESCRIPTION:MONKEY=FUN would be no problem. This is what I thought too until I read section 4.1.1 in iCal. In that section there are the following two paragraphs: Some property values are defined in terms of multiple parts. These structured property values MUST have their value parts separated by a SEMICOLON character (US-ASCII decimal 59). This says that property *value* can be a structured value. I also found an example of this on page 44 of iCal RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1 Some properties allow a list of parameters. Each property parameter in a list of property parameters MUST be separated by a SEMICOLON character (US-ASCII decimal 59). This paragraph directly follows, which discusses list of parameters. So a property value *can* have structured values, unless I'm not reading these paragraphs right? -Mike ----- Original Message ----- From: "Andrea Campi" To: "Mike Hixson" Sent: Wednesday, July 17, 2002 1:55 AM Subject: Re: Text value data type in iCal > On Wed, Jul 17, 2002 at 12:51:04AM -0700, Mike Hixson wrote: > > Hi All, > > > > Anyone know if the text value data type in iCal has been updated to include a requirement for the equals sign to be escaped? The reason I ask is because I don't see how to distinguish between a property that has a structured value and one that just has a regular value -- both of which are defined as valid TEXT types. For example: > > > > Property with a text value as a structured value (I don't know of a real text property that uses structured values so I made one up): > > MYPROP:FREQ=YEARLY > > > > Property with a regular text value: > > DESCRIPTION:MONKEY=FUN > > > > If the second example were like the following there would be no problem: > > DESCRIPTION:MONKEY\=FUN > > > > Also, anyone know where I can find the ABNF or more info for a structured value? Specifically, I'm looking for the valid characters for the TEXT and VALUE parts of a structured value. Only discussion about structured values in iCal is: > > > > Uhm... it's my understanding that structured types are expressed > using parameters, so that your example would become something like: > > MYPROP;FREQ=YEARLY:value > > DESCRIPTION:MONKEY=FUN would be no problem. > > Bye, > Andrea > > -- > Andrea Campi mailto:a.campi@inet.it > I.NET S.p.A. http://www.inet.it > Direzione Tecnica - R&D phone: +39 02 32863 ext 1 > v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 > Settimo Milanese (MI), Italy > Fact - Over 85% of viruses enter networks via e-mail. This message has been scanned for viruses and delivered by Rockliffe MailSite. http://www.rockliffe.com/products/av From owner-ietf-calendar@mail.imc.org Wed Jul 17 05:49:29 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11145 for ; Wed, 17 Jul 2002 05:49:28 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6H9dKG18880 for ietf-calendar-bks; Wed, 17 Jul 2002 02:39:20 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6H9dJw18876 for ; Wed, 17 Jul 2002 02:39:19 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 13DD415510; Wed, 17 Jul 2002 11:39:19 +0200 (CEST) Date: Wed, 17 Jul 2002 11:39:18 +0200 From: Andrea Campi To: Mike Hixson Cc: ietf-calendar@imc.org Subject: Re: Text value data type in iCal Message-ID: <20020717093918.GC19507@inet.it> References: <000c01c22d66$b3e94ac0$8d7385d1@mars> <20020717085518.GB19507@inet.it> <004101c22d74$252393a0$8d7385d1@mars> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004101c22d74$252393a0$8d7385d1@mars> Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Wed, Jul 17, 2002 at 02:27:17AM -0700, Mike Hixson wrote: > > Uhm... it's my understanding that structured types are expressed > > using parameters, so that your example would become something like: > > > > MYPROP;FREQ=YEARLY:value > > > > DESCRIPTION:MONKEY=FUN would be no problem. > > This is what I thought too until I read section 4.1.1 in iCal. In that > section there are the following two paragraphs: > > Some property values are defined in terms of multiple parts. These > structured property values MUST have their value parts separated by a > SEMICOLON character (US-ASCII decimal 59). > > This says that property *value* can be a structured value. I also found an > example of this on page 44 of iCal > RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1 > > Some properties allow a list of parameters. Each property parameter > in a list of property parameters MUST be separated by a SEMICOLON > character (US-ASCII decimal 59). > > This paragraph directly follows, which discusses list of parameters. So a > property value *can* have structured values, unless I'm not reading these > paragraphs right? You are right, I didn't really understand the question, sorry. But still I don't see any reason to change anything. What you quote says exactly that "some property values are defined in terms of multiple parts". The only such value (that I can think ok) is RECUR, and it's properly defined in such a way not to cause ambiguity. No other value type allows for multiple parts (in particular TEXT, which you used in your example, doesn't), so RFC2445 is perfectly consistent. The problem would exist if there were (or a future revision introduced) a value type like: example = "A" "=" "something" (";" text) or example = "A" "=" "something" (";" "B" "=" text) But as things stand, IMHOwe're perfectly safe. Bye, Andrea > > -Mike > > ----- Original Message ----- > From: "Andrea Campi" > To: "Mike Hixson" > Sent: Wednesday, July 17, 2002 1:55 AM > Subject: Re: Text value data type in iCal > > > > On Wed, Jul 17, 2002 at 12:51:04AM -0700, Mike Hixson wrote: > > > Hi All, > > > > > > Anyone know if the text value data type in iCal has been updated to > include a requirement for the equals sign to be escaped? The reason I ask is > because I don't see how to distinguish between a property that has a > structured value and one that just has a regular value -- both of which are > defined as valid TEXT types. For example: > > > > > > Property with a text value as a structured value (I don't know of a real > text property that uses structured values so I made one up): > > > MYPROP:FREQ=YEARLY > > > > > > Property with a regular text value: > > > DESCRIPTION:MONKEY=FUN > > > > > > If the second example were like the following there would be no problem: > > > DESCRIPTION:MONKEY\=FUN > > > > > > Also, anyone know where I can find the ABNF or more info for a > structured value? Specifically, I'm looking for the valid characters for the > TEXT and VALUE parts of a structured value. Only discussion about structured > values in iCal is: > > > > > > > Uhm... it's my understanding that structured types are expressed > > using parameters, so that your example would become something like: > > > > MYPROP;FREQ=YEARLY:value > > > > DESCRIPTION:MONKEY=FUN would be no problem. > > > > Bye, > > Andrea > > > > -- > > Andrea Campi mailto:a.campi@inet.it > > I.NET S.p.A. http://www.inet.it > > Direzione Tecnica - R&D phone: +39 02 32863 ext 1 > > v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 > > Settimo Milanese (MI), Italy > > > > > > Fact - Over 85% of viruses enter networks via e-mail. > This message has been scanned for viruses and delivered by Rockliffe MailSite. > http://www.rockliffe.com/products/av > -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Wed Jul 17 09:14:40 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15526 for ; Wed, 17 Jul 2002 09:14:40 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6HD5jt03774 for ietf-calendar-bks; Wed, 17 Jul 2002 06:05:45 -0700 (PDT) Received: from CarWash.IncentiveSystems.com (CarWash.IncentiveSystems.com [66.152.247.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g6HD5hw03770 for ; Wed, 17 Jul 2002 06:05:44 -0700 (PDT) Received: from minglewood.incentivesystems.com ([172.16.0.25]) by CarWash.IncentiveSystems.com (NAVGW 2.5.2.11) with SMTP id M2002071709111807209 for ; Wed, 17 Jul 2002 09:11:18 -0400 Received: from incentivesystems.com ([10.10.48.190]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 17 Jul 2002 09:04:15 -0400 Message-ID: <3D356B4F.8090804@incentivesystems.com> Date: Wed, 17 Jul 2002 09:04:15 -0400 From: John Stracke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Text value data type in iCal References: <000c01c22d66$b3e94ac0$8d7385d1@mars> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Jul 2002 13:04:15.0865 (UTC) FILETIME=[74406E90:01C22D92] Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Mike Hixson wrote: > Anyone know if the text value data type in iCal has been updated to > include a requirement for the equals sign to be escaped? The reason I > ask is because I don't see how to distinguish between a property that > has a structured value and one that just has a regular value -- both > of which are defined as valid TEXT types. For example: > You can't parse a property value unless you know the definition of the property. -- /========================================================\ |John Stracke |Principal Engineer | |jstracke@incentivesystems.com |Incentive Systems, Inc.| |http://www.incentivesystems.com |My opinions are my own.| |========================================================| |This is the .sig that says... Ni! | \========================================================/ From owner-ietf-calendar@mail.imc.org Wed Jul 17 12:01:54 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19956 for ; Wed, 17 Jul 2002 12:01:54 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6HFtev10273 for ietf-calendar-bks; Wed, 17 Jul 2002 08:55:40 -0700 (PDT) Received: from capricorn.iris.com (capricorn.notesdev.ibm.com [198.112.211.43]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6HFtYw10265 for ; Wed, 17 Jul 2002 08:55:39 -0700 (PDT) In-Reply-To: <004101c22d74$252393a0$8d7385d1@mars> To: "Mike Hixson" Cc: "Andrea Campi" , ietf-calendar@imc.org Subject: Re: Text value data type in iCal MIME-Version: 1.0 X-Mailer: Lotus Notes Build V60_07152002NP July 15, 2002 Message-ID: From: Bruce_Kahn@notesdev.ibm.com Date: Wed, 17 Jul 2002 11:38:50 -0400 X-MIMETrack: Serialize by Router on Capricorn/Iris(Build V60_M14_07142002 Release Candidate|July 14, 2002) at 07/17/2002 11:50:16 AM, Serialize complete at 07/17/2002 11:50:16 AM Content-Type: multipart/alternative; boundary="=_alternative 00575FA485256BF9_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 00575FA485256BF9_= Content-Type: text/plain; charset="US-ASCII" Mike Hixon replied on 07/17/2002 05:27:17 AM: > Some property values are defined in terms of multiple parts. These > structured property values MUST have their value parts separated by a > SEMICOLON character (US-ASCII decimal 59). > > This says that property *value* can be a structured value. I also found an > example of this on page 44 of iCal > RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1 > > Some properties allow a list of parameters. Each property parameter > in a list of property parameters MUST be separated by a SEMICOLON > character (US-ASCII decimal 59). > > This paragraph directly follows, which discusses list of parameters. So a > property value *can* have structured values, unless I'm not reading these > paragraphs right? They have structured data types, NOT structured TEXT. The ABNF for RRULE (Section 4.8.5.4 Recurrence Rule) defines the RRULE as: rrule = "RRULE" rrulparam ":" recur CRLF and 'recur' is defined in Section 4.3.10 Recurrence Rule and that adheres to the text you cited in Section 4.1.1. Bruce =========================================================================== Bruce Kahn INet: Bruce_Kahn@notesdev.ibm.com Messaging & Collaboration Phone: 978.399.6496 IBM Software Group FAX: and nothing but the FAX... Standard disclaimers apply, even where prohibited by law... --=_alternative 00575FA485256BF9_= Content-Type: text/html; charset="US-ASCII"
Mike Hixon replied on 07/17/2002 05:27:17 AM:
>    Some property values are defined in terms of multiple parts. These
>    structured property values MUST have their value parts separated by a
>    SEMICOLON character (US-ASCII decimal 59).
>
> This says that property *value* can be a structured value. I also found an
> example of this on page 44 of iCal
> RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1
>
>    Some properties allow a list of parameters. Each property parameter
>    in a list of property parameters MUST be separated by a SEMICOLON
>    character (US-ASCII decimal 59).
>
> This paragraph directly follows, which discusses list of parameters. So a
> property value *can* have structured values, unless I'm not reading these
> paragraphs right?
They have structured data types, NOT structured TEXT.  The ABNF for RRULE (Section 4.8.5.4 Recurrence Rule) defines the RRULE as:

     rrule      = "RRULE" rrulparam ":" recur CRLF
and 'recur' is defined in Section 4.3.10 Recurrence Rule and that adheres to the text you cited in Section 4.1.1.

Bruce
===========================================================================
Bruce Kahn                                INet: Bruce_Kahn@notesdev.ibm.com
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law... --=_alternative 00575FA485256BF9_=-- From owner-ietf-calendar@mail.imc.org Wed Jul 17 14:18:40 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25637 for ; Wed, 17 Jul 2002 14:18:39 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6HIA7C18330 for ietf-calendar-bks; Wed, 17 Jul 2002 11:10:07 -0700 (PDT) Received: from rockpub2.rockliffe.com (rockpub2.rockliffe.com [147.208.187.183]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6HIA5w18324 for ; Wed, 17 Jul 2002 11:10:05 -0700 (PDT) Received: from mars (peluzo-sdsl-141.istep.com [209.133.115.141]) by rockliffe.com (Rockliffe SMTPRA 5.2.4) with ESMTP id for ; Wed, 17 Jul 2002 11:10:10 -0700 Message-ID: <005401c22dbd$55566770$8d7385d1@mars> From: "Mike Hixson" To: References: <000c01c22d66$b3e94ac0$8d7385d1@mars> <3D356B4F.8090804@incentivesystems.com> Subject: Re: Text value data type in iCal Date: Wed, 17 Jul 2002 11:11:11 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit I was afraid of that. Well back to the drawing board :o). Thanks John. -Mike ----- Original Message ----- From: "John Stracke" To: Sent: Wednesday, July 17, 2002 6:04 AM Subject: Re: Text value data type in iCal > > Mike Hixson wrote: > > > Anyone know if the text value data type in iCal has been updated to > > include a requirement for the equals sign to be escaped? The reason I > > ask is because I don't see how to distinguish between a property that > > has a structured value and one that just has a regular value -- both > > of which are defined as valid TEXT types. For example: > > > > You can't parse a property value unless you know the definition of the > property. > > -- > /========================================================\ > |John Stracke |Principal Engineer | > |jstracke@incentivesystems.com |Incentive Systems, Inc.| > |http://www.incentivesystems.com |My opinions are my own.| > |========================================================| > |This is the .sig that says... Ni! | > \========================================================/ > > > > Fact - Over 85% of viruses enter networks via e-mail. This message has been scanned for viruses and delivered by Rockliffe MailSite. http://www.rockliffe.com/products/av From owner-ietf-calendar@mail.imc.org Wed Jul 17 14:44:11 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26498 for ; Wed, 17 Jul 2002 14:44:09 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6HIaJx20224 for ietf-calendar-bks; Wed, 17 Jul 2002 11:36:19 -0700 (PDT) Received: from CarWash.IncentiveSystems.com (CarWash.IncentiveSystems.com [66.152.247.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g6HIaIw20220 for ; Wed, 17 Jul 2002 11:36:18 -0700 (PDT) Received: from minglewood.incentivesystems.com ([172.16.0.25]) by CarWash.IncentiveSystems.com (NAVGW 2.5.2.11) with SMTP id M2002071714415421320 for ; Wed, 17 Jul 2002 14:41:54 -0400 Received: from incentivesystems.com ([10.10.48.190]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 17 Jul 2002 14:34:51 -0400 Message-ID: <3D35B8CB.2070203@incentivesystems.com> Date: Wed, 17 Jul 2002 14:34:51 -0400 From: John Stracke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Text value data type in iCal References: <000c01c22d66$b3e94ac0$8d7385d1@mars> <3D356B4F.8090804@incentivesystems.com> <005401c22dbd$55566770$8d7385d1@mars> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Jul 2002 18:34:51.0095 (UTC) FILETIME=[A2F85670:01C22DC0] Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Mike Hixson wrote: >I was afraid of that. Well back to the drawing board :o). Thanks John. > Actually, I think I spoke too soon--Bruce's post reminded me that the structured property values are typed. IIRC, what I did when I wrote a parser (about 1.5-2 years ago, I think) was to have methods for parsing each type, and a hashtable mapping properties to their default types. >>Mike Hixson wrote: >> >> >> >>>Anyone know if the text value data type in iCal has been updated to >>>include a requirement for the equals sign to be escaped? The reason I >>>ask is because I don't see how to distinguish between a property that >>>has a structured value and one that just has a regular value -- both >>>of which are defined as valid TEXT types. For example: >>> >>> >>> >>You can't parse a property value unless you know the definition of the >>property. >> > > -- /========================================================\ |John Stracke |Principal Engineer | |jstracke@incentivesystems.com |Incentive Systems, Inc.| |http://www.incentivesystems.com |My opinions are my own.| |========================================================| |This is the .sig that says... Ni! | \========================================================/ From owner-ietf-calendar@mail.imc.org Wed Jul 17 17:20:46 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00069 for ; Wed, 17 Jul 2002 17:20:45 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6HLDiH29552 for ietf-calendar-bks; Wed, 17 Jul 2002 14:13:44 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6HLDgw29547 for ; Wed, 17 Jul 2002 14:13:43 -0700 (PDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id RAA21501 for ; Wed, 17 Jul 2002 17:13:44 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id RAA00643 for ; Wed, 17 Jul 2002 17:13:44 -0400 (EDT) Received: from [66.92.67.186] (BOB.MIT.EDU [18.18.1.170]) by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id RAA28033 for ; Wed, 17 Jul 2002 17:13:43 -0400 (EDT) Mime-Version: 1.0 Message-Id: Date: Wed, 17 Jul 2002 17:13:40 -0400 To: ietf-calendar@imc.org From: Bob Mahoney Subject: Apple's "iCal"? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Does anyone know any specifics about: http://www.apple.com/ical/ "Apple redefines the desktop calendar" From owner-ietf-calendar@mail.imc.org Thu Jul 18 01:22:30 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11922 for ; Thu, 18 Jul 2002 01:22:30 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6I5FGM12232 for ietf-calendar-bks; Wed, 17 Jul 2002 22:15:16 -0700 (PDT) Received: from rockpub2.rockliffe.com (rockpub2.rockliffe.com [147.208.187.183]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6I5FEw12228 for ; Wed, 17 Jul 2002 22:15:14 -0700 (PDT) Received: from mars (peluzo-sdsl-141.istep.com [209.133.115.141]) by rockliffe.com (Rockliffe SMTPRA 5.2.4) with ESMTP id for ; Wed, 17 Jul 2002 22:15:21 -0700 Message-ID: <008001c22e1a$4206bb40$8d7385d1@mars> From: "Mike Hixson" To: References: <000c01c22d66$b3e94ac0$8d7385d1@mars> <3D356B4F.8090804@incentivesystems.com> <005401c22dbd$55566770$8d7385d1@mars> <3D35B8CB.2070203@incentivesystems.com> Subject: Re: Text value data type in iCal Date: Wed, 17 Jul 2002 22:16:22 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Thanks guys, your comments have been very helpful. Regards, Mike ----- Original Message ----- From: "John Stracke" To: Sent: Wednesday, July 17, 2002 11:34 AM Subject: Re: Text value data type in iCal > > Mike Hixson wrote: > > >I was afraid of that. Well back to the drawing board :o). Thanks John. > > > Actually, I think I spoke too soon--Bruce's post reminded me that the > structured property values are typed. IIRC, what I did when I wrote a > parser (about 1.5-2 years ago, I think) was to have methods for parsing > each type, and a hashtable mapping properties to their default types. > > >>Mike Hixson wrote: > >> > >> > >> > >>>Anyone know if the text value data type in iCal has been updated to > >>>include a requirement for the equals sign to be escaped? The reason I > >>>ask is because I don't see how to distinguish between a property that > >>>has a structured value and one that just has a regular value -- both > >>>of which are defined as valid TEXT types. For example: > >>> > >>> > >>> > >>You can't parse a property value unless you know the definition of the > >>property. > >> > > > > > > > -- > /========================================================\ > |John Stracke |Principal Engineer | > |jstracke@incentivesystems.com |Incentive Systems, Inc.| > |http://www.incentivesystems.com |My opinions are my own.| > |========================================================| > |This is the .sig that says... Ni! | > \========================================================/ > > > > Fact - Over 85% of viruses enter networks via e-mail. This message has been scanned for viruses and delivered by Rockliffe MailSite. http://www.rockliffe.com/products/av From owner-ietf-calendar@mail.imc.org Thu Jul 18 09:27:58 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02075 for ; Thu, 18 Jul 2002 09:27:58 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6IDINe03993 for ietf-calendar-bks; Thu, 18 Jul 2002 06:18:23 -0700 (PDT) Received: from CarWash.IncentiveSystems.com (CarWash.IncentiveSystems.com [66.152.247.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g6IDILw03989 for ; Thu, 18 Jul 2002 06:18:22 -0700 (PDT) Received: from minglewood.incentivesystems.com ([172.16.0.25]) by CarWash.IncentiveSystems.com (NAVGW 2.5.2.11) with SMTP id M2002071809235531243 for ; Thu, 18 Jul 2002 09:23:55 -0400 Received: from incentivesystems.com ([10.10.48.190]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 18 Jul 2002 09:16:53 -0400 Message-ID: <3D36BFC5.7090208@incentivesystems.com> Date: Thu, 18 Jul 2002 09:16:53 -0400 From: John Stracke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Apple's "iCal"? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Jul 2002 13:16:53.0312 (UTC) FILETIME=[62236C00:01C22E5D] Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Bob Mahoney wrote: > Does anyone know any specifics about: > > http://www.apple.com/ical/ Hmm: Publishing calendars on the Internet requires a .Mac membership or a WebDAV server. Sounds like they're going the Exchange route, using HTTP to push the calendar data up to a server. Probably not compatible with Exchange, or they'd say so. The big question is, are they using iCalendar, or something proprietary? -- /========================================================\ |John Stracke |Principal Engineer | |jstracke@incentivesystems.com |Incentive Systems, Inc.| |http://www.incentivesystems.com |My opinions are my own.| |========================================================| |This is the .sig that says... Ni! | \========================================================/ From owner-ietf-calendar@mail.imc.org Thu Jul 18 10:13:19 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03101 for ; Thu, 18 Jul 2002 10:13:19 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6IE5WU05112 for ietf-calendar-bks; Thu, 18 Jul 2002 07:05:32 -0700 (PDT) Received: from oe-mp1.bizmailsrvcs.net (oe-mp1pub.managedmail.com [206.46.164.22]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6IE5Vw05108 for ; Thu, 18 Jul 2002 07:05:31 -0700 (PDT) Received: from oe-ismta1.bizmailsrvcs.net ([206.46.164.26]) by oe-mp1.bizmailsrvcs.net (InterMail vM.5.01.03.15 201-253-122-118-115-20011108) with ESMTP id <20020718140527.OASD21795.oe-mp1.bizmailsrvcs.net@oe-ismta1.bizmailsrvcs.net> for ; Thu, 18 Jul 2002 09:05:27 -0500 Received: from champagned ([24.49.157.9]) by oe-ismta1.bizmailsrvcs.net (InterMail vM.5.01.03.15 201-253-122-118-115-20011108) with SMTP id <20020718140526.DVPU939.oe-ismta1.bizmailsrvcs.net@champagned> for ; Thu, 18 Jul 2002 09:05:26 -0500 Reply-To: From: "Darryl Champagne" To: Subject: RE: Apple's "iCal"? Date: Thu, 18 Jul 2002 10:07:27 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <3D36BFC5.7090208@incentivesystems.com> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit They list support for SyncML, which allows any standard type. This would boil down to using either vCal or iCal for calendar data, as those are the only two standards currently that can be certified for calendar data. Most current SyncML devices only support vCal. Which they use up to a server could be either (or proprietary, although they already must support the standard versions). dgc Darryl G. Champagne Openwave Systems Inc. Mobile Development One Burlington Woods Drive Email: Darryl.Champagne@Openwave.com Burlington, MA 01803 USA (W) +1.781.313.1361 (M) +1.781.820.2283 ------------------------------------------------------------- Privacy and Confidentiality Notice: The information contained in this electronic mail message is intended for the named recipient(s) only. It may contain privileged and confidential information. If you are not an intended recipient, you must not copy, forward, distribute, or take any action in reliance on it. If you have received this electronic mail message in error, please notify the sender immediately. ------------------------------------------------------------- -----Original Message----- From: owner-ietf-calendar@mail.imc.org [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke Sent: Thursday, July 18, 2002 9:17 AM To: ietf-calendar@imc.org Subject: Re: Apple's "iCal"? Bob Mahoney wrote: > Does anyone know any specifics about: > > http://www.apple.com/ical/ Hmm: Publishing calendars on the Internet requires a .Mac membership or a WebDAV server. Sounds like they're going the Exchange route, using HTTP to push the calendar data up to a server. Probably not compatible with Exchange, or they'd say so. The big question is, are they using iCalendar, or something proprietary? -- /========================================================\ |John Stracke |Principal Engineer | |jstracke@incentivesystems.com |Incentive Systems, Inc.| |http://www.incentivesystems.com |My opinions are my own.| |========================================================| |This is the .sig that says... Ni! | \========================================================/ From owner-ietf-calendar@mail.imc.org Thu Jul 18 11:44:29 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05573 for ; Thu, 18 Jul 2002 11:44:29 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6IFc6l09676 for ietf-calendar-bks; Thu, 18 Jul 2002 08:38:06 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6IFc5w09672 for ; Thu, 18 Jul 2002 08:38:05 -0700 (PDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id LAA26802 for ; Thu, 18 Jul 2002 11:38:06 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by grand-central-station.mit.edu (8.9.2/8.9.2) with ESMTP id LAA00396 for ; Thu, 18 Jul 2002 11:38:05 -0400 (EDT) Received: from [66.92.67.186] (airport.bobmah.com [66.92.67.186]) by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id LAA03494 for ; Thu, 18 Jul 2002 11:38:05 -0400 (EDT) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Thu, 18 Jul 2002 11:38:01 -0400 To: From: Bob Mahoney Subject: RE: Apple's "iCal"? 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've been told this morning by a Mac developer that it does indeed use iCal, but his info came from a private list, so I don't have any official word as yet. (trying...) This would obviously be a Good Thing if true. -Bob From owner-ietf-calendar@mail.imc.org Thu Jul 18 12:37:40 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07603 for ; Thu, 18 Jul 2002 12:37:40 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6IGMjr11737 for ietf-calendar-bks; Thu, 18 Jul 2002 09:22:45 -0700 (PDT) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6IGMhw11730 for ; Thu, 18 Jul 2002 09:22:43 -0700 (PDT) Received: from compaqp1000 ([213.10.149.128]) by smtp01.wxs.nl (Netscape Messaging Server 4.15) with SMTP id GZGDHM01.21B for ; Thu, 18 Jul 2002 18:22:34 +0200 Message-ID: <007701c22e77$56495e70$0200a8c0@compaqp1000> Reply-To: "ArentJan Banck" From: "ArentJan Banck" To: References: Subject: Re: Apple's "iCal"? Date: Thu, 18 Jul 2002 18:22:40 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1050 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1050 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit I did not see any reference to SyncML on the Apple page. The only talk about iSync, but the iSync page http://www.apple.com/isync/ doesn't mention compatibility with SyncML... The Ericsson T68i mentioned on the Apple site however does support SyncML, and if it uses Symbian, Symbian seems to support vCalendar. So I would expect vCal and SyncML is used for syncing, no mention of the internal format used. ArentJan ----- Original Message ----- From: "Darryl Champagne" To: Sent: Thursday, July 18, 2002 4:07 PM Subject: RE: Apple's "iCal"? > > They list support for SyncML, which allows any standard type. This would > boil down to using either vCal or iCal for calendar data, as those are the > only two standards currently that can be certified for calendar data. Most > current SyncML devices only support vCal. > > Which they use up to a server could be either (or proprietary, although they > already must support the standard versions). > > dgc > Darryl G. Champagne Openwave Systems Inc. > Mobile Development One Burlington Woods Drive > Email: Darryl.Champagne@Openwave.com Burlington, MA 01803 USA > (W) +1.781.313.1361 (M) +1.781.820.2283 > ------------------------------------------------------------- > Privacy and Confidentiality Notice: > The information contained in this electronic mail message > is intended for the named recipient(s) only. It may contain > privileged and confidential information. If you are not an > intended recipient, you must not copy, forward, distribute, > or take any action in reliance on it. If you have received > this electronic mail message in error, please notify the > sender immediately. > ------------------------------------------------------------- > > > -----Original Message----- > From: owner-ietf-calendar@mail.imc.org > [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke > Sent: Thursday, July 18, 2002 9:17 AM > To: ietf-calendar@imc.org > Subject: Re: Apple's "iCal"? > > > > Bob Mahoney wrote: > > > Does anyone know any specifics about: > > > > http://www.apple.com/ical/ > > Hmm: > > Publishing calendars on the Internet requires a .Mac > membership or a WebDAV server. > > Sounds like they're going the Exchange route, using HTTP to push the > calendar data up to a server. Probably not compatible with Exchange, or > they'd say so. The big question is, are they using iCalendar, or > something proprietary? > > -- > /========================================================\ > |John Stracke |Principal Engineer | > |jstracke@incentivesystems.com |Incentive Systems, Inc.| > |http://www.incentivesystems.com |My opinions are my own.| > |========================================================| > |This is the .sig that says... Ni! | > \========================================================/ > > > > > > From owner-ietf-calendar@mail.imc.org Thu Jul 18 14:13:04 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09559 for ; Thu, 18 Jul 2002 14:13:04 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6II3wv16782 for ietf-calendar-bks; Thu, 18 Jul 2002 11:03:58 -0700 (PDT) Received: from mail.starfish.com ([66.120.209.7]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6II3tw16777 for ; Thu, 18 Jul 2002 11:03:55 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Apple's "iCal"? Date: Thu, 18 Jul 2002 11:01:26 -0700 Message-ID: <74EF44B9E920D74F95746FBBB8017AD323AF87@mailtail.starfish.com> Thread-Topic: Apple's "iCal"? Thread-Index: AcIuel8a265Ql+DrTO6xDWsxHitnuQABqLTg From: "Peter Thompson" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id g6II3vw16778 Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8bit One of the reasons they don't mention SyncML, is that they cannot. The product has not gone through the SyncML interop testing, and hence is not legally able to mention SyncML. If they are using SyncML in the product, then I'm sure they will be bringing it to a SyncFest Real Soon Now (tm). However, I'm doubtful that they are using SyncML for the Palm, as the current Palm OBEX stack is rather broken. Cheers, Peter Thompson > -----Original Message----- > From: ArentJan Banck [mailto:spamfilter@planet.nl] > Sent: Thursday, July 18, 2002 9:23 AM > To: ietf-calendar@imc.org > Subject: Re: Apple's "iCal"? > > > > I did not see any reference to SyncML on the Apple page. The > only talk about > iSync, but the > iSync page http://www.apple.com/isync/ doesn't mention > compatibility with > SyncML... > > The Ericsson T68i mentioned on the Apple site however does > support SyncML, > and if it uses Symbian, Symbian seems to support vCalendar. > > So I would expect vCal and SyncML is used for syncing, no > mention of the > internal format used. > > ArentJan > > > ----- Original Message ----- > From: "Darryl Champagne" > To: > Sent: Thursday, July 18, 2002 4:07 PM > Subject: RE: Apple's "iCal"? > > > > > > They list support for SyncML, which allows any standard > type. This would > > boil down to using either vCal or iCal for calendar data, > as those are the > > only two standards currently that can be certified for > calendar data. > Most > > current SyncML devices only support vCal. > > > > Which they use up to a server could be either (or > proprietary, although > they > > already must support the standard versions). > > > > dgc > > Darryl G. Champagne Openwave Systems Inc. > > Mobile Development One Burlington Woods Drive > > Email: Darryl.Champagne@Openwave.com Burlington, MA 01803 USA > > (W) +1.781.313.1361 (M) +1.781.820.2283 > > ------------------------------------------------------------- > > Privacy and Confidentiality Notice: > > The information contained in this electronic mail message > > is intended for the named recipient(s) only. It may contain > > privileged and confidential information. If you are not an > > intended recipient, you must not copy, forward, distribute, > > or take any action in reliance on it. If you have received > > this electronic mail message in error, please notify the > > sender immediately. > > ------------------------------------------------------------- > > > > > > -----Original Message----- > > From: owner-ietf-calendar@mail.imc.org > > [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke > > Sent: Thursday, July 18, 2002 9:17 AM > > To: ietf-calendar@imc.org > > Subject: Re: Apple's "iCal"? > > > > > > > > Bob Mahoney wrote: > > > > > Does anyone know any specifics about: > > > > > > http://www.apple.com/ical/ > > > > Hmm: > > > > Publishing calendars on the Internet requires a .Mac > > membership or a WebDAV server. > > > > Sounds like they're going the Exchange route, using HTTP to push the > > calendar data up to a server. Probably not compatible with > Exchange, or > > they'd say so. The big question is, are they using iCalendar, or > > something proprietary? > > > > -- > > /========================================================\ > > |John Stracke |Principal Engineer | > > |jstracke@incentivesystems.com |Incentive Systems, Inc.| > > |http://www.incentivesystems.com |My opinions are my own.| > > |========================================================| > > |This is the .sig that says... Ni! | > > \========================================================/ > > > > > > > > > > > > > > From owner-ietf-calendar@mail.imc.org Thu Jul 18 15:05:37 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10730 for ; Thu, 18 Jul 2002 15:05:36 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6IIufA19853 for ietf-calendar-bks; Thu, 18 Jul 2002 11:56:41 -0700 (PDT) Received: from capricorn.iris.com (capricorn.notesdev.ibm.com [198.112.211.43]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6IIubw19849 for ; Thu, 18 Jul 2002 11:56:37 -0700 (PDT) In-Reply-To: <007701c22e77$56495e70$0200a8c0@compaqp1000> To: "ArentJan Banck" Cc: ietf-calendar@imc.org Subject: Re: Apple's "iCal"? MIME-Version: 1.0 X-Mailer: Lotus Notes Build V60_07152002NP July 15, 2002 Message-ID: From: Bruce_Kahn@notesdev.ibm.com Date: Thu, 18 Jul 2002 14:56:26 -0400 X-MIMETrack: Serialize by Router on Capricorn/Iris(Build V60_M14_07142002 Release Candidate|July 14, 2002) at 07/18/2002 02:51:07 PM, Serialize complete at 07/18/2002 02:51:07 PM Content-Type: multipart/alternative; boundary="=_alternative 0067F9E985256BFA_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0067F9E985256BFA_= Content-Type: text/plain; charset="US-ASCII" ArentJan wrote on 07/18/2002 12:22:40 PM: > The Ericsson T68i mentioned on the Apple site however does support SyncML, > and if it uses Symbian, Symbian seems to support vCalendar. > > So I would expect vCal and SyncML is used for syncing, no mention of the > internal format used. On the web page they claim "Send standards-based email event invitations" and that is only doable in iCalendar (vCalendar is "PIM only" really). Maybe we can get them to vAttend CalConnect III since they dont have to worry about anyone peeking under their kimono that way. Bruce =========================================================================== Bruce Kahn INet: Bruce_Kahn@notesdev.ibm.com Messaging & Collaboration Phone: 978.399.6496 IBM Software Group FAX: and nothing but the FAX... Standard disclaimers apply, even where prohibited by law... --=_alternative 0067F9E985256BFA_= Content-Type: text/html; charset="US-ASCII"
ArentJan wrote on 07/18/2002 12:22:40 PM:
> The Ericsson T68i mentioned on the Apple site however does support SyncML,
> and if it uses Symbian, Symbian seems to support vCalendar.
>
> So I would expect vCal and SyncML is used for syncing, no mention of the
> internal format used.
On the web page they claim "Send standards-based email event invitations" and that is only doable in iCalendar (vCalendar is "PIM only" really).  Maybe we can get them to vAttend CalConnect III since they dont have to worry about anyone peeking under their kimono that way.

Bruce
===========================================================================
Bruce Kahn                                INet: Bruce_Kahn@notesdev.ibm.com
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law... --=_alternative 0067F9E985256BFA_=-- From owner-ietf-calendar@mail.imc.org Thu Jul 18 15:07:30 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10780 for ; Thu, 18 Jul 2002 15:07:29 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6IIxnK19973 for ietf-calendar-bks; Thu, 18 Jul 2002 11:59:49 -0700 (PDT) Received: from oe-mp2.bizmailsrvcs.net (oe-mp2pub.managedmail.com [206.46.164.23]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6IIxmw19969 for ; Thu, 18 Jul 2002 11:59:48 -0700 (PDT) Received: from oe-ismta2.bizmailsrvcs.net ([206.46.164.27]) by oe-mp2.bizmailsrvcs.net (InterMail vM.5.01.03.15 201-253-122-118-115-20011108) with ESMTP id <20020718185945.ENIY21482.oe-mp2.bizmailsrvcs.net@oe-ismta2.bizmailsrvcs.net> for ; Thu, 18 Jul 2002 13:59:45 -0500 Received: from champagned ([24.49.157.9]) by oe-ismta2.bizmailsrvcs.net (InterMail vM.5.01.03.15 201-253-122-118-115-20011108) with SMTP id <20020718185931.LRXO2222.oe-ismta2.bizmailsrvcs.net@champagned> for ; Thu, 18 Jul 2002 13:59:31 -0500 Reply-To: From: "Darryl Champagne" To: Subject: RE: Apple's "iCal"? Date: Thu, 18 Jul 2002 15:01:33 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <74EF44B9E920D74F95746FBBB8017AD323AF87@mailtail.starfish.com> Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Sorry, Yes, my use of the term "list support" was incorrect. My understanding is that they _mentioned it_ in the MacWorld Address, and my understanding is that they use the SyncML protocol. http://maccentral.macworld.com/news/0207/17.keynote.php dgc Darryl G. Champagne -----Original Message----- From: owner-ietf-calendar@mail.imc.org [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of Peter Thompson Sent: Thursday, July 18, 2002 2:01 PM To: ietf-calendar@imc.org Subject: RE: Apple's "iCal"? One of the reasons they don't mention SyncML, is that they cannot. The product has not gone through the SyncML interop testing, and hence is not legally able to mention SyncML. If they are using SyncML in the product, then I'm sure they will be bringing it to a SyncFest Real Soon Now (tm). However, I'm doubtful that they are using SyncML for the Palm, as the current Palm OBEX stack is rather broken. Cheers, Peter Thompson > -----Original Message----- > From: ArentJan Banck [mailto:spamfilter@planet.nl] > Sent: Thursday, July 18, 2002 9:23 AM > To: ietf-calendar@imc.org > Subject: Re: Apple's "iCal"? > > > > I did not see any reference to SyncML on the Apple page. The > only talk about > iSync, but the > iSync page http://www.apple.com/isync/ doesn't mention > compatibility with > SyncML... > > The Ericsson T68i mentioned on the Apple site however does > support SyncML, > and if it uses Symbian, Symbian seems to support vCalendar. > > So I would expect vCal and SyncML is used for syncing, no > mention of the > internal format used. > > ArentJan > > > ----- Original Message ----- > From: "Darryl Champagne" > To: > Sent: Thursday, July 18, 2002 4:07 PM > Subject: RE: Apple's "iCal"? > > > > > > They list support for SyncML, which allows any standard > type. This would > > boil down to using either vCal or iCal for calendar data, > as those are the > > only two standards currently that can be certified for > calendar data. > Most > > current SyncML devices only support vCal. > > > > Which they use up to a server could be either (or > proprietary, although > they > > already must support the standard versions). > > > > dgc > > Darryl G. Champagne Openwave Systems Inc. > > Mobile Development One Burlington Woods Drive > > Email: Darryl.Champagne@Openwave.com Burlington, MA 01803 USA > > (W) +1.781.313.1361 (M) +1.781.820.2283 > > ------------------------------------------------------------- > > Privacy and Confidentiality Notice: > > The information contained in this electronic mail message > > is intended for the named recipient(s) only. It may contain > > privileged and confidential information. If you are not an > > intended recipient, you must not copy, forward, distribute, > > or take any action in reliance on it. If you have received > > this electronic mail message in error, please notify the > > sender immediately. > > ------------------------------------------------------------- > > > > > > -----Original Message----- > > From: owner-ietf-calendar@mail.imc.org > > [mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of John Stracke > > Sent: Thursday, July 18, 2002 9:17 AM > > To: ietf-calendar@imc.org > > Subject: Re: Apple's "iCal"? > > > > > > > > Bob Mahoney wrote: > > > > > Does anyone know any specifics about: > > > > > > http://www.apple.com/ical/ > > > > Hmm: > > > > Publishing calendars on the Internet requires a .Mac > > membership or a WebDAV server. > > > > Sounds like they're going the Exchange route, using HTTP to push the > > calendar data up to a server. Probably not compatible with > Exchange, or > > they'd say so. The big question is, are they using iCalendar, or > > something proprietary? > > > > -- > > /========================================================\ > > |John Stracke |Principal Engineer | > > |jstracke@incentivesystems.com |Incentive Systems, Inc.| > > |http://www.incentivesystems.com |My opinions are my own.| > > |========================================================| > > |This is the .sig that says... Ni! | > > \========================================================/ > > > > > > > > > > > > > > From owner-ietf-calendar@mail.imc.org Thu Jul 18 15:35:44 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11400 for ; Thu, 18 Jul 2002 15:35:44 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6IJRBY21544 for ietf-calendar-bks; Thu, 18 Jul 2002 12:27:11 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6IJRAw21540 for ; Thu, 18 Jul 2002 12:27:10 -0700 (PDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id PAA29807; Thu, 18 Jul 2002 15:27:03 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id PAA05187; Thu, 18 Jul 2002 15:27:02 -0400 (EDT) Received: from [66.92.67.186] (BOB.MIT.EDU [18.18.1.170]) by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id PAA13935; Thu, 18 Jul 2002 15:27:01 -0400 (EDT) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Thu, 18 Jul 2002 15:27:00 -0400 To: Bruce_Kahn@notesdev.ibm.com From: Bob Mahoney Subject: Re: Apple's "iCal"? Cc: "ArentJan Banck" , 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 2:56 PM -0400 7/18/02, Bruce_Kahn@notesdev.ibm.com wrote: On the web page they claim "Send standards-based email event invitations" and that is only doable in iCalendar (vCalendar is "PIM only" really). Maybe we can get them to vAttend CalConnect III since they dont have to worry about anyone peeking under their kimono that way. Our Apple rep is down in NYC, and he's going to try and chase down a definitive contact for me. I'll certainly try and interest them in CC3... :-) -Bob From owner-ietf-calendar@mail.imc.org Sat Jul 20 16:15:13 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14658 for ; Sat, 20 Jul 2002 16:15:13 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6KK2i126773 for ietf-calendar-bks; Sat, 20 Jul 2002 13:02:44 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6KK2hw26769 for ; Sat, 20 Jul 2002 13:02:43 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6KK2MM9025402 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 20 Jul 2002 13:02:34 -0700 Message-ID: <3D39BF12.90E45171@Royer.com> Date: Sat, 20 Jul 2002 13:50:42 -0600 From: Doug Royer Reply-To: ietf-calendar@imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: CAL-QUERY definition References: <20020716171417.GJ67602@inet.it> <3D3472E4.8800C360@Royer.com> <20020717080951.GA19507@inet.it> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms1B386C7F968AFA76A77CF383" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a cryptographically signed message in MIME format. --------------ms1B386C7F968AFA76A77CF383 Content-Type: multipart/mixed; boundary="------------D559B8BC6E555BABCD9F97F4" This is a multi-part message in MIME format. --------------D559B8BC6E555BABCD9F97F4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Andrea Campi wrote: > While I was writing the text below, I noticed formal definitions for > ENABLE Parameter (6.2.1) and LOCAL Parameter (6.2.2) are incorrect > (copy and past-o :-?). Also, there's a typo (Format Definition instead > of Formal) all over the draft. I just updated the draft - thanks. > Also, ALLOW-CONFLICT property doesn't specify the default in case no > ALLOW-CONFLICT is present. The ALLOW-CONFLICT property is only used in a VCALSTORE and VAGENDA and MUST BE specified once. So no default is needed. --------------D559B8BC6E555BABCD9F97F4 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------D559B8BC6E555BABCD9F97F4-- --------------ms1B386C7F968AFA76A77CF383 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIKQwYJKoZIhvcNAQcCoIIKNDCCCjACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B88wggSZMIIEAqADAgECAhA85nVyQ1LlncKock/RLC9dMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDEyMjAwMDAw MFoXDTAyMTAxMjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0B CQEWDmRvdWdAcm95ZXIuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7uTPDnj/U t/EKae6vnKPIWpCI2HoHAl3n5uSf/gIwD4Z+j3gewsR0Dm70bjAcWxwps6FNphsMUBolBwKo L73DGK8NNSz+G8fvzMrDa6SA+Pv/hv0IhkqqmCkEdgawKzzs3i3t3qQy8zOVhXNQSkhUvzlu TDNi0FS2bsCepU7hwwIDAQABo4IBODCCATQwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDAGCmCGSAGG+EUBBgcEIhYgMTgwNjlhZjY3YjMyNzNhNTAyMzQw MWRjMjU3MWY3NjQwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20v Y2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQAirjMwaw74Gbr3M61qm+BnzaNOeTMvriFN twfq1XDwgW4VBGhP1jHFL1bg6TJwEonPLJepixj0Y6/SahwkG1QUo86aCyJSyrB7qWl5q4PI XvjcGvN3jgVLlM5CYcXIyEXL9sGm8hxdxPB15yKd519QNkzNp+sd5QU8Ww5DM0AYczCCAy4w ggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYT AlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1 MTIyMzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5 L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24g Q2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVk MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xU v7zodyqdufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbaw NkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQAB o3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsG CCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYB Af8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEe kmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPH vhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWi kK5uMYICPDCCAjgCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW YWxpZGF0ZWQCEDzmdXJDUuWdwqhyT9EsL10wCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMjA3MjAxOTUwNDJaMCMGCSqGSIb3DQEJ BDEWBBTamQe4Q4iMHs4sCjYansF9RsypyDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIB KDANBgkqhkiG9w0BAQEFAASBgCh8ZkCGkYtjD1i/DeoXLPao8lZ5TtJI9C4ZOUCDr7pXqnw9 qKDFyNsA9vdSy8v0FlS14harSHr4Tgbxf9mn0TMQJnvFFwYuSq7K1S+A+qqNkmX8T6UUv+MY Nb5QX6YivmpoJemMFlotx6Lgf4f1vP80s7dIXuE6jOo+a8zxrtUc --------------ms1B386C7F968AFA76A77CF383-- From owner-ietf-calendar@mail.imc.org Sat Jul 20 16:33:13 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14912 for ; Sat, 20 Jul 2002 16:33:13 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6KKNkp27232 for ietf-calendar-bks; Sat, 20 Jul 2002 13:23:46 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6KKNjw27228 for ; Sat, 20 Jul 2002 13:23:45 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6KKNhM9025532 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 20 Jul 2002 13:23:47 -0700 Message-ID: <3D39C413.264FE4A@Royer.com> Date: Sat, 20 Jul 2002 14:12:03 -0600 From: Doug Royer Reply-To: "ietf-calendar@imc.org" Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: CAP draft typos: bibliography/references References: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms89B10C1F40677F990EF541BA" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a cryptographically signed message in MIME format. --------------ms89B10C1F40677F990EF541BA Content-Type: multipart/mixed; boundary="------------CBAB7703616F2966A7BDB1FE" This is a multi-part message in MIME format. --------------CBAB7703616F2966A7BDB1FE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "G. Barnes" wrote: Thanks - I have updated the draft. > While reading the latest CAP draft, I noticed the bibliography > didn't match completely with the references in the text. This isn't > surprising in a draft, so I did a little work which hopefully someone > can use to make the bibliography/references more useful. > > Here are my notes, which hopefully are self-explanatory: > > -------------------------------------------------------- > Text abbreviation different from bibliographic abbreviation > > In text: [BEEP] (numerous places) > In bibliography: [RFC3080] > > text: [MIME] (numerous places) > bib: [RFC2045] > > text: [BEEPTCP] (p21) > bib: [RFC3081] > > text: [SASL] (p23) > bib: [RFC2222] > > text: [SQL92] (p32) > bib: [SQL] > > text: [RFC396] (p9) > bib: [RFC2396] > Note: 2396 is correct > > -------------------------------------------------------- > in text, but not in bibliography > [GUIDE] (p5) --- I think this is RFC 3283, Guide to Internet Calendaring > [RFC2718] (p9) --- Guidelines for new URL Schemes > [RFC 2459] (p24) --- Internet X.509 Public Key Infrastructure > Certificate and CRL Profile (obsoleted by RFC3280) > [RFC 2278] (p57) --- IANA Charset Registration Procedures (obsoleted by > RFC 2978) > [RFC 2277] (p58) --- IETF Policy on Character Sets and Languages > > -------------------------------------------------------- > in bibliography, but not in text: > [RFC1521] Borenstein, N., Freed, N., "Specifying and Describing the > Format of Internet Message Bodies", RFC 1521, September 1993 > ftp://ftp.isi.edu/in-notes/rfc1521.txt > > [RFC2246] Dierks, T. and Allen, C., "The TLS Protocol Version 1.0", > RFC 2246, January 1999 > ftp://ftp.isi.edu/in-notes/rfc2246.txt > > [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource > Locators", RFC 2392, August 1998 > ftp://ftp.isi.edu/in-notes/rfc2392.txt > > [UNICODE] The Unicode Consortium, "The Unicode Standard, Version 3.1" > http://www.unicode.org/unicode/standard/standard.html > > [US-ASCII] Coded Character Set -- 7-bit American Standard Code for > Information Interchange, ANSI X3.4-1986. > > [CharEncoding] "Worldwide Character Encoding -- Version 1.0", > Addison-Wesley, Volume 1, 1991, Volume 2, 1992. > UTF-8 is described in Unicode Technical Report #4. > -------------------------------------------------------- > > Greg Barnes > Computing and Communications, University of Washington > gsbarnes@cac.washington.edu > (206) 685-3295 --------------CBAB7703616F2966A7BDB1FE Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------CBAB7703616F2966A7BDB1FE-- --------------ms89B10C1F40677F990EF541BA Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIKQwYJKoZIhvcNAQcCoIIKNDCCCjACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B88wggSZMIIEAqADAgECAhA85nVyQ1LlncKock/RLC9dMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDEyMjAwMDAw MFoXDTAyMTAxMjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0B CQEWDmRvdWdAcm95ZXIuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7uTPDnj/U t/EKae6vnKPIWpCI2HoHAl3n5uSf/gIwD4Z+j3gewsR0Dm70bjAcWxwps6FNphsMUBolBwKo L73DGK8NNSz+G8fvzMrDa6SA+Pv/hv0IhkqqmCkEdgawKzzs3i3t3qQy8zOVhXNQSkhUvzlu TDNi0FS2bsCepU7hwwIDAQABo4IBODCCATQwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDAGCmCGSAGG+EUBBgcEIhYgMTgwNjlhZjY3YjMyNzNhNTAyMzQw MWRjMjU3MWY3NjQwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20v Y2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQAirjMwaw74Gbr3M61qm+BnzaNOeTMvriFN twfq1XDwgW4VBGhP1jHFL1bg6TJwEonPLJepixj0Y6/SahwkG1QUo86aCyJSyrB7qWl5q4PI XvjcGvN3jgVLlM5CYcXIyEXL9sGm8hxdxPB15yKd519QNkzNp+sd5QU8Ww5DM0AYczCCAy4w ggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYT AlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1 MTIyMzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5 L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24g Q2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVk MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xU v7zodyqdufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbaw NkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQAB o3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsG CCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYB Af8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEe kmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPH vhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWi kK5uMYICPDCCAjgCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW YWxpZGF0ZWQCEDzmdXJDUuWdwqhyT9EsL10wCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMjA3MjAyMDEyMDNaMCMGCSqGSIb3DQEJ BDEWBBR5Q9+nA/GRw6SsmsETC900UtHfoDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIB KDANBgkqhkiG9w0BAQEFAASBgKOa5m79b6HH7FwgpxyNTkpQnn/470zg6vi4DE9WxuTvQZOl NcAaJrdqLp+H1ANSe2wKPqTy2AxYC3PwcaGlJ59i1FnnByJkuy0sBTRIpb4CVui7lczSYMiq 2SulmNOKRuYUvyu7auhKlYk2oj5fNYcYaQIvQ2yw9H9AcdIIL/cp --------------ms89B10C1F40677F990EF541BA-- From owner-ietf-calendar@mail.imc.org Sat Jul 20 16:53:36 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15166 for ; Sat, 20 Jul 2002 16:53:34 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6KKj2k27557 for ietf-calendar-bks; Sat, 20 Jul 2002 13:45:02 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6KKj1w27552 for ; Sat, 20 Jul 2002 13:45:01 -0700 (PDT) Received: from Royer.com (mail.docutechcorp.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6KKj0M9025670 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 20 Jul 2002 13:45:03 -0700 Message-ID: <3D39C910.5C771650@Royer.com> Date: Sat, 20 Jul 2002 14:33:20 -0600 From: Doug Royer Reply-To: "ietf-calendar@imc.org" Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: CREATE command definition in draft-08 References: <3D32D20D.2000902@samsungcontact.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms1E4FF48F3015D164E16978D8" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a cryptographically signed message in MIME format. --------------ms1E4FF48F3015D164E16978D8 Content-Type: multipart/mixed; boundary="------------8C61F643752E206C62B0D64D" This is a multi-part message in MIME format. --------------8C61F643752E206C62B0D64D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Davidson wrote: > > In section 9.1.4 > > create-vreply = "BEGIN" ":" "VREPLY" CRLF > created-id > request-status > *(x-prop) > "END" ":" "VREPLY" CRLF > > ; Where the id is appropriate for the > ; type of object created: > ; > ; VAGENDA = calid > ; VCAR = carid > ; VEVENT, VFREEBUSY, VJOURNAL, VTODO = uid > ; VQUERY = queryid > ; ALARM = sequence > ; x-component = x-id > ; > > I think the comments should be as I don't think you can create > ALARMS ... (by them selves - your right ). Removed from draft. > ...with CREATE, you would use MODIFY (If I am wrong about creating > ALARMS, then some different changes need to be made around what a > TARGET can be): I just removed VALARM from the 'create-reply'. Thanks! > ... > Just under that: > > created-id = ( calid / carid / uid / uid dtstamp > / queryid / tzid / sequence / x-id) > > When would "uid timestamp" be used? Is it "uid" space "timestamp"? It must be a typo - removed. > A bit further down in this section: > > create-reply = "BEGIN" ":" "VCALENDAR" CRLF > calprops > *(iana-prop) > *(x-prop) > 1*(create-comp-vreply) > "END" ":" "VCALENDAR" CRLF > > create-comp-vreply is not defined. I am also unsure of what the > restrictions table for a create reply is telling me, that the Responce: > section did not (apart from it is possible to send an iTIP response). Your right, it was in there twice - I removed the 2nd copy. > Also a small typo in the same section (page 95) > The CS would sends the REPLY in separate MIME objects, one per > TARGET. > > Should be: > The CS would send the REPLY in separate MIME objects, one per > TARGET. Fixed - thanks. --------------8C61F643752E206C62B0D64D Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------8C61F643752E206C62B0D64D-- --------------ms1E4FF48F3015D164E16978D8 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIKQwYJKoZIhvcNAQcCoIIKNDCCCjACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B88wggSZMIIEAqADAgECAhA85nVyQ1LlncKock/RLC9dMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDEyMjAwMDAw MFoXDTAyMTAxMjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0B CQEWDmRvdWdAcm95ZXIuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7uTPDnj/U t/EKae6vnKPIWpCI2HoHAl3n5uSf/gIwD4Z+j3gewsR0Dm70bjAcWxwps6FNphsMUBolBwKo L73DGK8NNSz+G8fvzMrDa6SA+Pv/hv0IhkqqmCkEdgawKzzs3i3t3qQy8zOVhXNQSkhUvzlu TDNi0FS2bsCepU7hwwIDAQABo4IBODCCATQwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDAGCmCGSAGG+EUBBgcEIhYgMTgwNjlhZjY3YjMyNzNhNTAyMzQw MWRjMjU3MWY3NjQwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20v Y2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQAirjMwaw74Gbr3M61qm+BnzaNOeTMvriFN twfq1XDwgW4VBGhP1jHFL1bg6TJwEonPLJepixj0Y6/SahwkG1QUo86aCyJSyrB7qWl5q4PI XvjcGvN3jgVLlM5CYcXIyEXL9sGm8hxdxPB15yKd519QNkzNp+sd5QU8Ww5DM0AYczCCAy4w ggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYT AlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1 MTIyMzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5 L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24g Q2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVk MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xU v7zodyqdufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbaw NkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQAB o3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsG CCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYB Af8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEe kmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPH vhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWi kK5uMYICPDCCAjgCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW YWxpZGF0ZWQCEDzmdXJDUuWdwqhyT9EsL10wCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMjA3MjAyMDMzMjBaMCMGCSqGSIb3DQEJ BDEWBBQ/MW4oLu1yJpKi7KgGh3EGfiDYETBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIB KDANBgkqhkiG9w0BAQEFAASBgFf0ypgPoGtY93zhurn8WQs8S+L6skFAJ6Qi1tZn7vdLNakD NPIG4/KhZI/N5GyqHD66loy6Lhq7bzMONMjtYQxsTPt2zJBoNX57CivTWKirV9+Vrwv4jgw2 NHnyYoRJD6RuMDkWv41qFCXsXNqm66hm0UweCgDvCOTBnwTr62Eu --------------ms1E4FF48F3015D164E16978D8-- From owner-ietf-calendar@mail.imc.org Sun Jul 21 09:46:29 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06088 for ; Sun, 21 Jul 2002 09:46:28 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6LDdQZ23467 for ietf-calendar-bks; Sun, 21 Jul 2002 06:39:26 -0700 (PDT) Received: from server1.egenconsulting.com ([208.31.106.94]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6LDdNw23463 for ; Sun, 21 Jul 2002 06:39:24 -0700 (PDT) To: ietf-calendar@imc.org Subject: Virtual Interop - September 4-5 MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: pregen@egenconsulting.com Date: Sun, 21 Jul 2002 09:39:10 -0400 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.9a |January 7, 2002) at 07/21/2002 09:39:26 AM, Serialize complete at 07/21/2002 09:39:26 AM Content-Type: multipart/alternative; boundary="=_alternative 004AFF9485256BFD_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 004AFF9485256BFD_= Content-Type: text/plain; charset="us-ascii" We've settled on the Virtual Interop dates for testing RFCs 2445, 2446, 2447. You can go to the calsch.org website and click on interoperability testing to see the details. Anyone who has not contacted Bob or myself, and who is interested in participating, should let us know. This should be an interesting adventure. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 --=_alternative 004AFF9485256BFD_= Content-Type: text/html; charset="us-ascii"
We've settled on the Virtual Interop dates for testing RFCs 2445, 2446, 2447.  You can go to the calsch.org website and click on interoperability testing to see the details.  Anyone who has not contacted Bob or myself, and who is interested in participating, should let us know.  This should be an interesting adventure.  
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652 --=_alternative 004AFF9485256BFD_=-- From owner-ietf-calendar@mail.imc.org Tue Jul 23 10:27:37 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13601 for ; Tue, 23 Jul 2002 10:27:36 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6NEGFU15941 for ietf-calendar-bks; Tue, 23 Jul 2002 07:16:15 -0700 (PDT) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6NEGEw15937 for ; Tue, 23 Jul 2002 07:16:14 -0700 (PDT) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id g6NEGFk11140 for ; Tue, 23 Jul 2002 07:16:15 -0700 (PDT) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Tue, 23 Jul 2002 07:15:23 -0700 Received: from localhost ([17.68.41.12]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id g6NEG0l15158; Tue, 23 Jul 2002 07:16:00 -0700 (PDT) Date: Tue, 23 Jul 2002 16:16:06 +0200 Subject: Re: Apple's "iCal"? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Cc: ietf-calendar@imc.org To: Bob Mahoney From: Olivier Gutknecht In-Reply-To: Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.482) Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Hello, Bob Mahoney wrote: > On the web page they claim "Send standards-based email event > invitations" and that is only doable in iCalendar (vCalendar is "PIM > only" really). Yes, Apple iCal is iCalendar based. > Maybe we can get them to vAttend CalConnect III since they dont have to > worry about anyone peeking under their kimono that way. :-) We plan to participate to standard and interoperability efforts in the future. For release schedule reasons, we don't know yet if we will be able to attend vCalConnect III. Ol. From owner-ietf-calendar@mail.imc.org Tue Jul 23 11:11:11 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16674 for ; Tue, 23 Jul 2002 11:11:10 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6NF3O117162 for ietf-calendar-bks; Tue, 23 Jul 2002 08:03:24 -0700 (PDT) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6NF3Nw17158 for ; Tue, 23 Jul 2002 08:03:23 -0700 (PDT) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id g6NF3Ok20073 for ; Tue, 23 Jul 2002 08:03:24 -0700 (PDT) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Tue, 23 Jul 2002 08:02:38 -0700 Received: from Bertrand-Guiheneufs-Computer.local. ([17.68.41.10]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id g6NF3Fl08122; Tue, 23 Jul 2002 08:03:15 -0700 (PDT) Date: Tue, 23 Jul 2002 17:03:11 +0200 Subject: Re: Apple's "iCal"? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v539) Cc: ietf-calendar@imc.org, Olivier Gutknecht To: Bob Mahoney From: Bertrand Guiheneuf In-Reply-To: Message-Id: <4DFF6F66-9E4D-11D6-B7FF-003065EFF5FA@apple.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.539) Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit also, we have to admit we put no specific efforts in ensuring perfect inter-operability in this version, but we definitely aim at being better citizens in future releases. Bertrand. On Tuesday, July 23, 2002, at 04:16 PM, Olivier Gutknecht wrote: > > Hello, > > Bob Mahoney wrote: >> On the web page they claim "Send standards-based email event >> invitations" and that is only doable in iCalendar (vCalendar is "PIM >> only" really). > > Yes, Apple iCal is iCalendar based. > >> Maybe we can get them to vAttend CalConnect III since they dont have >> to worry about anyone peeking under their kimono that way. > > :-) > We plan to participate to standard and interoperability efforts in the > future. For release schedule reasons, we don't know yet if we will be > able to attend vCalConnect III. > > Ol. > From owner-ietf-calendar@mail.imc.org Mon Jul 29 08:24:04 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26291 for ; Mon, 29 Jul 2002 08:24:03 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TC9Zb17479 for ietf-calendar-bks; Mon, 29 Jul 2002 05:09:35 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TC9Xw17475 for ; Mon, 29 Jul 2002 05:09:34 -0700 (PDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25423; Mon, 29 Jul 2002 08:08:25 -0400 (EDT) Message-Id: <200207291208.IAA25423@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-many-xcal-02.txt Date: Mon, 29 Jul 2002 08:08:25 -0400 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 : iCalendar DTD Document (xCal) Author(s) : F. Dawson Jr., S. Reddy, D. Royer, E. Plamondon Filename : draft-ietf-calsch-many-xcal-02.txt Pages : 53 Date : 26-Jul-02 This memo defines a [XML] Document Type Definition (DTD) that corresponds to the iCalendar, Internet Calendaring and Scheduling Core Object Specification defined by [RFC 2445]. This DTD provides equivalent functionality to the standard format defined by [RFC 2445]. Documents structured in accordance with this DTD may also be known as 'XML iCalendar' documents or 'xCal'. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-many-xcal-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-many-xcal-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: <20020726114205.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-calsch-many-xcal-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-calsch-many-xcal-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020726114205.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-calendar@mail.imc.org Mon Jul 29 10:47:23 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02160 for ; Mon, 29 Jul 2002 10:47:22 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TEeLj25059 for ietf-calendar-bks; Mon, 29 Jul 2002 07:40:21 -0700 (PDT) Received: from CarWash.IncentiveSystems.com (CarWash.IncentiveSystems.com [66.152.247.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g6TEeJw25055 for ; Mon, 29 Jul 2002 07:40:20 -0700 (PDT) Received: from minglewood.incentivesystems.com ([172.16.0.25]) by CarWash.IncentiveSystems.com (NAVGW 2.5.2.11) with SMTP id M2002072910464304972 for ; Mon, 29 Jul 2002 10:46:43 -0400 Received: from incentivesystems.com ([10.10.48.190]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 29 Jul 2002 10:38:30 -0400 Message-ID: <3D455366.7010203@incentivesystems.com> Date: Mon, 29 Jul 2002 10:38:30 -0400 From: John Stracke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt References: <200207291208.IAA25423@ietf.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Jul 2002 14:38:30.0305 (UTC) FILETIME=[9B848110:01C2370D] Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Internet-Drafts@ietf.org wrote: >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. > So how come it got updated when it hasn't been discussed in the WG since February? In any case, the presence of mapping tables in the draft is sufficient to demonstrate that the format specified by the draft is not isomorphic to text/calendar (the mapping tables have to be updated whenever text/calendar is extended), which means interoperability cannot be guaranteed, which means the format is a non-starter. -- /===========================================================\ |John Stracke |jstracke@centivinc.com | |Principal Engineer|http://www.centivinc.com | |Centiv |My opinions are my own. | |===========================================================| |We must be devious, cunning, inventive... too bad we're us.| \===========================================================/ From owner-ietf-calendar@mail.imc.org Mon Jul 29 11:22:35 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03719 for ; Mon, 29 Jul 2002 11:22:34 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TFGIP26159 for ietf-calendar-bks; Mon, 29 Jul 2002 08:16:18 -0700 (PDT) Received: from server1.egenconsulting.com ([208.31.106.94]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TFGFw26150 for ; Mon, 29 Jul 2002 08:16:15 -0700 (PDT) To: John Stracke Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: pregen@egenconsulting.com Date: Mon, 29 Jul 2002 11:15:57 -0400 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.9a |January 7, 2002) at 07/29/2002 11:16:17 AM, Serialize complete at 07/29/2002 11:16:17 AM Content-Type: multipart/alternative; boundary="=_alternative 0053DCCF85256C05_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0053DCCF85256C05_= Content-Type: text/plain; charset="us-ascii" I know there is another mailing list that discusses xCal. However, since this draft says - "calsch-many", John is right - it is supposed to be discussed on this list as well - particularly if something gets submitted to the IETF. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 John Stracke Sent by: owner-ietf-calendar@mail.imc.org 07/29/2002 10:38 To: ietf-calendar@imc.org cc: Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt Internet-Drafts@ietf.org wrote: >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. > So how come it got updated when it hasn't been discussed in the WG since February? In any case, the presence of mapping tables in the draft is sufficient to demonstrate that the format specified by the draft is not isomorphic to text/calendar (the mapping tables have to be updated whenever text/calendar is extended), which means interoperability cannot be guaranteed, which means the format is a non-starter. -- /===========================================================\ |John Stracke |jstracke@centivinc.com | |Principal Engineer|http://www.centivinc.com | |Centiv |My opinions are my own. | |===========================================================| |We must be devious, cunning, inventive... too bad we're us.| \===========================================================/ --=_alternative 0053DCCF85256C05_= Content-Type: text/html; charset="us-ascii"
I know there is another mailing list that discusses xCal.  However, since this draft says - "calsch-many", John is right - it is supposed to be discussed on this list as well - particularly if something gets submitted to the IETF.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


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

07/29/2002 10:38

       
        To:        ietf-calendar@imc.org
        cc:        
        Subject:        Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt




Internet-Drafts@ietf.org wrote:

>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.
>
So how come it got updated when it hasn't been discussed in the WG since
February?

In any case, the presence of mapping tables in the draft is sufficient
to demonstrate that the format specified by the draft is not isomorphic
to text/calendar (the mapping tables have to be updated whenever
text/calendar is extended), which means interoperability cannot be
guaranteed, which means the format is a non-starter.

--
/===========================================================\
|John Stracke      |jstracke@centivinc.com                  |
|Principal Engineer|http://www.centivinc.com                |
|Centiv            |My opinions are my own.                 |
|===========================================================|
|We must be devious, cunning, inventive... too bad we're us.|
\===========================================================/

--=_alternative 0053DCCF85256C05_=-- From owner-ietf-calendar@mail.imc.org Mon Jul 29 12:25:55 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06263 for ; Mon, 29 Jul 2002 12:25:55 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TGJu229164 for ietf-calendar-bks; Mon, 29 Jul 2002 09:19:56 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TGJtw29160 for ; Mon, 29 Jul 2002 09:19:55 -0700 (PDT) Received: from Royer.com (blackhole.dtdocs.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6TGJqXB020290 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 29 Jul 2002 09:19:56 -0700 Message-ID: <3D456802.D3267940@Royer.com> Date: Mon, 29 Jul 2002 10:06:26 -0600 From: Doug Royer Reply-To: owner-ietf-calendar@mail.imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt References: Content-Type: multipart/mixed; boundary="------------26B7DC79B0EB8E14110A8A18" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------26B7DC79B0EB8E14110A8A18 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit pregen@egenconsulting.com wrote: > > I know there is another mailing list that discusses xCal. However, > since this draft says - "calsch-many", John is right - it is supposed > to be discussed on this list as well - particularly if something gets > submitted to the IETF. It is not a WG submission. It does not have to be discussed on *this* list. The plan is to keep it going until we feel it is ready - then ask he WG to endorse it. I did not pick the name, I just bumped the revision :-) I have no problem with changing the name of the draft. There will probibaly be another revision out next month with an updated DTD. See: http://INET-Consulting.com/xcal-dev I noticed that Pat and Bob we on the Cc list for part of the discussion. http://INET-Consulting.com/xcal-dev/msg00129.html -Doug --------------26B7DC79B0EB8E14110A8A18 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------26B7DC79B0EB8E14110A8A18-- From owner-ietf-calendar@mail.imc.org Mon Jul 29 12:37:43 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06844 for ; Mon, 29 Jul 2002 12:37:42 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TGVx529488 for ietf-calendar-bks; Mon, 29 Jul 2002 09:31:59 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TGVww29484 for ; Mon, 29 Jul 2002 09:31:58 -0700 (PDT) Received: from Royer.com (blackhole.dtdocs.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6TGVvXB020419 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 29 Jul 2002 09:31:59 -0700 Message-ID: <3D456AD8.4800F149@Royer.com> Date: Mon, 29 Jul 2002 10:18:32 -0600 From: Doug Royer Reply-To: owner-ietf-calendar@mail.imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt References: Content-Type: multipart/mixed; boundary="------------FF278A27E0CF36899DAB48FE" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------FF278A27E0CF36899DAB48FE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit pregen@egenconsulting.com wrote: > > I know there is another mailing list that discusses xCal. However, > since this draft says - "calsch-many", John is right - it is supposed > to be discussed on this list as well - particularly if something gets > submitted to the IETF. It is not a WG submission. It does not have to be discussed on this list. The plan is to keep it going until we feel it is ready - then ask he WG to endorse it. I did not pick the name, I just bumped the revision :-) I have no problem with changing the name of the draft. There will probably be another revision out next month with an updated DTD that Eric, Frank, and I have been working on (Surendra is on a leave of absence until fall). See: http://INET-Consulting.com/xcal-dev Feel free to join the list, however it is not a CALSCH WG list. It is used by the authors of the draft to communicate and it is open and public. The purpose of the list is for those interested in a 1:1 mapping between XML-iCal and iCal. Some non-1:1 mapping is in the draft and we are working to remove those from the DTD. However the submission is supposed to be at this time, an individual submission. To join the list: xcal-dev-request@inet-consulting.com -Doug --------------FF278A27E0CF36899DAB48FE Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------FF278A27E0CF36899DAB48FE-- From owner-ietf-calendar@mail.imc.org Mon Jul 29 13:00:00 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07402 for ; Mon, 29 Jul 2002 12:59:59 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6TGrfD01816 for ietf-calendar-bks; Mon, 29 Jul 2002 09:53:41 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TGrew01810 for ; Mon, 29 Jul 2002 09:53:40 -0700 (PDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id MAA02077 for ; Mon, 29 Jul 2002 12:53:41 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id MAA17853 for ; Mon, 29 Jul 2002 12:53:41 -0400 (EDT) Received: from [66.92.67.186] (airport.bobmah.com [66.92.67.186]) by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id MAA27215 for ; Mon, 29 Jul 2002 12:53:40 -0400 (EDT) Mime-Version: 1.0 X-Sender: bobmah@po12.mit.edu Message-Id: In-Reply-To: <3D456AD8.4800F149@Royer.com> References: <3D456AD8.4800F149@Royer.com> Date: Mon, 29 Jul 2002 12:55:13 -0400 To: ietf-calendar@mail.imc.org From: Bob Mahoney Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt 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:18 AM -0600 7/29/02, Doug Royer wrote: > >It is not a WG submission. It does not have to be discussed >on this list. The plan is to keep it going until we feel >it is ready - then ask he WG to endorse it. A couple of small points: In the current form, this is a revision of a WG draft. The intent of the chairs was that a subset of interested and motivated folks work on the xcal issues, and come pack with one or more proposals for consider by the WG. (essentially as a "design team" for these issues) We encourage everyone with an interest to participate in these side discussions. Renaming the draft to whatever that group might feel best suits their discussions is appropriate. Please understand that the current title implies some process-related meaning that is not quite accurate at the moment. The xcal work will certainly remain an interest of the WG, and even as an individual draft would probably be funneled back this way by the ADs as it matures. We need to retain a sense of the -01 version of this title, as that is the "official" WG state. This (probably quite obsolete) -01 draft will be what we revise, based on the xcal group's work and the sense at that time of the WG. The chairs will work to combat confusion so that when we bring the design team's work back in for general discussion, we aren't too much more befuddled than usual... The overall hope is that those most interested in this draft ,and related subjects, can hash out some of the issues off to one side, and later present the WG with a more mature/finished/whatever treatment, which will ease the search for consensus. -Bob From owner-ietf-calendar@mail.imc.org Mon Jul 29 13:05:48 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07598 for ; Mon, 29 Jul 2002 13:05:47 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TGxOQ02607 for ietf-calendar-bks; Mon, 29 Jul 2002 09:59:24 -0700 (PDT) Received: from server1.egenconsulting.com ([208.31.106.94]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TGxLw02594 for ; Mon, 29 Jul 2002 09:59:21 -0700 (PDT) To: owner-ietf-calendar@mail.imc.org Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: pregen@egenconsulting.com Date: Mon, 29 Jul 2002 12:59:17 -0400 X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.9a |January 7, 2002) at 07/29/2002 12:59:24 PM Content-Type: multipart/mixed; boundary="=_mixed 005D51EE85256C05_=" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --=_mixed 005D51EE85256C05_= Content-Type: multipart/alternative; boundary="=_alternative 005D51EE85256C05_=" --=_alternative 005D51EE85256C05_= Content-Type: text/plain; charset="us-ascii" If this is going to be discussed on another list, then the name has to be changed. If it pertains to iCalendar work, though, then dialog should be discussed on this list so vendors are aware of what is going on and what may impact iCalendar implementations. ___________________ Patricia Egen Consulting www.egenconsulting.com 423-875-2652 Doug Royer Sent by: owner-ietf-calendar@mail.imc.org 07/29/2002 12:06 Please respond to owner-ietf-calendar To: ietf-calendar@imc.org cc: Subject: Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt pregen@egenconsulting.com wrote: > > I know there is another mailing list that discusses xCal. However, > since this draft says - "calsch-many", John is right - it is supposed > to be discussed on this list as well - particularly if something gets > submitted to the IETF. It is not a WG submission. It does not have to be discussed on *this* list. The plan is to keep it going until we feel it is ready - then ask he WG to endorse it. I did not pick the name, I just bumped the revision :-) I have no problem with changing the name of the draft. There will probibaly be another revision out next month with an updated DTD. See: http://INET-Consulting.com/xcal-dev I noticed that Pat and Bob we on the Cc list for part of the discussion. http://INET-Consulting.com/xcal-dev/msg00129.html -Doug --=_alternative 005D51EE85256C05_= Content-Type: text/html; charset="us-ascii"
If this is going to be discussed on another list, then the name has to be changed.  If it pertains to iCalendar work, though, then dialog should be discussed on this list so vendors are aware of what is going on and what may impact iCalendar implementations.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


Doug Royer <Doug@royer.com>
Sent by: owner-ietf-calendar@mail.imc.org

07/29/2002 12:06
Please respond to owner-ietf-calendar

       
        To:        ietf-calendar@imc.org
        cc:        
        Subject:        Re: I-D ACTION:draft-ietf-calsch-many-xcal-02.txt



pregen@egenconsulting.com wrote:
>
> I know there is another mailing list that discusses xCal.  However,
> since this draft says - "calsch-many", John is right - it is supposed
> to be discussed on this list as well - particularly if something gets
> submitted to the IETF.

It is not a WG submission. It does not have to be discussed
on *this* list. The plan is to keep it going until we feel
it is ready - then ask he WG to endorse it.

I did not pick the name, I just bumped the revision :-)
I have no problem with changing the name of the draft.

There will probibaly be another revision out next month
with an updated DTD.

See:

                http://INET-Consulting.com/xcal-dev

I noticed that Pat and Bob we on the Cc list for part
of the discussion.

                http://INET-Consulting.com/xcal-dev/msg00129.html

-Doug

--=_alternative 005D51EE85256C05_=-- --=_mixed 005D51EE85256C05_= Content-Type: application/octet-stream; name="Doug.vcf" Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 YmVnaW46dmNhcmQgDQpuOlJveWVyO0RvdWcNCnRlbDtwYWdlcjpwYWdlckBSb3llci5jb20NCnRl bDtjZWxsOjIwOC01MjAtNDA0NA0KdGVsO2ZheDo4NjYtNTk0LTg1NzQNCnRlbDt3b3JrOjg2Ni01 OTQtODU3NA0KeC1tb3ppbGxhLWh0bWw6RkFMU0UNCnVybDpodHRwOi8vUm95ZXIuY29tL1Blb3Bs ZS9Eb3VnDQpvcmc6aHR0cDovL0lORVQtQ29uc3VsdGluZy5jb20NCmFkcjo7OzE3OTUgVy4gQnJv YWR3YXkgIzI2NjtJZGFobyBGYWxscztJZGFobzs4MzQwMjtVLlMuQS4NCnZlcnNpb246Mi4xDQpl bWFpbDtpbnRlcm5ldDpEb3VnQFJveWVyLmNvbQ0KdGl0bGU6Q2hpZWYgRXhlY3V0aXZlIE1hbmFn ZXINCngtbW96aWxsYS1jcHQ6OzEyNzA0DQpmbjpEb3VnIFJveWVyDQplbmQ6dmNhcmQNCg== --=_mixed 005D51EE85256C05_=-- From owner-ietf-calendar@mail.imc.org Mon Jul 29 14:23:20 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09695 for ; Mon, 29 Jul 2002 14:23:20 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TIGeg10192 for ietf-calendar-bks; Mon, 29 Jul 2002 11:16:40 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TIGdw10187 for ; Mon, 29 Jul 2002 11:16:40 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 7D38115510; Mon, 29 Jul 2002 20:16:40 +0200 (CEST) Date: Mon, 29 Jul 2002 20:16:40 +0200 From: Andrea Campi To: ietf-calendar@imc.org Subject: Question about iTIP + VCARs Message-ID: <20020729181640.GA31142@inet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I think I need some help, as some things don't make much sense to me; I guess I'm missing something. The CREATE command stores iTIP objects, which may or may not contain a METHOD property; this is quite clear. So I would expect something like: C: Content-Type: text/calendar C: C: BEGIN:VCALENDAR C: VERSION:2.0 C: CMD;ID=creation02:CREATE C: TARGET:relcalz1 C: BEGIN:VEVENT C: DTSTART:99990307T180000Z C: METHOD:REQUEST C: UID:abcd12345 C: DTEND:99990307T190000Z C: SUMMARY:Important Meeting C: END:VEVENT C: BEGIN:VEVENT C: DTSTART:99990307T190000Z C: METHOD:REQUEST C: UID:abcd12346 C: DTEND:99990307T193000Z C: SUMMARY:Dinner C: END:VEVENT C: END:VCALENDAR However, the only example containing a METHOD shows the METHOD request in the VCALENDAR. Is this the only way, the preferred way, or it's just the same? And what happens when a VCALENDAR with a METHOD property contains >1 component, do they all take on the same METHOD (I guess so)? Can they override it? Regardless of the exact semantics of this, I expect the result to be the same; that is, the contained objects will be stored in the target with the appropriate METHOD (and state). So, my real question is (looking at 4.2.3 Predefined VCARs): BEGIN:VCAR CARID:REQUESTONLY BEGIN:VRIGHT GRANT:NONOWNER PERMISSION:WRITE RESTRICTION:SELECT * FROM VCALENDAR WHERE METHOD = 'REQUEST' END:VRIGHT END:VCAR Does this make sense? What would it return? Looking at 6.1.1, VCALENDAR is not in comp-name, so I think it's wrong. Even if it was right, isn't the METHOD property referring to any component found? In this case, this would violate rule 4 in 6.1.1, as the WHERE clause refers to a property of a component which is not in the FROM. Should this be written as: BEGIN:VCAR CARID:REQUESTONLY BEGIN:VRIGHT GRANT:NONOWNER PERMISSION:WRITE RESTRICTION:SELECT * FROM VEVENT WHERE METHOD = 'REQUEST' RESTRICTION:SELECT * FROM VTODO WHERE METHOD = 'REQUEST' RESTRICTION:SELECT * FROM VJOURNAL WHERE METHOD = 'REQUEST' END:VRIGHT END:VCAR Bye, Andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Mon Jul 29 16:57:54 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14617 for ; Mon, 29 Jul 2002 16:57:53 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6TKrda20501 for ietf-calendar-bks; Mon, 29 Jul 2002 13:53:39 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6TKrcw20497 for ; Mon, 29 Jul 2002 13:53:38 -0700 (PDT) Received: from Royer.com (blackhole.dtdocs.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6TKraXB022159 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 29 Jul 2002 13:53:40 -0700 Message-ID: <3D45A828.AA7EE885@Royer.com> Date: Mon, 29 Jul 2002 14:40:08 -0600 From: Doug Royer Reply-To: ietf-calendar@imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: Question about iTIP + VCARs References: <20020729181640.GA31142@inet.it> Content-Type: multipart/mixed; boundary="------------765A75AD1F6DEC73906B9CE7" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------765A75AD1F6DEC73906B9CE7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Andrea Campi wrote: > > Hi all, > > I think I need some help, as some things don't make much sense to me; > I guess I'm missing something. > > The CREATE command stores iTIP objects, which may or may not contain > a METHOD property; this is quite clear. So I would expect something > like: The CREATE command stores iCalendar objects, some of which are iTIP objects. iTIP objects are identifyabl as they contain a METHOD property. > ... > > However, the only example containing a METHOD shows the METHOD > request in the VCALENDAR. Is this the only way, the preferred way, > or it's just the same? I don't understand the question. > And what happens when a VCALENDAR with a METHOD property > contains > 1 component, do they all take on the same METHOD (I guess so)? iCalendar objects are MIME objects. And all objects in the same MIME object MUST have the same METHOD. > Can they override it? No. > Regardless of the exact semantics of this, > I expect the result to be the same; that is, the contained objects > will be stored in the target with the appropriate METHOD (and state). Yes. > > Should this be written as: > > BEGIN:VCAR > CARID:REQUESTONLY > BEGIN:VRIGHT > GRANT:NONOWNER > PERMISSION:WRITE > RESTRICTION:SELECT * FROM VEVENT WHERE METHOD = 'REQUEST' > RESTRICTION:SELECT * FROM VTODO WHERE METHOD = 'REQUEST' > RESTRICTION:SELECT * FROM VJOURNAL WHERE METHOD = 'REQUEST' > END:VRIGHT > END:VCAR Yes - thanks! --------------765A75AD1F6DEC73906B9CE7 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------765A75AD1F6DEC73906B9CE7-- From owner-ietf-calendar@mail.imc.org Mon Jul 29 17:51:39 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16296 for ; Mon, 29 Jul 2002 17:51:38 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6TLjiV22082 for ietf-calendar-bks; Mon, 29 Jul 2002 14:45:44 -0700 (PDT) Received: from CarWash.IncentiveSystems.com (CarWash.IncentiveSystems.com [66.152.247.41]) by above.proper.com (8.11.6/8.11.3) with SMTP id g6TLjgw22077 for ; Mon, 29 Jul 2002 14:45:42 -0700 (PDT) Received: from minglewood.incentivesystems.com ([172.16.0.25]) by CarWash.IncentiveSystems.com (NAVGW 2.5.2.11) with SMTP id M2002072917522602812 for ; Mon, 29 Jul 2002 17:52:26 -0400 Received: from centivinc.com ([10.10.48.190]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 29 Jul 2002 17:44:13 -0400 Message-ID: <3D45B72D.8000507@centivinc.com> Date: Mon, 29 Jul 2002 17:44:13 -0400 From: John Stracke Organization: Centiv User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-calendar@imc.org Subject: Re: Question about iTIP + VCARs References: <20020729181640.GA31142@inet.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Jul 2002 21:44:13.0232 (UTC) FILETIME=[1449DB00:01C23749] Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Andrea Campi wrote: >However, the only example containing a METHOD shows the METHOD >request in the VCALENDAR. Is this the only way, the preferred way, >or it's just the same? > The only way. See the ABNF in RFC-2445, section 4.6 (and the "Conformance:" text in section 4.7.2). -- /===========================================================\ |John Stracke |jstracke@centivinc.com | |Principal Engineer|http://www.centivinc.com | |Centiv |My opinions are my own. | |===========================================================| |We must be devious, cunning, inventive... too bad we're us.| \===========================================================/ From owner-ietf-calendar@mail.imc.org Tue Jul 30 05:47:59 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10436 for ; Tue, 30 Jul 2002 05:47:58 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g6U9bgc07203 for ietf-calendar-bks; Tue, 30 Jul 2002 02:37:42 -0700 (PDT) Received: from acampi.inet.it ([213.92.1.165]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6U9bfw07199 for ; Tue, 30 Jul 2002 02:37:41 -0700 (PDT) Received: by acampi.inet.it (Postfix, from userid 210) id 2615015510; Tue, 30 Jul 2002 11:37:40 +0200 (CEST) Date: Tue, 30 Jul 2002 11:37:40 +0200 From: Andrea Campi To: ietf-calendar@imc.org Subject: Re: Question about iTIP + VCARs Message-ID: <20020730093740.GA33124@inet.it> References: <20020729181640.GA31142@inet.it> <3D45A828.AA7EE885@Royer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D45A828.AA7EE885@Royer.com> Organization: I.NET S.p.A. User-Agent: Mutt/1.5.1i Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Mon, Jul 29, 2002 at 02:40:08PM -0600, Doug Royer wrote: > The CREATE command stores iCalendar objects, some of which > are iTIP objects. iTIP objects are identifyabl as they > contain a METHOD property. [...] Thanks, the answers I got helped me get a better understanding, now it's clear. > > Regardless of the exact semantics of this, > > I expect the result to be the same; that is, the contained objects > > will be stored in the target with the appropriate METHOD (and state). > > Yes. Uhm, what I said is probably not correct - the individual objects (VEVENT etc) are going to be store without a METHOD property, but with some kind of "metadata" to keep the state. Right? > > > > Should this be written as: > > > > BEGIN:VCAR > > CARID:REQUESTONLY > > BEGIN:VRIGHT > > GRANT:NONOWNER > > PERMISSION:WRITE > > RESTRICTION:SELECT * FROM VEVENT WHERE METHOD = 'REQUEST' > > RESTRICTION:SELECT * FROM VTODO WHERE METHOD = 'REQUEST' > > RESTRICTION:SELECT * FROM VJOURNAL WHERE METHOD = 'REQUEST' > > END:VRIGHT > > END:VCAR > > Yes - thanks! Ok, so it wasn't me! ;-) Bye, andrea -- Andrea Campi mailto:a.campi@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - R&D phone: +39 02 32863 ext 1 v. Darwin, 85 - I-20019 fax: +39 02 32863 ext 7705 Settimo Milanese (MI), Italy From owner-ietf-calendar@mail.imc.org Tue Jul 30 11:19:22 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23163 for ; Tue, 30 Jul 2002 11:19:21 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6UF6iF27478 for ietf-calendar-bks; Tue, 30 Jul 2002 08:06:44 -0700 (PDT) Received: from royer.com (royer.com [4.23.9.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6UF6hw27474 for ; Tue, 30 Jul 2002 08:06:43 -0700 (PDT) Received: from Royer.com (blackhole.dtdocs.com [12.23.70.30]) by royer.com (8.12.2/8.12.2) with ESMTP id g6UF6gXB030888 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 30 Jul 2002 08:06:45 -0700 Message-ID: <3D46A852.CC144DEC@Royer.com> Date: Tue, 30 Jul 2002 08:53:06 -0600 From: Doug Royer Reply-To: ietf-calendar@imc.org Organization: http://INET-Consulting.com X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "ietf-calendar@imc.org" Subject: Re: Question about iTIP + VCARs References: <20020729181640.GA31142@inet.it> <3D45A828.AA7EE885@Royer.com> <20020730093740.GA33124@inet.it> Content-Type: multipart/mixed; boundary="------------76BFE74545D5BA614A91546D" Sender: owner-ietf-calendar@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------76BFE74545D5BA614A91546D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > > Regardless of the exact semantics of this, > > > I expect the result to be the same; that is, the contained objects > > > will be stored in the target with the appropriate METHOD (and state). > > > > Yes. > > Uhm, what I said is probably not correct - the individual objects > (VEVENT etc) are going to be store without a METHOD property, but > with some kind of "metadata" to keep the state. Right? The CS can store them any way the implementation wishes. It is independent of the CAP protocol. Some implementations may use the METHOD property, others may use some other metadata. --------------76BFE74545D5BA614A91546D Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:http://INET-Consulting.com adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;12704 fn:Doug Royer end:vcard --------------76BFE74545D5BA614A91546D--