Re: [ischedule] Fwd: I-D Action:draft-desruisseaux-ischedule-01.txt

Bernard Desruisseaux <bernard.desruisseaux@oracle.com> Thu, 01 April 2010 19:13 UTC

Message-ID: <4BB4F048.3090100@oracle.com>
Date: Thu, 01 Apr 2010 15:13:12 -0400
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 OracleBeehiveExtension/1.0.0.0pre5 Thunderbird/3.0.3
MIME-Version: 1.0
To: Mike Douglass <douglm@rpi.edu>
References: <4B96714C.6030103@oracle.com> <4BB4B6F7.7050902@rpi.edu>
In-Reply-To: <4BB4B6F7.7050902@rpi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ischedule@ietf.org
Subject: Re: [ischedule] Fwd: I-D Action:draft-desruisseaux-ischedule-01.txt
Precedence: list

On 4/1/2010 11:08 AM, Mike Douglass wrote:
> Minor type:
>
> Section 6.1 POST method
>
>     ATTENDEE property depending on the specify METHOD property value as
>
> should be
>
>     ATTENDEE property depending on the specified METHOD property value as
>    

Thanks!

>
> Also a question of clarification:
>
> I'm assuming it's the responsibility of the sender to tailor the REQUEST
> for recurring meetings depending upon the attendees presence or
> otherwise, e.g. add exdates or whatever.
>    

Correct.

> Is it worth being explicit about that given that we can send to multiple
> recipients?
>    

Perhaps we could copy the following text from CalDAV scheduling:

http://tools.ietf.org/html/draft-desruisseaux-caldav-sched-08#section-5.2.6

Cheers,
Bernard

[ischedule] Fwd: I-D Action:draft-desruisseaux-is… Bernard Desruisseaux
Re: [ischedule] Fwd: I-D Action:draft-desruisseau… Mike Douglass
Re: [ischedule] Fwd: I-D Action:draft-desruisseau… Bernard Desruisseaux