From ietf-calsify-bounces@osafoundation.org Tue Nov 06 04:03:16 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IpKL6-0005WI-O7
	for calsify-archive-Feit0ahl@lists.ietf.org; Tue, 06 Nov 2007 04:03:16 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IpKL1-00045C-NL
	for calsify-archive-Feit0ahl@lists.ietf.org; Tue, 06 Nov 2007 04:03:16 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 462B78076A;
	Tue,  6 Nov 2007 01:04:05 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 60FEE8071B
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 01:04:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id A53E914220D
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 01:03:09 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-50 required=4 tests=[AWL=0.529, 
	BAYES_00=-2.599, FORGED_RCVD_HELO=0.135, SPF_PASS=-0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id jaxlulXOezz8 for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 01:03:03 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 78AAA14220C
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 01:03:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.21,377,1188770400"; d="scan'208";a="156985993"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 06 Nov 2007 10:02:59 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lA692xKe012868; 
	Tue, 6 Nov 2007 10:02:59 +0100
Received: from adsl-247-6-fixip.tiscali.ch (ams3-vpn-dhcp380.cisco.com
	[10.61.65.124])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lA692kqT022292; 
	Tue, 6 Nov 2007 09:02:46 GMT
Message-ID: <47302DB0.1050207@cisco.com>
Date: Tue, 06 Nov 2007 10:02:40 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <471612F8.9020306@cisco.com>
In-Reply-To: <471612F8.9020306@cisco.com>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2693; t=1194339779;
	x=1195203779; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com;
	z=From:=20Eliot=20Lear=20<lear@cisco.com>
	|Subject:=20Re=3A=20[Ietf-calsify]=20RFC=202445bis=20Issue=2063=3A=20Cons
	ensus=20needed |Sender:=20;
	bh=SkvBzISSAe7XUyqoKiqeaaKjHEROBp9t9QKQSt7wpQ8=;
	b=c6tSaOriQRk5qXP2Gbd0Ldn5ksyaamfwlhHnq9ixpzsihhRwVMJTULV5IL9ZoN79LqIYWQcm
	AkdnAgUg7S5U60VxUnvcFzmwD38huTQ3zHU5CDziY6Zp/HCZiUZa7Ue1;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass (s
	ig from cisco.com/amsdkim1002 verified; ); 
Cc: "ietf-calsify@osafoundation.org" <ietf-calsify@osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30

Bernard,

We have heard no discussion on your proposal.  Fair warning to all:
silence shall equal consent to the request below.

Eliot

Eliot Lear wrote:
> Dear all,
>
> On August 3rd, Bernard tried for the third time to gain consensus on
> this topic.  Please comment now.  We would like to close RFC2445bis and
> this is one of several niggling points remaining.
>
> Please state your preference as to which solution below you prefer.
>
> Thank you,
>
> Eliot
>   
>
> ------------------------------------------------------------------------
>
> Subject:
> [Ietf-calsify] Issue 63: Section 4.8.5.3 Recurrence Date/Times: RDATE
> < DTSTART
> From:
> Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
> Date:
> Fri, 03 Aug 2007 17:22:51 -0400
> To:
> Calsify WG <ietf-calsify@osafoundation.org>
>
> To:
> Calsify WG <ietf-calsify@osafoundation.org>
>
>
> Disclaimer: This is the third time I bring up this issue. See:
>
> http://lists.osafoundation.org/pipermail/ietf-calsify/2006-November/001349.html
>
> http://lists.osafoundation.org/pipermail/ietf-calsify/2007-February/001522.html
>
>
> Cyrus recently brought up the fact that the deprecation of
> RANGE=THISANDFUTURE (Issue 48) might be an issue with unbounded
> recurring calendar components in the context of iTIP.
>
> I have already suggested a solution for the case where an
> organizer cancels all future recurrence instances of a
> recurring calendar component.  See:
>
> http://lists.osafoundation.org/pipermail/ietf-calsify/2007-July/001746.html
>
>
> This time I would like to suggest a solution for the case where
> an organizer changes all future recurrence instances of a recurring
> calendar component:
>
> 1- Specify RDATE properties for all past recurrence instances
>    and define exception components for them if needed. The
>    number of past recurrence instances is always finite...
>
> 2- Remove EXDATE properties for any past recurrence instances.
>
> 3- Set DTSTART to the first recurrence instance to which you
>    want the change to apply.
>
> The only issue here is that we need to clarify that RDATE can
> specify a value less than the value specified by DTSTART.
>
> Cheers,
> Bernard
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>   
_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Tue Nov 06 17:14:07 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IpWgR-0001MX-1N
	for calsify-archive-Feit0ahl@lists.ietf.org; Tue, 06 Nov 2007 17:14:07 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IpWgN-0001sd-Hl
	for calsify-archive-Feit0ahl@lists.ietf.org; Tue, 06 Nov 2007 17:14:07 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 971AA809E3;
	Tue,  6 Nov 2007 14:14:56 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 257FA809DC
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 14:14:50 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 683B7142206
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 14:13:55 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.383
X-Spam-Level: 
X-Spam-Status: No, score=-1.383 tagged_above=-50 required=4 tests=[AWL=1.215, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id GUCh2CtmBNFY for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 14:13:49 -0800 (PST)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 963C1142202
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 14:13:49 -0800 (PST)
Received: from fe-sfbay-10.sun.com ([192.18.43.129])
	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	lA6MDlVV012104 for <ietf-calsify@osafoundation.org>;
	Tue, 6 Nov 2007 14:13:49 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	id <0JR300E01V11O600@fe-sfbay-10.sun.com>
	(original mail from Ciny.Joy@Sun.COM) for
	ietf-calsify@osafoundation.org; Tue, 06 Nov 2007 14:13:47 -0800 (PST)
Received: from [192.18.126.79] by fe-sfbay-10.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	with ESMTPSA id <0JR300L5GV2NASC0@fe-sfbay-10.sun.com> for
	ietf-calsify@osafoundation.org; Tue, 06 Nov 2007 14:13:35 -0800 (PST)
Date: Tue, 06 Nov 2007 14:14:56 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
In-reply-to: <20071106200005.569D080A03@leilani.osafoundation.org>
To: ietf-calsify@osafoundation.org
Message-id: <4730E760.4090309@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
References: <20071106200005.569D080A03@leilani.osafoundation.org>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20051027
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69


>
>>
>>This time I would like to suggest a solution for the case where
>>an organizer changes all future recurrence instances of a recurring
>>calendar component:
>>
>>1- Specify RDATE properties for all past recurrence instances
>>   and define exception components for them if needed. 
>>
How do you define "if needed"?

>>The
>>   number of past recurrence instances is always finite...
>>
>>2- Remove EXDATE properties for any past recurrence instances.
>>
>>3- Set DTSTART to the first recurrence instance to which you
>>   want the change to apply.
>>    
>>
So is original DTSTART lost completely? Doesn't this go against the 
statement, "However, in such cases the original "DTSTART" date MUST 
still be maintained by the calendaring and scheduling system because the 
original "DTSTART" value has inherent usage dependencies by other 
properties such as the "RECURRENCE-ID"."
If not, is there a standard way of maintaining it?
Also, in multiple places it is stated "The "DTSTART" property defines 
the first instance in the recurrence set". Will that be modified?

Thanks,
Ciny

>>The only issue here is that we need to clarify that RDATE can
>>specify a value less than the value specified by DTSTART.
>>
>>Cheers,
>>Bernard
>>    
>>

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 07 00:00:38 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ipd1q-0004at-H6
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 07 Nov 2007 00:00:38 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ipd1m-00089F-Jc
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 07 Nov 2007 00:00:38 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 4E86E80A51;
	Tue,  6 Nov 2007 21:01:17 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 81A9780A45
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 21:01:15 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id C887F14220D
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 21:00:20 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.453
X-Spam-Level: 
X-Spam-Status: No, score=-1.453 tagged_above=-50 required=4 tests=[AWL=1.011, 
	BAYES_00=-2.599, FORGED_RCVD_HELO=0.135]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id fuHK-r32GMxZ for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 21:00:14 -0800 (PST)
Received: from smtp22.ihug.co.nz (smtp22.ihug.co.nz [203.109.136.122])
	by laweleka.osafoundation.org (Postfix) with ESMTP id BF843142203
	for <ietf-calsify@osafoundation.org>;
	Tue,  6 Nov 2007 21:00:11 -0800 (PST)
Received: from cust.filter2.content.ihug.net.nz (smtp.mailfilter2.ihug.co.nz)
	[10.80.50.2] by smtp22.ihug.co.nz with esmtp
	(Exim 4.60 #1 (Debian); Ihug conf #192)
	id 1Ipd1N-0003JC-0b; Wed, 07 Nov 2007 18:00:09 +1300
Ironport-Content-Filter: send-to-smtp
Received: from 121-73-60-39.cable.telstraclear.net (HELO [127.0.0.1])
	([121.73.60.39])
	by smtp.mailfilter2.ihug.co.nz with ESMTP; 07 Nov 2007 18:00:08 +1300
Message-ID: <47314658.4010502@softdesign.net.nz>
Date: Wed, 07 Nov 2007 18:00:08 +1300
From: Andrew N Dowden <andrew_dowden@softdesign.net.nz>
Organization: Dowden Software Associates
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf-calsify <ietf-calsify@osafoundation.org>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <471612F8.9020306@cisco.com> <47302DB0.1050207@cisco.com>
In-Reply-To: <47302DB0.1050207@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

Eliot Lear wrote:
>> This time I would like to suggest a solution for the case where
>> an organizer changes all future recurrence instances of a recurring
>> calendar component:
>>
>> 1- Specify RDATE properties for all past recurrence instances
>>    and define exception components for them if needed. The
>>    number of past recurrence instances is always finite...
>>
>> 2- Remove EXDATE properties for any past recurrence instances.
>>
>> 3- Set DTSTART to the first recurrence instance to which you
>>    want the change to apply.
>>
>> The only issue here is that we need to clarify that RDATE can
>> specify a value less than the value specified by DTSTART.
>>     
Is there anything wrong with? :

1- Specify RDATE properties for all past recurrence instances,
    while excluding those removed by EXDATE properties..
   ( The number of past recurrence instances is always finite. )

2- Remove any RRULE and EXDATE properties.

3- Set DTSTART to match the first RDATE property.

-- 
_______________________________________________

  SoftDesign Group
  Dowden Software Associates
  P O Box 31 132, Lower Hutt 5040, NEW ZEALAND

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 07 08:32:06 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ipl0o-0002yA-HL
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 07 Nov 2007 08:32:06 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ipl0k-0008VT-UK
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 07 Nov 2007 08:32:06 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 86714808F6;
	Wed,  7 Nov 2007 05:32:56 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id C004F808BE
	for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:32:55 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 12968142203
	for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:32:01 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-50 required=4 tests=[AWL=0.778, 
	BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id Jzkf5c6vTqCY for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:31:52 -0800 (PST)
Received: from mgw-ext14.nokia.com (smtp.nokia.com [131.228.20.173])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 0D562142212
	for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:31:51 -0800 (PST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA7DVRCr015160
	for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:31:48 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Nov 2007 15:31:46 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Nov 2007 15:26:02 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh101.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 7 Nov 2007 15:26:01 +0200
Received: from [172.21.40.154] (esdhcp040154.research.nokia.com
	[172.21.40.154])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA7DPxUK009638
	for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:25:59 +0200
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify <ietf-calsify@osafoundation.org>
In-Reply-To: <1194441607.28623.0.camel@scotty>
References: <1194441607.28623.0.camel@scotty>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Wed, 07 Nov 2007 15:26:05 +0200
Message-Id: <1194441965.28623.3.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2007 13:26:01.0549 (UTC)
	FILETIME=[BD793FD0:01C82141]
X-Nokia-AV: Clean
Subject: [Ietf-calsify] Correction: in *1 hour* and 5 minutes. (was: Re:
	Reminder: scheduled weekly jabber chat starting in 10 minutes)
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed

(Sigh) :)


_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 07 08:43:54 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IplCE-0004Rz-SP
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 07 Nov 2007 08:43:54 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IplCA-0000bM-QJ
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 07 Nov 2007 08:43:54 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 87E06808FA;
	Wed,  7 Nov 2007 05:44:44 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id BC840808F6
	for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:44:42 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 0FB83142212
	for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:43:48 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.728
X-Spam-Level: 
X-Spam-Status: No, score=-1.728 tagged_above=-50 required=4 tests=[AWL=0.871, 
	BAYES_00=-2.599]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id YF8lPb17BKmR for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:43:43 -0800 (PST)
Received: from mgw-ext13.nokia.com (smtp.nokia.com [131.228.20.172])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 30D71142203
	for <ietf-calsify@osafoundation.org>;
	Wed,  7 Nov 2007 05:43:42 -0800 (PST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA7DhcMd016031
	for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:43:39 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Nov 2007 15:42:43 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Nov 2007 15:20:16 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 7 Nov 2007 15:20:15 +0200
Received: from [172.21.41.205] (esdhcp041205.research.nokia.com
	[172.21.41.205])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA7DK22I002132
	for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:20:14 +0200
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify <ietf-calsify@osafoundation.org>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Wed, 07 Nov 2007 15:20:07 +0200
Message-Id: <1194441607.28623.0.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2007 13:20:15.0982 (UTC)
	FILETIME=[EF7FE8E0:01C82140]
X-Nokia-AV: Clean
Subject: [Ietf-calsify] Reminder: scheduled weekly jabber chat starting in
	10 minutes
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea



_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Thu Nov 08 06:26:15 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iq5WZ-0002aH-KC
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 08 Nov 2007 06:26:15 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iq5WV-0001cX-Jb
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 08 Nov 2007 06:26:15 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id A2D8B80AB5;
	Thu,  8 Nov 2007 03:27:05 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 541C480A62
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:27:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 9CD1014220E
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:26:09 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.636
X-Spam-Level: 
X-Spam-Status: No, score=-1.636 tagged_above=-50 required=4 tests=[AWL=0.763, 
	BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id zQ+rfNmVsABt for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:26:04 -0800 (PST)
Received: from mgw-ext11.nokia.com (smtp.nokia.com [131.228.20.170])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id AB25D142207
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:26:03 -0800 (PST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA8BPhxh011094; Thu, 8 Nov 2007 13:25:44 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Nov 2007 13:25:20 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 13:25:19 +0200
Received: from [172.21.41.182] (esdhcp041182.research.nokia.com
	[172.21.41.182])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA8BPFE2001199; Thu, 8 Nov 2007 13:25:16 +0200
Subject: Re: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request
From: Aki Niemi <aki.niemi@nokia.com>
To: ext Cyrus Daboo <cyrus@daboo.name>
In-Reply-To: <9605B38742013AA84E9B408F@ninevah.local>
References: <454E6755.9040809@oracle.com>
	<9605B38742013AA84E9B408F@ninevah.local>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Thu, 08 Nov 2007 13:25:21 +0200
Message-Id: <1194521121.5053.5.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Nov 2007 11:25:19.0808 (UTC)
	FILETIME=[0B790400:01C821FA]
X-Nokia-AV: Clean
Cc: Calsify WG <ietf-calsify@osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

[as chair]

Folks,

We need to resolve this issue, which to my knowledge is still pending.
Option a) below would require a change in rfc2445bis, which is almost
done now, so your input is needed *now*.

Cheers
Aki


ma, 2006-11-06 kello 07:25 -0800, ext Cyrus Daboo kirjoitti:
> Hi Bernard,
> 
> --On November 5, 2006 5:36:05 PM -0500 Bernard Desruisseaux 
> <bernard.desruisseaux@oracle.com> wrote:
> 
> >  > In a "VFREEBUSY" calendar component the property may be
> >  > used to specify the interval of free time being requested.
> >
> > Yet, section 3.3.2 REQUEST of RFC 2446 (iTIP) specifies that
> > the DURATION property is not allowed in a VFREEBUSY request.
> >
> > I see three options:
> >
> > a) Remove statement from iCalendar to be in sync with iTIP;
> >
> > b) Change iTIP to allow the DURATION property in a VFREEBUSY
> >     request and define the semantic as specified in iCalendar.
> >
> > c) Status quo.
> 
> We should rule out (c) as it represents an inconsistency between the two 
> specs. Note that 2445 does not clearly define what it means to have 
> DURATION present. e.g. is it allowed for the responder to only return free 
> times slots that are equal to or larger than the DURATION, or should they 
> still return the full list? If we can clearly specify the behavior then I 
> think (b) is reasonable, otherwise we have to do (a).
> 

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Thu Nov 08 06:32:52 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iq5cy-0001bg-RI
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 08 Nov 2007 06:32:52 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iq5cv-0001po-QU
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 08 Nov 2007 06:32:52 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 8216B80ABF;
	Thu,  8 Nov 2007 03:33:43 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 50C0E80AB5
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:33:41 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 97FA8142210
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:32:46 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.642
X-Spam-Level: 
X-Spam-Status: No, score=-1.642 tagged_above=-50 required=4 tests=[AWL=0.757, 
	BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id NzQ11pmD70Y1 for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:32:40 -0800 (PST)
Received: from mgw-ext14.nokia.com (smtp.nokia.com [131.228.20.173])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 36160142207
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 03:32:39 -0800 (PST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA8BWSTg022418; Thu, 8 Nov 2007 13:32:35 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Nov 2007 13:32:08 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 13:32:08 +0200
Received: from [172.21.41.182] (esdhcp041182.research.nokia.com
	[172.21.41.182])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA8BW65L007629; Thu, 8 Nov 2007 13:32:06 +0200
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify@osafoundation.org, Eliot Lear <lear@cisco.com>
Organization: Nokia-TP-MSW/Helsinki
Date: Thu, 08 Nov 2007 13:32:12 +0200
Message-Id: <1194521532.5053.7.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
X-OriginalArrivalTime: 08 Nov 2007 11:32:08.0308 (UTC)
	FILETIME=[FEF52B40:01C821FA]
X-Nokia-AV: Clean
Subject: [Ietf-calsify] Calsify WG jabber chat
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1331572644=="
Mime-version: 1.0
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17

--===============1331572644==
Content-Type: text/calendar; name=calendar.ics; charset=utf-8; METHOD=REQUEST
Content-Transfer-Encoding: 7bit

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:/softwarestudio.org/Tzfile/Europe/Helsinki
X-LIC-LOCATION:Europe/Helsinki
BEGIN:STANDARD
TZNAME:EET
DTSTART:19701026T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-2SU;BYMONTH=10
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
TZNAME:EEST
DTSTART:19700330T040000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:20071023T072226Z-6691-1000-1-1@scotty
DTSTAMP:20071108T113212Z
DTSTART;TZID=/softwarestudio.org/Tzfile/Europe/Helsinki:20071024T163000
DTEND;TZID=/softwarestudio.org/Tzfile/Europe/Helsinki:20071024T173000
TRANSP:OPAQUE
SEQUENCE:3
SUMMARY:Calsify WG jabber chat
LOCATION:xmpp:calsify@jabber.ietf.org
CLASS:PUBLIC
ORGANIZER;CN=Aki Niemi:MAILTO:aki.niemi@nokia.com
X-MICROSOFT-CDO-REPLYTIME:20071031T150125Z
CREATED:20071031T150125
LAST-MODIFIED:20071031T150125
RECURRENCE-ID;TZID=/softwarestudio.org/Tzfile/Europe/Helsinki:
 20071024T163000
DESCRIPTION:Weekly jabber chat for the Calsify WG. Template agenda: going 
 through and closing issues on the WG issue tracker:\n\nhttp:
 //www.ofcourseimright.com/cgi-bin/roundup/calsify\n
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=CHAIR;PARTSTAT=ACCEPTED;RSVP=TRUE;CN=Aki 
 Niemi;LANGUAGE=en:MAILTO:aki.niemi@nokia.com
ATTENDEE;CUTYPE=GROUP;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;LANGUAGE=en:MAILTO:ietf-calsify@osafoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=CHAIR;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;
 CN=Eliot Lear;LANGUAGE=en:MAILTO:lear@cisco.com
EXDATE;VALUE=DATE:20071205
EXDATE;VALUE=DATE:20071114
RRULE:FREQ=WEEKLY;UNTIL=20071231T143000Z;INTERVAL=1;BYDAY=WE
END:VEVENT
END:VCALENDAR


--===============1331572644==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify

--===============1331572644==--



From ietf-calsify-bounces@osafoundation.org Thu Nov 08 07:13:37 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iq6GP-0004CC-Gj
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 08 Nov 2007 07:13:37 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iq6GL-0002xb-LI
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 08 Nov 2007 07:13:37 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 5297D80A88;
	Thu,  8 Nov 2007 04:14:27 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 3967C80A62
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 04:14:25 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 82F1A14220D
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 04:13:30 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.648
X-Spam-Level: 
X-Spam-Status: No, score=-1.648 tagged_above=-50 required=4 tests=[AWL=0.751, 
	BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 9LxTI663Fr4P for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 04:13:25 -0800 (PST)
Received: from mgw-ext12.nokia.com (smtp.nokia.com [131.228.20.171])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id AE4CD142207
	for <ietf-calsify@osafoundation.org>;
	Thu,  8 Nov 2007 04:13:24 -0800 (PST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA8CCpkR004900; Thu, 8 Nov 2007 14:13:17 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Nov 2007 14:12:40 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 14:12:39 +0200
Received: from [172.21.41.182] (esdhcp041182.research.nokia.com
	[172.21.41.182])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	lA8CCch1010325; Thu, 8 Nov 2007 14:12:38 +0200
Subject: Next week's jabber chat. (was: Re: [Ietf-calsify] Calsify WG
	jabber chat)
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify@osafoundation.org
In-Reply-To: <1194521532.5053.7.camel@scotty>
References: <1194521532.5053.7.camel@scotty>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Thu, 08 Nov 2007 14:12:44 +0200
Message-Id: <1194523964.5053.9.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Nov 2007 12:12:39.0730 (UTC)
	FILETIME=[A832B920:01C82200]
X-Nokia-AV: Clean
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

Note that next week's jabber chat has been canceled. We will chat again
on Nov 21st, focusing on preparations for IETF70.

Cheers,
Aki


to, 2007-11-08 kello 13:32 +0200, ext Aki Niemi kirjoitti:
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Sat Nov 10 08:54:34 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IqqnC-0004j2-8g
	for calsify-archive-Feit0ahl@lists.ietf.org; Sat, 10 Nov 2007 08:54:34 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iqqn7-0000RY-6Q
	for calsify-archive-Feit0ahl@lists.ietf.org; Sat, 10 Nov 2007 08:54:34 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 4303F80A1D;
	Sat, 10 Nov 2007 05:55:23 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id BCA6D808CF
	for <ietf-calsify@osafoundation.org>;
	Sat, 10 Nov 2007 05:55:21 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 127DB142210
	for <ietf-calsify@osafoundation.org>;
	Sat, 10 Nov 2007 05:54:27 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: 0.168
X-Spam-Level: 
X-Spam-Status: No, score=0.168 tagged_above=-50 required=4 tests=[AWL=-0.334, 
	BAYES_00=-2.599, DNS_FROM_RFC_POST=1.708,
	MSGID_FROM_MTA_ID=1.393]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id hiPZWq-Y9FBC for <ietf-calsify@osafoundation.org>;
	Sat, 10 Nov 2007 05:54:21 -0800 (PST)
Received: from QMTA10.westchester.pa.mail.comcast.net
	(qmta10.westchester.pa.mail.comcast.net [76.96.62.17])
	by laweleka.osafoundation.org (Postfix) with ESMTP id D007B1421FF
	for <ietf-calsify@osafoundation.org>;
	Sat, 10 Nov 2007 05:54:20 -0800 (PST)
Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52])
	by QMTA10.westchester.pa.mail.comcast.net with smtp
	id B0QF1Y00617dt5G0004i00; Sat, 10 Nov 2007 13:54:20 +0000
Received: from THare ([71.203.100.120])
	by OMTA13.westchester.pa.mail.comcast.net with comcast
	id B1uE1Y0022brFRz0000000; Sat, 10 Nov 2007 13:54:19 +0000
X-Authority-Analysis: v=1.0 c=1 a=PFsjAnyDAAAA:8 a=vhZX8rZXDXiGRdjmUM4A:9
	a=wkb5aLYAyd-8kW5hZJYA:7 a=MUqRm-V3JLOFch614JiaTsDlRB4A:4
	a=YewFc9KQ5U8A:10 a=7DSvI1NPTFQA:10 a=Cq1YcKPHAxQA:10
From: "Tim Hare" <TimHare@comcast.net>
To: "'Calsify WG'" <ietf-calsify@osafoundation.org>
Subject: RE: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request
Date: Sat, 10 Nov 2007 08:54:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-reply-to: <1194521121.5053.5.camel@scotty>
Thread-Index: Acgh+ivGxuKSmMesT32Kugp2Uxd/RwBptNCw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Message-Id: <20071110135420.D007B1421FF@laweleka.osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1

DURATION is used in VFREEBUSY requests in the sense of "search for a
half-hour block of free time", at least according to my interpretation of
this paragraph in 3.6.4 of draft-ietf-calsify-rfc2445bis-07.txt

"When present in a "VFREEBUSY" calendar component, the "DTSTART"
      and "DTEND" properties SHOULD be specified prior to any "FREEBUSY"
      properties.  In a free time request, these properties can be used
      in combination with the "DURATION" property to represent a request
      for a duration of free time within a specified window of time." 

Since this is probably a fairly common use case when scheduling meetings,
the only choice that makes sense, in my opinion, is (b) .

To eliminate perceived vagueness, in the second sentence of the paragraph
from 3.6.4 we could change the wording to read:

"In a free tine request, the DTSTART, DTEND, and DURATION properties can be
used to represent a request to find a period of free time, of length
DURATION, within the period of time bounded inclusively by DTSTART and
DTEND."

It might also help to have one of the examples show that kind of request.

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: ietf-calsify-bounces@osafoundation.org
[mailto:ietf-calsify-bounces@osafoundation.org] On Behalf Of Aki Niemi
Sent: Thursday, November 08, 2007 6:25 AM
To: ext Cyrus Daboo
Cc: Calsify WG
Subject: Re: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request

[as chair]

Folks,

We need to resolve this issue, which to my knowledge is still pending.
Option a) below would require a change in rfc2445bis, which is almost done
now, so your input is needed *now*.

Cheers
Aki


ma, 2006-11-06 kello 07:25 -0800, ext Cyrus Daboo kirjoitti:
> Hi Bernard,
> 
> --On November 5, 2006 5:36:05 PM -0500 Bernard Desruisseaux 
> <bernard.desruisseaux@oracle.com> wrote:
> 
> >  > In a "VFREEBUSY" calendar component the property may be  > used 
> > to specify the interval of free time being requested.
> >
> > Yet, section 3.3.2 REQUEST of RFC 2446 (iTIP) specifies that the 
> > DURATION property is not allowed in a VFREEBUSY request.
> >
> > I see three options:
> >
> > a) Remove statement from iCalendar to be in sync with iTIP;
> >
> > b) Change iTIP to allow the DURATION property in a VFREEBUSY
> >     request and define the semantic as specified in iCalendar.
> >
> > c) Status quo.
> 
> We should rule out (c) as it represents an inconsistency between the 
> two specs. Note that 2445 does not clearly define what it means to 
> have DURATION present. e.g. is it allowed for the responder to only 
> return free times slots that are equal to or larger than the DURATION, 
> or should they still return the full list? If we can clearly specify 
> the behavior then I think (b) is reasonable, otherwise we have to do (a).
> 

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify


