Re: [calsify] «For a given pair of "UID" and "SEQUENCE" property values, the "RECURRENCE-ID" value for a recurrence instance is fixed.»
Neil Jenkins <neilj@fastmailteam.com> Thu, 06 January 2022 05:33 UTC
Return-Path: <neilj@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id B431E3A0983
for <calsify@ietfa.amsl.com>; Wed, 5 Jan 2022 21:33:31 -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=uKnRo2gQ;
dkim=pass (2048-bit key)
header.d=messagingengine.com header.b=kTcAh5Dm
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 FSFYavPqSgtn for <calsify@ietfa.amsl.com>;
Wed, 5 Jan 2022 21:33:27 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
[66.111.4.26])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 154423A0990
for <calsify@ietf.org>; Wed, 5 Jan 2022 21:33:26 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
by mailout.nyi.internal (Postfix) with ESMTP id 752CD5C0080
for <calsify@ietf.org>; Thu, 6 Jan 2022 00:33:25 -0500 (EST)
Received: from imap43 ([10.202.2.93])
by compute5.internal (MEProxy); Thu, 06 Jan 2022 00:33:25 -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=jz4RMSx
pvQzeXtTfTkT4dmFHZIAvYtgwD46mG1eA0LQ=; b=uKnRo2gQCyC7ljSoFjuuFev
jkJkOj36gD0WmGZuHEkfY80agE1XgfPIpfvbtlvZx+vi7x8GXAYNzfeQTOXsS0G8
ZLLev2CVWLeiwplVciOSr4/FGRbq2OeaRi1eTHT2e/PTfGU15D2tHYJj/Iacb3hT
gD2/rKXToVeyLHiHSPS+/LL2Qt9XP+X5UFE9ndII3Xx8RURtr07t9PMPWxo8fT9u
hglXf6EpuWdEF7jRvi1ga6cFk7t3c67G5zmTf1bwfI1RZ+CBhfGGOXkWAAyBtqVK
ecIRiiOLr7rnSTdEEFumtldGjWgI8v5tiIcpuWpevhYhUhCA1ZAgdpfao1U/G/A=
=
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=jz4RMS
xpvQzeXtTfTkT4dmFHZIAvYtgwD46mG1eA0LQ=; b=kTcAh5DmaJ3zzYKX1lFWOP
QMG4Z1Ckua82OzwAiX8aKza2VnrVgV8x6gCIpCTWPHkCLvQlJAlNZETdUCexZZ6U
fsvkCcHctaAWIZ7ja2MbLRWRwCgO/DPce/ZXi96TN+JZnBwjnQszoaMG/f8Sj9E/
a6LUbuEgAJpH4sLmq855HnD34tEUBsuKAGloK7jX4Ztutyem/3yRk0uZHgzi2E4X
QdfTcWugcH2OIfzI2tk5BPu7y7V/3mljvYH7Nmevjopv0iNPhJaXwMbj+BQXQOQW
Vbmunm7kCMc+KWeK+Fn7ahJ12TZckuRHOggAqQq9q9CC6NYGbxSeDxrxvMvuZa8Q
==
X-ME-Sender: <xms:JX_WYQkYxdbkhBIvC_f-l0XiHGk3ybVoApd6b4IWqywXn65_Irw06g>
<xme:JX_WYf1txcNw2M28veuGjJR6x8nPcL0luzImwSieb9VQ5YTvL2rDJh1RBUeEbEMYU
JvbwauUrSdAJA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudefkedgtdefucetufdoteggodetrfdotf
fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd
erreerreejnecuhfhrohhmpedfpfgvihhlucflvghnkhhinhhsfdcuoehnvghilhhjsehf
rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepffeukeejkeefhe
ehfeekfeekieelkeffvddufeetgfeihfejveelieeuveetuefhnecuffhomhgrihhnpehi
vghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh
hrohhmpehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:JX_WYep6fX46yiRQroUXnM_XawN5S7OKDpFIhFiM8b6RA3s9yK7IQQ>
<xmx:JX_WYcn9dhjQqZca0Ug7xdL3DYW5Q6PJnefc-pKzOcPbEfg_o57R4w>
<xmx:JX_WYe1oPNJHPFXRJrvaxie4Lvlq7EEehEYfeF4xZ2qZDDbgsZRdjw>
<xmx:JX_WYfAa87UJzHXpZ9lwoItl0FsOkRsyIkF6XUEPnPP8OJqYd3J1Qg>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
id 443E9AC0E99; Thu, 6 Jan 2022 00:33:25 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4526-gbc24f4957e-fm-20220105.001-gbc24f495
Mime-Version: 1.0
Message-Id: <6f410e94-6ccf-4309-bbf8-989356f13578@beta.fastmail.com>
In-Reply-To: <20220103182050.Horde.sYMd8P3bXgRD5RvdFf4KzOW@webmail.aegee.org>
References: <20220103182050.Horde.sYMd8P3bXgRD5RvdFf4KzOW@webmail.aegee.org>
Date: Thu, 06 Jan 2022 16:33:24 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=ec8717cbe04847ccb1488d5c5ac9f989
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Bswxc25HiunXFf69BWqDq55LgAw>
Subject: Re: [calsify]
=?utf-8?q?=C2=ABFor_a_given_pair_of_=22UID=22_and_=22S?=
=?utf-8?q?EQUENCE=22_property_values=2C_the_=22RECURRENCE-ID=22_value_for?=
=?utf-8?q?_a_recurrence_instance_is_fixed=2E=C2=BB?=
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Calendaring and Scheduling Standards Simplification <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, 06 Jan 2022 05:33:32 -0000
On Tue, 4 Jan 2022, at 5:20 AM, Dilyan Palauzov wrote: > https://datatracker.ietf.org/doc/html/rfc5545#page-113 says for > RECURRENCE-ID: «For a given pair of "UID" and "SEQUENCE" property > values, the "RECURRENCE-ID" value for a recurrence instance is fixed.» Given the text above, I'm pretty sure that "for a recurrence instance" means a specific instance of a recurring event. This seems a bit tautological to me, as the recurrence id by definition is unique for a specific recurrence instance of a particualr UID, regardless of SEQUENCE. I'm not sure what the authors really intended to say there, but my reading is this statement doesn't really mean anything. > Consider this iCalendar object: > > BEGIN:VCALENDAR > VERSION:2.0 > BEGIN:VEVENT > UID:123 > SEQUENCE:1 > DTSTART:20211201T221500Z > DTEND:20211201T223000Z > SUMMARY:ANNA NANA ANAN NANA > RRULE:FREQ=DAILY;COUNT=14 > END:VEVENT > BEGIN:VEVENT > UID:123 > SEQUENCE:2 > DTSTART:20211208T221500Z > DTEND:20211208T223000Z > SUMMARY:Exception > RECURRENCE-ID:20211208T221500Z > END:VEVENT > BEGIN:VEVENT > UID:123 > SEQUENCE:2 > DTSTART:20211213T103000Z > DTEND:20211213T230000Z > SUMMARY:Another exception > RECURRENCE-ID:20211213T221500Z > END:EVENT > END:VCALENDAR > > As can be seen, the last two VEVENTs have the same UID and SEQUENCE, > but different RECURRENCE-ID. So for a given UID and SEQUENCE, the > RECURRENCE-ID is not fixed in that file. > > Is the VCALENDAR valid or invalid? So based on the above, my view is that this is valid. —Neil
- [calsify] «For a given pair of "UID" and "SEQUENC… Dilyan Palauzov
- Re: [calsify] «For a given pair of "UID" and "SEQ… Neil Jenkins