Re: [calsify] I-D Action: draft-ietf-calext-caldav-attachments-02.txt

Tobias Friedrich <tf@ox.io> Wed, 15 March 2017 14:17 UTC

Return-Path: <tf@ox.io>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 335E4131576 for <calsify@ietfa.amsl.com>; Wed, 15 Mar 2017 07:17:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ox.io
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xyW0hC7qV5UT for <calsify@ietfa.amsl.com>; Wed, 15 Mar 2017 07:17:20 -0700 (PDT)
Received: from oxmailout01.ox.io (oxmailout01.ox.io [91.223.20.31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A028131525 for <calsify@ietf.org>; Wed, 15 Mar 2017 07:17:19 -0700 (PDT)
Received: from localhost (oxmailout01.mgmt.heinlein-hosting.de [91.223.20.31]) by oxmailout01.ox.io (Postfix) with ESMTP id BAC5A2406AD for <calsify@ietf.org>; Wed, 15 Mar 2017 15:17:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ox.io; h= content-transfer-encoding:content-type:content-type:mime-version :subject:subject:references:in-reply-to:message-id:reply-to:from :from:date:date:received:received; s=main; t=1489587436; bh=bluX 1ihXuwwS9V6QnTOsE8JeNKLQAKrL7he/bmo+WNY=; b=G/ly62FX9jopnY390/YA GuoKbKTmSKcbxQEww33Kulk9nvV+3ynVdrkE/yBrhcZ4sAFpLAyopCCyjAe4/T5M D/HAGb92QI6c13q4sDbCozCZZDPprbYxz+n/dnoDcyrIoSA0sxFWBDcWboXSLvAm VhdWrPLiU/COy6LgGImR/Wo=
X-Virus-Scanned: amavisd-new at ox.io
Received: from smtp2.mailbox.org ([80.241.60.241]) by localhost (mailout01.ox.io [91.223.20.31]) (amavisd-new, port 10024) with ESMTP id 8anyEeLv8hjM for <calsify@ietf.org>; Wed, 15 Mar 2017 15:17:16 +0100 (CET)
Received: from ox01.ox.io (unknown [10.192.4.30]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.ox.io (Postfix) with ESMTPSA id DC6FA276 for <calsify@ietf.org>; Wed, 15 Mar 2017 15:17:16 +0100 (CET)
Date: Wed, 15 Mar 2017 15:17:16 +0100
From: Tobias Friedrich <tf@ox.io>
Reply-To: Tobias Friedrich <tf@ox.io>
To: calsify@ietf.org
Message-ID: <154978740.4223.1489587436644@app.ox.io>
In-Reply-To: <148943479822.20333.15175294910025553176@ietfa.amsl.com>
References: <148943479822.20333.15175294910025553176@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
Importance: Medium
X-OX-Guard-Marker: false
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/PVTm1-Sno-Plj7iUNR6s5XVx_YI>
Subject: Re: [calsify] I-D Action: draft-ietf-calext-caldav-attachments-02.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2017 14:20:29 -0000

We at Open-Xchange are supporting "calendar-managed-attachments", too.

Two smaller issues in the draft I stumbled across:

3. Overview: 
> In the case of the remove operation, the client can alternatively directly update the calendar object resource and remove the relevant "ATTACH" properties.

Guess a reference to the other alternative (action=attachment-remove) is missing here?

3.1 Requirements / 3.4., 3.5, 3.6 Adding, Updating, Removing Attachments
> ... such a server MUST support the "return=representation" Prefer header field value...
vs.
> ... If the client included a Prefer header field with the "return=representation" preference in the request, the server SHOULD return ... 

MUST or SHOULD?

Apart from that, the spec appears to be in a final state.

Tobias 


> internet-drafts@ietf.org hat am 13. März 2017 um 20:53 geschrieben:
> 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Calendaring Extensions of the IETF.
> 
>         Title           : CalDAV Managed Attachments
>         Authors         : Cyrus Daboo
>                           Arnaud Quillaud
>                           Kenneth Murchison
> 	Filename        : draft-ietf-calext-caldav-attachments-02.txt
> 	Pages           : 33
> 	Date            : 2017-03-13
> 
> Abstract:
>    This specification defines an extension to the calendar access
>    protocol (CalDAV) to allow attachments associated with iCalendar data
>    to be stored and managed on the server.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-calext-caldav-attachments/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-calext-caldav-attachments-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-caldav-attachments-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>