Re: request + add

Michael Fair wrote:

> 
> So reconstructing Attendee-2's CS if it did not receive messages a or b
> (SEQ:0 and 1 respectively) the CUA will look in its store for UID:XXX and
> not find it.
> 
> The results are undefined.
> 
> However, consistent with iTIP's mandate to handle lost and missequenced
> messages it should treat the ADD like a REQUEST and then since it obviously
> is missing data (as evidneced by both a SEQ:2 and that it has just received
> an ADD for a non-existant event (i.e. way out of context for the UID)) it
> sends a REFRESH request to the ORGANIZER.

Okay, now what if it gets the sequence:1 request and the sequence:2
'add'
as shown in 'B'. As all three instances can not be represented in
one 'method request' object because the duration of all three instances
are not the same. Now the master object is at sequence:2, as is
attendee-2.

The recurrence-id's can be calculated from what attendee-2 has. Correct?
And it will be the same recurrence-id's as organizer. Correct?