From owner-ietf-calendar@mail.imc.org  Tue Jul  1 12:58:26 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07072
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 12:58:25 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61GkQFK068174
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 09:46:26 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h61GkQG9068173
	for ietf-calendar-bks; Tue, 1 Jul 2003 09:46:26 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61GkOFK068167
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 09:46:24 -0700 (PDT)
	(envelope-from satyanarayana.vempati@Sun.COM)
Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42])
	by nwkea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h61GkLfU010921
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 09:46:21 -0700 (PDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail2sca.sfbay.sun.com (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h61GkLaJ001414
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 09:46:21 -0700 (PDT)
Received: from pranav.red.iplanet.com (pranav.red.iplanet.com [192.18.144.109])
 by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HHC00CYVUL80Z@ha13sca-mail1.sfbay.sun.com> for
 ietf-calendar@imc.org; Tue, 01 Jul 2003 09:46:20 -0700 (PDT)
Date: Tue, 01 Jul 2003 09:46:20 -0700
From: Satya Vempati <satyanarayana.vempati@sun.com>
Subject: RE: CAP draft - last call, etc.
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_4_.20030701094620.2036H@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_n28sl2MaCS+gj6/yHeOLjA)"; DIFFERENCES=Content-Language
Content-language: en-USA
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



--Boundary_(ID_n28sl2MaCS+gj6/yHeOLjA)
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

Some of the iCAL/iTIP questions will impact the decisions on CAP.
Especially, the outcome of the discussion on RECURRENCE-ID fundamentally
affects the CAP spec based on how it is eventually resolved.

IMHO, one final draft (hopefully 11) to iron out the differences is
required before going to RFC.

-----Original Message-----



From: Doug Royer [mailto:Doug@royer.com]
Sent: Monday, June 30, 2003 8:19 PM
To: ietf-calendar@imc.org
Subject: Re: CAP draft - last call, etc.




Items that will be changed in the -11 version of the draft.

(1) Sorting is out per this WG. (I submitted my own add on draft).
(2) The ABNF will be fixed per the email on this WG.
(3) Various typos sent to me and this list.
(4) CS to generate FREEBUSY data (NOT CUA).

As of the San Francisco IETF meeting (-10 release) there have been no
other new CAP issues that seem to have reach consensus. The only
new issue seems to be if TARGET will default and I did not think
that made it past a couple of questions and opinions sent to the list.

Unless I missed something, all of the other issues are
all iCal/iTIP/iMIP issues.

PLEASE SPEAK UP if you think that something else should make the -11
version of the draft - I AM EDITING IT NOW.

Still To do:

(I) Beep profile.
(II) Document the 1:1 or 1:MANY replies.

Item (II) was discussed in S.F. and the thoughts were that
you would bundle all single TARGET replies in one blob,
and for each unique TARGET in the CS reply, the CS would
send another blob of data.

pregen@egenconsulting.com wrote:
> 
> Well, there's been a lot of traffic going on about all sort of issues 
> and topics.  However, it came to a halt when one note came up with what 
> may be a "show-stopper."  So, I think we need to make a decision here. 
>  Do we take items that are too hard to fix, remove them, and put in an 
> addendum that says "the following items need to be resolved in the next 
> version"?  Or do we try to take a stab at fixing them.  We need to get a 
> version of CAP into RFC status.  We need to get people interoperating so 
> we can see what's really working and what's really hosed badly.  I asked 
> for a last call and that didn't work.  We really do need to get this out 
> the door.  Therefore, I'm once again asking for a last hard look at what 
> can stay and what needs to go in the current CAP draft.  If it's broken 
> and needs a lot of work - it goes out.  I am going to go back over the 
> last year's thr! eads and see what I can determine are the big issues. 
>  I'll post a note to the list with the items and will ask for a "hm" 
> from the list as to whether the item stays or goes.  If it goes, we'll 
> need help changing the draft to remove all text regarding that topic.
> 
> If you disagree with the items I post - say so.  If you agree with the 
> items - say so.  That way I know people are reading the list and will 
> agree with what we produce as the final draft.  
> 
> Cool?
> ___________________
> Patricia Egen Consulting
> www.egenconsulting.com
> 423-875-2652


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--Boundary_(ID_n28sl2MaCS+gj6/yHeOLjA)
Content-id: 0
Content-type: TEXT/html; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

<html><head></head><body>
<font size=2 >Some of the iCAL/iTIP questions will impact the decisions on
CAP. Especially, the outcome of the discussion on RECURRENCE-ID
fundamentally affects the CAP spec based on how it is eventually
resolved.</font><div>
<font size=2 ></font><div>
<font size=2 >IMHO, one final draft (hopefully 11) to iron out the
differences is required before going to RFC.</font><div>
<font size=2 ></font><div>
<font size=2 >-----Original Message-----</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >From: Doug Royer [mailto:Doug@royer.com]</font><div>
<font size=2 >Sent: Monday, June 30, 2003 8:19 PM</font><div>
<font size=2 >To: ietf-calendar@imc.org</font><div>
<font size=2 >Subject: Re: CAP draft - last call, etc.</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >Items that will be changed in the -11 version of the
draft.</font><div>
<font size=2 ></font><div>
<font size=2 >(1) Sorting is out per this WG. (I submitted my own add on
draft).</font><div>
<font size=2 >(2) The ABNF will be fixed per the email on this
WG.</font><div>
<font size=2 >(3) Various typos sent to me and this list.</font><div>
<font size=2 >(4) CS to generate FREEBUSY data (NOT CUA).</font><div>
<font size=2 ></font><div>
<font size=2 >As of the San Francisco IETF meeting (-10 release) there
have been no</font><div>
<font size=2 >other new CAP issues that seem to have reach consensus. The
only</font><div>
<font size=2 >new issue seems to be if TARGET will default and I did not
think</font><div>
<font size=2 >that made it past a couple of questions and opinions sent to
the list.</font><div>
<font size=2 ></font><div>
<font size=2 >Unless I missed something, all of the other issues
are</font><div>
<font size=2 >all iCal/iTIP/iMIP issues.</font><div>
<font size=2 ></font><div>
<font size=2 >PLEASE SPEAK UP if you think that something else should make
the -11</font><div>
<font size=2 >version of the draft - I AM EDITING IT NOW.</font><div>
<font size=2 ></font><div>
<font size=2 >Still To do:</font><div>
<font size=2 ></font><div>
<font size=2 >(I) Beep profile.</font><div>
<font size=2 >(II) Document the 1:1 or 1:MANY replies.</font><div>
<font size=2 ></font><div>
<font size=2 >Item (II) was discussed in S.F. and the thoughts were
that</font><div>
<font size=2 >you would bundle all single TARGET replies in one
blob,</font><div>
<font size=2 >and for each unique TARGET in the CS reply, the CS
would</font><div>
<font size=2 >send another blob of data.</font><div>
<font size=2 ></font><div>
<font size=2 >pregen@egenconsulting.com wrote:</font><div>
<font size=2 >&gt; </font><div>
<font size=2 >&gt; Well, there's been a lot of traffic going on about all
sort of issues </font><div>
<font size=2 >&gt; and topics.  However, it came to a halt when one note
came up with what </font><div>
<font size=2 >&gt; may be a "show-stopper."  So, I think we need to make a
decision here. </font><div>
<font size=2 >&gt;  Do we take items that are too hard to fix, remove
them, and put in an </font><div>
<font size=2 >&gt; addendum that says "the following items need to be
resolved in the next </font><div>
<font size=2 >&gt; version"?  Or do we try to take a stab at fixing them. 
We need to get a </font><div>
<font size=2 >&gt; version of CAP into RFC status.  We need to get people
interoperating so </font><div>
<font size=2 >&gt; we can see what's really working and what's really
hosed badly.  I asked </font><div>
<font size=2 >&gt; for a last call and that didn't work.  We really do
need to get this out </font><div>
<font size=2 >&gt; the door.  Therefore, I'm once again asking for a last
hard look at what </font><div>
<font size=2 >&gt; can stay and what needs to go in the current CAP draft.
 If it's broken </font><div>
<font size=2 >&gt; and needs a lot of work - it goes out.  I am going to
go back over the </font><div>
<font size=2 >&gt; last year's thr! eads and see what I can determine are
the big issues. </font><div>
<font size=2 >&gt;  I'll post a note to the list with the items and will
ask for a "hm" </font><div>
<font size=2 >&gt; from the list as to whether the item stays or goes.  If
it goes, we'll </font><div>
<font size=2 >&gt; need help changing the draft to remove all text
regarding that topic.</font><div>
<font size=2 >&gt; </font><div>
<font size=2 >&gt; If you disagree with the items I post - say so.  If you
agree with the </font><div>
<font size=2 >&gt; items - say so.  That way I know people are reading the
list and will </font><div>
<font size=2 >&gt; agree with what we produce as the final draft. 
</font><div>
<font size=2 >&gt; </font><div>
<font size=2 >&gt; Cool?</font><div>
<font size=2 >&gt; ___________________</font><div>
<font size=2 >&gt; Patricia Egen Consulting</font><div>
<font size=2 >&gt; www.egenconsulting.com</font><div>
<font size=2 >&gt; 423-875-2652</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >-- </font><div>
<font size=2 ></font><div>
<font size=2 >  Doug Royer                     |  
http://INET-Consulting.com</font><div>
<font size=2 > 
-------------------------------|-----------------------------</font><div>
<font size=2 >  Doug@Royer.com                 | Office:
(208)612-INET</font><div>
<font size=2 >  http://Royer.com/People/Doug   |    Fax:
(866)594-8574</font><div>
<font size=2 >                                 |   Cell:
(208)520-4044</font><div>
<font size=2 ></font><div>
<font size=2 >                 We Do Standards - You Need
Standards</font><div>
<font ></font></body></html>

--Boundary_(ID_n28sl2MaCS+gj6/yHeOLjA)--


From owner-ietf-calendar@mail.imc.org  Tue Jul  1 13:29:09 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07555
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 13:29:08 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61HL8FK069500
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 10:21:08 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h61HL76R069499
	for ietf-calendar-bks; Tue, 1 Jul 2003 10:21:07 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61HL5FK069488
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 10:21:05 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: ietf-calendar@imc.org
Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
Subject: Re: CAP draft - last call, etc.
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFCA5A59A1.BFE61A76-ON85256D56.005F4D93-85256D56.005F50ED@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Tue, 1 Jul 2003 13:21:06 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/01/2003 01:21:07 PM,
	Serialize complete at 07/01/2003 01:21:07 PM
Content-Type: multipart/alternative; boundary="=_alternative 005F50E485256D56_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 005F50E485256D56_=
Content-Type: text/plain; charset="us-ascii"

What about the scoping issue?
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




Doug Royer <Doug@royer.com>
Sent by: owner-ietf-calendar@mail.imc.org
06/30/2003 23:18
Please respond to ietf-calendar

 
        To:     ietf-calendar@imc.org
        cc: 
        Subject:        Re: CAP draft - last call, etc.




Items that will be changed in the -11 version of the draft.

(1) Sorting is out per this WG. (I submitted my own add on draft).
(2) The ABNF will be fixed per the email on this WG.
(3) Various typos sent to me and this list.
(4) CS to generate FREEBUSY data (NOT CUA).

As of the San Francisco IETF meeting (-10 release) there have been no
other new CAP issues that seem to have reach consensus. The only
new issue seems to be if TARGET will default and I did not think
that made it past a couple of questions and opinions sent to the list.

Unless I missed something, all of the other issues are
all iCal/iTIP/iMIP issues.

PLEASE SPEAK UP if you think that something else should make the -11
version of the draft - I AM EDITING IT NOW.

Still To do:

(I) Beep profile.
(II) Document the 1:1 or 1:MANY replies.

Item (II) was discussed in S.F. and the thoughts were that
you would bundle all single TARGET replies in one blob,
and for each unique TARGET in the CS reply, the CS would
send another blob of data.

pregen@egenconsulting.com wrote:
> 
> Well, there's been a lot of traffic going on about all sort of issues 
> and topics.  However, it came to a halt when one note came up with what 
> may be a "show-stopper."  So, I think we need to make a decision here. 
>  Do we take items that are too hard to fix, remove them, and put in an 
> addendum that says "the following items need to be resolved in the next 
> version"?  Or do we try to take a stab at fixing them.  We need to get a 

> version of CAP into RFC status.  We need to get people interoperating so 

> we can see what's really working and what's really hosed badly.  I asked 

> for a last call and that didn't work.  We really do need to get this out 

> the door.  Therefore, I'm once again asking for a last hard look at what 

> can stay and what needs to go in the current CAP draft.  If it's broken 
> and needs a lot of work - it goes out.  I am going to go back over the 
> last year's thr! eads and see what I can determine are the big issues. 
>  I'll post a note to the list with the items and will ask for a "hm" 
> from the list as to whether the item stays or goes.  If it goes, we'll 
> need help changing the draft to remove all text regarding that topic.
> 
> If you disagree with the items I post - say so.  If you agree with the 
> items - say so.  That way I know people are reading the list and will 
> agree with what we produce as the final draft. 
> 
> Cool?
> ___________________
> Patricia Egen Consulting
> www.egenconsulting.com
> 423-875-2652


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards



--=_alternative 005F50E485256D56_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">What about the scoping issue?<br>
___________________<br>
Patricia Egen Consulting<br>
www.egenconsulting.com<br>
423-875-2652</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Doug Royer &lt;Doug@royer.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">06/30/2003 23:18</font>
<br><font size=1 face="sans-serif">Please respond to ietf-calendar</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;ietf-calendar@imc.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: CAP draft - last call, etc.</font></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
Items that will be changed in the -11 version of the draft.<br>
<br>
(1) Sorting is out per this WG. (I submitted my own add on draft).<br>
(2) The ABNF will be fixed per the email on this WG.<br>
(3) Various typos sent to me and this list.<br>
(4) CS to generate FREEBUSY data (NOT CUA).<br>
<br>
As of the San Francisco IETF meeting (-10 release) there have been no<br>
other new CAP issues that seem to have reach consensus. The only<br>
new issue seems to be if TARGET will default and I did not think<br>
that made it past a couple of questions and opinions sent to the list.<br>
<br>
Unless I missed something, all of the other issues are<br>
all iCal/iTIP/iMIP issues.<br>
<br>
PLEASE SPEAK UP if you think that something else should make the -11<br>
version of the draft - I AM EDITING IT NOW.<br>
<br>
Still To do:<br>
<br>
(I) Beep profile.<br>
(II) Document the 1:1 or 1:MANY replies.<br>
<br>
Item (II) was discussed in S.F. and the thoughts were that<br>
you would bundle all single TARGET replies in one blob,<br>
and for each unique TARGET in the CS reply, the CS would<br>
send another blob of data.<br>
<br>
pregen@egenconsulting.com wrote:<br>
&gt; <br>
&gt; Well, there's been a lot of traffic going on about all sort of issues <br>
&gt; and topics. &nbsp;However, it came to a halt when one note came up with what <br>
&gt; may be a &quot;show-stopper.&quot; &nbsp;So, I think we need to make a decision here. <br>
&gt; &nbsp;Do we take items that are too hard to fix, remove them, and put in an <br>
&gt; addendum that says &quot;the following items need to be resolved in the next <br>
&gt; version&quot;? &nbsp;Or do we try to take a stab at fixing them. &nbsp;We need to get a <br>
&gt; version of CAP into RFC status. &nbsp;We need to get people interoperating so <br>
&gt; we can see what's really working and what's really hosed badly. &nbsp;I asked <br>
&gt; for a last call and that didn't work. &nbsp;We really do need to get this out <br>
&gt; the door. &nbsp;Therefore, I'm once again asking for a last hard look at what <br>
&gt; can stay and what needs to go in the current CAP draft. &nbsp;If it's broken <br>
&gt; and needs a lot of work - it goes out. &nbsp;I am going to go back over the <br>
&gt; last year's thr! eads and see what I can determine are the big issues. <br>
&gt; &nbsp;I'll post a note to the list with the items and will ask for a &quot;hm&quot; <br>
&gt; from the list as to whether the item stays or goes. &nbsp;If it goes, we'll <br>
&gt; need help changing the draft to remove all text regarding that topic.<br>
&gt; <br>
&gt; If you disagree with the items I post - say so. &nbsp;If you agree with the <br>
&gt; items - say so. &nbsp;That way I know people are reading the list and will <br>
&gt; agree with what we produce as the final draft. &nbsp;<br>
&gt; <br>
&gt; Cool?<br>
&gt; ___________________<br>
&gt; Patricia Egen Consulting<br>
&gt; www.egenconsulting.com<br>
&gt; 423-875-2652<br>
<br>
<br>
-- <br>
<br>
 &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
 &nbsp;-------------------------------|-----------------------------<br>
 &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
 &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards - You Need Standards<br>
</tt></font>
<br>
<br>
--=_alternative 005F50E485256D56_=--


From owner-ietf-calendar@mail.imc.org  Tue Jul  1 14:29:48 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10061
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 14:29:48 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61IJhFK074254
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 11:19:43 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h61IJh7l074253
	for ietf-calendar-bks; Tue, 1 Jul 2003 11:19:43 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61IJgFK074248
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 11:19:42 -0700 (PDT)
	(envelope-from bobmah@MIT.EDU)
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.12.4/8.9.2) with ESMTP id h61IJhnO018186;
	Tue, 1 Jul 2003 14:19:43 -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.12.4/8.9.2) with ESMTP id h61IJhZl006733;
	Tue, 1 Jul 2003 14:19:43 -0400 (EDT)
Received: from [18.18.1.170] (BOB.MIT.EDU [18.18.1.170])
	(authenticated bits=0)
	(User authenticated as bobmah@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id h61IJfU9000056;
	Tue, 1 Jul 2003 14:19:43 -0400 (EDT)
Mime-Version: 1.0
X-Sender: bobmah@PO12.MIT.EDU
Message-Id: <p05200f0dbb277f4e1b61@[18.18.1.170]>
In-Reply-To: <ISSMTP.2003_4_.20030701094620.2036H@sun.com>
References: <ISSMTP.2003_4_.20030701094620.2036H@sun.com>
Date: Tue, 1 Jul 2003 14:19:39 -0400
To: Satya Vempati <satyanarayana.vempati@sun.com>
From: Bob Mahoney <bobmah@MIT.EDU>
Subject: RE: CAP draft - last call, etc.
Cc: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


Satya-

Pat and I are pursuing an interpretation from one of the original authors, and hope to be able to shed some light on your questions soon...

(i.e., "we hear you and we're working on it."  :-)

-Bob

At 9:46 AM -0700 7/1/03, Satya Vempati wrote:
>
>Some of the iCAL/iTIP questions will impact the decisions on CAP. Especially, the outcome of the discussion on RECURRENCE-ID fundamentally affects the CAP spec based on how it is eventually resolved.
>IMHO, one final draft (hopefully 11) to iron out the differences is required before going to RFC.



From owner-ietf-calendar@mail.imc.org  Tue Jul  1 15:16:19 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13086
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 15:16:18 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61J7RFK079070
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 12:07:27 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h61J7RW5079069
	for ietf-calendar-bks; Tue, 1 Jul 2003 12:07:27 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61J7QFK079061
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 12:07:26 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h61J7MOR031732
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 12:07:27 -0700
Message-ID: <3F01DBE5.2000703@Royer.com>
Date: Tue, 01 Jul 2003 13:07:17 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP draft - last call, etc.
References: <ISSMTP.2003_4_.20030701094620.2036H@sun.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090404040407000103060003"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms090404040407000103060003
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Satya Vempati wrote:
> Some of the iCAL/iTIP questions will impact the decisions on CAP. 
> Especially, the outcome of the discussion on RECURRENCE-ID fundamentally 
> affects the CAP spec based on how it is eventually resolved.

I can see how that proposal could have effected the iTIP protocol
but not the CAP protocol. It would indirectly effected CUAs that used
CAP to store local CU data in the object across recurrence rule
changes. No matter which way it went, it would not have effected
the CAP 'protocol' at all. It would have effected all CUAs that
used iTIP to process scheduling requests via iMIP, CAP, or
any other transport.

That proposal that in iCal version-next that the recurrence-id
be tied to SEQUECEN:0  objects in order to be compatible with some
vendors seems to have died. (read Bruce's last email on the subject).
It was never necessary and I think that Burce agrees.

Does any disagree?

> IMHO, one final draft (hopefully 11) to iron out the differences is 
> required before going to RFC.



-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms090404040407000103060003
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDExOTA3MTdaMCMGCSqGSIb3DQEJBDEWBBTM
XGc0SXw9++FBN1Y5u7eeiGUciTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAhG5dhr7YQWPY
4hzvhTt+DtSsDJKSCn65/XBfHKlGzOZV7SKqgOsfQjh/DpY5vK2jCIa23oB5xqgLIyCyU87X
V9QKndmRdKAVP0CJPG9ub7ihvFKQc0wWg7y3I2E+boCU104EC+f/L2qEyhucSGrlT/xbaje4
VUl30htf8XztScwlCkdR1XEzoF6xqxW5l7K3wm63Hlm/qUsjUpYxOx/Ywwnukow3xQo+MRsM
COwxNbsYlUHWeyq2xtNSU1Aiu4dwXcQ51LLyA0rznFPWqegnqI8bVTnSLS5DTXhrU4q0Khze
RAgJqMMcGZgs+RrG8MAFVoV1g9yUoWEn4JmJD44kIgAAAAAAAA==
--------------ms090404040407000103060003--



From owner-ietf-calendar@mail.imc.org  Tue Jul  1 17:10:53 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16561
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 17:10:51 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61L05FK084414
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 14:00:05 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h61L0554084413
	for ietf-calendar-bks; Tue, 1 Jul 2003 14:00:05 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61L03FK084408
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 14:00:03 -0700 (PDT)
	(envelope-from satyanarayana.vempati@Sun.COM)
Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42])
	by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h61L051J002735
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 15:00:05 -0600 (MDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail2sca.sfbay.sun.com (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h61L05aJ010460
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 14:00:05 -0700 (PDT)
Received: from pranav.red.iplanet.com (pranav.red.iplanet.com [192.18.144.109])
 by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HHD00C246C50Z@ha13sca-mail1.sfbay.sun.com> for
 ietf-calendar@imc.org; Tue, 01 Jul 2003 14:00:05 -0700 (PDT)
Date: Tue, 01 Jul 2003 14:00:04 -0700
From: Satya Vempati <satyanarayana.vempati@sun.com>
Subject: RE: CAP draft - last call, etc.
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_4_.20030701140004.2036J@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_rDmo6VzXCBFpWFXbK/ZOoA)"; DIFFERENCES=Content-Language
Content-language: en-USA
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



--Boundary_(ID_rDmo6VzXCBFpWFXbK/ZOoA)
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

From your mail to the news group on 6/19/03:

"Fixating the recurrence-id to sequence zero
prevents the recurrence rules from ever changing and will make CAP
VCARs, NOTIFICATIONS, local CU VALARMs break in CAP. So I just do
not see how that will work."

Additionally, from the CAP draft 10: 

-----------
6.1.1.17 Query by Date-Time range

   This query selects the entire content of every booked "VEVENT"
   component that has an instance greater than or equal to July 1st,
   2000 00:00:00 UTC and less than or equal to July 31st, 2000 23:59:59
   UTC.  This includes single instance "VEVENT" components that do no
   explicitly contain a "RECURRENCE-ID" property.


   BEGIN:VQUERY
   EXPAND:TRUE
   QUERY:SELECT * FROM VEVENT
   WHERE RECURRENCE-ID >= '20000801T000000Z'
   AND RECURRENCE-ID <= '20000831T235959Z'
   AND STATE() = 'BOOKED'
   END:VQUERY

---------------

If RECURRENCE-IDs stay rooted at their instantiated values, the query as
formulated above will return erroneous results.

I haven't seen an email in which Bruce Kahn conceded that RECURRENCE-IDs
should change.


-----Original Message-----
From: Doug Royer [mailto:Doug@royer.com]
Sent: Tuesday, July 01, 2003 12:07 PM
To: ietf-calendar@imc.org
Subject: Re: CAP draft - last call, etc.




Satya Vempati wrote:
> Some of the iCAL/iTIP questions will impact the decisions on CAP. 
> Especially, the outcome of the discussion on RECURRENCE-ID fundamentally 
> affects the CAP spec based on how it is eventually resolved.

I can see how that proposal could have effected the iTIP protocol
but not the CAP protocol. It would indirectly effected CUAs that used
CAP to store local CU data in the object across recurrence rule
changes. No matter which way it went, it would not have effected
the CAP 'protocol' at all. It would have effected all CUAs that
used iTIP to process scheduling requests via iMIP, CAP, or
any other transport.

That proposal that in iCal version-next that the recurrence-id
be tied to SEQUECEN:0  objects in order to be compatible with some
vendors seems to have died. (read Bruce's last email on the subject).
It was never necessary and I think that Burce agrees.

Does any disagree?

> IMHO, one final draft (hopefully 11) to iron out the differences is 
> required before going to RFC.



-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--Boundary_(ID_rDmo6VzXCBFpWFXbK/ZOoA)
Content-id: 0
Content-type: TEXT/html; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

<html><head></head><body>
<font size=2 >From your mail to the news group on 6/19/03:</font><div>
<font size=2 ></font><div>
<font size=2 >"Fixating the recurrence-id to sequence zero</font><div>
<font size=2 >prevents the recurrence rules from ever changing and will
make CAP</font><div>
<font size=2 >VCARs, NOTIFICATIONS, local CU VALARMs break in CAP. So I
just do</font><div>
<font size=2 >not see how that will work."</font><div>
<font size=2 ></font><div>
<font size=2 >Additionally, from the CAP draft 10: </font><div>
<font size=2 ></font><div>
<font size=2 >-----------</font><div>
<font size=2 >6.1.1.17 Query by Date-Time range</font><div>
<font size=2 ></font><div>
<font size=2 >   This query selects the entire content of every booked
"VEVENT"</font><div>
<font size=2 >   component that has an instance greater than or equal to
July 1st,</font><div>
<font size=2 >   2000 00:00:00 UTC and less than or equal to July 31st,
2000 23:59:59</font><div>
<font size=2 >   UTC.  This includes single instance "VEVENT" components
that do no</font><div>
<font size=2 >   explicitly contain a "RECURRENCE-ID" property.</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >   BEGIN:VQUERY</font><div>
<font size=2 >   EXPAND:TRUE</font><div>
<font size=2 >   QUERY:SELECT * FROM VEVENT</font><div>
<font size=2 >   WHERE RECURRENCE-ID &gt;= '20000801T000000Z'</font><div>
<font size=2 >   AND RECURRENCE-ID &lt;= '20000831T235959Z'</font><div>
<font size=2 >   AND STATE() = 'BOOKED'</font><div>
<font size=2 >   END:VQUERY</font><div>
<font size=2 ></font><div>
<font size=2 >---------------</font><div>
<font size=2 ></font><div>
<font size=2 >If RECURRENCE-IDs stay rooted at their instantiated values,
the query as formulated above will return erroneous results.</font><div>
<font size=2 ></font><div>
<font size=2 >I haven't seen an email in which Bruce Kahn conceded that
RECURRENCE-IDs should change.</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >-----Original Message-----</font><div>
<font size=2 >From: Doug Royer [mailto:Doug@royer.com]</font><div>
<font size=2 >Sent: Tuesday, July 01, 2003 12:07 PM</font><div>
<font size=2 >To: ietf-calendar@imc.org</font><div>
<font size=2 >Subject: Re: CAP draft - last call, etc.</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >Satya Vempati wrote:</font><div>
<font size=2 >&gt; Some of the iCAL/iTIP questions will impact the
decisions on CAP. </font><div>
<font size=2 >&gt; Especially, the outcome of the discussion on
RECURRENCE-ID fundamentally </font><div>
<font size=2 >&gt; affects the CAP spec based on how it is eventually
resolved.</font><div>
<font size=2 ></font><div>
<font size=2 >I can see how that proposal could have effected the iTIP
protocol</font><div>
<font size=2 >but not the CAP protocol. It would indirectly effected CUAs
that used</font><div>
<font size=2 >CAP to store local CU data in the object across recurrence
rule</font><div>
<font size=2 >changes. No matter which way it went, it would not have
effected</font><div>
<font size=2 >the CAP 'protocol' at all. It would have effected all CUAs
that</font><div>
<font size=2 >used iTIP to process scheduling requests via iMIP, CAP,
or</font><div>
<font size=2 >any other transport.</font><div>
<font size=2 ></font><div>
<font size=2 >That proposal that in iCal version-next that the
recurrence-id</font><div>
<font size=2 >be tied to SEQUECEN:0  objects in order to be compatible
with some</font><div>
<font size=2 >vendors seems to have died. (read Bruce's last email on the
subject).</font><div>
<font size=2 >It was never necessary and I think that Burce
agrees.</font><div>
<font size=2 ></font><div>
<font size=2 >Does any disagree?</font><div>
<font size=2 ></font><div>
<font size=2 >&gt; IMHO, one final draft (hopefully 11) to iron out the
differences is </font><div>
<font size=2 >&gt; required before going to RFC.</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >-- </font><div>
<font size=2 ></font><div>
<font size=2 >  Doug Royer                     |  
http://INET-Consulting.com</font><div>
<font size=2 > 
-------------------------------|-----------------------------</font><div>
<font size=2 >  Doug@Royer.com                 | Office:
(208)612-INET</font><div>
<font size=2 >  http://Royer.com/People/Doug   |    Fax:
(866)594-8574</font><div>
<font size=2 >                                 |   Cell:
(208)520-4044</font><div>
<font size=2 ></font><div>
<font size=2 >                 We Do Standards - You Need
Standards</font><div>
<font ></font></body></html>

--Boundary_(ID_rDmo6VzXCBFpWFXbK/ZOoA)--


From owner-ietf-calendar@mail.imc.org  Tue Jul  1 18:37:27 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19525
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 18:37:27 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61MPSFK089765
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 15:25:28 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h61MPSrC089764
	for ietf-calendar-bks; Tue, 1 Jul 2003 15:25:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61MPQFK089759
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 15:25:27 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h61MPPOR001183
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 15:25:28 -0700
Message-ID: <3F020A4B.3030902@Royer.com>
Date: Tue, 01 Jul 2003 16:25:15 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP draft - last call, etc.
References: <ISSMTP.2003_4_.20030701140004.2036J@sun.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030004020502000107050608"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms030004020502000107050608
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Satya Vempati wrote:
>  From your mail to the news group on 6/19/03:
> "Fixating the recurrence-id to sequence zero
> prevents the recurrence rules from ever changing and will make CAP
> VCARs, NOTIFICATIONS, local CU VALARMs break in CAP. So I just do
> not see how that will work."

As in they get DELETED if the UID changes. Not the same as breaking
the CAP protocol.

> Additionally, from the CAP draft 10:
> -----------
> 6.1.1.17 Query by Date-Time range
> This query selects the entire content of every booked "VEVENT"
> component that has an instance greater than or equal to July 1st,
> 2000 00:00:00 UTC and less than or equal to July 31st, 2000 23:59:59
> UTC. This includes single instance "VEVENT" components that do no
> explicitly contain a "RECURRENCE-ID" property.
> BEGIN:VQUERY
> EXPAND:TRUE
> QUERY:SELECT * FROM VEVENT
> WHERE RECURRENCE-ID >= '20000801T000000Z'
> AND RECURRENCE-ID <= '20000831T235959Z'
> AND STATE() = 'BOOKED'
> END:VQUERY
> ---------------
> If RECURRENCE-IDs stay rooted at their instantiated values, the query as 
> formulated above will return erroneous results.
> I haven't seen an email in which Bruce Kahn conceded that RECURRENCE-IDs 
> should change.

In Bruces email dated: June 26 3:55PM

  ...The other way I described it also works but could mistakenly make some
  think that the CUA must preserve both the SEQUENCE:0 definition and then
  all the current ones and thats not necessary.  Both ways will achieve
  the same effect. ...

So, no.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms030004020502000107050608
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDEyMjI1MTVaMCMGCSqGSIb3DQEJBDEWBBRl
MkuiyWfko1TeZXIol8S2wTjf2zBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAHM5dQxEx2ItL
cDxQxXNk+4r4wz5A3Zhe1EFZ+FQHTwBwqF1ZHOCHcXRh/Rsvyz8INxzifdPlUiwew4yo3IWx
Cd8AXlrhNH8x3f4cjcN22fOzBaIXaOsO7zoBvc/BjKD394aYwd/bSZvaf0pWeelTXjAqP+Ma
p1hzK7MkaCl1D10QCnEXeIY3AdqbwrPLKsDZlvaE9HIOrCNBsT6jSlwuKFAmYUx5GT14hf+5
gXoGGXdYUb1kl/dZQvUpj8DRpd3iuN3rhBQLbalCJOD7RYInboubMFedIMaw/QpMnXN0kKJI
u9a/nK2Hr1NZPFuwkOVyYF7l0s3dZjOdyAmeJn37nQAAAAAAAA==
--------------ms030004020502000107050608--



From owner-ietf-calendar@mail.imc.org  Tue Jul  1 19:13:45 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20315
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 19:13:45 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61N3ZFK090876
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 16:03:35 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h61N3Zdv090875
	for ietf-calendar-bks; Tue, 1 Jul 2003 16:03:35 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h61N3XFK090870
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 16:03:34 -0700 (PDT)
	(envelope-from satyanarayana.vempati@Sun.COM)
Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42])
	by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h61N3Zvc000575
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 17:03:36 -0600 (MDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail2sca.sfbay.sun.com (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h61N3ZaJ010844
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 16:03:35 -0700 (PDT)
Received: from pranav.red.iplanet.com (pranav.red.iplanet.com [192.18.144.109])
 by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HHD00CFVC1Z0Z@ha13sca-mail1.sfbay.sun.com> for
 ietf-calendar@imc.org; Tue, 01 Jul 2003 16:03:35 -0700 (PDT)
Date: Tue, 01 Jul 2003 16:03:35 -0700
From: Satya Vempati <satyanarayana.vempati@sun.com>
Subject: RE: CAP draft - last call, etc.
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_4_.20030701160335.2036N@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_7BxBffSX5Kdt9DHzJbhqdg)"; DIFFERENCES=Content-Language
Content-language: en-USA
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



--Boundary_(ID_7BxBffSX5Kdt9DHzJbhqdg)
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT


I might have misunderstood Bruce but I took it differently. Since
RECURRENCE-ID "never" changes in his model, SEQUENCE:0 is not really
required. All SEQUENCE numbers point to the same RECURRENCE-ID and there
is no need to "preserve" SEQUENCE:0.

-----Original Message-----
From: Doug Royer [mailto:Doug@royer.com]
Sent: Tuesday, July 01, 2003 3:25 PM
To: ietf-calendar@imc.org
Subject: Re: CAP draft - last call, etc.




Satya Vempati wrote:
>  From your mail to the news group on 6/19/03:
> "Fixating the recurrence-id to sequence zero
> prevents the recurrence rules from ever changing and will make CAP
> VCARs, NOTIFICATIONS, local CU VALARMs break in CAP. So I just do
> not see how that will work."

As in they get DELETED if the UID changes. Not the same as breaking
the CAP protocol.

> Additionally, from the CAP draft 10:
> -----------
> 6.1.1.17 Query by Date-Time range
> This query selects the entire content of every booked "VEVENT"
> component that has an instance greater than or equal to July 1st,
> 2000 00:00:00 UTC and less than or equal to July 31st, 2000 23:59:59
> UTC. This includes single instance "VEVENT" components that do no
> explicitly contain a "RECURRENCE-ID" property.
> BEGIN:VQUERY
> EXPAND:TRUE
> QUERY:SELECT * FROM VEVENT
> WHERE RECURRENCE-ID >= '20000801T000000Z'
> AND RECURRENCE-ID <= '20000831T235959Z'
> AND STATE() = 'BOOKED'
> END:VQUERY
> ---------------
> If RECURRENCE-IDs stay rooted at their instantiated values, the query as 
> formulated above will return erroneous results.
> I haven't seen an email in which Bruce Kahn conceded that RECURRENCE-IDs 
> should change.

In Bruces email dated: June 26 3:55PM

  ...The other way I described it also works but could mistakenly make some
  think that the CUA must preserve both the SEQUENCE:0 definition and then
  all the current ones and thats not necessary.  Both ways will achieve
  the same effect. ...

So, no.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--Boundary_(ID_7BxBffSX5Kdt9DHzJbhqdg)
Content-id: 0
Content-type: TEXT/html; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

<html><head></head><body>
<font size=2 ></font><div>
<font size=2 >I might have misunderstood Bruce but I took it differently.
Since RECURRENCE-ID "never" changes in his model, SEQUENCE:0 is not really
required. All SEQUENCE numbers point to the same RECURRENCE-ID and there
is no need to "preserve" SEQUENCE:0.</font><div>
<font size=2 ></font><div>
<font size=2 >-----Original Message-----</font><div>
<font size=2 >From: Doug Royer [mailto:Doug@royer.com]</font><div>
<font size=2 >Sent: Tuesday, July 01, 2003 3:25 PM</font><div>
<font size=2 >To: ietf-calendar@imc.org</font><div>
<font size=2 >Subject: Re: CAP draft - last call, etc.</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >Satya Vempati wrote:</font><div>
<font size=2 >&gt;  From your mail to the news group on
6/19/03:</font><div>
<font size=2 >&gt; "Fixating the recurrence-id to sequence zero</font><div>
<font size=2 >&gt; prevents the recurrence rules from ever changing and
will make CAP</font><div>
<font size=2 >&gt; VCARs, NOTIFICATIONS, local CU VALARMs break in CAP. So
I just do</font><div>
<font size=2 >&gt; not see how that will work."</font><div>
<font size=2 ></font><div>
<font size=2 >As in they get DELETED if the UID changes. Not the same as
breaking</font><div>
<font size=2 >the CAP protocol.</font><div>
<font size=2 ></font><div>
<font size=2 >&gt; Additionally, from the CAP draft 10:</font><div>
<font size=2 >&gt; -----------</font><div>
<font size=2 >&gt; 6.1.1.17 Query by Date-Time range</font><div>
<font size=2 >&gt; This query selects the entire content of every booked
"VEVENT"</font><div>
<font size=2 >&gt; component that has an instance greater than or equal to
July 1st,</font><div>
<font size=2 >&gt; 2000 00:00:00 UTC and less than or equal to July 31st,
2000 23:59:59</font><div>
<font size=2 >&gt; UTC. This includes single instance "VEVENT" components
that do no</font><div>
<font size=2 >&gt; explicitly contain a "RECURRENCE-ID"
property.</font><div>
<font size=2 >&gt; BEGIN:VQUERY</font><div>
<font size=2 >&gt; EXPAND:TRUE</font><div>
<font size=2 >&gt; QUERY:SELECT * FROM VEVENT</font><div>
<font size=2 >&gt; WHERE RECURRENCE-ID &gt;= '20000801T000000Z'</font><div>
<font size=2 >&gt; AND RECURRENCE-ID &lt;= '20000831T235959Z'</font><div>
<font size=2 >&gt; AND STATE() = 'BOOKED'</font><div>
<font size=2 >&gt; END:VQUERY</font><div>
<font size=2 >&gt; ---------------</font><div>
<font size=2 >&gt; If RECURRENCE-IDs stay rooted at their instantiated
values, the query as </font><div>
<font size=2 >&gt; formulated above will return erroneous
results.</font><div>
<font size=2 >&gt; I haven't seen an email in which Bruce Kahn conceded
that RECURRENCE-IDs </font><div>
<font size=2 >&gt; should change.</font><div>
<font size=2 ></font><div>
<font size=2 >In Bruces email dated: June 26 3:55PM</font><div>
<font size=2 ></font><div>
<font size=2 >  ...The other way I described it also works but could
mistakenly make some</font><div>
<font size=2 >  think that the CUA must preserve both the SEQUENCE:0
definition and then</font><div>
<font size=2 >  all the current ones and thats not necessary.  Both ways
will achieve</font><div>
<font size=2 >  the same effect. ...</font><div>
<font size=2 ></font><div>
<font size=2 >So, no.</font><div>
<font size=2 ></font><div>
<font size=2 ></font><div>
<font size=2 >-- </font><div>
<font size=2 ></font><div>
<font size=2 >  Doug Royer                     |  
http://INET-Consulting.com</font><div>
<font size=2 > 
-------------------------------|-----------------------------</font><div>
<font size=2 >  Doug@Royer.com                 | Office:
(208)612-INET</font><div>
<font size=2 >  http://Royer.com/People/Doug   |    Fax:
(866)594-8574</font><div>
<font size=2 >                                 |   Cell:
(208)520-4044</font><div>
<font size=2 ></font><div>
<font size=2 >                 We Do Standards - You Need
Standards</font><div>
<font ></font></body></html>

--Boundary_(ID_7BxBffSX5Kdt9DHzJbhqdg)--


From owner-ietf-calendar@mail.imc.org  Tue Jul  1 20:28:27 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22414
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 20:28:26 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h620GtFK092817
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 17:16:55 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h620GssF092816
	for ietf-calendar-bks; Tue, 1 Jul 2003 17:16:54 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h620GrFK092810
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 17:16:53 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h620GqOR002205
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 17:16:55 -0700
Message-ID: <3F022466.7080406@Royer.com>
Date: Tue, 01 Jul 2003 18:16:38 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP draft - last call, etc.
References: <ISSMTP.2003_4_.20030701160335.2036N@sun.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms040401040906080609060805"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms040401040906080609060805
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Satya Vempati wrote:
> I might have misunderstood Bruce but I took it differently. Since 
> RECURRENCE-ID "never" changes in his model, SEQUENCE:0 is not really 
> required. All SEQUENCE numbers point to the same RECURRENCE-ID and there 
> is no need to "preserve" SEQUENCE:0.

Ether way, it may break iTIP clients, but not the CAP protocol.

And his belief is contrary to the text in iCAL/iTIP, he is simply
telling people how he wants it, not how it is.

Plus, the CUA can do a full REFRESH and ignore that rule anyway.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms040401040906080609060805
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIwMDE2MzhaMCMGCSqGSIb3DQEJBDEWBBR9
0dBn9MY+P9xPjb968XUmy1MDCDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAeqtVyiUPnqhi
No7hY4D18L+dPEfSFQUSdKep9XubC7JQUARzmMjq6J7uASvxjKKh9y/ioROrLJ7Uf4dqN+0z
OkW+I6jJTpiflNvTu0F2H2tu+XeiPzxLMeVj+TJZ5MJc8sUbyLPhedM9rTKeRbuCiSW5KHrT
Bu3TsVmV8pqm2aDF670pQWYb3OXgutCUD+KfCQm5zxYFou6Si7A6cnS7lgK3hT3CFGfyuSt6
oawW4iXi00Kwm9BeoDj9u2L5/oV40RvvoegUY1mEJCoLOataE130W/oy5Z+VMW3es2g3TfcV
E8zN6iNak4a8SMnrsANrW1ovkriVXLsialcaR2XvDwAAAAAAAA==
--------------ms040401040906080609060805--



From owner-ietf-calendar@mail.imc.org  Tue Jul  1 22:24:40 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25080
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 22:24:40 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h622DpFK096571
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 19:13:51 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h622Dpgc096570
	for ietf-calendar-bks; Tue, 1 Jul 2003 19:13:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h622DnFK096559
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 19:13:49 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Cc: "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: Re: CAP draft - last call, etc.
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF5375CB48.20800FF8-ON85256D57.000C2596-85256D57.000C41DF@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Tue, 1 Jul 2003 22:13:52 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/01/2003 10:13:52 PM,
	Serialize complete at 07/01/2003 10:13:52 PM
Content-Type: multipart/alternative; boundary="=_alternative 000C41D685256D57_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 000C41D685256D57_=
Content-Type: text/plain; charset="us-ascii"

Doug, I don't believe that Bruce is telling people how he wants it - but 
rather how he "interprets" the draft.  That's why we need an author of the 
original iTIP to tell us what they thought they meant.  That's coming 
soon. 8-)
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




Doug Royer <Doug@royer.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/01/2003 20:16
Please respond to "ietf-calendar@imc.org"

 
        To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
        cc: 
        Subject:        Re: CAP draft - last call, etc.




Satya Vempati wrote:
> I might have misunderstood Bruce but I took it differently. Since 
> RECURRENCE-ID "never" changes in his model, SEQUENCE:0 is not really 
> required. All SEQUENCE numbers point to the same RECURRENCE-ID and there 

> is no need to "preserve" SEQUENCE:0.

Ether way, it may break iTIP clients, but not the CAP protocol.

And his belief is contrary to the text in iCAL/iTIP, he is simply
telling people how he wants it, not how it is.

Plus, the CUA can do a full REFRESH and ignore that rule anyway.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards



--=_alternative 000C41D685256D57_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Doug, I don't believe that Bruce is telling people how he wants it - but rather how he &quot;interprets&quot; the draft. &nbsp;That's why we need an author of the original iTIP to tell us what they thought they meant. &nbsp;That's coming soon. 8-)<br>
___________________<br>
Patricia Egen Consulting<br>
www.egenconsulting.com<br>
423-875-2652</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Doug Royer &lt;Doug@royer.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/01/2003 20:16</font>
<br><font size=1 face="sans-serif">Please respond to &quot;ietf-calendar@imc.org&quot;</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: CAP draft - last call, etc.</font></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
Satya Vempati wrote:<br>
&gt; I might have misunderstood Bruce but I took it differently. Since <br>
&gt; RECURRENCE-ID &quot;never&quot; changes in his model, SEQUENCE:0 is not really <br>
&gt; required. All SEQUENCE numbers point to the same RECURRENCE-ID and there <br>
&gt; is no need to &quot;preserve&quot; SEQUENCE:0.<br>
<br>
Ether way, it may break iTIP clients, but not the CAP protocol.<br>
<br>
And his belief is contrary to the text in iCAL/iTIP, he is simply<br>
telling people how he wants it, not how it is.<br>
<br>
Plus, the CUA can do a full REFRESH and ignore that rule anyway.<br>
<br>
<br>
-- <br>
<br>
 &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
 &nbsp;-------------------------------|-----------------------------<br>
 &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
 &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards - You Need Standards<br>
</tt></font>
<br>
<br>
--=_alternative 000C41D685256D57_=--


From owner-ietf-calendar@mail.imc.org  Tue Jul  1 23:14:12 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25963
	for <calsch-archive@lists.ietf.org>; Tue, 1 Jul 2003 23:14:11 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6234SFK098035
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 20:04:28 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6234SHk098034
	for ietf-calendar-bks; Tue, 1 Jul 2003 20:04:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6234QFK098029
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 20:04:27 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6234POR003580
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 20:04:28 -0700
Message-ID: <3F024BB0.80706@Royer.com>
Date: Tue, 01 Jul 2003 21:04:16 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP draft - last call, etc.
References: <OF5375CB48.20800FF8-ON85256D57.000C2596-85256D57.000C41DF@egenconsulting.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms000506010307080909000705"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms000506010307080909000705
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



pregen@egenconsulting.com wrote:
> 
> Doug, I don't believe that Bruce is telling people how he wants it - but 
> rather how he "interprets" the draft.

You mean how he interprets" RFC 2446?

It may effect CUA's that use CAP. But it will effect
any iTIP CUA, it is not limited to CAP.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms000506010307080909000705
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIwMzA0MTZaMCMGCSqGSIb3DQEJBDEWBBTU
EEyvcDmK7ZfdrtdDO8to3oTVQTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAWx0p+Qs//OZG
60Zz7oICzoORaB+dpZsUlI6TxyeDZNEuLj6AXtNqs4zUjOtJLVkbbbCuYmEkwCsNStW0W7sC
SEo9WYe61wbAX9xCu3PUS1aZHpBmZzVUSd5wXxLZfuUkWJ7alIhK029gJoLLyGGFbUoGkwr/
KNhCBlC5B90NhX72uSu4JigMGmnSi4EjpT/BtBZBbLg1o3sT9YFulmZI8LffuZfLihS8VLv2
y3FAx0hFiXlnfc9wz3DT4O2KqacNei9+gba1aXeB6nmqRay1s6LpVleYx+bT9hzLoomg092O
1bl2unW2nrPzciS56pjB2Ik0AX2lg6R+MqlG0+AhwQAAAAAAAA==
--------------ms000506010307080909000705--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 00:00:40 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27025
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 00:00:39 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h623pAFK099284
	for <ietf-calendar-bks@above.proper.com>; Tue, 1 Jul 2003 20:51:10 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h623pAmi099283
	for ietf-calendar-bks; Tue, 1 Jul 2003 20:51:10 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h623p7FK099277
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 20:51:08 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h623p4OR003946
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 1 Jul 2003 20:51:09 -0700
Message-ID: <3F02569C.6000804@Royer.com>
Date: Tue, 01 Jul 2003 21:50:52 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: Changing iTIP RECURRECE rules [was CAP last call...]
References: <ISSMTP.2003_4_.20030701160335.2036N@sun.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060807090708000600070306"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060807090708000600070306
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce - you are a friend - but in this debate I think
you may be lost :-)


Satya Vempati wrote:
> I might have misunderstood Bruce but I took it differently. Since 
> RECURRENCE-ID "never" changes in his model, SEQUENCE:0 is not really 
> required. All SEQUENCE numbers point to the same RECURRENCE-ID and there 
> is no need to "preserve" SEQUENCE:0.

His model is not iCAL or iTIP it is a NEW proposal for the
next version of iCAL or iTIP.

In iTIP:

    Hence, CUAs must persist the following component properties: "UID",
    "RECURRENCE-ID", "SEQUENCE", and "DTSTAMP".  Furthermore, for each
    "ATTENDEE" property of a component CUAs must persist the "SEQUENCE"
    and "DTSTAMP" property values associated with the "Attendee's"
    response.


And what about the "ADD" method:

   4.4.6 Add A New Instance To A Recurring Event

    This example adds a one-time additional instance to the recurring
    event.  "Organizer" adds a second July meeting on the 15th.

The text and examples CLEARLY show the SEQUENCE number being bumped
and the new SEQUENCE has at least one instance in it that is NOT
in SEQUENCE:0. Thus NO ONE CAN JOIN if you follow Burce's model
and Bruce agrees. Then Bruce made a NEW assertion - that you MUST
throw away the UID and start over. Sorry but his model is just
not thought out.

And what about:

  4.4.7 Add A New Series of Instances To A Recurring Event

   ...
    Alternatively, if the "Organizer" is not concerned with per-instance
    updates, the entire event can be rescheduled using a "REQUEST". This
    is done by using the "UID" of the event to reschedule and including
    the modified "RRULE". Note, that since this is an entire rescheduling
    of the event, any instance-specific information will be lost.
                                                            ^^^^^
    ...


It does not say, 'Throw away the UID', it says 'reschedule'
using the 'UID' and 'any instance-specific information will be lost.'.
Why is that confusing to anyone?

If you follow the debate from the start by reading the archives
I think you will agree that it started from an assertion that
a specific vendor does it incorrectly and Bruce wanted to be
compatible. For which I reply - you can be - ISSUE a full REFRESH
and you are back in sync with that vendor. You do NOT need
to re-issue an iTIP RFC removing MULTIPLE paragraphs saying you
CAN reschedule. If that vendor throws away the UID - so what?
It does not effect iTIP. It only effects those users who
loose data - a point NOT disputed at all. My testing shows
that that vendor CAN reschedule to an entirely different
set of recurrence rules. No proof is provided from Bruce,
just another assertion that if we break iTIP in this
way it works in some new way and other things that were
not busted are newly busted.

Bruce has NOT shown any thing busted. He simply says that
if you do something that is not documented (in a way that
looks to me to be a way not to have to follow iTIP and
bump the sequence number), then the undocumented way does
not work. So what? Do it the documented way.

This debate reminds me of a class project where you
would get an 'A+' if you could so confuse a truth
to make it appear to be a problem. Bruce gets an 'A++'.
It is NOT busted! DO A REFRESH - AND the text in ITIP
tells you HOW and WHEN to detect you need to do that
REFRESH and for EXACTLY the reasons in this debate.
Yet Burce has NEVER debated that fact.

Bruce - you are a friend - but in this debate I think
you may be lost :-)


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060807090708000600070306
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIwMzUwNTNaMCMGCSqGSIb3DQEJBDEWBBTY
2lNAIYUJF2c3GgFX92T0KZbuATBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEApfdSehtyBHm9
eEVWeVdXTZGj5efoCNrOZkHd28ssu1Pt+4+z6N4m6+xYTkZ1QilPV+Ba2womqHrdIPM8+CuG
cGwDApoDlAzqgvOEJW94bJtY6AoM/KI8wxId9HrxwBHznl03KEw3cgmCfuKxC/E4+CLlbA51
csZB41qlh4rpIjLrKCVoPF6NACxzXXcgg2wkHs3FdHdPswG59c+3aZeFGwWgoySwIuy7FWSv
ugYKypvsjh47Re47GG/vEXleNpmDhRawFG04PxaCCcGqkB9a+dSIr8rZ321KLn1uMUr1gMyP
aKOcbnEhBvkTmFgCaw6QgcbzxeO5CJES32Z/0NG/HQAAAAAAAA==
--------------ms060807090708000600070306--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 13:44:22 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03819
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 13:44:22 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62HTmFK070909
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 10:29:48 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62HTmG3070908
	for ietf-calendar-bks; Wed, 2 Jul 2003 10:29:48 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62HTkFK070897
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 10:29:47 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Cc: "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: Re: CAP draft - last call, etc.
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF2EB0CAF2.F6DFE5B1-ON85256D57.005FFFB1-85256D57.00601E3D@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Wed, 2 Jul 2003 13:29:51 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/02/2003 01:29:48 PM,
	Serialize complete at 07/02/2003 01:29:48 PM
Content-Type: multipart/alternative; boundary="=_alternative 00601E3485256D57_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 00601E3485256D57_=
Content-Type: text/plain; charset="us-ascii"

Yes, I meant all the RFC's.  And yes, if something is mis-interpretted, it 
affects a lot of things.  Remember, all three drafts, iCalendar, iTIP and 
iMIP were written at different times and by different authors.  So, to say 
there may be semantic issues is putting it mildly.  And remember, we are 
in interop testing so that we can find these problems and resolve them.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




Doug Royer <Doug@royer.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/01/2003 23:04
Please respond to "ietf-calendar@imc.org"

 
        To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
        cc: 
        Subject:        Re: CAP draft - last call, etc.




pregen@egenconsulting.com wrote:
> 
> Doug, I don't believe that Bruce is telling people how he wants it - but 

> rather how he "interprets" the draft.

You mean how he interprets" RFC 2446?

It may effect CUA's that use CAP. But it will effect
any iTIP CUA, it is not limited to CAP.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards



--=_alternative 00601E3485256D57_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Yes, I meant all the RFC's. &nbsp;And yes, if something is mis-interpretted, it affects a lot of things. &nbsp;Remember, all three drafts, iCalendar, iTIP and iMIP were written at different times and by different authors. &nbsp;So, to say there may be semantic issues is putting it mildly. &nbsp;And remember, we are in interop testing so that we can find these problems and resolve them.<br>
___________________<br>
Patricia Egen Consulting<br>
www.egenconsulting.com<br>
423-875-2652</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Doug Royer &lt;Doug@royer.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/01/2003 23:04</font>
<br><font size=1 face="sans-serif">Please respond to &quot;ietf-calendar@imc.org&quot;</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: CAP draft - last call, etc.</font></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
pregen@egenconsulting.com wrote:<br>
&gt; <br>
&gt; Doug, I don't believe that Bruce is telling people how he wants it - but <br>
&gt; rather how he &quot;interprets&quot; the draft.<br>
<br>
You mean how he interprets&quot; RFC 2446?<br>
<br>
It may effect CUA's that use CAP. But it will effect<br>
any iTIP CUA, it is not limited to CAP.<br>
<br>
-- <br>
<br>
 &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
 &nbsp;-------------------------------|-----------------------------<br>
 &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
 &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards - You Need Standards<br>
</tt></font>
<br>
<br>
--=_alternative 00601E3485256D57_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 14:20:00 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05221
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 14:20:00 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62I9rFK074268
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 11:09:53 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62I9rwk074267
	for ietf-calendar-bks; Wed, 2 Jul 2003 11:09:53 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62I9rFK074242;
	Wed, 2 Jul 2003 11:09:53 -0700 (PDT)
	(envelope-from arnaud.quillaud@sun.com)
Received: from dm-usca15-11.red.iplanet.com (host-185-56-18-192.iplanet.com [192.18.56.185] (may be forged))
	by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h62I9lKo002011;
	Wed, 2 Jul 2003 11:09:47 -0700 (PDT)
Received: from gotmail-2.red.iplanet.com (gotmail-2.red.iplanet.com [192.18.73.252])
	by dm-usca15-11.red.iplanet.com (8.11.7+Sun/8.10.2/IPLANET,v1.2) with ESMTP id h62I9AN22835;
	Wed, 2 Jul 2003 11:09:10 -0700 (PDT)
Received: from lamachine (vpn-129-150-17-197.SFBay.Sun.COM [129.150.17.197])
 by we-gotmail.red.iplanet.com
 (Sun ONE Messaging Server 6.0 (built Jun 26 2003))
 with ESMTP id <0HHE00L0FT490I30@we-gotmail.red.iplanet.com>; Wed,
 02 Jul 2003 11:09:47 -0700 (PDT)
Date: Wed, 02 Jul 2003 11:11:55 -0700
From: Arnaud Quillaud <arnaud.quillaud@sun.com>
Subject: RE: CAP draft - last call, etc.
To: "pregen@egenconsulting.com" <pregen@egenconsulting.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Cc: "owner-ietf-calendar@mail.imc.org" <owner-ietf-calendar@mail.imc.org>
Message-id: <ISSMTP.2003_7_.20030702111155.3092C@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_bqfqwjAifsCoceXXXCenoQ)"; DIFFERENCES=Content-Language
Content-language: en-USA
Content-transfer-encoding: 8BIT
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



--Boundary_(ID_bqfqwjAifsCoceXXXCenoQ)
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Content-language: en-USA
Content-Transfer-Encoding: QUOTED-PRINTABLE

Talking about interop=85
=20
Are the results of the past interop meetings published somewhere ?
Is there an =93official=94 list of tests ?
When is the next interop meeting ?
=20
Thanks,
=20
Arnaud
=20
-----Original Message-----
From: pregen@egenconsulting.com [mailto:pregen@egenconsulting.com]
Sent: Wednesday, July 02, 2003 9:30 AM
To: ietf-calendar@imc.org
Cc: owner-ietf-calendar@mail.imc.org
Subject: Re: CAP draft - last call, etc.
=20

Yes, I meant all the RFC's.  And yes, if something is mis-interpretted, it
affects a lot of things.  Remember, all three drafts, iCalendar, iTIP and
iMIP were written at different times and by different authors.  So, to say
there may be semantic issues is putting it mildly.  And remember, we are
in interop testing so that we can find these problems and resolve them.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652=20


=20
Doug Royer <Doug@royer.com>=20
Sent by: owner-ietf-calendar@mail.imc.org=20
07/01/2003 23:04=20
Please respond to "ietf-calendar@imc.org"=20
       =20
        To:        "ietf-calendar@imc.org" <ietf-calendar@imc.org>=20
        cc:        =20
        Subject:        Re: CAP draft - last call, etc.





pregen@egenconsulting.com wrote:
>=20
> Doug, I don't believe that Bruce is telling people how he wants it - but=
=20
> rather how he "interprets" the draft.

You mean how he interprets" RFC 2446?

It may effect CUA's that use CAP. But it will effect
any iTIP CUA, it is not limited to CAP.

--=20

 Doug Royer                     |   http://INET-Consulting.com
 -------------------------------|-----------------------------
 Doug@Royer.com                 | Office: (208)612-INET
 http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                |   Cell: (208)520-4044

                We Do Standards - You Need Standards



--Boundary_(ID_bqfqwjAifsCoceXXXCenoQ)
Content-id: 0
Content-type: TEXT/html; CHARSET=iso-8859-1
Content-language: en-USA
Content-Transfer-Encoding: QUOTED-PRINTABLE

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">=
<head><meta name=3DProgId content=3DWord.Document><meta name=3DGenerator co=
ntent=3D"Microsoft Word 9"><meta name=3DOriginator content=3D"Microsoft Wor=
d 9"><link rel=3DFile-List href=3D"cid:filelist.xml@01C3408A.BEE10BB0"><!--=
[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:DoNotRelyOnCSS/>  </o=
:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:Wor=
dDocument>   <w:Zoom>0</w:Zoom>   <w:DocumentKind>DocumentEmail</w:Document=
Kind>   <w:EnvelopeVis/>  </w:WordDocument> </xml><![endif]--><style></styl=
e></head><body lang=3DEN-US style=3D'tab-interval:.5in'><div class=3DSectio=
n1>
   <DIV class=3DMsoNormal> <span class=3DEmailStyle17> <font size=3D2 color=
=3Dnavy face=3DArial> <span style=3D'font-size:10.0pt;mso-bidi-font-size:12=
.0pt;font-family:Arial'>Talking about interop &#8230; <o:p> </o:p> </span> =
</font> </span>  </DIV>   <DIV class=3DMsoNormal> <span class=3DEmailStyle1=
7> <font size=3D2 color=3Dnavy face=3DArial> <span style=3D'font-size:10.0p=
t;mso-bidi-font-size:12.0pt;font-family:Arial'> <![if !supportEmptyParas]> =
&nbsp; <![endif]> <o:p> </o:p> </span> </font> </span>  </DIV>   <DIV class=
=3DMsoNormal> <span class=3DEmailStyle17> <font size=3D2 color=3Dnavy face=
=3DArial> <span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-fa=
mily:Arial'>Are the results of the past interop meetings published somewher=
e ? <o:p> </o:p> </span> </font> </span>  </DIV>   <DIV class=3DMsoNormal> =
<span class=3DEmailStyle17> <font size=3D2 color=3Dnavy face=3DArial> <span=
 style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>Is =
there an  &#8220;official &#8221; list of tests ? <o:p> </o:p> </span> </fo=
nt> </span>  </DIV>   <DIV class=3DMsoNormal> <span class=3DEmailStyle17> <=
font size=3D2 color=3Dnavy face=3DArial> <span style=3D'font-size:10.0pt;ms=
o-bidi-font-size:12.0pt;font-family:Arial'>When is the next interop meeting=
 ? <o:p> </o:p> </span> </font> </span>  </DIV>   <DIV class=3DMsoNormal> <=
span class=3DEmailStyle17> <font size=3D2 color=3Dnavy face=3DArial> <span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'> <![=
if !supportEmptyParas]> &nbsp; <![endif]> <o:p> </o:p> </span> </font> </sp=
an>  </DIV>   <DIV class=3DMsoNormal> <span class=3DEmailStyle17> <font siz=
e=3D2 color=3Dnavy face=3DArial> <span style=3D'font-size:10.0pt;mso-bidi-f=
ont-size:12.0pt;font-family:Arial'>Thanks, <o:p> </o:p> </span> </font> </s=
pan>  </DIV>   <DIV class=3DMsoNormal> <span class=3DEmailStyle17> <font si=
ze=3D2 color=3Dnavy face=3DArial> <span style=3D'font-size:10.0pt;mso-bidi-=
font-size:12.0pt;font-family:Arial'> <![if !supportEmptyParas]> &nbsp; <![e=
ndif]> <o:p> </o:p> </span> </font> </span>  </DIV>   <DIV class=3DMsoNorma=
l> <span class=3DEmailStyle17> <font size=3D2 color=3Dnavy face=3DArial> <s=
pan style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>=
Arnaud <o:p> </o:p> </span> </font> </span>  </DIV>   <DIV class=3DMsoNorma=
l> <span class=3DEmailStyle17> <font size=3D2 color=3Dnavy face=3DArial> <s=
pan style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>=
 <![if !supportEmptyParas]> &nbsp; <![endif]> <o:p> </o:p> </span> </font> =
</span>  </DIV>   <DIV class=3DMsoNormal style=3D'margin-left:.5in'> <font =
size=3D2 color=3Dblack face=3DTahoma> <span style=3D'font-size:10.0pt;font-=
family:Tahoma;color:black'>-----Original Message----- <br>
  <b> <span style=3D'font-weight:bold'>From: </span> </b> pregen@egenconsul=
ting.com [mailto:pregen@egenconsulting.com] <br>
  <b> <span style=3D'font-weight:bold'>Sent: </span> </b> Wednesday, July 0=
2, 2003 9:30 AM <br>
  <b> <span style=3D'font-weight:bold'>To: </span> </b> ietf-calendar@imc.o=
rg <br>
  <b> <span style=3D'font-weight:bold'>Cc: </span> </b> owner-ietf-calendar=
@mail.imc.org <br>
  <b> <span style=3D'font-weight:bold'>Subject: </span> </b> Re: CAP draft =
- last call, etc. </span> </font>  </DIV>   <DIV class=3DMsoNormal style=3D=
'margin-left:.5in'> <font size=3D3 face=3D"Times New Roman"> <span style=3D=
'font-size:12.0pt'> <![if !supportEmptyParas]> &nbsp; <![endif]> <o:p> </o:=
p> </span> </font>  </DIV>   <DIV class=3DMsoNormal style=3D'mso-margin-top=
-alt:0in;margin-right:0in;margin-bottom: 12.0pt;margin-left:.5in'> <font si=
ze=3D3 color=3Dblack face=3D"Times New Roman"> <span style=3D'font-size:12.=
0pt;color:black'> <br>
  </span> </font> <font size=3D2 color=3Dblack face=3Dsans-serif> <span sty=
le=3D'font-size: 10.0pt;font-family:sans-serif;color:black'>Yes, I meant al=
l the RFC's.  &nbsp;And yes, if something is mis-interpretted, it affects a=
 lot of things.  &nbsp;Remember, all three drafts, iCalendar, iTIP and iMIP=
 were written at different times and by different authors.  &nbsp;So, to sa=
y there may be semantic issues is putting it mildly.  &nbsp;And remember, w=
e are in interop testing so that we can find these problems and resolve the=
m. <br>
 ___________________ <br>
 Patricia Egen Consulting <br>
 www.egenconsulting.com <br>
 423-875-2652 </span> </font> <font color=3Dblack> <span style=3D'color:bla=
ck'>  <br style=3D'mso-special-character:line-break'>  <![if !supportLineBr=
eakNewLine]> <br style=3D'mso-special-character:line-break'>  <![endif]> </=
span> </font> <font color=3Dblack> <span style=3D'color:black;mso-color-alt=
: windowtext'> <o:p> </o:p> </span> </font>  </DIV>   <table border=3D0 cel=
lpadding=3D0 width=3D"100%" style=3D'width:100.0%;mso-cellspacing:  1.5pt;m=
argin-left:.5in'>    <tr>     <td valign=3Dtop style=3D'padding:.75pt .75pt=
 .75pt .75pt'>     <DIV class=3DMsoNormal> <![if !supportEmptyParas]> &nbsp=
; <![endif]> <font size=3D3   color=3Dblack face=3D"Times New Roman"> <span=
 style=3D'font-size:12.0pt;color:black;   mso-color-alt:windowtext'> <o:p> =
</o:p> </span> </font>  </DIV>     </td>     <td valign=3Dtop style=3D'padd=
ing:.75pt .75pt .75pt .75pt'>     <DIV class=3DMsoNormal> <b> <font size=3D=
1 color=3Dblack face=3Dsans-serif> <span   style=3D'font-size:7.5pt;font-fa=
mily:sans-serif;color:black;font-weight:bold'>Doug    Royer  &lt;Doug@royer=
.com &gt; </span> </font> </b> <font color=3Dblack> <span   style=3D'color:=
black'>  <br>
     </span> </font> <font size=3D1 color=3Dblack face=3Dsans-serif> <span =
  style=3D'font-size:7.5pt;font-family:sans-serif;color:black'>Sent by:    =
owner-ietf-calendar@mail.imc.org </span> </font> <font color=3Dblack> <span=
   style=3D'color:black'>  </span> </font> <font color=3Dblack> <span style=
=3D'color:black;   mso-color-alt:windowtext'> <o:p> </o:p> </span> </font> =
 </DIV>     <DIV>
 <font size=3D1 color=3Dblack face=3Dsans-serif> <span style=3D'font-size:7=
.5pt;   font-family:sans-serif;color:black'>07/01/2003 23:04 </span> </font=
> <font   color=3Dblack> <span style=3D'color:black'>  <br>
     </span> </font> <font size=3D1 color=3Dblack face=3Dsans-serif> <span =
  style=3D'font-size:7.5pt;font-family:sans-serif;color:black'>Please respo=
nd to     &quot;ietf-calendar@imc.org &quot; </span> </font> <font color=3D=
black> <span   style=3D'color:black'>  </span> </font> <font color=3Dblack>=
 <span style=3D'color:black;   mso-color-alt:windowtext'> <o:p> </o:p> </sp=
an> </font>  </DIV>     </td>     <td valign=3Dtop style=3D'padding:.75pt .=
75pt .75pt .75pt'>     <DIV class=3DMsoNormal> <font size=3D1 color=3Dblack=
 face=3DArial> <span   style=3D'font-size:7.5pt;font-family:Arial;color:bla=
ck'> &nbsp;  &nbsp;  &nbsp;     &nbsp;  </span> </font> <font color=3Dblack=
> <span style=3D'color:black'> <br>
     </span> </font> <font size=3D1 color=3Dblack face=3Dsans-serif> <span =
  style=3D'font-size:7.5pt;font-family:sans-serif;color:black'> &nbsp;  &nb=
sp;  &nbsp;     &nbsp; To:  &nbsp;  &nbsp;  &nbsp;  &nbsp; &quot;ietf-calen=
dar@imc.org &quot;     &lt;ietf-calendar@imc.org &gt; </span> </font> <font=
 color=3Dblack> <span   style=3D'color:black'>  <br>
     </span> </font> <font size=3D1 color=3Dblack face=3Dsans-serif> <span =
  style=3D'font-size:7.5pt;font-family:sans-serif;color:black'> &nbsp;  &nb=
sp;  &nbsp;     &nbsp; cc:  &nbsp;  &nbsp;  &nbsp;  &nbsp; </span> </font> =
<font color=3Dblack> <span   style=3D'color:black'>  <br>
     </span> </font> <font size=3D1 color=3Dblack face=3Dsans-serif> <span =
  style=3D'font-size:7.5pt;font-family:sans-serif;color:black'> &nbsp;  &nb=
sp;  &nbsp;     &nbsp; Subject:  &nbsp;  &nbsp;  &nbsp;  &nbsp;Re: CAP draf=
t - last call, etc. </span> </font> <font   color=3Dblack> <span style=3D'c=
olor:black;mso-color-alt:windowtext'> <o:p> </o:p> </span> </font>  </DIV> =
    </td>    </tr>  </table>   <DIV class=3DMsoNormal style=3D'mso-margin-t=
op-alt:0in;margin-right:0in;margin-bottom: 12.0pt;margin-left:.5in'> <font =
size=3D3 color=3Dblack face=3D"Times New Roman"> <span style=3D'font-size:1=
2.0pt;color:black'> <br>
  <br>
  <br>
  </span> </font> <font size=3D2 color=3Dblack face=3D"Courier New"> <span =
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-family=
:"Courier New"; color:black'> <br>
  <br>
  <tt>pregen@egenconsulting.com wrote: </tt> <br>
  <tt> &gt;  </tt> <br>
  <tt> &gt; Doug, I don't believe that Bruce is telling people how he wants=
 it - but  </tt> <br>
  <tt> &gt; rather how he  &quot;interprets &quot; the draft. </tt> <br>
  <br>
  <tt>You mean how he interprets &quot; RFC 2446? </tt> <br>
  <br>
  <tt>It may effect CUA's that use CAP. But it will effect </tt> <br>
  <tt>any iTIP CUA, it is not limited to CAP. </tt> <br>
  <br>
  <tt>--  </tt> <br>
  <br>
  <tt> &nbsp;Doug Royer  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &n=
bsp;  &nbsp;  &nbsp;  &nbsp; |  &nbsp; http://INET-Consulting.com </tt> <br=
>
  <tt> &nbsp;-------------------------------|----------------------------- =
</tt> <br>
  <tt> &nbsp;Doug@Royer.com  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;=
  &nbsp;  &nbsp; | Office: (208)612-INET </tt> <br>
  <tt> &nbsp;http://Royer.com/People/Doug  &nbsp; |  &nbsp;  &nbsp;Fax: (86=
6)594-8574 </tt> <br>
  <tt> &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbs=
p;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp; |  &nbsp; Cell: =
(208)520-4044 </tt> <br>
  <br>
  <tt> &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp; We Do=
 Standards - You Need Standards </tt> <br style=3D'mso-special-character:li=
ne-break'>  <![if !supportLineBreakNewLine]> <br style=3D'mso-special-chara=
cter:line-break'>  <![endif]> </span> </font> <font color=3Dblack> <span st=
yle=3D'color:black;mso-color-alt: windowtext'> <o:p> </o:p> </span> </font>=
  </DIV>   </div>
   </body>   </html>=

--Boundary_(ID_bqfqwjAifsCoceXXXCenoQ)--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 14:23:53 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05336
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 14:23:52 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62IDKFK074818
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 11:13:20 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62IDKXm074817
	for ietf-calendar-bks; Wed, 2 Jul 2003 11:13:20 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62IDJFK074812
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 11:13:19 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h62IDHOR011930
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 11:13:20 -0700
Message-ID: <3F0320B8.3060004@Royer.com>
Date: Wed, 02 Jul 2003 12:13:12 -0600
From: Doug Royer <Doug@Royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: INTEROP testing results - [was: CAP draft - last call, etc.]
References: <OF2EB0CAF2.F6DFE5B1-ON85256D57.005FFFB1-85256D57.00601E3D@egenconsulting.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090606060309040505070704"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms090606060309040505070704
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Your email brings up a good point.

If someone found a problem as has been claimed, it is NOT in
the interoperability testing reports on www.calsch.org .

Is there some other list of interoperability testing that
has been published? Then it would be easier to have a fact based
debate where the results or problems are documented and not just
declared.

pregen@egenconsulting.com wrote:
> 
> Yes, I meant all the RFC's.  And yes, if something is mis-interpretted, 
> it affects a lot of things.  Remember, all three drafts, iCalendar, iTIP 
> and iMIP were written at different times and by different authors.  So, 
> to say there may be semantic issues is putting it mildly.  And remember, 
> we are in interop testing so that we can find these problems and resolve 
> them.
>
-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms090606060309040505070704
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIxODEzMTJaMCMGCSqGSIb3DQEJBDEWBBQV
79DV8oApZciS3SbzqP3sd/OnZjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAE2HW40LyYC6K
TXMGSWT3UbRM5tYT5yaPIW/bFWBIcYUuIxJh+OBdd5gWX5vfAVFhi4E7TJsYsXQSImkVr2Ya
qaSHWL+Wphk9yEtS3IUwRt3r763wgC4wJ/urHQNpL9KrVrKgeQJ4PAJ/g3uhiI9YlgCTpds/
II3HGzuLxJvLwIrz+KVLVqSC8+H7z7kfzh8b2znZP9Uxnup8tDo8g+Pxl6YXq5A9nxobqe3b
AwoKbrNL0E/Ym0Z9khX9ekfQWDxJ3ROHas7IMV1jWqWkEEyWPo06nhCMwApYO2/GUsA1/hYp
EqT2el2CbnIJvB3kbA2tTob8Bz8T/QOR0a3QklY88AAAAAAAAA==
--------------ms090606060309040505070704--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 14:44:33 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05837
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 14:44:33 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62IWIFK076083
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 11:32:18 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62IWIVf076082
	for ietf-calendar-bks; Wed, 2 Jul 2003 11:32:18 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62IWHFK076073
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 11:32:18 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <20030612192905.M32638@asitturnsout.org>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF522DC1B6.F33F37BD-ON85256D57.0063A06E-85256D57.00657D3A@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Wed, 2 Jul 2003 14:28:03 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/02/2003
 02:32:03 PM,
	Serialize complete at 07/02/2003 02:32:03 PM
Content-Type: multipart/alternative; boundary="=_alternative 00657D3685256D57_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 00657D3685256D57_=
Content-Type: text/plain; charset="US-ASCII"

Chris wrote on 06/12/2003 04:28:45 PM:
>              I believe that "the most recent version" is the correct 
answer.
> My reasoning is that while RECURRENCE-ID is, if present, part of the 
primary
> key to use in finding an instance, it is only valid when used in 
relation to
> the correct version of the object in question.

I refer to the SEQUENCE:0 RECURRENCE-ID since so far no shipping C&S 
products that do C&S support ADD add or do a good job of 'changing the 
repeat set' so as such they are always '0' based.  There is no SEQUENCE:0 
for an ADDed instance and so far the discussions were foucsed around the 
most common and basic model of invitations and reschedules to the initial 
set.  This is by far the most common set of actions performed in C&S and 
thus relevant to the discussions here.  It is of no value to discuss less 
common paths if they do not work for the more common ones.  Solutions that 
work only for the 20 in the 80/20 rule are of little value to the larger 
80...

Chris seems to espouse a fixed RECURRENCE-ID as being necessary to key to 
the instance (ala UID for finding the set) but then says that a changing 
RID is the way to go.  Its simple to show that its NOT possible to resync 
a particular instance of the set if even 1 reschedule is missed. 

Doug has claimed it can be resyncd and his answer is a "full REFRESH". 
Putting asside the semantic oddities (Organiers do not issue REFRESHes, 
they respond to them), Doug has actually tacitly agreed that a specific 
instance resync is not possible; the entire set must be resync for this 
model to recover.  An expensive proposition for a single missed REQUEST 
(esp. given the "small footprint" preferances of some who like this "send 
it all again" model) by resending the current 'base' defintion plus all 
the current individual instances (esp. if only 1 instance needed to be 
resync'd!).

However, in taking a step back I think that the key to this is a phrase 
that seems to have been misinterpreted by some and misunderstood by 
others.  Doug and George have cited the following as the basis for 
claiming a changing RECURRENCE-ID model:

                                   For a given pair of "UID" and
   "SEQUENCE" property values, the "RECURRENCE-ID" value for a
   recurrence instance is fixed. When the definition of the recurrence
   set for a calendar component changes, and hence the "SEQUENCE"
   property value changes, the "RECURRENCE-ID" for a given recurrence
   instance might also change.

The operative phrase here is "definition of the recurrence set for a 
calendar component changes".  This means when the entrys repeat _set_ 
changes from "Every Monday for 5 weeks" to "Every Thursday and Friday for 
3 months", NOT "When the individual instance is rescheduled to a different 
date/time." 

When an instance itself is rescheduled, its RECURRENCE-ID _does_not_change
_.  This _is_ coherent w/the paragraph previous to the citation in 2445 
and w/the message sequencing and method interpreation sections in iTIP 
because it means the UID/RECURRENCE-ID values do not change with each 
reschedule.  As such a single (or 100) missed reschedules (or CANCELs, 
etc) can be safely ignored and no "full REFRESH" or full resyncs are 
necessary. 

> Please help me understand if this model is broken, and if so, how.

Before we go further I think that its important to realize that the cited 
text for why RECURRENCE-IDs change has been misunderstood/misread by some 
as meaning the RECURRENCE-ID changes whenever the instance is rescheduled. 
 Once we all grasp that it does NOT say that a rescheduling an instance 
means RECURRENCE-ID changes then we can revisit any other confusion folks 
have.  Sound ok??

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 00657D3685256D57_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Chris wrote on 06/12/2003 04:28:45 PM:<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;I believe that &quot;the
most recent version&quot; is the correct answer.<br>
&gt; My reasoning is that while RECURRENCE-ID is, if present, part of the
primary<br>
&gt; key to use in finding an instance, it is only valid when used in relation
to<br>
&gt; the correct version of the object in question.<br>
</tt></font>
<br><font size=2 face="sans-serif">I refer to the SEQUENCE:0 RECURRENCE-ID
since so far no shipping C&amp;S products that do C&amp;S support ADD add
or do a good job of 'changing the repeat set' so as such they are always
'0' based. &nbsp;There is no SEQUENCE:0 for an ADDed instance and so far
the discussions were foucsed around the most common and basic model of
invitations and reschedules to the initial set. &nbsp;This is by far the
most common set of actions performed in C&amp;S and thus relevant to the
discussions here. &nbsp;It is of no value to discuss less common paths
if they do not work for the more common ones. &nbsp;Solutions that work
only for the 20 in the 80/20 rule are of little value to the larger 80...</font>
<br>
<br><font size=2 face="sans-serif">Chris seems to espouse a fixed RECURRENCE-ID
as being necessary to key to the instance (ala UID for finding the set)
but then says that a changing RID is the way to go. &nbsp;Its simple to
show that its NOT possible to resync a particular instance of the set if
even 1 reschedule is missed. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Doug has claimed it can be resyncd and
his answer is a &quot;full REFRESH&quot;. &nbsp;Putting asside the semantic
oddities (Organiers do not issue REFRESHes, they respond to them), Doug
has actually tacitly agreed that a specific instance resync is not possible;
the entire set must be resync for this model to recover. &nbsp;An expensive
proposition for a single missed REQUEST (esp. given the &quot;small footprint&quot;
preferances of some who like this &quot;send it all again&quot; model)
by resending the current 'base' defintion plus all the current individual
instances (esp. if only 1 instance needed to be resync'd!).</font>
<br>
<br><font size=2 face="sans-serif">However, in taking a step back I think
that the key to this is a phrase that seems to have been misinterpreted
by some and misunderstood by others. &nbsp;Doug and George have cited the
following as the basis for claiming a changing RECURRENCE-ID model:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;For
a given pair of &quot;UID&quot; and<br>
 &nbsp; &quot;SEQUENCE&quot; property values, the &quot;RECURRENCE-ID&quot;
value for a<br>
 &nbsp; recurrence instance is fixed. When the definition of the recurrence<br>
 &nbsp; set for a calendar component changes, and hence the &quot;SEQUENCE&quot;<br>
 &nbsp; property value changes, the &quot;RECURRENCE-ID&quot; for a given
recurrence<br>
 &nbsp; instance might also change.</tt></font>
<br>
<br><font size=2 face="sans-serif">The operative phrase here is &quot;definition
of the recurrence set for a calendar component changes&quot;. &nbsp;This
means when the entrys repeat _<u>set</u>_ changes from &quot;Every Monday
for 5 weeks&quot; to &quot;Every Thursday and Friday for 3 months&quot;,
NOT &quot;When the individual instance is rescheduled to a different date/time.&quot;
&nbsp;</font>
<br>
<br><font size=2 face="sans-serif">When an instance itself is rescheduled,
its RECURRENCE-ID _<u>does_not_change</u>_. &nbsp;This _is_ coherent w/the
paragraph previous to the citation in 2445 and w/the message sequencing
and method interpreation sections in iTIP because it means the UID/RECURRENCE-ID
values do not change with each reschedule. &nbsp;As such a single (or 100)
missed reschedules (or CANCELs, etc) can be safely ignored and no &quot;full
REFRESH&quot; or full resyncs are necessary. &nbsp;</font>
<br>
<br><font size=2><tt>&gt; Please help me understand if this model is broken,
and if so, how.<br>
</tt></font>
<br><font size=2 face="sans-serif">Before we go further I think that its
important to realize that the cited text for why RECURRENCE-IDs change
has been misunderstood/misread by some as meaning the RECURRENCE-ID changes
whenever the instance is rescheduled. &nbsp;Once we all grasp that it does
NOT say that a rescheduling an instance means RECURRENCE-ID changes then
we can revisit any other confusion folks have. &nbsp;Sound ok??</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 00657D3685256D57_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 14:56:28 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06190
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 14:56:27 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62IixFK076805
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 11:44:59 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62IixOF076804
	for ietf-calendar-bks; Wed, 2 Jul 2003 11:44:59 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62IiwFK076798
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 11:44:58 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <20030612192905.M32638@asitturnsout.org>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF02C713BD.6E90AA99-ON85256D57.0065B2C7-85256D57.0066A662@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Wed, 2 Jul 2003 14:40:43 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/02/2003
 02:44:43 PM,
	Serialize complete at 07/02/2003 02:44:43 PM
Content-Type: multipart/alternative; boundary="=_alternative 0066A65D85256D57_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0066A65D85256D57_=
Content-Type: text/plain; charset="US-ASCII"

Chris wrote on 06/12/2003 04:28:45 PM:
> > > If later the SEQUENCE gets updated again, the ORGANIZER would send
> > > the SEQUENCE:<next> object and the CUAs REPLY.
> > 
> > This does not address how the CUA would match the changed RECURRENCE-
> > ID to the correct instance in the set.  If the RECURRENCE-ID changed 
> > at each change of SEQUENCE as you claim then the CUA can only 
> > process the latest REQUEST if they have _all_ of the previous 
> > REQUESTs too so they can say "RECURRENCE-ID changes to Wednesday for 
> > SEQUENCE:1.  Now it changes to Thursday for SEQUENCE:2.  Finally it 
> > changes to Friday for SEQUENCE:3". If ANY of the REQUESTs between 
> > SEQUENCE:0 and SEQUENCE:3 are missing then its not possible to 
> > properly determine which Friday instance the Organizer is referring 
> > to.  Right?
> 
> Wrong.  If I got SEQUENCE:0, and then SEQUENCE:3 for UID:xyzzy, I would 
ask
> for a REFRESH of UID:xyzzy, and defer processing until I got SEQUENCE:3 
(or
> greater, but then the SEQUENCE:3 data would be discarded). 

Huh?  If you just got a UID:xyzzy, SEQUENCE:3 REQUEST you would send a 
REFRESH to the Organzier who would send you the SAME REQUEST back which 
you would then process?  If you get the same (or a higher) REQUEST in 
response to the REFRESH then what have you learned new?  Nothing?  If you 
can act on the 2nd REQUEST w/the exact same info (assuming SEQUENCE:3 
here) then why couldnt you act on the 1st REQUEST?  Sorry but I must be 
missing something here...

Since rescheduling an individual instance means changing its SEQUENCE 
value then by using UID then SEQUENCE you effectively tie all instances to 
a single SEQUENCE value.  Surely you did not mean for that to happen.  If 
so, do you realize that it means rescheduling 1 instance means that you 
invalidate all the workflow to all other instances even though they have 
not changed??

Doug is saying that RECURRNECE-ID changes with _each_ reschedule of the 
instance.  Chris seems to agree w/him but  some of the the stuff he 
describes sounds like a fixed RECURRENCE-ID that can be used as like a key 
to find the instance once you "know the SEQUENCE" (my term, not Chriss') 
so you can do workflow on the instances.  Thats not possible with SEQUENCE 
since thats not the meaning of SEQUENCE.

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 0066A65D85256D57_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Chris wrote on 06/12/2003 04:28:45 PM:<br>
&gt; &gt; &gt; If later the SEQUENCE gets updated again, the ORGANIZER
would send<br>
&gt; &gt; &gt; the SEQUENCE:&lt;next&gt; object and the CUAs REPLY.<br>
&gt; &gt; <br>
&gt; &gt; This does not address how the CUA would match the changed RECURRENCE-<br>
&gt; &gt; ID to the correct instance in the set. &nbsp;If the RECURRENCE-ID
changed <br>
&gt; &gt; at each change of SEQUENCE as you claim then the CUA can only
<br>
&gt; &gt; process the latest REQUEST if they have _all_ of the previous
<br>
&gt; &gt; REQUESTs too so they can say &quot;RECURRENCE-ID changes to Wednesday
for <br>
&gt; &gt; SEQUENCE:1. &nbsp;Now it changes to Thursday for SEQUENCE:2.
&nbsp;Finally it <br>
&gt; &gt; changes to Friday for SEQUENCE:3&quot;. If ANY of the REQUESTs
between <br>
&gt; &gt; SEQUENCE:0 and SEQUENCE:3 are missing then its not possible to
<br>
&gt; &gt; properly determine which Friday instance the Organizer is referring
<br>
&gt; &gt; to. &nbsp;Right?<br>
&gt; <br>
&gt; Wrong. &nbsp;If I got SEQUENCE:0, and then SEQUENCE:3 for UID:xyzzy,
I would ask<br>
&gt; for a REFRESH of UID:xyzzy, and defer processing until I got SEQUENCE:3
(or<br>
&gt; greater, but then the SEQUENCE:3 data would be discarded). </tt></font>
<br>
<br><font size=2 face="sans-serif">Huh? &nbsp;If you just got a UID:xyzzy,
SEQUENCE:3 REQUEST you would send a REFRESH to the Organzier who would
send you the SAME REQUEST back which you would then process? &nbsp;If you
get the same (or a higher) REQUEST in response to the REFRESH then what
have you learned new? &nbsp;Nothing? &nbsp;If you can act on the 2nd REQUEST
w/the exact same info (assuming SEQUENCE:3 here) then why couldnt you act
on the 1st REQUEST? &nbsp;Sorry but I must be missing something here...</font>
<br>
<br><font size=2 face="sans-serif">Since rescheduling an individual instance
means changing its SEQUENCE value then by using UID then SEQUENCE you effectively
tie all instances to a single SEQUENCE value. &nbsp;Surely you did not
mean for that to happen. &nbsp;If so, do you realize that it means rescheduling
1 instance means that you invalidate all the workflow to all other instances
even though they have not changed??</font>
<br>
<br><font size=2 face="sans-serif">Doug is saying that RECURRNECE-ID changes
with _each_ reschedule of the instance. &nbsp;Chris seems to agree w/him
but &nbsp;some of the the stuff he describes sounds like a fixed RECURRENCE-ID
that can be used as like a key to find the instance once you &quot;know
the SEQUENCE&quot; (my term, not Chriss') so you can do workflow on the
instances. &nbsp;Thats not possible with SEQUENCE since thats not the meaning
of SEQUENCE.</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 0066A65D85256D57_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 15:18:02 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08242
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 15:18:02 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62J4TFK079010
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 12:04:29 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62J4Tnl079009
	for ietf-calendar-bks; Wed, 2 Jul 2003 12:04:29 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62J4SFK079001
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 12:04:28 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3EE8E6A7.8010301@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF072754A7.CEF06BC7-ON85256D57.0066B321-85256D57.00687063@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Wed, 2 Jul 2003 15:00:16 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/02/2003
 03:04:12 PM,
	Serialize complete at 07/02/2003 03:04:12 PM
Content-Type: multipart/alternative; boundary="=_alternative 0068705E85256D57_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0068705E85256D57_=
Content-Type: text/plain; charset="US-ASCII"

Doug wrote on 06/12/2003 04:46:31 PM:
> > You can easily if the RECURRENCE-ID never changes. 
> 
> 1) Unless you do not have it because you joined the event
>     after SEQUENCE:0 was obsoleted.

Not true.  Per iTIP, Section 3.2.2 REQUEST:

   The "UID" and "SEQUENCE" properties are used to distinguish the
   various uses of the "REQUEST" method. If the "UID" property value in
   the "REQUEST" is not found on the recipient's calendar, then the
   "REQUEST" is for a new "VEVENT" calendar component. If the "UID"
   property value is found on the recipient's calendar, then the
   "REQUEST" is for a rescheduling, an update, or a reconfirm of the
   "VEVENT" calendar component.

In this case the REQUEST is for an unknown UID/RECURRENCE-ID and thus its 
a new invitation to a particular instance.  Thats exactly why we allow 
sending RECURRENCE-IDs in the REQUESTs; so particular instances can be 
consistantly and accurately identified and referenced and workflow for 
each instance can occur independent of the workflow on other instances in 
the set.

> 2) Unless NONE of the current instances match up to ANY
>     of the original instances.

"Original instances" = what??  I dont want to misinterpret this...

In the "delta" model it only takes 5 steps to misidentify once instance 
for another as I demonstrated 3 weeks ago.  And thats _without_ changing 
the set!!!!

> You do not have to SYNC - simply do a REFRESH and get the latest object
> version.

I said 'resync', not SYNC (a new METHOD?).  You also seem to agree that 
its impossible to resync a particular instance if you miss 1 rescheduling 
REQUEST in your model; you MUST resync ALL instances in the set!  After 
all thats what a REFRESH w/o a RECURRENCE-ID does, it resends a 'base' 
definition and then you MUST follow it with the current individual 
instance definitions since they realistically wont share the same attendee 
list, agenda, ATTACHments and other details.  However your assumption 
seems to be that all instances share the same SEQUENCE value (they MUST 
for the 'base' defintion to be useful/accurate).  Still though Ive asked 
for more info on this to be sure and I haven't seen any yet.

So far Ive been talking about the case where we are simply doing workflow 
on the original set of instances.  Despite what Doug may claim, 2445 is 
not ambiguous about RECURRENCE-IDs value for this.  It clearly says:

   The date/time value is set to the time when the original recurrence
   instance would occur; meaning that if the intent is to change a
   Friday meeting to Thursday, the date/time is still set to the
   original Friday meeting.

   The "RECURRENCE-ID" property is used in conjunction with the "UID"
   and "SEQUENCE" property to identify a particular instance of a
   recurring event, to-do or journal. For a given pair of "UID" and
   "SEQUENCE" property values, the "RECURRENCE-ID" value for a
   recurrence instance is fixed. When the definition of the recurrence
   set for a calendar component changes, and hence the "SEQUENCE"
   property value changes, the "RECURRENCE-ID" for a given recurrence
   instance might also change.

The 1st paragraph clearly says that the value does not change when the 
instance moves to a different date (and time too really).  The entire 
justification for this "delta" model of RECURRENCE-ID has been the 
highlighted line in the 2nd paragraph.  However if you read it accurately 
it clearly says "recurrence set for a calendar compoennt changes" meaning 
that the set gets changes; NOT the instance gets changed!

A set change is "Every Monday for 5 weeks" to "Every Monday and Friday for 
3 months"; NOT "Lets move the 2nd instance back 3 hours".  At the time we 
wrote that noone was doing set changes and so noone worked thru all the 
scenarios; much like the multipart issues with some CUAs...

So despite claims to the contrary I think some folks have misinterpreted 
"recurrence set... changes" as meaning "instance reschedules" and that has 
lead to the rest of this discussion.  If you take a technical look at the 
basic cases where we are not changing the set then it should be pretty 
clear why RECURRENCE-ID must stay fixed.  Id like to reach a conclusion 
for this before we digress totally into "Well I can change the set to XXX 
instead of YYY so..." or "What about method Z vs Q..." discussion since 
this set changes are much more the exception than the rule.

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...
Warning: Dates in Calendar are closer than they appear.


--=_alternative 0068705E85256D57_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug wrote on 06/12/2003 04:46:31 PM:<br>
&gt; &gt; You can easily if the RECURRENCE-ID never changes. &nbsp;<br>
&gt; <br>
&gt; 1) Unless you do not have it because you joined the event<br>
&gt; &nbsp; &nbsp; after SEQUENCE:0 was obsoleted.<br>
</tt></font>
<br><font size=2 face="sans-serif">Not true. &nbsp;Per iTIP, Section 3.2.2
REQUEST:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The &quot;UID&quot; and &quot;SEQUENCE&quot;
properties are used to distinguish the<br>
 &nbsp; various uses of the &quot;REQUEST&quot; method. If the &quot;UID&quot;
property value in<br>
 &nbsp; the &quot;REQUEST&quot; is not found on the recipient's calendar,
then the<br>
 &nbsp; &quot;REQUEST&quot; is for a new &quot;VEVENT&quot; calendar component.
If the &quot;UID&quot;<br>
 &nbsp; property value is found on the recipient's calendar, then the<br>
 &nbsp; &quot;REQUEST&quot; is for a rescheduling, an update, or a reconfirm
of the<br>
 &nbsp; &quot;VEVENT&quot; calendar component.</tt></font>
<br>
<br><font size=2 face="sans-serif">In this case the REQUEST is for an unknown
UID/RECURRENCE-ID and thus its a new invitation to a particular instance.
&nbsp;Thats exactly why we allow sending RECURRENCE-IDs in the REQUESTs;
so particular instances can be consistantly and accurately identified and
referenced and workflow for each instance can occur independent of the
workflow on other instances in the set.</font>
<br>
<br><font size=2><tt>&gt; 2) Unless NONE of the current instances match
up to ANY<br>
&gt; &nbsp; &nbsp; of the original instances.<br>
</tt></font>
<br><font size=2 face="sans-serif">&quot;Original instances&quot; = what??
&nbsp;I dont want to misinterpret this...</font>
<br>
<br><font size=2 face="sans-serif">In the &quot;delta&quot; model it only
takes 5 steps to misidentify once instance for another as I demonstrated
3 weeks ago. &nbsp;And thats _without_ changing the set!!!!</font>
<br>
<br><font size=2><tt>&gt; You do not have to SYNC - simply do a REFRESH
and get the latest object<br>
&gt; version.<br>
</tt></font>
<br><font size=2 face="sans-serif">I said 'resync', not SYNC (a new METHOD?).
&nbsp;You also seem to agree that its impossible to resync a particular
instance if you miss 1 rescheduling REQUEST in your model; you MUST resync
ALL instances in the set! &nbsp;After all thats what a REFRESH w/o a RECURRENCE-ID
does, it resends a 'base' definition and then you MUST follow it with the
current individual instance definitions since they realistically wont share
the same attendee list, agenda, ATTACHments and other details. &nbsp;However
your assumption seems to be that all instances share the same SEQUENCE
value (they MUST for the 'base' defintion to be useful/accurate). &nbsp;Still
though Ive asked for more info on this to be sure and I haven't seen any
yet.</font>
<br>
<br><font size=2 face="sans-serif">So far Ive been talking about the case
where we are simply doing workflow on the original set of instances. &nbsp;Despite
what Doug may claim, 2445 is not ambiguous about RECURRENCE-IDs value for
this. &nbsp;It clearly says:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The date/time value is set to the time
when the original recurrence<br>
 &nbsp; instance would occur; meaning that if the intent is to change a<br>
 &nbsp; Friday meeting to Thursday, the date/time is still set to the<br>
 &nbsp; original Friday meeting.<br>
<br>
 &nbsp; The &quot;RECURRENCE-ID&quot; property is used in conjunction with
the &quot;UID&quot;<br>
 &nbsp; and &quot;SEQUENCE&quot; property to identify a particular instance
of a<br>
 &nbsp; recurring event, to-do or journal. For a given pair of &quot;UID&quot;
and<br>
 &nbsp; &quot;SEQUENCE&quot; property values, the &quot;RECURRENCE-ID&quot;
value for a<br>
 &nbsp; recurrence instance is fixed. <b>When the definition of the recurrence<br>
 &nbsp; set for a calendar component changes, and hence the &quot;SEQUENCE&quot;<br>
 &nbsp; property value changes, the &quot;RECURRENCE-ID&quot; for a given
recurrence<br>
 &nbsp; instance might also change.</b></tt></font>
<br>
<br><font size=2 face="sans-serif">The 1st paragraph clearly says that
the value does not change when the instance moves to a different date (and
time too really). &nbsp;The entire justification for this &quot;delta&quot;
model of RECURRENCE-ID has been the highlighted line in the 2nd paragraph.
&nbsp;However if you read it accurately it clearly says &quot;recurrence
set for a calendar compoennt changes&quot; meaning that the set gets changes;
NOT the instance gets changed!</font>
<br>
<br><font size=2 face="sans-serif">A set change is &quot;Every Monday for
5 weeks&quot; to &quot;Every Monday and Friday for 3 months&quot;; NOT
&quot;Lets move the 2nd instance back 3 hours&quot;. &nbsp;At the time
we wrote that noone was doing set changes and so noone worked thru all
the scenarios; much like the multipart issues with some CUAs...</font>
<br>
<br><font size=2 face="sans-serif">So despite claims to the contrary I
think some folks have misinterpreted &quot;recurrence set... changes&quot;
as meaning &quot;instance reschedules&quot; and that has lead to the rest
of this discussion. &nbsp;If you take a technical look at the basic cases
where we are not changing the set then it should be pretty clear why RECURRENCE-ID
must stay fixed. &nbsp;Id like to reach a conclusion for this before we
digress totally into &quot;Well I can change the set to XXX instead of
YYY so...&quot; or &quot;What about method Z vs Q...&quot; discussion since
this set changes are much more the exception than the rule.</font>
<br><font size=2 face="sans-serif"><br>
Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...<br>
Warning: Dates in Calendar are closer than they appear.</font>
<br>
<br>
--=_alternative 0068705E85256D57_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 15:24:45 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08578
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 15:24:44 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62JCdFK079547
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 12:12:39 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62JCdNH079546
	for ietf-calendar-bks; Wed, 2 Jul 2003 12:12:39 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62JCdFK079530
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 12:12:39 -0700 (PDT)
	(envelope-from arnaud.quillaud@sun.com)
Received: from dm-usca19-13.red.iplanet.com (host-179-56-18-192.iplanet.com [192.18.56.179] (may be forged))
	by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h62JCZKo002428;
	Wed, 2 Jul 2003 12:12:35 -0700 (PDT)
Received: from gotmail-2.red.iplanet.com (gotmail-2.red.iplanet.com [192.18.73.252])
	by dm-usca19-13.red.iplanet.com (8.11.7+Sun/8.10.2/IPLANET,v1.2) with ESMTP id h62JBvJ01409;
	Wed, 2 Jul 2003 12:11:57 -0700 (PDT)
Received: from lamachine (vpn-129-150-17-197.SFBay.Sun.COM [129.150.17.197])
 by we-gotmail.red.iplanet.com
 (Sun ONE Messaging Server 6.0 (built Jun 26 2003))
 with ESMTP id <0HHE00L7FW0Y0I30@we-gotmail.red.iplanet.com>; Wed,
 02 Jul 2003 12:12:35 -0700 (PDT)
Date: Wed, 02 Jul 2003 12:14:44 -0700
From: Arnaud Quillaud <arnaud.quillaud@sun.com>
Subject: RE: Correct handling of Recurrence-id
To: "Bruce_Kahn@notesdev.ibm.com" <Bruce_Kahn@notesdev.ibm.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_7_.20030702121444.572C@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_2xi+cP/g5rIPki+vcAth/A)"; DIFFERENCES=Content-Language
Content-language: en-USA
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



--Boundary_(ID_2xi+cP/g5rIPki+vcAth/A)
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

 
-----Original Message-----
From: Bruce_Kahn@notesdev.ibm.com [mailto:Bruce_Kahn@notesdev.ibm.com]
Sent: Wednesday, July 02, 2003 10:28 AM
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
 
 
However, in taking a step back I think that the key to this is a phrase
that seems to have been misinterpreted by some and misunderstood by
others.  Doug and George have cited the following as the basis for
claiming a changing RECURRENCE-ID model: 

                                   For a given pair of "UID" and
  "SEQUENCE" property values, the "RECURRENCE-ID" value for a
  recurrence instance is fixed. When the definition of the recurrence
  set for a calendar component changes, and hence the "SEQUENCE"
  property value changes, the "RECURRENCE-ID" for a given recurrence
  instance might also change. 

The operative phrase here is "definition of the recurrence set for a
calendar component changes".  This means when the entrys repeat _set_
changes from "Every Monday for 5 weeks" to "Every Thursday and Friday for
3 months", NOT "When the individual instance is rescheduled to a different
date/time."   

When an instance itself is rescheduled, its RECURRENCE-ID
_does_not_change_.  This _is_ coherent w/the paragraph previous to the
citation in 2445 and w/the message sequencing and method interpreation
sections in iTIP because it means the UID/RECURRENCE-ID values do not
change with each reschedule.  As such a single (or 100) missed reschedules
(or CANCELs, etc) can be safely ignored and no "full REFRESH" or full
resyncs are necessary.   
 
 
This makes a lot of sense I think.
 
Arnaud

--Boundary_(ID_2xi+cP/g5rIPki+vcAth/A)
Content-id: 0
Content-type: TEXT/html; CHARSET=iso-8859-1
Content-language: en-USA
Content-Transfer-Encoding: QUOTED-PRINTABLE

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">=
<head><meta name=3DProgId content=3DWord.Document><meta name=3DGenerator co=
ntent=3D"Microsoft Word 9"><meta name=3DOriginator content=3D"Microsoft Wor=
d 9"><link rel=3DFile-List href=3D"cid:filelist.xml@01C34093.852EC1B0"><!--=
[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:DoNotRelyOnCSS/>  </o=
:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:Wor=
dDocument>   <w:Zoom>0</w:Zoom>   <w:DocumentKind>DocumentEmail</w:Document=
Kind>   <w:EnvelopeVis/>  </w:WordDocument> </xml><![endif]--><style></styl=
e></head><body lang=3DEN-US style=3D'tab-interval:.5in'><div class=3DSectio=
n1>
   <DIV class=3DMsoNormal> <span class=3DEmailStyle16> <font size=3D2 color=
=3Dnavy face=3DArial> <span style=3D'font-size:10.0pt;mso-bidi-font-size:12=
.0pt;font-family:Arial'> <![if !supportEmptyParas]> &nbsp; <![endif]> <o:p>=
 </o:p> </span> </font> </span>  </DIV>   <DIV class=3DMsoNormal style=3D'm=
argin-left:.5in'> <font size=3D2 color=3Dblack face=3DTahoma> <span style=
=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original Message-=
---- <br>
  <b> <span style=3D'font-weight:bold'>From: </span> </b> Bruce_Kahn@notesd=
ev.ibm.com [mailto:Bruce_Kahn@notesdev.ibm.com] <br>
  <b> <span style=3D'font-weight:bold'>Sent: </span> </b> Wednesday, July 0=
2, 2003 10:28 AM <br>
  <b> <span style=3D'font-weight:bold'>To: </span> </b> ietf-calendar@imc.o=
rg <br>
  <b> <span style=3D'font-weight:bold'>Subject: </span> </b> Re: Correct ha=
ndling of Recurrence-id </span> </font>  </DIV>   <DIV class=3DMsoNormal st=
yle=3D'margin-left:.5in'> <tt> <font size=3D2 color=3Dnavy face=3D"Courier =
New"> <span style=3D'font-size:10.0pt;font-family:"Courier New"; color:navy=
'> <![if !supportEmptyParas]> &nbsp; <![endif]> </span> </font> </tt> <tt> =
<font size=3D2 color=3Dnavy face=3D"Courier New"> <span style=3D'font-size:=
10.0pt;font-family: "Courier New";color:navy;mso-color-alt:windowtext'> <o:=
p> </o:p> </span> </font> </tt>  </DIV>   <DIV class=3DMsoNormal> <span cla=
ss=3DEmailStyle16> <font size=3D2 color=3Dnavy face=3DArial> <span style=3D=
'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'> <![if !supp=
ortEmptyParas]> &nbsp; <![endif]> <o:p> </o:p> </span> </font> </span>  </D=
IV>   <DIV class=3DMsoNormal style=3D'margin-left:.5in'> <font size=3D2 col=
or=3Dblack face=3Dsans-serif> <span style=3D'font-size:10.0pt;font-family:s=
ans-serif; color:black'>However, in taking a step back I think that the key=
 to this is a phrase that seems to have been misinterpreted by some and mis=
understood by others.  &nbsp;Doug and George have cited the following as th=
e basis for claiming a changing RECURRENCE-ID model: </span> </font> <font =
color=3Dblack> <span style=3D'color:black'>  <br>
  <br>
  </span> </font> <tt> <font size=3D2 color=3Dblack face=3D"Courier New"> <=
span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'> &nbs=
p;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp; =
 &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;  &nbsp;For a given =
pair of  &quot;UID &quot; and </span> </font> </tt> <font size=3D2 color=3D=
black face=3D"Courier New"> <span style=3D'font-size:10.0pt;font-family: "C=
ourier New";mso-fareast-font-family:"Courier New";color:black'> <br>
  <tt> &nbsp;  &quot;SEQUENCE &quot; property values, the  &quot;RECURRENCE=
-ID &quot; value for a </tt> <br>
  <tt> &nbsp; recurrence instance is fixed. When the definition of the recu=
rrence </tt> <br>
  <tt> &nbsp; set for a calendar component changes, and hence the  &quot;SE=
QUENCE &quot; </tt> <br>
  <tt> &nbsp; property value changes, the  &quot;RECURRENCE-ID &quot; for a=
 given recurrence </tt> <br>
  <tt> &nbsp; instance might also change. </tt> </span> </font> <font color=
=3Dblack> <span style=3D'color:black'>  <br>
  <br>
  </span> </font> <font size=3D2 color=3Dblack face=3Dsans-serif> <span sty=
le=3D'font-size: 10.0pt;font-family:sans-serif;color:black'>The operative p=
hrase here is  &quot;definition of the recurrence set for a calendar compon=
ent changes &quot;.  &nbsp;This means when the entrys repeat _ <u>set </u>_=
 changes from  &quot;Every Monday for 5 weeks &quot; to  &quot;Every Thursd=
ay and Friday for 3 months &quot;, NOT  &quot;When the individual instance =
is rescheduled to a different date/time. &quot;  &nbsp; </span> </font> <fo=
nt color=3Dblack> <span style=3D'color:black'>  <br>
  <br>
  </span> </font> <font size=3D2 color=3Dblack face=3Dsans-serif> <span sty=
le=3D'font-size: 10.0pt;font-family:sans-serif;color:black'>When an instanc=
e itself is rescheduled, its RECURRENCE-ID _ <u>does_not_change </u>_.  &nb=
sp;This _is_ coherent w/the paragraph previous to the citation in 2445 and =
w/the message sequencing and method interpreation sections in iTIP because =
it means the UID/RECURRENCE-ID values do not change with each reschedule.  =
&nbsp;As such a single (or 100) missed reschedules (or CANCELs, etc) can be=
 safely ignored and no  &quot;full REFRESH &quot; or full resyncs are neces=
sary.  &nbsp; </span> </font> <font color=3Dblack> <span style=3D'color:bla=
ck'>  </span> </font> <font color=3Dnavy> <span style=3D'color:navy;mso-col=
or-alt:windowtext'> <o:p> </o:p> </span> </font>  </DIV>   <DIV class=3DMso=
Normal> <span class=3DEmailStyle16> <font size=3D2 color=3Dnavy face=3DAria=
l> <span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Ar=
ial'> <![if !supportEmptyParas]> &nbsp; <![endif]> <o:p> </o:p> </span> </f=
ont> </span>  </DIV>   <DIV class=3DMsoNormal> <tt> <font size=3D2 color=3D=
navy face=3D"Courier New"> <span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:navy'> <![if !supportEmptyParas]> &nbsp; <![endif]> </span>=
 </font> </tt> <tt> <font size=3D2 color=3Dnavy face=3D"Courier New"> <span=
 style=3D'font-size:10.0pt;font-family: "Courier New";color:navy;mso-color-=
alt:windowtext'> <o:p> </o:p> </span> </font> </tt>  </DIV>   <DIV class=3D=
MsoNormal> <span class=3DEmailStyle16> <font size=3D2 color=3Dnavy face=3DA=
rial> <span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family=
:Arial'>This makes a lot of sense I think. <o:p> </o:p> </span> </font> </s=
pan>  </DIV>   <DIV class=3DMsoNormal> <span class=3DEmailStyle16> <font si=
ze=3D2 color=3Dnavy face=3DArial> <span style=3D'font-size:10.0pt;mso-bidi-=
font-size:12.0pt;font-family:Arial'> <![if !supportEmptyParas]> &nbsp; <![e=
ndif]> <o:p> </o:p> </span> </font> </span>  </DIV>   <DIV class=3DMsoNorma=
l> <span class=3DEmailStyle16> <font size=3D2 color=3Dnavy face=3DArial> <s=
pan style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>=
Arnaud <o:p> </o:p> </span> </font> </span>  </DIV>   </div>
   </body>   </html>=

--Boundary_(ID_2xi+cP/g5rIPki+vcAth/A)--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 15:28:06 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08641
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 15:28:05 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62JGoFK079907
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 12:16:50 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62JGooU079906
	for ietf-calendar-bks; Wed, 2 Jul 2003 12:16:50 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62JGnFK079901
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 12:16:50 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <20030612213402.M31365@asitturnsout.org>
To: ietf-calendar@imc.org
Subject: RE: Fw: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF33514D73.F5F75154-ON85256D57.00687EB2-85256D57.00699218@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Wed, 2 Jul 2003 15:12:38 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/02/2003
 03:16:33 PM,
	Serialize complete at 07/02/2003 03:16:33 PM
Content-Type: multipart/alternative; boundary="=_alternative 0069921385256D57_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0069921385256D57_=
Content-Type: text/plain; charset="US-ASCII"

Chris wrote on 06/12/2003 05:49:02 PM:
> In Bruce's model, I need to keep track of the original recurrence-id of 
each
> instance of an event as they evolve. 

You are mixing the scenarios up.  The basic senario is that the set is 
rolled and then workflow takes place on the instances in the set.  You 
seem to be tossing in some kind of "and we reroll the set and then do a 
reschedule". 

Once the set is rolled you MUST have a fixed RECURRENCE-ID so you can 
properly track workflow and changes to the correct instance. 

If you change the RECURRENCE-ID with each set roll AND each reschedule 
then what good is the RECURRENCE-ID?  As both Chris and Doug have noted 
then a missed reschedule (detected by the fact that the RECURRENCE-ID is 
unknown?) can only be recovered by resending the entire set and rerolling 
it again.  All of this is wasted cycles and bandwidth since with fixed 
RECURRENCE-ID missed workflow is not an issue; its simply ignored and the 
latest REQUEST is acted upon.

>                                        In the REFRESH model, all I need 
to do
> is get the current version of the object and I'm done.

All REQUESTs are complete 'current versions' of the instance at the time 
they are sent.  I suspect you are trying to use SEQUENCE to detect the 
"current version" of the entire recurrence set and thats NOT what SEQUENCE 
is used for. 

SEQUENCE is simply the "the revision sequence number of the calendar 
component within a sequence of revisions."  We have no recurrence set 
sequencing property and you cannot use SEQUENCE for that because SEQUENCE 
is defined differently.

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...
Warning: Dates in Calendar are closer than they appear.


--=_alternative 0069921385256D57_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Chris wrote on 06/12/2003 05:49:02 PM:<br>
&gt; In Bruce's model, I need to keep track of the original recurrence-id
of each<br>
&gt; instance of an event as they evolve. &nbsp;</tt></font>
<br>
<br><font size=2 face="sans-serif">You are mixing the scenarios up. &nbsp;The
basic senario is that the set is rolled and then workflow takes place on
the instances in the set. &nbsp;You seem to be tossing in some kind of
&quot;and we reroll the set and then do a reschedule&quot;. </font>
<br>
<br><font size=2 face="sans-serif">Once the set is rolled you MUST have
a fixed RECURRENCE-ID so you can properly track workflow and changes to
the correct instance. </font>
<br>
<br><font size=2 face="sans-serif">If you change the RECURRENCE-ID with
each set roll AND each reschedule then what good is the RECURRENCE-ID?
&nbsp;As both Chris and Doug have noted then a missed reschedule (detected
by the fact that the RECURRENCE-ID is unknown?) can only be recovered by
resending the entire set and rerolling it again. &nbsp;All of this is wasted
cycles and bandwidth since with fixed RECURRENCE-ID missed workflow is
not an issue; its simply ignored and the latest REQUEST is acted upon.</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp;In the REFRESH model, all I need to do<br>
&gt; is get the current version of the object and I'm done.</tt></font>
<br>
<br><font size=2 face="sans-serif">All REQUESTs are complete 'current versions'
of the instance at the time they are sent. &nbsp;I suspect you are trying
to use SEQUENCE to detect the &quot;current version&quot; of the entire
recurrence set and thats NOT what SEQUENCE is used for. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">SEQUENCE is simply the &quot;the revision
sequence number of the calendar component within a sequence of revisions.&quot;
&nbsp;We have no recurrence set sequencing property and you cannot use
SEQUENCE for that because SEQUENCE is defined differently.</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...<br>
Warning: Dates in Calendar are closer than they appear.</font>
<br>
<br>
--=_alternative 0069921385256D57_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 15:37:22 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09030
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 15:37:21 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62JLaFK080043
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 12:21:36 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62JLaeu080042
	for ietf-calendar-bks; Wed, 2 Jul 2003 12:21:36 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62JLaFK080032
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 12:21:36 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3EE8F4C6.5010504@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF1AABFB5D.A42C7DAC-ON85256D57.00699913-85256D57.006A022E@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Wed, 2 Jul 2003 15:17:24 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/02/2003
 03:19:28 PM,
	Serialize complete at 07/02/2003 03:19:28 PM
Content-Type: multipart/alternative; boundary="=_alternative 006A022985256D57_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 006A022985256D57_=
Content-Type: text/plain; charset="US-ASCII"

Doug totally missed the point on 06/12/2003 05:46:46 PM:
> You are totally hosed if you were not part of SEQUENCE:0
> or somehow loose your data.

Totally wrong!

Go reread iTIP 3.2.2 REQUEST where it clearly tells you how to distinguish 
between a NEW request and a reschedule/update. 

If the UID/RECURRENCE-ID is new to you, its a new REQUEST.  If its NOT new 
then its an update/reschedule.  Since the REQUEST is fully self contained 
it has all the CUA needs to properly instanciate it on the users calendar. 
 Done.  No "Oh, whats this?  I dont know so Ill do a 'full' REFRESH and 
wait".   No extra thrashing or having to resend data that may exactly 
match the already recieved REQUEST.

> And when 100% of the original instances change and you
> somehow missed an important change. The new instances
> will not map to the SEQUENCE:0 instances and you
> might apply them incorrectly.

If the key does not change then any missed messages are IRRELEVANT if you 
get a higher SEQUENCE (or later DTSTAMP) one than you currently have NO 
MATTER the difference in SEQUENCE or DTSTAMP.  The higher SEQUENCE simply 
means that the REQUEST obsoletes whatever you have (or missed that came 
before) and workflow is restored righ then and there.

FUD wont work here...

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 006A022985256D57_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug totally missed the point on 06/12/2003 05:46:46
PM:<br>
&gt; You are totally hosed if you were not part of SEQUENCE:0<br>
&gt; or somehow loose your data.<br>
</tt></font>
<br><font size=2 face="sans-serif">Totally wrong!</font>
<br>
<br><font size=2 face="sans-serif">Go reread iTIP 3.2.2 REQUEST where it
clearly tells you how to distinguish between a NEW request and a reschedule/update.
&nbsp;</font>
<br>
<br><font size=2 face="sans-serif">If the UID/RECURRENCE-ID is new to you,
its a new REQUEST. &nbsp;If its NOT new then its an update/reschedule.
&nbsp;Since the REQUEST is fully self contained it has all the CUA needs
to properly instanciate it on the users calendar. &nbsp;Done. &nbsp;No
&quot;Oh, whats this? &nbsp;I dont know so Ill do a 'full' REFRESH and
wait&quot;. &nbsp; No extra thrashing or having to resend data that may
exactly match the already recieved REQUEST.</font>
<br><font size=2><tt><br>
&gt; And when 100% of the original instances change and you<br>
&gt; somehow missed an important change. The new instances<br>
&gt; will not map to the SEQUENCE:0 instances and you<br>
&gt; might apply them incorrectly.<br>
</tt></font>
<br><font size=2 face="sans-serif">If the key does not change then any
missed messages are IRRELEVANT if you get a higher SEQUENCE (or later DTSTAMP)
one than you currently have NO MATTER the difference in SEQUENCE or DTSTAMP.
&nbsp;The higher SEQUENCE simply means that the REQUEST obsoletes whatever
you have (or missed that came before) and workflow is restored righ then
and there.</font>
<br>
<br><font size=2 face="sans-serif">FUD wont work here...</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 006A022985256D57_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  2 18:39:27 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27725
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 18:39:26 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MR6FK089058
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 15:27:06 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62MR5IP089057
	for ietf-calendar-bks; Wed, 2 Jul 2003 15:27:05 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MR4FK089051
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:27:04 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h62MQxOR014488
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:27:03 -0700
Message-ID: <3F035C2E.8050105@Royer.com>
Date: Wed, 02 Jul 2003 16:26:54 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF02C713BD.6E90AA99-ON85256D57.0065B2C7-85256D57.0066A662@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms040404010003080209020203"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms040404010003080209020203
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:

> 
> Doug is saying that RECURRNECE-ID changes with _each_ reschedule of the 
> instance. 

No but almost, it is tied to the latest SEQUENCE.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms040404010003080209020203
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIyMjI2NTRaMCMGCSqGSIb3DQEJBDEWBBST
v9IkDx5kpe9dkUi6aJ16D0hXHTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAddBJD+X8+Eyz
Upxt+/61VCr41pZwDpJkm+0ajPM0EMCKtc8Kq9iS/4Z8UhnCZ1aUhf6ythK3AmmBtjBlgTQW
cLyvJjOZrKjrGfX78ysUgcQpZ43b1PkMvRVS0XqppKNw4bzOfOxh13Hx+KEp7cuySSh3zNc7
eSQ7GzJrStAvfN6B0yLt7vAH1Pb0sJFQO3l+a2gRVe+4Shg7FQO+LDQEKZ2Qvsyun9ZqJPyq
FCC481SPz7a/ERzpX0fhvsvJrkpqX7cWJmsOftbCU47XWCHYQFZCSd3zgF7PhR+NoUi7lDYR
SwMRNaRSu9u4ZXvfm7STmMqUbWAQml8goC4YEgXzUAAAAAAAAA==
--------------ms040404010003080209020203--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 18:39:27 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27726
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 18:39:26 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MOjFK088984
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 15:24:45 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62MOjT4088983
	for ietf-calendar-bks; Wed, 2 Jul 2003 15:24:45 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MOhFK088978
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:24:43 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h62MOTOR014441
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:24:33 -0700
Message-ID: <3F035B94.3080402@Royer.com>
Date: Wed, 02 Jul 2003 16:24:20 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF522DC1B6.F33F37BD-ON85256D57.0063A06E-85256D57.00657D3A@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020104070408040709060008"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020104070408040709060008
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Chris wrote on 06/12/2003 04:28:45 PM:
>  >              I believe that "the most recent version" is the correct 
> answer.
>  > My reasoning is that while RECURRENCE-ID is, if present, part of the 
> primary
>  > key to use in finding an instance, it is only valid when used in 
> relation to
>  > the correct version of the object in question.
> 
> I refer to the SEQUENCE:0 RECURRENCE-ID since so far no shipping C&S 
> products that do C&S support ADD add or do a good job of 'changing the 
> repeat set' so as such they are always '0' based.


> There is no SEQUENCE:0 for an ADDed instance ...

True an no one has said there is that I can find in the archives.

 > ...and so far the discussions were foucsed
> around the most common and basic model of invitations and reschedules to 
> the initial set.

I have not seen any one claim that including you in the debate.
But assuming it is - so what?

 > This is by far the most common set of actions
> performed in C&S and thus relevant to the discussions here.  It is of no 
> value to discuss less common paths if they do not work for the more 
> common ones.  Solutions that work only for the 20 in the 80/20 rule are 
> of little value to the larger 80...

And by the word 'this' do you mean doing it your way, or rescheduling?

And when there is a way to make it work 100% of the time?

> Chris seems to espouse a fixed RECURRENCE-ID as being necessary to key 
> to the instance (ala UID for finding the set) but then says that a 
> changing RID is the way to go.  Its simple to show that its NOT possible 
> to resync a particular instance of the set if even 1 reschedule is 
> missed.  

No, there has been no such proof offered. If the ATTENDEE can't
figure it out, they do a full REFRESH and they are back in sync.

> Doug has claimed it can be resyncd and his answer is a "full REFRESH". 

Yes, per the text in iTIP.

>  Putting asside the semantic oddities (Organiers do not issue REFRESHes, 
> they respond to them),

I have made NO such claim and I have told you that I have made
no such claim.

> Doug has actually tacitly agreed that a specific 
> instance resync is not possible;

No, I said when that happens the attendee must do a full REFRESH.

> the entire set must be resync for this 
> model to recover. 

In your model if an newly invited ATTENDEE would not have
a clue what recurrence-id:x is if is all they get is a
instance change. They also must do a full REFRESH. That
is exactly the same problem as if they get out of sync.
Except in your model you said throw the UID away if the
RRULE, RDATE, EXRULE, or EXDATE change, forcing EVERYONE
to have to reply to a new REQUEST.

> An expensive proposition for a single missed REQUEST 
> (esp. given the "small footprint" preferances of some who like this 
> "send it all again" model) by resending the current 'base' defintion 
> plus all the current individual instances (esp. if only 1 instance 
> needed to be resync'd!).

So how is one attendee doing a full REFRESH more expensive than
them never having SEQUENCE:0 and asking for a full REFRESH?

If they miss one of the single instance recurrence updates, then
they will also have to do a full REFRESH as no matter how many
times they do a single instance REFRESH, if that instance did
not exist in their copy of the object, they will not get anything
useful - they MUST do a full REFRESH ether way. Its a wash.

> However, in taking a step back I think that the key to this is a phrase 
> that seems to have been misinterpreted by some and misunderstood by 
> others.  Doug and George have cited the following as the basis for 
> claiming a changing RECURRENCE-ID model:
> 
>                                    For a given pair of "UID" and
>   "SEQUENCE" property values, the "RECURRENCE-ID" value for a
>   recurrence instance is fixed. When the definition of the recurrence
>   set for a calendar component changes, and hence the "SEQUENCE"
>   property value changes, the "RECURRENCE-ID" for a given recurrence
>   instance might also change.
> 
> The operative phrase here is "definition of the recurrence set for a 
> calendar component changes".  This means when the entrys repeat _set_ 
> changes from "Every Monday for 5 weeks" to "Every Thursday and Friday 
> for 3 months", NOT "When the individual instance is rescheduled to a 
> different date/time."  
> 
> When an instance itself is rescheduled, its RECURRENCE-ID 
> _does_not_change_.  This _is_ coherent w/the paragraph previous to the 
> citation in 2445 and w/the message sequencing and method interpreation 
> sections in iTIP because it means the UID/RECURRENCE-ID values do not 
> change with each reschedule.  As such a single (or 100) missed 
> reschedules (or CANCELs, etc) can be safely ignored and no "full 
> REFRESH" or full resyncs are necessary.  

So if two or more instances need to change, you do what? (a) Issue
a bunch of single instance changes and handle multiple REPLYs
to/from EACH attendee? (b) Do you issue a FULL REQUEST which WILL
change the recurrence rules? (c) Or do you throw the UID away if you
need to change the RRULE, RDATE, EXRULE, or EXDATE as you have
stated in previous email to this list?

Given:

	I == Instances that change (instance REQUEST message).
	A == Number of attendees.
         C == A CANCEL message
         R == A full REQUEST
       SET == one data blob from the ORGANIZER plus ONE blob from ATTENDEE.
         F == Number of REFRESH requests.

(a) Will generate (I * A) objects in (A) communications SETs.
(a.1) Plus (F * A) objects *IF* any attendee is out of sync in (A)
     communication sets.

(b) Will generate (A) objects in (A) communication SETs.

(c) WIll generate (C * A) in (A) communication SETs.
     Plus (A * R) in (A) communication SETs.

Which one is more expensive? I would go with (B).

The above is more complex to calculate when you only send
objects when you know which ATTENDEE has replied to which
SEQUENCES, as you can optimize out several of the (a)
objects and eliminate (a.1). Or eliminate some of the (b)
steps if you know it does not effect some ATTENDEES.
(c) can not be optimized.

>  > Please help me understand if this model is broken, and if so, how.
> 
> Before we go further I think that its important to realize that the 
> cited text for why RECURRENCE-IDs change has been misunderstood/misread 
> by some as meaning the RECURRENCE-ID changes whenever the instance is 
> rescheduled.  Once we all grasp that it does NOT say that a rescheduling 
> an instance means RECURRENCE-ID changes then we can revisit any other 
> confusion folks have.  Sound ok??

So are you claiming that if I do a reschedule as described in iTIP
"4.4.7 Add A New Series of Instances To A Recurring Event" that
the 'instances' do not change in the example after the paragraph
that starts with:

    The next series of examples illustrate how an "Organizer" would
    respond to a "REFRESH" submitted by an "Attendee" after a series of
    instance-specific modifications. To convey all instance-specific
    changes, the "Organizer" must provide the latest event description
    and the relevant instances. The first three examples show the history
    including the initial "VEVENT" request and subsequent instance
    changes and finally the "REFRESH".

Note the words 'instance changes' above.

    < followed by example changing the 'instance >

Summary of steps in that example:

   (a) The first example after the above paragraph is the original SEQUENCE:0
       object.

   (b) The ORGANIZER changes ONE instance (TIME-A to TIME-B) and the
       SEQUENCE becomes '1' as shown in the iTIP text.

   (c) The ORGANIZER ADD's ONE instance (TIME-C) . The SEQUENCE is now '2'
       as shown in the iTIP text.

   (d) The ATTENDEE does a full REFRESH and gets back the SEQUENCE:2 object.

At this point a NEW attendee would only get SEQUENCE:2 objects back
from the ORGANIZER on REFRESH. And all NEW ATTENDEES would get
a SEQUENCE:2 REQUEST to join.

If the recurence-id were tied to the 'original' object as you claim,
then ALL new ATTENDEEs would be UNABLE to reschedule single instances
which have start times not in SEQUENCE:2 (TIME-A in this example) and
would be FORCED to do a full REFRESH on each and every single
instance REQUEST in that case using your model.

Now let say the the ORGANIZER needs to re-schedule the instance added
in (c) (TIME-C to TIME-E). Lets call this step (e). We are now at SEQUENCE:3.

And lets also say that that step (e) has LOCATION:Room B in it.

Now what *if* just by chance that the 'instance' added in (c) [SEQUENCE:2,
TIME-C] just happened to have a start time the same as the (a) instance
[SEQUENE:0, TIME-A] (TIME-C coincidentally was the SAME as TIME-A)
that was rescheduled in (b) [SEQUENCE:1 to TIME-B].

Which instance data has changed in step (e) and which LOCATION is
the meeting in? Simple, it is the SEQUENCE:3/TIME-E instance in
'Room B' and NOT the SEQUENCE:0/TIME-A instance that was changed to a
SEQUENCE:2/TIME-B and SEQUENCE:3/TIME-B instance in 'Conference Room A'
that just coincidentally had the same same start time. The RECURRENCE-ID
is tied to the SEQUENCE number and NOT to the original object
or over time long standing meeting that get rescheduled are going
to be a mess or impossible to reschedule.

Now what if the ATTENDEE missed (b), they would have
instead reschedule the (a) instance to (e). And would
not know about the (b) change. So the ATTENDEE MUST
track instances to SEQUENCE and if all of the SEQUENCEs
have not been received between the last full REQUEST
and a specific instance update - They MUST do a full REFRESH
else they would not have a clue.

You have NOT shown that anything is busted. And you model
breaks when as shown in this example when there have been
updates that change the instances to a previous SEQUENCE
instance (TIME-A == TIME-E in this example).


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020104070408040709060008
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIyMjI0MjBaMCMGCSqGSIb3DQEJBDEWBBS0
vFGCtJwChj1CtQW33LL+o4CnczBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAosFMKzq7tHqc
jxySI6uYPmZ0bdlVZq9g20DUprFik1RHnUC013kn8qFuDrEF12S4IvC+Hg3CdOdOwEOp8NGH
GcncOH6u0tTTDEQQ8RbYJLlVzgnyXZvKGmaF5aDF8qjMuBCDHr/MtmqsVpqMVKtaTt0EMUOa
u76DdxFkXfaxrCNCHwtXRj1DCaqnkdXEzr1mShXfl0dobT5PPM7kYoL/I3VEjowb4l96Ftws
0IVvkA9ltfeYVPQY7HBGyMI9OhA2XJTUGcKx//+YlFXuzrMFTq2R/7y4R960RaVnEWIFsep8
GdTGdJX4KD83nfUvmpB7+qwedBxOqx5EFj6XJ2G4OgAAAAAAAA==
--------------ms020104070408040709060008--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 18:57:57 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28999
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 18:57:57 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MhoFK089573
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 15:43:50 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62MhoFH089572
	for ietf-calendar-bks; Wed, 2 Jul 2003 15:43:50 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MhlFK089566
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:43:48 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h62MhcOR014670
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:43:42 -0700
Message-ID: <3F036010.6010302@Royer.com>
Date: Wed, 02 Jul 2003 16:43:28 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
References: <OF072754A7.CEF06BC7-ON85256D57.0066B321-85256D57.00687063@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms040503010607080505000301"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms040503010607080505000301
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug wrote on 06/12/2003 04:46:31 PM:
>  > > You can easily if the RECURRENCE-ID never changes.  
>  >
>  > 1) Unless you do not have it because you joined the event
>  >     after SEQUENCE:0 was obsoleted.
> 
> Not true.  Per iTIP, Section 3.2.2 REQUEST:
> 
>    The "UID" and "SEQUENCE" properties are used to distinguish the
>   various uses of the "REQUEST" method. If the "UID" property value in
>   the "REQUEST" is not found on the recipient's calendar, then the
>   "REQUEST" is for a new "VEVENT" calendar component. If the "UID"
>   property value is found on the recipient's calendar, then the
>   "REQUEST" is for a rescheduling, an update, or a reconfirm of the
>   "VEVENT" calendar component.
> 
> In this case the REQUEST is for an unknown UID/RECURRENCE-ID and thus 
> its a new invitation to a particular instance.  Thats exactly why we 
> allow sending RECURRENCE-IDs in the REQUESTs; so particular instances 
> can be consistantly and accurately identified and referenced and 
> workflow for each instance can occur independent of the workflow on 
> other instances in the set.

To invite an ATTENDEE to a single instance, send
them a REQUEST with that UID, the latest SEQUENCE
and the instance(s) in RRULEs, RDATEs, EXRULEs, and EXDATEs
they are requested to attend and let them reply. (NO RECURRENCE-ID).

No RECURRENCE-ID needed. If you add RECURRENCE-ID to the REQUEST
and call it a new invitation, the ATTENDEE would be unable to
distinguish it from a single instance reschedule where they
have somehow missed the full REQUEST. They would then have
to do a REFRESH and get back the latest copy without
any RECURRENCE-ID in it anyway, so why do it that way? I could
not find a single example or text in iTIP that said you
can do that anyway.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms040503010607080505000301
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIyMjQzMjhaMCMGCSqGSIb3DQEJBDEWBBQz
AIj+mwOcg8mK9tcmjc2JWhwcyTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAFRuPQLc4sKyo
OENteBHr/1OdcPI7Y4cUGJBbNnVg2iGxQ9+givBbHwyVRN5lk5qoJ4/xKi3N/ddNG18RMfWL
KLImCQwoDW9uZMwxklVvLZDDbcyacMM3fFvMN3Nu1AZIIfXMndtY/GDSmKcUz4FZ7P9c7SPF
+I/W5DGz1u6pTrClp+slUNyijS2ZF2LHof2C5WojY9e7zmTAdDh6r5D51P0fmVR29xBM3bGq
lFJUgZbqAikf2KuiMz1FJ0ryQSvUozmIDtwDhfLnC+ONo1+oADNi+gl9xO8kEDB/Hndj5985
nlwbp/I7fBPYdj90us3gVB13TG2VCfD0fAIFoJtMkAAAAAAAAA==
--------------ms040503010607080505000301--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 18:59:42 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29126
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 18:59:41 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MkEFK089630
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 15:46:14 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62MkEcw089629
	for ietf-calendar-bks; Wed, 2 Jul 2003 15:46:14 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MkDFK089624
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:46:13 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h62MkAOR014712
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:46:14 -0700
Message-ID: <3F0360AC.8010004@Royer.com>
Date: Wed, 02 Jul 2003 16:46:04 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
References: <OF072754A7.CEF06BC7-ON85256D57.0066B321-85256D57.00687063@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms040502050000090202030506"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms040502050000090202030506
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:

> "Original instances" = what??  I dont want to misinterpret this...
> 
> In the "delta" model it only takes 5 steps to misidentify once instance 
> for another as I demonstrated 3 weeks ago.  And thats _without_ changing 
> the set!!!!

No you proposed a new way to invite someone, you did not show
that anything is busted.


>  > You do not have to SYNC - simply do a REFRESH and get the latest object
>  > version.
> 
> I said 'resync', not SYNC (a new METHOD?). 

No are you saying 'resync' is a new METHOD - I did not use the
word METHOD - only you did in your reply.

> You also seem to agree that 
> its impossible to resync a particular instance if you miss 1 
> rescheduling REQUEST in your model;

NO I SAID IT IS POSSIBLE - DO A REFRESH.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms040502050000090202030506
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIyMjQ2MDVaMCMGCSqGSIb3DQEJBDEWBBTC
K/S9ulFBTq8DPwsStvDxxlan6DBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAMmDOHZOzl2U3
Jz8pz/plF9BB8d6bYaXGQjnvg5D3x1UXTJaRJ2R25sH3ky7Cdt3W5IgyW2W1yQ27LmeYkqH7
9w25V96+QCprBEDdFcEWZsdYVR1/qK65ifNefjt20ZcfcNvHZrv6wGmszkYOxyX7HOKPa9Y1
lsEyFxJqhbPWoubiq6YswKQqnJuiHFCz13XywalYe8mnhUlkLQKrr34d78BimK4BbPukrfTH
37e1OYd+rWZaMy1BLvfRjZHCNuGNTGA7/xV7NVzegzTK6wawQtN4SHQQB1ZzftRUOhTaS+RP
8JDPn7nMXC8WMLfHx2/fiZhBm5YCVFbENmKvvkBL6AAAAAAAAA==
--------------ms040502050000090202030506--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 19:00:19 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29267
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 19:00:18 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MltFK089695
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 15:47:55 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62MltEZ089694
	for ietf-calendar-bks; Wed, 2 Jul 2003 15:47:55 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MlsFK089687
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:47:54 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h62MllOR014741
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:47:55 -0700
Message-ID: <3F03610E.3030607@Royer.com>
Date: Wed, 02 Jul 2003 16:47:42 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
References: <OF33514D73.F5F75154-ON85256D57.00687EB2-85256D57.00699218@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms040606000604050307000401"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms040606000604050307000401
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


I can't follow, please define what you mean by 'rolled'.


Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Chris wrote on 06/12/2003 05:49:02 PM:
>  > In Bruce's model, I need to keep track of the original recurrence-id 
> of each
>  > instance of an event as they evolve.  
> 
> You are mixing the scenarios up.  The basic senario is that the set is 
> rolled and then workflow takes place on the instances in the set.  You 
> seem to be tossing in some kind of "and we reroll the set and then do a 
> reschedule".
> 
> Once the set is rolled you MUST have a fixed RECURRENCE-ID so you can 
> properly track workflow and changes to the correct instance.
> 
> If you change the RECURRENCE-ID with each set roll AND each reschedule 
> then what good is the RECURRENCE-ID?  As both Chris and Doug have noted 
> then a missed reschedule (detected by the fact that the RECURRENCE-ID is 
> unknown?) can only be recovered by resending the entire set and 
> rerolling it again.  All of this is wasted cycles and bandwidth since 
> with fixed RECURRENCE-ID missed workflow is not an issue; its simply 
> ignored and the latest REQUEST is acted upon.
> 


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms040606000604050307000401
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIyMjQ3NDJaMCMGCSqGSIb3DQEJBDEWBBSN
a9+Mq8DnWVbywAMUr+JGcgpEszBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAX42iwxlHGyU2
aVNtWEOtG9dojVmnS14G5lrRf2ldr+HDPtz5bOCxvmsVgP/LbYYHvl6eBC0g8RGpNDNjcY0o
UjWVZma2ZBi7MB93Jp42AVpdLtUzGvKkZVQkc0FBy1IGDJ11W/n8pVt611AhhyVUtP9gPohq
X9Zqu+m86q8phnTppXG/N9q5J0OmfgGJ6aDC0gmfkJKGAxbQiLiNp9IkI8gZfmDrAUeBkUqU
a2+W1OJ/zLtIt3N92EaXnk7XpdhZQvwT5qPRxXcsAMPkF69TZZEIwjtEzS6VRs/f3zJ69REX
9VfRA+3lft7ZLcpU5PeJC8gUuBByEg97T75XVMUUPgAAAAAAAA==
--------------ms040606000604050307000401--



From owner-ietf-calendar@mail.imc.org  Wed Jul  2 19:12:04 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29967
	for <calsch-archive@lists.ietf.org>; Wed, 2 Jul 2003 19:12:03 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MsLFK089923
	for <ietf-calendar-bks@above.proper.com>; Wed, 2 Jul 2003 15:54:21 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h62MsLcY089922
	for ietf-calendar-bks; Wed, 2 Jul 2003 15:54:21 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h62MsJFK089917
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:54:19 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h62MsHOR014813
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 2 Jul 2003 15:54:21 -0700
Message-ID: <3F036294.7010802@Royer.com>
Date: Wed, 02 Jul 2003 16:54:12 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
References: <OF1AABFB5D.A42C7DAC-ON85256D57.00699913-85256D57.006A022E@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050304060505080008050605"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms050304060505080008050605
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug totally missed the point on 06/12/2003 05:46:46 PM:
>  > You are totally hosed if you were not part of SEQUENCE:0
>  > or somehow loose your data.
> 
> Totally wrong!
> 
> Go reread iTIP 3.2.2 REQUEST where it clearly tells you how to 
> distinguish between a NEW request and a reschedule/update.  
> 
> If the UID/RECURRENCE-ID is new to you, its a new REQUEST.  If its NOT 
> new then its an update/reschedule.  Since the REQUEST is fully self 
> contained it has all the CUA needs to properly instanciate it on the 
> users calendar.  Done.  No "Oh, whats this?  I dont know so Ill do a 
> 'full' REFRESH and wait".   No extra thrashing or having to resend data 
> that may exactly match the already recieved REQUEST.

If I get an object that looks exactly the same as an
update to an instance, I am going to do a REFRESH
to make sure that I did not miss the original full REQUEST.
They look *exactly* the same. Don't do it that way. Send
the ATTENDEE a REQUEST (minus RECURRENCE-ID) on their
first invite custom tailored to what they will be attending
(What is what I expect to get back from the REFRESH anyway).

ITIP shows that (REQUEST with RECURRENCE-ID) as an example of how
to update an instance, not how to originally invite an  ATTENDEE.
I think it is reasonable to assume that implementation will use
that method as the way to update an instance and use the documented
ways to originally invite a new ATTENDEE.

--

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms050304060505080008050605
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDIyMjU0MTJaMCMGCSqGSIb3DQEJBDEWBBQ4
yTIia8RW2IfKG8cMPWSnpSpOYzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAgYztHIyGVsAs
+frsdMJR/U21G+a5CMRYqg/E9HMpdga3q9OIg27PcZr/HPV8yy+VayuOaUyqBpBMev46DZSq
jn04MVjC93CLB8dgjqE1fG+ezVuTK84nm+fj2TIUGNxGd7+ZgB4wVODYYhex73XbhidW4n02
m9iXsJEqZjJzmg5krHdnoYjXWr6DveEjkAfa35yxMA9aOT0ifajR65hwFSLgmzQVK4TQYilD
vMbgJ6wWGZ1P/KStTy+WxG0sHBTZvdQM6fRkw3n8hcX4+k353END0aaykfGJiI1nRDUgk7qH
v/OT3slDwh1mHVLecu/TXqqMOZUmWnTqFoHR/J9gAQAAAAAAAA==
--------------ms050304060505080008050605--



From owner-ietf-calendar@mail.imc.org  Thu Jul  3 16:40:49 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05339
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 16:40:48 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63KR2qt018569
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 13:27:02 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63KR2cs018568
	for ietf-calendar-bks; Thu, 3 Jul 2003 13:27:02 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63KR1qt018563
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 13:27:02 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F035C2E.8050105@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OFF56618A7.13636046-ON85256D58.006F549E-85256D58.006FF949@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 3 Jul 2003 16:22:44 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/03/2003
 04:27:01 PM,
	Serialize complete at 07/03/2003 04:27:01 PM
Content-Type: multipart/alternative; boundary="=_alternative 006FF94485256D58_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 006FF94485256D58_=
Content-Type: text/plain; charset="US-ASCII"

Doug wrote on 07/02/2003 06:26:54 PM:
> > Doug is saying that RECURRNECE-ID changes with _each_ reschedule of 
the 
> > instance. 
> 
> No but almost, it is tied to the latest SEQUENCE.

Ok, help me out here then. 

Since the SEQUENCE is changed with each reschedule of the instance then 
each time a higher SEQUENCE becomes "the latest" doesn't the RECURRENCE-ID 
also change?  Back on May 20th you replied:

If SEQUENCE:1 has an instance of MONDAY      <- ORIGINAL
And you say yes (book it).

If SEQUENCE:2 changes the MONDAY instance to TUESDAY <- UPDATE '1'
And you say yes (book it)

If SEQUENCE:3 uses the RECURRANCE-ID of MONDAY  <- UPDATE '2'
  Nothing matches - the sending CUA is busted.

UPDATE '2' MUST use the RECURRANCE-ID of the UPDATE '1'
instance (currently booked entry), not the original.

So how does that different from "RECURRENCE-ID changes with each 
reschedule of the instance"?  Each update (at the next higher SEQUENCE) 
"MUST use the RECURRANCE-ID" of the previous update.  That sound like what 
I said...

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 006FF94485256D58_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug wrote on 07/02/2003 06:26:54 PM:<br>
&gt; &gt; Doug is saying that RECURRNECE-ID changes with _each_ reschedule
of the <br>
&gt; &gt; instance. <br>
&gt; <br>
&gt; No but almost, it is tied to the latest SEQUENCE.<br>
</tt></font>
<br><font size=2 face="sans-serif">Ok, help me out here then. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Since the SEQUENCE is changed with each
reschedule of the instance then each time a higher SEQUENCE becomes &quot;the
latest&quot; doesn't the RECURRENCE-ID also change? &nbsp;Back on May 20th
you replied:</font>
<br>
<br><font size=2><tt>If SEQUENCE:1 has an instance of MONDAY &nbsp; &nbsp;
&nbsp;&lt;- ORIGINAL<br>
And you say yes (book it).<br>
<br>
If SEQUENCE:2 changes the MONDAY instance to TUESDAY &lt;- UPDATE '1'<br>
And you say yes (book it)<br>
<br>
If SEQUENCE:3 uses the RECURRANCE-ID of MONDAY &nbsp;&lt;- UPDATE '2'<br>
 &nbsp;Nothing matches - the sending CUA is busted.<br>
<br>
UPDATE '2' MUST use the RECURRANCE-ID of the UPDATE '1'<br>
instance (currently booked entry), not the original.</tt></font>
<br>
<br><font size=2 face="sans-serif">So how does that different from &quot;RECURRENCE-ID
changes with each reschedule of the instance&quot;? &nbsp;Each update (at
the next higher SEQUENCE) &quot;MUST use the RECURRANCE-ID&quot; of the
previous update. &nbsp;That sound like what I said...</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 006FF94485256D58_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul  3 17:11:40 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06849
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 17:11:39 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Kxhqt019814
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 13:59:43 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63KxhQf019813
	for ietf-calendar-bks; Thu, 3 Jul 2003 13:59:43 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Kxgqt019808
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 13:59:42 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h63KxaOR026512
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 13:59:41 -0700
Message-ID: <3F04992F.4050305@Royer.com>
Date: Thu, 03 Jul 2003 14:59:27 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OFF56618A7.13636046-ON85256D58.006F549E-85256D58.006FF949@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090307020208000208040503"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms090307020208000208040503
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug wrote on 07/02/2003 06:26:54 PM:
>  > > Doug is saying that RECURRNECE-ID changes with _each_ reschedule of 
> the
>  > > instance.
>  >
>  > No but almost, it is tied to the latest SEQUENCE.
> 
> Ok, help me out here then.   ..
> 
> So how does that different from "RECURRENCE-ID changes with each 
> reschedule of the instance"?  Each update (at the next higher SEQUENCE) 
> "MUST use the RECURRANCE-ID" of the previous update.  That sound like 
> what I said...

The difference is simply my assertion that RECURRENCE-ID is tied to SEQUENCE.
A reschedule is only one of the reasons that SEQUENCE changes.


--
Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms090307020208000208040503
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDMyMDU5MjdaMCMGCSqGSIb3DQEJBDEWBBTu
bnjKs7m5mpe6BteTuca8KSAYYzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAfOGJaAzCkAfe
/WkHZb0DeOfFgC7DH6uULo/ai6/J9CfuEWHv2C/BL2zrbSJCXC3iFic6Ndfr/QdEhlQZYc0T
N0QeMtYqYTU6S19S9hanyf35wafLrqAWiDG1+XNYQNrjOQl/QVz1qQJd/9+zeW0r7DqlOLNY
WpflbwuQcHRQJ4EQuIcKmMeF0cN6bVUm1t6f6MVbtDsnjjBl5bA2eGZXyOsJ6NjzDa/ScH8h
39Tyi6XDsshPc3hFiXO5fguGIXIqSTyKuecA58bvPH/MAxQq17uvz1yZ5V6skwcxXl0Cr2zP
LSPGWBliQeyrN8BJSLpeERIjX9IEoc5W0qdwTOGmmAAAAAAAAA==
--------------ms090307020208000208040503--



From owner-ietf-calendar@mail.imc.org  Thu Jul  3 17:15:37 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07116
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 17:15:36 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63L4eqt020047
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 14:04:40 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63L4eoc020046
	for ietf-calendar-bks; Thu, 3 Jul 2003 14:04:40 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63L4dqt020040
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 14:04:40 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F036010.6010302@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF3E195FC2.7E9018BE-ON85256D58.00700AB1-85256D58.00736B65@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 3 Jul 2003 17:00:22 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/03/2003
 05:04:37 PM,
	Serialize complete at 07/03/2003 05:04:37 PM
Content-Type: multipart/alternative; boundary="=_alternative 00736B6085256D58_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 00736B6085256D58_=
Content-Type: text/plain; charset="US-ASCII"

Doug replied on 07/02/2003 06:43:28 PM:
> To invite an ATTENDEE to a single instance, send
> them a REQUEST with that UID, the latest SEQUENCE
> and the instance(s) in RRULEs, RDATEs, EXRULEs, and EXDATEs
> they are requested to attend and let them reply. (NO RECURRENCE-ID).

If you are inviting to a single instance there you do NOT include RRULEs, 
RDATEs, EXDATES or EXRULES.  Those are for defining the repeat set.  By 
definition in iCalendar the RECURRENCE-ID _is_ expressly used "to identify 
a specific instance of a recurring" calendar entry.

Since the invitation is for an instance in that set and NOT the entire set 
you do not send them.  They are NOT of any relevance since the REQUEST by 
definition is the full snapshot of the instance in question.

> No RECURRENCE-ID needed. If you add RECURRENCE-ID to the REQUEST
> and call it a new invitation, the ATTENDEE would be unable to
> distinguish it from a single instance reschedule where they
> have somehow missed the full REQUEST. 

Whoa!  Lots of things in that hairball...

First off, each REQUEST is a "full REQUEST".  At no point is a REQUEST NOT 
the full and current defintion of the instance in question. 

Second, by NOT including a RECURRENCE-ID in the REQUEST for the instance 
you give the wrong impression that the REQUEST is for the entire set of 
instances defined by that UID (and associated RDATEs, etc that were 
included at top). 

Also, RECURRENCE-IDs are necessary so that you can properly detect if the 
workflow (ie: REQUEST/REPLY) is for a particular instance, a range of 
instances or the entire recurrence set.  Why do you think the REQUEST 
restriction table has:

    RECURRENCE-ID   0 or 1  only if referring to an instance of a
                            recurring calendar component.  Otherwise it
                            MUST NOT be present.

in it.  The text clearly says "if referring to an instance of a recurring 
calendar component".  Since we are talking about the invitation to an 
instance of the set then this certainly fits the bill and should be used. 
A REQUEST without a RECURRENCE-ID propery is therefore one that is NOT 
"referring to an instnace of a recurring calendar component".  So if Im 
inviting someone to a single instance then Im referring to just that 
single instance and as such my REQUEST must contain the RECURRENCE-ID 
property.

This also jives with the iTIP message sequencing rules that state:

   1.  The primary key for referencing a particular iCalendar component
       is the "UID" property value. To reference an instance of a
       recurring component, the primary key is composed of the "UID" and
       the "RECURRENCE-ID" properties.

(emphasis added).  So since the REQUEST is for a particular instance it 
MUST have the proper RECURRENCE-ID property for that instance so you can 
properly distinguish a new invitation from a reschedule (per iTIP Section 
3.2.2 REQUEST).

Still none of this justifys the original claim that RECURRENCE-ID changes 
on each reschedule (paraphrased pretty closely from Dougs May 20th reply). 
 In fact that claim is clearly disallowed by the defintion of 
RECURRENCE-ID in iCalendar:

   The date/time value is set to the time when the original recurrence
   instance would occur; meaning that if the intent is to change a
   Friday meeting to Thursday, the date/time is still set to the
   original Friday meeting.

and the other misinterpreted text:

                                When the definition of the recurrence
   set for a calendar component changes, and hence the "SEQUENCE"
   property value changes, the "RECURRENCE-ID" for a given recurrence
   instance might also change.

which allows for RECURRENCE-ID changing only for the case where "the 
definition of the recurrence set for a calendar component changes".  A 
reschedule REQUEST does not qualify as a change to "the definition of the 
recurrence set for a calendar component changes", it is merely moving an 
instance in the set around.

>                                        They would then have
> to do a REFRESH and get back the latest copy without
> any RECURRENCE-ID in it anyway, so why do it that way? I could
> not find a single example or text in iTIP that said you
> can do that anyway.

No need for a REFRESH if you get a new UID/RECURRENCE-ID.  By applying:

   The "UID" and "SEQUENCE" properties are used to distinguish the
   various uses of the "REQUEST" method. If the "UID" property value in
   the "REQUEST" is not found on the recipient's calendar, then the
   "REQUEST" is for a new "VEVENT" calendar component. If the "UID"
   property value is found on the recipient's calendar, then the
   "REQUEST" is for a rescheduling, an update, or a reconfirm of the
   "VEVENT" calendar component.

and treating the "UID" reference as "UID"/"RECURRENCE-ID" since its a 
repeating instance (per Section 2.1.5s Rule #1) you will correctly treat 
the new REQUEST as just that, a new invitation and act accordingly. 

Interestingly enough, Doug cited iTIP Section 4.7.2 Bad RECURRENCE-ID as 
another reason to justify using UID then SEQUENCE then RECURRENCE-ID for 
message sequencing but I think the text from Bullet 1 there failed to sink 
in too:

   1.  The component with the referenced "UID" and "RECURRENCE-ID" has
       been found but the "SEQUENCE" number in the calendar store does
       not match that of the ITIP message.

This means that the UID and RECURRENCE-ID do not change when the SEQUENCE 
does.  In fact the text describing case 1 that followed does not say 
SEQUENCE is "higher by 1" or "lower by 1", it merely says "smaller" or 
"larger".  This means that RECURRENCE-ID does change with each SEQUENCE 
change as some believe.

Bullet 2 under that example talks about a found UID and SEQUENCE but no 
matching RECURRENCE-ID and this is likely what gives some the wrong 
impression about using UID then SEQUENCE then RECURRENCE-ID in message 
sequencing.   The description for that bullet says:

   In case (2), something has gone wrong.  Both the "Organizer" and the
   "Attendee" should have the same instances, but the "Attendee" does
   not have the referenced instance.  In this case the "Attendee" SHOULD
   send a "REFRESH" to the "Organizer" to get an updated version of the
   event.

It should be noted that:

1: The initial REQUEST with the unknown UID/RECURRENCE-ID (and yes 
SEQUENCE) will NOT be found and hence is not covered by this case.  It 
simply is treated as the initial REQUEST as described in Section 3.2.2.
2: Just because an invitation to a single instance results in the UID 
being known it does not mean that all instances are known to the invitee. 
As such the new UID/RECURRENCE-ID key is treated like a new invitation 
which it is.
3: This text makes NO mention of changing the RECURRENCE-ID when SEQUENCE 
is changed so its not valid supporting evidence for that claim.

So lets get back to the facts:

1: iCalendar clearly says that RECURRENCE-ID does not change when a 
reschedule of an instance takes place.  The only time RECURRENCE-ID 
"might" change is if the repeat set itself changes.  Reschedules are not 
the same as rerolling the repeat set.
2: iTIP does not say that RECURRENCE-ID changes with each reschedule of an 
instance.
3: The citation from iTIP Section 4.7.2 clearly describes the case where 
UID and RECURRENCE-ID do not change when SEQUENCE does.  Any other reading 
of Bullet 1 there is a misinterpretation.
4: The WG covered this exact question at least as far back as July 1999 
and the concensus then was that it does not change on the reschedule.

Any misinterpretations to the contrary are just that, misinterpretations.

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 00736B6085256D58_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug replied on 07/02/2003 06:43:28 PM:<br>
&gt; To invite an ATTENDEE to a single instance, send<br>
&gt; them a REQUEST with that UID, the latest SEQUENCE<br>
&gt; and the instance(s) in RRULEs, RDATEs, EXRULEs, and EXDATEs<br>
&gt; they are requested to attend and let them reply. (NO RECURRENCE-ID).<br>
</tt></font>
<br><font size=2 face="sans-serif">If you are inviting to a single instance
there you do NOT include RRULEs, RDATEs, EXDATES or EXRULES. &nbsp;Those
are for defining the repeat set. &nbsp;By definition in iCalendar the RECURRENCE-ID
_is_ expressly used &quot;</font><font size=2><tt>to identify a specific
instance of a recurring</tt></font><font size=2 face="sans-serif">&quot;
calendar entry.</font>
<br>
<br><font size=2 face="sans-serif">Since the invitation is for an instance
in that set and NOT the entire set you do not send them. &nbsp;They are
NOT of any relevance since the REQUEST by definition is the full snapshot
of the instance in question.</font>
<br>
<br><font size=2><tt>&gt; No RECURRENCE-ID needed. If you add RECURRENCE-ID
to the REQUEST<br>
&gt; and call it a new invitation, the ATTENDEE would be unable to<br>
&gt; distinguish it from a single instance reschedule where they<br>
&gt; have somehow missed the full REQUEST. </tt></font>
<br>
<br><font size=2 face="sans-serif">Whoa! &nbsp;Lots of things in that hairball...</font>
<br>
<br><font size=2 face="sans-serif">First off, each REQUEST is a &quot;full
REQUEST&quot;. &nbsp;At no point is a REQUEST NOT the full and current
defintion of the instance in question. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Second, by NOT including a RECURRENCE-ID
in the REQUEST for the instance you give the wrong impression that the
REQUEST is for the entire set of instances defined by that UID (and associated
RDATEs, etc that were included at top). &nbsp; </font>
<br>
<br><font size=2 face="sans-serif">Also, RECURRENCE-IDs are necessary so
that you can properly detect if the workflow (ie: REQUEST/REPLY) is for
a particular instance, a range of instances or the entire recurrence set.
&nbsp;Why do you think the REQUEST restriction table has:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; RECURRENCE-ID &nbsp; 0 or 1 &nbsp;only
if referring to an instance of a<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;recurring calendar component. &nbsp;Otherwise
it<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;MUST NOT be present.<br>
</tt></font>
<br><font size=2 face="sans-serif">in it. &nbsp;The text clearly says &quot;if
referring to an instance of a recurring calendar component&quot;. &nbsp;Since
we are talking about the invitation to an instance of the set then this
certainly fits the bill and should be used. &nbsp;A REQUEST without a RECURRENCE-ID
propery is therefore one that is NOT &quot;referring to an instnace of
a recurring calendar component&quot;. &nbsp;So if Im inviting someone to
a single instance then Im referring to just that single instance and as
such my REQUEST must contain the RECURRENCE-ID property.</font>
<br>
<br><font size=2 face="sans-serif">This also jives with the iTIP message
sequencing rules that state:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;1. &nbsp;The primary key for referencing
a particular iCalendar component<br>
 &nbsp; &nbsp; &nbsp; is the &quot;UID&quot; property value. <b>To reference
an instance of a<br>
 &nbsp; &nbsp; &nbsp; recurring component, the primary key is composed
of the &quot;UID&quot; and<br>
 &nbsp; &nbsp; &nbsp; the &quot;RECURRENCE-ID&quot; properties.</b></tt></font>
<br>
<br><font size=2 face="sans-serif">(emphasis added). &nbsp;So since the
REQUEST is for a particular instance it MUST have the proper RECURRENCE-ID
property for that instance so you can properly distinguish a new invitation
from a reschedule (per iTIP Section 3.2.2 REQUEST).</font>
<br>
<br><font size=2 face="sans-serif">Still none of this justifys the original
claim that RECURRENCE-ID changes on each reschedule (paraphrased pretty
closely from Dougs May 20th reply). &nbsp;In fact that claim is clearly
disallowed by the defintion of RECURRENCE-ID in iCalendar:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The date/time value is set to the time
when the original recurrence<br>
 &nbsp; instance would occur; meaning that if the intent is to change a<br>
 &nbsp; Friday meeting to Thursday, the date/time is still set to the<br>
 &nbsp; original Friday meeting.<br>
</tt></font>
<br><font size=2 face="sans-serif">and the other misinterpreted text:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; When the definition
of the recurrence<br>
 &nbsp; set for a calendar component changes, and hence the &quot;SEQUENCE&quot;<br>
 &nbsp; property value changes, the &quot;RECURRENCE-ID&quot; for a given
recurrence<br>
 &nbsp; instance might also change.</tt></font>
<br>
<br><font size=2 face="sans-serif">which allows for RECURRENCE-ID changing
only for the case where &quot;</font><font size=2><tt>the definition of
the recurrence set for a calendar component changes&quot;</tt></font><font size=2 face="sans-serif">.
&nbsp;A reschedule REQUEST does not qualify as a change to </font><font size=2><tt>&quot;the
definition of the recurrence set for a calendar component changes&quot;</tt></font><font size=2 face="sans-serif">,
it is merely moving an instance in the set around.</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp;They would then have<br>
&gt; to do a REFRESH and get back the latest copy without<br>
&gt; any RECURRENCE-ID in it anyway, so why do it that way? I could<br>
&gt; not find a single example or text in iTIP that said you<br>
&gt; can do that anyway.<br>
</tt></font>
<br><font size=2 face="sans-serif">No need for a REFRESH if you get a new
UID/RECURRENCE-ID. &nbsp;By applying:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The &quot;UID&quot; and &quot;SEQUENCE&quot;
properties are used to distinguish the<br>
 &nbsp; various uses of the &quot;REQUEST&quot; method. If the &quot;UID&quot;
property value in<br>
 &nbsp; the &quot;REQUEST&quot; is not found on the recipient's calendar,
then the<br>
 &nbsp; &quot;REQUEST&quot; is for a new &quot;VEVENT&quot; calendar component.
If the &quot;UID&quot;<br>
 &nbsp; property value is found on the recipient's calendar, then the<br>
 &nbsp; &quot;REQUEST&quot; is for a rescheduling, an update, or a reconfirm
of the<br>
 &nbsp; &quot;VEVENT&quot; calendar component.</tt></font>
<br>
<br><font size=2 face="sans-serif">and treating the &quot;UID&quot; reference
as &quot;UID&quot;/&quot;RECURRENCE-ID&quot; since its a repeating instance
(per Section 2.1.5s Rule #1) you will correctly treat the new REQUEST as
just that, a new invitation and act accordingly. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Interestingly enough, Doug cited iTIP
Section 4.7.2 Bad RECURRENCE-ID as another reason to justify using UID
then SEQUENCE then RECURRENCE-ID for message sequencing but I think the
text from Bullet 1 there failed to sink in too:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;1. &nbsp;The component with the referenced
&quot;UID&quot; and &quot;RECURRENCE-ID&quot; has<br>
 &nbsp; &nbsp; &nbsp; been found but the &quot;SEQUENCE&quot; number in
the calendar store does<br>
 &nbsp; &nbsp; &nbsp; not match that of the ITIP message.<br>
</tt></font>
<br><font size=2 face="sans-serif">This means that the UID and RECURRENCE-ID
do not change when the SEQUENCE does. &nbsp;In fact the text describing
case 1 that followed does not say SEQUENCE is &quot;higher by 1&quot; or
&quot;lower by 1&quot;, it merely says &quot;smaller&quot; or &quot;larger&quot;.
&nbsp;This means that RECURRENCE-ID does change with each SEQUENCE change
as some believe.</font>
<br>
<br><font size=2 face="sans-serif">Bullet 2 under that example talks about
a found UID and SEQUENCE but no matching RECURRENCE-ID and this is likely
what gives some the wrong impression about using UID then SEQUENCE <u>then</u>
RECURRENCE-ID in message sequencing. &nbsp; The description for that bullet
says:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;In case (2), something has gone wrong.
&nbsp;Both the &quot;Organizer&quot; and the<br>
 &nbsp; &quot;Attendee&quot; should have the same instances, but the &quot;Attendee&quot;
does<br>
 &nbsp; not have the referenced instance. &nbsp;In this case the &quot;Attendee&quot;
SHOULD<br>
 &nbsp; send a &quot;REFRESH&quot; to the &quot;Organizer&quot; to get
an updated version of the<br>
 &nbsp; event.</tt></font>
<br>
<br><font size=2 face="sans-serif">It should be noted that:</font>
<br>
<br><font size=2 face="sans-serif">1: The initial REQUEST with the unknown
UID/RECURRENCE-ID (and yes SEQUENCE) will NOT be found and hence is not
covered by this case. &nbsp;It simply is treated as the initial REQUEST
as described in Section 3.2.2.</font>
<br><font size=2 face="sans-serif">2: Just because an invitation to a single
instance results in the UID being known it does not mean that all instances
are known to the invitee. &nbsp;As such the new UID/RECURRENCE-ID key is
treated like a new invitation which it is.</font>
<br><font size=2 face="sans-serif">3: This text makes NO mention of changing
the RECURRENCE-ID when SEQUENCE is changed so its not valid supporting
evidence for that claim.</font>
<br>
<br><font size=2 face="sans-serif">So lets get back to the facts:</font>
<br>
<br><font size=2 face="sans-serif">1: iCalendar clearly says that RECURRENCE-ID
does not change when a reschedule of an instance takes place. &nbsp;The
only time RECURRENCE-ID &quot;might&quot; change is if the repeat set itself
changes. &nbsp;Reschedules are not the same as rerolling the repeat set.</font>
<br><font size=2 face="sans-serif">2: iTIP does not say that RECURRENCE-ID
changes with each reschedule of an instance.</font>
<br><font size=2 face="sans-serif">3: The citation from iTIP Section 4.7.2
clearly describes the case where UID and RECURRENCE-ID do not change when
SEQUENCE does. &nbsp;Any other reading of Bullet 1 there is a misinterpretation.</font>
<br><font size=2 face="sans-serif">4: The WG covered this exact question
at least as far back as July 1999 and the concensus then was that it does
not change on the reschedule.</font>
<br>
<br><font size=2 face="sans-serif">Any misinterpretations to the contrary
are just that, misinterpretations.</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 00736B6085256D58_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul  3 17:45:10 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08114
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 17:45:09 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63LXtqt021765
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 14:33:56 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63LXtuR021764
	for ietf-calendar-bks; Thu, 3 Jul 2003 14:33:55 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63LXtqt021759
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 14:33:55 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F03610E.3030607@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OFAE306412.57C25795-ON85256D58.0075EC0C-85256D58.007618DA@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 3 Jul 2003 17:29:37 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/03/2003
 05:33:51 PM,
	Serialize complete at 07/03/2003 05:33:51 PM
Content-Type: multipart/alternative; boundary="=_alternative 007618D585256D58_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 007618D585256D58_=
Content-Type: text/plain; charset="US-ASCII"

Doug asked on 07/02/2003 06:47:42 PM:
> I can't follow, please define what you mean by 'rolled'.

Are you serious?  That terms been used in the WG for years.  What do you 
think it means?

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 007618D585256D58_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug asked on 07/02/2003 06:47:42 PM:<br>
&gt; I can't follow, please define what you mean by 'rolled'.<br>
</tt></font>
<br><font size=2 face="sans-serif">Are you serious? &nbsp;That terms been
used in the WG for years. &nbsp;What do you think it means?</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 007618D585256D58_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul  3 17:46:33 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08185
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 17:46:31 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63LVNqt021705
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 14:31:24 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63LVNfc021704
	for ietf-calendar-bks; Thu, 3 Jul 2003 14:31:23 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63LVMqt021699
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 14:31:23 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F0360AC.8010004@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OFDEEF32A6.DFABA59A-ON85256D58.0073776C-85256D58.0075DDB6@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 3 Jul 2003 17:27:06 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/03/2003
 05:31:19 PM,
	Serialize complete at 07/03/2003 05:31:19 PM
Content-Type: multipart/alternative; boundary="=_alternative 0075DDB185256D58_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0075DDB185256D58_=
Content-Type: text/plain; charset="US-ASCII"

Doug claimed on 07/02/2003 06:46:04 PM:
> No you proposed a new way to invite someone, you did not show
> that anything is busted.

Perhaps you missed my posting that showed how easy it is to break the 
delta model by misidentifying instances in 5 steps.  From my response 
dated 05/27/2003 01:38:43 PM AST:

It can become worse if instances in a repeat set 'cross' at some point 
such that the rekeyd RECURRENCE-ID is shared between different instances 
at different points in time.  The SEQUENCE values could match when the 
overlap happens so then it becomes impossible to accurately tell which 
instance is being referred to at any given time.  To see this, simply do 
the following 5 steps: 

1: Create a 2 entry repeating set for every Wednesday @ a given time. 
2: Reschedule the first instance to the Friday between the two Wednesdays 
(now SEQUENCE:1) 
3: Reschedule it again to the day before (Thursday, SEQUENCE:2) 
4: Reschedule the second instance to the Friday between the two Wednesdays 
(now SEQUENCE:1 and same RECURRENCE-ID) 
5: Reschedule it again to another day. 

So now if a REPLY for RECURRENCE-ID:THURSDAY / SEQUENCE:1 comes in, can 
you tell me which instance it was for AND more to the point what the 
correct new RECURRENCE-ID is??  Didn't think you could, at least not 
accurately... 

Essentially if each instance gets rescheduled to the same RECURRENCE-ID / 
SEQUENCE values at some point then you cannot accurately match the 
invitees REPLY for that UID / RECURRENCE-ID / SEQUENCE to the proper 
instance.

> No are you saying 'resync' is a new METHOD - I did not use the
> word METHOD - only you did in your reply.

Not sure how you got that all a sudden when Ive been using that term all 
along and not as a new method.  Simply put, if the RECURRENCE-IDs get out 
of sync due to a missed REQUEST then the invitee and the Organizer need to 
get back in sync (aka resync) so that they can do workflow on the same 
instances and be certain that that both sides are dealing with the same 
data/dates/times/etc.  Doug was the only one to use "SYNC" in any message 
so far...

> > You also seem to agree that 
> > its impossible to resync a particular instance if you miss 1 
> > rescheduling REQUEST in your model;
> 
> NO I SAID IT IS POSSIBLE - DO A REFRESH.

Yes you've said that all along.  So lets get the terminology straight 
shall we?

The invitee is the only party who sends REFRESH messages and thus the only 
party in this who "does a REFRESH" or "full REFRESH" as its been called. 
REFRESH is specifically defined as:

3.2.6 REFRESH

   The "REFRESH" method in a "VEVENT" calendar component is used by
   "Attendees" of an existing event to request an updated description
   from the event "Organizer". The "REFRESH" method must specify the
   "UID" property of the event to update. A recurrence instance of an
   event may be requested by specifying the "RECURRENCE-ID" property
   corresponding to the associated event. The "Organizer" responds with
   the latest description and version of the event.

The Organizers response to a REFRESH messge is to send "the latest 
description and version of the event" which would be in the form of a 
REQUEST.  So far I think we all agree.  As the hilighted description above 
says, RECURRENCE-IDs are used when particular instances are being 
referenced.  In the delta model of things this would _NEVER_ be necessary 
since the only reason to actually do a REFRESH is because the invitee 
needs to get back in sync w/the Organizer.  _ANY_ RECURRENCE-ID used would 
be invalid from the Organizers perspective if the invitee and Organzier 
are out of sync so that negates the whole benefit of REFRESH.  If the 
invitee is current with the Organzier then why would they need to do a 
REFRESH in the first place?  Thus there is no apparent need for REFRESH 
for particular instances.

Now it did appear that Doug was intending to send a REFRESH message 
without a RECURRENCE-ID in it and that was what he means by a "full 
REFRESH" or all other references to "doing" REFRESH, etc.  If Im wrong I 
appologize and Ill await my punishment for putting words into Dougs mouth. 
 However it it should be noted that the only way for a REFRESH on a 
particular RECURRENCE-ID to be of any value is if RECURRENCE-ID does not 
change between reschedules.   The only other alternative reading is that 
someone just decided for no real reason that they wanted to ask for a 
REFRESH just because they can.   All that results in is a new REQUEST has 
the same UID / RECURRENCE-ID / SEQUENCE and a newer DTSTAMP.

Now by NOT using RECURRENCE-ID in the REFRESH message the invitee is 
asking for a refresh of the entire event or set (assuming its a repeating 
entry).  As noted above, if the invitee is just invited to a particular 
instance then the REQUEST MUST contain a RECURRENCE-ID property.  However 
if RECURRENCE-ID change with each reschedule of each instance then there 
is still no way to match up the initial REQUEST for RECURRENCE-ID:XXX at 
SEQUENCE:5 with RECURRENCE-ID:YYY at SEQUENCE:10.  As such the invitee 
thinks they are invited to 2 instances rather than just the single one.

Still, this is all a distraction from the facts that iCalendar was 
misinterpreted (and the parts that directly say RECURRENCE-ID does not 
change were ignored) and that iTIP does NOT say that RECURRENCE-ID changes 
with each reschedule REQUEST (recheck Bullet 1 under Section 4.7.2 and its 
case description if you think otherwise).

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 0075DDB185256D58_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug claimed on 07/02/2003 06:46:04 PM:<br>
&gt; No you proposed a new way to invite someone, you did not show<br>
&gt; that anything is busted.</tt></font>
<br>
<br><font size=2 face="sans-serif">Perhaps you missed my posting that showed
how easy it is to break the delta model by misidentifying instances in
5 steps. &nbsp;From my response dated 05/27/2003 01:38:43 PM AST:</font>
<br>
<br><font size=2><tt>It can become worse if instances in a repeat set 'cross'
at some point such that the rekeyd RECURRENCE-ID is shared between different
instances at different points in time. &nbsp;The SEQUENCE values could
match when the overlap happens so then it becomes impossible to accurately
tell which instance is being referred to at any given time. &nbsp;To see
this, simply do the following 5 steps: <br>
<br>
1: Create a 2 entry repeating set for every Wednesday @ a given time. <br>
2: Reschedule the first instance to the Friday between the two Wednesdays
(now SEQUENCE:1) <br>
3: Reschedule it again to the day before (Thursday, SEQUENCE:2) <br>
4: Reschedule the second instance to the Friday between the two Wednesdays
(now SEQUENCE:1 and same RECURRENCE-ID) <br>
5: Reschedule it again to another day. <br>
<br>
So now if a REPLY for RECURRENCE-ID:THURSDAY / SEQUENCE:1 comes in, can
you tell me which instance it was for AND more to the point what the correct
new RECURRENCE-ID is?? &nbsp;Didn't think you could, at least not accurately...
</tt></font><font size=3><br>
</font>
<br><font size=2 face="sans-serif">Essentially if each instance gets rescheduled
to the same RECURRENCE-ID / SEQUENCE values at some point then you cannot
accurately match the invitees REPLY for that UID / RECURRENCE-ID / SEQUENCE
to the proper instance.</font>
<br>
<br><font size=2><tt>&gt; No are you saying 'resync' is a new METHOD -
I did not use the<br>
&gt; word METHOD - only you did in your reply.<br>
</tt></font>
<br><font size=2 face="sans-serif">Not sure how you got that all a sudden
when Ive been using that term all along and not as a new method. &nbsp;Simply
put, if the RECURRENCE-IDs get out of sync due to a missed REQUEST then
the invitee and the Organizer need to get back in sync (aka resync) so
that they can do workflow on the same instances and be certain that that
both sides are dealing with the same data/dates/times/etc. &nbsp;Doug was
the only one to use &quot;SYNC&quot; in any message so far...</font>
<br>
<br><font size=2><tt>&gt; &gt; You also seem to agree that <br>
&gt; &gt; its impossible to resync a particular instance if you miss 1
<br>
&gt; &gt; rescheduling REQUEST in your model;<br>
&gt; <br>
&gt; NO I SAID IT IS POSSIBLE - DO A REFRESH.<br>
</tt></font>
<br><font size=2 face="sans-serif">Yes you've said that all along. &nbsp;So
lets get the terminology straight shall we?</font>
<br>
<br><font size=2 face="sans-serif">The invitee is the only party who sends
REFRESH messages and thus the only party in this who &quot;does a REFRESH&quot;
or &quot;full REFRESH&quot; as its been called. &nbsp;REFRESH is specifically
defined as:</font>
<br>
<br><font size=2><tt>3.2.6 REFRESH<br>
<br>
 &nbsp; The &quot;REFRESH&quot; method in a &quot;VEVENT&quot; calendar
component is used by<br>
 &nbsp; &quot;Attendees&quot; of an existing event to request an updated
description<br>
 &nbsp; from the event &quot;Organizer&quot;. The &quot;REFRESH&quot; method
must specify the<br>
 &nbsp; &quot;UID&quot; property of the event to update. <b>A recurrence
instance of an<br>
 &nbsp; event may be requested by specifying the &quot;RECURRENCE-ID&quot;
property<br>
 &nbsp; corresponding to the associated event.</b> The &quot;Organizer&quot;
responds with<br>
 &nbsp; the latest description and version of the event.</tt></font>
<br>
<br><font size=2 face="sans-serif">The Organizers response to a REFRESH
messge is to send &quot;</font><font size=2><tt>the latest description
and version of the event</tt></font><font size=2 face="sans-serif">&quot;
which would be in the form of a REQUEST. &nbsp;So far I think we all agree.
&nbsp;As the hilighted description above says, RECURRENCE-IDs are used
when particular instances are being referenced. &nbsp;In the delta model
of things this would <b><u>_NEVER</u></b>_ be necessary since the only
reason to actually do a REFRESH is because the invitee needs to get back
in sync w/the Organizer. &nbsp;_<b><u>ANY</u></b>_ RECURRENCE-ID used would
be invalid from the Organizers perspective if the invitee and Organzier
are out of sync so that negates the whole benefit of REFRESH. &nbsp;If
the invitee is current with the Organzier then why would they need to do
a REFRESH in the first place? &nbsp;Thus there is no apparent need for
REFRESH for particular instances.</font>
<br>
<br><font size=2 face="sans-serif">Now it did appear that Doug was intending
to send a REFRESH message without a RECURRENCE-ID in it and that was what
he means by a &quot;full REFRESH&quot; or all other references to &quot;doing&quot;
REFRESH, etc. &nbsp;If Im wrong I appologize and Ill await my punishment
for putting words into Dougs mouth. &nbsp;However it it should be noted
that the only way for a REFRESH on a particular RECURRENCE-ID to be of
any value is if RECURRENCE-ID does not change between reschedules. &nbsp;
The only other alternative reading is that someone just decided for no
real reason that they wanted to ask for a REFRESH just because they can.
&nbsp; All that results in is a new REQUEST has the same UID / RECURRENCE-ID
/ SEQUENCE and a newer DTSTAMP.</font>
<br>
<br><font size=2 face="sans-serif">Now by NOT using RECURRENCE-ID in the
REFRESH message the invitee is asking for a refresh of the entire event
or set (assuming its a repeating entry). &nbsp;As noted above, if the invitee
is just invited to a particular instance then the REQUEST MUST contain
a RECURRENCE-ID property. &nbsp;However if RECURRENCE-ID change with each
reschedule of each instance then there is still no way to match up the
initial REQUEST for RECURRENCE-ID:XXX at SEQUENCE:5 with RECURRENCE-ID:YYY
at SEQUENCE:10. &nbsp;As such the invitee thinks they are invited to 2
instances rather than just the single one.</font>
<br>
<br><font size=2 face="sans-serif">Still, this is all a distraction from
the facts that iCalendar was misinterpreted (and the parts that directly
say RECURRENCE-ID does not change were ignored) and that iTIP does NOT
say that RECURRENCE-ID changes with each reschedule REQUEST (recheck Bullet
1 under Section 4.7.2 and its case description if you think otherwise).</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 0075DDB185256D58_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul  3 18:04:30 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08791
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 18:04:29 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Lrwqt023554
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 14:53:58 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63Lrw8r023553
	for ietf-calendar-bks; Thu, 3 Jul 2003 14:53:58 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Lrvqt023548
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 14:53:57 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F035B94.3080402@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OFA324D02E.C25C8EFF-ON85256D58.00767E21-85256D58.0077EE7D@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 3 Jul 2003 17:49:39 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/03/2003
 05:53:52 PM,
	Serialize complete at 07/03/2003 05:53:52 PM
Content-Type: multipart/alternative; boundary="=_alternative 0077EE7885256D58_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0077EE7885256D58_=
Content-Type: text/plain; charset="US-ASCII"

Doug pondered on 07/02/2003 06:24:20 PM:
>  > ...and so far the discussions were foucsed
> > around the most common and basic model of invitations and reschedules 
to 
> > the initial set.
> 
> I have not seen any one claim that including you in the debate.
> But assuming it is - so what?

The point is to put misinterpretations to rest and get on with other WG 
business.  I just do not want some folks misinterpreation of the RFCs to 
become contagious causing us no end of grief to those that read the RFCs 
correctly.

Lets get back to the facts of this shall we:

1: iCalendar clearly says that RECURRENCE-ID does not change on a 
reschedule.  For those that missed it the last 4 times:

   The date/time value is set to the time when the original recurrence
   instance would occur; meaning that if the intent is to change a
   Friday meeting to Thursday, the date/time is still set to the
   original Friday meeting.

2: iCalendar has been misquoted/misread by some as saying that the 
RECURRENCE-ID does change on a reschedule.  The misunderstanding stems 
from:

   The "RECURRENCE-ID" property is used in conjunction with the "UID"
   and "SEQUENCE" property to identify a particular instance of a
   recurring event, to-do or journal. For a given pair of "UID" and
   "SEQUENCE" property values, the "RECURRENCE-ID" value for a
   recurrence instance is fixed. When the definition of the recurrence
   set for a calendar component changes, and hence the "SEQUENCE"
   property value changes, the "RECURRENCE-ID" for a given recurrence
   instance might also change.

which says that RECURRENCE-ID "might also change" but ONLY for the case 
where "the definition of the recurrence set for a calendar component 
changes".  A reschedule of an entry in the recurrence (aka repeat) set is 
NOT changing the set definition!  Changing the definition is going from 
repeating "Every Monday for 3 weeks" to "Every Wednesday and Thursday for 
2 months" (or some other pattern).  Sounds like confusion on the part of 
some between the two.

3: iTIP does not describe changing the RECURRENCE-ID value on a reschedule 
depsite instances to the contrary.  Section 4.7.2 Bad RECURRENCE-ID says:

   1.  The component with the referenced "UID" and "RECURRENCE-ID" has
       been found but the "SEQUENCE" number in the calendar store does
       not match that of the ITIP message.

In order for the UID and RECURRENCE-ID  to match but the SEQUENCE to be 
"larger" or "smaller" then obviously UID and RECURRENCE-ID cannot be 
changed when SEQUENCE changes or they would never match the correct 
instance in question.

Section 2.1.5 Message Sequencing clearly states that UID and RECURRENCE-ID 
are to be used as the primary key when sequencing any iTIP message for a 
particular repeating instance.  They are to be combined into a key to find 
the particular instance and then SEQUENCE is to be looked for (as 
described in Section 4.7.2 bullet 1 even).  Missed messages at lower 
SEQUENCE values are irrelevant because they are obsoleted by the newer 
SEQUENCE versions.  As such missed messages are not a problem for workflow 
(unless you need them to change the RECURRENCE-ID values).

Section 3.2.2 REQUEST clearly describes how to differentiate between a new 
request and a reschedule of an existing one.  If RECURRENCE-ID changed on 
each reschedule then it would be impossible to match it to an existing 
entry correctly. 

Any attempts to change the model so that RECURRENCE-ID changes on each 
reschedule is either a misinterpretation of the RFCs or an attempt to 
change their behaviour that is clearly outlined otherwise. 

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 0077EE7885256D58_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug pondered on 07/02/2003 06:24:20 PM:<br>
&gt; &nbsp;&gt; ...and so far the discussions were foucsed<br>
&gt; &gt; around the most common and basic model of invitations and reschedules
to <br>
&gt; &gt; the initial set.<br>
&gt; <br>
&gt; I have not seen any one claim that including you in the debate.<br>
&gt; But assuming it is - so what?<br>
</tt></font>
<br><font size=2 face="sans-serif">The point is to put misinterpretations
to rest and get on with other WG business. &nbsp;I just do not want some
folks misinterpreation of the RFCs to become contagious causing us no end
of grief to those that read the RFCs correctly.</font>
<br>
<br><font size=2 face="sans-serif">Lets get back to the facts of this shall
we:</font>
<br>
<br><font size=2 face="sans-serif">1: iCalendar clearly says that RECURRENCE-ID
does not change on a reschedule. &nbsp;For those that missed it the last
4 times:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The date/time value is set to the time
when the original recurrence<br>
 &nbsp; instance would occur; meaning that if the intent is to change a<br>
 &nbsp; Friday meeting to Thursday, the date/time is still set to the<br>
 &nbsp; original Friday meeting.</tt></font>
<br>
<br><font size=2 face="sans-serif">2: iCalendar has been misquoted/misread
by some as saying that the RECURRENCE-ID does change on a reschedule. &nbsp;The
misunderstanding stems from:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The &quot;RECURRENCE-ID&quot; property
is used in conjunction with the &quot;UID&quot;<br>
 &nbsp; and &quot;SEQUENCE&quot; property to identify a particular instance
of a<br>
 &nbsp; recurring event, to-do or journal. For a given pair of &quot;UID&quot;
and<br>
 &nbsp; &quot;SEQUENCE&quot; property values, the &quot;RECURRENCE-ID&quot;
value for a<br>
 &nbsp; recurrence instance is fixed. When the definition of the recurrence<br>
 &nbsp; set for a calendar component changes, and hence the &quot;SEQUENCE&quot;<br>
 &nbsp; property value changes, the &quot;RECURRENCE-ID&quot; for a given
recurrence<br>
 &nbsp; instance might also change.</tt></font>
<br>
<br><font size=2 face="sans-serif">which says that RECURRENCE-ID </font><font size=2><tt>&quot;might
also change&quot;</tt></font><font size=2 face="sans-serif"> but ONLY for
the case where </font><font size=2><tt>&quot;the definition of the recurrence
set for a calendar component changes&quot;</tt></font><font size=2 face="sans-serif">.
&nbsp;A reschedule of an entry in the recurrence (aka repeat) set is NOT
changing the set definition! &nbsp;Changing the definition is going from
repeating &quot;Every Monday for 3 weeks&quot; to &quot;Every Wednesday
and Thursday for 2 months&quot; (or some other pattern). &nbsp;Sounds like
confusion on the part of some between the two.</font>
<br>
<br><font size=2 face="sans-serif">3: iTIP does not describe changing the
RECURRENCE-ID value on a reschedule depsite instances to the contrary.
&nbsp;Section 4.7.2 Bad RECURRENCE-ID says:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;1. &nbsp;The component with the referenced
&quot;UID&quot; and &quot;RECURRENCE-ID&quot; has<br>
 &nbsp; &nbsp; &nbsp; been found but the &quot;SEQUENCE&quot; number in
the calendar store does<br>
 &nbsp; &nbsp; &nbsp; not match that of the ITIP message.</tt></font>
<br>
<br><font size=2 face="sans-serif">In order for the UID and RECURRENCE-ID
&nbsp;to match but the SEQUENCE to be &quot;larger&quot; or &quot;smaller&quot;
then obviously UID and RECURRENCE-ID cannot be changed when SEQUENCE changes
or they would never match the correct instance in question.</font>
<br>
<br><font size=2 face="sans-serif">Section 2.1.5 Message Sequencing clearly
states that UID and RECURRENCE-ID are to be used as the primary key when
sequencing any iTIP message for a particular repeating instance. &nbsp;They
are to be combined into a key to find the particular instance and then
SEQUENCE is to be looked for (as described in Section 4.7.2 bullet 1 even).
&nbsp;Missed messages at lower SEQUENCE values are irrelevant because they
are obsoleted by the newer SEQUENCE versions. &nbsp;As such missed messages
are not a problem for workflow (unless you need them to change the RECURRENCE-ID
values).</font>
<br>
<br><font size=2 face="sans-serif">Section 3.2.2 REQUEST clearly describes
how to differentiate between a new request and a reschedule of an existing
one. &nbsp;If RECURRENCE-ID changed on each reschedule then it would be
impossible to match it to an existing entry correctly. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Any attempts to change the model so
that RECURRENCE-ID changes on each reschedule is either a misinterpretation
of the RFCs or an attempt to change their behaviour that is clearly outlined
otherwise. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 0077EE7885256D58_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul  3 18:14:10 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10925
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 18:14:09 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63M46qt023948
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 15:04:06 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63M46hc023947
	for ietf-calendar-bks; Thu, 3 Jul 2003 15:04:06 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63M45qt023942
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 15:04:05 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F035B94.3080402@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF456F414E.B85445FC-ON85256D58.0077F986-85256D58.0078DBF2@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 3 Jul 2003 17:59:47 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/03/2003
 06:04:00 PM,
	Serialize complete at 07/03/2003 06:04:00 PM
Content-Type: multipart/alternative; boundary="=_alternative 0078DBED85256D58_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0078DBED85256D58_=
Content-Type: text/plain; charset="US-ASCII"

Doug noted on 07/02/2003 06:24:20 PM:
> > Doug has claimed it can be resyncd and his answer is a "full REFRESH". 

> 
> Yes, per the text in iTIP.

There is no phrase "full REFRESH" in iTIP that I can find.  There is an 
iTIP REFRESH message that can contain the following properties:

METHOD              1      MUST be "REFRESH"

VEVENT              1
    ATTENDEE        1      MUST be the address of requestor
    DTSTAMP         1
    ORGANIZER       1
    UID             1      MUST be the UID associated with original
                           REQUEST
    COMMENT         0 or 1
    RECURRENCE-ID   0 or 1 MUST only if referring to an instance of a
                           recurring calendar component.  Otherwise
                           it must NOT be present.
    X-PROPERTY      0+

Since Ive been referring to resycing up a particular instance Ive been 
talking about sending a REFRESH for that particular RECURRENCE-ID (as 
described in the defintion of REFRESH).

I can only find 1 instance of the phrase 'full' in iTIP and thats NOT in 
REFESH (besides "Full Copyright"). It is in ADD:

                                                   Unlike the "REQUEST"
   method, when using issuing an "ADD" method, the "Organizer" does not
   send the full "VEVENT" description; only the new instance(s).

so thats clearly not what Doug is referring to.

Arnaud asked if Doug was referring to a REFRESH message that had no 
RECURRENCE-ID and I thought he said yes.  However he later said no when I 
checked.  The definition for REFRESH says:

                                         A recurrence instance of an
   event may be requested by specifying the "RECURRENCE-ID" property
   corresponding to the associated event. The "Organizer" responds with
   the latest description and version of the event.

and the restriction table clearly says "MUST only if referring to an 
instance" (which we were or at least I was since I had an particular 
RECURRENCE-ID I need to REFRESH for). 

Since the REQUEST was for a single instance (thats all I was invited to) 
then the REQUEST the Organzier sends in response must also contain a 
RECURRENCE-ID so we can be sure all REQUEST/REPLYs are relevant to the 
same instance and not the repeat set as a whole.

In any case I view some of this as moot given the fact that nothing in 
iCalendar or iTIP supports the claim that RECURRENCE-IDs change on each 
instance reschedule...

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 0078DBED85256D58_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug noted on 07/02/2003 06:24:20 PM:<br>
&gt; &gt; Doug has claimed it can be resyncd and his answer is a &quot;full
REFRESH&quot;. <br>
&gt; <br>
&gt; Yes, per the text in iTIP.<br>
</tt></font>
<br><font size=2 face="sans-serif">There is no phrase &quot;full REFRESH&quot;
in iTIP that I can find. &nbsp;There is an iTIP REFRESH message that can
contain the following properties:</font>
<br>
<br><font size=2><tt>METHOD &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1
&nbsp; &nbsp; &nbsp;MUST be &quot;REFRESH&quot;<br>
<br>
VEVENT &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1<br>
 &nbsp; &nbsp;ATTENDEE &nbsp; &nbsp; &nbsp; &nbsp;1 &nbsp; &nbsp; &nbsp;MUST
be the address of requestor<br>
 &nbsp; &nbsp;DTSTAMP &nbsp; &nbsp; &nbsp; &nbsp; 1<br>
 &nbsp; &nbsp;ORGANIZER &nbsp; &nbsp; &nbsp; 1<br>
 &nbsp; &nbsp;UID &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1 &nbsp; &nbsp;
&nbsp;MUST be the UID associated with original<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; REQUEST<br>
 &nbsp; &nbsp;COMMENT &nbsp; &nbsp; &nbsp; &nbsp; 0 or 1<br>
 &nbsp; &nbsp;RECURRENCE-ID &nbsp; 0 or 1 MUST only if referring to an
instance of a<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; recurring calendar component. &nbsp;Otherwise<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; it must NOT be present.<br>
 &nbsp; &nbsp;X-PROPERTY &nbsp; &nbsp; &nbsp;0+</tt></font>
<br>
<br><font size=2 face="sans-serif">Since Ive been referring to resycing
up a particular instance Ive been talking about sending a REFRESH for that
particular RECURRENCE-ID (as described in the defintion of REFRESH).</font>
<br>
<br><font size=2 face="sans-serif">I can only find 1 instance of the phrase
'full' in iTIP and thats NOT in REFESH (besides &quot;Full Copyright&quot;).
It is in ADD:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unlike the &quot;REQUEST&quot;<br>
 &nbsp; method, when using issuing an &quot;ADD&quot; method, the &quot;Organizer&quot;
does not<br>
 &nbsp; send the full &quot;VEVENT&quot; description; only the new instance(s).</tt></font>
<br>
<br><font size=2 face="sans-serif">so thats clearly not what Doug is referring
to.</font>
<br>
<br><font size=2 face="sans-serif">Arnaud asked if Doug was referring to
a REFRESH message that had no RECURRENCE-ID and I thought he said yes.
&nbsp;However he later said no when I checked. &nbsp;The definition for
REFRESH says:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp;A recurrence instance of an<br>
 &nbsp; event may be requested by specifying the &quot;RECURRENCE-ID&quot;
property<br>
 &nbsp; corresponding to the associated event. The &quot;Organizer&quot;
responds with<br>
 &nbsp; the latest description and version of the event.<br>
</tt></font>
<br><font size=2 face="sans-serif">and the restriction table clearly says
&quot;MUST only if referring to an instance&quot; (which we were or at
least I was since I had an particular RECURRENCE-ID I need to REFRESH for).
&nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Since the REQUEST was for a single instance
(thats all I was invited to) then the REQUEST the Organzier sends in response
must also contain a RECURRENCE-ID so we can be sure all REQUEST/REPLYs
are relevant to the same instance and not the repeat set as a whole.</font>
<br>
<br><font size=2 face="sans-serif">In any case I view some of this as moot
given the fact that nothing in iCalendar or iTIP supports the claim that
RECURRENCE-IDs change on each instance reschedule...</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 0078DBED85256D58_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul  3 18:57:34 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19098
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 18:57:33 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Mmmqt026393
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 15:48:48 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63MmmHl026392
	for ietf-calendar-bks; Thu, 3 Jul 2003 15:48:48 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Mmlqt026387
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 15:48:47 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h63MmiOR027383
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 15:48:47 -0700
Message-ID: <3F04B2C7.6050800@Royer.com>
Date: Thu, 03 Jul 2003 16:48:39 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
References: <OFDEEF32A6.DFABA59A-ON85256D58.0073776C-85256D58.0075DDB6@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010006000900040700030503"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms010006000900040700030503
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug claimed on 07/02/2003 06:46:04 PM:
>  > No you proposed a new way to invite someone, you did not show
>  > that anything is busted.
> 
>

> It can become worse if instances in a repeat set 'cross' at some point 
> such that the rekeyd RECURRENCE-ID is shared between different instances 
> at different points in time.  The SEQUENCE values could match when the 
> overlap happens so then it becomes impossible to accurately tell which 
> instance is being referred to at any given time.  To see this, simply do 
> the following 5 steps:
> 
> 1: Create a 2 entry repeating set for every Wednesday @ a given time.
> 2: Reschedule the first instance to the Friday between the two 
> Wednesdays (now SEQUENCE:1)
> 3: Reschedule it again to the day before (Thursday, SEQUENCE:2)
> 4: Reschedule the second instance to the Friday between the two 
> Wednesdays (now SEQUENCE:1 and same RECURRENCE-ID)
> 5: Reschedule it again to another day.
>
> So now if a REPLY for RECURRENCE-ID:THURSDAY / SEQUENCE:1 comes in, can 
> you tell me which instance it was for AND more to the point what the 
> correct new RECURRENCE-ID is??  Didn't think you could, at least not 
> accurately...

If a REPLY comes in with SEQUENCE:1 and the current object is SEQUENCE:2
Do the following:

        Did you already send them a SEQUENCE:2 request:

             yes - toss the SEQUENCE:1 reply
                   and wait for the SEQUENCE:2 reply

             no  - toss the SEQUENCE:1 reply
                   and send them a SEQUENCE:2 REQUEST

Problem solved.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms010006000900040700030503
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDMyMjQ4MzlaMCMGCSqGSIb3DQEJBDEWBBQB
2kh1GFEe7MCEtULTTTOZTeacDTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEABcGfAL+5H3AS
aRsb1tr4PpJhvFaSSTGx+DogyPxrcl0HyoBUsklBvFoJ/fBgNiDNInbCPcyr8tgelpN/l4ca
ocV466hM515yjdETT7fMZIGWKetrWBljjc+CAbnnOunACfvTT9ba2AXt0NcBkaaST7942grA
HZRn5yLZsKEWrQLbCTz+wPhraZj3Q9S3LwWCg0Pqr0yglp44kkMLk9qj/HCugSyz5gFQwn4V
ADNdDLRy2THNkwFb9UgHAjTdcj2MMEkN/sJJklTdcSv+0MXDnGfFSkTocHw20tvlGU/UNYS0
iP2mEQY9Nzk7gjKnjPYz/VhWDRwwU1jDvcc3KGclOwAAAAAAAA==
--------------ms010006000900040700030503--



From owner-ietf-calendar@mail.imc.org  Thu Jul  3 19:03:23 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19430
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 19:03:22 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Mrcqt026592
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 15:53:38 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63MrcbV026591
	for ietf-calendar-bks; Thu, 3 Jul 2003 15:53:38 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Mrbqt026586
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 15:53:37 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h63MrYOR027425
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 15:53:37 -0700
Message-ID: <3F04B3E8.9000800@Royer.com>
Date: Thu, 03 Jul 2003 16:53:28 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF456F414E.B85445FC-ON85256D58.0077F986-85256D58.0078DBF2@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070800070108040901000601"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms070800070108040901000601
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug noted on 07/02/2003 06:24:20 PM:
>  > > Doug has claimed it can be resyncd and his answer is a "full REFRESH".
>  >
>  > Yes, per the text in iTIP.
> 
> There is no phrase "full REFRESH" in iTIP that I can find.

Your correct bruce, but we have been using that term
ever since Arnaud (I think) pointed out there was
a misunderstand about what a REFRESH vs. instance
specific REFRESH.

Perhaps you mised that post?

--


  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms070800070108040901000601
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDMyMjUzMjhaMCMGCSqGSIb3DQEJBDEWBBQl
CLGMj3yM5RGCkXMyTnU/oq7iGjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAPj4umpWX1w3f
FV/6U6ZS2FfmNWjaYz2udZTG2ogOkNhffux4BnWNjdc7Nmz6/dVGcEACRbk25hdK+8mpZobW
RCezeSEDRYoRS1CReGIvT1AdtGWn4hW9JUeWsH6D4L7tLGM2Qu2t/R1ba+1tiaGNgwMIHqXV
bSU60Ra7Yc70aiGge1dWGeOToZLp+o76laNkUdT3mJWgtVj6vMga+60fSuj0HWb4hoKfgiop
RVDsEP41/As0IFZz7zXj8Lg2EZ+7S/Y6a30AbwiPPmbC1SxVL//jdp/jUElaGzgMduQdbyUd
1CwjFZSP2Q7SnBhrZto2qVJlEyxJt0T2vHraT45+8AAAAAAAAA==
--------------ms070800070108040901000601--



From owner-ietf-calendar@mail.imc.org  Thu Jul  3 19:30:12 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25857
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 19:30:11 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63NJDqt027575
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 16:19:13 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63NJD85027574
	for ietf-calendar-bks; Thu, 3 Jul 2003 16:19:13 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63NJCqt027569
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 16:19:12 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h63NJ9OR027625
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 16:19:12 -0700
Message-ID: <3F04B9E4.2000100@Royer.com>
Date: Thu, 03 Jul 2003 17:19:00 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF456F414E.B85445FC-ON85256D58.0077F986-85256D58.0078DBF2@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030604050608020603070003"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms030604050608020603070003
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:

> In any case I view some of this as moot given the fact that nothing in 
> iCalendar or iTIP supports the claim that RECURRENCE-IDs change on each 
> instance reschedule...

I have quoted it several times from iCal where is says that the
UID and SEQUENCE property identify a particular instance (3rd
paragraph below). And one reason to increment the SEQUENCE number
is a recurrence change. If the organizer is at SEQUENCE:X for
a given UID and it gets a REPLY for less than X, it (if it has
not already done so) needs to issue a new REQUEST/SEQUNCE:X to
that attendee. If an ATTENDEE has SEQUENCE:W where W < X,
and gets an instance specific update for SEQUENCE:X,
then the attendee needs to do a REFRESH, the attendee can
toss the instance specific update and wait for the REQUEST
(REFRESH reply) from the ORGANIZER.

The text is in iCal is clear, the UID+SEQUENCE pair identify
a particular instance (RECURRENCE-ID).

  4.8.4.4 Recurrence ID

    Property Name: RECURRENCE-ID

    Purpose: This property is used in conjunction with the "UID" and
    "SEQUENCE" property to identify a specific instance of a recurring
    "VEVENT", "VTODO" or "VJOURNAL" calendar component. The property
    value is the effective value of the "DTSTART" property of the
    recurrence instance.

    ...

    Description: The full range of calendar components specified by a
    recurrence set is referenced by referring to just the "UID" property
    value corresponding to the calendar component. The "RECURRENCE-ID"
    property allows the reference to an individual instance within the
    recurrence set.

    ...The "RECURRENCE-ID" property is used in conjunction with the "UID"
    and "SEQUENCE" property to identify a particular instance of a
    recurring event, to-do or journal. For a given pair of "UID" and
    "SEQUENCE" property values, the "RECURRENCE-ID" value for a
    recurrence instance is fixed..


    ...When the definition of the recurrence
    set for a calendar component changes, and hence the "SEQUENCE"
    property value changes, the "RECURRENCE-ID" for a given recurrence
    instance might also change. ...

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms030604050608020603070003
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDMyMzE5MDBaMCMGCSqGSIb3DQEJBDEWBBQW
smvwl958ROOrs1G/vwAMCNA5KjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAj0P9CJDpvLNF
xfd/6rWAwAyubNlIH9kehtoqAVL+sepoXigfPwJwTRH5i7bOcPq1Ny5xYDUi8RisjoUZVCNE
rY+2yqMLbAVymjZSubafk7UWjOOXCbQk9RrkrkECMnohwQUB3eGUlegdczt2mq1EpXzMWg3U
iKsNWLGPokFXFcSzXxvZv0YkmyLeqgwAIufekQW9gDnjYQYezk2C7Upfn9NtRswrypsVOxiz
yLArKMWxq9N6m6JCa4hG1jaDIbHQneUHH000k+GcH5GSs3bu1Nk18xj5Ukmq2JiLZ8DYeBHZ
LXHHGlo5Y+bwkDQaSlyXkv3BtuGyWaU/O20PemEl5gAAAAAAAA==
--------------ms030604050608020603070003--



From owner-ietf-calendar@mail.imc.org  Thu Jul  3 20:12:04 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27818
	for <calsch-archive@lists.ietf.org>; Thu, 3 Jul 2003 20:12:03 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Me6qt025619
	for <ietf-calendar-bks@above.proper.com>; Thu, 3 Jul 2003 15:40:06 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h63Me6uj025618
	for ietf-calendar-bks; Thu, 3 Jul 2003 15:40:06 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h63Me5qt025612
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 15:40:05 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h63MdtOR027307
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 3 Jul 2003 15:40:05 -0700
Message-ID: <3F04B0B1.6030703@Royer.com>
Date: Thu, 03 Jul 2003 16:39:45 -0600
From: Doug Royer <Doug@Royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Fw: Correct handling of Recurrence-id
References: <OFAE306412.57C25795-ON85256D58.0075EC0C-85256D58.007618DA@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060606090802070408030404"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060606090802070408030404
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Rolled up as in fan out?

Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug asked on 07/02/2003 06:47:42 PM:
>  > I can't follow, please define what you mean by 'rolled'.
> 
> Are you serious?  That terms been used in the WG for years.  What do you 
> think it means?
> 
> 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...


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060606090802070408030404
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDMyMjM5NDVaMCMGCSqGSIb3DQEJBDEWBBQh
aUsfhm7Zx11lLy6f8TVPkPxOWzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAhksElpdiab3z
qBwoBEZDCxqCGox19WHioUYI1a1FtukczJqFi1taHqNr7mmrTn2CycwKX9SoXNNHbie/hifa
rw3+SUyltRHBfEAPV8KFrzIvFGm3fP7Y7DeV/RqwgvHtucHEO1RMKqxICGAPredwg4ZuMR89
NP1LJDpYzMCw6G2b5U5cb5SrAok0PeRTdwwa1R581EYBqgK/86YjBtR7yYABLD7asHuQko7+
fwQaXwZB7uwl2QyJdjDd3flSaGN3ipcn0v9uofRlfjERlSdP97tV4xw/yilcnDVbSw7fO16+
9Q8Zhb7WviWWatGtL5xt/sYqqSpxWqPyxfjMIdcpnwAAAAAAAA==
--------------ms060606090802070408030404--



From owner-ietf-calendar@mail.imc.org  Mon Jul  7 10:50:01 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28241
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 10:50:00 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67EXrqt066879
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 07:33:53 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67EXrOd066878
	for ietf-calendar-bks; Mon, 7 Jul 2003 07:33:53 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67EXqqt066872
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 07:33:52 -0700 (PDT)
	(envelope-from Robert_Ransdell@notesdev.ibm.com)
In-Reply-To: <3F01DBE5.2000703@Royer.com>
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP draft - last call, etc.
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V65_06232003 June 23, 2003
Message-ID: <OFA0145FEA.337858C7-ON85256D5C.004F8DAC-85256D5C.004F8DCA@notesdev.ibm.com>
From: Robert_Ransdell@notesdev.ibm.com
Date: Mon, 7 Jul 2003 10:29:13 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/07/2003
 10:33:36 AM,
	Serialize complete at 07/07/2003 10:33:36 AM
Content-Type: multipart/alternative; boundary="=_alternative 004F8DC085256D5C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 004F8DC085256D5C_=
Content-Type: text/plain; charset="US-ASCII"

I has not died... We have been on vacation.
_____________________
Note: new email address

tom_ransdell@notesdev.ibm.com



Doug Royer <Doug@royer.com> 
Sent by: owner-ietf-calendar@mail.imc.org
07/01/2003 03:07 PM
Please respond to
"ietf-calendar@imc.org" <ietf-calendar@imc.org>


To
"ietf-calendar@imc.org" <ietf-calendar@imc.org>
cc

Subject
Re: CAP draft - last call, etc.








Satya Vempati wrote:
> Some of the iCAL/iTIP questions will impact the decisions on CAP. 
> Especially, the outcome of the discussion on RECURRENCE-ID fundamentally 

> affects the CAP spec based on how it is eventually resolved.

I can see how that proposal could have effected the iTIP protocol
but not the CAP protocol. It would indirectly effected CUAs that used
CAP to store local CU data in the object across recurrence rule
changes. No matter which way it went, it would not have effected
the CAP 'protocol' at all. It would have effected all CUAs that
used iTIP to process scheduling requests via iMIP, CAP, or
any other transport.

That proposal that in iCal version-next that the recurrence-id
be tied to SEQUECEN:0  objects in order to be compatible with some
vendors seems to have died. (read Bruce's last email on the subject).
It was never necessary and I think that Burce agrees.

Does any disagree?

> IMHO, one final draft (hopefully 11) to iron out the differences is 
> required before going to RFC.



-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards


--=_alternative 004F8DC085256D5C_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">I has not died... We have been on vacation.</font>
<br><font size=2 face="sans-serif">_____________________<br>
Note: new email address<br>
<br>
tom_ransdell@notesdev.ibm.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Doug Royer &lt;Doug@royer.com&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/01/2003 03:07 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
&quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">&quot;ietf-calendar@imc.org&quot;
&lt;ietf-calendar@imc.org&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: CAP draft - last call,
etc.</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
Satya Vempati wrote:<br>
&gt; Some of the iCAL/iTIP questions will impact the decisions on CAP.
<br>
&gt; Especially, the outcome of the discussion on RECURRENCE-ID fundamentally
<br>
&gt; affects the CAP spec based on how it is eventually resolved.<br>
<br>
I can see how that proposal could have effected the iTIP protocol<br>
but not the CAP protocol. It would indirectly effected CUAs that used<br>
CAP to store local CU data in the object across recurrence rule<br>
changes. No matter which way it went, it would not have effected<br>
the CAP 'protocol' at all. It would have effected all CUAs that<br>
used iTIP to process scheduling requests via iMIP, CAP, or<br>
any other transport.<br>
<br>
That proposal that in iCal version-next that the recurrence-id<br>
be tied to SEQUECEN:0 &nbsp;objects in order to be compatible with some<br>
vendors seems to have died. (read Bruce's last email on the subject).<br>
It was never necessary and I think that Burce agrees.<br>
<br>
Does any disagree?<br>
<br>
&gt; IMHO, one final draft (hopefully 11) to iron out the differences is
<br>
&gt; required before going to RFC.<br>
<br>
<br>
<br>
-- <br>
<br>
 &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
 &nbsp;-------------------------------|-----------------------------<br>
 &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; | Office: (208)612-INET<br>
 &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards
- You Need Standards<br>
</tt></font>
<br>
--=_alternative 004F8DC085256D5C_=--


From owner-ietf-calendar@mail.imc.org  Mon Jul  7 13:39:26 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04837
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 13:39:25 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67HRLqt079170
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 10:27:21 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67HRLoq079169
	for ietf-calendar-bks; Mon, 7 Jul 2003 10:27:21 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67HRIqt079162
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 10:27:19 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: Satya Vempati <satyanarayana.vempati@sun.com>
Cc: "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: RE: CAP draft - last call, etc.
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFA903242A.F5DB98E3-ON85256D5C.005EEC23-85256D5C.005FE207@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Mon, 7 Jul 2003 13:27:17 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/07/2003 01:27:21 PM,
	Serialize complete at 07/07/2003 01:27:21 PM
Content-Type: multipart/alternative; boundary="=_alternative 005FE1EA85256D5C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 005FE1EA85256D5C_=
Content-Type: text/plain; charset="us-ascii"

Hi Satya, I agree with your comments.  That's why we do last drafts. Based 
on a conversation I had over the weekend, I don't believe the 
Recurrence-Id issue is going to impact CAP.  Frank Dawson, one of the 
original authors of iCal and iTIP has chatted with Derek, another of the 
authors and is going to give us some comments to help clear this up. 
Several people have already "sort of" agreed with Bruce's assertions 
regarding Recurrence-IDs and his opinion of what the draft means.  It is 
Bruce's job as the Methods Reviewer for those drafts to make sure changes 
to them don't break the RFC's and to interpret comments regarding those 
drafts. 

Now, back to the discussion about CAP.  I think we are ok with CAP as it 
pertains to Recurrece-ID's but that will be confirmed a bit later.  What's 
left in CAP that needs to be fixed/removed/discussed.  Bruce brought up 
Scoping.  I don't see where that was resolved.  Is it an issue?  List?

If someone sees other items in CAP that need to be 
fixed/removed/discussed, please discuss them now.  And if you have text 
that should change, provide your example as text so we can snap it into 
the draft.  That really helps the editor.

Thanks!




Satya Vempati <satyanarayana.vempati@sun.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/01/2003 12:46

 
        To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
        cc: 
        Subject:        RE: CAP draft - last call, etc.


Some of the iCAL/iTIP questions will impact the decisions on CAP. 
Especially, the outcome of the discussion on RECURRENCE-ID fundamentally 
affects the CAP spec based on how it is eventually resolved.

IMHO, one final draft (hopefully 11) to iron out the differences is 
required before going to RFC.

-----Original Message-----



From: Doug Royer [mailto:Doug@royer.com]
Sent: Monday, June 30, 2003 8:19 PM
To: ietf-calendar@imc.org
Subject: Re: CAP draft - last call, etc.




Items that will be changed in the -11 version of the draft.

(1) Sorting is out per this WG. (I submitted my own add on draft).
(2) The ABNF will be fixed per the email on this WG.
(3) Various typos sent to me and this list.
(4) CS to generate FREEBUSY data (NOT CUA).

As of the San Francisco IETF meeting (-10 release) there have been no
other new CAP issues that seem to have reach consensus. The only
new issue seems to be if TARGET will default and I did not think
that made it past a couple of questions and opinions sent to the list.

Unless I missed something, all of the other issues are
all iCal/iTIP/iMIP issues.

PLEASE SPEAK UP if you think that something else should make the -11
version of the draft - I AM EDITING IT NOW.

Still To do:

(I) Beep profile.
(II) Document the 1:1 or 1:MANY replies.

Item (II) was discussed in S.F. and the thoughts were that
you would bundle all single TARGET replies in one blob,
and for each unique TARGET in the CS reply, the CS would
send another blob of data.

pregen@egenconsulting.com wrote:
> 
> Well, there's been a lot of traffic going on about all sort of issues 
> and topics.  However, it came to a halt when one note came up with what 
> may be a "show-stopper."  So, I think we need to make a decision here. 
>  Do we take items that are too hard to fix, remove them, and put in an 
> addendum that says "the following items need to be resolved in the next 
> version"?  Or do we try to take a stab at fixing them.  We need to get a 

> version of CAP into RFC status.  We need to get people interoperating so 

> we can see what's really working and what's really hosed badly.  I asked 

> for a last call and that didn't work.  We really do need to get this out 

> the door.  Therefore, I'm once again asking for a last hard look at what 

> can stay and what needs to go in the current CAP draft. If it's broken 
> and needs a lot of work - it goes out.  I am going to go back over the 
> last year's thr! eads and see what I can determine are the big issues. 
>  I'll post a note to the list with the items and will ask for a "hm" 
> from the list as to whether the item stays or goes.  If it goes, we'll 
> need help changing the draft to remove all text regarding that topic.
> 
> If you disagree with the items I post - say so.  If you agree with the 
> items - say so.  That way I know people are reading the list and will 
> agree with what we produce as the final draft. 
> 
> Cool?
> ___________________
> Patricia Egen Consulting
> www.egenconsulting.com
> 423-875-2652


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards



--=_alternative 005FE1EA85256D5C_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Hi Satya, I agree with your comments. &nbsp;That's why we do last drafts. &nbsp;Based on a conversation I had over the weekend, I don't believe the Recurrence-Id issue is going to impact CAP. &nbsp;Frank Dawson, one of the original authors of iCal and iTIP has chatted with Derek, another of the authors and is going to give us some comments to help clear this up. &nbsp;Several people have already &quot;sort of&quot; agreed with Bruce's assertions regarding Recurrence-IDs and his opinion of what the draft means. &nbsp;It is Bruce's job as the Methods Reviewer for those drafts to make sure changes to them don't break the RFC's and to interpret comments regarding those drafts. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Now, back to the discussion about CAP. &nbsp;I think we are ok with CAP as it pertains to Recurrece-ID's but that will be confirmed a bit later. &nbsp;What's left in CAP that needs to be fixed/removed/discussed. &nbsp;Bruce brought up Scoping. &nbsp;I don't see where that was resolved. &nbsp;Is it an issue? &nbsp;List?</font>
<br>
<br><font size=2 face="sans-serif">If someone sees other items in CAP that need to be fixed/removed/discussed, please discuss them now. &nbsp;And if you have text that should change, provide your example as text so we can snap it into the draft. &nbsp;That really helps the editor.</font>
<br>
<br><font size=2 face="sans-serif">Thanks!</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Satya Vempati &lt;satyanarayana.vempati@sun.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/01/2003 12:46</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;RE: CAP draft - last call, etc.</font></table>
<br>
<br>
<br><font size=2>Some of the iCAL/iTIP questions will impact the decisions on CAP. Especially, the outcome of the discussion on RECURRENCE-ID fundamentally affects the CAP spec based on how it is eventually resolved.</font>
<br>
<br><font size=2>IMHO, one final draft (hopefully 11) to iron out the differences is required before going to RFC.</font>
<br>
<br><font size=2>-----Original Message-----</font>
<br>
<br>
<br>
<br><font size=2>From: Doug Royer [mailto:Doug@royer.com]</font>
<br><font size=2>Sent: Monday, June 30, 2003 8:19 PM</font>
<br><font size=2>To: ietf-calendar@imc.org</font>
<br><font size=2>Subject: Re: CAP draft - last call, etc.</font>
<br>
<br>
<br>
<br>
<br><font size=2>Items that will be changed in the -11 version of the draft.</font>
<br>
<br><font size=2>(1) Sorting is out per this WG. (I submitted my own add on draft).</font>
<br><font size=2>(2) The ABNF will be fixed per the email on this WG.</font>
<br><font size=2>(3) Various typos sent to me and this list.</font>
<br><font size=2>(4) CS to generate FREEBUSY data (NOT CUA).</font>
<br>
<br><font size=2>As of the San Francisco IETF meeting (-10 release) there have been no</font>
<br><font size=2>other new CAP issues that seem to have reach consensus. The only</font>
<br><font size=2>new issue seems to be if TARGET will default and I did not think</font>
<br><font size=2>that made it past a couple of questions and opinions sent to the list.</font>
<br>
<br><font size=2>Unless I missed something, all of the other issues are</font>
<br><font size=2>all iCal/iTIP/iMIP issues.</font>
<br>
<br><font size=2>PLEASE SPEAK UP if you think that something else should make the -11</font>
<br><font size=2>version of the draft - I AM EDITING IT NOW.</font>
<br>
<br><font size=2>Still To do:</font>
<br>
<br><font size=2>(I) Beep profile.</font>
<br><font size=2>(II) Document the 1:1 or 1:MANY replies.</font>
<br>
<br><font size=2>Item (II) was discussed in S.F. and the thoughts were that</font>
<br><font size=2>you would bundle all single TARGET replies in one blob,</font>
<br><font size=2>and for each unique TARGET in the CS reply, the CS would</font>
<br><font size=2>send another blob of data.</font>
<br>
<br><font size=2>pregen@egenconsulting.com wrote:</font>
<br><font size=2>&gt; </font>
<br><font size=2>&gt; Well, there's been a lot of traffic going on about all sort of issues </font>
<br><font size=2>&gt; and topics. &nbsp;However, it came to a halt when one note came up with what </font>
<br><font size=2>&gt; may be a &quot;show-stopper.&quot; &nbsp;So, I think we need to make a decision here. </font>
<br><font size=2>&gt; &nbsp;Do we take items that are too hard to fix, remove them, and put in an </font>
<br><font size=2>&gt; addendum that says &quot;the following items need to be resolved in the next </font>
<br><font size=2>&gt; version&quot;? &nbsp;Or do we try to take a stab at fixing them. &nbsp;We need to get a </font>
<br><font size=2>&gt; version of CAP into RFC status. &nbsp;We need to get people interoperating so </font>
<br><font size=2>&gt; we can see what's really working and what's really hosed badly. &nbsp;I asked </font>
<br><font size=2>&gt; for a last call and that didn't work. &nbsp;We really do need to get this out </font>
<br><font size=2>&gt; the door. &nbsp;Therefore, I'm once again asking for a last hard look at what </font>
<br><font size=2>&gt; can stay and what needs to go in the current CAP draft. If it's broken </font>
<br><font size=2>&gt; and needs a lot of work - it goes out. &nbsp;I am going to go back over the </font>
<br><font size=2>&gt; last year's thr! eads and see what I can determine are the big issues. </font>
<br><font size=2>&gt; &nbsp;I'll post a note to the list with the items and will ask for a &quot;hm&quot; </font>
<br><font size=2>&gt; from the list as to whether the item stays or goes. &nbsp;If it goes, we'll </font>
<br><font size=2>&gt; need help changing the draft to remove all text regarding that topic.</font>
<br><font size=2>&gt; </font>
<br><font size=2>&gt; If you disagree with the items I post - say so. &nbsp;If you agree with the </font>
<br><font size=2>&gt; items - say so. &nbsp;That way I know people are reading the list and will </font>
<br><font size=2>&gt; agree with what we produce as the final draft. &nbsp;</font>
<br><font size=2>&gt; </font>
<br><font size=2>&gt; Cool?</font>
<br><font size=2>&gt; ___________________</font>
<br><font size=2>&gt; Patricia Egen Consulting</font>
<br><font size=2>&gt; www.egenconsulting.com</font>
<br><font size=2>&gt; 423-875-2652</font>
<br>
<br>
<br><font size=2>-- </font>
<br>
<br><font size=2>&nbsp; Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com</font>
<br><font size=2>&nbsp; -------------------------------|-----------------------------</font>
<br><font size=2>&nbsp; Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET</font>
<br><font size=2>&nbsp; http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574</font>
<br><font size=2>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; Cell: (208)520-4044</font>
<br>
<br><font size=2>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;We Do Standards - You Need Standards</font>
<br>
<br>
<br>
--=_alternative 005FE1EA85256D5C_=--


From owner-ietf-calendar@mail.imc.org  Mon Jul  7 14:08:21 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05736
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 14:08:20 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67HoSqt079986
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 10:50:28 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67HoSnx079985
	for ietf-calendar-bks; Mon, 7 Jul 2003 10:50:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67HoPqt079975
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 10:50:25 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: Bruce_Kahn@notesdev.ibm.com
Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF10478229.5DD4D8DE-ON85256D5C.0061E272-85256D5C.00620064@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Mon, 7 Jul 2003 13:50:25 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/07/2003 01:50:27 PM,
	Serialize complete at 07/07/2003 01:50:27 PM
Content-Type: multipart/alternative; boundary="=_alternative 0062005985256D5C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0062005985256D5C_=
Content-Type: text/plain; charset="us-ascii"

Bruce, I think this is a good summary of the recurrence issue.  Hopefully, 
we'll have Frank's note to the list by this week to put an end to the 
discussion and make it clear for everyone. 

So, now, back to the real issue that should be on the list.  Is CAP ready? 
If not, what's wrong/missing/needs clarification/etc.... Keep those cards 
and letters coming.

And, keep it nice!




Bruce_Kahn@notesdev.ibm.com
Sent by: owner-ietf-calendar@mail.imc.org
07/03/2003 17:49

 
        To:     ietf-calendar@imc.org
        cc: 
        Subject:        Re: Correct handling of Recurrence-id



Doug pondered on 07/02/2003 06:24:20 PM:
>  > ...and so far the discussions were foucsed
> > around the most common and basic model of invitations and reschedules 
to 
> > the initial set.
> 
> I have not seen any one claim that including you in the debate.
> But assuming it is - so what?
 
The point is to put misinterpretations to rest and get on with other WG 
business.  I just do not want some folks misinterpreation of the RFCs to 
become contagious causing us no end of grief to those that read the RFCs 
correctly. 

Lets get back to the facts of this shall we: 

1: iCalendar clearly says that RECURRENCE-ID does not change on a 
reschedule.  For those that missed it the last 4 times: 

   The date/time value is set to the time when the original recurrence
  instance would occur; meaning that if the intent is to change a
  Friday meeting to Thursday, the date/time is still set to the
  original Friday meeting. 

2: iCalendar has been misquoted/misread by some as saying that the 
RECURRENCE-ID does change on a reschedule.  The misunderstanding stems 
from: 

   The "RECURRENCE-ID" property is used in conjunction with the "UID"
  and "SEQUENCE" property to identify a particular instance of a
  recurring event, to-do or journal. For a given pair of "UID" and
  "SEQUENCE" property values, the "RECURRENCE-ID" value for a
  recurrence instance is fixed. When the definition of the recurrence
  set for a calendar component changes, and hence the "SEQUENCE"
  property value changes, the "RECURRENCE-ID" for a given recurrence
  instance might also change. 

which says that RECURRENCE-ID "might also change" but ONLY for the case where "the definition of the recurrence set for a calendar component changes".  A reschedule of an entry in the recurrence (aka repeat) set is NOT 
changing the set definition!  Changing the definition is going from 
repeating "Every Monday for 3 weeks" to "Every Wednesday and Thursday for 
2 months" (or some other pattern).  Sounds like confusion on the part of 
some between the two. 

3: iTIP does not describe changing the RECURRENCE-ID value on a reschedule 
depsite instances to the contrary.  Section 4.7.2 Bad RECURRENCE-ID says: 

   1.  The component with the referenced "UID" and "RECURRENCE-ID" has
      been found but the "SEQUENCE" number in the calendar store does
      not match that of the ITIP message. 

In order for the UID and RECURRENCE-ID  to match but the SEQUENCE to be 
"larger" or "smaller" then obviously UID and RECURRENCE-ID cannot be 
changed when SEQUENCE changes or they would never match the correct 
instance in question. 

Section 2.1.5 Message Sequencing clearly states that UID and RECURRENCE-ID 
are to be used as the primary key when sequencing any iTIP message for a 
particular repeating instance.  They are to be combined into a key to find 
the particular instance and then SEQUENCE is to be looked for (as 
described in Section 4.7.2 bullet 1 even).  Missed messages at lower 
SEQUENCE values are irrelevant because they are obsoleted by the newer 
SEQUENCE versions.  As such missed messages are not a problem for workflow 
(unless you need them to change the RECURRENCE-ID values). 

Section 3.2.2 REQUEST clearly describes how to differentiate between a new 
request and a reschedule of an existing one.  If RECURRENCE-ID changed on 
each reschedule then it would be impossible to match it to an existing 
entry correctly.   

Any attempts to change the model so that RECURRENCE-ID changes on each 
reschedule is either a misinterpretation of the RFCs or an attempt to 
change their behaviour that is clearly outlined otherwise.   

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 0062005985256D5C_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Bruce, I think this is a good summary of the recurrence issue. &nbsp;Hopefully, we'll have Frank's note to the list by this week to put an end to the discussion and make it clear for everyone. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">So, now, back to the real issue that should be on the list. &nbsp;Is CAP ready? If not, what's wrong/missing/needs clarification/etc.... Keep those cards and letters coming.</font>
<br>
<br><font size=2 face="sans-serif">And, keep it nice!</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Bruce_Kahn@notesdev.ibm.com</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/03/2003 17:49</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;ietf-calendar@imc.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: Correct handling of Recurrence-id</font></table>
<br>
<br>
<br>
<br><font size=2><tt>Doug pondered on 07/02/2003 06:24:20 PM:</tt></font>
<br><font size=2><tt>&gt; &nbsp;&gt; ...and so far the discussions were foucsed</tt></font>
<br><font size=2><tt>&gt; &gt; around the most common and basic model of invitations and reschedules to </tt></font>
<br><font size=2><tt>&gt; &gt; the initial set.</tt></font>
<br><font size=2><tt>&gt; </tt></font>
<br><font size=2><tt>&gt; I have not seen any one claim that including you in the debate.</tt></font>
<br><font size=2><tt>&gt; But assuming it is - so what?</tt></font>
<br><font size=3>&nbsp;</font>
<br><font size=2>The point is to put misinterpretations to rest and get on with other WG business. &nbsp;I just do not want some folks misinterpreation of the RFCs to become contagious causing us no end of grief to those that read the RFCs correctly.</font><font size=3> </font>
<br>
<br><font size=2>Lets get back to the facts of this shall we:</font><font size=3> </font>
<br>
<br><font size=2>1: iCalendar clearly says that RECURRENCE-ID does not change on a reschedule. &nbsp;For those that missed it the last 4 times:</font><font size=3> </font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The date/time value is set to the time when the original recurrence</tt></font>
<br><font size=2><tt>&nbsp; instance would occur; meaning that if the intent is to change a</tt></font>
<br><font size=2><tt>&nbsp; Friday meeting to Thursday, the date/time is still set to the</tt></font>
<br><font size=2><tt>&nbsp; original Friday meeting.</tt></font><font size=3> </font>
<br>
<br><font size=2>2: iCalendar has been misquoted/misread by some as saying that the RECURRENCE-ID does change on a reschedule. &nbsp;The misunderstanding stems from:</font><font size=3> </font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The &quot;RECURRENCE-ID&quot; property is used in conjunction with the &quot;UID&quot;</tt></font>
<br><font size=2><tt>&nbsp; and &quot;SEQUENCE&quot; property to identify a particular instance of a</tt></font>
<br><font size=2><tt>&nbsp; recurring event, to-do or journal. For a given pair of &quot;UID&quot; and</tt></font>
<br><font size=2><tt>&nbsp; &quot;SEQUENCE&quot; property values, the &quot;RECURRENCE-ID&quot; value for a</tt></font>
<br><font size=2><tt>&nbsp; recurrence instance is fixed. When the definition of the recurrence</tt></font>
<br><font size=2><tt>&nbsp; set for a calendar component changes, and hence the &quot;SEQUENCE&quot;</tt></font>
<br><font size=2><tt>&nbsp; property value changes, the &quot;RECURRENCE-ID&quot; for a given recurrence</tt></font>
<br><font size=2><tt>&nbsp; instance might also change.</tt></font><font size=3> </font>
<br>
<br><font size=2>which says that RECURRENCE-ID </font><font size=2><tt>&quot;might also change&quot;</tt></font><font size=2> but ONLY for the case where </font><font size=2><tt>&quot;the definition of the recurrence set for a calendar component changes&quot;</tt></font><font size=2>. &nbsp;A reschedule of an entry in the recurrence (aka repeat) set is NOT changing the set definition! &nbsp;Changing the definition is going from repeating &quot;Every Monday for 3 weeks&quot; to &quot;Every Wednesday and Thursday for 2 months&quot; (or some other pattern). &nbsp;Sounds like confusion on the part of some between the two.</font><font size=3> </font>
<br>
<br><font size=2>3: iTIP does not describe changing the RECURRENCE-ID value on a reschedule depsite instances to the contrary. &nbsp;Section 4.7.2 Bad RECURRENCE-ID says:</font><font size=3> </font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;1. &nbsp;The component with the referenced &quot;UID&quot; and &quot;RECURRENCE-ID&quot; has</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; been found but the &quot;SEQUENCE&quot; number in the calendar store does</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; not match that of the ITIP message.</tt></font><font size=3> </font>
<br>
<br><font size=2>In order for the UID and RECURRENCE-ID &nbsp;to match but the SEQUENCE to be &quot;larger&quot; or &quot;smaller&quot; then obviously UID and RECURRENCE-ID cannot be changed when SEQUENCE changes or they would never match the correct instance in question.</font><font size=3> </font>
<br>
<br><font size=2>Section 2.1.5 Message Sequencing clearly states that UID and RECURRENCE-ID are to be used as the primary key when sequencing any iTIP message for a particular repeating instance. &nbsp;They are to be combined into a key to find the particular instance and then SEQUENCE is to be looked for (as described in Section 4.7.2 bullet 1 even). &nbsp;Missed messages at lower SEQUENCE values are irrelevant because they are obsoleted by the newer SEQUENCE versions. &nbsp;As such missed messages are not a problem for workflow (unless you need them to change the RECURRENCE-ID values).</font><font size=3> </font>
<br>
<br><font size=2>Section 3.2.2 REQUEST clearly describes how to differentiate between a new request and a reschedule of an existing one. &nbsp;If RECURRENCE-ID changed on each reschedule then it would be impossible to match it to an existing entry correctly. &nbsp;</font><font size=3> </font>
<br>
<br><font size=2>Any attempts to change the model so that RECURRENCE-ID changes on each reschedule is either a misinterpretation of the RFCs or an attempt to change their behaviour that is clearly outlined otherwise. &nbsp;</font><font size=3> </font>
<br>
<br><font size=2>Bruce</font><font size=3> </font>
<br><font size=2>===========================================================================</font>
<br><font size=2>Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com</font>
<br><font size=2>Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Phone: 978.399.6496</font>
<br><font size=2>IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...</font>
<br><font size=2>Standard disclaimers apply, even where prohibited by law...</font><font size=3> </font>
<br>
<br>
--=_alternative 0062005985256D5C_=--


From owner-ietf-calendar@mail.imc.org  Mon Jul  7 15:33:35 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10717
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 15:33:34 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67JDQqt085148
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 12:13:26 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67JDQa7085147
	for ietf-calendar-bks; Mon, 7 Jul 2003 12:13:26 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67JDMqt085140
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 12:13:25 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h67JDJYa022142
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 12:13:22 -0700
Message-ID: <3F09C647.9090803@Royer.com>
Date: Mon, 07 Jul 2003 13:13:11 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP draft - last call, etc. (scoping)
References: <OFA903242A.F5DB98E3-ON85256D5C.005EEC23-85256D5C.005FE207@egenconsulting.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010305000901090805080805"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms010305000901090805080805
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



pregen@egenconsulting.com wrote:

> 
> Now, back to the discussion about CAP.  I think we are ok with CAP as it 
> pertains to Recurrece-ID's but that will be confirmed a bit later. 
>  What's left in CAP that needs to be fixed/removed/discussed.  Bruce 
> brought up Scoping.  I don't see where that was resolved.  Is it an 
> issue?  List?

That is part of the ABNF changes that are being updated. ABNF
as many know is a real pain to write. So far there have been
no suggested fixes just those noticing issues. Which is a good
thing, suggested fixes would speed it up.

So if anyone wishes to submit ABNF changes to the list, I would
appreciate it. Not a re-write as that would cause a few month
delay as everyone reevaluated. Just updates, additions, fixes
or whatever you think would help.


Thanks!

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms010305000901090805080805
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDcxOTEzMTFaMCMGCSqGSIb3DQEJBDEWBBTd
rFmiZZ0MfFpTPR8PNVvrPmUkpjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAMAjZDoyThqFx
f2TKLWSdLoqHpamphWW9F3rAA+bluvE+unGm+hPTRsbtoGBK4GoXMy0KUQC7HTIcOszdH8Ef
i5LpmHgNVdl31ylQhecb7cTATmg+0YVbkeGIZX2q07cgraprIfO2b0x11fkyDS7iJEb0ujnf
zGGr6OMjQsJtgmSykJrkwrXnasmPu17XQPy07UHYX0n5d2nz1P9UV7CqfpkN/CN0GCnuTZWC
cfcwtJMAtFxLwBHanNtoyZY3TZAvFXdFaSN0WKUxvjM4DD/dW8Wn2nZNXFuN0HkZqJhBthjY
jjjLoD1lNUUlHO+r1QjmgbqgxDEtZ4uCHBNk9xvI5wAAAAAAAA==
--------------ms010305000901090805080805--



From owner-ietf-calendar@mail.imc.org  Mon Jul  7 15:33:40 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10733
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 15:33:39 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67JFmqt085271
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 12:15:48 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67JFlcv085270
	for ietf-calendar-bks; Mon, 7 Jul 2003 12:15:47 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from zeus.corpsite.com (zeus.corpsite.com [12.162.64.233])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67JFkqt085263
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 12:15:47 -0700 (PDT)
	(envelope-from dhickman@rockinsoftware.com)
Received: from rockin1 (x1-6-00-d0-09-d6-9c-1b.entouch.net [65.124.87.93])
	(authenticated)
	by zeus.corpsite.com (8.11.1/8.11.1) with ESMTP id h67JFmv00842
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 14:15:48 -0500 (EST)
From: "Dan Hickman" <dhickman@rockinsoftware.com>
To: <ietf-calendar@imc.org>
Subject: BYDAY and YEARLY
Date: Mon, 7 Jul 2003 14:16:10 -0500
Message-ID: <LNBBLMNOGOCILCNAGNONKELACGAF.dhickman@rockinsoftware.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


The correct usage of BYDAY in a yearly RRULE has been discussed several
times on the working group before but I have not seen a resolution about the
correct meaning.  I would like to put it to rest once and for all.

The issue is the use of BYDAY as follows to mean the last Sunday in October.
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10

The BYDAY on yearly refers to weeks of the year and not weeks of the month
so this really means the last Sunday of the year but only if it occurs in
October.  The last week of the year will always be in December of course so
the above rule never resolves to any valid dates.

The following examples would be correct:
RRULE:FREQ=MONTHLY;BYDAY=-1SU;BYMONTH=10
or
RRULE:FREQ=YEARLY;BYDAY=SU;BYMONTH=10;BYSETPOS=-1

The problem is that RFC2445 incorrectly uses this syntax in VTIMEZONE
examples so it makes it look like it is valid.  I am finding now that both
MS Outlook and Apple iCal both use YEARLY/BYDAY in this way.

It was suggested on this mailing list in the past that the VTIMEZONE text
should be corrected in the RFC.  I really think this should be addressed,
one way or another.

If the opinion is that "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" does mean
the last Sunday in October, then that raises further questions.  For
example, what dates would the following rule resolve to?
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12

Regards,
Dan Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com



From owner-ietf-calendar@mail.imc.org  Mon Jul  7 16:28:13 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13544
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 16:28:12 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67KJ5qt090624
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 13:19:05 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67KJ59v090623
	for ietf-calendar-bks; Mon, 7 Jul 2003 13:19:05 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67KJ3qt090618
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 13:19:03 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h67KJ1Ya022699
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 13:19:04 -0700
Message-ID: <3F09D5AC.4000502@Royer.com>
Date: Mon, 07 Jul 2003 14:18:52 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP draft - last call, etc. (BEEP profile)
References: <OFA903242A.F5DB98E3-ON85256D5C.005EEC23-85256D5C.005FE207@egenconsulting.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030103010206050007020409"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms030103010206050007020409
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



pregen@egenconsulting.com wrote:

> 
> If someone sees other items in CAP that need to be 
> fixed/removed/discussed, please discuss them now.  And if you have text 
> that should change, provide your example as text so we can snap it into 
> the draft.  That really helps the editor.

As there have been no replies to my comments to the BEEP profile
and after re-reading the WG archives, I will put the following
into -11 (still not too late to comment on my proposal).

Beep replies will be one to one (1:1 MSG/RPY) if possible
and one to many (1:many MSG/ANS) when the TARGET changes.


    Profile Identification: specify a URI [10] that authoritatively
       identifies this profile.

		http://iana.org/beep/cap/1.0

    Message Exchanged during Channel Creation: specify the datatypes that
       may be exchanged during channel creation.

		CUAs SHOULD supply the BEEP "localize" attributes
		in the BEEP "greeting" messages.

		CSs SHOULD supply the BEEP "localize" attributes
		in the BEEP "greeting" messages.

		CUAs SHOULD supply the BEEP "serverName" attribute at
                 channel creation time to the CS so that if the CS is
		performing virtual hosting the CS can determine the
		intended virtual host. CSs that do not support virtual
		hosting may ignore the BEEP "serverName" attribute.
	
    Messages starting one-to-one exchanges: specify the datatypes that
       may be present when an exchange starts.

		The initial message each direction MUST BE single	
		"text/calendar" object containing a CAP "CAPABILITY" CMD
		and must not be part of a MIME multipart message.

		After the initial message then a BEEP "MSG" may contain
		one or more MIME objects at least one of which MUST be
		"text/calendar" and each "text/calendar" MIME object
                 MUST contain a CAP "CMD" property.

		The BEEP "MSG" messages can only contain MIME "multipart"
		MIME objects if the other endpoint has received a CAP
		"CAPABILITY" indicating the other endpoint supports
		multipart MIME objects. This does not prevent the endpoint
		from sending multiple "text/calendar" MIME objects
		in a single BEEP "MSG" so long as all of the
		"text/calendar" CAP objects have the same "TARGET"
		property value.

    Messages in positive replies: specify the datatypes that may be
       present in a positive reply.

		After the initial message then a BEEP "RPY" may contain
		one or more MIME objects at least one of which MUST be
		"text/calendar" and each "text/calendar" MIME object
                 MUST contain a CAP "CMD" property. All "text/calendar"
		MIME objects in a single BEEP "RPY" messages MUST have
		the same "TARGET" property value.

		The BEEP "RPY" messages can only contain MIME "multipart"
		MIME objects if the other endpoint has received a CAP
		"CAPABILITY" indicating the other endpoint supports
		multipart MIME objects. This does not prevent the endpoint
		from sending multiple "text/calendar" MIME objects
		in a single BEEP "RPY" so long as all of the
		"text/calendar" CAP objects have the same "TARGET"
		property value.

    Messages in negative replies: specify the datatypes that may be
       present in a negative reply.

		Any valid "text/calendar" MIME object that contains
		CAP "REQUEST-STATUS" property and a CAP "CMD" property
                 with a property value of "REPLY". And where the CS has
		determined the requested operation to be a fatal error.
		And when the CS has performed NO operation that effected
		the contents of any part of the CS or any calendar
		controlled by the CS.

    Messages in one-to-many exchanges: specify the datatypes that may be
       present in a one-to-many exchange.

		After the initial message then a BEEP "MSG" may contain
		one or more MIME objects at least one of which MUST be
		"text/calendar" and each "text/calendar" MIME object
                 MUST contain a CAP "CMD" property.

		The BEEP "MSG" messages can only contain MIME "multipart"
		MIME objects if the other endpoint has received a CAP
		"CAPABILITY" indicating the other endpoint supports
		multipart MIME objects. This does not prevent the endpoint
		from sending multiple "text/calendar" MIME objects
		in a single BEEP "MSG" so long as all of the
		"text/calendar" CAP objects have the same "TARGET"
		property value.

		The BEEP "RPY" messages can only contain MIME "multipart"
		MIME objects if the other endpoint has received a CAP
		"CAPABILITY" indicating the other endpoint supports
		multipart MIME objects. This does not prevent the endpoint
		from sending multiple "text/calendar" MIME objects
		in a single BEEP "ANS" so long as all of the
		"text/calendar" CAP objects in EACH BEEP "ANS" message
		have the same "TARGET" property value. Each unique
		"TARGET" property value per BEEP "ANS" message.

    Message Syntax: specify the syntax of the datatypes exchanged by the
       profile.

		They are CAP "text/calendar" MIME objects as specified
		in this memo. (Remember this text will be part of CAP).


    Message Semantics: specify the semantics of the datatypes exchanged
       by the profile.

		As defined in this memo. (Remember this will be part
		of CAP).

--

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms030103010206050007020409
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDcyMDE4NTJaMCMGCSqGSIb3DQEJBDEWBBRa
WnKH8zFQiiZj3X0Nb0Shr9eKsDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAGlhOymGig2cW
/cwz9nhGKy3X6gLR/yvXvZFdqEZi50Rhe/4ychm/x6Sz5WlPVfYED1Arem/w3sX5Hk43Yupd
C4Ot36TjPFQKnowLwsMkpqvqffNnvMzRfzrGcx2Zii4LfbwMAtF4j7WXCf6j2TcdypuvkXG+
DtXmGztQWFQ3D3fgY1MzRv6rsRRuHtbXvY94MlgX8gveivtm8xF+e1zcjE5YSedmXyrN1VT1
YxZRUnxNLqC3PSQBDZ1+mBOYozhQPe6iJFBH0UjsOdOW2xlN0gcoD4R2yURZAIyAfpRr3xbI
343i7+4wLyNWbTsSDEHDu47V2q5N3ofdqRf9ffcf1wAAAAAAAA==
--------------ms030103010206050007020409--



From owner-ietf-calendar@mail.imc.org  Mon Jul  7 16:50:45 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14714
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 16:50:44 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67KgNqt091384
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 13:42:23 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67KgNrC091383
	for ietf-calendar-bks; Mon, 7 Jul 2003 13:42:23 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67KgLqt091378
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 13:42:22 -0700 (PDT)
	(envelope-from ki.wong@Sun.COM)
Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42])
	by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h67KgNvc005782;
	Mon, 7 Jul 2003 14:42:23 -0600 (MDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail2sca.sfbay.sun.com (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h67KgMaJ018393;
	Mon, 7 Jul 2003 13:42:22 -0700 (PDT)
Received: from J02K.dvd2kdom.red.iplanet.com
 (j02k.red.iplanet.com [192.18.144.134]) by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HHO005S89IM0E@ha13sca-mail1.sfbay.sun.com>; Mon,
 07 Jul 2003 13:42:22 -0700 (PDT)
Date: Mon, 07 Jul 2003 13:43:21 -0700
From: kiwong <ki.wong@sun.com>
Subject: RE: BYDAY and YEARLY
To: Dan Hickman <dhickman@rockinsoftware.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_6_.20030707134321.684A@sun.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-transfer-encoding: 7BIT
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7BIT


RFC section 4.3.10
   If multiple BYxxx rule parts are specified, then after evaluating the
   specified FREQ and INTERVAL rule parts, the BYxxx rule parts are
   applied to the current set of evaluated occurrences in the following
   order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR,
   BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.

I will interpret 

RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 as the last Sunday in October
every year.

RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12 as the last Sunday in
October, Nov, Dec every year.

ki

> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> Sent: Monday, July 07, 2003 12:16 PM
> To: ietf-calendar@imc.org
> Subject: BYDAY and YEARLY
> 
> 
> The correct usage of BYDAY in a yearly RRULE has been discussed several
> times on the working group before but I have not seen a resolution about
the
> correct meaning.  I would like to put it to rest once and for all.
> 
> The issue is the use of BYDAY as follows to mean the last Sunday in
October.
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
> 
> The BYDAY on yearly refers to weeks of the year and not weeks of the
month
> so this really means the last Sunday of the year but only if it occurs in
> October.  The last week of the year will always be in December of course
so
> the above rule never resolves to any valid dates.
> 
> The following examples would be correct:
> RRULE:FREQ=MONTHLY;BYDAY=-1SU;BYMONTH=10
> or
> RRULE:FREQ=YEARLY;BYDAY=SU;BYMONTH=10;BYSETPOS=-1
> 
> The problem is that RFC2445 incorrectly uses this syntax in VTIMEZONE
> examples so it makes it look like it is valid.  I am finding now that
both
> MS Outlook and Apple iCal both use YEARLY/BYDAY in this way.
> 
> It was suggested on this mailing list in the past that the VTIMEZONE text
> should be corrected in the RFC.  I really think this should be addressed,
> one way or another.
> 
> If the opinion is that "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" does
mean
> the last Sunday in October, then that raises further questions.  For
> example, what dates would the following rule resolve to?
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12
> 
> Regards,
> Dan Hickman
> Rockin' Software
> dhickman@rockinsoftware.com
> http://www.rockinsoftware.com




From owner-ietf-calendar@mail.imc.org  Mon Jul  7 17:14:45 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16453
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 17:14:44 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67L4nqt092377
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 14:04:49 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67L4nqI092376
	for ietf-calendar-bks; Mon, 7 Jul 2003 14:04:49 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from zeus.corpsite.com (zeus.corpsite.com [12.162.64.233])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67L4mqt092371
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 14:04:48 -0700 (PDT)
	(envelope-from dhickman@rockinsoftware.com)
Received: from rockin1 (x1-6-00-d0-09-d6-9c-1b.entouch.net [65.124.87.93])
	(authenticated)
	by zeus.corpsite.com (8.11.1/8.11.1) with ESMTP id h67L4nv04392;
	Mon, 7 Jul 2003 16:04:49 -0500 (EST)
From: "Dan Hickman" <dhickman@rockinsoftware.com>
To: "kiwong" <ki.wong@sun.com>, <ietf-calendar@imc.org>
Subject: RE: BYDAY and YEARLY
Date: Mon, 7 Jul 2003 16:05:13 -0500
Message-ID: <LNBBLMNOGOCILCNAGNONAELGCGAF.dhickman@rockinsoftware.com>
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.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <ISSMTP.2003_6_.20030707134321.684A@sun.com>
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


But the from the same section 4.3.10
   Information, not contained in the rule, necessary to determine the
   various recurrence instance start time and dates are derived from the
   Start Time (DTSTART) entry attribute. For example,
   "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
   month or a time. This information would be the same as what is
   specified for DTSTART.

Using your logic, the following RRULE example from the RFC would assume May
as the BYMONTH and would mean the 20th Monday in May.
     DTSTART;TZID=US-Eastern:19970519T090000
     RRULE:FREQ=YEARLY;BYDAY=20MO

This RFC sample RRULE states this is the 20th Monday of the Year.

Regards,
Dan Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com


-----Original Message-----
From: kiwong [mailto:ki.wong@Sun.COM]
Sent: Monday, July 07, 2003 3:43 PM
To: Dan Hickman; ietf-calendar@imc.org
Subject: RE: BYDAY and YEARLY


RFC section 4.3.10
   If multiple BYxxx rule parts are specified, then after evaluating the
   specified FREQ and INTERVAL rule parts, the BYxxx rule parts are
   applied to the current set of evaluated occurrences in the following
   order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR,
   BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.

I will interpret

RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 as the last Sunday in October
every year.

RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12 as the last Sunday in
October, Nov, Dec every year.

ki

> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> Sent: Monday, July 07, 2003 12:16 PM
> To: ietf-calendar@imc.org
> Subject: BYDAY and YEARLY
>
>
> The correct usage of BYDAY in a yearly RRULE has been discussed several
> times on the working group before but I have not seen a resolution about
the
> correct meaning.  I would like to put it to rest once and for all.
>
> The issue is the use of BYDAY as follows to mean the last Sunday in
October.
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
>
> The BYDAY on yearly refers to weeks of the year and not weeks of the
month
> so this really means the last Sunday of the year but only if it occurs in
> October.  The last week of the year will always be in December of course
so
> the above rule never resolves to any valid dates.
>
> The following examples would be correct:
> RRULE:FREQ=MONTHLY;BYDAY=-1SU;BYMONTH=10
> or
> RRULE:FREQ=YEARLY;BYDAY=SU;BYMONTH=10;BYSETPOS=-1
>
> The problem is that RFC2445 incorrectly uses this syntax in VTIMEZONE
> examples so it makes it look like it is valid.  I am finding now that
both
> MS Outlook and Apple iCal both use YEARLY/BYDAY in this way.
>
> It was suggested on this mailing list in the past that the VTIMEZONE text
> should be corrected in the RFC.  I really think this should be addressed,
> one way or another.
>
> If the opinion is that "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" does
mean
> the last Sunday in October, then that raises further questions.  For
> example, what dates would the following rule resolve to?
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12
>
> Regards,
> Dan Hickman
> Rockin' Software
> dhickman@rockinsoftware.com
> http://www.rockinsoftware.com




From owner-ietf-calendar@mail.imc.org  Mon Jul  7 17:40:44 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17387
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 17:40:43 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67LVTqt093543
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 14:31:29 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67LVToR093542
	for ietf-calendar-bks; Mon, 7 Jul 2003 14:31:29 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67LVSqt093534
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 14:31:28 -0700 (PDT)
	(envelope-from ki.wong@Sun.COM)
Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42])
	by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h67LVPKo012721
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 14:31:25 -0700 (PDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail2sca.sfbay.sun.com (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h67LVPaJ009064
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 14:31:25 -0700 (PDT)
Received: from J02K.dvd2kdom.red.iplanet.com
 (j02k.red.iplanet.com [192.18.144.134]) by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HHO005GABSD0E@ha13sca-mail1.sfbay.sun.com> for
 ietf-calendar@imc.org; Mon, 07 Jul 2003 14:31:25 -0700 (PDT)
Date: Mon, 07 Jul 2003 14:32:23 -0700
From: kiwong <ki.wong@Sun.COM>
Subject: RE: BYDAY and YEARLY
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_9_.20030707143223.2984E@sun.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-transfer-encoding: 7BIT
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7BIT




> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> Sent: Monday, July 07, 2003 2:05 PM
> To: kiwong; ietf-calendar@imc.org
> Subject: RE: BYDAY and YEARLY
> 
> 
> But the from the same section 4.3.10
>    Information, not contained in the rule, necessary to determine the
>    various recurrence instance start time and dates are derived from the
>    Start Time (DTSTART) entry attribute. For example,
>    "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
>    month or a time. This information would be the same as what is
>    specified for DTSTART.
> 
> Using your logic, the following RRULE example from the RFC would assume
May
> as the BYMONTH and would mean the 20th Monday in May.
>      DTSTART;TZID=US-Eastern:19970519T090000
>      RRULE:FREQ=YEARLY;BYDAY=20MO
> 

But the day here is defined, which is the 20th Monday of the year.
However, the time is not defined, so I will interpret it as 20th Monday of
the year at time 090000. 

> This RFC sample RRULE states this is the 20th Monday of the Year.
> 
> Regards,
> Dan Hickman
> Rockin' Software
> dhickman@rockinsoftware.com
> http://www.rockinsoftware.com
> 
> 
> -----Original Message-----
> From: kiwong [mailto:ki.wong@Sun.COM]
> Sent: Monday, July 07, 2003 3:43 PM
> To: Dan Hickman; ietf-calendar@imc.org
> Subject: RE: BYDAY and YEARLY
> 
> 
> RFC section 4.3.10
>    If multiple BYxxx rule parts are specified, then after evaluating the
>    specified FREQ and INTERVAL rule parts, the BYxxx rule parts are
>    applied to the current set of evaluated occurrences in the following
>    order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR,
>    BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.
> 
> I will interpret
> 
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 as the last Sunday in October
> every year.
> 
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12 as the last Sunday in
> October, Nov, Dec every year.
> 
> ki
> 
> > -----Original Message-----
> > From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> > Sent: Monday, July 07, 2003 12:16 PM
> > To: ietf-calendar@imc.org
> > Subject: BYDAY and YEARLY
> >
> >
> > The correct usage of BYDAY in a yearly RRULE has been discussed several
> > times on the working group before but I have not seen a resolution
about
> the
> > correct meaning.  I would like to put it to rest once and for all.
> >
> > The issue is the use of BYDAY as follows to mean the last Sunday in
> October.
> > RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
> >
> > The BYDAY on yearly refers to weeks of the year and not weeks of the
> month
> > so this really means the last Sunday of the year but only if it occurs
in
> > October.  The last week of the year will always be in December of
course
> so
> > the above rule never resolves to any valid dates.
> >
> > The following examples would be correct:
> > RRULE:FREQ=MONTHLY;BYDAY=-1SU;BYMONTH=10
> > or
> > RRULE:FREQ=YEARLY;BYDAY=SU;BYMONTH=10;BYSETPOS=-1
> >
> > The problem is that RFC2445 incorrectly uses this syntax in VTIMEZONE
> > examples so it makes it look like it is valid.  I am finding now that
> both
> > MS Outlook and Apple iCal both use YEARLY/BYDAY in this way.
> >
> > It was suggested on this mailing list in the past that the VTIMEZONE
text
> > should be corrected in the RFC.  I really think this should be
addressed,
> > one way or another.
> >
> > If the opinion is that "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" does
> mean
> > the last Sunday in October, then that raises further questions.  For
> > example, what dates would the following rule resolve to?
> > RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12
> >
> > Regards,
> > Dan Hickman
> > Rockin' Software
> > dhickman@rockinsoftware.com
> > http://www.rockinsoftware.com
> 




From owner-ietf-calendar@mail.imc.org  Mon Jul  7 18:05:18 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18507
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 18:05:17 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67Lrpqt094800
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 14:53:51 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67Lrp6h094799
	for ietf-calendar-bks; Mon, 7 Jul 2003 14:53:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67Lroqt094794
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 14:53:50 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F04B9E4.2000100@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF3DB2F062.B9E4921C-ON85256D5C.00747E61-85256D5C.0077D66F@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Mon, 7 Jul 2003 17:49:19 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/07/2003
 05:53:51 PM,
	Serialize complete at 07/07/2003 05:53:51 PM
Content-Type: multipart/alternative; boundary="=_alternative 0077D66785256D5C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0077D66785256D5C_=
Content-Type: text/plain; charset="US-ASCII"

Doug persisted on 07/03/2003 07:19:00 PM:
> > In any case I view some of this as moot given the fact that nothing in 

> > iCalendar or iTIP supports the claim that RECURRENCE-IDs change on 
each 
> > instance reschedule...
> 
> I have quoted it several times from iCal where is says that the
> UID and SEQUENCE property identify a particular instance (3rd
> paragraph below). 

Doug may have quoted the iCalendar text but he seems to be overlooking 
some inconvenient prose and misinterpreting other bits.

Lets get this straight once and for all shall we.  iCalendar Section 
4.8.4.4 Recurrence ID describes the property with:

   Description: The full range of calendar components specified by a
   recurrence set is referenced by referring to just the "UID" property
   value corresponding to the calendar component. The "RECURRENCE-ID"
   property allows the reference to an individual instance within the
   recurrence set.

   If the value of the "DTSTART" property is a DATE type value, then the
   value MUST be the calendar date for the recurrence instance.

   The date/time value is set to the time when the original recurrence
   instance would occur; meaning that if the intent is to change a
   Friday meeting to Thursday, the date/time is still set to the
   original Friday meeting.

   The "RECURRENCE-ID" property is used in conjunction with the "UID"
   and "SEQUENCE" property to identify a particular instance of a
   recurring event, to-do or journal. For a given pair of "UID" and
   "SEQUENCE" property values, the "RECURRENCE-ID" value for a
   recurrence instance is fixed. When the definition of the recurrence
   set for a calendar component changes, and hence the "SEQUENCE"
   property value changes, the "RECURRENCE-ID" for a given recurrence
   instance might also change.The "RANGE" parameter is used to specify
   the effective range of recurrence instances from the instance
   specified by the "RECURRENCE-ID" property value. The default value
   for the range parameter is the single recurrence instance only. The
   value can also be "THISANDPRIOR" to indicate a range defined by the
   given recurrence instance and all prior instances or the value can be
   "THISANDFUTURE" to indicate a range defined by the given recurrence
   instance and all subsequent instances.

Now, lets reread the 3rd paragraph again:

   The date/time value is set to the time when the original recurrence
   instance would occur; meaning that if the intent is to change a
   Friday meeting to Thursday, the date/time is still set to the
   original Friday meeting.

This paragraph expressly says that the RECURRENCE-ID value "is still set 
to the original" value AFTER the reschedule occurs.  "The date/time value 
is set to the time when the original recurrence instance would occur" 
clearly says "original recurrence instance" and not "latest recurrence 
instance" or "most recent" value.  No amout of misreading or 
misinterpretation can overcome this.

Now the next paragraph clearly defines the case where RECURRENCE-ID "might 
also change" with the prose:

                               When the definition of the recurrence
   set for a calendar component changes, and hence the "SEQUENCE"
   property value changes, the "RECURRENCE-ID" for a given recurrence
   instance might also change.

Rescheduling an instance to a different date/time is just that, a 
reschedule.  It is not recreating the instances in the set which is what "
When the definition of the recurrence set for a calendar component changes
" means.

>                    And one reason to increment the SEQUENCE number
> is a recurrence change. 

Corect but incrementing the SEQUENCE property does NOT mean that the 
recurrence definition has changed.

>                If an ATTENDEE has SEQUENCE:W where W < X,
> and gets an instance specific update for SEQUENCE:X,
> then the attendee needs to do a REFRESH, the attendee can
> toss the instance specific update and wait for the REQUEST
> (REFRESH reply) from the ORGANIZER.

This does not follow from reading the RFCs.  You are not applying the iTIP 
Section 2.1.5 rules for message sequencing to the REQUEST and you are 
misapplying the example from iTIP Section 4.7.2. 

The invite uses the UID/RECURRENCE-ID as the primary key to indentify the 
instance to see if they have it already or not. 

A: If they find the UID/RECURRENCE-ID pair THEN they use SEQUENCE to tell 
if W<X or not.  There are 3 possible cases at this point:
        1: W<X therefore the new REQUEST "obsoletes" the existing one and 
the invitee can take some action on it.
        2: W=X therefore the next rule regarding using DTSTAMP needs to be 
applyed to the REQUEST to determine if something should take place.
        3: W>X therefore the new REQUEST is obsolete since the one the 
invitee already has is higher.  This jives with Dougs cited Section 4.7.2 
bullet 1.
B: If they do not find the UID/RECURRENCE-ID pair then its a new instance 
(per iTIP Section 3.2.2 REQUEST) and there is no need to check SEQUENCE 
(or DTSTAMP).

The invitee simply treats it as a new invitation to a new instance.  No 
need to ask for a REFRESH.  The REQUEST is new and the invitee can take 
immediate action on it.

If you read the description for bullet 1 in iTIP Section 4.7.2 it clearly 
talks about using UID/RECURRENCE-ID and SEQUENCE:

   In case (1), two things can happen. If the "SEQUENCE" number of the
   "Attendee's" instance is larger than that in the "Organizer's"
   message then the "Attendee" is receiving an out-of-sequence message
   and MUST ignore it.  If the "SEQUENCE" number of the "Attendee's"
   instance is smaller, then the "Organizer" is sending out a newer
   version of the component and the "Attendee's" version needs to be
   updated

In order for the invitee to be able to find the UID/RECURRENCE-ID pair at 
a level other than "1 off" from the current SEQUENCE the values MUST stay 
fixed.  Otherwise its not possible to match them and then compare SEQUENCE 
values of X and W if W != X - 1.  Clearly the values of UID/RECURRENCE-ID 
MUST stay "fixed" so that SEQUENCE checks can properly detect "larger" or 
"smaller" otherwise this "larger" or "smaller" check is just not possible.

>     ...When the definition of the recurrence
>     set for a calendar component changes, and hence the "SEQUENCE"
>     property value changes, the "RECURRENCE-ID" for a given recurrence
>     instance might also change. ...

I noticed that the cited description did NOT contain the paragraph that 
clearly described that RECURRENCE-ID did not change on a reschedule. 

Also, as I noted before a reschedule is not a change to the "definition of 
the recurrence _set_".  Its a change to an instance _in_ the set!

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 0077D66785256D5C_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug persisted on 07/03/2003 07:19:00 PM:<br>
&gt; &gt; In any case I view some of this as moot given the fact that nothing
in <br>
&gt; &gt; iCalendar or iTIP supports the claim that RECURRENCE-IDs change
on each <br>
&gt; &gt; instance reschedule...<br>
&gt; <br>
&gt; I have quoted it several times from iCal where is says that the<br>
&gt; UID and SEQUENCE property identify a particular instance (3rd<br>
&gt; paragraph below). </tt></font>
<br>
<br><font size=2 face="sans-serif">Doug may have quoted the iCalendar text
but he seems to be overlooking some inconvenient prose and misinterpreting
other bits.</font>
<br>
<br><font size=2 face="sans-serif">Lets get this straight once and for
all shall we. &nbsp;iCalendar Section 4.8.4.4 Recurrence ID describes the
property with:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;Description: The full range of calendar
components specified by a<br>
 &nbsp; recurrence set is referenced by referring to just the &quot;UID&quot;
property<br>
 &nbsp; value corresponding to the calendar component. The &quot;RECURRENCE-ID&quot;<br>
 &nbsp; property allows the reference to an individual instance within
the<br>
 &nbsp; recurrence set.<br>
<br>
 &nbsp; If the value of the &quot;DTSTART&quot; property is a DATE type
value, then the<br>
 &nbsp; value MUST be the calendar date for the recurrence instance.<br>
<br>
 &nbsp; The date/time value is set to the time when the original recurrence<br>
 &nbsp; instance would occur; meaning that if the intent is to change a<br>
 &nbsp; Friday meeting to Thursday, the date/time is still set to the<br>
 &nbsp; original Friday meeting.<br>
<br>
 &nbsp; The &quot;RECURRENCE-ID&quot; property is used in conjunction with
the &quot;UID&quot;<br>
 &nbsp; and &quot;SEQUENCE&quot; property to identify a particular instance
of a<br>
 &nbsp; recurring event, to-do or journal. For a given pair of &quot;UID&quot;
and<br>
 &nbsp; &quot;SEQUENCE&quot; property values, the &quot;RECURRENCE-ID&quot;
value for a<br>
 &nbsp; recurrence instance is fixed. When the definition of the recurrence<br>
 &nbsp; set for a calendar component changes, and hence the &quot;SEQUENCE&quot;<br>
 &nbsp; property value changes, the &quot;RECURRENCE-ID&quot; for a given
recurrence<br>
 &nbsp; instance might also change.The &quot;RANGE&quot; parameter is used
to specify<br>
 &nbsp; the effective range of recurrence instances from the instance<br>
 &nbsp; specified by the &quot;RECURRENCE-ID&quot; property value. The
default value<br>
 &nbsp; for the range parameter is the single recurrence instance only.
The<br>
 &nbsp; value can also be &quot;THISANDPRIOR&quot; to indicate a range
defined by the<br>
 &nbsp; given recurrence instance and all prior instances or the value
can be<br>
 &nbsp; &quot;THISANDFUTURE&quot; to indicate a range defined by the given
recurrence<br>
 &nbsp; instance and all subsequent instances.</tt></font>
<br>
<br><font size=2 face="sans-serif">Now, lets reread the 3rd paragraph again:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The date/time value is set to the time
when the original recurrence<br>
 &nbsp; instance would occur; meaning that if the intent is to change a<br>
 &nbsp; Friday meeting to Thursday, the date/time is still set to the<br>
 &nbsp; original Friday meeting.<br>
</tt></font>
<br><font size=2 face="sans-serif">This paragraph expressly says that the
RECURRENCE-ID value </font><font size=2><tt>&quot;is still set to the original&quot;</tt></font><font size=2 face="sans-serif">
value AFTER the reschedule occurs. &nbsp;</font><font size=2><tt>&quot;The
date/time value is set to the time when the original recurrence instance
would occur&quot;</tt></font><font size=2 face="sans-serif"> clearly says
</font><font size=2><tt>&quot;original recurrence instance&quot;</tt></font><font size=2 face="sans-serif">
and not </font><font size=2><tt>&quot;latest recurrence instance&quot;</tt></font><font size=2 face="sans-serif">
or </font><font size=2><tt>&quot;most recent&quot;</tt></font><font size=2 face="sans-serif">
value. &nbsp;No amout of misreading or misinterpretation can overcome this.</font>
<br>
<br><font size=2 face="sans-serif">Now the next paragraph clearly defines
the case where RECURRENCE-ID &quot;might also change&quot; with the prose:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;When the definition
of the recurrence<br>
 &nbsp; set for a calendar component changes, and hence the &quot;SEQUENCE&quot;<br>
 &nbsp; property value changes, the &quot;RECURRENCE-ID&quot; for a given
recurrence<br>
 &nbsp; instance might also change.</tt></font>
<br>
<br><font size=2 face="sans-serif">Rescheduling an instance to a different
date/time is just that, a reschedule. &nbsp;It is not recreating the instances
in the set which is what &quot;</font><font size=2><tt>When the definition
of the recurrence set for a calendar component changes</tt></font><font size=2 face="sans-serif">&quot;
means.</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp;And one reason to increment the SEQUENCE number<br>
&gt; is a recurrence change. </tt></font>
<br>
<br><font size=2 face="sans-serif">Corect but incrementing the SEQUENCE
property does <u>NOT</u> mean that the recurrence definition has changed.</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;If an ATTENDEE has SEQUENCE:W where W &lt; X,<br>
&gt; and gets an instance specific update for SEQUENCE:X,<br>
&gt; then the attendee needs to do a REFRESH, the attendee can<br>
&gt; toss the instance specific update and wait for the REQUEST<br>
&gt; (REFRESH reply) from the ORGANIZER.<br>
</tt></font>
<br><font size=2 face="sans-serif">This does not follow from reading the
RFCs. &nbsp;You are not applying the iTIP Section 2.1.5 rules for message
sequencing to the REQUEST and you are misapplying the example from iTIP
Section 4.7.2. </font>
<br>
<br><font size=2 face="sans-serif">The invite uses the UID/RECURRENCE-ID
as the primary key to indentify the instance to see if they have it already
or not. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">A: If they find the UID/RECURRENCE-ID
pair THEN they use SEQUENCE to tell if W&lt;X or not. &nbsp;There are 3
possible cases at this point:</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 1:
W&lt;X therefore the new REQUEST &quot;obsoletes&quot; the existing one
and the invitee can take some action on it.</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 2:
W=X therefore the next rule regarding using DTSTAMP needs to be applyed
to the REQUEST to determine if something should take place.</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 3:
W&gt;X therefore the new REQUEST is obsolete since the one the invitee
already has is higher. &nbsp;This jives with Dougs cited Section 4.7.2
bullet 1.</font>
<br><font size=2 face="sans-serif">B: If they do not find the UID/RECURRENCE-ID
pair then its a new instance (per iTIP Section 3.2.2 REQUEST) and there
is no need to check SEQUENCE (or DTSTAMP).</font>
<br>
<br><font size=2 face="sans-serif">The invitee simply treats it as a new
invitation to a new instance. &nbsp;No need to ask for a REFRESH. &nbsp;The
REQUEST is new and the invitee can take immediate action on it.</font>
<br>
<br><font size=2 face="sans-serif">If you read the description for bullet
1 in iTIP Section 4.7.2 it clearly talks about using UID/RECURRENCE-ID
and SEQUENCE:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;In case (1), two things can happen. If
the &quot;SEQUENCE&quot; number of the<br>
 &nbsp; &quot;Attendee's&quot; instance is larger than that in the &quot;Organizer's&quot;<br>
 &nbsp; message then the &quot;Attendee&quot; is receiving an out-of-sequence
message<br>
 &nbsp; and MUST ignore it. &nbsp;If the &quot;SEQUENCE&quot; number of
the &quot;Attendee's&quot;<br>
 &nbsp; instance is smaller, then the &quot;Organizer&quot; is sending
out a newer<br>
 &nbsp; version of the component and the &quot;Attendee's&quot; version
needs to be<br>
 &nbsp; updated</tt></font>
<br>
<br><font size=2 face="sans-serif">In order for the invitee to be able
to find the UID/RECURRENCE-ID pair at a level other than &quot;1 off&quot;
from the current SEQUENCE the values MUST stay fixed. &nbsp;Otherwise its
not possible to match them and then compare SEQUENCE values of X and W
if W != X - 1. &nbsp;Clearly the values of UID/RECURRENCE-ID MUST stay
&quot;fixed&quot; so that SEQUENCE checks can properly detect &quot;larger&quot;
or &quot;smaller&quot; otherwise this &quot;larger&quot; or &quot;smaller&quot;
check is just not possible.</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; ...When the definition of the recurrence<br>
&gt; &nbsp; &nbsp; set for a calendar component changes, and hence the
&quot;SEQUENCE&quot;<br>
&gt; &nbsp; &nbsp; property value changes, the &quot;RECURRENCE-ID&quot;
for a given recurrence<br>
&gt; &nbsp; &nbsp; instance might also change. ...<br>
</tt></font>
<br><font size=2 face="sans-serif">I noticed that the cited description
did NOT contain the paragraph that clearly described that RECURRENCE-ID
did not change on a reschedule. </font>
<br>
<br><font size=2 face="sans-serif">Also, as I noted before a reschedule
is not a change to the &quot;definition of the recurrence _set_&quot;.
&nbsp;Its a change to an instance _in_ the set!</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 0077D66785256D5C_=--


From owner-ietf-calendar@mail.imc.org  Mon Jul  7 18:11:20 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19186
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 18:11:20 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67M1fqt095638
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 15:01:41 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67M1f05095637
	for ietf-calendar-bks; Mon, 7 Jul 2003 15:01:41 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from zeus.corpsite.com (zeus.corpsite.com [12.162.64.233])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67M1eqt095630
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 15:01:40 -0700 (PDT)
	(envelope-from dhickman@rockinsoftware.com)
Received: from rockin1 (x1-6-00-d0-09-d6-9c-1b.entouch.net [65.124.87.93])
	(authenticated)
	by zeus.corpsite.com (8.11.1/8.11.1) with ESMTP id h67M1ev14512;
	Mon, 7 Jul 2003 17:01:40 -0500 (EST)
From: "Dan Hickman" <dhickman@rockinsoftware.com>
To: "kiwong" <ki.wong@sun.com>, <ietf-calendar@imc.org>
Subject: RE: BYDAY and YEARLY
Date: Mon, 7 Jul 2003 17:02:04 -0500
Message-ID: <LNBBLMNOGOCILCNAGNONEELJCGAF.dhickman@rockinsoftware.com>
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.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <ISSMTP.2003_9_.20030707143223.2984E@sun.com>
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


You miss my point.  For yearly events, the BYMONTH is also derived from
DTSTART.  For the sample, it would derive BYMONTH=5 since BYMONTH is not
included in the RRULE.

Dan

> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> Sent: Monday, July 07, 2003 2:05 PM
> To: kiwong; ietf-calendar@imc.org
> Subject: RE: BYDAY and YEARLY
>
>
> But the from the same section 4.3.10
>    Information, not contained in the rule, necessary to determine the
>    various recurrence instance start time and dates are derived from the
>    Start Time (DTSTART) entry attribute. For example,
>    "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
>    month or a time. This information would be the same as what is
>    specified for DTSTART.
>
> Using your logic, the following RRULE example from the RFC would assume
May
> as the BYMONTH and would mean the 20th Monday in May.
>      DTSTART;TZID=US-Eastern:19970519T090000
>      RRULE:FREQ=YEARLY;BYDAY=20MO
>

But the day here is defined, which is the 20th Monday of the year.
However, the time is not defined, so I will interpret it as 20th Monday of
the year at time 090000.




From owner-ietf-calendar@mail.imc.org  Mon Jul  7 18:12:10 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19274
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 18:12:09 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67M1vqt095682
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 15:01:57 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67M1umk095680
	for ietf-calendar-bks; Mon, 7 Jul 2003 15:01:56 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from zeus.corpsite.com (zeus.corpsite.com [12.162.64.233])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67M1tqt095674
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 15:01:56 -0700 (PDT)
	(envelope-from dhickman@rockinsoftware.com)
Received: from rockin1 (x1-6-00-d0-09-d6-9c-1b.entouch.net [65.124.87.93])
	(authenticated)
	by zeus.corpsite.com (8.11.1/8.11.1) with ESMTP id h67M1vv14655;
	Mon, 7 Jul 2003 17:01:57 -0500 (EST)
From: "Dan Hickman" <dhickman@rockinsoftware.com>
To: "kiwong" <ki.wong@sun.com>, <ietf-calendar@imc.org>
Subject: RE: BYDAY and YEARLY
Date: Mon, 7 Jul 2003 17:02:21 -0500
Message-ID: <LNBBLMNOGOCILCNAGNONEELJCGAF.dhickman@rockinsoftware.com>
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.2910.0)
Importance: Normal
In-Reply-To: <ISSMTP.2003_9_.20030707143223.2984E@sun.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


You miss my point.  For yearly events, the BYMONTH is also derived from
DTSTART.  For the sample, it would derive BYMONTH=5 since BYMONTH is not
included in the RRULE.

Dan

> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> Sent: Monday, July 07, 2003 2:05 PM
> To: kiwong; ietf-calendar@imc.org
> Subject: RE: BYDAY and YEARLY
>
>
> But the from the same section 4.3.10
>    Information, not contained in the rule, necessary to determine the
>    various recurrence instance start time and dates are derived from the
>    Start Time (DTSTART) entry attribute. For example,
>    "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
>    month or a time. This information would be the same as what is
>    specified for DTSTART.
>
> Using your logic, the following RRULE example from the RFC would assume
May
> as the BYMONTH and would mean the 20th Monday in May.
>      DTSTART;TZID=US-Eastern:19970519T090000
>      RRULE:FREQ=YEARLY;BYDAY=20MO
>

But the day here is defined, which is the 20th Monday of the year.
However, the time is not defined, so I will interpret it as 20th Monday of
the year at time 090000.




From owner-ietf-calendar@mail.imc.org  Mon Jul  7 18:31:04 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20065
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 18:31:03 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67MKSqt096858
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 15:20:28 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67MKSqV096857
	for ietf-calendar-bks; Mon, 7 Jul 2003 15:20:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67MKRqt096852
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 15:20:27 -0700 (PDT)
	(envelope-from ki.wong@Sun.COM)
Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35])
	by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h67MKT1J013343;
	Mon, 7 Jul 2003 16:20:29 -0600 (MDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail1sca.SFBay.Sun.COM (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h67MKThD007093;
	Mon, 7 Jul 2003 15:20:29 -0700 (PDT)
Received: from J02K.dvd2kdom.red.iplanet.com
 (j02k.red.iplanet.com [192.18.144.134]) by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HHO005D8E250E@ha13sca-mail1.sfbay.sun.com>; Mon,
 07 Jul 2003 15:20:29 -0700 (PDT)
Date: Mon, 07 Jul 2003 15:21:27 -0700
From: kiwong <ki.wong@sun.com>
Subject: RE: BYDAY and YEARLY
To: Dan Hickman <dhickman@rockinsoftware.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_9_.20030707152127.3748B@sun.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-transfer-encoding: 7BIT
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7BIT




> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> Sent: Monday, July 07, 2003 3:02 PM
> To: kiwong; ietf-calendar@imc.org
> Subject: RE: BYDAY and YEARLY
> 
> 
> You miss my point.  For yearly events, the BYMONTH is also derived from
> DTSTART.  For the sample, it would derive BYMONTH=5 since BYMONTH is not
> included in the RRULE.
> 

I don't think I miss your point. The RFC you quoted below is valid if the
recurring instance cannot be obtained by the RRULE, then use the DTSTART.
But the example RRULE:FREQ=YEARLY;BYDAY=20MO clearly defines the date of
the recurring instances, which are 20th Monday yearly. Whether it is in
May or not is not relevant because the date is already defined by the
RRULE.

ki


> Dan
> 
> > -----Original Message-----
> > From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> > Sent: Monday, July 07, 2003 2:05 PM
> > To: kiwong; ietf-calendar@imc.org
> > Subject: RE: BYDAY and YEARLY
> >
> >
> > But the from the same section 4.3.10
> >    Information, not contained in the rule, necessary to determine the
> >    various recurrence instance start time and dates are derived from
the
> >    Start Time (DTSTART) entry attribute. For example,
> >    "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
> >    month or a time. This information would be the same as what is
> >    specified for DTSTART.
> >
> > Using your logic, the following RRULE example from the RFC would assume
> May
> > as the BYMONTH and would mean the 20th Monday in May.
> >      DTSTART;TZID=US-Eastern:19970519T090000
> >      RRULE:FREQ=YEARLY;BYDAY=20MO
> >
> 
> But the day here is defined, which is the 20th Monday of the year.
> However, the time is not defined, so I will interpret it as 20th Monday
of
> the year at time 090000.
> 




From owner-ietf-calendar@mail.imc.org  Mon Jul  7 19:16:07 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21186
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 19:16:06 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67N4jqt099722
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 16:04:45 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67N4jAS099721
	for ietf-calendar-bks; Mon, 7 Jul 2003 16:04:45 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67N4hqt099716
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 16:04:44 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h67N4NYa024180
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 16:04:41 -0700
Message-ID: <3F09FC50.6000606@Royer.com>
Date: Mon, 07 Jul 2003 17:03:44 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF3DB2F062.B9E4921C-ON85256D5C.00747E61-85256D5C.0077D66F@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020305070002030609010004"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020305070002030609010004
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:

> Now, lets reread the 3rd paragraph again:
> 
>    The date/time value is set to the time when the original recurrence
>   instance would occur; meaning that if the intent is to change a
>   Friday meeting to Thursday, the date/time is still set to the
>   original Friday meeting.
> 
> This paragraph expressly says that the RECURRENCE-ID value "is still set 
> to the original" value AFTER the reschedule occurs.  ...

Orignal means the value of the object you are changing FROM.
It does not mean the value of SEQUENCE:0

You set the RECURRENCE-ID to the effective DTSTART time
of the instance you are change from which is NOT always SEQUENCE:0.

The "the date/time is still set to the original Friday meeting." is
refering to the value of the RECURRENCE-ID in the object that causes
the RECURRENCE-ID  to change in the next SEQUENCE.

  To change an instance, set the RECURRENE-ID to the 'was' value.
                         set the DTSTART to the 'is now' value.
                         And you supply the NEW  SEQUENCE number

After that object is processed the effective dtstart value
is now the value supplied in the DTSTART of the update object,
not the pre-updated (orignal) object. And the effective dtstart
time is the 'RECURRENCE-ID'.

 >
 > This paragraph expressly says that the RECURRENCE-ID value "is still set
 > to the original" value AFTER the reschedule occurs. ...


If you want update DTSTART:FRIDAY / SEQUENCE:3
                 to DTSTART:FRIDAY / SEQUENCE:4

Then provide the SEQUENCE:3 / DTSTART:FRIDAY recurrance-id
and the new DTSTART:value of THURSDAY and SEQUENCE:4.
And the examples in iTIP:

    An instance of a recurring event is assigned a unique identification,
    "RECURRENCE-ID" property, when that instance is renegotiated.
    Negotiation may be necessary when a substantive change to the event
    or to-do has be made (such as changing the start time, end time, due
    date or location). The "Organizer" can identify a specific recurrence
    instance using the "RECURRENCE-ID" property. The property value is
    equal to the date/time of the instance. If the "Organizer" wishes to
    change the "DTSTART", the original "DTSTART" value is used for
    "RECURRENCE-ID" property and the new "DTSTART" and "DTEND" values
    reflect the change.  Note that after the change has occurred, the
    "RECURRENCE-ID" has changed to the new "DTSTART" value.

Note that RECURRENEC-ID 'has changed to the new "DTSTART" value.'
And the word 'original' does NOT mean SEQUENCE:0, it means the
original value prior to the change.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020305070002030609010004
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDcyMzAzNDRaMCMGCSqGSIb3DQEJBDEWBBSn
wWvvFg9IY8Hi1sGwfZZ6GKQPvDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAeeH9YmYmbbpZ
KZqgiESO6J6hSkTd2viTrTwMiGFelVOEA8Q7YkNBF8EAvCqVd0ojiEDY7EJiUk4pcuXm0pvH
ubxCzOoC4ydH99JIl1Yw7h16hMA/KwRlfz2IP7oQYrtnS0p9ZSenAHRSecwXfj7mJ70p/xYU
jIwI6vZ+62SO3fhvonfJ/Rc8E0M/hpLgUrhARrGgbqvtCgOS98ZB0i2z5qIRiLySttDUN1NC
ON8zuFWyCQT5IYhCZ0/+tV+ivU8rqa2zUyd2y5em95NPbYf4V7iW6urQti0QkC/0Br00fwXn
vKkddK9tqp+nJBqHks9g7LqsF8vqDJE+HoPJQTix8gAAAAAAAA==
--------------ms020305070002030609010004--



From owner-ietf-calendar@mail.imc.org  Mon Jul  7 19:23:39 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21306
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 19:23:38 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67NCJqt000214
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 16:12:19 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67NCJbe000213
	for ietf-calendar-bks; Mon, 7 Jul 2003 16:12:19 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67NCIqt000207
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 16:12:18 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h67NC1Ya024246
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 16:12:16 -0700
Message-ID: <3F09FE3B.8030705@Royer.com>
Date: Mon, 07 Jul 2003 17:11:55 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF3DB2F062.B9E4921C-ON85256D5C.00747E61-85256D5C.0077D66F@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090703020905050604030902"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms090703020905050604030902
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:

> In order for the invitee to be able to find the UID/RECURRENCE-ID pair 
> at a level other than "1 off" from the current SEQUENCE the values MUST 
> stay fixed.  Otherwise its not possible to match them and then compare 
> SEQUENCE values of X and W if W != X - 1.  Clearly the values of 
> UID/RECURRENCE-ID MUST stay "fixed" so that SEQUENCE checks can properly 
> detect "larger" or "smaller" otherwise this "larger" or "smaller" check 
> is just not possible.

If they do not equal and you are the ORGANIZER - then throw
away their REPLY and generate them a new REQUEST as they do
not have a clue what they are replying to. If they send you
are REPLY that is less than the current object SEQUENCE, they
are replying to old news anyway - no matter which model you use.

If you get an instance specific update for SEQUENCE:x and you are an
ATTENDEE and you have SEQUENCE:z (where z <= (x-2)), then DO a REFRESH
as you do not have a clue what SEQUENCE (x-1) is at all and no matter
what model you use for RECURRENCE-ID, they will need to do a REFRESH.

If you get an instance specific update for SEQUENCE:x and you are an
ATTENDEE and you have SEQUENCE:z (where z = (x-1), Then you DO
have the latest object and can apply the instance change.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms090703020905050604030902
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDcyMzExNTVaMCMGCSqGSIb3DQEJBDEWBBRu
x0fyXe0QGovLqcIIoqXmY9hoUDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAFXDfXVY3MK1W
c/MwUDB2ONhtq1Vb2Ie2R1Q5UPR7kGZAnprofrlbegFVJVz/MspgI+IvNaVNlMfDxwLBniyl
wxy/yeEkInnT4S4dG/w77/zq4GJdsnpt+IW+KdmAx9AAN+GkrYTDL+dxHWzAJusgHF8VokuO
Epof5WwT1SEcvtCSearZN3fKZUvrPnhrxcllZ68j4HhyOcR9ueQ81pU5nw46IF6C8PXqX3xX
bdYm6bsToHTtHEjq22EQMC+JqIbKKzGiTKp/S3APGeYtk9SxoAPcSaj4yRBh++VgPM57RzjR
QyB0g0i4KvvRCNs43OZxF4mUi3utk9s6dG5/C5PMhAAAAAAAAA==
--------------ms090703020905050604030902--



From owner-ietf-calendar@mail.imc.org  Mon Jul  7 19:28:53 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21422
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 19:28:52 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67NIHqt000520
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 16:18:17 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h67NIHsX000519
	for ietf-calendar-bks; Mon, 7 Jul 2003 16:18:17 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h67NIFqt000508
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 16:18:16 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h67NHtYa024294
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 16:18:13 -0700
Message-ID: <3F09FF9C.1000309@Royer.com>
Date: Mon, 07 Jul 2003 17:17:48 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF3DB2F062.B9E4921C-ON85256D5C.00747E61-85256D5C.0077D66F@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070508070901030104060700"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms070508070901030104060700
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:

> I noticed that the cited description did NOT contain the paragraph that 
> clearly described that RECURRENCE-ID did not change on a reschedule.

I noticed that no such text exists in "4.8.4.4 Recurrence ID" which
is why I did not quote it :-)



-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms070508070901030104060700
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDcyMzE3NDlaMCMGCSqGSIb3DQEJBDEWBBRo
0nVzLQmROn9K9eqs/A+qwXdsPjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEATly3b59lbiC0
fwLABDGWYy8K2VfhoyGWZwWeIP5wgGgQ/Cti4N/yBP5YdGxp7ycEJ9rU8xtIdkSfUDrwfcGk
GZMnLfeSSFBuF6bu/cH2DWlJR3IGf1R/ifUPA5CrKL2ZlYoSkdrHQVrDm1BThJhNdo2w3Y1K
W5d9I2zE/7hMDGvArNyFjiGGiATIlp+Vqst6Q6oYUGRoEoEDTEiaz8IAihlIBXy2WQBWd9Wr
0gILmTxAMOHJrmtcQSxfEiSXsPkDjhf3DZoPzKC5GyO/d5msWNtr+VlZTVR5v5VteMYBsdgM
BInhSqU/GmPLy3WiQ9VeyzEdJIxAbuTWEc3+hHghGQAAAAAAAA==
--------------ms070508070901030104060700--



From owner-ietf-calendar@mail.imc.org  Mon Jul  7 21:08:08 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23604
	for <calsch-archive@lists.ietf.org>; Mon, 7 Jul 2003 21:08:08 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h680sKqt003688
	for <ietf-calendar-bks@above.proper.com>; Mon, 7 Jul 2003 17:54:20 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h680sKSD003687
	for ietf-calendar-bks; Mon, 7 Jul 2003 17:54:20 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from zeus.corpsite.com (zeus.corpsite.com [12.162.64.233])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h680sJqt003682
	for <ietf-calendar@imc.org>; Mon, 7 Jul 2003 17:54:19 -0700 (PDT)
	(envelope-from dhickman@rockinsoftware.com)
Received: from rockin1 (x1-6-00-d0-09-d6-9c-1b.entouch.net [65.124.87.93])
	(authenticated)
	by zeus.corpsite.com (8.11.1/8.11.1) with ESMTP id h680sKv19422;
	Mon, 7 Jul 2003 19:54:20 -0500 (EST)
From: "Dan Hickman" <dhickman@rockinsoftware.com>
To: "kiwong" <ki.wong@sun.com>, <ietf-calendar@imc.org>
Subject: RE: BYDAY and YEARLY
Date: Mon, 7 Jul 2003 19:54:44 -0500
Message-ID: <LNBBLMNOGOCILCNAGNONOEMCCGAF.dhickman@rockinsoftware.com>
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.2910.0)
In-Reply-To: <ISSMTP.2003_9_.20030707152127.3748B@sun.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


So your saying if BYMONTH is specified then the integer on BYDAY is now
relative to a month instead of a year.  In my opinion, that is not at all
clear from the RFC.  I'm curious if everyone else agrees with the following:

RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 as the last Sunday in October
every year.

RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12 as the last Sunday in
October, Nov, Dec every year.

Regards,
Dan Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com


-----Original Message-----
From: owner-ietf-calendar@mail.imc.org
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of kiwong
Sent: Monday, July 07, 2003 5:21 PM
To: Dan Hickman; ietf-calendar@imc.org
Subject: RE: BYDAY and YEARLY





> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> Sent: Monday, July 07, 2003 3:02 PM
> To: kiwong; ietf-calendar@imc.org
> Subject: RE: BYDAY and YEARLY
>
>
> You miss my point.  For yearly events, the BYMONTH is also derived from
> DTSTART.  For the sample, it would derive BYMONTH=5 since BYMONTH is not
> included in the RRULE.
>

I don't think I miss your point. The RFC you quoted below is valid if the
recurring instance cannot be obtained by the RRULE, then use the DTSTART.
But the example RRULE:FREQ=YEARLY;BYDAY=20MO clearly defines the date of
the recurring instances, which are 20th Monday yearly. Whether it is in
May or not is not relevant because the date is already defined by the
RRULE.

ki


> Dan
>
> > -----Original Message-----
> > From: Dan Hickman [mailto:dhickman@rockinsoftware.com]
> > Sent: Monday, July 07, 2003 2:05 PM
> > To: kiwong; ietf-calendar@imc.org
> > Subject: RE: BYDAY and YEARLY
> >
> >
> > But the from the same section 4.3.10
> >    Information, not contained in the rule, necessary to determine the
> >    various recurrence instance start time and dates are derived from
the
> >    Start Time (DTSTART) entry attribute. For example,
> >    "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
> >    month or a time. This information would be the same as what is
> >    specified for DTSTART.
> >
> > Using your logic, the following RRULE example from the RFC would assume
> May
> > as the BYMONTH and would mean the 20th Monday in May.
> >      DTSTART;TZID=US-Eastern:19970519T090000
> >      RRULE:FREQ=YEARLY;BYDAY=20MO
> >
>
> But the day here is defined, which is the 20th Monday of the year.
> However, the time is not defined, so I will interpret it as 20th Monday
of
> the year at time 090000.
>




From owner-ietf-calendar@mail.imc.org  Tue Jul  8 09:04:09 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20280
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 09:04:08 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68Co6qt072426
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 05:50:06 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h68Co6XN072425
	for ietf-calendar-bks; Tue, 8 Jul 2003 05:50:06 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68Co4qt072405
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 05:50:04 -0700 (PDT)
	(envelope-from lennox@grandcentral.cs.columbia.edu)
Received: from grandcentral.cs.columbia.edu (grandcentral.cs.columbia.edu [128.59.19.196])
	by cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h68CnmkN007420
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Tue, 8 Jul 2003 08:49:49 -0400 (EDT)
Received: from grandcentral.cs.columbia.edu (localhost [127.0.0.1])
	by grandcentral.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h68CnK5U027969;
	Tue, 8 Jul 2003 08:49:20 -0400 (EDT)
Received: (from lennox@localhost)
	by grandcentral.cs.columbia.edu (8.12.9/8.12.9/Submit) id h68CnJ48027966;
	Tue, 8 Jul 2003 08:49:19 -0400 (EDT)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16138.48591.568075.144668@grandcentral.cs.columbia.edu>
Date: Tue, 8 Jul 2003 08:49:19 -0400
To: "Dan Hickman" <dhickman@rockinsoftware.com>
Cc: "kiwong" <ki.wong@sun.com>, <ietf-calendar@imc.org>
Subject: RE: BYDAY and YEARLY
In-Reply-To: <LNBBLMNOGOCILCNAGNONOEMCCGAF.dhickman@rockinsoftware.com>
References: <ISSMTP.2003_9_.20030707152127.3748B@sun.com>
	<LNBBLMNOGOCILCNAGNONOEMCCGAF.dhickman@rockinsoftware.com>
X-Mailer: VM 7.16 under Emacs 20.7.1
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


On Monday, July 7 2003, "Dan Hickman" wrote to "kiwong, <ietf-calendar@imc.org>" saying:

> 
> So your saying if BYMONTH is specified then the integer on BYDAY is now
> relative to a month instead of a year.  In my opinion, that is not at all
> clear from the RFC.  I'm curious if everyone else agrees with the following:
> 
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 as the last Sunday in October
> every year.
> 
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12 as the last Sunday in
> October, Nov, Dec every year.

I disagree.  This is the description of the intDAY grammar from RFC2445:

   Each BYDAY value can also be preceded by a positive (+n) or negative
   (-n) integer. If present, this indicates the nth occurrence of the
   specific day within the MONTHLY or YEARLY RRULE. For example, within
   a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday
   within the month, whereas -1MO represents the last Monday of the
   month.

It's poorly worded, but clear when you read it; the integer applies to the
Nth occurence *within the interval*.  Also notice that in the grammar, ordwk
is defined as being in the range 1 to 53.

My code will resolve your two rules above as "no occurences other than
DTSTART" and "the last Sunday of the year" respectively, since the last
Sunday of the year always falls in December.

The rules with the descriptions you want are:
  RRULE:FREQ=MONTHLY;BYDAY=-1SU;BYMONTH=10
and
  RRULE:FREQ=MONTHLY;BYDAY=-1SU;BYMONTH=10,11,12

-- 
Jonathan Lennox
lennox at cs dot columbia dot edu


From owner-ietf-calendar@mail.imc.org  Tue Jul  8 10:36:45 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24737
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 10:36:45 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68ELGqt077909
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 07:21:16 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h68ELGQn077908
	for ietf-calendar-bks; Tue, 8 Jul 2003 07:21:16 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68ELFqt077903
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 07:21:15 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <LNBBLMNOGOCILCNAGNONKELACGAF.dhickman@rockinsoftware.com>
To: ietf-calendar@imc.org
Subject: Re: BYDAY and YEARLY
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF5765B5C6.B9474713-ON85256D5D.004C570F-85256D5D.004E567B@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Tue, 8 Jul 2003 10:16:09 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/08/2003
 10:17:29 AM,
	Serialize complete at 07/08/2003 10:17:29 AM
Content-Type: multipart/alternative; boundary="=_alternative 004E567685256D5D_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 004E567685256D5D_=
Content-Type: text/plain; charset="US-ASCII"

Dan wrote on 07/07/2003 03:16:10 PM:
> The issue is the use of BYDAY as follows to mean the last Sunday in 
October.
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
> 
> The BYDAY on yearly refers to weeks of the year and not weeks of the 
month
> so this really means the last Sunday of the year but only if it occurs 
in
> October.  The last week of the year will always be in December of course 
so
> the above rule never resolves to any valid dates.

I think a couple points from 2445 may help here (all from Section 4.3.10 
Recurrence Rule).  The first tidbit:

   Each BYDAY value can also be preceded by a positive (+n) or negative
   (-n) integer. If present, this indicates the nth occurrence of the
   specific day within the MONTHLY or YEARLY RRULE. For example, within
   a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday
   within the month, whereas -1MO represents the last Monday of the
   month. If an integer modifier is not present, it means all days of
   this type within the specified frequency. For example, within a
   MONTHLY rule, MO represents all Mondays within the month.

The second tidbit is:

   BYxxx rule parts modify the recurrence in some manner. BYxxx rule
   parts for a period of time which is the same or greater than the
   frequency generally reduce or limit the number of occurrences of the
   recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" reduces the
   number of recurrence instances from all days (if BYMONTH tag is not
   present) to all days in January. BYxxx rule parts for a period of
   time less than the frequency generally increase or expand the number
   of occurrences of the recurrence. For example,
   "FREQ=YEARLY;BYMONTH=1,2" increases the number of days within the
   yearly recurrence set from 1 (if BYMONTH tag is not present) to 2.

   If multiple BYxxx rule parts are specified, then after evaluating the
   specified FREQ and INTERVAL rule parts, the BYxxx rule parts are
   applied to the current set of evaluated occurrences in the following
   order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR,
   BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.

This second tidbit describes the case in Dans example rule; the BYDAY and 
BYMONTH modify the recurrence by expanding the set.  However since the 
BYMONTH and BYDAY parts only have 1 value each the set is not actually 
expanded but more modified.

By applying the first tidbit alone to just RRULE:FREQ=YEARLY;BYDAY=-1SU 
alone I would get the last Sunday in the year (the date is calculatable, 
the time is inherited from DTSTART).  However as Ki noted (from the second 
tidbit) there are other modifiers in play here and that is BYMONTH (or 
BYDAY if you follow the expressed order in the last paragraph cited).

Thus evaluating the rule:

RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10

You start with DTSTART and apply the FREQ and INTERVAL to get "Repeats 
yearly on the DTSTART date/time".

Then you apply the BYxxx rule parts in the order proscribed.  The first 
would be BYMONTH resulting in "Repeats yearly on the DTSTART date/time in 
the month of October" (the day and time are inherited, the month is 
overridden by BYMONTH).  The next step would be to apply the next BYxxx 
rule part we have, BYDAY.  This would result in "Repeats yearly on the 
Last Sunday (at the DTSTART time) in the month of October".

So the final set of instances would be DTSTART and on the last Sunday in 
October that immediately follows the DTSTART (it could be the next year or 
the same year depending on when DTSTART was).  At least thats how I take 
the text from the RFCs on recurrence rule evaluation.

In rechecking Dans text I see that he said "The BYDAY on yearly refers to 
weeks of the year and not weeks of the month" but BYDAY is defined as:

   The BYDAY rule part specifies a COMMA character (US-ASCII decimal 44)
   separated list of days of the week; MO indicates Monday; TU indicates
   Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates
   Friday; SA indicates Saturday; SU indicates Sunday.

which is not quite the same.  BYWEEK would be "weeks of the year".  BYDAY 
is defined as "days of the week".

> If the opinion is that "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" does 
mean
> the last Sunday in October, then that raises further questions.  For
> example, what dates would the following rule resolve to?
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12

With a BYMONTH=10,11,12 we would follow the same evaluation logic above 
and get 3 instances (the last Sundays of October, November and December) 
and that exactly jives w/the bit about "expand the number of occurences of 
the recurrence" from 2445.

The same expansion logic can be confirmed by using more than 1 value for 
the BYDAY as well. 

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 004E567685256D5D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Dan wrote on 07/07/2003 03:16:10 PM:<br>
&gt; The issue is the use of BYDAY as follows to mean the last Sunday in
October.<br>
&gt; RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10<br>
&gt; <br>
&gt; The BYDAY on yearly refers to weeks of the year and not weeks of the
month<br>
&gt; so this really means the last Sunday of the year but only if it occurs
in<br>
&gt; October. &nbsp;The last week of the year will always be in December
of course so<br>
&gt; the above rule never resolves to any valid dates.<br>
</tt></font>
<br><font size=2 face="sans-serif">I think a couple points from 2445 may
help here (all from Section 4.3.10 Recurrence Rule). &nbsp;The first tidbit:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;Each BYDAY value can also be preceded
by a positive (+n) or negative<br>
 &nbsp; (-n) integer. If present, this indicates the nth occurrence of
the<br>
 &nbsp; specific day within the MONTHLY or YEARLY RRULE. For example, within<br>
 &nbsp; a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday<br>
 &nbsp; within the month, whereas -1MO represents the last Monday of the<br>
 &nbsp; month. If an integer modifier is not present, it means all days
of<br>
 &nbsp; this type within the specified frequency. For example, within a<br>
 &nbsp; MONTHLY rule, MO represents all Mondays within the month.<br>
</tt></font>
<br><font size=2 face="sans-serif">The second tidbit is:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;BYxxx rule parts modify the recurrence
in some manner. BYxxx rule<br>
 &nbsp; parts for a period of time which is the same or greater than the<br>
 &nbsp; frequency generally reduce or limit the number of occurrences of
the<br>
 &nbsp; recurrence generated. For example, &quot;FREQ=DAILY;BYMONTH=1&quot;
reduces the<br>
 &nbsp; number of recurrence instances from all days (if BYMONTH tag is
not<br>
 &nbsp; present) to all days in January. BYxxx rule parts for a period
of<br>
 &nbsp; time less than the frequency generally increase or expand the number<br>
 &nbsp; of occurrences of the recurrence. For example,<br>
 &nbsp; &quot;FREQ=YEARLY;BYMONTH=1,2&quot; increases the number of days
within the<br>
 &nbsp; yearly recurrence set from 1 (if BYMONTH tag is not present) to
2.<br>
<br>
 &nbsp; If multiple BYxxx rule parts are specified, then after evaluating
the<br>
 &nbsp; specified FREQ and INTERVAL rule parts, the BYxxx rule parts are<br>
 &nbsp; applied to the current set of evaluated occurrences in the following<br>
 &nbsp; order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR,<br>
 &nbsp; BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.</tt></font>
<br>
<br><font size=2 face="sans-serif">This second tidbit describes the case
in Dans example rule; the BYDAY and BYMONTH modify the recurrence by expanding
the set. &nbsp;However since the BYMONTH and BYDAY parts only have 1 value
each the set is not actually expanded but more modified.</font>
<br>
<br><font size=2 face="sans-serif">By applying the first tidbit alone to
just RRULE:FREQ=YEARLY;BYDAY=-1SU alone I would get the last Sunday in
the year (the date is calculatable, the time is inherited from DTSTART).
&nbsp;However as Ki noted (from the second tidbit) there are other modifiers
in play here and that is BYMONTH (or BYDAY if you follow the expressed
order in the last paragraph cited).</font>
<br>
<br><font size=2 face="sans-serif">Thus evaluating the rule:</font>
<br>
<br><font size=2 face="sans-serif">RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10</font>
<br>
<br><font size=2 face="sans-serif">You start with DTSTART and apply the
FREQ and INTERVAL to get &quot;Repeats yearly on the DTSTART date/time&quot;.</font>
<br>
<br><font size=2 face="sans-serif">Then you apply the BYxxx rule parts
in the order proscribed. &nbsp;The first would be BYMONTH resulting in
&quot;Repeats yearly on the DTSTART date/time in the month of October&quot;
(the day and time are inherited, the month is overridden by BYMONTH). &nbsp;The
next step would be to apply the next BYxxx rule part we have, BYDAY. &nbsp;This
would result in &quot;Repeats yearly on the Last Sunday (at the DTSTART
time) in the month of October&quot;.</font>
<br>
<br><font size=2 face="sans-serif">So the final set of instances would
be DTSTART and on the last Sunday in October that immediately follows the
DTSTART (it could be the next year or the same year depending on when DTSTART
was). &nbsp;At least thats how I take the text from the RFCs on recurrence
rule evaluation.</font>
<br>
<br><font size=2 face="sans-serif">In rechecking Dans text I see that he
said &quot;</font><font size=2><tt>The BYDAY on yearly refers to weeks
of the year and not weeks of the month</tt></font><font size=2 face="sans-serif">&quot;
but BYDAY is defined as:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The BYDAY rule part specifies a COMMA
character (US-ASCII decimal 44)<br>
 &nbsp; separated list of days of the week; MO indicates Monday; TU indicates<br>
 &nbsp; Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates<br>
 &nbsp; Friday; SA indicates Saturday; SU indicates Sunday.</tt></font>
<br>
<br><font size=2 face="sans-serif">which is not quite the same. &nbsp;BYWEEK
would be &quot;weeks of the year&quot;. &nbsp;BYDAY is defined as &quot;days
of the week&quot;.</font>
<br>
<br><font size=2><tt>&gt; If the opinion is that &quot;RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10&quot;
does mean<br>
&gt; the last Sunday in October, then that raises further questions. &nbsp;For<br>
&gt; example, what dates would the following rule resolve to?<br>
&gt; RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10,11,12<br>
</tt></font>
<br><font size=2 face="sans-serif">With a BYMONTH=10,11,12 we would follow
the same evaluation logic above and get 3 instances (the last Sundays of
October, November and December) and that exactly jives w/the bit about
&quot;expand the number of occurences of the recurrence&quot; from 2445.</font>
<br>
<br><font size=2 face="sans-serif">The same expansion logic can be confirmed
by using more than 1 value for the BYDAY as well. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 004E567685256D5D_=--


From owner-ietf-calendar@mail.imc.org  Tue Jul  8 11:01:10 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25399
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 11:01:06 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68Elrqt079128
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 07:47:53 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h68ElrV8079127
	for ietf-calendar-bks; Tue, 8 Jul 2003 07:47:53 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68Elqqt079122
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 07:47:53 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F09FE3B.8030705@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF0E999961.3684732B-ON85256D5D.004E67CA-85256D5D.0050D24F@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Tue, 8 Jul 2003 10:43:17 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/08/2003
 10:44:05 AM,
	Serialize complete at 07/08/2003 10:44:05 AM
Content-Type: multipart/alternative; boundary="=_alternative 0050D24A85256D5D_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0050D24A85256D5D_=
Content-Type: text/plain; charset="US-ASCII"

Doug wrote on 07/07/2003 07:11:55 PM:
> If they do not equal and you are the ORGANIZER - then throw
> away their REPLY and generate them a new REQUEST as they do
> not have a clue what they are replying to. 

You absolutely DO if the RECURRENCE-ID is fixed.  You absolutely DO NOT if 
the RECURRENCE-ID changed on each reschedule.  However the latter case is 
contrary to the RFC where a fixed RECURRENCE-ID is clearly described:

   The date/time value is set to the time when the original recurrence
   instance would occur; meaning that if the intent is to change a
   Friday meeting to Thursday, the date/time is still set to the
   original Friday meeting.

If RECURRENCE-ID were NOT fixed then the only solution would be to rescyc 
ALL instances the invitee was invited too, not just the one in question.

With a fixed RECURRENCE-ID identifying the exact instance in question is 
trival (its part of the primary key used to find the instance) and thus 
the Organizer can quickly and easily just send a newer REQUEST for that 
particular instance.  No need to rewrite all instances the invitee has 
been invited to.  No need to resend all that extra data.

>                                            If they send you
> are REPLY that is less than the current object SEQUENCE, they
> are replying to old news anyway - no matter which model you use.

We have been talking about instance specific workflow but your phrase 
"current object SEQUENCE" has lots of loaded and undefined meaning. 

Each instance in the set has its own SEQUENCE value (thats how workflow 
for each instance can proceeded independent of all the other instances!). 
SEQUENCE is NOT shared among all the instances because if you did that 
then ANY reschedule of ANY single instance would raise the shared SEQUENCE 
value and invalidate ALL workflow for ALL other instances in the set. 

That generates TONS of extra wasted workflow messaging and renegotation. 
It also does NOT jive with the way message sequencing works in 2446.  If 
the UID/RECURRENCE-ID are the primary keys to find the instance (per rule 
1 in Section 2.1.5 in iTIP) and SEQUENCE is the secondary key (per rule 2) 
then clearly each instance MUST have its own SEQUENCE value.

So can you please clearly describe what you mean be "the current object 
SEQUENCE" because it sounds like it means each instance in the recurrence 
set shares the same SEQUENCE value...

> If you get an instance specific update for SEQUENCE:x and you are an
> ATTENDEE and you have SEQUENCE:z (where z <= (x-2)), then DO a REFRESH
> as you do not have a clue what SEQUENCE (x-1) is at all and no matter
> what model you use for RECURRENCE-ID, they will need to do a REFRESH.

Sorry but thats patently NOT true; its ONLY true for the case of a 
RECURRENCE-ID that changs on each reschedule (which is clearly contrary to 
the text from 2445 at top!)

If the RECURRENCE-ID is fixed then you have no doubt that it refers to the 
same RECURRENCE-ID you have but at a lower or higher SEQUENCE value.  You 
use the UID/RECURRENCE-ID to find the instance and then you check the 
SEQUENCE value. 

As iTIP clearly describes in 2 places its NOT an issue if you missed any 
intermediate REQUESTs since:

                                                              the
       component with the highest numeric value for the "SEQUENCE"
       property obsoletes all other revisions of the component with
       lower values.

That means if find the correct instance and detect that your SEQUENCE is 1 
or 2 or 100 below the one in the REQUEST then your copy is clearly 
obsolete.  NO need for a REFRESH as the REQUEST is a complete snapshot of 
that instance at that SEQUENCE value.  You simply accept, decline, etc and 
save away the new information.  Now if you are still thinking that Section 
4.7.2 of iTIP justifys the need to do a REFRESH because it says:

                      If the "SEQUENCE" number of the "Attendee's"
   instance is smaller, then the "Organizer" is sending out a newer
   version of the component and the "Attendee's" version needs to be
   updated. Since one or more updates have been missed, the "Attendee"
   SHOULD send a "REFRESH" message to the "Organizer" to get an updated
   version of the event.

then you need to consider some facts:

1:  In order for the UID/RECURRENCE-ID to match so you can do the SEQUENCE 
check of "larger" or "smaller" then clearly UID & RECURRENCE-ID  have to 
remain fixed!  Otherwise you cannot match the UID and RECURRENCE-ID values 
to the correct instance in question to do the SEQUENCE check.

2: As noted by Section 2.1.5 a higher SEQUENCE "obsoletes" all lower 
SEQUENCE values and this agrees when it says that the invitees "version 
needs to be updated.".  However since each REFRESH is a complete snapshot 
we no longer have to worry about missed "updates" because we no longer 
need them.  This was another benefit of going to full snapshots on 
REQUESTs from the early model of rolling changes forward (akin to changing 
the RECURRENCE-ID on each reschedule).  The new REQUEST obsoletes any 
lower SEQUENCE valued info, plain and simple.  No need to worry about 
missed updates, unless of course you try to ignore 2445 and change 
RECURRENCE-ID each time you reschedule.

3: The only way to recover a missed reschedule REQUEST is to resync ALL 
instances; you cannot just resync a single instance if RECURRENCE-ID 
changes.  Lots of wasted bandwidth and workflow thrashing.  However the 
text clearly says "SHOULD send a "REFRESH"" and NOT "MUST send a "REFRESH" 
to the Organzier.  In the delta model of RECURRENCE-IDs it would have to 
be a MUST in order to restore order.  SHOULD would not cut it.

> If you get an instance specific update for SEQUENCE:x and you are an
> ATTENDEE and you have SEQUENCE:z (where z = (x-1), Then you DO
> have the latest object and can apply the instance change.

The new REQUEST does NOT mean that you change the RECURRENCE-ID.  Thats 
contrary to 2445 no matter how you try to read bits of 2446. 

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 0050D24A85256D5D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug wrote on 07/07/2003 07:11:55 PM:<br>
&gt; If they do not equal and you are the ORGANIZER - then throw<br>
&gt; away their REPLY and generate them a new REQUEST as they do<br>
&gt; not have a clue what they are replying to. </tt></font>
<br>
<br><font size=2 face="sans-serif">You absolutely DO if the RECURRENCE-ID
is fixed. &nbsp;You absolutely DO NOT if the RECURRENCE-ID changed on each
reschedule. &nbsp;However the latter case is contrary to the RFC where
a fixed RECURRENCE-ID is clearly described:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The date/time value is set to the time
when the original recurrence<br>
 &nbsp; instance would occur; meaning that if the intent is to change a<br>
 &nbsp; Friday meeting to Thursday, the date/time is still set to the<br>
 &nbsp; original Friday meeting.</tt></font>
<br>
<br><font size=2 face="sans-serif">If RECURRENCE-ID were NOT fixed then
the only solution would be to rescyc ALL instances the invitee was invited
too, not just the one in question.</font>
<br>
<br><font size=2 face="sans-serif">With a fixed RECURRENCE-ID identifying
the exact instance in question is trival (its part of the primary key used
to find the instance) and thus the Organizer can quickly and easily just
send a newer REQUEST for that particular instance. &nbsp;No need to rewrite
all instances the invitee has been invited to. &nbsp;No need to resend
all that extra data.</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;If they send you<br>
&gt; are REPLY that is less than the current object SEQUENCE, they<br>
&gt; are replying to old news anyway - no matter which model you use.<br>
</tt></font>
<br><font size=2 face="sans-serif">We have been talking about instance
specific workflow but your phrase &quot;current object SEQUENCE&quot; has
lots of loaded and undefined meaning. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Each instance in the set has its own
SEQUENCE value (thats how workflow for each instance can proceeded independent
of all the other instances!). &nbsp;SEQUENCE is NOT shared among all the
instances because if you did that then ANY reschedule of ANY single instance
would raise the shared SEQUENCE value and invalidate ALL workflow for ALL
other instances in the set. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">That generates TONS of extra wasted
workflow messaging and renegotation. &nbsp;It also does NOT jive with the
way message sequencing works in 2446. &nbsp;If the UID/RECURRENCE-ID are
the primary keys to find the instance (per rule 1 in Section 2.1.5 in iTIP)
and SEQUENCE is the secondary key (per rule 2) then clearly each instance
MUST have its own SEQUENCE value.</font>
<br>
<br><font size=2 face="sans-serif">So can you please clearly describe what
you mean be &quot;the current object SEQUENCE&quot; because it sounds like
it means each instance in the recurrence set shares the same SEQUENCE value...</font>
<br>
<br><font size=2><tt>&gt; If you get an instance specific update for SEQUENCE:x
and you are an<br>
&gt; ATTENDEE and you have SEQUENCE:z (where z &lt;= (x-2)), then DO a
REFRESH<br>
&gt; as you do not have a clue what SEQUENCE (x-1) is at all and no matter<br>
&gt; what model you use for RECURRENCE-ID, they will need to do a REFRESH.<br>
</tt></font>
<br><font size=2 face="sans-serif">Sorry but thats patently NOT true; its
ONLY true for the case of a RECURRENCE-ID that changs on each reschedule
(which is clearly contrary to the text from 2445 at top!)</font>
<br>
<br><font size=2 face="sans-serif">If the RECURRENCE-ID is fixed then you
have no doubt that it refers to the same RECURRENCE-ID you have but at
a lower or higher SEQUENCE value. &nbsp;You use the UID/RECURRENCE-ID to
find the instance and then you check the SEQUENCE value. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">As iTIP clearly describes in 2 places
its NOT an issue if you missed any intermediate REQUESTs since:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; the<br>
 &nbsp; &nbsp; &nbsp; component with the highest numeric value for the
&quot;SEQUENCE&quot;<br>
 &nbsp; &nbsp; &nbsp; property obsoletes all other revisions of the component
with<br>
 &nbsp; &nbsp; &nbsp; lower values.</tt></font>
<br>
<br><font size=2 face="sans-serif">That means if find the correct instance
and detect that your SEQUENCE is 1 or 2 or 100 below the one in the REQUEST
then your copy is clearly obsolete. &nbsp;NO need for a REFRESH as the
REQUEST is a complete snapshot of that instance at that SEQUENCE value.
&nbsp;You simply accept, decline, etc and save away the new information.
&nbsp;Now if you are still thinking that Section 4.7.2 of iTIP justifys
the need to do a REFRESH because it says:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; If the &quot;SEQUENCE&quot; number of the &quot;Attendee's&quot;<br>
 &nbsp; instance is smaller, then the &quot;Organizer&quot; is sending
out a newer<br>
 &nbsp; version of the component and the &quot;Attendee's&quot; version
needs to be<br>
 &nbsp; updated. Since one or more updates have been missed, the &quot;Attendee&quot;<br>
 &nbsp; SHOULD send a &quot;REFRESH&quot; message to the &quot;Organizer&quot;
to get an updated<br>
 &nbsp; version of the event.</tt></font>
<br>
<br><font size=2 face="sans-serif">then you need to consider some facts:</font>
<br>
<br><font size=2 face="sans-serif">1: &nbsp;In order for the UID/RECURRENCE-ID
to match so you can do the SEQUENCE check of &quot;larger&quot; or &quot;smaller&quot;
then clearly UID &amp; RECURRENCE-ID &nbsp;have to remain fixed! &nbsp;Otherwise
you cannot match the UID and RECURRENCE-ID values to the correct instance
in question to do the SEQUENCE check.</font>
<br>
<br><font size=2 face="sans-serif">2: As noted by Section 2.1.5 a higher
SEQUENCE &quot;obsoletes&quot; all lower SEQUENCE values and this agrees
when it says that the invitees &quot;</font><font size=2><tt>version needs
to be updated.</tt></font><font size=2 face="sans-serif">&quot;. &nbsp;However
since each REFRESH is a complete snapshot we no longer have to worry about
missed &quot;updates&quot; because we no longer need them. &nbsp;This was
another benefit of going to full snapshots on REQUESTs from the early model
of rolling changes forward (akin to changing the RECURRENCE-ID on each
reschedule). &nbsp;The new REQUEST obsoletes any lower SEQUENCE valued
info, plain and simple. &nbsp;No need to worry about missed updates, unless
of course you try to ignore 2445 and change RECURRENCE-ID each time you
reschedule.</font>
<br>
<br><font size=2 face="sans-serif">3: The only way to recover a missed
reschedule REQUEST is to resync ALL instances; you cannot just resync a
single instance if RECURRENCE-ID changes. &nbsp;Lots of wasted bandwidth
and workflow thrashing. &nbsp;However the text clearly says &quot;SHOULD
send a &quot;REFRESH&quot;&quot; and NOT &quot;MUST send a &quot;REFRESH&quot;
to the Organzier. &nbsp;In the delta model of RECURRENCE-IDs it would have
to be a MUST in order to restore order. &nbsp;SHOULD would not cut it.</font>
<br>
<br><font size=2><tt>&gt; If you get an instance specific update for SEQUENCE:x
and you are an<br>
&gt; ATTENDEE and you have SEQUENCE:z (where z = (x-1), Then you DO<br>
&gt; have the latest object and can apply the instance change.<br>
</tt></font>
<br><font size=2 face="sans-serif">The new REQUEST does NOT mean that you
change the RECURRENCE-ID. &nbsp;Thats contrary to 2445 no matter how you
try to read bits of 2446. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 0050D24A85256D5D_=--


From owner-ietf-calendar@mail.imc.org  Tue Jul  8 11:48:35 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27727
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 11:48:34 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68FZEqt083305
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 08:35:14 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h68FZEs1083303
	for ietf-calendar-bks; Tue, 8 Jul 2003 08:35:14 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68FZCqt083297
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 08:35:13 -0700 (PDT)
	(envelope-from lennox@grandcentral.cs.columbia.edu)
Received: from grandcentral.cs.columbia.edu (grandcentral.cs.columbia.edu [128.59.19.196])
	by cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h68FZDkN027621
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Tue, 8 Jul 2003 11:35:13 -0400 (EDT)
Received: from grandcentral.cs.columbia.edu (localhost [127.0.0.1])
	by grandcentral.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h68FZC5U028528;
	Tue, 8 Jul 2003 11:35:12 -0400 (EDT)
Received: (from lennox@localhost)
	by grandcentral.cs.columbia.edu (8.12.9/8.12.9/Submit) id h68FZBOx028525;
	Tue, 8 Jul 2003 11:35:11 -0400 (EDT)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16138.58543.857825.899326@grandcentral.cs.columbia.edu>
Date: Tue, 8 Jul 2003 11:35:11 -0400
To: Bruce_Kahn@notesdev.ibm.com
Cc: ietf-calendar@imc.org
Subject: Re: BYDAY and YEARLY
In-Reply-To: <OF5765B5C6.B9474713-ON85256D5D.004C570F-85256D5D.004E567B@notesdev.ibm.com>
References: <LNBBLMNOGOCILCNAGNONKELACGAF.dhickman@rockinsoftware.com>
	<OF5765B5C6.B9474713-ON85256D5D.004C570F-85256D5D.004E567B@notesdev.ibm.com>
X-Mailer: VM 7.16 under Emacs 20.7.1
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


On Tuesday, July 8 2003, "Bruce_Kahn@notesdev.ibm.com" wrote to "ietf-calendar@imc.org" saying:

> Thus evaluating the rule:
> 
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
> 
> You start with DTSTART and apply the FREQ and INTERVAL to get "Repeats 
> yearly on the DTSTART date/time".
> 
> Then you apply the BYxxx rule parts in the order proscribed.  The first 
> would be BYMONTH resulting in "Repeats yearly on the DTSTART date/time in 
> the month of October" (the day and time are inherited, the month is 
> overridden by BYMONTH).  The next step would be to apply the next BYxxx 
> rule part we have, BYDAY.  This would result in "Repeats yearly on the 
> Last Sunday (at the DTSTART time) in the month of October".

I agree with this so far, but in your next step (concluding that this means
"the last Sunday in October") you make an unwarranted leap.  The definition
of the integer parts of BYDAY says, as you quoted previously:

>    Each BYDAY value can also be preceded by a positive (+n) or negative
>    (-n) integer. If present, this indicates the nth occurrence of the
>    specific day within the MONTHLY or YEARLY RRULE. 

Thus, since this is a YEARLY RRULE, the phrase "Last Sunday" means "Last
Sunday of the Year", not "Last Sunday of the Month."  The presence of a
BYMONTH rule doesn't affect this; by the spec, the integer part of BYDAY
depends *only* on the FREQ.

There is, of course, no last Sunday of the Year in October.  But this just
means that the quoted rule is vacuous, and its recurrence defines the empty
set, except for its DTSTART.  There's nothing "wrong" with that, any more
than there's something "wrong" with
     RRULE:FREQ=YEARLY;BYMONTH=2;BYMONTHDAY=30

-- 
Jonathan Lennox
lennox at cs dot columbia dot edu


From owner-ietf-calendar@mail.imc.org  Tue Jul  8 15:26:34 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06639
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 15:26:32 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68J9cqt000295
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 12:09:38 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h68J9cvT000294
	for ietf-calendar-bks; Tue, 8 Jul 2003 12:09:38 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h68J9bqt000288
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 12:09:37 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <16138.58543.857825.899326@grandcentral.cs.columbia.edu>
To: Jonathan Lennox <lennox@cs.columbia.edu>
Cc: ietf-calendar@imc.org
Subject: Re: BYDAY and YEARLY
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OF06CC861D.F2A29C8B-ON85256D5D.006700B8-85256D5D.00687FB4@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Tue, 8 Jul 2003 15:06:31 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/08/2003
 03:09:28 PM,
	Serialize complete at 07/08/2003 03:09:28 PM
Content-Type: multipart/alternative; boundary="=_alternative 00687FAF85256D5D_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 00687FAF85256D5D_=
Content-Type: text/plain; charset="US-ASCII"

Jonathan wrote on 07/08/2003 11:35:11 AM:
> I agree with this so far, but in your next step (concluding that this 
means
> "the last Sunday in October") you make an unwarranted leap.  The 
definition
> of the integer parts of BYDAY says, as you quoted previously:
> 
> >    Each BYDAY value can also be preceded by a positive (+n) or 
negative
> >    (-n) integer. If present, this indicates the nth occurrence of the
> >    specific day within the MONTHLY or YEARLY RRULE. 
> 
> Thus, since this is a YEARLY RRULE, the phrase "Last Sunday" means "Last
> Sunday of the Year", not "Last Sunday of the Month."  The presence of a
> BYMONTH rule doesn't affect this; by the spec, the integer part of BYDAY
> depends *only* on the FREQ.

The assumption about BYDAY would be accurate without other BYxxx modifiers 
present.  When I read:

   If multiple BYxxx rule parts are specified, then after evaluating the
   specified FREQ and INTERVAL rule parts, the BYxxx rule parts are
   applied to the current set of evaluated occurrences in the following
   order:

I take the phrase "applied to the current set of evaluated occurrences" to 
be that BYDAY works on the modified occurrences generated by applying the 
BYMONTH first.  This BYxxx modifier scopes the instance set to the month 
of October rather than the entire year. 

If BYMONTH were multivalued (ie: BYMONTH=10,11,12) then the occurrences 
would be scoped to the months of October thru December.  If no other BYxxx 
rule parts were there then Id say that the rule would evaluate to "The 
last Sunday in December" but because other BYxxx modfiiers were involved 
this is not true.

On the top of page 45 in 2445 there is an example of this that is pretty 
similar to Dans rule:

   Here is an example of evaluating multiple BYxxx rule parts.

     DTSTART;TZID=US-Eastern:19970105T083000
     RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
      BYMINUTE=30

   First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to arrive
   at "every other year". Then, "BYMONTH=1" would be applied to arrive
   at "every January, every other year". Then, "BYDAY=SU" would be
   applied to arrive at "every Sunday in January, every other year".
...

This evaluates just like I did for the BYDAY=-1SU;BYMONTH=10.  It follows 
the same logic I used (or I should say that my logic followed it w/o 
actually seeing this @ first) by applying the cited bits of 2445.

>                                                             But this 
just
> means that the quoted rule is vacuous, and its recurrence defines the 
empty
> set, except for its DTSTART. 

I do not think so given that the evaluation of the rule matches the way 
that the multiple BYxxx parts are described to modify each other (and are 
not applyed in parallel) and that the example in 2445 seems to confirm 
this.

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 00687FAF85256D5D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Jonathan wrote on 07/08/2003 11:35:11 AM:<br>
&gt; I agree with this so far, but in your next step (concluding that this
means<br>
&gt; &quot;the last Sunday in October&quot;) you make an unwarranted leap.
&nbsp;The definition<br>
&gt; of the integer parts of BYDAY says, as you quoted previously:<br>
&gt; <br>
&gt; &gt; &nbsp; &nbsp;Each BYDAY value can also be preceded by a positive
(+n) or negative<br>
&gt; &gt; &nbsp; &nbsp;(-n) integer. If present, this indicates the nth
occurrence of the<br>
&gt; &gt; &nbsp; &nbsp;specific day within the MONTHLY or YEARLY RRULE.
<br>
&gt; <br>
&gt; Thus, since this is a YEARLY RRULE, the phrase &quot;Last Sunday&quot;
means &quot;Last<br>
&gt; Sunday of the Year&quot;, not &quot;Last Sunday of the Month.&quot;
&nbsp;The presence of a<br>
&gt; BYMONTH rule doesn't affect this; by the spec, the integer part of
BYDAY<br>
&gt; depends *only* on the FREQ.<br>
</tt></font>
<br><font size=2 face="sans-serif">The assumption about BYDAY would be
accurate without other BYxxx modifiers present. &nbsp;When I read:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;If multiple BYxxx rule parts are specified,
then after evaluating the<br>
 &nbsp; specified FREQ and INTERVAL rule parts, the BYxxx rule parts are<br>
 &nbsp; applied to the current set of evaluated occurrences in the following<br>
 &nbsp; order:</tt></font>
<br>
<br><font size=2 face="sans-serif">I take the phrase &quot;applied to the
current set of evaluated occurrences&quot; to be that BYDAY works on the
modified occurrences generated by applying the BYMONTH first. &nbsp;This
BYxxx modifier scopes the instance set to the month of October rather than
the entire year. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">If BYMONTH were multivalued (ie: BYMONTH=10,11,12)
then the occurrences would be scoped to the months of October thru December.
&nbsp;If no other BYxxx rule parts were there then Id say that the rule
would evaluate to &quot;The last Sunday in December&quot; but because other
BYxxx modfiiers were involved this is not true.</font>
<br>
<br><font size=2 face="sans-serif">On the top of page 45 in 2445 there
is an example of this that is pretty similar to Dans rule:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;Here is an example of evaluating multiple
BYxxx rule parts.<br>
<br>
 &nbsp; &nbsp; DTSTART;TZID=US-Eastern:19970105T083000<br>
 &nbsp; &nbsp; RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;<br>
 &nbsp; &nbsp; &nbsp;BYMINUTE=30<br>
<br>
 &nbsp; First, the &quot;INTERVAL=2&quot; would be applied to &quot;FREQ=YEARLY&quot;
to arrive<br>
 &nbsp; at &quot;every other year&quot;. Then, &quot;BYMONTH=1&quot; would
be applied to arrive<br>
 &nbsp; at &quot;every January, every other year&quot;. Then, &quot;BYDAY=SU&quot;
would be<br>
 &nbsp; applied to arrive at &quot;every Sunday in January, every other
year&quot;.<br>
...</tt></font>
<br>
<br><font size=2 face="sans-serif">This evaluates just like I did for the
BYDAY=-1SU;BYMONTH=10. &nbsp;It follows the same logic I used (or I should
say that my logic followed it w/o actually seeing this @ first) by applying
the cited bits of 2445.</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; But this just<br>
&gt; means that the quoted rule is vacuous, and its recurrence defines
the empty<br>
&gt; set, except for its DTSTART. &nbsp;</tt></font>
<br>
<br><font size=2 face="sans-serif">I do not think so given that the evaluation
of the rule matches the way that the multiple BYxxx parts are described
to modify each other (and are not applyed in parallel) and that the example
in 2445 seems to confirm this.</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 00687FAF85256D5D_=--


From owner-ietf-calendar@mail.imc.org  Tue Jul  8 20:56:56 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17268
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 20:56:55 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h690cbqt021124
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 17:38:37 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h690cbeN021123
	for ietf-calendar-bks; Tue, 8 Jul 2003 17:38:37 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from zeus.corpsite.com (zeus.corpsite.com [12.162.64.233])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h690caqt021118
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 17:38:36 -0700 (PDT)
	(envelope-from dhickman@rockinsoftware.com)
Received: from rockin1 (x1-6-00-d0-09-d6-9c-1b.entouch.net [65.124.87.93])
	(authenticated)
	by zeus.corpsite.com (8.11.1/8.11.1) with ESMTP id h690bG705460;
	Tue, 8 Jul 2003 19:37:16 -0500 (EST)
From: "Dan Hickman" <dhickman@rockinsoftware.com>
To: <Bruce_Kahn@notesdev.ibm.com>, "Jonathan Lennox" <lennox@cs.columbia.edu>
Cc: <ietf-calendar@imc.org>
Subject: RE: BYDAY and YEARLY
Date: Tue, 8 Jul 2003 19:37:42 -0500
Message-ID: <LNBBLMNOGOCILCNAGNONMEPCCGAF.dhickman@rockinsoftware.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000A_01C34588.65CA2040"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <OF06CC861D.F2A29C8B-ON85256D5D.006700B8-85256D5D.00687FB4@notesdev.ibm.com>
Importance: Normal
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multi-part message in MIME format.

------=_NextPart_000_000A_01C34588.65CA2040
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The one thing that is obvious given the repeated conversations on this topic
is that the specification of BYDAY on YEARLY is ambiguous in the RFC. I see
both sides as valid interpretations. I suppose the real question is what was
the original intention of the author(s)?

Given the following:
1. Numerous VTIMEZONE examples in the RFC use
"RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" to mean "The last Sunday in
October", making it a big statement to say that these are not valid.
2. There are a number of implementations that already work this way now.
3. Rules like "The 5th Monday of the year but only in February" are probably
not that useful.

it appears there is much less impact if we go ahead and consider
"FREQ=YEARLY;BYMONTH=2;BYDAY=5MO" to mean the "5th Monday in February".  I
suggest we accept this interpretation.

Too bad I picked the wrong interpretation to implement :-|

Regards,
Dan Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com

  -----Original Message-----
  From: owner-ietf-calendar@mail.imc.org
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of
Bruce_Kahn@notesdev.ibm.com
  Sent: Tuesday, July 08, 2003 2:07 PM
  To: Jonathan Lennox
  Cc: ietf-calendar@imc.org
  Subject: Re: BYDAY and YEARLY



  Jonathan wrote on 07/08/2003 11:35:11 AM:
  > I agree with this so far, but in your next step (concluding that this
means
  > "the last Sunday in October") you make an unwarranted leap.  The
definition
  > of the integer parts of BYDAY says, as you quoted previously:
  >
  > >    Each BYDAY value can also be preceded by a positive (+n) or
negative
  > >    (-n) integer. If present, this indicates the nth occurrence of the
  > >    specific day within the MONTHLY or YEARLY RRULE.
  >
  > Thus, since this is a YEARLY RRULE, the phrase "Last Sunday" means "Last
  > Sunday of the Year", not "Last Sunday of the Month."  The presence of a
  > BYMONTH rule doesn't affect this; by the spec, the integer part of BYDAY
  > depends *only* on the FREQ.

  The assumption about BYDAY would be accurate without other BYxxx modifiers
present.  When I read:

     If multiple BYxxx rule parts are specified, then after evaluating the
    specified FREQ and INTERVAL rule parts, the BYxxx rule parts are
    applied to the current set of evaluated occurrences in the following
    order:

  I take the phrase "applied to the current set of evaluated occurrences" to
be that BYDAY works on the modified occurrences generated by applying the
BYMONTH first.  This BYxxx modifier scopes the instance set to the month of
October rather than the entire year.

  If BYMONTH were multivalued (ie: BYMONTH=10,11,12) then the occurrences
would be scoped to the months of October thru December.  If no other BYxxx
rule parts were there then Id say that the rule would evaluate to "The last
Sunday in December" but because other BYxxx modfiiers were involved this is
not true.

  On the top of page 45 in 2445 there is an example of this that is pretty
similar to Dans rule:

     Here is an example of evaluating multiple BYxxx rule parts.

      DTSTART;TZID=US-Eastern:19970105T083000
      RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
       BYMINUTE=30

    First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to arrive
    at "every other year". Then, "BYMONTH=1" would be applied to arrive
    at "every January, every other year". Then, "BYDAY=SU" would be
    applied to arrive at "every Sunday in January, every other year".
  ...

  This evaluates just like I did for the BYDAY=-1SU;BYMONTH=10.  It follows
the same logic I used (or I should say that my logic followed it w/o
actually seeing this @ first) by applying the cited bits of 2445.

  >                                                             But this
just
  > means that the quoted rule is vacuous, and its recurrence defines the
empty
  > set, except for its DTSTART.

  I do not think so given that the evaluation of the rule matches the way
that the multiple BYxxx parts are described to modify each other (and are
not applyed in parallel) and that the example in 2445 seems to confirm this.

  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...

------=_NextPart_000_000A_01C34588.65CA2040
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<P><FONT size=3D2>The one thing that is obvious given the repeated =
conversations=20
on this topic is that the specification of BYDAY on YEARLY is ambiguous =
in the=20
RFC. I see both sides a<SPAN class=3D477362800-09072003>s</SPAN> valid=20
interpretations. I suppose the real question is what was the original =
intention=20
of the author(s)<SPAN class=3D477362800-09072003>?</SPAN></FONT></P>
<P><FONT size=3D2>Given the following:<BR><SPAN =
class=3D477362800-09072003>1.=20
N</SPAN>umerous VTIMEZONE examples in the RFC&nbsp;<SPAN=20
class=3D477362800-09072003>use =
"RRULE:FREQ=3DYEARLY;BYDAY=3D-1SU;BYMONTH=3D10" to mean=20
"The last Sunday in October"</SPAN>, making it a big statement to say =
that these=20
are not valid.<BR><SPAN class=3D477362800-09072003>2.</SPAN> There are a =
number of=20
implementations that already work this way now.<BR><SPAN=20
class=3D477362800-09072003>3.</SPAN> Rules like "The 5th Monday of the =
year but=20
only in February" are probably not that useful.</FONT></P>
<P><FONT size=3D2>it appears there is much less impact if we go ahead =
and consider=20
"FREQ=3DYEARLY;BYMONTH=3D2;BYDAY=3D5MO" to mean the "5th Monday in=20
February".&nbsp;<SPAN class=3D477362800-09072003> </SPAN></FONT><SPAN=20
class=3D477362800-09072003><FONT size=3D2>I suggest we accept this=20
interpretation.</FONT></SPAN></P>
<P><SPAN class=3D477362800-09072003><FONT size=3D2>Too bad I picked the =
wrong=20
interpretation to implement :-|</FONT></SPAN></P>
<P><SPAN class=3D477362800-09072003><FONT =
size=3D2>Regards,<BR></FONT></SPAN><SPAN=20
class=3D477362800-09072003><FONT size=3D2>Dan =
Hickman<BR></FONT></SPAN><SPAN=20
class=3D477362800-09072003><FONT size=3D2>Rockin' =
Software<BR></FONT></SPAN><SPAN=20
class=3D477362800-09072003><FONT size=3D2><A=20
href=3D"mailto:dhickman@rockinsoftware.com">dhickman@rockinsoftware.com</=
A><BR></FONT></SPAN><SPAN=20
class=3D477362800-09072003><FONT size=3D2><A=20
href=3D"http://www.rockinsoftware.com">http://www.rockinsoftware.com</A><=
/FONT></SPAN></P></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B>=20
  owner-ietf-calendar@mail.imc.org=20
  [mailto:owner-ietf-calendar@mail.imc.org]<B>On Behalf Of=20
  </B>Bruce_Kahn@notesdev.ibm.com<BR><B>Sent:</B> Tuesday, July 08, 2003 =
2:07=20
  PM<BR><B>To:</B> Jonathan Lennox<BR><B>Cc:</B>=20
  ietf-calendar@imc.org<BR><B>Subject:</B> Re: BYDAY and=20
  YEARLY<BR><BR></FONT></DIV><BR><FONT size=3D2><TT>Jonathan wrote on =
07/08/2003=20
  11:35:11 AM:<BR>&gt; I agree with this so far, but in your next step=20
  (concluding that this means<BR>&gt; "the last Sunday in October") you =
make an=20
  unwarranted leap. &nbsp;The definition<BR>&gt; of the integer parts of =
BYDAY=20
  says, as you quoted previously:<BR>&gt; <BR>&gt; &gt; &nbsp; =
&nbsp;Each BYDAY=20
  value can also be preceded by a positive (+n) or negative<BR>&gt; &gt; =
&nbsp;=20
  &nbsp;(-n) integer. If present, this indicates the nth occurrence of=20
  the<BR>&gt; &gt; &nbsp; &nbsp;specific day within the MONTHLY or =
YEARLY RRULE.=20
  <BR>&gt; <BR>&gt; Thus, since this is a YEARLY RRULE, the phrase "Last =
Sunday"=20
  means "Last<BR>&gt; Sunday of the Year", not "Last Sunday of the =
Month."=20
  &nbsp;The presence of a<BR>&gt; BYMONTH rule doesn't affect this; by =
the spec,=20
  the integer part of BYDAY<BR>&gt; depends *only* on the=20
  FREQ.<BR></TT></FONT><BR><FONT face=3Dsans-serif size=3D2>The =
assumption about=20
  BYDAY would be accurate without other BYxxx modifiers present. =
&nbsp;When I=20
  read:</FONT> <BR><BR><FONT size=3D2><TT>&nbsp; &nbsp;If multiple BYxxx =
rule=20
  parts are specified, then after evaluating the<BR>&nbsp; specified =
FREQ and=20
  INTERVAL rule parts, the BYxxx rule parts are<BR>&nbsp; applied to the =
current=20
  set of evaluated occurrences in the following<BR>&nbsp; =
order:</TT></FONT>=20
  <BR><BR><FONT face=3Dsans-serif size=3D2>I take the phrase "applied to =
the current=20
  set of evaluated occurrences" to be that BYDAY works on the modified=20
  occurrences generated by applying the BYMONTH first. &nbsp;This BYxxx =
modifier=20
  scopes the instance set to the month of October rather than the entire =
year.=20
  &nbsp;</FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>If BYMONTH were =
multivalued=20
  (ie: BYMONTH=3D10,11,12) then the occurrences would be scoped to the =
months of=20
  October thru December. &nbsp;If no other BYxxx rule parts were there =
then Id=20
  say that the rule would evaluate to "The last Sunday in December" but =
because=20
  other BYxxx modfiiers were involved this is not true.</FONT> =
<BR><BR><FONT=20
  face=3Dsans-serif size=3D2>On the top of page 45 in 2445 there is an =
example of=20
  this that is pretty similar to Dans rule:</FONT> <BR><BR><FONT=20
  size=3D2><TT>&nbsp; &nbsp;Here is an example of evaluating multiple =
BYxxx rule=20
  parts.<BR><BR>&nbsp; &nbsp; =
DTSTART;TZID=3DUS-Eastern:19970105T083000<BR>&nbsp;=20
  &nbsp; =
RRULE:FREQ=3DYEARLY;INTERVAL=3D2;BYMONTH=3D1;BYDAY=3DSU;BYHOUR=3D8,9;<BR>=
&nbsp;=20
  &nbsp; &nbsp;BYMINUTE=3D30<BR><BR>&nbsp; First, the "INTERVAL=3D2" =
would be=20
  applied to "FREQ=3DYEARLY" to arrive<BR>&nbsp; at "every other year". =
Then,=20
  "BYMONTH=3D1" would be applied to arrive<BR>&nbsp; at "every January, =
every=20
  other year". Then, "BYDAY=3DSU" would be<BR>&nbsp; applied to arrive =
at "every=20
  Sunday in January, every other year".<BR>...</TT></FONT> <BR><BR><FONT =

  face=3Dsans-serif size=3D2>This evaluates just like I did for the=20
  BYDAY=3D-1SU;BYMONTH=3D10. &nbsp;It follows the same logic I used (or =
I should say=20
  that my logic followed it w/o actually seeing this @ first) by =
applying the=20
  cited bits of 2445.</FONT> <BR><BR><FONT size=3D2><TT>&gt; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; But this just<BR>&gt; means that =
the quoted=20
  rule is vacuous, and its recurrence defines the empty<BR>&gt; set, =
except for=20
  its DTSTART. &nbsp;</TT></FONT> <BR><BR><FONT face=3Dsans-serif =
size=3D2>I do not=20
  think so given that the evaluation of the rule matches the way that =
the=20
  multiple BYxxx parts are described to modify each other (and are not =
applyed=20
  in parallel) and that the example in 2445 seems to confirm =
this.</FONT>=20
  <BR><BR><FONT face=3Dsans-serif size=3D2>Bruce</FONT> <BR><FONT =
face=3Dsans-serif=20
  =
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<BR>Bruce=20
  Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet:=20
  Bruce_Kahn@notesdev.ibm.com<BR>Messaging &amp; Collaboration &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Phone: 978.399.6496<BR>IBM =
Software=20
  Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; FAX: and nothing but the FAX...<BR>Standard disclaimers =
apply,=20
  even where prohibited by law...</FONT></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000A_01C34588.65CA2040--



From owner-ietf-calendar@mail.imc.org  Tue Jul  8 22:31:40 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19645
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 22:31:40 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h692M4qt025875
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 19:22:04 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h692M47v025874
	for ietf-calendar-bks; Tue, 8 Jul 2003 19:22:04 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h692M3qt025869
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 19:22:03 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h692M0Ya005396
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 19:22:04 -0700
Message-ID: <3F0B7C3E.2010202@Royer.com>
Date: Tue, 08 Jul 2003 20:21:50 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OF0E999961.3684732B-ON85256D5D.004E67CA-85256D5D.0050D24F@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080609060307010903000007"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms080609060307010903000007
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug wrote on 07/07/2003 07:11:55 PM:
>  > If they do not equal and you are the ORGANIZER - then throw
>  > away their REPLY and generate them a new REQUEST as they do
>  > not have a clue what they are replying to.
> 
> You absolutely DO if the RECURRENCE-ID is fixed.  You absolutely DO NOT 
> if the RECURRENCE-ID changed on each reschedule.

My reply was to your single instance REQUEST, NOT a full REQUEST.
Your points (deleted) because we agree that if you get a FULL
REQUEST you do not need to do an REFRESH.

And I think we agree, if you get a single instance change,
and you are (>=2) lower than that SEQUENCE value in the object,
the ATTENDEE must do a REFRESH no matter what the model.



-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms080609060307010903000007
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDkwMjIxNTBaMCMGCSqGSIb3DQEJBDEWBBRR
9IsKxA/xBIdCn8kMUwhPVJGWsTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAT08Q8VJF2FzZ
BliqEYQe74gaPWDGD9dheO3ZiGvkW1+kOVRJOT1xecBhQyPKbFYuYTLBlhTkjtVh6Z+p9BXh
B+oIBKYDpXBPAW52B0YdH8B9Jb1wUMZvtYGVlPnuuCWi2qtz2OcQkLh5gGRpBqU+JnNqIawM
oifT2lpPyS3+BI2RHiihT+tLZCGclFpeyjae78wUzaW3kgerkGxfoEf5JrwN3cwMKZXrfAtV
XLcVB+MQNgXZU6KifnsI5hLawgvzhrMo/r9ErQCT77ybd5kR89zzUokPy7GRURdCA+k/5U/5
djx7fMf8+qgLFj0WuCG69z871InD7Hs33TU0HsWslQAAAAAAAA==
--------------ms080609060307010903000007--



From owner-ietf-calendar@mail.imc.org  Tue Jul  8 22:59:26 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19953
	for <calsch-archive@lists.ietf.org>; Tue, 8 Jul 2003 22:59:25 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h692n2qt027028
	for <ietf-calendar-bks@above.proper.com>; Tue, 8 Jul 2003 19:49:02 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h692n2KD027027
	for ietf-calendar-bks; Tue, 8 Jul 2003 19:49:02 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h692mxqt027020
	for <ietf-calendar@imc.org>; Tue, 8 Jul 2003 19:48:59 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: "Dan Hickman" <dhickman@rockinsoftware.com>
Cc: Bruce_Kahn@notesdev.ibm.com, ietf-calendar@imc.org,
        "Jonathan Lennox" <lennox@cs.columbia.edu>,
        owner-ietf-calendar@mail.imc.org
Subject: RE: BYDAY and YEARLY
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF68CE7BD7.45367453-ON85256D5E.000F5F87-85256D5E.000F7CAB@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Tue, 8 Jul 2003 22:49:08 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/08/2003 10:49:03 PM,
	Serialize complete at 07/08/2003 10:49:03 PM
Content-Type: multipart/alternative; boundary="=_alternative 000F7CA285256D5E_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 000F7CA285256D5E_=
Content-Type: text/plain; charset="us-ascii"

We are in dialog with the original authors - maybe we can try to get some 
sort of ruling on what they think this should be.  And if it's wrong, we 
need to get it fixed.  We need to make some adjustments to the RFC's 
anyway because of findings from interop testing.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




"Dan Hickman" <dhickman@rockinsoftware.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/08/2003 20:37

 
        To:     <Bruce_Kahn@notesdev.ibm.com>, "Jonathan Lennox" <lennox@cs.columbia.edu>
        cc:     <ietf-calendar@imc.org>
        Subject:        RE: BYDAY and YEARLY




The one thing that is obvious given the repeated conversations  on this 
topic is that the specification of BYDAY on YEARLY is ambiguous in the 
RFC. I see both sides asvalid  interpretations. I suppose the real 
question is what was the original intention  of the author(s)?

Given the following:
1.  umerous VTIMEZONE examples in the RFC use 
"RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" to mean  "The last Sunday in 
October", making it a big statement to say that these  are not valid.
2.There are a number of  implementations that already work this way now.
3.Rules like "The 5th Monday of the year but  only in February" are 
probably not that useful.

it appears there is much less impact if we go ahead and consider 
"FREQ=YEARLY;BYMONTH=2;BYDAY=5MO" to mean the "5th Monday in  February". I 
suggest we accept this  interpretation.

Too bad I picked the wrong  interpretation to implement :-|

Regards,
Dan Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com
-----Original Message-----
From:  owner-ietf-calendar@mail.imc.org 
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of  Bruce_Kahn@notesdev.ibm.com
Sent: Tuesday, July 08, 2003 2:07  PM
To: Jonathan Lennox
Cc:  ietf-calendar@imc.org
Subject: Re: BYDAY and  YEARLY



Jonathan wrote on 07/08/2003  11:35:11 AM:
> I agree with this so far, but in your next step  (concluding that this 
means
> "the last Sunday in October") you make an  unwarranted leap.  The 
definition
> of the integer parts of BYDAY  says, as you quoted previously:
> 
> >    Each BYDAY  value can also be preceded by a positive (+n) or 
negative
> >     (-n) integer. If present, this indicates the nth occurrence of the
> >    specific day within the MONTHLY or YEARLY RRULE. 
> 
> Thus, since this is a YEARLY RRULE, the phrase "Last Sunday"  means 
"Last
> Sunday of the Year", not "Last Sunday of the Month."   The presence of a
> BYMONTH rule doesn't affect this; by the spec,  the integer part of 
BYDAY
> depends *only* on the  FREQ.

The assumption about  BYDAY would be accurate without other BYxxx 
modifiers present.  When I  read: 

   If multiple BYxxx rule  parts are specified, then after evaluating the
  specified FREQ and  INTERVAL rule parts, the BYxxx rule parts are
  applied to the current  set of evaluated occurrences in the following
  order: 

I take the phrase "applied to the current  set of evaluated occurrences" 
to be that BYDAY works on the modified  occurrences generated by applying 
the BYMONTH first.  This BYxxx modifier  scopes the instance set to the 
month of October rather than the entire year.    

If BYMONTH were multivalued  (ie: BYMONTH=10,11,12) then the occurrences 
would be scoped to the months of  October thru December.  If no other 
BYxxx rule parts were there then Id  say that the rule would evaluate to 
"The last Sunday in December" but because  other BYxxx modfiiers were 
involved this is not true. 

On the top of page 45 in 2445 there is an example of  this that is pretty 
similar to Dans rule: 

   Here is an example of evaluating multiple BYxxx rule  parts.

    DTSTART;TZID=US-Eastern:19970105T083000
     RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
      BYMINUTE=30

  First, the "INTERVAL=2" would be  applied to "FREQ=YEARLY" to arrive
  at "every other year". Then,  "BYMONTH=1" would be applied to arrive
  at "every January, every  other year". Then, "BYDAY=SU" would be
  applied to arrive at "every  Sunday in January, every other year".
... 

This evaluates just like I did for the  BYDAY=-1SU;BYMONTH=10.  It follows 
the same logic I used (or I should say  that my logic followed it w/o 
actually seeing this @ first) by applying the  cited bits of 2445. 

>                                                                But this 
just
> means that the quoted  rule is vacuous, and its recurrence defines the 
empty
> set, except for  its DTSTART.   

I do not  think so given that the evaluation of the rule matches the way 
that the  multiple BYxxx parts are described to modify each other (and are 
not applyed  in parallel) and that the example in 2445 seems to confirm 
this. 

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 000F7CA285256D5E_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">We are in dialog with the original authors - maybe we can try to get some sort of ruling on what they think this should be. &nbsp;And if it's wrong, we need to get it fixed. &nbsp;We need to make some adjustments to the RFC's anyway because of findings from interop testing.<br>
___________________<br>
Patricia Egen Consulting<br>
www.egenconsulting.com<br>
423-875-2652</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>&quot;Dan Hickman&quot; &lt;dhickman@rockinsoftware.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/08/2003 20:37</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&lt;Bruce_Kahn@notesdev.ibm.com&gt;, &quot;Jonathan Lennox&quot; &lt;lennox@cs.columbia.edu&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;&lt;ietf-calendar@imc.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;RE: BYDAY and YEARLY</font></table>
<br>
<br>
<br>
<br>
<br><font size=2>The one thing that is obvious given the repeated conversations &nbsp;on this topic is that the specification of BYDAY on YEARLY is ambiguous in the &nbsp;RFC. I see both sides asvalid &nbsp;interpretations. I suppose the real question is what was the original intention &nbsp;of the author(s)?</font>
<br>
<br><font size=2>Given the following:</font>
<br><font size=2>1. &nbsp;umerous VTIMEZONE examples in the RFC&nbsp;use &quot;RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10&quot; to mean &nbsp;&quot;The last Sunday in October&quot;, making it a big statement to say that these &nbsp;are not valid.</font>
<br><font size=2>2.There are a number of &nbsp;implementations that already work this way now.</font>
<br><font size=2>3.Rules like &quot;The 5th Monday of the year but &nbsp;only in February&quot; are probably not that useful.</font>
<br>
<br><font size=2>it appears there is much less impact if we go ahead and consider &nbsp;&quot;FREQ=YEARLY;BYMONTH=2;BYDAY=5MO&quot; to mean the &quot;5th Monday in &nbsp;February&quot;.&nbsp;I suggest we accept this &nbsp;interpretation.</font>
<br>
<br><font size=2>Too bad I picked the wrong &nbsp;interpretation to implement :-|</font>
<br>
<br><font size=2>Regards,</font>
<br><font size=2>Dan Hickman</font>
<br><font size=2>Rockin' Software</font>
<br><a href=mailto:dhickman@rockinsoftware.com><font size=2 color=blue><u>dhickman@rockinsoftware.com</u></font></a>
<br><a href=http://www.rockinsoftware.com><font size=2 color=blue><u>http://www.rockinsoftware.com</u></font></a>
<br><font size=2>-----Original Message-----</font>
<br><font size=2><b>From:</b> &nbsp;owner-ietf-calendar@mail.imc.org &nbsp;[mailto:owner-ietf-calendar@mail.imc.org]<b>On Behalf Of &nbsp;</b>Bruce_Kahn@notesdev.ibm.com</font>
<br><font size=2><b>Sent:</b> Tuesday, July 08, 2003 2:07 &nbsp;PM</font>
<br><font size=2><b>To:</b> Jonathan Lennox</font>
<br><font size=2><b>Cc:</b> &nbsp;ietf-calendar@imc.org</font>
<br><font size=2><b>Subject:</b> Re: BYDAY and &nbsp;YEARLY</font>
<br>
<br>
<br>
<br><font size=2><tt>Jonathan wrote on 07/08/2003 &nbsp;11:35:11 AM:</tt></font>
<br><font size=2><tt>&gt; I agree with this so far, but in your next step &nbsp;(concluding that this means</tt></font>
<br><font size=2><tt>&gt; &quot;the last Sunday in October&quot;) you make an &nbsp;unwarranted leap. &nbsp;The definition</tt></font>
<br><font size=2><tt>&gt; of the integer parts of BYDAY &nbsp;says, as you quoted previously:</tt></font>
<br><font size=2><tt>&gt; </tt></font>
<br><font size=2><tt>&gt; &gt; &nbsp; &nbsp;Each BYDAY &nbsp;value can also be preceded by a positive (+n) or negative</tt></font>
<br><font size=2><tt>&gt; &gt; &nbsp; &nbsp;&nbsp;(-n) integer. If present, this indicates the nth occurrence of &nbsp;the</tt></font>
<br><font size=2><tt>&gt; &gt; &nbsp; &nbsp;specific day within the MONTHLY or YEARLY RRULE. &nbsp;</tt></font>
<br><font size=2><tt>&gt; </tt></font>
<br><font size=2><tt>&gt; Thus, since this is a YEARLY RRULE, the phrase &quot;Last Sunday&quot; &nbsp;means &quot;Last</tt></font>
<br><font size=2><tt>&gt; Sunday of the Year&quot;, not &quot;Last Sunday of the Month.&quot; &nbsp;&nbsp;The presence of a</tt></font>
<br><font size=2><tt>&gt; BYMONTH rule doesn't affect this; by the spec, &nbsp;the integer part of BYDAY</tt></font>
<br><font size=2><tt>&gt; depends *only* on the &nbsp;FREQ.</tt></font>
<br>
<br><font size=2>The assumption about &nbsp;BYDAY would be accurate without other BYxxx modifiers present. &nbsp;When I &nbsp;read:</font><font size=3> </font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;If multiple BYxxx rule &nbsp;parts are specified, then after evaluating the</tt></font>
<br><font size=2><tt>&nbsp; specified FREQ and &nbsp;INTERVAL rule parts, the BYxxx rule parts are</tt></font>
<br><font size=2><tt>&nbsp; applied to the current &nbsp;set of evaluated occurrences in the following</tt></font>
<br><font size=2><tt>&nbsp; order:</tt></font><font size=3> &nbsp;</font>
<br>
<br><font size=2>I take the phrase &quot;applied to the current &nbsp;set of evaluated occurrences&quot; to be that BYDAY works on the modified &nbsp;occurrences generated by applying the BYMONTH first. &nbsp;This BYxxx modifier &nbsp;scopes the instance set to the month of October rather than the entire year. &nbsp;&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>If BYMONTH were multivalued &nbsp;(ie: BYMONTH=10,11,12) then the occurrences would be scoped to the months of &nbsp;October thru December. &nbsp;If no other BYxxx rule parts were there then Id &nbsp;say that the rule would evaluate to &quot;The last Sunday in December&quot; but because &nbsp;other BYxxx modfiiers were involved this is not true.</font><font size=3> </font>
<br>
<br><font size=2>On the top of page 45 in 2445 there is an example of &nbsp;this that is pretty similar to Dans rule:</font><font size=3> </font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;Here is an example of evaluating multiple BYxxx rule &nbsp;parts.</tt></font>
<br>
<br><font size=2><tt>&nbsp; &nbsp; DTSTART;TZID=US-Eastern:19970105T083000</tt></font>
<br><font size=2><tt>&nbsp; &nbsp;&nbsp; RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;</tt></font>
<br><font size=2><tt>&nbsp; &nbsp;&nbsp; &nbsp;BYMINUTE=30</tt></font>
<br>
<br><font size=2><tt>&nbsp; First, the &quot;INTERVAL=2&quot; would be &nbsp;applied to &quot;FREQ=YEARLY&quot; to arrive</tt></font>
<br><font size=2><tt>&nbsp; at &quot;every other year&quot;. Then, &nbsp;&quot;BYMONTH=1&quot; would be applied to arrive</tt></font>
<br><font size=2><tt>&nbsp; at &quot;every January, every &nbsp;other year&quot;. Then, &quot;BYDAY=SU&quot; would be</tt></font>
<br><font size=2><tt>&nbsp; applied to arrive at &quot;every &nbsp;Sunday in January, every other year&quot;.</tt></font>
<br><font size=2><tt>...</tt></font><font size=3> </font>
<br>
<br><font size=2>This evaluates just like I did for the &nbsp;BYDAY=-1SU;BYMONTH=10. &nbsp;It follows the same logic I used (or I should say &nbsp;that my logic followed it w/o actually seeing this @ first) by applying the &nbsp;cited bits of 2445.</font><font size=3> </font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; But this just</tt></font>
<br><font size=2><tt>&gt; means that the quoted &nbsp;rule is vacuous, and its recurrence defines the empty</tt></font>
<br><font size=2><tt>&gt; set, except for &nbsp;its DTSTART. &nbsp;</tt></font><font size=3> </font>
<br>
<br><font size=2>I do not &nbsp;think so given that the evaluation of the rule matches the way that the &nbsp;multiple BYxxx parts are described to modify each other (and are not applyed &nbsp;in parallel) and that the example in 2445 seems to confirm this.</font><font size=3> &nbsp;</font>
<br>
<br><font size=2>Bruce</font><font size=3> </font>
<br><font size=2>===========================================================================</font>
<br><font size=2>Bruce &nbsp;Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: &nbsp;Bruce_Kahn@notesdev.ibm.com</font>
<br><font size=2>Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Phone: 978.399.6496</font>
<br><font size=2>IBM Software &nbsp;Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; FAX: and nothing but the FAX...</font>
<br><font size=2>Standard disclaimers apply, &nbsp;even where prohibited by law...</font>
<br>
<br>
--=_alternative 000F7CA285256D5E_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  9 11:24:43 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05611
	for <calsch-archive@lists.ietf.org>; Wed, 9 Jul 2003 11:24:42 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h69EwYqt001079
	for <ietf-calendar-bks@above.proper.com>; Wed, 9 Jul 2003 07:58:34 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h69EwYHt001078
	for ietf-calendar-bks; Wed, 9 Jul 2003 07:58:34 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h69EwXqt001071
	for <ietf-calendar@imc.org>; Wed, 9 Jul 2003 07:58:33 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <3F0B7C3E.2010202@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_06182003NP June 18, 2003
Message-ID: <OFFD7EEBAF.C4A0FB07-ON85256D5E.004EF65B-85256D5E.0051C73B@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Wed, 9 Jul 2003 10:58:29 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/09/2003
 10:58:19 AM,
	Serialize complete at 07/09/2003 10:58:19 AM
Content-Type: multipart/alternative; boundary="=_alternative 0051C73685256D5E_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0051C73685256D5E_=
Content-Type: text/plain; charset="US-ASCII"

Doug wrote on 07/08/2003 10:21:50 PM:
> >  > If they do not equal and you are the ORGANIZER - then throw
> >  > away their REPLY and generate them a new REQUEST as they do
> >  > not have a clue what they are replying to.
> > 
> > You absolutely DO if the RECURRENCE-ID is fixed.  You absolutely DO 
NOT 
> > if the RECURRENCE-ID changed on each reschedule.
> 
> My reply was to your single instance REQUEST, NOT a full REQUEST.
> Your points (deleted) because we agree that if you get a FULL
> REQUEST you do not need to do an REFRESH.

We also agree that the stale REPLY needs to be ignored and a new REQUEST 
needs to be sent.  However I was taking about a REPLY to a particular 
instance and we were only talking about an instance REQUEST.

If the RECURRENCE-ID changed on each reschedule then the Organizer has NO 
consistant and reliable way to match stale REPLYs ( UID / RECURRENCE-ID / 
(older) SEQUENCE ) to the proper current instance unless they track all 
UID / RECURRENCE-ID / SEQUENCE combos and can properly indentify the 
instance in question.  However as I showed using just 5 steps, at some 
point in time 2 instances can share the same UID / RECURRENCE-ID / 
SEQUENCE values thus this possible mechansim is not consistantly reliable. 
 As such a REPLY that the Organizer gets is not uniquely matachable to the 
instance the invitee was REPLYing to and the Orgaizer has no accurate way 
to decide which instance to send the new REQUEST for.

With a fixed RECURRENCE-ID, the Organizer can unambiguously tell exactly 
which instance the stale REPLY was for and send out the proper new 
REQUEST.  They simply match the UID & RECURRENCE-ID to find the instance 
and then check the SEQUENCE value.  If its different then the Organizer 
must not process the REPLY and sends the instances current defintion in a 
new REQUEST.  No fumbling.  No guessing.  No mis-matching.

> And I think we agree, if you get a single instance change,
> and you are (>=2) lower than that SEQUENCE value in the object,
> the ATTENDEE must do a REFRESH no matter what the model.

Sorry but I never said that nor do I agree with that.  In fact Ive said 
that its not necessary when you use fixed RECURRENCE-IDs.

Accepting your suggestion supposes that I accept that RECURRENCE-ID 
changes on each reschedule which I do not.  Thats because 2445 clearly 
says otherwise in no uncertain terms.  Thats also because it makes 
applying the iTIP rules on Message Sequencing, etc impossible!  If the 
primary key used to find the instance changes on each action then the key 
is no good for finding the instance and ordering the changes! 

In addition, the iTIP section you referred to only say "SHOULD" (not 
"must") because "one or more updates have been missed".  However since 
each REQUEST is a full snapshot missed updates are irrelevant since the 
would be obsoleted anyway at the higher SEQUENCE.  In addition if you read 
the description for the cases it should be clear that the only way for the 
UID/RECURRENCE-ID to match so that you can do a "higher" or "lower" 
SEQUENCE check is if UID and RECURRENCE-ID do not change.

Finally, since higher SEQUENCE versions obsolete lower SEQUENCE versions 
and each REQUEST is a fully defintion of that instance then _WHY_ would I 
need to do a REFRESH (full or otherwise) for the >=2 case?  The  REQUEST I 
just got simply "obsoletes" what I have currently and therefore I can 
safely take some action on it such as REPLYing.  I can safely and simply 
ignore the missed (or delayed) SEQUENCE+1 case since the REQUEST Im 
currently parsing is newer and has obsoleted the missed or delayed 
REQUEST.

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 0051C73685256D5E_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Doug wrote on 07/08/2003 10:21:50 PM:<br>
&gt; &gt; &nbsp;&gt; If they do not equal and you are the ORGANIZER - then
throw<br>
&gt; &gt; &nbsp;&gt; away their REPLY and generate them a new REQUEST as
they do<br>
&gt; &gt; &nbsp;&gt; not have a clue what they are replying to.<br>
&gt; &gt; <br>
&gt; &gt; You absolutely DO if the RECURRENCE-ID is fixed. &nbsp;You absolutely
DO NOT <br>
&gt; &gt; if the RECURRENCE-ID changed on each reschedule.<br>
&gt; <br>
&gt; My reply was to your single instance REQUEST, NOT a full REQUEST.<br>
&gt; Your points (deleted) because we agree that if you get a FULL<br>
&gt; REQUEST you do not need to do an REFRESH.<br>
</tt></font>
<br><font size=2 face="sans-serif">We also agree that the stale REPLY needs
to be ignored and a new REQUEST needs to be sent. &nbsp;However I was taking
about a REPLY to a particular instance and we were only talking about an
instance REQUEST.</font>
<br>
<br><font size=2 face="sans-serif">If the RECURRENCE-ID changed on each
reschedule then the Organizer has NO consistant and reliable way to match
stale REPLYs ( UID / RECURRENCE-ID / (older) SEQUENCE ) to the proper current
instance unless they track all UID / RECURRENCE-ID / SEQUENCE combos and
can properly indentify the instance in question. &nbsp;However as I showed
using just 5 steps, at some point in time 2 instances can share the same
UID / RECURRENCE-ID / SEQUENCE values thus this possible mechansim is not
consistantly reliable. &nbsp;As such a REPLY that the Organizer gets is
not uniquely matachable to the instance the invitee was REPLYing to and
the Orgaizer has no accurate way to decide which instance to send the new
REQUEST for.</font>
<br>
<br><font size=2 face="sans-serif">With a fixed RECURRENCE-ID, the Organizer
can unambiguously tell exactly which instance the stale REPLY was for and
send out the proper new REQUEST. &nbsp;They simply match the UID &amp;
RECURRENCE-ID to find the instance and then check the SEQUENCE value. &nbsp;If
its different then the Organizer must not process the REPLY and sends the
instances current defintion in a new REQUEST. &nbsp;No fumbling. &nbsp;No
guessing. &nbsp;No mis-matching.</font>
<br>
<br><font size=2><tt>&gt; And I think we agree, if you get a single instance
change,<br>
&gt; and you are (&gt;=2) lower than that SEQUENCE value in the object,<br>
&gt; the ATTENDEE must do a REFRESH no matter what the model.<br>
</tt></font>
<br><font size=2 face="sans-serif">Sorry but I never said that nor do I
agree with that. &nbsp;In fact Ive said that its not necessary when you
use fixed RECURRENCE-IDs.</font>
<br>
<br><font size=2 face="sans-serif">Accepting your suggestion supposes that
I accept that RECURRENCE-ID changes on each reschedule which I do not.
&nbsp;Thats because 2445 clearly says otherwise in no uncertain terms.
&nbsp;Thats also because it makes applying the iTIP rules on Message Sequencing,
etc impossible! &nbsp;If the primary key used to find the instance changes
on each action then the key is no good for finding the instance and ordering
the changes! </font>
<br>
<br><font size=2 face="sans-serif">In addition, the iTIP section you referred
to only say &quot;SHOULD&quot; (not &quot;must&quot;) because &quot;</font><font size=2><tt>one
or more updates have been missed</tt></font><font size=2 face="sans-serif">&quot;.
&nbsp;However since each REQUEST is a full snapshot missed updates are
irrelevant since the would be obsoleted anyway at the higher SEQUENCE.
&nbsp;In addition if you read the description for the cases it should be
clear that the only way for the UID/RECURRENCE-ID to match so that you
can do a &quot;higher&quot; or &quot;lower&quot; SEQUENCE check is if UID
and RECURRENCE-ID do not change.</font>
<br>
<br><font size=2 face="sans-serif">Finally, since higher SEQUENCE versions
obsolete lower SEQUENCE versions and each REQUEST is a fully defintion
of that instance then _WHY_ would I need to do a REFRESH (full or otherwise)
for the &gt;=2 case? &nbsp;The &nbsp;REQUEST I just got simply &quot;obsoletes&quot;
what I have currently and therefore I can safely take some action on it
such as REPLYing. &nbsp;I can safely and simply ignore the missed (or delayed)
SEQUENCE+1 case since the REQUEST Im currently parsing is newer and has
obsoleted the missed or delayed REQUEST.</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 0051C73685256D5E_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul  9 13:20:27 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10992
	for <calsch-archive@lists.ietf.org>; Wed, 9 Jul 2003 13:20:26 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h69H3uqt010564
	for <ietf-calendar-bks@above.proper.com>; Wed, 9 Jul 2003 10:03:56 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h69H3u36010563
	for ietf-calendar-bks; Wed, 9 Jul 2003 10:03:56 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h69H3sqt010558
	for <ietf-calendar@imc.org>; Wed, 9 Jul 2003 10:03:54 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h69H3pYa012903
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 9 Jul 2003 10:03:54 -0700
Message-ID: <3F0C4AED.2070300@Royer.com>
Date: Wed, 09 Jul 2003 11:03:41 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Correct handling of Recurrence-id
References: <OFFD7EEBAF.C4A0FB07-ON85256D5E.004EF65B-85256D5E.0051C73B@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020408010008080805040207"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020408010008080805040207
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:
> 
> Doug wrote on 07/08/2003 10:21:50 PM:
>  > >  > If they do not equal and you are the ORGANIZER - then throw
>  > >  > away their REPLY and generate them a new REQUEST as they do
>  > >  > not have a clue what they are replying to.
>  > >
>  > > You absolutely DO if the RECURRENCE-ID is fixed.  You absolutely DO 
> NOT
>  > > if the RECURRENCE-ID changed on each reschedule.
>  >
>  > My reply was to your single instance REQUEST, NOT a full REQUEST.
>  > Your points (deleted) because we agree that if you get a FULL
>  > REQUEST you do not need to do an REFRESH.
> 
> We also agree that the stale REPLY needs to be ignored and a new REQUEST 
> needs to be sent.  However I was taking about a REPLY to a particular 
> instance and we were only talking about an instance REQUEST.
> 
> If the RECURRENCE-ID changed on each reschedule then the Organizer has 
> NO consistant and reliable way to match stale REPLYs ( UID / 
> RECURRENCE-ID / (older) SEQUENCE ) to the proper current instance unless 
> they track all UID / RECURRENCE-ID / SEQUENCE combos and can properly 
> indentify the instance in question.  However as I showed using just 5 
> steps, at some point in time 2 instances can share the same UID / 
> RECURRENCE-ID / SEQUENCE values thus this possible mechansim is not 
> consistantly reliable.  As such a REPLY that the Organizer gets is not 
> uniquely matachable to the instance the invitee was REPLYing to and the 
> Orgaizer has no accurate way to decide which instance to send the new 
> REQUEST for.

As ALL REPLYs contain the SEQUENCE number they are replying to.
And ALL REQUESTS that change any recurrence date MUST bump the SEQUENCE
number. Then why can't you match them up as no matter what, they
must equal.
If the SEQUENCE number is OLD in a REPLY to a single instance change.
Send them the new REQUEST. Also note that in iTIP - ALL such text and
examples show that a single instance updates - bumps the SEQUENCE number.
So in ALL cases the SEQUENCE in the REPLY MUST match the SEQUENCE in
the REQUEST (single or full update).

If the ORGANIZER changes an instance twice, then the SEQUENCE number
gets bumped twice and the REPLY to each of those single instance updates
MUST have matching SEQUENCE numbers. It is ALWAYS reliable as they MUST
match ALL of the time.

There is NO difference between single and full updates with respect
to the SEQUENCE number, they both update the sequence number.

> With a fixed RECURRENCE-ID, the Organizer can unambiguously tell exactly 
> which instance the stale REPLY was for and send out the proper new 
> REQUEST.  They simply match the UID & RECURRENCE-ID to find the instance 
> and then check the SEQUENCE value.  If its different then the Organizer 
> must not process the REPLY and sends the instances current defintion in 
> a new REQUEST.  No fumbling.  No guessing.  No mis-matching.
> 
>  > And I think we agree, if you get a single instance change,
>  > and you are (>=2) lower than that SEQUENCE value in the object,
>  > the ATTENDEE must do a REFRESH no matter what the model.
> 
> Sorry but I never said that nor do I agree with that.  


> Accepting your suggestion supposes that I accept that RECURRENCE-ID 
> changes on each reschedule which I do not.  Thats because 2445 clearly 
> says otherwise in no uncertain terms. 

Only when you ignore all of the other text in iCAL and iTIP that
clearly and specifically disagrees with you.

Sequence of events. Assume your conflicting dates issue:
Assume ALL of the instance changes are for conflicting
dates/times.

	ORGANIZER sends a SINGLE instance update, SEQUENCE:3
	to ATTENDEE:a

	ORGANIZER sends a second SINGLE instance update, SEQUENEC:4
	to ATTENDEE:a

	ORGANIZER sends a third SINGLE instance update, SEQUENEC:5
	to ATTENDEE:a

	ORGANIZER gets a REPLY to SEQUENCE:5 from ATTENDEE:a
	ORGANIZER gets a REPLY to SEQUENCE:3 from ATTENDEE:a
	ORGANIZER gets a REPLY to SEQUENCE:4 from ATTENDEE:a

No matter which order you get them in, they are ALL resolvable.
There is NO breakage.

> 
> Finally, since higher SEQUENCE versions obsolete lower SEQUENCE versions 
> and each REQUEST is a fully defintion of that instance then _WHY_ would 
> I need to do a REFRESH (full or otherwise) for the >=2 case? 

Sequence of events. Assume that ATTENDEE has SEQUENCE:2 of
the object and that is the SEQUENCE number of their FIRST invitation
(they were not originally on the guest list).

	ORGANIZER sends a SINGLE instance update, SEQUENCE:3
	to ATTENDEE:a

	ORGANIZER sends a second SINGLE instance update, SEQUENCE:4
	to ATTENDEE:a

	ORGANIZER sends a third SINGLE instance update, SEQUENEC:5
	to ATTENDEE:a

	ATTENDEE gets the single instance update, SEQUENCE:4 and
         the CUA has determined that too much time has gone by and
         for some reason (vendor lost your inbox an you did iMIP) the
	single instance SEQUENCE:3 change is lost. The ATTENDEE MUST
	do a REFRESH as they would have no idea what was in the
	SEQUENCE:3 object. Now as the ORGANIZER is NOT required
	to remember the state of past object/sequence sets, the
	ATTENDEE MUST do a full REFRESH.

> The 
>  REQUEST I just got simply "obsoletes" what I have currently and 
> therefore I can safely take some action on it such as REPLYing.  I can 
> safely and simply ignore the missed (or delayed) SEQUENCE+1 case since 
> the REQUEST Im currently parsing is newer and has obsoleted the missed 
> or delayed REQUEST.

Full REQUEST - yes. The SEQUENCE:3 single instance change (in the
example above) may have changed the DTSTART of a MONDAY meeting to
another time on MONDAY and the SEQUENCE:4 change may have only changed
the DTSTART of the TUESDAY meeting to another time on TUESDAY. Without
doing a REFRESH, the ATTENDEE would not have a clue.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020408010008080805040207
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggO1
MIIDsQIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIIBqDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MDkxNzAzNDJaMCMGCSqGSIb3DQEJBDEWBBSX
/I+cvZJP+XLEAFwwveC9SoD74jBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB9AYL
KoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQCEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEBBQAEggEAoaxXSvXtphjH
j1dwU93LvUEbDSYUdAygsdPSg/dBrs6k9rpV6QTPb+bLK8fBrVUt8HUrCeqJoxWIJaiBRqAp
59YvI6QOSz+mnrj/dzlyQ5VqnHx+jywmbPHvlY/SyUgoPaacgp/CHSI9HB2F3i9KTLKpupqi
mAqCjrTK5D6sWiOwcQerqOsXWDX8ZQTujtYyQjQUqWJEcHxF/n+hicEW80QfufI+nECczDiZ
/e3e6N2G2b5q+QGniXZYZmL84wnPRuHFbnsThSFqt2vDx8+DVXEStMxIfLz7xPXwUCm1I4UW
atqSnkx90u17+3yhlWJTlT/INqfLr2ci89OFL0SfDwAAAAAAAA==
--------------ms020408010008080805040207--



From owner-ietf-calendar@mail.imc.org  Tue Jul 15 07:22:31 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14322
	for <calsch-archive@lists.ietf.org>; Tue, 15 Jul 2003 07:22:31 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6FB8bqt063950
	for <ietf-calendar-bks@above.proper.com>; Tue, 15 Jul 2003 04:08:37 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6FB8bKT063949
	for ietf-calendar-bks; Tue, 15 Jul 2003 04:08:37 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6FB8aqt063942
	for <ietf-calendar@imc.org>; Tue, 15 Jul 2003 04:08:37 -0700 (PDT)
	(envelope-from bobmah@MIT.EDU)
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.12.4/8.9.2) with ESMTP id h6FB8YYA017669
	for <ietf-calendar@imc.org>; Tue, 15 Jul 2003 07:08:34 -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.12.4/8.9.2) with ESMTP id h6FB8YnS001705
	for <ietf-calendar@imc.org>; Tue, 15 Jul 2003 07:08:34 -0400 (EDT)
Received: from [81.160.15.47] ([81.160.15.47])
	(authenticated bits=0)
	(User authenticated as bobmah@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id h6FB8VU9015988
	for <ietf-calendar@imc.org>; Tue, 15 Jul 2003 07:08:33 -0400 (EDT)
Mime-Version: 1.0
X-Sender: bobmah@PO12.MIT.EDU
Message-Id: <p05200f03bb398b253d47@[81.160.15.47]>
Date: Tue, 15 Jul 2003 07:08:30 -0400
To: ietf-calendar@imc.org
From: Bob Mahoney <bobmah@MIT.EDU>
Subject: IPv6 transition and calsch RFCs
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


As a part of their work, The IPv6 Operations Working Group (v6ops) is reviewing current standards for IPv4-specific references and dependances.  The AppsArea-related I-D is:

http://www.ietf.org/internet-drafts/draft-ietf-v6ops-ipv4survey-apps-01.txt

Most of our work is is clean of dependencies, although one issue is identified regarding the UID property in RFC 2445.   (In Section 4.8.4.7 "Unique Identifier")

From the IPv4 survey document:

>  Although the above does not explicitly state the use of IPv4
>  addresses, it addresses the explicit use of RFC 822, which is IPv4
>  dependent, as already described in section 3.4. To be IPv6 compliant
>  it should instead explicitly disallow the use of IPv4 addresses.

-Bob


From owner-ietf-calendar@mail.imc.org  Tue Jul 15 08:21:04 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16069
	for <calsch-archive@lists.ietf.org>; Tue, 15 Jul 2003 08:21:03 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6FC8tqt068630
	for <ietf-calendar-bks@above.proper.com>; Tue, 15 Jul 2003 05:08:55 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6FC8tMP068629
	for ietf-calendar-bks; Tue, 15 Jul 2003 05:08:55 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by above.proper.com (8.12.9/8.12.8) with SMTP id h6FC8sqt068624
	for <ietf-calendar@imc.org>; Tue, 15 Jul 2003 05:08:54 -0700 (PDT)
	(envelope-from JStracke@centive.com)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003071508181517452
 for <ietf-calendar@imc.org>; Tue, 15 Jul 2003 08:18:15 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 15 Jul 2003 08:06:10 -0400
Message-ID: <3F13EE32.80808@centive.com>
Date: Tue, 15 Jul 2003 08:06:10 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: IPv6 transition and calsch RFCs
References: <p05200f03bb398b253d47@[81.160.15.47]>
In-Reply-To: <p05200f03bb398b253d47@[81.160.15.47]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Jul 2003 12:06:10.0989 (UTC) FILETIME=[7B0DCDD0:01C34AC9]
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Bob Mahoney wrote:

>From the IPv4 survey document:
>  
>
>> Although the above does not explicitly state the use of IPv4
>> addresses, it addresses the explicit use of RFC 822,
>>
Can we reference RFC-2822 instead?

-- 
/=================================================================\
|John Stracke      |jstracke@centive.com                          |
|Principal Engineer|http://www.centive.com                        |
|Centive           |My opinions are my own.                       |
|=================================================================|
|You know that logic puzzle with the fox, the goose and the grain?|
|What kind of farmer owns a *fox*?                                |
\=================================================================/




From owner-ietf-calendar@mail.imc.org  Tue Jul 15 09:00:00 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17118
	for <calsch-archive@lists.ietf.org>; Tue, 15 Jul 2003 09:00:00 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6FCl3qt072829
	for <ietf-calendar-bks@above.proper.com>; Tue, 15 Jul 2003 05:47:03 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6FCl3Pe072827
	for ietf-calendar-bks; Tue, 15 Jul 2003 05:47:03 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6FCl2qt072821
	for <ietf-calendar@imc.org>; Tue, 15 Jul 2003 05:47:03 -0700 (PDT)
	(envelope-from bobmah@MIT.EDU)
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.12.4/8.9.2) with ESMTP id h6FCkvTQ009195;
	Tue, 15 Jul 2003 08:46:57 -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.12.4/8.9.2) with ESMTP id h6FCkva3006748;
	Tue, 15 Jul 2003 08:46:57 -0400 (EDT)
Received: from [81.160.15.47] ([81.160.152.210])
	(authenticated bits=0)
	(User authenticated as bobmah@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id h6FCk4U9026694;
	Tue, 15 Jul 2003 08:46:50 -0400 (EDT)
Mime-Version: 1.0
X-Sender: bobmah@PO12.MIT.EDU
Message-Id: <p05200f04bb39a5057e36@[81.160.15.47]>
In-Reply-To: <3F13EE32.80808@centive.com>
References: <p05200f03bb398b253d47@[81.160.15.47]>
 <3F13EE32.80808@centive.com>
Date: Tue, 15 Jul 2003 08:45:52 -0400
To: John Stracke <jstracke@centive.com>
From: Bob Mahoney <bobmah@MIT.EDU>
Subject: Re: IPv6 transition and calsch RFCs
Cc: ietf-calendar@imc.org
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


At 8:06 AM -0400 7/15/03, John Stracke wrote:
>
>Can we reference RFC-2822 instead?

I expect so.  The IPv6 folks gave an overview presentation at the Apps Area meeting, and there were some examples of RFCs they cited as having problems where the audience gave "We already fixed that" feedback...   They will be incorporating this info, and contacting the working groups that have documents requiring changes.

-Bob


From owner-ietf-calendar@mail.imc.org  Wed Jul 16 22:47:26 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27757
	for <calsch-archive@lists.ietf.org>; Wed, 16 Jul 2003 22:47:25 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6H2Vuqt024748
	for <ietf-calendar-bks@above.proper.com>; Wed, 16 Jul 2003 19:31:56 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6H2Vu1I024747
	for ietf-calendar-bks; Wed, 16 Jul 2003 19:31:56 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from zeus.corpsite.com (zeus.corpsite.com [12.162.64.233])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6H2Vrqt024737;
	Wed, 16 Jul 2003 19:31:53 -0700 (PDT)
	(envelope-from dhickman@rockinsoftware.com)
Received: from rockin1 (host-65-122-42-46.etstelephone.com [65.122.42.46] (may be forged))
	(authenticated)
	by zeus.corpsite.com (8.11.1/8.11.1) with ESMTP id h6H2Vm713451;
	Wed, 16 Jul 2003 21:31:50 -0500 (EST)
From: "Dan Hickman" <dhickman@rockinsoftware.com>
To: <pregen@egenconsulting.com>
Cc: <Bruce_Kahn@notesdev.ibm.com>, <ietf-calendar@imc.org>,
        "Jonathan Lennox" <lennox@cs.columbia.edu>,
        <owner-ietf-calendar@mail.imc.org>
Subject: RE: BYDAY and YEARLY
Date: Wed, 16 Jul 2003 21:32:10 -0500
Message-ID: <LNBBLMNOGOCILCNAGNONEEMACIAF.dhickman@rockinsoftware.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0031_01C34BE1.B6EB3AE0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <OF68CE7BD7.45367453-ON85256D5E.000F5F87-85256D5E.000F7CAB@egenconsulting.com>
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multi-part message in MIME format.

------=_NextPart_000_0031_01C34BE1.B6EB3AE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Any luck talking to the original authors.  I think we need to make a ruling
on this and get on down the road.

At this point, I feel it makes the most sense to conclude that
"RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" means "The last Sunday in
October".

Regards,
Dan Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com

  -----Original Message-----
  From: owner-ietf-calendar@mail.imc.org
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of
pregen@egenconsulting.com
  Sent: Tuesday, July 08, 2003 9:49 PM
  To: Dan Hickman
  Cc: Bruce_Kahn@notesdev.ibm.com; ietf-calendar@imc.org; Jonathan Lennox;
owner-ietf-calendar@mail.imc.org
  Subject: RE: BYDAY and YEARLY



  We are in dialog with the original authors - maybe we can try to get some
sort of ruling on what they think this should be.  And if it's wrong, we
need to get it fixed.  We need to make some adjustments to the RFC's anyway
because of findings from interop testing.
  ___________________
  Patricia Egen Consulting
  www.egenconsulting.com
  423-875-2652


       "Dan Hickman" <dhickman@rockinsoftware.com>
        Sent by: owner-ietf-calendar@mail.imc.org
        07/08/2003 20:37


                To:        <Bruce_Kahn@notesdev.ibm.com>, "Jonathan Lennox"
<lennox@cs.columbia.edu>
                cc:        <ietf-calendar@imc.org>
                Subject:        RE: BYDAY and YEARLY





  The one thing that is obvious given the repeated conversations  on this
topic is that the specification of BYDAY on YEARLY is ambiguous in the  RFC.
I see both sides asvalid  interpretations. I suppose the real question is
what was the original intention  of the author(s)?

  Given the following:
  1.  umerous VTIMEZONE examples in the RFC use
"RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" to mean  "The last Sunday in
October", making it a big statement to say that these  are not valid.
  2.There are a number of  implementations that already work this way now.
  3.Rules like "The 5th Monday of the year but  only in February" are
probably not that useful.

  it appears there is much less impact if we go ahead and consider
"FREQ=YEARLY;BYMONTH=2;BYDAY=5MO" to mean the "5th Monday in  February". I
suggest we accept this  interpretation.

  Too bad I picked the wrong  interpretation to implement :-|

  Regards,
  Dan Hickman
  Rockin' Software
  dhickman@rockinsoftware.com
  http://www.rockinsoftware.com
  -----Original Message-----
  From:  owner-ietf-calendar@mail.imc.org
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of
Bruce_Kahn@notesdev.ibm.com
  Sent: Tuesday, July 08, 2003 2:07  PM
  To: Jonathan Lennox
  Cc:  ietf-calendar@imc.org
  Subject: Re: BYDAY and  YEARLY



  Jonathan wrote on 07/08/2003  11:35:11 AM:
  > I agree with this so far, but in your next step  (concluding that this
means
  > "the last Sunday in October") you make an  unwarranted leap.  The
definition
  > of the integer parts of BYDAY  says, as you quoted previously:
  >
  > >    Each BYDAY  value can also be preceded by a positive (+n) or
negative
  > >     (-n) integer. If present, this indicates the nth occurrence of
the
  > >    specific day within the MONTHLY or YEARLY RRULE.
  >
  > Thus, since this is a YEARLY RRULE, the phrase "Last Sunday"  means
"Last
  > Sunday of the Year", not "Last Sunday of the Month."   The presence of a
  > BYMONTH rule doesn't affect this; by the spec,  the integer part of
BYDAY
  > depends *only* on the  FREQ.

  The assumption about  BYDAY would be accurate without other BYxxx
modifiers present.  When I  read:

     If multiple BYxxx rule  parts are specified, then after evaluating the
    specified FREQ and  INTERVAL rule parts, the BYxxx rule parts are
    applied to the current  set of evaluated occurrences in the following
    order:

  I take the phrase "applied to the current  set of evaluated occurrences"
to be that BYDAY works on the modified  occurrences generated by applying
the BYMONTH first.  This BYxxx modifier  scopes the instance set to the
month of October rather than the entire year.

  If BYMONTH were multivalued  (ie: BYMONTH=10,11,12) then the occurrences
would be scoped to the months of  October thru December.  If no other BYxxx
rule parts were there then Id  say that the rule would evaluate to "The last
Sunday in December" but because  other BYxxx modfiiers were involved this is
not true.

  On the top of page 45 in 2445 there is an example of  this that is pretty
similar to Dans rule:

     Here is an example of evaluating multiple BYxxx rule  parts.

      DTSTART;TZID=US-Eastern:19970105T083000
       RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
        BYMINUTE=30

    First, the "INTERVAL=2" would be  applied to "FREQ=YEARLY" to arrive
    at "every other year". Then,  "BYMONTH=1" would be applied to arrive
    at "every January, every  other year". Then, "BYDAY=SU" would be
    applied to arrive at "every  Sunday in January, every other year".
  ...

  This evaluates just like I did for the  BYDAY=-1SU;BYMONTH=10.  It follows
the same logic I used (or I should say  that my logic followed it w/o
actually seeing this @ first) by applying the  cited bits of 2445.

  >                                                                But this
just
  > means that the quoted  rule is vacuous, and its recurrence defines the
empty
  > set, except for  its DTSTART.

  I do not  think so given that the evaluation of the rule matches the way
that the  multiple BYxxx parts are described to modify each other (and are
not applyed  in parallel) and that the example in 2445 seems to confirm
this.

  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...



------=_NextPart_000_0031_01C34BE1.B6EB3AE0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =
size=3D2>Any=20
luck talking to the original authors.&nbsp; I think we need to make a =
ruling on=20
this and get on down the road.</FONT></SPAN></DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =
size=3D2>At=20
this point, I feel it makes the most sense to conclude that=20
"RRULE:FREQ=3DYEARLY;BYDAY=3D-1SU;BYMONTH=3D10" means "The last Sunday =
in=20
October".</FONT></SPAN></DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =

size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =
size=3D2>Dan=20
Hickman</FONT></SPAN></DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =

size=3D2>Rockin' Software</FONT></SPAN></DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =
size=3D2><A=20
href=3D"mailto:dhickman@rockinsoftware.com">dhickman@rockinsoftware.com</=
A></FONT></SPAN></DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =
size=3D2><A=20
href=3D"http://www.rockinsoftware.com">http://www.rockinsoftware.com</A><=
/FONT></SPAN></DIV>
<DIV><SPAN class=3D903592902-17072003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B>=20
  owner-ietf-calendar@mail.imc.org=20
  [mailto:owner-ietf-calendar@mail.imc.org]<B>On Behalf Of=20
  </B>pregen@egenconsulting.com<BR><B>Sent:</B> Tuesday, July 08, 2003 =
9:49=20
  PM<BR><B>To:</B> Dan Hickman<BR><B>Cc:</B> =
Bruce_Kahn@notesdev.ibm.com;=20
  ietf-calendar@imc.org; Jonathan Lennox;=20
  owner-ietf-calendar@mail.imc.org<BR><B>Subject:</B> RE: BYDAY and=20
  YEARLY<BR><BR></FONT></DIV><BR><FONT face=3Dsans-serif size=3D2>We are =
in dialog=20
  with the original authors - maybe we can try to get some sort of =
ruling on=20
  what they think this should be. &nbsp;And if it's wrong, we need to =
get it=20
  fixed. &nbsp;We need to make some adjustments to the RFC's anyway =
because of=20
  findings from interop testing.<BR>___________________<BR>Patricia Egen =

  Consulting<BR>www.egenconsulting.com<BR>423-875-2652</FONT> =
<BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD>
      <TD><FONT face=3Dsans-serif size=3D1><B>"Dan Hickman"=20
        &lt;dhickman@rockinsoftware.com&gt;</B></FONT> <BR><FONT =
face=3Dsans-serif=20
        size=3D1>Sent by: owner-ietf-calendar@mail.imc.org</FONT>=20
        <P><FONT face=3Dsans-serif size=3D1>07/08/2003 20:37</FONT> =
<BR></P>
      <TD><FONT face=3DArial size=3D1>&nbsp; &nbsp; &nbsp; &nbsp; =
</FONT><BR><FONT=20
        face=3Dsans-serif size=3D1>&nbsp; &nbsp; &nbsp; &nbsp; To: =
&nbsp; &nbsp;=20
        &nbsp; &nbsp;&lt;Bruce_Kahn@notesdev.ibm.com&gt;, "Jonathan =
Lennox"=20
        &lt;lennox@cs.columbia.edu&gt;</FONT> <BR><FONT =
face=3Dsans-serif=20
        size=3D1>&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp;=20
        &nbsp;&lt;ietf-calendar@imc.org&gt;</FONT> <BR><FONT =
face=3Dsans-serif=20
        size=3D1>&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; =
&nbsp;=20
        &nbsp;RE: BYDAY and=20
  YEARLY</FONT></TR></TBODY></TABLE><BR><BR><BR><BR><BR><FONT =
size=3D2>The one=20
  thing that is obvious given the repeated conversations &nbsp;on this =
topic is=20
  that the specification of BYDAY on YEARLY is ambiguous in the =
&nbsp;RFC. I see=20
  both sides asvalid &nbsp;interpretations. I suppose the real question =
is what=20
  was the original intention &nbsp;of the author(s)?</FONT> =
<BR><BR><FONT=20
  size=3D2>Given the following:</FONT> <BR><FONT size=3D2>1. =
&nbsp;umerous VTIMEZONE=20
  examples in the RFC&nbsp;use =
"RRULE:FREQ=3DYEARLY;BYDAY=3D-1SU;BYMONTH=3D10" to mean=20
  &nbsp;"The last Sunday in October", making it a big statement to say =
that=20
  these &nbsp;are not valid.</FONT> <BR><FONT size=3D2>2.There are a =
number of=20
  &nbsp;implementations that already work this way now.</FONT> <BR><FONT =

  size=3D2>3.Rules like "The 5th Monday of the year but &nbsp;only in =
February"=20
  are probably not that useful.</FONT> <BR><BR><FONT size=3D2>it appears =
there is=20
  much less impact if we go ahead and consider=20
  &nbsp;"FREQ=3DYEARLY;BYMONTH=3D2;BYDAY=3D5MO" to mean the "5th Monday =
in=20
  &nbsp;February".&nbsp;I suggest we accept this =
&nbsp;interpretation.</FONT>=20
  <BR><BR><FONT size=3D2>Too bad I picked the wrong &nbsp;interpretation =
to=20
  implement :-|</FONT> <BR><BR><FONT size=3D2>Regards,</FONT> <BR><FONT =
size=3D2>Dan=20
  Hickman</FONT> <BR><FONT size=3D2>Rockin' Software</FONT> <BR><A=20
  href=3D"mailto:dhickman@rockinsoftware.com"><FONT color=3Dblue=20
  size=3D2><U>dhickman@rockinsoftware.com</U></FONT></A> <BR><A=20
  href=3D"http://www.rockinsoftware.com"><FONT color=3Dblue=20
  size=3D2><U>http://www.rockinsoftware.com</U></FONT></A> <BR><FONT=20
  size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2><B>From:</B>=20
  &nbsp;owner-ietf-calendar@mail.imc.org=20
  &nbsp;[mailto:owner-ietf-calendar@mail.imc.org]<B>On Behalf Of=20
  &nbsp;</B>Bruce_Kahn@notesdev.ibm.com</FONT> <BR><FONT =
size=3D2><B>Sent:</B>=20
  Tuesday, July 08, 2003 2:07 &nbsp;PM</FONT> <BR><FONT =
size=3D2><B>To:</B>=20
  Jonathan Lennox</FONT> <BR><FONT size=3D2><B>Cc:</B>=20
  &nbsp;ietf-calendar@imc.org</FONT> <BR><FONT size=3D2><B>Subject:</B> =
Re: BYDAY=20
  and &nbsp;YEARLY</FONT> <BR><BR><BR><BR><FONT size=3D2><TT>Jonathan =
wrote on=20
  07/08/2003 &nbsp;11:35:11 AM:</TT></FONT> <BR><FONT size=3D2><TT>&gt; =
I agree=20
  with this so far, but in your next step &nbsp;(concluding that this=20
  means</TT></FONT> <BR><FONT size=3D2><TT>&gt; "the last Sunday in =
October") you=20
  make an &nbsp;unwarranted leap. &nbsp;The definition</TT></FONT> =
<BR><FONT=20
  size=3D2><TT>&gt; of the integer parts of BYDAY &nbsp;says, as you =
quoted=20
  previously:</TT></FONT> <BR><FONT size=3D2><TT>&gt; =
</TT></FONT><BR><FONT=20
  size=3D2><TT>&gt; &gt; &nbsp; &nbsp;Each BYDAY &nbsp;value can also be =
preceded=20
  by a positive (+n) or negative</TT></FONT> <BR><FONT size=3D2><TT>&gt; =
&gt;=20
  &nbsp; &nbsp;&nbsp;(-n) integer. If present, this indicates the nth =
occurrence=20
  of &nbsp;the</TT></FONT> <BR><FONT size=3D2><TT>&gt; &gt; &nbsp; =
&nbsp;specific=20
  day within the MONTHLY or YEARLY RRULE. &nbsp;</TT></FONT> <BR><FONT=20
  size=3D2><TT>&gt; </TT></FONT><BR><FONT size=3D2><TT>&gt; Thus, since =
this is a=20
  YEARLY RRULE, the phrase "Last Sunday" &nbsp;means "Last</TT></FONT> =
<BR><FONT=20
  size=3D2><TT>&gt; Sunday of the Year", not "Last Sunday of the Month." =

  &nbsp;&nbsp;The presence of a</TT></FONT> <BR><FONT size=3D2><TT>&gt; =
BYMONTH=20
  rule doesn't affect this; by the spec, &nbsp;the integer part of=20
  BYDAY</TT></FONT> <BR><FONT size=3D2><TT>&gt; depends *only* on the=20
  &nbsp;FREQ.</TT></FONT> <BR><BR><FONT size=3D2>The assumption about =
&nbsp;BYDAY=20
  would be accurate without other BYxxx modifiers present. &nbsp;When I=20
  &nbsp;read:</FONT><FONT size=3D3> </FONT><BR><BR><FONT =
size=3D2><TT>&nbsp;=20
  &nbsp;If multiple BYxxx rule &nbsp;parts are specified, then after =
evaluating=20
  the</TT></FONT> <BR><FONT size=3D2><TT>&nbsp; specified FREQ and =
&nbsp;INTERVAL=20
  rule parts, the BYxxx rule parts are</TT></FONT> <BR><FONT =
size=3D2><TT>&nbsp;=20
  applied to the current &nbsp;set of evaluated occurrences in the=20
  following</TT></FONT> <BR><FONT size=3D2><TT>&nbsp; =
order:</TT></FONT><FONT=20
  size=3D3> &nbsp;</FONT> <BR><BR><FONT size=3D2>I take the phrase =
"applied to the=20
  current &nbsp;set of evaluated occurrences" to be that BYDAY works on =
the=20
  modified &nbsp;occurrences generated by applying the BYMONTH first. =
&nbsp;This=20
  BYxxx modifier &nbsp;scopes the instance set to the month of October =
rather=20
  than the entire year. &nbsp;&nbsp;</FONT><FONT size=3D3> =
</FONT><BR><BR><FONT=20
  size=3D2>If BYMONTH were multivalued &nbsp;(ie: BYMONTH=3D10,11,12) =
then the=20
  occurrences would be scoped to the months of &nbsp;October thru =
December.=20
  &nbsp;If no other BYxxx rule parts were there then Id &nbsp;say that =
the rule=20
  would evaluate to "The last Sunday in December" but because =
&nbsp;other BYxxx=20
  modfiiers were involved this is not true.</FONT><FONT size=3D3>=20
  </FONT><BR><BR><FONT size=3D2>On the top of page 45 in 2445 there is =
an example=20
  of &nbsp;this that is pretty similar to Dans rule:</FONT><FONT =
size=3D3>=20
  </FONT><BR><BR><FONT size=3D2><TT>&nbsp; &nbsp;Here is an example of =
evaluating=20
  multiple BYxxx rule &nbsp;parts.</TT></FONT> <BR><BR><FONT =
size=3D2><TT>&nbsp;=20
  &nbsp; DTSTART;TZID=3DUS-Eastern:19970105T083000</TT></FONT> <BR><FONT =

  size=3D2><TT>&nbsp; &nbsp;&nbsp;=20
  =
RRULE:FREQ=3DYEARLY;INTERVAL=3D2;BYMONTH=3D1;BYDAY=3DSU;BYHOUR=3D8,9;</TT=
></FONT>=20
  <BR><FONT size=3D2><TT>&nbsp; &nbsp;&nbsp; =
&nbsp;BYMINUTE=3D30</TT></FONT>=20
  <BR><BR><FONT size=3D2><TT>&nbsp; First, the "INTERVAL=3D2" would be =
&nbsp;applied=20
  to "FREQ=3DYEARLY" to arrive</TT></FONT> <BR><FONT size=3D2><TT>&nbsp; =
at "every=20
  other year". Then, &nbsp;"BYMONTH=3D1" would be applied to =
arrive</TT></FONT>=20
  <BR><FONT size=3D2><TT>&nbsp; at "every January, every &nbsp;other =
year". Then,=20
  "BYDAY=3DSU" would be</TT></FONT> <BR><FONT size=3D2><TT>&nbsp; =
applied to arrive=20
  at "every &nbsp;Sunday in January, every other year".</TT></FONT> =
<BR><FONT=20
  size=3D2><TT>...</TT></FONT><FONT size=3D3> </FONT><BR><BR><FONT =
size=3D2>This=20
  evaluates just like I did for the &nbsp;BYDAY=3D-1SU;BYMONTH=3D10. =
&nbsp;It=20
  follows the same logic I used (or I should say &nbsp;that my logic =
followed it=20
  w/o actually seeing this @ first) by applying the &nbsp;cited bits of=20
  2445.</FONT><FONT size=3D3> </FONT><BR><BR><FONT size=3D2><TT>&gt; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; But this =

  just</TT></FONT> <BR><FONT size=3D2><TT>&gt; means that the quoted =
&nbsp;rule is=20
  vacuous, and its recurrence defines the empty</TT></FONT> <BR><FONT=20
  size=3D2><TT>&gt; set, except for &nbsp;its DTSTART. =
&nbsp;</TT></FONT><FONT=20
  size=3D3> </FONT><BR><BR><FONT size=3D2>I do not &nbsp;think so given =
that the=20
  evaluation of the rule matches the way that the &nbsp;multiple BYxxx =
parts are=20
  described to modify each other (and are not applyed &nbsp;in parallel) =
and=20
  that the example in 2445 seems to confirm this.</FONT><FONT size=3D3>=20
  &nbsp;</FONT> <BR><BR><FONT size=3D2>Bruce</FONT><FONT size=3D3> =
</FONT><BR><FONT=20
  =
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D</FONT>=20
  <BR><FONT size=3D2>Bruce &nbsp;Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
  &nbsp;INet: &nbsp;Bruce_Kahn@notesdev.ibm.com</FONT> <BR><FONT=20
  size=3D2>Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp;&nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; Phone: 978.399.6496</FONT> <BR><FONT size=3D2>IBM =
Software=20
  &nbsp;Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp;&nbsp; &nbsp; FAX: and nothing but the FAX...</FONT> =
<BR><FONT=20
  size=3D2>Standard disclaimers apply, &nbsp;even where prohibited by=20
  law...</FONT> <BR><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0031_01C34BE1.B6EB3AE0--



From owner-ietf-calendar@mail.imc.org  Thu Jul 17 14:11:31 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16131
	for <calsch-archive@lists.ietf.org>; Thu, 17 Jul 2003 14:11:31 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6HHrsqt012472
	for <ietf-calendar-bks@above.proper.com>; Thu, 17 Jul 2003 10:53:54 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6HHrsQO012471
	for ietf-calendar-bks; Thu, 17 Jul 2003 10:53:54 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6HHrqqt012465
	for <ietf-calendar@imc.org>; Thu, 17 Jul 2003 10:53:53 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6HHrpYa020426
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 17 Jul 2003 10:53:53 -0700
Message-ID: <3F16E2A9.3000200@Royer.com>
Date: Thu, 17 Jul 2003 11:53:45 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: BYDAY and YEARLY
References: <LNBBLMNOGOCILCNAGNONEEMACIAF.dhickman@rockinsoftware.com>
In-Reply-To: <LNBBLMNOGOCILCNAGNONEEMACIAF.dhickman@rockinsoftware.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060006090504020409090706"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060006090504020409090706
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Dan Hickman wrote:
> Any luck talking to the original authors.  I think we need to make a 
> ruling on this and get on down the road.

I agree that getting Derik's, Frank's, both Steve's, and Ross's input
is *extremely* valuable.

However I object to it being done off of this working group mailing list.
They put in a tremendous effort to produce RFC 2445 and 2446. The discussions
that produced those RFCs were a WG effort and not individual submissions.
In so far as typo's and what led you to put in this text in, and so on, their
input is needed. As far as what it should mean, I think that reading the
archives is more valuable.

> At this point, I feel it makes the most sense to conclude that 
> "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" means "The last Sunday in 
> October".

I also agree.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060006090504020409090706
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINRDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDIwOTE4MDAw
MDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD
EEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuOjEp298xKmKaSoPmY4WupTfjVMvob
cj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umSqlGIEwX6u2g2lfhJIG1nAYCAItpB
JXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzvq3gGiEg4kjV+KC+peZLB9YpiuEFx
3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvfvMcUKdzRub3F/GNvDgu6dd1Jq52t
VrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJJKkkZRaZAgMBAAGjggEGMIIBAjAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAo
oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9ttwSYnVsHPS1PcjLxGL5gSrWxN1G
VNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcUioomgeYc81cGfR1diWN7mnZNFuXZ
Ztb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJ
PKEwDQYJKoZIhvcNAQEEBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQwHhcNMDIwOTE4MDAwMDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD
VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixM
SUFCLkxURChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsT
KkRpZ2l0YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQK
RG91ZyBSb3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDEEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuO
jEp298xKmKaSoPmY4WupTfjVMvobcj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umS
qlGIEwX6u2g2lfhJIG1nAYCAItpBJXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzv
q3gGiEg4kjV+KC+peZLB9YpiuEFx3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvf
vMcUKdzRub3F/GNvDgu6dd1Jq52tVrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJ
JKkkZRaZAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG
+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIG
CCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhC
AQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xh
c3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9
ttwSYnVsHPS1PcjLxGL5gSrWxN1GVNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcU
ioomgeYc81cGfR1diWN7mnZNFuXZZtb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jGCBKowggSm
AgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ
QSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh
c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAe
jFNQR/pY9ailMryViTyhMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDcxNzE3NTM0NVowIwYJKoZIhvcNAQkEMRYEFAczfnRk
pl59VMbnnoDkKnw1QP/bMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEE
AYI3EAQxgeQwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEB6MU1BH+lj1qKUyvJWJPKEwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAejFNQR/pY9ailMryViTyhMA0G
CSqGSIb3DQEBAQUABIIBAAdMKcel7azmn/uoIN4JjOy5sXZMAnKHFQty4I1/y1HNzT2WxHkl
xLTRE1U0TFBsE4l7n0qu++6I2L2nKmnf9l8aJZukHdNCPrbG7aUqqP6mE4rCvB3dekMkztyV
U7E7VjvKlswt6fZS3vm6w8ekntYxRQPRbV2vw8hkuVokBas5CAnk9u0P4HgTHlnNyk2vHZ5u
2Ifd6eTImF8pFDwhFoDBqdxgR2XtZEgiAGH0ZT2aRTvBA3ixyCoxqqAddXC2KEt0G+zl51Ar
DKJbmiLWlIGHWljTVxolqWLJJp87pvhu4oPVkCgaSYJUnr3loge4RZKibOlKP2NBYJx7PPYp
hIIAAAAAAAA=
--------------ms060006090504020409090706--



From owner-ietf-calendar@mail.imc.org  Thu Jul 17 16:35:48 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21839
	for <calsch-archive@lists.ietf.org>; Thu, 17 Jul 2003 16:35:48 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6HKKMqt021538
	for <ietf-calendar-bks@above.proper.com>; Thu, 17 Jul 2003 13:20:22 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6HKKMVH021537
	for ietf-calendar-bks; Thu, 17 Jul 2003 13:20:22 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6HKKLqt021532
	for <ietf-calendar@imc.org>; Thu, 17 Jul 2003 13:20:21 -0700 (PDT)
	(envelope-from Robert_Ransdell@notesdev.ibm.com)
In-Reply-To: <3F16E2A9.3000200@Royer.com>
To: ietf-calendar@imc.org
Subject: Re: BYDAY and YEARLY
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V65_06232003 June 23, 2003
Message-ID: <OFB3750A1E.3C4A5CC5-ON85256D66.006FEAFC-85256D66.006F5FC2@notesdev.ibm.com>
From: Robert_Ransdell@notesdev.ibm.com
Date: Thu, 17 Jul 2003 16:20:20 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Build V602_05222003NP|May 22, 2003) at 07/17/2003
 04:19:59 PM,
	Serialize complete at 07/17/2003 04:19:59 PM
Content-Type: multipart/alternative; boundary="=_alternative 006F5FB985256D66_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 006F5FB985256D66_=
Content-Type: text/plain; charset="US-ASCII"

Just for the record.  I also agree 
> At this point, I feel it makes the most sense to conclude that 
> "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" means "The last Sunday in 
> October".

_____________________
Note: new email address

tom_ransdell@notesdev.ibm.com



Doug Royer <Doug@royer.com> 
Sent by: owner-ietf-calendar@mail.imc.org
07/17/2003 01:53 PM
Please respond to
ietf-calendar@imc.org


To
ietf-calendar@imc.org
cc

Subject
Re: BYDAY and YEARLY








Dan Hickman wrote:
> Any luck talking to the original authors.  I think we need to make a 
> ruling on this and get on down the road.

I agree that getting Derik's, Frank's, both Steve's, and Ross's input
is *extremely* valuable.

However I object to it being done off of this working group mailing list.
They put in a tremendous effort to produce RFC 2445 and 2446. The 
discussions
that produced those RFCs were a WG effort and not individual submissions.
In so far as typo's and what led you to put in this text in, and so on, 
their
input is needed. As far as what it should mean, I think that reading the
archives is more valuable.

> At this point, I feel it makes the most sense to conclude that 
> "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" means "The last Sunday in 
> October".

I also agree.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards


--=_alternative 006F5FB985256D66_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Just for the record. &nbsp;I also agree
</font>
<br><font size=2><tt>&gt; At this point, I feel it makes the most sense
to conclude that <br>
&gt; &quot;RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10&quot; means &quot;The
last Sunday in <br>
&gt; October&quot;.<br>
</tt></font>
<br><font size=2 face="sans-serif">_____________________<br>
Note: new email address<br>
<br>
tom_ransdell@notesdev.ibm.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Doug Royer &lt;Doug@royer.com&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/17/2003 01:53 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
ietf-calendar@imc.org</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">ietf-calendar@imc.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: BYDAY and YEARLY</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
Dan Hickman wrote:<br>
&gt; Any luck talking to the original authors. &nbsp;I think we need to
make a <br>
&gt; ruling on this and get on down the road.<br>
<br>
I agree that getting Derik's, Frank's, both Steve's, and Ross's input<br>
is *extremely* valuable.<br>
<br>
However I object to it being done off of this working group mailing list.<br>
They put in a tremendous effort to produce RFC 2445 and 2446. The discussions<br>
that produced those RFCs were a WG effort and not individual submissions.<br>
In so far as typo's and what led you to put in this text in, and so on,
their<br>
input is needed. As far as what it should mean, I think that reading the<br>
archives is more valuable.<br>
<br>
&gt; At this point, I feel it makes the most sense to conclude that <br>
&gt; &quot;RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10&quot; means &quot;The
last Sunday in <br>
&gt; October&quot;.<br>
<br>
I also agree.<br>
<br>
<br>
-- <br>
<br>
 &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
 &nbsp;-------------------------------|-----------------------------<br>
 &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; | Office: (208)612-INET<br>
 &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards
- You Need Standards<br>
</tt></font>
<br>
--=_alternative 006F5FB985256D66_=--


From owner-ietf-calendar@mail.imc.org  Fri Jul 18 02:11:15 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17086
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 02:11:14 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6I5xAqt046709
	for <ietf-calendar-bks@above.proper.com>; Thu, 17 Jul 2003 22:59:10 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6I5xAHW046708
	for ietf-calendar-bks; Thu, 17 Jul 2003 22:59:10 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6I5x8qt046697
	for <ietf-calendar@imc.org>; Thu, 17 Jul 2003 22:59:09 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
Subject: Re: BYDAY and YEARLY
To: ietf-calendar@imc.org
Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OF651E783F.4C493912-ON85256D67.0020B6E2-85256D67.0020CAA8@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Fri, 18 Jul 2003 01:58:55 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/18/2003 01:59:12 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



Doug, we are not getting input off the list.  We're asking that their
responses be put on the list - not off of it.  You should know by now that
I don't favor discussions off of the list - and never have.


                                                                                                                                           
                      Doug Royer                                                                                                           
                      <Doug@royer.com>             To:       ietf-calendar@imc.org                                                         
                      Sent by:                     cc:                                                                                     
                      owner-ietf-calendar@m        Subject:  Re: BYDAY and YEARLY                                                          
                      ail.imc.org                                                                                                          
                                                                                                                                           
                                                                                                                                           
                      07/17/2003 01:53 PM                                                                                                  
                      Please respond to                                                                                                    
                      ietf-calendar                                                                                                        
                                                                                                                                           
                                                                                                                                           






Dan Hickman wrote:
> Any luck talking to the original authors.  I think we need to make a
> ruling on this and get on down the road.

I agree that getting Derik's, Frank's, both Steve's, and Ross's input
is *extremely* valuable.

However I object to it being done off of this working group mailing list.
They put in a tremendous effort to produce RFC 2445 and 2446. The
discussions
that produced those RFCs were a WG effort and not individual submissions.
In so far as typo's and what led you to put in this text in, and so on,
their
input is needed. As far as what it should mean, I think that reading the
archives is more valuable.

> At this point, I feel it makes the most sense to conclude that
> "RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" means "The last Sunday in
> October".

I also agree.


--

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards







From owner-ietf-calendar@mail.imc.org  Fri Jul 18 02:11:15 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17089
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 02:11:14 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6I60Oqt046815
	for <ietf-calendar-bks@above.proper.com>; Thu, 17 Jul 2003 23:00:24 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6I60Oi7046814
	for ietf-calendar-bks; Thu, 17 Jul 2003 23:00:24 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6I60Lqt046801
	for <ietf-calendar@imc.org>; Thu, 17 Jul 2003 23:00:21 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
Subject: RE: BYDAY and YEARLY
To: "Dan Hickman" <dhickman@rockinsoftware.com>
Cc: Bruce_Kahn@notesdev.ibm.com, ietf-calendar@imc.org,
        "Jonathan Lennox" <lennox@cs.columbia.edu>,
        owner-ietf-calendar@mail.imc.org
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFCA401170.48895BEA-ON85256D67.0020D5D8-85256D67.0020E791@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Fri, 18 Jul 2003 02:00:09 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/18/2003 02:00:24 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id h6I60Nqt046805
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit



Dan, I asked Frank to post his comments on the list.  I know he's been out
of the country.  I'll try to nudge him.  He chatted with the other author
so they could formulate a reply for the list.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


                                                                                                                                        
                      "Dan Hickman"                                                                                                     
                      <dhickman@rockinso        To:       <pregen@egenconsulting.com>                                                   
                      ftware.com>               cc:       <Bruce_Kahn@notesdev.ibm.com>, <ietf-calendar@imc.org>, "Jonathan Lennox"     
                                                 <lennox@cs.columbia.edu>, <owner-ietf-calendar@mail.imc.org>                           
                      07/16/2003 10:32          Subject:  RE: BYDAY and YEARLY                                                          
                      PM                                                                                                                
                                                                                                                                        
                                                                                                                                        





Any  luck talking to the original authors.  I think we need to make a
ruling on  this and get on down the road.

At  this point, I feel it makes the most sense to conclude that
"RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" means "The last Sunday in
October".

Regards,
Dan  Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com

-----Original Message-----
From:  owner-ietf-calendar@mail.imc.org
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of
pregen@egenconsulting.com
Sent: Tuesday, July 08, 2003 9:49  PM
To: Dan Hickman
Cc: Bruce_Kahn@notesdev.ibm.com;  ietf-calendar@imc.org; Jonathan Lennox;
owner-ietf-calendar@mail.imc.org
Subject: RE: BYDAY and  YEARLY



We are in dialog  with the original authors - maybe we can try to get some
sort of ruling on  what they think this should be.  And if it's wrong, we
need to get it  fixed.  We need to make some adjustments to the RFC's
anyway because of  findings from interop testing.
___________________
Patricia Egen  Consulting
www.egenconsulting.com
423-875-2652


                                                                          
      "Dan Hickman"                                                       
      <dhickman@rockinsoftwa                To:                           
      re.com>                       <Bruce_Kahn@notesdev.ibm.com>,        
      Sent by:                      "Jonathan Lennox"                     
      owner-ietf-calendar@ma        <lennox@cs.columbia.edu>              
      il.imc.org                            cc:                           
                                    <ietf-calendar@imc.org>               
      07/08/2003 20:37                      Subject:         RE: BYDAY    
                                    and  YEARLY                           
                                                                          






The one  thing that is obvious given the repeated conversations  on this
topic is  that the specification of BYDAY on YEARLY is ambiguous in the
RFC. I see  both sides asvalid  interpretations. I suppose the real
question is what  was the original intention  of the author(s)?

Given the following:
1.  umerous VTIMEZONE  examples in the RFC use
"RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10" to mean   "The last Sunday in
October", making it a big statement to say that  these  are not valid.
2.There are a number of   implementations that already work this way now.
3.Rules like "The 5th Monday of the year but  only in February"  are
probably not that useful.

it appears there is  much less impact if we go ahead and consider
"FREQ=YEARLY;BYMONTH=2;BYDAY=5MO" to mean the "5th Monday in   February". I
suggest we accept this  interpretation.

Too bad I picked the wrong  interpretation to  implement :-|

Regards,
Dan  Hickman
Rockin' Software
dhickman@rockinsoftware.com
http://www.rockinsoftware.com
-----Original Message-----
From:   owner-ietf-calendar@mail.imc.org
[mailto:owner-ietf-calendar@mail.imc.org]On Behalf Of
Bruce_Kahn@notesdev.ibm.com
Sent:  Tuesday, July 08, 2003 2:07  PM
To:  Jonathan Lennox
Cc:   ietf-calendar@imc.org
Subject: Re: BYDAY  and  YEARLY



Jonathan wrote on  07/08/2003  11:35:11 AM:
> I agree  with this so far, but in your next step  (concluding that this
means
> "the last Sunday in October") you  make an  unwarranted leap.  The
definition
> of the integer parts of BYDAY  says, as you quoted  previously:
>
> >    Each BYDAY  value can also be preceded  by a positive (+n) or
negative
> >      (-n) integer. If present, this indicates the nth occurrence  of
the
> >    specific  day within the MONTHLY or YEARLY RRULE.
>
> Thus, since this is a  YEARLY RRULE, the phrase "Last Sunday"  means
"Last
> Sunday of the Year", not "Last Sunday of the Month."    The presence of a
> BYMONTH  rule doesn't affect this; by the spec,  the integer part of
BYDAY
> depends *only* on the   FREQ.

The assumption about  BYDAY  would be accurate without other BYxxx
modifiers present.  When I   read:

    If multiple BYxxx rule  parts are specified, then after evaluating  the
  specified FREQ and  INTERVAL  rule parts, the BYxxx rule parts are
   applied to the current  set of evaluated occurrences in the  following
  order:

I take the phrase "applied to the  current  set of evaluated occurrences"
to be that BYDAY works on the  modified  occurrences generated by applying
the BYMONTH first.  This  BYxxx modifier  scopes the instance set to the
month of October rather  than the entire year.

If BYMONTH were multivalued  (ie: BYMONTH=10,11,12) then the  occurrences
would be scoped to the months of  October thru December.   If no other
BYxxx rule parts were there then Id  say that the rule  would evaluate to
"The last Sunday in December" but because  other BYxxx  modfiiers were
involved this is not true.

On the top of page 45 in 2445 there is an example  of  this that is pretty
similar to Dans rule:

   Here is an example of evaluating  multiple BYxxx rule  parts.

     DTSTART;TZID=US-Eastern:19970105T083000
      RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
      BYMINUTE=30

  First, the "INTERVAL=2" would be  applied  to "FREQ=YEARLY" to arrive
  at "every  other year". Then,  "BYMONTH=1" would be applied to arrive
  at "every January, every  other year". Then,  "BYDAY=SU" would be
  applied to arrive  at "every  Sunday in January, every other year".
...

This  evaluates just like I did for the  BYDAY=-1SU;BYMONTH=10.  It
follows the same logic I used (or I should say  that my logic followed it
w/o actually seeing this @ first) by applying the  cited bits of  2445.

>                                                                   But
this  just
> means that the quoted  rule is  vacuous, and its recurrence defines the
empty
> set, except for  its DTSTART.

I do not  think so given that the  evaluation of the rule matches the way
that the  multiple BYxxx parts are  described to modify each other (and are
not applyed  in parallel) and  that the example in 2445 seems to confirm
this.

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...









From owner-ietf-calendar@mail.imc.org  Fri Jul 18 14:15:39 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07135
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 14:15:38 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6IHwIqt012099
	for <ietf-calendar-bks@above.proper.com>; Fri, 18 Jul 2003 10:58:18 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6IHwIw2012098
	for ietf-calendar-bks; Fri, 18 Jul 2003 10:58:18 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6IHwHqt012087
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 10:58:17 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6IHwGYa030831
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 10:58:17 -0700
Message-ID: <3F183532.5010908@Royer.com>
Date: Fri, 18 Jul 2003 11:58:10 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: BYDAY and YEARLY
References: <OF651E783F.4C493912-ON85256D67.0020B6E2-85256D67.0020CAA8@egenconsulting.com>
In-Reply-To: <OF651E783F.4C493912-ON85256D67.0020B6E2-85256D67.0020CAA8@egenconsulting.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020207070202040608060009"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020207070202040608060009
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



pregen@egenconsulting.com wrote:
> 
> Doug, we are not getting input off the list.  We're asking that their
> responses be put on the list - not off of it.  You should know by now that
> I don't favor discussions off of the list - and never have.

Thank you. I really did know that and I do and have believed you felt
that way and have promoted that everything is on the list. It just
appeared to me as if for convenience and *not* for subversion that
it may had happened.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020207070202040608060009
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINRDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDIwOTE4MDAw
MDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD
EEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuOjEp298xKmKaSoPmY4WupTfjVMvob
cj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umSqlGIEwX6u2g2lfhJIG1nAYCAItpB
JXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzvq3gGiEg4kjV+KC+peZLB9YpiuEFx
3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvfvMcUKdzRub3F/GNvDgu6dd1Jq52t
VrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJJKkkZRaZAgMBAAGjggEGMIIBAjAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAo
oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9ttwSYnVsHPS1PcjLxGL5gSrWxN1G
VNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcUioomgeYc81cGfR1diWN7mnZNFuXZ
Ztb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJ
PKEwDQYJKoZIhvcNAQEEBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQwHhcNMDIwOTE4MDAwMDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD
VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixM
SUFCLkxURChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsT
KkRpZ2l0YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQK
RG91ZyBSb3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDEEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuO
jEp298xKmKaSoPmY4WupTfjVMvobcj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umS
qlGIEwX6u2g2lfhJIG1nAYCAItpBJXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzv
q3gGiEg4kjV+KC+peZLB9YpiuEFx3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvf
vMcUKdzRub3F/GNvDgu6dd1Jq52tVrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJ
JKkkZRaZAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG
+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIG
CCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhC
AQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xh
c3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9
ttwSYnVsHPS1PcjLxGL5gSrWxN1GVNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcU
ioomgeYc81cGfR1diWN7mnZNFuXZZtb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jGCBKowggSm
AgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ
QSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh
c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAe
jFNQR/pY9ailMryViTyhMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDcxODE3NTgxMFowIwYJKoZIhvcNAQkEMRYEFMmW+ML5
5mocjUUfdG/fdpjZy/AzMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEE
AYI3EAQxgeQwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEB6MU1BH+lj1qKUyvJWJPKEwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAejFNQR/pY9ailMryViTyhMA0G
CSqGSIb3DQEBAQUABIIBABRVME43+bXfObQ/j+HBDpX+9tblfmo7GHbw8qlKtWN0f7Cgg1nL
+2vuK186PS8NBCkSayKwB2wj80CGK24DT/LtDqRMll1olvQ3SKJOlx54/HGoxfIWh2eUala4
2tJr2gAzg6zNXakwemkfoHktb4OVcwKFFvt6Inr9a/alXOlOcf0ustTbwqheUhblK8P2k/jW
mg108ag5kc0iXLK3u1+8PKcXFCQQgq/SD5+pwFmzCMUr6rHVmqG6Dx8zwKC0u5gpSgNxDJ3u
OBWfl+ErqCp1Ub4q00ZDpW8urpq7w9Z945YsDiXnE5wBP5pI1IjwNrOliwu008JfXjujb2Um
hPoAAAAAAAA=
--------------ms020207070202040608060009--



From owner-ietf-calendar@mail.imc.org  Fri Jul 18 14:27:19 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07428
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 14:27:18 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6II9kqt012611
	for <ietf-calendar-bks@above.proper.com>; Fri, 18 Jul 2003 11:09:46 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6II9k1p012610
	for ietf-calendar-bks; Fri, 18 Jul 2003 11:09:46 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6II9iqt012600
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 11:09:44 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
Subject: Re: BYDAY and YEARLY
To: ietf-calendar@imc.org
Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFDA736E64.F584F97B-ON85256D67.0063A9F9-85256D67.0063AD15@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Fri, 18 Jul 2003 14:09:43 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/18/2003 02:09:46 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



Cool.  8-)
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652


                                                                                                                                           
                      Doug Royer                                                                                                           
                      <Doug@royer.com>             To:       ietf-calendar@imc.org                                                         
                      Sent by:                     cc:                                                                                     
                      owner-ietf-calendar@m        Subject:  Re: BYDAY and YEARLY                                                          
                      ail.imc.org                                                                                                          
                                                                                                                                           
                                                                                                                                           
                      07/18/2003 01:58 PM                                                                                                  
                      Please respond to                                                                                                    
                      ietf-calendar                                                                                                        
                                                                                                                                           
                                                                                                                                           






pregen@egenconsulting.com wrote:
>
> Doug, we are not getting input off the list.  We're asking that their
> responses be put on the list - not off of it.  You should know by now
that
> I don't favor discussions off of the list - and never have.

Thank you. I really did know that and I do and have believed you felt
that way and have promoted that everything is on the list. It just
appeared to me as if for convenience and *not* for subversion that
it may had happened.

--

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards







From owner-ietf-calendar@mail.imc.org  Fri Jul 18 18:22:26 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16318
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 18:22:26 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6IM1fqt028507
	for <ietf-calendar-bks@above.proper.com>; Fri, 18 Jul 2003 15:01:41 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6IM1fKN028506
	for ietf-calendar-bks; Fri, 18 Jul 2003 15:01:41 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6IM1eqt028501
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 15:01:40 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Fri, 18 Jul 2003 16:00:20 -0600
Message-Id: <sf181994.076@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Fri, 18 Jul 2003 15:02:30 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Cap Free-Busy Request
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part59077376.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__Part59077376.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

A discussion was started on Mar 31, 2003, regarding how a CUA can
request free-busy information using CAP.  It was noted that the CAP spec
promised to "specify how to search for available busy time information"
but there was nothing in the spec that described how to do this.  While
several ideas were discussed the key issue was not resolved.  Toward the
end of the discussion Pat Egen called for proposals, with text, to
resolve the issue.  So far, none have been presented. I wish to make a
proposal for requesting free-busy information via CAP.   From the
abovementioned discussion there seemed to be agreement on some issues:- 
The request should be simple: just specify targets and period of
interest.-  The request should be unambiguous.-  The CS should reply to
the request with the free-busy information (i.e. respond in real-time).-
 To respond in real-time, the CS should
retrieve/compose/generate/formulate/synthesize (or whatever it needs to
do) to provide the free-busy information. With this in mind, my proposal
for a CAP free-busy request is to use the SEARCH command with a
VFREEBUSY object.  The following is an example: C: BEGIN:VCALENDARC:
VERSION:2.0C: PRODID:-//Someone's ProdidC: CMD;ID=FB001:SEARCHC:
TARGET:UserAC: TARGET:UserBC: BEGIN:VFREEBUSYC:
DTSTART:20030804T080000ZC: DTEND:20030808T170000ZC: END:VFREEBUSYC:
END:VCALENDAR Upon receiving this command a Calendar Store (CS) will
compose a response for each TARGET.  A sample response to the above
request would be:  S: BEGIN:VCALENDARS: VERSION:2.0S: PRODID:-//Some
Calendar StoreS: CMD;ID=FB001:REPLYS: TARGET:UserAS: BEGIN:VREPLYS:
BEGIN:VFREEBUSYS: DTSTART:20030804T080000ZS: DTEND:20030808T170000ZS:
DTSTAMP:20030710T131103ZS: FREEBUSY:20030805T100000Z/20030805T110000ZS:
FREEBUSY:20030805T140000Z/20030805T150000ZS: END:VFREEBUSYS:
END:VREPLYS: END:VCALENDAR S: BEGIN:VCALENDARS: VERSION:2.0S:
PRODID:-//Some Calendar StoreS: CMD;ID=FB001:REPLYS: TARGET:UserBS:
BEGIN:VREPLYS: BEGIN:VFREEBUSYS: DTSTART:20030804T080000ZS:
DTEND:20030808T170000ZS: DTSTAMP:20030710T131103ZS:
FREEBUSY:20030806T130000Z/20030805T150000ZS: END:VFREEBUSYS:
END:VREPLYS: END:VCALENDAR This proposal has several advantages:-  It is
simple and straightforward.  No ambiguity about the request.-  It is
'natural' and 'familiar' because it uses an already defined, well
understood object (VFREEBUSY) of which one purpose is "to describe a
request for free/busy time" (RFC 2445, p. 58).  We aren't reinventing or
proposing something new or radically different.-  It is similar to an
iTIP free-busy request which also uses VFREEBUSY.  This creates
uniformity and consistency between CAP and iTIP for requesting free-busy
information.  This is somewhat important and advantageous.  Implementers
will expect that a free-busy request, whether sent via iMIP/iTIP,
CAP/iTIP, or CAP real-time, will result in the same data being returned!
 Using a similar scheme for requesting free-busy information is a step
toward uniformity.  In addition, this will facilitate and simplify
implementations that already have code to handle iTIP free-busy requests
by allowing re-use of that code for CAP free-busy requests.-  It
accommodates a free-busy request/response regardless of how (or whether)
a Calendar Store supports VFREEBUSY as an AGENDA component (i.e. whether
or not VFREEBUSY is listed on the COMPONENTS property in response to
GET-CAPABILITIES).  Calendar Stores that support the VFREEBUSY component
can create a response from them.  Calendar Stores that do not support
the VFREEBUSY component can compose a response from VEVENTs and/or other
vender specific data related to free-busy time.  CUAs are insulated from
the specifics of how a Calendar Store internally represents free-busy
information. The ABNF to accommodate this proposal simply adds
"freebusyc" to the "search-comp" definition.  The ABNF for
"search-comp" was not in the most recent draft (this was noted by B
Kahn  on 6/14/2003 and acknowledged by D Royer on 6/19/2003.)  The
following is the presumed ABNF for "search-comp" that includes
"freebusyc".  It would appear in section "10.8 SEARCH Command"   
ABNF for a "SEARCH" object is:    search-object = "BEGIN" ":"
"VCALENDAR" CRLF                 ;                 ; calprops MUST
include 'search-cmd'                 ;                   calprops       
           other-props                   1*(search-comp)                
  "END" ":" "VCALENDAR" CRLF    search-comp   = queryc / freebusyc      
            / iana-comp / x-component    freebusyc     = "BEGIN" ":"
"VFREEBUSY" CRLF                 ;                  ; The following MUST
occur exactly once.                 ;                   / dtstart       
           / dtend                 ;                 ; The following are
optional,                 ; but MUST NOT occur more than once.          
      ;                   / dtstamp                   / uid             
   ;                 ; The following are optional,                 ; and
MAY occur more than once.                 ;                   /
other-props                    "END" ":" "VFREEBUSY" CRLF I look forward
to response and feedback regarding this proposal. --C Johnson

--=__Part59077376.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">A discussion&nbsp;was started&nbsp;on <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:date Month="3" Day="31" Year="2003">Mar 31, 2003</st1:date>, regarding how a CUA can request free-busy information using CAP.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>It was noted that the CAP spec promised to “specify how to search for available busy time information” but there was nothing in the spec that described how to do this.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>While several ideas were discussed the key issue was not resolved.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>Toward the end of the discussion Pat Egen called for proposals, with text, to resolve the issue.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>So far, none have been presented.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>&nbsp;</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">I wish to make a proposal for requesting free-busy information via CAP.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p>&nbsp;</o:p></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">From the abovementioned discussion there seemed to be agreement on some issues:</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>The request should be simple: just specify targets and period of interest.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>The request should be unambiguous.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>The CS should reply&nbsp;to the request with the free-busy information (i.e. respond in real-time).</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>To respond in real-time, the CS should retrieve/compose/generate/formulate/synthesize (or whatever it needs to do) to provide&nbsp;the free-busy information.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p>&nbsp;</o:p></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">With this in mind, my proposal for a CAP free-busy request is to use the SEARCH command with a VFREEBUSY object.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>The following is an example:</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p><FONT face="Times New Roman">&nbsp;</FONT></o:p></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: BEGIN:VCALENDAR<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: VERSION:2.0<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: PRODID:-//Someone’s Prodid<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: CMD;ID=FB001:SEARCH<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: TARGET:UserA<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: TARGET:UserB<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: BEGIN:VFREEBUSY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN lang=NL style="FONT-FAMILY: 'Courier New'; mso-ansi-language: NL"><FONT face=Terminal>C: DTSTART:20030804T080000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN lang=NL style="FONT-FAMILY: 'Courier New'; mso-ansi-language: NL"><FONT face=Terminal>C: DTEND:20030808T170000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: END:VFREEBUSY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>C: END:VCALENDAR<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">Upon receiving this command a Calendar Store (CS) will compose a response for each TARGET.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>A sample response to the above request would be: </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: BEGIN:VCALENDAR<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: VERSION:2.0<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: PRODID:-//Some Calendar Store<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: CMD;ID=FB001:REPLY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: TARGET:UserA<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: BEGIN:VREPLY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: BEGIN:VFREEBUSY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: DTSTART:20030804T080000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: DTEND:20030808T170000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: DTSTAMP:20030710T131103Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: FREEBUSY:20030805T100000Z/20030805T110000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: FREEBUSY:20030805T140000Z/20030805T150000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: END:VFREEBUSY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: END:VREPLY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: END:VCALENDAR<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><o:p><FONT face=Terminal>&nbsp;</FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: BEGIN:VCALENDAR<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: VERSION:2.0<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: PRODID:-//Some Calendar Store<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: CMD;ID=FB001:REPLY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: TARGET:UserB<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: BEGIN:VREPLY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: BEGIN:VFREEBUSY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: DTSTART:20030804T080000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: DTEND:20030808T170000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: DTSTAMP:20030710T131103Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: FREEBUSY:20030806T130000Z/20030805T150000Z<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: END:VFREEBUSY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: END:VREPLY<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>S: END:VCALENDAR<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p><FONT face="Times New Roman">&nbsp;</FONT></o:p></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">This proposal has several advantages:</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>It is simple and straightforward.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>No ambiguity about the request.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>It is ‘natural’ and ‘familiar’ because it uses an already defined, well understood object (VFREEBUSY) of which one purpose is “<FONT face=Tahoma><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>to describe a request for free/busy time</FONT></SPAN>” (RFC 2445, p. 58). <SPAN style="mso-spacerun: yes">&nbsp;</SPAN>We aren’t reinventing or proposing something new or radically different.</FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>It is similar to an iTIP free-busy request which also uses VFREEBUSY.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>This creates uniformity and consistency between CAP and iTIP for requesting free-busy information.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>This is somewhat important and advantageous.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>Implementers will expect that a free-busy request, whether sent via iMIP/iTIP, CAP/iTIP, or CAP real-time, will result in the same data being returned!<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>Using a similar scheme for requesting free-busy information is a step toward uniformity.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>In addition, this will facilitate and simplify implementation!
 s that already have code to handle iTIP free-busy requests by allowing re-use of that code for CAP free-busy requests.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style="mso-list: Ignore">-<SPAN style="FONT: 7pt 'Times New Roman'"><FONT face=Tahoma>&nbsp;&nbsp;</FONT></SPAN></SPAN>It accommodates a free-busy request/response regardless of how (or whether) a Calendar Store supports VFREEBUSY as an AGENDA component (i.e. whether or not VFREEBUSY is listed on the COMPONENTS property in response to GET-CAPABILITIES).<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>Calendar Stores that support the VFREEBUSY component can create a response from them.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>Calendar Stores that do not support the VFREEBUSY component can compose a response from VEVENTs and/or other vender specific data related to free-busy time.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>CUAs are insulated from the&nbsp;specifics of how a Calendar Store internally represents free-busy information.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p>&nbsp;</o:p></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">The ABNF to accommodate this proposal simply adds “freebusyc” to the “search-comp” definition.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>The ABNF for “search-comp” was not in the most recent draft (this was noted by B Kahn <SPAN style="mso-spacerun: yes">&nbsp;</SPAN>on <st1:date Month="6" Day="14" Year="2003">6/14/2003</st1:date> and acknowledged by D Royer on <st1:date Month="6" Day="19" Year="2003">6/19/2003</st1:date>.)<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>The following is the presumed ABNF for “search-comp” that includes “freebusyc”.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>It would appear in section “10.8 SEARCH Command”</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p><FONT face="Times New Roman">&nbsp;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>ABNF for a "SEARCH" object is:<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>search-object = "BEGIN" ":" "VCALENDAR" CRLF<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>;<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><SPAN style="mso-spacerun: yes">&nbsp;</SPAN>; calprops MUST include 'search-cmd'<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>;<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>calprops<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>other-props<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>1*(search-comp)<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>"END" ":" "VCALENDAR" CRLF<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>search-comp <SPAN style="mso-spacerun: yes">&nbsp;</SPAN><SPAN style="mso-spacerun: yes">&nbsp;</SPAN>= queryc / freebusyc<o:p></o:p></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><SPAN style="mso-spacerun: yes">&nbsp;</SPAN>/ iana-comp / x-component</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>freebusyc<SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>= "BEGIN" ":" "VFREEBUSY" CRLF</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;&nbsp;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;</SPAN><SPAN style="mso-spacerun: yes">&nbsp;</SPAN>; The following MUST occur exactly once.</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>/ dtstart</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>/ dtend</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>; The following are optional,</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>; but MUST NOT occur more than once.</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>/ dtstamp</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>/ uid</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>; The following are optional,</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>; and MAY occur more than once.</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>/ other-props</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><o:p><FONT face=Terminal>&nbsp;</FONT></o:p></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT face=Terminal><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>"END" ":" "VFREEBUSY" CRLF</FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt">&nbsp;</P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt">I look forward to response and feedback regarding this proposal.</P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt">&nbsp;</P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt">--C Johnson</P></BODY></HTML>
--=__Part59077376.0__=--


From owner-ietf-calendar@mail.imc.org  Fri Jul 18 19:23:47 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17818
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 19:23:46 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6IN9aqt030673
	for <ietf-calendar-bks@above.proper.com>; Fri, 18 Jul 2003 16:09:36 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6IN9aK3030671
	for ietf-calendar-bks; Fri, 18 Jul 2003 16:09:36 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6IN9Yqt030666
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 16:09:35 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6IN9XYa000844
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 16:09:35 -0700
Message-ID: <3F187E28.1070607@Royer.com>
Date: Fri, 18 Jul 2003 17:09:28 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: undisclosed-recipients:;
Subject: Re: Cap Free-Busy Request - vs QUERY?
References: <sf181994.076@gw.provo.novell.com>
In-Reply-To: <sf181994.076@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010409030605000601020501"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms010409030605000601020501
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable



Craig Johnson wrote:

> This proposal has several advantages:
>=20
> -  It is simple and straightforward.  No ambiguity about the request.
>=20
> -  It is =91natural=92 and =91familiar=92 because it uses an already de=
fined,=20
> well understood object (VFREEBUSY) of which one purpose is =93to descri=
be=20
> a request for free/busy time=94 (RFC 2445, p. 58).  We aren=92t reinven=
ting=20
> or proposing something new or radically different.

Would you want to disallow:

C: BEGIN:VCALENDAR
C: VERSION:2.0
C: PRODID:-//Someone=92s Prodid
C: CMD;ID=3DFB001:SEARCH
C: TARGET:CalA
C: TARGET:CalB
C: BEGIN:VQUERY
C: QUERY:SELECT DTSTART,DTEND,FREEBUSY FROM VFREEBUSY
C:  WHERE DTEND >=3D ''20030808T170000Z
C:  AND DTSTART <=3D '20030804T080000Z'
C: END:VQUERY

--=20

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms010409030605000601020501
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINRDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDIwOTE4MDAw
MDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD
EEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuOjEp298xKmKaSoPmY4WupTfjVMvob
cj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umSqlGIEwX6u2g2lfhJIG1nAYCAItpB
JXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzvq3gGiEg4kjV+KC+peZLB9YpiuEFx
3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvfvMcUKdzRub3F/GNvDgu6dd1Jq52t
VrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJJKkkZRaZAgMBAAGjggEGMIIBAjAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAo
oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9ttwSYnVsHPS1PcjLxGL5gSrWxN1G
VNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcUioomgeYc81cGfR1diWN7mnZNFuXZ
Ztb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJ
PKEwDQYJKoZIhvcNAQEEBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQwHhcNMDIwOTE4MDAwMDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD
VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixM
SUFCLkxURChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsT
KkRpZ2l0YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQK
RG91ZyBSb3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDEEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuO
jEp298xKmKaSoPmY4WupTfjVMvobcj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umS
qlGIEwX6u2g2lfhJIG1nAYCAItpBJXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzv
q3gGiEg4kjV+KC+peZLB9YpiuEFx3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvf
vMcUKdzRub3F/GNvDgu6dd1Jq52tVrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJ
JKkkZRaZAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG
+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIG
CCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhC
AQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xh
c3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9
ttwSYnVsHPS1PcjLxGL5gSrWxN1GVNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcU
ioomgeYc81cGfR1diWN7mnZNFuXZZtb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jGCBKowggSm
AgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ
QSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh
c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAe
jFNQR/pY9ailMryViTyhMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDcxODIzMDkyOFowIwYJKoZIhvcNAQkEMRYEFJgcWGXO
uuuASjOV7pBNDWNA4RHYMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEE
AYI3EAQxgeQwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEB6MU1BH+lj1qKUyvJWJPKEwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAejFNQR/pY9ailMryViTyhMA0G
CSqGSIb3DQEBAQUABIIBAG2hYHSrT+DLnTZmMC21mGv8CWHjHICOepOzTsYEIqgwq+TibZv4
jttsQhBGtIsMho2yeC8nbaqBmeXkG2NuT/i0cU06m5wVQJgPBZ9z72CueZpjt/Oi6bSlsZWW
wfJG7qTnvKmn8INRVO/1VTjREjD+hRKqOd0xQO41O1OwvBQ8GqcNGpXVFFsXrxiYo/OEY3H4
RblT0lMD0NenuzghCYY4LeI+q67ONV3BWEQPE94UpeGyhtEelHYMqxd96P5y5EvtuY85wUuM
9dJDHedtIjymSqK3AujsUVrEOuh8YA8Z4ixHR1gHN8EpuedYQWMxej0j2/6/Dn6f7nGxqX9X
WWoAAAAAAAA=
--------------ms010409030605000601020501--



From owner-ietf-calendar@mail.imc.org  Fri Jul 18 19:27:09 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17859
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 19:27:08 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6INFjqt030921
	for <ietf-calendar-bks@above.proper.com>; Fri, 18 Jul 2003 16:15:46 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6INFjXQ030920
	for ietf-calendar-bks; Fri, 18 Jul 2003 16:15:45 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6INFiqt030915
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 16:15:44 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6INFiYa000906
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 16:15:45 -0700
Message-ID: <3F187F9A.6010000@Royer.com>
Date: Fri, 18 Jul 2003 17:15:38 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request - UPN vs CALID?
References: <sf181994.076@gw.provo.novell.com>
In-Reply-To: <sf181994.076@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020001040307060505030705"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020001040307060505030705
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable



Craig Johnson wrote:

> With this in mind, my proposal for a CAP free-busy request is to
> use the SEARCH command with a VFREEBUSY object.  The following is an ex=
ample:
> =20
>=20
> C: BEGIN:VCALENDAR
> C: VERSION:2.0
> C: PRODID:-//Someone=92s Prodid
> C: CMD;ID=3DFB001:SEARCH
> C: TARGET:UserA
> C: TARGET:UserB

Above you use 'UserA' and 'UserB', did your proposal also
imply that you can do a search based on a UPN across CALIDs?
Or are those still CALID's that just happen to be named 'User'X ?

AND THANK YOU VERY MUCH FOR PROPOSING A SOLUTION. Without specific
proposals, 'I' end up adding and making up the solution and it
makes it SO MUCH easier when others provide solutions!!!

--=20

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020001040307060505030705
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINRDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDIwOTE4MDAw
MDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD
EEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuOjEp298xKmKaSoPmY4WupTfjVMvob
cj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umSqlGIEwX6u2g2lfhJIG1nAYCAItpB
JXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzvq3gGiEg4kjV+KC+peZLB9YpiuEFx
3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvfvMcUKdzRub3F/GNvDgu6dd1Jq52t
VrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJJKkkZRaZAgMBAAGjggEGMIIBAjAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAo
oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9ttwSYnVsHPS1PcjLxGL5gSrWxN1G
VNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcUioomgeYc81cGfR1diWN7mnZNFuXZ
Ztb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJ
PKEwDQYJKoZIhvcNAQEEBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQwHhcNMDIwOTE4MDAwMDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD
VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixM
SUFCLkxURChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsT
KkRpZ2l0YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQK
RG91ZyBSb3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDEEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuO
jEp298xKmKaSoPmY4WupTfjVMvobcj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umS
qlGIEwX6u2g2lfhJIG1nAYCAItpBJXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzv
q3gGiEg4kjV+KC+peZLB9YpiuEFx3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvf
vMcUKdzRub3F/GNvDgu6dd1Jq52tVrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJ
JKkkZRaZAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG
+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIG
CCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhC
AQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xh
c3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9
ttwSYnVsHPS1PcjLxGL5gSrWxN1GVNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcU
ioomgeYc81cGfR1diWN7mnZNFuXZZtb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jGCBKowggSm
AgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ
QSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh
c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAe
jFNQR/pY9ailMryViTyhMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDcxODIzMTUzOFowIwYJKoZIhvcNAQkEMRYEFHTLpunu
b4lWemL01HwFJrGAUuujMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEE
AYI3EAQxgeQwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEB6MU1BH+lj1qKUyvJWJPKEwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAejFNQR/pY9ailMryViTyhMA0G
CSqGSIb3DQEBAQUABIIBAE1xRry6PLSYE0EiV3OZu3nS6Ftb0dqdb9coCMBvhlL9N+Y/ozNE
ib3y/IZ+fazKcnLgob49h30t/KtWzEMaFJadad/4Bw+V2bdNoztZT7svx8D/uWM2NObMbD8F
w8oAhAOd1/fy3D390Wn5oZqZsx0TcH8vEDQOky0R0hEB2pqKkhECAMTmbFcRnnttyUQZlBH8
Ygwl1NPGWdVQLhVKgsTznV4RP0nZPsAlEBdL5e3WPZESfGrIPyl2HCm4iW5ym30rluIM2Bwg
bEGYbVORITDoe4x/yPQq515Jl0zwFXHrKawZUUMWGB7mFXiqLnCcrOBqvxm8n4TUTWV8Tl9r
flMAAAAAAAA=
--------------ms020001040307060505030705--



From owner-ietf-calendar@mail.imc.org  Fri Jul 18 19:55:25 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18286
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 19:55:25 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6INgpqt031439
	for <ietf-calendar-bks@above.proper.com>; Fri, 18 Jul 2003 16:42:51 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6INgpoo031438
	for ietf-calendar-bks; Fri, 18 Jul 2003 16:42:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6INgoqt031433
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 16:42:50 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6INgoYa001094
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 16:42:51 -0700
Message-ID: <3F1885F4.4090902@Royer.com>
Date: Fri, 18 Jul 2003 17:42:44 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request - vs QUERY?
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010200060108030801000303"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms010200060108030801000303
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable


[I think I mis-emailed this one - it may be a duplicate]

Craig Johnson wrote:

> This proposal has several advantages:
>=20
> -  It is simple and straightforward.  No ambiguity about the request.
>=20
> -  It is =91natural=92 and =91familiar=92 because it uses an already de=
fined,=20
> well understood object (VFREEBUSY) of which one purpose is =93to descri=
be=20
> a request for free/busy time=94 (RFC 2445, p. 58).  We aren=92t reinven=
ting=20
> or proposing something new or radically different.

Would you want to disallow:

C: BEGIN:VCALENDAR
C: VERSION:2.0
C: PRODID:-//Someone=92s Prodid
C: CMD;ID=3DFB001:SEARCH
C: TARGET:CalA
C: TARGET:CalB
C: BEGIN:VQUERY
C: QUERY:SELECT DTSTART,DTEND,FREEBUSY FROM VFREEBUSY
C:  WHERE DTEND >=3D ''20030808T170000Z
C:  AND DTSTART <=3D '20030804T080000Z'
C: END:VQUERY

--=20

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms010200060108030801000303
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINRDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDIwOTE4MDAw
MDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD
EEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuOjEp298xKmKaSoPmY4WupTfjVMvob
cj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umSqlGIEwX6u2g2lfhJIG1nAYCAItpB
JXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzvq3gGiEg4kjV+KC+peZLB9YpiuEFx
3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvfvMcUKdzRub3F/GNvDgu6dd1Jq52t
VrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJJKkkZRaZAgMBAAGjggEGMIIBAjAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAo
oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9ttwSYnVsHPS1PcjLxGL5gSrWxN1G
VNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcUioomgeYc81cGfR1diWN7mnZNFuXZ
Ztb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJ
PKEwDQYJKoZIhvcNAQEEBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQwHhcNMDIwOTE4MDAwMDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD
VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixM
SUFCLkxURChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsT
KkRpZ2l0YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQK
RG91ZyBSb3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDEEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuO
jEp298xKmKaSoPmY4WupTfjVMvobcj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umS
qlGIEwX6u2g2lfhJIG1nAYCAItpBJXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzv
q3gGiEg4kjV+KC+peZLB9YpiuEFx3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvf
vMcUKdzRub3F/GNvDgu6dd1Jq52tVrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJ
JKkkZRaZAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG
+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIG
CCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhC
AQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xh
c3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9
ttwSYnVsHPS1PcjLxGL5gSrWxN1GVNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcU
ioomgeYc81cGfR1diWN7mnZNFuXZZtb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jGCBKowggSm
AgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ
QSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh
c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAe
jFNQR/pY9ailMryViTyhMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDcxODIzNDI0NFowIwYJKoZIhvcNAQkEMRYEFBaUPRRj
9O1neUWxuKUtP4pxOpFfMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEE
AYI3EAQxgeQwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEB6MU1BH+lj1qKUyvJWJPKEwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAejFNQR/pY9ailMryViTyhMA0G
CSqGSIb3DQEBAQUABIIBABtKYpy5Qtxz005U3ur3L1LYjjKr842wqUIAiDXC4o/fjF+wKc5A
gXyqfHWMjDLNCgZKBEBcQCLLdtkGKw09lvK8RocH22jtARUaqmXTzASleKkbVSci2hEnkGWh
RyFIwmeF+uxRgzPd8DzKR3mYxvAUszlXfOmk/yXhPux+OPN5tT8++rL29L+esxc/t68hZgR/
2jWfC3iBbsmit1UJKj10yAum5Jb0k7E5mm/v1I7OVH8RJ7dfsUFpgtkYRwhHpg5bxoJnfX6e
NQk/kxLvv2hsoXpbANiFsh2wedf+64kKweyQNlINZ3PCggCmZ28oklQRY30BEB47wgtgJmdC
nQkAAAAAAAA=
--------------ms010200060108030801000303--



From owner-ietf-calendar@mail.imc.org  Fri Jul 18 23:25:31 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21863
	for <calsch-archive@lists.ietf.org>; Fri, 18 Jul 2003 23:25:30 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6J38bqt038629
	for <ietf-calendar-bks@above.proper.com>; Fri, 18 Jul 2003 20:08:37 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6J38bBj038628
	for ietf-calendar-bks; Fri, 18 Jul 2003 20:08:37 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6J38Xqt038618
	for <ietf-calendar@imc.org>; Fri, 18 Jul 2003 20:08:33 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: "Craig Johnson" <cjohnson@gw.novell.com>
Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
Subject: Re: Cap Free-Busy Request
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
From: pregen@egenconsulting.com
Message-ID: <OFDE83EF53.215BDA46-ON85256D68.00004672-85256D68.00112A2A@egenconsulting.com>
Date: Fri, 18 Jul 2003 23:08:31 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/18/2003 11:08:36 PM,
	Serialize complete at 07/18/2003 11:08:36 PM
Content-Type: multipart/alternative; boundary="=_alternative 00004C1885256D68_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 00004C1885256D68_=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thank you Craig.  Thoughts/comments anyone?





"Craig Johnson" <cjohnson@gw.novell.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/18/2003 05:02 PM

=20
        To:     <ietf-calendar@imc.org>
        cc:=20
        Subject:        Cap Free-Busy Request




A discussion was started on Mar 31, 2003, regarding how a CUA can request=20
free-busy information using CAP.  It was noted that the CAP spec promised=20
to "specify how to search for available busy time information" but there=20
was nothing in the spec that described how to do this.  While several=20
ideas were discussed the key issue was not resolved.  Toward the end of=20
the discussion Pat Egen called for proposals, with text, to resolve the=20
issue.  So far, none have been presented.

=20

I wish to make a proposal for requesting free-busy information via CAP. =20

=20

From the abovementioned discussion there seemed to be agreement on some=20
issues:

-  The request should be simple: just specify targets and period of=20
interest.

-  The request should be unambiguous.

-  The CS should reply to the request with the free-busy information (i.e. =

respond in real-time).

-  To respond in real-time, the CS should=20
retrieve/compose/generate/formulate/synthesize (or whatever it needs to=20
do) to provide the free-busy information.

=20

With this in mind, my proposal for a CAP free-busy request is to use the=20
SEARCH command with a VFREEBUSY object.  The following is an example:

=20

C: BEGIN:VCALENDAR

C: VERSION:2.0

C: PRODID:-//Someone's Prodid

C: CMD;ID=3DFB001:SEARCH

C: TARGET:UserA

C: TARGET:UserB

C: BEGIN:VFREEBUSY

C: DTSTART:20030804T080000Z

C: DTEND:20030808T170000Z

C: END:VFREEBUSY

C: END:VCALENDAR

=20

Upon receiving this command a Calendar Store (CS) will compose a response=20
for each TARGET.  A sample response to the above request would be:=20

=20

S: BEGIN:VCALENDAR

S: VERSION:2.0

S: PRODID:-//Some Calendar Store

S: CMD;ID=3DFB001:REPLY

S: TARGET:UserA

S: BEGIN:VREPLY

S: BEGIN:VFREEBUSY

S: DTSTART:20030804T080000Z

S: DTEND:20030808T170000Z

S: DTSTAMP:20030710T131103Z

S: FREEBUSY:20030805T100000Z/20030805T110000Z

S: FREEBUSY:20030805T140000Z/20030805T150000Z

S: END:VFREEBUSY

S: END:VREPLY

S: END:VCALENDAR

=20

S: BEGIN:VCALENDAR

S: VERSION:2.0

S: PRODID:-//Some Calendar Store

S: CMD;ID=3DFB001:REPLY

S: TARGET:UserB

S: BEGIN:VREPLY

S: BEGIN:VFREEBUSY

S: DTSTART:20030804T080000Z

S: DTEND:20030808T170000Z

S: DTSTAMP:20030710T131103Z

S: FREEBUSY:20030806T130000Z/20030805T150000Z

S: END:VFREEBUSY

S: END:VREPLY

S: END:VCALENDAR

=20

This proposal has several advantages:

-  It is simple and straightforward.  No ambiguity about the request.

-  It is 'natural' and 'familiar' because it uses an already defined, well =

understood object (VFREEBUSY) of which one purpose is "to describe a=20
request for free/busy time" (RFC 2445, p. 58).  We aren't reinventing or=20
proposing something new or radically different.

-  It is similar to an iTIP free-busy request which also uses VFREEBUSY. =20
This creates uniformity and consistency between CAP and iTIP for=20
requesting free-busy information.  This is somewhat important and=20
advantageous.  Implementers will expect that a free-busy request, whether=20
sent via iMIP/iTIP, CAP/iTIP, or CAP real-time, will result in the same=20
data being returned!  Using a similar scheme for requesting free-busy=20
information is a step toward uniformity.  In addition, this will=20
facilitate and simplify implementations that already have code to handle=20
iTIP free-busy requests by allowing re-use of that code for CAP free-busy=20
requests.

-  It accommodates a free-busy request/response regardless of how (or=20
whether) a Calendar Store supports VFREEBUSY as an AGENDA component (i.e.=20
whether or not VFREEBUSY is listed on the COMPONENTS property in response=20
to GET-CAPABILITIES).  Calendar Stores that support the VFREEBUSY=20
component can create a response from them.  Calendar Stores that do not=20
support the VFREEBUSY component can compose a response from VEVENTs and/or =

other vender specific data related to free-busy time.  CUAs are insulated=20
from the specifics of how a Calendar Store internally represents free-busy =

information.

=20

The ABNF to accommodate this proposal simply adds "freebusyc" to the=20
"search-comp" definition.  The ABNF for "search-comp" was not in the most=20
recent draft (this was noted by B Kahn  on 6/14/2003and acknowledged by D=20
Royer on 6/19/2003.)  The following is the presumed ABNF for "search-comp" =

that includes "freebusyc".  It would appear in section "10.8 SEARCH=20
Command"

=20

   ABNF for a "SEARCH" object is:

=20

   search-object =3D "BEGIN" ":" "VCALENDAR" CRLF

                 ;

                 ; calprops MUST include 'search-cmd'

                 ;

                   calprops

                   other-props

                   1*(search-comp)

                   "END" ":" "VCALENDAR" CRLF

=20

   search-comp   =3D queryc / freebusyc

                   / iana-comp / x-component

=20

   freebusyc     =3D "BEGIN" ":" "VFREEBUSY" CRLF

                 ;=20

                 ; The following MUST occur exactly once.

                 ;

                   / dtstart

                   / dtend

                 ;

                 ; The following are optional,

                 ; but MUST NOT occur more than once.

                 ;

                   / dtstamp

                   / uid

                 ;

                 ; The following are optional,

                 ; and MAY occur more than once.

                 ;

                   / other-props

=20

                   "END" ":" "VFREEBUSY" CRLF

=20

I look forward to response and feedback regarding this proposal.

=20

--C Johnson



--=_alternative 00004C1885256D68_=
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">Thank you Craig. &nbsp;Thoughts/comm=
ents anyone?<br>
</font>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<td><font size=3D1 face=3D"sans-serif"><b>&quot;Craig Johnson&quot; &lt;cjo=
hnson@gw.novell.com&gt;</b></font>
<br><font size=3D1 face=3D"sans-serif">Sent by: owner-ietf-calendar@mail.im=
c.org</font>
<p><font size=3D1 face=3D"sans-serif">07/18/2003 05:02 PM</font>
<br>
<td><font size=3D1 face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbs=
p; &nbsp; &nbsp; &nbsp;&lt;ietf-calendar@imc.org&gt;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbs=
p; &nbsp; &nbsp; &nbsp;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject:=
 &nbsp; &nbsp; &nbsp; &nbsp;Cap Free-Busy Request</font></table>
<br>
<br>
<br>
<br>
<br><font size=3D3>A discussion&nbsp;was started&nbsp;on Mar 31, 2003, rega=
rding how a CUA can request free-busy information using CAP.&nbsp; It was n=
oted that the CAP spec promised to "specify how to search for available bus=
y time information" but there was nothing in the spec that described how to=
 do this.&nbsp; While several ideas were discussed the key issue was not re=
solved.&nbsp; Toward the end of the discussion Pat Egen called for proposal=
s, with text, to resolve the issue.&nbsp; So far, none have been presented.=
</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>I wish to make a proposal for requesting free-busy infor=
mation via CAP.&nbsp; </font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>From the abovementioned discussion there seemed to be ag=
reement on some issues:</font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;The request should be simple: just specify =
targets and period of interest.</font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;The request should be unambiguous.</font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;The CS should reply&nbsp;to the request wit=
h the free-busy information (i.e. respond in real-time).</font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;To respond in real-time, the CS should retr=
ieve/compose/generate/formulate/synthesize (or whatever it needs to do) to =
provide&nbsp;the free-busy information.</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>With this in mind, my proposal for a CAP free-busy reque=
st is to use the SEARCH command with a VFREEBUSY object.&nbsp; The followin=
g is an example:</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>C: BEGIN:VCALENDAR</font>
<br>
<br><font size=3D3>C: VERSION:2.0</font>
<br>
<br><font size=3D3>C: PRODID:-//Someone's Prodid</font>
<br>
<br><font size=3D3>C: CMD;ID=3DFB001:SEARCH</font>
<br>
<br><font size=3D3>C: TARGET:UserA</font>
<br>
<br><font size=3D3>C: TARGET:UserB</font>
<br>
<br><font size=3D3>C: BEGIN:VFREEBUSY</font>
<br>
<br><font size=3D3>C: DTSTART:20030804T080000Z</font>
<br>
<br><font size=3D3>C: DTEND:20030808T170000Z</font>
<br>
<br><font size=3D3>C: END:VFREEBUSY</font>
<br>
<br><font size=3D3>C: END:VCALENDAR</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>Upon receiving this command a Calendar Store (CS) will c=
ompose a response for each TARGET.&nbsp; A sample response to the above req=
uest would be: </font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>S: BEGIN:VCALENDAR</font>
<br>
<br><font size=3D3>S: VERSION:2.0</font>
<br>
<br><font size=3D3>S: PRODID:-//Some Calendar Store</font>
<br>
<br><font size=3D3>S: CMD;ID=3DFB001:REPLY</font>
<br>
<br><font size=3D3>S: TARGET:UserA</font>
<br>
<br><font size=3D3>S: BEGIN:VREPLY</font>
<br>
<br><font size=3D3>S: BEGIN:VFREEBUSY</font>
<br>
<br><font size=3D3>S: DTSTART:20030804T080000Z</font>
<br>
<br><font size=3D3>S: DTEND:20030808T170000Z</font>
<br>
<br><font size=3D3>S: DTSTAMP:20030710T131103Z</font>
<br>
<br><font size=3D3>S: FREEBUSY:20030805T100000Z/20030805T110000Z</font>
<br>
<br><font size=3D3>S: FREEBUSY:20030805T140000Z/20030805T150000Z</font>
<br>
<br><font size=3D3>S: END:VFREEBUSY</font>
<br>
<br><font size=3D3>S: END:VREPLY</font>
<br>
<br><font size=3D3>S: END:VCALENDAR</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>S: BEGIN:VCALENDAR</font>
<br>
<br><font size=3D3>S: VERSION:2.0</font>
<br>
<br><font size=3D3>S: PRODID:-//Some Calendar Store</font>
<br>
<br><font size=3D3>S: CMD;ID=3DFB001:REPLY</font>
<br>
<br><font size=3D3>S: TARGET:UserB</font>
<br>
<br><font size=3D3>S: BEGIN:VREPLY</font>
<br>
<br><font size=3D3>S: BEGIN:VFREEBUSY</font>
<br>
<br><font size=3D3>S: DTSTART:20030804T080000Z</font>
<br>
<br><font size=3D3>S: DTEND:20030808T170000Z</font>
<br>
<br><font size=3D3>S: DTSTAMP:20030710T131103Z</font>
<br>
<br><font size=3D3>S: FREEBUSY:20030806T130000Z/20030805T150000Z</font>
<br>
<br><font size=3D3>S: END:VFREEBUSY</font>
<br>
<br><font size=3D3>S: END:VREPLY</font>
<br>
<br><font size=3D3>S: END:VCALENDAR</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>This proposal has several advantages:</font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;It is simple and straightforward.&nbsp; No =
ambiguity about the request.</font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;It is 'natural' and 'familiar' because it u=
ses an already defined, well understood object (VFREEBUSY) of which one pur=
pose is "to describe a request for free/busy time" (RFC 2445, p. 58). &nbsp=
;We aren't reinventing or proposing something new or radically different.</=
font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;It is similar to an iTIP free-busy request =
which also uses VFREEBUSY.&nbsp; This creates uniformity and consistency be=
tween CAP and iTIP for requesting free-busy information.&nbsp; This is some=
what important and advantageous.&nbsp; Implementers will expect that a free=
-busy request, whether sent via iMIP/iTIP, CAP/iTIP, or CAP real-time, will=
 result in the same data being returned!&nbsp; Using a similar scheme for r=
equesting free-busy information is a step toward uniformity.&nbsp; In addit=
ion, this will facilitate and simplify implementations that already have co=
de to handle iTIP free-busy requests by allowing re-use of that code for CA=
P free-busy requests.</font>
<br>
<br><font size=3D3>-&nbsp;&nbsp;It accommodates a free-busy request/respons=
e regardless of how (or whether) a Calendar Store supports VFREEBUSY as an =
AGENDA component (i.e. whether or not VFREEBUSY is listed on the COMPONENTS=
 property in response to GET-CAPABILITIES).&nbsp; Calendar Stores that supp=
ort the VFREEBUSY component can create a response from them.&nbsp; Calendar=
 Stores that do not support the VFREEBUSY component can compose a response =
from VEVENTs and/or other vender specific data related to free-busy time.&n=
bsp; CUAs are insulated from the&nbsp;specifics of how a Calendar Store int=
ernally represents free-busy information.</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>The ABNF to accommodate this proposal simply adds "freeb=
usyc" to the "search-comp" definition.&nbsp; The ABNF for "search-comp" was=
 not in the most recent draft (this was noted by B Kahn &nbsp;on 6/14/2003a=
nd acknowledged by D Royer on 6/19/2003.)&nbsp; The following is the presum=
ed ABNF for "search-comp" that includes "freebusyc".&nbsp; It would appear =
in section "10.8 SEARCH Command"</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp; ABNF for a &quot;SEARCH&quot; object is:</f=
ont>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp; search-object =3D &quot;BEGIN&quot; &quot;:=
&quot; &quot;VCALENDAR&quot; CRLF</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;; calprops MUST include 'search-cm=
d'</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; calprops</font>
<br>
<br><font size=3D3>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;other-props</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1*(search-comp)</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;END&quot; &quot;=
:&quot; &quot;VCALENDAR&quot; CRLF</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp; search-comp &nbsp;&nbsp;=3D queryc / freebu=
syc</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;/ iana-comp / x-compon=
ent</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp; freebusyc&nbsp;&nbsp;&nbsp;&nbsp; =3D &quot=
;BEGIN&quot; &quot;:&quot; &quot;VFREEBUSY&quot; CRLF</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;&nbsp;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;; The following MUST occur exactly=
 once.</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / dtstart</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / dtend</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; The following are optional,</fon=
t>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; but MUST NOT occur more than onc=
e.</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / dtstamp</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / uid</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; The following are optional,</fon=
t>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; and MAY occur more than once.</f=
ont>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / other-props</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;END&quot; &quot;=
:&quot; &quot;VFREEBUSY&quot; CRLF</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>I look forward to response and feedback regarding this p=
roposal.</font>
<br>
<br><font size=3D3>&nbsp;</font>
<br>
<br><font size=3D3>--C Johnson</font>
<br>
<br>
<br>
--=_alternative 00004C1885256D68_=--


From subs-reminder@imc.org  Sat Jul 19 18:41:53 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25133
	for <calsch-archive@lists.ietf.org>; Sat, 19 Jul 2003 18:41:52 -0400 (EDT)
From: subs-reminder@imc.org
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6JMfsqt024415
	for <calsch-archive@lists.ietf.org>; Sat, 19 Jul 2003 15:41:54 -0700 (PDT)
	(envelope-from subs-reminder@imc.org)
Received: (from root@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6JMfrpb024414;
	Sat, 19 Jul 2003 15:41:53 -0700 (PDT)
Date: Sat, 19 Jul 2003 15:41:53 -0700 (PDT)
Message-Id: <200307192241.h6JMfrpb024414@above.proper.com>
To: calsch-archive@ietf.org
Subject: [[807101840]] Subscription to ietf-calendar for calsch-archive@lists.ietf.org

Greetings. This message is a periodic reminder that
     calsch-archive@lists.ietf.org
is subscribed to the
     ietf-calendar
mailing list.

*** SEE BELOW: PLEASE DO NOT RESPOND TO THIS MESSAGE. ***

There are two purposes for this message:
- If this message is bounced by your mail server, I can remove you from
  the mailing list and reduce waste of bandwidth and resources. (If you
  are reading this message, it clearly didn't get bounced!)
- Some people stay subscribed to mailing lists even though they do not
  want to because they do not know how to unsubscribe. 

If you want to stay subscribed to the ietf-calendar mailing list,
you do not need to do anything. Feel free to delete this message.

On the other hand, if you want to unsubscribe from this list, simply go
to the following link:
     <http://www.imc.org/Unsubs/807101840>

If for some reason you cannot go to that web site, you can also
unsubscribe by email; however, doing so is not as likely to get you
unsubscribed as the web site is. To unsubscribe using email, you can
respond to this message and I will unsubscribe you by hand in the next
few days. Again, this is not assured to work because your mail system
may make it impossible for me to determine who you are or what you want
to unsubscribe to.

Alternatively, you can send a plain-text message to:
     ietf-calendar-request@imc.org
with the single word
     unsubscribe
in the body of the message. This last method assumes that the "From:"
address in your mail is "calsch-archive@lists.ietf.org". Again, using the
web site above is more likely to work than this method (due to limitations
in Majordomo, the mailing list software we currently use).

If you have any questions, feel free to contact me.

--Paul Hoffman, list administrator


From owner-ietf-calendar@mail.imc.org  Mon Jul 21 14:39:14 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06455
	for <calsch-archive@lists.ietf.org>; Mon, 21 Jul 2003 14:39:13 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6LIHKqt059726
	for <ietf-calendar-bks@above.proper.com>; Mon, 21 Jul 2003 11:17:20 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6LIHKOE059725
	for ietf-calendar-bks; Mon, 21 Jul 2003 11:17:20 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6LIHKqt059707
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 11:17:20 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Mon, 21 Jul 2003 12:15:45 -0600
Message-Id: <sf1bd971.016@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 21 Jul 2003 11:18:10 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request - vs QUERY?
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part29770742.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__Part29770742.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

D Royer asked: > Would you want to disallow:> > C: BEGIN:VCALENDAR> C: =
VERSION:2.0> C: PRODID:-//Someone's Prodid> C: CMD;ID=3DFB001:SEARCH> C: =
TARGET:CalA> C: TARGET:CalB> C: BEGIN:VQUERY> C: QUERY:SELECT DTSTART,DTEND=
,FREEBUSY FROM VFREEBUSY> C:  WHERE DTEND >=3D '20030808T170000Z'> C:  AND =
DTSTART <=3D '20030804T080000Z'> C: END:VQUERY No, I do not suggest we =
disallow this QUERY.  Such a QUERY is necessary for Calendar Stores that =
support the VFREEBUSY component.  Allow me to elaborate on a few distinguis=
hing issues... 1. Let's make a distinction between "a request for =
free-busy information" and "a QUERY for VFREEBUSY components".  This =
distinction comes clearly into focus when dealing with a Calendar Store =
that does not support the VFREEBUSY component. Suppose we have a simple =
Calendar Store that supports VEVENTs but does not support VTODO, VJOURNAL =
or VFREEBUSY (i.e. VEVENT is on the COMPONENTS property; VTODO, VJOURNAL =
and VFREEBUSY are not).  The Calendar Store is capable of providing =
free-busy information, but how do you get it?  A QUERY of VFREEBUSY would =
be formally invalid because it is not listed on the COMPONENTS property.  =
Would a QUERY of VTODOs be valid?  No.  Why would a VFREEBUSY be any =
different?  Nothing in the CAP spec allows for this incongruency (i.e. =
no-where does the spec indicate that a Calendar Store must support a QUERY =
of VFREEBUSY regardless of whether it is listed on the COMPONENTS =
property.) This is avoided by making SEARCH/VFREEBUSY the way to "request =
free-busy information".  It works regardless of how the Calendar Store =
keeps track of "free-busy" information (i.e. whether or not it supports =
the VFREEBUSY component).  SEARCH/VQUERY only works for Calendar Stores =
that support the VFREEBUSY object. 2.  A SEARCH/VQUERY may not return the =
same information as a SEARCH/VFREEBUSY (although both will return the =
needed information). Suppose we have a Calendar Store that supports the =
VFREEBUSY component.  Within a VAGENDA there is a VFREEBUSY object for =
each month containing FREEBUSY properties for busy times in that month.  =
Now, suppose I need free-busy information for a particular week* - A =
SEARCH/VQUERY would find the VFREEBUSY object(s) that overlap the week of =
interest.  The VFREEBUSY object would be returned with FREEBUSY properties =
for the entire month , not just FREEBUSY properties for the requested =
week.- A SEARCH/VFREEBUSY would also find the VFREEBUSY object(s) that =
overlap the week of interest.  However, in creating a response, the =
SEARCH/VFREEBUSY can include only FREEBUSY properties overlapping the week =
of interest and others can be left out. 3. The above QUERY may need =
additional criteria to return the correct information: C: QUERY:SELECT =
DTSTART,DTEND,FREEBUSY FROM VFREEBUSYC:  WHERE DTEND >=3D '20030808T170000Z=
'C:  AND DTSTART <=3D '20030804T080000Z'C:  AND STATE() =3D 'BOOKED'. The =
addition of STATE() =3D 'BOOKED' is necessary to avoid retrieving =
'unprocessed' VFREEBUSY records that may be present in the VAGENDA. QUERY =
is a 'nuts and bolts' way of getting information; powerful and flexible =
... but inherently complex.  In contrast, a 'VFREEBUSY request' is a 'high =
level' operation; very specific ...  but simple. Thanks,--C Johnson     =
=20

--=__Part29770742.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">D Royer =
asked:<?xml:namespace prefix =3D o ns =3D "urn:schemas-microsoft-com:office=
:office" /><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; Would you =
want to disallow:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; <o:p></o:p><=
/SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
BEGIN:VCALENDAR<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
VERSION:2.0<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
PRODID:-//Someone=92s Prodid<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
CMD;ID=3DFB001:SEARCH<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
TARGET:CalA<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
TARGET:CalB<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
BEGIN:VQUERY<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
QUERY:SELECT DTSTART,DTEND,FREEBUSY FROM VFREEBUSY<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C:<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>WHERE DTEND &gt;=3D '20030808T170=
000Z'<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C:<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>AND DTSTART &lt;=3D '20030804T080=
000Z'<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">&gt; C: =
END:VQUERY<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">No, I do not =
suggest we disallow this QUERY.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Such a QUERY is necessary for Calendar Stores that support the =
VFREEBUSY component.<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;</SPAN></=
SPAN><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><SPAN style=3D"mso=
-spacerun: yes">A</SPAN>llow me to&nbsp;elaborate on a few distinguishing =
issues...</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"></SPAN><SPAN =
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">1. Let's make a =
distinction between "a request for free-busy information" and "a QUERY for =
VFREEBUSY components".<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>This =
distinction comes clearly&nbsp;into focus when dealing with a Calendar =
Store that does not support the VFREEBUSY component.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">Suppose we have =
a simple Calendar Store that supports VEVENTs but does not support VTODO, =
VJOURNAL or VFREEBUSY (i.e. VEVENT is on the COMPONENTS property; VTODO, =
VJOURNAL and VFREEBUSY are not).<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>The Calendar Store is capable of providing free-busy information, =
but how do you get it?<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>A =
QUERY of VFREEBUSY would be formally invalid because it is not listed on =
the COMPONENTS property.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Wou=
ld a QUERY of VTODOs be valid?&nbsp; No.<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>Why would a VFREEBUSY be any different?<SPAN style=3D"ms=
o-spacerun: yes">&nbsp; </SPAN>Nothing in the CAP spec allows for this =
incongruency&nbsp;(i.e. no-where does the spec indicate that a Calendar =
Store must support a QUERY of VFREEBUSY regardless of whether it is listed =
on the COMPONENTS property.)<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">This is avoided =
by making SEARCH/VFREEBUSY the way to "request free-busy information".<SPAN=
 style=3D"mso-spacerun: yes">&nbsp; </SPAN>It works regardless of how the =
Calendar Store keeps track of "free-busy" information (i.e. whether or not =
it supports the VFREEBUSY component).&nbsp; SEARCH/VQUERY only works for =
Calendar Stores that support the VFREEBUSY object.</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"></SPAN>&nbsp;</P>=

<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma; mso-fareast-font-=
family: Tahoma"><SPAN style=3D"mso-list: Ignore">2.&nbsp;<SPAN style=3D"FON=
T: 7pt 'Times New Roman'">&nbsp;</SPAN></SPAN></SPAN><SPAN style=3D"FONT-SI=
ZE: 8pt; FONT-FAMILY: Tahoma">A SEARCH/VQUERY may not return the same =
information as a SEARCH/VFREEBUSY<SPAN style=3D"mso-spacerun: yes"> =
(although both will return the needed information).</SPAN><o:p></o:p></SPAN=
></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">Suppose we have =
a Calendar Store that supports the VFREEBUSY component.<SPAN style=3D"mso-s=
pacerun: yes">&nbsp; </SPAN>Within a VAGENDA there is a VFREEBUSY object =
for each month containing FREEBUSY properties for busy times in that =
month.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Now, suppose I need =
free-busy information for a particular week=85<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">- A SEARCH/VQUERY=
 would find the VFREEBUSY object(s) that overlap the week of interest. =
<SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>The&nbsp;VFREEBUSY object =
would be returned with FREEBUSY properties for the entire month , not just =
FREEBUSY properties for the requested week.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">- A SEARCH/VFREEB=
USY would also find the VFREEBUSY object(s) that overlap the week of =
interest.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>However, in =
creating a response, the SEARCH/VFREEBUSY can include only FREEBUSY =
properties overlapping the week of interest and others can be left =
out.</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"></SPAN>&nbsp;</P>=
<SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">3.&nbsp;The =
above QUERY may need additional criteria to return the correct information:=
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">C: QUERY:SELECT =
DTSTART,DTEND,FREEBUSY FROM VFREEBUSY<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">C:<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>WHERE DTEND &gt;=3D '20030808T170=
000Z'<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">C:<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>AND DTSTART &lt;=3D '20030804T080=
000Z'<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">C:<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>AND STATE() =3D 'BOOKED'.<o:p></o=
:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">The addition of =
STATE() =3D 'BOOKED' is necessary to avoid retrieving 'unprocessed' =
VFREEBUSY records that may be present in the VAGENDA.<o:p></o:p></SPAN></P>=

<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">QUERY&nbsp;is a =
'nuts and bolts' way of getting information; powerful and flexible =
...&nbsp;but inherently complex.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>In contrast, a 'VFREEBUSY request' is a 'high level' operation; =
very specific&nbsp;... &nbsp;but simple.</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"></SPAN>&nbsp;</P>=

<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">Thanks,</SPAN></P=
>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">--C Johnson</SPAN=
></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"></SPAN>&nbsp;</P>=

<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"></SPAN>&nbsp;</P>=

<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"></SPAN>&nbsp;</P>=

<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p></o:p></SPAN=
>&nbsp;</P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p>=
</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none">&nbsp;</o:p></SPAN></P></BODY></HTML>

--=__Part29770742.0__=--


From owner-ietf-calendar@mail.imc.org  Mon Jul 21 15:26:09 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08478
	for <calsch-archive@lists.ietf.org>; Mon, 21 Jul 2003 15:26:09 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6LJCvqt063200
	for <ietf-calendar-bks@above.proper.com>; Mon, 21 Jul 2003 12:12:57 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6LJCuKV063199
	for ietf-calendar-bks; Mon, 21 Jul 2003 12:12:56 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6LJCtqt063186
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 12:12:55 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Mon, 21 Jul 2003 13:11:26 -0600
Message-Id: <sf1be67e.025@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 21 Jul 2003 12:13:44 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request - UPN vs CALID?
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


D Royer Asked:
> Craig Johnson wrote:
> > With this in mind, my proposal for a CAP free-busy request is to
> > use the SEARCH command with a VFREEBUSY object. The following is an
example:
> > 
> > C: BEGIN:VCALENDAR
> > C: VERSION:2.0
> > C: PRODID:-//Someone's Prodid
> > C: CMD;ID=FB001:SEARCH
> > C: TARGET:UserA
> > C: TARGET:UserB
>
> Above you use 'UserA' and 'UserB', did your proposal also
> imply that you can do a search based on a UPN across CALIDs?
> Or are those still CALID's that just happen to be named 'User'X ?

CALID's that just happen to be named 'UserX'. 

> AND THANK YOU VERY MUCH FOR PROPOSING A SOLUTION. Without specific
> proposals, 'I' end up adding and making up the solution and it
> makes it SO MUCH easier when others provide solutions!!!

Thanks,

--C Johnson


From owner-ietf-calendar@mail.imc.org  Mon Jul 21 17:02:15 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10759
	for <calsch-archive@lists.ietf.org>; Mon, 21 Jul 2003 17:02:14 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6LKiRqt067843
	for <ietf-calendar-bks@above.proper.com>; Mon, 21 Jul 2003 13:44:27 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6LKiRtc067842
	for ietf-calendar-bks; Mon, 21 Jul 2003 13:44:27 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6LKiQqt067837
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 13:44:26 -0700 (PDT)
	(envelope-from satyanarayana.vempati@Sun.COM)
Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35])
	by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h6LKiRCW002635
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 14:44:28 -0600 (MDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail1sca.SFBay.Sun.COM (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h6LKiRhD016200
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 13:44:27 -0700 (PDT)
Received: from pranav.red.iplanet.com (pranav.red.iplanet.com [192.18.144.109])
 by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HIE00AJP6Y3YB@ha13sca-mail1.sfbay.sun.com> for
 ietf-calendar@imc.org; Mon, 21 Jul 2003 13:44:27 -0700 (PDT)
Date: Mon, 21 Jul 2003 13:44:28 -0700
From: Satya Vempati <satyanarayana.vempati@Sun.COM>
Subject: RE: Cap Free-Busy Request
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_4_.20030721134428.944C@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_V6msix92UoHIzAXxVmIC8Q)"; DIFFERENCES=Content-Language
Content-language: en-USA
Content-transfer-encoding: 8BIT
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



--Boundary_(ID_V6msix92UoHIzAXxVmIC8Q)
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Content-language: en-USA
Content-Transfer-Encoding: QUOTED-PRINTABLE

A high-level command to get FREEBUSY seems like a good addition. I have
one suggestion.
=20
It seems that the FBTYPE implicit in VREPLY. Per RFC 2445, other FBTYPE's
are possible apart  from the simple FREE/BUSY. They are BUSY-UNAVAILABLE,
BUSY-TENTATIVE. You can add even more types through X-tokens.
=20
Shouldn't there be an FBTYPE in the VREPLY?

-----Original Message-----
From: Craig Johnson [mailto:cjohnson@gw.novell.com]
Sent: Friday, July 18, 2003 2:03 PM
To: ietf-calendar@imc.org
Subject: Cap Free-Busy Request



A discussion was started on Mar 31, 2003, regarding how a CUA can request
free-busy information using CAP.  It was noted that the CAP spec promised
to =93specify how to search for available busy time information=94 but ther=
e
was nothing in the spec that described how to do this.  While several
ideas were discussed the key issue was not resolved.  Toward the end of
the discussion Pat Egen called for proposals, with text, to resolve the
issue.  So far, none have been presented.

=20

I wish to make a proposal for requesting free-busy information via CAP. =20

=20

From the abovementioned discussion there seemed to be agreement on some
issues:

-  The request should be simple: just specify targets and period of
interest.

-  The request should be unambiguous.

-  The CS should reply to the request with the free-busy information (i.e.
respond in real-time).

-  To respond in real-time, the CS should
retrieve/compose/generate/formulate/synthesize (or whatever it needs to
do) to provide the free-busy information.

=20

With this in mind, my proposal for a CAP free-busy request is to use the
SEARCH command with a VFREEBUSY object.  The following is an example:

=20

C: BEGIN:VCALENDAR

C: VERSION:2.0

C: PRODID:-//Someone=92s Prodid

C: CMD;ID=3DFB001:SEARCH

C: TARGET:UserA

C: TARGET:UserB

C: BEGIN:VFREEBUSY

C: DTSTART:20030804T080000Z

C: DTEND:20030808T170000Z

C: END:VFREEBUSY

C: END:VCALENDAR

=20

Upon receiving this command a Calendar Store (CS) will compose a response
for each TARGET.  A sample response to the above request would be:=20

=20

S: BEGIN:VCALENDAR

S: VERSION:2.0

S: PRODID:-//Some Calendar Store

S: CMD;ID=3DFB001:REPLY

S: TARGET:UserA

S: BEGIN:VREPLY

S: BEGIN:VFREEBUSY

S: DTSTART:20030804T080000Z

S: DTEND:20030808T170000Z

S: DTSTAMP:20030710T131103Z

S: FREEBUSY:20030805T100000Z/20030805T110000Z

S: FREEBUSY:20030805T140000Z/20030805T150000Z

S: END:VFREEBUSY

S: END:VREPLY

S: END:VCALENDAR

=20

S: BEGIN:VCALENDAR

S: VERSION:2.0

S: PRODID:-//Some Calendar Store

S: CMD;ID=3DFB001:REPLY

S: TARGET:UserB

S: BEGIN:VREPLY

S: BEGIN:VFREEBUSY

S: DTSTART:20030804T080000Z

S: DTEND:20030808T170000Z

S: DTSTAMP:20030710T131103Z

S: FREEBUSY:20030806T130000Z/20030805T150000Z

S: END:VFREEBUSY

S: END:VREPLY

S: END:VCALENDAR

=20

This proposal has several advantages:

-  It is simple and straightforward.  No ambiguity about the request.

-  It is =91natural=92 and =91familiar=92 because it uses an already define=
d, well
understood object (VFREEBUSY) of which one purpose is =93to describe a
request for free/busy time=94 (RFC 2445, p. 58).  We aren=92t reinventing o=
r
proposing something new or radically different.

-  It is similar to an iTIP free-busy request which also uses VFREEBUSY.=20
This creates uniformity and consistency between CAP and iTIP for
requesting free-busy information.  This is somewhat important and
advantageous.  Implementers will expect that a free-busy request, whether
sent via iMIP/iTIP, CAP/iTIP, or CAP real-time, will result in the same
data being returned!  Using a similar scheme for requesting free-busy
information is a step toward uniformity.  In addition, this will
facilitate and simplify implementation! s that already have code to handle
iTIP free-busy requests by allowing re-use of that code for CAP free-busy
requests.

-  It accommodates a free-busy request/response regardless of how (or
whether) a Calendar Store supports VFREEBUSY as an AGENDA component (i.e.
whether or not VFREEBUSY is listed on the COMPONENTS property in response
to GET-CAPABILITIES).  Calendar Stores that support the VFREEBUSY
component can create a response from them.  Calendar Stores that do not
support the VFREEBUSY component can compose a response from VEVENTs and/or
other vender specific data related to free-busy time.  CUAs are insulated
from the specifics of how a Calendar Store internally represents free-busy
information.

=20

The ABNF to accommodate this proposal simply adds =93freebusyc=94 to the
=93search-comp=94 definition.  The ABNF for =93search-comp=94 was not in th=
e most
recent draft (this was noted by B Kahn  on 6/14/2003 and acknowledged by D
Royer on 6/19/2003.)  The following is the presumed ABNF for =93search-comp=
=94
that includes =93freebusyc=94.  It would appear in section =9310.8 SEARCH
Command=94

=20

   ABNF for a "SEARCH" object is:

=20

   search-object =3D "BEGIN" ":" "VCALENDAR" CRLF

                 ;

                 ; calprops MUST include 'search-cmd'

                 ;

                   calprops

                   other-props

                   1*(search-comp)

                   "END" ":" "VCALENDAR" CRLF

=20

   search-comp   =3D queryc / freebusyc

                   / iana-comp / x-component

=20

   freebusyc     =3D "BEGIN" ":" "VFREEBUSY" CRLF

                 ;=20

                 ; The following MUST occur exactly once.

                 ;

                   / dtstart

                   / dtend

                 ;

                 ; The following are optional,

                 ; but MUST NOT occur more than once.

                 ;

                   / dtstamp

                   / uid

                 ;

                 ; The following are optional,

                 ; and MAY occur more than once.

                 ;

                   / other-props

=20

                   "END" ":" "VFREEBUSY" CRLF

=20

I look forward to response and feedback regarding this proposal.

=20

--C Johnson


--Boundary_(ID_V6msix92UoHIzAXxVmIC8Q)
Content-id: 0
Content-type: TEXT/html; CHARSET=iso-8859-1
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML xmlns:st1 = "urn:schemas-microsoft-com:office:smarttags" xmlns:o =  "urn:schemas-microsoft-com:office:office"><HEAD><META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD><BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma"><DIV>
 <SPAN class=390583720-21072003>A high-level command to get FREEBUSY seems  like a good addition. I have one suggestion. </SPAN>  </DIV>
  <DIV>
 <SPAN class=390583720-21072003> </SPAN> &nbsp;  </DIV>
  <DIV>
 <SPAN class=390583720-21072003>It seems that &nbsp;the FBTYPE implicit in  VREPLY. Per RFC 2445, other FBTYPE's are possible apart &nbsp; from the simple  FREE/BUSY. They are BUSY-UNAVAILABLE, BUSY-TENTATIVE. You can add even more  types through X-tokens. </SPAN>  </DIV>
  <DIV>
 <SPAN class=390583720-21072003> </SPAN> &nbsp;  </DIV>
  <DIV>
 <SPAN class=390583720-21072003>Shouldn't there be an FBTYPE in the  VREPLY? </SPAN>  </DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">     <DIV class=OutlookMessageHeader dir=ltr align=left>
 -----Original     Message----- <BR>
 <B>From: </B> Craig Johnson     [mailto:cjohnson@gw.novell.com] <BR>
 <B>Sent: </B> Friday, July 18, 2003 2:03     PM <BR>
 <B>To: </B> ietf-calendar@imc.org <BR>
 <B>Subject: </B> Cap Free-Busy     Request <BR>
 <BR>
  </DIV>
     <P class=MsoNormal style="MARGIN: 0in 0in 0pt"> A discussion &nbsp;was     started &nbsp;on  <st1:date Year="2003" Day="31" Month="3">Mar 31,     2003 </st1:date>, regarding how a CUA can request free-busy information using     CAP. <SPAN style="mso-spacerun: yes"> &nbsp;  </SPAN>It was noted that the CAP     spec promised to &#147specify how to search for available busy time information&#148     but there was nothing in the spec that described how to do this. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>While several ideas were discussed the     key issue was not resolved. <SPAN style="mso-spacerun: yes"> &nbsp;      </SPAN>Toward the end of the discussion Pat Egen called for proposals, with     text, to resolve the issue. <SPAN style="mso-spacerun: yes"> &nbsp;  </SPAN>So     far, none have been presented.  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <o:p> </o:p> &nbsp;  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt"> I wish to make a prop!
 osal for 
information via CAP. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <o:p> &nbsp; </o:p>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt"> From the abovementioned     discussion there seemed to be agreement on some issues:  </P>     <P class=MsoNormal    style="MARGIN: 0in 0in 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>The request should be simple:     just specify targets and period of interest.  </P>     <P class=MsoNormal    style="MARGIN: 0in 0in 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>The request should be     unambiguous.  </P>     <P class=!
 MsoNormal
n 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>The CS should reply &nbsp;to the     request with the free-busy information (i.e. respond in real-time).  </P>     <P class=MsoNormal    style="MARGIN: 0in 0in 0pt 22.5pt; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2; tab-stops: list 22.5pt">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>To respond in real-time, the CS     should retrieve/compose/generate/formulate/synthesize (or whatever it needs to     do) to provide &nbsp;the free-busy information.  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <o:p> &nbsp; </o:p>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt"> With this in mind, my proposal     for a CAP free-busy request is to use th!
 e SEARCH 
    object. <SPAN style="mso-spacerun: yes"> &nbsp;  </SPAN>The following is an     example:  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face="Times New Roman"> &nbsp; </FONT> </o:p>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C:     BEGIN:VCALENDAR <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C:     VERSION:2.0 <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C: PRODID:-//Someone&#146s     Prodid <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C:     CMD;ID=FB001:SEARCH <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">!
   <SPAN  
urier New'"> <FONT face=Terminal>C:     TARGET:UserA <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C:     TARGET:UserB <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C:     BEGIN:VFREEBUSY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN lang=NL    style="FONT-FAMILY: 'Courier New'; mso-ansi-language: NL"> <FONT    face=Terminal>C: DTSTART:20030804T080000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN lang=NL    style="FONT-FAMILY: 'Courier New'; mso-ansi-language: NL"> <FONT    face=Terminal>C: DTEND:20030808T170000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C:    !
  END:VFRE
> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>C:     END:VCALENDAR <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <o:p> &nbsp; </o:p> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt"> Upon receiving this command a     Calendar Store (CS) will compose a response for each TARGET. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>A sample response to the above request     would be:   </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <o:p> &nbsp; </o:p> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     BEGIN:VCALENDAR <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FO!
 NT face=T
0 <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S: PRODID:-//Some     Calendar Store <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     CMD;ID=FB001:REPLY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     TARGET:UserA <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     BEGIN:VREPLY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     BEGIN:VFREEBUSY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN   !
  style="F
"> <FONT face=Terminal>S:     DTSTART:20030804T080000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     DTEND:20030808T170000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     DTSTAMP:20030710T131103Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     FREEBUSY:20030805T100000Z/20030805T110000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     FREEBUSY:20030805T140000Z/20030805T150000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     !
 END:VFREE
 </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     END:VREPLY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     END:VCALENDAR <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <o:p> <FONT    face=Terminal> &nbsp; </FONT> </o:p> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     BEGIN:VCALENDAR <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     VERSION:2.0 <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal!
 >S: PRODI
ore <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     CMD;ID=FB001:REPLY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     TARGET:UserB <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     BEGIN:VREPLY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     BEGIN:VFREEBUSY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     DTSTART:20030804T080000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    st!
 yle="FONT
<FONT face=Terminal>S:     DTEND:20030808T170000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     DTSTAMP:20030710T131103Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     FREEBUSY:20030806T130000Z/20030805T150000Z <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     END:VFREEBUSY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     END:VREPLY <o:p> </o:p> </FONT> </SPAN>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>S:     END:VCALENDAR <o:p> </o:p> </FONT> </SPAN>  </!
 P>     <P
ARGIN: 0in 0in 0pt">  <o:p> <FONT    face="Times New Roman"> &nbsp; </FONT> </o:p>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt"> This proposal has several     advantages:  </P>     <P class=MsoNormal    style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>It is simple and     straightforward. <SPAN style="mso-spacerun: yes"> &nbsp;  </SPAN>No ambiguity     about the request.  </P>     <P class=MsoNormal    style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>It is &#145natural&#146 and &#145familiar&#146     because it uses an already defined, well understood object (VFREEBUSY) of     whi!
 ch one pu
=Tahoma> <SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT face=Terminal>to describe a request     for free/busy time </FONT> </SPAN>&#148 (RFC 2445, p. 58).  <SPAN    style="mso-spacerun: yes"> &nbsp; </SPAN>We aren&#146t reinventing or proposing     something new or radically different. </FONT>  </P>     <P class=MsoNormal    style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>It is similar to an iTIP     free-busy request which also uses VFREEBUSY. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>This creates uniformity and     consistency between CAP and iTIP for requesting free-busy information. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>This is somewhat important and     advantageous. <SPAN style="mso-spacerun: yes"> &nbsp;  </SPAN>Implementers will     expect that a fr!
 ee-busy r
iMIP/iTIP, CAP/iTIP, or CAP     real-time, will result in the same data being returned! <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>Using a similar scheme for requesting     free-busy information is a step toward uniformity. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>In addition, this will facilitate and     simplify implementation! s that already have code to handle iTIP free-busy     requests by allowing re-use of that code for CAP free-busy requests.  </P>     <P class=MsoNormal    style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in">  <SPAN    style="mso-list: Ignore">- <SPAN style="FONT: 7pt 'Times New Roman'"> <FONT    face=Tahoma> &nbsp; &nbsp; </FONT> </SPAN> </SPAN>It accommodates a free-busy     request/response regardless of how (or whether) a Calendar Store supports     VFREEBUSY as an AGENDA component (i.e. whether or not VFREEBUSY is listed on     the COMPONENTS property in response to GET-CAPABI!
 LITIES). 
run: yes"> &nbsp;  </SPAN>Calendar Stores that support the     VFREEBUSY component can create a response from them. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>Calendar Stores that do not support     the VFREEBUSY component can compose a response from VEVENTs and/or other     vender specific data related to free-busy time. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>CUAs are insulated from     the &nbsp;specifics of how a Calendar Store internally represents free-busy     information.  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <o:p> &nbsp; </o:p>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt"> The ABNF to accommodate this     proposal simply adds &#147freebusyc&#148 to the &#147search-comp&#148 definition. <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>The ABNF for &#147search-comp&#148 was not in     the most recent draft (this was noted by B Kahn  <SPAN    style="mso-spacerun: yes"> &nbsp; </SPAN>on  <st1:date Year="2003" Day="14!
 "    Mont
e> and acknowledged by D Royer on  <st1:date    Year="2003" Day="19" Month="6">6/19/2003 </st1:date>.) <SPAN    style="mso-spacerun: yes"> &nbsp;  </SPAN>The following is the presumed ABNF for     &#147search-comp&#148 that includes &#147freebusyc&#148. <SPAN style="mso-spacerun: yes"> &nbsp;      </SPAN>It would appear in section &#14710.8 SEARCH Command&#148  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face="Times New Roman"> &nbsp; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp;  </SPAN>ABNF for a "SEARCH" object     is: <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp;  </SPAN>search-object = "BEGIN" ":"     "VCALENDAR" CRLF <o:p>!
  </o:p> <
=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>; <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN> <SPAN style="mso-spacerun: yes"> &nbsp; </SPAN>; calprops MUST include     'search-cmd' <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>; <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nb!
 sp; &nbsp
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>calprops <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp;  </SPAN> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </SPAN>other-props <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>1*(search-comp) <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb!
 sp;      
AR" CRLF <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp;  </SPAN>search-comp  <SPAN    style="mso-spacerun: yes"> &nbsp; </SPAN> <SPAN    style="mso-spacerun: yes"> &nbsp; </SPAN>= queryc /     freebusyc <o:p> </o:p> </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN> <SPAN style="mso-spacerun: yes"> &nbsp; </SPAN>/ iana-comp /     x-component </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    st!
 yle="mso-
bsp;  </SPAN>freebusyc <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp;  </SPAN>= "BEGIN" ":"     "VFREEBUSY" CRLF </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;     ; &nbsp; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN> <SPAN style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; </SPAN> <SPAN    style="mso-spacerun: yes"> &nbsp; </SPAN>; The following MUST occur exactly     once. </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;; </FONT> </o:p>  </P>     <!
 P class=M
: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>/ dtstart </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>/ dtend </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;     ; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>; The following ar!
 e optiona
lass=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>; but MUST NOT occur more than once. </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>/ dtstamp </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb!
 sp; &nbsp
   </SPAN>/ uid </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;     ; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>; The following are optional, </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>; and MAY occur more than once. </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; !
 &nbsp; &n
</FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      </SPAN>/ other-props </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <o:p> <FONT    face=Terminal> &nbsp; </FONT> </o:p>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  <FONT face=Terminal> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  </SPAN> <SPAN    style="mso-spacerun: yes"> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </SPAN>"END"     ":" "VFREEBUSY" CRLF </FONT>  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt">  &nbsp;  </P>     <P class=MsoPlainText style="MARGIN: 0in 0in 0pt"> I look forward to response     and feedback regarding this proposal.  </P>     <P class=MsoPlainText style="MARGIN:!
  0in 0in 
P class=MsoPlainText style="MARGIN: 0in 0in 0pt"> --C  Johnson  </P> </BLOCKQUOTE> </BODY> </HTML>

--Boundary_(ID_V6msix92UoHIzAXxVmIC8Q)--


From owner-ietf-calendar@mail.imc.org  Mon Jul 21 20:24:01 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15782
	for <calsch-archive@lists.ietf.org>; Mon, 21 Jul 2003 20:24:01 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6M04Lqt077988
	for <ietf-calendar-bks@above.proper.com>; Mon, 21 Jul 2003 17:04:21 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6M04LbA077987
	for ietf-calendar-bks; Mon, 21 Jul 2003 17:04:21 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6M04Kqt077977
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 17:04:20 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Mon, 21 Jul 2003 18:02:50 -0600
Message-Id: <sf1c2aca.097@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 21 Jul 2003 18:05:14 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: RE: Cap Free-Busy Request
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part9EC0B0AA.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__Part9EC0B0AA.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Satya Vempati asked:
> Shouldn't there be an FBTYPE in the VREPLY?
 
An FBTYPE is not necessary when the FBTYPE=BUSY.  From RFC 2445:
 
4.2.9 Free/Busy Time Type

   Parameter Name: FBTYPE
 
   . . .                                 If not specified on a
property that allows this parameter, the default is BUSY.

The following would be equivalent:
 
FREEBUSY:20030805T100000Z/20030805T110000ZFREEBUSY;FBTYPE=BUSY:20030805T100000Z/20030805T110000Z

 

--=__Part9EC0B0AA.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML xmlns:st1 = "urn:schemas-microsoft-com:office:smarttags" xmlns:o = "urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Satya Vempati asked:</DIV>
<DIV><SPAN class=390583720-21072003>&gt; Shouldn't there be an FBTYPE in the VREPLY?</SPAN></DIV>
<DIV><SPAN class=390583720-21072003></SPAN><SPAN class=390583720-21072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=390583720-21072003><FONT size=2>An FBTYPE is not necessary when the FBTYPE=BUSY.&nbsp; From RFC 2445:</FONT></SPAN></DIV>
<DIV><SPAN class=390583720-21072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=390583720-21072003><FONT size=2><FONT face=Terminal>4.2.9 Free/Busy Time Type</FONT></FONT></SPAN></DIV><SPAN class=390583720-21072003><FONT size=2><FONT face=Terminal><FONT size=2>
<P>&nbsp;&nbsp; Parameter Name: FBTYPE<BR></P>
<DIV></FONT>&nbsp;</DIV>
<DIV><FONT size=2>&nbsp;&nbsp;&nbsp;. . .&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If not specified on a<BR>property that allows this parameter, the default is BUSY.<BR></FONT></DIV>
<DIV><FONT face=Tahoma>The following would be equivalent:</FONT></DIV>
<DIV><FONT face=Tahoma></FONT>&nbsp;</DIV>
<DIV><FONT face=Tahoma>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>FREEBUSY:20030805T100000Z/20030805T110000Z</FONT></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-FAMILY: 'Courier New'"><FONT face=Terminal>FREEBUSY;FBTYPE=BUSY:20030805T100000Z/20030805T110000Z</FONT></SPAN><BR></P></DIV></FONT></FONT></SPAN>
<DIV><SPAN class=390583720-21072003></SPAN>&nbsp;</DIV></BODY></HTML>
--=__Part9EC0B0AA.0__=--


From owner-ietf-calendar@mail.imc.org  Mon Jul 21 21:01:24 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16389
	for <calsch-archive@lists.ietf.org>; Mon, 21 Jul 2003 21:01:23 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6M0njqt080362
	for <ietf-calendar-bks@above.proper.com>; Mon, 21 Jul 2003 17:49:45 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6M0njrd080361
	for ietf-calendar-bks; Mon, 21 Jul 2003 17:49:45 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6M0niqt080356
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 17:49:44 -0700 (PDT)
	(envelope-from satyanarayana.vempati@Sun.COM)
Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35])
	by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h6M0nkbj014904
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 18:49:46 -0600 (MDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail1sca.SFBay.Sun.COM (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h6M0nkhD027094
	for <ietf-calendar@imc.org>; Mon, 21 Jul 2003 17:49:46 -0700 (PDT)
Received: from pranav.red.iplanet.com (pranav.red.iplanet.com [192.18.144.109])
 by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HIE00DGRIAYBC@ha13sca-mail1.sfbay.sun.com> for
 ietf-calendar@imc.org; Mon, 21 Jul 2003 17:49:46 -0700 (PDT)
Date: Mon, 21 Jul 2003 17:49:47 -0700
From: Satya Vempati <satyanarayana.vempati@Sun.COM>
Subject: RE: Cap Free-Busy Request
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_4_.20030721174947.944G@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Cw3zUW/l+7QHN46C4staBQ)"; DIFFERENCES=Content-Language
Content-language: en-USA
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>



--Boundary_(ID_Cw3zUW/l+7QHN46C4staBQ)
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

Fair enough. Maybe you could just tweak the examples to hightlight both
UPN/Calid & FBTypes considerations to make them clearer.

-----Original Message-----
From: Craig Johnson [mailto:cjohnson@gw.novell.com]
Sent: Monday, July 21, 2003 5:05 PM
To: ietf-calendar@imc.org
Subject: RE: Cap Free-Busy Request


Satya Vempati asked:
> Shouldn't there be an FBTYPE in the VREPLY?
 
An FBTYPE is not necessary when the FBTYPE=BUSY.  From RFC 2445:
 
4.2.9 Free/Busy Time Type
   Parameter Name: FBTYPE


 
   . . .                                 If not specified on a
property that allows this parameter, the default is BUSY.

The following would be equivalent:
 
FREEBUSY:20030805T100000Z/20030805T110000Z

FREEBUSY;FBTYPE=BUSY:20030805T100000Z/20030805T110000Z


 


--Boundary_(ID_Cw3zUW/l+7QHN46C4staBQ)
Content-id: 0
Content-type: TEXT/html; CHARSET=US-ASCII
Content-language: en-USA
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML
xmlns:st1 = "urn:schemas-microsoft-com:office:smarttags" xmlns:o = 
"urn:schemas-microsoft-com:office:office"><HEAD><META content="MSHTML
6.00.2800.1170" name=GENERATOR></HEAD><BODY style="MARGIN: 4px 4px 1px;
FONT: 10pt Tahoma"><DIV>
 <SPAN class=234344600-22072003>Fair enough. Maybe you could just tweak
the  examples to hightlight both UPN/Calid  &amp; FBTypes considerations
to make them  clearer. </SPAN>  </DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">     <DIV
class=OutlookMessageHeader dir=ltr align=left>
 -----Original     Message----- <BR>
 <B>From: </B> Craig Johnson     [mailto:cjohnson@gw.novell.com] <BR>
 <B>Sent: </B> Monday, July 21, 2003 5:05     PM <BR>
 <B>To: </B> ietf-calendar@imc.org <BR>
 <B>Subject: </B> RE: Cap Free-Busy     Request <BR>
 <BR>
  </DIV>
     <DIV>
 Satya Vempati asked:  </DIV>
     <DIV>
  <SPAN class=390583720-21072003> &gt; Shouldn't there be an FBTYPE in the
    VREPLY? </SPAN>  </DIV>
     <DIV>
  <SPAN class=390583720-21072003> </SPAN> <SPAN   
class=390583720-21072003> </SPAN> &nbsp;  </DIV>
     <DIV>
  <SPAN class=390583720-21072003>An FBTYPE is not necessary when the    
FBTYPE=BUSY. &nbsp; From RFC 2445: </SPAN>  </DIV>
     <DIV>
  <SPAN class=390583720-21072003> </SPAN> &nbsp;  </DIV>
     <DIV>
  <SPAN class=390583720-21072003> <FONT face=Terminal>4.2.9 Free/Busy Time
    Type </FONT> </SPAN>  </DIV>
  <SPAN class=390583720-21072003> <FONT face=Terminal>     <P>
 &nbsp; &nbsp; Parameter Name: FBTYPE <BR>
  </P>     <DIV>
  &nbsp;  </DIV>
     <DIV>
  &nbsp; &nbsp; &nbsp;. .     . &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;     If not specified on a <BR>
property that allows this parameter, the default is     BUSY. <BR>
  </DIV>
     <DIV>
  <FONT face=Tahoma>The following would be equivalent: </FONT>  </DIV>
     <DIV>
  <FONT face=Tahoma> </FONT> &nbsp;  </DIV>
     <DIV>
  <FONT face=Tahoma>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">
<SPAN    style="FONT-FAMILY: 'Courier New'"> <FONT   
face=Terminal>FREEBUSY:20030805T100000Z/20030805T110000Z </FONT> </SPAN>
</FONT>  </P>     <P class=MsoNormal style="MARGIN: 0in 0in 0pt">  <SPAN  
 style="FONT-FAMILY: 'Courier New'"> <FONT   
face=Terminal>FREEBUSY;FBTYPE=BUSY:20030805T100000Z/20030805T110000Z
</FONT> </SPAN> <BR>
  </P> </DIV>
 </FONT> </SPAN>     <DIV>
  <SPAN  class=390583720-21072003> </SPAN> &nbsp;  </DIV>
 </BLOCKQUOTE> </BODY> </HTML>

--Boundary_(ID_Cw3zUW/l+7QHN46C4staBQ)--


From owner-ietf-calendar@mail.imc.org  Tue Jul 22 12:41:04 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19179
	for <calsch-archive@lists.ietf.org>; Tue, 22 Jul 2003 12:41:02 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MGN0qt056381
	for <ietf-calendar-bks@above.proper.com>; Tue, 22 Jul 2003 09:23:00 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6MGN0EK056380
	for ietf-calendar-bks; Tue, 22 Jul 2003 09:23:00 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MGMwqt056375
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 09:22:59 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6MGMmYa026883
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 09:22:56 -0700
Message-ID: <3F1D64D3.3000907@Royer.com>
Date: Tue, 22 Jul 2003 10:22:43 -0600
From: Doug Royer <Doug@royer.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: CAP -11
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050200060100080902040902"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms050200060100080902040902
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


As there have been no proposals for fixing the current ABNF, I'll work
on it this weekend.

I intend to submit -11 by Monday (CAP expires in AUG).

As the Craig Johnson is very new, I am going to hold off on it
until the chairs rule on it.


  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms050200060100080902040902
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjIxNjIyNDNaMCMGCSqGSIb3DQEJBDEWBBRz
QE/Eb+1XgETLCliiok4yt7NdPDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQBBcb7jcTstpexqYRSQ3+B7KS+48mAlqQIpxMM82dLzLF38
NA+ohJ0BQydwlO8ronA3ydUR2NBOrXGtXRSnu9SmGmXZEMaGFs9l5XX1Diei0eljvM/c2UVB
L5FK4+8lMn24GUEi61DjWhb1++WSXf99PKXccRoJGouEcl3dCHjOSaOEhcRgiu4uBlm0nC2i
27dItkPJMV7SXZiPs2xbGMpvTUDqvY4yUI5Y48GYedBx98RkSdB9zmKzJSiD3jpyX2/MQ1NY
117U3Df+ojrWRlC8jRCQ4UUV/2yVn3sOostqZNXC53/CrkSmXwbtiRfw9p9P8OO5Eg46i55D
EPeWkub3AAAAAAAA
--------------ms050200060100080902040902--



From owner-ietf-calendar@mail.imc.org  Tue Jul 22 12:41:19 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19201
	for <calsch-archive@lists.ietf.org>; Tue, 22 Jul 2003 12:41:18 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MGGpqt056145
	for <ietf-calendar-bks@above.proper.com>; Tue, 22 Jul 2003 09:16:51 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6MGGpHK056144
	for ietf-calendar-bks; Tue, 22 Jul 2003 09:16:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MGGmqt056139
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 09:16:49 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6MGGYYa026841
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 09:16:42 -0700
Message-ID: <3F1D635C.5080800@Royer.com>
Date: Tue, 22 Jul 2003 10:16:28 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request - vs QUERY?
References: <sf1bd971.016@gw.provo.novell.com>
In-Reply-To: <sf1bd971.016@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms000408010808060803070309"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms000408010808060803070309
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable



Craig Johnson wrote:
>
>=20
> No, I do not suggest we disallow this QUERY.  Such a QUERY is necessary=
=20
> for Calendar Stores that support the VFREEBUSY component.  Allow me=20
> to elaborate on a few distinguishing issues...
>=20
> =20
> 1. Let's make a distinction between "a request for free-busy=20
> information" and "a QUERY for VFREEBUSY components".  This distinction =

> comes clearly into focus when dealing with a Calendar Store that does=20
> not support the VFREEBUSY component.
>=20

After thinking about this, there is no difference. With all other
components they are booked or not. Why should VFREEBUSY be any different?=

This WG decided on dynamically created VFREEBUSY replies from the CS.
It did not decide (as you use in your example below) that they be
kind of static relative to a month (or whatever time frame).


>=20
> Suppose we have a simple Calendar Store that supports VEVENTs but does =

> not support VTODO, VJOURNAL or VFREEBUSY (i.e. VEVENT is on the=20
> COMPONENTS property; VTODO, VJOURNAL and VFREEBUSY are not).  The=20
> Calendar Store is capable of providing free-busy information, but how d=
o=20
> you get it?  A QUERY of VFREEBUSY would be formally invalid because it =

> is not listed on the COMPONENTS property.  Would a QUERY of VTODOs be=20
> valid?  No.  Why would a VFREEBUSY be any different?  Nothing in the CA=
P=20
> spec allows for this incongruency (i.e. no-where does the spec indicate=
=20
> that a Calendar Store must support a QUERY of VFREEBUSY regardless of=20
> whether it is listed on the COMPONENTS property.)

If a CS does not support other components they also can not be returned.
Why make VFREEBUSY an exception? If the CS did not support VFREEBUSY
could I not just do this in a single search command:

	QUERY:SELECT DTSTART,DTEND FROM VEVENT
          WHERE DTSTART >=3D range AND DTEND <=3D range
          AND ( TRANSP =3D 'OPAQUE' OR TRANSP =3D 'OPAQUE-NOCONFLICT' )
	QUERY:SELECT DTSTART,DTEND FROM VTODO
          WHERE DTSTART >=3D range AND DTEND <=3D range
          AND ( TRANSP =3D 'OPAQUE' OR TRANSP =3D 'OPAQUE-NOCONFLICT' )
=09
Which is how I dynamically calculate VFREEBUSY information anyway.
Trimming the results to the CUA's exact start/stop times is trivial.
As is combining the results into blocks of time and forming a VFREEBUSY
component from those results.

> This is avoided by making SEARCH/VFREEBUSY the way to "request free-bus=
y=20
> information".  It works regardless of how the Calendar Store keeps trac=
k=20
> of "free-busy" information (i.e. whether or not it supports the=20
> VFREEBUSY component).  SEARCH/VQUERY only works for Calendar Stores tha=
t=20
> support the VFREEBUSY object.

Why should a 'BOOKED' VFREEBUSY be any different than any other component=
?

> 2.  A SEARCH/VQUERY may not return the same information as a=20
> SEARCH/VFREEBUSY (although both will return the needed information).

As this WG has decided on dynamic VFREEBUSY replies, why do you
think they would not satisfy the QUERY? Do you envision that
each CALOWNERs CUA will deposit exactly the correct VFREEBUSY information=

for each month into the CS? It is my understanding that this WG decided
that the VFREEBUAY replies be dynamic, so that would then be useless. So =
where
would these replies come from? And who would use the static results
that you example below (month boundary)?

> Suppose we have a Calendar Store that supports the VFREEBUSY component.=
 =20
> Within a VAGENDA there is a VFREEBUSY object for each month containing =

> FREEBUSY properties for busy times in that month.  Now, suppose I need =

> free-busy information for a particular week=85

Bruces assertion was that booked VFREEBUSY entries are calculated and not=

stored.  You are proposing two booked VFREEBUSY dynamic component replies=
=2E
Please explain why a CUA would want each of the two. Then maybe I can
understand the difference.

> - A SEARCH/VQUERY would find the VFREEBUSY object(s) that overlap the=20
> week of interest.  The VFREEBUSY object would be returned with FREEBUSY=
=20
> properties for the entire month ,not just FREEBUSY properties for the r=
equested week.

The entire proposal on this list was for a dynamic VFREEBUSY, your
assertion assumes that they are not dynamic. So you invented a second
type of VFREEBUSY. Correct?

> - A SEARCH/VFREEBUSY would also find the VFREEBUSY object(s) that=20
> overlap the week of interest.  However, in creating a response, the=20
> SEARCH/VFREEBUSY can include only FREEBUSY properties overlapping the=20
> week of interest and others can be left out.

Why not just declare that booked VFREEEBUSY's return what the CUA
asks for in the QUERY and in the time range specified in the QUERY?
If VFREEBUSY replies are dynamic as this WG wants, then 100% of
all VFREEBUSY components stored into the TARGET can be thrown away
and ignored anyway. They would NEVER be fetched as this WG wants
dynamic VFREEBUSY replies.

The only thing that I can think of is if a CUA wished to add
blocked out time to a TARGET by storing a VFREEBUSY. But there
would be no way to undo or change the contents of one once
stored. That should be on the 'do not do that' list.

Can anyone think of any reason that a CUA would want a static
booked VFREEBUSY reply when a dynamic one that is guaranteed to represent=

the state of the TARGET is available?

> The addition of STATE() =3D 'BOOKED' is necessary to avoid retrieving=20
> 'unprocessed' VFREEBUSY records that may be present in the VAGENDA.

Yes - thanks.
And with dynamic VFREEBUSY replies 100% of all non-booked VFREEBUSY
components can be ignored and never stored by the CS - correct?

> QUERY is a 'nuts and bolts' way of getting information; powerful and=20
> flexible ... but inherently complex.  In contrast, a 'VFREEBUSY request=
'=20
> is a 'high level' operation; very specific ...  but simple.

The VFREEBUSY component was invented because iMIP is not real time and
a CUA needed to be able to make best guess as scheduling on the first
attempt. Having the CS dynamically create a VFREEBUSY seems to be
what this WG wants. I do not see that having two kinds of dynamically
created VFREEBUSY replies is useful.


--=20

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms000408010808060803070309
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjIxNjE2MjhaMCMGCSqGSIb3DQEJBDEWBBTA
bJ7/fybi9PAI2zaQGWWJk26qDjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQCxUtGOuG8NnNUHe7TJHRsF16ZnZjYnFtBLEKjU57vZ27r8
QqTqi+9YdCEcqZo+Wihb6/yI5/PQVkLboQShrrt2TFQ0nk/HLluLIZMAYOlEzH7OzAStwnOL
1IL/OhhjFl/YFeGRYjymHdMYIfT4KTlydrYGi6NS33dbbgluJZ9vGDMSIzk801ZVqOB6eurj
TR+b1m164uorqIXudBuqWrh+V1Eql6TqFA4K0z9oDp8zxKiIE1dPmmXOR4NW380WphUG9SFm
sl+xgftHipyyEO9QE6TQP7oCqTcHCD9Cv5qe/5IiP/s80luyunhiiRrOOPKWFJSoaOf+i+By
53yByK9zAAAAAAAA
--------------ms000408010808060803070309--



From owner-ietf-calendar@mail.imc.org  Tue Jul 22 17:05:21 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26891
	for <calsch-archive@lists.ietf.org>; Tue, 22 Jul 2003 17:05:21 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MKrTqt070343
	for <ietf-calendar-bks@above.proper.com>; Tue, 22 Jul 2003 13:53:29 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6MKrTeI070342
	for ietf-calendar-bks; Tue, 22 Jul 2003 13:53:29 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MKrSqt070334
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 13:53:28 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Tue, 22 Jul 2003 14:51:43 -0600
Message-Id: <sf1d4f7f.068@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 22 Jul 2003 14:54:01 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request - vs QUERY?
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part97C9B879.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__Part97C9B879.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I shall attempt to respond to some of Dougs questions in another post. =20
But to keep things focused on a CAP method for obtaining free/busy =
information, consider the following that have been presented:
=20
1.
BEGIN:VQUERY
QUERY:SELECT DTSTART,DTEND,FREEBUSY FROM VFREEBUSY WHERE DTEND >=3D =
'end-range'  AND DTSTART <=3D 'start-range'  AND STATE() =3D 'BOOKED'END:VQ=
UERY
=20
2.
BEGIN:VQUERY
QUERY:SELECT DTSTART,DTEND FROM VEVENT
 WHERE DTSTART >=3D range? AND DTEND <=3D range?
  AND ( TRANSP =3D 'OPAQUE' OR TRANSP =3D 'OPAQUE-NOCONFLICT' )
  AND STATE() =3D 'BOOKED'
END:VQUERY
=20
3.
BEGIN:VFREEBUSY
DTSTART:start-range
DTEND:end-range
END:VFREEBUSY
=20
Which of these methods is the most simple?
Which most clearly and unambiguously expresses the request?
Which is most consistent with iTIP?
=20
If you had to vote, which would you prefer?
=20
Give me door number 3, please.
=20
* C Johnson

=20

--=__Part97C9B879.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>I shall attempt to respond&nbsp;to some of Dougs questions in another =
post.&nbsp; </DIV>
<DIV>But to keep things focused on a CAP method&nbsp;for obtaining =
free/busy information,&nbsp;consider the following that have been =
presented:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1.</DIV>
<DIV><FONT face=3DTerminal>BEGIN:VQUERY</FONT></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><FONT size=3D2><F=
ONT face=3DTerminal>QUERY:SELECT DTSTART,DTEND,FREEBUSY FROM VFREEBUSY<?xml=
:namespace prefix =3D o ns =3D "urn:schemas-microsoft-com:office:office" =
/><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><FONT size=3D2><F=
ONT face=3DTerminal>&nbsp;WHERE DTEND &gt;=3D 'end-range'<o:p></o:p></FONT>=
</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><FONT size=3D2><F=
ONT face=3DTerminal>&nbsp; AND DTSTART &lt;=3D 'start-range'<o:p></o:p></FO=
NT></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><FONT size=3D2><F=
ONT face=3DTerminal>&nbsp; AND STATE() =3D 'BOOKED'</FONT></FONT></SPAN></P=
><FONT face=3DTerminal>END:VQUERY</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2>2.</FONT></FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>BEGIN:VQUERY</FONT></FONT></FONT>=
</DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>QUERY:SELECT DTSTART,DTEND FROM =
VEVENT</FONT></FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>&nbsp;WHERE DTSTART &gt;=3D =
range? AND DTEND &lt;=3D range?</FONT></FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>&nbsp; AND ( TRANSP =3D 'OPAQUE' =
OR TRANSP =3D 'OPAQUE-NOCONFLICT' )</FONT></FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>&nbsp; AND STATE() =3D 'BOOKED'</=
FONT></FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>END:VQUERY</FONT></FONT></FONT></=
DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2>3.</FONT></FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>BEGIN:VFREEBUSY</FONT></FONT></FO=
NT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>DTSTART:start-range</FONT></FONT>=
</FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>DTEND:end-range</FONT></FONT></FO=
NT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2>END:VFREEBUSY</FONT></FONT></FONT=
></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT face=3DTerminal size=3D2></FONT></FONT></FONT>&nbsp;</DIV>=

<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2>Which of these methods is the most simple?</FONT>=
</FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft>Which most clearly =
and unambiguously expresses the request?</DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2>Which&nbsp;is most consistent with iTIP?</FONT></=
FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft>&nbsp;</DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2>If you had to vote, which&nbsp;would you =
prefer?</FONT></FONT></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2>Give me door number 3, please.</FONT></FONT></FON=
T></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><FONT size=3D1><FON=
T size=3D1><FONT size=3D2>=97 C Johnson</FONT></DIV>
<P></FONT><FONT size=3D2></FONT>&nbsp;</P></FONT></BODY></HTML>

--=__Part97C9B879.0__=--


From owner-ietf-calendar@mail.imc.org  Tue Jul 22 18:14:25 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29039
	for <calsch-archive@lists.ietf.org>; Tue, 22 Jul 2003 18:14:24 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MM4Sqt074837
	for <ietf-calendar-bks@above.proper.com>; Tue, 22 Jul 2003 15:04:28 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6MM4Si1074836
	for ietf-calendar-bks; Tue, 22 Jul 2003 15:04:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MM4Qqt074817
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 15:04:26 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: Doug Royer <Doug@royer.com>
Cc: "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: Re: CAP -11
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF621DBBEE.C1D95837-ON85256D6B.00792A98-85256D6B.007941BE@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Tue, 22 Jul 2003 18:04:26 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/22/2003 06:04:29 PM,
	Serialize complete at 07/22/2003 06:04:29 PM
Content-Type: multipart/alternative; boundary="=_alternative 007941B485256D6B_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 007941B485256D6B_=
Content-Type: text/plain; charset="us-ascii"

Actually, the chair's don't rule on this - the list does.  We need more 
feedback from the list.  Is Craig's proposal ok?  If I don't hear back 
that it's wrong - then do I read a "nod" from everyone that it's ok to be 
added?  List?




Doug Royer <Doug@royer.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/22/2003 12:22

 
        To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
        cc: 
        Subject:        CAP -11



As there have been no proposals for fixing the current ABNF, I'll work
on it this weekend.

I intend to submit -11 by Monday (CAP expires in AUG).

As the Craig Johnson is very new, I am going to hold off on it
until the chairs rule on it.


  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards



--=_alternative 007941B485256D6B_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Actually, the chair's don't rule on this - the list does. &nbsp;We need more feedback from the list. &nbsp;Is Craig's proposal ok? &nbsp;If I don't hear back that it's wrong - then do I read a &quot;nod&quot; from everyone that it's ok to be added? &nbsp;List?</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Doug Royer &lt;Doug@royer.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/22/2003 12:22</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;CAP -11</font></table>
<br>
<br>
<br><font size=2><tt><br>
As there have been no proposals for fixing the current ABNF, I'll work<br>
on it this weekend.<br>
<br>
I intend to submit -11 by Monday (CAP expires in AUG).<br>
<br>
As the Craig Johnson is very new, I am going to hold off on it<br>
until the chairs rule on it.<br>
<br>
<br>
 &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
 &nbsp;-------------------------------|-----------------------------<br>
 &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
 &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards - You Need Standards<br>
</tt></font>
<br>
<br>
--=_alternative 007941B485256D6B_=--


From owner-ietf-calendar@mail.imc.org  Tue Jul 22 18:42:05 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29708
	for <calsch-archive@lists.ietf.org>; Tue, 22 Jul 2003 18:42:04 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MMWwqt077938
	for <ietf-calendar-bks@above.proper.com>; Tue, 22 Jul 2003 15:32:58 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6MMWwI0077937
	for ietf-calendar-bks; Tue, 22 Jul 2003 15:32:58 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6MMWvqt077932
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 15:32:57 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6MMWlEB030080
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 15:32:55 -0700
Message-ID: <3F1DBB8A.6010504@Royer.com>
Date: Tue, 22 Jul 2003 16:32:42 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request - vs QUERY?
References: <sf1d4f7f.068@gw.provo.novell.com>
In-Reply-To: <sf1d4f7f.068@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060705000307020507000002"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060705000307020507000002
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


I vote for do not invent jet another QUERY.
    We would just need to add text saying 'do it this way'.

#1 Can be done right now - no change to CAP needed.
    I vote for #1

#2 Can be done right now - no change to CAP needed.
    In fact, you can not stop a CUA from doing this.

#3 Looks like a VFEEBUSY, but it is not.
    It is also NOT an iTIP VFREEBUSY REQUEST/REPLY.

    From iTIP:

      The busy time information within the iCalendar object MAY be grouped
      into more than one "VFREEBUSY" calendar component. This capability
      allows busy time periods to be grouped according to some common
      periodicity, such as a calendar week, month, or year. In this case,
      each "VFREEBUSY" calendar component MUST include the "ATTENDEE",
      "DTSTART" and "DTEND" properties in order to specify the source of
      the busy time information and the date and time interval over which
      the busy time information covers.

    So the CS MAY round to the nearest week, month, or year anyway.
    No functional gain from #1 or #2

#4 Another way would be to allow the CUA to deposit an iTIP
    VFREEBUSY REQUEST (as documented in iTIP) and then the next SEARCH
    for VFREEBUSY by the UPN (searching for a ORGANIZER with a matching
    value) and then provide the VFREEBUSY REPLY. Then it is EXACTLY like iTIP.
    However this requires two full round trips.

    Do we need to support VFREEBUSY REQUEST/REPLY at the CS? Or
    can be specify that the CUA takes those objects and just
    queries the CS?

I think that CAP is no longer open to new ideas, but how to close
CAP and ship it. #1 and #2 require no change to CAP. #3 requires
a new idea to be added to CAP. And #3 adds another way to
do the same thing that can already be done.

#3 may look prettier, but its not more functional.

Craig Johnson wrote:
> I shall attempt to respond to some of Dougs questions in another post. 
> But to keep things focused on a CAP method for obtaining free/busy 
> information, consider the following that have been presented:
>  
> 1.
> BEGIN:VQUERY
> 
> QUERY:SELECT DTSTART,DTEND,FREEBUSY FROM VFREEBUSY
> 
>  WHERE DTEND >= 'end-range'
> 
>   AND DTSTART <= 'start-range'
> 
>   AND STATE() = 'BOOKED'
> 
> END:VQUERY
>  
> 2.
> BEGIN:VQUERY
> QUERY:SELECT DTSTART,DTEND FROM VEVENT
>  WHERE DTSTART >= range? AND DTEND <= range?
>   AND ( TRANSP = 'OPAQUE' OR TRANSP = 'OPAQUE-NOCONFLICT' )
>   AND STATE() = 'BOOKED'
> END:VQUERY
>  
> 3.
> BEGIN:VFREEBUSY
> DTSTART:start-range
> DTEND:end-range
> END:VFREEBUSY
>  
> Which of these methods is the most simple?

We are trying to close CAP, not invent new methods.
So 'simple' is not high priority.

> Which most clearly and unambiguously expresses the request?

Just an opinion.

> Which is most consistent with iTIP?

None of them are iTIP compliant and existing iTIP
releases would choke on them.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060705000307020507000002
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjIyMjMyNDJaMCMGCSqGSIb3DQEJBDEWBBS1
lIUDxLnrKxE0IXhqq4q1hip9IjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQB5tqIdQ8avCJx7WVAFPBiNUlruAAxtjNr6wn/+PW7aHMuf
CJOG8aq5QLgebFc+50Ewxy8Fqvg9rZgdpE0IFpQcIhGdn5zoo/utYtlyO0FL+kKzAvcU+0kE
ivuHQweMTZ1kPB8NaDRKs6uxw1o15TRwsI1y76PbsqPiFcjNI89Xq231ZIraCYNxNyIVzVWL
gQqhwPuIvCNz1hsobkqeyn0kcs1keSdkQybXUDgKYthrbzoNmGnCXyg/pucTKeg1mgrzzteJ
uSGBajc1v8b3Yt5hMdUvxG9Cdc6+Nnffmi+3lWLS4uMJsk0RR7CprFz+KPK51mzEVBhWTuwJ
DN0pFaJaAAAAAAAA
--------------ms060705000307020507000002--



From owner-ietf-calendar@mail.imc.org  Wed Jul 23 00:46:22 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05561
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 00:46:20 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6N4WJqt088177
	for <ietf-calendar-bks@above.proper.com>; Tue, 22 Jul 2003 21:32:19 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6N4WJ0s088176
	for ietf-calendar-bks; Tue, 22 Jul 2003 21:32:19 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6N4WIqt088170
	for <ietf-calendar@imc.org>; Tue, 22 Jul 2003 21:32:18 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Tue, 22 Jul 2003 22:30:43 -0600
Message-Id: <sf1dbb13.085@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 22 Jul 2003 22:33:12 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request - vs QUERY?
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part411F6D18.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__Part411F6D18.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

In Doug's response, his VFREEBUSY 'models' for a Calendar Store were not =
the same as I was describing.  Hence, many unnecessary questions, =
misunderstanding and confusion.  Allow me to attempt to clarify and =
differentiate . . . Between Doug and I, I identified at least 4 models =
regarding how a Calendar Stores might deal with VFREEBUSY components: A.  =
VFREEBUSY appears on the COMPONENTS property; VFREEBUSY components are =
static/real entities. [Doug seemed surprised at this model, but it has =
been discussed several times in previous threads.  Because VFREEBUSY is =
treated on an equally plane with VEVENT, VTODO, and VJOURNAL it is the =
most logical model one might derive from a casual reading of the spec.]
B.  VFREEBUSY appears on the COMPONENTS property; VFREEBUSY components are =
dynamic.
C.  VFREEBUSY does not appear on the COMPONENTS property; VFREEBUSY =
components are not supported; however, the Calendar Store is capable of =
providing free-busy information (read on for further clarification**).
D.  VFREEBUSY does not appear on the COMPONENTS property; VFREEBUSY =
components are not supported; it cannot provide VFREEBUSY components or =
free-busy information.
=20
    The models I was referring to are A and C.  The model Doug primarily =
refered to is B; he questioned the viability of A; and thought my Model C =
was Model D.
    Model A maintains some or all free-busy information within static/real =
VFREEBUSY objects.  Past threads discussed issues and complexities =
involved with maintaining such data.  Doug's response asserted in several =
places that the "WG decided that VFREEBUSY be generated dynamically".  Did =
that also mean that Model A is dead?  That no-one should implement Model =
A?  Or did it simply mean that Model B is preferred?    Model B and C are =
actually quite similar.  They both dynamically provide VFREEBUSY informatio=
n.  The key difference is the presence/absence of VFREEBUSY on the =
COMPONENTS property and the implications of what that means.    What does =
it mean when VFREEBUSY (or any other component) is listed on the COMPONENTS=
 property?  The spec simply states that if a component appears on the =
COMPONENTS property then the component is "supported by the endpoint".  =
What does "supported" mean?    One defition is that "supported" means that =
I can CREATE the component; also MODIFY, DELETE, MOVE and SEARCH the =
component (using VQUERY with 'SELECT component-name').  What in the spec =
tells me I can do some but not all these operations on a component?  =
Nothing in the spec differentiates what "support" means for VEVENT, VNOTE, =
VJOURNAL  vs  VFREEBUSY.  Nothing in the spec regarding GET-CAPABILITIES =
provides 'finer' granularity to say something like "you can SEARCH, but =
cannot CREATE, MODIFY, DELETE or MOVE".  "Supported" seems like an all or =
nothing deal (unless we change the spec).    This inconsistency was =
encountered while attempting to implement a Type B Calendar Store.  I =
could conceivably do a SEARCH/VQUERY, but I could not CREATE, DELETE, or =
MODIFY of 'dynamic' VFREEBUSY components.  That's what compelled me to =
Model C.    **For Model C and D  VFREEBUSY is not a supported component.  =
A strict interpretation might be "you cannot send/receive any VFREEBUSY =
object from the endpoint" (Model D).  A less strict interpretation is that =
the component is not supported, meaning "you cannot CREATE, MODIFY, DELETE =
or SEARCH for VFREEBUSY (ie use VFREEBUSY in a VQUERY SELECT clause)" =
(Model C).  The SPEC does not provide much clarity regarding these two =
interpretations, but I chose the latter.  But, whether you accept this =
interpretation or not is inconsequential to my proposal.     This resolved =
the issues with CREATE, DELETE, MODIFY, and the complexities of trying to =
interpret the SEARCH/VQUERY criteria and applying that to dynamic =
VFREEBUSY components.  But, then, how do I get free-busy information?  A =
VFREEBUSY request (dtstart, dtend) was the answer.  It turns out that a =
VFREEBUSY request also works for models A and B* and is much simpler* and =
doesn't deal with the inconsistencies described above. With the above =
explanations in mind, I can response to some of Doug's questions and =
comments: D Royer Wrote:

> Craig Johnson wrote:
> >
> >=20
> > No, I do not suggest we disallow this QUERY.  Such a QUERY is =
necessary=20
> > for Calendar Stores that support the VFREEBUSY component.  Allow me=20
> > to elaborate on a few distinguishing issues...
> >=20
> > =20
> > 1. Let's make a distinction between "a request for free-busy=20
> > information" and "a QUERY for VFREEBUSY components".  This distinction=
=20
> > comes clearly into focus when dealing with a Calendar Store that =
does=20
> > not support the VFREEBUSY component.
> >=20
>=20
> After thinking about this, there is no difference. With all other
> components they are booked or not. Why should VFREEBUSY be any different?=
 The difference is a "high level" request for free-busy information vs a =
"low level" query of VFREEBUSY objects (whether dynamic or static).The =
"high-level" request shields the CUA from idiosyncrasies inherent in =
"dynamic vs static" implementations.  It works with all models.  It is =
much simpler to understand and implement.I'm somewhat confident the =
"low-level" approach can produce the same information... if it is =
correctly constructed.
> This WG decided on dynamically created VFREEBUSY replies from the CS. =
I'm all for that.  My proposal is consistent with that.
> It did not decide (as you use in your example below) that they be
> kind of static relative to a month (or whatever time frame). Again, is =
Model A 'dead'?The example was derived from a previous thread that =
discussed possible implementations and implications for static VFREEBUSY =
objects.  I do not mean to imply that that is the way it should be done* =
but to illustrate differences in the reply between using a "high-level" =
and "low-level" method for getting free-busy data.  If Model A is not =
supported* then say so in the spec.
> >=20
> > Suppose we have a simple Calendar Store that supports VEVENTs but =
does=20
> > not support VTODO, VJOURNAL or VFREEBUSY (i.e. VEVENT is on the=20
> > COMPONENTS property; VTODO, VJOURNAL and VFREEBUSY are not).  The=20
> > Calendar Store is capable of providing free-busy information, but how =
do=20
> > you get it?  A QUERY of VFREEBUSY would be formally invalid because =
it=20
> > is not listed on the COMPONENTS property.  Would a QUERY of VTODOs =
be=20
> > valid?  No.  Why would a VFREEBUSY be any different?  Nothing in the =
CAP=20
> > spec allows for this incongruency (i.e. no-where does the spec =
indicate=20
> > that a Calendar Store must support a QUERY of VFREEBUSY regardless =
of=20
> > whether it is listed on the COMPONENTS property.)
>=20
> If a CS does not support other components they also can not be returned.
> Why make VFREEBUSY an exception?  You are thinking "Model D".  I am =
thinking "Model C".  VFREEBUSY is not an exception for Model C. > If the =
CS did not support VFREEBUSY
> could I not just do this in a single search command:
>=20
>          QUERY:SELECT DTSTART,DTEND FROM VEVENT
>           WHERE DTSTART >=3D range AND DTEND <=3D range
>           AND ( TRANSP =3D 'OPAQUE' OR TRANSP =3D 'OPAQUE-NOCONFLICT' )
>          QUERY:SELECT DTSTART,DTEND FROM VTODO
>           WHERE DTSTART >=3D range AND DTEND <=3D range
>           AND ( TRANSP =3D 'OPAQUE' OR TRANSP =3D 'OPAQUE-NOCONFLICT' )
>         =20
> Which is how I dynamically calculate VFREEBUSY information anyway.
> Trimming the results to the CUA's exact start/stop times is trivial.
> As is combining the results into blocks of time and forming a VFREEBUSY
> component from those results. A CUA might encounter VCAR rights problems =
trying to issue the above commands.  But, Model C allows free-busy request =
so it isn't necessary to resort to a request against VEVENTs. Does your CS =
issue this command to itself?  Seems like it would be trivial to convert a =
VFREEBUSY request (dtstart, dtend) into this form.  It does not seem as =
trivial to convert a VQUERY of VFREEBUSY components, with all the =
potential variations and permutations of the query criteria, into this =
form.  (Another compelling reason I moved from Model B to Model C).
>=20
> > This is avoided by making SEARCH/VFREEBUSY the way to "request =
free-busy=20
> > information".  It works regardless of how the Calendar Store keeps =
track=20
> > of "free-busy" information (i.e. whether or not it supports the=20
> > VFREEBUSY component).  SEARCH/VQUERY only works for Calendar Stores =
that=20
> > support the VFREEBUSY object.
>=20
> Why should a 'BOOKED' VFREEBUSY be any different than any other =
component?Sorry.  I'm lost on what your question is here.  I think it's a =
Model C/Model D issue.  That makes it moot.
> > 2.  A SEARCH/VQUERY may not return the same information as a=20
> > SEARCH/VFREEBUSY (although both will return the needed information).
>=20
> As this WG has decided on dynamic VFREEBUSY replies, why do you
> think they would not satisfy the QUERY? I said "both will return the =
needed information".  I think that is the same as saying "they will =
satisfy the query" I believe for Model B and C the same information will =
be returned.  Model A can potentially be different, although it may be the =
same. > Do you envision that
> each CALOWNERs CUA will deposit exactly the correct VFREEBUSY information=

> for each month into the CS? It is my understanding that this WG decided
> that the VFREEBUAY replies be dynamic, so that would then be useless. So =
where
> would these replies come from? And who would use the static results
> that you example below (month boundary)  Again, I am not trying to imply =
how a Model A calendar store might organize its static VFREEBUSY data.  =
Ideas for that were discussed on previous threads.  They are presented =
here only to show potential differences between FREEBUSY responses of =
Model A and that of Model B/C. Model B and C do provide 'dynamic' data, =
consistent with the WG decision (which, BTW, is not reflected in the =
spec).
>=20
> > Suppose we have a Calendar Store that supports the VFREEBUSY component.=
 =20
> > Within a VAGENDA there is a VFREEBUSY object for each month containing=
=20
> > FREEBUSY properties for busy times in that month.  Now, suppose I =
need=20
> > free-busy information for a particular week*
>=20
> Bruces assertion was that booked VFREEBUSY entries are calculated and =
not
> stored.  You are proposing two booked VFREEBUSY dynamic component =
replies.
> Please explain why a CUA would want each of the two. Then maybe I can
> understand the difference.Again, a Model A vs Model B/C issue.
> > - A SEARCH/VQUERY would find the VFREEBUSY object(s) that overlap =
the=20
> > week of interest.  The VFREEBUSY object would be returned with =
FREEBUSY=20
> > properties for the entire month ,not just FREEBUSY properties for the =
requested week.
>=20
> The entire proposal on this list was for a dynamic VFREEBUSY, your
> assertion assumes that they are not dynamic. So you invented a second
> type of VFREEBUSY. Correct? No.  Didn't invent anything.  Just describing=
 model A (as per previous threads).
>=20
> > - A SEARCH/VFREEBUSY would also find the VFREEBUSY object(s) that=20
> > overlap the week of interest.  However, in creating a response, the=20
> > SEARCH/VFREEBUSY can include only FREEBUSY properties overlapping =
the=20
> > week of interest and others can be left out.
>=20
> Why not just declare that booked VFREEEBUSY's return what the CUA
> asks for in the QUERY and in the time range specified in the QUERY?
> If VFREEBUSY replies are dynamic as this WG wants, then 100% of
> all VFREEBUSY components stored into the TARGET can be thrown away
> and ignored anyway. They would NEVER be fetched as this WG wants
> dynamic VFREEBUSY replies.If you don't support Type A then that would be =
true.
> The only thing that I can think of is if a CUA wished to add
> blocked out time to a TARGET by storing a VFREEBUSY. But there
> would be no way to undo or change the contents of one once
> stored. That should be on the 'do not do that' list.Now, you are saying =
I cannot do a CREATE, MODIFY, DELETE of VFREEBUSY components; that =
VFREEBUSY is different than the other components.  Where is that in the =
spec?  What operations are possible with the VFREEBUSY component?  Only =
SEARCH/VQUERY?  If that's the case, I have another proposal in mind.
> Can anyone think of any reason that a CUA would want a static
> booked VFREEBUSY reply when a dynamic one that is guaranteed to =
represent
> the state of the TARGET is available?If you support Model A you have to =
expect static booked VFREEBUSY replies (perhaps along with some dynamically=
 generated ones).  Yes, there are many complications involved to support =
Model A. =20
> > The addition of STATE() =3D 'BOOKED' is necessary to avoid retrieving=
=20
> > 'unprocessed' VFREEBUSY records that may be present in the VAGENDA.
>=20
> Yes - thanks.
> And with dynamic VFREEBUSY replies 100% of all non-booked VFREEBUSY
> components can be ignored and never stored by the CS - correct? Not =
correct.  Whether or not they are stored depends on the CS and CUA... and =
non-booked (ie unprocessed) VFREEBUSY components usually have little to do =
with 'dynamic' VFREEBUSY components.There are two types of "unprocessed" =
VFREEBUSY objects that may show up in your VAGENDA:  (1) a request for =
your free-busy time (an iTIP request), and (2) a response to a free-busy =
request that you made (an iTIP reply).  A request might be handled =
immediately by the CS and not stored; but if it's handled by a CUA or =
CUA-BOT it will be stored until it gets handled.  A response would be =
stored until a CUA retrieves and deletes it.It seems necessary that =
"unprocessed" vs "booked" needs to be specified in VFREEBUSY SEARCH/VQUERY =
operations.  With my proposal it is not necessary; it is implied we are =
dealing with "booked" entities. >=20
> > QUERY is a 'nuts and bolts' way of getting information; powerful =
and=20
> > flexible ... but inherently complex.  In contrast, a 'VFREEBUSY =
request'=20
> > is a 'high level' operation; very specific ...  but simple.
>=20
> The VFREEBUSY component was invented because iMIP is not real time and
> a CUA needed to be able to make best guess as scheduling on the first
> attempt. Having the CS dynamically create a VFREEBUSY seems to be
> what this WG wants. Again, we agree on this point!  Dynamically created =
VFREEBUSY is the preferred way to go.  My proposal supports this!  There =
is no issue about that. > I do not see that having two kinds of dynamically=

> created VFREEBUSY replies is useful.
There are not two kinds of dynamic VFREEBUSY replies.  Only one.  However, =
there are two proposed ways of making the request.  One simple, one not. =
One easy to understand, one not.  One easy to implement, one not as easy. =
My proposal has been implemented and running on a preliminary CAP =
implementation for over two months... with great success and acceptance.  =
More on this in another post...

--=__Part411F6D18.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">In Doug's&nbsp;r=
esponse, his VFREEBUSY =91models=92 for a Calendar Store&nbsp;were not the =
same as I was describing.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Hence,&nbsp;many unnecessary questions, misunderstanding and =
confusion.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Allow me to =
attempt to clarify and differentiate . . .<?xml:namespace prefix =3D o ns =
=3D "urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p=
></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Between Doug =
and I, I identified at least 4 models&nbsp;regarding how a Calendar Stores =
might deal with VFREEBUSY components:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p=
></SPAN></P>
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align:=
 none; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Tahoma">A.&nbsp; VFREEBUSY appears on the =
COMPONENTS property; VFREEBUSY components are static/real entities. [Doug =
seemed surprised at this model, but it has been discussed several times in =
previous threads.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Because =
VFREEBUSY is treated on an equally plane with VEVENT, VTODO, and VJOURNAL =
it is the most logical model one might derive from a casual reading of the =
spec.]<o:p></o:p></SPAN></DIV>
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align:=
 none; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Tahoma">B.&nbsp; VFREEBUSY appears on the =
COMPONENTS property; VFREEBUSY components are dynamic.</SPAN></DIV>
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align:=
 none; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Tahoma">C.&nbsp; VFREEBUSY does not appear on the =
COMPONENTS property; VFREEBUSY components are not supported; however, the =
Calendar Store is capable of providing free-busy information (read on for =
further clarification**).<o:p></o:p></SPAN></DIV>
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align:=
 none; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Tahoma">D.&nbsp; VFREEBUSY does not appear on the =
COMPONENTS property; VFREEBUSY components are not supported; it cannot =
provide VFREEBUSY components or free-busy information.</SPAN></DIV>
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align:=
 none; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Tahoma"></SPAN>&nbsp;</DIV>
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align:=
 none; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Tahoma">&nbsp;&nbsp;&nbsp; The models I was =
referring to are A and C.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>The model&nbsp;Doug primarily refered to is B;&nbsp;he questioned =
the viability of A;&nbsp;and thought my Model C was&nbsp;Model&nbsp;D.</SPA=
N></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">&nbsp;&nbsp;&nbs=
p; Model A maintains some or all free-busy information within static/real =
VFREEBUSY objects.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Past =
threads discussed issues and complexities involved with maintaining such =
data.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Doug=92s response =
asserted in several places that the =93WG decided that VFREEBUSY be =
generated dynamically=94.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Did that also mean that Model A is dead?<SPAN style=3D"mso-spacerun:=
 yes">&nbsp; </SPAN>That no-one should implement Model A?<SPAN style=3D"mso=
-spacerun: yes">&nbsp; </SPAN>Or did it simply mean that Model B is =
preferred?</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN style=3D"m=
so-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>Model B and C are actually =
quite similar.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>They both =
dynamically provide VFREEBUSY information.<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>The key difference is the presence/absence of VFREEBUSY =
on the COMPONENTS property and the implications of what that means.<o:p></o=
:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN style=3D"m=
so-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>What does it mean when =
VFREEBUSY (or any other component) is listed on the COMPONENTS property?<SP=
AN style=3D"mso-spacerun: yes">&nbsp; </SPAN>The spec simply states that =
if a component appears on the COMPONENTS property then the component is =
=93supported by the endpoint=94.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>What does =93supported=94 mean?<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN style=3D"m=
so-spacerun: yes">&nbsp;&nbsp;&nbsp; One defition is that&nbsp;</SPAN>=93su=
pported=94 means that I can CREATE the component; also MODIFY, DELETE, =
MOVE and SEARCH the component (using VQUERY with =91SELECT component-name=
=92).<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>What in the spec =
tells me I can do <U>some</U> but not <U>all</U> these operations on a =
component?<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Nothing in the =
spec differentiates what&nbsp;"support" means for&nbsp;VEVENT, VNOTE, =
VJOURNAL&nbsp; vs&nbsp;&nbsp;VFREEBUSY.<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>Nothing in the spec regarding GET-CAPABILITIES provides =
=91finer=92 granularity to say something like =93you can SEARCH, but =
cannot CREATE, MODIFY, DELETE or MOVE=94.<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>=93Supported=94 seems like an all or nothing deal =
(unless we change the spec).<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN style=3D"m=
so-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>This inconsistency was =
encountered while&nbsp;attempting to implement a Type B Calendar Store.<SPA=
N style=3D"mso-spacerun: yes">&nbsp; </SPAN>I could conceivably do a =
SEARCH/VQUERY, but I could not CREATE, DELETE, or MODIFY of =91dynamic=92 =
VFREEBUSY components. <SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>That=
=92s what compelled me to Model C.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN style=3D"m=
so-spacerun: yes">&nbsp;&nbsp;&nbsp; **</SPAN>For Model C and D&nbsp; =
VFREEBUSY is not a supported component.<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>A strict interpretation might be =93you cannot =
send/receive any VFREEBUSY object from the endpoint=94 (Model D).<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>A less strict interpretation is =
that the component is not supported,&nbsp;meaning =93you cannot CREATE, =
MODIFY, DELETE or SEARCH for VFREEBUSY (ie use VFREEBUSY in a VQUERY =
SELECT clause)=94 (Model C).<SPAN style=3D"mso-spacerun: yes">&nbsp; The =
SPEC</SPAN> does not provide&nbsp;much clarity regarding these two =
interpretations, but I chose the latter.&nbsp; But, whether you accept =
this interpretation or not&nbsp;is inconsequential to my proposal.</SPAN></=
P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN style=3D"m=
so-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>This resolved the issues =
with CREATE, DELETE, MODIFY, and the complexities of trying to interpret =
the SEARCH/VQUERY criteria and applying that to dynamic VFREEBUSY =
components. <SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>But, then, how =
do I get free-busy information?<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>A VFREEBUSY request (dtstart, dtend) was the answer.<SPAN style=3D"m=
so-spacerun: yes">&nbsp; </SPAN>It turns out that a VFREEBUSY request also =
works for models A and B=85 and is much simpler=85 and doesn=92t&nbsp;deal =
with the inconsistencies described above.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p=
></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">With the above =
explanations in mind, I can response to some of Doug=92s questions and =
comments:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><o:p>&nbsp;</o:p=
></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">D Royer =
Wrote:<BR><BR>&gt; </SPAN><?xml:namespace prefix =3D st1 ns =3D "urn:schema=
s-microsoft-com:office:smarttags" /><st1:PersonName><st1:PersonName><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Craig J</SPAN></st1:PersonNa=
me><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">ohnson</SPAN></st1:=
PersonName><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> wrote:<BR>=
&gt; &gt;<BR>&gt; &gt; <BR>&gt; &gt; No, I do not suggest we disallow this =
QUERY.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Such a QUERY is =
necessary <BR>&gt; &gt; for Calendar Stores that support the VFREEBUSY =
component.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Allow me =
<BR>&gt; &gt; to elaborate on a few distinguishing issues...<BR>&gt; &gt; =
<BR>&gt; &gt;<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN><BR>&gt; &gt; =
1. Let's make a distinction between "a request for free-busy <BR>&gt; &gt; =
information" and "a QUERY for VFREEBUSY components".<SPAN style=3D"mso-spac=
erun: yes">&nbsp; </SPAN>This distinction <BR>&gt; &gt; comes clearly into =
focus when dealing with a Calendar Store that does <BR>&gt; &gt; not =
support the VFREEBUSY component.<BR>&gt; &gt; <BR><SPAN style=3D"COLOR: =
blue"><FONT color=3D#000000>&gt; <BR>&gt; After thinking about this, there =
is no difference. With all other<BR>&gt; components they are booked or =
not. Why should VFREEBUSY be any different?<o:p></o:p></FONT></SPAN></SPAN>=
</P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>The difference is a =93high level=94 request for =
free-busy information vs a =93low level=94 query of VFREEBUSY objects =
(whether dynamic or static).</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>The =93high-level=94 request shields the CUA from =
idiosyncrasies inherent in =93dynamic vs static=94 implementations.<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>It works with all models.&nbsp; =
It is much simpler to understand and implement.</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>I'm somewhat confident the "low-level" approach can =
produce the same information... if it is correctly constructed.</FONT></SPA=
N></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
><FONT color=3D#000000>&gt; This WG decided on dynamically created =
VFREEBUSY replies from the CS.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>I=92m all for that.<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>My proposal is consistent with that.<o:p></o:p></FONT></=
SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
><FONT color=3D#000000>&gt; It did not decide (as you use in your example =
below) that they be<BR>&gt; kind of static relative to a month (or =
whatever time frame).<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Again, is Model A 'dead'?</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>The example was derived from a previous thread that =
discussed possible implementations and implications for static VFREEBUSY =
objects.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I do not mean to =
imply that that is the way it should be done=85 but to illustrate =
differences in the reply between using a =93high-level=94 and =93low-level=
=94 method for getting free-busy data.<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>If Model A is not supported=85 then say so in the =
spec.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><SP=
AN style=3D"mso-spacerun: yes"></SPAN><BR></SPAN><SPAN style=3D"FONT-SIZE: =
10pt; FONT-FAMILY: Tahoma">&gt; &gt; <BR>&gt; &gt; Suppose we have a =
simple Calendar Store that supports VEVENTs but does <BR>&gt; &gt; not =
support VTODO, VJOURNAL or VFREEBUSY (i.e. VEVENT is on the <BR>&gt; &gt; =
COMPONENTS property; VTODO, VJOURNAL and VFREEBUSY are not).<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The <BR>&gt; &gt; Calendar Store =
is capable of providing free-busy information, but how do <BR>&gt; &gt; =
you get it?<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>A QUERY of =
VFREEBUSY would be formally invalid because it <BR>&gt; &gt; is not listed =
on the COMPONENTS property.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Would a QUERY of VTODOs be <BR>&gt; &gt; valid?<SPAN style=3D"mso-sp=
acerun: yes">&nbsp; </SPAN>No.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Why would a VFREEBUSY be any different?<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>Nothing in the CAP <BR>&gt; &gt; spec allows for this =
incongruency (i.e. no-where does the spec indicate <BR>&gt; &gt; that a =
Calendar Store must support a QUERY of VFREEBUSY regardless of <BR>&gt; =
&gt; whether it is listed on the COMPONENTS property.)<BR>&gt; <BR><SPAN =
style=3D"COLOR: blue"><FONT color=3D#000000>&gt; If a CS does not support =
other components they also can not be returned.<BR>&gt; Why make VFREEBUSY =
an exception? <o:p></o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>You are thinking =93Model D=94.<SPAN style=3D"mso-spacer=
un: yes">&nbsp; </SPAN>I am thinking =93Model C=94.<SPAN style=3D"mso-space=
run: yes">&nbsp; </SPAN>VFREEBUSY is not an exception for Model C.<o:p></o:=
p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>&gt; If the CS did not support VFREEBUSY<BR>&gt; could =
I not just do this in a single search command:<BR>&gt; <BR>&gt; <SPAN =
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 </SPAN>QUERY:SELECT DTSTART,DTEND FROM VEVENT<BR>&gt;<SPAN style=3D"mso-sp=
acerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>WHERE DTSTART &gt;=3D range AND DTEND &lt;=3D range<BR>&gt;<SPAN =
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; </SPAN>AND ( TRANSP =3D 'OPAQUE' OR TRANSP =3D 'OPAQUE-NOCONF=
LICT' )<BR>&gt; <SPAN style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; </SPAN>QUERY:SELECT DTSTART,DTEND FROM VTODO<BR>&gt;=
<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; </SPAN>WHERE DTSTART &gt;=3D range AND DTEND &lt;=3D =
range<BR>&gt;<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>AND ( TRANSP =3D 'OPAQUE' OR =
TRANSP =3D 'OPAQUE-NOCONFLICT' )<BR>&gt; <SPAN style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><BR>&gt; Which =
is how I dynamically calculate VFREEBUSY information anyway.<BR>&gt; =
Trimming the results to the CUA's exact start/stop times is trivial.<BR>&gt=
; As is combining the results into blocks of time and forming a VFREEBUSY<B=
R>&gt; component from those results.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>A CUA might encounter VCAR rights problems trying to =
issue the above commands.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>But, Model C allows free-busy request so it isn=92t necessary to =
resort to a request against VEVENTs.</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Does your CS issue this command to itself?<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Seems like it would be trivial =
to convert a VFREEBUSY request (dtstart, dtend) into this form.<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>It does not seem as trivial to =
convert a VQUERY of VFREEBUSY components, with all the potential variations=
 and permutations of the query criteria, into this form.<SPAN style=3D"mso-=
spacerun: yes">&nbsp; </SPAN>(Another compelling reason I moved from Model =
B to Model C).</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
><FONT color=3D#000000>&gt; <BR></FONT></SPAN><SPAN style=3D"FONT-SIZE: =
10pt; FONT-FAMILY: Tahoma">&gt; &gt; This is avoided by making SEARCH/VFREE=
BUSY the way to "request free-busy <BR>&gt; &gt; information".<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>It works regardless of how the =
Calendar Store keeps track <BR>&gt; &gt; of "free-busy" information (i.e. =
whether or not it supports the <BR>&gt; &gt; VFREEBUSY component).<SPAN =
style=3D"mso-spacerun: yes">&nbsp; </SPAN>SEARCH/VQUERY only works for =
Calendar Stores that <BR>&gt; &gt; support the VFREEBUSY object.<BR><SPAN =
style=3D"COLOR: blue"><FONT color=3D#000000>&gt; <BR>&gt; Why should a =
'BOOKED' VFREEBUSY be any different than any other component?<BR style=3D"m=
so-special-character: line-break"><BR style=3D"mso-special-character: =
line-break"><o:p></o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Sorry.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>I=92m lost on what your question is here.<SPAN style=3D"mso-spacerun=
: yes">&nbsp; </SPAN>I think it=92s a Model C/Model D issue.&nbsp; That =
makes it moot.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
></SPAN><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">&gt; &gt; =
2.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>A SEARCH/VQUERY may not =
return the same information as a <BR>&gt; &gt; SEARCH/VFREEBUSY (although =
both will return the needed information).<BR><SPAN style=3D"COLOR: =
blue"><FONT color=3D#000000>&gt; <BR>&gt; As this WG has decided on =
dynamic VFREEBUSY replies, why do you<BR>&gt; think they would not satisfy =
the QUERY?<o:p></o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>I said =93both will return the needed information=94.<SP=
AN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I think that is the same as =
saying =93they will satisfy the query=94<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>I believe for Model B and C the same information will =
be returned.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Model A can =
potentially be different, although it may be the same.<o:p></o:p></FONT></S=
PAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>&gt; Do you envision that<BR>&gt; each CALOWNERs CUA =
will deposit exactly the correct VFREEBUSY information<BR>&gt; for each =
month into the CS? It is my understanding that this WG decided<BR>&gt; =
that the VFREEBUAY replies be dynamic, so that would then be useless. So =
where<BR>&gt; would these replies come from? And who would use the static =
results<BR>&gt; that you example below (month boundary)<o:p></o:p></FONT></=
SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Again, I am not trying to imply how a Model A calendar =
store might organize its static VFREEBUSY data.<SPAN style=3D"mso-spacerun:=
 yes">&nbsp; </SPAN>Ideas for that were discussed on previous threads.<SPAN=
 style=3D"mso-spacerun: yes">&nbsp; </SPAN>They are presented here only to =
show potential differences between FREEBUSY responses of Model A and that =
of Model B/C.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Model B and C do provide =91dynamic=92 data, consistent =
with the WG decision (which, BTW, is not reflected in the spec).<o:p></o:p>=
</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
><FONT color=3D#000000>&gt; <BR></FONT></SPAN><SPAN style=3D"FONT-SIZE: =
10pt; FONT-FAMILY: Tahoma">&gt; &gt; Suppose we have a Calendar Store that =
supports the VFREEBUSY component.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><BR>&gt; &gt; Within a VAGENDA there is a VFREEBUSY object for each =
month containing <BR>&gt; &gt; FREEBUSY properties for busy times in that =
month.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Now, suppose I need =
<BR>&gt; &gt; free-busy information for a particular week</SPAN><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Terminal; mso-bidi-font-family: =
Terminal">=85</SPAN><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><B=
R><SPAN style=3D"COLOR: blue"><FONT color=3D#000000>&gt; <BR>&gt; Bruces =
assertion was that booked VFREEBUSY entries are calculated and not<BR>&gt; =
stored.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>You are proposing =
two booked VFREEBUSY dynamic component replies.<BR>&gt; Please explain why =
a CUA would want each of the two. Then maybe I can<BR>&gt; understand the =
difference.<BR style=3D"mso-special-character: line-break"><BR style=3D"mso=
-special-character: line-break"><o:p></o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Again, a Model A vs Model B/C issue.<o:p></o:p></FONT></=
SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
></SPAN><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">&gt; &gt; - A =
SEARCH/VQUERY would find the VFREEBUSY object(s) that overlap the <BR>&gt; =
&gt; week of interest.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>The =
VFREEBUSY object would be returned with FREEBUSY <BR>&gt; &gt; properties =
for the entire month ,not just FREEBUSY properties for the requested =
week.<BR><SPAN style=3D"COLOR: blue"><FONT color=3D#000000>&gt; <BR>&gt; =
The entire proposal on this list was for a dynamic VFREEBUSY, your<BR>&gt; =
assertion assumes that they are not dynamic. So you invented a second<BR>&g=
t; type of VFREEBUSY. Correct?<o:p></o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>No.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Didn=
=92t invent anything.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Just =
describing model A (as per previous threads).<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
><FONT color=3D#000000>&gt; <BR></FONT></SPAN><SPAN style=3D"FONT-SIZE: =
10pt; FONT-FAMILY: Tahoma">&gt; &gt; - A SEARCH/VFREEBUSY would also find =
the VFREEBUSY object(s) that <BR>&gt; &gt; overlap the week of interest.<SP=
AN style=3D"mso-spacerun: yes">&nbsp; </SPAN>However, in creating a =
response, the <BR>&gt; &gt; SEARCH/VFREEBUSY can include only FREEBUSY =
properties overlapping the <BR>&gt; &gt; week of interest and others can =
be left out.<BR><SPAN style=3D"COLOR: blue"><FONT color=3D#000000>&gt; =
<BR>&gt; Why not just declare that booked VFREEEBUSY's return what the =
CUA<BR>&gt; asks for in the QUERY and in the time range specified in the =
QUERY?<BR>&gt; If VFREEBUSY replies are dynamic as this WG wants, then =
100% of<BR>&gt; all VFREEBUSY components stored into the TARGET can be =
thrown away<BR>&gt; and ignored anyway. They would NEVER be fetched as =
this WG wants<BR>&gt; dynamic VFREEBUSY replies.<BR style=3D"mso-special-ch=
aracter: line-break"><BR style=3D"mso-special-character: line-break"><o:p><=
/o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>If you don=92t support Type A then that would be =
true.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><SP=
AN style=3D"mso-spacerun: yes"></SPAN><BR><FONT color=3D#000000>&gt; The =
only thing that I can think of is if a CUA wished to add<BR>&gt; blocked =
out time to a TARGET by storing a VFREEBUSY. But there<BR>&gt; would be no =
way to undo or change the contents of one once<BR>&gt; stored. That should =
be on the 'do not do that' list.<BR style=3D"mso-special-character: =
line-break"><BR style=3D"mso-special-character: line-break"><o:p></o:p></FO=
NT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Now, you are saying I cannot do a CREATE, MODIFY, =
DELETE of VFREEBUSY components; that VFREEBUSY is different than the other =
components.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Where is that =
in the spec?<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>What operations=
 are possible with the VFREEBUSY component? <SPAN style=3D"mso-spacerun: =
yes">&nbsp;</SPAN>Only SEARCH/VQUERY?<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>If that=92s the case, I have another proposal in =
mind.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
><FONT color=3D#000000>&gt; Can anyone think of any reason that a CUA =
would want a static<BR>&gt; booked VFREEBUSY reply when a dynamic one that =
is guaranteed to represent<BR>&gt; the state of the TARGET is available?<BR=
 style=3D"mso-special-character: line-break"><BR style=3D"mso-special-chara=
cter: line-break"><o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>If you support Model A you have to expect static booked =
VFREEBUSY replies (perhaps along with some dynamically generated ones).<SPA=
N style=3D"mso-spacerun: yes">&nbsp; </SPAN>Yes, there are many complicatio=
ns involved to support Model A.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><BR=
></SPAN><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">&gt; &gt; The =
addition of STATE() =3D 'BOOKED' is necessary to avoid retrieving <BR>&gt; =
&gt; 'unprocessed' VFREEBUSY records that may be present in the VAGENDA.<BR=
><SPAN style=3D"COLOR: blue"><FONT color=3D#000000>&gt; <BR>&gt; Yes - =
thanks.<BR>&gt; And with dynamic VFREEBUSY replies 100% of all non-booked =
VFREEBUSY<BR>&gt; components can be ignored and never stored by the CS - =
correct?<o:p></o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Not correct. <SPAN style=3D"mso-spacerun: yes">&nbsp;</S=
PAN>Whether or not they are stored depends on the CS and CUA... and =
non-booked (ie unprocessed)&nbsp;VFREEBUSY components usually have little =
to do with 'dynamic' VFREEBUSY components.</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>There are two types of =93unprocessed=94 VFREEBUSY =
objects that may show up in your VAGENDA:<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>(1) a request for your free-busy time (an iTIP =
request), and (2) a response to a free-busy request that you made (an iTIP =
reply).<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>A request might be =
handled immediately by the CS and not stored; but if it=92s handled by a =
CUA or CUA-BOT it will be stored until it gets handled.<SPAN style=3D"mso-s=
pacerun: yes">&nbsp; </SPAN>A response would be stored until a CUA =
retrieves and deletes it.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>It seems necessary that =93unprocessed=94 vs =
=93booked=94 needs to be specified in VFREEBUSY SEARCH/VQUERY operations.&n=
bsp;&nbsp;With my proposal it is not necessary; it is implied we are =
dealing with "booked" entities.</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>&gt; <BR></FONT></SPAN><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">&gt; &gt; QUERY is a 'nuts and bolts' way of getting =
information; powerful and <BR>&gt; &gt; flexible ... but inherently =
complex.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>In contrast, a =
'VFREEBUSY request' <BR>&gt; &gt; is a 'high level' operation; very =
specific ...<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>but simple.<BR>=
<SPAN style=3D"COLOR: blue"><FONT color=3D#000000>&gt; <BR>&gt; The =
VFREEBUSY component was invented because iMIP is not real time and<BR>&gt; =
a CUA needed to be able to make best guess as scheduling on the first<BR>&g=
t; attempt. Having the CS dynamically create a VFREEBUSY seems to =
be<BR>&gt; what this WG wants.<o:p></o:p></FONT></SPAN></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:=
p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>Again, we agree on this point!<SPAN style=3D"mso-spaceru=
n: yes">&nbsp; </SPAN>Dynamically created VFREEBUSY is the preferred way =
to go.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>My proposal supports =
this!<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>There is no issue =
about that.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"></S=
PAN><FONT color=3D#000000><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Tahoma"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><FONT color=3D#000000><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Tahoma"><FONT color=3D#000000>&gt; I do not see that having =
two kinds of dynamically<BR>&gt; created VFREEBUSY replies is useful.</FONT=
><BR></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>There are not two kinds of dynamic VFREEBUSY replies.<SP=
AN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Only one.<SPAN style=3D"mso-sp=
acerun: yes">&nbsp; </SPAN>However, there are two proposed ways of making =
the request.&nbsp; One simple, one not. One easy to understand, one =
not.&nbsp; One easy to implement, one not as easy.</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: =
none"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><FO=
NT color=3D#000000>My proposal has been implemented and running on&nbsp;a =
preliminary CAP implementation for over two months... with great success =
and acceptance.&nbsp; More on this in another post...</FONT></SPAN></P></BO=
DY></HTML>

--=__Part411F6D18.0__=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 04:01:07 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05228
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 04:01:06 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6N7nRqt007648
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 00:49:27 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6N7nRJg007644
	for ietf-calendar-bks; Wed, 23 Jul 2003 00:49:27 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from acampi.inet.it (acampi.inet.it [213.92.1.165])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6N7nPqt007622
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 00:49:26 -0700 (PDT)
	(envelope-from acampi@acampi.inet.it)
Received: by acampi.inet.it (Postfix, from userid 210)
	id 2A863155C9; Wed, 23 Jul 2003 09:49:18 +0200 (CEST)
Date: Wed, 23 Jul 2003 09:49:18 +0200
From: Andrea Campi <a.campi@inet.it>
To: pregen@egenconsulting.com
Cc: Doug Royer <Doug@royer.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: Re: CAP -11
Message-ID: <20030723074918.GA42502@inet.it>
References: <OF621DBBEE.C1D95837-ON85256D6B.00792A98-85256D6B.007941BE@egenconsulting.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF621DBBEE.C1D95837-ON85256D6B.00792A98-85256D6B.007941BE@egenconsulting.com>
Organization: I.NET S.p.A.
User-Agent: Mutt/1.5.4i
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


On Tue, Jul 22, 2003 at 06:04:26PM -0400, pregen@egenconsulting.com wrote:
> Actually, the chair's don't rule on this - the list does.  We need more 
> feedback from the list.  Is Craig's proposal ok?  If I don't hear back 
> that it's wrong - then do I read a "nod" from everyone that it's ok to be 
> added?  List?

Personally, I don't have much time at hands and Craig's weird formatting
makes it particularly painful to read all emails. However, my guts feeling
is that we don't need to add another way to retrieve VFREEBUSY information,
or at least I see no compelling reason.

In fact, I saw objections from Doug but I saw no strong enough replies from
Craig - and I don't think Doug himself changed his mind. So as things stand
right now I don't think "silence = agreement" would be a wise default, rather,
"silence = nothing to do".

Bye,
	Andrea

> 
> Doug Royer <Doug@royer.com>
> Sent by: owner-ietf-calendar@mail.imc.org
> 07/22/2003 12:22
> 
>  
>         To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
>         cc: 
>         Subject:        CAP -11
> 
> 
> 
> As there have been no proposals for fixing the current ABNF, I'll work
> on it this weekend.
> 
> I intend to submit -11 by Monday (CAP expires in AUG).
> 
> As the Craig Johnson is very new, I am going to hold off on it
> until the chairs rule on it.
> 
> 
>   Doug Royer                     |   http://INET-Consulting.com
>   -------------------------------|-----------------------------
>   Doug@Royer.com                 | Office: (208)612-INET
>   http://Royer.com/People/Doug   |    Fax: (866)594-8574
>                                  |   Cell: (208)520-4044
> 
>                  We Do Standards - You Need Standards
> 
> 

-- 
Andrea Campi                              mailto:a.campi@inet.it
I.NET S.p.A. - BT Ignite                  http://www.inet.it
Technical Dept. - 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 23 10:34:52 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15090
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 10:34:52 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NEB6qt047841
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 07:11:06 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NEB6UN047839
	for ietf-calendar-bks; Wed, 23 Jul 2003 07:11:06 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NEB4qt047823
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 07:11:04 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: Andrea Campi <a.campi@inet.it>
Cc: Doug Royer <Doug@royer.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: Re: CAP -11
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF7F666F7D.04498814-ON85256D6C.004DE61E-85256D6C.004DEA7A@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Wed, 23 Jul 2003 10:11:02 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/23/2003 10:11:05 AM,
	Serialize complete at 07/23/2003 10:11:05 AM
Content-Type: multipart/alternative; boundary="=_alternative 004DEA7285256D6C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 004DEA7285256D6C_=
Content-Type: text/plain; charset="us-ascii"

Ok.  I'll buy that.  Anyone else?
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




Andrea Campi <a.campi@inet.it>
Sent by: owner-ietf-calendar@mail.imc.org
07/23/2003 03:49

 
        To:     pregen@egenconsulting.com
        cc:     Doug Royer <Doug@royer.com>, "ietf-calendar@imc.org" 
<ietf-calendar@imc.org>, owner-ietf-calendar@mail.imc.org
        Subject:        Re: CAP -11



On Tue, Jul 22, 2003 at 06:04:26PM -0400, pregen@egenconsulting.com wrote:
> Actually, the chair's don't rule on this - the list does.  We need more
> feedback from the list.  Is Craig's proposal ok?  If I don't hear back
> that it's wrong - then do I read a "nod" from everyone that it's ok to 
be
> added?  List?

Personally, I don't have much time at hands and Craig's weird formatting
makes it particularly painful to read all emails. However, my guts feeling
is that we don't need to add another way to retrieve VFREEBUSY 
information,
or at least I see no compelling reason.

In fact, I saw objections from Doug but I saw no strong enough replies 
from
Craig - and I don't think Doug himself changed his mind. So as things 
stand
right now I don't think "silence = agreement" would be a wise default, 
rather,
"silence = nothing to do".

Bye,
Andrea

>
> Doug Royer <Doug@royer.com>
> Sent by: owner-ietf-calendar@mail.imc.org
> 07/22/2003 12:22
>
>
>         To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
>         cc:
>         Subject:        CAP -11
>
>
>
> As there have been no proposals for fixing the current ABNF, I'll work
> on it this weekend.
>
> I intend to submit -11 by Monday (CAP expires in AUG).
>
> As the Craig Johnson is very new, I am going to hold off on it
> until the chairs rule on it.
>
>
>   Doug Royer                     |   http://INET-Consulting.com
>   -------------------------------|-----------------------------
>   Doug@Royer.com                 | Office: (208)612-INET
>   http://Royer.com/People/Doug   |    Fax: (866)594-8574
>                                  |   Cell: (208)520-4044
>
>                  We Do Standards - You Need Standards
>
>

--
Andrea Campi                              mailto:a.campi@inet.it
I.NET S.p.A. - BT Ignite                  http://www.inet.it
Technical Dept. - R&D                     phone: +39 02 32863 ext 1
v. Darwin, 85 - I-20019                   fax: +39 02 32863 ext 7705
Settimo Milanese (MI), Italy


--=_alternative 004DEA7285256D6C_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Ok. &nbsp;I'll buy that. &nbsp;Anyone else?<br>
___________________<br>
Patricia Egen Consulting<br>
www.egenconsulting.com<br>
423-875-2652</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Andrea Campi &lt;a.campi@inet.it&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/23/2003 03:49</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;pregen@egenconsulting.com</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;Doug Royer &lt;Doug@royer.com&gt;, &quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;, owner-ietf-calendar@mail.imc.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: CAP -11</font></table>
<br>
<br>
<br>
<br><font size=2><tt>On Tue, Jul 22, 2003 at 06:04:26PM -0400, pregen@egenconsulting.com wrote:<br>
&gt; Actually, the chair's don't rule on this - the list does. &nbsp;We need more<br>
&gt; feedback from the list. &nbsp;Is Craig's proposal ok? &nbsp;If I don't hear back<br>
&gt; that it's wrong - then do I read a &quot;nod&quot; from everyone that it's ok to be<br>
&gt; added? &nbsp;List?<br>
</tt></font>
<br><font size=2><tt>Personally, I don't have much time at hands and Craig's weird formatting<br>
makes it particularly painful to read all emails. However, my guts feeling<br>
is that we don't need to add another way to retrieve VFREEBUSY information,<br>
or at least I see no compelling reason.<br>
</tt></font>
<br><font size=2><tt>In fact, I saw objections from Doug but I saw no strong enough replies from<br>
Craig - and I don't think Doug himself changed his mind. So as things stand<br>
right now I don't think &quot;silence = agreement&quot; would be a wise default, rather,<br>
&quot;silence = nothing to do&quot;.<br>
</tt></font>
<br><font size=2><tt>Bye,<br>
Andrea</tt></font>
<br>
<br><font size=2><tt>&gt;<br>
&gt; Doug Royer &lt;Doug@royer.com&gt;<br>
&gt; Sent by: owner-ietf-calendar@mail.imc.org<br>
&gt; 07/22/2003 12:22<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; cc:<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;CAP -11<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; As there have been no proposals for fixing the current ABNF, I'll work<br>
&gt; on it this weekend.<br>
&gt;<br>
&gt; I intend to submit -11 by Monday (CAP expires in AUG).<br>
&gt;<br>
&gt; As the Craig Johnson is very new, I am going to hold off on it<br>
&gt; until the chairs rule on it.<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
&gt; &nbsp; -------------------------------|-----------------------------<br>
&gt; &nbsp; Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
&gt; &nbsp; http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; Cell: (208)520-4044<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;We Do Standards - You Need Standards<br>
&gt;<br>
&gt;<br>
</tt></font>
<br><font size=2><tt>--<br>
Andrea Campi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;mailto:a.campi@inet.it<br>
I.NET S.p.A. - BT Ignite &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;http://www.inet.it<br>
Technical Dept. - R&amp;D &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;phone: +39 02 32863 ext 1<br>
v. Darwin, 85 - I-20019 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;fax: +39 02 32863 ext 7705</tt></font>
<br><font size=2><tt>Settimo Milanese (MI), Italy</tt></font>
<br>
<br>
--=_alternative 004DEA7285256D6C_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 10:34:53 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15093
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 10:34:52 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NEC8qt047899
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 07:12:08 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NEC7wS047898
	for ietf-calendar-bks; Wed, 23 Jul 2003 07:12:07 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NEC5qt047887
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 07:12:06 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: Andrea Campi <a.campi@inet.it>
Cc: Doug Royer <Doug@royer.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: Re: CAP -11
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF8EC49B15.F7E84266-ON85256D6C.004DFA5E-85256D6C.004E0357@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Wed, 23 Jul 2003 10:12:06 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/23/2003 10:12:07 AM,
	Serialize complete at 07/23/2003 10:12:07 AM
Content-Type: multipart/alternative; boundary="=_alternative 004E034F85256D6C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 004E034F85256D6C_=
Content-Type: text/plain; charset="us-ascii"

Also, what do you mean by wierd formatting.  His emails look ok in my mail 
engine?




Andrea Campi <a.campi@inet.it>
07/23/2003 03:49

 
        To:     pregen@egenconsulting.com
        cc:     Doug Royer <Doug@royer.com>, "ietf-calendar@imc.org" 
<ietf-calendar@imc.org>, owner-ietf-calendar@mail.imc.org
        Subject:        Re: CAP -11


On Tue, Jul 22, 2003 at 06:04:26PM -0400, pregen@egenconsulting.com wrote:
> Actually, the chair's don't rule on this - the list does.  We need more
> feedback from the list.  Is Craig's proposal ok?  If I don't hear back
> that it's wrong - then do I read a "nod" from everyone that it's ok to 
be
> added?  List?

Personally, I don't have much time at hands and Craig's weird formatting
makes it particularly painful to read all emails. However, my guts feeling
is that we don't need to add another way to retrieve VFREEBUSY 
information,
or at least I see no compelling reason.

In fact, I saw objections from Doug but I saw no strong enough replies 
from
Craig - and I don't think Doug himself changed his mind. So as things 
stand
right now I don't think "silence = agreement" would be a wise default, 
rather,
"silence = nothing to do".

Bye,
Andrea

>
> Doug Royer <Doug@royer.com>
> Sent by: owner-ietf-calendar@mail.imc.org
> 07/22/2003 12:22
>
>
>         To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
>         cc:
>         Subject:        CAP -11
>
>
>
> As there have been no proposals for fixing the current ABNF, I'll work
> on it this weekend.
>
> I intend to submit -11 by Monday (CAP expires in AUG).
>
> As the Craig Johnson is very new, I am going to hold off on it
> until the chairs rule on it.
>
>
>   Doug Royer                     |   http://INET-Consulting.com
>   -------------------------------|-----------------------------
>   Doug@Royer.com                 | Office: (208)612-INET
>   http://Royer.com/People/Doug   |    Fax: (866)594-8574
>                                  |   Cell: (208)520-4044
>
>                  We Do Standards - You Need Standards
>
>

--
Andrea Campi                              mailto:a.campi@inet.it
I.NET S.p.A. - BT Ignite                  http://www.inet.it
Technical Dept. - R&D                     phone: +39 02 32863 ext 1
v. Darwin, 85 - I-20019                   fax: +39 02 32863 ext 7705
Settimo Milanese (MI), Italy


--=_alternative 004E034F85256D6C_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Also, what do you mean by wierd formatting. &nbsp;His emails look ok in my mail engine?</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Andrea Campi &lt;a.campi@inet.it&gt;</b></font>
<p><font size=1 face="sans-serif">07/23/2003 03:49</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;pregen@egenconsulting.com</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;Doug Royer &lt;Doug@royer.com&gt;, &quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;, owner-ietf-calendar@mail.imc.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: CAP -11</font></table>
<br>
<br>
<br><font size=2><tt>On Tue, Jul 22, 2003 at 06:04:26PM -0400, pregen@egenconsulting.com wrote:<br>
&gt; Actually, the chair's don't rule on this - the list does. &nbsp;We need more<br>
&gt; feedback from the list. &nbsp;Is Craig's proposal ok? &nbsp;If I don't hear back<br>
&gt; that it's wrong - then do I read a &quot;nod&quot; from everyone that it's ok to be<br>
&gt; added? &nbsp;List?<br>
</tt></font>
<br><font size=2><tt>Personally, I don't have much time at hands and Craig's weird formatting<br>
makes it particularly painful to read all emails. However, my guts feeling<br>
is that we don't need to add another way to retrieve VFREEBUSY information,<br>
or at least I see no compelling reason.<br>
</tt></font>
<br><font size=2><tt>In fact, I saw objections from Doug but I saw no strong enough replies from<br>
Craig - and I don't think Doug himself changed his mind. So as things stand<br>
right now I don't think &quot;silence = agreement&quot; would be a wise default, rather,<br>
&quot;silence = nothing to do&quot;.<br>
</tt></font>
<br><font size=2><tt>Bye,<br>
Andrea</tt></font>
<br>
<br><font size=2><tt>&gt;<br>
&gt; Doug Royer &lt;Doug@royer.com&gt;<br>
&gt; Sent by: owner-ietf-calendar@mail.imc.org<br>
&gt; 07/22/2003 12:22<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; cc:<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;CAP -11<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; As there have been no proposals for fixing the current ABNF, I'll work<br>
&gt; on it this weekend.<br>
&gt;<br>
&gt; I intend to submit -11 by Monday (CAP expires in AUG).<br>
&gt;<br>
&gt; As the Craig Johnson is very new, I am going to hold off on it<br>
&gt; until the chairs rule on it.<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
&gt; &nbsp; -------------------------------|-----------------------------<br>
&gt; &nbsp; Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
&gt; &nbsp; http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; Cell: (208)520-4044<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;We Do Standards - You Need Standards<br>
&gt;<br>
&gt;<br>
</tt></font>
<br><font size=2><tt>--<br>
Andrea Campi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;mailto:a.campi@inet.it<br>
I.NET S.p.A. - BT Ignite &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;http://www.inet.it<br>
Technical Dept. - R&amp;D &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;phone: +39 02 32863 ext 1<br>
v. Darwin, 85 - I-20019 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;fax: +39 02 32863 ext 7705</tt></font>
<br><font size=2><tt>Settimo Milanese (MI), Italy</tt></font>
<br>
<br>
--=_alternative 004E034F85256D6C_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 10:43:58 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15564
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 10:43:57 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NEWJqt048403
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 07:32:19 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NEWJo1048402
	for ietf-calendar-bks; Wed, 23 Jul 2003 07:32:19 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by above.proper.com (8.12.9/8.12.8) with SMTP id h6NEWIqt048397
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 07:32:18 -0700 (PDT)
	(envelope-from JStracke@centive.com)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003072310415431594
 for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 10:41:54 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 23 Jul 2003 10:29:34 -0400
Message-ID: <3F1E9BCD.9040300@centive.com>
Date: Wed, 23 Jul 2003 10:29:33 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP -11
References: <OF8EC49B15.F7E84266-ON85256D6C.004DFA5E-85256D6C.004E0357@egenconsulting.com>
In-Reply-To: <OF8EC49B15.F7E84266-ON85256D6C.004DFA5E-85256D6C.004E0357@egenconsulting.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jul 2003 14:29:34.0213 (UTC) FILETIME=[D6479B50:01C35126]
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


pregen@egenconsulting.com wrote:

>
> Also, what do you mean by wierd formatting.  His emails look ok in my 
> mail engine? 

Andrea uses Mutt, so she sees Craig's text/plain instead of his text/html.

HTML on mailing lists is often considered a bad idea, especially on IETF 
lists where you get people using text-based mailers.

-- 
/=================================================================\
|John Stracke      |jstracke@centive.com                          |
|Principal Engineer|http://www.centive.com                        |
|Centive           |My opinions are my own.                       |
|=================================================================|
|I imagine the wages of sin *are* death, but by the time they take|
|taxes out it's just sort of a tired feeling. --Paula Poundstone  |
\=================================================================/




From owner-ietf-calendar@mail.imc.org  Wed Jul 23 12:10:17 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18301
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 12:10:15 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NFvkqt051734
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 08:57:46 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NFvk30051733
	for ietf-calendar-bks; Wed, 23 Jul 2003 08:57:46 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NFviqt051722
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 08:57:44 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: John Stracke <jstracke@centive.com>
Cc: "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        owner-ietf-calendar@mail.imc.org
Subject: Re: CAP -11
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFA38453C2.178026E7-ON85256D6C.0057ACB0-85256D6C.0057AF20@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Wed, 23 Jul 2003 11:57:44 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/23/2003 11:57:46 AM,
	Serialize complete at 07/23/2003 11:57:46 AM
Content-Type: multipart/alternative; boundary="=_alternative 0057AF1085256D6C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0057AF1085256D6C_=
Content-Type: text/plain; charset="us-ascii"

Ah, thanks John.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




John Stracke <jstracke@centive.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/23/2003 10:29

 
        To:     "ietf-calendar@imc.org" <ietf-calendar@imc.org>
        cc: 
        Subject:        Re: CAP -11



pregen@egenconsulting.com wrote:

>
> Also, what do you mean by wierd formatting.  His emails look ok in my
> mail engine?

Andrea uses Mutt, so she sees Craig's text/plain instead of his text/html.

HTML on mailing lists is often considered a bad idea, especially on IETF
lists where you get people using text-based mailers.

--
/=================================================================\
|John Stracke      |jstracke@centive.com                          |
|Principal Engineer|http://www.centive.com                        |
|Centive           |My opinions are my own.                       |
|=================================================================|
|I imagine the wages of sin *are* death, but by the time they take|
|taxes out it's just sort of a tired feeling. --Paula Poundstone  |
\=================================================================/




--=_alternative 0057AF1085256D6C_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Ah, thanks John.<br>
___________________<br>
Patricia Egen Consulting<br>
www.egenconsulting.com<br>
423-875-2652</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>John Stracke &lt;jstracke@centive.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/23/2003 10:29</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;ietf-calendar@imc.org&quot; &lt;ietf-calendar@imc.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: CAP -11</font></table>
<br>
<br>
<br>
<br><font size=2><tt>pregen@egenconsulting.com wrote:<br>
</tt></font>
<br><font size=2><tt>&gt;<br>
&gt; Also, what do you mean by wierd formatting. &nbsp;His emails look ok in my<br>
&gt; mail engine?<br>
</tt></font>
<br><font size=2><tt>Andrea uses Mutt, so she sees Craig's text/plain instead of his text/html.<br>
</tt></font>
<br><font size=2><tt>HTML on mailing lists is often considered a bad idea, especially on IETF<br>
lists where you get people using text-based mailers.<br>
</tt></font>
<br><font size=2><tt>--<br>
/=================================================================\<br>
|John Stracke &nbsp; &nbsp; &nbsp;|jstracke@centive.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<br>
|Principal Engineer|http://www.centive.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<br>
|Centive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |My opinions are my own. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
|=================================================================|<br>
|I imagine the wages of sin *are* death, but by the time they take|<br>
|taxes out it's just sort of a tired feeling. --Paula Poundstone &nbsp;|<br>
\=================================================================/<br>
</tt></font>
<br>
<br>
<br>
--=_alternative 0057AF1085256D6C_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 12:26:15 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18892
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 12:26:15 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NGHUqt052505
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 09:17:30 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NGHTDF052504
	for ietf-calendar-bks; Wed, 23 Jul 2003 09:17:29 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from acampi.inet.it (acampi.inet.it [213.92.1.165])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NGHSqt052499
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 09:17:29 -0700 (PDT)
	(envelope-from acampi@acampi.inet.it)
Received: by acampi.inet.it (Postfix, from userid 210)
	id 513F9155C9; Wed, 23 Jul 2003 18:17:29 +0200 (CEST)
Date: Wed, 23 Jul 2003 18:17:29 +0200
From: Andrea Campi <a.campi@inet.it>
To: John Stracke <jstracke@centive.com>
Cc: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP -11
Message-ID: <20030723161729.GC42502@inet.it>
References: <OF8EC49B15.F7E84266-ON85256D6C.004DFA5E-85256D6C.004E0357@egenconsulting.com> <3F1E9BCD.9040300@centive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F1E9BCD.9040300@centive.com>
Organization: I.NET S.p.A.
User-Agent: Mutt/1.5.4i
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


On Wed, Jul 23, 2003 at 10:29:33AM -0400, John Stracke wrote:
> Andrea uses Mutt, so she sees Craig's text/plain instead of his text/html.
> 
> HTML on mailing lists is often considered a bad idea, especially on IETF 
> lists where you get people using text-based mailers.

Exactly. Apart from the fact that, rather confusingly, Andrea is a
male name in Italy, so I am in fact `he' ;-)

Bye,
	Andrea

-- 
Andrea Campi                              mailto:a.campi@inet.it
I.NET S.p.A. - BT Ignite                  http://www.inet.it
Technical Dept. - 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 23 12:34:02 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19060
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 12:34:01 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NGP4qt052744
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 09:25:04 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NGP4hj052743
	for ietf-calendar-bks; Wed, 23 Jul 2003 09:25:04 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by above.proper.com (8.12.9/8.12.8) with SMTP id h6NGP2qt052735
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 09:25:03 -0700 (PDT)
	(envelope-from JStracke@centive.com)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003072312344702375
 for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 12:34:47 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 23 Jul 2003 12:22:26 -0400
Message-ID: <3F1EB643.8040300@centive.com>
Date: Wed, 23 Jul 2003 12:22:27 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: CAP -11
References: <OF8EC49B15.F7E84266-ON85256D6C.004DFA5E-85256D6C.004E0357@egenconsulting.com> <3F1E9BCD.9040300@centive.com> <20030723161729.GC42502@inet.it>
In-Reply-To: <20030723161729.GC42502@inet.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jul 2003 16:22:26.0992 (UTC) FILETIME=[9B2BAB00:01C35136]
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Andrea Campi wrote:

>On Wed, Jul 23, 2003 at 10:29:33AM -0400, John Stracke wrote:
>  
>
>>Andrea uses Mutt, so she sees Craig's text/plain
>>    
>>
>Andrea is a
>male name in Italy, so I am in fact `he' ;-)
>  
>
And you've said that before on this list, and I forgot.  Excuse me.

-- 
/===========================================\
|John Stracke      |jstracke@centive.com    |
|Principal Engineer|http://www.centive.com  |
|Centive           |My opinions are my own. |
|===========================================|
|See what bilateral symmetry can do for YOU!|
\===========================================/




From owner-ietf-calendar@mail.imc.org  Wed Jul 23 13:41:45 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20799
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 13:41:44 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NHTqqt055528
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 10:29:52 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NHTqxf055527
	for ietf-calendar-bks; Wed, 23 Jul 2003 10:29:52 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NHTqqt055522
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 10:29:52 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Wed, 23 Jul 2003 11:28:07 -0600
Message-Id: <sf1e7147.019@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 23 Jul 2003 11:30:36 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Cap Free-Busy Request; some compelling thoughts
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartA3FD8F2C.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__PartA3FD8F2C.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Perhaps this narrative will provide insight that some might find compelling=
. . .
=20
We have a preliminary CAP implementation in use by customers (early =
adopters) both inside and outside our organization.  Months ago, we were =
attempting to satisfy the need of these customers to perform a CAP =
real-time busy search.  At the time the only option offered by the CAP =
spec was the iTIP approach (not real-time).  Customers were not enthused =
about this approach and deficiency in CAP.
=20
Later, we posed the SEARCH/VQUERY concept.  It got a cool reception.  The =
response was that "it seems like a step backward" compared with the =
simplicity of an iTIP request.  We assured them the spec was not yet final =
and something better might be forthcoming.
=20
After implementing the CAP iTIP-VFREEBUSY request/response, the idea of =
using a VFREEBUSY request 'directly' occurred to us.  We implemented it as =
an X-GETFREEBUSY command.  Implementation was very quick because it =
leveraged the already existing iTIP-VFREEBUSY code.
=20
When presented to customers the response was universally positive and =
enthusiastic!  "That's more like it."  "That makes much more sense."  The =
simplicity and consistency with iTIP were also positives. Considering the =
previous alternatives, these customers urged us to lobby the CalSch WG to =
adopt this method of requesting free-busy information.  They would very =
much like to see it in the spec so they can deal with other CAP implementat=
ions in a similar manner.
=20
The proposal for using VFREEBUSY (dtstart, dtend) to request free-busy =
information is not a recent idea.  It has been implemented, adopted and in =
use for over two months.  The experience has been very good at both ends.
=20
Our experience has been compelling.  In sharing this narrative I'm hoping =
the WG can benefit from our experience and from the response of CAP =
adopters* and that it might be compelling to the WG at-large.   If =
presented a choice, I am confident potential CAP adopters would choose the =
'VFREEBUSY request' over 'VQUERY request' by a significant majority.
=20
I see no problem offering both in the spec.  While some call it as =
unnecessary, our experience indicates otherwise.  Why not give adopters =
two ways to "get a cart up a hill"?  Adopters can choose whether they want =
to "push it by hand" or "pull it with a truck".  Let's give them a =
"truck".  It's what they want.
=20
--cjohnson


--=__PartA3FD8F2C.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Perhaps this narrative will provide&nbsp;insight that some might find =
compelling. . .</DIV>
<DIV>&nbsp;</DIV>
<DIV>We have a preliminary CAP implementation in use by customers (early =
adopters) both inside and outside our organization.&nbsp; Months ago, we =
were attempting to satisfy the need of these customers to perform a CAP =
real-time busy search.&nbsp; At the time the only option offered by the =
CAP spec was the iTIP approach (not real-time).&nbsp; Customers were not =
enthused about this approach and deficiency in CAP.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Later, we posed the SEARCH/VQUERY concept.&nbsp; It got a cool =
reception.&nbsp; The response was that "it seems like a step backward" =
compared with the simplicity of an iTIP request.&nbsp; We assured them the =
spec was not yet final and something better might be forthcoming.</DIV>
<DIV>&nbsp;</DIV>
<DIV>After implementing the CAP iTIP-VFREEBUSY request/response, the idea =
of using a VFREEBUSY request 'directly' occurred to us.&nbsp; We implemente=
d it as an X-GETFREEBUSY command.&nbsp; Implementation was <U>very =
quick</U> because it leveraged the already existing iTIP-VFREEBUSY =
code.</DIV>
<DIV>&nbsp;</DIV>
<DIV>When presented to customers the response was universally positive and =
enthusiastic!&nbsp; "That's more like it."&nbsp; "That makes much more =
sense."&nbsp; The simplicity and consistency with iTIP were also positives.=
 Considering the previous alternatives, these customers&nbsp;urged us to =
lobby the CalSch WG to adopt this method of requesting free-busy informatio=
n.&nbsp; They would very much like to see it in the spec so they can deal =
with&nbsp;other CAP implementations in a similar manner.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The proposal for using VFREEBUSY (dtstart, dtend) to request =
free-busy information is not a recent idea.&nbsp; It has been implemented, =
adopted and&nbsp;in use for over two months.&nbsp; The experience has been =
very good at both ends.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Our experience has been compelling.&nbsp; In sharing this narrative =
I=92m hoping the WG can benefit from our experience and from the response =
of CAP adopters=85 and that it might be compelling to the WG at-large.&nbsp=
;&nbsp; If presented a choice, I am confident potential CAP adopters would =
choose the 'VFREEBUSY request' over 'VQUERY request' by a significant =
majority.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I see no problem offering both in the spec.&nbsp; While some&nbsp;call=
 it as unnecessary, our experience indicates otherwise.&nbsp; Why not give =
adopters two ways to "get a cart up a hill"?&nbsp; Adopters can choose =
whether they want to "push it by hand" or "pull it with a truck".&nbsp; =
Let's give them a "truck".&nbsp; It's what they want.</DIV>
<DIV>&nbsp;</DIV>
<DIV>--cjohnson</DIV></BODY></HTML>

--=__PartA3FD8F2C.0__=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 13:51:11 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21235
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 13:51:10 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NHfnqt056457
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 10:41:49 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NHfnNV056456
	for ietf-calendar-bks; Wed, 23 Jul 2003 10:41:49 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by above.proper.com (8.12.9/8.12.8) with SMTP id h6NHfmqt056451
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 10:41:48 -0700 (PDT)
	(envelope-from JStracke@centive.com)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003072313513220790
 for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 13:51:32 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 23 Jul 2003 13:39:12 -0400
Message-ID: <3F1EC841.1050903@centive.com>
Date: Wed, 23 Jul 2003 13:39:13 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request; some compelling thoughts
References: <sf1e7147.019@gw.provo.novell.com>
In-Reply-To: <sf1e7147.019@gw.provo.novell.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jul 2003 17:39:12.0702 (UTC) FILETIME=[54633DE0:01C35141]
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Craig Johnson wrote:

> If presented a choice, I am confident potential CAP adopters would 
> choose the 'VFREEBUSY request' over 'VQUERY request' by a significant 
> majority.
>  
> I see no problem offering both in the spec.  While some call it as 
> unnecessary

Actually, I'd call the VQUERY version unnecessary--it doesn't match 
users' expectations, and it doesn't match the implementation style of 
any product I've heard of (except Exchange, which isn't going to 
implement CAP anyway).  When you give someone access to your freebusy 
information, they expect the *current* information, not whatever it was 
when last you updated your store.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|The Player's Litany: The Wind is the Storm, and the Storm is|
|Data, and the Data is Life. --Daniel Keys Moran             |
\============================================================/




From owner-ietf-calendar@mail.imc.org  Wed Jul 23 14:26:32 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22456
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 14:26:31 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NIGPqt059506
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 11:16:25 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NIGPFJ059505
	for ietf-calendar-bks; Wed, 23 Jul 2003 11:16:25 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NIGOqt059500
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 11:16:24 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <sf1e7147.019@gw.provo.novell.com>
To: "Craig Johnson" <cjohnson@gw.novell.com>
Cc: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request; some compelling thoughts
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_07142003NP July 14, 2003
Message-ID: <OF2BD5BE03.19C33AEA-ON85256D6C.0061866A-85256D6C.006333FB@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Wed, 23 Jul 2003 14:06:51 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Release 6.0.2CF2|July 18, 2003) at 07/23/2003
 02:15:22 PM,
	Serialize complete at 07/23/2003 02:15:22 PM
Content-Type: multipart/alternative; boundary="=_alternative 006333F585256D6C_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 006333F585256D6C_=
Content-Type: text/plain; charset="US-ASCII"

Craig wrote on 07/23/2003 01:30:36 PM:
>                               At the time the only option offered by 
> the CAP spec was the iTIP approach (not real-time).

Umm, iTIP busytime REQUEST/REPLY can be done "real-time"; there is no 
store-and-forward lag inherent in iTIP.  iMIP is the store-and-forward 
binding (aka email binding) of iTIP.  CAP is a superset of what started 
out as iRIP, the real-time binding of iTIP.

In CAP it should just be a matter of using an iTIP Section 3.3.2 REQUEST 
whose response is an iTIP Section 3.3.3 REPLY message.    iTIP VFREEBUSY 
REPLYs are defined as:

   The "REPLY" method in a "VFREEBUSY" calendar component is used to
   respond to a busy time request. The method is sent by the recipient
   of a busy time request to the originator of the request.

so since the CAP server needs to generate some kind of response for the 
VFREEBUSY REQUEST its logical that it generate this. 

I have not been able to keep track of the recent flury of emails this 
thread so perhaps I missed some discussion on why this is NOT doable in 
CAP utilizing iTIP messages. 

BTW: Back on 3-Apr-03 I had proposed we reinstate the CAP-Draft-03 (thru 
05) text regarding CS and VFREEBUSY creation/maintenance.  It was removed 
in Draft-06 w/o any WG discussion and this went unnoticed for a while.  I 
think any design that expects CUAs to maintain busytime data is inherently 
flawed and unscalable; the CS is best suited to do this mainteance and 
this results in much more accurate busytime data.  Exactly how the CS does 
this internally is not relevant to CAP since thats an implementation 
detail. 

Yes Virginia that means someone could code up a CS that statically 
calculates the data at some interval and thus is not as consistanly 
accurate as a dynamically calculated/updated CS but so??   We cannot 
design a protocol to deal with poor implementation details and provide the 
functionality users want.   In any case, was there any disent or thought 
to readding the prose back and would it address some of the busytime 
concerns others have too?

Bruce
===========================================================================
Bruce Kahn                                INet: 
Bruce_Kahn@notesdev.ibm.com
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Warning: Dates in Calendar are closer than they appear.
--=_alternative 006333F585256D6C_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Craig wrote on 07/23/2003 01:30:36 PM:<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; At the time the only option offered
by <br>
&gt; the CAP spec was the iTIP approach (not real-time).</tt></font>
<br>
<br><font size=2 face="sans-serif">Umm, iTIP busytime REQUEST/REPLY can
be done &quot;real-time&quot;; there is no store-and-forward lag inherent
in iTIP. &nbsp;iMIP is the store-and-forward binding (aka email binding)
of iTIP. &nbsp;CAP is a superset of what started out as iRIP, the real-time
binding of iTIP.</font>
<br>
<br><font size=2 face="sans-serif">In CAP it should just be a matter of
using an iTIP Section 3.3.2 REQUEST whose response is an iTIP Section 3.3.3
REPLY message. &nbsp; &nbsp;iTIP VFREEBUSY REPLYs are defined as:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;The &quot;REPLY&quot; method in a &quot;VFREEBUSY&quot;
calendar component is used to<br>
 &nbsp; respond to a busy time request. The method is sent by the recipient<br>
 &nbsp; of a busy time request to the originator of the request.</tt></font>
<br>
<br><font size=2 face="sans-serif">so since the CAP server needs to generate
some kind of response for the VFREEBUSY REQUEST its logical that it generate
this. &nbsp; </font>
<br>
<br><font size=2 face="sans-serif">I have not been able to keep track of
the recent flury of emails this thread so perhaps I missed some discussion
on why this is NOT doable in CAP utilizing iTIP messages. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">BTW: Back on 3-Apr-03 I had proposed
we reinstate the CAP-Draft-03 (thru 05) text regarding CS and VFREEBUSY
creation/maintenance. &nbsp;It was removed in Draft-06 w/o any WG discussion
and this went unnoticed for a while. &nbsp;I think any design that expects
CUAs to maintain busytime data is inherently flawed and unscalable; the
CS is best suited to do this mainteance and this results in much more accurate
busytime data. &nbsp;Exactly how the CS does this internally is not relevant
to CAP since thats an implementation detail. </font>
<br>
<br><font size=2 face="sans-serif">Yes Virginia that means someone could
code up a CS that statically calculates the data at some interval and thus
is not as consistanly accurate as a dynamically calculated/updated CS but
so?? &nbsp; We cannot design a protocol to deal with poor implementation
details and provide the functionality users want. &nbsp; In any case, was
there any disent or thought to readding the prose back and would it address
some of the busytime concerns others have too?</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...</font>
<br><font size=2 face="sans-serif">Warning: Dates in Calendar are closer
than they appear.</font>
--=_alternative 006333F585256D6C_=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 14:50:51 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23498
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 14:50:50 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NIeSqt060251
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 11:40:28 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NIeSZV060250
	for ietf-calendar-bks; Wed, 23 Jul 2003 11:40:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NIeQqt060245
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 11:40:26 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6NIeGEB006775
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 11:40:24 -0700
Message-ID: <3F1ED68B.5090509@Royer.com>
Date: Wed, 23 Jul 2003 12:40:11 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request; some compelling thoughts
References: <sf1e7147.019@gw.provo.novell.com> <3F1EC841.1050903@centive.com>
In-Reply-To: <3F1EC841.1050903@centive.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020606070500030501050703"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020606070500030501050703
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



John Stracke wrote:
> 
> Craig Johnson wrote:
> 
>> If presented a choice, I am confident potential CAP adopters would 
>> choose the 'VFREEBUSY request' over 'VQUERY request' by a significant 
>> majority.
>>  
>> I see no problem offering both in the spec.  While some call it as 
>> unnecessary
> 
> 
> Actually, I'd call the VQUERY version unnecessary--it doesn't match 
> users' expectations, and it doesn't match the implementation style of 
> any product I've heard of (except Exchange, which isn't going to 
> implement CAP anyway).  When you give someone access to your freebusy 
> information, they expect the *current* information, not whatever it was 
> when last you updated your store.

I think the confusion is that some may not know that this WG already
decided that VFREEBUSY information is dynamic. So the QUERY *will*
return dynamically generated information and not 'whatever it
was last when you updated your store.'. So I think we agree.
This is not in the -10 version of CAP as it was decided upon just
as -10 was coming out. It however *IS* in -11 that is coming out
this weekend.

Text in -11 version to soon be published (based on the WG input
and existing CAP text):

<section anchor="SEARCHVFREEBUSY" title="Searching for VFREEBYSY">

  For CSs that set the "CAPABILITY" "RECUR-EXPAND" property to "TRUE"
  and have the "VFREEBUSY" component in the "COMPONENTS" value in
  the "CAPABILITY" reply, the CS MUST dynamically create the results
  of a search for the "VFREEBUSY" component at search time.
  For these CSs it is the the CS is responsibility and not the CUAs
  responsibility to provide the correct "VFREEBUSY" information for
  a calendar. If a CUA  performs a "CREATE" "VFREEBUSY" the CS MUST
  return success and not store the "VFREEBUSY" component.

  For CSs that set the "CAPABILITY" "RECUR-EXPAND" property to "FALSE"
  and have the "VFREEBUSY" component in the "COMPONENTS" value in
  the "CAPABILITY" reply, a CUA MAY store the "VFREEBUSY" information
  on the CS. These CSs then MUST return a "VFREEBUSY" component
  calculated from the stored components. If no "VFREEBUSY" information
  is available for the "TARGET" calendar, then a "VFREEBUSY" with
  no blocked out time will be returned with a success code.

  If a CS does not set the "VFREEBUSY" value in the "COMPONENTS"
  "CAPABILITY" value, the CS does not support the "VFREEBUSY"
  component and all creation and searching for a "VFREEBUSY"
  component MUST fail. Examples of calendars that may be in this
  category are public event calendars that will never require
  scheduling with other UPNs.

--

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020606070500030501050703
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjMxODQwMTFaMCMGCSqGSIb3DQEJBDEWBBQY
uBJSMnZIamkLRupdhnP56bw6CDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQBJEYZnLVKmbeDnWcuOIK+hiwyilptZ5PC/pGHlqgMG7yen
u0SyC3dMyzn1UNKCKjwZr3SjA3zE7osWfwHOneF9W4IvJ36hgzMo3Iwcj9m+BKEWIK+Y53IN
gz/XZiPlnCqYk3c8TV8rSssLT53W3GmneKu+1HpoXRUBHlOG/qFsq9ZXh40JURuX0ml1um7E
4ueyxie4P2CivuvUuq2kYNogdDmNOiojSmKoBb7B/43a0eJUJkC1svvIuY7z6jsAEfA++4Eq
DOov7aiihsL5muFG7+w4YohZdfaRhKhWGlSdkEflLo02OpRcpK1Z5Kvn+zpyDY0O0tWUZqs/
NzOPz7JvAAAAAAAA
--------------ms020606070500030501050703--



From owner-ietf-calendar@mail.imc.org  Wed Jul 23 14:58:38 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23658
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 14:58:37 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NInFqt060615
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 11:49:15 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NInFSH060614
	for ietf-calendar-bks; Wed, 23 Jul 2003 11:49:15 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by above.proper.com (8.12.9/8.12.8) with SMTP id h6NInDqt060597
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 11:49:14 -0700 (PDT)
	(envelope-from JStracke@centive.com)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003072314585831575
 for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 14:58:58 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 23 Jul 2003 14:46:38 -0400
Message-ID: <3F1ED80E.3010408@centive.com>
Date: Wed, 23 Jul 2003 14:46:38 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request; some compelling thoughts
References: <sf1e7147.019@gw.provo.novell.com> <3F1EC841.1050903@centive.com> <3F1ED68B.5090509@Royer.com>
In-Reply-To: <3F1ED68B.5090509@Royer.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jul 2003 18:46:38.0222 (UTC) FILETIME=[BFB49AE0:01C3514A]
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Doug Royer wrote:

> John Stracke wrote:
>
>> Actually, I'd call the VQUERY version unnecessary--it doesn't match 
>> users' expectations
>
> I think the confusion is that some may not know that this WG already
> decided that VFREEBUSY information is dynamic.

Oops.  Sorry, I missed that.  OK, then, whether you ask for it by one 
type of request or another is not something users will care about.

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|"Who died and made you king?" "My father."|
\==========================================/




From owner-ietf-calendar@mail.imc.org  Wed Jul 23 15:14:50 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25206
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 15:14:50 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NJ3Kqt061697
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 12:03:20 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NJ3K7f061696
	for ietf-calendar-bks; Wed, 23 Jul 2003 12:03:20 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NJ3Jqt061679
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 12:03:19 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Wed, 23 Jul 2003 13:01:39 -0600
Message-Id: <sf1e8733.034@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 23 Jul 2003 13:04:03 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request; some compelling thoughts
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartA6F88A33.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__PartA6F88A33.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

B Kahn wrote:
>  iTIP busytime REQUEST/REPLY can be done "real-time"; there is no
store-and-forward 
>  lag inherent in iTIP.  iMIP is the store-and-forward binding (aka
email binding) of iTIP.  
>  CAP is a superset of what started out as iRIP, the real-time binding
of iTIP. 
>  In CAP it should just be a matter of using an iTIP Section 3.3.2
REQUEST whose response 
>  is an iTIP Section 3.3.3 REPLY message.
<snip> 
>  so since the CAP server needs to generate some kind of response for
the VFREEBUSY REQUEST 
>  its logical that it generate this.   

This is contrary to your post of 31 Mar 2003 17:34:53...
 
>  ... if my CUA CREATEs a VFREEBUSY with METHOD:REQUEST, all I get
back is essentially a "Yes, your VFREEBUSY
>  was created in the TARGET", NOT the actual results Im querying for! 
So how does my CUA get the RESULTS of
> the query?? CAP is realtime so I would assume that the query/response
for busy time woud/should be realtime too!.
 
Your earlier post was correct.  You can't do CAP iTIP 'real-time'
VFREEBUSY request.

--=__PartA6F88A33.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV><FONT face=Arial>B Kahn wrote:</FONT></DIV>
<DIV><FONT face=Arial>&gt;&nbsp;&nbsp;</FONT><FONT face=Arial>iTIP busytime REQUEST/REPLY can be done "real-time"; there is no store-and-forward </FONT></DIV>
<DIV><FONT face=Arial>&gt;&nbsp; lag inherent in iTIP. &nbsp;iMIP is the store-and-forward binding (aka email binding) of iTIP.&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=Arial>&gt;&nbsp; CAP is a superset of what started out as iRIP, the real-time binding of iTIP.</FONT> <BR>&gt;&nbsp; <FONT face=sans-serif size=2>In CAP it should just be a matter of using an iTIP Section 3.3.2 REQUEST whose response </FONT></DIV>
<DIV><FONT face=sans-serif size=2>&gt;&nbsp; is an iTIP Section 3.3.3 REPLY message.</FONT><BR><FONT size=2><TT>&lt;snip&gt;</TT></FONT> <BR>&gt;&nbsp; <FONT face=sans-serif size=2>so since the CAP server needs to generate some kind of response for the VFREEBUSY REQUEST </FONT></DIV>
<DIV><FONT face=sans-serif size=2>&gt;&nbsp; its logical that it generate this.&nbsp;&nbsp; </FONT><BR></DIV>
<DIV>This is contrary to your&nbsp;post of 31 Mar 2003 17:34:53...</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&nbsp; ... if my CUA CREATEs a VFREEBUSY with METHOD:REQUEST, all I get back is essentially a "Yes, your VFREEBUSY</DIV>
<DIV>&gt;&nbsp; was created in the TARGET", NOT the actual results Im querying for!&nbsp; So how does my CUA get the RESULTS of</DIV>
<DIV>&gt; the query?? CAP is realtime so I would assume that the query/response for busy time woud/should be realtime too!.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Your earlier post was correct.&nbsp; You can't do&nbsp;CAP iTIP 'real-time' VFREEBUSY request.</DIV></BODY></HTML>
--=__PartA6F88A33.0__=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 15:20:28 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25845
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 15:20:27 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NJBeqt062952
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 12:11:40 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NJBeDv062951
	for ietf-calendar-bks; Wed, 23 Jul 2003 12:11:40 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NJBeqt062935
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 12:11:40 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Wed, 23 Jul 2003 13:10:00 -0600
Message-Id: <sf1e8928.036@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 23 Jul 2003 13:12:37 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request; some compelling thoughts
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartA2FC8E35.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__PartA2FC8E35.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

J Stracke wrote:
 
>  OK, then, whether you ask for it by one type of request or another
is not something users will care about.
 
On the contrary, from our experience users/customers DO care. 
Strongly.  The preference is VFREEBUSY request over VQUERY request. 
Just allow both.  Everyone will be happy.

--=__PartA2FC8E35.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>J Stracke wrote:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&nbsp;&nbsp;OK, <FONT size=1><FONT size=2>then, whether you ask for it by one </FONT><FONT size=2>type of request or another is not something users will care about.</FONT></FONT></DIV>
<DIV><FONT size=1><FONT size=2></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=1><FONT size=2>On the contrary, from our experience&nbsp;users/customers&nbsp;DO care.&nbsp; Strongly.&nbsp; The preference is VFREEBUSY request&nbsp;over VQUERY request.&nbsp; Just&nbsp;allow both.&nbsp; Everyone will be happy.</FONT></DIV></FONT></BODY></HTML>
--=__PartA2FC8E35.0__=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 16:10:22 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00694
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 16:10:21 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NK0Yqt067224
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 13:00:34 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NK0YtB067223
	for ietf-calendar-bks; Wed, 23 Jul 2003 13:00:34 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NK0Wqt067218
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 13:00:32 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6NK0MEB007601
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 13:00:30 -0700
Message-ID: <3F1EE951.6000302@Royer.com>
Date: Wed, 23 Jul 2003 14:00:17 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request; some compelling thoughts
References: <sf1e8928.036@gw.provo.novell.com>
In-Reply-To: <sf1e8928.036@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070300000000030606060905"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms070300000000030606060905
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Craig Johnson wrote:
> J Stracke wrote:
>  
>  >  OK, then, whether you ask for it by one type of request or another 
> is not something users will care about.
>  
> On the contrary, from our experience users/customers DO care.  
> Strongly.  The preference is VFREEBUSY request over VQUERY request.  
> Just allow both.  Everyone will be happy.

Users will not have a clue how the protocol is implemented. They
never see it. And as dynamically creating VFREEBUSY components
will involve exactly the same code ether way, then wrapped with
a CAP reply (which ever format is chosen) - I do not buy the
argument that one is faster than the other in any measurable way.

So for clarity, I am proposing that for CSs that do support
'RECUR EXPAND' and do support "VFREEBUSY":

    QUERY: SELECT * FROM VFREEBUSY
     WHERE dtstart >= start range
     AND dtend <= enduring

  The value of STATE is irrelevant as they are only created
  dynamically. And if STATE is supplied it MUST be ignored.


Then all queries for any components are exactly the same.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms070300000000030606060905
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjMyMDAwMTdaMCMGCSqGSIb3DQEJBDEWBBRw
a/8PJPg22JU7qoyvxDYyjf9sDDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQCGYnpcZyBmWz2DLAH6pd2/XlsSqcBGEi9kQinIASx/cWQm
MrU+NImWR3IQ8cSKy9j0DdQuUH45VpsawDjOk//oNLaXRxtAVpKxSgC8WiW+6Fs+XXqUXvEJ
S9RuD4SCg1VLMjSXRPtKF7qxwmz0DbPHyrjX/Q6+ofM25izPD9zeslEHcZVHxAIQUs9ZMNVa
TfjFzyOEo4cOUeW1JxJSdMbVEd+IaI1A99gIGXmAFRRSQhMx7dHnU9kSKhwPvD58fD+4V4yp
Sbm16niXzZq21U7uY1Lnz27bLYibXSGJwOq+NbjON/lXhFaXV4P+4dYkOZ2o+6SPQx6XShFJ
9UDB1scMAAAAAAAA
--------------ms070300000000030606060905--



From owner-ietf-calendar@mail.imc.org  Wed Jul 23 16:23:13 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01348
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 16:23:12 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NKEoqt068047
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 13:14:50 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NKEoH1068046
	for ietf-calendar-bks; Wed, 23 Jul 2003 13:14:50 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NKEnqt068041
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 13:14:49 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Wed, 23 Jul 2003 14:13:09 -0600
Message-Id: <sf1e97f4.065@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 23 Jul 2003 14:15:42 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request;
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part5B0577FE.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__Part5B0577FE.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Doug wrote
> Craig Johnson wrote:
> 
> > On the contrary, from our experience users/customers DO care.  
> > Strongly.  The preference is VFREEBUSY request over VQUERY request.
 
> > Just allow both.  Everyone will be happy.
 
> Users will not have a clue how the protocol is implemented. They
> never see it.
 
The users/customers I am referring to are creating applications against
our CAP implementation.  They are NOT end users.  They see the protocol.
 They care.  They have voiced their opinion.

--=__Part5B0577FE.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Doug wrote</DIV>
<DIV>&gt; Craig Johnson wrote:<BR>&gt; <BR>&gt; &gt; On the contrary, from our experience users/customers DO care.&nbsp; <BR>&gt; &gt; Strongly.&nbsp; The preference is VFREEBUSY request over VQUERY request.&nbsp; <BR>&gt; &gt; Just allow both.&nbsp; Everyone will be happy.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; Users will not have a clue how the protocol is implemented. They<BR>&gt; never see it.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;users/customers I am referring to are creating applications against&nbsp;our CAP implementation.&nbsp; They are NOT end users.&nbsp; They see the protocol.&nbsp; They care.&nbsp;&nbsp;They have voiced their opinion.</DIV></BODY></HTML>
--=__Part5B0577FE.0__=--


From owner-ietf-calendar@mail.imc.org  Wed Jul 23 16:29:40 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01479
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 16:29:39 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NKDnqt067988
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 13:13:49 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NKDn0S067987
	for ietf-calendar-bks; Wed, 23 Jul 2003 13:13:49 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NKDmqt067982
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 13:13:48 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6NKDcEB007742
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 13:13:46 -0700
Message-ID: <3F1EEC6D.6020803@Royer.com>
Date: Wed, 23 Jul 2003 14:13:33 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: Cap Free-Busy Request; some compelling thoughts
References: <sf1e8733.034@gw.provo.novell.com>
In-Reply-To: <sf1e8733.034@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060005020100070405060708"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060005020100070405060708
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



QUERY and iTIP are not the same thing. Different topics.


Craig Johnson wrote:
> B Kahn wrote:
>  >  iTIP busytime REQUEST/REPLY can be done "real-time"; there is no 
> store-and-forward
>  >  lag inherent in iTIP.  iMIP is the store-and-forward binding (aka 
> email binding) of iTIP.  
>  >  CAP is a superset of what started out as iRIP, the real-time binding 
> of iTIP.
>  >  In CAP it should just be a matter of using an iTIP Section 3.3.2 
> REQUEST whose response
>  >  is an iTIP Section 3.3.3 REPLY message.
> <snip>
>  >  so since the CAP server needs to generate some kind of response for 
> the VFREEBUSY REQUEST
>  >  its logical that it generate this.  
> This is contrary to your post of 31 Mar 2003 17:34:53...
>  
>  >  ... if my CUA CREATEs a VFREEBUSY with METHOD:REQUEST, all I get 
> back is essentially a "Yes, your VFREEBUSY
>  >  was created in the TARGET", NOT the actual results Im querying for!  
> So how does my CUA get the RESULTS of
>  > the query?? CAP is realtime so I would assume that the query/response 
> for busy time woud/should be realtime too!.
>  
> Your earlier post was correct.  You can't do CAP iTIP 'real-time' 
> VFREEBUSY request.


In Bruce's 2nd paragraph that you quoted, the is saying
that CAP lacked any text to describe what to do. Both are correct.

He was also proposing that the response from a:

  CMD:CREATE/METHOD:REQUEST on a VFREEBUSY

be a dynamically created VREPLY containing a:

  CMD:REPLY/METHOD:REPLY VFREEBUSY component.

And NOT just an 'okay' VREPLY.

If we are going to do both a query and iTIP  then lets
be compatible and not invent something new.

I would prefer only the QUERY be allowed as even if
we mandate the VREPLY containing a VFREEBUSY, the query
syntax is still valid and would therefore have to also
be supported.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060005020100070405060708
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjMyMDEzMzNaMCMGCSqGSIb3DQEJBDEWBBSU
V7vM364dWTZiIzPGC9YM5tRfRDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQAxBOc4FP7uAxKgHdbvYEOi3GQI32nrYsfE09igNSCrH9wL
4hyuipGJMsy0PGbVidH+Xpfmb2VDUnMoWB3mnLrj74hF2+l4MzKgc4M4Ol+yfOL62il46m6H
toSMjyFeGqe04cR8BrFcQ6dNjjQIoDD5UU84/oSnT2L4b0vFwX39jESY6NGA1zIshRUSXW7N
ojo6lbqTH6DH9dU2VwU0RiidT7wniLpy5IavOwqoRvRrQ80yPHW2Zye4eFtJvk90NXYCpIxP
NtjgnSx+EVunwr6aSfSnEJgO08WRtMLkHWsqlHxLSmnpY4/Bg4VPk0ijIzJeh3j3C9rGtJHo
JIDOvEYSAAAAAAAA
--------------ms060005020100070405060708--



From owner-ietf-calendar@mail.imc.org  Wed Jul 23 19:55:35 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08124
	for <calsch-archive@lists.ietf.org>; Wed, 23 Jul 2003 19:55:34 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NNgHqt079729
	for <ietf-calendar-bks@above.proper.com>; Wed, 23 Jul 2003 16:42:17 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6NNgGMj079728
	for ietf-calendar-bks; Wed, 23 Jul 2003 16:42:16 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6NNgGqt079723
	for <ietf-calendar@imc.org>; Wed, 23 Jul 2003 16:42:16 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Wed, 23 Jul 2003 17:40:36 -0600
Message-Id: <sf1ec894.008@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 23 Jul 2003 17:43:05 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: free-busy QUERY
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartCC92E199.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__PartCC92E199.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Doug Proposed:
 
> So for clarity, I am proposing that for CSs that do support
> 'RECUR EXPAND' and do support "VFREEBUSY":
>
>     QUERY: SELECT * FROM VFREEBUSY
>      WHERE dtstart >= start range
>      AND dtend <= enduring
 
The query does not work in the following cases:  
It excludes vfreebusys(vevents) that overlap the start of the period of
interest (ie that start before startrange and end after startrange).
It excludes vfreebusys(vevents) that overlap the end of the period of
interest (ie that start before endrange and end after endrange).
Try this:
 
    WHERE dtstart < endrange
    AND   dtend   > startrange
 
>   The value of STATE is irrelevant as they are only created
>   dynamically. And if STATE is supplied it MUST be ignored.
 
Unless I missed something, that severly cripples iTIP VFREEBUSY.  
How is a CUA supposed to retrieve unprocessed iTIP VFREEBUSY objects if
STATE is now ignored?  The following will no longer work:
 
     QUERY: Select * from VFREEBUSY
      WHERE STATE() = 'unprocessed'
 
Instead of returning iTIP VFREEBUSYs the above query returns
dynamically generated VFREEBUSYs ... ALL of them.
I may want to retrieve iTIP VFREEBUSY objects from a VAGENDA for a
specific time period.  The query would look very similar to the first
query above:
 
      QUERY: SELECT * FROM VFREEBUSY
       WHERE dtstart < endrange
       AND   dtend   > startrange
       AND   STATE() = 'unprocessed'
 
However, because STATE is ignored I will get a dynamic VFREEBUSYs and
not the iTIP VFREEBUSYs I wanted.
 
I understand your eagerness to simplify the free-busy QUERY, but I'm
not convinced you can omit STATE for VFREEBUSY.  Maybe you have
something else in mind.  Please avoid 'special case' handling of
VFREEBUSY and STATE just to keep it simple.  Let's keep it consistent
with the syntax for other components (VEVENTS, etc.)
 

--=__PartCC92E199.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Doug Proposed:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; So for clarity, I am proposing that for CSs that do support<BR>&gt; 'RECUR EXPAND' and do support "VFREEBUSY":<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; QUERY: SELECT * FROM VFREEBUSY<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WHERE dtstart &gt;= start range<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND dtend &lt;= enduring</DIV>
<DIV>&nbsp;</DIV>
<DIV>The query does not work in the following cases:&nbsp; <BR>It excludes vfreebusys(vevents) that overlap the start of the period of interest (ie that start before startrange and end after startrange).<BR>It excludes vfreebusys(vevents) that overlap the end of the period of interest (ie that start before endrange and end after endrange).<BR>Try this:</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Courier>&nbsp;&nbsp;&nbsp; WHERE dtstart &lt; endrange<BR>&nbsp;&nbsp;&nbsp; AND&nbsp;&nbsp; dtend&nbsp;&nbsp; &gt; startrange</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&nbsp;&nbsp; The value of STATE is irrelevant as they are only created<BR>&gt;&nbsp;&nbsp; dynamically. And if STATE is supplied it MUST be ignored.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Unless I missed something, that severly cripples iTIP VFREEBUSY.&nbsp; </DIV>
<DIV>How is a CUA supposed to retrieve unprocessed iTIP VFREEBUSY objects if STATE is now ignored?&nbsp; The following will no longer work:</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Courier>&nbsp;&nbsp;&nbsp;&nbsp; QUERY: Select * from VFREEBUSY<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WHERE STATE() = 'unprocessed'</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>Instead of returning iTIP VFREEBUSYs the above query returns&nbsp;dynamically generated VFREEBUSYs ... ALL of them.<BR>I may want to retrieve iTIP VFREEBUSY objects from a VAGENDA&nbsp;for a specific time period.&nbsp; The query would&nbsp;look very similar to the first query above:</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Courier>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QUERY: SELECT * FROM VFREEBUSY<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WHERE dtstart &lt; endrange<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND&nbsp;&nbsp; dtend&nbsp;&nbsp; &gt; startrange<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND&nbsp;&nbsp; STATE() = 'unprocessed'</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>However, because STATE is ignored I will get a&nbsp;dynamic VFREEBUSYs and not the iTIP VFREEBUSYs I wanted.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I understand your eagerness to simplify the free-busy QUERY, but I'm not convinced you can omit STATE for VFREEBUSY.&nbsp;&nbsp;Maybe you have something else in mind.&nbsp; Please avoid 'special case' handling of VFREEBUSY and STATE just to keep it simple.&nbsp; Let's&nbsp;keep it consistent with the syntax for other components (VEVENTS, etc.)</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>
--=__PartCC92E199.0__=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 24 10:48:08 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09727
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 10:48:08 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OEZpqt053161
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 07:35:51 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OEZpa7053160
	for ietf-calendar-bks; Thu, 24 Jul 2003 07:35:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OEZoqt053154
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 07:35:51 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <sf1e8733.034@gw.provo.novell.com>
To: "Craig Johnson" <cjohnson@gw.novell.com>
Cc: ietf-calendar@imc.org
Subject: Re: Cap Free-Busy Request; some compelling thoughts
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_07142003NP July 14, 2003
Message-ID: <OF7FAB51E5.7F1F2CCD-ON85256D6D.004EF17B-85256D6D.004FDCD6@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 24 Jul 2003 10:35:47 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Release 6.0.2CF2|July 18, 2003) at 07/24/2003
 10:35:41 AM,
	Serialize complete at 07/24/2003 10:35:41 AM
Content-Type: multipart/alternative; boundary="=_alternative 004FDCD085256D6D_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 004FDCD085256D6D_=
Content-Type: text/plain; charset="US-ASCII"

Craig responded on 07/23/2003 03:04:03 PM:
> >  In CAP it should just be a matter of using an iTIP Section 3.3.2 
> REQUEST whose response 
> >  is an iTIP Section 3.3.3 REPLY message.
> <snip> 
> >  so since the CAP server needs to generate some kind of response 
> for the VFREEBUSY REQUEST 
> >  its logical that it generate this. 
> This is contrary to your post of 31 Mar 2003 17:34:53...

The phrase I think you missed in my reply was "In CAP it _should_...".  I 
did not say "In CAP it does...".  The essential points are:

1: iTIP is NOT the limiting factor here; its not "store-and-forward" only, 
it can be done "real-time" w/o any changes.
2: What CAP does and what it should do not always match. 

> Your earlier post was correct.  You can't do CAP iTIP 'real-time' 
> VFREEBUSY request.

The last point jives w/my previous posting that you correctly cited.   I 
am too busy in Real Work (TM) to keep up w/the other threads so if your 
proposal is a way to resolve this then I think the WG should consider it. 

After all in order to do Scheduling (as in Calendaring & Scheduling) you 
really need to have some way to check busytime; it makes the entire 
process so much smoother for everyone!

Bruce
===========================================================================
Bruce Kahn                                INet: 
Bruce_Kahn@notesdev.ibm.com
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Warning: Dates in Calendar are closer than they appear.
--=_alternative 004FDCD085256D6D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Craig responded on 07/23/2003 03:04:03 PM:<br>
&gt; &gt; &nbsp;In CAP it should just be a matter of using an iTIP Section
3.3.2 <br>
&gt; REQUEST whose response </tt></font>
<br><font size=2><tt>&gt; &gt; &nbsp;is an iTIP Section 3.3.3 REPLY message.<br>
&gt; &lt;snip&gt; <br>
&gt; &gt; &nbsp;so since the CAP server needs to generate some kind of
response <br>
&gt; for the VFREEBUSY REQUEST </tt></font>
<br><font size=2><tt>&gt; &gt; &nbsp;its logical that it generate this.
&nbsp; </tt></font>
<br><font size=2><tt>&gt; This is contrary to your post of 31 Mar 2003
17:34:53...</tt></font>
<br>
<br><font size=2 face="sans-serif">The phrase I think you missed in my
reply was &quot;In CAP it <u>_should_</u>...&quot;. &nbsp;I did not say
&quot;In CAP it does...&quot;. &nbsp;The essential points are:</font>
<br>
<br><font size=2 face="sans-serif">1: iTIP is NOT the limiting factor here;
its not &quot;store-and-forward&quot; only, it can be done &quot;real-time&quot;
w/o any changes.</font>
<br><font size=2 face="sans-serif">2: What CAP does and what it should
do not always match. &nbsp;</font>
<br>
<br><font size=2><tt>&gt; Your earlier post was correct. &nbsp;You can't
do CAP iTIP 'real-time' <br>
&gt; VFREEBUSY request.</tt></font>
<br>
<br><font size=2 face="sans-serif">The last point jives w/my previous posting
that you correctly cited. &nbsp; I am too busy in Real Work (TM) to keep
up w/the other threads so if your proposal is a way to resolve this then
I think the WG should consider it. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">After all in order to do Scheduling
(as in Calendaring &amp; Scheduling) you really need to have some way to
check busytime; it makes the entire process so much smoother for everyone!</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Warning: Dates in Calendar are closer than they appear.</font>
--=_alternative 004FDCD085256D6D_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 24 11:42:39 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11332
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 11:42:38 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OFYCqt055849
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 08:34:12 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OFYChN055848
	for ietf-calendar-bks; Thu, 24 Jul 2003 08:34:12 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OFYBqt055843
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 08:34:11 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6OFY9EB016352
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 08:34:11 -0700
Message-ID: <3F1FFC6B.8060701@Royer.com>
Date: Thu, 24 Jul 2003 09:34:03 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: free-busy QUERY
References: <sf1ec894.008@gw.provo.novell.com>
In-Reply-To: <sf1ec894.008@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020608020901080509070005"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020608020901080509070005
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Craig Johnson wrote:
> Doug Proposed:
>  
>  > So for clarity, I am proposing that for CSs that do support
>  > 'RECUR EXPAND' and do support "VFREEBUSY":
>  >
>  >     QUERY: SELECT * FROM VFREEBUSY
>  >      WHERE dtstart >= start range
>  >      AND dtend <= enduring
>  
> The query does not work in the following cases: 
> It excludes vfreebusys(vevents) that overlap the start of the period of 
> interest (ie that start before startrange and end after startrange).
> It excludes vfreebusys(vevents) that overlap the end of the period of 
> interest (ie that start before endrange and end after endrange).
> Try this:
>  
>     WHERE dtstart < endrange
>     AND   dtend   > startrange

Thanks.

>  >   The value of STATE is irrelevant as they are only created
>  >   dynamically. And if STATE is supplied it MUST be ignored.
>  
> Unless I missed something, that severly cripples iTIP VFREEBUSY. 
> How is a CUA supposed to retrieve unprocessed iTIP VFREEBUSY objects if 
> STATE is now ignored?  The following will no longer work:

Because they are useless for CSs that support EXPAND-RECUR. No point
in saving them or fetching them. If the CS is to dynamically create
the results, who would ever fetch the static ones? Why?

>      QUERY: Select * from VFREEBUSY
>       WHERE STATE() = 'unprocessed'
>  
> Instead of returning iTIP VFREEBUSYs the above query returns dynamically 
> generated VFREEBUSYs ... ALL of them.
> I may want to retrieve iTIP VFREEBUSY objects from a VAGENDA for a 
> specific time period.  The query would look very similar to the first 
> query above:
>  
>       QUERY: SELECT * FROM VFREEBUSY
>        WHERE dtstart < endrange
>        AND   dtend   > startrange
>        AND   STATE() = 'unprocessed'
>  
> However, because STATE is ignored I will get a dynamic VFREEBUSYs and 
> not the iTIP VFREEBUSYs I wanted.

How would you ever use the static VFREEBUSY's?


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020608020901080509070005
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjQxNTM0MDNaMCMGCSqGSIb3DQEJBDEWBBTH
9iKjBsulbYRvWCOWG7pWxjXpLjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQCLGPy5w9rtJeIH8OVyH0Eir6NJGYS9cINRkc4ba10sgsmz
kkR39FxIIxkbMv90wCNcZBbsQnIBQhevGZOc+NCbEfQYQVemY50ttV1RICiKWmf2wFVDYSUK
OMPjdWdzxK+aj+W2mr4CUQuVdtUVmL9IvhtfeB8PJ6jhR/w9PeKqB4WTd7QtcvYi8LZkuzeY
04FyfbD8++Tp1waXPumStSy/Dz6HTZ+SKdxbvde5NHxvFr4ORykDHfhyw132rRGKTNWFTTsn
nMvIQUZBD4bMKKgaitKu8fXiDDaMkCyCrEzQMAT/F6dQF2z9i76CC52dBY2v/u1LcWcCB+RF
vdIJSK1FAAAAAAAA
--------------ms020608020901080509070005--



From owner-ietf-calendar@mail.imc.org  Thu Jul 24 11:57:37 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11760
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 11:57:34 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OFlrqt056297
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 08:47:53 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OFlqgm056296
	for ietf-calendar-bks; Thu, 24 Jul 2003 08:47:52 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OFlpqt056289
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 08:47:52 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <sf1ec894.008@gw.provo.novell.com>
To: ietf-calendar@imc.org
Subject: Re: free-busy QUERY
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_07142003NP July 14, 2003
Message-ID: <OFCE19BD0A.264F0333-ON85256D6D.00500E1E-85256D6D.005629C9@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Thu, 24 Jul 2003 11:44:36 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Release 6.0.2CF2|July 18, 2003) at 07/24/2003
 11:47:39 AM,
	Serialize complete at 07/24/2003 11:47:39 AM
Content-Type: multipart/alternative; boundary="=_alternative 005629C485256D6D_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 005629C485256D6D_=
Content-Type: text/plain; charset="US-ASCII"

Craig wrote on 07/23/2003 07:43:05 PM:
> Try this:
> 
>     WHERE dtstart < endrange
>     AND   dtend   > startrange

Yep, thats the correct formula.  Extra credit to those (besides Craig) who 
can demonstrate why...

> >   The value of STATE is irrelevant as they are only created
> >   dynamically. And if STATE is supplied it MUST be ignored.
> 
> Unless I missed something, that severly cripples iTIP VFREEBUSY. 
> How is a CUA supposed to retrieve unprocessed iTIP VFREEBUSY objects
> if STATE is now ignored?  The following will no longer work:
> 
>      QUERY: Select * from VFREEBUSY
>       WHERE STATE() = 'unprocessed'

Umm, VFREEBUSYs should be generated to reflect the _other_ contents of the 
TARGETed calendar (VAGENDA).  They do NOT have any 'state' of their own. 
You do not set the VFREEBUSYs state to 'booked', 'deleted', etc. as thats 
just non-sensensical.

Do not confuse that with the iTIP REQUEST/REPLY workflow where busytime is 
asked for and returned.  The difference is that recipients of the 
VFREEBUSY data do no treat it like a REPLY for a VEVENT that needs to be 
reflected in the Organizers 'booked' copy, they treat the busytime data as 
information useful in performing scheduling with other users.  The 
Organizer does not 'process' the VFREEBUSY by doing actions like doing 
DECLINE-COUNTER or modifying their copy to reflect delegation, etc; they 
simply use the data then and there.

As such STATE() is a meaningless factor on the QUERY when VFREEBUSYs are 
involved.  The data inside the VFREEBUSY response is essentially a summary 
of the ATTENDEEs free/busy time, it represents an extraction of data from 
other components in the calendar.  In fact nearly ALL of the cap-factor 
nodes in the ABNF are non-sensical for VFREEBUSYs (what the hell does "NOT 
LIKE" mean in this context??). 

I do agree w/Doug that meaningless query factors MUST be ignored but there 
is NO prose in 6.1.1.  CAL-QUERY Value Type to this effect.  I think some 
prose is definitely in order on this topic.  A simple line or two like 
"Any query factor that is in error or meaningless MUST be ignored.   For 
example, using STATE() = "fizbin" or DTEND LIKE "TODAY" should result in 
that query factor being ignored.".  The only question that remains then is 
does the CS indicate this in some way to the CUA and if so, how??

Now some may argue that the Organzier may want to preserve the VFREEBUSY 
data for later use (kind of like reading but not 'processing' a REPLY to 
an event).  However this is not reasonable behaviour in a real-time 
environment.  The VFREEBUSY data may be stale by that later time.  In a 
real-time system like CAP the Organzier should perform another VFREEBUSY 
search so they get the most accurate busytime picture for the invitees as 
possible.

> Instead of returning iTIP VFREEBUSYs the above query returns 
> dynamically generated VFREEBUSYs ... ALL of them.

VFREEBUSYs should always be dynamically generated in my view of things but 
some folks do not share that opinion.  Thats fine by me.  Ive owned the 
busytime system in Lotus Notes for 5+ years now so I think I have a feel 
for how well this works and how a CS can do it efficiently.

Generating static VFREEBUSYs is viable for some cases but since the 
generator cannot guarantee that their staticlly generated VFREEBUSYs will 
exactly match the intervals requested there are 2 possible options: The CS 
manually trims down or joins multiple static VFREEBUSYs into a single 
response that matches the requested interval OR the CUA is expected to 
take all the VFREEBUSY data that the CS sends, sift thru it to find what 
it wants and toss what it does not want.  This can be done but its either 
extra cycles for the CS (former case) or its lots of wasted network 
bandwidth and CUA cycles (latter case).  The latter case is also a concern 
for those thin client fans out there...

>       QUERY: SELECT * FROM VFREEBUSY
>        WHERE dtstart < endrange
>        AND   dtend   > startrange
>        AND   STATE() = 'unprocessed'
> 
> However, because STATE is ignored I will get a dynamic VFREEBUSYs 
> and not the iTIP VFREEBUSYs I wanted.

Ahh, now I see your case better: You want to get both the dynamic CS 
genreated VFREEBUSY data for the specific interval AND the iMIP VFREEBUSY 
REPLYs that the CUA may have sent out all in 1 operation. 

If any CUA actually did busytime lookups over iMIP I could agree to this 
scenario.  However so far not a single CUA at any CalConnect has 
demonstrated VFREEBUSY REQUEST/REPLY abilities over iMIP.  The reason Ive 
heard for this is that although it _can_ be done, the lag makes the 
response inherently useless to the Organzier when they are sitting in 
their calendar trying to schedule a meeting.  Users want immediate 
responses for busytime, not some unknown lag inherent in iMIP.

Does anyone know of any CUAs that actually do VFREEBUSY REQUEST/REPLY? 
Please speak up now so we can decide if this is a viable case to factor 
into the CAP design.  I suspect it is not a scenario we need to consider 
though.   I  could see wanting to keep the ability in CAP to at least be 
able to find and remove these from the users queue so whats the way to go 
on this...

FWIW: CAP appears to be divergent from iTIP in doing VFREEBUSY 
REQUEST/REPLYs given what Ive read so far in these recent threads.  It 
seems that the current expectation is that the CUA would do a:

   C: Content-Type: text/calendar
   C:
   C: BEGIN:VCALENDAR
   C: VERSION:2.0
   C: PRODID:-//ACME/DesktopCalendar//EN
   C: CMD:SEARCH
   C: TARGET:relcalB
   C: TARGET:relcalC
   C: BEGIN:VQUERY
   C: QUERY:SELECT * FROM VFREEBUSY
   C:  WHERE DTEND > '19990310T080000Z'
   C:  AND DTSTART < '19990310T190000Z'
   C: END:VQUERY
   C: END:VCALENDAR

but thats NOT the way iTIP describes how the REQUEST is done:

   BEGIN:VCALENDAR
   PRODID:-//ACME/DesktopCalendar//EN
   METHOD:REQUEST
   VERSION:2.0
   BEGIN:VFREEBUSY
   ORGANIZER:Mailto:A@example.com
   ATTENDEE:Mailto:B@example.com
   ATTENDEE:Mailto:C@example.com
   DTSTAMP:19990303T190000Z
   DTSTART:19990310T080000Z
   DTEND:19990310T190000Z
   UID:calsrv.example.com-873970198738777@example.com
   END:VFREEBUSY
   END:VCALENDAR

Its not clear to me the CS can properly generate an iTIP VFREEBUSY REPLY 
since A) there are NO iTIP required properties (ie: ATTENDEE, ORGANIZER or 
UID) and B) unlike other CAP commands where the payload is in iTIP format, 
the SEARCH command does lend its payload to being in iTIP, its in 
CAL-QUERY.  The SEARCH command is semantically what the user wants (they 
want to search for other users busytime) but it does not lend itself to 
doing busytime searches that are iTIP compliant.  Bit of a quandry. 
Hmmm...

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 005629C485256D6D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Craig wrote on 07/23/2003 07:43:05 PM:<br>
&gt; Try this:</tt></font>
<br><font size=2><tt>&gt; &nbsp;</tt></font>
<br><font size=2><tt>&gt; &nbsp; &nbsp; WHERE dtstart &lt; endrange<br>
&gt; &nbsp; &nbsp; AND &nbsp; dtend &nbsp; &gt; startrange</tt></font>
<br>
<br><font size=2 face="sans-serif">Yep, thats the correct formula. &nbsp;Extra
credit to those (besides Craig) who can demonstrate why...</font>
<br>
<br><font size=2><tt>&gt; &gt; &nbsp; The value of STATE is irrelevant
as they are only created<br>
&gt; &gt; &nbsp; dynamically. And if STATE is supplied it MUST be ignored.</tt></font>
<br><font size=2><tt>&gt; &nbsp;</tt></font>
<br><font size=2><tt>&gt; Unless I missed something, that severly cripples
iTIP VFREEBUSY. &nbsp;</tt></font>
<br><font size=2><tt>&gt; How is a CUA supposed to retrieve unprocessed
iTIP VFREEBUSY objects<br>
&gt; if STATE is now ignored? &nbsp;The following will no longer work:</tt></font>
<br><font size=2><tt>&gt; &nbsp;</tt></font>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp;QUERY: Select * from VFREEBUSY<br>
&gt; &nbsp; &nbsp; &nbsp; WHERE STATE() = 'unprocessed'</tt></font>
<br>
<br><font size=2 face="sans-serif">Umm, VFREEBUSYs should be generated
to reflect the _<u>other</u>_ contents of the TARGETed calendar (VAGENDA).
&nbsp;They do NOT have any 'state' of their own. &nbsp;You do not set the
VFREEBUSYs state to 'booked', 'deleted', etc. as thats just non-sensensical.</font>
<br>
<br><font size=2 face="sans-serif">Do not confuse that with the iTIP REQUEST/REPLY
workflow where busytime is asked for and returned. &nbsp;The difference
is that recipients of the VFREEBUSY data do no treat it like a REPLY for
a VEVENT that needs to be reflected in the Organizers 'booked' copy, they
treat the busytime data as information useful in performing scheduling
with other users. &nbsp;The Organizer does not 'process' the VFREEBUSY
by doing actions like doing DECLINE-COUNTER or modifying their copy to
reflect delegation, etc; they simply use the data then and there.</font>
<br>
<br><font size=2 face="sans-serif">As such STATE() is a meaningless factor
on the QUERY when VFREEBUSYs are involved. &nbsp;The data inside the VFREEBUSY
response is essentially a summary of the ATTENDEEs free/busy time, it represents
an extraction of data from other components in the calendar. &nbsp;In fact
nearly ALL of the cap-factor nodes in the ABNF are non-sensical for VFREEBUSYs
(what the hell does &quot;NOT LIKE&quot; mean in this context??). &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">I do agree w/Doug that meaningless query
factors MUST be ignored but there is NO prose in 6.1.1.&nbsp; CAL-QUERY
Value Type to this effect. &nbsp;I think some prose is definitely in order
on this topic. &nbsp;A simple line or two like &quot;Any query factor that
is in error or meaningless MUST be ignored. &nbsp; For example, using STATE()
= &quot;fizbin&quot; or DTEND LIKE &quot;TODAY&quot; should result in that
query factor being ignored.&quot;. &nbsp;The only question that remains
then is does the CS indicate this in some way to the CUA and if so, how??</font>
<br>
<br><font size=2 face="sans-serif">Now some may argue that the Organzier
may want to preserve the VFREEBUSY data for later use (kind of like reading
but not 'processing' a REPLY to an event). &nbsp;However this is not reasonable
behaviour in a real-time environment. &nbsp;The VFREEBUSY data may be stale
by that later time. &nbsp;In a real-time system like CAP the Organzier
should perform another VFREEBUSY search so they get the most accurate busytime
picture for the invitees as possible.</font>
<br>
<br><font size=2><tt>&gt; Instead of returning iTIP VFREEBUSYs the above
query returns <br>
&gt; dynamically generated VFREEBUSYs ... ALL of them.<br>
</tt></font>
<br><font size=2 face="sans-serif">VFREEBUSYs should always be dynamically
generated in my view of things but some folks do not share that opinion.
&nbsp;Thats fine by me. &nbsp;Ive owned the busytime system in Lotus Notes
for 5+ years now so I think I have a feel for how well this works and how
a CS can do it efficiently.</font>
<br>
<br><font size=2 face="sans-serif">Generating static VFREEBUSYs is viable
for some cases but since the generator cannot guarantee that their staticlly
generated VFREEBUSYs will exactly match the intervals requested there are
2 possible options: The CS manually trims down or joins multiple static
VFREEBUSYs into a single response that matches the requested interval OR
the CUA is expected to take all the VFREEBUSY data that the CS sends, sift
thru it to find what it wants and toss what it does not want. &nbsp;This
can be done but its either extra cycles for the CS (former case) or its
lots of wasted network bandwidth and CUA cycles (latter case). &nbsp;The
latter case is also a concern for those thin client fans out there...</font>
<br>
<br><font size=2><tt>&gt; &nbsp; &nbsp; &nbsp; QUERY: SELECT * FROM VFREEBUSY<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;WHERE dtstart &lt; endrange<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;AND &nbsp; dtend &nbsp; &gt; startrange<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;AND &nbsp; STATE() = 'unprocessed'</tt></font>
<br><font size=2><tt>&gt; &nbsp;</tt></font>
<br><font size=2><tt>&gt; However, because STATE is ignored I will get
a dynamic VFREEBUSYs <br>
&gt; and not the iTIP VFREEBUSYs I wanted.</tt></font>
<br>
<br><font size=2 face="sans-serif">Ahh, now I see your case better: You
want to get both the dynamic CS genreated VFREEBUSY data for the specific
interval AND the iMIP VFREEBUSY REPLYs that the CUA may have sent out all
in 1 operation. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">If any CUA actually did busytime lookups
over iMIP I could agree to this scenario. &nbsp;However so far not a single
CUA at any CalConnect has demonstrated VFREEBUSY REQUEST/REPLY abilities
over iMIP. &nbsp;The reason Ive heard for this is that although it _can_
be done, the lag makes the response inherently useless to the Organzier
when they are sitting in their calendar trying to schedule a meeting. &nbsp;Users
want immediate responses for busytime, not some unknown lag inherent in
iMIP.</font>
<br>
<br><font size=2 face="sans-serif">Does anyone know of any CUAs that actually
do VFREEBUSY REQUEST/REPLY? &nbsp;Please speak up now so we can decide
if this is a viable case to factor into the CAP design. &nbsp;I suspect
it is not a scenario we need to consider though. &nbsp; I &nbsp;could see
wanting to keep the ability in CAP to at least be able to find and remove
these from the users queue so whats the way to go on this...</font>
<br>
<br><font size=2 face="sans-serif">FWIW: CAP appears to be divergent from
iTIP in doing VFREEBUSY REQUEST/REPLYs given what Ive read so far in these
recent threads. &nbsp;It seems that the current expectation is that the
CUA would do a:</font>
<br>
<br><font size=2 color=#333333><tt>&nbsp; &nbsp;C: Content-Type: text/calendar<br>
 &nbsp; C:<br>
 &nbsp; C: BEGIN:VCALENDAR<br>
 &nbsp; C: VERSION:2.0<br>
 &nbsp; C: PRODID:</tt></font><font size=2><tt>-//ACME/DesktopCalendar//EN</tt></font><font size=2 color=#333333><tt><br>
 &nbsp; C: CMD:SEARCH<br>
 &nbsp; C: TARGET:relcalB<br>
 &nbsp; C: TARGET:relcalC<br>
 &nbsp; C: BEGIN:VQUERY<br>
 &nbsp; C: QUERY:SELECT * FROM VFREEBUSY<br>
 &nbsp; C: &nbsp;WHERE DTEND &gt; '19990310T080000Z'<br>
 &nbsp; C: &nbsp;AND DTSTART &lt; '19990310T190000Z'<br>
 &nbsp; C: END:VQUERY<br>
 &nbsp; C: END:VCALENDAR<br>
</tt></font>
<br><font size=2 face="sans-serif">but thats NOT the way iTIP describes
how the REQUEST is done:</font>
<br>
<br><font size=2><tt>&nbsp; &nbsp;BEGIN:VCALENDAR<br>
 &nbsp; PRODID:-//ACME/DesktopCalendar//EN<br>
 &nbsp; METHOD:REQUEST<br>
 &nbsp; VERSION:2.0<br>
 &nbsp; BEGIN:VFREEBUSY<br>
 &nbsp; ORGANIZER:Mailto:A@example.com<br>
 &nbsp; ATTENDEE:Mailto:B@example.com<br>
 &nbsp; ATTENDEE:Mailto:C@example.com<br>
 &nbsp; DTSTAMP:19990303T190000Z<br>
 &nbsp; DTSTART:</tt></font><font size=2 color=#333333><tt>19990310T080000Z</tt></font><font size=2><tt><br>
 &nbsp; DTEND:</tt></font><font size=2 color=#333333><tt>19990310T190000Z</tt></font><font size=2><tt><br>
 &nbsp; UID:calsrv.example.com-873970198738777@example.com<br>
 &nbsp; END:VFREEBUSY<br>
 &nbsp; END:VCALENDAR<br>
</tt></font>
<br><font size=2 face="sans-serif">Its not clear to me the CS can properly
generate an iTIP VFREEBUSY REPLY since A) there are NO iTIP required properties
(ie: ATTENDEE, ORGANIZER or UID) and B) unlike other CAP commands where
the payload is in iTIP format, the SEARCH command does lend its payload
to being in iTIP, its in CAL-QUERY. &nbsp;The SEARCH command is semantically
what the user wants (they want to search for other users busytime) but
it does not lend itself to doing busytime searches that are iTIP compliant.
&nbsp;Bit of a quandry. Hmmm...</font>
<br>
<br><font size=2 face="sans-serif">Bruce</font>
<br><font size=2 face="sans-serif">===========================================================================<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce_Kahn@notesdev.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Standard disclaimers apply, even where prohibited by law...</font>
--=_alternative 005629C485256D6D_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 24 12:27:44 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12808
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 12:27:42 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OGHiqt057817
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 09:17:44 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OGHicf057816
	for ietf-calendar-bks; Thu, 24 Jul 2003 09:17:44 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OGHhqt057810
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 09:17:43 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6OGHgEB016740
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 09:17:43 -0700
Message-ID: <3F2006A0.4050709@Royer.com>
Date: Thu, 24 Jul 2003 10:17:36 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: free-busy QUERY
References: <OFCE19BD0A.264F0333-ON85256D6D.00500E1E-85256D6D.005629C9@notesdev.ibm.com>
In-Reply-To: <OFCE19BD0A.264F0333-ON85256D6D.00500E1E-85256D6D.005629C9@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070500080202050501010109"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms070500080202050501010109
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit




>  >       QUERY: SELECT * FROM VFREEBUSY
>  >        WHERE dtstart < endrange
>  >        AND   dtend   > startrange
>  >        AND   STATE() = 'unprocessed'
>  >  
>  > However, because STATE is ignored I will get a dynamic VFREEBUSYs
>  > and not the iTIP VFREEBUSYs I wanted.
> 
> Ahh, now I see your case better: You want to get both the dynamic CS 
> genreated VFREEBUSY data for the specific interval AND the iMIP 
> VFREEBUSY REPLYs that the CUA may have sent out all in 1 operation.  
> 
> If any CUA actually did busytime lookups over iMIP I could agree to this 
> scenario.  However so far not a single CUA at any CalConnect has 
> demonstrated VFREEBUSY REQUEST/REPLY abilities over iMIP.  The reason 
> Ive heard for this is that although it _can_ be done, the lag makes the 
> response inherently useless to the Organzier when they are sitting in 
> their calendar trying to schedule a meeting.  Users want immediate 
> responses for busytime, not some unknown lag inherent in iMIP.
> 
> Does anyone know of any CUAs that actually do VFREEBUSY REQUEST/REPLY? 
>  Please speak up now so we can decide if this is a viable case to factor 
> into the CAP design.  I suspect it is not a scenario we need to consider 
> though.   I  could see wanting to keep the ability in CAP to at least be 
> able to find and remove these from the users queue so whats the way to 
> go on this...

And as the CS is not an iMIP aware MUA it would not be its job to worry
about any iMIP objects. The CUA if acting as an iMIP agent can generate
any iMIP replies from the results it gets back from the CS.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms070500080202050501010109
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjQxNjE3MzZaMCMGCSqGSIb3DQEJBDEWBBSw
1WcCYbQSosAbvouY+qTk2PYgADBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQAMg7lqTlyOF4nnBvpeOBG8U/Tq7t2LoNOYtpsKOw0U+jwq
ASQkJt+h8K+2A7B/dNn99M3SGCFwdNGySzAUn5Fov++pgthsPOxzMem3bmhD05/N57kKNGK9
faotGNSeyoSRQ8BM7cNfvCBfzPAzll9T2qwZzTtLNdV22wnHEK+G/Tb+SoezMuxBcTnPHjC+
IMO+IAG7uDBad3nn0b3qo8PuIU6LcFOeKw06sDwcSjyY6YkQtTBthzIZHG8hqDoiJpBWSLNU
qnOJMweEz1QvPgV9AQ0Xt8ifxUCCqmmh63Y1RQoA6FANwZaJwXMU9fbyrFMEX9/Oa3S6xZl+
s8KuzpQIAAAAAAAA
--------------ms070500080202050501010109--



From owner-ietf-calendar@mail.imc.org  Thu Jul 24 13:20:50 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16664
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 13:20:50 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OHAMqt059545
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 10:10:22 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OHAMCQ059543
	for ietf-calendar-bks; Thu, 24 Jul 2003 10:10:22 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OHAKqt059532
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 10:10:20 -0700 (PDT)
	(envelope-from PStephenson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Thu, 24 Jul 2003 11:08:30 -0600
Message-Id: <sf1fbe2e.018@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Thu, 24 Jul 2003 11:09:56 -0600
From: "Preston Stephenson" <PStephenson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Clarification on SEARCH command
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


When I first read the SEARCH command, I think I misunderstood it. I got
confused with rule (7) and cases (a, b and c) in 6.1.1. I took that to
mean the component as well as the sub component.

Based on sections 6.1.1 CAL-QUERY Value Type and 10.8 SEARCH Command,
which is the correct response to:

BEGIN:VCALENDAR
VERSION:2.0
CMD:SEARCH
TARGET:mytarget
BEGIN:VQUERY
QUERY:SELECT DTSTART,DTEND,SUMMARY,UID FROM VEVENT
END:VQUERY
END:VCALENDAR

(no component)
BEGIN:VCALENDAR
VERSION:2.0
CMD:REPLY
TARGET:mytarget
BEGIN:VREPLY
REQUEST-STATUS:2.0
DTSTART:20030725200000Z
DTEND:20030725203000Z
SUMMARY:Event1
UID:Uid1
DTSTART:20030725210000Z
DTEND:20030725213000Z
SUMMARY:Event2
UID:Uid2
END:VREPLY

(component)
BEGIN:VCALENDAR
VERSION:2.0
CMD:REPLY
TARGET:mytarget
BEGIN:VREPLY
REQUEST-STATUS:2.0
BEGIN:VEVENT
DTSTART:20030725200000Z
DTEND:20030725203000Z
SUMMARY:Event1
UID:Uid1
END:VEVENT
BEGIN:VEVENT
DTSTART:20030725210000Z
DTEND:20030725213000Z
SUMMARY:Event2
UID:Uid2
END:VEVENT
END:VREPLY

As always, if you are putting in more examples, that would be great.

Thanks.
Preston



From owner-ietf-calendar@mail.imc.org  Thu Jul 24 14:56:27 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21552
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 14:56:26 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OIkLqt064489
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 11:46:21 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OIkL9I064488
	for ietf-calendar-bks; Thu, 24 Jul 2003 11:46:21 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OIkKqt064483
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 11:46:20 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Thu, 24 Jul 2003 12:44:35 -0600
Message-Id: <sf1fd4b3.031@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Thu, 24 Jul 2003 12:47:10 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>, <Bruce_Kahn@notesdev.ibm.com>
Subject: Re: free-busy QUERY
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartE0BEF2BE.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__PartE0BEF2BE.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

B Kahn Wrote:
 
> FWIW: CAP appears to be divergent from iTIP in doing 
> VFREEBUSY REQUEST/REPLYs given what I've read so far 
> in these recent threads.
 
YES!! YES!!  Thank-you! Thank-you!  That's one of the points I've been
making (or trying to).
 
The ability to deal with free-busy information is fundamental to
Calendaring & Scheduling.  It was so fundamental that the VFREEBUSY
object was established to handle it.  Two key purposes of the VFREEBUSY
object are (1) request busy time information, and (2) reply to a request
with busy time information.
 
As previously noted, the CAP spec (-10) does NOT define how to request
free-busy information.  So why doesn't CAP use the VFREEBUSY object to
make the request?  It seems so obvious.  I do not understand the
resistance toward using this Working Group's own standards to address
this issue.
 
Instead, to bolster a VQUERY method, there has been flurry of new "spec
text" generated and suggestions that appear to compromise CAP's support
for iTIP.  This makes me uneasy (especially with final call
approaching).  Using VQUERY for free-busy requests is divergent from the
Working Group's own standards.
 
Again, I propose that CAP use VFREEBUSY to make a request for free-busy
information.  It could be done using SEARCH:
 
C: BEGIN:VCALENDAR
C: VERSION:2.0
C: PRODID:-//Someone's Prodid
C: CMD;ID=FB001:SEARCH
C: TARGET:usera
C: TARGET:userb
C: BEGIN:VFREEBUSY
C: DTSTART:startrange
C: DTEND:endrange
C: END:VFREEBUSY
C: END:VCALENDAR
 
Or we could give it its own command:
 
C: BEGIN:VCALENDAR
C: VERSION:2.0
C: PRODID:-//Someone's Prodid
C: CMD;ID=FB001:GET-FREEBUSY
C: TARGET:usera
C: TARGET:userb
C: BEGIN:VFREEBUSY
C: DTSTART:startrange
C: DTEND:endrange
C: END:VFREEBUSY
C: END:VCALENDAR
 
In either case, the CS dynamically provides the return information. 
The request is simple.  It is unambiguous to the CS what data needs to
be returned.  Consistency and continuity with the Working Group's
previous standards are upheld.  Consistency between an iTIP vs CAP
free-busy is secured.

--=__PartE0BEF2BE.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>B Kahn Wrote:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; FWIW: CAP appears to be divergent from iTIP in doing <BR>&gt; VFREEBUSY REQUEST/REPLYs given what I’ve read so far <BR>&gt; in these recent threads.</DIV>
<DIV>&nbsp;</DIV>
<DIV>YES!! YES!!&nbsp; Thank-you! Thank-you!&nbsp; That’s&nbsp;one of the points I’ve been making (or trying to).</DIV>
<DIV>&nbsp;</DIV>
<DIV>The ability to deal with free-busy information is fundamental to Calendaring &amp; Scheduling.&nbsp; It was so fundamental that the VFREEBUSY object was established to handle it.&nbsp; Two key purposes of the VFREEBUSY object are (1) <U>request busy time information</U>, and (2) reply to a request with busy time information.</DIV>
<DIV>&nbsp;</DIV>
<DIV>As previously noted, the CAP spec (-10) does NOT define how to request free-busy information.&nbsp; So why doesn’t CAP use the VFREEBUSY object to make the request?&nbsp; It seems so obvious.&nbsp; I do not understand the resistance toward using this Working Group’s own standards to address this issue.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Instead, to bolster a VQUERY method, there has been flurry of new "spec text" generated and suggestions that appear to compromise CAP’s support for iTIP.&nbsp; This makes me uneasy (especially with final call approaching).&nbsp; Using VQUERY for&nbsp;free-busy requests is divergent from the Working Group's own standards.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Again, I propose that CAP use VFREEBUSY to make a request for free-busy information.&nbsp; It could be done using SEARCH:</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Courier>C: BEGIN:VCALENDAR<BR>C: VERSION:2.0<BR>C: PRODID:-//Someone’s Prodid<BR>C: CMD;ID=FB001:SEARCH<BR>C: TARGET:usera<BR>C: TARGET:userb<BR>C: BEGIN:VFREEBUSY<BR>C: DTSTART:startrange<BR>C: DTEND:endrange<BR>C: END:VFREEBUSY<BR>C: END:VCALENDAR</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>Or we could give it its own command:</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Courier>C: BEGIN:VCALENDAR<BR>C: VERSION:2.0<BR>C: PRODID:-//Someone’s Prodid<BR>C: CMD;ID=FB001:GET-FREEBUSY<BR>C: TARGET:usera<BR>C: TARGET:userb<BR>C: BEGIN:VFREEBUSY<BR>C: DTSTART:startrange<BR>C: DTEND:endrange<BR>C: END:VFREEBUSY<BR>C: END:VCALENDAR</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>In either case, the CS dynamically provides the return information.&nbsp; The request is simple.&nbsp; It is unambiguous to the CS what data needs to be returned.&nbsp; Consistency and continuity with the Working Group’s previous standards are upheld.&nbsp; Consistency between an iTIP vs CAP free-busy is secured.</DIV></BODY></HTML>
--=__PartE0BEF2BE.0__=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 24 15:04:54 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22572
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 15:04:53 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OIuFqt064694
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 11:56:15 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OIuFol064693
	for ietf-calendar-bks; Thu, 24 Jul 2003 11:56:15 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OIuCqt064681
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 11:56:13 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: "Craig Johnson" <cjohnson@gw.novell.com>
Cc: Bruce_Kahn@notesdev.ibm.com, ietf-calendar@imc.org,
        owner-ietf-calendar@mail.imc.org
Subject: Re: free-busy QUERY
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFEE2B774F.159E4CC5-ON85256D6D.0067FA18-85256D6D.0068064C@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Thu, 24 Jul 2003 14:56:12 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/24/2003 02:56:15 PM,
	Serialize complete at 07/24/2003 02:56:15 PM
Content-Type: multipart/alternative; boundary="=_alternative 0068064385256D6D_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0068064385256D6D_=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Craig, this sounds well thought out.  Bruce, do you agree?  List, is this=20
the right way to go.  I agree - let's work with our own standards.





"Craig Johnson" <cjohnson@gw.novell.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/24/2003 14:47

=20
        To:     <ietf-calendar@imc.org>, <Bruce=5FKahn@notesdev.ibm.com>
        cc:=20
        Subject:        Re: free-busy QUERY



B Kahn Wrote:
=20
> FWIW: CAP appears to be divergent from iTIP in doing=20
> VFREEBUSY REQUEST/REPLYs given what I've read so far=20
> in these recent threads.
=20
YES!! YES!!  Thank-you! Thank-you!  That's one of the points I've been=20
making (or trying to).
=20
The ability to deal with free-busy information is fundamental to=20
Calendaring & Scheduling.  It was so fundamental that the VFREEBUSY object =

was established to handle it.  Two key purposes of the VFREEBUSY object=20
are (1) request busy time information, and (2) reply to a request with busy=
 time information.
=20
As previously noted, the CAP spec (-10) does NOT define how to request=20
free-busy information.  So why doesn't CAP use the VFREEBUSY object to=20
make the request?  It seems so obvious.  I do not understand the=20
resistance toward using this Working Group's own standards to address this =

issue.
=20
Instead, to bolster a VQUERY method, there has been flurry of new "spec=20
text" generated and suggestions that appear to compromise CAP's support=20
for iTIP.  This makes me uneasy (especially with final call approaching).  =

Using VQUERY for free-busy requests is divergent from the Working Group's=20
own standards.
=20
Again, I propose that CAP use VFREEBUSY to make a request for free-busy=20
information.  It could be done using SEARCH:
=20
C: BEGIN:VCALENDAR
C: VERSION:2.0
C: PRODID:-//Someone's Prodid
C: CMD;ID=3DFB001:SEARCH
C: TARGET:usera
C: TARGET:userb
C: BEGIN:VFREEBUSY
C: DTSTART:startrange
C: DTEND:endrange
C: END:VFREEBUSY
C: END:VCALENDAR
=20
Or we could give it its own command:
=20
C: BEGIN:VCALENDAR
C: VERSION:2.0
C: PRODID:-//Someone's Prodid
C: CMD;ID=3DFB001:GET-FREEBUSY
C: TARGET:usera
C: TARGET:userb
C: BEGIN:VFREEBUSY
C: DTSTART:startrange
C: DTEND:endrange
C: END:VFREEBUSY
C: END:VCALENDAR
=20
In either case, the CS dynamically provides the return information.  The=20
request is simple.  It is unambiguous to the CS what data needs to be=20
returned.  Consistency and continuity with the Working Group's previous=20
standards are upheld.  Consistency between an iTIP vs CAP free-busy is=20
secured.


--=_alternative 0068064385256D6D_=
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">Craig, this sounds well thought out.=
 &nbsp;Bruce, do you agree? &nbsp;List, is this the right way to go. &nbsp;=
I agree - let's work with our own standards.<br>
</font>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<td><font size=3D1 face=3D"sans-serif"><b>&quot;Craig Johnson&quot; &lt;cjo=
hnson@gw.novell.com&gt;</b></font>
<br><font size=3D1 face=3D"sans-serif">Sent by: owner-ietf-calendar@mail.im=
c.org</font>
<p><font size=3D1 face=3D"sans-serif">07/24/2003 14:47</font>
<br>
<td><font size=3D1 face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbs=
p; &nbsp; &nbsp; &nbsp;&lt;ietf-calendar@imc.org&gt;, &lt;Bruce=5FKahn@note=
sdev.ibm.com&gt;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbs=
p; &nbsp; &nbsp; &nbsp;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject:=
 &nbsp; &nbsp; &nbsp; &nbsp;Re: free-busy QUERY</font></table>
<br>
<br>
<br>
<br><font size=3D3>B Kahn Wrote:</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>&gt; FWIW: CAP appears to be divergent from iTIP in doin=
g </font>
<br><font size=3D3>&gt; VFREEBUSY REQUEST/REPLYs given what I've read so fa=
r </font>
<br><font size=3D3>&gt; in these recent threads.</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>YES!! YES!!&nbsp; Thank-you! Thank-you!&nbsp; That's&nbs=
p;one of the points I've been making (or trying to).</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>The ability to deal with free-busy information is fundam=
ental to Calendaring &amp; Scheduling.&nbsp; It was so fundamental that the=
 VFREEBUSY object was established to handle it.&nbsp; Two key purposes of t=
he VFREEBUSY object are (1) <u>request busy time information</u>, and (2) r=
eply to a request with busy time information.</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>As previously noted, the CAP spec (-10) does NOT define =
how to request free-busy information.&nbsp; So why doesn't CAP use the VFRE=
EBUSY object to make the request?&nbsp; It seems so obvious.&nbsp; I do not=
 understand the resistance toward using this Working Group's own standards =
to address this issue.</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>Instead, to bolster a VQUERY method, there has been flur=
ry of new &quot;spec text&quot; generated and suggestions that appear to co=
mpromise CAP's support for iTIP.&nbsp; This makes me uneasy (especially wit=
h final call approaching).&nbsp; Using VQUERY for&nbsp;free-busy requests i=
s divergent from the Working Group's own standards.</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>Again, I propose that CAP use VFREEBUSY to make a reques=
t for free-busy information.&nbsp; It could be done using SEARCH:</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>C: BEGIN:VCALENDAR</font>
<br><font size=3D3>C: VERSION:2.0</font>
<br><font size=3D3>C: PRODID:-//Someone's Prodid</font>
<br><font size=3D3>C: CMD;ID=3DFB001:SEARCH</font>
<br><font size=3D3>C: TARGET:usera</font>
<br><font size=3D3>C: TARGET:userb</font>
<br><font size=3D3>C: BEGIN:VFREEBUSY</font>
<br><font size=3D3>C: DTSTART:startrange</font>
<br><font size=3D3>C: DTEND:endrange</font>
<br><font size=3D3>C: END:VFREEBUSY</font>
<br><font size=3D3>C: END:VCALENDAR</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>Or we could give it its own command:</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>C: BEGIN:VCALENDAR</font>
<br><font size=3D3>C: VERSION:2.0</font>
<br><font size=3D3>C: PRODID:-//Someone's Prodid</font>
<br><font size=3D3>C: CMD;ID=3DFB001:GET-FREEBUSY</font>
<br><font size=3D3>C: TARGET:usera</font>
<br><font size=3D3>C: TARGET:userb</font>
<br><font size=3D3>C: BEGIN:VFREEBUSY</font>
<br><font size=3D3>C: DTSTART:startrange</font>
<br><font size=3D3>C: DTEND:endrange</font>
<br><font size=3D3>C: END:VFREEBUSY</font>
<br><font size=3D3>C: END:VCALENDAR</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D3>In either case, the CS dynamically provides the return i=
nformation.&nbsp; The request is simple.&nbsp; It is unambiguous to the CS =
what data needs to be returned.&nbsp; Consistency and continuity with the W=
orking Group's previous standards are upheld.&nbsp; Consistency between an =
iTIP vs CAP free-busy is secured.</font>
<br>
<br>
--=_alternative 0068064385256D6D_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 24 16:00:15 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27644
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 16:00:14 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OJmvqt070394
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 12:48:57 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6OJmvbA070393
	for ietf-calendar-bks; Thu, 24 Jul 2003 12:48:57 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6OJmuqt070388
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 12:48:56 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6OJmtEB018544
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 12:48:57 -0700
Message-ID: <3F203822.7010506@Royer.com>
Date: Thu, 24 Jul 2003 13:48:50 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: free-busy QUERY
References: <OFEE2B774F.159E4CC5-ON85256D6D.0067FA18-85256D6D.0068064C@egenconsulting.com>
In-Reply-To: <OFEE2B774F.159E4CC5-ON85256D6D.0067FA18-85256D6D.0068064C@egenconsulting.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090505070000060207020308"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms090505070000060207020308
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Except for Graig's proposal is also not iTIP compliant and adds a
new component that is also called VFREEBUSY and does not look
like an iTIP VFREEBUSY.

pregen@egenconsulting.com wrote:
> 
> Craig, this sounds well thought out.  Bruce, do you agree?  List, is 
> this the right way to go.  I agree - let's work with our own standards.
> 
>
-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms090505070000060207020308
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjQxOTQ4NTBaMCMGCSqGSIb3DQEJBDEWBBSW
94VcMmDCcvEtp2MlQVmi2zFQKjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQBVHHh6ShICUTllABQ9MZ+sHdjfeIDyt+SEfQCoDEdJjbnz
6NJD/MOBn9qY6En1vJJUveX+ys1zTQqpl1vpNl+KlBvGf/DEOkhSP4lEGkZiHXNVkAuUCQzM
R86qQrbzeiaYRHuw0ULjcSvQfqsmMSifDH/n3ud0J89cmie1zk7Rp1X6ZQQg9IrKjzfy85M5
2LgO129XGlIMtyAjG3nffWrRBcAKXsf7JadvfPoQaMKyA/BPXfzKKaTUVTIl+Y9iCoTjFrO/
PT5ECSD2xj/YW/Z7nTeN5cv2qnJSj4QwyXaBo7l2t8Z20fQU76I596Q1tUFyttIugpJlU1/c
i2HrDLotAAAAAAAA
--------------ms090505070000060207020308--



From owner-ietf-calendar@mail.imc.org  Thu Jul 24 20:08:37 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06572
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 20:08:36 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6ONsvqt082671
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 16:54:57 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6ONsvUL082670
	for ietf-calendar-bks; Thu, 24 Jul 2003 16:54:57 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6ONsuqt082664
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 16:54:56 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Thu, 24 Jul 2003 17:53:11 -0600
Message-Id: <sf201d07.075@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Thu, 24 Jul 2003 17:55:44 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: free-busy QUERY
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part154B0710.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__Part154B0710.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

D Royer wrote:
 
> Except for Graig's proposal is also not iTIP compliant and adds a
> new component that is also called VFREEBUSY and does not look
> like an iTIP VFREEBUSY.
 
There's no need for iTIP compliance.  We are doing a CAP free-busy
request, not an iTIP-via-CAP free-busy request.  We are not bound by
iTIP 'rules' in forming the CAP VFREEBUSY request.
 
Consistency with iTIP (not compliance) is the objective.  Consistency
occurs when both CAP and iTIP use the VFREEBUSY object to make a
free-busy request.  
 
There is a noteworthy difference...
 
CAP's use of VFREEBUSY has one inherent difference from iTIP: the
ORGANIZER and ATTENDEE properties are not required to be present.  They
are not needed by CAP because they are functionally replaced by the
"Session Identity" and TARGET(s).  (This is not so different than many
other CAP operations.)  Importantly, the vital part of the free-busy
request remains the same: DTSTART & DTEND which describe the period of
interest.  This 'tailored for CAP' use of VFREEBUSY is no different than
the "tailored for iTIP" use of VFREEBUSY.  Of course, the details will
need to be articulated in the spec (and I would be glad to help out
there).
 
 

--=__Part154B0710.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>D Royer wrote:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; Except for Graig's proposal is also not iTIP compliant and adds a<BR>&gt; new component that is also called VFREEBUSY and does not look<BR>&gt; like an iTIP VFREEBUSY.</DIV>
<DIV>&nbsp;</DIV>
<DIV>There's no&nbsp;need for iTIP compliance.&nbsp;&nbsp;We are doing a CAP free-busy request, not an iTIP-via-CAP free-busy request.&nbsp; We are not bound by iTIP 'rules' in forming the CAP VFREEBUSY request.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Consistency with iTIP&nbsp;(not compliance) is the objective.&nbsp; Consistency occurs&nbsp;when&nbsp;both CAP and iTIP use the VFREEBUSY object&nbsp;to make a free-busy request.&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>There is&nbsp;a noteworthy difference...</DIV>
<DIV>&nbsp;</DIV>
<DIV>CAP's use of&nbsp;VFREEBUSY&nbsp;has one&nbsp;inherent&nbsp;difference&nbsp;from iTIP:&nbsp;the ORGANIZER and ATTENDEE properties&nbsp;are not&nbsp;required to be present.&nbsp; They are not needed by CAP because&nbsp;they&nbsp;are functionally replaced by the "Session Identity" and TARGET(s).&nbsp; (This is not so different than many other CAP operations.)&nbsp;&nbsp;Importantly, the&nbsp;vital part of the free-busy request remains&nbsp;the same: DTSTART &amp; DTEND which describe&nbsp;the period of interest.&nbsp; This 'tailored for CAP' use of&nbsp;VFREEBUSY&nbsp;is no different than the "tailored for iTIP" use of VFREEBUSY.&nbsp; Of course,&nbsp;the details will need to be articulated in the spec (and I would be glad to help out there).</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>
--=__Part154B0710.0__=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 24 20:58:54 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07280
	for <calsch-archive@lists.ietf.org>; Thu, 24 Jul 2003 20:58:53 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6P0nLqt084593
	for <ietf-calendar-bks@above.proper.com>; Thu, 24 Jul 2003 17:49:21 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6P0nLal084592
	for ietf-calendar-bks; Thu, 24 Jul 2003 17:49:21 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6P0nJqt084585
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 17:49:20 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6P0nJEB020971
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 24 Jul 2003 17:49:21 -0700
Message-ID: <3F207E8A.8050704@Royer.com>
Date: Thu, 24 Jul 2003 18:49:14 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: undisclosed-recipients:;
Subject: Re: free-busy QUERY
References: <sf201d07.075@gw.provo.novell.com>
In-Reply-To: <sf201d07.075@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060109060402020606020403"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060109060402020606020403
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Craig Johnson wrote:
> D Royer wrote:
>  
>  > Except for Graig's proposal is also not iTIP compliant and adds a
>  > new component that is also called VFREEBUSY and does not look
>  > like an iTIP VFREEBUSY.
>  
> There's no need for iTIP compliance.  We are doing a CAP free-busy 
> request, not an iTIP-via-CAP free-busy request.  We are not bound by 
> iTIP 'rules' in forming the CAP VFREEBUSY request.

Then QUERY should be sufficient :-)

> Consistency with iTIP (not compliance) is the objective.  Consistency 
> occurs when both CAP and iTIP use the VFREEBUSY object to make a 
> free-busy request. 
>  
> There is a noteworthy difference...
>  
> CAP's use of VFREEBUSY has one inherent difference from iTIP: the 
> ORGANIZER and ATTENDEE properties are not required to be present.

For CS that have RECUR-EXPAND=true you are correct.

For CS that have RECUR-EXPAND=false they would need the ORGANIZER.
If a CUA gets an iMIP message in with the ATTENDEE value set to a
mailto URL, then the CUA could have to connect to the correct
CAP URL and deposit the iTIP message into the CS for later processing
by the CALID'd (VFREEBUSY/ATTENDEEs) OWNERs CUA. Then that CUA will
have to know the mailto URL that originated the iMIP request in
order to reply, so it MUST BE in the iTIP object that the OWNERs CUA
fetches (The VFREEBUSY ORGANIZER value). Your method will not work
for those CSs.


 > They
> are not needed by CAP because they are functionally replaced by the 
> "Session Identity" and TARGET(s).  (This is not so different than many 
> other CAP operations.)  Importantly, the vital part of the free-busy 
> request remains the same: DTSTART & DTEND which describe the period of 
> interest.  This 'tailored for CAP' use of VFREEBUSY is no different than 
> the "tailored for iTIP" use of VFREEBUSY.  Of course, the details will 
> need to be articulated in the spec (and I would be glad to help out there).

Only for RECUR-EXPAND=ture CS's which do not use VFREEBUSY (Well they
do use VFREEBUSY - just an in compatible one in your proposal).
For RECUR-EXPAND=false, your proposal breaks them because they MUST
use iTIP.

So again if we are going to go with 2 methods to get VFREEBUSY, lets
use Bruce's that is iTIP compliant.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060109060402020606020403
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjUwMDQ5MTRaMCMGCSqGSIb3DQEJBDEWBBQn
gzUr65qmhYV2NUe8g1WjzUHfWzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQArK0lXMzi1FxAN3IO5GJsGp0WhD0zHxn/UG/7ShEF+x9Zl
XUmSSRH9e0eWAWwPcKgSLmI0DXVC4DsvnlTAOyN18URqWIwBUWvqgDiv0W2x/On6D6i1UDwo
sJC3/8S51TOqeZisYKRReM6blDxTWDeMEu9iSEhU8flQpAhhiWgz/hsbEJcr9KwYQdByug05
u81VRFyMYbwtp46dwULWHc42CPfz+Xw13eA6lPAFGcWJkYxyChe8DCmk3/CEMplLIg19hst2
eENuaksd6ZgaT3yfuvHyDglTmf9npgQs0cM0o1EGWOuJtlTbokbth/IjovyOuikmwp6pgOVV
mCBS544oAAAAAAAA
--------------ms060109060402020606020403--



From owner-ietf-calendar@mail.imc.org  Fri Jul 25 11:42:04 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09587
	for <calsch-archive@lists.ietf.org>; Fri, 25 Jul 2003 11:42:04 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PFUlqt068775
	for <ietf-calendar-bks@above.proper.com>; Fri, 25 Jul 2003 08:30:47 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6PFUlfY068774
	for ietf-calendar-bks; Fri, 25 Jul 2003 08:30:47 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ace.notesdev.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PFUjqt068769
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 08:30:46 -0700 (PDT)
	(envelope-from Bruce_Kahn@notesdev.ibm.com)
In-Reply-To: <sf1fd4b3.031@gw.provo.novell.com>
To: "Craig Johnson" <cjohnson@gw.novell.com>
Cc: ietf-calendar@imc.org
Subject: Re: free-busy QUERY
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_07142003NP July 14, 2003
Message-ID: <OF8D7782D5.B0050438-ON85256D6E.00505ABE-85256D6E.0054DE79@notesdev.ibm.com>
From: Bruce_Kahn@notesdev.ibm.com
Date: Fri, 25 Jul 2003 11:30:42 -0400
X-MIMETrack: Serialize by Router on Ace/Iris(Release 6.0.2CF2|July 23, 2003) at 07/25/2003
 11:22:56 AM,
	Serialize complete at 07/25/2003 11:22:56 AM
Content-Type: multipart/alternative; boundary="=_alternative 0054DE7485256D6E_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0054DE7485256D6E_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Craig responed on 07/24/2003 02:47:10 PM:
> The ability to deal with free-busy information is fundamental to=20
> Calendaring & Scheduling.=20

Hear, hear!  Thats why it MUST be part of CAP 1.0 IMNHO.

> As previously noted, the CAP spec (-10) does NOT define how to=20
> request free-busy information.  So why doesn?t CAP use the VFREEBUSY
> object to make the request?  It seems so obvious.  I do not=20
> understand the resistance toward using this Working Group?s own=20
> standards to address this issue.

Not sure its the entire WG resisting anything.  The lurker-to-participant=20
ratio is quite high here (300+ lurkers to ~10 participants last I=20
checked).

In any case, since CAP is using iTIP messages in the payloads it should be =

using the VFREEBUSY the same way it does other components.

> Again, I propose that CAP use VFREEBUSY to make a request for free-
> busy information.  It could be done using SEARCH:
>=20
> C: BEGIN:VCALENDAR
> C: VERSION:2.0
> C: PRODID:-//Someone?s Prodid
> C: CMD;ID=3DFB001:SEARCH
> C: TARGET:usera
> C: TARGET:userb
> C: BEGIN:VFREEBUSY
> C: DTSTART:startrange
> C: DTEND:endrange
> C: END:VFREEBUSY
> C: END:VCALENDAR

In order to by a valid iTIP payload it would look more like:

C: BEGIN:VCALENDAR
C: VERSION:2.0
C: PRODID:-//Someone?s Prodid
C: CMD;ID=3DFB001:SEARCH
C: TARGET:UserA
C: TARGET:UserB
C: BEGIN:VFREEBUSY
C: ORGANIZER:UserA
C: ATTENDEE:UserA
C: ATTENDEE:UserB
C: DTSTAMP:19970613T190000Z
C: DTSTART:19970701T080000Z
C: DTEND:19970701T200000
C: UID:calsrv.example.com-873970198738777@example.com
C: END:VFREEBUSY
C: END:VCALENDAR

but the information in the TARGETs duplicates the info in the ATTENDEEs so =

it could be simplified by removing the TARGETs w/o violating CAP.  Also, a =

UID was added for a particular purpose, to match up REPLYs to REQUESTs.=20
This is effectively duplicated in the ID property parameter on the CMD so=20
it could also be simplified and removed from the CMD property.

While its reasonable to expect that the ORGANIZER value would match the=20
requestors identity (since iTIP says "MUST be the request originator's=20
address" which in CAP maps to their identity) it is possible that someone=20
could use a different value.  This should be treated as a failure and the=20
request rejected entirely.

Removing the duplicate properties by removing them from the iTIP payload=20
is contrary to the intent of keeping the payload iTIP compliant.  Plus=20
since CAP says that it makes no changes to iTIP relevant to scheduling=20
workflow and busytime lookups would qualify as scheduling workflow then=20
removing the ATTENDEE and UID properties from the iTIP payload would be=20
contrary to the stated goal.

The ABNF for the SEARCH command should also reflect that VFREEBUSY and=20
VQUERY components are mutually exclusive and not permitted w/in the same=20
SEARCH command.

> Or we could give it its own command:
>=20
> C: BEGIN:VCALENDAR
> C: VERSION:2.0
> C: PRODID:-//Someone?s Prodid
> C: CMD;ID=3DFB001:GET-FREEBUSY
> C: TARGET:usera
> C: TARGET:userb
> C: BEGIN:VFREEBUSY
> C: DTSTART:startrange
> C: DTEND:endrange
> C: END:VFREEBUSY
> C: END:VCALENDAR

Another possibility but it has a non-iTIP payload so it is just as=20
divergent as using SEARCH with a VQUERY so its not fixing the problem.  If =

the payload were the iTIP VFREEBUSY REQUEST (as described above) then=20
thats another choice.

If being able to search the users queue for iMIP VFREEBUSY REQUESTs is=20
something we need to have in CAP (I suspect it may be if the CUA has to=20
perform iMIP fallback but wants the results returned to the users queue=20
for it to find later) then perhaps a compromise is possible:

1: SEARCH on VFREEBUSY does NOT perform a busytime search for the TARGETs. =

 It would be the mechanism the CUA uses to search for iTIP VFREEBUSY=20
messages in the TARGET queues.  As such the command would have an implcit=20
STATE() =3D 'BOOKED' whenever the component in question were a VFREEBUSY.

2: GET-FREEBUSY DOES perform a busytime search for the ATTENDEEs (no need=20
for TARGETs for this command).  It would be the mechanism the CUA uses to=20
search for users free/busy time when trying to schedule meetings.  As such =

the command request and response payloads are fully iTIP compliant.

Thus we have iTIP compliance when doing scheduling workflow, we keep using =

iTIP payloads correctly and we have a clear and unambiguious means for=20
doing the desired actions.

> In either case, the CS dynamically provides the return information.=20

Oh yeah!...

Bruce
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Bruce Kahn                                INet:=20
Bruce=5FKahn@notesdev.ibm.com
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Warning: Dates in Calendar are closer than they appear.
--=_alternative 0054DE7485256D6E_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2><tt>Craig responed on 07/24/2003 02:47:10 PM:<br>
&gt; The ability to deal with free-busy information is fundamental to <br>
&gt; Calendaring &amp; Scheduling. &nbsp;</tt></font>
<br>
<br><font size=3D2 face=3D"sans-serif">Hear, hear! &nbsp;Thats why it MUST
be part of CAP 1.0 IMNHO.</font>
<br>
<br><font size=3D2><tt>&gt; As previously noted, the CAP spec (-10) does
NOT define how to <br>
&gt; request free-busy information. &nbsp;So why doesn&#8217;t CAP use the =
VFREEBUSY<br>
&gt; object to make the request? &nbsp;It seems so obvious. &nbsp;I do
not <br>
&gt; understand the resistance toward using this Working Group&#8217;s own =
<br>
&gt; standards to address this issue.</tt></font>
<br>
<br><font size=3D2 face=3D"sans-serif">Not sure its the entire WG resisting
anything. &nbsp;The lurker-to-participant ratio is quite high here (300+
lurkers to ~10 participants last I checked).</font>
<br>
<br><font size=3D2 face=3D"sans-serif">In any case, since CAP is using iTIP
messages in the payloads it should be using the VFREEBUSY the same way
it does other components.</font>
<br>
<br><font size=3D2><tt>&gt; Again, I propose that CAP use VFREEBUSY to make
a request for free-<br>
&gt; busy information. &nbsp;It could be done using SEARCH:</tt></font>
<br><font size=3D2><tt>&gt; &nbsp;</tt></font>
<br><font size=3D2><tt>&gt; C: BEGIN:VCALENDAR<br>
&gt; C: VERSION:2.0<br>
&gt; C: PRODID:-//Someone&#8217;s Prodid<br>
&gt; C: CMD;ID=3DFB001:SEARCH<br>
&gt; C: TARGET:usera<br>
&gt; C: TARGET:userb<br>
&gt; C: BEGIN:VFREEBUSY<br>
&gt; C: DTSTART:startrange<br>
&gt; C: DTEND:endrange<br>
&gt; C: END:VFREEBUSY<br>
&gt; C: END:VCALENDAR</tt></font>
<br>
<br><font size=3D2 face=3D"sans-serif">In order to by a valid iTIP payload
it would look more like:</font>
<br>
<br><font size=3D2><tt>C: BEGIN:VCALENDAR<br>
C: VERSION:2.0<br>
C: PRODID:-//Someone&#8217;s Prodid<br>
C: CMD;ID=3DFB001:SEARCH<br>
C: TARGET:UserA<br>
C: TARGET:UserB<br>
C: BEGIN:VFREEBUSY<br>
C: ORGANIZER:</tt></font><font size=3D2 color=3D#333333><tt>UserA</tt></fon=
t><font size=3D2><tt><br>
C: ATTENDEE:</tt></font><font size=3D2 color=3D#333333><tt>UserA</tt></font=
><font size=3D2><tt><br>
C: ATTENDEE:</tt></font><font size=3D2 color=3D#333333><tt>UserB</tt></font=
><font size=3D2><tt><br>
C: DTSTAMP:19970613T190000Z<br>
C: DTSTART:19970701T080000Z<br>
C: DTEND:19970701T200000<br>
C: UID:calsrv.example.com-873970198738777@example.com<br>
C: END:VFREEBUSY</tt></font>
<br><font size=3D2><tt>C: END:VCALENDAR</tt></font>
<br>
<br><font size=3D2 face=3D"sans-serif">but the information in the TARGETs d=
uplicates
the info in the ATTENDEEs so it could be simplified by removing the TARGETs
w/o violating CAP. &nbsp;Also, a UID was added for a particular purpose,
to match up REPLYs to REQUESTs. &nbsp;This is effectively duplicated in
the ID property parameter on the CMD so it could also be simplified and
removed from the CMD property.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">While its reasonable to expect that
the ORGANIZER value would match the requestors identity (since iTIP says
&quot;MUST be the request originator's address&quot; which in CAP maps
to their identity) it is possible that someone could use a different value.
&nbsp;This should be treated as a failure and the request rejected entirely=
.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Removing the duplicate properties by
removing them from the iTIP payload is contrary to the intent of keeping
the payload iTIP compliant. &nbsp;Plus since CAP says that it makes no
changes to iTIP relevant to scheduling workflow and busytime lookups would
qualify as scheduling workflow then removing the ATTENDEE and UID properties
from the iTIP payload would be contrary to the stated goal.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">The ABNF for the SEARCH command shou=
ld
also reflect that VFREEBUSY and VQUERY components are mutually exclusive
and not permitted w/in the same SEARCH command.</font>
<br>
<br><font size=3D2><tt>&gt; Or we could give it its own command:</tt></font>
<br><font size=3D2><tt>&gt; &nbsp;</tt></font>
<br><font size=3D2><tt>&gt; C: BEGIN:VCALENDAR<br>
&gt; C: VERSION:2.0<br>
&gt; C: PRODID:-//Someone&#8217;s Prodid<br>
&gt; C: CMD;ID=3DFB001:GET-FREEBUSY<br>
&gt; C: TARGET:usera<br>
&gt; C: TARGET:userb<br>
&gt; C: BEGIN:VFREEBUSY<br>
&gt; C: DTSTART:startrange<br>
&gt; C: DTEND:endrange<br>
&gt; C: END:VFREEBUSY<br>
&gt; C: END:VCALENDAR</tt></font>
<br>
<br><font size=3D2 face=3D"sans-serif">Another possibility but it has a non=
-iTIP
payload so it is just as divergent as using SEARCH with a VQUERY so its
not fixing the problem. &nbsp;If the payload were the iTIP VFREEBUSY REQUEST
(as described above) then thats another choice.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">If being able to search the users qu=
eue
for iMIP VFREEBUSY REQUESTs is something we need to have in CAP (I suspect
it may be if the CUA has to perform iMIP fallback but wants the results
returned to the users queue for it to find later) then perhaps a compromise
is possible:</font>
<br>
<br><font size=3D2 face=3D"sans-serif">1: SEARCH on VFREEBUSY does NOT perf=
orm
a busytime search for the TARGETs. &nbsp;It would be the mechanism the
CUA uses to search for iTIP VFREEBUSY messages in the TARGET queues. &nbsp;=
As
such the command would have an implcit STATE() =3D 'BOOKED' whenever the
component in question were a VFREEBUSY.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">2: GET-FREEBUSY DOES perform a busyt=
ime
search for the ATTENDEEs (no need for TARGETs for this command). &nbsp;It
would be the mechanism the CUA uses to search for users free/busy time
when trying to schedule meetings. &nbsp;As such the command request and
response payloads are fully iTIP compliant.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Thus we have iTIP compliance when do=
ing
scheduling workflow, we keep using iTIP payloads correctly and we have
a clear and unambiguious means for doing the desired actions.</font>
<br>
<br><font size=3D2><tt>&gt; In either case, the CS dynamically provides the
return information. <br>
</tt></font>
<br><font size=3D2 face=3D"sans-serif">Oh yeah!...</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Bruce</font>
<br><font size=3D2 face=3D"sans-serif">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Bruce Kahn &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;INet: Bruce=5FKahn@notesdev=
.ibm.com<br>
Messaging &amp; Collaboration &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; Phone: 978.399.6496<br>
IBM Software Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; FAX: and nothing but the FAX...<br>
Warning: Dates in Calendar are closer than they appear.</font>
--=_alternative 0054DE7485256D6E_=--


From owner-ietf-calendar@mail.imc.org  Fri Jul 25 13:33:13 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13439
	for <calsch-archive@lists.ietf.org>; Fri, 25 Jul 2003 13:33:12 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PHNSqt072893
	for <ietf-calendar-bks@above.proper.com>; Fri, 25 Jul 2003 10:23:28 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6PHNS2A072892
	for ietf-calendar-bks; Fri, 25 Jul 2003 10:23:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PHNQqt072887
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 10:23:26 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6PHNOEB028156
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 10:23:26 -0700
Message-ID: <3F216786.7010702@Royer.com>
Date: Fri, 25 Jul 2003 11:23:18 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: free-busy QUERY
References: <OF8D7782D5.B0050438-ON85256D6E.00505ABE-85256D6E.0054DE79@notesdev.ibm.com>
In-Reply-To: <OF8D7782D5.B0050438-ON85256D6E.00505ABE-85256D6E.0054DE79@notesdev.ibm.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms040802030004060008020905"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms040802030004060008020905
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bruce_Kahn@notesdev.ibm.com wrote:

> 
> but the information in the TARGETs duplicates the info in the ATTENDEEs 
> so it could be simplified by removing the TARGETs w/o violating CAP. 
>  Also, a UID was added for a particular purpose, to match up REPLYs to 
> REQUESTs.  This is effectively duplicated in the ID property parameter 
> on the CMD so it could also be simplified and removed from the CMD 
> property.
 >
> While its reasonable to expect that the ORGANIZER value would match the 
> requestors identity (since iTIP says "MUST be the request originator's 
> address" which in CAP maps to their identity) it is possible that 
> someone could use a different value.  This should be treated as a 
> failure and the request rejected entirely.

And they will not match when the ORGANIZERs CUA was reached via an iMIP
message and the CUA uses CAP to get the data and iMIP to REPLY back
to the requester. I agree all data must be preserved for the flow to work.

The ATTENDEEs can not be removed from the VFREEBUSY REQUESTs for the
same reason, they may be iMIP addresses and not CAP addresses, so
the CUA will have to know who to forward them back to for
RECUR-EXPAND=false CUAs when the CUA is manually processing
the VFREEBUSY requests/replies.

> Removing the duplicate properties by removing them from the iTIP payload 
> is contrary to the intent of keeping the payload iTIP compliant.  Plus 
> since CAP says that it makes no changes to iTIP relevant to scheduling 
> workflow and busytime lookups would qualify as scheduling workflow then 
> removing the ATTENDEE and UID properties from the iTIP payload would be 
> contrary to the stated goal.

In which case you could CMD:CREATE/METHOD:REQUEST a VFREEBUSY and
get back as the reply a CMD:REPLY/METHOD:REPLY VFREEBUSY - correct?
The advantage being that it is only one round trip to get the
results.

> The ABNF for the SEARCH command should also reflect that VFREEBUSY and 
> VQUERY components are mutually exclusive and not permitted w/in the same 
> SEARCH command.

I still do not see any reason to change the SEARCH command just for VFREEBUSY.
The existing syntax works. And I am not sure why searching for a component
will be broken and mutually exclusive. They don't seem mutually exclusive
to me and I have not seen posts explaining why.

> Another possibility but it has a non-iTIP payload so it is just as 
> divergent as using SEARCH with a VQUERY so its not fixing the problem. 
>  If the payload were the iTIP VFREEBUSY REQUEST (as described above) 
> then thats another choice.

I do not follow the above. Not sure which way you are
saying does not work.

> If being able to search the users queue for iMIP VFREEBUSY REQUESTs is 
> something we need to have in CAP (I suspect it may be if the CUA has to 
> perform iMIP fallback but wants the results returned to the users queue 
> for it to find later) then perhaps a compromise is possible:
> 
> 1: SEARCH on VFREEBUSY does NOT perform a busytime search for the 
> TARGETs.  It would be the mechanism the CUA uses to search for iTIP 
> VFREEBUSY messages in the TARGET queues.  As such the command would have 
> an implcit STATE() = 'BOOKED' whenever the component in question were a 
> VFREEBUSY.

In which case iTIP REQUESTS will always be ignored? What is the gain?
If you wanted to say that BOOKED == do the processing and UNPROCESSED
is get the raw components then yes I see your point. But declaring that
all searches for VFREEBUSY are not the 'UNPROCESSED' violates the
generic SEARCH rules. Why make VFREEBUSY an exception?

> 2: GET-FREEBUSY DOES perform a busytime search for the ATTENDEEs (no 
> need for TARGETs for this command).  It would be the mechanism the CUA 
> uses to search for users free/busy time when trying to schedule 
> meetings.  As such the command request and response payloads are fully 
> iTIP compliant.

Why not just process VFREEBUSY REQUEST component the same as every other
component? We already have a way to deposit (CREATE) iTIP REQUEST components
and  fetch iTIP REPLY components (QUERY). So far there have been zero new
features added - absolutely NONE.

The above is true for every iTIP component, not just VFREEBUSY. When
SEARCHING for VEVENT == BOOKED, you do not get the same results as
searching for the VEVENT != BOOKED components, you get the dynamic
live VEVENTs when searching for VEVENT == BOOKED. There is NO difference
here between VFREEBUSY and any other iTIP component.

We are just adding a clarification that VFREEBUSY == BOOKED means the
same as every other iTIP component - calculate the results and send
them back.

There is no new problem being solved. Just a clarification.

That in it self does not justify adding a new method/syntax to query just
for VFREEBUSY when the existing methods work for all iTIP components. And
if we specify that BOOKED means go calculate the results for VFREEBUSY
and UNPROCESSED means go get the raw iTIP messages then it is 100% compatible 
with existing CAP commands, methods, and usage.

Now if we want to optimize the path so that we do not have to have
two full round trips to get the data, then that is a new useful
feature.

If we take Bruce's original proposal that a reply to a unmodified
CMD:CREATE/METHOD:REQUEST VFREEBUSY returns a BOOKED and dynamically
CMD:REPLY/METHOD:REPLY VFREEBUSY, then that works for CS that
have RECUR-EXPAND=true. Then we have added a new useful feature.

I would like that to not be the action when the CS has RECUR-EXPAND=false
as those  CS's can NOT dynamically create VFREEBUSY data as a CS
can allow recurrence rules to be stored and not know how to expand
them.

> Thus we have iTIP compliance when doing scheduling workflow, we keep 
> using iTIP payloads correctly and we have a clear and unambiguious means 
> for doing

Again I was not clear which method you were proposing. So are you saying
that we treat iTIP VFREEBUSY components exactly like every other iTIP
component? That is in all cases a SEARCH where BOOKED are dynamic real
time results? And that != BOOKED is for the raw iTIP packets? If so
yes we agree as that is 100% just like every other component.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms040802030004060008020905
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjUxNzIzMTlaMCMGCSqGSIb3DQEJBDEWBBTy
tT1T2LBIMHbQLVWMsXWxiQHTdjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQCn+IeRqfhynYgzPKXizivQL7IqTk3IhpVHMwvyIJFF0JSv
ULiPGoGXn3wWFutBUtQ57kc5Itp3nB6iXisMA7udIEaVGGdst6/eGvntbaHQqsWEXEqmsBH0
MYVwXcX+ZjmZ4SQ6ls740KyioQD5HryGZrEX8mn1sH3sIMZTEh5XdaRfUb6M0CjatfWSEhlV
LdhjwMxiiH3YOjgguR9vR93cNvTTs+sNfosVZRck3oWjOSKoEwQFB9GeQnYameHBfw+DhRD8
0d2V34X84V3pKti42qO6LCi7uEx8lxvkQRJ8wQNhVYsW1HDR2kh7nRgumCNl6ik0MHTV9pl0
Yczt5fFRAAAAAAAA
--------------ms040802030004060008020905--



From owner-ietf-calendar@mail.imc.org  Fri Jul 25 15:24:10 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17128
	for <calsch-archive@lists.ietf.org>; Fri, 25 Jul 2003 15:24:10 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PJ7qqt078493
	for <ietf-calendar-bks@above.proper.com>; Fri, 25 Jul 2003 12:07:52 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6PJ7qPu078492
	for ietf-calendar-bks; Fri, 25 Jul 2003 12:07:52 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from gw.provo.novell.com (gw.provo.novell.com [137.65.47.29])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PJ7pqt078486
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 12:07:51 -0700 (PDT)
	(envelope-from cjohnson@gw.novell.com)
Received: from PROVO3-MTA by gw.provo.novell.com
	with Novell_GroupWise; Fri, 25 Jul 2003 13:05:51 -0600
Message-Id: <sf212b2f.095@gw.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Fri, 25 Jul 2003 13:08:30 -0600
From: "Craig Johnson" <cjohnson@gw.novell.com>
To: <ietf-calendar@imc.org>
Subject: Re: free-busy QUERY
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartC896DB3E.0__="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--=__PartC896DB3E.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

If there are sound reasons for a "CAP VFREEBUSY request object" to
conform more closely to an "iTIP VFREEBUSY request object" I have no
objections.  In fact, there are advantages to doing so (next paragraph).
 However, it would be nice to apply reason where appropriate.  Some
properties required/needed by iTIP have no relevance or are redundant
with CAP.
 
It makes a whole lot of sense for CUA to be able to create a "VFREEBUSY
request object" not knowing (or caring) beforehand if the request is
destined for a CAP or iMIP/iTIP recipient.  The "VFREEBUSY request
object" can then be bundled up and handled/delivered in the manner
appropriate for each recipient.  THE CRUCIAL AND IMPORTANT POINT IS: 
the same "VFREEBUSY request object" is used regardless of whether we are
dealing with CAP, iTIP/iMIP or anything that comes up in the future! 
This creates consistency and continuity among the WG standards for
dealing with free-busy requests and responses.  It makes it easier for
CUAs because there is one way to formulate the request that works for
all types of recipients.

--=__PartC896DB3E.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Description: HTML
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>If there are sound reasons for a "CAP VFREEBUSY request object" to conform more closely to an "iTIP VFREEBUSY request object" I have no objections.&nbsp; In fact, there are advantages to doing so (next paragraph).&nbsp; However, it would be nice to apply&nbsp;reason where appropriate.&nbsp; Some properties required/needed by iTIP have no relevance or are redundant with CAP.</DIV>
<DIV>&nbsp;</DIV>
<DIV>It makes a whole lot of sense for CUA to be able to create a "VFREEBUSY request object" not knowing (or caring) beforehand if the request is destined for a CAP or iMIP/iTIP recipient.&nbsp; The "VFREEBUSY request object" can then be bundled up and handled/delivered in the manner appropriate for each recipient.&nbsp; THE CRUCIAL AND IMPORTANT POINT IS:&nbsp; the same "VFREEBUSY request object" is used regardless of whether we are dealing with CAP, iTIP/iMIP or anything that comes up in the future!&nbsp; This creates <U>consistency and continuity</U> among the WG standards for dealing with free-busy requests and responses.&nbsp; It makes it easier for CUAs because there is one way to formulate the request that works for all types of recipients.</DIV></BODY></HTML>
--=__PartC896DB3E.0__=--


From owner-ietf-calendar@mail.imc.org  Fri Jul 25 16:18:46 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21432
	for <calsch-archive@lists.ietf.org>; Fri, 25 Jul 2003 16:18:45 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PK9Xqt084998
	for <ietf-calendar-bks@above.proper.com>; Fri, 25 Jul 2003 13:09:33 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6PK9XQs084997
	for ietf-calendar-bks; Fri, 25 Jul 2003 13:09:33 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PK9Wqt084990
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 13:09:32 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6PK9VEB029381
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 13:09:32 -0700
Message-ID: <3F218E75.9020204@Royer.com>
Date: Fri, 25 Jul 2003 14:09:25 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: free-busy QUERY
References: <sf212b2f.095@gw.provo.novell.com>
In-Reply-To: <sf212b2f.095@gw.provo.novell.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020504020901050903040405"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms020504020901050903040405
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Craig Johnson wrote:
> If there are sound reasons for a "CAP VFREEBUSY request object" to 
> conform more closely to an "iTIP VFREEBUSY request object" I have no 
> objections.  In fact, there are advantages to doing so (next 
> paragraph).  However, it would be nice to apply reason where 
> appropriate.  Some properties required/needed by iTIP have no relevance 
> or are redundant with CAP.

I think the email send so far justifies they all be present as their
are edge cases that need that data (Mixed iMIP/CAP and RECUR-EXPAND=false).

In addition to the points already made, a CUA that deposits the
information may not be the same as the CUA that requests the dynamic
VFREEBUSY information. This can happen when there is a CUA-BOT that
grabs incoming iMIP information from your POP or IMAP servers or filters
the incoming email for your CUA. Such a CUA would never want the
dynamic information and the GUI that the user used would have to
know all of the iMIP information from the original request, thus
it must be saved a sent.

> It makes a whole lot of sense for CUA to be able to create a "VFREEBUSY 
> request object" not knowing (or caring) beforehand if the request is 
> destined for a CAP or iMIP/iTIP recipient.

I think we are all 100% in agreement on that point.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms020504020901050903040405
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjUyMDA5MjVaMCMGCSqGSIb3DQEJBDEWBBTG
1YIVL7kheoIglQhtZ5zgppTgBjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQAF4O5Oui/0RqZJ6D5E2SiqtXqJZ8OFL7XVaHY70f6D+V1k
cQDVbpTU7V9pXGYg9KQ56eT5t35r14mAOW3DfsA96NQK4CnKglBtU3ZXmpwUWXueoDKdLQGR
Yh/AKtwbbXcw904lbqVS//mfRU0eS621Nkpa1SBjIBmZ78ykWF+xO8Tq3HmfQgDzK0ymBi30
BZOB/h9GKEaJ7HaY2rQ9467r5NV1tWuA2HcHp+bnGATWASyhd5X9O3DBTClsIm8LzHPCDzkc
C+x4BahcgwVDnKeYjuCaM0p7biXb6rZYXNP7qN9bfYG4kUm831pVW+UQtYmHM3XRwlV7bk2b
NYttOSReAAAAAAAA
--------------ms020504020901050903040405--



From owner-ietf-calendar@mail.imc.org  Fri Jul 25 16:42:29 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23757
	for <calsch-archive@lists.ietf.org>; Fri, 25 Jul 2003 16:42:29 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PKVdqt085875
	for <ietf-calendar-bks@above.proper.com>; Fri, 25 Jul 2003 13:31:39 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6PKVdaX085874
	for ietf-calendar-bks; Fri, 25 Jul 2003 13:31:39 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6PKVcqt085869
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 13:31:38 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6PKVbEB029599
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Fri, 25 Jul 2003 13:31:39 -0700
Message-ID: <3F2193A4.6030908@Royer.com>
Date: Fri, 25 Jul 2003 14:31:32 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: free-busy QUERY - summary (I think)
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060800070501040800050104"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060800070501040800050104
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Thanks Craig for forcing us to rethink and rehash this point.

I think the following could be accepted by all:

    In order to be 100% compatible with all existing iTIP objects
    in CAP.

    The CUA MUST send all VFREEBUSY objects "as is" to the CS.

    Use existing CMD:CREATE to store VFREEBUSY objects.

    Use SEARCH STATE() = 'BOOKED' to get the dynamic results.

    Use SEARCH STATE() = 'UNPROCESSED' to get the raw iTIP objects.
    Or do a METHOD:REQUEST requesting the METHOD:REPLY as the reply
    (see below for more on this)

I think the following is still unspecified so I propose
the following VFREEBUSY changes to CAP:

   For a CS that has EXPAND-RECUR=true:

      - Only REQUEST and REPLY have any meaning. PUBLISH
        is useless.

      - What happens when such a CS gets a VFREEBUSY PUBLISH?
        Does the CS say thanks, success, then throw it away?
        Or is it an error?

        I would say success then throw it away.

      - Does the CS reply to a CMD:CREATE/METHOD:REQUST
        with a CMD:REPLY/METHOD:REPLY as the VREPLY saving
        the extra round trip?

          If yes, I think we need to be able to turn that
          off for CUA-BOTs that deposit only.

          So how about we use the EXPAND parameter in the
          CMD property, if 'true', return the METHOD:REPLY
          VFREEBUSY in the VREPLY. And if 'false', do not,
          just a VREPLY with no VFREEBUSY.

        I like the idea of allowing the REPLY to come back
        in the VREPLY. And I think we need the EXPAND=true/false
        to turn it on/off.

   For a CS that has EXPAND-RECUR=false.

      - Automatic creation of VFREEBUSY status is not possible.

      - So a CUA MUST send a PUBLISH to such a CS. If none has
        been saved, only an empty VFREEBUSY can ever be returned.

      - Mandate that such a CS calculates the BOOKED VFREEBUSY
        from the PUBLISHed components that are saved.

      - Also allow the EXPAND=true/false when creating a REQUEST.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060800070501040800050104
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSDCC
A2YwggLPoAMCAQICEA2LT+6q0hhb9HVqnSnhf/swDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbQwgbEwEQYJYIZIAYb4QgEBBAQDAgEGMDUGA1UdHwQuMCwwKqAooCaGJGh0dHA6Ly9j
cmwudmVyaXNpZ24uY29tL3BjYTEuMS4xLmNybDBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEB
MC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0T
BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQECBQADgYEAQnwO34x5TKy/COxN
VS9QiaDFXk4uXpUym3mtZRELHEpSxNWoMSGO3hCbbAjFB+YDuefINHgJCfK8BkL4WoyD0Yre
qiL12eMh0s9ljAYzsM0gsjPNCr0+4Z3BNalksKelJFvp8WjrE8R8N/SUZA2axb0zF++DM6A+
5ao+rthzH60wggTrMIIEVKADAgECAhAejFNQR/pY9ailMryViTyhMA0GCSqGSIb3DQEBBAUA
MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD
QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDkx
ODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf
MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWdu
LmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwG
A1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNz
IDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkq
hkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv43FbjoxKdvfMSpimkqD5mOFrqU34
1TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2YlebpkqpRiBMF+rtoNpX4SSBtZwGA
gCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jPD7x876t4BohIOJI1figvqXmSwfWK
YrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn0W6r37zHFCnc0bm9xfxjbw4LunXd
SaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgKbpWFSSSpJGUWmQIDAQABo4IBBjCC
AQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEF
BQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZl
cmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNl
IGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2NsYXNzMS5jcmwwDQYJKoZIhvcN
AQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdkOPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq
1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiWyFDnFIqKJoHmHPNXBn0dXYlje5p2
TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIwggTrMIIEVKADAgECAhAejFNQR/pY9ail
MryViTyhMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv
bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE
AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkMB4XDTAyMDkxODAwMDAwMFoXDTAzMDkxODIzNTk1OVowggELMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFG
MEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJl
Zi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYD
VQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNV
BAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdAcm95ZXIuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwxBHUCJd14lkzkJJKSLcpUSNqym8VYNSM5HEKWdv
43FbjoxKdvfMSpimkqD5mOFrqU341TL6G3I/KkvQ9TzGWprYryi/qJveMah6Pz7HPQOe4m2Y
lebpkqpRiBMF+rtoNpX4SSBtZwGAgCLaQSV7jA6QyAiEv5/QPYY5KcA9N3I4PemEoC5kS1jP
D7x876t4BohIOJI1figvqXmSwfWKYrhBcd/tXNk68VpOqUOZSuSrn+RHHKEuIS2eOj285IAn
0W6r37zHFCnc0bm9xfxjbw4LunXdSaudrVa5UdYSxkTgxF4WgXwh3JfZM8ioRCVESN3DpsgK
bpWFSSSpJGUWmQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtg
hkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ
UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT
IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZI
AYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAoIZ4BrBjrJxUvZW7bAmWyHrGWv+oBfdk
OPGBvbbcEmJ1bBz0tT3Iy8Ri+YEq1sTdRlTWp1XTKo8/hfCudzbRqUN2CNcojkBAy0zH3hiW
yFDnFIqKJoHmHPNXBn0dXYlje5p2TRbl2WbW/hvpM1DstHIhyOB5WadIC14xmrS66eIxggSq
MIIEpgIBATCB4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9y
eS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWdu
IENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRl
ZAIQHoxTUEf6WPWopTK8lYk8oTAJBgUrDgMCGgUAoIICnTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA3MjUyMDMxMzJaMCMGCSqGSIb3DQEJBDEWBBQS
vdBYRtSW28cYKy7FMrDNmI4u7zBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB8gYJ
KwYBBAGCNxAEMYHkMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVy
aVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs
aWRhdGVkAhAejFNQR/pY9ailMryViTyhMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQHoxTUEf6WPWopTK8lYk8
oTANBgkqhkiG9w0BAQEFAASCAQBl2W27gvnl8Xgwaz8/6bH5Bo5PrEiFbizKUBJv8O6Ijo76
TLLOx3qC97E7pN25yVuI4btXCJDbS2BhrRDDeFzqQALGuN9OzLZFFeCSqXKA/CWAKMQaSZ1w
9Neidp4YWN+89j3B1ysTJ/cwM7SPwYQpOqHRy+oziNm+vhUH6ECmQjke8XFdqMPoeNEADst0
GY54O3WCVw07F2Ff31qMegLkGzuYKFh8m7aQs04d+x4qnOwQPaD0s0JbRgd2mEkrFrep6N78
Rdg5+wUdghN8emzkEN1JMRIng4hP6NycIq89EdJY9iIC1CEGqUQr6J+rARqabmtIRl+fd5jO
6z6BxnW8AAAAAAAA
--------------ms060800070501040800050104--



From owner-ietf-calendar@mail.imc.org  Mon Jul 28 11:19:15 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06120
	for <calsch-archive@lists.ietf.org>; Mon, 28 Jul 2003 11:19:14 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6SF5Pqt066196
	for <ietf-calendar-bks@above.proper.com>; Mon, 28 Jul 2003 08:05:25 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6SF5PUC066194
	for ietf-calendar-bks; Mon, 28 Jul 2003 08:05:25 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6SF5Oqt066187
	for <ietf-calendar@imc.org>; Mon, 28 Jul 2003 08:05:24 -0700 (PDT)
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04201;
	Mon, 28 Jul 2003 11:05:20 -0400 (EDT)
Message-Id: <200307281505.LAA04201@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-11.txt
Date: Mon, 28 Jul 2003 11:05:20 -0400
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=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 et al.
	Filename	: draft-ietf-calsch-cap-11.txt
	Pages		: 141
	Date		: 2003-7-28
	
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-11.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-11.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-11.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:	<2003-7-28111035.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsch-cap-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-calsch-cap-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-7-28111035.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-calendar@mail.imc.org  Mon Jul 28 21:09:35 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26264
	for <calsch-archive@lists.ietf.org>; Mon, 28 Jul 2003 21:09:35 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6T0vsqt098411
	for <ietf-calendar-bks@above.proper.com>; Mon, 28 Jul 2003 17:57:54 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6T0vsAE098410
	for ietf-calendar-bks; Mon, 28 Jul 2003 17:57:54 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6T0vqqt098405
	for <ietf-calendar@imc.org>; Mon, 28 Jul 2003 17:57:52 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6T0vqEB016960
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Mon, 28 Jul 2003 17:57:53 -0700
Message-ID: <3F25C68A.6020804@Royer.com>
Date: Mon, 28 Jul 2003 18:57:46 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: CAP-11 is out
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060101090204040806080007"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms060101090204040806080007
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


CAP Issues:

-> Search for TBD - Its in the BEEP profile registration
                     suggestions welcome.

 From this point forward I am going to start updating the CALSCH.ORG
website with issues and tracking them. I'll send the URL as
soon as issues start to be posted.

Unless the chairs override me, I plan on NO MORE NEW CAP PROPOSALS
(except the BEEP profile).

At this point in CAPs life there should be the following type
of CAP issues:

    1) I found something busted and must be fixed issues.
    2) I do not understand what the text is saying.
    3) The text is conflicting.
    4) Missing data/text/something.
    5) Typo's.
    6) We agreed to ... and it is not in CAP.

Please post so we can do our LAST CALL.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms060101090204040806080007
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINRDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDIwOTE4MDAw
MDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD
EEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuOjEp298xKmKaSoPmY4WupTfjVMvob
cj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umSqlGIEwX6u2g2lfhJIG1nAYCAItpB
JXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzvq3gGiEg4kjV+KC+peZLB9YpiuEFx
3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvfvMcUKdzRub3F/GNvDgu6dd1Jq52t
VrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJJKkkZRaZAgMBAAGjggEGMIIBAjAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAo
oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9ttwSYnVsHPS1PcjLxGL5gSrWxN1G
VNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcUioomgeYc81cGfR1diWN7mnZNFuXZ
Ztb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJ
PKEwDQYJKoZIhvcNAQEEBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQwHhcNMDIwOTE4MDAwMDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD
VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixM
SUFCLkxURChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsT
KkRpZ2l0YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQK
RG91ZyBSb3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDEEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuO
jEp298xKmKaSoPmY4WupTfjVMvobcj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umS
qlGIEwX6u2g2lfhJIG1nAYCAItpBJXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzv
q3gGiEg4kjV+KC+peZLB9YpiuEFx3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvf
vMcUKdzRub3F/GNvDgu6dd1Jq52tVrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJ
JKkkZRaZAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG
+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIG
CCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhC
AQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xh
c3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9
ttwSYnVsHPS1PcjLxGL5gSrWxN1GVNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcU
ioomgeYc81cGfR1diWN7mnZNFuXZZtb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jGCBKowggSm
AgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ
QSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh
c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAe
jFNQR/pY9ailMryViTyhMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDcyOTAwNTc0NlowIwYJKoZIhvcNAQkEMRYEFPkv/29c
Huf9ZyQRfbhUg7uw/Hz0MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEE
AYI3EAQxgeQwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEB6MU1BH+lj1qKUyvJWJPKEwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAejFNQR/pY9ailMryViTyhMA0G
CSqGSIb3DQEBAQUABIIBAF1D7DGvy21bZramnDN+FrjM/L8Vhx+YcbCFKix9e0mhcs12C7Uv
eQ5pbBHoXBwYs6ZA7h6cy8R91Nb/0tZ6IALwPitfA9uUlmMGP/87g9xntj8Nl8q27JqaxWyu
d0d3f+Fp39Uh/IilSh3lg17NaDAHe+ckNrTcd2sLSnjzsrQTLwaqbYdqWL9VZpS2HL/lihfR
+mMpPBtG6mIOClVK2pN4cwwlPB8GgJ1aUuAVQ7HVTskATrIHSeuzJOxvnfgMGLQALXovx8gT
cQp8NSfDVgXAOsD3pygTUUPQPt0PmVAqvoZE/uWOS9LUgYH6lXW0Na57D+GJeqQhV7RCtyad
XdgAAAAAAAA=
--------------ms060101090204040806080007--



From owner-ietf-calendar@mail.imc.org  Thu Jul 31 15:12:38 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09489
	for <calsch-archive@lists.ietf.org>; Thu, 31 Jul 2003 15:12:38 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VJ04qt003218
	for <ietf-calendar-bks@above.proper.com>; Thu, 31 Jul 2003 12:00:04 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6VJ04X6003217
	for ietf-calendar-bks; Thu, 31 Jul 2003 12:00:04 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VJ02qt003212
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 12:00:03 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: ietf-calendar@imc.org
Subject: Free Busy topic 
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF0B3C479A.5630273D-ON85256D74.006803C6-85256D74.00686087@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Thu, 31 Jul 2003 15:00:04 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/31/2003 03:00:05 PM,
	Serialize complete at 07/31/2003 03:00:05 PM
Content-Type: multipart/alternative; boundary="=_alternative 0068607F85256D74_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0068607F85256D74_=
Content-Type: text/plain; charset="us-ascii"

Hi, I'm posting the following note from a calendaring user who is 
currently working on creating icalendar objects. He's a programmer - but 
calendaring is not his thing.  He's just recently learned about reading 
RFC's to get the rules.  He will be subscribing to the list - but in the 
mean time I thought I'd post his note.  He did not know we've had some 
debate on the list about free busy.  I thought it would be a good thing to 
post his note - because this is a user who understands what a calendaring 
object can do.  He has supported email and calendar systems most of this 
career.  He gets it - and since we see lots of stuff on the list from 
vendors and not from users - this might be helpful.

Here's his note = somewhat cyptic - but I think you'll get the gist.

"This actually was sent to me today (vendor name filed off to protect their
miserable hides):

We are trying to arrange a conference call with the vendor development
staff for sometime this week.

They have a copy of your questions, and when we can arrange for the
call, I am sure they will discuss them.

I sent them a series of times that were available where everyone could
be on the call, I will check with them this morning and see if they
have agreed on a time.

(this is Tim's question for the list below)

The next challenge for calendaring and scheduling? I'm sure you guys have
free/busy time in the standards - but is there ongoing work about having
that data permeate the "cell membrane" of the organization without pubicly
publishing other calendar data?

Tim Hare
Senior Systems Programmer
Florida Department of Transportation

--=_alternative 0068607F85256D74_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Hi, I'm posting the following note from a calendaring user who is currently working on creating icalendar objects. He's a programmer - but calendaring is not his thing. &nbsp;He's just recently learned about reading RFC's to get the rules. &nbsp;He will be subscribing to the list - but in the mean time I thought I'd post his note. &nbsp;He did not know we've had some debate on the list about free busy. &nbsp;I thought it would be a good thing to post his note - because this is a user who understands what a calendaring object can do. &nbsp;He has supported email and calendar systems most of this career. &nbsp;He gets it - and since we see lots of stuff on the list from vendors and not from users - this might be helpful.</font>
<br>
<br><font size=2 face="sans-serif">Here's his note = somewhat cyptic - but I think you'll get the gist.</font>
<br>
<br><font size=2 face="sans-serif">&quot;</font><font size=2><tt>This actually was sent to me today (vendor name filed off to protect their<br>
miserable hides):<br>
</tt></font>
<br><font size=2><tt>We are trying to arrange a conference call with the vendor development<br>
staff for sometime this week.<br>
</tt></font>
<br><font size=2><tt>They have a copy of your questions, and when we can arrange for the<br>
call, I am sure they will discuss them.<br>
</tt></font>
<br><font size=2><tt>I sent them a series of times that were available where everyone could<br>
be on the call, I will check with them this morning and see if they<br>
have agreed on a time.</tt></font>
<br>
<br><font size=2><tt>(this is Tim's question for the list below)<br>
</tt></font>
<br><font size=2><tt>The next challenge for calendaring and scheduling? I'm sure you guys have<br>
free/busy time in the standards - but is there ongoing work about having<br>
that data permeate the &quot;cell membrane&quot; of the organization without pubicly<br>
publishing other calendar data?<br>
</tt></font>
<br><font size=2><tt>Tim Hare<br>
Senior Systems Programmer<br>
Florida Department of Transportation<br>
</tt></font>
--=_alternative 0068607F85256D74_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 31 15:26:44 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10205
	for <calsch-archive@lists.ietf.org>; Thu, 31 Jul 2003 15:26:44 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VJE3qt003827
	for <ietf-calendar-bks@above.proper.com>; Thu, 31 Jul 2003 12:14:03 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6VJE3RM003826
	for ietf-calendar-bks; Thu, 31 Jul 2003 12:14:03 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by above.proper.com (8.12.9/8.12.8) with SMTP id h6VJE1qt003816
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 12:14:02 -0700 (PDT)
	(envelope-from JStracke@centive.com)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003073115233910189
 for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 15:23:39 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 31 Jul 2003 15:11:16 -0400
Message-ID: <3F2969D4.4070005@centive.com>
Date: Thu, 31 Jul 2003 15:11:16 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Free Busy topic
References: <OF0B3C479A.5630273D-ON85256D74.006803C6-85256D74.00686087@egenconsulting.com>
In-Reply-To: <OF0B3C479A.5630273D-ON85256D74.006803C6-85256D74.00686087@egenconsulting.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jul 2003 19:11:17.0004 (UTC) FILETIME=[846ED4C0:01C35797]
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


pregen@egenconsulting.com wrote:

> I'm sure you guys have
> free/busy time in the standards - but is there ongoing work about having
> that data permeate the "cell membrane" of the organization without pubicly
> publishing other calendar data?

That can be done with iTIP, right? A VFREEBUSY request comes in, and the 
CUA or CS can decide what to do about it.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"Chris is the most self-effacing guy I know." "Well, I'm not|
|*that* good at it."                                         |
\============================================================/




From owner-ietf-calendar@mail.imc.org  Thu Jul 31 16:03:06 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12180
	for <calsch-archive@lists.ietf.org>; Thu, 31 Jul 2003 16:03:05 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VJqjqt005691
	for <ietf-calendar-bks@above.proper.com>; Thu, 31 Jul 2003 12:52:45 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6VJqiUS005690
	for ietf-calendar-bks; Thu, 31 Jul 2003 12:52:44 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from royer.com (inet-consulting.com [4.23.9.166])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VJqhqt005683
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 12:52:43 -0700 (PDT)
	(envelope-from Doug@Royer.com)
Received: from Royer.com (inet-products.com [12.110.12.238])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id h6VJqgEB012459
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 12:52:44 -0700
Message-ID: <3F297385.9060608@Royer.com>
Date: Thu, 31 Jul 2003 13:52:37 -0600
From: Doug Royer <Doug@royer.com>
Reply-To: ietf-calendar@imc.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Free Busy topic
References: <OF0B3C479A.5630273D-ON85256D74.006803C6-85256D74.00686087@egenconsulting.com>
In-Reply-To: <OF0B3C479A.5630273D-ON85256D74.006803C6-85256D74.00686087@egenconsulting.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070304060106070007030107"
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a cryptographically signed message in MIME format.

--------------ms070304060106070007030107
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit




> 
> The next challenge for calendaring and scheduling? I'm sure you guys have
> free/busy time in the standards - but is there ongoing work about having
> that data permeate the "cell membrane" of the organization without pubicly
> publishing other calendar data?

Using iMIP - The feature already exists.

Using CAP - Yes. Using VCARs allow a CUA to fetch the VFREEBUSY
             time. And using VCARs the other components can be
             restricted (or allowed) as the owner sees fit.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards

--------------ms070304060106070007030107
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINRDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJPKEwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDIwOTE4MDAw
MDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD
EEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuOjEp298xKmKaSoPmY4WupTfjVMvob
cj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umSqlGIEwX6u2g2lfhJIG1nAYCAItpB
JXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzvq3gGiEg4kjV+KC+peZLB9YpiuEFx
3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvfvMcUKdzRub3F/GNvDgu6dd1Jq52t
VrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJJKkkZRaZAgMBAAGjggEGMIIBAjAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAo
oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9ttwSYnVsHPS1PcjLxGL5gSrWxN1G
VNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcUioomgeYc81cGfR1diWN7mnZNFuXZ
Ztb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jCCBOswggRUoAMCAQICEB6MU1BH+lj1qKUyvJWJ
PKEwDQYJKoZIhvcNAQEEBQAwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl
cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W
ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW
YWxpZGF0ZWQwHhcNMDIwOTE4MDAwMDAwWhcNMDMwOTE4MjM1OTU5WjCCAQsxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD
VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixM
SUFCLkxURChjKTk4MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsT
KkRpZ2l0YWwgSUQgQ2xhc3MgMSAtIE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQK
RG91ZyBSb3llcjEdMBsGCSqGSIb3DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDEEdQIl3XiWTOQkkpItylRI2rKbxVg1IzkcQpZ2/jcVuO
jEp298xKmKaSoPmY4WupTfjVMvobcj8qS9D1PMZamtivKL+om94xqHo/Psc9A57ibZiV5umS
qlGIEwX6u2g2lfhJIG1nAYCAItpBJXuMDpDICIS/n9A9hjkpwD03cjg96YSgLmRLWM8PvHzv
q3gGiEg4kjV+KC+peZLB9YpiuEFx3+1c2TrxWk6pQ5lK5Kuf5EccoS4hLZ46PbzkgCfRbqvf
vMcUKdzRub3F/GNvDgu6dd1Jq52tVrlR1hLGRODEXhaBfCHcl9kzyKhEJURI3cOmyApulYVJ
JKkkZRaZAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG
+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIG
CCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhC
AQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xh
c3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQCghngGsGOsnFS9lbtsCZbIesZa/6gF92Q48YG9
ttwSYnVsHPS1PcjLxGL5gSrWxN1GVNanVdMqjz+F8K53NtGpQ3YI1yiOQEDLTMfeGJbIUOcU
ioomgeYc81cGfR1diWN7mnZNFuXZZtb+G+kzUOy0ciHI4HlZp0gLXjGatLrp4jGCBKowggSm
AgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ
QSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh
c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAe
jFNQR/pY9ailMryViTyhMAkGBSsOAwIaBQCgggKdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDczMTE5NTIzN1owIwYJKoZIhvcNAQkEMRYEFE5soi61
a+Qzkfhqa5tc5BnyKDjbMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHyBgkrBgEE
AYI3EAQxgeQwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEB6MU1BH+lj1qKUyvJWJPKEwgfQGCyqGSIb3DQEJEAILMYHkoIHhMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAejFNQR/pY9ailMryViTyhMA0G
CSqGSIb3DQEBAQUABIIBAHlvLyc+N1z4L+08HPeZmios5cyJaU1pOzaROUTUCFWQOpoORFll
C59eR4Zvd6vh1oh/MkOjGl4+XUFQzlPjFU4XydHE3JGMHajRmQLO+yuAbyymTZUeZtLyqptv
zTxq7rO1zIPOGyROA4sOxOHNMiRwA3hvCEFZkUtYzB34o2x2SjuJ9uMphPlozgb60TT55yBF
B/9JLJ8R1RzngcTEHXQ0+fYCYm0F4qQguk0NwCOTc9BQn2r7GTQsgXHUn7bs79CERcLaYkQp
kzYMJFtsOGRhX9mfo40Evbd+/QaRh0JbPsNagVwF+1szPCZ0QH6Udt5k2B/nwKBtqntKq9h7
BFUAAAAAAAA=
--------------ms070304060106070007030107--



From owner-ietf-calendar@mail.imc.org  Thu Jul 31 16:42:07 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13209
	for <calsch-archive@lists.ietf.org>; Thu, 31 Jul 2003 16:42:07 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VKWbqt010867
	for <ietf-calendar-bks@above.proper.com>; Thu, 31 Jul 2003 13:32:37 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6VKWblj010865
	for ietf-calendar-bks; Thu, 31 Jul 2003 13:32:37 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VKWaqt010854
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 13:32:36 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: ietf-calendar@imc.org
Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
Subject: Re: Free Busy topic
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF99D989A0.9DE9CB90-ON85256D74.0070CD91-85256D74.0070D916@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Thu, 31 Jul 2003 16:32:35 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/31/2003 04:32:38 PM,
	Serialize complete at 07/31/2003 04:32:38 PM
Content-Type: multipart/alternative; boundary="=_alternative 0070D90985256D74_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 0070D90985256D74_=
Content-Type: text/plain; charset="us-ascii"

Interesting.  John says iTIP and Doug says iMIP.  Sounds like maybe it's 
confusing?
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




Doug Royer <Doug@royer.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/31/2003 15:52
Please respond to ietf-calendar

 
        To:     ietf-calendar@imc.org
        cc: 
        Subject:        Re: Free Busy topic





> 
> The next challenge for calendaring and scheduling? I'm sure you guys 
have
> free/busy time in the standards - but is there ongoing work about having
> that data permeate the "cell membrane" of the organization without 
pubicly
> publishing other calendar data?

Using iMIP - The feature already exists.

Using CAP - Yes. Using VCARs allow a CUA to fetch the VFREEBUSY
             time. And using VCARs the other components can be
             restricted (or allowed) as the owner sees fit.

-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug@Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards



--=_alternative 0070D90985256D74_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Interesting. &nbsp;John says iTIP and Doug says iMIP. &nbsp;Sounds like maybe it's confusing?<br>
___________________<br>
Patricia Egen Consulting<br>
www.egenconsulting.com<br>
423-875-2652</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Doug Royer &lt;Doug@royer.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/31/2003 15:52</font>
<br><font size=1 face="sans-serif">Please respond to ietf-calendar</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;ietf-calendar@imc.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: Free Busy topic</font></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
<br>
&gt; <br>
&gt; The next challenge for calendaring and scheduling? I'm sure you guys have<br>
&gt; free/busy time in the standards - but is there ongoing work about having<br>
&gt; that data permeate the &quot;cell membrane&quot; of the organization without pubicly<br>
&gt; publishing other calendar data?<br>
<br>
Using iMIP - The feature already exists.<br>
<br>
Using CAP - Yes. Using VCARs allow a CUA to fetch the VFREEBUSY<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; time. And using VCARs the other components can be<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; restricted (or allowed) as the owner sees fit.<br>
<br>
-- <br>
<br>
 &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
 &nbsp;-------------------------------|-----------------------------<br>
 &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
 &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards - You Need Standards<br>
</tt></font>
<br>
<br>
--=_alternative 0070D90985256D74_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 31 16:56:44 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13619
	for <calsch-archive@lists.ietf.org>; Thu, 31 Jul 2003 16:56:43 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VKmKqt011770
	for <ietf-calendar-bks@above.proper.com>; Thu, 31 Jul 2003 13:48:20 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6VKmKt8011769
	for ietf-calendar-bks; Thu, 31 Jul 2003 13:48:20 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by above.proper.com (8.12.9/8.12.8) with SMTP id h6VKmIqu011752
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 13:48:19 -0700 (PDT)
	(envelope-from JStracke@centive.com)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003073116575412707
 ; Thu, 31 Jul 2003 16:57:54 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 31 Jul 2003 16:45:33 -0400
Message-ID: <3F297FEC.30303@centive.com>
Date: Thu, 31 Jul 2003 16:45:32 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pregen@egenconsulting.com
CC: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
Subject: Re: Free Busy topic
References: <OF99D989A0.9DE9CB90-ON85256D74.0070CD91-85256D74.0070D916@egenconsulting.com>
In-Reply-To: <OF99D989A0.9DE9CB90-ON85256D74.0070CD91-85256D74.0070D916@egenconsulting.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jul 2003 20:45:33.0018 (UTC) FILETIME=[AFAE13A0:01C357A4]
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


pregen@egenconsulting.com wrote:

>
> Interesting.  John says iTIP and Doug says iMIP.  Sounds like maybe 
> it's confusing?

<shrug> Not very.  I said iTIP because that's where the feature is 
defined; Doug probably said iMIP because that'd be the common way of 
exposing it to the world.

>
> ___________________
> Patricia Egen Consulting
> www.egenconsulting.com
> 423-875-2652
>
>
>
> 	*Doug Royer <Doug@royer.com>*
> Sent by: owner-ietf-calendar@mail.imc.org
>
> 07/31/2003 15:52
> Please respond to ietf-calendar
>
> 	       
>         To:        ietf-calendar@imc.org
>         cc:        
>         Subject:        Re: Free Busy topic
>
>
>
>
>
>
>
> >
> > The next challenge for calendaring and scheduling? I'm sure you guys 
> have
> > free/busy time in the standards - but is there ongoing work about having
> > that data permeate the "cell membrane" of the organization without 
> pubicly
> > publishing other calendar data?
>
> Using iMIP - The feature already exists.
>
> Using CAP - Yes. Using VCARs allow a CUA to fetch the VFREEBUSY
>             time. And using VCARs the other components can be
>             restricted (or allowed) as the owner sees fit.
>
> -- 
>
>  Doug Royer                     |   http://INET-Consulting.com
>  -------------------------------|-----------------------------
>  Doug@Royer.com                 | Office: (208)612-INET
>  http://Royer.com/People/Doug   |    Fax: (866)594-8574
>                                 |   Cell: (208)520-4044
>
>                 We Do Standards - You Need Standards
>
>


-- 
/================================================================\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|================================================================|
|The voices say I'm not schizophrenic, but they're not sure about|
|you.                                                            |
\================================================================/




From owner-ietf-calendar@mail.imc.org  Thu Jul 31 17:10:51 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14125
	for <calsch-archive@lists.ietf.org>; Thu, 31 Jul 2003 17:10:50 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VL2pqt012442
	for <ietf-calendar-bks@above.proper.com>; Thu, 31 Jul 2003 14:02:51 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6VL2p5E012441
	for ietf-calendar-bks; Thu, 31 Jul 2003 14:02:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from www.egenconsulting.com (www.egenconsulting.com [208.31.106.82])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VL2nqt012421
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 14:02:49 -0700 (PDT)
	(envelope-from pregen@egenconsulting.com)
To: John Stracke <jstracke@centive.com>
Cc: ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
Subject: Re: Free Busy topic
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFF5041EFF.8DE4672F-ON85256D74.007399AB-85256D74.00739E8F@egenconsulting.com>
From: pregen@egenconsulting.com
Date: Thu, 31 Jul 2003 17:02:52 -0400
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.12  |February
 13, 2003) at 07/31/2003 05:02:52 PM,
	Serialize complete at 07/31/2003 05:02:52 PM
Content-Type: multipart/alternative; boundary="=_alternative 00739E6C85256D74_="
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


This is a multipart message in MIME format.
--=_alternative 00739E6C85256D74_=
Content-Type: text/plain; charset="us-ascii"

gotcha.




John Stracke <jstracke@centive.com>
Sent by: owner-ietf-calendar@mail.imc.org
07/31/2003 16:45

 
        To:     pregen@egenconsulting.com
        cc:     ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org
        Subject:        Re: Free Busy topic



pregen@egenconsulting.com wrote:

>
> Interesting.  John says iTIP and Doug says iMIP.  Sounds like maybe
> it's confusing?

<shrug> Not very.  I said iTIP because that's where the feature is
defined; Doug probably said iMIP because that'd be the common way of
exposing it to the world.

>
> ___________________
> Patricia Egen Consulting
> www.egenconsulting.com
> 423-875-2652
>
>
>
>       *Doug Royer <Doug@royer.com>*
> Sent by: owner-ietf-calendar@mail.imc.org
>
> 07/31/2003 15:52
> Please respond to ietf-calendar
>
>
>         To:        ietf-calendar@imc.org
>         cc:
>         Subject:        Re: Free Busy topic
>
>
>
>
>
>
>
> >
> > The next challenge for calendaring and scheduling? I'm sure you guys
> have
> > free/busy time in the standards - but is there ongoing work about 
having
> > that data permeate the "cell membrane" of the organization without
> pubicly
> > publishing other calendar data?
>
> Using iMIP - The feature already exists.
>
> Using CAP - Yes. Using VCARs allow a CUA to fetch the VFREEBUSY
>             time. And using VCARs the other components can be
>             restricted (or allowed) as the owner sees fit.
>
> --
>
>  Doug Royer                     |   http://INET-Consulting.com
>  -------------------------------|-----------------------------
>  Doug@Royer.com                 | Office: (208)612-INET
>  http://Royer.com/People/Doug   |    Fax: (866)594-8574
>                                 |   Cell: (208)520-4044
>
>                 We Do Standards - You Need Standards
>
>


--
/================================================================\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|================================================================|
|The voices say I'm not schizophrenic, but they're not sure about|
|you.                                                            |
\================================================================/




--=_alternative 00739E6C85256D74_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">gotcha.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>John Stracke &lt;jstracke@centive.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/31/2003 16:45</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;pregen@egenconsulting.com</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;ietf-calendar@imc.org, owner-ietf-calendar@mail.imc.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: Free Busy topic</font></table>
<br>
<br>
<br>
<br><font size=2><tt>pregen@egenconsulting.com wrote:<br>
</tt></font>
<br><font size=2><tt>&gt;<br>
&gt; Interesting. &nbsp;John says iTIP and Doug says iMIP. &nbsp;Sounds like maybe<br>
&gt; it's confusing?<br>
</tt></font>
<br><font size=2><tt>&lt;shrug&gt; Not very. &nbsp;I said iTIP because that's where the feature is<br>
defined; Doug probably said iMIP because that'd be the common way of<br>
exposing it to the world.<br>
</tt></font>
<br><font size=2><tt>&gt;<br>
&gt; ___________________<br>
&gt; Patricia Egen Consulting<br>
&gt; www.egenconsulting.com<br>
&gt; 423-875-2652<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; *Doug Royer &lt;Doug@royer.com&gt;*<br>
&gt; Sent by: owner-ietf-calendar@mail.imc.org<br>
&gt;<br>
&gt; 07/31/2003 15:52<br>
&gt; Please respond to ietf-calendar<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;ietf-calendar@imc.org<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; cc:<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: Free Busy topic<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; The next challenge for calendaring and scheduling? I'm sure you guys<br>
&gt; have<br>
&gt; &gt; free/busy time in the standards - but is there ongoing work about having<br>
&gt; &gt; that data permeate the &quot;cell membrane&quot; of the organization without<br>
&gt; pubicly<br>
&gt; &gt; publishing other calendar data?<br>
&gt;<br>
&gt; Using iMIP - The feature already exists.<br>
&gt;<br>
&gt; Using CAP - Yes. Using VCARs allow a CUA to fetch the VFREEBUSY<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; time. And using VCARs the other components can be<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; restricted (or allowed) as the owner sees fit.<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt; &nbsp;Doug Royer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; http://INET-Consulting.com<br>
&gt; &nbsp;-------------------------------|-----------------------------<br>
&gt; &nbsp;Doug@Royer.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Office: (208)612-INET<br>
&gt; &nbsp;http://Royer.com/People/Doug &nbsp; | &nbsp; &nbsp;Fax: (866)594-8574<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; Cell: (208)520-4044<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; We Do Standards - You Need Standards<br>
&gt;<br>
&gt;<br>
</tt></font>
<br>
<br><font size=2><tt>--<br>
/================================================================\<br>
|John Stracke &nbsp; &nbsp; &nbsp;|jstracke@centive.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
|Principal Engineer|http://www.centive.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
|Centive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |My opinions are my own. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<br>
|================================================================|<br>
|The voices say I'm not schizophrenic, but they're not sure about|<br>
|you. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<br>
\================================================================/<br>
</tt></font>
<br>
<br>
<br>
--=_alternative 00739E6C85256D74_=--


From owner-ietf-calendar@mail.imc.org  Thu Jul 31 18:52:36 2003
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17913
	for <calsch-archive@lists.ietf.org>; Thu, 31 Jul 2003 18:52:36 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VMhaqt017016
	for <ietf-calendar-bks@above.proper.com>; Thu, 31 Jul 2003 15:43:36 -0700 (PDT)
	(envelope-from owner-ietf-calendar@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.9/8.12.9/Submit) id h6VMhaia017015
	for ietf-calendar-bks; Thu, 31 Jul 2003 15:43:36 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-calendar@mail.imc.org using -f
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h6VMhYqt017006
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 15:43:34 -0700 (PDT)
	(envelope-from satyanarayana.vempati@Sun.COM)
Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42])
	by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h6VMha8H007229
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 16:43:37 -0600 (MDT)
Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91])
	by sfbaymail2sca.sfbay.sun.com (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h6VMhaaJ028695
	for <ietf-calendar@imc.org>; Thu, 31 Jul 2003 15:43:36 -0700 (PDT)
Received: from pranav.red.iplanet.com (pranav.red.iplanet.com [192.18.144.109])
 by ha13sca-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct  1 2002))
 with ESMTP id <0HIW00BB7V4OAD@ha13sca-mail1.sfbay.sun.com> for
 ietf-calendar@imc.org; Thu, 31 Jul 2003 15:43:36 -0700 (PDT)
Date: Thu, 31 Jul 2003 15:43:38 -0700
From: Satya Vempati <satyanarayana.vempati@Sun.COM>
Subject: RECURRENCE-ID discussion
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Message-id: <ISSMTP.2003_10b_.20030731154338.2260B@sun.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-language: en-USA
Content-transfer-encoding: 7BIT
Sender: owner-ietf-calendar@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-ID: <ietf-calendar.imc.org>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7BIT


Is there an update on when the iCal authors will post their thinking on
the subject?