_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 14 00:06:37 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsAST-0001i8-IS
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 00:06:37 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IsASO-00057j-IS
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 00:06:37 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id BD36680BD6;
	Tue, 13 Nov 2007 21:07:25 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id ACE2D808DE
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 21:07:23 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 12D10142202
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 21:06:29 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.309
X-Spam-Level: 
X-Spam-Status: No, score=-2.309 tagged_above=-50 required=4 tests=[AWL=0.289, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id KWjla6ArBFgd for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 21:06:22 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id AE8021421F6
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 21:06:22 -0800 (PST)
Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212])
	by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id
	lAE56KWO027337
	for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 23:06:20 -0600
Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150])
	by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id
	lADA1QKZ000569
	for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:06:19 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-106-55.vpn.oracle.com by
	acsmt350.oracle.com
	with ESMTP id 3364192171195016679; Tue, 13 Nov 2007 21:04:39 -0800
Message-ID: <473A81E6.4030002@oracle.com>
Date: Wed, 14 Nov 2007 00:04:38 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf-calsify@osafoundation.org
Subject: Section 4.8.7.4 Sequence Number [Re: [Ietf-calsify] Re: Ietf-calsify
	Digest, Vol 38, Issue 10]
References: <20070918190006.D4825802A3@leilani.osafoundation.org>	<46FD4C1D.1060801@sun.com>
	<E5A8403BFDBC7B88DB846818@caldav.corp.apple.com>
In-Reply-To: <E5A8403BFDBC7B88DB846818@caldav.corp.apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

Do we want to remove the text in section 4.8.7.4 Sequence Number of
RFC 2445 that specifies when the sequence number MUST be incremented
as Cyrus was "tempted to suggest"?

Cheers,
Bernard

Cyrus Daboo wrote:
> Hi Ciny,
> 
> --On September 28, 2007 11:46:53 AM -0700 Ciny Joy <Ciny.Joy@Sun.COM> 
> wrote:
> 
>>     So was their a conclusion on the SEQUENCE, DTSTAMP discussion? I am
>> especially interested in knowing which fields should be used to determine
>> the latest update received in iMIP. Also, is there a proposal to
>> standardize when these fields should be modified?
> 
> I am crafting a response to all the discussion that took place on this 
> recently.
> 
> My conclusions are the following:
> 
> 1) We do need SEQUENCE to properly allow an organizer to match up 
> responses from attendees with the latest revisions sent out by the 
> organizer.
> 
> 2) Clarify that SEQUENCE is not meant to be any kind of indicator to the 
> client that a response is needed. RSVP=TRUE must be used instead.
> 
> 3) Clarify that clients must determine for themselves what constitutes a 
> significant change to an event that would cause a new accept/decline 
> prompt to be presented to a user. Clients may treat a change in SEQUENCE 
> number as always causing a prompt, but should not rely solely on a 
> change of SEQUENCE number.
> 
> 4) Clarify under what circumstances SEQUENCE should change. There is 
> currently some text on that in 2445bis, but I am tempted to suggest that 
> really belongs in 2446bis in a single section dealing with SEQUENCE 
> issues. The text here would list some properties for which changes MUST 
> result in a sequence change, and others that MAY result in a change 
> depending on the exact nature of the property change. I don't think we 
> can go further than that.
> 
> I am working on putting together some text on this so that we can seek 
> consensus on these points.
> 

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 14 01:21:50 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsBdG-0006RK-2D
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 01:21:50 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IsBdA-0006kl-GV
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 01:21:49 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 1FF8C80B78;
	Tue, 13 Nov 2007 22:22:37 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 635D2808A1
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:22:35 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id BD688142202
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:21:40 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-50 required=4 tests=[AWL=0.286, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id x10YVNeTk6L1 for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:21:35 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 185A81421FF
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:21:34 -0800 (PST)
Received: from rgmgw2.us.oracle.com (rgmgw2.us.oracle.com [138.1.186.111])
	by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id
	lAE6LRqK023297; Wed, 14 Nov 2007 00:21:27 -0600
Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150])
	by rgmgw2.us.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id
	lAE6LOrB014004; Tue, 13 Nov 2007 23:21:24 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-106-55.vpn.oracle.com by
	acsmt350.oracle.com
	with ESMTP id 3364222501195021207; Tue, 13 Nov 2007 22:20:07 -0800
Message-ID: <473A9396.9050600@oracle.com>
Date: Wed, 14 Nov 2007 01:20:06 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <20071106200005.569D080A03@leilani.osafoundation.org>
	<4730E760.4090309@sun.com>
In-Reply-To: <4730E760.4090309@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17

Hi Ciny,

Ciny Joy wrote:
> 
>>
>>>
>>> This time I would like to suggest a solution for the case where
>>> an organizer changes all future recurrence instances of a recurring
>>> calendar component:
>>>
>>> 1- Specify RDATE properties for all past recurrence instances
>>>   and define exception components for them if needed.
> How do you define "if needed"?

A past recurrence instance identical to the recurrence instance
defined by DTSTART, except for its scheduled time, would not need
a separate component.

> 
>>> The
>>>   number of past recurrence instances is always finite...
>>>
>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>
>>> 3- Set DTSTART to the first recurrence instance to which you
>>>   want the change to apply.
>>>   
> So is original DTSTART lost completely?

The recurrence instance previously defined by DTSTART would become
a simple recurrence instance defined by an RDATE property. You
wouldn't be able to figure out what was the original DTSTART.

 > Doesn't this go against the
> statement, "However, in such cases the original "DTSTART" date MUST 
> still be maintained by the calendaring and scheduling system because the 
> original "DTSTART" value has inherent usage dependencies by other 
> properties such as the "RECURRENCE-ID"."

I would think that what really matter is that the set of RECURRENCE-ID
is maintained.

> If not, is there a standard way of maintaining it?
> Also, in multiple places it is stated "The "DTSTART" property defines 
> the first instance in the recurrence set". Will that be modified?

That would clearly need to be modified.

