From nobody Thu Jun 4 13:46:18 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D55EF1A92E4 for ; Thu, 4 Jun 2015 13:46:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.609 X-Spam-Level: X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 eX7Cuu_kEu0D for ; Thu, 4 Jun 2015 13:46:15 -0700 (PDT) Received: from smtpvbsrv1.mitre.org (smtpvbsrv1.mitre.org [198.49.146.234]) by ietfa.amsl.com (Postfix) with ESMTP id 0E16D1A92B4 for ; Thu, 4 Jun 2015 13:46:14 -0700 (PDT) Received: from smtpvbsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id BA939B2E371 for ; Thu, 4 Jun 2015 16:46:13 -0400 (EDT) Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpvbsrv1.mitre.org (Postfix) with ESMTP id AF2D5B2E351 for ; Thu, 4 Jun 2015 16:46:13 -0400 (EDT) Received: from imshyb02.MITRE.ORG (129.83.29.3) by IMCCAS03.MITRE.ORG (129.83.29.80) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 4 Jun 2015 16:46:13 -0400 Received: from imshyb02.MITRE.ORG (129.83.29.3) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Thu, 4 Jun 2015 16:46:13 -0400 Received: from na01-bn1-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1044.25 via Frontend Transport; Thu, 4 Jun 2015 16:46:13 -0400 Received: from CY1PR09MB0809.namprd09.prod.outlook.com (10.163.43.147) by CY1PR09MB0809.namprd09.prod.outlook.com (10.163.43.147) with Microsoft SMTP Server (TLS) id 15.1.184.17; Thu, 4 Jun 2015 20:46:12 +0000 Received: from CY1PR09MB0809.namprd09.prod.outlook.com ([10.163.43.147]) by CY1PR09MB0809.namprd09.prod.outlook.com ([10.163.43.147]) with mapi id 15.01.0184.014; Thu, 4 Jun 2015 20:46:12 +0000 From: "Anganes, Amanda L" To: Calsify Thread-Topic: Request for feedback/discussion Thread-Index: AQHQnwd9bOzkamuUvk2VR+nPYGe9gg== Date: Thu, 4 Jun 2015 20:46:11 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.5.0.150423 authentication-results: spf=none (sender IP is ) smtp.mailfrom=aanganes@mitre.org; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [192.160.51.87] x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR09MB0809; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(520003)(5005006)(3002001); SRVR:CY1PR09MB0809; BCL:0; PCL:0; RULEID:; SRVR:CY1PR09MB0809; x-forefront-prvs: 0597911EE1 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(84964002)(199003)(189002)(5002640100001)(122556002)(2900100001)(19580395003)(40100003)(229853001)(15975445007)(5001830100001)(5001860100001)(105586002)(87936001)(83506001)(106356001)(102836002)(64706001)(92566002)(86362001)(66066001)(19617315012)(450100001)(50986999)(46102003)(77096005)(36756003)(54356999)(189998001)(16236675004)(62966003)(77156002)(110136002)(99286002)(5001960100002)(4001350100001)(4001540100001)(107886002)(68736005)(106116001)(101416001)(2656002)(81156007)(97736004); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR09MB0809; H:CY1PR09MB0809.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts) Content-Type: multipart/alternative; boundary="_000_D196315030DC3aanganesmitreorg_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2015 20:46:11.8719 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB0809 X-OriginatorOrg: mitre.org Archived-At: Subject: [calsify] Request for feedback/discussion X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2015 20:46:17 -0000 --_000_D196315030DC3aanganesmitreorg_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi CalExt WG, We have two remaining drafts to finish, and discussion has slowed down late= ly. The two drafts are: Draft-ietf-calext-availability-00 and Draft-ietf-calext-extensions-00 Please review these two documents, and reply back to the WG with any commen= ts, questions, concerns, or to let us know if you think they're ready for W= G Last Call. Looking forward to hearing from you, -Amanda & Donald, CalExt Co-chairs --_000_D196315030DC3aanganesmitreorg_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <13D8801BD8438A4B9F507BFDE7048281@namprd09.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Hi CalExt WG,

We have two remaining drafts to finish, and discussion has slowed down= lately. The two drafts are:


Please review these two documents, and reply back to the WG with any c= omments, questions, concerns, or to let us know if you think they’re = ready for WG Last Call.

Looking forward to hearing from you,

—Amanda & Donald, CalExt Co-chairs

