Re: [calsify] draft-ietf-calext-jscalendar and participants
Neil Jenkins <neilj@fastmailteam.com> Mon, 15 February 2021 23:06 UTC
Return-Path: <neilj@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 BF22C3A12B7
for <calsify@ietfa.amsl.com>; Mon, 15 Feb 2021 15:06:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001,
URIBL_BLOCKED=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=DLVDpKMM;
dkim=pass (2048-bit key)
header.d=messagingengine.com header.b=LXEJQ3ep
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 Rfx26ZbLrtvv for <calsify@ietfa.amsl.com>;
Mon, 15 Feb 2021 15:06:53 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
[66.111.4.25])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id CE69B3A12B4
for <calsify@ietf.org>; Mon, 15 Feb 2021 15:06:53 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
by mailout.nyi.internal (Postfix) with ESMTP id F05355C00AE
for <calsify@ietf.org>; Mon, 15 Feb 2021 18:06:52 -0500 (EST)
Received: from imap7 ([10.202.2.57])
by compute3.internal (MEProxy); Mon, 15 Feb 2021 18:06:52 -0500
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=/nw+zl3
qcS/6UTLIH0wZ15GBtFQma5if751sCLjHGZA=; b=DLVDpKMMkkIKGBZrOGukp39
nEbERVW8cLef30jWCNoGw7zzaAsDpea7b3EOiUoBUFzYG5o7fmoxB9HmM/Yaefxu
leTRpxaCzZ4Bj4IrODn93f1jHQADqbzDeP1QCJCIi/q95v6OiZe6nTzvaMy82opr
XAAHFfMSDV6lu6Hn00d0giirwpv85gVe8QnuNcfiwjO0HQA8onCnaqTrzn21BdLL
SYJ4ChQgsspzKfBg6RpkQpD6KvGo87ijlepzwxNFn1Ik63IXbMKAgMTLBamUuyph
SKflDyAPwmzin+dyhLS8XyymttEtFlate5sE4SzFqzcaml8lEzztKMNZuGiwqVA=
=
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=/nw+zl
3qcS/6UTLIH0wZ15GBtFQma5if751sCLjHGZA=; b=LXEJQ3epIyBsFKzrGJwDwI
o7K3FdKS05XbI1MPor3zheFMQOTjOHa+5xq+auE3MGgWYB5E352lZFhK8XKoZgCx
Jk3MHlwrnp7y+ixjpUfILMqqtiOXSyGDpFV69qF4VWCyYIjYBnC3vafUI5b2n53P
z4GJ6yLjSUQ0eAH2ah8DbPnIwex8z+MOkkPAVGiwV0Yc+C4nF42qIqXEAeC4augE
6Huri9QIiuPlfhWJ3Gutvz1g7lhwTGzeZBKS5ne3hgTwjm73prH3TxNU75gxZev1
qyo9sPc3eLwV3BEXjtc0G7ZqDXUXAe5SCPlaiS4mdz4CIRuLDHMwVF7j4fFHLGcQ
==
X-ME-Sender: <xms:jP4qYPNjyeD-IIUpk0KJGQWjfcqI3cXzmqTSX6Q__5SKM2RpBi76_g>
<xme:jP4qYJ_8hcuzdGEHzg9av-sdHzXzjzyx5m3Ur5QGHzJTuFL8VuXA3G8BP3Tv5Yfby
rPbiOJovC4h3Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrieelgddtiecutefuodetggdotefrodftvf
curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre
erreerjeenucfhrhhomhepfdfpvghilhculfgvnhhkihhnshdfuceonhgvihhljhesfhgr
shhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeehuefhudejtdeive
ekvdfhfffgleeflefhfeekhefhkeelkefhfeeufeevffejieenucevlhhushhtvghrufhi
iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghilh
htvggrmhdrtghomh
X-ME-Proxy: <xmx:jP4qYOTB98TNAseBBo6IfhtZvYMp-_h4dzeVzjqirHP_g7G1gNEw9w>
<xmx:jP4qYDvSwzDshsc-0fQPq-DuJBb8Tmu6yYB8yPflY3u218zfYv1C5g>
<xmx:jP4qYHdJ6eafC7fr1BL1gDyuaPOf-mTBVKZmvC5NZJNHx8imxVLZnQ>
<xmx:jP4qYBo6efpWryir_gCmAADiyfWxb5wfXRrcNmS1V665Jgo5AMQJZw>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
id ABB8836005C; Mon, 15 Feb 2021 18:06:52 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <f3631111-c3d7-46e1-b83a-2e994621a799@dogfood.fastmail.com>
In-Reply-To: <cf63883d-e134-62ea-3e53-af6945b755e1@gmail.com>
References: <cf63883d-e134-62ea-3e53-af6945b755e1@gmail.com>
Date: Tue, 16 Feb 2021 10:06:52 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=8c947e03e0934295aab56321ba68ac5f
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/g8bjm7JJJQyUfyXNPzhX4eo0IKA>
Subject: Re: [calsify] draft-ietf-calext-jscalendar and participants
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: Mon, 15 Feb 2021 23:06:56 -0000
On Tue, 16 Feb 2021, at 04:29, Michael Douglass wrote:
> I ran into a problem mapping iCalendar ATTENDEE onto jscalendar participants.
> For example I might have an ATTENDEE that looks like
> ATTENDEE;CN=Michael Douglass;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=mikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/
> The value is a URI but certainly not an email address.
> Additionally the value is used as a unique key to the attendee - something we don't have clearly defined in jscalendar.
Unless I'm missing something, that's just the participant id (i.e. the key in the participants object).
> I suggest we add a calendarAddress property which maps on to the value of the ORGANIZER or ATTENDEE properties.
I don't see the purpose of this proposed property.
> The "calendarAddress" and "email" properties can then match the behavior specified for the EMAIL parameter and ORGANIZER/ATTENDEE values -
> Description: This property parameter MAY be specified on "ORGANIZER"
or "ATTENDEE" properties. This property can be used in situations
where the calendar user address value of the "ORGANIZER" and
"ATTENDEE" properties is not likely to be an identifier that
recipients of scheduling messages could use to match the calendar
user with, for example, an address book entry. The value of this
property is an email address that can easily be matched by
recipients. Recipients can also use this value as an alternative
means of contacting the calendar user via email. If a recipient's
calendar user agent allows the recipient to save contact
information based on the "ORGANIZER" or "ATTENDEE" properties,
those calendar user agents SHOULD use any "EMAIL" property
parameter value for the email address of the contact over any
mailto: calendar user address specified as the value of the
property. Calendar user agents SHOULD NOT include an "EMAIL"
property parameter when its value matches the calendar user
address specified as the value of the property.
>
> While I appreciate the intent of the jscalendar sendTo I'd suggest it's in general unnecessary to specify iMip - iMip is sending email with a calendar attachment and it goes to the email address.
No, there is a difference:
* Participant email property: this is the person's email address and can be used if you want to send them an email.
* sendTo imip property: the user a) accepts calendar updates via iMIP; b) at this address (which may or may not be the same as the email – it may be a calendar-specific address that's just used for iMIP).
> Additional to all this I realised there is no clear mapping for the SENT-BY parameter. This is used on ATTENDEE and ORGANIZER when somebody else sends on behalf of the participant. I suggest we add a "sentBy" jscalendar property for participants.
Sure.
> I believe there's no mapping for the jscalendar "invitedBy" from iCalendar - is that so?
Potentially not, we can register a new iCalendar property.
Neil.
- [calsify] draft-ietf-calext-jscalendar and partic… Michael Douglass
- Re: [calsify] draft-ietf-calext-jscalendar and pa… Neil Jenkins
- Re: [calsify] draft-ietf-calext-jscalendar and pa… Robert Stepanek
- Re: [calsify] draft-ietf-calext-jscalendar and pa… Neil Jenkins
- Re: [calsify] draft-ietf-calext-jscalendar and pa… Michael Douglass