
From nobody Mon Feb  1 07:38:48 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 974FE3A1208; Mon,  1 Feb 2021 07:38:46 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <161219392657.4989.687987386609600348@ietfa.amsl.com>
Date: Mon, 01 Feb 2021 07:38:46 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/AW79pRDqral_Db1OJSL-fTia2m0>
Subject: [calsify] I-D Action: draft-ietf-calext-valarm-extensions-04.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Feb 2021 15:38:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : VALARM Extensions for iCalendar
        Authors         : Cyrus Daboo
                          Kenneth Murchison
	Filename        : draft-ietf-calext-valarm-extensions-04.txt
	Pages           : 16
	Date            : 2021-02-01

Abstract:
   This document defines a set of extensions to the iCalendar VALARM
   component to enhance use of alarms and improve interoperability
   between clients and servers.

   This document updates RFC5545.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-calext-valarm-extensions-04
https://datatracker.ietf.org/doc/html/draft-ietf-calext-valarm-extensions-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-valarm-extensions-04


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/



From nobody Mon Feb  1 07:39:54 2021
Return-Path: <murch@fastmail.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 5FA0D3A1209; Mon,  1 Feb 2021 07:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=fastmail.com header.b=DSXLtlaa; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=U5PJWAvp
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 I6QsXkoFOIff; Mon,  1 Feb 2021 07:39:51 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE7653A1208; Mon,  1 Feb 2021 07:39:50 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id A9993B00; Mon,  1 Feb 2021 10:39:49 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 01 Feb 2021 10:39:49 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:from:to:cc:references:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=o 6XC1T/UmkVekZYEU4F086QiGFSQ38ZLlWLK7luCPXU=; b=DSXLtlaaPa4fVWOpD QuvzP8Te0yqlPCidIeRdG2ilNTpBDLeIkvGQbvRQT4qTJmGj/EgE+v6ShLqWydY4 bJ7822kUfFABE7yuX1nn+cH+5uCO90kmrXleAvJQa11ycDQE8sVs7jVlSQUZxq6X nIJMB7JPnJrMPkhBvT8roZaGxuHkgWG1/Qo1V8kEVUMDEDHS4kg34fbqTtX+J437 9CjzD9PeGYYqQxcoAAgWZ1uRzRyR9P/o+nSNLAkz/R4wBX6FLdw8Zn8aCExKZjR7 nzNc3xM0+aZelvquJE/k9k3NhQGJ5PEm4J3uaFAoGz3gUPTRubiYk8Fd6cmS6YEq a48Pw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm1; bh=o6XC1T/UmkVekZYEU4F086QiGFSQ38ZLlWLK7luCP XU=; b=U5PJWAvpyIJdRthKFlEgcSI+7hIiAldD4sxwO8KzwpGwVda2+GV38Tuq5 wYwG9piODw/ml0ZPwm0Kpm2yvkIKhzawax+6csB5RfZ+DraVsNUaQhI7JH0HpLuR VNdzeFgpeLHsVM3RSrOeeMWxqy+RrHeR9QZ0WYabPjex/0xjQnq9RO7CwS1mV1fV 2aUXeKKvFECZA+t7ANNOSwTghHRjQ9uG1glSrzkoMc89E/zPNzHZ0Mq5feEg2ida Mfpq+T4Y/RIli6tHATvapRKnGYT4+D9VC1kJMM4wByLPPbJwC1zw33fCM7FXeIzy EOCAZQCG2ucXFg31amrMtS/Rpegig==
X-ME-Sender: <xms:xCAYYEJXGbkBHX8wZ-qJnNdulgr1hblGnxuTLmnfW5MoywEkMYCYpg> <xme:xCAYYEKP_YhNdAa_AvczQWiOFlmsR_dCIRBsoONH8M-yXc5MZp0XvWnwZpKqWG-qo mwiSktxLmYb_g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeekgdejlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuhffvfhfkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpeejgfeufeegudefieetvdefjeevhfejhedtvedtfeeuffefieeggfdugfdv keekffenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeejgedrjeejrdekhedrvd ehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm uhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:xCAYYEuj42YU1HfUEyYZi7B4PBqYPea8qugP5L7amOIILVsRXW6rqA> <xmx:xCAYYBZVqSt-looy1f-rjDOgK5SruH9vSFzRwjwF6Z43HKuCwut-4Q> <xmx:xCAYYLbCFnpJnibC1detfGVH-IBYK4YMbq-WlysGBgHN9X0-AogvCA> <xmx:xSAYYCytMd4J-89yUHsWfm6kP7LrLd_q6NemXKR-7eDKu7wtziWNVg>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 4DA541080069; Mon,  1 Feb 2021 10:39:48 -0500 (EST)
From: Ken Murchison <murch@fastmail.com>
To: Cyrus Daboo <cyrus@daboo.name>, Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <6b55aa41-0153-3335-d053-f8bf084a2938@fastmail.com> <a5ba5dea-7f86-4231-aa0f-31f82d82a6d9@cyrus.local> <aef47d99-431e-e683-e012-974c321f9569@fastmail.com>
Message-ID: <0b89afb0-e15d-75f9-5b2a-2b2befdcd740@fastmail.com>
Date: Mon, 1 Feb 2021 10:39:47 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <aef47d99-431e-e683-e012-974c321f9569@fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/uTckigw5ygARCoz8B6BswXxz5hY>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
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, 01 Feb 2021 15:39:52 -0000

I didn't see any objections to the diff, so I went ahead and posted 
draft -04.


On 1/29/21 2:11 PM, Ken Murchison wrote:
>
> On 1/29/21 2:00 PM, Cyrus Daboo wrote:
>> Hi Ken,
>>
>> --On Fri, 29 Jan 2021 13:01:39 -0500 Ken Murchison 
>> <murch@fastmail.com> wrote:
>>
>>
>>>> I read the above as zero or more 'x' and/or 'y'  OR zero or more 
>>>> 'z'.   I
>>>> don't see how https://tools.ietf.org/html/rfc5234#section-3.2
>>>> <https://tools.ietf.org/html/rfc5234#section-3.2> would allow 
>>>> having  'x'
>>>> and 'z' together.
>>>
>>>
>>> To continue my thought. Given:
>>>
>>> a = *(x /y) / *(z)
>>>
>>> *a would equate to: *(x / y / z)
>>>
>>
>> Yeah, OK. I guess I got it wrong in 7986 then :-(
>
>
> We all got it wrong, since it passed review without being caught.
>
> Anyhow, attached are my proposed changes per Barry's review and our 
> ABNF discussion.
>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Mon Feb  1 12:55:59 2021
Return-Path: <marten@dmfs.org>
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 DA96F3A1487 for <calsify@ietfa.amsl.com>; Mon,  1 Feb 2021 12:55:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.884
X-Spam-Level: 
X-Spam-Status: No, score=-0.884 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, BIGNUM_EMAILS=1.214, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dmfs.org
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 hzMkNo0Gi6wN for <calsify@ietfa.amsl.com>; Mon,  1 Feb 2021 12:55:56 -0800 (PST)
Received: from mailrelay2-1.pub.mailoutpod1-cph3.one.com (mailrelay2-1.pub.mailoutpod1-cph3.one.com [46.30.210.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEA4F3A1485 for <calsify@ietf.org>; Mon,  1 Feb 2021 12:55:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dmfs.org; s=20191106;  h=content-type:mime-version:date:message-id:subject:from:to:from;  bh=/FOeLHwVxNwNRRIzoP6rgZ6nF7Uj2hK+fNeIDiQ7qW4=; b=myS0XJ+Xk/RB0KGtglgGHGRhHXdEvHyuFOSi++Igq/bKiwnNoPC18oGNl1IiJcknL4kA8E0+mwayM veMKT46vdEkuVMp6LKRdHQLM0p1M/eFk7InJQxsmr/DIiI/OAH4rjYAZLQgGNjFLWS1xYcZHjifUl9 YuuaJUlQUls+S8h+/ptIcrZDWMqO3X2mqLCT4qB5ScagFir7OMHG4S9DJJGCu4Vk8CgyzX+QwQLjS0 +r6xFapHPvykXU4HsnirzgFt6hVYlUhjPLbJDVUPMQwB6aGzAO+9pwCj4bxddT3CGUsiEgoIsyKRtp RDk1NshJTauUVQKDaojT+NaNZ8bORww==
X-HalOne-Cookie: 6934c67ae78e687d127b8213d527bd4ba1e77b6c
X-HalOne-ID: de3d13ed-64cf-11eb-b55b-d0431ea8a290
Received: from smtp.dmfs.org (p5093adb8.dip0.t-ipconnect.de [80.147.173.184]) by mailrelay2.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id de3d13ed-64cf-11eb-b55b-d0431ea8a290; Mon, 01 Feb 2021 20:55:52 +0000 (UTC)
Received: from boss.localdomain (i5C756652.versanet.de [92.117.102.82]) by smtp.dmfs.org (Postfix) with ESMTPSA id 8F4FF2213AB for <calsify@ietf.org>; Mon,  1 Feb 2021 23:10:56 +0100 (CET)
To: calsify@ietf.org
From: Marten Gajda <marten@dmfs.org>
Message-ID: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org>
Date: Mon, 1 Feb 2021 21:55:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="RM1jyR7jeGf260v3PGOuhLGKB8K9PjdMc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/D4a8ooWWhMBFqafKY-TQS9ynIo8>
Subject: [calsify] jscalendar event/task overrides without master
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, 01 Feb 2021 20:55:58 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--RM1jyR7jeGf260v3PGOuhLGKB8K9PjdMc
Content-Type: multipart/mixed; boundary="X8XexYBTPJMahxuSslGHeo2478zSiNSrE";
 protected-headers="v1"
From: Marten Gajda <marten@dmfs.org>
To: calsify@ietf.org
Message-ID: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org>
Subject: jscalendar event/task overrides without master

--X8XexYBTPJMahxuSslGHeo2478zSiNSrE
Content-Type: multipart/mixed;
 boundary="------------2BC7B903588179DB4A99D9E3"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------2BC7B903588179DB4A99D9E3
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi all,

I've started to implement a simple task list to JSGroup file export and=20
came across an issue I couldn't find an answer to. So hopefully someone=20
is able to help me with this.

It may happen that the task list contains a recurring task instance=20
without also containing the master task. This might happen when you are=20
assigned to a single instance of a recurring task.

In icalendar I'd just omit the master VTODO, but how do I do that in=20
jscalendar? IIRC the base object must be a valid jstask.

The same issue applies to events, of course. Not sure if we have=20
discussed this before but I can't remember nor can I find anything about =
it.

So what's the right way to store such a task/event if I don't have any=20
information about the master?

Cheers,

Marten

--=20
Marten Gajda
CEO

dmfs GmbH
Frankenstra=C3=9Fe 9
01309 Dresden
GERMANY

phone: +49 177 4427167
email: marten@dmfs.org

Managing Director: Marten Gajda
Registered address: Dresden
Registered No.: AG Dresden HRB 34881
VAT Reg. No.: DE303248743


--------------2BC7B903588179DB4A99D9E3
Content-Type: application/pgp-keys;
 name="OpenPGP_0x19D7E3CE3D3EBE91.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="OpenPGP_0x19D7E3CE3D3EBE91.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----

xsFNBF+V5XkBEACfzBAkl8CbWDwPLhArqyU14LYuEyxLtleoDFuOkGuf9NM+M+1qNqMUTENb/=
C+P
r3D3QQQMRTSARnpUj0G0L3Kx1CXTEhJgDf+JUx1UKY91cuB3MGEuxT+xYOe7i6O5/WHV88x8v=
oTj
yhpUMyVvjN0L/Vl3WoEV1pP7YmKXPi3OX6aoPZWrq9vdKNKdfvRz8MA/zHuoU9LHLYCATuNQl=
Kim
5PJHNompgXPB++PoqAd4QA1CKEhHyI6g+S4DoldbAQhm4hJ9cJO/0ck7L9EAYdbUWSK5KmLXY=
dWT
QujEcU7/uSRZvhVXSnrgF1PyJcCTNFEBfZmXRXRULJRuTsoO3SiMFkRDU+6eLEq3o1Fn01yJI=
JP4
P4603IOSVyGR3KLQDPeldio5Z7wKWZdEX4MlhsyJD7vhUS/h07Pi087MHG+sHbKjXSN9FDk2y=
T/W
GxlkHkqjafJltMS3j3k+5qK9JTeSzrHRpuedh1TtPHhUv6mbgtoYLWPgbldqbIrfUaRAJg46q=
BUV
/Pua+1ORZiVOLQhAf/K7iqt5MV7ha/T6IEefmqzvkYHn958H/S7jgsQCisAJ24CVM/apL2+iv=
vQC
Va1XPtXuH9uNUMZjxCNQaR4toFl21+38Tyb3oILgRfoJvvDulKzUUmwYRiUzMPYI9d22TL/Os=
exI
AnOP1aWzDbJLPQARAQABzR5NYXJ0ZW4gR2FqZGEgPG1hcnRlbkBkbWZzLm9yZz7CwZQEEwEKA=
D4C
GwEFCQlmAYACHgECF4AWIQQLq654Hd/aoJI9s4YZ1+POPT6+kQUCX5XodAULCQgHAwUVCgkIC=
wUW
AgMBAAAKCRAZ1+POPT6+kQZ5D/wImwqmmOkyPtFu+s3/CnwmwoudhfOuMYW32Y0uSxjOWTqh3=
1WK
CXIE+roN0ktDiYT5c7YoAvfnXdj1yyxxcT5Pwfe4SukoS4WfSp3gXNyb73BfjC/cMDvlcrmLv=
2Y/
nb4ZXrZCB0+g12V4xJ9RUSdFVM2oie0sqbSEjcPAgWZTJ/Kv4ykXxj6obfJOdTwNEuHUBuxLw=
gXP
0mT873NonUnG1p9bUuup5MtPEWg8fXTRuxXwpJvvpl6/Pobq726EUc1IYCN5i52lXcGDz/U8d=
RVk
04cXCRmMWOgxXIFTvb0SP0odo6qsdrRArO8PGkQ2JtvyPYMSFXVc8acpD30je3YOPCYBA2Mdy=
wug
G0Wy30TA3y2nxUllccBWlsszoK/t+NPE9DPypDvgIdKNySRapVSZSRko7SZs3AgfJuF4ktuPf=
nnG
QIH+3JUhJtQOQPolA/ogIQbp7/8Bkc1RkQWFABJl2lRHspeuAR8n5aJhyo3Xk3w+6RfS5zI/g=
ys8
EwYRKL0/RLXc5H9m5oCrvvD4Blh+dh8auqX4bKUmTwJ2npKYSpNRmpNKFihBvflePeDkl1dwn=
HB/
nucN3ObWBA0K2rLlznjOWx9pLVGsb55QaQJJwYf5fSKy0Wovd/5hhu9rWpcnKCxsmAPfupW+i=
Ih5
fwUcpMTAat3WnW2xZVOdADXmK87BTQRfleitARAA2TSuLM9PlhfHk0a3CWavZx/J3+gKMh1rw=
BIU
IO7FaB9HZYt2xy1c/7Gh+07rSQ5Jhr6t3GT0ZxpqS6sHHkgEqDLHPjlu/NSMSaynuY2DzPlrF=
tKj
6LCcSvjJA0ABH/Ipmpf6pt6WxZ7OgKTxWNaUu9UcUpz4dFWS/PzyflsQmikyZd+Wd2Epctskp=
fPy
QWzdkDulf5f39mJViLY1jvMZA5ozwuWAItUHSkqpO0jc2Qj9wXYpisd2LrU+3Fefrz9iRr9H9=
wlG
ejDbmNImwHKzbV6VQret6pqlRAA1wsBam+2mMU0oiemgivLRw2hpEgzUVnbtED098IMEDTWMI=
wHY
/bj1SGTg2D7U3V38XeFadtxx2l+qBVvNmpup146Uz6uSbXGthz6pSPB/lmIlnIKh+vipTd1bO=
yLf
BYhJLNr0vKDhHRt+jjH+tDkPgEjl9FL98xc7hDv80uqhAPMCX3DdCqS0LRN/h+kCc42yg3W/C=
PgX
m8/r64yfGx6SU/47hV4wrZYnd+n6FjZ+i0Ta8TlmRLFTXmbpx+cSvKN3A9shEhVl90aYMK5a3=
nt9
6T3jpxuYIyeBtvFK24FNeumt/w3+ERVhw7Mt72E2NW3yi6d8AGsnd4gwoINaCStHYO0S13NVk=
eLH
VEy/Z0zzGlZfnjVmnDdLjgo6PWEZfWJHbv5OsmMAEQEAAcLDsgQYAQoAJhYhBAurrngd39qgk=
j2z
hhnX4849Pr6RBQJfleitAhsCBQkDwmcAAkAJEBnX4849Pr6RwXQgBBkBCgAdFiEEGGyG200+r=
qXB
ulPJnaKs97VvkHkFAl+V6K0ACgkQnaKs97VvkHl7lg/7BR0aJmcm5cmpMqyUfXVDj3RemxyuZ=
7Ms
YtKuOsJbqhdKSa4r8MOxkVm8lp7X/+6UQvAx3uW4YdGgJJZqvg2hcLtDoFAgvOANsdGCqK39t=
+GH
c/6xejWibeGKlzhRI5syOdBkjcM3j+JMBCjtdeuq9qKfuyi5PDTN2iInwkUSPFQCiu1uAMeIU=
0xP
BUzcWUBCZ/d82NNe7V1JMOQMqnPMst0qEvu7nBF/Bdp8Mmc777B8b3DHuH9L307qBsyp9oFaB=
1TG
PMkxvwsezMT6A/I40ACItnx9T4ceMkHXR5KBjZjTK3ZNdp3GM2Q4Y4lQh2wtc7zXZEcfu3omC=
HYn
0+O0jsXW9NNu+ktnpIvzDz3doQhoHRAEX8ljURi//VkBOJDnRfB4YLY3DeBf7WZyl4U0MvCAn=
4ON
lU7hJAF4+IESNC/k8x80imDx2MnA+ui21ZkzAyLwHR4fUhbbuRHNgl1fJPoAjIqvMQpCO6Ul5=
GgF
diB2l4BvB0D+oQJhwzIUCPXQikMJnfbv7Cy429k7xPaZQNLH8iGwLDqA6C5EnkPJ0BkRHrYRL=
961
GwtmSpprSChBcuzvvEQkIDKK+oLEeQAEZzf3y6bHj2uBe+60AABQc+JHeWCe8ZoSq/elD7uhD=
X18
JfrIT1aW6Ae+ZaCpk+xBjXRdbdSXDwIAMZOpUYLbSF+Glg/+M89nk3T7PVeqWGsmQ2mwk3k5d=
3Vq
Uh9N9OTnsi8e17JtwO2RDj0yKSF8cVNhJX3rXfVzpYeDHe02AuLX505SKsIt9ImswtzFrE5/I=
Ixp
bdCar290Q62hESIevzhR987Hpl/qFKikga6w77L+f+jbHlaMUFa59jHvM25kJA6FVil55Kyh9=
KCY
ylEIm2kD+q/VROY2E4NX2ynGvZh2lTrzhpYp2bQn5+8Nt/6IsZA/i8MSJ+Ltz+BLyGiGKIwad=
Dt7
v2z5TVhNgbd3RG8FhpX6vc9ZHpM3KZ1wvsv6iW0xAUwUlLuW8ShnGH2nQpnCZ3Ry2WYAZAFUE=
SbS
czbkj+tffH3Da6TIwUud+rhaEI5MoIePQKdASa9kKvtWiI1haWq9OS0eL9063LG+PudzTT3Jt=
aFg
ET2Xzwdp0gZ20J+jWa5UcPh+nC+7Jy2wdwFQI7YOTU49/Kp1Sny/IsvWc1Bh0Ce5OsKdgcklx=
0ND
Y6zziaKVdwE6Hxy3L4x0apky60LX8TLifFLqvF4BgFIchnBBjhFYcLwfNO/+VkM2GTWYxWADG=
Av6
HwOO2Xl3zZyN37rPtys+Hi+pgweNz9j51DlBqbAuzzuSoBAMpv67A/tJ7WtEGi7ooRUw0jT/c=
Wbd
qjAxoUQlejcGLKYrouO0+BPqq9IQe+6uKj15N2o9u7LYPFLOwU0EX5XpEQEQAMEURD7nQV5Qg=
2il
cn6LTWd7GBY1J7KnnGZkfEV6/Sg82JMqaxQ2idjeVAri4lpcTwl16fn6zqtvFT4Y1xoZAKKZW=
ObN
BgAMKEXcVBP8YJ+4JtsIuCM+pI5/nXX9riQ9SmtRPHWt6vus+TeYZRdEONvTtwHExRkaALXpS=
ojn
yjeSo32Pi5OV6r8MkDMllCXrba+dcVcIxtwwDLRyqCCe94rnrsZ7I/uQfqy8uF0PiQzsk9IDx=
sGN
ggFVJo6gT/HDfCPekSsKUURvNe2PLAIqOacoRS38PAn9+oKx/CYVAqem3yshoaMfF6jSGaXmn=
XhD
9nakNkI0s9t18u7Ft512qDPcXlHWKysYE9w8Uah4+ARWOeRJbg8jNh0A49jGtjsG/CBo9ZtF2=
meX
5hjj2tA7xPziwkPDCrpTTwCn4z8aOiiMzOSfgAYIx6j1E4X5Suzxdo5dlfrLfT/uLWVliDSBQ=
36C
IGDUQGbkGxXci5eTTE2vM4/++HfBTD1wDQCHZwlopchJSRdhKmWhiCKSONm0wsoRgbzhKCzKu=
2hD
yQub+9ozgxdfESyEsi3804g0Q5IbGv7LbcErX8KAxWovTgLAj4T+Ut3DsojO0sUCH5su8hgar=
mDB
HZ5GXzMsrhlTji+YSe+9Aa/wafCaSdkJ5QJKON0jovS0oHmXxYr5WlkfRUdNABEBAAHCwXwEG=
AEK
ACYWIQQLq654Hd/aoJI9s4YZ1+POPT6+kQUCX5XpEQIbDAUJA8JnAAAKCRAZ1+POPT6+kSyyD=
/92
kc8BkmlUaJ1IelM4GDMKfFZSpxPNrQQ38Zrcjp+YCcfpvFqYKNS35lo3DlEH/6d5To2FJ5pJn=
CxN
ew2Y+GQvC/Ug0h1pyRVT4fQBdFkBtQ4jOCwujVDDvh7BTtx8hUXif/PxC8qHo8zZO12PrzdXa=
WZR
3pkXhGgP/qvKeejZzBY13fhOXOPGtfDRU/qz9eNHKnBaAAyVvKq8awpIa6WGDNff5iMjIEN8H=
HTW
i2YeyyIwVo1/DxGAqsy1vV0eQyBw0JHKHnMoqE1VoTHv2bMsly0L6q9x33Z4+DNiNJlrk9KOG=
WFk
BAFMNZxhTHFW83owQojo13iOG5aJrxuljAvnFL4rYIdaYqve3ZXzvfumM/p8UPP2oI0XkayiT=
gpJ
S/5bkPLjpozLqeoUxSR2fxY2s43/FqFi8+PUzcFfOaAv3VAs1G7EoXQsXhu/SOR7+j2RROGUK=
Jxp
xHRyQuL5RavNEoeMF/n4QDYpCIAyBflovyhIW4btwuVm4bzf+f37VBEKFk5Ctq6Y8fR3h4s04=
7R7
xelho+p0EJuJoog1j3KtNqBD4OepVjXQSDQnLt/5SYFUsj6toNy02ygkkylLluObZY+GmDPuV=
td+
lSDSE4/2HWJLNymnuqqWod9Yn4JaVAvtt4UfwmGHVWzBCcwTi2AsFVrM6/c8cKr8dYZRkdF1f=
c7B
TQRflelFARAAxrnuqgo1ylltqBYI/MRWnOUnE9R1nLmFaCDuVAnEnFEVhReWccN3bCkMAR5CL=
eYK
XOrFniUCKReagGK3a7ftjtKwhz4yqiRMMNMA4YvUbjohyqKuPhJeJmCywQzyU59iP1Q3saNhb=
3ni
bcVTJ7hvJndQ9qhpaL6V5PfoRvAJZUobK2fY1za3ZTGuF0HQAEEuPiTdPgIUCshMlLMClOyeJ=
P7y
JXzTIktevNp16zS+QBMRW7NamZxB2rbIiA9KKzA5xoVautnK+l+LNsCk5mXBShQ9Z2NXB8vPW=
gMU
JeCMz9rO+YZCj+ihsuBcZwJwUO23BxfAx6UIBFbSNwypPL92qstwuLirK41Xt2w1YvpfFO/nj=
Lmv
2JVEvoHoaP2ZNusEsc1lF8BdMk/Zs+qPIH5QmuJRBGtjrwnfQxuyOg5fbKNaxj//HO90vAyj/=
Soy
KdiXJvaxYdYlHD3S2qqTDM3lAVOtIYxy2UXiGbrf6koh1L0DFCCFmWu+zJplWq+9V7Mq72kmq=
5dA
r6dASS+WTgTgbNoAIbtkqamA2RmS5b/Bg1XctqNZ6FnHGf0wBsPAQ3na5uA5V6ZgBxYCPyxHQ=
XqA
axO2aJTfxH6og70AKQJdoot6EhDsBOukbuh1pbdwUTR+E/PRMYdhTo9K+ztaXklqkqL2FG7iS=
11F
VhD2oifiJgcAEQEAAcLBfAQYAQoAJhYhBAurrngd39qgkj2zhhnX4849Pr6RBQJflelFAhsgB=
QkD
wmcAAAoJEBnX4849Pr6RXXkP/0qb5oHys6fu4eSyXryndtvS7JfZHz7J679o65AtANDwQ5a9M=
DMz
C5bn/tLtmIq5hKj1elA0Bj2XRiLp3VUIyH8sd/6UdDZlkzqnI1G4ny8Pq5GYHDzBaGf2tTx5n=
naF
9E9ftdveMXHV6aVIorjqdXDKhGB+9YIX4DrG+GGTKLWXRCnCFpqQL62Qs2GPhfwg+DQVvNtld=
LT/
F4x8AwdtrFamaZtYglRWPEjo8yhAsDuHYUK4r/ponQ5FDNjieso3xP54doIs0EizGq85t4j3P=
Rxa
4NZNILEs49EqgqWjmuEMDl2D7pglteZEYPnYJcf945PR4dQF0Lj0qMSFpt5OIbptkGZ4VgONp=
lKo
LwFaBU52IpudUiGi4YlG7B4tECzxvSwsMB4KByJrwQWuvL2kc6NDPChRpOrz/ra0+rJQ8jN61=
lrK
Sddn6vqV38MYT/fXrlVc+gTOZr5hEbdAF1nG9JSVbNI7nJZu09MrkNyGrDEaSa3X0LA6RFVEj=
M6L
2qFivqlk0CQHyNVLdHQCLkyc7n2qFGnTaN7GckyFtE53Yd19ntxKLMr9SA94vDt0xo9q4Hnsl=
pWU
TIQPNUcquRRBVyXZgHkxJDx77XnhEim1eqV9FhyP4TqYbbYVGbhjYu/QTRvKIqGQbQt/zFDL7=
WdL
qBtTdzvT/Y0zYQK/Rmma/tQ/
=3DEzgo
-----END PGP PUBLIC KEY BLOCK-----

--------------2BC7B903588179DB4A99D9E3--

--X8XexYBTPJMahxuSslGHeo2478zSiNSrE--

--RM1jyR7jeGf260v3PGOuhLGKB8K9PjdMc
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEGGyG200+rqXBulPJnaKs97VvkHkFAmAYatYFAwAAAAAACgkQnaKs97VvkHnw
GQ//Vl6tpZtKBj3qRkkusdSLqeW9HSaTKW28VQBQZhvJ6YtGsCNTSJmqktgSUQEc7yjT9G999RAT
SoAlQOOu6iuMbmGDQRslBSNCEjHbv39mnCmQSAPM3m1nn+OTW8hTVz3BpY0YdQJ1sEIUIaMxIftj
Hm7C4qsg/R/q7LF7urS5N+77f6VYUOvFTKKUFOZxWFqBwJ3Jek0ABnkNjf4T7v0rMRWY4+yPxS8F
R8jy7sMb9UVa2eaCJvIA3cRodkacuSg5vT/dM3xiVvqskUAcF4tcfS2YAqwoh8P1uOIfNF7xy78u
mRAyFSEemA6wiMrwBqAyAY1000AYpLdAQgiFlVO3wrGvFkQGdMWV7lZBRh1UcI0vAsnBuJSxQxwO
h51oOuBTFUq00Ix4UQii2pr//NcOBQ2yzS62pnNjtDMyCGftpkPPDzgp+s1Pl+GR8/6twc8MlW/n
qvWLW6e7k9ZBvosMoSsuDwp8Ozifj6RRIczxP1CaudUlRGPJVZXjC3+MvxKhP5jz6TpizoR24rvQ
3iRubQ6+foh4UvTdjAwDgVqQm48F+PPpX77cKRUGv7IOmERf7QAWcvZAIx9ixZoUikfVHNVBOSyK
OqDLp6KwA+qd6vjLq81QoV5bhaz56rTYBQqgjRQh0noCGqpoOeES1FKb86OOlqUfyohs2Mn5Rk6/
RZQ=
=o17x
-----END PGP SIGNATURE-----

--RM1jyR7jeGf260v3PGOuhLGKB8K9PjdMc--


From nobody Mon Feb  1 14:03:26 2021
Return-Path: <mikeadouglass@gmail.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 467EC3A1517 for <calsify@ietfa.amsl.com>; Mon,  1 Feb 2021 14:03:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=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=gmail.com
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 ncu5ryvTVYDO for <calsify@ietfa.amsl.com>; Mon,  1 Feb 2021 14:03:23 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 6B2DD3A1518 for <calsify@ietf.org>; Mon,  1 Feb 2021 14:03:23 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id 19so17963498qkh.3 for <calsify@ietf.org>; Mon, 01 Feb 2021 14:03:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=zVkX7tcw4p117ZT7y4MYf01JTRzswYu+V6a0tMu24sk=; b=DCZnmp2tan9eamB6InONxCe+SDeMM0h7K0yGJrS6rtXCHymKJ/cGMzIpyUJQnjUrBe XB+XcdPKk56ZaoSGJjghRowuvyPn7DJEgYMxJp36pRktn+uQAXm1D/TEbN0kGD0bwMEz pQ9mqRUN9DAvTjJfsk8RJweZk2J1izVY6pANKh+GPay4tpUI8uc5n5npr2rQd8PmSCzL giLQvcTxxhMpmzwNSd+hPMvjXLG+fXnrKAS5Zd/zQ9ZNPw+P/nUJZydZEsdjRFzdocpt ezxcIlAzoRDy3x3PdwOEI0Dv/mJzJ9vMJZMqOUWfXFwgxAWvAuQvDMNJWI5f6QjeDfEB QzMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=zVkX7tcw4p117ZT7y4MYf01JTRzswYu+V6a0tMu24sk=; b=mRJaLMN7vEIN0OZhwSDokppostxON3AfTS5qE+xp6RSSbsgjPZC44WFrMB2BLxqrc+ d0j3SRwm+EWlaR3dolrahXAxOGpx8nhrXYFIDd9Y4otSKPBTvNV8tOTxtfb/oKEf6W7k 7uYYe2+hNt51kp/79ybgjYoJVhegUNnEA6gjcKvcV23qJON0Iljg+dSJ52ScIDoYGnpI 7fk73JMi1QOXw4H3eafxbuKHkmgJpRb3l4AltfSfXJmKW+V5sYhOKBNaObbclbqqiod8 tq5wWWp+O3ENnOOWfzdc3hPBqxp2oaXCdIlp/8xhrIiQvqu9LqEfjtRnBdQ6vdiOnRf8 ZPrg==
X-Gm-Message-State: AOAM530jVW7kJe8zIZFUWwa7hPz7S+NIaTjJ0SokoP3f4fr5hN7ervcx iv/t+afwdkO9RN9nqtAFu2J9ZpdqGaE=
X-Google-Smtp-Source: ABdhPJykE5MYDfqjSZX7GepttZLR8/KdusDWGptnbveOkGLDp6Tsvz84oAidm36zou37FOYQN/NeyA==
X-Received: by 2002:a37:8b81:: with SMTP id n123mr18350376qkd.242.1612217001975;  Mon, 01 Feb 2021 14:03:21 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id k8sm14255771qkk.79.2021.02.01.14.03.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 14:03:21 -0800 (PST)
To: Marten Gajda <marten@dmfs.org>, calsify@ietf.org
References: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <5d72a4ea-c78d-a582-b062-5737ea43632b@gmail.com>
Date: Mon, 1 Feb 2021 17:03:20 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org>
Content-Type: multipart/alternative; boundary="------------F60DBDACCE6D99C7DAA850B4"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/_fcba8r9OtBYyuXoTxLrkcrMhUI>
Subject: Re: [calsify] jscalendar event/task overrides without master
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, 01 Feb 2021 22:03:25 -0000

This is a multi-part message in MIME format.
--------------F60DBDACCE6D99C7DAA850B4
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 2/1/21 15:55, Marten Gajda wrote:
> Hi all,
>
> I've started to implement a simple task list to JSGroup file export 
> and came across an issue I couldn't find an answer to. So hopefully 
> someone is able to help me with this.
>
> It may happen that the task list contains a recurring task instance 
> without also containing the master task. This might happen when you 
> are assigned to a single instance of a recurring task.
>
> In icalendar I'd just omit the master VTODO, but how do I do that in 
> jscalendar? IIRC the base object must be a valid jstask.
>
> The same issue applies to events, of course. Not sure if we have 
> discussed this before but I can't remember nor can I find anything 
> about it.
>
> So what's the right way to store such a task/event if I don't have any 
> information about the master?

I ran into this issue as I was implementing the conversion for bedework. 
The situation obviously arises during scheduling but might also arise 
with publishing a single instance.

I think the short answer is that the overrride must be a complete 
representation of the event/task as modified by the override. I did 
raise an issue with that. If the override has the start timezone 
modified then there's no way to determine the actual timezone of the 
master. In iCal the recurrence id has the timezone represented as the 
tzid parameter.

The suggestion made was to use a "recurrenceIdTimeZone" property to 
specify the timezone used for recurrence ids.

>
> Cheers,
>
> Marten
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--------------F60DBDACCE6D99C7DAA850B4
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2/1/21 15:55, Marten Gajda wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org">Hi all,
      <br>
      <br>
      I've started to implement a simple task list to JSGroup file
      export and came across an issue I couldn't find an answer to. So
      hopefully someone is able to help me with this.
      <br>
      <br>
      It may happen that the task list contains a recurring task
      instance without also containing the master task. This might
      happen when you are assigned to a single instance of a recurring
      task.
      <br>
      <br>
      In icalendar I'd just omit the master VTODO, but how do I do that
      in jscalendar? IIRC the base object must be a valid jstask.
      <br>
      <br>
      The same issue applies to events, of course. Not sure if we have
      discussed this before but I can't remember nor can I find anything
      about it.
      <br>
      <br>
      So what's the right way to store such a task/event if I don't have
      any information about the master?
      <br>
    </blockquote>
    <p>I ran into this issue as I was implementing the conversion for
      bedework. The situation obviously arises during scheduling but
      might also arise with publishing a single instance.<br>
    </p>
    <p>I think the short answer is that the overrride must be a complete
      representation of the event/task as modified by the override. I
      did raise an issue with that. If the override has the start
      timezone modified then there's no way to determine the actual
      timezone of the master. In iCal the recurrence id has the timezone
      represented as the tzid parameter. <br>
    </p>
    <p>The suggestion made was to use a "recurrenceIdTimeZone" property
      to specify the timezone used for recurrence ids.<br>
    </p>
    <blockquote type="cite"
      cite="mid:416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org">
      <br>
      Cheers,
      <br>
      <br>
      Marten
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
  </body>
</html>

--------------F60DBDACCE6D99C7DAA850B4--


From nobody Mon Feb  1 14:12:19 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 528C13A1529; Mon,  1 Feb 2021 14:12:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <161221753429.6318.13830461705241642805@ietfa.amsl.com>
Date: Mon, 01 Feb 2021 14:12:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/0lX_F3BWPBH3P91f1ksRCARQiuI>
Subject: [calsify] I-D Action: draft-ietf-calext-subscription-upgrade-03.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Feb 2021 22:12:14 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : Calendar subscription upgrades
        Author          : Michael Douglass
	Filename        : draft-ietf-calext-subscription-upgrade-03.txt
	Pages           : 15
	Date            : 2021-02-01

Abstract:
   This specification updates [RFC5545] to add the value DELETED to the
   STATUS property.

   This specification also updates [RFC7240] to add the subscribe-
   enhanced-get and limit preferences.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-subscription-upgrade/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-calext-subscription-upgrade-03.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-subscription-upgrade-03


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/



From nobody Mon Feb  1 18:01:09 2021
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 AC0703A166A for <calsify@ietfa.amsl.com>; Mon,  1 Feb 2021 18:01:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 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.01, RCVD_IN_MSPIKE_WL=-0.01, 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=aSJShXjE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=fUYczTp3
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 sedeEnQNCT6p for <calsify@ietfa.amsl.com>; Mon,  1 Feb 2021 18:01:05 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.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 B59293A1668 for <calsify@ietf.org>; Mon,  1 Feb 2021 18:01:05 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id DECF4C73 for <calsify@ietf.org>; Mon,  1 Feb 2021 21:01:03 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Mon, 01 Feb 2021 21:01:04 -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=fm1; bh=nMFKIIH sKf6/9sZLGEVvJ75jbwcCgxBMLNFctBb6L/4=; b=aSJShXjEVp39HT8J0N+976m 5yycClhm2yX3i6VzeLvUqHaz2fYj7Q8n39KYI9nPYdUsLczGzXkmrkx56x7d4ap1 lT6MO4DOiSP1URfutocAWrJK7YEPmv4QmJhISe6sb75aQIjl131e4B/rns69fKJd ctRB6jEl7YJUJ+EEMpuAoFWzXsIKiY9u43Ms7wN726T2sEb+5rLPfE+KU4aS9IMD na2LIOIUsDcAZjiAkmyoqA1CgSs373niu5v3P0y5L0xHXHzBGYm2lsk+7dRr8qUd IIW79OSUwqM/7d3XEJjik+/wq3cHi67pO2rS3xe+DGFCBzAqAaRDvI8JhtIVWUg= =
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=fm1; bh=nMFKII HsKf6/9sZLGEVvJ75jbwcCgxBMLNFctBb6L/4=; b=fUYczTp3VZvIpMjFsqOBnE QyNmj2VjgBHOKme0p1RK1+JQm/sj3+YOFukQl1NQb8gTC0u8qLo7ZegSV6+s5iE+ pC+idhln6ISkNVUlIks61T2oxe9QNN6jaqZ7EDKV/HmtFzDe0NIwI1/crITf/FFu oE/A8WaqqA3b65GkFQ5mPN1pg+eWYxjLznDavlz8uqPD9K4+qgZzS5yVT4wENX3H hX4f7ZOp7OEDL1DXdsfZ3kRvTyQcJlV7wS0enlYx1Op/AI3hXamCp2fjL2XDhLME U3gz7BEyBm8GfA5YNwGTAW1Q6FNqe4zTGCVrW/Dl7iER6fP8YtYL6B1zGGMcUagQ ==
X-ME-Sender: <xms:XrIYYNBRe1UWTnt4Xn0c2nRQ151BigDEqtIye7jcbuS_6arD7YAWOQ> <xme:XrIYYLjRuESXjchEbFZu3fD_w49hWjrzZri6DqMmQwoHVTfnVU8LR0ZGUkuyR347M vh4wu9GOUELJQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeelgdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdfpvghilhculfgvnhhkihhnshdfuceonhgvihhljhesfhgr shhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeevvdetvdduleekhf eghfetfeettdelhfehfeevffevleekuddtudffieevjeevhfenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghilh htvggrmhdrtghomh
X-ME-Proxy: <xmx:XrIYYInzHCw0Uoxn2OPFDUd_UHsLSfTYeJd6Aq8pu6CzglewYpIM8w> <xmx:XrIYYHwzUGA8OmjdDnpuFgHTN_JVVdqvJNzym7FWBqTE2CYL8QFimA> <xmx:XrIYYCQY-0p-sAAp52gL36dF0C1WTYF-OCznUKiVrk5FnVMaZ4XsLw> <xmx:X7IYYJcmFiwHI5hc4kY0QMbhULpWdStNUEqsE-p_KeklU84Kf3VFKg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id AD14736005C; Mon,  1 Feb 2021 21:01:02 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-93-gef6c4048e6-fm-20210128.002-gef6c4048
Mime-Version: 1.0
Message-Id: <db6fa284-271a-41a6-9c39-d3a6fc8d8b4e@dogfood.fastmail.com>
In-Reply-To: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org>
References: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org>
Date: Tue, 02 Feb 2021 13:00:46 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=06e1052c15084b84a7dd3ad3e0ebede5
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/HaSfO0c1MP2sX6w7O-_vJaOS_tc>
Subject: Re: [calsify] jscalendar event/task overrides without master
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: Tue, 02 Feb 2021 02:01:08 -0000

--06e1052c15084b84a7dd3ad3e0ebede5
Content-Type: text/plain

On Tue, 2 Feb 2021, at 07:55, Marten Gajda wrote:
> In icalendar I'd just omit the master VTODO, but how do I do that in 
> jscalendar? IIRC the base object must be a valid jstask.

It's much the same in JSCalendar: you include a JSTask object for each expanded occurrence instead of a single master JSTask with a recurrence rule.  So in the JSGroup `entries` list, you would have something like:

[{
  "uid": "123",
  "recurrenceId": "2020-01-01T00:00:00",
  ... etc.
}, {
  "uid": "123",
  "recurrenceId": "2020-01-02T00:00:00",
  ... etc.
},
...
]

Cheers,
Neil.
--06e1052c15084b84a7dd3ad3e0ebede5
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Tue, 2 Feb 2=
021, at 07:55, Marten Gajda wrote:<br></div><blockquote type=3D"cite" id=
=3D"qt" style=3D""><div>In icalendar I'd just omit the master VTODO, but=
 how do I do that in&nbsp;<br></div><div>jscalendar? IIRC the base objec=
t must be a valid jstask.<br></div></blockquote><div><br></div><div>It's=
 much the same in JSCalendar: you include a JSTask object for each expan=
ded occurrence instead of a single master JSTask with a recurrence rule.=
&nbsp; So in the JSGroup <code style=3D"border-top-color:rgb(204, 204, 2=
04);border-top-style:solid;border-top-width:1px;border-right-color:rgb(2=
04, 204, 204);border-right-style:solid;border-right-width:1px;border-bot=
tom-color:rgb(204, 204, 204);border-bottom-style:solid;border-bottom-wid=
th:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;bord=
er-left-width:1px;border-image-outset:0;border-image-repeat:stretch;bord=
er-image-slice:100%;border-image-source:none;border-image-width:1;border=
-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-rad=
ius:3px;border-bottom-left-radius:3px;background-color:rgb(246, 246, 246=
);background-position-x:0%;background-position-y:0%;background-repeat:re=
peat;background-attachment:scroll;background-image:none;background-size:=
auto;background-origin:padding-box;background-clip:border-box;font-famil=
y:menlo, consolas, monospace;font-size:90%;padding-top:1px;padding-right=
:3px;padding-bottom:1px;padding-left:3px;">entries</code> list, you woul=
d have something like:<br></div><div><br></div><pre style=3D"border-top-=
color:rgb(204, 204, 204);border-top-style:solid;border-top-width:1px;bor=
der-right-color:rgb(204, 204, 204);border-right-style:solid;border-right=
-width:1px;border-bottom-color:rgb(204, 204, 204);border-bottom-style:so=
lid;border-bottom-width:1px;border-left-color:rgb(204, 204, 204);border-=
left-style:solid;border-left-width:1px;border-image-outset:0;border-imag=
e-repeat:stretch;border-image-slice:100%;border-image-source:none;border=
-image-width:1;border-top-left-radius:3px;border-top-right-radius:3px;bo=
rder-bottom-right-radius:3px;border-bottom-left-radius:3px;background-co=
lor:rgb(246, 246, 246);background-position-x:0%;background-position-y:0%=
;background-repeat:repeat;background-attachment:scroll;background-image:=
none;background-size:auto;background-origin:padding-box;background-clip:=
border-box;font-family:menlo, consolas, monospace;font-size:90%;margin-t=
op:7px;margin-right:0px;margin-bottom:7px;margin-left:0px;padding-top:7p=
x;padding-right:10px;padding-bottom:7px;padding-left:10px;white-space:pr=
e-wrap;overflow-wrap:break-word;">[{
  "uid": "123",
  "recurrenceId": "2020-01-01T00:00:00",
  ... etc.
}, {
  "uid": "123",
  "recurrenceId": "2020-01-02T00:00:00",
  ... etc.
},
...
]<br></pre><div><br></div><div>Cheers,<br></div><div>Neil.<br></div></bo=
dy></html>
--06e1052c15084b84a7dd3ad3e0ebede5--


