IETF Logo Mail Archive

Re: [calsify] draft-gondwana-caldav-scheduling-controls

"Bron Gondwana" <brong@fastmailteam.com> Sat, 23 March 2019 10:29 UTC

Return-Path: <brong@fastmailteam.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 CEC55127AC2 for <calsify@ietfa.amsl.com>; Sat, 23 Mar 2019 03:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=R4wLK1ar; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nyOxZISE
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 tjtNcLKBcHDD for <calsify@ietfa.amsl.com>; Sat, 23 Mar 2019 03:29:53 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18F3312D4F2 for <calsify@ietf.org>; Sat, 23 Mar 2019 03:29:53 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 529B238A7; Sat, 23 Mar 2019 06:29:52 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Sat, 23 Mar 2019 06:29:52 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=MJIqj79 EJftbzueZeREtI+SxfRXeWe0eQe27FlLm8nQ=; b=R4wLK1artqriQ0a9p4Xb7+m 7nDdi72+IMu2SZ8XIwF/vRIUCq2MntpBj1YQJ8DhD3eCEK2InZbzIcJ75de9eJdH OmJXYtLvHKcpH0qEvIF0yAobx/bI3j8h9GpA3pE5NyU5+hh/Al61Doj9uPJ/PRi7 8PgYkXHaKZY0aUAR69/t0xtyx6a8OMx+7+DCBuZdVKCd+viXqeP2DeKR0gKPDE2L loVKjPlwcnJSc1RCgkq8gZAh/yF3zxOmPDYvmv0VDvPWmE2uCHKXChOdq6GfHmwc WFvgZOf3caLob0y3omkWaqAuzPUmw6CJPcqGSFMmynN4SaCh697HWOlNN08WkQQ= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=MJIqj7 9EJftbzueZeREtI+SxfRXeWe0eQe27FlLm8nQ=; b=nyOxZISEM/wr6bYY2uC6Wr 3X/eBRAK4Xo5+MInnP7q471tWS5AnDPcp1QlxHZQirWFa8LkBowLfAjd5hA9albd xBF9MEn8snA5kz2ntL6QlXTVoxHdBPI5qezag0XHFX4+5kis627U4sxqyaT1qW74 Yi1/E+KbFm6hP9C4BGTZ0TbnVjLbV0KVAO5VXdyc7z9mrHSqo+7JV3Mo04OSQQk0 Y95jloNc6cnYJmiL4oMUlipYLcnwGjQRCJPWEkZhqGkJcksi4LtaYTeGrqpEPSJB p5Vj7YSPztGRjZWp6kRcQyFFsHkq/XDHiUan3Ljm9Fx3SDvnl5tN085OWHTLXiGg ==
X-ME-Sender: <xms:nwqWXHGC7jEf9vvaY1il6qQgKcPFS9Mkux4IxRelqps9iFEkaDDdcA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrjeefgddujecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuffhomhgrihhnpehivghtfhdrohhrghenuc frrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:nwqWXNYFWiOexvJUzK6wtmIIwZ_n2PAygzSQ990v102NUjb4nf8QGg> <xmx:nwqWXCMdR-jglQHBKZ6LTPtgdBpXN6avqkrdiDoOgP3dva5ilDE4wQ> <xmx:nwqWXA1ZmyE_yNtiudFWdZaF4Eahq-d9YSLE0l6c3vsh-GkIDu4Sag> <xmx:nwqWXNkoreNf0hthbFJzJCYduN3pk5IS4eD8ezsJhimI5BbfA5mUEA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7258620617; Sat, 23 Mar 2019 06:29:51 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-976-g376b1f3-fmstable-20190314v3
Mime-Version: 1.0
X-Me-Personality: 56629417
Message-Id: <45d24d8d-0f39-41f4-bd43-1966d2e36892@www.fastmail.com>
In-Reply-To: <b494657f65e736d68082a9db2f78f9143d6c2cb1.camel@aegee.org>
References: <f2e29443-b5bb-42d3-bf42-6865a46ab5cf@www.fastmail.com> <b494657f65e736d68082a9db2f78f9143d6c2cb1.camel@aegee.org>
Date: Sat, 23 Mar 2019 06:29:47 -0400
From: Bron Gondwana <brong@fastmailteam.com>
To: Дилян Палау зов <dilyan.palauzov@aegee.org>, calsify <calsify@ietf.org>
Content-Type: multipart/alternative; boundary="c217ab4885134138950d534c3765efd7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/1L5xg5Kz8JhwlnQjbHxVkClyWN8>
Subject: Re: [calsify] draft-gondwana-caldav-scheduling-controls
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 23 Mar 2019 10:29:55 -0000

On Sat, Mar 9, 2019, at 06:00, Дилян Палаузов wrote:
> Hello Bron,
> 
> irrespective of the WG-addoptation, CALDAV:calendar-user-address-set (https://tools.ietf.org/html/rfc6638#section-2.4.1)
> defines per principal all the aliases a user has, so the server does not have to guess anything.
> 
> When the Schedule-User-Address header is skipped, your draft says, that the CALDAV:schedule-user-address property on a
> calendar or user/principal shall be used. The draft references only RFC6638 “Scheduling Extensions to CalDAV” and the
> latter does not say anything about CALDAV:schedule-user-address. Where is CALDAV:schedule-user-address defined?
> 
> Are CALDAV:schedule-user-address and CALDAV:calendar-user-address-set supposed to mean the same?

Yes - I expect that was an early mistake that I just didn't notice. Oops. I'll fix that up in the next one.

> In any case, it would be good to be able to specify several addresses in the Schedule-User-Address header: an invitation
> having Organizer and Attendee, where the same person is both the organizer and the attendee, but uses different
> addresses for both, is supposed not to trigger any scheduling to the same person. This assumes that the system can
> match the addresses as Attendee and Organizer belonging to the same person and both addresses could arrive as headers.

The server will always have you acting as a particular user when you're updating the record - but yeah, to avoid scheduling to multiple addresses makes sense. This will also be something interesting to discuss in JMAP calendars.

Bron.

--
 Bron Gondwana, CEO, FastMail Pty Ltd
 brong@fastmailteam.com

v2.23.0 | Report a Bug | By Email