--_000_D196315030DC3aanganesmitreorg_-- From nobody Thu Jun 4 15:50:57 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09CAF1A886D for ; Thu, 4 Jun 2015 15:50:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.31 X-Spam-Level: X-Spam-Status: No, score=-2.31 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 5C30obFrgSLT for ; Thu, 4 Jun 2015 15:50:53 -0700 (PDT) Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.105.203]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 901991A8795 for ; Thu, 4 Jun 2015 15:50:53 -0700 (PDT) Received: from localhost.localdomain (cpe-76-180-151-43.buffalo.res.rr.com [76.180.151.43]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.8/8.14.8) with ESMTP id t54MopMb000878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Jun 2015 18:50:52 -0400 Message-ID: <5570D64B.5060306@andrew.cmu.edu> Date: Thu, 04 Jun 2015 18:50:51 -0400 From: Ken Murchison Organization: Carnegie Mellon University User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "Anganes, Amanda L" , Calsify References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------060207070701030509070004" X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.6.4.224216 X-SMTP-Spam-Clean: 28% ( SXL_IP_DYNAMIC 3, BODY_PARA_IS_SENTENCE_URL 0.1, BODYTEXTH_SIZE_10000_LESS 0, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_4000_4999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, REFERENCES 0, URI_ENDS_IN_HTML 0, __ANY_URI 0, __BAT_BOUNDARY 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_HTML 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_HTML 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __MOZILLA_USER_AGENT 0, __RDNS_POOLED_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TAG_EXISTS_HTML 0, __TO_MALFORMED_2 0, __URI_NS , __USER_AGENT 0) X-SMTP-Spam-Score: 28% X-Scanned-By: MIMEDefang 2.74 on 128.2.105.203 Archived-At: Subject: Re: [calsify] Request for feedback/discussion X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2015 22:50:56 -0000 This is a multi-part message in MIME format. --------------060207070701030509070004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Amanda, I sent out messages on April 7 concerning both these documents: http://www.ietf.org/mail-archive/web/calsify/current/msg02689.html http://www.ietf.org/mail-archive/web/calsify/current/msg02692.html Cyrus proposed some new clarifying text for draft-ietf-calext-extensions which probably needs to be posted as -01. I don't believe that my comments regarding draft-ietf-calext-availability have been addressed yet. On 06/04/2015 04:46 PM, Anganes, Amanda L wrote: > Hi CalExt WG, > > We have two remaining drafts to finish, and discussion has slowed down > lately. The two drafts are: > > Draft-ietf-calext-availability-00 > and > Draft-ietf-calext-extensions-00 > > > Please review these two documents, and reply back to the WG with any > comments, questions, concerns, or to let us know if you think they're > ready for WG Last Call. > > Looking forward to hearing from you, > > ---Amanda & Donald, CalExt Co-chairs > > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University --------------060207070701030509070004 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Amanda,

I sent out messages on April 7 concerning both these documents:

http://www.ietf.org/mail-archive/web/calsify/current/msg02689.html
http://www.ietf.org/mail-archive/web/calsify/current/msg02692.html

Cyrus proposed some new clarifying text for draft-ietf-calext-extensions which probably needs to be posted as -01.

I don't believe that my comments regarding draft-ietf-calext-availability have been addressed yet.



On 06/04/2015 04:46 PM, Anganes, Amanda L wrote:
Hi CalExt WG,

We have two remaining drafts to finish, and discussion has slowed down lately. The two drafts are:


Please review these two documents, and reply back to the WG with any comments, questions, concerns, or to let us know if you think they’re ready for WG Last Call.

Looking forward to hearing from you,

—Amanda & Donald, CalExt Co-chairs



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