Cheers,
Bernard
> 
> Thanks,
> Ciny
> 
>>> The only issue here is that we need to clarify that RDATE can
>>> specify a value less than the value specified by DTSTART.
>>>
>>> Cheers,
>>> Bernard
>>>   
> 
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
> 

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 14 01:33:54 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsBow-0005Tj-VB
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 01:33:54 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IsBor-0006zU-Pg
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 01:33:54 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 154AD80B78;
	Tue, 13 Nov 2007 22:34:42 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 1B7E880847
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:34:40 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 75184142202
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:33:45 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.315
X-Spam-Level: 
X-Spam-Status: No, score=-2.315 tagged_above=-50 required=4 tests=[AWL=0.283, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id vXSxKsXx5C6p for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:33:39 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id CA82E1421FF
	for <ietf-calsify@osafoundation.org>;
	Tue, 13 Nov 2007 22:33:39 -0800 (PST)
Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212])
	by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id
	lAE6Xb0x019791; Tue, 13 Nov 2007 23:33:38 -0700
Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151])
	by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id
	lAE6382G018364; Tue, 13 Nov 2007 23:33:36 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-106-55.vpn.oracle.com by
	acsmt350.oracle.com
	with ESMTP id 3364228811195022016; Tue, 13 Nov 2007 22:33:36 -0800
Message-ID: <473A96BE.6010209@oracle.com>
Date: Wed, 14 Nov 2007 01:33:34 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew N Dowden <andrew_dowden@softdesign.net.nz>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <471612F8.9020306@cisco.com> <47302DB0.1050207@cisco.com>
	<47314658.4010502@softdesign.net.nz>
In-Reply-To: <47314658.4010502@softdesign.net.nz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify <ietf-calsify@osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

Hi Andrew,

Andrew N Dowden wrote:
> Eliot Lear wrote:
>>> This time I would like to suggest a solution for the case where
>>> an organizer changes all future recurrence instances of a recurring
>>> calendar component:
>>>
>>> 1- Specify RDATE properties for all past recurrence instances
>>>    and define exception components for them if needed. The
>>>    number of past recurrence instances is always finite...
>>>
>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>
>>> 3- Set DTSTART to the first recurrence instance to which you
>>>    want the change to apply.
>>>
>>> The only issue here is that we need to clarify that RDATE can
>>> specify a value less than the value specified by DTSTART.
>>>     
> Is there anything wrong with? :
> 
> 1- Specify RDATE properties for all past recurrence instances,
>     while excluding those removed by EXDATE properties..
>    ( The number of past recurrence instances is always finite. )
> 
> 2- Remove any RRULE and EXDATE properties.

We're trying to address an issue with *unbounded* recurring
calendar components here (i.e., RRULE doesn't specify the
COUNT nor the UNTIL rule parts).

Removing the RRULE property would clearly make the recurring
calendar component bounded which is not want we want.

Cheers,
Bernard

> 
> 3- Set DTSTART to match the first RDATE property.
> 
_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 14 13:59:24 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsNSO-0000K8-Nx
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 13:59:24 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IsNSJ-0003Sb-Mn
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 14 Nov 2007 13:59:24 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 05CC180C51;
	Wed, 14 Nov 2007 10:59:19 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 7782780176
	for <ietf-calsify@osafoundation.org>;
	Wed, 14 Nov 2007 10:59:16 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id EF340142204
	for <ietf-calsify@osafoundation.org>;
	Wed, 14 Nov 2007 10:59:16 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-50 required=4 tests=[AWL=0.650, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id X-oZhoWVI4lX for <ietf-calsify@osafoundation.org>;
	Wed, 14 Nov 2007 10:59:11 -0800 (PST)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 54EAD1421FD
	for <ietf-calsify@osafoundation.org>;
	Wed, 14 Nov 2007 10:59:11 -0800 (PST)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	lAEIx0Qf018598 for <ietf-calsify@osafoundation.org>;
	Wed, 14 Nov 2007 10:59:10 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	id <0JRI00D01EWZ0500@fe-sfbay-09.sun.com>
	(original mail from Ciny.Joy@Sun.COM) for
	ietf-calsify@osafoundation.org; Wed, 14 Nov 2007 10:59:00 -0800 (PST)
Received: from [129.150.19.172] by fe-sfbay-09.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	with ESMTPSA id <0JRI00AROFEBECG0@fe-sfbay-09.sun.com>; Wed,
	14 Nov 2007 10:59:00 -0800 (PST)
Date: Wed, 14 Nov 2007 10:59:01 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
In-reply-to: <473A9396.9050600@oracle.com>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
Message-id: <473B4575.5030806@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <20071106200005.569D080A03@leilani.osafoundation.org>
	<4730E760.4090309@sun.com> <473A9396.9050600@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976

Thanks Bernard. Just one question below...

Bernard Desruisseaux wrote:
> Hi Ciny,
>
> Ciny Joy wrote:
>>
>>>
>>>>
>>>> This time I would like to suggest a solution for the case where
>>>> an organizer changes all future recurrence instances of a recurring
>>>> calendar component:
>>>>
>>>> 1- Specify RDATE properties for all past recurrence instances
>>>>   and define exception components for them if needed.
>> How do you define "if needed"?
>
> A past recurrence instance identical to the recurrence instance
> defined by DTSTART, except for its scheduled time, would not need
> a separate component.
If we are making a "This & Future" change and changing dtstart to the 
first instance of the newly created series, won't all past instances be 
different from DTSTART? Or am I understanding this wrong?

Thanks,
Ciny
>
>>
>>>> The
>>>>   number of past recurrence instances is always finite...
>>>>
>>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>>
>>>> 3- Set DTSTART to the first recurrence instance to which you
>>>>   want the change to apply.
>>>>   
>> So is original DTSTART lost completely?
>
> The recurrence instance previously defined by DTSTART would become
> a simple recurrence instance defined by an RDATE property. You
> wouldn't be able to figure out what was the original DTSTART.
>
> > Doesn't this go against the
>> statement, "However, in such cases the original "DTSTART" date MUST 
>> still be maintained by the calendaring and scheduling system because 
>> the original "DTSTART" value has inherent usage dependencies by other 
>> properties such as the "RECURRENCE-ID"."
>
> I would think that what really matter is that the set of RECURRENCE-ID
> is maintained.
>
>> If not, is there a standard way of maintaining it?
>> Also, in multiple places it is stated "The "DTSTART" property defines 
>> the first instance in the recurrence set". Will that be modified?
>
> That would clearly need to be modified.
>
> Cheers,
> Bernard
>>
>> Thanks,
>> Ciny
>>
>>>> The only issue here is that we need to clarify that RDATE can
>>>> specify a value less than the value specified by DTSTART.
>>>>
>>>> Cheers,
>>>> Bernard
>>>>   
>>
>> _______________________________________________
>> Ietf-calsify mailing list
>> Ietf-calsify@osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>>
>

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Thu Nov 15 15:05:10 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iskxa-0006Ow-4P
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 15 Nov 2007 15:05:10 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IskxW-0004uA-PJ
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 15 Nov 2007 15:05:10 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 9CE2180CE8;
	Thu, 15 Nov 2007 12:05:05 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id C415F80CD5
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 12:05:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 494CA142207
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 12:05:05 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.318
X-Spam-Level: 
X-Spam-Status: No, score=-2.318 tagged_above=-50 required=4 tests=[AWL=0.280, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id Vhqio9mVTqMh for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 12:04:59 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 5715E1421F6
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 12:04:59 -0800 (PST)
Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213])
	by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id
	lAFK4uYY010252; Thu, 15 Nov 2007 14:04:56 -0600
Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150])
	by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id
	lAELM3D5026333; Thu, 15 Nov 2007 13:04:55 -0700
Received: from bdesruis-ca.ca.oracle.com by acsmt350.oracle.com
	with ESMTP id 3368948591195157041; Thu, 15 Nov 2007 12:04:01 -0800
Message-ID: <473CA62F.6080302@oracle.com>
Date: Thu, 15 Nov 2007 15:03:59 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <20071106200005.569D080A03@leilani.osafoundation.org>
	<4730E760.4090309@sun.com> <473A9396.9050600@oracle.com>
	<473B4575.5030806@sun.com>
In-Reply-To: <473B4575.5030806@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e

Hi Ciny,

Ciny Joy wrote:
> Thanks Bernard. Just one question below...
> 
> Bernard Desruisseaux wrote:
>> Hi Ciny,
>>
>> Ciny Joy wrote:
>>>
>>>>
>>>>>
>>>>> This time I would like to suggest a solution for the case where
>>>>> an organizer changes all future recurrence instances of a recurring
>>>>> calendar component:
>>>>>
>>>>> 1- Specify RDATE properties for all past recurrence instances
>>>>>   and define exception components for them if needed.
>>> How do you define "if needed"?
>>
>> A past recurrence instance identical to the recurrence instance
>> defined by DTSTART, except for its scheduled time, would not need
>> a separate component.
> If we are making a "This & Future" change and changing dtstart to the 
> first instance of the newly created series, won't all past instances be 
> different from DTSTART? Or am I understanding this wrong?

Here's a simple example where separate components would not be
needed for past recurrence instances:

A.1 Schedule a daily event at 9:00 AM forever starting on Nov. 12.

     BEGIN:VEVENT
     DTSTART;TZID=America/Montreal:20071112T090000
     DTEND;TZID=America/Montreal:20071112T100000
     RRULE:FREQ=DAILY
     ...
     END:VEVENT

A.2 Reschedule 4th recurrence instance (Nov. 15) as well as
     all future recurrence instances at 10:00 AM

     BEGIN:VEVENT
     RDATE;TZID=America/Montreal:20071112T090000/20071112T100000
     RDATE;TZID=America/Montreal:20071113T090000/20071113T100000
     RDATE;TZID=America/Montreal:20071114T090000/20071114T100000
     DTSTART;TZID=America/Montreal:20071115T100000
     DTEND;TZID=America/Montreal:20071115T110000
     RRULE:FREQ=DAILY;COUNT=5
     ...
     END:VEVENT

Now let's look at a slightly more complex example:

B.1 Schedule a daily event at 9:00 AM forever starting on Nov. 12.

     BEGIN:VEVENT
     DTSTART;TZID=America/Montreal:20071112T090000
     DTEND;TZID=America/Montreal:20071112T100000
     RRULE:FREQ=DAILY
     ...
     END:VEVENT

B.2 Reschedule 2nd recurrence instance (Nov. 13) at 10:00 AM.

     BEGIN:VEVENT
     DTSTART;TZID=America/Montreal:20071112T090000
     DTEND;TZID=America/Montreal:20071112T100000
     RRULE:FREQ=DAILY;COUNT=5
     ...
     END:VEVENT
     BEGIN:VEVENT
     RECURRENCE-ID;TZID=America/Montreal:20071113T090000
     DTSTART;TZID=America/Montreal:20071113T100000
     DTEND;TZID=America/Montreal:20071113T110000
     ...
     END:VEVENT

B.3 Reschedule 4th recurrence instance (Nov. 15) as well as
     all future recurrence instances at 10:00 AM

     BEGIN:VEVENT
     RDATE;TZID=America/Montreal:20071112T090000/20071112T100000
     RDATE;TZID=America/Montreal:20071113T090000/20071113T100000
     RDATE;TZID=America/Montreal:20071114T090000/20071114T100000
     DTSTART;TZID=America/Montreal:20071115T100000
     DTEND;TZID=America/Montreal:20071115T110000
     RRULE:FREQ=DAILY;COUNT=5
     ...
     END:VEVENT
     BEGIN:VEVENT
     RECURRENCE-ID;TZID=America/Montreal:20071113T090000
     DTSTART;TZID=America/Montreal:20071113T100000
     DTEND;TZID=America/Montreal:20071113T110000
     ...
     END:VEVENT

Here you'll notice that the RDATE for the 2nd recurrence instance
specifies the original scheduled time of this instance in order to
preserve the original RECURRENCE-ID.


The real concern here is that starting from the 4th recurrence
instance, we have lost the original RECURRENCE-IDs. We need to
think carefully about how bad that really is.  What are our
options?

1- Keep the RANGE parameter and address its issues.  Hummm...

2- Remove the RANGE parameter, and recommend to move DTSTART
    to the future instance that corresponds to the new recurrence
    pattern for all future instances (current proposal) and
    live with the fact that the RECURRENCE-ID of all those
    instances will have changed.

3- Remove the RANGE parameter, and recommend to split the
    calendar component in two. One calendar component with
    the original RRULE modified to specify a COUNT or UNTIL
    rule part, and a second calendar component that specify
    a new RRULE with no COUNT or UNTIL rule part.

4- Something we haven't thought about yet...

Not clear which is the best (or less worse) solution.
Perhaps it depends on the situation.  When an Organizer
decide to reschedule all future recurrence instances
option (3) might be the way to go.  On the other hand,
when an Attendee decide to decline all future recurrence
instances, option (2) might be the only way to go.
I'm wondering how many people bothered to read this email
that far. Send me a private email if you did. Just curious.
Sorry.

Cheers,
Bernard


> 
> Thanks,
> Ciny
>>
>>>
>>>>> The
>>>>>   number of past recurrence instances is always finite...
>>>>>
>>>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>>>
>>>>> 3- Set DTSTART to the first recurrence instance to which you
>>>>>   want the change to apply.
>>>>>   
>>> So is original DTSTART lost completely?
>>
>> The recurrence instance previously defined by DTSTART would become
>> a simple recurrence instance defined by an RDATE property. You
>> wouldn't be able to figure out what was the original DTSTART.
>>
>> > Doesn't this go against the
>>> statement, "However, in such cases the original "DTSTART" date MUST 
>>> still be maintained by the calendaring and scheduling system because 
>>> the original "DTSTART" value has inherent usage dependencies by other 
>>> properties such as the "RECURRENCE-ID"."
>>
>> I would think that what really matter is that the set of RECURRENCE-ID
>> is maintained.
>>
>>> If not, is there a standard way of maintaining it?
>>> Also, in multiple places it is stated "The "DTSTART" property defines 
>>> the first instance in the recurrence set". Will that be modified?
>>
>> That would clearly need to be modified.
>>
>> Cheers,
>> Bernard
>>>
>>> Thanks,
>>> Ciny
>>>
>>>>> The only issue here is that we need to clarify that RDATE can
>>>>> specify a value less than the value specified by DTSTART.
>>>>>
>>>>> Cheers,
>>>>> Bernard
>>>>>   
>>>
>>> _______________________________________________
>>> Ietf-calsify mailing list
>>> Ietf-calsify@osafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>>>
>>
> 
> 

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Thu Nov 15 17:03:41 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsmoH-0004rD-Qm
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 15 Nov 2007 17:03:41 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IsmoD-0008Ta-W2
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 15 Nov 2007 17:03:41 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id C9E2080CDA;
	Thu, 15 Nov 2007 14:03:36 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id F332580CC4
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 14:03:34 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 78EDF14220D
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 14:03:35 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.462
X-Spam-Level: 
X-Spam-Status: No, score=-2.462 tagged_above=-50 required=4 tests=[AWL=0.137, 
	BAYES_00=-2.599]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id yvnYBnEhn3jy for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 14:03:30 -0800 (PST)
Received: from mulberrymail.com (piper.mulberrymail.com [151.201.22.177])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id B6BD91421FC
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 14:03:25 -0800 (PST)
Received: from caldav.corp.apple.com ([17.101.32.44]) (authenticated bits=0)
	by mulberrymail.com (8.13.6/8.13.6) with ESMTP id lAFM1s6l008376
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 15 Nov 2007 17:01:59 -0500
Date: Thu, 15 Nov 2007 17:01:49 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>,
	Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
Message-ID: <1C603AE21E804344D7EA043C@caldav.corp.apple.com>
In-Reply-To: <473CA62F.6080302@oracle.com>
References: <20071106200005.569D080A03@leilani.osafoundation.org>
	<4730E760.4090309@sun.com>
	<473A9396.9050600@oracle.com>	<473B4575.5030806@sun.com>
	<473CA62F.6080302@oracle.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Hi Bernard,

--On November 15, 2007 3:03:59 PM -0500 Bernard Desruisseaux 
<bernard.desruisseaux@oracle.com> wrote:

> The real concern here is that starting from the 4th recurrence
> instance, we have lost the original RECURRENCE-IDs. We need to
> think carefully about how bad that really is.  What are our
> options?
>
> 1- Keep the RANGE parameter and address its issues.  Hummm...
>
> 2- Remove the RANGE parameter, and recommend to move DTSTART
>     to the future instance that corresponds to the new recurrence
>     pattern for all future instances (current proposal) and
>     live with the fact that the RECURRENCE-ID of all those
>     instances will have changed.
>
> 3- Remove the RANGE parameter, and recommend to split the
>     calendar component in two. One calendar component with
>     the original RRULE modified to specify a COUNT or UNTIL
>     rule part, and a second calendar component that specify
>     a new RRULE with no COUNT or UNTIL rule part.
>
> 4- Something we haven't thought about yet...

> On the other hand, when an Attendee decide to decline all future
> recurrence instances, option (2) might be the only way to go.

Actually I disagree. In that case there is a finite set of instances that 
the attendee has accepted and an infinite set that is declined. So the 
master component is marked as declined, and then overridden components for 
the finite set added with accepted status for that attendee. None of that 
involves either (1), (2) or (3).