From nobody Mon Feb  1 20:19:58 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B43603A172B; Mon,  1 Feb 2021 20:19:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <161223959668.12956.9784802645568052019@ietfa.amsl.com>
Date: Mon, 01 Feb 2021 20:19:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/LrEUIXBrDi630QrCCM_k5ZVcCg4>
Subject: [calsify] I-D Action: draft-ietf-calext-serverside-subscriptions-01.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 04:19:57 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : Serverside Subscriptions
        Author          : Michael Douglass
	Filename        : draft-ietf-calext-serverside-subscriptions-01.txt
	Pages           : 11
	Date            : 2021-02-01

Abstract:
   This specification provides a mechanism whereby subscriptions to
   external resources can be handled by the server.

   This specification updates [RFC4791] to add new properties for the
   MKCOL request.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-serverside-subscriptions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-calext-serverside-subscriptions-01
https://datatracker.ietf.org/doc/html/draft-ietf-calext-serverside-subscriptions-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-serverside-subscriptions-01


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/



From nobody Tue Feb  2 00:25:36 2021
Return-Path: <marten@dmfs.org>
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 DC60F3A185F for <calsify@ietfa.amsl.com>; Tue,  2 Feb 2021 00:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.903
X-Spam-Level: 
X-Spam-Status: No, score=-0.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, BIGNUM_EMAILS=1.214, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dmfs.org
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 PuRLacC-7kj0 for <calsify@ietfa.amsl.com>; Tue,  2 Feb 2021 00:25:32 -0800 (PST)
Received: from mailrelay3-1.pub.mailoutpod1-cph3.one.com (mailrelay3-1.pub.mailoutpod1-cph3.one.com [46.30.210.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33DBA3A185E for <calsify@ietf.org>; Tue,  2 Feb 2021 00:25:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dmfs.org; s=20191106;  h=content-type:in-reply-to:mime-version:date:message-id:subject:from:references: to:from; bh=RlG5mdE2LZpz6o1wm9+nhaDZdOijvWhf6Wh1Afcyboc=; b=PJSLZl38NjHPcYMtuuN1j5SaWTGhGIiaYmC6FbNEetzLUgofZB5pUvcGS2TqWLHBLaXpMdc8OfkOu Es9PM2fi+5nOKWtwQ+rqCQlLcdAal1uL3cnacl5I9kcrDL2+65wdn5D8Bt5xXQbK5mmpn+Oiq+9rxe Fa14yAIrfsEJBhYumi9KBke6Bxv04crfZ9oJUA10PsGBPylFZI6v7ia0W11hY1M4xAw3YEWS8BMtem A8HR0TSNDBQRclLeDa83qmUxjkOrXS3LL7dJoqSDOiLElW1FDsY7Hc1Yeiwe1K2pR841kkqGa6WM98 fmflroKzF9uBKmjDIYIs+ZkYw3iYQsg==
X-HalOne-Cookie: 85c8dda5bb7f1ff40ec69494ecc9b9aeb48b57be
X-HalOne-ID: 34cdd9bd-6530-11eb-8cc3-d0431ea8bb03
Received: from smtp.dmfs.org (p5093adb8.dip0.t-ipconnect.de [80.147.173.184]) by mailrelay3.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id 34cdd9bd-6530-11eb-8cc3-d0431ea8bb03; Tue, 02 Feb 2021 08:25:28 +0000 (UTC)
Received: from boss.localdomain (p5093adb8.dip0.t-ipconnect.de [80.147.173.184]) by smtp.dmfs.org (Postfix) with ESMTPSA id 946252213AB for <calsify@ietf.org>; Tue,  2 Feb 2021 10:41:02 +0100 (CET)
To: calsify@ietf.org
References: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org> <db6fa284-271a-41a6-9c39-d3a6fc8d8b4e@dogfood.fastmail.com>
From: Marten Gajda <marten@dmfs.org>
Message-ID: <51c3aa64-3a61-cc43-00de-ea7e0df685ca@dmfs.org>
Date: Tue, 2 Feb 2021 09:25:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <db6fa284-271a-41a6-9c39-d3a6fc8d8b4e@dogfood.fastmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bXPMvy3yvmXN3DfOfyHjy9FxmMZWJaMq5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/RD_08E2ayBAaM2NN_XM3-njVjyI>
Subject: Re: [calsify] jscalendar event/task overrides without master
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: Tue, 02 Feb 2021 08:25:35 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bXPMvy3yvmXN3DfOfyHjy9FxmMZWJaMq5
Content-Type: multipart/mixed; boundary="pNOwyeKAe2PgDXTGysSMnXrvaeaWnxFUQ";
 protected-headers="v1"
From: Marten Gajda <marten@dmfs.org>
To: calsify@ietf.org
Message-ID: <51c3aa64-3a61-cc43-00de-ea7e0df685ca@dmfs.org>
Subject: Re: [calsify] jscalendar event/task overrides without master
References: <416d125e-7be5-92ff-fa4f-e1fc35895fb2@dmfs.org>
 <db6fa284-271a-41a6-9c39-d3a6fc8d8b4e@dogfood.fastmail.com>
In-Reply-To: <db6fa284-271a-41a6-9c39-d3a6fc8d8b4e@dogfood.fastmail.com>

--pNOwyeKAe2PgDXTGysSMnXrvaeaWnxFUQ
Content-Type: multipart/mixed;
 boundary="------------7485148D5C4BBAA575205AC8"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------7485148D5C4BBAA575205AC8
Content-Type: multipart/alternative;
 boundary="------------F7CA4840D99832FB937F57CE"


--------------F7CA4840D99832FB937F57CE
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Thanks for your responses.

I guess that requires a broader definition of "JSCalendar object" then.

Section "4.1.2. uid" says

> The value of this property MUST be unique across all JSCalendar objects=

And section 3 says:

> A JSCalendar object is a JSON object
Taken together, these two contradict the proposed solution.

This case is so special and counter intuitive, it should be mentioned=20
explicitly in a suitable section.

A concrete example would be helpful too.

Cheers,

Marten

Am 02.02.21 um 03:00 schrieb Neil Jenkins:
> On Tue, 2 Feb 2021, at 07:55, Marten Gajda wrote:
>> In icalendar I'd just omit the master VTODO, but how do I do that in
>> jscalendar? IIRC the base object must be a valid jstask.
>
> It's much the same in JSCalendar: you include a JSTask object for each =

> expanded occurrence instead of a single master JSTask with a=20
> recurrence rule.=C2=A0 So in the JSGroup |entries| list, you would have=
=20
> something like:
>
> [{
>    "uid": "123",
>    "recurrenceId": "2020-01-01T00:00:00",
>    ... etc.
> }, {
>    "uid": "123",
>    "recurrenceId": "2020-01-02T00:00:00",
>    ... etc.
> },
> ...
> ]
>
> Cheers,
> Neil.
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--=20
Marten Gajda
CEO

dmfs GmbH
Frankenstra=C3=9Fe 9
01309 Dresden
GERMANY

phone: +49 177 4427167
email: marten@dmfs.org

Managing Director: Marten Gajda
Registered address: Dresden
Registered No.: AG Dresden HRB 34881
VAT Reg. No.: DE303248743


--------------F7CA4840D99832FB937F57CE
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body>
    <p>Thanks for your responses.</p>
    <p>I guess that requires a broader definition of "JSCalendar object"
      then. <br>
    </p>
    <p>Section "4.1.2. uid" says<br>
    </p>
    <p>
      <blockquote type=3D"cite">
        <pre class=3D"newpage">The value of this property MUST be unique =
across all JSCalendar objects</pre>
      </blockquote>
      And section 3 says:</p>
    <p>
      <blockquote type=3D"cite">
        <pre class=3D"newpage">A JSCalendar object is a JSON object</pre>=

      </blockquote>
      Taken together, these two contradict the proposed solution.</p>
    <p>This case is so special and counter intuitive, it should be
      mentioned explicitly in a suitable section.<br>
    </p>
    <p>A concrete example would be helpful too.</p>
    <p>Cheers,</p>
    <p>Marten<br>
    </p>
    <div class=3D"moz-cite-prefix">Am 02.02.21 um 03:00 schrieb Neil
      Jenkins:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:db6fa284-271a-41a6-9c39-d3a6fc8d8b4e@dogfood.fastmail.c=
om">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DU=
TF-8">
      <title></title>
      <style type=3D"text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</styl=
e>
      <div>On Tue, 2 Feb 2021, at 07:55, Marten Gajda wrote:<br>
      </div>
      <blockquote type=3D"cite" id=3D"qt" style=3D"">
        <div>In icalendar I'd just omit the master VTODO, but how do I
          do that in=C2=A0<br>
        </div>
        <div>jscalendar? IIRC the base object must be a valid jstask.<br>=

        </div>
      </blockquote>
      <div><br>
      </div>
      <div>It's much the same in JSCalendar: you include a JSTask object
        for each expanded occurrence instead of a single master JSTask
        with a recurrence rule.=C2=A0 So in the JSGroup <code
          style=3D"border-top-color:rgb(204, 204,
204);border-top-style:solid;border-top-width:1px;border-right-color:rgb(2=
04,
          204,
204);border-right-style:solid;border-right-width:1px;border-bottom-color:=
rgb(204,
          204,
204);border-bottom-style:solid;border-bottom-width:1px;border-left-color:=
rgb(204,
          204,
204);border-left-style:solid;border-left-width:1px;border-image-outset:0;=
border-image-repeat:stretch;border-image-slice:100%;border-image-source:n=
one;border-image-width:1;border-top-left-radius:3px;border-top-right-radi=
us:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;backg=
round-color:rgb(246,
          246,
246);background-position-x:0%;background-position-y:0%;background-repeat:=
repeat;background-attachment:scroll;background-image:none;background-size=
:auto;background-origin:padding-box;background-clip:border-box;font-famil=
y:menlo,
          consolas,
monospace;font-size:90%;padding-top:1px;padding-right:3px;padding-bottom:=
1px;padding-left:3px;">entries</code>
        list, you would have something like:<br>
      </div>
      <div><br>
      </div>
      <pre style=3D"border-top-color:rgb(204, 204, 204);border-top-style:=
solid;border-top-width:1px;border-right-color:rgb(204, 204, 204);border-r=
ight-style:solid;border-right-width:1px;border-bottom-color:rgb(204, 204,=
 204);border-bottom-style:solid;border-bottom-width:1px;border-left-color=
:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;border-=
image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border=
-image-source:none;border-image-width:1;border-top-left-radius:3px;border=
-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-r=
adius:3px;background-color:rgb(246, 246, 246);background-position-x:0%;ba=
ckground-position-y:0%;background-repeat:repeat;background-attachment:scr=
oll;background-image:none;background-size:auto;background-origin:padding-=
box;background-clip:border-box;font-family:menlo, consolas, monospace;fon=
t-size:90%;margin-top:7px;margin-right:0px;margin-bottom:7px;margin-left:=
0px;padding-top:7px;padding-right:10px;padding-bottom:7px;padding-left:10=
px;white-space:pre-wrap;overflow-wrap:break-word;">[{
  "uid": "123",
  "recurrenceId": "2020-01-01T00:00:00",
  ... etc.
}, {
  "uid": "123",
  "recurrenceId": "2020-01-02T00:00:00",
  ... etc.
},
=2E..
]
</pre>
      <div><br>
      </div>
      <div>Cheers,<br>
      </div>
      <div>Neil.<br>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <pre class=3D"moz-quote-pre" wrap=3D"">____________________________=
___________________
calsify mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:calsify@ietf.org">ca=
lsify@ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Marten Gajda
CEO

dmfs GmbH
Frankenstra=C3=9Fe 9
01309 Dresden
GERMANY

phone: +49 177 4427167
email: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:marten@dmfs.o=
rg">marten@dmfs.org</a>

Managing Director: Marten Gajda
Registered address: Dresden
Registered No.: AG Dresden HRB 34881
VAT Reg. No.: DE303248743</pre>
  </body>
</html>

--------------F7CA4840D99832FB937F57CE--

--------------7485148D5C4BBAA575205AC8
Content-Type: application/pgp-keys;
 name="OpenPGP_0x19D7E3CE3D3EBE91.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="OpenPGP_0x19D7E3CE3D3EBE91.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----

xsFNBF+V5XkBEACfzBAkl8CbWDwPLhArqyU14LYuEyxLtleoDFuOkGuf9NM+M+1qNqMUTENb/=
C+P
r3D3QQQMRTSARnpUj0G0L3Kx1CXTEhJgDf+JUx1UKY91cuB3MGEuxT+xYOe7i6O5/WHV88x8v=
oTj
yhpUMyVvjN0L/Vl3WoEV1pP7YmKXPi3OX6aoPZWrq9vdKNKdfvRz8MA/zHuoU9LHLYCATuNQl=
Kim
5PJHNompgXPB++PoqAd4QA1CKEhHyI6g+S4DoldbAQhm4hJ9cJO/0ck7L9EAYdbUWSK5KmLXY=
dWT
QujEcU7/uSRZvhVXSnrgF1PyJcCTNFEBfZmXRXRULJRuTsoO3SiMFkRDU+6eLEq3o1Fn01yJI=
JP4
P4603IOSVyGR3KLQDPeldio5Z7wKWZdEX4MlhsyJD7vhUS/h07Pi087MHG+sHbKjXSN9FDk2y=
T/W
GxlkHkqjafJltMS3j3k+5qK9JTeSzrHRpuedh1TtPHhUv6mbgtoYLWPgbldqbIrfUaRAJg46q=
BUV
/Pua+1ORZiVOLQhAf/K7iqt5MV7ha/T6IEefmqzvkYHn958H/S7jgsQCisAJ24CVM/apL2+iv=
vQC
Va1XPtXuH9uNUMZjxCNQaR4toFl21+38Tyb3oILgRfoJvvDulKzUUmwYRiUzMPYI9d22TL/Os=
exI
AnOP1aWzDbJLPQARAQABzR5NYXJ0ZW4gR2FqZGEgPG1hcnRlbkBkbWZzLm9yZz7CwZQEEwEKA=
D4C
GwEFCQlmAYACHgECF4AWIQQLq654Hd/aoJI9s4YZ1+POPT6+kQUCX5XodAULCQgHAwUVCgkIC=
wUW
AgMBAAAKCRAZ1+POPT6+kQZ5D/wImwqmmOkyPtFu+s3/CnwmwoudhfOuMYW32Y0uSxjOWTqh3=
1WK
CXIE+roN0ktDiYT5c7YoAvfnXdj1yyxxcT5Pwfe4SukoS4WfSp3gXNyb73BfjC/cMDvlcrmLv=
2Y/
nb4ZXrZCB0+g12V4xJ9RUSdFVM2oie0sqbSEjcPAgWZTJ/Kv4ykXxj6obfJOdTwNEuHUBuxLw=
gXP
0mT873NonUnG1p9bUuup5MtPEWg8fXTRuxXwpJvvpl6/Pobq726EUc1IYCN5i52lXcGDz/U8d=
RVk
04cXCRmMWOgxXIFTvb0SP0odo6qsdrRArO8PGkQ2JtvyPYMSFXVc8acpD30je3YOPCYBA2Mdy=
wug
G0Wy30TA3y2nxUllccBWlsszoK/t+NPE9DPypDvgIdKNySRapVSZSRko7SZs3AgfJuF4ktuPf=
nnG
QIH+3JUhJtQOQPolA/ogIQbp7/8Bkc1RkQWFABJl2lRHspeuAR8n5aJhyo3Xk3w+6RfS5zI/g=
ys8
EwYRKL0/RLXc5H9m5oCrvvD4Blh+dh8auqX4bKUmTwJ2npKYSpNRmpNKFihBvflePeDkl1dwn=
HB/
nucN3ObWBA0K2rLlznjOWx9pLVGsb55QaQJJwYf5fSKy0Wovd/5hhu9rWpcnKCxsmAPfupW+i=
Ih5
fwUcpMTAat3WnW2xZVOdADXmK87BTQRfleitARAA2TSuLM9PlhfHk0a3CWavZx/J3+gKMh1rw=
BIU
IO7FaB9HZYt2xy1c/7Gh+07rSQ5Jhr6t3GT0ZxpqS6sHHkgEqDLHPjlu/NSMSaynuY2DzPlrF=
tKj
6LCcSvjJA0ABH/Ipmpf6pt6WxZ7OgKTxWNaUu9UcUpz4dFWS/PzyflsQmikyZd+Wd2Epctskp=
fPy
QWzdkDulf5f39mJViLY1jvMZA5ozwuWAItUHSkqpO0jc2Qj9wXYpisd2LrU+3Fefrz9iRr9H9=
wlG
ejDbmNImwHKzbV6VQret6pqlRAA1wsBam+2mMU0oiemgivLRw2hpEgzUVnbtED098IMEDTWMI=
wHY
/bj1SGTg2D7U3V38XeFadtxx2l+qBVvNmpup146Uz6uSbXGthz6pSPB/lmIlnIKh+vipTd1bO=
yLf
BYhJLNr0vKDhHRt+jjH+tDkPgEjl9FL98xc7hDv80uqhAPMCX3DdCqS0LRN/h+kCc42yg3W/C=
PgX
m8/r64yfGx6SU/47hV4wrZYnd+n6FjZ+i0Ta8TlmRLFTXmbpx+cSvKN3A9shEhVl90aYMK5a3=
nt9
6T3jpxuYIyeBtvFK24FNeumt/w3+ERVhw7Mt72E2NW3yi6d8AGsnd4gwoINaCStHYO0S13NVk=
eLH
VEy/Z0zzGlZfnjVmnDdLjgo6PWEZfWJHbv5OsmMAEQEAAcLDsgQYAQoAJhYhBAurrngd39qgk=
j2z
hhnX4849Pr6RBQJfleitAhsCBQkDwmcAAkAJEBnX4849Pr6RwXQgBBkBCgAdFiEEGGyG200+r=
qXB
ulPJnaKs97VvkHkFAl+V6K0ACgkQnaKs97VvkHl7lg/7BR0aJmcm5cmpMqyUfXVDj3RemxyuZ=
7Ms
YtKuOsJbqhdKSa4r8MOxkVm8lp7X/+6UQvAx3uW4YdGgJJZqvg2hcLtDoFAgvOANsdGCqK39t=
+GH
c/6xejWibeGKlzhRI5syOdBkjcM3j+JMBCjtdeuq9qKfuyi5PDTN2iInwkUSPFQCiu1uAMeIU=
0xP
BUzcWUBCZ/d82NNe7V1JMOQMqnPMst0qEvu7nBF/Bdp8Mmc777B8b3DHuH9L307qBsyp9oFaB=
1TG
PMkxvwsezMT6A/I40ACItnx9T4ceMkHXR5KBjZjTK3ZNdp3GM2Q4Y4lQh2wtc7zXZEcfu3omC=
HYn
0+O0jsXW9NNu+ktnpIvzDz3doQhoHRAEX8ljURi//VkBOJDnRfB4YLY3DeBf7WZyl4U0MvCAn=
4ON
lU7hJAF4+IESNC/k8x80imDx2MnA+ui21ZkzAyLwHR4fUhbbuRHNgl1fJPoAjIqvMQpCO6Ul5=
GgF
diB2l4BvB0D+oQJhwzIUCPXQikMJnfbv7Cy429k7xPaZQNLH8iGwLDqA6C5EnkPJ0BkRHrYRL=
961
GwtmSpprSChBcuzvvEQkIDKK+oLEeQAEZzf3y6bHj2uBe+60AABQc+JHeWCe8ZoSq/elD7uhD=
X18
JfrIT1aW6Ae+ZaCpk+xBjXRdbdSXDwIAMZOpUYLbSF+Glg/+M89nk3T7PVeqWGsmQ2mwk3k5d=
3Vq
Uh9N9OTnsi8e17JtwO2RDj0yKSF8cVNhJX3rXfVzpYeDHe02AuLX505SKsIt9ImswtzFrE5/I=
Ixp
bdCar290Q62hESIevzhR987Hpl/qFKikga6w77L+f+jbHlaMUFa59jHvM25kJA6FVil55Kyh9=
KCY
ylEIm2kD+q/VROY2E4NX2ynGvZh2lTrzhpYp2bQn5+8Nt/6IsZA/i8MSJ+Ltz+BLyGiGKIwad=
Dt7
v2z5TVhNgbd3RG8FhpX6vc9ZHpM3KZ1wvsv6iW0xAUwUlLuW8ShnGH2nQpnCZ3Ry2WYAZAFUE=
SbS
czbkj+tffH3Da6TIwUud+rhaEI5MoIePQKdASa9kKvtWiI1haWq9OS0eL9063LG+PudzTT3Jt=
aFg
ET2Xzwdp0gZ20J+jWa5UcPh+nC+7Jy2wdwFQI7YOTU49/Kp1Sny/IsvWc1Bh0Ce5OsKdgcklx=
0ND
Y6zziaKVdwE6Hxy3L4x0apky60LX8TLifFLqvF4BgFIchnBBjhFYcLwfNO/+VkM2GTWYxWADG=
Av6
HwOO2Xl3zZyN37rPtys+Hi+pgweNz9j51DlBqbAuzzuSoBAMpv67A/tJ7WtEGi7ooRUw0jT/c=
Wbd
qjAxoUQlejcGLKYrouO0+BPqq9IQe+6uKj15N2o9u7LYPFLOwU0EX5XpEQEQAMEURD7nQV5Qg=
2il
cn6LTWd7GBY1J7KnnGZkfEV6/Sg82JMqaxQ2idjeVAri4lpcTwl16fn6zqtvFT4Y1xoZAKKZW=
ObN
BgAMKEXcVBP8YJ+4JtsIuCM+pI5/nXX9riQ9SmtRPHWt6vus+TeYZRdEONvTtwHExRkaALXpS=
ojn
yjeSo32Pi5OV6r8MkDMllCXrba+dcVcIxtwwDLRyqCCe94rnrsZ7I/uQfqy8uF0PiQzsk9IDx=
sGN
ggFVJo6gT/HDfCPekSsKUURvNe2PLAIqOacoRS38PAn9+oKx/CYVAqem3yshoaMfF6jSGaXmn=
XhD
9nakNkI0s9t18u7Ft512qDPcXlHWKysYE9w8Uah4+ARWOeRJbg8jNh0A49jGtjsG/CBo9ZtF2=
meX
5hjj2tA7xPziwkPDCrpTTwCn4z8aOiiMzOSfgAYIx6j1E4X5Suzxdo5dlfrLfT/uLWVliDSBQ=
36C
IGDUQGbkGxXci5eTTE2vM4/++HfBTD1wDQCHZwlopchJSRdhKmWhiCKSONm0wsoRgbzhKCzKu=
2hD
yQub+9ozgxdfESyEsi3804g0Q5IbGv7LbcErX8KAxWovTgLAj4T+Ut3DsojO0sUCH5su8hgar=
mDB
HZ5GXzMsrhlTji+YSe+9Aa/wafCaSdkJ5QJKON0jovS0oHmXxYr5WlkfRUdNABEBAAHCwXwEG=
AEK
ACYWIQQLq654Hd/aoJI9s4YZ1+POPT6+kQUCX5XpEQIbDAUJA8JnAAAKCRAZ1+POPT6+kSyyD=
/92
kc8BkmlUaJ1IelM4GDMKfFZSpxPNrQQ38Zrcjp+YCcfpvFqYKNS35lo3DlEH/6d5To2FJ5pJn=
CxN
ew2Y+GQvC/Ug0h1pyRVT4fQBdFkBtQ4jOCwujVDDvh7BTtx8hUXif/PxC8qHo8zZO12PrzdXa=
WZR
3pkXhGgP/qvKeejZzBY13fhOXOPGtfDRU/qz9eNHKnBaAAyVvKq8awpIa6WGDNff5iMjIEN8H=
HTW
i2YeyyIwVo1/DxGAqsy1vV0eQyBw0JHKHnMoqE1VoTHv2bMsly0L6q9x33Z4+DNiNJlrk9KOG=
WFk
BAFMNZxhTHFW83owQojo13iOG5aJrxuljAvnFL4rYIdaYqve3ZXzvfumM/p8UPP2oI0XkayiT=
gpJ
S/5bkPLjpozLqeoUxSR2fxY2s43/FqFi8+PUzcFfOaAv3VAs1G7EoXQsXhu/SOR7+j2RROGUK=
Jxp
xHRyQuL5RavNEoeMF/n4QDYpCIAyBflovyhIW4btwuVm4bzf+f37VBEKFk5Ctq6Y8fR3h4s04=
7R7
xelho+p0EJuJoog1j3KtNqBD4OepVjXQSDQnLt/5SYFUsj6toNy02ygkkylLluObZY+GmDPuV=
td+
lSDSE4/2HWJLNymnuqqWod9Yn4JaVAvtt4UfwmGHVWzBCcwTi2AsFVrM6/c8cKr8dYZRkdF1f=
c7B
TQRflelFARAAxrnuqgo1ylltqBYI/MRWnOUnE9R1nLmFaCDuVAnEnFEVhReWccN3bCkMAR5CL=
eYK
XOrFniUCKReagGK3a7ftjtKwhz4yqiRMMNMA4YvUbjohyqKuPhJeJmCywQzyU59iP1Q3saNhb=
3ni
bcVTJ7hvJndQ9qhpaL6V5PfoRvAJZUobK2fY1za3ZTGuF0HQAEEuPiTdPgIUCshMlLMClOyeJ=
P7y
JXzTIktevNp16zS+QBMRW7NamZxB2rbIiA9KKzA5xoVautnK+l+LNsCk5mXBShQ9Z2NXB8vPW=
gMU
JeCMz9rO+YZCj+ihsuBcZwJwUO23BxfAx6UIBFbSNwypPL92qstwuLirK41Xt2w1YvpfFO/nj=
Lmv
2JVEvoHoaP2ZNusEsc1lF8BdMk/Zs+qPIH5QmuJRBGtjrwnfQxuyOg5fbKNaxj//HO90vAyj/=
Soy
KdiXJvaxYdYlHD3S2qqTDM3lAVOtIYxy2UXiGbrf6koh1L0DFCCFmWu+zJplWq+9V7Mq72kmq=
5dA
r6dASS+WTgTgbNoAIbtkqamA2RmS5b/Bg1XctqNZ6FnHGf0wBsPAQ3na5uA5V6ZgBxYCPyxHQ=
XqA
axO2aJTfxH6og70AKQJdoot6EhDsBOukbuh1pbdwUTR+E/PRMYdhTo9K+ztaXklqkqL2FG7iS=
11F
VhD2oifiJgcAEQEAAcLBfAQYAQoAJhYhBAurrngd39qgkj2zhhnX4849Pr6RBQJflelFAhsgB=
QkD
wmcAAAoJEBnX4849Pr6RXXkP/0qb5oHys6fu4eSyXryndtvS7JfZHz7J679o65AtANDwQ5a9M=
DMz
C5bn/tLtmIq5hKj1elA0Bj2XRiLp3VUIyH8sd/6UdDZlkzqnI1G4ny8Pq5GYHDzBaGf2tTx5n=
naF
9E9ftdveMXHV6aVIorjqdXDKhGB+9YIX4DrG+GGTKLWXRCnCFpqQL62Qs2GPhfwg+DQVvNtld=
LT/
F4x8AwdtrFamaZtYglRWPEjo8yhAsDuHYUK4r/ponQ5FDNjieso3xP54doIs0EizGq85t4j3P=
Rxa
4NZNILEs49EqgqWjmuEMDl2D7pglteZEYPnYJcf945PR4dQF0Lj0qMSFpt5OIbptkGZ4VgONp=
lKo
LwFaBU52IpudUiGi4YlG7B4tECzxvSwsMB4KByJrwQWuvL2kc6NDPChRpOrz/ra0+rJQ8jN61=
lrK
Sddn6vqV38MYT/fXrlVc+gTOZr5hEbdAF1nG9JSVbNI7nJZu09MrkNyGrDEaSa3X0LA6RFVEj=
M6L
2qFivqlk0CQHyNVLdHQCLkyc7n2qFGnTaN7GckyFtE53Yd19ntxKLMr9SA94vDt0xo9q4Hnsl=
pWU
TIQPNUcquRRBVyXZgHkxJDx77XnhEim1eqV9FhyP4TqYbbYVGbhjYu/QTRvKIqGQbQt/zFDL7=
WdL
qBtTdzvT/Y0zYQK/Rmma/tQ/
=3DEzgo
-----END PGP PUBLIC KEY BLOCK-----

--------------7485148D5C4BBAA575205AC8--

--pNOwyeKAe2PgDXTGysSMnXrvaeaWnxFUQ--

--bXPMvy3yvmXN3DfOfyHjy9FxmMZWJaMq5
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEGGyG200+rqXBulPJnaKs97VvkHkFAmAZDHcFAwAAAAAACgkQnaKs97VvkHlA
iQ/9EXebibJYpcQ0p8WQcm/HwCeBMfRYSrB1p/4sGyoyX0LHgj+LQaJ5LLLCBVhgc+rgbaVGmlcs
rtfNxsHqD5Fnt+/YelAATptaW3xkiilEVFEmRs+/DBivTTpzf9It5CwuPm4ep14xk4EdKgMD+8UV
ufFRKzzicmSWIrjQ8jRT8Ep4w4rTF3yxryiv6iEaT1CHE5TMARlHZ91brRbyS7mF0idAJAPtChuP
7jOG3RzxUt0EPNxpsgJ/hj4mZ3ppilDmaL1KHNxiT6fSMTaxqmmvbfB0fhHjxTMnk6Uwmg+5xdr0
7D70DD1xIfYfBrzcKpYlPmmAJsjk0N+UTF45X+vBp8jyoVfb7KTRFBt7Qk675BrFhanF3HuqzczO
wd4xPSmYEku5WEDmdRQ9mXmtfy9MfdJL+dFpUVHgn0NrxPBrHT3dDKy8JkW4ukoecxDdYKjDp2yT
zhDhVkjnqRG58gSpqyad2jNpM2uuPJDH599Ipa6mGQFgserYlPIBcI0ZLihrdyN6lfHX+wcGD9Cg
D1HqSXqJKVImaPTp0xFeN0nlaksG1b7NS7TJwXe+QWlcnZRHBGW8g0xRb1PuvcGCPJbIBYc9+3Mg
Cp+RkVwQJPxaKRRDUuQbt+b7nBkccZc/hq9amGR6luN6qs84g5+/ONhB3Yh6L2g5vsmdCS5JEX9K
EkM=
=dbcm
-----END PGP SIGNATURE-----

--bXPMvy3yvmXN3DfOfyHjy9FxmMZWJaMq5--


From nobody Tue Feb  2 08:15:07 2021
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B7B3A1BF5; Tue,  2 Feb 2021 08:15:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>, barryleiba@gmail.com, calext-chairs@ietf.org, calsify@ietf.org, draft-ietf-calext-valarm-extensions@ietf.org, mglt.ietf@gmail.com
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <161228250588.8877.12519186694626464530@ietfa.amsl.com>
Date: Tue, 02 Feb 2021 08:15:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/RGaFYDIZXfYnIRVngBkYGrhiGKk>
Subject: [calsify] Last Call: <draft-ietf-calext-valarm-extensions-04.txt> (VALARM Extensions for iCalendar) to Proposed Standard
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Feb 2021 16:15:06 -0000

The IESG has received a request from the Calendaring Extensions WG (calext)
to consider the following document: - 'VALARM Extensions for iCalendar'
  <draft-ietf-calext-valarm-extensions-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2021-02-16. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document defines a set of extensions to the iCalendar VALARM
   component to enhance use of alarms and improve interoperability
   between clients and servers.

   This document updates RFC5545.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



No IPR declarations have been submitted directly on this I-D.






From nobody Wed Feb 10 04:44:49 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0593A0EC6; Wed, 10 Feb 2021 04:44:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Valery Smyslov via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: calsify@ietf.org, draft-ietf-calext-valarm-extensions.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161296108746.13523.4234835837695144328@ietfa.amsl.com>
Reply-To: Valery Smyslov <valery@smyslov.net>
Date: Wed, 10 Feb 2021 04:44:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Z2_fC76mAaYXOawIE7PujEw1ejg>
Subject: [calsify] Secdir last call review of draft-ietf-calext-valarm-extensions-04
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Feb 2021 12:44:48 -0000

Reviewer: Valery Smyslov
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
Document editors and WG chairs should treat these comments just like any other
last call comments.

The draft defines a set of extensions to the VALARM component of iCalendar.
The document is short and well written, its Security Considerations and Privacy Considerations
sections are sensible. I found the document ready.

Nit: I would recommend adding a sentence to the Security Considerations section saying that 
these VALARM extensions inherited security properties of iCalendar [RFC5545].