-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
--------------060207070701030509070004-- From nobody Tue Jun 9 18:29:58 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C55C31A908D for ; Tue, 9 Jun 2015 18:29:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.691 X-Spam-Level: X-Spam-Status: No, score=0.691 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 TSoYUpKAq2-A for ; Tue, 9 Jun 2015 18:29:55 -0700 (PDT) Received: from resqmta-po-05v.sys.comcast.net (resqmta-po-05v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:164]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519D01A908C for ; Tue, 9 Jun 2015 18:29:55 -0700 (PDT) Received: from resomta-po-14v.sys.comcast.net ([96.114.154.238]) by resqmta-po-05v.sys.comcast.net with comcast id eRVE1q00258ss0Y01RVup7; Wed, 10 Jun 2015 01:29:54 +0000 Received: from THARE ([73.42.15.222]) by resomta-po-14v.sys.comcast.net with comcast id eRVu1q0064nTr3d01RVuNJ; Wed, 10 Jun 2015 01:29:54 +0000 From: "Tim Hare" To: Date: Tue, 9 Jun 2015 21:29:50 -0400 Message-ID: <021e01d0a31c$f1fee510$d5fcaf30$@net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_021F_01D0A2FB.6AED4510" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdCjHPGT1DN9p95JQ2enPGPWBp4i/Q== Content-Language: en-us DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1433899794; bh=iNsnEGZRaM0XwMpBzQiO9vbwhL61ukieiyg1lS1mYOw=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=kARdo7XZw8XDBzrMo7Ldxh16R7KO9qeprriHbl6+bmy0/tUzsFfrxUjAF1nL6LYvt iy2/462Czw+/cMVAbyKjZOtX5D8qjsk1Zqb1u6zUQWi9Bjy6rwvWef39eI5e6Zt0pT J32zvX1o2cw1Zlc3TlR4fUC7ZcGBnzuEWaGVt4S8pR68rbD9nJWRponxPbbBP+0QsM TeTsWDswyz2qtIoUhoXh/xmBW8yznAm4HfAWe5Z59uHHszUIw5SeTrmUkxgchB++6Y sITPqPbsNlcqwwy+pkiOX/BU3RK4gAWQAJDZDBKygXDk+JTaMr6MJXfQ6MMSEw4j4n 3ytjbRqWy9mlQ== Archived-At: Subject: [calsify] Persistent UID? X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 01:29:56 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_021F_01D0A2FB.6AED4510 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit This came up on the caldeveloper list. Someone's client is downloading events, and the events change UID with each download; I am guessing the UIDs are regenerated each time the file is created. I looked at RFC 5545 and didn't see any requirement for persistence of a UID for a particular VEVENT or other calendar object. Is this something that should be addressed? At the very least should there be a statement that the UID for a calendar component SHOULD persist for the life of the event? Tim Hare Interested Bystander, Non-Inc. ------=_NextPart_000_021F_01D0A2FB.6AED4510 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This came = up on the caldeveloper list.   Someone's client is downloading = events, and the events change UID with each download;  I am = guessing the UIDs are regenerated each time the file is created. =   I looked at RFC 5545 and didn't see any requirement for = persistence of a UID for a particular VEVENT or other calendar = object.   Is this something that should be addressed?  At = the very least should there be a statement that the UID for a calendar = component SHOULD persist for the life of the event?

 

Tim = Hare
Interested Bystander, Non-Inc.

 

 

