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

[Philipp Kewisch <[e-mail]>]

Hello All,

I've gotten around to finishing my review on this document. Aside from a
minor typo, I have two simple questions, just to clarify out of personal
interest:

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

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


I've added the shepherd writeup to the datatracker, there were no
irregularities. With those questions clarified I think this is good to
go. Thank you for working on this document, I am looking forward to
having it published.

Kind Regards,
Philipp