From nobody Wed Feb 10 05:18:34 2021
Return-Path: <murch@fastmail.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 9307E3A0FC5; Wed, 10 Feb 2021 05:18:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=fastmail.com header.b=eDDFRlml; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=sjf1R1Iy
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 fFIuthlKeNM0; Wed, 10 Feb 2021 05:18:30 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF0B13A0FBD; Wed, 10 Feb 2021 05:18:30 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 21A6D5C020F; Wed, 10 Feb 2021 08:18:30 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 10 Feb 2021 08:18:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=WaHfuOLWVaLpq9BSdRnvauia+fL E9ASVWhmf/k4MjVY=; b=eDDFRlmlU61rV8Jl5f+TPecLUzW088J7bjPg8sgQgVY 5ELXKDLNPV6WO4N9kpXWulgbqHYu46PysgFB+1AXa2Zbf+QYLPdTAnpNToA9LF2k mTS9Oq3Bcu9c8g4zuNtxadGFqJ2D/iHoKRZa9l1WcPjykV9BZrxMaa8nai0RB9DA jyObalY1noZhX7Ch4gC8cwwVJxfJnCnQvFhaZdZTPzsppXelKPKdBlw0OA94RZvE ctXzWHup3dMh0SYePSAYa/ohNEXKJFpYXGZ7+cTs1ZsZGPC3RRfKB/ZFP8iToS0/ FHabRkIwMHhLyFTtdGuXBkiVJe/AaBCSRSFeMe2Tdjw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=WaHfuO LWVaLpq9BSdRnvauia+fLE9ASVWhmf/k4MjVY=; b=sjf1R1Iy/0h9UBPwiE/Si3 cMnebkHFUWNuJzEGNRjXQVSXpAhc9Rr+lh0sQO1jiE/3Eoeo6XgHJxevMrafy1GG RwD85OceQvWu1wxKBoNIvecjXSfxIZYegp0rfF8AN3wOtkQ6Rwhca6nWSf5SN5eJ cKtxc0zVsoX9IRTVajqPCGGVoBIeg+JIyV0Td98A+/tYP5nZ57J6HvPu19uO6AAG azPUbbgZXgJ1Ar8xZQ8eesi954yF+Hm6TBhRuPYQ1/XKJ0GNRDF6d9GYTcRaxEYc q7uU+u6SHED2SUujp4UwTSb4tlMp9PsF4RcB6Ft1KBhkzs+m+wfUvaHgHMYNbs3g ==
X-ME-Sender: <xms:Jd0jYDo5mxTyB4fhSszRO16ljsiZaL_v-fElFYyOnMeZRg9_yocxiA> <xme:Jd0jYC6D-FefYjiV8oCIIthekt2xTg9GO3oqm7nJtQ6X72dcxnfklzpMyopz5aNnf YTdTVES_vdvZQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrheejgdehtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgesrgdtreertdefjeenucfhrhhomhepmfgvnhcuofhu rhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrfgrth htvghrnhepffeuhfevgffgvdduuedvteeijeeuvddvkedugeegvdffvefgudffueeileeg geegnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeegrdejjedrkeehrddvhe dtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhu rhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:Jd0jYB7OpmWNO27le-pzrwD9TmTKhkw64FDqsjpHWQ26RhIrleC9SQ> <xmx:Jd0jYPGsJWFAox0dmyy1GvQCKFIPzuSZy8LXdf6UZFaSiZqAv2qgYQ> <xmx:Jd0jYKRxccpT_ggL4nqXt-nIRmQ5JVDr3--vQPsc35HFKI54UVpDIw> <xmx:Jt0jYN1p2wTnZ0PsYRylMceWZmx3tVM-PjGPGwE2pMRt-SqKNNGSQw>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id B2A291080069; Wed, 10 Feb 2021 08:18:29 -0500 (EST)
To: Valery Smyslov <valery@smyslov.net>, secdir@ietf.org
Cc: calsify@ietf.org, draft-ietf-calext-valarm-extensions.all@ietf.org, last-call@ietf.org
References: <161296108746.13523.4234835837695144328@ietfa.amsl.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <c244b012-3ecb-95b6-fec4-b8ebec3086e2@fastmail.com>
Date: Wed, 10 Feb 2021 08:18:28 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <161296108746.13523.4234835837695144328@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------428DE647C397FD62D781091F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/sUS0H2iH6JNwzPW1hk_BUrIDRXI>
Subject: Re: [calsify] Secdir last call review of draft-ietf-calext-valarm-extensions-04
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: Wed, 10 Feb 2021 13:18:33 -0000

This is a multi-part message in MIME format.
--------------428DE647C397FD62D781091F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Valery,

Thank you for the review.  Per your recommendation, I have added the 
following phrase to the beginning of the Security Considerations section:

"In addition to the security properties of iCalendar (see Section of 
[RFC5545] <https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi#RFC5545>), 
..."

Is this sufficient, or do you have alternative text that you'd like to see?


On 2/10/21 7:44 AM, Valery Smyslov via Datatracker wrote:
> Reviewer: Valery Smyslov
> Review result: Ready
>
> I have reviewed this document as part of the security directorate's ongoing
> effort to review all IETF documents being processed by the IESG.  These
> comments were written primarily for the benefit of the security area directors.
> Document editors and WG chairs should treat these comments just like any other
> last call comments.
>
> The draft defines a set of extensions to the VALARM component of iCalendar.
> The document is short and well written, its Security Considerations and Privacy Considerations
> sections are sensible. I found the document ready.
>
> Nit: I would recommend adding a sentence to the Security Considerations section saying that
> these VALARM extensions inherited security properties of iCalendar [RFC5545].
>
>
>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------428DE647C397FD62D781091F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Valery,</p>
    <p>Thank you for the review.  Per your recommendation, I have added
      the following phrase to the beginning of the Security
      Considerations section:<br>
    </p>
    <p><font face="monospace">"In addition to the security properties of
        iCalendar (see Section of <a
          href="https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi#RFC5545"
          class="xref">[RFC5545]</a>), ..."</font></p>
    <p>Is this sufficient, or do you have alternative text that you'd
      like to see?</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2/10/21 7:44 AM, Valery Smyslov via
      Datatracker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:161296108746.13523.4234835837695144328@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Reviewer: Valery Smyslov
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
Document editors and WG chairs should treat these comments just like any other
last call comments.

The draft defines a set of extensions to the VALARM component of iCalendar.
The document is short and well written, its Security Considerations and Privacy Considerations
sections are sensible. I found the document ready.

Nit: I would recommend adding a sentence to the Security Considerations section saying that 
these VALARM extensions inherited security properties of iCalendar [RFC5545].



</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </body>
</html>

--------------428DE647C397FD62D781091F--


From nobody Wed Feb 10 05:20:57 2021
Return-Path: <murch@fastmail.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 55D353A0FD2; Wed, 10 Feb 2021 05:20:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=fastmail.com header.b=Q/vZ8yUx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=voR+P45E
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 rHwGhHWT-2PF; Wed, 10 Feb 2021 05:20:49 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CBD93A0FCF; Wed, 10 Feb 2021 05:20:49 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 5BF8F5C0207; Wed, 10 Feb 2021 08:20:48 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 10 Feb 2021 08:20:48 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:from:to:cc:references:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=lkeE1/ScwmCaRjT1G9twD85TiS7 s/dUkFBfymlXutYk=; b=Q/vZ8yUxK+/gIJENuj2vBPoQTpJBXSL3/y2cYexgrU6 BtL5fRo5fbKZTj6l8rGxDuRgLSj7oBGWfrn8/OCVlY3U9dM5EduI5iLMUzNKT+t4 /Z3xz+led4tzOkHM0ZLqxo4HpsdbvdwVvQq1fEESUsuyPftLtbZK4DP9mSWPrjBc WwK0rTxWWnTdJbUnoIBHhz28MkIhBvoVQ+hRzDbTlH4JHMntER4YEMqHl9kRzN4l 2swZubwTRnUXkX8z8DuR5JCkVoQYloBvdV5AeDKcLIIqcawd7AlpjdEEZaQ0ITTl yExtnbfFWtLrEya93cZtjzpyercH9G4iGUGbhqrhr9A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=lkeE1/ ScwmCaRjT1G9twD85TiS7s/dUkFBfymlXutYk=; b=voR+P45EAlo3rWb5jfci8e IpSk6lVOI74AsO/LUEo/XC9ubN4A4Xhq0B06kpxdZN5Vp6KjllmL18+PLY6EwvQv n+T5iF2ZCJVcorPLQsOFQ03LQaTF4jxYtu9MF8MjUtPXZxnxYsKnGy5y3+jWXSOj bZf87m0CdXOZRxC6Dxmc3PKEKp6aqgE45xgiWC8tFf7PuXQ84udr03wsF4yYhJtr q9w+t0zyhAYROGGU6iml4jXqquebQqtas0ftC9Fxln+esDoEf6jQK+S6AP61DNTQ 0ns0Ey6vs0ke5vftoaApiOP+9btzpYKPqd/q4Qq1Clyp/+5DY6gMreBJP9EwO+pA ==
X-ME-Sender: <xms:r90jYOpOjpIdrDXIUGqvZycWgawhsXDFq1ddxIgV1bNxK56jBaSU-Q> <xme:r90jYMrxKzVb3qBLGE0AM2DKPh39Ak0tSsVXx3UT_ewh1z_LvmTBOxjNHb0IPRDMw oIsPAVT2IfEuQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrheejgdehudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuhffvfhfkffgfgggjtgesrgdtreertdefjeenucfhrhhomhepmfgvnhcuofhu rhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrfgrth htvghrnhepvdefueejffdukedtfffhjeejtdffudejhfdvkeeujeffjeevgeekffelgefg vddvnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeegrdejjedrkeehrddvhe dtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhu rhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:r90jYDPHiShp3degBWLUwyv8XdXKqOnLvFR9qczvdZ7ZEO8o4wzVkg> <xmx:r90jYN4OiS18hO_QmAz0xIsC_bUDwTTgxLNagbTsRcp0Hk1fbQn9Tg> <xmx:r90jYN6MovvSK49ClmZN95SG19YlCV0aAu2ZNkDRmseL8Ymw9brvJA> <xmx:sN0jYNEXU2C0WwLQm74I5WiKS3eu8pbPf4jAhUelbu9ghPHFA6pw9A>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 837A9108006B; Wed, 10 Feb 2021 08:20:47 -0500 (EST)
From: Ken Murchison <murch@fastmail.com>
To: Valery Smyslov <valery@smyslov.net>, secdir@ietf.org
Cc: calsify@ietf.org, draft-ietf-calext-valarm-extensions.all@ietf.org, last-call@ietf.org
References: <161296108746.13523.4234835837695144328@ietfa.amsl.com> <c244b012-3ecb-95b6-fec4-b8ebec3086e2@fastmail.com>
Message-ID: <c3b99101-d778-4012-8910-f3a10e086d19@fastmail.com>
Date: Wed, 10 Feb 2021 08:20:47 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <c244b012-3ecb-95b6-fec4-b8ebec3086e2@fastmail.com>
Content-Type: multipart/alternative; boundary="------------97990FC17170505E4241F062"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/ifQWqOcf8AnroZ14N7eI39-QBmU>
Subject: Re: [calsify] Secdir last call review of draft-ietf-calext-valarm-extensions-04
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: Wed, 10 Feb 2021 13:20:52 -0000

This is a multi-part message in MIME format.
--------------97990FC17170505E4241F062
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 2/10/21 8:18 AM, Ken Murchison wrote:
>
> Hi Valery,
>
> Thank you for the review.  Per your recommendation, I have added the 
> following phrase to the beginning of the Security Considerations section:
>
> "In addition to the security properties of iCalendar (see Section of 
> [RFC5545] 
> <https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi#RFC5545>), ..."
>
Copy and paste error above: this should say "Section 7 of"


> Is this sufficient, or do you have alternative text that you'd like to 
> see?
>
>
> On 2/10/21 7:44 AM, Valery Smyslov via Datatracker wrote:
>> Reviewer: Valery Smyslov
>> Review result: Ready
>>
>> I have reviewed this document as part of the security directorate's ongoing
>> effort to review all IETF documents being processed by the IESG.  These
>> comments were written primarily for the benefit of the security area directors.
>> Document editors and WG chairs should treat these comments just like any other
>> last call comments.
>>
>> The draft defines a set of extensions to the VALARM component of iCalendar.
>> The document is short and well written, its Security Considerations and Privacy Considerations
>> sections are sensible. I found the document ready.
>>
>> Nit: I would recommend adding a sentence to the Security Considerations section saying that
>> these VALARM extensions inherited security properties of iCalendar [RFC5545].
>>
>>
>>
> -- 
> Kenneth Murchison
> Senior Software Developer
> Fastmail US LLC

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------97990FC17170505E4241F062
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2/10/21 8:18 AM, Ken Murchison
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:c244b012-3ecb-95b6-fec4-b8ebec3086e2@fastmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p>Hi Valery,</p>
      <p>Thank you for the review.  Per your recommendation, I have
        added the following phrase to the beginning of the Security
        Considerations section:<br>
      </p>
      <p><font face="monospace">"In addition to the security properties
          of iCalendar (see Section of <a
            href="https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi#RFC5545"
            class="xref" moz-do-not-send="true">[RFC5545]</a>), ..."</font></p>
    </blockquote>
    <p>Copy and paste error above: this should say "Section 7 of"<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:c244b012-3ecb-95b6-fec4-b8ebec3086e2@fastmail.com">
      <p>Is this sufficient, or do you have alternative text that you'd
        like to see?</p>
      <p><br>
      </p>
      <div class="moz-cite-prefix">On 2/10/21 7:44 AM, Valery Smyslov
        via Datatracker wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:161296108746.13523.4234835837695144328@ietfa.amsl.com">
        <pre class="moz-quote-pre" wrap="">Reviewer: Valery Smyslov
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
Document editors and WG chairs should treat these comments just like any other
last call comments.

The draft defines a set of extensions to the VALARM component of iCalendar.
The document is short and well written, its Security Considerations and Privacy Considerations
sections are sensible. I found the document ready.

Nit: I would recommend adding a sentence to the Security Considerations section saying that 
these VALARM extensions inherited security properties of iCalendar [RFC5545].



</pre>
      </blockquote>
      <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </body>
</html>

--------------97990FC17170505E4241F062--


From nobody Wed Feb 10 05:33:10 2021
Return-Path: <smyslov.ietf@gmail.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 1FCA73A0FED; Wed, 10 Feb 2021 05:33:04 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=gmail.com
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 BOPIBPxXpe-o; Wed, 10 Feb 2021 05:33:02 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 DCEFC3A0FEC; Wed, 10 Feb 2021 05:33:01 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id l12so3020937edt.3; Wed, 10 Feb 2021 05:33:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=kiYb9XsXypYSW/XSeW0U/9cLZac76nHv4gmLMWNbh3Q=; b=n8VamtSxmLeI4dOjRlIHhT86xTbELfBY6nHEj4SFZUwPIDrxpKehwLnkksFsEgJV6e lOyX6wtECwuu2a5EkWq0v33ucu0u138EuuA1TgOLdxPJs7E+Rd+dpooZaBI8dl3Vvx/F EBsak8YdruVd4FcvNx9qE4vRfBxauD7lEQr2bmrmA9SxJ/KTC5W9u11l8hrQ4bd0IjQg DzekufmAeHVZ9E86nmjZNU3XKbSoh8Al/6rQMEkUbP5bpr7LdS+P1QGFWNaG2XoLkE5+ 4wa+8+13GeBHs1cc3lgJrEOSBM6oQhyiwf9GSorXqhjU3d0XE3Vj0PFUsxGZqQU/xioW lo6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=kiYb9XsXypYSW/XSeW0U/9cLZac76nHv4gmLMWNbh3Q=; b=DcpxIIIq8CssVlZ8RxH8nVQiDlOWyL6KF3GO6wuwEXLOdCEiX7JJFH7aYuoI+UlYSt 6o9diICS0usxKSxZQqJoOam2pALJwh54GwZVzRRqy3uoJhFeOUQK6KBLLTbxl7YfwTOz e1fafeu/rBWIdfJBwL6c9N7E8qiwk3ymMsWdjK9b5xnzb7S4Qt1DL4oMYAsEd5sh+8yJ 5Lsmvi3OZ/EA3cXEbHUehBkNsLz/y+Xqq5FWXSycVB/rYjKqQVU5Vi2tISbM174Juvm4 /3VJjhhV8LB/nL6fpf7+Tx3ged/GV5fS572q4gjL3PcNFMq96m1DaoOh8iJgUQA5XAqa yF5A==
X-Gm-Message-State: AOAM531yy49fzFfU8Gman1HEjeepW9jt7DGpfwKNVcJ7eoLwOK0y03oB bXkMp1Vpc7Hruna7ZZtnP6uPJQuEdbY=
X-Google-Smtp-Source: ABdhPJy6IEUK5fQwbJ1+pb7aWb9bZ1ia/DFatGKGuh6UMQmlvX/XJDwE3jiJkCgmt1qUWdCicoRWBQ==
X-Received: by 2002:a05:6402:1398:: with SMTP id b24mr3050535edv.108.1612963978917;  Wed, 10 Feb 2021 05:32:58 -0800 (PST)
Received: from buildpc ([93.188.44.203]) by smtp.gmail.com with ESMTPSA id c3sm1027535edr.94.2021.02.10.05.32.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Feb 2021 05:32:58 -0800 (PST)
From: "Valery Smyslov" <smyslov.ietf@gmail.com>
To: "'Ken Murchison'" <murch@fastmail.com>, "'Valery Smyslov'" <valery@smyslov.net>, <secdir@ietf.org>
Cc: <last-call@ietf.org>, <calsify@ietf.org>, <draft-ietf-calext-valarm-extensions.all@ietf.org>
References: <161296108746.13523.4234835837695144328@ietfa.amsl.com> <c244b012-3ecb-95b6-fec4-b8ebec3086e2@fastmail.com>
In-Reply-To: <c244b012-3ecb-95b6-fec4-b8ebec3086e2@fastmail.com>
Date: Wed, 10 Feb 2021 16:33:00 +0300
Message-ID: <03b801d6ffb1$40de67e0$c29b37a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03B9_01D6FFCA.662D2680"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLTTaZ0+UFogF+cMETFyy7NkxKZ3AJur/63qEVQr2A=
Content-Language: ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/hlgug8mIdjOAd_8MzEXCKQK6XwQ>
Subject: Re: [calsify] [Last-Call] Secdir last call review of draft-ietf-calext-valarm-extensions-04
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: Wed, 10 Feb 2021 13:33:04 -0000

This is a multipart message in MIME format.

------=_NextPart_000_03B9_01D6FFCA.662D2680
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Kenneth,

=20

I think this addition is OK.

=20

Thank you,

Valery.

=20

Hi Valery,

Thank you for the review.  Per your recommendation, I have added the =
following phrase to the beginning of the Security Considerations =
section:

"In addition to the security properties of iCalendar (see Section of =
[RFC5545] <https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi#RFC5545> =
), ..."

Is this sufficient, or do you have alternative text that you'd like to =
see?

=20

On 2/10/21 7:44 AM, Valery Smyslov via Datatracker wrote:

Reviewer: Valery Smyslov
Review result: Ready
=20
I have reviewed this document as part of the security directorate's =
ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area =
directors.
Document editors and WG chairs should treat these comments just like any =
other
last call comments.
=20
The draft defines a set of extensions to the VALARM component of =
iCalendar.
The document is short and well written, its Security Considerations and =
Privacy Considerations
sections are sensible. I found the document ready.
=20
Nit: I would recommend adding a sentence to the Security Considerations =
section saying that=20
these VALARM extensions inherited security properties of iCalendar =
[RFC5545].
=20
=20
=20

--=20
Kenneth Murchison
Senior Software Developer
Fastmail US LLC

------=_NextPart_000_03B9_01D6FFCA.662D2680
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#44546A;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DRU link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546=
A'>Hi Kenneth,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546=
A'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546=
A'>I think this addition is OK.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546=
A'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546=
A'>Thank you,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546=
A'>Valery.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546=
A'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><p><span lang=3DEN-US>Hi Valery,<o:p></o:p></span></p><p>Thank =
you for the review.&nbsp; Per your recommendation, I have added the =
following phrase to the beginning of the Security Considerations =
section:<o:p></o:p></p><p><span style=3D'font-family:"Courier =
New"'>&quot;In addition to the security properties of iCalendar (see =
Section of <a =
href=3D"https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi#RFC5545">[RFC5=
545]</a>), ...&quot;</span><o:p></o:p></p><p>Is this sufficient, or do =
you have alternative text that you'd like to =
see?<o:p></o:p></p><p><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On =
2/10/21 7:44 AM, Valery Smyslov via Datatracker =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Reviewer: Valery =
Smyslov<o:p></o:p></pre><pre>Review result: =
Ready<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I have reviewed =
this document as part of the security directorate's =
ongoing<o:p></o:p></pre><pre>effort to review all IETF documents being =
processed by the IESG.=C2=A0 These<o:p></o:p></pre><pre>comments were =
written primarily for the benefit of the security area =
directors.<o:p></o:p></pre><pre>Document editors and WG chairs should =
treat these comments just like any other<o:p></o:p></pre><pre>last call =
comments.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>The draft =
defines a set of extensions to the VALARM component of =
iCalendar.<o:p></o:p></pre><pre>The document is short and well written, =
its Security Considerations and Privacy =
Considerations<o:p></o:p></pre><pre>sections are sensible. I found the =
document ready.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Nit: I =
would recommend adding a sentence to the Security Considerations section =
saying that <o:p></o:p></pre><pre>these VALARM extensions inherited =
security properties of iCalendar =
[RFC5545].<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</=
o:p></pre><pre><o:p>&nbsp;</o:p></pre></blockquote><pre>-- =
<o:p></o:p></pre><pre>Kenneth Murchison<o:p></o:p></pre><pre>Senior =
Software Developer<o:p></o:p></pre><pre>Fastmail US =
LLC<o:p></o:p></pre></div></div></body></html>
------=_NextPart_000_03B9_01D6FFCA.662D2680--


From nobody Fri Feb 12 16:39:09 2021
Return-Path: <agenda@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 20F9A3A11CE; Fri, 12 Feb 2021 16:33:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <calext-chairs@ietf.org>, <mglt.ietf@gmail.com>
Cc: barryleiba@computer.org, calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161317641612.31337.9248630303932259864@ietfa.amsl.com>
Date: Fri, 12 Feb 2021 16:33:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Ywj5eO8E4vFantsX99QCOvSh68g>
Subject: [calsify] calext - Requested session has been scheduled for IETF 110
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Feb 2021 00:33:46 -0000

Dear Daniel Migault,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    calext Session 1 (1:00 requested)
    Wednesday, 10 March 2021, Session II 1530-1630
    Room Name: Room 1 size: 501
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/110/sessions/calext.ics

Request Information:


---------------------------------------------------------
Working Group Name: Calendaring Extensions
Area Name: Applications and Real-Time Area
Session Requester: Daniel Migault


Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 20
Conflicts to Avoid: 
 Chair Conflict: ace tls add saag homenet ipsecme dprive drip jmap extra







People who must be present:
  Barry Leiba
  Bron Gondwana
  Daniel Migault

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Mon Feb 15 02:32:22 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DEA33A10E8; Mon, 15 Feb 2021 02:32:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: calsify@ietf.org, draft-ietf-calext-valarm-extensions.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161338513250.5032.11173671129331374190@ietfa.amsl.com>
Reply-To: Roni Even <ron.even.tlv@gmail.com>
Date: Mon, 15 Feb 2021 02:32:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/q0Zoffabuh_-49TojL1pDjhJi-E>
Subject: [calsify] Genart last call review of draft-ietf-calext-valarm-extensions-04
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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 10:32:13 -0000

Reviewer: Roni Even
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-calext-valarm-extensions-??
Reviewer: Roni Even
Review Date: 2021-02-15
IETF LC End Date: 2021-02-16
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is ready for publication as standard track RFC with nits

Major issues:

Minor issues:

Nits/editorial comments:

1. The structured-location is optional so if it is not specified for proximity
I assume that it implies current location?




From nobody Mon Feb 15 04:27:16 2021
Return-Path: <murch@fastmail.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 A48443A121B; Mon, 15 Feb 2021 04:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-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=fastmail.com header.b=nFj5CVMn; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=lHB1Eyv1
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 RoxQEih8G9aB; Mon, 15 Feb 2021 04:27:13 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D1933A1219; Mon, 15 Feb 2021 04:27:13 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2C8005C009B; Mon, 15 Feb 2021 07:27:12 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 15 Feb 2021 07:27:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=s 12W5IjmeldeaoKkJurQTHBnYWOQqhhuFCevbXbu2ZA=; b=nFj5CVMno4T3j7kq6 S72Rjv1XisXUnZDYaz8fJ29Yui16aZ25VNfDliQYuX8g4obSCKH6Goq3qXaB0h3A L6WhM5QmL9NTBX5SIJ2bulKFdfealoYHh2l7XwIGsfmn90/2xGnN/lvVxkzcRRgt E7KMU08QJ2ZMjxBMZ3P+PCiQYJNUEAP2RqSp9Ws4DRzLcBd45IVT8QDSdoKOLG1S RWl3TO0sSc3rG5vqUBb3mQjajjUN0dTPzaA6AL4haBvsN7a5tcW5fm4aHLt3vegy R2zZcnF5yXsRFJzPzpjXspV2PRCith2wGI5f59c75OT+mBVJww4CDjRMBVQTeBaM GU21Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=s12W5IjmeldeaoKkJurQTHBnYWOQqhhuFCevbXbu2 ZA=; b=lHB1Eyv1QwXo6Msix4xCEKM/Twgx+dh6Szq2xxvOL1pOhSxuctWlc4E0O 4fC3eNYBFlOajze8xRn3TBYWG18dlcJ4XLw1KlDUSZV638ON2v+Ueu7P3hxnRUT2 2ww2F6yNs2/U97w+Q4FCbbTtqNQA5cyhwrPupihkbAPqTrOHotArDiPMB0y04qIv qy8bTU4OnypcyW2A+fT4IBBr2P6i6JR+ciA58fG41rnEq0rpu9Tgypvmg6LeaZwJ Ae48MYXyMZ0hXKEmBf61F4XZgk1ofj5wTM1Hi8zOT1hVRKyNhudZOnjinQZbv3hb jjIzLB0/wmJXsOD0TAZcUU/O1/b7w==
X-ME-Sender: <xms:n2gqYLYENYmEohNkb2IDPXeZqz1evsn35hAU-yvQfcb25mZ9esGDVQ> <xme:n2gqYKahjIHaj1suKpA5M6LxNiT1puFZCUPj_1ft9keglzU6ohg9q8t6gEZucvayu P7o-WrPGZzQDw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrieekgdefjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvnhcuofhurhgthhhishhonhcuoehmuhhrtghhsehfrghs thhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepvdeutedugeeiffeitedvhfeiud etvdegjeekkedutedvvddvudetjeevgffhvdeknecuffhomhgrihhnpehivghtfhdrohhr ghenucfkphepjeegrdejjedrkeehrddvhedtnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:n2gqYN9PhHIBZI87B7zuF6x-3VETEQYtRXuGgUps9AJ5V0rsfhweaw> <xmx:n2gqYBrIj-qSzYccKE5BZTkoWChSH58HD0H8FJjgSFxdz1zCOluJzg> <xmx:n2gqYGpTO00pUYAs8m34WT0GVZEHT-qsZjgj5li94CR9uL4lVFOQlw> <xmx:oGgqYN2jkW5C43gcgmWcMp4yGjhN9ZUJLxrYg4kha8ApcfGiD-A_Wg>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 7F69D240057; Mon, 15 Feb 2021 07:27:11 -0500 (EST)
To: Roni Even <ron.even.tlv@gmail.com>, gen-art@ietf.org
Cc: calsify@ietf.org, draft-ietf-calext-valarm-extensions.all@ietf.org, last-call@ietf.org
References: <161338513250.5032.11173671129331374190@ietfa.amsl.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <a87b7942-9976-39c5-43dd-23f4acfa9a6a@fastmail.com>
Date: Mon, 15 Feb 2021 07:27:10 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <161338513250.5032.11173671129331374190@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/QNLizQpUJalveYtmnbClaXER73I>
Subject: Re: [calsify] Genart last call review of draft-ietf-calext-valarm-extensions-04
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 12:27:15 -0000

Hi Roni,

Thanks for the review.  Your comment is addressed below.


On 2/15/21 5:32 AM, Roni Even via Datatracker wrote:
> Reviewer: Roni Even
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-calext-valarm-extensions-??
> Reviewer: Roni Even
> Review Date: 2021-02-15
> IETF LC End Date: 2021-02-16
> IESG Telechat date: Not scheduled for a telechat
>
> Summary:
> The document is ready for publication as standard track RFC with nits
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>
> 1. The structured-location is optional so if it is not specified for proximity
> I assume that it implies current location?


STRUCTURED-LOCATION is optional because its not used for PROXIMITY: 
[DIS]CONNECT.  I've made the following change to the text:

              <t hangText="Description:">This property is used to
              indicate that an alarm has a location-based trigger. Its
              value identifies the direction of motion used to trigger
-            the alarm. One or more location values are set using
+            the alarm. One or more location values MUST be set using
              "STRUCTURED-LOCATION" properties.</t>

