Re: [calsify] Ben Campbell's No Objection on draft-ietf-calext-caldav-attachments-03: (with COMMENT)

Ben Campbell <ben@nostrum.com> Thu, 17 August 2017 01:18 UTC

Return-Path: <ben@nostrum.com>
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 491FB132391; Wed, 16 Aug 2017 18:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vaqodUFpvcTx; Wed, 16 Aug 2017 18:18:44 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC1A126BF0; Wed, 16 Aug 2017 18:18:44 -0700 (PDT)
Received: from [10.0.1.63] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v7H1IUNV071338 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 16 Aug 2017 20:18:35 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.63]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <AC41C565FCAA862101F32B29@cyrus.local>
Date: Wed, 16 Aug 2017 20:18:30 -0500
Cc: The IESG <iesg@ietf.org>, draft-ietf-calext-caldav-attachments@ietf.org, mozilla@kewis.ch, calext-chairs@ietf.org, calsify@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD3A1D81-71F0-48D7-B6D3-C7DA63AD5400@nostrum.com>
References: <150292180466.12103.5598790566803871517.idtracker@ietfa.amsl.com> <AC41C565FCAA862101F32B29@cyrus.local>
To: Cyrus Daboo <cyrus@daboo.name>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/8O3zCl8xNuYZJKJhrcY56-1g-oM>
Subject: Re: [calsify] Ben Campbell's No Objection on draft-ietf-calext-caldav-attachments-03: (with COMMENT)
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: Thu, 17 Aug 2017 01:18:48 -0000

> On Aug 16, 2017, at 6:02 PM, Cyrus Daboo <cyrus@daboo.name> wrote:
> 
> Hi Ben,
> 
> --On August 16, 2017 at 3:16:44 PM -0700 Ben Campbell <ben@nostrum.com> wrote:
> 
>> - 3.12.2: "Access to the managed attachments store in a calendar object
>> resource    SHOULD be restricted to only those calendar users who have
>> access to    that calendar object either directly, or indirectly (via
>> being an    attendee who would receive a scheduling message)."
>> 
>> Why not MUST? When might it make sense to allow others to access
>> attachments?
> 
> Well there are several different ways in which a calendar user might have access to another calendar users' data - such as delegation and sharing. But perhaps that is implied by the statement above. How about (with one typo fixed too):
> 
>  Access to the managed attachments stored in a calendar object resource
>  MUST be restricted to only those calendar users who are authorized to
>  access that calendar object either directly, or indirectly (via being
>  an attendee who would receive a scheduling message).

That works for me. (Although I would have also been happy with a SHOULD along with some guidance on when it might make sense to do otherwise.)

> 
> (If the above is acceptable I will leave it to Ken to make the change since he has the "edit token". Or Alexey can add as an RFC editor note.)
> 
> -- 
> Cyrus Daboo
>