------=_NextPart_000_021F_01D0A2FB.6AED4510-- From nobody Tue Jun 9 21:46:54 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D527F1A912C for ; Tue, 9 Jun 2015 21:46:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.51 X-Spam-Level: X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham 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 aK3XSSvUDbxJ for ; Tue, 9 Jun 2015 21:46:52 -0700 (PDT) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 243591A1A94 for ; Tue, 9 Jun 2015 21:46:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4419; q=dns/txt; s=iport; t=1433911612; x=1435121212; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=5JZzmLR8pyGAV75KGoN+Iyrk8BjrUQbRM3G/JWGzU88=; b=DzDv7izU1Xbty9ZCDqB9UmQm90SuHUDe3G8zC9SMayc8u9cSBU54xjMD ubykSSYLYeic/zfpkn1NDr4VjPeGgmPcpcLw0ubKf6KwOZ/7EjZiEBknE IRDrYhxakXmiqsOgEBA1EGlkND5FraGH0mHXVh2DhNiBs18GZNcIV2M9q 4=; X-Files: signature.asc : 481 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DnBAAswHdV/xbLJq1cgkWFHLtrh1wCggETAQEBAQEBAYEKhCMBAQEDIwpLEQsEFAkWCwICCQMCAQIBRQYBDAgBARWIFa0PpBQBAQEBAQEBAQEBAQEBAQEBAQEBAQEXi0OFDYJogUUBBJVagUmHUIgMj2ckYoEoHIFUPIJ4AQEB X-IronPort-AV: E=Sophos;i="5.13,585,1427760000"; d="asc'?scan'208,217";a="538190669" Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 10 Jun 2015 04:46:50 +0000 Received: from [10.61.106.232] (dhcp-10-61-106-232.cisco.com [10.61.106.232]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t5A4knVG022285; Wed, 10 Jun 2015 04:46:50 GMT Message-ID: <5577C13B.2040703@cisco.com> Date: Wed, 10 Jun 2015 06:46:51 +0200 From: Eliot Lear User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Tim Hare , calsify@ietf.org References: <021e01d0a31c$f1fee510$d5fcaf30$@net> In-Reply-To: <021e01d0a31c$f1fee510$d5fcaf30$@net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XdirPt55IFWa1uh81khjWwubxxPbbDldM" Archived-At: Subject: Re: [calsify] Persistent UID? X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 04:46:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XdirPt55IFWa1uh81khjWwubxxPbbDldM Content-Type: multipart/alternative; boundary="------------030701060700080301050304" This is a multi-part message in MIME format. --------------030701060700080301050304 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, On 6/10/15 3:29 AM, Tim Hare wrote: > > This came up on the caldeveloper list. Someone's client is > downloading events, and the events change UID with each download; I > am guessing the UIDs are regenerated each time the file is created. > I looked at RFC 5545 and didn't see any requirement for persistence > of a UID for a particular VEVENT or other calendar object. Is this > something that should be addressed? At the very least should there be > a statement that the UID for a calendar component SHOULD persist for > the life of the event? > > That's just bizarre. Anyone know their logic? Eliot --------------030701060700080301050304 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,

On 6/10/15 3:29 AM, Tim Hare wrote:

This came up on the caldeveloper list.=C2=A0= =C2=A0 Someone's client is downloading events, and the events change UID with each download;=C2=A0 I am guessing the UIDs are regenerated each time the file is created. =C2=A0=C2=A0I looked= at RFC 5545 and didn't see any requirement for persistence of a UID for a particular VEVENT or other calendar object.=C2=A0=C2=A0 I= s this something that should be addressed?=C2=A0 At the very least sho= uld there be a statement that the UID for a calendar component SHOULD persist for the life of the event?



That's just bizarre.=C2=A0 Anyone know their logic?

Eliot
--------------030701060700080301050304-- --XdirPt55IFWa1uh81khjWwubxxPbbDldM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 iQEcBAEBCAAGBQJVd8E7AAoJEIe2a0bZ0nozBtMIAMawC4WPD6bofAT4KJDyMicR dvvkRrHQQHl/DGhnT01R6EdlX29WVIbD8RKWXxTp8PUnTwcZ/gLfU17toLGvfqWv Z0Lqbv95rv1wuEkk/Bi8Nz5Ikxt5RpvjiHxXUD+oj+KU3C4YLNqOmEj83Y4lPzNr cTQtO+3TSS+dGObozVp8nw0pNSFZd8ElsCIx0qmB6ute2k1u8lvQlzRbUXDe30ex W7p72GzCX0hdj4Acza6W1Y3IyT3swWk+vGX4j2LHsFVOmGFgTVepcJ3i+Bt3D+j1 7J2O4bo4CSXxC3BTEhZU3qCZ6PotjSlIBQ4JRMQIRr2/Tjgx//t9/bU4pp+d2tI= =K4Pg -----END PGP SIGNATURE----- --XdirPt55IFWa1uh81khjWwubxxPbbDldM-- From nobody Tue Jun 9 23:57:56 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16E1E1A1BB4 for ; Tue, 9 Jun 2015 23:57:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.277 X-Spam-Level: X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 PULEWL_8eUUU for ; Tue, 9 Jun 2015 23:57:53 -0700 (PDT) Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) (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 786051A1B53 for ; Tue, 9 Jun 2015 23:57:53 -0700 (PDT) Received: by yhak3 with SMTP id k3so16820830yha.2 for ; Tue, 09 Jun 2015 23:57:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Ek6J3AHRMnqz4UVk7GxDztbIU7/EmuJZV2XTpHtyRhY=; b=n5SRoBCayxOukfqR2NF89XlTsYxCDyOjRSTVJbw2O2irX1pRDXpinRmUjCgJ/yR/w4 I4/2oCeqoPnKIkKn9e99XmKPXr0o9/1bPcMVpsdDafd2Ucsuci3B2LPCH3Pg7KQE2BT9 loQGbAEyZ8582AemULFBcUXNnB1ej7me8SPJAEQLf3PhWNX7fxmJLxatx4m2dZyH60+g Gwk2OtRvxp6ttkb0IEN5j617r10bAMLwRR4YuJh8DHQrPGkNd5stVKYkiNUafI9v4+6o gNrs3OFPkiLbeX7tvQe70zn1TuuA5tZ9DpHJ076h3x6bj7YoOgYnNhp7jBfAz3oNKNHd tS3g== MIME-Version: 1.0 X-Received: by 10.170.79.5 with SMTP id v5mr1995349ykv.52.1433919472881; Tue, 09 Jun 2015 23:57:52 -0700 (PDT) Sender: quillaud@gmail.com Received: by 10.129.86.84 with HTTP; Tue, 9 Jun 2015 23:57:52 -0700 (PDT) In-Reply-To: <021e01d0a31c$f1fee510$d5fcaf30$@net> References: <021e01d0a31c$f1fee510$d5fcaf30$@net> Date: Wed, 10 Jun 2015 08:57:52 +0200 X-Google-Sender-Auth: MvgiC7Xw1k3p98DLmsVOYbZubcU Message-ID: From: Arnaud Quillaud To: Tim Hare Content-Type: multipart/alternative; boundary=001a113a08a2d157c705182464f8 Archived-At: Cc: calsify@ietf.org Subject: Re: [calsify] Persistent UID? X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 06:57:55 -0000 --001a113a08a2d157c705182464f8 Content-Type: text/plain; charset=UTF-8 On Wed, Jun 10, 2015 at 3:29 AM, Tim Hare wrote: > This came up on the caldeveloper list. Someone's client is downloading > events, and the events change UID with each download; I am guessing the > UIDs are regenerated each time the file is created. I looked at RFC 5545 > and didn't see any requirement for persistence of a UID for a particular > VEVENT or other calendar object. Is this something that should be > addressed? At the very least should there be a statement that the UID for > a calendar component SHOULD persist for the life of the event? > Well, as far as I can see, it is there in the definition of the UID property itself: << Purpose: This property defines the persistent, globally unique identifier for the calendar component. >> (https://tools.ietf.org/html/rfc5545#section-3.8.4.7) Arnaud Quillaud > > > Tim Hare > Interested Bystander, Non-Inc. > > > > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify > > --001a113a08a2d157c705182464f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Jun 10, 2015 at 3:29 AM, Tim Hare <TimHare@comcast.net&g= t; wrote:

T= his came up on the caldeveloper list.=C2=A0=C2=A0 Someone's client is d= ownloading events, and the events change UID with each download;=C2=A0 I am= guessing the UIDs are regenerated each time the file is created. =C2=A0=C2= =A0I looked at RFC 5545 and didn't see any requirement for persistence = of a UID for a particular VEVENT or other calendar object.=C2=A0=C2=A0 Is t= his something that should be addressed?=C2=A0 At the very least should ther= e be a statement that the UID for a calendar component SHOULD persist for t= he life of the event?


Well,= as far as I can see, it is there in the=C2=A0 definition of the UID proper= ty itself:

<<
   Purpose:  This property de=
fines the persistent, globally unique
      identifier for the calendar component.

>>=C2=A0 (https://tools.ie= tf.org/html/rfc5545#section-3.8.4.7)


A= rnaud Quillaud
<= div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">

=C2=A0

Tim Hare
Interested Bystander, Non-Inc.

=

=C2=A0

=C2=A0


__________________________= _____________________
calsify mailing list
calsify@ietf.org<= br> https://www.ietf.org/mailman/listinfo/calsify


--001a113a08a2d157c705182464f8-- From nobody Wed Jun 10 06:50:51 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 027201B2A45 for ; Wed, 10 Jun 2015 06:50:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.788 X-Spam-Level: X-Spam-Status: No, score=0.788 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 1rUEIyHVQ3gp for ; Wed, 10 Jun 2015 06:50:48 -0700 (PDT) Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07D751B2A44 for ; Wed, 10 Jun 2015 06:50:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 221F9160A273; Wed, 10 Jun 2015 09:50:45 -0400 (EDT) X-Virus-Scanned: amavisd-new at example.com Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxXogCEERJqg; Wed, 10 Jun 2015 09:50:45 -0400 (EDT) Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 6547B160A268; Wed, 10 Jun 2015 09:50:44 -0400 (EDT) Date: Wed, 10 Jun 2015 09:50:41 -0400 From: Cyrus Daboo To: Tim Hare , calsify@ietf.org Message-ID: <91A6CF7AD17CBC20BC3DC983@caldav.corp.apple.com> In-Reply-To: <021e01d0a31c$f1fee510$d5fcaf30$@net> References: <021e01d0a31c$f1fee510$d5fcaf30$@net> X-Mailer: Mulberry/4.1.0b1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1005 Archived-At: Subject: Re: [calsify] Persistent UID? X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 13:50:49 -0000 Hi Tim, --On June 9, 2015 at 9:29:50 PM -0400 Tim Hare wrote: > This came up on the caldeveloper list. Someone's client is downloading > events, and the events change UID with each download; I am guessing the > UIDs are regenerated each time the file is created. I looked at RFC 5545 > and didn't see any requirement for persistence of a UID for a particular > VEVENT or other calendar object. Is this something that should be > addressed? At the very least should there be a statement that the UID > for a calendar component SHOULD persist for the life of the event? One of the things CalConnect is working on is a "developer's guide" document that will cover a lot of "best practices" (such as maintaining a persistent UID), as well as explanation of some of the iCalendar features that often trip people up (obvious ones being time zones and recurrences). Some of that could certainly feed into any future updates to iCalendar that the IETF does. -- Cyrus Daboo From nobody Wed Jun 10 07:13:32 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1420E1B2ACA for ; Wed, 10 Jun 2015 07:13:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.79 X-Spam-Level: X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 Swvb0ODwafdb for ; Wed, 10 Jun 2015 07:13:30 -0700 (PDT) Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79CAB1B2ACC for ; Wed, 10 Jun 2015 07:13:30 -0700 (PDT) Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 920E92916 for ; Wed, 10 Jun 2015 07:13:29 -0700 (PDT) Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.ucolick.org (Postfix) with ESMTP id 8E9F9290F for ; Wed, 10 Jun 2015 07:13:29 -0700 (PDT) Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (8.14.4/8.13.8) with ESMTP id t5AEDTxp002087 for ; Wed, 10 Jun 2015 07:13:29 -0700 Received: (from sla@localhost) by geneva.ucolick.org (8.14.4/8.14.4/Submit) id t5AEDTQ9002086 for calsify@ietf.org; Wed, 10 Jun 2015 07:13:29 -0700 Date: Wed, 10 Jun 2015 07:13:29 -0700 From: Steve Allen To: calsify@ietf.org Message-ID: <20150610141328.GD2035@ucolick.org> References: <021e01d0a31c$f1fee510$d5fcaf30$@net> <91A6CF7AD17CBC20BC3DC983@caldav.corp.apple.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <91A6CF7AD17CBC20BC3DC983@caldav.corp.apple.com> User-Agent: Mutt/1.5.20 (2009-12-10) Archived-At: Subject: Re: [calsify] Persistent UID? X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 14:13:32 -0000 On Wed 2015-06-10T09:50:41 -0400, Cyrus Daboo hath writ: > --On June 9, 2015 at 9:29:50 PM -0400 Tim Hare wrote: > >This came up on the caldeveloper list. Someone's client is downloading > >events, and the events change UID with each download; I am guessing the > >UIDs are regenerated each time the file is created. I was guilty of this for events generated by a webserver from a database. The toolkit for constructing VEVENT objects added its own UID if that method was not invoked. I would never have noticed if I had not seen my calendar client running slow enough to see the repainting of every event. I fixed after identifying suitable primary keys and date stamps from the records where the components of the event are stored. > One of the things CalConnect is working on is a "developer's guide" > document that will cover a lot of "best practices" +1 -- Steve Allen WGS-84 (GPS) UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m From nobody Thu Jun 11 01:40:33 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F66C1B2D7A for ; Thu, 11 Jun 2015 01:40:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 YMSwQ5gDXfJd for ; Thu, 11 Jun 2015 01:40:26 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 752ED1B2D63 for ; Thu, 11 Jun 2015 01:40:26 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 57529209BE for ; Thu, 11 Jun 2015 04:40:24 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute5.internal (MEProxy); Thu, 11 Jun 2015 04:40:25 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:reply-to:subject:to:x-sasl-enc:x-sasl-enc; s= mesmtp; bh=vjSe2idPJaQGtHNn1djzOSrhWrk=; b=oK2K1vDERDtqfih3tBkks oFAkcQwmCYQqfMLgzaC0TC6tnFWzACaiJD9c1QpanaqQooljo5aTIkwwo3JTQkIG fjJegWqYdrIn0R6JF4hBOJtMDEIGk/dbMkFQmUdMsEhA7YjmIluHbYCvji3F8FpE Hj1v1YNy+0nYMFHC6Ni1IE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:reply-to:subject:to :x-sasl-enc:x-sasl-enc; s=smtpout; bh=vjSe2idPJaQGtHNn1djzOSrhWr k=; b=R6b9E7F779Hd+kWWHKQV38O4XOgMw0DnD4zKzQdGAGTTRoaOUZMktlHSUU 12s2ycwZ4zFN3/SJ2tUlj0oXiStyaPnC3QYeGEwxF9Ueryz3mlmZDvUBjtEcL8bx sSRKkeiQMwJAIxtxFHnv3dYrQQwqOSwCoHBJd/Sg/Gtg/c4Gg= Received: by web2.nyi.internal (Postfix, from userid 99) id B92A7540192; Thu, 11 Jun 2015 04:40:24 -0400 (EDT) Message-Id: <1434012024.1199990.292612161.2CD0F5DA@webmail.messagingengine.com> X-Sasl-Enc: YStktyuAc+O5GfM0rLkeqYK6hWbDNc26nYGNCVLjBcTp 1434012024 From: Alfie John To: calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ff004c4b Date: Thu, 11 Jun 2015 18:40:24 +1000 Archived-At: Subject: [calsify] Clarificaton on cancelling events with recurrence instances X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: alfiej@fastmail.fm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2015 08:40:31 -0000 Hi list, I'm a bit confused by some possible ambiguity in RFC 5546. From section 3.2.5. CANCEL: "To cancel the complete range of a recurring event, the "UID" property value for the event MUST be specified and a "RECURRENCE-ID" MUST NOT be specified in the "CANCEL" method." If a CANCEL message has the following: BEGIN:VEVENT UID:FOO SUMMARY:ABC ... END:VEVENT BEGIN:VEVENT UID:FOO SUMMARY:XYZ RECURRENCE-ID:20150621T220000Z ... END:VEVENT as there is a RECURRENCE-ID in the second VEVENT, my reading from above means that only the recurrence instance should be deleted and not the complete range. However, the table below it: - RECURRENCE-ID - 0 or 1 - Only if referring to an instance of a recurring calendar component. Otherwise, it MUST NOT be present. as this event was produced by Outlook 2013 when doing a "delete entire series", I'm now thinking that it's a bug in my understanding. Trying to fit this into my new mental model, I'm now reading this as: - For each VEVENT in the CANCEL message, delete the event - There are two VEVENTS (the recurrence instance, and the range) - Delete the event corresponding to the recurrence instance - Delete the event corresponding to the range This matches with how Outlook produces "delete occurrence" CANCEL messages (note that the following VEVENT does not have the complete event definition which is allowed from RFC 4791 section 4.1: BEGIN:VEVENT UID:FOO SUMMARY:XYZ RECURRENCE-ID:20150621T220000Z ... END:VEVENT In other words from my new mental model: - For each VEVENT in the CANCEL message, delete the event - There is only one VEVENT (the recurrence instance) - Delete the event corresponding to the recurrence instance Is this how it should work, or should Outlook _not_ be including recurrence instance VEVENTs within a "delete entire series" message? Hopefully this all makes sense... Alfie -- Alfie John alfiej@fastmail.fm From nobody Thu Jun 11 07:03:26 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68B801AD353 for ; Thu, 11 Jun 2015 07:03:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.013 X-Spam-Level: X-Spam-Status: No, score=-0.013 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 fIw_tfVgEIq6 for ; Thu, 11 Jun 2015 07:03:24 -0700 (PDT) Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E746B1AD34F for ; Thu, 11 Jun 2015 07:03:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 32F761623794; Thu, 11 Jun 2015 10:03:23 -0400 (EDT) X-Virus-Scanned: amavisd-new at example.com Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4TlHzObQyCRU; Thu, 11 Jun 2015 10:03:22 -0400 (EDT) Received: from [17.45.162.247] (unknown [17.45.162.247]) by daboo.name (Postfix) with ESMTPSA id 420051623789; Thu, 11 Jun 2015 10:03:21 -0400 (EDT) Date: Thu, 11 Jun 2015 10:03:19 -0400 From: Cyrus Daboo To: alfiej@fastmail.fm, calsify@ietf.org Message-ID: <57905DFC53A37C267A221BC7@cyrus.local> In-Reply-To: <1434012024.1199990.292612161.2CD0F5DA@webmail.messagingengine.com> References: <1434012024.1199990.292612161.2CD0F5DA@webmail.messagingengine.com> X-Mailer: Mulberry/4.1.0b1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1292 Archived-At: Subject: Re: [calsify] Clarificaton on cancelling events with recurrence instances X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2015 14:03:25 -0000 Hi Alfie, --On June 11, 2015 at 6:40:24 PM +1000 Alfie John wrote: > Is this how it should work, or should Outlook _not_ be including > recurrence > instance VEVENTs within a "delete entire series" message? I think the following can safely be used when processing a CANCEL message: 1) If the master component (the one without a RECURRENCE-ID and with the RRULE/RDATE/EXDATE properties) is present, cancel ALL instances of the event on the attendee's side, irrespective of whether any overridden instances (the ones with RECURRENCE-ID) are present in the CANCEL. 2) If the CANCEL contains only overridden components (ones with a RECURRENCE-ID property), cancel just those instances on the attendee's side. #2 is covered by item (b) in Section 3.2.5 of 5546. #1 is a variation on the "strict" requirement of Section 3.2.5 that says to cancel an entire series the RECURRENCE-ID MUST NOT be present. #1 loosens the restriction by allowing overridden components to be present - something that it seems you observed coming from Outlook. That said, from the perspective of a client generating a CANCEL message, it really should follow the spec and use the strict behavior for canceling the entire event (i.e., just send the master component). -- Cyrus Daboo From nobody Thu Jun 11 15:09:08 2015 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D07791B321F for ; Thu, 11 Jun 2015 15:09:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 D795tUCu6v2P for ; Thu, 11 Jun 2015 15:09:06 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 752AF1B31E9 for ; Thu, 11 Jun 2015 15:06:47 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 315A520F35 for ; Thu, 11 Jun 2015 18:06:45 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute5.internal (MEProxy); Thu, 11 Jun 2015 18:06:45 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:reply-to:subject:to :x-sasl-enc:x-sasl-enc; s=mesmtp; bh=SU81UubV3RtuTZvX8pFtmiufGuQ =; b=qGZ+rX+cyqVUYkpDHIL/hQwQ/EnXDMilKvuYtAIB27u3xOjBBfxtoUU57yI 8oaILQHL4IrnsSUSHaWcWOPUwWZyeOX4QHaPPllJ56TlBVKoDTt+GcwNPCsuiBOU YskAln9gDL65AflAmw9oL1/SOxps8B84WLvtdrB0g3agyGtA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :reply-to:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=SU81Uu bV3RtuTZvX8pFtmiufGuQ=; b=jyxtHE8n5ITQAiYdXbffhOzFFcatpF7vJ4qWpB i38nn8ADqT5UAHGdK2uqkgZfgXUUuiEC2BwrdqcvZSbVIb9RCUrlztZidU4jo3iR yCktGJ1UBOA1CsuZTT1rv99R0jbPeCkxDMNr/5Fi0ahVJRoZPOqjo93LKEvjOXSf 5WOCg= Received: by web4.nyi.internal (Postfix, from userid 99) id 07D61110F0F; Thu, 11 Jun 2015 18:06:45 -0400 (EDT) Message-Id: <1434060404.3665369.293371577.69BF0454@webmail.messagingengine.com> X-Sasl-Enc: aWC4snVNAqMiiTcjJfmtziqVHzbv6rdbfuQkTVPdQ/5N 1434060404 From: Alfie John To: Cyrus Daboo , calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ff004c4b Date: Fri, 12 Jun 2015 08:06:44 +1000 In-Reply-To: <57905DFC53A37C267A221BC7@cyrus.local> References: <1434012024.1199990.292612161.2CD0F5DA@webmail.messagingengine.com> <57905DFC53A37C267A221BC7@cyrus.local> Archived-At: Subject: Re: [calsify] Clarificaton on cancelling events with recurrence instances X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: alfiej@fastmail.fm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2015 22:09:08 -0000 Hey Cyrus, On Fri, Jun 12, 2015, at 12:03 AM, Cyrus Daboo wrote: > I think the following can safely be used when processing a CANCEL > message: Awesome, exactly what I needed. > That said, from the perspective of a client generating a CANCEL message, > it really should follow the spec and use the strict behavior for canceling > the entire event (i.e., just send the master component). Thanks for that. This looks all clear now. Much appreciated! Alfie -- Alfie John alfiej@fastmail.fm