Re: [calsify] Shepherd Review of draft-ietf-calext-caldav-attachments

[Cyrus Daboo <[e-mail]>]

Hi Philipp,
Thanks for you review.

--On April 13, 2017 at 12:05:55 PM +0200 Philipp Kewisch <[e-mail]> 
wrote:

>>    Specific instance  A specific iCalendar instance is targeted by using
>>       its "RECURRENCE-ID" value as the item value.  That value MUST
>>       correspond to the RECURRENCE-ID value as stored in the calendar
>>       object resource (i.e. without any conversion to UTC).  If multiple
>>       items of this form are used, they MUST be unique values.
> Can you clarify why you chose to not allow specifying this value in any
> form, so that the server does timezone translation if needed?

I think we wanted to avoid the need for the server or client to have to do 
any conversions, which could prove problematic particularly if the time 
zone definitions the client and server have differ (which was something 
that could happen at the time we wrote the initial spec, but is now less 
likely to happen with the time zones by reference feature).

>>        D.  Upon successful creation of the attachment resource, and
>>            modification of the targeted calendar object resource, the
>>            server MUST return an appropriate HTTP success status
>>            response and include a "Cal-Managed-ID" header field
>>            containing the "MANAGED-ID" parameter value of the newly
>>            created "ATTACH" property.
> Any specific reason to shorten "Calendar" to "Cal" here?

I don't recall any specific version for that choice. However, it would be 
best not to change that given that existing deployments do make use of it.

>>  Malicious content could be introduced into the Calendar Server by way
>>    of a managed attachment, and propagated to many end users via
>>    scheduling.  Servers SHOULD check managed attachments for malicious
>>    or inappropriate content.  Upon detecting of such content, servers
>>    SHOULD remove the attachment, following the rules described in
>>    Section 3.12.5.
> "Calendar Server" should probably be lowercase here, as you are not
> referring to a specific product.

Agreed. Ken can make that change.

-- 
Cyrus Daboo