I'm still not sure what the best overall solution for this is though. I am 
concerned about the loss of RECURRENCE-ID sync caused by (2). I think the 
rule should be if you have to do something that causes the recurrence-ids 
to change then you have to split the events. So that would cover the case 
of changing the time of all future instances, or changing the pattern of 
the rule, but not of changing the location of all future instances. For the 
later you would change the location of the master, then override all 
components upto the actual point of change and use the old location in 
those. Same would apply to attendee state etc. However, if we take that 
approach, it actually eliminates some of the problems with RANGE= and makes 
that more viable.

-- 
Cyrus Daboo

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Thu Nov 15 19:10:54 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsonO-0003bS-AH
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 15 Nov 2007 19:10:54 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IsonH-0007Ul-7u
	for calsify-archive-Feit0ahl@lists.ietf.org; Thu, 15 Nov 2007 19:10:54 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 1814080CE7;
	Thu, 15 Nov 2007 16:10:46 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 9526980CCB
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 16:10:44 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 1A973142215
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 16:10:45 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.165
X-Spam-Level: 
X-Spam-Status: No, score=-2.165 tagged_above=-50 required=4 tests=[AWL=0.433, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id xu1xJrx+a6Bp for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 16:10:39 -0800 (PST)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 44BEF14220E
	for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 16:10:39 -0800 (PST)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	lAG0Acn8022501 for <ietf-calsify@osafoundation.org>;
	Thu, 15 Nov 2007 16:10:38 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	id <0JRK00501OFJYH00@fe-sfbay-09.sun.com>
	(original mail from Ciny.Joy@Sun.COM) for
	ietf-calsify@osafoundation.org; Thu, 15 Nov 2007 16:10:38 -0800 (PST)
Received: from [129.150.18.236] by fe-sfbay-09.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	with ESMTPSA id <0JRK0048NOHOAEE0@fe-sfbay-09.sun.com>; Thu,
	15 Nov 2007 16:10:37 -0800 (PST)
Date: Thu, 15 Nov 2007 16:10:37 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
In-reply-to: <473CDA4A.8020505@oracle.com>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
Message-id: <473CDFFD.7050801@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <20071106200005.569D080A03@leilani.osafoundation.org>
	<4730E760.4090309@sun.com> <473A9396.9050600@oracle.com>
	<473B4575.5030806@sun.com> <473CA62F.6080302@oracle.com>
	<473CCF36.5040000@sun.com> <473CDA4A.8020505@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0

Thanks again Bernard.
Sorry about not cc'ing the list earlier. It was an accidental omission.
I usually get the digest of the mailing list emails. So haven't seen 
Cyrus's reply yet. But glad to know I wasn't completely off track.
Looking forward to more discussions that might provide a solution to the 
preserving of future exceptions on a time change issue.

Thanks,
Ciny

Bernard Desruisseaux wrote:
> Hi Ciny,
>
> I'm only replying to you since you didn't CC the list on your message.
> Not sure why though!
>
> Ciny Joy wrote:
>> Bernard Desruisseaux wrote:
>>>
>>> Here you'll notice that the RDATE for the 2nd recurrence instance
>>> specifies the original scheduled time of this instance in order to
>>> preserve the original RECURRENCE-ID.
>> Thanks a lot for the detailed explanation. But if the "This & Future" 
>> change is for any field other than dtstart/dtend like description, 
>> attendee etc, we will need to create exceptions for all past instances?
>
> Yes.
>
>>> The real concern here is that starting from the 4th recurrence
>>> instance, we have lost the original RECURRENCE-IDs. 
>> We also remove any existing exception components in the future?
>
> You're right!  All the recurrence instance that were cancelled
> by mean of an EXDATE would also disappear.
>
>>> We need to
>>> think carefully about how bad that really is.  What are our
>>> options?
>>>
>>> 1- Keep the RANGE parameter and address its issues.  Hummm...
>>>
>>> 2- Remove the RANGE parameter, and recommend to move DTSTART
>>>    to the future instance that corresponds to the new recurrence
>>>    pattern for all future instances (current proposal) and
>>>    live with the fact that the RECURRENCE-ID of all those
>>>    instances will have changed.
>>>
>>> 3- Remove the RANGE parameter, and recommend to split the
>>>    calendar component in two. One calendar component with
>>>    the original RRULE modified to specify a COUNT or UNTIL
>>>    rule part, and a second calendar component that specify
>>>    a new RRULE with no COUNT or UNTIL rule part.
>>>
>>> 4- Something we haven't thought about yet...
>>>
>>> Not clear which is the best (or less worse) solution.
>>> Perhaps it depends on the situation.  When an Organizer
>>> decide to reschedule all future recurrence instances
>>> option (3) might be the way to go.  On the other hand,
>>> when an Attendee decide to decline all future recurrence
>>> instances, option (2) might be the only way to go.
>> The way I was thinking was, the difference is between a change that 
>> affects time and a change that doesn't. For the latter, wouldn't 
>> creating exceptions for the past events with the old data and 
>> updating master and existing future exceptions with the new be enough?
>
> Cyrus pointed this out on the mailing list and I agree.
>
> > For the
>> former, we were thinking of option 3 but some folks wanted to keep 
>> future exceptions. And that meant exception components with 
>> recurrence-ids that did not match the master. We got stuck there :-(
>
> I don't have much time to investigate right now, but it seems that
> Apple iCal is able to do that.  I'll get back to you when I'll have
> a chance to look at what they are actually sending to our server...
>
>>
>> Again, I might be way off track on this.
>
> No, you're not!
>
> Cheers,
> Bernard
>
>>
>> Thanks,
>> Ciny
>>> I'm wondering how many people bothered to read this email
>>> that far. Send me a private email if you did. Just curious.
>>> Sorry.
>>>
>>> Cheers,
>>> Bernard
>>>
>>>
>>>>
>>>> Thanks,
>>>> Ciny
>>>>>
>>>>>>
>>>>>>>> The
>>>>>>>>   number of past recurrence instances is always finite...
>>>>>>>>
>>>>>>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>>>>>>
>>>>>>>> 3- Set DTSTART to the first recurrence instance to which you
>>>>>>>>   want the change to apply.
>>>>>>>>   
>>>>>> So is original DTSTART lost completely?
>>>>>
>>>>> The recurrence instance previously defined by DTSTART would become
>>>>> a simple recurrence instance defined by an RDATE property. You
>>>>> wouldn't be able to figure out what was the original DTSTART.
>>>>>
>>>>> > Doesn't this go against the
>>>>>> statement, "However, in such cases the original "DTSTART" date 
>>>>>> MUST still be maintained by the calendaring and scheduling system 
>>>>>> because the original "DTSTART" value has inherent usage 
>>>>>> dependencies by other properties such as the "RECURRENCE-ID"."
>>>>>
>>>>> I would think that what really matter is that the set of 
>>>>> RECURRENCE-ID
>>>>> is maintained.
>>>>>
>>>>>> If not, is there a standard way of maintaining it?
>>>>>> Also, in multiple places it is stated "The "DTSTART" property 
>>>>>> defines the first instance in the recurrence set". Will that be 
>>>>>> modified?
>>>>>
>>>>> That would clearly need to be modified.
>>>>>
>>>>> Cheers,
>>>>> Bernard
>>>>>>
>>>>>> Thanks,
>>>>>> Ciny
>>>>>>
>>>>>>>> The only issue here is that we need to clarify that RDATE can
>>>>>>>> specify a value less than the value specified by DTSTART.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Bernard
>>>>>>>>   
>>>>>>
>>>>>> _______________________________________________
>>>>>> Ietf-calsify mailing list
>>>>>> Ietf-calsify@osafoundation.org
>>>>>> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Mon Nov 19 00:00:17 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ityk5-0003c1-Sp
	for calsify-archive-Feit0ahl@lists.ietf.org; Mon, 19 Nov 2007 00:00:17 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ityk1-00060l-Pg
	for calsify-archive-Feit0ahl@lists.ietf.org; Mon, 19 Nov 2007 00:00:17 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 6C04980A1A;
	Sun, 18 Nov 2007 21:00:12 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 41C4780A17
	for <ietf-calsify@osafoundation.org>;
	Sun, 18 Nov 2007 21:00:09 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id CCFE6142203
	for <ietf-calsify@osafoundation.org>;
	Sun, 18 Nov 2007 21:00:09 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -0.825
X-Spam-Level: 
X-Spam-Status: No, score=-0.825 tagged_above=-50 required=4 tests=[AWL=0.400, 
	BAYES_00=-2.599, FORGED_RCVD_HELO=0.135,
	MIME_BOUND_NEXTPART=0.278, NO_REAL_NAME=0.961]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id ji+jfXHFsK00 for <ietf-calsify@osafoundation.org>;
	Sun, 18 Nov 2007 21:00:04 -0800 (PST)
Received: from ns4.neustar.com (ns4.neustar.com [156.154.24.139])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 38FEC1421FD
	for <ietf-calsify@osafoundation.org>;
	Sun, 18 Nov 2007 21:00:04 -0800 (PST)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 89FC42AC50;
	Mon, 19 Nov 2007 05:00:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Ityjq-00038B-A1; Mon, 19 Nov 2007 00:00:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Ityjq-00038B-A1@stiedprstage1.ietf.org>
Date: Mon, 19 Nov 2007 00:00:02 -0500
Cc: ietf-calsify@osafoundation.org
Subject: [Ietf-calsify] I-D Action:draft-ietf-calsify-2446bis-04.txt 
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

--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 Standards Simplification Working Group of the IETF.


	Title           : iCalendar Transport-Independent Interoperability Protocol (iTIP)
	Author(s)       : C. Daboo
	Filename        : draft-ietf-calsify-2446bis-04.txt
	Pages           : 122
	Date            : 2007-11-18

This document specifies a protocol using the iCalendar object
specification to provide scheduling interoperability between
different calendar systems.  This is done without reference to a
specific transport protocol so as to allow multiple methods of
communication between systems.  Subsequent documents will define
profiles of this protocol using specific interoperable methods of
communications between systems.
iTIP complements the iCalendar object specification by adding
semantics for group scheduling methods commonly available in current
calendar systems.  These scheduling methods permit two or more
calendar systems to perform transactions such as publish, schedule,
reschedule, respond to scheduling requests, negotiation of changes or
cancel.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-calsify-2446bis-04.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-calsify-2446bis-04.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-calsify-2446bis-04.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: <2007-11-18235549.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsify-2446bis-04.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-calsify-2446bis-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-11-18235549.I-D\@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify

--NextPart--



From ietf-calsify-bounces@osafoundation.org Tue Nov 20 17:39:40 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iubkq-0004GB-Sr
	for calsify-archive-Feit0ahl@lists.ietf.org; Tue, 20 Nov 2007 17:39:40 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iubkl-000631-EN
	for calsify-archive-Feit0ahl@lists.ietf.org; Tue, 20 Nov 2007 17:39:40 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id D702280A53;
	Tue, 20 Nov 2007 14:39:33 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 3041E8020F
	for <ietf-calsify@osafoundation.org>;
	Tue, 20 Nov 2007 14:39:33 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id CCF571421FD
	for <ietf-calsify@osafoundation.org>;
	Tue, 20 Nov 2007 14:39:33 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-50 required=4 tests=[AWL=0.977, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id VS6KqegNNuJT for <ietf-calsify@osafoundation.org>;
	Tue, 20 Nov 2007 14:39:28 -0800 (PST)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 7B3C11421F2
	for <ietf-calsify@osafoundation.org>;
	Tue, 20 Nov 2007 14:39:28 -0800 (PST)
Received: from fe-sfbay-10.sun.com ([192.18.43.129])
	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	lAKMdRRi023218 for <ietf-calsify@osafoundation.org>;
	Tue, 20 Nov 2007 14:39:27 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	id <0JRT00101TFZQE00@fe-sfbay-10.sun.com>
	(original mail from Ciny.Joy@Sun.COM) for
	ietf-calsify@osafoundation.org; Tue, 20 Nov 2007 14:39:27 -0800 (PST)
Received: from [192.18.126.79] by fe-sfbay-10.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	with ESMTPSA id <0JRT001BQTLH9FC0@fe-sfbay-10.sun.com> for
	ietf-calsify@osafoundation.org; Tue, 20 Nov 2007 14:39:18 -0800 (PST)
Date: Tue, 20 Nov 2007 14:42:15 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
To: ietf-calsify@osafoundation.org
Message-id: <474362C7.9010205@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20051027
Subject: [Ietf-calsify] iTip Cancel
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199

Hi,
   I am assuming support for RANGE in RECURRENCE-ID will be removed from 
iTIP too. If so, how do I cancel all future instances of an existing 
never ending series? Would it be a request to change the RRULEe to put 
in an until, instead of a cancel?

Thanks,
Ciny
_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 21 10:24:21 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IurR7-0003ZX-8V
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 21 Nov 2007 10:24:21 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IurR3-0008Jk-Dv
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 21 Nov 2007 10:24:21 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 9B95380B5E;
	Wed, 21 Nov 2007 07:24:16 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 2A62580B51
	for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 07:24:16 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id CA5841421FB
	for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 07:24:16 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.282
X-Spam-Level: 
X-Spam-Status: No, score=-1.282 tagged_above=-50 required=4 tests=[AWL=1.316, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id NUA-pMktD7GS for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 07:24:11 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 51FAE1421F2
	for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 07:24:11 -0800 (PST)
Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110])
	by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id
	lALFO3XN022458; Wed, 21 Nov 2007 08:24:04 -0700
Received: from rcsmt251.oracle.com (rcsmt251.oracle.com [148.87.90.196])
	by rgmgw1.us.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id
	lALEv3kN009639; Wed, 21 Nov 2007 08:23:59 -0700
Received: from bdesruis-ca.ca.oracle.com by acsmt351.oracle.com
	with ESMTP id 3380326991195658636; Wed, 21 Nov 2007 07:23:56 -0800
Message-ID: <47444D80.1090307@oracle.com>
Date: Wed, 21 Nov 2007 10:23:44 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] iTip Cancel
References: <474362C7.9010205@sun.com>
In-Reply-To: <474362C7.9010205@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

Ciny Joy wrote:
> Hi,
>   I am assuming support for RANGE in RECURRENCE-ID will be removed from 
> iTIP too. If so, how do I cancel all future instances of an existing 
> never ending series? Would it be a request to change the RRULEe to put 
> in an until, instead of a cancel?

Yes.

Another option would be to modify the master component with
DTSTART set to the first instance to cancel and specify
STATUS:CANCELLED, and specify RDATE and exception components
for all previous recurrence instances.  Humm...

That being said, truncating the RRULE with COUNT or UNTIL
looks much simpler to me.

Cheers,
Bernard

> 
> Thanks,
> Ciny
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
> 

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Wed Nov 21 13:37:10 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IuuRi-00009S-9h
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 21 Nov 2007 13:37:10 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IuuRe-00073h-Hi
	for calsify-archive-Feit0ahl@lists.ietf.org; Wed, 21 Nov 2007 13:37:10 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 8D20680B5E;
	Wed, 21 Nov 2007 10:37:05 -0800 (PST)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 9394980B5D
	for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 10:37:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 3ED2A1421F6
	for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 10:37:05 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-50 required=4 tests=[AWL=0.149,
	BAYES_00=-2.599]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id DtkaKIy7GRR3 for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 10:36:59 -0800 (PST)
Received: from mulberrymail.com (piper.mulberrymail.com [151.201.22.177])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 14CF41421FF
	for <ietf-calsify@osafoundation.org>;
	Wed, 21 Nov 2007 10:36:58 -0800 (PST)
Received: from [10.0.1.228] (piper.mulberrymail.com [151.201.22.177] (may be
	forged)) (authenticated bits=0)
	by mulberrymail.com (8.13.6/8.13.6) with ESMTP id lALIaGT9005938
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 21 Nov 2007 13:36:32 -0500
Date: Wed, 21 Nov 2007 13:48:19 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>,
	Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] iTip Cancel
Message-ID: <E5DC15D12F1B6B5BA535914C@[10.0.1.228]>
In-Reply-To: <47444D80.1090307@oracle.com>
References: <474362C7.9010205@sun.com> <47444D80.1090307@oracle.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

Hi Bernard,

--On Wednesday, November 21, 2007 10:23 -0500 Bernard Desruisseaux 
<bernard.desruisseaux@oracle.com> wrote:

>> Hi,
>>   I am assuming support for RANGE in RECURRENCE-ID will be removed from
>> iTIP too. If so, how do I cancel all future instances of an existing
>> never ending series? Would it be a request to change the RRULEe to put
>> in an until, instead of a cancel?
>
> Yes.
>
> Another option would be to modify the master component with
> DTSTART set to the first instance to cancel and specify
> STATUS:CANCELLED, and specify RDATE and exception components
> for all previous recurrence instances.  Humm...

That would be extremely ugly!

> That being said, truncating the RRULE with COUNT or UNTIL
> looks much simpler to me.

Is that sufficient? Shouldn't CANCEL's be sent?