Is this sufficient?

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Mon Feb 15 09:29:45 2021
Return-Path: <mikeadouglass@gmail.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 2AFB83A0E11 for <calsify@ietfa.amsl.com>; Mon, 15 Feb 2021 09:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.802
X-Spam-Level: 
X-Spam-Status: No, score=0.802 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6y8DPtO6mw5z for <calsify@ietfa.amsl.com>; Mon, 15 Feb 2021 09:29:41 -0800 (PST)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (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 B56E33A0E04 for <calsify@ietf.org>; Mon, 15 Feb 2021 09:29:41 -0800 (PST)
Received: by mail-qv1-xf2d.google.com with SMTP id t18so3464586qvn.8 for <calsify@ietf.org>; Mon, 15 Feb 2021 09:29:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:message-id:date:user-agent:mime-version :content-language; bh=ciY7JjEe0wiLsFAp+dmLnporjx2AZwKCBYRwF57fscg=; b=Ft9Ek7Ik7vNnjgaXtBg7XL+KSE5AEOn3SCsJnCdLpzI2pj4ApnmULxT1Rs/XT3K5i2 dggE3ZtZglUNhXJuz3xgagi3I5/kljl536AkwwMLbSyFbFR4N84q15nHC/eSitCEwSgh +WmUzDF2aDRJt/AEhCCpikafj8jpRMmrrgJthQeJLxDiiVFu2QuB9iO4LIayVzXTWNb4 QSdlip8jik6+Yt+beiZSBAQniMz0jG5ui9J7/iftkNTjrvJdVYCQ2Dx+2R36xtCCSNhn BKyOtZ/WWKx5cj2BW8zJ0p+Hy+pIVvO47fgZPUNrOYbeOt4oAvK3db+JBaZaF23Gy+bP nkhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language; bh=ciY7JjEe0wiLsFAp+dmLnporjx2AZwKCBYRwF57fscg=; b=q3owWX9ryj22h+QWlHA41ESLLECsH4v15uyP9iODrDyJyiC5zJFWhXKCBtXr52OeT8 ZHDDeKuWMev81nyKV86QH+H+V1D6TcuL56xjvSAqnicfBrzk/hgtCZHlXg6d4/wQK5M5 Z8RJCdZWT1ZzeqcI9yngUepMbT5QlFXpCFW08W3FKA95GltTY0sN6d/fvpYgJ3p5+D6j Y3Wf8x+4tFo3VrsyeDyiq5hxambv9V529xCdA5vE9FIFpDVz9tz2mXaNu9U+uxBaHIxT 13g84BD0tJY9s/FwMeacLGLGVSigvrjrNVdOTIDyZjVAYTRVvzCHlQ1mJo0DobIxuiou rojQ==
X-Gm-Message-State: AOAM532khWHCuqMvQFtxtS1PSbg/t/EA8SGygSg7sOcVbYPwkKdWECxw I5ORO/Q0sWkz4g4H3ivCT7DrUrcTXXU=
X-Google-Smtp-Source: ABdhPJzlzogNm/j0w2zDRaSz0ScnOd+g4XNjcG9frfEK+JF22oxfH08qX5Pd18rODPD+gAJJ/UDm/w==
X-Received: by 2002:ad4:57a2:: with SMTP id g2mr15574832qvx.33.1613410180202;  Mon, 15 Feb 2021 09:29:40 -0800 (PST)
Received: from [192.168.1.150] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id w28sm2372217qtv.37.2021.02.15.09.29.39 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 Feb 2021 09:29:39 -0800 (PST)
To: Calsify <calsify@ietf.org>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <cf63883d-e134-62ea-3e53-af6945b755e1@gmail.com>
Date: Mon, 15 Feb 2021 12:29:38 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------2BD50C6BE940E9D682CC7B71"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/BBvvuWI9rmBHEWNN19eaNQXJ2TU>
Subject: [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 17:29:43 -0000

This is a multi-part message in MIME format.
--------------2BD50C6BE940E9D682CC7B71
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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.

I suggest we add a calendarAddress property which maps on to the value 
of the ORGANIZER or ATTENDEE properties.

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.

I'd suggest that sendTo only be used for non-iMip alternatives - or if 
iMip really should be sent to a different address from email.

So the above would become:

"participants": {

    "123": {

       ....

      "calendarAddress": 
"/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/"

     "email": "mikeadouglass@gmail.com"

      ...}


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.

I believe there's no mapping for the jscalendar "invitedBy" from 
iCalendar - is that so?



--------------2BD50C6BE940E9D682CC7B71
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I ran into a problem mapping iCalendar ATTENDEE onto jscalendar
      participants.</p>
    <p>For example I might have an ATTENDEE that looks like</p>
    <p>ATTENDEE;CN=Michael
      <a class="moz-txt-link-abbreviated"
href="mailto:Douglass;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=mikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/">Douglass;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=mikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/</a></p>
    <p>The value is a URI but certainly not an email address.</p>
    <p>Additionally the value is used as a unique key to the attendee -
      something we don't have clearly defined in jscalendar. <br>
    </p>
    <p>I suggest we add a calendarAddress property which maps on to the
      value of the ORGANIZER or ATTENDEE properties.</p>
    <p>The "calendarAddress" and "email" properties can then match the
      behavior specified for the EMAIL parameter and ORGANIZER/ATTENDEE
      values - <br>
    </p>
    <pre class="newpage">   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.</pre>
    <p> <br>
    </p>
    <p>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.</p>
    <p>I'd suggest that sendTo only be used for non-iMip alternatives -
      or if iMip really should be sent to a different address from
      email.</p>
    <p>So the above would become:</p>
    <p>"participants": {</p>
    <p>   "123": {</p>
    <p>      ....</p>
    <p>     "calendarAddress":
"/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/"</p>
    <p>    "email": <a class="moz-txt-link-rfc2396E" href="mailto:mikeadouglass@gmail.com">"mikeadouglass@gmail.com"</a>   <br>
    </p>
    <p>     ...}</p>
    <p><br>
    </p>
    <p>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.</p>
    <p>I believe there's no mapping for the jscalendar "invitedBy" from
      iCalendar - is that so?</p>
    <p>  <br>
    </p>
  </body>
</html>

--------------2BD50C6BE940E9D682CC7B71--


From nobody Mon Feb 15 11:56:01 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C3A3A1073; Mon, 15 Feb 2021 11:55:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <161341895851.12892.11297032267274574480@ietfa.amsl.com>
Date: Mon, 15 Feb 2021 11:55:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/RZdUtXA10sqHSgK-esoUw2si5Bc>
Subject: [calsify] I-D Action: draft-ietf-calext-valarm-extensions-05.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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 19:55:59 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : VALARM Extensions for iCalendar
        Authors         : Cyrus Daboo
                          Kenneth Murchison
	Filename        : draft-ietf-calext-valarm-extensions-05.txt
	Pages           : 17
	Date            : 2021-02-15

Abstract:
   This document defines a set of extensions to the iCalendar VALARM
   component to enhance use of alarms and improve interoperability
   between clients and servers.

   This document updates RFC5545.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-calext-valarm-extensions-05
https://datatracker.ietf.org/doc/html/draft-ietf-calext-valarm-extensions-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-valarm-extensions-05


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/



From nobody Mon Feb 15 15:06:57 2021
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

--8c947e03e0934295aab56321ba68ac5f
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Tue, 16 Feb 2021, at 04:29, Michael Douglass wrote:
> I ran into a problem mapping iCalendar ATTENDEE onto jscalendar partic=
ipants.

> For example I might have an ATTENDEE that looks like

> ATTENDEE;CN=3DMichael Douglass;CUTYPE=3DINDIVIDUAL;PARTSTAT=3DACCEPTED=
;ROLE=3DCHAIR;EMAIL=3Dmikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQPu=
XCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/

> The value is a URI but certainly not an email address.

> Additionally the value is used as a unique key to the attendee - somet=
hing we don't have clearly defined in jscalendar.=20


Unless I'm missing something, that's just the participant id (i.e. the k=
ey 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 behavi=
or specified for the EMAIL parameter and ORGANIZER/ATTENDEE values -=20

>    Description:  This property parameter MAY be specified on "ORGANIZE=
R"
      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.
>=20

> 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 ca=
n 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 =E2=80=
=93 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 SE=
NT-BY parameter. This is used on ATTENDEE and ORGANIZER when somebody el=
se sends on behalf of the participant. I suggest we add a "sentBy" jscal=
endar property for participants.


Sure.

> I believe there's no mapping for the jscalendar "invitedBy" from iCale=
ndar - is that so?


Potentially not, we can register a new iCalendar property.

Neil.
--8c947e03e0934295aab56321ba68ac5f
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Tue, 16 Feb =
2021, at 04:29, Michael Douglass wrote:<br></div><blockquote type=3D"cit=
e" id=3D"qt" style=3D""><p>I ran into a problem mapping iCalendar ATTEND=
EE onto jscalendar
      participants.<br></p><p>For example I might have an ATTENDEE that =
looks like<br></p><p>ATTENDEE;CN=3DMichael <a class=3D"qt-moz-txt-link-a=
bbreviated" href=3D"mailto:Douglass;CUTYPE=3DINDIVIDUAL;PARTSTAT=3DACCEP=
TED;ROLE=3DCHAIR;EMAIL=3Dmikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzN=
QPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/">Douglass;CUTYPE=3D=
INDIVIDUAL;PARTSTAT=3DACCEPTED;ROLE=3DCHAIR;EMAIL=3Dmikeadouglass@gmail.=
com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/p=
rincipal/</a><br></p><p>The value is a URI but certainly not an email ad=
dress.<br></p><p>Additionally the value is used as a unique key to the a=
ttendee -
      something we don't have clearly defined in jscalendar. <br></p></b=
lockquote><div><br></div><div>Unless I'm missing something, that's just =
the participant id (i.e. the key in the participants object).<br></div><=
div><br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><p>I sugges=
t we add a calendarAddress property which maps on to the
      value of the ORGANIZER or ATTENDEE properties.<br></p></blockquote=
><div><br></div><div>I don't see the purpose of this proposed property.<=
br></div><div><br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><=
p>The "calendarAddress" and "email" properties can then match the
      behavior specified for the EMAIL parameter and ORGANIZER/ATTENDEE
      values - <br></p><pre class=3D"qt-newpage">   Description:  This p=
roperty 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.<br></pre><p><br></=
p><p>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.<br></p></blockquote><div><br></div><div>No, there is a di=
fference:<br></div><ul><li>Participant email property: this is the perso=
n's email address and can be used if you want to send them an email.<br>=
</li><li>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 =
=E2=80=93 it may be a calendar-specific address that's just used for iMI=
P).<br></li></ul><div><br></div><blockquote type=3D"cite" id=3D"qt" styl=
e=3D""><p>Additional to all this I realised there is no clear mapping fo=
r
      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.<br></p></blockquo=
te><div><br></div><div>Sure.<br></div><div><br></div><blockquote type=3D=
"cite" id=3D"qt" style=3D""><p>I believe there's no mapping for the jsca=
lendar "invitedBy" from
      iCalendar - is that so?<br></p></blockquote><div><br></div><div>Po=
tentially not, we can register a new iCalendar property.<br></div><div><=
br></div><div>Neil.<br></div></body></html>
--8c947e03e0934295aab56321ba68ac5f--


From nobody Tue Feb 16 09:17:46 2021
Return-Path: <rsto@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 A95173A0C6C for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 09:17:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 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_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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=UlqzQjg2; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=pJBaHFsT
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 iLQXOr_zMf5m for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 09:17:42 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF263A0C5B for <calsify@ietf.org>; Tue, 16 Feb 2021 09:17:42 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 81E64B25 for <calsify@ietf.org>; Tue, 16 Feb 2021 12:17:41 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute4.internal (MEProxy); Tue, 16 Feb 2021 12:17:41 -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=Rb7wsQ+ 7zf/Am4+9bGusgq9qRM+1D6WyWLfYXqPNAz8=; b=UlqzQjg2PWu9OlTaXO12xMP agp1YugGoFZtllSEtHEApJUjkIRN1tCFlv6iAOdRDHUbPkQzq+ML25dQuD/XYMgj 2HffTe53kl/IQEGyh8VZJ/tAtxetEFF+2d3EMzLsHhPJgQs4eg24NeTfi9sOjVY2 ifLY5n/IbfOaMd3yWWlPPLbuMu8hudL5CvEYHY294LmD4G4lx/FZ1vFv0n/isV9d I3cr5vY15QtHq5j8zu+zl39dUHfMlJXz4YKxBOot/xeqW2tF57oAJaCtgR138G28 PpGzF9fGFowCFpfAMlLVUjyqxCqTX2WotsgVU4okjUPKkvVBqAWLN2QODm0PpzQ= =
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=Rb7wsQ +7zf/Am4+9bGusgq9qRM+1D6WyWLfYXqPNAz8=; b=pJBaHFsTz1rDrQVfFcCua5 lhZM9bpDiHtPvvWWLLvh0dP3BSBFhCgTF3p9NY7VtGlJDyxuXYb3v8gM5t1F/VEz cl9MlNu6QBHncBZa2SA8uhgd7UraLcjTkTPvSGqWV85t14tKZt2zj3HdzVh/+Tat IRo7AJQE/Kv1jKb+H54MYtG6e1AzaG4Q71EXh+7SvEf0i5tUk2vbZNl09CuWp3aJ JxeMSra6UZWtkpTgtHBrRkH4XZzkYSVoorYQ0RL/rwfMppMWnMtbknqy29oOCfeF 3wad2v93GlUmsEPwhvMoucUX0fnguAsJDbm/oIKIvhRlEWYYDyomd+o6j7KUOt5A ==
X-ME-Sender: <xms:M_4rYE2bqW9PaUX719TpxxMePQqdILysOrQPGEnplo5mbRKdxae4Xg> <xme:M_4rYPFpsCWWIVtlz6yux23DLR4WYgU1cVUymXRvjVohe8W8cq3tSwvD4uuhOP6hF oaIeaNh_aFVRA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjedtgdellecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdftohgsvghrthcuufhtvghprghnvghkfdcuoehrshhtohes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeeijefhvefgge ekleetieeuuefgtdfhveetvdeileelveelueekjeffgffhgeeuueenucffohhmrghinhep ihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomheprhhsthhosehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:M_4rYM751ypf1KTOkclNkPd0Y2QwD7OpSWJp8xKFiH632pMRSpBC6Q> <xmx:M_4rYN3cL3smIA0hosbsr9-p6zs5UeFN67ZCLfj2RPURTKDbhXDtWQ> <xmx:M_4rYHFcz_HIJyxFkwYXjKZpnOsIPQPbKZQbCwxJGMcDwHxMzBoG6w> <xmx:NP4rYLRCw43kCz3dFYmlndNDuB5MdvDdiLowSpzKzOG_O2W7k7RNYQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 55D3836005C; Tue, 16 Feb 2021 12:17:39 -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: <d240c4fe-1961-4493-97e2-f9b3e5c13668@www.fastmail.com>
In-Reply-To: <f3631111-c3d7-46e1-b83a-2e994621a799@dogfood.fastmail.com>
References: <cf63883d-e134-62ea-3e53-af6945b755e1@gmail.com> <f3631111-c3d7-46e1-b83a-2e994621a799@dogfood.fastmail.com>
Date: Tue, 16 Feb 2021 18:17:05 +0100
From: "Robert Stepanek" <rsto@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=0c93d4634df74358ae9cbf56782ad3e9
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/icrHCc-60hSEOA6DExo9K90rW4I>
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: Tue, 16 Feb 2021 17:17:45 -0000

--0c93d4634df74358ae9cbf56782ad3e9
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 16, 2021, at 12:06 AM, Neil Jenkins wrote:
> On Tue, 16 Feb 2021, at 04:29, Michael Douglass wrote:
>> I ran into a problem mapping iCalendar ATTENDEE onto jscalendar parti=
cipants.

>> For example I might have an ATTENDEE that looks like

>> ATTENDEE;CN=3DMichael Douglass;CUTYPE=3DINDIVIDUAL;PARTSTAT=3DACCEPTE=
D;ROLE=3DCHAIR;EMAIL=3Dmikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQP=
uXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/

>> The value is a URI but certainly not an email address.

>> Additionally the value is used as a unique key to the attendee - some=
thing we don't have clearly defined in jscalendar.=20

>=20
> Unless I'm missing something, that's just the participant id (i.e. the=
 key in the participants object).

The difference is that the participant id has no meaning outside a singl=
e JSEvent. But a calendar user address is an identifier for an entity ac=
ross events.

>=20
>> I suggest we add a calendarAddress property which maps on to the valu=
e of the ORGANIZER or ATTENDEE properties.

>=20
> I don't see the purpose of this proposed property.

It allows for unambigously mapping the ATTENDEE or ORGANIZER property va=
lue to JSCalendar and reverse. It's not clear from a multi-valued sendTo=
 property which one should be used as the property value.

There is one other benefit of making more use of calendar user addresses=
 in JSCalendar: the DELEGATED-FROM, DELEGATED-TO, MEMBER-OF, SENT-BY par=
ameters all use calendar user addresses. But in JSCalendar we use partic=
ipant ids for these properties. If a DELEGATED-FROM calendar user addres=
s has no ATTENDEE in iCalendar, we would need to create an artificial pa=
rticipant in JSCalendar. This participant could have an "informational" =
role, expectReply=3Dfalse, because it's really not a participant. When m=
apping back to iCalendar we would need to figure out if to create an ATT=
ENDEE for that. When we use calendar user addresses rather than particip=
ant ids for these properties then there is no ambiguity.


>> The "calendarAddress" and "email" properties can then match the behav=
ior specified for the EMAIL parameter and ORGANIZER/ATTENDEE values -=20=


>>    Description:  This property parameter MAY be specified on "ORGANIZ=
ER"
      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.
>>=20

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

>=20
> 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 =E2=80=
=93 it may be a calendar-specific address that's just used for iMIP).
>=20
>> Additional to all this I realised there is no clear mapping for the S=
ENT-BY parameter. This is used on ATTENDEE and ORGANIZER when somebody e=
lse sends on behalf of the participant. I suggest we add a "sentBy" jsca=
lendar property for participants.

>=20
> Sure.
>=20
>> I believe there's no mapping for the jscalendar "invitedBy" from iCal=
endar - is that so?

>=20
> Potentially not, we can register a new iCalendar property.
>=20
> Neil.
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>=20

--0c93d4634df74358ae9cbf56782ad3e9
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Tue, Fe=
b 16, 2021, at 12:06 AM, Neil Jenkins wrote:<br></div><blockquote type=3D=
"cite" id=3D"qt" style=3D""><div>On Tue, 16 Feb 2021, at 04:29, Michael =
Douglass wrote:<br></div><blockquote type=3D"cite" id=3D"qt-qt" style=3D=
""><p>I ran into a problem mapping iCalendar ATTENDEE onto jscalendar
      participants.<br></p><p>For example I might have an ATTENDEE that =
looks like<br></p><p>ATTENDEE;CN=3DMichael <a class=3D"qt-qt-moz-txt-lin=
k-abbreviated" href=3D"mailto:Douglass;CUTYPE=3DINDIVIDUAL;PARTSTAT=3DAC=
CEPTED;ROLE=3DCHAIR;EMAIL=3Dmikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4Mz=
kzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/">Douglass;CUTY=
PE=3DINDIVIDUAL;PARTSTAT=3DACCEPTED;ROLE=3DCHAIR;EMAIL=3Dmikeadouglass@g=
mail.com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXe=
jTR/principal/</a><br></p><p>The value is a URI but certainly not an ema=
il address.<br></p><p>Additionally the value is used as a unique key to =
the attendee -
      something we don't have clearly defined in jscalendar. <br></p></b=
lockquote><div><br></div><div>Unless I'm missing something, that's just =
the participant id (i.e. the key in the participants object).<br></div><=
/blockquote><div><br></div><div>The difference is that the participant i=
d has no meaning outside a single JSEvent. But a calendar user address i=
s an identifier for an entity across events.<br></div><div><br></div><bl=
ockquote type=3D"cite" id=3D"qt" style=3D""><div><br></div><blockquote t=
ype=3D"cite" id=3D"qt-qt" style=3D""><p>I suggest we add a calendarAddre=
ss property which maps on to the
      value of the ORGANIZER or ATTENDEE properties.<br></p></blockquote=
><div><br></div><div>I don't see the purpose of this proposed property.<=
br></div></blockquote><div><br></div><div>It allows for unambigously map=
ping the ATTENDEE or ORGANIZER property value to JSCalendar and reverse.=
 It's not clear from a multi-valued sendTo property which one should be =
used as the property value.<br></div><div><br></div><div>There is one ot=
her benefit of making more use of calendar user addresses in JSCalendar:=
 the DELEGATED-FROM, DELEGATED-TO, MEMBER-OF, SENT-BY parameters all use=
 calendar user addresses. But in JSCalendar we use participant ids for t=
hese properties. If a DELEGATED-FROM calendar user address has no ATTEND=
EE in iCalendar, we would need to create an artificial participant in JS=
Calendar. This participant could have an "informational" role, expectRep=
ly=3Dfalse, because it's really not a participant. When mapping back to =
iCalendar we would need to figure out if to create an ATTENDEE for that.=
 When we use calendar user addresses rather than participant ids for the=
se properties then there is no ambiguity.<br></div><div><br></div><div><=
br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><blockquote type=
=3D"cite" id=3D"qt-qt" style=3D""><p>The "calendarAddress" and "email" p=
roperties can then match the
      behavior specified for the EMAIL parameter and ORGANIZER/ATTENDEE
      values - <br></p><pre class=3D"qt-qt-newpage">   Description:  Thi=
s 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.<br></pre><p><br></=
p><p>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.<br></p></blockquote><div><br></div><div>No, there is a di=
fference:<br></div><ul><li>Participant email property: this is the perso=
n's email address and can be used if you want to send them an email.<br>=
</li><li>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 =
=E2=80=93 it may be a calendar-specific address that's just used for iMI=
P).<br></li></ul><div><br></div><blockquote type=3D"cite" id=3D"qt-qt" s=
tyle=3D""><p>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.<br></p></blockquo=
te><div><br></div><div>Sure.<br></div><div><br></div><blockquote type=3D=
"cite" id=3D"qt-qt" style=3D""><p>I believe there's no mapping for the j=
scalendar "invitedBy" from
      iCalendar - is that so?<br></p></blockquote><div><br></div><div>Po=
tentially not, we can register a new iCalendar property.<br></div><div><=
br></div><div>Neil.<br></div><div>______________________________________=
_________<br></div><div>calsify mailing list<br></div><div><a href=3D"ma=
ilto:calsify@ietf.org">calsify@ietf.org</a><br></div><div><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman=
/listinfo/calsify</a><br></div><div><br></div></blockquote><div><br></di=
v></body></html>
--0c93d4634df74358ae9cbf56782ad3e9--


From nobody Tue Feb 16 18:50:14 2021
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 3CFE53A0E25 for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 18:50:12 -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=rIhPkIL+; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ttuVVFiv
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 AYsM_aCuxOYB for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 18:50:10 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A8FE3A0B83 for <calsify@ietf.org>; Tue, 16 Feb 2021 18:50:09 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id C84B15C01BC for <calsify@ietf.org>; Tue, 16 Feb 2021 21:50:08 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Tue, 16 Feb 2021 21:50:08 -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=Ia3e+v0 tkWcRt8obZqXW3gBqWtg9QXBJeOtFGy8yu9M=; b=rIhPkIL+YpsrdInGEo1LOZ2 uAUuBIFnPFCD7bUchyDdfS8QnTc/NmyhA/nyASAOkMjlAeNQjOQI4ChiDFmlHsNc e43knOusqz+V07x+xsh0MjoYSwObMTKvipY/oX0xTscbHqJ6DTql6WvIQVF1uPOm khltxvQKMGkeQF+dK19nrajXE+b4AA/B4KRCXOZe0WAbR81vv4mk/k14Q8JjMxoD 2sSkOZ9fIX9OdnExJJ13v8HULswgM7qLcKdE1MQbu++bVPYIl/jaHTofN8Xz5e1H fiTxFGjPpkbX9NUmyc0F4I/mlD2U+HrKkW5vTZOtuyNLcGG+L/OQxZEhFhxWufw= =
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=Ia3e+v 0tkWcRt8obZqXW3gBqWtg9QXBJeOtFGy8yu9M=; b=ttuVVFivLpiqLPRatThs4p wMn2pW4f74fdXkT8xxZixQDUdjgyQ4mduXHGU/V8ZFaTLogkOwbwhjUAaTrFJioz BXZTU/84y7GQ4VODywqBzJGt3qZxmMI0fxAKRcQpE3I3l06OKMwTJnmi0eRDaJ8l jjkmkbtRJze9Ze7fSc9cT1AEu78eZdlIAXjIUDOLg3/6glD8lo/Ge2ASJVe5dgh8 xA7vbi2BxGds20xhmM+6b0upgGL64qMYDTcAYOK6nE+E6ZciY9ai4jctIGrcyHbQ pjoaknN71TuN4dMGtKnLAfh3k4QzJjQpbWuPIWP/wTVtJNsf/VDp3V8ABz7MqDpA ==
X-ME-Sender: <xms:YIQsYL-vsbMitbwEzRzzIF3ZlOIzE2AOOKFyP1P0Tu7tWhYA9eY4mQ> <xme:YIQsYHuKlxTSSMNGh6Ga7Qu14WJ9gwQpuxDvvlKlyzx5DYmckJAfBt4FkMAVD_0cg Slx0hQtpmLh7Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjedugdehtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdfpvghilhculfgvnhhkihhnshdfuceonhgvihhljhesfhgr shhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeevvdetvdduleekhf eghfetfeettdelhfehfeevffevleekuddtudffieevjeevhfenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghilh htvggrmhdrtghomh
X-ME-Proxy: <xmx:YIQsYJDQtDUMM_xfK7X3jMOOzGPawB1ppvr0lpaijZRskXlR132IQg> <xmx:YIQsYHeZAbuPxkSxcbIHerME57spCle4c2a4VMAMp1TyP_qTMvs_FQ> <xmx:YIQsYAMGh_cVjiaAjfwzpj_W5YfzvCZ5Z2wEKXTda77XR_JEYw-G7Q> <xmx:YIQsYGaz-hkOn95X42Gu3Op19Jl_MZzBr4-Hw3JQMy9DbGvvd-LM5w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 58C8A36005C; Tue, 16 Feb 2021 21:50:08 -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: <d2de6358-9994-4d41-aa6c-1258e5ff2d0b@dogfood.fastmail.com>
In-Reply-To: <d240c4fe-1961-4493-97e2-f9b3e5c13668@www.fastmail.com>
References: <cf63883d-e134-62ea-3e53-af6945b755e1@gmail.com> <f3631111-c3d7-46e1-b83a-2e994621a799@dogfood.fastmail.com> <d240c4fe-1961-4493-97e2-f9b3e5c13668@www.fastmail.com>
Date: Wed, 17 Feb 2021 13:50:07 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=b899406c38684ed89ec8a8797c22cc96
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/XHKf_UHX02AaPQBcF3tW3jpCmGM>
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: Wed, 17 Feb 2021 02:50:12 -0000

--b899406c38684ed89ec8a8797c22cc96
Content-Type: text/plain

On Wed, 17 Feb 2021, at 04:17, Robert Stepanek wrote:
>> 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 difference is that the participant id has no meaning outside a single JSEvent. But a calendar user address is an identifier for an entity across events.
> 
> It allows for unambigously mapping the ATTENDEE or ORGANIZER property value to JSCalendar and reverse. It's not clear from a multi-valued sendTo property which one should be used as the property value.

My reading of the current RFCs, although I think they are not super clear, is that the calendar user address is the only "sendTo" method. An email may be specified in addition but this is not intended as an iMIP destination (so would not be in the JSCalendar sendTo, just the participant's email property). Is your interpretation that the calendar user address is more like a uid? If so, can you use it for anything other than as an opaque token for equality comparison?

> There is one other benefit of making more use of calendar user addresses in JSCalendar: the DELEGATED-FROM, DELEGATED-TO, MEMBER-OF, SENT-BY parameters all use calendar user addresses. But in JSCalendar we use participant ids for these properties. If a DELEGATED-FROM calendar user address has no ATTENDEE in iCalendar, we would need to create an artificial participant in JSCalendar. This participant could have an "informational" role, expectReply=false, because it's really not a participant. When mapping back to iCalendar we would need to figure out if to create an ATTENDEE for that. When we use calendar user addresses rather than participant ids for these properties then there is no ambiguity.

It seems a bit weird to me that you would have unresolvable identifiers like this (they don't seem particularly useful). I'd also say that you'd be making the JSCalendar object more awkward to work with (you'd have to linearly scan or build a separate index to get from one of these pointers to the participant it refers to). I would generally say a slightly more cumbersome translation is preferable to all objects in the new format being harder to use.

Neil.
--b899406c38684ed89ec8a8797c22cc96
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, 17=
 Feb 2021, at 04:17, Robert Stepanek wrote:<br></div><blockquote type=3D=
"cite"><blockquote type=3D"cite"><div>For example I might have an ATTEND=
EE that looks like<br></div><div>ATTENDEE;CN=3DMichael Douglass;CUTYPE=3D=
INDIVIDUAL;PARTSTAT=3DACCEPTED;ROLE=3DCHAIR;EMAIL=3D<a href=3D"mailto:mi=
keadouglass@gmail.com">mikeadouglass@gmail.com</a>:/aMzkzNTI4MzkzNTI4Mzk=
zNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/<br></div></bloc=
kquote><div>The difference is that the participant id has no meaning out=
side a single JSEvent. But a calendar user address is an identifier for =
an entity across events.<br></div><div><br></div><div>It allows for unam=
bigously mapping the ATTENDEE or ORGANIZER property value to JSCalendar =
and reverse. It's not clear from a multi-valued sendTo property which on=
e should be used as the property value.<br></div></blockquote><div><br><=
/div><div>My reading of the current RFCs, although I think they are not =
super clear, is that the calendar user address is the only "sendTo" meth=
od. An email may be specified in addition but this is not intended as an=
 iMIP destination (so would not be in the JSCalendar sendTo, just the pa=
rticipant's email property). Is your interpretation that the calendar us=
er address is more like a uid? If so, can you use it for anything other =
than as an opaque token for equality comparison?<br></div><div><br></div=
><blockquote type=3D"cite" id=3D"qt" style=3D""><div>There is one other =
benefit of making more use of calendar user addresses in JSCalendar: the=
 DELEGATED-FROM, DELEGATED-TO, MEMBER-OF, SENT-BY parameters all use cal=
endar user addresses. But in JSCalendar we use participant ids for these=
 properties. If a DELEGATED-FROM calendar user address has no ATTENDEE i=
n iCalendar, we would need to create an artificial participant in JSCale=
ndar. This participant could have an "informational" role, expectReply=3D=
false, because it's really not a participant. When mapping back to iCale=
ndar we would need to figure out if to create an ATTENDEE for that. When=
 we use calendar user addresses rather than participant ids for these pr=
operties then there is no ambiguity.<br></div></blockquote><div><br></di=
v><div>It seems a bit weird to me that you would have unresolvable ident=
ifiers like this (they don't seem particularly useful). I'd also say tha=
t you'd be making the JSCalendar object more awkward to work with (you'd=
 have to linearly scan or build a separate index to get from one of thes=
e pointers to the participant it refers to). I would generally say a sli=
ghtly more cumbersome translation is preferable to all objects in the ne=
w format being harder to use.<br></div><div><br></div><div>Neil.<br></di=
v></body></html>
--b899406c38684ed89ec8a8797c22cc96--


From nobody Tue Feb 16 20:35:03 2021
Return-Path: <mikeadouglass@gmail.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 A74B03A1496 for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 20:35:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.098 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 IV4_tff89O-2 for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 20:34:59 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 E578E3A1491 for <calsify@ietf.org>; Tue, 16 Feb 2021 20:34:58 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id w20so8734135qta.0 for <calsify@ietf.org>; Tue, 16 Feb 2021 20:34:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=yL5pmFc5ZRxCu91Z3C/qYrFCKMDW2AZ0ynEdJEnnd5A=; b=byVnC1pcHULtCDlzOyuiUp4VQMipgVO9ljHxAfjEr08Vlk+GqMBNRSM+s073UJsvil IPRgJHMJGacxNxRSq2jf6KKI6q5VsOc+KKxB6257xdrTdI6IF5uI+9HFz/ciPFkfOPws /vrscgk8szLzzI0xAvGMy6XPnfO4IYeggm/r9opDNPdy/oLrV3omQeOHIhwMw0DShV8P kQ/RtueZP0n2LsJhsLF/oDD2wDGjXtTS17YWkalRYPVZyPupUvwikCz9wZ73aD6Fdt+J VGeNtcLfr2lbnATVgLDkV9lfdEUURRI+4AbPybhpqykCysMexXwYDr+Ofck1K43/VeC+ wzYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=yL5pmFc5ZRxCu91Z3C/qYrFCKMDW2AZ0ynEdJEnnd5A=; b=JCAgKHJuMR4fqzMmekzK8zfxuLDeLYzDjcJV0eiayR2tJe9txokzPL89sET53nxKWT RYlWzvhBHDL0jflIQpoh5RqLI6IRBInrz/6Y/qmWrdZeiS8EEDI5WcO48HzK3HTX2C19 5P9YQzr4JFIm+Td/umkpNrWLIF9CqU8OTjPKsPbsNkp84F+Xo1tZwhpNitO4LlURIDKJ 5XAeWxcTHGLzIMTuKxVtkYJAhSathwATbsxs65IDyG2beOR0+dUVqMauoHYpBq/VvbnZ YPPIdVhO5T+kIa5u7JVi70Sc2L5xtmQFZpdlWy8ZJ6m71bmiHGxwUJhdVPPm3Hn3UnPZ MyZA==
X-Gm-Message-State: AOAM532Wj9o0vGBArZk4+YYBn5gxs3/YqASw1IXf0EMBKwsM+sPTk5Hv PeblI4g3VdrwNw37Aj+7XA6ncNioweA=
X-Google-Smtp-Source: ABdhPJwU3E0uXz4ljFz6R5NzE4d1EcgIhKIUcS1dBffFoSyx9yz41YSY9xyFehAkQe2oGXd9f32YOA==
X-Received: by 2002:ac8:6c5d:: with SMTP id z29mr22188189qtu.145.1613536497426;  Tue, 16 Feb 2021 20:34:57 -0800 (PST)
Received: from [192.168.1.150] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id f188sm850821qkj.110.2021.02.16.20.34.56 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Feb 2021 20:34:56 -0800 (PST)
To: calsify@ietf.org
References: <cf63883d-e134-62ea-3e53-af6945b755e1@gmail.com> <f3631111-c3d7-46e1-b83a-2e994621a799@dogfood.fastmail.com> <d240c4fe-1961-4493-97e2-f9b3e5c13668@www.fastmail.com> <d2de6358-9994-4d41-aa6c-1258e5ff2d0b@dogfood.fastmail.com>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <e5f6b4ba-f5de-b18a-2705-7d7c11abdc03@gmail.com>
Date: Tue, 16 Feb 2021 23:34:55 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <d2de6358-9994-4d41-aa6c-1258e5ff2d0b@dogfood.fastmail.com>
Content-Type: multipart/alternative; boundary="------------B8B48F244AA39348CE0DEE03"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/tYkDzj39HrfL5RXhXS6gW87okuk>
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: Wed, 17 Feb 2021 04:35:02 -0000

This is a multi-part message in MIME format.
--------------B8B48F244AA39348CE0DEE03
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 2/16/21 21:50, Neil Jenkins wrote:
> On Wed, 17 Feb 2021, at 04:17, Robert Stepanek wrote:
>>> For example I might have an ATTENDEE that looks like
>>> ATTENDEE;CN=Michael 
>>> Douglass;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=mikeadouglass@gmail.com 
>>> <mailto:mikeadouglass@gmail.com>:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/
>> The difference is that the participant id has no meaning outside a 
>> single JSEvent. But a calendar user address is an identifier for an 
>> entity across events.
>>
>> It allows for unambigously mapping the ATTENDEE or ORGANIZER property 
>> value to JSCalendar and reverse. It's not clear from a multi-valued 
>> sendTo property which one should be used as the property value.
>
> My reading of the current RFCs, although I think they are not super 
> clear, is that the calendar user address is the only "sendTo" method. 
> An email may be specified in addition but this is not intended as an 
> iMIP destination (so would not be in the JSCalendar sendTo, just the 
> participant's email property). Is your interpretation that the 
> calendar user address is more like a uid? If so, can you use it for 
> anything other than as an opaque token for equality comparison?

5545 only requires that the calendar address be a URI - it does not 
require it be a mailto URI - UNLESS it is used as the destination for email.

The ATTENDEE and ORGANIZER properties typically had a mailto uri as a 
value. When it was decided that the value should NOT be a mailto there 
was clearly a need for somewhere to put the address of the user so iMip 
could be sent - that's the EMAIL parameter. I don't see anything that 
suggests the calendar-address is no longer the identifier for the property.

5545 and 5546 very likely have no mention of an email address other than 
the mailto uri in the value because there was no EMAIL parameter at the 
time.

>
>> There is one other benefit of making more use of calendar user 
>> addresses in JSCalendar: the DELEGATED-FROM, DELEGATED-TO, MEMBER-OF, 
>> SENT-BY parameters all use calendar user addresses. But in JSCalendar 
>> we use participant ids for these properties. If a DELEGATED-FROM 
>> calendar user address has no ATTENDEE in iCalendar, we would need to 
>> create an artificial participant in JSCalendar. This participant 
>> could have an "informational" role, expectReply=false, because it's 
>> really not a participant. When mapping back to iCalendar we would 
>> need to figure out if to create an ATTENDEE for that. When we use 
>> calendar user addresses rather than participant ids for these 
>> properties then there is no ambiguity.
>
> It seems a bit weird to me that you would have unresolvable 
> identifiers like this (they don't seem particularly useful).
Any UID is intended to be an unresolvable identifier - doesn't make them 
any less useful.
> I'd also say that you'd be making the JSCalendar object more awkward 
> to work with (you'd have to linearly scan or build a separate index to 
> get from one of these pointers to the participant it refers to). I 
> would generally say a slightly more cumbersome translation is 
> preferable to all objects in the new format being harder to use.
It was precisely because I was having to do that that I raised the 
issue. The jscalendar spec DOES NOT specify that the id for a 
participant is the calendar address and the examples don't show it either.

What concerns me is that jscalendar seems to be essentially rewriting 
iTip - perhaps not intentionally.

We currently have 2 'properties' - the iCalendar attendee value - a 
calendar user address and an email address which may be the same or 
specified in the EMAIL parameter.

I do believe the EMAIL parameter to be underspecified but nothing in the 
text leads me to believe it is intended to replace the calendar address.

If we add a jscalendar calendarAddress property the mapping is simple 
and what works now will continue to work.

We *could* try some experiments and mess around with the values but if 
we don't have an easy reversible mapping between jscalendar and 
icalendar things will almost certainly break.


>
> Neil.
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--------------B8B48F244AA39348CE0DEE03
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <br>
    <div class="moz-cite-prefix">On 2/16/21 21:50, Neil Jenkins wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:d2de6358-9994-4d41-aa6c-1258e5ff2d0b@dogfood.fastmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <title></title>
      <style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
      <div>On Wed, 17 Feb 2021, at 04:17, Robert Stepanek wrote:<br>
      </div>
      <blockquote type="cite">
        <blockquote type="cite">
          <div>For example I might have an ATTENDEE that looks like<br>
          </div>
          <div>ATTENDEE;CN=Michael
            Douglass;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=<a
              href="mailto:mikeadouglass@gmail.com"
              moz-do-not-send="true">mikeadouglass@gmail.com</a>:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/<br>
          </div>
        </blockquote>
        <div>The difference is that the participant id has no meaning
          outside a single JSEvent. But a calendar user address is an
          identifier for an entity across events.<br>
        </div>
        <div><br>
        </div>
        <div>It allows for unambigously mapping the ATTENDEE or
          ORGANIZER property value to JSCalendar and reverse. It's not
          clear from a multi-valued sendTo property which one should be
          used as the property value.<br>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>My reading of the current RFCs, although I think they are not
        super clear, is that the calendar user address is the only
        "sendTo" method. An email may be specified in addition but this
        is not intended as an iMIP destination (so would not be in the
        JSCalendar sendTo, just the participant's email property). Is
        your interpretation that the calendar user address is more like
        a uid? If so, can you use it for anything other than as an
        opaque token for equality comparison?<br>
      </div>
    </blockquote>
    <p>5545 only requires that the calendar address be a URI - it does
      not require it be a mailto URI - UNLESS it is used as the
      destination for email.</p>
    <p>The ATTENDEE and ORGANIZER properties typically had a mailto uri
      as a value. When it was decided that the value should NOT be a
      mailto there was clearly a need for somewhere to put the address
      of the user so iMip could be sent - that's the EMAIL parameter. I
      don't see anything that suggests the calendar-address is no longer
      the identifier for the property. <br>
    </p>
    <p>5545 and 5546 very likely have no mention of an email address
      other than the mailto uri in the value because there was no EMAIL
      parameter at the time.</p>
    <blockquote type="cite"
      cite="mid:d2de6358-9994-4d41-aa6c-1258e5ff2d0b@dogfood.fastmail.com">
      <div><br>
      </div>
      <blockquote type="cite" id="qt" style="">
        <div>There is one other benefit of making more use of calendar
          user addresses in JSCalendar: the DELEGATED-FROM,
          DELEGATED-TO, MEMBER-OF, SENT-BY parameters all use calendar
          user addresses. But in JSCalendar we use participant ids for
          these properties. If a DELEGATED-FROM calendar user address
          has no ATTENDEE in iCalendar, we would need to create an
          artificial participant in JSCalendar. This participant could
          have an "informational" role, expectReply=false, because it's
          really not a participant. When mapping back to iCalendar we
          would need to figure out if to create an ATTENDEE for that.
          When we use calendar user addresses rather than participant
          ids for these properties then there is no ambiguity.<br>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>It seems a bit weird to me that you would have unresolvable
        identifiers like this (they don't seem particularly useful). </div>
    </blockquote>
    Any UID is intended to be an unresolvable identifier - doesn't make
    them any less useful.<br>
    <blockquote type="cite"
      cite="mid:d2de6358-9994-4d41-aa6c-1258e5ff2d0b@dogfood.fastmail.com">
      <div>I'd also say that you'd be making the JSCalendar object more
        awkward to work with (you'd have to linearly scan or build a
        separate index to get from one of these pointers to the
        participant it refers to). I would generally say a slightly more
        cumbersome translation is preferable to all objects in the new
        format being harder to use.<br>
      </div>
    </blockquote>
    It was precisely because I was having to do that that I raised the
    issue. The jscalendar spec DOES NOT specify that the id for a
    participant is the calendar address and the examples don't show it
    either. <br>
    <p>What concerns me is that jscalendar seems to be essentially
      rewriting iTip - perhaps not intentionally. <br>
    </p>
    <p>We currently have 2 'properties' - the iCalendar attendee value -
      a calendar user address and an email address which may be the same
      or specified in the EMAIL parameter. <br>
    </p>
    <p>I do believe the EMAIL parameter to be underspecified but nothing
      in the text leads me to believe it is intended to replace the
      calendar address.</p>
    <p>If we add a jscalendar calendarAddress property the mapping is
      simple and what works now will continue to work.</p>
    <p>We *could* try some experiments and mess around with the values
      but if we don't have an easy reversible mapping between jscalendar
      and icalendar things will almost certainly break. <br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:d2de6358-9994-4d41-aa6c-1258e5ff2d0b@dogfood.fastmail.com">
      <div><br>
      </div>
      <div>Neil.<br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
  </body>
</html>

--------------B8B48F244AA39348CE0DEE03--


From nobody Tue Feb 16 20:46:36 2021
Return-Path: <mikeadouglass@gmail.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 1C97F3A14A8 for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 20:46:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 7s08mK243XCH for <calsify@ietfa.amsl.com>; Tue, 16 Feb 2021 20:46:33 -0800 (PST)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 A90993A14A6 for <calsify@ietf.org>; Tue, 16 Feb 2021 20:46:33 -0800 (PST)
Received: by mail-qv1-xf2b.google.com with SMTP id p6so5738162qvm.12 for <calsify@ietf.org>; Tue, 16 Feb 2021 20:46:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:message-id:date:user-agent:mime-version :content-language; bh=LgmZctRBCRCjeNq4NTJW3txW0Wy2py5eRNmCBxzAQ4Q=; b=cAdECJ98KiPKCUuw/UcVhpuOQjDdtzl4hPos+K11DU66Yt3pwQ0qd2xB1WRtym+4Ts K72EyD06jeZNTAS20UKid9Pq3bxmp/mTRBTZHeOTcjyCUdTrSEExQK8ZzIEMFPIIrBue Mj6sap7psLVLe6EW3X2jZJ8r3ddVNUNja0fsaFLV5jk0UhMRMXam3eIOkNSGTvxFaeY9 9x55PRLsYrv5soE3ZO4E2KRkYtiEdUCpOkMWanv6Vws2TEF3OIxh+G7dEXX4wdTNpY5h 8NDVSna10ktWGcAvvlrGIgyFVinyfkGzim21gSlxLNY5F7KedDsz3tubW9aNNZuZ5MFe vMEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language; bh=LgmZctRBCRCjeNq4NTJW3txW0Wy2py5eRNmCBxzAQ4Q=; b=Fw0tBHRbEkyVI48DTnFIeenJJH887jnA+taJkjVTHvlb7yOVnh6Wc9d4fUYv4d+tMS 5Cqk20rqZ8GSM5hkrucaIMB16bQGn5he4t7XWVRhh1AhlCcOUWsnTG9NU/R3UYQJVaGc C+EzbPfuo8gArYFN7GiXjIyusGsWJc1KD30vajVhzNLh4vqFtxwchO8b8pMgnmGde8Kn mYPEHCml1zyMZJtPdMjjo7RbbuXe612n6exT3e4SuFcz94/3/1kh8xFvKPJW4CNzKZGg dzcYHbb87e9RrKxkSKADWemT80QLsrEm6DfDSEbQeXmtLuu4z/eC2Wx6EqMiAMCWJ2rG voXQ==
X-Gm-Message-State: AOAM532KdDUDzR9FWBICWCTDwSTgUI7TusMTEgB72QzGsGOj/Zc4W3nz GV+25QDd6X9y6MpopHD5GeYFZVG6o6Q=
X-Google-Smtp-Source: ABdhPJy5/rd1FkVwdfyt3XZtcbZk7y91iCNnP3vN33WcxahNgf/4u809PSXuIK1+abXsm/63eyuW0Q==
X-Received: by 2002:a05:6214:16cf:: with SMTP id d15mr23004110qvz.32.1613537192559;  Tue, 16 Feb 2021 20:46:32 -0800 (PST)
Received: from [192.168.1.150] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id y35sm490672qtd.10.2021.02.16.20.46.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Feb 2021 20:46:32 -0800 (PST)
To: Calsify <calsify@ietf.org>, Cyrus Daboo <cyrus@daboo.name>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <a44f9c2c-18ff-9f6f-ca43-82e0a104889f@gmail.com>
Date: Tue, 16 Feb 2021 23:46:31 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------FBBA52171442DA9DBE3FE59D"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/u4I1EcFR_npRjbC5fdIV-vuapw4>
Subject: [calsify] RFC7986 and EMAIL parameter
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: Wed, 17 Feb 2021 04:46:35 -0000

This is a multi-part message in MIME format.
--------------FBBA52171442DA9DBE3FE59D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

I wonder if Cyrus could help clarify a couple of issues.

The text says:

  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.

So

question 1:

Is it the case that the value - the calendar address is still the 
identifier for the attendee?

Question 2:

is it legal to send a REPLY back with a different EMAIL value - e.g. 
attendee decides they want to use a different email address?

Question 3:

Does "Recipients can also use this value as an alternative means of 
contacting the calendar user via email." include sending iMip messages?

Question 4: (already past a 'couple')

5546 says:

    When used to provide a delegation response,
    the "Delegator" SHOULD include the calendar address of the "Delegate"
    on the "DELEGATED-TO" property parameter of the "Delegator's"
    "ATTENDEE" property.  The "Delegate" SHOULD include the calendar
    address of the "Delegator" on the "DELEGATED-FROM" property parameter
    of the "Delegate's" "ATTENDEE" property.

So that implies that the DELEGATED-TO value might also be a non mailto 
URI? 7986 says nothing about these parameters

I assume that we could have something like:

ATTENDEE;CN=Michael 
Douglass;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=mdouglass@bedework.com 
<mailto:mikeadouglass@gmail.com>:/sadlksdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKjLkjLKJ/principal/

ATTENDEE;CN=Another Michael 
Douglass;PARTSTAT=ACCEPTED;DELEGATED-TO="/sadlksdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKjLkjLKJ/principal/";EMAIL=mikeadouglass@gmail.com 
<mailto:mikeadouglass@gmail.com>:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/







--------------FBBA52171442DA9DBE3FE59D
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I wonder if Cyrus could help clarify a couple of issues.</p>
    <p>The text says:</p>
    <pre class="newpage"> 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.
</pre>
    <p>So <br>
    </p>
    <p>question 1:</p>
    <p>Is it the case that the value - the calendar address is still the
      identifier for the attendee?</p>
    <p>Question 2:</p>
    <p>is it legal to send a REPLY back with a different EMAIL value -
      e.g. attendee decides they want to use a different email address?</p>
    <p>Question 3:</p>
    <p>Does "Recipients can also use this value as an alternative means
      of contacting the calendar user via email." include sending iMip
      messages?</p>
    <p>Question 4: (already past a 'couple')</p>
    <p>5546 says:</p>
    <pre class="newpage">   When used to provide a delegation response,
   the "Delegator" SHOULD include the calendar address of the "Delegate"
   on the "DELEGATED-TO" property parameter of the "Delegator's"
   "ATTENDEE" property.  The "Delegate" SHOULD include the calendar
   address of the "Delegator" on the "DELEGATED-FROM" property parameter
   of the "Delegate's" "ATTENDEE" property.</pre>
    <p>So that implies that the DELEGATED-TO value might also be a non
      mailto URI? 7986 says nothing about these parameters<br>
    </p>
    <p>I assume that we could have something like:</p>
    <p>ATTENDEE;CN=Michael Douglass;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=<a
        href="mailto:mikeadouglass@gmail.com">mdouglass@bedework.com</a>:/sadlksdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKjLkjLKJ/principal/</p>
    <p>ATTENDEE;CN=Another Michael
      Douglass;PARTSTAT=ACCEPTED;DELEGATED-TO="/sadlksdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKjLkjLKJ/principal/";EMAIL=<a
        href="mailto:mikeadouglass@gmail.com">mikeadouglass@gmail.com</a>:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/</p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------FBBA52171442DA9DBE3FE59D--


From nobody Tue Feb 16 21:07:51 2021
Return-Path: <ron.even.tlv@gmail.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 9A8843A14DF; Tue, 16 Feb 2021 21:07:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=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=gmail.com
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 zIC-cp7mzfPv; Tue, 16 Feb 2021 21:07:48 -0800 (PST)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 B5E063A14DD; Tue, 16 Feb 2021 21:07:47 -0800 (PST)
Received: by mail-wm1-x336.google.com with SMTP id n10so1346916wmq.0; Tue, 16 Feb 2021 21:07:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=/gqfXgdh/mEpSJsHqR85PBOujlxEqs4qQYPY01fHzNw=; b=JcfPv4pvQSMIykMQXSMfCIwTKuMNgdTw/tf0ptc8C2ONI8SUaiF4Vs/xkRUjQj9gtI Wj2uz2WUkEbHgUUJntPjZXl2VBo9FQEJYT8jj7neLBo6E677Mhhmt98gy2sKORq0md4f BaRrtcqZkQJ/mlstkcLafgdNlTNhB+puO8Ee7Jif69WPg1GD2yHKSJgTcPkkajLOQTfe iJBLiZIw2b5XxdflITgwvIjga/599tx/NUzaR53BoNemhS24mcJs39dkGI7H25ghoP0R hOtdAWZ6uTwMN25p/eRUHDB+3Yss4QerCEruCjDH/q7weaMdUO5+BCmRA3QmrUJFPqkK EcUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=/gqfXgdh/mEpSJsHqR85PBOujlxEqs4qQYPY01fHzNw=; b=BjI3yR+7ZPWD1oJgq1ivr53aOsfl7muVB9wTTKukUKUMEDx9NdvOp+kkwuQrk6EvQD +pF2Iqru28qCz+zIVqzc0mqdyb8UOgtcvh8fmzOXR+tqNpxaSJApySlOxILJqQ1a+aBl 2igaK8uh5elhNMCORRLW+3olgBXgkBzY6EcW4fHVrVWyrkTkPhOS+aApTNkxGB6V8TnL oy1iZqw/K34Hy23KTqe5R56xduzDJRijAgMsAyZdVdDgnxuZ6+TglUPOQM/17Nn9ej5w FphH1L2peCBnt2rPLXlon+RdTEvarkSZfbHkbBpb+usB0oRPpRprPtcReDHVB+K5L+GN yqvw==
X-Gm-Message-State: AOAM531pL6Yu4s5c3VhWcWrsxAhPutl0NjtHi7NkNUk1cBATnqonLP3m DTWed6p7eGVU48T1OTKqkndVlzt/q5k=
X-Google-Smtp-Source: ABdhPJy41TTyAx4EeZNOMZ0xYwhkbQnnFjYzWGvrEePZblDrKPMDDe/yhGyBOhHOshjllGDCMh7V/w==
X-Received: by 2002:a7b:c5cc:: with SMTP id n12mr5436430wmk.123.1613538465826;  Tue, 16 Feb 2021 21:07:45 -0800 (PST)
Received: from RoniPC (bzq-109-65-42-55.red.bezeqint.net. [109.65.42.55]) by smtp.gmail.com with ESMTPSA id i8sm2247930wry.90.2021.02.16.21.07.44 (version=TLS1 cipher=ECDHE-ECDSA-AES128-SHA bits=128/128); Tue, 16 Feb 2021 21:07:45 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Ken Murchison'" <murch@fastmail.com>, <gen-art@ietf.org>
Cc: <calsify@ietf.org>, <draft-ietf-calext-valarm-extensions.all@ietf.org>, <last-call@ietf.org>
References: <161338513250.5032.11173671129331374190@ietfa.amsl.com> <a87b7942-9976-39c5-43dd-23f4acfa9a6a@fastmail.com>
In-Reply-To: <a87b7942-9976-39c5-43dd-23f4acfa9a6a@fastmail.com>
Date: Wed, 17 Feb 2021 07:07:42 +0200
Message-ID: <244d01d704ea$d2e76f40$78b64dc0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJmwDIr8DqYv1HStF1XR4ItQwCmlAMJDWRfqSQMsPA=
Content-Language: he
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/A7luCwTAc_uWvijGlRQneYWqaE8>
Subject: Re: [calsify] Genart last call review of draft-ietf-calext-valarm-extensions-04
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: Wed, 17 Feb 2021 05:07:50 -0000

Hi Ken,
Thanks, it is OK=20
Roni

> -----Original Message-----
> From: Ken Murchison [mailto:murch@fastmail.com]
> Sent: Monday, February 15, 2021 2:27 PM
> To: Roni Even; gen-art@ietf.org
> Cc: calsify@ietf.org; =
draft-ietf-calext-valarm-extensions.all@ietf.org; last-
> call@ietf.org
> Subject: Re: Genart last call review of =
draft-ietf-calext-valarm-extensions-04
>=20
> Hi Roni,
>=20
> Thanks for the review.  Your comment is addressed below.
>=20
>=20
> On 2/15/21 5:32 AM, Roni Even via Datatracker wrote:
> > Reviewer: Roni Even
> > Review result: Ready with Nits
> >
> > I am the assigned Gen-ART reviewer for this draft. The General Area
> > Review Team (Gen-ART) reviews all IETF documents being processed by
> > the IESG for the IETF Chair.  Please treat these comments just like
> > any other last call comments.
> >
> > For more information, please see the FAQ at
> >
> > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> >
> > Document: draft-ietf-calext-valarm-extensions-??
> > Reviewer: Roni Even
> > Review Date: 2021-02-15
> > IETF LC End Date: 2021-02-16
> > IESG Telechat date: Not scheduled for a telechat
> >
> > Summary:
> > The document is ready for publication as standard track RFC with =
nits
> >
> > Major issues:
> >
> > Minor issues:
> >
> > Nits/editorial comments:
> >
> > 1. The structured-location is optional so if it is not specified for
> > proximity I assume that it implies current location?
>=20
>=20
> STRUCTURED-LOCATION is optional because its not used for PROXIMITY:
> [DIS]CONNECT.  I've made the following change to the text:
>=20
>               <t hangText=3D"Description:">This property is used to
>               indicate that an alarm has a location-based trigger. Its
>               value identifies the direction of motion used to trigger
> -            the alarm. One or more location values are set using
> +            the alarm. One or more location values MUST be set using
>               "STRUCTURED-LOCATION" properties.</t>
>=20
> Is this sufficient?
>=20
> --
> Kenneth Murchison
> Senior Software Developer
> Fastmail US LLC


From nobody Wed Feb 17 07:23:15 2021
Return-Path: <cyrus@daboo.name>
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 AEFB43A1ADD for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 07:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 umCvxwjOkCnV for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 07:23:12 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 077933A1ADA for <calsify@ietf.org>; Wed, 17 Feb 2021 07:23:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 1F63130449D25C; Wed, 17 Feb 2021 10:23:05 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eT9o52cN7uvR; Wed, 17 Feb 2021 10:23:00 -0500 (EST)
Received: from cyrus.local (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id A212430449D243; Wed, 17 Feb 2021 10:23:00 -0500 (EST)
Date: Wed, 17 Feb 2021 10:22:57 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Michael Douglass <mikeadouglass@gmail.com>, Calsify <calsify@ietf.org>
Message-ID: <c816206e-13de-4dda-afac-1f8923257296@cyrus.local>
In-Reply-To: <a44f9c2c-18ff-9f6f-ca43-82e0a104889f@gmail.com>
References: <a44f9c2c-18ff-9f6f-ca43-82e0a104889f@gmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=6558
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/8MTpKczT7q5G9j41_njGnjVvXI0>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Wed, 17 Feb 2021 15:23:14 -0000

Hi Michael,

--On Tue, 16 Feb 2021 23:46:31 -0500 Michael Douglass 
<mikeadouglass@gmail.com> wrote:

Some background first: when we were working on CalendarServer and deploying 
it within Apple, we initially used email addresses as the ORGNAIZER/ATTENDEE 
calendar user address value. However, we quickly ran into a problem with 
that: it turns out that there are frequent email address (and name) changes 
that happen for individuals for a variety of reasons, and we needed a way to 
change the mailto: values. Doing that with scheduling messages is 
problematic because it requires rewriting/resending invites to all 
particpants. With recurring messages, we probably would not want to re-write 
past instances, so that would require "splitting" the recurrence.

In the end we decided on a different solution: internally, the server would 
use a `urn:uuid` URI for the calendar user address values. Those URIs were 
the stable directory GUID for each user, and would not change even if other 
properties of the user record did (email, name, etc). So CalendarServer 
would return urn:uuid values in any iCalendar data transmitted over CalDAV. 
But when sending scheduling messages externally (via iMIP and iSchedule, 
when that was a thing) we would rewrite the ORGANIZER and ATTENDEE property 
values to the current value of the corresponding user's email address URI. 
Similarly, for scheduling messages being delivered from an outside source 
into the server, we would rewrite the mailto URIs to urn:uuid ones.

There were some client-side implications to this: the client does an 
attendee auto-complete when an organizer is adding attendees to an event. It 
does that using the CalDAV principal search, querying on name, email etc, 
and it extracts one of several prossible calendar user addresses for the 
attendee and inserts that into the iCalendar object sent to the server. The 
server always rewrites incoming (PUT) iCalendar data to "normalize" 
ORGANIZER and ATTENDEE property values to the urn:uuid form.

The problem with this on the client side, was that they wanted to be able to 
relate calendar particpants to address book entries, so that they could show 
additional details about the attendee (i.e., show a telephone number, or IM 
contact info etc). However, the urn:uuid values are not in any contacts 
records (yes we - Apple/CalConnect - had lots of dicussions about the need 
for a separate calendar user address field in contact databases but there 
was never consensus on how best to do that, or even whether users would 
grasp the purpose). So, to allow the client to match urn:uuid values to 
local contact data, we added the EMAIL parameter. The server always rewrites 
the EMAIL parameter to the most recent value for incoming (PUT)/outgoing 
(GET) events sent over CalDAV, so there is a strong liklihood it will match 
a contact (or match a record in the directory service the AddressBook.app 
can use). Also, in the case no contact could be matched, the EMAIL value 
could be used as an alternative, out-of-band, way to contact the particpant 
over email.

> So
>
> question 1:
>
> Is it the case that the value - the calendar address is still the
> identifier for the attendee?

Yes, the calendar user address is always the "key" for identifying/matching 
ORGANIZER and ATTENDEE properties across iCalendar objects, be they distinct 
events or recurrence instances.

> Question 2:
>
> is it legal to send a REPLY back with a different EMAIL value - e.g.
> attendee decides they want to use a different email address?

The EMAIL parameter value was never intended to be an iMIP address used for 
scheduling. The calendar user address value of the relevent iCalendar 
property would always be the scheduling address. We handled that by always 
rewriting iCalendar data on the way into, and out of, our external 
scheduling system.

> Question 3:
>
> Does "Recipients can also use this value as an alternative means of
> contacting the calendar user via email." include sending iMip messages?

As per above, no, it was never intended that EMAIL be used for iMIP. It is 
important to note, that some calendar systems allow users to "sign-up" using 
a 3rd party email address as their "identifier", but generate their own 
mailto calendar user address for iMIP (usually with a domain set to the 
calendar server host and an "opaque" identifier for thew local part). In 
such a case there could be two email addresses on a property: one in the 
EMAIL paramater (the 3rd party address that could be matched to a contact 
record); and the other the calendar user address value in the property.

> Question 4: (already past a 'couple')
>
> 5546 says:
>
>     When used to provide a delegation response,
>     the "Delegator" SHOULD include the calendar address of the "Delegate"
>     on the "DELEGATED-TO" property parameter of the "Delegator's"
>     "ATTENDEE" property.  The "Delegate" SHOULD include the calendar
>     address of the "Delegator" on the "DELEGATED-FROM" property parameter
>     of the "Delegate's" "ATTENDEE" property.
>
> So that implies that the DELEGATED-TO value might also be a non mailto URI?
> 7986 says nothing about these parameters

Those parameters typically reference other ATTENDEE properties (via the 
calendar user address value) and those other properties can have an EMAIL 
parameter that can be used with the delegate.

> I assume that we could have something like:
>
> ATTENDEE;CN=Michael
> Douglass;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=mdouglass@bedework.com <mailto:
> mikeadouglass@gmail.com>:/sadlksdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKj
> LkjLKJ/principal/

I think the EMAIL parameter value is wrong (at the very least it is missing 
some DQUOTEs). It should just be the address spec, not the full address. I 
think that is my fault as I know see that 7986 did not properly define the 
parameter value. It just said "email address", but shouyld have references 
RFC5322 3.4.1 for the addr-spec definition.

> ATTENDEE;CN=Another Michael Douglass;PARTSTAT=ACCEPTED;DELEGATED-TO="/sadlk
> sdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKjLkjLKJ/principal/";EMAIL=mikead
> ouglass@gmail.com <mailto:mikeadouglass@gmail.com>:/aMzkzNTI4MzkzNTI4MzkzNQ
> PuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/

Same issue with EMAIL parameter value. However, the concept of relating 
properties via the DELEGATED-* parameters is fine.

BTW: I am not sure the calendar user address values in your example are 
legal. As per RFC 3986, there should be a "scheme:" prefix present.

-- 
Cyrus Daboo


From nobody Wed Feb 17 08:04:50 2021
Return-Path: <mikeadouglass@gmail.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 3EA403A1B2D for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 08:04:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=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=gmail.com
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 myrZnbO2X-k4 for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 08:04:47 -0800 (PST)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 1F02B3A1B25 for <calsify@ietf.org>; Wed, 17 Feb 2021 08:04:47 -0800 (PST)
Received: by mail-qk1-x734.google.com with SMTP id r77so13164627qka.12 for <calsify@ietf.org>; Wed, 17 Feb 2021 08:04:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=rCLpuEiky02sAWoi3YNU2spQJj80pNNve+tWkALDmFo=; b=TSYheaWRVTAfvIppUBPIAkPTPl1PFTuu4vULl3wAJ7TxaXCwVSqj+ZOCtWjDpijW3F D3K12nUvmiNFx8h/Yo3SkYHqu6ca+HzAyKiRs4ioWM2mPQgllW2GbaybuVP/Qsr9iVJl mDYt/9WMuIt7qlqc/rDIKMDhkMmQtyoWoULGox16Y1GofLQ2c/gljtzx2u+4VkRlvfFb SsdpWOGVirzGnptwwrFIeP3v9HbRTULbk5R9T7BaModox0g4oyFtFZYKI63OZ1I24oIb K1g6LOAygc79yWRwit9twZxQQmXwkmwQqtCWKsaXT34+CtAuPppFC+Y0dy9dhvOxtyE4 ulmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=rCLpuEiky02sAWoi3YNU2spQJj80pNNve+tWkALDmFo=; b=ToNxUOpMNHjUpLqLVmd7nGo2hUA7EuXJ6imsEqOkwFTyZOHQIji2Qv3pH8EwRHlt7p 2SGhBlwL+4i0P7I6bDRFPFUF7pNAwQfaTqgojplONvcsCC59VBreqzBsanQHZx5q7zNW /Nlb3f0xqTnduS5GZFAOB0juD0azEWUZkaoGA3rWp0kbZDMwnhvAzceoeBkBR30+bVUR i15JNZq56jaxwtOnYXFT/va/tcussq3Lv0sWevkvZ3pCErdddoADk7i/i46nCP29x4gP cEXPxqUSutiXX0QvFGkbkqlu0cnrun7rTRG/eDQc0IG2n7yPzv3MJgly3T81cijWsPCQ i9gA==
X-Gm-Message-State: AOAM530+HX0ofCxwAN52+Hs9PzJrAmfuA3HxXTkVkjdyIVVhyT/Pc7kd QMb5XY2QPsiww/2yGy4rXBDXEs1lSmE=
X-Google-Smtp-Source: ABdhPJwdYPoZ1UKxwscgkGEd6KA8H+SSqNoJ8ZRgsvMR2S15b955H8+9p57JFLsHK9y485mDAzFlEQ==
X-Received: by 2002:a37:67d3:: with SMTP id b202mr24000327qkc.178.1613577883628;  Wed, 17 Feb 2021 08:04:43 -0800 (PST)
Received: from [192.168.1.150] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id d22sm1439211qtp.34.2021.02.17.08.04.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Feb 2021 08:04:42 -0800 (PST)
To: Cyrus Daboo <cyrus@daboo.name>, Calsify <calsify@ietf.org>
References: <a44f9c2c-18ff-9f6f-ca43-82e0a104889f@gmail.com> <c816206e-13de-4dda-afac-1f8923257296@cyrus.local>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <304feeb6-9633-358d-5143-bd5264776c74@gmail.com>
Date: Wed, 17 Feb 2021 11:04:41 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <c816206e-13de-4dda-afac-1f8923257296@cyrus.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/pQJDFzOPsv2aazH1i8Jnincyzec>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Wed, 17 Feb 2021 16:04:49 -0000

Thanks Cyrus.

See below

On 2/17/21 10:22, Cyrus Daboo wrote:
> Hi Michael,
>
> --On Tue, 16 Feb 2021 23:46:31 -0500 Michael Douglass 
> <mikeadouglass@gmail.com> wrote:
>
> Some background first: when we were working on CalendarServer and 
> deploying it within Apple, we initially used email addresses as the 
> ORGNAIZER/ATTENDEE calendar user address value. However, we quickly 
> ran into a problem with that: it turns out that there are frequent 
> email address (and name) changes that happen for individuals for a 
> variety of reasons, and we needed a way to change the mailto: values. 
> Doing that with scheduling messages is problematic because it requires 
> rewriting/resending invites to all particpants. With recurring 
> messages, we probably would not want to re-write past instances, so 
> that would require "splitting" the recurrence.
>
> In the end we decided on a different solution: internally, the server 
> would use a `urn:uuid` URI for the calendar user address values. Those 
> URIs were the stable directory GUID for each user, and would not 
> change even if other properties of the user record did (email, name, 
> etc). So CalendarServer would return urn:uuid values in any iCalendar 
> data transmitted over CalDAV. But when sending scheduling messages 
> externally (via iMIP and iSchedule, when that was a thing) we would 
> rewrite the ORGANIZER and ATTENDEE property values to the current 
> value of the corresponding user's email address URI. Similarly, for 
> scheduling messages being delivered from an outside source into the 
> server, we would rewrite the mailto URIs to urn:uuid ones.
>
> There were some client-side implications to this: the client does an 
> attendee auto-complete when an organizer is adding attendees to an 
> event. It does that using the CalDAV principal search, querying on 
> name, email etc, and it extracts one of several prossible calendar 
> user addresses for the attendee and inserts that into the iCalendar 
> object sent to the server. The server always rewrites incoming (PUT) 
> iCalendar data to "normalize" ORGANIZER and ATTENDEE property values 
> to the urn:uuid form.
>
> The problem with this on the client side, was that they wanted to be 
> able to relate calendar particpants to address book entries, so that 
> they could show additional details about the attendee (i.e., show a 
> telephone number, or IM contact info etc). However, the urn:uuid 
> values are not in any contacts records (yes we - Apple/CalConnect - 
> had lots of dicussions about the need for a separate calendar user 
> address field in contact databases but there was never consensus on 
> how best to do that, or even whether users would grasp the purpose). 
> So, to allow the client to match urn:uuid values to local contact 
> data, we added the EMAIL parameter. The server always rewrites the 
> EMAIL parameter to the most recent value for incoming (PUT)/outgoing 
> (GET) events sent over CalDAV, so there is a strong liklihood it will 
> match a contact (or match a record in the directory service the 
> AddressBook.app can use). Also, in the case no contact could be 
> matched, the EMAIL value could be used as an alternative, out-of-band, 
> way to contact the particpant over email.
>
>> So
>>
>> question 1:
>>
>> Is it the case that the value - the calendar address is still the
>> identifier for the attendee?
>
> Yes, the calendar user address is always the "key" for 
> identifying/matching ORGANIZER and ATTENDEE properties across 
> iCalendar objects, be they distinct events or recurrence instances.
>
>> Question 2:
>>
>> is it legal to send a REPLY back with a different EMAIL value - e.g.
>> attendee decides they want to use a different email address?
>
> The EMAIL parameter value was never intended to be an iMIP address 
> used for scheduling. The calendar user address value of the relevent 
> iCalendar property would always be the scheduling address. We handled 
> that by always rewriting iCalendar data on the way into, and out of, 
> our external scheduling system.
>
>> Question 3:
>>
>> Does "Recipients can also use this value as an alternative means of
>> contacting the calendar user via email." include sending iMip messages?
>
> As per above, no, it was never intended that EMAIL be used for iMIP. 
> It is important to note, that some calendar systems allow users to 
> "sign-up" using a 3rd party email address as their "identifier", but 
> generate their own mailto calendar user address for iMIP (usually with 
> a domain set to the calendar server host and an "opaque" identifier 
> for thew local part). In such a case there could be two email 
> addresses on a property: one in the EMAIL paramater (the 3rd party 
> address that could be matched to a contact record); and the other the 
> calendar user address value in the property.
>
I think I meant only if the value is not a mailto:. I assume in the 
absence of any other indication (e.g. a valid email) this might be a 
fallback?


>> Question 4: (already past a 'couple')
>>
>> 5546 says:
>>
>>     When used to provide a delegation response,
>>     the "Delegator" SHOULD include the calendar address of the 
>> "Delegate"
>>     on the "DELEGATED-TO" property parameter of the "Delegator's"
>>     "ATTENDEE" property.  The "Delegate" SHOULD include the calendar
>>     address of the "Delegator" on the "DELEGATED-FROM" property 
>> parameter
>>     of the "Delegate's" "ATTENDEE" property.
>>
>> So that implies that the DELEGATED-TO value might also be a non 
>> mailto URI?
>> 7986 says nothing about these parameters
>
> Those parameters typically reference other ATTENDEE properties (via 
> the calendar user address value) and those other properties can have 
> an EMAIL parameter that can be used with the delegate.
>
>> I assume that we could have something like:
>>
>> ATTENDEE;CN=Michael
>> Douglass;PARTSTAT=ACCEPTED;ROLE=CHAIR;EMAIL=mdouglass@bedework.com 
>> <mailto:
>> mikeadouglass@gmail.com>:/sadlksdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKj 
>>
>> LkjLKJ/principal/
>
> I think the EMAIL parameter value is wrong (at the very least it is 
> missing some DQUOTEs). It should just be the address spec, not the 
> full address. I think that is my fault as I know see that 7986 did not 
> properly define the parameter value. It just said "email address", but 
> shouyld have references RFC5322 3.4.1 for the addr-spec definition.
>
>> ATTENDEE;CN=Another Michael 
>> Douglass;PARTSTAT=ACCEPTED;DELEGATED-TO="/sadlk
>> sdfkkljklkjjklljkkjjLKJLKJjLKjJKLKLjJKLLkjKjLkjLKJ/principal/";EMAIL=mikead 
>>
>> ouglass@gmail.com 
>> <mailto:mikeadouglass@gmail.com>:/aMzkzNTI4MzkzNTI4MzkzNQ
>> PuXCcDTdG5iXfOhcljjCSqMYrUXDcs6f1z7CyXejTR/principal/
>
> Same issue with EMAIL parameter value. However, the concept of 
> relating properties via the DELEGATED-* parameters is fine.
>
> BTW: I am not sure the calendar user address values in your example 
> are legal. As per RFC 3986, there should be a "scheme:" prefix present.

One of those was generated by Apple. I created an event yesterday which 
in full is

BEGIN:VCALENDAR
PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN
METHOD:REQUEST
VERSION:2.0
BEGIN:VEVENT
DTEND;TZID=America/New_York:20210219T100000
DTSTART;TZID=America/New_York:20210219T090000
ORGANIZER;CN=Michael Douglass;EMAIL=mikeadouglass@gmail.com:mailto:2_GM4T
  GNJSHAZTSMZVGI4DGOJTGW7UOVQIXU6S7IXFKVSLJVS4VP4YX5J2UCRWN6KC2YMIGY25PWAA
  I@imip.me.com
UID:E5C6F579-5003-4755-B29D-572E0FF147B1
DTSTAMP:20210217T051817Z
SEQUENCE:1
SUMMARY:Testing email param
LAST-MODIFIED:20210217T051817Z
CREATED:20210217T051744Z
ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=mdouglass@bedework.com;RSVP=TRUE;PARTSTA
  T=NEEDS-ACTION:mailto:mdouglass@bedework.com
ATTENDEE;CN=Ken Murchison;CUTYPE=INDIVIDUAL;EMAIL=murch@fastmail.com;RSVP
  =TRUE;PARTSTAT=NEEDS-ACTION:mailto:murch@fastmail.com
ATTENDEE;CN=Michael Douglass;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED;ROLE=CHA
  IR;EMAIL=mikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOh
  cljjCSqMYrUXDcs6f1z7CyXejTR/principal/
END:VEVENT

I believe a URI doesn't require a scheme - a simple path is sufficient



From nobody Wed Feb 17 08:24:36 2021
Return-Path: <cyrus@daboo.name>
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 A97A33A0C2A for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 08:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 YQ-jTjGnPuuu for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 08:24:32 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 694943A0C1E for <calsify@ietf.org>; Wed, 17 Feb 2021 08:24:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 9A89E30449E331; Wed, 17 Feb 2021 11:24:31 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eLm5UDcixtB8; Wed, 17 Feb 2021 11:24:30 -0500 (EST)
Received: from cyrus.local (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id 9D74430449E31F; Wed, 17 Feb 2021 11:24:30 -0500 (EST)
Date: Wed, 17 Feb 2021 11:24:30 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Michael Douglass <mikeadouglass@gmail.com>, Calsify <calsify@ietf.org>
Message-ID: <0e03fc6b-15ba-43bd-8122-73069886ba61@cyrus.local>
In-Reply-To: <304feeb6-9633-358d-5143-bd5264776c74@gmail.com>
References: <304feeb6-9633-358d-5143-bd5264776c74@gmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size=2870
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/oR-xjAllEFZzeo19Ztk34Z12cFM>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Wed, 17 Feb 2021 16:24:35 -0000

Hi Michael,

--On Wed, 17 Feb 2021 11:04:41 -0500 Michael Douglass=20
<mikeadouglass@gmail.com> wrote:


> Thanks Cyrus.
>
> See below
>
>> As per above, no, it was never intended that EMAIL be used for iMIP.  It
>> is important to note, that some calendar systems allow users to  "sign-
>> up" using a 3rd party email address as their "identifier", but  generate
>> their own mailto calendar user address for iMIP (usually with  a domain
>> set to the calendar server host and an "opaque" identifier  for thew
>> local part). In such a case there could be two email  addresses on a
>> property: one in the EMAIL paramater (the 3rd party  address that could
>> be matched to a contact record); and the other the  calendar user address
>> value in the property.
>>
> I think I meant only if the value is not a mailto:. I assume in the absen=
ce
> of any other indication (e.g. a valid email) this might be a fallback?

Of course you can send an iMIP message to any email address and hope it get=
s=20
to the right place! I think the poiunt here is that it should never have to=
=20
be used as a fallback. The ORGANIZER or ATTENDEE property values should be =

mailto's if the intent is to use iMIP. You pasted an example iCalendar=20
message below which illustrates the point. The EMAIL parameter has a gmail =

domain, whilst the CUA value is me.com. Sending an iMIP to the EMAIL addres=
s=20
would result in the scheduling message being intercepted and stored on the =

Google calendar, and not the iCloud calendar.

> One of those was generated by Apple. I created an event yesterday which in
> full is
>
> BEGIN:VCALENDAR
> PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN
> METHOD:REQUEST
> VERSION:2.0
> BEGIN:VEVENT
> DTEND;TZID=3DAmerica/New_York:20210219T100000
> DTSTART;TZID=3DAmerica/New_York:20210219T090000
> ORGANIZER;CN=3DMichael Douglass;EMAIL=3Dmikeadouglass@gmail.com:mailto:2_=
GM4T
>  =C2=A0GNJSHAZTSMZVGI4DGOJTGW7UOVQIXU6S7IXFKVSLJVS4VP4YX5J2UCRWN6KC2YMIGY=
25PWAA
>  =C2=A0I@imip.me.com
> UID:E5C6F579-5003-4755-B29D-572E0FF147B1
> DTSTAMP:20210217T051817Z
> SEQUENCE:1
> SUMMARY:Testing email param
> LAST-MODIFIED:20210217T051817Z
> CREATED:20210217T051744Z
> ATTENDEE;CUTYPE=3DINDIVIDUAL;EMAIL=3Dmdouglass@bedework.com;RSVP=3DTRUE;P=
ARTSTA
>  =C2=A0T=3DNEEDS-ACTION:mailto:mdouglass@bedework.com
> ATTENDEE;CN=3DKen Murchison;CUTYPE=3DINDIVIDUAL;EMAIL=3Dmurch@fastmail.co=
m;RSVP
>  =C2=A0=3DTRUE;PARTSTAT=3DNEEDS-ACTION:mailto:murch@fastmail.com
> ATTENDEE;CN=3DMichael Douglass;CUTYPE=3DINDIVIDUAL;PARTSTAT=3DACCEPTED;RO=
LE=3DCHA
>  =C2=A0IR;EMAIL=3Dmikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDT=
dG5iXfOh
>  =C2=A0cljjCSqMYrUXDcs6f1z7CyXejTR/principal/
> END:VEVENT

Well that may well be a bug!

> I believe a URI doesn't require a scheme - a simple path is sufficient

I think the syntax and associated text in=20
https://www.rfc-editor.org/rfc/rfc3986#section-3 make it pretty clear a=20
scheme is required.

--=20
Cyrus Daboo


From nobody Wed Feb 17 08:56:55 2021
Return-Path: <mikeadouglass@gmail.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 40E1A3A1B56 for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 08:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=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=gmail.com
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 DiF8-FBzd4Py for <calsify@ietfa.amsl.com>; Wed, 17 Feb 2021 08:56:52 -0800 (PST)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 6D57F3A1B23 for <calsify@ietf.org>; Wed, 17 Feb 2021 08:56:52 -0800 (PST)
Received: by mail-qk1-x72c.google.com with SMTP id h8so13396751qkk.6 for <calsify@ietf.org>; Wed, 17 Feb 2021 08:56:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=VO3UiBp/mLy3vDJRyvLJk7+GV8NJdwemB5QIWNFssR8=; b=gaEHy47CmlESAfnRj62A576jfwSbhYNw+4UiVP5Mxy0GJsS5kCwQBb132lGouB+G7h HOMHjjUSFc6XVKiCYgsB0fLQcysHL9urv7ebHL3FC2RjpTqGaSWU5iX5IhoesfF8Yf4L aTT9GPMz3bsVAFWCOwpAveppbONRS7SGlT+6MPbjuyhPaSojmxW9LeLggbhdDE9dmte7 pfDjBh5DqIZKFDk6/JwtmJ1XjB8Xx7rxUQc8id0oc1xKL6YeeLL8oDjc3wGeZ0LaYNva cd1nx7qsvd3vWWjXwSeoXiwBF8xhDaa4M5iL1+UpszL1pe65Dt+hn3gInJYplKQ2n2// mYrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=VO3UiBp/mLy3vDJRyvLJk7+GV8NJdwemB5QIWNFssR8=; b=aMuy/os4UN1QYQfnAjC8tyOdAuyaesXYFHBfUR9k7A71i8PeSDAHxQw9IJNvT11geL qQMAzwWBPIter3tMTWcAHNgR3U8Csbu9nDuIFRcSRfd9X/bB52dj2AxV++RTpBJFc4ws Hn8eegv9HTtzXmqwWEjqgnm3y/CxHmGfCX4jnWqy1JZyJBpKb/2MfQzArZ4fe/a7RSKi ryvgYXomUuNnMvck9XGJq3cz3Tj3gH5F4TcKWg+W8Spd47rHrdoSLB/PqDGjN7oROHFt 1HnrMP+tXmRzcVN8+a/kE8UwrxxzJfwjzjLq69WW9s5HR+4tumj4rmos3Rvgkfmki0eZ Qd+Q==
X-Gm-Message-State: AOAM532oTEgpUSCPD244wiuf9/83/ySgvXOFDzmsB0D25s5cPDBkyT5u bnp0LiA3KYum5SdC8MTk67bYx9/+pdQ=
X-Google-Smtp-Source: ABdhPJxPArxBVlhYSYCseJTst9dzp3+EiCrCQRnwPlUbrQUsIQ10aAjdnP4An1lgs2YtWT7ZTqcilg==
X-Received: by 2002:ae9:e90c:: with SMTP id x12mr81629qkf.498.1613581011088; Wed, 17 Feb 2021 08:56:51 -0800 (PST)
Received: from [192.168.1.141] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.gmail.com with ESMTPSA id j2sm1940871qkk.96.2021.02.17.08.56.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Feb 2021 08:56:50 -0800 (PST)
From: Mike Douglass <mikeadouglass@gmail.com>
X-Google-Original-From: Mike Douglass <MikeADouglass@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Wed, 17 Feb 2021 11:56:49 -0500
Message-Id: <A1D09E1C-9FAD-45A9-92FA-B6936F338E0C@gmail.com>
References: <0e03fc6b-15ba-43bd-8122-73069886ba61@cyrus.local>
Cc: Calsify <calsify@ietf.org>
In-Reply-To: <0e03fc6b-15ba-43bd-8122-73069886ba61@cyrus.local>
To: Cyrus Daboo <cyrus@daboo.name>
X-Mailer: iPhone Mail (18D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/RP00vP07TJwmxE9qZS_WQj6Jg5Q>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Wed, 17 Feb 2021 16:56:54 -0000

Sent from my iPhone

> On Feb 17, 2021, at 11:24, Cyrus Daboo <cyrus@daboo.name> wrote:
>=20
> =EF=BB=BFHi Michael,
>=20
> --On Wed, 17 Feb 2021 11:04:41 -0500 Michael Douglass <mikeadouglass@gmail=
.com> wrote:
>=20
>=20
>> Thanks Cyrus.
>>=20
>> See below
>>=20
>>> As per above, no, it was never intended that EMAIL be used for iMIP.  It=

>>> is important to note, that some calendar systems allow users to  "sign-
>>> up" using a 3rd party email address as their "identifier", but  generate=

>>> their own mailto calendar user address for iMIP (usually with  a domain
>>> set to the calendar server host and an "opaque" identifier  for thew
>>> local part). In such a case there could be two email  addresses on a
>>> property: one in the EMAIL paramater (the 3rd party  address that could
>>> be matched to a contact record); and the other the  calendar user addres=
s
>>> value in the property.
>>>=20
>> I think I meant only if the value is not a mailto:. I assume in the absen=
ce
>> of any other indication (e.g. a valid email) this might be a fallback?
>=20
> Of course you can send an iMIP message to any email address and hope it ge=
ts to the right place! I think the poiunt here is that it should never have t=
o be used as a fallback. The ORGANIZER or ATTENDEE property values should be=
 mailto's if the intent is to use iMIP. You pasted an example iCalendar mess=
age below which illustrates the point. The EMAIL parameter has a gmail domai=
n, whilst the CUA value is me.com. Sending an iMIP to the EMAIL address woul=
d result in the scheduling message being intercepted and stored on the Googl=
e calendar, and not the iCloud calendar.
>=20
>> One of those was generated by Apple. I created an event yesterday which i=
n
>> full is
>>=20
>> BEGIN:VCALENDAR
>> PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN
>> METHOD:REQUEST
>> VERSION:2.0
>> BEGIN:VEVENT
>> DTEND;TZID=3DAmerica/New_York:20210219T100000
>> DTSTART;TZID=3DAmerica/New_York:20210219T090000
>> ORGANIZER;CN=3DMichael Douglass;EMAIL=3Dmikeadouglass@gmail.com:mailto:2_=
GM4T
>>  GNJSHAZTSMZVGI4DGOJTGW7UOVQIXU6S7IXFKVSLJVS4VP4YX5J2UCRWN6KC2YMIGY25PWAA=

>>  I@imip.me.com
>> UID:E5C6F579-5003-4755-B29D-572E0FF147B1
>> DTSTAMP:20210217T051817Z
>> SEQUENCE:1
>> SUMMARY:Testing email param
>> LAST-MODIFIED:20210217T051817Z
>> CREATED:20210217T051744Z
>> ATTENDEE;CUTYPE=3DINDIVIDUAL;EMAIL=3Dmdouglass@bedework.com;RSVP=3DTRUE;P=
ARTSTA
>>  T=3DNEEDS-ACTION:mailto:mdouglass@bedework.com
>> ATTENDEE;CN=3DKen Murchison;CUTYPE=3DINDIVIDUAL;EMAIL=3Dmurch@fastmail.co=
m;RSVP
>>  =3DTRUE;PARTSTAT=3DNEEDS-ACTION:mailto:murch@fastmail.com
>> ATTENDEE;CN=3DMichael Douglass;CUTYPE=3DINDIVIDUAL;PARTSTAT=3DACCEPTED;RO=
LE=3DCHA
>>  IR;EMAIL=3Dmikeadouglass@gmail.com:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXf=
Oh
>>  cljjCSqMYrUXDcs6f1z7CyXejTR/principal/
>> END:VEVENT
>=20
> Well that may well be a bug!
>=20
>> I believe a URI doesn't require a scheme - a simple path is sufficient
>=20
> I think the syntax and associated text in https://www.rfc-editor.org/rfc/r=
fc3986#section-3 make it pretty clear a scheme is required.

So it does - bug then. However it may be Thunderbird - it=E2=80=99s very har=
d (at least I don=E2=80=99t know of a way) to get apple calendar to export a=
 single email so I sent it and saved the attachment.

I=E2=80=99d need to check further


>=20
> --=20
> Cyrus Daboo


From nobody Thu Feb 18 19:07:07 2021
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 ED93D3A0C2A for <calsify@ietfa.amsl.com>; Thu, 18 Feb 2021 19:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=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=SqAlixiG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gAG/VqIb
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 KXK_T6GC2AWT for <calsify@ietfa.amsl.com>; Thu, 18 Feb 2021 19:07:00 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D402B3A0C20 for <calsify@ietf.org>; Thu, 18 Feb 2021 19:07:00 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 9D139B86; Thu, 18 Feb 2021 22:06:59 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Thu, 18 Feb 2021 22:06:59 -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=ncrsoRe 6UmlnCbJp3n8tR1NV++ltodgZ6RmhVv7s12c=; b=SqAlixiGJhBOWpryWjtl5FK Up44+UxdZYpwUoKvLQpgEc+3BWVdnojwoR8lHi1EssD+8eEMSV6ON1TMEwaE9YE6 Mw5xmtjxZvepJbuMfXH7DUEGV1KDFg2RmUA2G8H79t9bDVET+idNYOjZQ6axZdu+ T2/QTm77SGgr8KiZHM4dZQh2UzAUhKciLRY2h6IzeZfJrRFm1RxHmJvPCZhmOfvF uiTqsmHhn01l/zOYJv8fk6PkJE87Dxhu7ncR9k2TyOt2pyO1O8sopfiadzXdHDwG DbdcN8cWxqpvcGCiajZ1foB9PlGmEd6hmJX0JbUX2OFm78B2PKPxsO0qNniP44g= =
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=ncrsoR e6UmlnCbJp3n8tR1NV++ltodgZ6RmhVv7s12c=; b=gAG/VqIbPptT8wSQoCq5iV SzCRJd1H1CUcYbIiFom5eV894rhSck3X7C44NKyrQoTlZvOFZNh4PzMnefYKq5LV flX3dXvHnsMFJrNNVji/RBn0fzn/FeKn61QkXxyFV848aYY+q5yW1/hA5SRvqwjc GX7CBpDEiuVWJQ33VhAMdaKA+QJTBd5eRxTEbuVZP4PbJ11Tso+J1VtySSLE4y57 iODhdYniScrf6XwAFu/FrMbPWCytdkr4iSDq7rI2dYp0WhtVzdE9aiY3T8gzkLzT 3rjMy9mFrSLx1XUFtx3DA1txur9Gnj9tvJuWrzOqTouSY8FT3JVMbnBZ6hmd959w ==
X-ME-Sender: <xms:UisvYNkPKaTWHbxGoFt5ebIO3P8xwdMQb6tmACzH3kUrJL-dEtEJTg> <xme:UisvYI3Rutt18IPiIoQwGaouiRfft3TXYXRGGX9CYahzYcScUAXBeooC8vi35QjQw l0iA_P26rxKUw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjeehgdehgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfpfgvihhl ucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomheqne cuggftrfgrthhtvghrnhephfelheffteefueeivdekgeeijeeiuefhudfgveellefgvedu teeutdelieeggfejnecuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghi lhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:UisvYDo_LNKAxH7n3fdBpCGGSa8BIVtNkYe6VM3Ca5NJPMIdyDr_YA> <xmx:UisvYNlzABgtziG1E5-Gsiz4fntnXJvRyuU9Fa4K7ieP4jmi0KqbUQ> <xmx:UisvYL0NltYYlrDy_3f2f4BdxpTRMu74h-zuv9qjed-aV6AIzIVLSA> <xmx:UysvYAjJYKffvNJ0uDwV6UTJgZ5mWcSqhnc0xtaargaCZ9jqg1MoAg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7CF1236005C; Thu, 18 Feb 2021 22:06:58 -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: <e1e7222e-8c6e-40b3-a8cf-a45982acb00c@dogfood.fastmail.com>
In-Reply-To: <A1D09E1C-9FAD-45A9-92FA-B6936F338E0C@gmail.com>
References: <0e03fc6b-15ba-43bd-8122-73069886ba61@cyrus.local> <A1D09E1C-9FAD-45A9-92FA-B6936F338E0C@gmail.com>
Date: Fri, 19 Feb 2021 14:06:57 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: "Cyrus Daboo" <cyrus@daboo.name>, calsify@ietf.org
Content-Type: multipart/alternative; boundary=186db1c40ff04129b136a20e727c7f8d
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/pXvsVmp25Nlcgk6WjP_kJwKhhQw>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Fri, 19 Feb 2021 03:07:05 -0000

--186db1c40ff04129b136a20e727c7f8d
Content-Type: text/plain

Thanks for the background Cyrus. So just to confirm, the CUA is:
 * The target for sending iTIP messages. This may be a mailto URI for iMIP, but may also be some other UI (which is essentially an opaque string to clients) if you have some internal mechanism for delivering the messages.
 * A kind of UID that's consistent for the same participant across different events.
Is that right? Presuming so, then going back to the discussion of translation between iCalendar and JSCalendar, I think this maps very cleanly with the current spec:
 * The CUA maps to the sendTo property <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-32#page-36> of the Participant. There would be a single value in the sendTo map: if it's a `mailto:` URI the value would be under the key `imip`, otherwise it would be under the key `other`.
 * The EMAIL parameter value maps to the email <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-32#page-36> property of the Participant. Just as Cyrus says it's supposed to work in iCalendar, this may be different to the iMIP address and is for sending normal email to the participant, not iMIP messages.
Neil.
--186db1c40ff04129b136a20e727c7f8d
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Thanks for=
 the background Cyrus. So just to confirm, the CUA is:<br></div><ul><li>=
The target for sending iTIP messages. This may be a mailto URI for iMIP,=
 but may also be some other UI (which is essentially an opaque string to=
 clients) if you have some internal mechanism for delivering the message=
s.<br></li><li>A kind of UID that's consistent for the same participant =
across different events.<br></li></ul><div>Is that right? Presuming so, =
then going back to the discussion of translation between iCalendar and J=
SCalendar, I think this maps very cleanly with the current spec:<br></di=
v><ul><li>The CUA maps to the <a href=3D"https://tools.ietf.org/html/dra=
ft-ietf-calext-jscalendar-32#page-36">sendTo property</a> of the Partici=
pant.&nbsp;There would be a single value in the sendTo map: if it's a <c=
ode style=3D"border-top-color:rgb(204, 204, 204);border-top-style:solid;=
border-top-width:1px;border-right-color:rgb(204, 204, 204);border-right-=
style:solid;border-right-width:1px;border-bottom-color:rgb(204, 204, 204=
);border-bottom-style:solid;border-bottom-width:1px;border-left-color:rg=
b(204, 204, 204);border-left-style:solid;border-left-width:1px;border-im=
age-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-=
image-source:none;border-image-width:1;border-top-left-radius:3px;border=
-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-=
radius:3px;background-color:rgb(246, 246, 246);background-position-x:0%;=
background-position-y:0%;background-repeat:repeat;background-attachment:=
scroll;background-image:none;background-size:auto;background-origin:padd=
ing-box;background-clip:border-box;font-family:menlo, consolas, monospac=
e;font-size:90%;padding-top:1px;padding-right:3px;padding-bottom:1px;pad=
ding-left:3px;">mailto:</code> URI the value would be under the key <cod=
e style=3D"border-top-color:rgb(204, 204, 204);border-top-style:solid;bo=
rder-top-width:1px;border-right-color:rgb(204, 204, 204);border-right-st=
yle:solid;border-right-width:1px;border-bottom-color:rgb(204, 204, 204);=
border-bottom-style:solid;border-bottom-width:1px;border-left-color:rgb(=
204, 204, 204);border-left-style:solid;border-left-width:1px;border-imag=
e-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-im=
age-source:none;border-image-width:1;border-top-left-radius:3px;border-t=
op-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-ra=
dius:3px;background-color:rgb(246, 246, 246);background-position-x:0%;ba=
ckground-position-y:0%;background-repeat:repeat;background-attachment:sc=
roll;background-image:none;background-size:auto;background-origin:paddin=
g-box;background-clip:border-box;font-family:menlo, consolas, monospace;=
font-size:90%;padding-top:1px;padding-right:3px;padding-bottom:1px;paddi=
ng-left:3px;">imip</code>, otherwise it would be under the key <code sty=
le=3D"border-top-color:rgb(204, 204, 204);border-top-style:solid;border-=
top-width:1px;border-right-color:rgb(204, 204, 204);border-right-style:s=
olid;border-right-width:1px;border-bottom-color:rgb(204, 204, 204);borde=
r-bottom-style:solid;border-bottom-width:1px;border-left-color:rgb(204, =
204, 204);border-left-style:solid;border-left-width:1px;border-image-out=
set:0;border-image-repeat:stretch;border-image-slice:100%;border-image-s=
ource:none;border-image-width:1;border-top-left-radius:3px;border-top-ri=
ght-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:=
3px;background-color:rgb(246, 246, 246);background-position-x:0%;backgro=
und-position-y:0%;background-repeat:repeat;background-attachment:scroll;=
background-image:none;background-size:auto;background-origin:padding-box=
;background-clip:border-box;font-family:menlo, consolas, monospace;font-=
size:90%;padding-top:1px;padding-right:3px;padding-bottom:1px;padding-le=
ft:3px;">other</code>.<br></li><li>The EMAIL parameter value maps to the=
 <a href=3D"https://tools.ietf.org/html/draft-ietf-calext-jscalendar-32#=
page-36">email</a> property of the Participant. Just as Cyrus says it's =
supposed to work in iCalendar, this may be different to the iMIP address=
 and is for sending normal email to the participant, not iMIP messages.<=
br></li></ul><div>Neil.<br></div></body></html>
--186db1c40ff04129b136a20e727c7f8d--


From nobody Thu Feb 18 19:24:02 2021
Return-Path: <cyrus@daboo.name>
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 17F5C3A0F48 for <calsify@ietfa.amsl.com>; Thu, 18 Feb 2021 19:23:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 48M76grMFTfK for <calsify@ietfa.amsl.com>; Thu, 18 Feb 2021 19:23:53 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id EE35B3A0F4A for <calsify@ietf.org>; Thu, 18 Feb 2021 19:23:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 1A13A3044BEF3D; Thu, 18 Feb 2021 22:23:25 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIru117YIqcp; Thu, 18 Feb 2021 22:23:24 -0500 (EST)
Received: from 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa (c-24-131-225-210.hsd1.pa.comcast.net [24.131.225.210]) by daboo.name (Postfix) with ESMTPSA id F085A3044BEF24; Thu, 18 Feb 2021 22:23:23 -0500 (EST)
Date: Thu, 18 Feb 2021 22:23:22 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Neil Jenkins <neilj@fastmailteam.com>, calsify@ietf.org
Message-ID: <f7a8cc4c-6ed7-4fff-a719-ac577ee407ab@cyrus.local>
In-Reply-To: <e1e7222e-8c6e-40b3-a8cf-a45982acb00c@dogfood.fastmail.com>
References: <e1e7222e-8c6e-40b3-a8cf-a45982acb00c@dogfood.fastmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/bchPFZlbQZpwWF1R8laMIaf_-wA>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Fri, 19 Feb 2021 03:24:01 -0000

Hi Neil,

--On Fri, 19 Feb 2021 14:06:57 +1100 Neil Jenkins <neilj@fastmailteam.com> 
wrote:

> Thanks for the background Cyrus. So just to confirm, the CUA is:
>  * The target for sending iTIP messages. This may be a mailto URI for iMIP,
> but may also be some other UI (which is essentially an opaque string to
> clients) if you have some internal mechanism for delivering the messages.
>  * A kind of UID that's consistent for the same participant across
> different events.
> Is that right?

Yes.

> Presuming so, then going back to the discussion of
> translation between iCalendar and JSCalendar, I think this maps very
> cleanly with the current spec:
>  * The CUA maps to the sendTo property <https://tools.ietf.org/html/draft-
> ietf-calext-jscalendar-32#page-36> of the Participant. There would be a
> single value in the sendTo map: if it's a `mailto:` URI the value would be
> under the key `imip`, otherwise it would be under the key `other`.

Can't we just use the URI scheme to determine the method? Why do we need 
'imip' and 'other' nested keys? I realise we might one day have e.g., 
multiple HTTP based scheduling protocols, but I feel like those should all 
have some kind of unique scheme. (Note this is just a question as to what 
drove the current design, not a request for a change - I am cognizant of the 
fact that we spent many man-hours debating the form of calendar user 
addresses for iSchedule without getting anywhere).

>  * The EMAIL parameter value maps to the email
> <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-32#page-36>
> property of the Participant. Just as Cyrus says it's supposed to work in
> iCalendar, this may be different to the iMIP address and is for sending
> normal email to the participant, not iMIP messages.

Yes.
 
-- 
Cyrus Daboo


From nobody Thu Feb 18 20:01:33 2021
Return-Path: <mikeadouglass@gmail.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 AE6303A0CEB for <calsify@ietfa.amsl.com>; Thu, 18 Feb 2021 20:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=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=gmail.com
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 2y80lBRMfkvM for <calsify@ietfa.amsl.com>; Thu, 18 Feb 2021 20:01:30 -0800 (PST)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (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 107503A0CEA for <calsify@ietf.org>; Thu, 18 Feb 2021 20:01:30 -0800 (PST)
Received: by mail-qv1-xf34.google.com with SMTP id k8so1622929qvm.6 for <calsify@ietf.org>; Thu, 18 Feb 2021 20:01:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=QG0JtAA9McxoFBGugmDZRyJ/R7tB5ZjvaiVHtqkbgmc=; b=ujYwyAPLkUEbnuOS49BPkww6R4qIIfUc+lbYsJncuqd0fjf6oyzS8Ma0fB427NhNhv Ue1t8O8oXO8eSrn3nTUH8LFcIE6r5LzL6sLsb5Zk+Vrs2pZP7uitxSwYbx0J/HJxMypl y2Bymgw+S2IyzKjMadC9Jb1kJcObuUpwtwwRtCQityPc1zH1ecXLYCisV+YFQABgHey1 qv47pTpuaZAt+H6HkD3UsnBj7RYZnswtuLrogEA43FUPx+3fk1ZGRvDj7GsyIM52RkX4 wz0l2lLe9r3pM76u8AJfZrNezIP6ik7DbYW/PIMZbUGvZY/iH9UhWiiI3kiuFnkewLb7 D4JA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=QG0JtAA9McxoFBGugmDZRyJ/R7tB5ZjvaiVHtqkbgmc=; b=M1b/2q2Ed0iPBx4AmjCBSRHG23ZR6JXg8/J5vzD5lPKTnQ7eLzYhUN6CbcXxsp5UM/ KyHVq6YeCCwsoaDu9/bz6Yc3nspVtotKPb6Lsjo18dhPA/HwpQcY76kOvOcxwghw0SR2 fRmHA3JnABqZ+kuBGrCkfacBpOwnm/66KxL03zBCWlJk9cNRL2/N4gBwVol2z5X9jR17 TU1SUyeFuobqAImOsIIPU2aL1/YTcjETvu936izrxu9OkwBAnysWUznA5eEm/WY0NaJd sOqVWp99PhbsmaVogGIngyQeK4zh8ET9BkazYQGqd3rVnCRWpUsJ4AQKcaWPYyPIzIvE cwQQ==
X-Gm-Message-State: AOAM530eMk8xQtm5IfdJJLYiZmmOGZWtagH93ao8z5SV9LYrlox2iwIa F3qEZaf5P1t3PKnCFVmDPrwOKVA8TXQ=
X-Google-Smtp-Source: ABdhPJybyRFojao3TZS4JtOilM8DhfI/vuMso2BAMe30rCuZd0tnBJ/d63S5i9WbsvquAQ0ACDyQEA==
X-Received: by 2002:a0c:ef0f:: with SMTP id t15mr7419128qvr.35.1613707284203;  Thu, 18 Feb 2021 20:01:24 -0800 (PST)
Received: from [192.168.1.150] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id l128sm5409752qkf.68.2021.02.18.20.01.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Feb 2021 20:01:23 -0800 (PST)
To: Cyrus Daboo <cyrus@daboo.name>, Neil Jenkins <neilj@fastmailteam.com>, calsify@ietf.org
References: <e1e7222e-8c6e-40b3-a8cf-a45982acb00c@dogfood.fastmail.com> <f7a8cc4c-6ed7-4fff-a719-ac577ee407ab@cyrus.local>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <4955c116-ed6c-c06a-8dd4-c77aff9df349@gmail.com>
Date: Thu, 18 Feb 2021 23:01:22 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <f7a8cc4c-6ed7-4fff-a719-ac577ee407ab@cyrus.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/eLKPOahY-6KRANlCJEnxRv3uUVs>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Fri, 19 Feb 2021 04:01:32 -0000

On 2/18/21 22:23, Cyrus Daboo wrote:
> Hi Neil,
>
> --On Fri, 19 Feb 2021 14:06:57 +1100 Neil Jenkins 
> <neilj@fastmailteam.com> wrote:
>
>> Thanks for the background Cyrus. So just to confirm, the CUA is:
>>  * The target for sending iTIP messages. This may be a mailto URI for 
>> iMIP,
>> but may also be some other UI (which is essentially an opaque string to
>> clients) if you have some internal mechanism for delivering the 
>> messages.
>>  * A kind of UID that's consistent for the same participant across
>> different events.
>> Is that right?
>
> Yes.
>
>> Presuming so, then going back to the discussion of
>> translation between iCalendar and JSCalendar, I think this maps very
>> cleanly with the current spec:
>>  * The CUA maps to the sendTo property 
>> <https://tools.ietf.org/html/draft-
>> ietf-calext-jscalendar-32#page-36> of the Participant. There would be a
>> single value in the sendTo map: if it's a `mailto:` URI the value 
>> would be
>> under the key `imip`, otherwise it would be under the key `other`.
>
> Can't we just use the URI scheme to determine the method? Why do we 
> need 'imip' and 'other' nested keys? I realise we might one day have 
> e.g., multiple HTTP based scheduling protocols, but I feel like those 
> should all have some kind of unique scheme. (Note this is just a 
> question as to what drove the current design, not a request for a 
> change - I am cognizant of the fact that we spent many man-hours 
> debating the form of calendar user addresses for iSchedule without 
> getting anywhere).

I'd personally prefer that we don't get too specific about the method. 
Even if it looks like a regular recognizable email we might choose not 
to use iMip.

Could we just specify "schedule" rather than "imip". What if - e.g. - 
one E______e system wants to send a jsCalendar invite to another 
E______e system.


>
>>  * The EMAIL parameter value maps to the email
>> <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-32#page-36>
>> property of the Participant. Just as Cyrus says it's supposed to work in
>> iCalendar, this may be different to the iMIP address and is for sending
>> normal email to the participant, not iMIP messages.
>
> Yes.
>


From nobody Fri Feb 19 01:15:12 2021
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 681443A12C5 for <calsify@ietfa.amsl.com>; Fri, 19 Feb 2021 01:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_DNSWL_BLOCKED=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=Z83l+/qZ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=cLFsjzoY
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 4-Ra8_XZB_TQ for <calsify@ietfa.amsl.com>; Fri, 19 Feb 2021 01:15:09 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17FF63A12C3 for <calsify@ietf.org>; Fri, 19 Feb 2021 01:15:09 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6480F5C007E; Fri, 19 Feb 2021 04:15:08 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Fri, 19 Feb 2021 04:15:08 -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=Ov7uzMF RxdF/YAlhkkcTaq1kW2JUnKcMDzAccsxweOQ=; b=Z83l+/qZ+l1zjTNyPnn+QJp vZv2FRUCgs7ZZtMlmX0ixOuqCkqgBHv30DjMjZg8BtqC5Xpb1oFVuXjlKr6FDkty dfv1/z8OT6VN5GPVaKzsToELGRpX8/hdAWV7vddbT2WiQfB2N7XZMhP0uGQlxFu3 DTXGDxA0TgXuWXLctMR7uTgrbdn9WAchTcARsWXWfpeSWTKbxBcXqUjMCQC2dion aPjfoLQCv45thN3QlppTWGktKsjZLHXFe7+tI6bSckAwM0JViMDOhf2O74c/Viv6 IyT0hsVbucemNC8RwRz4CfYSzTYiiWwyqLjFd/ltjFoxX7MRq27c+cJ2OWpoINQ= =
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=Ov7uzM FRxdF/YAlhkkcTaq1kW2JUnKcMDzAccsxweOQ=; b=cLFsjzoYgag/3zoWE5tWZX pXWmi0hXkeEx1PlQGR0An7RYVcz1KGPqmET++9qLSQ41Bm9bbhGZNSP98x12lwnd /qWgeMJDEICuAt0XNssa9oLATimBv0gebCdYcY06ZrgYKCIiXCjOLEqU6gy/1F22 NQYugQNY1hnsDC0anc4pRuoDLIFTp4vT8PmDr4OM15zEcI2Uwgubvis1c0WVRf5p tg7CYeluR98UH3gd0XH1R+Y2H29EKP7aGmCIsqyAUVbHTJZqibKjJNySvZdWygVY d8fUy71x7x9UQuP6KJecET6DgFW1q3cBWSVJVX2iIJfgGEFJ7YpbjSjnr3/hSWCA ==
X-ME-Sender: <xms:m4EvYJIobWgEd6CVOQBu_UaGUnbZYQQrUWeYtDUbqgc8WN1XewBErQ> <xme:m4EvYFKOe9N302Q_YnvVy9OCVaii5gro7YrrfmrfnGS8ptBUwZ5Sjlccj5kWLOnaZ wXgd8lOFKDQOg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjeeigddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfpfgvihhl ucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomheqne cuggftrfgrthhtvghrnhepvedvtedvudelkefhgefhteeftedtlefhheefveffveelkedu tdduffeiveejvefhnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:m4EvYBudcVQzr_G6eGApr-pDJNJ0Dvfe7fQE_Xa7VHk5w3G4QJViuA> <xmx:m4EvYKaSTYvwCQZxHR-E40qj70glIipctWJmYCYuPDvS9jTHsZ-iQQ> <xmx:m4EvYAZZFGPqn18bKjeNS-L5iE5xw10S4lKSt3HuP1reeMG6q1MC3Q> <xmx:nIEvYG158O9P4iImxwc-xwkZB0vyQHQxmBvsflKB-G7c6oiJkLueAw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3E1B336005C; Fri, 19 Feb 2021 04:15:07 -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: <7f87de4f-5047-49f7-90e9-79eca4046a31@dogfood.fastmail.com>
In-Reply-To: <f7a8cc4c-6ed7-4fff-a719-ac577ee407ab@cyrus.local>
References: <e1e7222e-8c6e-40b3-a8cf-a45982acb00c@dogfood.fastmail.com> <f7a8cc4c-6ed7-4fff-a719-ac577ee407ab@cyrus.local>
Date: Fri, 19 Feb 2021 20:14:54 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: "Cyrus Daboo" <cyrus@daboo.name>, calsify@ietf.org
Content-Type: multipart/alternative; boundary=bc9ed706a2ca4b529243e19ac95f4967
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/KKL4WdTFAmHUoHNlWTkIPnNBDU8>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Fri, 19 Feb 2021 09:15:10 -0000

--bc9ed706a2ca4b529243e19ac95f4967
Content-Type: text/plain

On Fri, 19 Feb 2021, at 14:23, Cyrus Daboo wrote:
> Can't we just use the URI scheme to determine the method? Why do we need 
> 'imip' and 'other' nested keys?

The reason for nested keys is that you might have multiple. For example, at some point I'd like to look again at standardising an HTTP protocol we can use between servers rather than having to keep using iMIP forever. To invite someone external, you would still start by sending an iMIP email, as otherwise we still have the identity problem (we don't know where your calendar is, we just have your email). However, the invitation can include a JSCalendar version as well as the iCalendar version (for backwards compat), and the JSCalendar `replyTo` property can have entries for both imip and also the new protocol. If the invitee's calendar supports it, it can "upgrade" to the new protocol by replying with that instead of iMIP. If not, the iMIP option is still there.

As to why the values have keys instead of just an array of URIs where you just look at the scheme, it's mainly because it's more ergonomic: if my app just supports iMIP, I'll just look for an imip key. If I support multiple, I can quickly check for their presence in order of my preferred priority without having to scan. And of course we could end up with multiple HTTP protocols although I agree it would probably be better to give these unique schemes.

Neil.
--bc9ed706a2ca4b529243e19ac95f4967
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Fri, 19 Feb =
2021, at 14:23, Cyrus Daboo wrote:<br></div><blockquote type=3D"cite" id=
=3D"qt" style=3D""><div>Can't we just use the URI scheme to determine th=
e method? Why do we need&nbsp;<br></div><div>'imip' and 'other' nested k=
eys?<br></div></blockquote><div><br></div><div>The reason for nested key=
s is that you might have multiple. For example, at some point I'd like t=
o look again at standardising an HTTP protocol we can use between server=
s rather than having to keep using iMIP forever. To invite someone exter=
nal, you would still start by sending an iMIP email, as otherwise we sti=
ll have the identity problem (we don't know where your calendar is, we j=
ust have your email). However, the invitation can include a JSCalendar v=
ersion as well as the iCalendar version (for backwards compat), and the =
JSCalendar <code style=3D"border-top-color:rgb(204, 204, 204);border-top=
-style:solid;border-top-width:1px;border-right-color:rgb(204, 204, 204);=
border-right-style:solid;border-right-width:1px;border-bottom-color:rgb(=
204, 204, 204);border-bottom-style:solid;border-bottom-width:1px;border-=
left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:=
1px;border-image-outset:0;border-image-repeat:stretch;border-image-slice=
:100%;border-image-source:none;border-image-width:1;border-top-left-radi=
us:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border=
-bottom-left-radius:3px;background-color:rgb(246, 246, 246);background-p=
osition-x:0%;background-position-y:0%;background-repeat:repeat;backgroun=
d-attachment:scroll;background-image:none;background-size:auto;backgroun=
d-origin:padding-box;background-clip:border-box;font-family:menlo, conso=
las, monospace;font-size:90%;padding-top:1px;padding-right:3px;padding-b=
ottom:1px;padding-left:3px;">replyTo</code> property can have entries fo=
r both imip and also the new protocol. If the invitee's calendar support=
s it, it can "upgrade" to the new protocol by replying with that instead=
 of iMIP. If not, the iMIP option is still there.<br></div><div><br></di=
v><div>As to why the values have keys instead of just an array of URIs w=
here you just look at the scheme, it's mainly because it's more ergonomi=
c: if my app just supports iMIP, I'll just look for an imip key. If I su=
pport multiple, I can quickly check for their presence in order of my pr=
eferred priority without having to scan. And of course we could end up w=
ith multiple HTTP protocols although I agree it would probably be better=
 to give these unique schemes.<br></div><div><br></div><div>Neil.<br></d=
iv></body></html>
--bc9ed706a2ca4b529243e19ac95f4967--


From nobody Fri Feb 19 01:18:56 2021
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 6A6BF3A129F for <calsify@ietfa.amsl.com>; Fri, 19 Feb 2021 01:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_DNSWL_BLOCKED=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=ewDlvy2A; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=obsWAOps
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 vdZxD8_D0-in for <calsify@ietfa.amsl.com>; Fri, 19 Feb 2021 01:18:53 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77B0B3A12D1 for <calsify@ietf.org>; Fri, 19 Feb 2021 01:18:53 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 648245C00DE; Fri, 19 Feb 2021 04:18:51 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Fri, 19 Feb 2021 04:18:51 -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=gbaq7pI qTXQzmyvac0i3+3MOqpA0A4xziX5wqGw9yhE=; b=ewDlvy2A9XK0yPEmRoE6K6V /OqkdClRkbIAirjKOfDaHyDQ0HsG0LuCEPqMN4veWtXmFO4gnDchM3MNRp/Ue3vI wiKqYrb61pFGZ0GvTXavsGzLgsyE8gu3BsLeJ3i+HqgbSq+KFRNGx0HdSZ1eVOA4 tgVMVnmkSxC8VuLQOeBeh6toOI8+3Pv4T+6eMTjamjp4EtCzK7RlU6xMISn/ev7a YInRChWKsiaIM5uIYCQ3+KGg/7lq9T8TZafGZ6s37WJIMBYRbZTiNxKpRwORbPye nWJKZudc/mWFT2I4QZAA7L08Nb6pmVZgWjyLnKMPOarNm5q6MUMbZt4diMo+q0Q= =
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=gbaq7p IqTXQzmyvac0i3+3MOqpA0A4xziX5wqGw9yhE=; b=obsWAOpsnqGLXvSlFDhWkN RhilZ0rL6ZfQ/odkddEs5tel9vmZpGiGpfoJothRirnVf9lFeHbiNpjjYM01rgcO JCznD8lRZ/9hg8zr7b3ZyqWX6NC6fpi5tJFJgFwEMmQobFmrsBqpspXdHwZ0Qk4E vjJ5LSwao12SGcMbZPpz6KGKQMXahczMSOlYU3XOSG+x1WUNI1iPgk43lhm8A/58 MoBQ5TVRd2nmCOj7eZ7q8lh44wY3QrpuPglTWRAcH5lIEgUxJ+TNr+b3xPwmT/W8 TwNu9ICKTFePpFAra2CZo9yKIlBVhtRD7fI+6eqIzUkLkoBWIQlBeJASsL4dEFbQ ==
X-ME-Sender: <xms:eoIvYPqcj3WHVW0yot5DZOR2t3qX2rAh67PX-sArlHRFKLE0_pZh9A> <xme:eoIvYJqOnN-suvBajSIYIo8H2CpW1TMlDlr-NdT-YJ7ryiamDRmstTxHxFD2ky-_W Z_oLe34DNxhHg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjeeigddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfpfgvihhl ucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomheqne cuggftrfgrthhtvghrnhepvedvtedvudelkefhgefhteeftedtlefhheefveffveelkedu tdduffeiveejvefhnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilh hfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:eoIvYMNrH9d8c8xdXWComKX4yLnFllrrX0B5HIyslybwHKwaPM9foQ> <xmx:eoIvYC6A2YkWfHDAocluFqkkzdRVawMR_iXlGpz_3IChWHw4On3J4Q> <xmx:eoIvYO6rcGXULrIfk5aQngtq8c23KSb6mYe5n-RNztnKbPMqIL-Esg> <xmx:e4IvYDgedxcn5leVIUQwos4C6ha9VK9Ww2xnoXjKEiBWpw9rjuqEEA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4303236005C; Fri, 19 Feb 2021 04:18:50 -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: <e78529f8-22b4-49e3-8707-ee4ecfefb0ca@dogfood.fastmail.com>
In-Reply-To: <4955c116-ed6c-c06a-8dd4-c77aff9df349@gmail.com>
References: <e1e7222e-8c6e-40b3-a8cf-a45982acb00c@dogfood.fastmail.com> <f7a8cc4c-6ed7-4fff-a719-ac577ee407ab@cyrus.local> <4955c116-ed6c-c06a-8dd4-c77aff9df349@gmail.com>
Date: Fri, 19 Feb 2021 20:18:49 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: "Michael Douglass" <mikeadouglass@gmail.com>, "Cyrus Daboo" <cyrus@daboo.name>, calsify@ietf.org
Content-Type: multipart/alternative; boundary=bb66e057f1dd4a38a8a8976f632076f2
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/N9ldc8tDoHwr-R0JsOtzIaKAO10>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
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: Fri, 19 Feb 2021 09:18:55 -0000

--bb66e057f1dd4a38a8a8976f632076f2
Content-Type: text/plain

On Fri, 19 Feb 2021, at 15:01, Michael Douglass wrote:
> I'd personally prefer that we don't get too specific about the method. 
> Even if it looks like a regular recognizable email we might choose not 
> to use iMip.

I'm not quite sure what you mean by this. The keys are advertising what methods you support. You definitely need this, because if you are sending an invitation across federated systems, the other side has no other way to know what protocols you support for exchanging scheduling messages. If you're supplying an email that's not for iMIP, you would not include an `imip` property in the participant's `sendTo`; you would just put it in the `email` property, as discussed earlier in the thread.

Neil.
--bb66e057f1dd4a38a8a8976f632076f2
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Fri, 19 Feb =
2021, at 15:01, Michael Douglass wrote:<br></div><blockquote type=3D"cit=
e" id=3D"qt" style=3D""><div>I'd personally prefer that we don't get too=
 specific about the method.&nbsp;<br></div><div>Even if it looks like a =
regular recognizable email we might choose not&nbsp;<br></div><div>to us=
e iMip.<br></div></blockquote><div><br></div><div>I'm not quite sure wha=
t you mean by this. The keys are advertising what methods you support. Y=
ou definitely need this, because if you are sending an invitation across=
 federated systems, the other side has no other way to know what protoco=
ls you support for exchanging scheduling messages. If you're supplying a=
n email that's not for iMIP, you would not include an <code style=3D"bor=
der-top-color:rgb(204, 204, 204);border-top-style:solid;border-top-width=
:1px;border-right-color:rgb(204, 204, 204);border-right-style:solid;bord=
er-right-width:1px;border-bottom-color:rgb(204, 204, 204);border-bottom-=
style:solid;border-bottom-width:1px;border-left-color:rgb(204, 204, 204)=
;border-left-style:solid;border-left-width:1px;border-image-outset:0;bor=
der-image-repeat:stretch;border-image-slice:100%;border-image-source:non=
e;border-image-width:1;border-top-left-radius:3px;border-top-right-radiu=
s:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;backg=
round-color:rgb(246, 246, 246);background-position-x:0%;background-posit=
ion-y:0%;background-repeat:repeat;background-attachment:scroll;backgroun=
d-image:none;background-size:auto;background-origin:padding-box;backgrou=
nd-clip:border-box;font-family:menlo, consolas, monospace;font-size:90%;=
padding-top:1px;padding-right:3px;padding-bottom:1px;padding-left:3px;">=
imip</code> property in the participant's <code style=3D"border-top-colo=
r:rgb(204, 204, 204);border-top-style:solid;border-top-width:1px;border-=
right-color:rgb(204, 204, 204);border-right-style:solid;border-right-wid=
th:1px;border-bottom-color:rgb(204, 204, 204);border-bottom-style:solid;=
border-bottom-width:1px;border-left-color:rgb(204, 204, 204);border-left=
-style:solid;border-left-width:1px;border-image-outset:0;border-image-re=
peat:stretch;border-image-slice:100%;border-image-source:none;border-ima=
ge-width:1;border-top-left-radius:3px;border-top-right-radius:3px;border=
-bottom-right-radius:3px;border-bottom-left-radius:3px;background-color:=
rgb(246, 246, 246);background-position-x:0%;background-position-y:0%;bac=
kground-repeat:repeat;background-attachment:scroll;background-image:none=
;background-size:auto;background-origin:padding-box;background-clip:bord=
er-box;font-family:menlo, consolas, monospace;font-size:90%;padding-top:=
1px;padding-right:3px;padding-bottom:1px;padding-left:3px;">sendTo</code=
>; you would just put it in the <code style=3D"border-top-color:rgb(204,=
 204, 204);border-top-style:solid;border-top-width:1px;border-right-colo=
r:rgb(204, 204, 204);border-right-style:solid;border-right-width:1px;bor=
der-bottom-color:rgb(204, 204, 204);border-bottom-style:solid;border-bot=
tom-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:sol=
id;border-left-width:1px;border-image-outset:0;border-image-repeat:stret=
ch;border-image-slice:100%;border-image-source:none;border-image-width:1=
;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-ri=
ght-radius:3px;border-bottom-left-radius:3px;background-color:rgb(246, 2=
46, 246);background-position-x:0%;background-position-y:0%;background-re=
peat:repeat;background-attachment:scroll;background-image:none;backgroun=
d-size:auto;background-origin:padding-box;background-clip:border-box;fon=
t-family:menlo, consolas, monospace;font-size:90%;padding-top:1px;paddin=
g-right:3px;padding-bottom:1px;padding-left:3px;">email</code> property,=
 as discussed earlier in the thread.<br></div><div><br></div><div>Neil.<=
br></div></body></html>
--bb66e057f1dd4a38a8a8976f632076f2--


From nobody Sat Feb 20 21:53:36 2021
Return-Path: <mikeadouglass@gmail.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 3612C3A14D0 for <calsify@ietfa.amsl.com>; Sat, 20 Feb 2021 21:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kBtB7Vo0gwbr for <calsify@ietfa.amsl.com>; Sat, 20 Feb 2021 21:53:34 -0800 (PST)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 EEFA13A14CD for <calsify@ietf.org>; Sat, 20 Feb 2021 21:53:33 -0800 (PST)
Received: by mail-qt1-x834.google.com with SMTP id e15so7088593qte.9 for <calsify@ietf.org>; Sat, 20 Feb 2021 21:53:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=czj/GcE0nHEFx62CT9WcG6n1msBlgccI0qW2CrdS98I=; b=cwNdKRT7XpSjapXuTWQDoB4D6pxGizYak1re3HdiV2f7Cw8i6kEAChcoO3Ga44Vt/7 n1uijvW+/+9tOJ7Q34Jq8fffnjng3QQRm7UrDLpflbF2FwTZZnc7cmiZajDvU0qUuUlk 6xJvJWcQgPNDvwwSnzkP6wnYJyqplE+Ke1Sls34hxWS10thxyhWegQ6xNjLvy2EM8rZj lZU5+6XL+pe5D/qdBnfDyCLvWQ9PNkWhIkkDziqV1o9z3i6f7PCKp9OJAhClN0qi8xVl KDhES3fOb0DkkROK5ZHR55WsqUBAp7WDjG2sWeZwIpzqhh4IlkXZTNHhG+0Xy1VosR8S fL2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=czj/GcE0nHEFx62CT9WcG6n1msBlgccI0qW2CrdS98I=; b=bgNvO0swXaic4SGrFunk4ZtwsE0csUo8zCZeRzdB5pLhZx1Bw0ozK4kitRVVZl/0SG 2e6uf8+jSxORZM21rVgMTK2rKndi3GnEwkaHFEd54EK8cNIhFEJGFzj66epWCTM2Lcxx CXAbOVXS9VWDTO3z4lefug+976u8tccoYzbpIkSO0iEaqfQGVjFPRM9Rrirm/rDZLTZF xb7So+CAut3Czrub0bdqlwpcuDF1s6clrKrqDoOfw9Hf+UXFlJG+SHnNsmBBBleGj9gb e5MfYadEw/Who72qFP0r1ZKuFNs2x1BKp4b6VYFVeaH4LTFs3sjGNKpXdkVolFDCVF2N GVLw==
X-Gm-Message-State: AOAM533jgGn4shIvdwgoFdDm5K4to/LjbqLreieioyXUVKCNkrL1gcFw ZGi3nENCssbo5JQOeC1MbxUHjAcb+0A=
X-Google-Smtp-Source: ABdhPJz9QQNawo955ehKR1BEl9vNw55QVQZGbLmP27DpFmEbT2YwnS25zT25PU/D98IleYeubHn89A==
X-Received: by 2002:aed:2ae6:: with SMTP id t93mr700182qtd.360.1613886812455;  Sat, 20 Feb 2021 21:53:32 -0800 (PST)
Received: from [192.168.1.150] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id l6sm9727632qki.25.2021.02.20.21.53.31 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 20 Feb 2021 21:53:31 -0800 (PST)
To: Calsify <calsify@ietf.org>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <4320dbab-8730-2d0a-0e2e-8db28029c399@gmail.com>
Date: Sun, 21 Feb 2021 00:53:30 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/NYS5c5FnwPXDHjMbq32i_-r0mgo>
Subject: [calsify] JsCalendar @type values
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: Sun, 21 Feb 2021 05:53:35 -0000

Just for consistency - why do we have values of "Participant" and 
"Location" - but "jsevent" and "jsgroup". Wouldn't "Event" and "Group" 
be better?


From nobody Sat Feb 20 22:03:33 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE3E23A14E9; Sat, 20 Feb 2021 22:03:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <161388740091.773.11719206303450142228@ietfa.amsl.com>
Date: Sat, 20 Feb 2021 22:03:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/tnsPf-XpXa9wKcwg9jRaEp1EMmA>
Subject: [calsify] I-D Action: draft-ietf-calext-jscalendar-icalendar-04.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 21 Feb 2021 06:03:21 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : JSCalendar: Converting from and to iCalendar
        Authors         : Neil Jenkins
                          Robert Stepanek
                          Michael Douglass
	Filename        : draft-ietf-calext-jscalendar-icalendar-04.txt
	Pages           : 58
	Date            : 2021-02-20

Abstract:
   This document provides the required methods for converting JSCalendar
   from and to iCalendar.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-jscalendar-icalendar/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-calext-jscalendar-icalendar-04
https://datatracker.ietf.org/doc/html/draft-ietf-calext-jscalendar-icalendar-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-jscalendar-icalendar-04


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/



From nobody Mon Feb 22 04:34:03 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1B63A0A27; Mon, 22 Feb 2021 04:34:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>, mglt.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <161399724141.22463.7074373932923061990@ietfa.amsl.com>
Date: Mon, 22 Feb 2021 04:34:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/XrXOeCtHog-B73TEn4l1afQOwME>
Subject: [calsify] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-calext-valarm-extensions-05=3A_=28with_COMMENT=29?=
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Feb 2021 12:34:02 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-calext-valarm-extensions-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for this document, it is easy to read and the "snooze" and "ack"
extensions will be indeed useful.

During my IESG review, I found nothing worth mentioning.

Regards

-éric




From nobody Mon Feb 22 10:03:51 2021
Return-Path: <dilyan.palauzov@aegee.org>
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 EED033A1E9E for <calsify@ietfa.amsl.com>; Mon, 22 Feb 2021 10:03:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
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 OuRLyFGXQhR1 for <calsify@ietfa.amsl.com>; Mon, 22 Feb 2021 10:03:47 -0800 (PST)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DD653A1E95 for <calsify@ietf.org>; Mon, 22 Feb 2021 10:03:46 -0800 (PST)
Authentication-Results: mail.aegee.org/11MI3UkC1697630; auth=pass (LOGIN) smtp.auth=didopalauzov@aegee.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1614017023; i=dkim+MSA-tls@aegee.org; bh=g62RPS1qBH8dFYYCSQNsW3Tk5GQHZzf7+ArOIWQQHjA=; h=Subject:From:To:Date:In-Reply-To:References; b=CK/Dz3Crf41rdPnZjuLvCGGFhR1/BafUpyyBsTfi/DGYI9SVKZUQZXverprButT0r eYNECAOkrh3nlFTyGYrcVHZsNowDNgknsIp5qmA736mhVYfa0YME9ZxOUKtb+AN2Rq g0bg4FRHwvmBHaO+C0Q4uVEPwDksJtPSZXNmUtzbf0eJi9ozogJ5nniUcSw38S6H0A OJIfVQ9Jp1EoZ011eSN6lKJBHMi2i8LNOBnRMfeNZf6g32QfCmyb+knnlFogJcdBTn 65jyATn1pcHUSmbUB8pI097M8PU3oAKq7jCEGfoT9cF3+zZnnQFsGYDJtgdJgEyED3 KINqDyEyhWlwXPor2fXrpspxNadP37TZ9vkc2cUACx7UiZtW4DNwvEwqIPflBbMoYn pkaGN1PWqDSEQgxN3mBfA2Sf+iMCdMTBQ0nIt+hbtCfB9xPzcW3/PtocNyMEdKtVKd 1MqypNJxtTy8xSTDZk9cwOQess0JLPARv+Ws19L+GO88fzx44IVxQ1esTEQOWTfEGX P2cHG7dWlkigPcw/azIQ4BXY4htJ/9qlWEsIujGIUPcgvibDiLeVP+0j463OObwyPJ YsqbI0uh2oNxfBCqActfsccFIg5p2aehAm/wTsTK0H8GptHl2Wvnyc8aWTcHTJgU9c L67LcNDpshFKYT7UgsPIlFT0=
Authentication-Results: mail.aegee.org/11MI3UkC1697630; dkim=none
Received: from [192.168.0.125] (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 11MI3UkC1697630 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <calsify@ietf.org>; Mon, 22 Feb 2021 18:03:34 GMT
Message-ID: <d76f6f845578ef8840daf75223908eae2a9f5bd9.camel@aegee.org>
From: =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= <dilyan.palauzov@aegee.org>
To: calsify@ietf.org
Date: Mon, 22 Feb 2021 20:03:27 +0200
In-Reply-To: <161221753429.6318.13830461705241642805@ietfa.amsl.com>
References: <161221753429.6318.13830461705241642805@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.39.3 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/ZyLY94NWus7WRYCaS417_FohWrQ>
Subject: Re: [calsify] I-D Action: draft-ietf-calext-subscription-upgrade-03.txt
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, 22 Feb 2021 18:03:50 -0000

Hello,

my messages to calsify@ietf.org about draft-ietf-calext-subscription-
upgrade from 6th October 2020 are not tackled yet.

These were also not addressed in draft-ietf-calext-subscription-
upgrade-03 .

I am against introducing STATUS:DELETED, as I do not see how it dяffers
from STATUS:CANCELLED.

About draft-ietf-calext-subscription-upgrade-03:

Section 2 Introduction:

>    The only available option for updating that resource is the usual
HTTP polling of cached resources using Etags.

Is Last-Modified interchangeable with ETags? 

> The use of subscription upgtafe may help reduce 

typo.

4.2.  Deletions
What purpose does delivering skeletons, empty deleted items?

> The receiving client is free to remove the entity or update it's
STATUS property.
It's → Its.

5.1.  Redefined Status property
This section is not adjusted for the DELETED value: the included
examples have no added value.

8.2.  subscribe-caldav
> for example to determine if sync-report is supported.
Please spell DAV:sync-collection report, as the report is not called
literally “sync-report”.

> The URL MAY include some form of token to allow write access to the
targeted collection.  The client must check it's permissions to
determine whether or not it has been granted write access.

I do not get this “token may be included” part.  Can you provide
example what this is supposed to mean?

It's → its.

8.4.  subscribe-webdav-sync
Does it require authentication or not?  What is the opposite option?

I propose:
- determine using OPTIONS call, whether WebDAV/CalDAV are supported
- comminucate over GET whether authentication is
necessary/optional/disabled. 

Greetings
  Дилян

On Mon, 2021-02-01 at 14:12 -0800, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Calendaring Extensions WG of the IETF.
> 
>         Title           : Calendar subscription upgrades
>         Author          : Michael Douglass
>         Filename        : draft-ietf-calext-subscription-upgrade-03.txt
>         Pages           : 15
>         Date            : 2021-02-01
> 
> Abstract:
>    This specification updates [RFC5545] to add the value DELETED to the
>    STATUS property.
> 
>    This specification also updates [RFC7240] to add the subscribe-
>    enhanced-get and limit preferences.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-calext-subscription-upgrade/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-calext-subscription-upgrade-03.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-subscription-upgrade-03
> 
> 
> 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/
> 
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify



From nobody Tue Feb 23 19:49:58 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C01C13A0927; Tue, 23 Feb 2021 19:49:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>, mglt.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <161413859617.6944.7507348820702497356@ietfa.amsl.com>
Date: Tue, 23 Feb 2021 19:49:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/hmrzkleimdfHP9lbIc32050YIMI>
Subject: [calsify] Benjamin Kaduk's Discuss on draft-ietf-calext-valarm-extensions-05: (with DISCUSS)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Feb 2021 03:49:57 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-calext-valarm-extensions-05: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Please update to reflect the changes made in draft-ietf-calext-eventpub-extensions-17
(e.g., there is no longer STRUCTURED-LOCATION and VLOCATION plays a similar
role).






From nobody Tue Feb 23 20:16:54 2021
Return-Path: <barryleiba@gmail.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 DA7573A0C49; Tue, 23 Feb 2021 20:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 iHJatiZ8X80t; Tue, 23 Feb 2021 20:16:51 -0800 (PST)
Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (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 28DBD3A0C5C; Tue, 23 Feb 2021 20:16:51 -0800 (PST)
Received: by mail-lf1-f45.google.com with SMTP id h125so968759lfd.7; Tue, 23 Feb 2021 20:16:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QmOacBzSgzRs9RRpLaN5z267x0fXlOzlsl5W3z4vakE=; b=hYsn1wy11VQ65e+WkZ/FXuv1xTlAPwgZmYifkqAkF4iOtvid+NnQBPW6BXyyl5brqU d3QHiV9Vvb6atnoEv1KsC/D5tHLiwdcxTKOnZUqy6kZjz/TdE43W+1G88lzLr4Dg9n8P NV01TW9vSQHDQOyo5jGk7bELJnqFglxYzW48U1+viSNJSrAiJ4dwQtYOfKazshpj7HbI WdmrK6mb8i3wPGjv64l8usbEznOmGvv7D8E3SkBboEC2loXby3ns9e4JhvQTwqPv3RFg qiZTFee4417niVBNRwSXMUBIY3pJCKDldOXaIx66aDVgEgSfOudS3sejRMdtnmlFfkku +4jA==
X-Gm-Message-State: AOAM532RBq/wbTNC8eBaostbTv57lsd5YXPbpvwAzheDpe5FYJ4BXNZq midBRMiwXZOxtjREvCqfGEFpMYL12S6hR0FoLy8=
X-Google-Smtp-Source: ABdhPJzJgL/4u4gTeHVDSyth8bNVbRk9ZFu5gvypcvCCX43unTk4mJQcWMSTqa1E9CcBQLwluBNg8+0KWPqpL0xaaJM=
X-Received: by 2002:a05:6512:31c1:: with SMTP id j1mr19121420lfe.313.1614140209018;  Tue, 23 Feb 2021 20:16:49 -0800 (PST)
MIME-Version: 1.0
References: <161413859617.6944.7507348820702497356@ietfa.amsl.com>
In-Reply-To: <161413859617.6944.7507348820702497356@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 23 Feb 2021 23:16:38 -0500
Message-ID: <CALaySJLzgDKb1L-JSqoFwk3sJrZ3UprDWAxFq-gVOYrzev=KfA@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, Bron Gondwana <brong@fastmailteam.com>,  Daniel Migault <mglt.ietf@gmail.com>, calsify@ietf.org, calext-chairs@ietf.org, draft-ietf-calext-valarm-extensions@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/v0BrSjs-VrBem4RcyKFYT5Tty38>
Subject: Re: [calsify] Benjamin Kaduk's Discuss on draft-ietf-calext-valarm-extensions-05: (with DISCUSS)
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: Wed, 24 Feb 2021 04:16:53 -0000

> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Please update to reflect the changes made in draft-ietf-calext-eventpub-extensions-17
> (e.g., there is no longer STRUCTURED-LOCATION and VLOCATION plays a similar
> role).

Indeed: this change came up in the IESG Evaluation of
eventpub-extensions, and was made shortly before valarm-extensions-04
was posted.  And I missed catching that issue when I moved
valarm-extensions into IESG Evaluation.

This should not be a big thing to fix in valarm-extensions, as the
real meat of VLOCATION is in eventpub-extensions.

Barry


From nobody Wed Feb 24 05:00:38 2021
Return-Path: <murch@fastmail.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 129ED3A155C; Wed, 24 Feb 2021 05:00:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-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=fastmail.com header.b=SAmLx/5k; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=R56KX0V/
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 pknT0Xv4k6pk; Wed, 24 Feb 2021 05:00:35 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 711903A155A; Wed, 24 Feb 2021 05:00:35 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 359D65C018B; Wed, 24 Feb 2021 08:00:32 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 24 Feb 2021 08:00:32 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=1 AojYa8XB4Kbge/x5ITCpZQyGOnjySjxOAHN7oQ76gM=; b=SAmLx/5knokGfqhio oE2MIbRUJmszF+4gCnAAtSjDyDk43m9JQaTiMkPi3f02bf15x/HaFOCl3nRTwkaJ Wgk2P0CjWSSBiT44yLD+zZ94JKY++s4WaFG4eBydUL0nCumSheIiMvehm7LyAWyd I9PKR9Hy0H5WAxHjtE+2XmLl8+5+IgJzljVZ5hxwo8B03plA5sKA8gJdLUVZfuD4 TnAhH5ztLXv57vIJ7UZsAub/TKU9WgRcVfpoaceC21Jbp5l2IgGpMVw+Y30J4ZPJ jeP0AOn2twNsO6/Z1DmlqcS6AGBh6+WJqDD9HLV+1SHi4VlUYr06LNaj7FGMaLSc SYMUA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=1AojYa8XB4Kbge/x5ITCpZQyGOnjySjxOAHN7oQ76 gM=; b=R56KX0V/sYRJOH0HwT3+Yn+OIiM3Xedr1L/t5S9RaBi4bGtBWjC/q7gsg 48cg5g3eLybDNK76iwUwLGq5OLA9kALB9yZPVpk05J1Skc8DpIuPkrtGkM9RDbbp A4K9lXX1yNnhWOT21C4cI/Ha5Ge6ZsFiy0v3tSB4JtTeEz0D9qY4qyV3QSU/9c/6 NL8DAjRv5V3dzD+hxr5KWVfJGLYkVBu3VorqmAEB8iu24g24lMoVYaEWEFkeCelb NT0XNgM2lZvvYB9Pal7qrVkR6mNa2pxDJB5QmnQfxDGh6RH0ntDruFJZtX6uIli5 ggglXeav8QOMXfiPOOnDfjwyDtpSw==
X-ME-Sender: <xms:7002YObwSlHhw1zABoj1M_ViVjSXZZXy6i2ifp0s00TSD2HvikMmow> <xme:7002YKNDGfg23aaZHCMWIX91eY8P97UItxvpm5CKgPJ6rVuXVXV1abSeyz4o2BaLO -RWjFA8K4esnw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeejgdeghecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpedvueetudegieffieetvdfhiedutedvgeejkeekudetvddvvdduteejvefg hfdvkeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeejgedrjeejrdekhedrvd ehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm uhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:7002YKTvm6dOGJsvb2_72cePa3aPS_26z61Hx515KrM2rSPhR7iNnw> <xmx:7002YF5lETXZM0YukEM4Q7DeC8Iqky61-d0Yx5tTl77Mj7q89JoK4A> <xmx:7002YNZE3todDT6rnPaSqLWLYj0pXqpDnNs40_Z9iw2b3gedIRaMdA> <xmx:8E02YCiOxh2KvoEZB81WQRFFnd0HpVuovql46TYEMx0Hxo10QF74qw>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 3306D24005A; Wed, 24 Feb 2021 08:00:31 -0500 (EST)
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>
References: <161413859617.6944.7507348820702497356@ietfa.amsl.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <8a461d03-a1a8-269e-bd9c-46b56d709003@fastmail.com>
Date: Wed, 24 Feb 2021 08:00:29 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <161413859617.6944.7507348820702497356@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/wfbY_o9JGfxYwzr4KQWQfrvdpbo>
Subject: Re: [calsify] Benjamin Kaduk's Discuss on draft-ietf-calext-valarm-extensions-05: (with DISCUSS)
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: Wed, 24 Feb 2021 13:00:37 -0000

Hi Benjamin,

Thanks for catching this.  I will address this as soon as the blackout 
on submitting drafts has been lifted.


On 2/23/21 10:49 PM, Benjamin Kaduk via Datatracker wrote:
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-calext-valarm-extensions-05: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Please update to reflect the changes made in draft-ietf-calext-eventpub-extensions-17
> (e.g., there is no longer STRUCTURED-LOCATION and VLOCATION plays a similar
> role).
>
>
>
>
>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Wed Feb 24 09:38:16 2021
Return-Path: <murch@fastmail.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 3FFF23A184A; Wed, 24 Feb 2021 09:38:14 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-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=fastmail.com header.b=gi7yv6ss; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dWiKsseK
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 xJ4tKSV3Krz7; Wed, 24 Feb 2021 09:38:12 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.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 7D5F13A1848; Wed, 24 Feb 2021 09:38:12 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 4D47195D; Wed, 24 Feb 2021 12:38:11 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 24 Feb 2021 12:38:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:from:to:cc:references:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=IQj9pXKm9fhgH5b7lEVyBX56V8N Ca5wDcETZJpaTm24=; b=gi7yv6ss52YAqkBVM71yK+6iYBmiO6lxyly6xC8qLXP iT5KhftWm9H4XbWzj4xQkqYlH/WRooxK2wIZ9VRcBAM5KvPZ5VSCaA3wkuDfZyfw 1De1V5djNMcVEpSCE8gtY9GTVDgXNmiOAiu5pF3nlttUrM2SBG8s/eTJ68TIEbin jSidYL6uWJgWwi0X6SQ1TWM+O7ntg70zZ7sSTUB++kJmabULUYlCyUoQptMuAOUt 05ms4oP3qePJFyC/Y1LmJOmmQ/R5xJDeJtPC0kADxnX07Ra843DGJX9bmVc5ugoZ a4CRbnhrFILkvaILoE7rLk0edH1d4Oa7ylxqyjUBZ/w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=IQj9pX Km9fhgH5b7lEVyBX56V8NCa5wDcETZJpaTm24=; b=dWiKsseKiEn2jP7GLl1VGO BQpPZhVW6kxg+qYVzcJ6devcy6HetLeAWoC+Qpmy+ToLtc/oGTDmAVC0ISeX6gNj aFTJX61PmDqFqnnqBLtkr9dMywGAxcCpxZ1MqLFpXa5p24+qB5WalW8qGNlV3Ml4 SzG4ayi7HtNK9td6rs3xBAmI2NVWbjfKWhqSsp+bZWthRUaswBejSEuOxdornu13 CBENZeLSnQluxpQpgA8oEP8u1N6ZEMj56h8dWb+C4gaKKmqOcEZCkwKvv3j8NOco eZmJJeuRret+PdmqIXEjstIVJr4U/YTvaIN0oYESm7thuZN6xdfxT4ljVVrSMk7Q ==
X-ME-Sender: <xms:Ao82YN8iqmJKaV9xkCtmCYV1a1SrERGohKvRttBCU7M_5t7LcoxIxQ> <xme:Ao82YBtPT63FJTJHKnej6b1Yutb6M_vQ-CUxVQYeq5W0qA_KR70K2Tmy_6dolWM7D QSDYyg0Ab7T6w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeejgddutdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffhvfhfkffffgggjggtsegrtderredtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpedvfeeujeffudektdffhfejjedtffdujefhvdekueejffejveegkeffleeg gfdvvdenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeejgedrjeejrdekhedrvd ehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm uhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:Ao82YLBIG1qpP5wCp56uIBv-57PKzuGvVrnzoKbH7duknLNnYAuuTw> <xmx:Ao82YBd_D8hGLVoEeX9bmAB5CRnKPTBEIxxoa8sZGqZGGAntBHab1g> <xmx:Ao82YCOLP3LmjS-DOmsyr9HVZDDbHtOzNuhf2O-Njbk1aDwIhqahQw> <xmx:Ao82YE22mCwBM3yV6zjtUI8riDbO6P2FoNj07K-wl9sX8xdYq3G-Zg>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 6590E240054; Wed, 24 Feb 2021 12:38:10 -0500 (EST)
From: Ken Murchison <murch@fastmail.com>
To: Calsify <calsify@ietf.org>
Cc: calext-chairs@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>
References: <161413859617.6944.7507348820702497356@ietfa.amsl.com> <8a461d03-a1a8-269e-bd9c-46b56d709003@fastmail.com>
Message-ID: <e663395a-bfb5-2b0f-0108-b97c9b9dfab2@fastmail.com>
Date: Wed, 24 Feb 2021 12:38:09 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <8a461d03-a1a8-269e-bd9c-46b56d709003@fastmail.com>
Content-Type: multipart/alternative; boundary="------------BE9DEC25ADC395F552A9EC11"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/RNOpFOLu4HzwTIRSdoblkcsONZc>
Subject: Re: [calsify] Benjamin Kaduk's Discuss on draft-ietf-calext-valarm-extensions-05: (with DISCUSS)
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: Wed, 24 Feb 2021 17:38:14 -0000

This is a multi-part message in MIME format.
--------------BE9DEC25ADC395F552A9EC11
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

All,

So, Mike Douglass and I were just discussing this and we came to the 
conclusion that the best place to put the geographic coordinates is 
going to be in a URL property rather than a GEO property, because the 
latter only encodes latitude and longitude. So, the proximity alarm 
would look something like this:

BEGIN:VALARM
UID:77D80D14-906B-4257-963F-85B1E734DBB6
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
ACTION:DISPLAY
DESCRIPTION:Remember to buy milk
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
PROXIMITY:DEPART
BEGIN:VLOCATION
UID:123456-abcdef-98765432
NAME:Office
URL:geo:40.443,-79.945;u=10
END:VLOCATION
END:VALARM

Does anyone have any objections, or other suggestions?


On 2/24/21 8:00 AM, Ken Murchison wrote:
> Hi Benjamin,
>
> Thanks for catching this.  I will address this as soon as the blackout 
> on submitting drafts has been lifted.
>
>
> On 2/23/21 10:49 PM, Benjamin Kaduk via Datatracker wrote:
>> Benjamin Kaduk has entered the following ballot position for
>> draft-ietf-calext-valarm-extensions-05: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to 
>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> Please update to reflect the changes made in 
>> draft-ietf-calext-eventpub-extensions-17
>> (e.g., there is no longer STRUCTURED-LOCATION and VLOCATION plays a 
>> similar
>> role).
>>
>>
>>
>>
>>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------BE9DEC25ADC395F552A9EC11
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>All,</p>
    <p>So, Mike Douglass and I were just discussing this and we came to
      the conclusion that the best place to put the geographic
      coordinates is going to be in a URL property rather than a GEO
      property, because the latter only encodes latitude and longitude. 
      So, the proximity alarm would look something like this:</p>
    <pre>BEGIN:VALARM
UID:77D80D14-906B-4257-963F-85B1E734DBB6
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
ACTION:DISPLAY
DESCRIPTION:Remember to buy milk
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
PROXIMITY:DEPART
BEGIN:VLOCATION
UID:123456-abcdef-98765432
NAME:Office
URL:geo:40.443,-79.945;u=10
END:VLOCATION
END:VALARM</pre>
    <p>Does anyone have any objections, or other suggestions?<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2/24/21 8:00 AM, Ken Murchison
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:8a461d03-a1a8-269e-bd9c-46b56d709003@fastmail.com">Hi
      Benjamin,
      <br>
      <br>
      Thanks for catching this.  I will address this as soon as the
      blackout on submitting drafts has been lifted.
      <br>
      <br>
      <br>
      On 2/23/21 10:49 PM, Benjamin Kaduk via Datatracker wrote:
      <br>
      <blockquote type="cite">Benjamin Kaduk has entered the following
        ballot position for
        <br>
        draft-ietf-calext-valarm-extensions-05: Discuss
        <br>
        <br>
        When responding, please keep the subject line intact and reply
        to all
        <br>
        email addresses included in the To and CC lines. (Feel free to
        cut this
        <br>
        introductory paragraph, however.)
        <br>
        <br>
        <br>
        Please refer to
        <a class="moz-txt-link-freetext" href="https://www.ietf.org/iesg/statement/discuss-criteria.html">https://www.ietf.org/iesg/statement/discuss-criteria.html</a>
        <br>
        for more information about IESG DISCUSS and COMMENT positions.
        <br>
        <br>
        <br>
        The document, along with other ballot positions, can be found
        here:
        <br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/">https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/</a>
        <br>
        <br>
        <br>
        <br>
----------------------------------------------------------------------
        <br>
        DISCUSS:
        <br>
----------------------------------------------------------------------
        <br>
        <br>
        Please update to reflect the changes made in
        draft-ietf-calext-eventpub-extensions-17
        <br>
        (e.g., there is no longer STRUCTURED-LOCATION and VLOCATION
        plays a similar
        <br>
        role).
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
      </blockquote>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </body>
</html>

--------------BE9DEC25ADC395F552A9EC11--


From nobody Wed Feb 24 11:42:40 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A3D23A1A77; Wed, 24 Feb 2021 11:42:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>, mglt.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <161419575402.26402.5025431239986205369@ietfa.amsl.com>
Date: Wed, 24 Feb 2021 11:42:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Dvp2blNJoZEXkC81gbCBOsxF9G0>
Subject: [calsify] Robert Wilton's No Record on draft-ietf-calext-valarm-extensions-05: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Feb 2021 19:42:34 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-calext-valarm-extensions-05: No Record

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

I was pleased to see the comments about security/privacy for UUIDs in section
4, but I wonder whether it would be helpful for chapters 9 and/or 10 to have a
back reference to the UUID security/privacy considerations.

Thanks,
Rob




From nobody Wed Feb 24 11:55:22 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 297753A1A91; Wed, 24 Feb 2021 11:55:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>, mglt.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <161419651563.19650.8529066342206368745@ietfa.amsl.com>
Date: Wed, 24 Feb 2021 11:55:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/GOGuPQq4mRio3NtjWXW8l_2g3R4>
Subject: [calsify] Alissa Cooper's No Objection on draft-ietf-calext-valarm-extensions-05: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Feb 2021 19:55:16 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-calext-valarm-extensions-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 8.2 uses the term "precision," but precision and uncertainty are not
the same thing and should not be confused. See RFC 7459. Please use the term
"uncertainty" here instead.




From nobody Wed Feb 24 11:57:14 2021
Return-Path: <alissa@cooperw.in>
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 C262B3A1A9E; Wed, 24 Feb 2021 11:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, 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=cooperw.in header.b=gAT0z3Jo; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=USsIwtaG
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 I2w2K7uAz8sc; Wed, 24 Feb 2021 11:57:04 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 717963A1A9D; Wed, 24 Feb 2021 11:57:04 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id AFF865C0198; Wed, 24 Feb 2021 14:57:03 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 24 Feb 2021 14:57:03 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=9 NoUdtKzzb4eneqvA+BodCeAf6ot4+IUBa8DCVY3wzw=; b=gAT0z3JomYWjpEZ2q QMX/U04mfkOmVmYtxGkVdH2NYcIMBhQlOgpYhD9BT7QDEoSWdUmRZAZ+acGglWZB t78tELb7W5HQcOsUlCouJKXaB81JoQAaZWjyqN4Q+Oob2oTg3fdo4RwfsdMrgS/z GF1o/lm7NO/HfqO01gruUp/b84nkplkgYEngbWsIabuqGbpsHua/k1tqL4E2SKj2 5V6521+Q6vBYQ8B4hfgeeNDTaTvJDlDMkReJIefrR4qN+6jaSuyuxRaKr0WQs7J+ om4eUTi2dAJ6snXEtkCaGDpRCsHxBfjW+nH5x4wQSHLp/37zF8ZEeelF2lL4desM BmB7A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=9NoUdtKzzb4eneqvA+BodCeAf6ot4+IUBa8DCVY3w zw=; b=USsIwtaG5Iq2pF5pjf+vejFC5hHsx3qclyM8lWIhHtq4K1mc5O+OsBLtG mdO9FqbvzyolyrwxE5YqF5FY/DFH2q+ebEPjoTjVl27BqkoUB76SrGVU7JVx2L6h 0Qq1XkqYRRxIxjbjfDxTJcEEjZaI/E+g3PoTOp2h195NGLraqGquAgE3SEpGWtIw n4rnYHxr1LG9J9EJ7OY1g/cqFHNaHFFNdVMotjbZ7Jr+iLwUyMlEJUSoa1s7aUIe JNw4QPVrxLBJnaJ4oTKqgADIyqOzUIB9JnmZ2Ef1OuJyjaJSRKyK4xBrkVj+uTJ+ Dh7lpU79TDB3Ca2+5P0XMFyov567A==
X-ME-Sender: <xms:j682YC6fqYF5N_5Zr1nag-_VHORa5emZjjW5zRAOQU1R0UribbSsYQ> <xme:j682YIlmTkrOQ3bHyKy_AzFRkM7D5mg7Bw0rVXrbZtO9_xrF1KgA4tyxzXJ0u7VMH VRncHe49al0SJRhVw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeejgdduvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucggtffrrg htthgvrhhnpefguedtkeethfekleehheethedvkeektedtvddvjefghfeikeffgeegveef ueegtdenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedrudduje drjeelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep rghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:j682YFWhuuFfY9dB5bmE-SGcj_c-5Tp61crmUyPlbmXefPfJ9jddMQ> <xmx:j682YJQCi9dn8XvYIeoMYj0pfJYHFzf9-uVAoWiaOv6nkxFQDEu9UA> <xmx:j682YKBeaCok6lme3zv3B7gf8E29S6rFHcAk-OZTwfFhA0V63Df2mA> <xmx:j682YO8Y2suAKqceg1h6DZWRTy8M8YvdbJC-lVD_RrY7Wj8YIo6Jdw>
Received: from rtp-vpn1-1499.cisco.com (unknown [173.38.117.79]) by mail.messagingengine.com (Postfix) with ESMTPA id 0133E240064; Wed, 24 Feb 2021 14:57:02 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <244d01d704ea$d2e76f40$78b64dc0$@gmail.com>
Date: Wed, 24 Feb 2021 14:57:02 -0500
Cc: Ken Murchison <murch@fastmail.com>, General Area Review Team <gen-art@ietf.org>, last-call@ietf.org, calsify@ietf.org, draft-ietf-calext-valarm-extensions.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <660CB3CA-F7E7-42DA-9854-200564C54A35@cooperw.in>
References: <161338513250.5032.11173671129331374190@ietfa.amsl.com> <a87b7942-9976-39c5-43dd-23f4acfa9a6a@fastmail.com> <244d01d704ea$d2e76f40$78b64dc0$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/imZfKj-ZlPa5_AtwvsjtIYYgjDw>
Subject: Re: [calsify] [Gen-art] Genart last call review of draft-ietf-calext-valarm-extensions-04
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: Wed, 24 Feb 2021 19:57:07 -0000

Roni, thanks for your review. Ken, thanks for addressing Roni=E2=80=99s =
comments. I entered a No Objection ballot.

Alissa


> On Feb 17, 2021, at 12:07 AM, Roni Even <ron.even.tlv@gmail.com> =
wrote:
>=20
> Hi Ken,
> Thanks, it is OK=20
> Roni
>=20
>> -----Original Message-----
>> From: Ken Murchison [mailto:murch@fastmail.com]
>> Sent: Monday, February 15, 2021 2:27 PM
>> To: Roni Even; gen-art@ietf.org
>> Cc: calsify@ietf.org; =
draft-ietf-calext-valarm-extensions.all@ietf.org; last-
>> call@ietf.org
>> Subject: Re: Genart last call review of =
draft-ietf-calext-valarm-extensions-04
>>=20
>> Hi Roni,
>>=20
>> Thanks for the review.  Your comment is addressed below.
>>=20
>>=20
>> On 2/15/21 5:32 AM, Roni Even via Datatracker wrote:
>>> Reviewer: Roni Even
>>> Review result: Ready with Nits
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>> Review Team (Gen-ART) reviews all IETF documents being processed by
>>> the IESG for the IETF Chair.  Please treat these comments just like
>>> any other last call comments.
>>>=20
>>> For more information, please see the FAQ at
>>>=20
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>=20
>>> Document: draft-ietf-calext-valarm-extensions-??
>>> Reviewer: Roni Even
>>> Review Date: 2021-02-15
>>> IETF LC End Date: 2021-02-16
>>> IESG Telechat date: Not scheduled for a telechat
>>>=20
>>> Summary:
>>> The document is ready for publication as standard track RFC with =
nits
>>>=20
>>> Major issues:
>>>=20
>>> Minor issues:
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> 1. The structured-location is optional so if it is not specified for
>>> proximity I assume that it implies current location?
>>=20
>>=20
>> STRUCTURED-LOCATION is optional because its not used for PROXIMITY:
>> [DIS]CONNECT.  I've made the following change to the text:
>>=20
>>              <t hangText=3D"Description:">This property is used to
>>              indicate that an alarm has a location-based trigger. Its
>>              value identifies the direction of motion used to trigger
>> -            the alarm. One or more location values are set using
>> +            the alarm. One or more location values MUST be set using
>>              "STRUCTURED-LOCATION" properties.</t>
>>=20
>> Is this sufficient?
>>=20
>> --
>> Kenneth Murchison
>> Senior Software Developer
>> Fastmail US LLC
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Feb 24 12:47:09 2021
Return-Path: <daniel.migault@ericsson.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 C41E13A1B18; Wed, 24 Feb 2021 12:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.57, 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_H2=-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=ericsson.com
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 sfwjWif0ajxm; Wed, 24 Feb 2021 12:47:06 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770043.outbound.protection.outlook.com [40.107.77.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7A383A1B16; Wed, 24 Feb 2021 12:47:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EmQdS6W1VjyZkf1W1BcLB0GPWjCrV+TVtX3NxqFwNgAIX/Hp5NhiW344EyZllbVowS5ngZnSE4dcvKl78jtJefDQ0WigP14Qx708kf5zYcCOmLsECjyReOEAKG1JWQvVIchlYXkicK1gFoPxiWO41MT5+8EkS/+bN3u79iLEdlgeZLK/X9EOp1tgSHHcGGSC+uqYdY/U71H7aFnauLVfsmJn/ojsJf4wWf9z0BV25oKS1ujVGwzkv+JV5R5L1gSRRa6rFVOogCP14dj69O41yBFbeq61UMxomUuqgS+sYJS2c5dXxyurt20Paf4b7NXAnHLIgbBduAdq/pa9AlhOzg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XTZ50aPM6eCHMkiQiiUGCZy4n59NpxlylXoRZHm5Hr4=; b=XudD2cAfcwy82QllsUDp9aEguicm6YSDZ+tavP3leZ8HHFDtmmURwJd1TtWnZ0eTRvbSKqc2QbBshk9om7ByeK831MKZI/F9SFi5s+j0ZxZ2mpkUqN4rSg0vzm/R7Lrcj/EaiVAZzObNhunl/bq2VCDepkMvhLYVP0Ai7qZ8tw6yxB710pWAGHBI2Wc9sGwwqON3gczSmyD+a9ovBDYnpTlFgPlERAlelK0KwHeQlCU/Ti1fhu8qKamIUgD7iCiAuNc1NuX6+TQ9tty6TiJRO43Giyp9nmXPXRCYw6JArrff7jnSNXH0JZ7vV9VQgke2VP2MZ8QL7VvFqbOR1pR2OA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XTZ50aPM6eCHMkiQiiUGCZy4n59NpxlylXoRZHm5Hr4=; b=J0zXcWoCjn9Cm+mc8H3KnmN67zcxLlsMRiB3YtUFFOi66WTgKFXGKc/9NOB7IwKeH1v6HSg9NwXKlNcfkeAOYkVd4rUjJtHUmWOkW5qHn+avmKPBDYFp8CDiWf768ubIYm5jdtxuKsEvW1GisR70kYbdV2eLaALLYRwXwynjA78=
Received: from DM6PR15MB2379.namprd15.prod.outlook.com (2603:10b6:5:8a::16) by DM5PR15MB1147.namprd15.prod.outlook.com (2603:10b6:3:bc::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3890.19; Wed, 24 Feb 2021 20:47:00 +0000
Received: from DM6PR15MB2379.namprd15.prod.outlook.com ([fe80::a9f9:326f:8cfb:157b]) by DM6PR15MB2379.namprd15.prod.outlook.com ([fe80::a9f9:326f:8cfb:157b%7]) with mapi id 15.20.3825.040; Wed, 24 Feb 2021 20:47:00 +0000
From: Daniel Migault <daniel.migault@ericsson.com>
To: Ken Murchison <murch@fastmail.com>, Calsify <calsify@ietf.org>
CC: "calext-chairs@ietf.org" <calext-chairs@ietf.org>
Thread-Topic: [calsify] Benjamin Kaduk's Discuss on draft-ietf-calext-valarm-extensions-05: (with DISCUSS)
Thread-Index: AQHXCmAnKpjD2+DkoECJfnmpVjfHjKpnRU2AgABNlICAADRBcA==
Date: Wed, 24 Feb 2021 20:47:00 +0000
Message-ID: <DM6PR15MB237952EBD1CC78B7AE10DDC5E39F9@DM6PR15MB2379.namprd15.prod.outlook.com>
References: <161413859617.6944.7507348820702497356@ietfa.amsl.com> <8a461d03-a1a8-269e-bd9c-46b56d709003@fastmail.com> <e663395a-bfb5-2b0f-0108-b97c9b9dfab2@fastmail.com>
In-Reply-To: <e663395a-bfb5-2b0f-0108-b97c9b9dfab2@fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: fastmail.com; dkim=none (message not signed) header.d=none;fastmail.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [96.22.11.129]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ad412e4f-1292-435d-44bf-08d8d9055568
x-ms-traffictypediagnostic: DM5PR15MB1147:
x-microsoft-antispam-prvs: <DM5PR15MB1147D26B70681140922C15C5E39F9@DM5PR15MB1147.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: aSyPh8DSzPuteH2m8tY7cRgPhcJl9/cY22SQRPZE3kTrMrmhtxFdEfrUg2micqVaGynE4ybE9hHdeJXgse9Nhdpzjksa+L2rbVa18IVmmKInel+A4tHu/wIYHkHBcqrLEM+Q+6KVscY6qqkW07d3Pq7gf7RHlUIJxUtI+oL5ayuczvIFNIbu3T9hLh5HskEJyS0l15Ar71ZwozLy8iPp2chaG9auGXkMlbmbw5UjOV5yP+6cK4bp6knDGFVi7Q2TwXVMoHjj7InJn3+0P9+H0r3nWEkNd+QwFHN0D/uupT70I2mrOKbOtG0Ozi+SEjsEz7YsLGl/xrl8EAs8+9edmNOZSNxv3TcIhVhyPOnV8udbho/Rgyd1S2+T3dbPpcskMTTWmBUu1rMolbun2bASSUugPoUXV8qv2pvhBW+GrC+38mxFyLZ+w3i1Qhk/SsZKEc+Uw61YFyTrN585ZEUKW21UL79zy7zH1sap8BHdHeH+gaiKe/m1CIylxWT3FrvgSfmogNCkj6qBmsd9FZHagm0bcjPHGdcabFoBEXwk6xwFJhzaiNrt2USvIdwKOn1TSOBliD+dp5C0I+wA5Iz4tmlq8XY6qP519yeXkFQiz/I=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR15MB2379.namprd15.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(39860400002)(376002)(346002)(366004)(136003)(186003)(83380400001)(4326008)(166002)(966005)(53546011)(71200400001)(86362001)(478600001)(110136005)(21615005)(44832011)(316002)(9686003)(76116006)(8936002)(26005)(66446008)(33656002)(55016002)(64756008)(8676002)(2906002)(6506007)(66556008)(66946007)(66476007)(7696005)(5660300002)(52536014); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?RFRJT3VIK2dTSCs1R1FJWnNzVFFqNXcvM3FnT0pRWVVxdWZRODcrWDZtWVVz?= =?utf-8?B?QXBWV1pIMG5TQmdiUEE3RU1sTmNQMy8zSDNoV1NxZmdHbGRjbmxFY3JyL2tH?= =?utf-8?B?VlFmT08vcE1wNmU0OUxWOUpaS1EvaUN3dE0rZHNDYmNJYWwvZGdVNEV0M09h?= =?utf-8?B?Um9GZFBVQ1Y3eXNtWVB5Q0xWdHZZa2JTWmh6anhLM2N6anJGWDQxeExjMXpm?= =?utf-8?B?YWZkb1J0bUNZOVcyNDdTN1VwM3JPdGhUa2p5VXhTZXZaM0FYclVOZzcrbWpB?= =?utf-8?B?UDFwWjQwN2I0cXpDN1lmNDBOT295S2lrVXBpWEZvZjlQZ0pzM3JkSHdmc21o?= =?utf-8?B?QjNYYmNXOXRLaTdya2VkYlFaemJURzhQZnJac1FCRFQxbllaZGNZZEY5MmRq?= =?utf-8?B?NzlzMUN2TVZzTUw1Y1dSb3kyb2FiR1FOeWpNM09JUldITGpuMDJQSnJiN2o3?= =?utf-8?B?clgrdUFNRHpOeHRjWVJoL3FRVlFNQ2ozb3IzVzVKdTZueEY4U0orRjJOTnZv?= =?utf-8?B?YlhYZjNYUmUzMUh2TlRldllPMExzMGdiOXFaTFVGYzBrV0s5ZjFqZ0RxRFFi?= =?utf-8?B?c0tGNHhyanlSbTlKRld5bmNEUk5YeDN6c0VyN3QydjJHZFJEdkZON1NQVmlh?= =?utf-8?B?bVBBQ2lDVktycGJCYXpRYyt1WlRWcW1DMldBNUZEL1kxTk83Rm52ZnlxNWQ5?= =?utf-8?B?a3pYMnVXUmpNQkxUbjMwUzdlVkhGSFdmMjZWV1c2d0pBdnlteDRONE9QaW4y?= =?utf-8?B?eE1sdS9kWG9pL0RYaFJiSndIVnE3ajh6d2ZsNmhYd2EwR3greDVNK2ZGV1Vw?= =?utf-8?B?dWN4QVJ4bkhUWU9OdXhIUW0vcE5JQ21pU0REVHVoeUIrUGNnSDM2NkRCTnor?= =?utf-8?B?TGRlSUZ5MWJCb2pOY1RzK1pBeU1YOXFqSWU1WklhZ2tDREdIb2orQ04vOFY1?= =?utf-8?B?eTRtU1JkUTkvcjJMT1dFbTBBek9GR1VhOEs4UnJ0eXcxb1lONlNTbnlyeEpI?= =?utf-8?B?ZldQS2gvMUxBajNRNU5HRzB6NXY1RFcrL2c3WW5YK0V6b0xqSXZXWTNqeUNI?= =?utf-8?B?Y3RoUXVSVlVYckVmMGZISEtYMkdrUEc2NHZsM00yMmFMMENMbHczMDlNSGRY?= =?utf-8?B?WVpQdUFNYi9Fdm9za2Yra1VUZ01JSDNDckZVaFNxblMxY2JUWDREa0lRRExq?= =?utf-8?B?MkZpS1AwYjZqc2xVUVc1NGVxWU5NNHZDaHp0Rlduc0ZzTlJGMU1xdktZWGs2?= =?utf-8?B?dG5zUEh2SkVQVHVZKzRndmI4Tk44VnY1anl1N2tpVVU2cVRWSEQ1c1pRb2VP?= =?utf-8?B?L0F1UjlwZ1dIV3hZZEgwa0JHTjdTS3Q0dTBLM3V1VjZRSVU5NlJyYUtqdEly?= =?utf-8?B?VXNydzFiNnF0OHFlbDNmcEF2ZjZ4NU9nQ0lQczc4WE41UzRVSEgzajhYTzEv?= =?utf-8?B?aVN6Q0I4bUg2cjRmT1NRVTJ4ejJVajMwT2pyeG1ieHNMd0FjMUR6U0xJV25Z?= =?utf-8?B?REFFYzNwVjI3YVdGMmJhck9JdUlwbGxQWlhMUkNBOW9MY0wzR0s2K0x4Vk9t?= =?utf-8?B?V0g4dTdSNlFaT0RvVm9vZFFsSjFOL1I4OUVUeXVIODRobVNTd0ZNTTd5eFps?= =?utf-8?B?aVBJbmhsVjdRZ1IrZzJ2V3o4UVZjT09yR0VrMWhxWTJDdXJKKzQ3UGhUb2F3?= =?utf-8?B?RDBJbnVudFhqL1U4SzRUdFJxZzhNaytaQmNqb3Q3UzFpK09YdDhQV0pibGNs?= =?utf-8?Q?oBD6G7Q9RnjH9vCK4c=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR15MB237952EBD1CC78B7AE10DDC5E39F9DM6PR15MB2379namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR15MB2379.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ad412e4f-1292-435d-44bf-08d8d9055568
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Feb 2021 20:47:00.2816 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qbbIL4jVQGn/0iFRbrUFn769BUXvkEDqRNU+XVdc6bePPZgTr6e8txnDWJ6MlHPjMvLfq1CYui9Ia/cSmz/XtPWN7StfjN9KMSajpoJ1mHE=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR15MB1147
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/_CZyDK1wcjcUcx3j4R6NoS61zKE>
Subject: Re: [calsify] Benjamin Kaduk's Discuss on draft-ietf-calext-valarm-extensions-05: (with DISCUSS)
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: Wed, 24 Feb 2021 20:47:08 -0000

--_000_DM6PR15MB237952EBD1CC78B7AE10DDC5E39F9DM6PR15MB2379namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

U2VlbXMgZmluZSB0byBtZS4NCllvdXJzLA0KRGFuaWVsDQoNCkZyb206IGNhbHNpZnkgPGNhbHNp
ZnktYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIEtlbiBNdXJjaGlzb24NClNlbnQ6IFdl
ZG5lc2RheSwgRmVicnVhcnkgMjQsIDIwMjEgMTI6MzggUE0NClRvOiBDYWxzaWZ5IDxjYWxzaWZ5
QGlldGYub3JnPg0KQ2M6IGNhbGV4dC1jaGFpcnNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbY2Fs
c2lmeV0gQmVuamFtaW4gS2FkdWsncyBEaXNjdXNzIG9uIGRyYWZ0LWlldGYtY2FsZXh0LXZhbGFy
bS1leHRlbnNpb25zLTA1OiAod2l0aCBESVNDVVNTKQ0KDQoNCkFsbCwNCg0KU28sIE1pa2UgRG91
Z2xhc3MgYW5kIEkgd2VyZSBqdXN0IGRpc2N1c3NpbmcgdGhpcyBhbmQgd2UgY2FtZSB0byB0aGUg
Y29uY2x1c2lvbiB0aGF0IHRoZSBiZXN0IHBsYWNlIHRvIHB1dCB0aGUgZ2VvZ3JhcGhpYyBjb29y
ZGluYXRlcyBpcyBnb2luZyB0byBiZSBpbiBhIFVSTCBwcm9wZXJ0eSByYXRoZXIgdGhhbiBhIEdF
TyBwcm9wZXJ0eSwgYmVjYXVzZSB0aGUgbGF0dGVyIG9ubHkgZW5jb2RlcyBsYXRpdHVkZSBhbmQg
bG9uZ2l0dWRlLiAgU28sIHRoZSBwcm94aW1pdHkgYWxhcm0gd291bGQgbG9vayBzb21ldGhpbmcg
bGlrZSB0aGlzOg0KDQpCRUdJTjpWQUxBUk0NCg0KVUlEOjc3RDgwRDE0LTkwNkItNDI1Ny05NjNG
LTg1QjFFNzM0REJCNg0KDQpUUklHR0VSO1ZBTFVFPURBVEUtVElNRToxOTc2MDQwMVQwMDU1NDVa
DQoNCkFDVElPTjpESVNQTEFZDQoNCkRFU0NSSVBUSU9OOlJlbWVtYmVyIHRvIGJ1eSBtaWxrDQoN
ClRSSUdHRVI7VkFMVUU9REFURS1USU1FOjE5NzYwNDAxVDAwNTU0NVoNCg0KUFJPWElNSVRZOkRF
UEFSVA0KDQpCRUdJTjpWTE9DQVRJT04NCg0KVUlEOjEyMzQ1Ni1hYmNkZWYtOTg3NjU0MzINCg0K
TkFNRTpPZmZpY2UNCg0KVVJMOmdlbzo0MC40NDMsLTc5Ljk0NTt1PTEwDQoNCkVORDpWTE9DQVRJ
T04NCg0KRU5EOlZBTEFSTQ0KDQpEb2VzIGFueW9uZSBoYXZlIGFueSBvYmplY3Rpb25zLCBvciBv
dGhlciBzdWdnZXN0aW9ucz8NCg0KDQpPbiAyLzI0LzIxIDg6MDAgQU0sIEtlbiBNdXJjaGlzb24g
d3JvdGU6DQpIaSBCZW5qYW1pbiwNCg0KVGhhbmtzIGZvciBjYXRjaGluZyB0aGlzLiAgSSB3aWxs
IGFkZHJlc3MgdGhpcyBhcyBzb29uIGFzIHRoZSBibGFja291dCBvbiBzdWJtaXR0aW5nIGRyYWZ0
cyBoYXMgYmVlbiBsaWZ0ZWQuDQoNCg0KT24gMi8yMy8yMSAxMDo0OSBQTSwgQmVuamFtaW4gS2Fk
dWsgdmlhIERhdGF0cmFja2VyIHdyb3RlOg0KDQpCZW5qYW1pbiBLYWR1ayBoYXMgZW50ZXJlZCB0
aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCmRyYWZ0LWlldGYtY2FsZXh0LXZhbGFy
bS1leHRlbnNpb25zLTA1OiBEaXNjdXNzDQoNCldoZW4gcmVzcG9uZGluZywgcGxlYXNlIGtlZXAg
dGhlIHN1YmplY3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbA0KZW1haWwgYWRkcmVzc2Vz
IGluY2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVsIGZyZWUgdG8gY3V0IHRoaXMN
CmludHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2ZXIuKQ0KDQoNClBsZWFzZSByZWZlciB0byBo
dHRwczovL3d3dy5pZXRmLm9yZy9pZXNnL3N0YXRlbWVudC9kaXNjdXNzLWNyaXRlcmlhLmh0bWwN
CmZvciBtb3JlIGluZm9ybWF0aW9uIGFib3V0IElFU0cgRElTQ1VTUyBhbmQgQ09NTUVOVCBwb3Np
dGlvbnMuDQoNCg0KVGhlIGRvY3VtZW50LCBhbG9uZyB3aXRoIG90aGVyIGJhbGxvdCBwb3NpdGlv
bnMsIGNhbiBiZSBmb3VuZCBoZXJlOg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtaWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lvbnMvDQoNCg0KDQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpESVNDVVNTOg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpQbGVhc2UgdXBkYXRlIHRvIHJlZmxlY3QgdGhl
IGNoYW5nZXMgbWFkZSBpbiBkcmFmdC1pZXRmLWNhbGV4dC1ldmVudHB1Yi1leHRlbnNpb25zLTE3
DQooZS5nLiwgdGhlcmUgaXMgbm8gbG9uZ2VyIFNUUlVDVFVSRUQtTE9DQVRJT04gYW5kIFZMT0NB
VElPTiBwbGF5cyBhIHNpbWlsYXINCnJvbGUpLg0KDQoNCg0KDQoNCi0tDQoNCktlbm5ldGggTXVy
Y2hpc29uDQoNClNlbmlvciBTb2Z0d2FyZSBEZXZlbG9wZXINCg0KRmFzdG1haWwgVVMgTExDDQo=

--_000_DM6PR15MB237952EBD1CC78B7AE10DDC5E39F9DM6PR15MB2379namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6ZTox
MS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFu
Lk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47
DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4u
SFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVk
IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQ
cmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCi5Nc29DaHBEZWZhdWx0DQoJ
e21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2Ug
V29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAx
LjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0t
Pjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0
PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4
dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4N
CjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBz
dHlsZT0id29yZC13cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNlZW1zIGZpbmUgdG8gbWUuIDxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+WW91cnMsIDxicj4NCkRhbmllbDxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6
My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IGNh
bHNpZnkgJmx0O2NhbHNpZnktYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mDQo8
L2I+S2VuIE11cmNoaXNvbjxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIEZlYnJ1YXJ5IDI0
LCAyMDIxIDEyOjM4IFBNPGJyPg0KPGI+VG86PC9iPiBDYWxzaWZ5ICZsdDtjYWxzaWZ5QGlldGYu
b3JnJmd0Ozxicj4NCjxiPkNjOjwvYj4gY2FsZXh0LWNoYWlyc0BpZXRmLm9yZzxicj4NCjxiPlN1
YmplY3Q6PC9iPiBSZTogW2NhbHNpZnldIEJlbmphbWluIEthZHVrJ3MgRGlzY3VzcyBvbiBkcmFm
dC1pZXRmLWNhbGV4dC12YWxhcm0tZXh0ZW5zaW9ucy0wNTogKHdpdGggRElTQ1VTUyk8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwPkFsbCw8bzpwPjwvbzpwPjwvcD4NCjxwPlNvLCBNaWtlIERvdWdsYXNz
IGFuZCBJIHdlcmUganVzdCBkaXNjdXNzaW5nIHRoaXMgYW5kIHdlIGNhbWUgdG8gdGhlIGNvbmNs
dXNpb24gdGhhdCB0aGUgYmVzdCBwbGFjZSB0byBwdXQgdGhlIGdlb2dyYXBoaWMgY29vcmRpbmF0
ZXMgaXMgZ29pbmcgdG8gYmUgaW4gYSBVUkwgcHJvcGVydHkgcmF0aGVyIHRoYW4gYSBHRU8gcHJv
cGVydHksIGJlY2F1c2UgdGhlIGxhdHRlciBvbmx5IGVuY29kZXMgbGF0aXR1ZGUgYW5kIGxvbmdp
dHVkZS4mbmJzcDsgU28sDQogdGhlIHByb3hpbWl0eSBhbGFybSB3b3VsZCBsb29rIHNvbWV0aGlu
ZyBsaWtlIHRoaXM6PG86cD48L286cD48L3A+DQo8cHJlPkJFR0lOOlZBTEFSTTxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlPlVJRDo3N0Q4MEQxNC05MDZCLTQyNTctOTYzRi04NUIxRTczNERCQjY8bzpw
PjwvbzpwPjwvcHJlPg0KPHByZT5UUklHR0VSO1ZBTFVFPURBVEUtVElNRToxOTc2MDQwMVQwMDU1
NDVaPG86cD48L286cD48L3ByZT4NCjxwcmU+QUNUSU9OOkRJU1BMQVk8bzpwPjwvbzpwPjwvcHJl
Pg0KPHByZT5ERVNDUklQVElPTjpSZW1lbWJlciB0byBidXkgbWlsazxvOnA+PC9vOnA+PC9wcmU+
DQo8cHJlPlRSSUdHRVI7VkFMVUU9REFURS1USU1FOjE5NzYwNDAxVDAwNTU0NVo8bzpwPjwvbzpw
PjwvcHJlPg0KPHByZT5QUk9YSU1JVFk6REVQQVJUPG86cD48L286cD48L3ByZT4NCjxwcmU+QkVH
SU46VkxPQ0FUSU9OPG86cD48L286cD48L3ByZT4NCjxwcmU+VUlEOjEyMzQ1Ni1hYmNkZWYtOTg3
NjU0MzI8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT5OQU1FOk9mZmljZTxvOnA+PC9vOnA+PC9wcmU+
DQo8cHJlPjxhIGhyZWY9IlVSTDpnZW86NDAuNDQzLC03OS45NDU7dT0xMCI+VVJMOmdlbzo0MC40
NDMsLTc5Ljk0NTt1PTEwPC9hPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPkVORDpWTE9DQVRJT048
bzpwPjwvbzpwPjwvcHJlPg0KPHByZT5FTkQ6VkFMQVJNPG86cD48L286cD48L3ByZT4NCjxwPkRv
ZXMgYW55b25lIGhhdmUgYW55IG9iamVjdGlvbnMsIG9yIG90aGVyIHN1Z2dlc3Rpb25zPzxvOnA+
PC9vOnA+PC9wPg0KPHA+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+T24gMi8yNC8yMSA4OjAwIEFNLCBLZW4gTXVyY2hpc29uIHdyb3RlOjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIEJlbmphbWluLCA8YnI+
DQo8YnI+DQpUaGFua3MgZm9yIGNhdGNoaW5nIHRoaXMuJm5ic3A7IEkgd2lsbCBhZGRyZXNzIHRo
aXMgYXMgc29vbiBhcyB0aGUgYmxhY2tvdXQgb24gc3VibWl0dGluZyBkcmFmdHMgaGFzIGJlZW4g
bGlmdGVkLg0KPGJyPg0KPGJyPg0KPGJyPg0KT24gMi8yMy8yMSAxMDo0OSBQTSwgQmVuamFtaW4g
S2FkdWsgdmlhIERhdGF0cmFja2VyIHdyb3RlOiA8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4N
CjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5CZW5q
YW1pbiBLYWR1ayBoYXMgZW50ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3IN
Cjxicj4NCmRyYWZ0LWlldGYtY2FsZXh0LXZhbGFybS1leHRlbnNpb25zLTA1OiBEaXNjdXNzIDxi
cj4NCjxicj4NCldoZW4gcmVzcG9uZGluZywgcGxlYXNlIGtlZXAgdGhlIHN1YmplY3QgbGluZSBp
bnRhY3QgYW5kIHJlcGx5IHRvIGFsbCA8YnI+DQplbWFpbCBhZGRyZXNzZXMgaW5jbHVkZWQgaW4g
dGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJlZSB0byBjdXQgdGhpcyA8YnI+DQppbnRyb2R1
Y3RvcnkgcGFyYWdyYXBoLCBob3dldmVyLikgPGJyPg0KPGJyPg0KPGJyPg0KUGxlYXNlIHJlZmVy
IHRvIDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL2llc2cvc3RhdGVtZW50L2Rpc2N1c3Mt
Y3JpdGVyaWEuaHRtbCI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9pZXNnL3N0YXRlbWVudC9kaXNj
dXNzLWNyaXRlcmlhLmh0bWw8L2E+IDxicj4NCmZvciBtb3JlIGluZm9ybWF0aW9uIGFib3V0IElF
U0cgRElTQ1VTUyBhbmQgQ09NTUVOVCBwb3NpdGlvbnMuIDxicj4NCjxicj4NCjxicj4NClRoZSBk
b2N1bWVudCwgYWxvbmcgd2l0aCBvdGhlciBiYWxsb3QgcG9zaXRpb25zLCBjYW4gYmUgZm91bmQg
aGVyZTogPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtaWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lvbnMvIj5odHRwczovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1pZXRmLWNhbGV4dC12YWxhcm0tZXh0ZW5zaW9ucy88L2E+DQo8YnI+
DQo8YnI+DQo8YnI+DQo8YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIDxicj4NCkRJU0NVU1M6IDxicj4NCi0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0gPGJyPg0KPGJyPg0KUGxlYXNlIHVwZGF0ZSB0byByZWZsZWN0IHRoZSBjaGFu
Z2VzIG1hZGUgaW4gZHJhZnQtaWV0Zi1jYWxleHQtZXZlbnRwdWItZXh0ZW5zaW9ucy0xNw0KPGJy
Pg0KKGUuZy4sIHRoZXJlIGlzIG5vIGxvbmdlciBTVFJVQ1RVUkVELUxPQ0FUSU9OIGFuZCBWTE9D
QVRJT04gcGxheXMgYSBzaW1pbGFyIDxicj4NCnJvbGUpLiA8YnI+DQo8YnI+DQo8YnI+DQo8YnI+
DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvYmxvY2txdW90ZT4NCjxw
cmU+LS0gPG86cD48L286cD48L3ByZT4NCjxwcmU+S2VubmV0aCBNdXJjaGlzb248bzpwPjwvbzpw
PjwvcHJlPg0KPHByZT5TZW5pb3IgU29mdHdhcmUgRGV2ZWxvcGVyPG86cD48L286cD48L3ByZT4N
CjxwcmU+RmFzdG1haWwgVVMgTExDPG86cD48L286cD48L3ByZT4NCjwvZGl2Pg0KPC9ib2R5Pg0K
PC9odG1sPg0K

--_000_DM6PR15MB237952EBD1CC78B7AE10DDC5E39F9DM6PR15MB2379namp_--


From nobody Wed Feb 24 15:04:14 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B9BDF3A1108; Wed, 24 Feb 2021 15:04:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>, mglt.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <161420784613.18632.5901912577537198998@ietfa.amsl.com>
Date: Wed, 24 Feb 2021 15:04:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/bX26EJzU57HSpfr70g-d3EV3ey4>
Subject: [calsify] Warren Kumari's No Objection on draft-ietf-calext-valarm-extensions-05: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Feb 2021 23:04:07 -0000

Warren Kumari has entered the following ballot position for
draft-ietf-calext-valarm-extensions-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Please note: I am not an iCal person (probably as demonstrated by the fact that
I call it ical), and parsing an icalendar file fills me with dread -- but even
I found this document clear, readable, understandable, and solving a set of
problems that I understand. Thank you for such a good read.




From nobody Wed Feb 24 17:26:00 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 455AB3A0ABB; Wed, 24 Feb 2021 17:25:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>, mglt.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <161421635519.4540.12134094030905577707@ietfa.amsl.com>
Date: Wed, 24 Feb 2021 17:25:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Z_GWPpNlDx3-jk-LYd11eMjWZNw>
Subject: [calsify] Benjamin Kaduk's Discuss on draft-ietf-calext-valarm-extensions-05: (with DISCUSS and COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Feb 2021 01:25:55 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-calext-valarm-extensions-05: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Please update to reflect the changes made in draft-ietf-calext-eventpub-extensions-17
(e.g., there is no longer STRUCTURED-LOCATION and VLOCATION plays a similar
role).


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

[edited to add a comment section, now that I finished my way through
the document]

A lot of these improvements look familiar from
draft-ietf-calext-jscalendar :)

Please note the question about interactions between "geo:" URIs and
(presumed mobile) vehicles, in Section 8; that was almost a Discuss.

Section 3

Is the new syntax for VALARM claimed to be exactly equivalent or just
"basically the same" as the RFC 5545 definition?

Section 6.1

   Description:  This property is used to specify when an alarm was last
      sent or acknowledged.  This allows clients to determine when a

(editorial) the "last sent" part only becomes clear in the second
paragraph; perhaps "when an alarm was last acknowledge (or sent, if
acknowledgment is not possible)" would help clarify (and would also do
better to set up the rest of this paragraph that mostly assumes the
"acknowledged" case).

Section 7

   To "snooze" an alarm, clients create a new "VALARM" component within
   the parent component of the "VALARM" that was triggered and is being
   "snoozed" (i.e., as a "sibling" component of the "VALARM" being
   snoozed).  [...]

The way this is written seems to imply something that does not seem
correct.  That is, the "i.e., as a 'sibling'" seems to imply that VALARM
will always exist in a parent/child relationship, with only "child"
instances ever actually triggering.  Since we only just in this document
allow VALARM to have the RELATED-TO property, I don't see how that could
be the case.  Perhaps it is enough to just say "e.g., as a "sibling"
component of the "VALARM" being snoozed", since "e.g." does not imply
that the statement applies for all cases, but I would expect some more
substantial discussion of the procedures involved when there is just a
single alarm being snoozed, and how the first child is created, what
needs to be done (if anything else) to create the overarching "parent",
etc.  The only text I see right now that covers this case is the
addition of "UID" if not already present (and UID has to be present if
there's a parent/child relationship), but that's not really the same
thing.

   Alternatively, if the "snooze" alarm is itself "snoozed", the client
   MUST remove the original "snooze" alarm and create a new one, with
   the appropriate trigger time and relationship set.

(This part seems a bit at odds with the "as a 'sibling' text above that
I complained about -- if the alarm being triggered is getting removed,
it seems hard for it to be a sibling of anything.)

Section 7.1

   This specification adds the "SNOOZE" relationship type for use with
   the "RELTYPE" property defined in Section 3.2.15 of [RFC5545].  This
   is used when relating a "snoozed" "VALARM" component to the original
   alarm that the "snooze" was generated for.

Is this going to be the "parent" or the "sibling" (or potentially
either)?  Note my previous comment about "sibling"s getting removed...

Section 8

      "STRUCTURED-LOCATION" [I-D.ietf-calext-eventpub-extensions] - used
      to indicate the actual location to trigger off, specified using a
      geo: URI [RFC5870] which allows for two or three coordinate values
      with an optional uncertainty

(nit?) maybe "trigger off of"?

      "STRUCTURED-LOCATION" [I-D.ietf-calext-eventpub-extensions] - used
      to indicate the actual location to trigger off, specified using a
      geo: URI [RFC5870] which allows for two or three coordinate values
      with an optional uncertainty

How do I use a geo: URI to indicate the vehicle to which I (dis)connect
via Bluetooth with?

Section 8.1

(side note) is there work underway to define proximity triggers for
JSCalendar?

   Description:  This property is used to indicate that an alarm has a
      location-based trigger.  Its value identifies the direction of
      motion used to trigger the alarm.  One or more location values
      MUST be set using "STRUCTURED-LOCATION" properties.

(editorial) I don't see how we get "direction of motion" from the rest
of the description.  What I see described is just, well, a
proximity-based trigger, without sensitivity to in what direction the
proximity is attained.  There are triggers based on whether the distance
metric crosses a threshold in one direction or the other, but that's
still not directional in a typical 3-dimentional vector sense.

Section 8.2

Is there a reason for the "TRIGGER" line to appear twice in the example?

Section 9

I think there is also potential for abuse in causing embarassing or
otherwise undesired alerts (especially audio ones) when a victim is in a
particular location.  (But the mitigation is basically the same as for
the already-indicated threats.)

Section 13

It's not entirely clear to me that RFC 4791 needs to be classified as
normative.




From nobody Wed Feb 24 23:00:10 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 991243A145D; Wed, 24 Feb 2021 23:00:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-valarm-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, Daniel Migault <mglt.ietf@gmail.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <161423640259.18976.6018954114099831363@ietfa.amsl.com>
Date: Wed, 24 Feb 2021 23:00:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/WnyAltrObMao4dRM1JAeI2V_1js>
Subject: [calsify] Murray Kucherawy's No Objection on draft-ietf-calext-valarm-extensions-05: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Feb 2021 07:00:03 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-calext-valarm-extensions-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This document appears to enable (or continue) support for the notion of
extension properties prefixed by "X-" (via the "x-prop" ABNF token).  That
seems contrary to BCP 178.  I realize this is just continuing in what was done
in RFC 5545, but should it be dropped her?

Other than this one concern, this is really well written.  Nice work.




From nobody Thu Feb 25 06:54:40 2021
Return-Path: <barryleiba@gmail.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 121F03A17DF; Thu, 25 Feb 2021 06:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 z81Nestdsm1v; Thu, 25 Feb 2021 06:54:37 -0800 (PST)
Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (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 672063A1669; Thu, 25 Feb 2021 06:54:37 -0800 (PST)
Received: by mail-lf1-f50.google.com with SMTP id 18so414961lff.6; Thu, 25 Feb 2021 06:54:37 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=p/rkZLJ6mzUardkoAOUKm1bKK6fV3hKOfoYC5G/QX1Q=; b=ZI7/awvzz2ZsSjujzzk83zVNBWs37HDSoYv4k9a57nAyeJDLkoqR9O082E0IvL2acz WPPIlFBQvWfWsyRMlgoM/eb4z0d6QhrnWujVino8RCj9ur4dTH+X3U3fcKmF1m6/uxjp f9qV/1fQESLMioXETDiON22ZWuzZyO76MZvZBW842xU0FcdFc38T+dm/qS2yyI7EK1W1 my8KxOQ0/v9jMaUldcyhHrYR415R9bgeZvELZpwogEdvf6Sxe5v7vofZyCd9LZtWlghO UIwgE6yPiDKh3JKLf3GLjQEaJLbAVtFG8xtw0PsexBF4BjqPO/Wn78mAsO1ciTpPhUku TK1A==
X-Gm-Message-State: AOAM533rD+yrW8Y/G/h4zrq3voB4G61R0jZnoUs/fHBE22tFwwqkIw6r LA2fplu4M30LYuGb6L6YVImuV2mqT18tYuErmQh/takjsGQ=
X-Google-Smtp-Source: ABdhPJzWx0CCxIsHWnSiaDc8iDbZBNAYD32EpaCpV/H4eNp00e/uYceHwMNbD3B1aL9cWlwIJvsLEKjUsT22vNI/GsI=
X-Received: by 2002:ac2:58c1:: with SMTP id u1mr2228620lfo.440.1614264875479;  Thu, 25 Feb 2021 06:54:35 -0800 (PST)
MIME-Version: 1.0
References: <161423640259.18976.6018954114099831363@ietfa.amsl.com>
In-Reply-To: <161423640259.18976.6018954114099831363@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 25 Feb 2021 09:54:24 -0500
Message-ID: <CALaySJ+pRFNFm04eudGuw8SgOtG69oPPqjDj+d_9TZf3w5ZuBw@mail.gmail.com>
To: Murray Kucherawy <superuser@gmail.com>
Cc: The IESG <iesg@ietf.org>, Bron Gondwana <brong@fastmailteam.com>,  Daniel Migault <mglt.ietf@gmail.com>, calsify@ietf.org, calext-chairs@ietf.org, draft-ietf-calext-valarm-extensions@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/_Ke0bP5LwuYErAHi1LGaVV_zjRQ>
Subject: Re: [calsify] Murray Kucherawy's No Objection on draft-ietf-calext-valarm-extensions-05: (with COMMENT)
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: Thu, 25 Feb 2021 14:54:39 -0000

I brought up the X- issue during AD Evaluation, and we talked about
it.  The problem is that the base document, RFC 5545, has them (as it
predates BCP 178), and removing them from the ABNF here is likely to
cause other problems.  We decided that the best approach is to put the
issue into the queue for an update to 5545, which is needed for other
reasons as well.

Barry

On Thu, Feb 25, 2021 at 2:00 AM Murray Kucherawy via Datatracker
<noreply@ietf.org> wrote:
>
> Murray Kucherawy has entered the following ballot position for
> draft-ietf-calext-valarm-extensions-05: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> This document appears to enable (or continue) support for the notion of
> extension properties prefixed by "X-" (via the "x-prop" ABNF token).  That
> seems contrary to BCP 178.  I realize this is just continuing in what was done
> in RFC 5545, but should it be dropped her?
>
> Other than this one concern, this is really well written.  Nice work.
>
>
>


From nobody Thu Feb 25 07:05:38 2021
Return-Path: <superuser@gmail.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 3A56E3A1B01; Thu, 25 Feb 2021 07:05:33 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=gmail.com
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 Hxe65GCDc00n; Thu, 25 Feb 2021 07:05:31 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (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 9B1693A1B26; Thu, 25 Feb 2021 07:04:53 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id y18so3074649vso.3; Thu, 25 Feb 2021 07:04:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YdtNVJGapbawCZQ2//HWdv3zZG3Ymu8YeKApN1cBt2A=; b=XnAC6uQZ9L36OQh9Ht7RQY7+Yz9+cT7rsu9pUoiZbBpz8vUivP3MKPPNfzmQhuPyew 3zAg6STmySg4PaHJH2KglTPUhDCrDlqVLIoO9Rvd51YV63oB6Y75FsEre6lPQLdlA0nC wanIxLINARFO6Jp5xBHvotVQ1Y0UOoeoJYfQRnn4bJKLMJNUQnVqeqXrOxkdqPL+5HOu y7ll+L6oYxKDZWgVH5Ws1ZwG3RV8iSiDzrtkNwC0XwMVQEB7nYetFzm+mPfn/TwgYD0n DZGSPdZmN6KioQgtvk3pGLBDZYU1LF6y0bMbuXUSiBAtIQfw1WO2LeTzJ702uqFe0RJt Ca7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YdtNVJGapbawCZQ2//HWdv3zZG3Ymu8YeKApN1cBt2A=; b=dME0UZr97DyBhQd1uZgzQqqlRn5RsMHXOC2C7kuzDTDFtVvcjQmIUx9YnwWSHnj85o Rs/DTqHoRxGvEwPpaxjDj8kXsKPP5aJ4gWCA1Lv4OPKTvm/VDe31A9TDKcaGbOd4CqKU 4KPloPW6S1PkuFXAnKOWa4poxUfXGAhcj2d86s8cL0JTf0EXE5IQzeGpgtTYoNP+cVfP ZibMEwl/9uNMde9utv5yIv9xaGdhNPyxqXerv9AeJpcQTXyLo0qMNJ/BDh9/uoOxB7cB oJTRjS2tazlIPc7EDdXX7fIzHaFJIkePW1llNhEPDRooTue/tsomzVRaugif8gQeAZr6 vm3A==
X-Gm-Message-State: AOAM532pD46YYNzwzBhjzKpwK0DAzYDivSatR3zxqb7CLlLVECA0K5qz y+QIt8i+1cHmU4rXYTkc8MjfIV3eb2qcUBl51iQ=
X-Google-Smtp-Source: ABdhPJy41+MdyAHf5YiZpR60/NvjQcUQnIYPnz1NncaPew04STjhg14K9v5Yy6lemrRD4iuNf7wJh7tmaBpwfpQbwH0=
X-Received: by 2002:a67:882:: with SMTP id 124mr1805630vsi.33.1614265492563; Thu, 25 Feb 2021 07:04:52 -0800 (PST)
MIME-Version: 1.0
References: <161423640259.18976.6018954114099831363@ietfa.amsl.com> <CALaySJ+pRFNFm04eudGuw8SgOtG69oPPqjDj+d_9TZf3w5ZuBw@mail.gmail.com>
In-Reply-To: <CALaySJ+pRFNFm04eudGuw8SgOtG69oPPqjDj+d_9TZf3w5ZuBw@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 25 Feb 2021 07:04:40 -0800
Message-ID: <CAL0qLwYy1OJXrjdX3k6OOibGaw7eDeYxCX-pVfSvxtAO3kGLiA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, Bron Gondwana <brong@fastmailteam.com>,  Daniel Migault <mglt.ietf@gmail.com>, calsify@ietf.org, calext-chairs@ietf.org, draft-ietf-calext-valarm-extensions@ietf.org
Content-Type: multipart/alternative; boundary="00000000000041ebd005bc2a79fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/2tcv2NjF2VGInA1BzcOb5bUIdrY>
Subject: Re: [calsify] Murray Kucherawy's No Objection on draft-ietf-calext-valarm-extensions-05: (with COMMENT)
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: Thu, 25 Feb 2021 15:05:33 -0000

--00000000000041ebd005bc2a79fc
Content-Type: text/plain; charset="UTF-8"

Thanks, that's what I figured was the outcome, but I thought I'd ask.

On Thu, Feb 25, 2021 at 6:54 AM Barry Leiba <barryleiba@computer.org> wrote:

> I brought up the X- issue during AD Evaluation, and we talked about
> it.  The problem is that the base document, RFC 5545, has them (as it
> predates BCP 178), and removing them from the ABNF here is likely to
> cause other problems.  We decided that the best approach is to put the
> issue into the queue for an update to 5545, which is needed for other
> reasons as well.
>
> Barry
>
> On Thu, Feb 25, 2021 at 2:00 AM Murray Kucherawy via Datatracker
> <noreply@ietf.org> wrote:
> >
> > Murray Kucherawy has entered the following ballot position for
> > draft-ietf-calext-valarm-extensions-05: No Objection
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-extensions/
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > This document appears to enable (or continue) support for the notion of
> > extension properties prefixed by "X-" (via the "x-prop" ABNF token).
> That
> > seems contrary to BCP 178.  I realize this is just continuing in what
> was done
> > in RFC 5545, but should it be dropped her?
> >
> > Other than this one concern, this is really well written.  Nice work.
> >
> >
> >
>

--00000000000041ebd005bc2a79fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, that&#39;s what I figured was the outcome, but I t=
hought I&#39;d ask.<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
" class=3D"gmail_attr">On Thu, Feb 25, 2021 at 6:54 AM Barry Leiba &lt;<a h=
ref=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I brought up =
the X- issue during AD Evaluation, and we talked about<br>
it.=C2=A0 The problem is that the base document, RFC 5545, has them (as it<=
br>
predates BCP 178), and removing them from the ABNF here is likely to<br>
cause other problems.=C2=A0 We decided that the best approach is to put the=
<br>
issue into the queue for an update to 5545, which is needed for other<br>
reasons as well.<br>
<br>
Barry<br>
<br>
On Thu, Feb 25, 2021 at 2:00 AM Murray Kucherawy via Datatracker<br>
&lt;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org<=
/a>&gt; wrote:<br>
&gt;<br>
&gt; Murray Kucherawy has entered the following ballot position for<br>
&gt; draft-ietf-calext-valarm-extensions-05: No Objection<br>
&gt;<br>
&gt; When responding, please keep the subject line intact and reply to all<=
br>
&gt; email addresses included in the To and CC lines. (Feel free to cut thi=
s<br>
&gt; introductory paragraph, however.)<br>
&gt;<br>
&gt;<br>
&gt; Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss=
-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/i=
esg/statement/discuss-criteria.html</a><br>
&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt;<br>
&gt;<br>
&gt; The document, along with other ballot positions, can be found here:<br=
>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-calext-valarm-e=
xtensions/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.o=
rg/doc/draft-ietf-calext-valarm-extensions/</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; COMMENT:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt;<br>
&gt; This document appears to enable (or continue) support for the notion o=
f<br>
&gt; extension properties prefixed by &quot;X-&quot; (via the &quot;x-prop&=
quot; ABNF token).=C2=A0 That<br>
&gt; seems contrary to BCP 178.=C2=A0 I realize this is just continuing in =
what was done<br>
&gt; in RFC 5545, but should it be dropped her?<br>
&gt;<br>
&gt; Other than this one concern, this is really well written.=C2=A0 Nice w=
ork.<br>
&gt;<br>
&gt;<br>
&gt;<br>
</blockquote></div>

--00000000000041ebd005bc2a79fc--