I still feel we are missing a lot by removing RANGE.

-- 
Cyrus Daboo

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



From ietf-calsify-bounces@osafoundation.org Fri Nov 23 07:06:52 2007
Return-path: <ietf-calsify-bounces@osafoundation.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IvXJ6-0001zC-VD
	for calsify-archive-Feit0ahl@lists.ietf.org; Fri, 23 Nov 2007 07:06:52 -0500
Received: from [2001:4f8:3:ba:230:48ff:fe43:1456] (helo=leilani.osafoundation.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IvXJ2-00061Y-2s
	for calsify-archive-Feit0ahl@lists.ietf.org; Fri, 23 Nov 2007 07:06:52 -0500
Received: from leilani.osafoundation.org (leilani.osafoundation.org [127.0.0.1])
	by leilani.osafoundation.org (Postfix) with ESMTP id 2F56A80BD0;
	Fri, 23 Nov 2007 04:06:47 -0800 (PST)
X-Original-To: Ietf-calsify@osafoundation.org
Delivered-To: Ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org
	[204.152.186.98])
	by leilani.osafoundation.org (Postfix) with ESMTP id 44FD880BCF
	for <Ietf-calsify@osafoundation.org>;
	Fri, 23 Nov 2007 04:06:46 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id EF99B14220D
	for <Ietf-calsify@osafoundation.org>;
	Fri, 23 Nov 2007 04:06:46 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-50 required=4 tests=[AWL=0.515, 
	BAYES_00=-2.599, FORGED_RCVD_HELO=0.135]
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 54wgiBsukS-j for <Ietf-calsify@osafoundation.org>;
	Fri, 23 Nov 2007 04:06:41 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 4401F142206
	for <Ietf-calsify@osafoundation.org>;
	Fri, 23 Nov 2007 04:06:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.21,456,1188770400"; d="scan'208";a="158610968"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 23 Nov 2007 13:06:39 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lANC6dcW009010
	for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 13:06:39 +0100
Received: from adsl-247-5-fixip.tiscali.ch (ams3-vpn-dhcp170.cisco.com
	[10.61.64.170])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lANC6cZZ005963
	for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 12:06:39 GMT
Message-ID: <4746C24E.5050405@cisco.com>
Date: Fri, 23 Nov 2007 13:06:38 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: CALSIFY Mailinglist <Ietf-calsify@osafoundation.org>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=481; t=1195819599;
	x=1196683599; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com;
	z=From:=20Eliot=20Lear=20<lear@cisco.com>
	|Subject:=20meeting=20agenda |Sender:=20;
	bh=6zdg/z8/J5iTIxi1OEmi0vWd1snsUOahygfXqHcXqOk=;
	b=XMgzxK+NhesixANe/Cf9Xax8N5v80UZ4wnstw6F0wW8bokCKPO/AxDASZHZgp2Iu4Ozv766u
	3LnXseO881BSdL/01JiVDteRsjp1234aq78O6B7EIyf5ACh+/n3q8Nw4;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass (s
	ig from cisco.com/amsdkim2001 verified; ); 
Subject: [Ietf-calsify] meeting agenda
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>, 
	<mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

Our agenda this time looks an awful lot like the agenda last time:

1.  Agenda Bashing (1 minute)
2.  Administrativia (Chairs - 3 minutes)
3.  RFC2445bis Status (Chairs - 5 minutes)
4.  RFC2446bis Discussion (Cyrus - the rest)

We plan on spending the vast bulk of the time on item 4, with the
expectation that we will close on changes sometime after the IETF
meeting.  Resolving RFC2446bis will also close ALL changes to
RFC2445bis, Issue 63 not withstanding.

Eliot
_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify




Return-Path: <lear@cisco.com>
X-Original-To: Ietf-calsify@osafoundation.org
Delivered-To: Ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 44FD880BCF for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 04:06:46 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id EF99B14220D for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 04:06:46 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-50 required=4 tests=[AWL=0.515,  BAYES_00=-2.599, FORGED_RCVD_HELO=0.135]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54wgiBsukS-j for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 04:06:41 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by laweleka.osafoundation.org (Postfix) with ESMTP id 4401F142206 for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 04:06:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.21,456,1188770400"; d="scan'208";a="158610968"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 23 Nov 2007 13:06:39 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lANC6dcW009010 for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 13:06:39 +0100
Received: from adsl-247-5-fixip.tiscali.ch (ams3-vpn-dhcp170.cisco.com [10.61.64.170]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lANC6cZZ005963 for <Ietf-calsify@osafoundation.org>; Fri, 23 Nov 2007 12:06:39 GMT
Message-ID: <4746C24E.5050405@cisco.com>
Date: Fri, 23 Nov 2007 13:06:38 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: CALSIFY Mailinglist <Ietf-calsify@osafoundation.org>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=481; t=1195819599; x=1196683599; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20meeting=20agenda |Sender:=20; bh=6zdg/z8/J5iTIxi1OEmi0vWd1snsUOahygfXqHcXqOk=; b=XMgzxK+NhesixANe/Cf9Xax8N5v80UZ4wnstw6F0wW8bokCKPO/AxDASZHZgp2Iu4Ozv766u 3LnXseO881BSdL/01JiVDteRsjp1234aq78O6B7EIyf5ACh+/n3q8Nw4;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass (s ig from cisco.com/amsdkim2001 verified; ); 
Subject: [Ietf-calsify] meeting agenda
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Nov 2007 12:06:46 -0000

Our agenda this time looks an awful lot like the agenda last time:

1.  Agenda Bashing (1 minute)
2.  Administrativia (Chairs - 3 minutes)
3.  RFC2445bis Status (Chairs - 5 minutes)
4.  RFC2446bis Discussion (Cyrus - the rest)

We plan on spending the vast bulk of the time on item 4, with the
expectation that we will close on changes sometime after the IETF
meeting.  Resolving RFC2446bis will also close ALL changes to
RFC2445bis, Issue 63 not withstanding.

Eliot


Return-Path: <cyrus@daboo.name>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 9394980B5D for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 10:37:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 3ED2A1421F6 for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 10:37:05 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-50 required=4 tests=[AWL=0.149, BAYES_00=-2.599]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DtkaKIy7GRR3 for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 10:36:59 -0800 (PST)
Received: from mulberrymail.com (piper.mulberrymail.com [151.201.22.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 14CF41421FF for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 10:36:58 -0800 (PST)
Received: from [10.0.1.228] (piper.mulberrymail.com [151.201.22.177] (may be forged)) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id lALIaGT9005938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Nov 2007 13:36:32 -0500
Date: Wed, 21 Nov 2007 13:48:19 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>, Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] iTip Cancel
Message-ID: <E5DC15D12F1B6B5BA535914C@[10.0.1.228]>
In-Reply-To: <47444D80.1090307@oracle.com>
References: <474362C7.9010205@sun.com> <47444D80.1090307@oracle.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2007 18:37:04 -0000

Hi Bernard,

--On Wednesday, November 21, 2007 10:23 -0500 Bernard Desruisseaux 
<bernard.desruisseaux@oracle.com> wrote:

>> Hi,
>>   I am assuming support for RANGE in RECURRENCE-ID will be removed from
>> iTIP too. If so, how do I cancel all future instances of an existing
>> never ending series? Would it be a request to change the RRULEe to put
>> in an until, instead of a cancel?
>
> Yes.
>
> Another option would be to modify the master component with
> DTSTART set to the first instance to cancel and specify
> STATUS:CANCELLED, and specify RDATE and exception components
> for all previous recurrence instances.  Humm...

That would be extremely ugly!

> That being said, truncating the RRULE with COUNT or UNTIL
> looks much simpler to me.

Is that sufficient? Shouldn't CANCEL's be sent?

I still feel we are missing a lot by removing RANGE.

-- 
Cyrus Daboo



Return-Path: <bernard.desruisseaux@oracle.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 2A62580B51 for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 07:24:16 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id CA5841421FB for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 07:24:16 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.282
X-Spam-Level: 
X-Spam-Status: No, score=-1.282 tagged_above=-50 required=4 tests=[AWL=1.316,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NUA-pMktD7GS for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 07:24:11 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 51FAE1421F2 for <ietf-calsify@osafoundation.org>; Wed, 21 Nov 2007 07:24:11 -0800 (PST)
Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id lALFO3XN022458; Wed, 21 Nov 2007 08:24:04 -0700
Received: from rcsmt251.oracle.com (rcsmt251.oracle.com [148.87.90.196]) by rgmgw1.us.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id lALEv3kN009639; Wed, 21 Nov 2007 08:23:59 -0700
Received: from bdesruis-ca.ca.oracle.com by acsmt351.oracle.com with ESMTP id 3380326991195658636; Wed, 21 Nov 2007 07:23:56 -0800
Message-ID: <47444D80.1090307@oracle.com>
Date: Wed, 21 Nov 2007 10:23:44 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] iTip Cancel
References: <474362C7.9010205@sun.com>
In-Reply-To: <474362C7.9010205@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2007 15:24:16 -0000

Ciny Joy wrote:
> Hi,
>   I am assuming support for RANGE in RECURRENCE-ID will be removed from 
> iTIP too. If so, how do I cancel all future instances of an existing 
> never ending series? Would it be a request to change the RRULEe to put 
> in an until, instead of a cancel?

Yes.

Another option would be to modify the master component with
DTSTART set to the first instance to cancel and specify
STATUS:CANCELLED, and specify RDATE and exception components
for all previous recurrence instances.  Humm...

That being said, truncating the RRULE with COUNT or UNTIL
looks much simpler to me.

Cheers,
Bernard

> 
> Thanks,
> Ciny
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
> 



Return-Path: <Ciny.Joy@Sun.COM>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3041E8020F for <ietf-calsify@osafoundation.org>; Tue, 20 Nov 2007 14:39:33 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id CCF571421FD for <ietf-calsify@osafoundation.org>; Tue, 20 Nov 2007 14:39:33 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-50 required=4 tests=[AWL=0.977,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VS6KqegNNuJT for <ietf-calsify@osafoundation.org>; Tue, 20 Nov 2007 14:39:28 -0800 (PST)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7B3C11421F2 for <ietf-calsify@osafoundation.org>; Tue, 20 Nov 2007 14:39:28 -0800 (PST)
Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id lAKMdRRi023218 for <ietf-calsify@osafoundation.org>; Tue, 20 Nov 2007 14:39:27 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JRT00101TFZQE00@fe-sfbay-10.sun.com> (original mail from Ciny.Joy@Sun.COM) for ietf-calsify@osafoundation.org; Tue, 20 Nov 2007 14:39:27 -0800 (PST)
Received: from [192.18.126.79] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JRT001BQTLH9FC0@fe-sfbay-10.sun.com> for ietf-calsify@osafoundation.org; Tue, 20 Nov 2007 14:39:18 -0800 (PST)
Date: Tue, 20 Nov 2007 14:42:15 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
Sender: Ciny.Joy@Sun.COM
To: ietf-calsify@osafoundation.org
Message-id: <474362C7.9010205@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20051027
Subject: [Ietf-calsify] iTip Cancel
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2007 22:39:33 -0000

Hi,
   I am assuming support for RANGE in RECURRENCE-ID will be removed from 
iTIP too. If so, how do I cancel all future instances of an existing 
never ending series? Would it be a request to change the RRULEe to put 
in an until, instead of a cancel?

Thanks,
Ciny


Return-Path: <ietf@ietf.org>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 41C4780A17 for <ietf-calsify@osafoundation.org>; Sun, 18 Nov 2007 21:00:09 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id CCFE6142203 for <ietf-calsify@osafoundation.org>; Sun, 18 Nov 2007 21:00:09 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -0.825
X-Spam-Level: 
X-Spam-Status: No, score=-0.825 tagged_above=-50 required=4 tests=[AWL=0.400,  BAYES_00=-2.599, FORGED_RCVD_HELO=0.135, MIME_BOUND_NEXTPART=0.278, NO_REAL_NAME=0.961]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ji+jfXHFsK00 for <ietf-calsify@osafoundation.org>; Sun, 18 Nov 2007 21:00:04 -0800 (PST)
Received: from ns4.neustar.com (ns4.neustar.com [156.154.24.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 38FEC1421FD for <ietf-calsify@osafoundation.org>; Sun, 18 Nov 2007 21:00:04 -0800 (PST)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 89FC42AC50; Mon, 19 Nov 2007 05:00:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Ityjq-00038B-A1; Mon, 19 Nov 2007 00:00:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Ityjq-00038B-A1@stiedprstage1.ietf.org>
Date: Mon, 19 Nov 2007 00:00:02 -0500
Cc: ietf-calsify@osafoundation.org
Subject: [Ietf-calsify] I-D Action:draft-ietf-calsify-2446bis-04.txt 
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2007 05:00:09 -0000

--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 Standards Simplification Working Group of the IETF.


	Title           : iCalendar Transport-Independent Interoperability Protocol (iTIP)
	Author(s)       : C. Daboo
	Filename        : draft-ietf-calsify-2446bis-04.txt
	Pages           : 122
	Date            : 2007-11-18

This document specifies a protocol using the iCalendar object
specification to provide scheduling interoperability between
different calendar systems.  This is done without reference to a
specific transport protocol so as to allow multiple methods of
communication between systems.  Subsequent documents will define
profiles of this protocol using specific interoperable methods of
communications between systems.
iTIP complements the iCalendar object specification by adding
semantics for group scheduling methods commonly available in current
calendar systems.  These scheduling methods permit two or more
calendar systems to perform transactions such as publish, schedule,
reschedule, respond to scheduling requests, negotiation of changes or
cancel.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-calsify-2446bis-04.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-calsify-2446bis-04.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-calsify-2446bis-04.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: <2007-11-18235549.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsify-2446bis-04.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-calsify-2446bis-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-11-18235549.I-D\@ietf.org>


--OtherAccess--

--NextPart--


Return-Path: <Ciny.Joy@Sun.COM>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 9526980CCB for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 16:10:44 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 1A973142215 for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 16:10:45 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.165
X-Spam-Level: 
X-Spam-Status: No, score=-2.165 tagged_above=-50 required=4 tests=[AWL=0.433,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xu1xJrx+a6Bp for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 16:10:39 -0800 (PST)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 44BEF14220E for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 16:10:39 -0800 (PST)
Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id lAG0Acn8022501 for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 16:10:38 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JRK00501OFJYH00@fe-sfbay-09.sun.com> (original mail from Ciny.Joy@Sun.COM) for ietf-calsify@osafoundation.org; Thu, 15 Nov 2007 16:10:38 -0800 (PST)
Received: from [129.150.18.236] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JRK0048NOHOAEE0@fe-sfbay-09.sun.com>; Thu, 15 Nov 2007 16:10:37 -0800 (PST)
Date: Thu, 15 Nov 2007 16:10:37 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
In-reply-to: <473CDA4A.8020505@oracle.com>
Sender: Ciny.Joy@Sun.COM
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
Message-id: <473CDFFD.7050801@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <20071106200005.569D080A03@leilani.osafoundation.org> <4730E760.4090309@sun.com> <473A9396.9050600@oracle.com> <473B4575.5030806@sun.com> <473CA62F.6080302@oracle.com> <473CCF36.5040000@sun.com> <473CDA4A.8020505@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2007 00:10:44 -0000

Thanks again Bernard.
Sorry about not cc'ing the list earlier. It was an accidental omission.
I usually get the digest of the mailing list emails. So haven't seen 
Cyrus's reply yet. But glad to know I wasn't completely off track.
Looking forward to more discussions that might provide a solution to the 
preserving of future exceptions on a time change issue.

Thanks,
Ciny

Bernard Desruisseaux wrote:
> Hi Ciny,
>
> I'm only replying to you since you didn't CC the list on your message.
> Not sure why though!
>
> Ciny Joy wrote:
>> Bernard Desruisseaux wrote:
>>>
>>> Here you'll notice that the RDATE for the 2nd recurrence instance
>>> specifies the original scheduled time of this instance in order to
>>> preserve the original RECURRENCE-ID.
>> Thanks a lot for the detailed explanation. But if the "This & Future" 
>> change is for any field other than dtstart/dtend like description, 
>> attendee etc, we will need to create exceptions for all past instances?
>
> Yes.
>
>>> The real concern here is that starting from the 4th recurrence
>>> instance, we have lost the original RECURRENCE-IDs. 
>> We also remove any existing exception components in the future?
>
> You're right!  All the recurrence instance that were cancelled
> by mean of an EXDATE would also disappear.
>
>>> We need to
>>> think carefully about how bad that really is.  What are our
>>> options?
>>>
>>> 1- Keep the RANGE parameter and address its issues.  Hummm...
>>>
>>> 2- Remove the RANGE parameter, and recommend to move DTSTART
>>>    to the future instance that corresponds to the new recurrence
>>>    pattern for all future instances (current proposal) and
>>>    live with the fact that the RECURRENCE-ID of all those
>>>    instances will have changed.
>>>
>>> 3- Remove the RANGE parameter, and recommend to split the
>>>    calendar component in two. One calendar component with
>>>    the original RRULE modified to specify a COUNT or UNTIL
>>>    rule part, and a second calendar component that specify
>>>    a new RRULE with no COUNT or UNTIL rule part.
>>>
>>> 4- Something we haven't thought about yet...
>>>
>>> Not clear which is the best (or less worse) solution.
>>> Perhaps it depends on the situation.  When an Organizer
>>> decide to reschedule all future recurrence instances
>>> option (3) might be the way to go.  On the other hand,
>>> when an Attendee decide to decline all future recurrence
>>> instances, option (2) might be the only way to go.
>> The way I was thinking was, the difference is between a change that 
>> affects time and a change that doesn't. For the latter, wouldn't 
>> creating exceptions for the past events with the old data and 
>> updating master and existing future exceptions with the new be enough?
>
> Cyrus pointed this out on the mailing list and I agree.
>
> > For the
>> former, we were thinking of option 3 but some folks wanted to keep 
>> future exceptions. And that meant exception components with 
>> recurrence-ids that did not match the master. We got stuck there :-(
>
> I don't have much time to investigate right now, but it seems that
> Apple iCal is able to do that.  I'll get back to you when I'll have
> a chance to look at what they are actually sending to our server...
>
>>
>> Again, I might be way off track on this.
>
> No, you're not!
>
> Cheers,
> Bernard
>
>>
>> Thanks,
>> Ciny
>>> I'm wondering how many people bothered to read this email
>>> that far. Send me a private email if you did. Just curious.
>>> Sorry.
>>>
>>> Cheers,
>>> Bernard
>>>
>>>
>>>>
>>>> Thanks,
>>>> Ciny
>>>>>
>>>>>>
>>>>>>>> The
>>>>>>>>   number of past recurrence instances is always finite...
>>>>>>>>
>>>>>>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>>>>>>
>>>>>>>> 3- Set DTSTART to the first recurrence instance to which you
>>>>>>>>   want the change to apply.
>>>>>>>>   
>>>>>> So is original DTSTART lost completely?
>>>>>
>>>>> The recurrence instance previously defined by DTSTART would become
>>>>> a simple recurrence instance defined by an RDATE property. You
>>>>> wouldn't be able to figure out what was the original DTSTART.
>>>>>
>>>>> > Doesn't this go against the
>>>>>> statement, "However, in such cases the original "DTSTART" date 
>>>>>> MUST still be maintained by the calendaring and scheduling system 
>>>>>> because the original "DTSTART" value has inherent usage 
>>>>>> dependencies by other properties such as the "RECURRENCE-ID"."
>>>>>
>>>>> I would think that what really matter is that the set of 
>>>>> RECURRENCE-ID
>>>>> is maintained.
>>>>>
>>>>>> If not, is there a standard way of maintaining it?
>>>>>> Also, in multiple places it is stated "The "DTSTART" property 
>>>>>> defines the first instance in the recurrence set". Will that be 
>>>>>> modified?
>>>>>
>>>>> That would clearly need to be modified.
>>>>>
>>>>> Cheers,
>>>>> Bernard
>>>>>>
>>>>>> Thanks,
>>>>>> Ciny
>>>>>>
>>>>>>>> The only issue here is that we need to clarify that RDATE can
>>>>>>>> specify a value less than the value specified by DTSTART.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Bernard
>>>>>>>>   
>>>>>>
>>>>>> _______________________________________________
>>>>>> Ietf-calsify mailing list
>>>>>> Ietf-calsify@osafoundation.org
>>>>>> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>



Return-Path: <cyrus@daboo.name>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id F332580CC4 for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 14:03:34 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 78EDF14220D for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 14:03:35 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.462
X-Spam-Level: 
X-Spam-Status: No, score=-2.462 tagged_above=-50 required=4 tests=[AWL=0.137,  BAYES_00=-2.599]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yvnYBnEhn3jy for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 14:03:30 -0800 (PST)
Received: from mulberrymail.com (piper.mulberrymail.com [151.201.22.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id B6BD91421FC for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 14:03:25 -0800 (PST)
Received: from caldav.corp.apple.com ([17.101.32.44]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id lAFM1s6l008376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Nov 2007 17:01:59 -0500
Date: Thu, 15 Nov 2007 17:01:49 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>, Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
Message-ID: <1C603AE21E804344D7EA043C@caldav.corp.apple.com>
In-Reply-To: <473CA62F.6080302@oracle.com>
References: <20071106200005.569D080A03@leilani.osafoundation.org> <4730E760.4090309@sun.com> <473A9396.9050600@oracle.com>	<473B4575.5030806@sun.com> <473CA62F.6080302@oracle.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2007 22:03:35 -0000

Hi Bernard,

--On November 15, 2007 3:03:59 PM -0500 Bernard Desruisseaux 
<bernard.desruisseaux@oracle.com> wrote:

> The real concern here is that starting from the 4th recurrence
> instance, we have lost the original RECURRENCE-IDs. We need to
> think carefully about how bad that really is.  What are our
> options?
>
> 1- Keep the RANGE parameter and address its issues.  Hummm...
>
> 2- Remove the RANGE parameter, and recommend to move DTSTART
>     to the future instance that corresponds to the new recurrence
>     pattern for all future instances (current proposal) and
>     live with the fact that the RECURRENCE-ID of all those
>     instances will have changed.
>
> 3- Remove the RANGE parameter, and recommend to split the
>     calendar component in two. One calendar component with
>     the original RRULE modified to specify a COUNT or UNTIL
>     rule part, and a second calendar component that specify
>     a new RRULE with no COUNT or UNTIL rule part.
>
> 4- Something we haven't thought about yet...

> On the other hand, when an Attendee decide to decline all future
> recurrence instances, option (2) might be the only way to go.

Actually I disagree. In that case there is a finite set of instances that 
the attendee has accepted and an infinite set that is declined. So the 
master component is marked as declined, and then overridden components for 
the finite set added with accepted status for that attendee. None of that 
involves either (1), (2) or (3).

I'm still not sure what the best overall solution for this is though. I am 
concerned about the loss of RECURRENCE-ID sync caused by (2). I think the 
rule should be if you have to do something that causes the recurrence-ids 
to change then you have to split the events. So that would cover the case 
of changing the time of all future instances, or changing the pattern of 
the rule, but not of changing the location of all future instances. For the 
later you would change the location of the master, then override all 
components upto the actual point of change and use the old location in 
those. Same would apply to attendee state etc. However, if we take that 
approach, it actually eliminates some of the problems with RANGE= and makes 
that more viable.

-- 
Cyrus Daboo



Return-Path: <bernard.desruisseaux@oracle.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C415F80CD5 for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 12:05:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 494CA142207 for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 12:05:05 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.318
X-Spam-Level: 
X-Spam-Status: No, score=-2.318 tagged_above=-50 required=4 tests=[AWL=0.280,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vhqio9mVTqMh for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 12:04:59 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 5715E1421F6 for <ietf-calsify@osafoundation.org>; Thu, 15 Nov 2007 12:04:59 -0800 (PST)
Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id lAFK4uYY010252; Thu, 15 Nov 2007 14:04:56 -0600
Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id lAELM3D5026333; Thu, 15 Nov 2007 13:04:55 -0700
Received: from bdesruis-ca.ca.oracle.com by acsmt350.oracle.com with ESMTP id 3368948591195157041; Thu, 15 Nov 2007 12:04:01 -0800
Message-ID: <473CA62F.6080302@oracle.com>
Date: Thu, 15 Nov 2007 15:03:59 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <20071106200005.569D080A03@leilani.osafoundation.org> <4730E760.4090309@sun.com> <473A9396.9050600@oracle.com> <473B4575.5030806@sun.com>
In-Reply-To: <473B4575.5030806@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2007 20:05:04 -0000

Hi Ciny,

Ciny Joy wrote:
> Thanks Bernard. Just one question below...
> 
> Bernard Desruisseaux wrote:
>> Hi Ciny,
>>
>> Ciny Joy wrote:
>>>
>>>>
>>>>>
>>>>> This time I would like to suggest a solution for the case where
>>>>> an organizer changes all future recurrence instances of a recurring
>>>>> calendar component:
>>>>>
>>>>> 1- Specify RDATE properties for all past recurrence instances
>>>>>   and define exception components for them if needed.
>>> How do you define "if needed"?
>>
>> A past recurrence instance identical to the recurrence instance
>> defined by DTSTART, except for its scheduled time, would not need
>> a separate component.
> If we are making a "This & Future" change and changing dtstart to the 
> first instance of the newly created series, won't all past instances be 
> different from DTSTART? Or am I understanding this wrong?

Here's a simple example where separate components would not be
needed for past recurrence instances:

A.1 Schedule a daily event at 9:00 AM forever starting on Nov. 12.

     BEGIN:VEVENT
     DTSTART;TZID=America/Montreal:20071112T090000
     DTEND;TZID=America/Montreal:20071112T100000
     RRULE:FREQ=DAILY
     ...
     END:VEVENT

A.2 Reschedule 4th recurrence instance (Nov. 15) as well as
     all future recurrence instances at 10:00 AM

     BEGIN:VEVENT
     RDATE;TZID=America/Montreal:20071112T090000/20071112T100000
     RDATE;TZID=America/Montreal:20071113T090000/20071113T100000
     RDATE;TZID=America/Montreal:20071114T090000/20071114T100000
     DTSTART;TZID=America/Montreal:20071115T100000
     DTEND;TZID=America/Montreal:20071115T110000
     RRULE:FREQ=DAILY;COUNT=5
     ...
     END:VEVENT

Now let's look at a slightly more complex example:

B.1 Schedule a daily event at 9:00 AM forever starting on Nov. 12.

     BEGIN:VEVENT
     DTSTART;TZID=America/Montreal:20071112T090000
     DTEND;TZID=America/Montreal:20071112T100000
     RRULE:FREQ=DAILY
     ...
     END:VEVENT

B.2 Reschedule 2nd recurrence instance (Nov. 13) at 10:00 AM.

     BEGIN:VEVENT
     DTSTART;TZID=America/Montreal:20071112T090000
     DTEND;TZID=America/Montreal:20071112T100000
     RRULE:FREQ=DAILY;COUNT=5
     ...
     END:VEVENT
     BEGIN:VEVENT
     RECURRENCE-ID;TZID=America/Montreal:20071113T090000
     DTSTART;TZID=America/Montreal:20071113T100000
     DTEND;TZID=America/Montreal:20071113T110000
     ...
     END:VEVENT

B.3 Reschedule 4th recurrence instance (Nov. 15) as well as
     all future recurrence instances at 10:00 AM

     BEGIN:VEVENT
     RDATE;TZID=America/Montreal:20071112T090000/20071112T100000
     RDATE;TZID=America/Montreal:20071113T090000/20071113T100000
     RDATE;TZID=America/Montreal:20071114T090000/20071114T100000
     DTSTART;TZID=America/Montreal:20071115T100000
     DTEND;TZID=America/Montreal:20071115T110000
     RRULE:FREQ=DAILY;COUNT=5
     ...
     END:VEVENT
     BEGIN:VEVENT
     RECURRENCE-ID;TZID=America/Montreal:20071113T090000
     DTSTART;TZID=America/Montreal:20071113T100000
     DTEND;TZID=America/Montreal:20071113T110000
     ...
     END:VEVENT

Here you'll notice that the RDATE for the 2nd recurrence instance
specifies the original scheduled time of this instance in order to
preserve the original RECURRENCE-ID.


The real concern here is that starting from the 4th recurrence
instance, we have lost the original RECURRENCE-IDs. We need to
think carefully about how bad that really is.  What are our
options?

1- Keep the RANGE parameter and address its issues.  Hummm...

2- Remove the RANGE parameter, and recommend to move DTSTART
    to the future instance that corresponds to the new recurrence
    pattern for all future instances (current proposal) and
    live with the fact that the RECURRENCE-ID of all those
    instances will have changed.

3- Remove the RANGE parameter, and recommend to split the
    calendar component in two. One calendar component with
    the original RRULE modified to specify a COUNT or UNTIL
    rule part, and a second calendar component that specify
    a new RRULE with no COUNT or UNTIL rule part.

4- Something we haven't thought about yet...

Not clear which is the best (or less worse) solution.
Perhaps it depends on the situation.  When an Organizer
decide to reschedule all future recurrence instances
option (3) might be the way to go.  On the other hand,
when an Attendee decide to decline all future recurrence
instances, option (2) might be the only way to go.
I'm wondering how many people bothered to read this email
that far. Send me a private email if you did. Just curious.
Sorry.

Cheers,
Bernard


> 
> Thanks,
> Ciny
>>
>>>
>>>>> The
>>>>>   number of past recurrence instances is always finite...
>>>>>
>>>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>>>
>>>>> 3- Set DTSTART to the first recurrence instance to which you
>>>>>   want the change to apply.
>>>>>   
>>> So is original DTSTART lost completely?
>>
>> The recurrence instance previously defined by DTSTART would become
>> a simple recurrence instance defined by an RDATE property. You
>> wouldn't be able to figure out what was the original DTSTART.
>>
>> > Doesn't this go against the
>>> statement, "However, in such cases the original "DTSTART" date MUST 
>>> still be maintained by the calendaring and scheduling system because 
>>> the original "DTSTART" value has inherent usage dependencies by other 
>>> properties such as the "RECURRENCE-ID"."
>>
>> I would think that what really matter is that the set of RECURRENCE-ID
>> is maintained.
>>
>>> If not, is there a standard way of maintaining it?
>>> Also, in multiple places it is stated "The "DTSTART" property defines 
>>> the first instance in the recurrence set". Will that be modified?
>>
>> That would clearly need to be modified.
>>
>> Cheers,
>> Bernard
>>>
>>> Thanks,
>>> Ciny
>>>
>>>>> The only issue here is that we need to clarify that RDATE can
>>>>> specify a value less than the value specified by DTSTART.
>>>>>
>>>>> Cheers,
>>>>> Bernard
>>>>>   
>>>
>>> _______________________________________________
>>> Ietf-calsify mailing list
>>> Ietf-calsify@osafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>>>
>>
> 
> 



Return-Path: <Ciny.Joy@Sun.COM>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 7782780176 for <ietf-calsify@osafoundation.org>; Wed, 14 Nov 2007 10:59:16 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id EF340142204 for <ietf-calsify@osafoundation.org>; Wed, 14 Nov 2007 10:59:16 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-50 required=4 tests=[AWL=0.650,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-oZhoWVI4lX for <ietf-calsify@osafoundation.org>; Wed, 14 Nov 2007 10:59:11 -0800 (PST)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 54EAD1421FD for <ietf-calsify@osafoundation.org>; Wed, 14 Nov 2007 10:59:11 -0800 (PST)
Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id lAEIx0Qf018598 for <ietf-calsify@osafoundation.org>; Wed, 14 Nov 2007 10:59:10 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JRI00D01EWZ0500@fe-sfbay-09.sun.com> (original mail from Ciny.Joy@Sun.COM) for ietf-calsify@osafoundation.org; Wed, 14 Nov 2007 10:59:00 -0800 (PST)
Received: from [129.150.19.172] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JRI00AROFEBECG0@fe-sfbay-09.sun.com>; Wed, 14 Nov 2007 10:59:00 -0800 (PST)
Date: Wed, 14 Nov 2007 10:59:01 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
In-reply-to: <473A9396.9050600@oracle.com>
Sender: Ciny.Joy@Sun.COM
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
Message-id: <473B4575.5030806@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <20071106200005.569D080A03@leilani.osafoundation.org> <4730E760.4090309@sun.com> <473A9396.9050600@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2007 18:59:17 -0000

Thanks Bernard. Just one question below...

Bernard Desruisseaux wrote:
> Hi Ciny,
>
> Ciny Joy wrote:
>>
>>>
>>>>
>>>> This time I would like to suggest a solution for the case where
>>>> an organizer changes all future recurrence instances of a recurring
>>>> calendar component:
>>>>
>>>> 1- Specify RDATE properties for all past recurrence instances
>>>>   and define exception components for them if needed.
>> How do you define "if needed"?
>
> A past recurrence instance identical to the recurrence instance
> defined by DTSTART, except for its scheduled time, would not need
> a separate component.
If we are making a "This & Future" change and changing dtstart to the 
first instance of the newly created series, won't all past instances be 
different from DTSTART? Or am I understanding this wrong?

Thanks,
Ciny
>
>>
>>>> The
>>>>   number of past recurrence instances is always finite...
>>>>
>>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>>
>>>> 3- Set DTSTART to the first recurrence instance to which you
>>>>   want the change to apply.
>>>>   
>> So is original DTSTART lost completely?
>
> The recurrence instance previously defined by DTSTART would become
> a simple recurrence instance defined by an RDATE property. You
> wouldn't be able to figure out what was the original DTSTART.
>
> > Doesn't this go against the
>> statement, "However, in such cases the original "DTSTART" date MUST 
>> still be maintained by the calendaring and scheduling system because 
>> the original "DTSTART" value has inherent usage dependencies by other 
>> properties such as the "RECURRENCE-ID"."
>
> I would think that what really matter is that the set of RECURRENCE-ID
> is maintained.
>
>> If not, is there a standard way of maintaining it?
>> Also, in multiple places it is stated "The "DTSTART" property defines 
>> the first instance in the recurrence set". Will that be modified?
>
> That would clearly need to be modified.
>
> Cheers,
> Bernard
>>
>> Thanks,
>> Ciny
>>
>>>> The only issue here is that we need to clarify that RDATE can
>>>> specify a value less than the value specified by DTSTART.
>>>>
>>>> Cheers,
>>>> Bernard
>>>>   
>>
>> _______________________________________________
>> Ietf-calsify mailing list
>> Ietf-calsify@osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>>
>



Return-Path: <bernard.desruisseaux@oracle.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 1B7E880847 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:34:40 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 75184142202 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:33:45 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.315
X-Spam-Level: 
X-Spam-Status: No, score=-2.315 tagged_above=-50 required=4 tests=[AWL=0.283,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vXSxKsXx5C6p for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:33:39 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id CA82E1421FF for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:33:39 -0800 (PST)
Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id lAE6Xb0x019791; Tue, 13 Nov 2007 23:33:38 -0700
Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id lAE6382G018364; Tue, 13 Nov 2007 23:33:36 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-106-55.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 3364228811195022016; Tue, 13 Nov 2007 22:33:36 -0800
Message-ID: <473A96BE.6010209@oracle.com>
Date: Wed, 14 Nov 2007 01:33:34 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew N Dowden <andrew_dowden@softdesign.net.nz>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <471612F8.9020306@cisco.com> <47302DB0.1050207@cisco.com> <47314658.4010502@softdesign.net.nz>
In-Reply-To: <47314658.4010502@softdesign.net.nz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify <ietf-calsify@osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2007 06:34:40 -0000

Hi Andrew,

Andrew N Dowden wrote:
> Eliot Lear wrote:
>>> This time I would like to suggest a solution for the case where
>>> an organizer changes all future recurrence instances of a recurring
>>> calendar component:
>>>
>>> 1- Specify RDATE properties for all past recurrence instances
>>>    and define exception components for them if needed. The
>>>    number of past recurrence instances is always finite...
>>>
>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>
>>> 3- Set DTSTART to the first recurrence instance to which you
>>>    want the change to apply.
>>>
>>> The only issue here is that we need to clarify that RDATE can
>>> specify a value less than the value specified by DTSTART.
>>>     
> Is there anything wrong with? :
> 
> 1- Specify RDATE properties for all past recurrence instances,
>     while excluding those removed by EXDATE properties..
>    ( The number of past recurrence instances is always finite. )
> 
> 2- Remove any RRULE and EXDATE properties.

We're trying to address an issue with *unbounded* recurring
calendar components here (i.e., RRULE doesn't specify the
COUNT nor the UNTIL rule parts).

Removing the RRULE property would clearly make the recurring
calendar component bounded which is not want we want.

Cheers,
Bernard

> 
> 3- Set DTSTART to match the first RDATE property.
> 


Return-Path: <bernard.desruisseaux@oracle.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 635D2808A1 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:22:35 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id BD688142202 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:21:40 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-50 required=4 tests=[AWL=0.286,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x10YVNeTk6L1 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:21:35 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 185A81421FF for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:21:34 -0800 (PST)
Received: from rgmgw2.us.oracle.com (rgmgw2.us.oracle.com [138.1.186.111]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id lAE6LRqK023297; Wed, 14 Nov 2007 00:21:27 -0600
Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by rgmgw2.us.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id lAE6LOrB014004; Tue, 13 Nov 2007 23:21:24 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-106-55.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 3364222501195021207; Tue, 13 Nov 2007 22:20:07 -0800
Message-ID: <473A9396.9050600@oracle.com>
Date: Wed, 14 Nov 2007 01:20:06 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <20071106200005.569D080A03@leilani.osafoundation.org> <4730E760.4090309@sun.com>
In-Reply-To: <4730E760.4090309@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
Cc: ietf-calsify@osafoundation.org
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2007 06:22:35 -0000

Hi Ciny,

Ciny Joy wrote:
> 
>>
>>>
>>> This time I would like to suggest a solution for the case where
>>> an organizer changes all future recurrence instances of a recurring
>>> calendar component:
>>>
>>> 1- Specify RDATE properties for all past recurrence instances
>>>   and define exception components for them if needed.
> How do you define "if needed"?

A past recurrence instance identical to the recurrence instance
defined by DTSTART, except for its scheduled time, would not need
a separate component.

> 
>>> The
>>>   number of past recurrence instances is always finite...
>>>
>>> 2- Remove EXDATE properties for any past recurrence instances.
>>>
>>> 3- Set DTSTART to the first recurrence instance to which you
>>>   want the change to apply.
>>>   
> So is original DTSTART lost completely?

The recurrence instance previously defined by DTSTART would become
a simple recurrence instance defined by an RDATE property. You
wouldn't be able to figure out what was the original DTSTART.

 > Doesn't this go against the
> statement, "However, in such cases the original "DTSTART" date MUST 
> still be maintained by the calendaring and scheduling system because the 
> original "DTSTART" value has inherent usage dependencies by other 
> properties such as the "RECURRENCE-ID"."

I would think that what really matter is that the set of RECURRENCE-ID
is maintained.

> If not, is there a standard way of maintaining it?
> Also, in multiple places it is stated "The "DTSTART" property defines 
> the first instance in the recurrence set". Will that be modified?

That would clearly need to be modified.

Cheers,
Bernard
> 
> Thanks,
> Ciny
> 
>>> The only issue here is that we need to clarify that RDATE can
>>> specify a value less than the value specified by DTSTART.
>>>
>>> Cheers,
>>> Bernard
>>>   
> 
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
> 



Return-Path: <bernard.desruisseaux@oracle.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id ACE2D808DE for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 21:07:23 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 12D10142202 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 21:06:29 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -2.309
X-Spam-Level: 
X-Spam-Status: No, score=-2.309 tagged_above=-50 required=4 tests=[AWL=0.289,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWjla6ArBFgd for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 21:06:22 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id AE8021421F6 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 21:06:22 -0800 (PST)
Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id lAE56KWO027337 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 23:06:20 -0600
Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id lADA1QKZ000569 for <ietf-calsify@osafoundation.org>; Tue, 13 Nov 2007 22:06:19 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-106-55.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 3364192171195016679; Tue, 13 Nov 2007 21:04:39 -0800
Message-ID: <473A81E6.4030002@oracle.com>
Date: Wed, 14 Nov 2007 00:04:38 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf-calsify@osafoundation.org
Subject: Section 4.8.7.4 Sequence Number [Re: [Ietf-calsify] Re: Ietf-calsify Digest, Vol 38, Issue 10]
References: <20070918190006.D4825802A3@leilani.osafoundation.org>	<46FD4C1D.1060801@sun.com> <E5A8403BFDBC7B88DB846818@caldav.corp.apple.com>
In-Reply-To: <E5A8403BFDBC7B88DB846818@caldav.corp.apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2007 05:07:23 -0000

Do we want to remove the text in section 4.8.7.4 Sequence Number of
RFC 2445 that specifies when the sequence number MUST be incremented
as Cyrus was "tempted to suggest"?

Cheers,
Bernard

Cyrus Daboo wrote:
> Hi Ciny,
> 
> --On September 28, 2007 11:46:53 AM -0700 Ciny Joy <Ciny.Joy@Sun.COM> 
> wrote:
> 
>>     So was their a conclusion on the SEQUENCE, DTSTAMP discussion? I am
>> especially interested in knowing which fields should be used to determine
>> the latest update received in iMIP. Also, is there a proposal to
>> standardize when these fields should be modified?
> 
> I am crafting a response to all the discussion that took place on this 
> recently.
> 
> My conclusions are the following:
> 
> 1) We do need SEQUENCE to properly allow an organizer to match up 
> responses from attendees with the latest revisions sent out by the 
> organizer.
> 
> 2) Clarify that SEQUENCE is not meant to be any kind of indicator to the 
> client that a response is needed. RSVP=TRUE must be used instead.
> 
> 3) Clarify that clients must determine for themselves what constitutes a 
> significant change to an event that would cause a new accept/decline 
> prompt to be presented to a user. Clients may treat a change in SEQUENCE 
> number as always causing a prompt, but should not rely solely on a 
> change of SEQUENCE number.
> 
> 4) Clarify under what circumstances SEQUENCE should change. There is 
> currently some text on that in 2445bis, but I am tempted to suggest that 
> really belongs in 2446bis in a single section dealing with SEQUENCE 
> issues. The text here would list some properties for which changes MUST 
> result in a sequence change, and others that MAY result in a change 
> depending on the exact nature of the property change. I don't think we 
> can go further than that.
> 
> I am working on putting together some text on this so that we can seek 
> consensus on these points.
> 



Return-Path: <timhare@comcast.net>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id BCA6D808CF for <ietf-calsify@osafoundation.org>; Sat, 10 Nov 2007 05:55:21 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 127DB142210 for <ietf-calsify@osafoundation.org>; Sat, 10 Nov 2007 05:54:27 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: 0.168
X-Spam-Level: 
X-Spam-Status: No, score=0.168 tagged_above=-50 required=4 tests=[AWL=-0.334,  BAYES_00=-2.599, DNS_FROM_RFC_POST=1.708, MSGID_FROM_MTA_ID=1.393]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiPZWq-Y9FBC for <ietf-calsify@osafoundation.org>; Sat, 10 Nov 2007 05:54:21 -0800 (PST)
Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by laweleka.osafoundation.org (Postfix) with ESMTP id D007B1421FF for <ietf-calsify@osafoundation.org>; Sat, 10 Nov 2007 05:54:20 -0800 (PST)
Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA10.westchester.pa.mail.comcast.net with smtp id B0QF1Y00617dt5G0004i00; Sat, 10 Nov 2007 13:54:20 +0000
Received: from THare ([71.203.100.120]) by OMTA13.westchester.pa.mail.comcast.net with comcast id B1uE1Y0022brFRz0000000; Sat, 10 Nov 2007 13:54:19 +0000
X-Authority-Analysis: v=1.0 c=1 a=PFsjAnyDAAAA:8 a=vhZX8rZXDXiGRdjmUM4A:9 a=wkb5aLYAyd-8kW5hZJYA:7 a=MUqRm-V3JLOFch614JiaTsDlRB4A:4 a=YewFc9KQ5U8A:10 a=7DSvI1NPTFQA:10 a=Cq1YcKPHAxQA:10
From: "Tim Hare" <TimHare@comcast.net>
To: "'Calsify WG'" <ietf-calsify@osafoundation.org>
Subject: RE: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request
Date: Sat, 10 Nov 2007 08:54:55 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-reply-to: <1194521121.5053.5.camel@scotty>
Thread-Index: Acgh+ivGxuKSmMesT32Kugp2Uxd/RwBptNCw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Message-Id: <20071110135420.D007B1421FF@laweleka.osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2007 13:55:21 -0000

DURATION is used in VFREEBUSY requests in the sense of "search for a
half-hour block of free time", at least according to my interpretation of
this paragraph in 3.6.4 of draft-ietf-calsify-rfc2445bis-07.txt

"When present in a "VFREEBUSY" calendar component, the "DTSTART"
      and "DTEND" properties SHOULD be specified prior to any "FREEBUSY"
      properties.  In a free time request, these properties can be used
      in combination with the "DURATION" property to represent a request
      for a duration of free time within a specified window of time." 

Since this is probably a fairly common use case when scheduling meetings,
the only choice that makes sense, in my opinion, is (b) .

To eliminate perceived vagueness, in the second sentence of the paragraph
from 3.6.4 we could change the wording to read:

"In a free tine request, the DTSTART, DTEND, and DURATION properties can be
used to represent a request to find a period of free time, of length
DURATION, within the period of time bounded inclusively by DTSTART and
DTEND."

It might also help to have one of the examples show that kind of request.

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: ietf-calsify-bounces@osafoundation.org
[mailto:ietf-calsify-bounces@osafoundation.org] On Behalf Of Aki Niemi
Sent: Thursday, November 08, 2007 6:25 AM
To: ext Cyrus Daboo
Cc: Calsify WG
Subject: Re: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request

[as chair]

Folks,

We need to resolve this issue, which to my knowledge is still pending.
Option a) below would require a change in rfc2445bis, which is almost done
now, so your input is needed *now*.

Cheers
Aki


ma, 2006-11-06 kello 07:25 -0800, ext Cyrus Daboo kirjoitti:
> Hi Bernard,
> 
> --On November 5, 2006 5:36:05 PM -0500 Bernard Desruisseaux 
> <bernard.desruisseaux@oracle.com> wrote:
> 
> >  > In a "VFREEBUSY" calendar component the property may be  > used 
> > to specify the interval of free time being requested.
> >
> > Yet, section 3.3.2 REQUEST of RFC 2446 (iTIP) specifies that the 
> > DURATION property is not allowed in a VFREEBUSY request.
> >
> > I see three options:
> >
> > a) Remove statement from iCalendar to be in sync with iTIP;
> >
> > b) Change iTIP to allow the DURATION property in a VFREEBUSY
> >     request and define the semantic as specified in iCalendar.
> >
> > c) Status quo.
> 
> We should rule out (c) as it represents an inconsistency between the 
> two specs. Note that 2445 does not clearly define what it means to 
> have DURATION present. e.g. is it allowed for the responder to only 
> return free times slots that are equal to or larger than the DURATION, 
> or should they still return the full list? If we can clearly specify 
> the behavior then I think (b) is reasonable, otherwise we have to do (a).
> 

_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify




Return-Path: <aki.niemi@nokia.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3967C80A62 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 04:14:25 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 82F1A14220D for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 04:13:30 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.648
X-Spam-Level: 
X-Spam-Status: No, score=-1.648 tagged_above=-50 required=4 tests=[AWL=0.751,  BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9LxTI663Fr4P for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 04:13:25 -0800 (PST)
Received: from mgw-ext12.nokia.com (smtp.nokia.com [131.228.20.171]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id AE4CD142207 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 04:13:24 -0800 (PST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA8CCpkR004900; Thu, 8 Nov 2007 14:13:17 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 8 Nov 2007 14:12:40 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 14:12:39 +0200
Received: from [172.21.41.182] (esdhcp041182.research.nokia.com [172.21.41.182]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA8CCch1010325; Thu, 8 Nov 2007 14:12:38 +0200
Subject: Next week's jabber chat. (was: Re: [Ietf-calsify] Calsify WG jabber chat)
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify@osafoundation.org
In-Reply-To: <1194521532.5053.7.camel@scotty>
References: <1194521532.5053.7.camel@scotty>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Thu, 08 Nov 2007 14:12:44 +0200
Message-Id: <1194523964.5053.9.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Nov 2007 12:12:39.0730 (UTC) FILETIME=[A832B920:01C82200]
X-Nokia-AV: Clean
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2007 12:14:25 -0000

Note that next week's jabber chat has been canceled. We will chat again
on Nov 21st, focusing on preparations for IETF70.

Cheers,
Aki


to, 2007-11-08 kello 13:32 +0200, ext Aki Niemi kirjoitti:
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



Return-Path: <aki.niemi@nokia.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 50C0E80AB5 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:33:41 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 97FA8142210 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:32:46 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.642
X-Spam-Level: 
X-Spam-Status: No, score=-1.642 tagged_above=-50 required=4 tests=[AWL=0.757,  BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzQ11pmD70Y1 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:32:40 -0800 (PST)
Received: from mgw-ext14.nokia.com (smtp.nokia.com [131.228.20.173]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 36160142207 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:32:39 -0800 (PST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA8BWSTg022418; Thu, 8 Nov 2007 13:32:35 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 8 Nov 2007 13:32:08 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh103.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 13:32:08 +0200
Received: from [172.21.41.182] (esdhcp041182.research.nokia.com [172.21.41.182]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA8BW65L007629; Thu, 8 Nov 2007 13:32:06 +0200
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify@osafoundation.org, Eliot Lear <lear@cisco.com>
Content-Type: text/calendar; name=calendar.ics; charset=utf-8; METHOD=REQUEST
Organization: Nokia-TP-MSW/Helsinki
Date: Thu, 08 Nov 2007 13:32:12 +0200
Message-Id: <1194521532.5053.7.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Nov 2007 11:32:08.0308 (UTC) FILETIME=[FEF52B40:01C821FA]
X-Nokia-AV: Clean
Subject: [Ietf-calsify] Calsify WG jabber chat
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2007 11:33:41 -0000

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:/softwarestudio.org/Tzfile/Europe/Helsinki
X-LIC-LOCATION:Europe/Helsinki
BEGIN:STANDARD
TZNAME:EET
DTSTART:19701026T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-2SU;BYMONTH=10
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
TZNAME:EEST
DTSTART:19700330T040000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:20071023T072226Z-6691-1000-1-1@scotty
DTSTAMP:20071108T113212Z
DTSTART;TZID=/softwarestudio.org/Tzfile/Europe/Helsinki:20071024T163000
DTEND;TZID=/softwarestudio.org/Tzfile/Europe/Helsinki:20071024T173000
TRANSP:OPAQUE
SEQUENCE:3
SUMMARY:Calsify WG jabber chat
LOCATION:xmpp:calsify@jabber.ietf.org
CLASS:PUBLIC
ORGANIZER;CN=Aki Niemi:MAILTO:aki.niemi@nokia.com
X-MICROSOFT-CDO-REPLYTIME:20071031T150125Z
CREATED:20071031T150125
LAST-MODIFIED:20071031T150125
RECURRENCE-ID;TZID=/softwarestudio.org/Tzfile/Europe/Helsinki:
 20071024T163000
DESCRIPTION:Weekly jabber chat for the Calsify WG. Template agenda: going 
 through and closing issues on the WG issue tracker:\n\nhttp:
 //www.ofcourseimright.com/cgi-bin/roundup/calsify\n
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=CHAIR;PARTSTAT=ACCEPTED;RSVP=TRUE;CN=Aki 
 Niemi;LANGUAGE=en:MAILTO:aki.niemi@nokia.com
ATTENDEE;CUTYPE=GROUP;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;LANGUAGE=en:MAILTO:ietf-calsify@osafoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=CHAIR;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;
 CN=Eliot Lear;LANGUAGE=en:MAILTO:lear@cisco.com
EXDATE;VALUE=DATE:20071205
EXDATE;VALUE=DATE:20071114
RRULE:FREQ=WEEKLY;UNTIL=20071231T143000Z;INTERVAL=1;BYDAY=WE
END:VEVENT
END:VCALENDAR



Return-Path: <aki.niemi@nokia.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 541C480A62 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:27:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 9CD1014220E for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:26:09 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.636
X-Spam-Level: 
X-Spam-Status: No, score=-1.636 tagged_above=-50 required=4 tests=[AWL=0.763,  BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQ+rfNmVsABt for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:26:04 -0800 (PST)
Received: from mgw-ext11.nokia.com (smtp.nokia.com [131.228.20.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id AB25D142207 for <ietf-calsify@osafoundation.org>; Thu,  8 Nov 2007 03:26:03 -0800 (PST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA8BPhxh011094; Thu, 8 Nov 2007 13:25:44 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 8 Nov 2007 13:25:20 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh103.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 13:25:19 +0200
Received: from [172.21.41.182] (esdhcp041182.research.nokia.com [172.21.41.182]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA8BPFE2001199; Thu, 8 Nov 2007 13:25:16 +0200
Subject: Re: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request
From: Aki Niemi <aki.niemi@nokia.com>
To: ext Cyrus Daboo <cyrus@daboo.name>
In-Reply-To: <9605B38742013AA84E9B408F@ninevah.local>
References: <454E6755.9040809@oracle.com> <9605B38742013AA84E9B408F@ninevah.local>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Thu, 08 Nov 2007 13:25:21 +0200
Message-Id: <1194521121.5053.5.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Nov 2007 11:25:19.0808 (UTC) FILETIME=[0B790400:01C821FA]
X-Nokia-AV: Clean
Cc: Calsify WG <ietf-calsify@osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2007 11:27:04 -0000

[as chair]

Folks,

We need to resolve this issue, which to my knowledge is still pending.
Option a) below would require a change in rfc2445bis, which is almost
done now, so your input is needed *now*.

Cheers
Aki


ma, 2006-11-06 kello 07:25 -0800, ext Cyrus Daboo kirjoitti:
> Hi Bernard,
> 
> --On November 5, 2006 5:36:05 PM -0500 Bernard Desruisseaux 
> <bernard.desruisseaux@oracle.com> wrote:
> 
> >  > In a "VFREEBUSY" calendar component the property may be
> >  > used to specify the interval of free time being requested.
> >
> > Yet, section 3.3.2 REQUEST of RFC 2446 (iTIP) specifies that
> > the DURATION property is not allowed in a VFREEBUSY request.
> >
> > I see three options:
> >
> > a) Remove statement from iCalendar to be in sync with iTIP;
> >
> > b) Change iTIP to allow the DURATION property in a VFREEBUSY
> >     request and define the semantic as specified in iCalendar.
> >
> > c) Status quo.
> 
> We should rule out (c) as it represents an inconsistency between the two 
> specs. Note that 2445 does not clearly define what it means to have 
> DURATION present. e.g. is it allowed for the responder to only return free 
> times slots that are equal to or larger than the DURATION, or should they 
> still return the full list? If we can clearly specify the behavior then I 
> think (b) is reasonable, otherwise we have to do (a).
> 



Return-Path: <aki.niemi@nokia.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id BC840808F6 for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:44:42 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 0FB83142212 for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:43:48 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.728
X-Spam-Level: 
X-Spam-Status: No, score=-1.728 tagged_above=-50 required=4 tests=[AWL=0.871,  BAYES_00=-2.599]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YF8lPb17BKmR for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:43:43 -0800 (PST)
Received: from mgw-ext13.nokia.com (smtp.nokia.com [131.228.20.172]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 30D71142203 for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:43:42 -0800 (PST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA7DhcMd016031 for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:43:39 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 7 Nov 2007 15:42:43 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 7 Nov 2007 15:20:16 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Nov 2007 15:20:15 +0200
Received: from [172.21.41.205] (esdhcp041205.research.nokia.com [172.21.41.205]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA7DK22I002132 for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:20:14 +0200
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify <ietf-calsify@osafoundation.org>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Wed, 07 Nov 2007 15:20:07 +0200
Message-Id: <1194441607.28623.0.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2007 13:20:15.0982 (UTC) FILETIME=[EF7FE8E0:01C82140]
X-Nokia-AV: Clean
Subject: [Ietf-calsify] Reminder: scheduled weekly jabber chat starting in 10 minutes
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2007 13:44:42 -0000


Return-Path: <aki.niemi@nokia.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C004F808BE for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:32:55 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 12968142203 for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:32:01 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-50 required=4 tests=[AWL=0.778,  BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jzkf5c6vTqCY for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:31:52 -0800 (PST)
Received: from mgw-ext14.nokia.com (smtp.nokia.com [131.228.20.173]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 0D562142212 for <ietf-calsify@osafoundation.org>; Wed,  7 Nov 2007 05:31:51 -0800 (PST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA7DVRCr015160 for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:31:48 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 7 Nov 2007 15:31:46 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 7 Nov 2007 15:26:02 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Nov 2007 15:26:01 +0200
Received: from [172.21.40.154] (esdhcp040154.research.nokia.com [172.21.40.154]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA7DPxUK009638 for <ietf-calsify@osafoundation.org>; Wed, 7 Nov 2007 15:25:59 +0200
From: Aki Niemi <aki.niemi@nokia.com>
To: ietf-calsify <ietf-calsify@osafoundation.org>
In-Reply-To: <1194441607.28623.0.camel@scotty>
References: <1194441607.28623.0.camel@scotty>
Content-Type: text/plain
Organization: Nokia-TP-MSW/Helsinki
Date: Wed, 07 Nov 2007 15:26:05 +0200
Message-Id: <1194441965.28623.3.camel@scotty>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2007 13:26:01.0549 (UTC) FILETIME=[BD793FD0:01C82141]
X-Nokia-AV: Clean
Subject: [Ietf-calsify] Correction: in *1 hour* and 5 minutes. (was: Re: Reminder: scheduled weekly jabber chat starting in 10 minutes)
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2007 13:32:55 -0000

(Sigh) :)




Return-Path: <andrew_dowden@softdesign.net.nz>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 81A9780A45 for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 21:01:15 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id C887F14220D for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 21:00:20 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.453
X-Spam-Level: 
X-Spam-Status: No, score=-1.453 tagged_above=-50 required=4 tests=[AWL=1.011,  BAYES_00=-2.599, FORGED_RCVD_HELO=0.135]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fuHK-r32GMxZ for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 21:00:14 -0800 (PST)
Received: from smtp22.ihug.co.nz (smtp22.ihug.co.nz [203.109.136.122]) by laweleka.osafoundation.org (Postfix) with ESMTP id BF843142203 for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 21:00:11 -0800 (PST)
Received: from cust.filter2.content.ihug.net.nz (smtp.mailfilter2.ihug.co.nz) [10.80.50.2] by smtp22.ihug.co.nz with esmtp (Exim 4.60 #1 (Debian); Ihug conf #192) id 1Ipd1N-0003JC-0b; Wed, 07 Nov 2007 18:00:09 +1300
Ironport-Content-Filter: send-to-smtp
Received: from 121-73-60-39.cable.telstraclear.net (HELO [127.0.0.1]) ([121.73.60.39]) by smtp.mailfilter2.ihug.co.nz with ESMTP; 07 Nov 2007 18:00:08 +1300
Message-ID: <47314658.4010502@softdesign.net.nz>
Date: Wed, 07 Nov 2007 18:00:08 +1300
From: Andrew N Dowden <andrew_dowden@softdesign.net.nz>
Organization: Dowden Software Associates
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf-calsify <ietf-calsify@osafoundation.org>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <471612F8.9020306@cisco.com> <47302DB0.1050207@cisco.com>
In-Reply-To: <47302DB0.1050207@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2007 05:01:15 -0000

Eliot Lear wrote:
>> This time I would like to suggest a solution for the case where
>> an organizer changes all future recurrence instances of a recurring
>> calendar component:
>>
>> 1- Specify RDATE properties for all past recurrence instances
>>    and define exception components for them if needed. The
>>    number of past recurrence instances is always finite...
>>
>> 2- Remove EXDATE properties for any past recurrence instances.
>>
>> 3- Set DTSTART to the first recurrence instance to which you
>>    want the change to apply.
>>
>> The only issue here is that we need to clarify that RDATE can
>> specify a value less than the value specified by DTSTART.
>>     
Is there anything wrong with? :

1- Specify RDATE properties for all past recurrence instances,
    while excluding those removed by EXDATE properties..
   ( The number of past recurrence instances is always finite. )

2- Remove any RRULE and EXDATE properties.

3- Set DTSTART to match the first RDATE property.

-- 
_______________________________________________

  SoftDesign Group
  Dowden Software Associates
  P O Box 31 132, Lower Hutt 5040, NEW ZEALAND



Return-Path: <Ciny.Joy@Sun.COM>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 257FA809DC for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 14:14:50 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 683B7142206 for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 14:13:55 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.383
X-Spam-Level: 
X-Spam-Status: No, score=-1.383 tagged_above=-50 required=4 tests=[AWL=1.215,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUCh2CtmBNFY for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 14:13:49 -0800 (PST)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 963C1142202 for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 14:13:49 -0800 (PST)
Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id lA6MDlVV012104 for <ietf-calsify@osafoundation.org>; Tue, 6 Nov 2007 14:13:49 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JR300E01V11O600@fe-sfbay-10.sun.com> (original mail from Ciny.Joy@Sun.COM) for ietf-calsify@osafoundation.org; Tue, 06 Nov 2007 14:13:47 -0800 (PST)
Received: from [192.18.126.79] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JR300L5GV2NASC0@fe-sfbay-10.sun.com> for ietf-calsify@osafoundation.org; Tue, 06 Nov 2007 14:13:35 -0800 (PST)
Date: Tue, 06 Nov 2007 14:14:56 -0800
From: Ciny Joy <Ciny.Joy@Sun.COM>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
In-reply-to: <20071106200005.569D080A03@leilani.osafoundation.org>
Sender: Ciny.Joy@Sun.COM
To: ietf-calsify@osafoundation.org
Message-id: <4730E760.4090309@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
References: <20071106200005.569D080A03@leilani.osafoundation.org>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20051027
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2007 22:14:51 -0000

>
>>
>>This time I would like to suggest a solution for the case where
>>an organizer changes all future recurrence instances of a recurring
>>calendar component:
>>
>>1- Specify RDATE properties for all past recurrence instances
>>   and define exception components for them if needed. 
>>
How do you define "if needed"?

>>The
>>   number of past recurrence instances is always finite...
>>
>>2- Remove EXDATE properties for any past recurrence instances.
>>
>>3- Set DTSTART to the first recurrence instance to which you
>>   want the change to apply.
>>    
>>
So is original DTSTART lost completely? Doesn't this go against the 
statement, "However, in such cases the original "DTSTART" date MUST 
still be maintained by the calendaring and scheduling system because the 
original "DTSTART" value has inherent usage dependencies by other 
properties such as the "RECURRENCE-ID"."
If not, is there a standard way of maintaining it?
Also, in multiple places it is stated "The "DTSTART" property defines 
the first instance in the recurrence set". Will that be modified?

Thanks,
Ciny

>>The only issue here is that we need to clarify that RDATE can
>>specify a value less than the value specified by DTSTART.
>>
>>Cheers,
>>Bernard
>>    
>>



Return-Path: <lear@cisco.com>
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 60FEE8071B for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 01:04:04 -0800 (PST)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id A53E914220D for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 01:03:09 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-50 required=4 tests=[AWL=0.529,  BAYES_00=-2.599, FORGED_RCVD_HELO=0.135, SPF_PASS=-0.001]
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jaxlulXOezz8 for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 01:03:03 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by laweleka.osafoundation.org (Postfix) with ESMTP id 78AAA14220C for <ietf-calsify@osafoundation.org>; Tue,  6 Nov 2007 01:03:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.21,377,1188770400"; d="scan'208";a="156985993"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 06 Nov 2007 10:02:59 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lA692xKe012868;  Tue, 6 Nov 2007 10:02:59 +0100
Received: from adsl-247-6-fixip.tiscali.ch (ams3-vpn-dhcp380.cisco.com [10.61.65.124]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lA692kqT022292;  Tue, 6 Nov 2007 09:02:46 GMT
Message-ID: <47302DB0.1050207@cisco.com>
Date: Tue, 06 Nov 2007 10:02:40 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: [Ietf-calsify] RFC 2445bis Issue 63: Consensus needed
References: <471612F8.9020306@cisco.com>
In-Reply-To: <471612F8.9020306@cisco.com>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2693; t=1194339779; x=1195203779; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[Ietf-calsify]=20RFC=202445bis=20Issue=2063=3A=20Cons ensus=20needed |Sender:=20; bh=SkvBzISSAe7XUyqoKiqeaaKjHEROBp9t9QKQSt7wpQ8=; b=c6tSaOriQRk5qXP2Gbd0Ldn5ksyaamfwlhHnq9ixpzsihhRwVMJTULV5IL9ZoN79LqIYWQcm AkdnAgUg7S5U60VxUnvcFzmwD38huTQ3zHU5CDziY6Zp/HCZiUZa7Ue1;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass (s ig from cisco.com/amsdkim1002 verified; ); 
Cc: "ietf-calsify@osafoundation.org" <ietf-calsify@osafoundation.org>
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2007 09:04:04 -0000

Bernard,

We have heard no discussion on your proposal.  Fair warning to all:
silence shall equal consent to the request below.

Eliot

Eliot Lear wrote:
> Dear all,
>
> On August 3rd, Bernard tried for the third time to gain consensus on
> this topic.  Please comment now.  We would like to close RFC2445bis and
> this is one of several niggling points remaining.
>
> Please state your preference as to which solution below you prefer.
>
> Thank you,
>
> Eliot
>   
>
> ------------------------------------------------------------------------
>
> Subject:
> [Ietf-calsify] Issue 63: Section 4.8.5.3 Recurrence Date/Times: RDATE
> < DTSTART
> From:
> Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
> Date:
> Fri, 03 Aug 2007 17:22:51 -0400
> To:
> Calsify WG <ietf-calsify@osafoundation.org>
>
> To:
> Calsify WG <ietf-calsify@osafoundation.org>
>
>
> Disclaimer: This is the third time I bring up this issue. See:
>
> http://lists.osafoundation.org/pipermail/ietf-calsify/2006-November/001349.html
>
> http://lists.osafoundation.org/pipermail/ietf-calsify/2007-February/001522.html
>
>
> Cyrus recently brought up the fact that the deprecation of
> RANGE=THISANDFUTURE (Issue 48) might be an issue with unbounded
> recurring calendar components in the context of iTIP.
>
> I have already suggested a solution for the case where an
> organizer cancels all future recurrence instances of a
> recurring calendar component.  See:
>
> http://lists.osafoundation.org/pipermail/ietf-calsify/2007-July/001746.html
>
>
> This time I would like to suggest a solution for the case where
> an organizer changes all future recurrence instances of a recurring
> calendar component:
>
> 1- Specify RDATE properties for all past recurrence instances
>    and define exception components for them if needed. The
>    number of past recurrence instances is always finite...
>
> 2- Remove EXDATE properties for any past recurrence instances.
>
> 3- Set DTSTART to the first recurrence instance to which you
>    want the change to apply.
>
> The only issue here is that we need to clarify that RDATE can
> specify a value less than the value specified by DTSTART.
>
> Cheers,
> Bernard
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>   

