From nobody Tue Jan 15 05:11:29 2019 Return-Path: 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 47F5C130E58 for ; Tue, 15 Jan 2019 05:11:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 V9LGa2gANCn5 for ; Tue, 15 Jan 2019 05:11:26 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A3DB130E57 for ; Tue, 15 Jan 2019 05:11:26 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 0B794B82439; Tue, 15 Jan 2019 05:11:24 -0800 (PST) To: bernard.desruisseaux@oracle.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, lear@cisco.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: cabo@tzi.org, calsify@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20190115131124.0B794B82439@rfc-editor.org> Date: Tue, 15 Jan 2019 05:11:24 -0800 (PST) Archived-At: Subject: [calsify] [Technical Errata Reported] RFC5545 (5602) X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2019 13:11:28 -0000 The following errata report has been submitted for RFC5545, "Internet Calendaring and Scheduling Core Object Specification (iCalendar)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5602 -------------------------------------- Type: Technical Reported by: Carsten Bormann Section: 3.1.3 Original Text ------------- ATTACH;FMTTYPE=text/plain;ENCODING=BASE64;VALUE=BINARY:VGhlIH F1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4 Corrected Text -------------- ATTACH;FMTTYPE=text/plain;ENCODING=BASE64;VALUE=BINARY:VGhlIH F1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4= Notes ----- The base64 text used in the example misses the base64 padding. RFC 5545 appears to be using base64 according to RFC 4648 Section 4 with padding throughout, except for this example. (The corrected text decodes to "The quick brown fox jumps over the lazy dog.") Beyond temporary confusion in implementers, it is possible that this example will turn up in a test suite and ultimately cause unnecessarily lenient behavior of decoders ("soup"); it should be either clarified that this lenient behavior is not the intention or the behavior should be codified. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5545 (draft-ietf-calsify-rfc2445bis-10) -------------------------------------- Title : Internet Calendaring and Scheduling Core Object Specification (iCalendar) Publication Date : September 2009 Author(s) : B. Desruisseaux, Ed. Category : PROPOSED STANDARD Source : Calendaring and Scheduling Standards Simplification Area : Applications Stream : IETF Verifying Party : IESG From nobody Tue Jan 15 05:47:38 2019 Return-Path: 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 82F1A130E58 for ; Tue, 15 Jan 2019 05:47:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.853 X-Spam-Level: X-Spam-Status: No, score=-8.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 g7JYq5NzxIAK for ; Tue, 15 Jan 2019 05:47:34 -0800 (PST) Received: from userp2120.oracle.com (userp2120.oracle.com [156.151.31.85]) (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 8594D130DE3 for ; Tue, 15 Jan 2019 05:47:34 -0800 (PST) Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id x0FDhv3C025297; Tue, 15 Jan 2019 13:47:29 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2018-07-02; bh=8TtNtGEMUFrwh36H/lRpsn14VzoLLPGDDjf6tlEiqdM=; b=uS14jtYKZ+3NGLr87kmHwqVxEGYiJP1mwXhew9KQkUl18ycRSc3YTi9GZkVpXSdJQcmY k4SXRbgh1g5kRYTij6ibV/F2uWnwy9ryfOEL3qkgEWCGi7bInuOEg4boPIANRK+6oXuk h/EXZT0JDXR1Djmt7rYReS7aDVPT1D0h/61P6jfoJGc9m+AzO7bbiaQaQdZO3JDfVzfn +zPj7y8pDuVNTHwW7YZzYbuNSdOB4M4DbVhIAYPlXig4KcYeGzlSzutQloSEvz9H47Lv mc82ytbzzDFG3hovenZQ/vWIhyzh2FZ1e3BLSnp8bxBEFgF9ZmFXtiSwlO7+mxpsFFjX Wg== Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp2120.oracle.com with ESMTP id 2pybjs3wb9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 15 Jan 2019 13:47:29 +0000 Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id x0FDlNDB013182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 15 Jan 2019 13:47:23 GMT Received: from abhmp0012.oracle.com (abhmp0012.oracle.com [141.146.116.18]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id x0FDlKMt030192; Tue, 15 Jan 2019 13:47:21 GMT Received: from dhcp-10-156-44-246.ca.oracle.com (/10.156.44.246) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 15 Jan 2019 05:47:20 -0800 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Bernard Desruisseaux In-Reply-To: <20190115131124.0B794B82439@rfc-editor.org> Date: Tue, 15 Jan 2019 08:47:24 -0500 Cc: ben@nostrum.com, Alexey Melnikov , adam@nostrum.com, Eliot Lear , Carsten Bormann , IETF Calsify Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190115131124.0B794B82439@rfc-editor.org> To: RFC Errata System X-Mailer: Apple Mail (2.3124) X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9136 signatures=668680 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=856 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901150115 Archived-At: Subject: Re: [calsify] [Technical Errata Reported] RFC5545 (5602) X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2019 13:47:36 -0000 Carsten is correct. This errata should be approved. > Le 15 janv. 2019 =C3=A0 08:11, RFC Errata System = a =C3=A9crit : >=20 > The following errata report has been submitted for RFC5545, > "Internet Calendaring and Scheduling Core Object Specification = (iCalendar)". >=20 > -------------------------------------- > You may review the report below and at: > = https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.rfc-2Deditor.org= _errata_eid5602&d=3DDwIBaQ&c=3DRoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE= &r=3D1KWjrk6WfltMq-xNvZw71GcUXlVStaOFvtc__OOO9f8&m=3DOPBWsu184D78UF-keK1yO= sOPaJ4sEtBNL6i4XDAUzHE&s=3Di8ZHje_e-qR9q5M2GBnZpVoywotcMWvFsx1UW1MM-Ec&e=3D= >=20 > -------------------------------------- > Type: Technical > Reported by: Carsten Bormann >=20 > Section: 3.1.3 >=20 > Original Text > ------------- > ATTACH;FMTTYPE=3Dtext/plain;ENCODING=3DBASE64;VALUE=3DBINARY:VGhlIH > F1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4 >=20 >=20 > Corrected Text > -------------- > ATTACH;FMTTYPE=3Dtext/plain;ENCODING=3DBASE64;VALUE=3DBINARY:VGhlIH > F1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4=3D >=20 >=20 > Notes > ----- > The base64 text used in the example misses the base64 padding. RFC = 5545 appears to be using base64 according to RFC 4648 Section 4 with = padding throughout, except for this example. (The corrected text = decodes to "The quick brown fox jumps over the lazy dog.") Beyond = temporary confusion in implementers, it is possible that this example = will turn up in a test suite and ultimately cause unnecessarily lenient = behavior of decoders ("soup"); it should be either clarified that this = lenient behavior is not the intention or the behavior should be = codified. >=20 > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party =20 > can log in to change the status and edit the report, if necessary.=20 >=20 > -------------------------------------- > RFC5545 (draft-ietf-calsify-rfc2445bis-10) > -------------------------------------- > Title : Internet Calendaring and Scheduling Core Object = Specification (iCalendar) > Publication Date : September 2009 > Author(s) : B. Desruisseaux, Ed. > Category : PROPOSED STANDARD > Source : Calendaring and Scheduling Standards = Simplification > Area : Applications > Stream : IETF > Verifying Party : IESG From nobody Wed Jan 16 19:36:57 2019 Return-Path: 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 0EE64130F4D for ; Wed, 16 Jan 2019 19:36:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.983 X-Spam-Level: X-Spam-Status: No, score=-1.983 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, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=vWYtwXo7; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=TOoByRIO 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 KQWSarkjlAUu for ; Wed, 16 Jan 2019 19:36:55 -0800 (PST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0CF412785F for ; Wed, 16 Jan 2019 19:36:54 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 34E2D13E6 for ; Wed, 16 Jan 2019 22:36:54 -0500 (EST) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Wed, 16 Jan 2019 22:36:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=message-id:date:from:to:subject :content-type; s=fm1; bh=57515LU3BdBX1keItJAJw1zSWytI004haSQfc51 0j6w=; b=vWYtwXo72yFCrj3/XxAZXDIpL7aCi+b9OvHpdPr5O3TCj9nC9Ck49H2 0+3rnkFrKhznLM5cKjBDDuebmgGzsTBM2q1PZq3R8U/JTqWWd2B5q4exi7oF85fD MCV1fpa+80VF2Yh9GNQwzMfJpsRzKJSqArxOuoXGMwhdluspKPf0xFIP4sXQM2Ol fTAvjVvYqVzo42VQ1AiFZRmVKBj21F8nAKxdaU5oqCAfR2eA5jT564yZHtRrvw+q BnpkcwS8p1N6cIk1v8zkHkJ3ba6XKmc1RxQutJK8HnckIaE0v/ykGQLXr2xgEu5z AwLv2cP0otgyxTxQLclEKlaX3aKwUNg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id:subject :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=57515LU3BdBX1keItJAJw1zSWytI004haSQfc510j6w=; b=TOoByRIO TH4v0ERudGDcYeJMY2bDVX+H43SLkRzQ78qR4AoPJTEVbtVnjFWDeeDuGJZZhT2J 8lXeV8TkSHTQGE4Givfq5bDd7PCC/JIQOBDdFiRdd44gjjJd24QnwyuSPZgy1AX1 lJVh74+Ja+xO+SjqxsV6BSzhdbC/Kj+MnEE/Y7Lb8gvPl9TUsSPj7TCWMYLhQw8M dZRShvSINI02csVlXwE5rRydhsl6gwJieZAkrWexyl3k5o8u/b21Znj4I44b2elW ZXSTAXISQdaSZIpixiEL4etqP95v84ecyqlHs5+mL9XDmCxONxAFzKGPyLHcDaVh P8/mXK0NAi9oCg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgeeigdeitdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucenucfjughrpefofgfkfffhvffutgesrgdtreerreertdenucfhrhhomhepfdeurh honhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtgho mheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvg grmhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6DBF02042D; Wed, 16 Jan 2019 22:36:53 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.5-761-gc103c9b-fmstable-20190103v1bis X-Me-Personality: 56629417 Message-Id: <05fe96b8-bed0-4379-bce7-0f2d7f839f81@beta.fastmail.com> Date: Wed, 16 Jan 2019 22:36:53 -0500 From: "Bron Gondwana" To: calsify@ietf.org Content-Type: multipart/alternative; boundary=15c5c17390b44ed6a49877c80336cfce Archived-At: Subject: [calsify] Going to be at CalConnect in Zurich in a couple of weeks X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 03:36:56 -0000 --15c5c17390b44ed6a49877c80336cfce Content-Type: text/plain Hello all, I'm your new co-chair! If you've been coming to CalConnect for a while, you might know me from there. I've missed a few recently due to all my other commitments, but I will get these two in a row at least. You may have heard that CalConnect has also started working more closely with ISO on standards, in particular the date/time work of ISO8601 which was partially duplicated into RFC3339. CalConnect has recently become a standards body in its own right, publishing or co-publishing standards with other bodies. To address the elephant in the room directly - there is a significant culture clash / divide between IETF and ISO, and CalConnect sits in the middle somewhere. My keen goal is to act as an ambassador between the two cultures and ensure that calendaring work which interacts with the internet and with internet standards comes to the IETF - at the very least as informational documents which we can reference, but much better if we can keep the collaborative process going and either only publish the calendaring standards as IETF documents and just duplicate them into the CalConnect standards namespace to allow referencing there. My primary goal for this Zurich trip is to extract any specifications which have been languishing as unpublished drafts but which describe real protocol elements being used by shipping client/server software and shepherd these through to publication. I'd also love to re-ignite the collaboration between IETF members and CalConnect members in the calendaring space, and make sure we capture the work that's being done. Please let me know if there's anything else you'd like my help or involvement in! Also - if you're going to be at Fosdem this year, I'm speaking about some of the other work I'm doing with my IETF hat as co-chair of the JMAP and EXTRA working groups on email standards. I'll be speaking at 3:40pm in the H.2215 (Ferrer) room on February 2nd. Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --15c5c17390b44ed6a49877c80336cfce Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Hello all, I'm your new co-chair!

If you've= been coming to CalConnect for a while, you might know me from there.&nb= sp; I've missed a few recently due to all my other commitments, but I wi= ll get these two in a row at least.

You may have heard th= at CalConnect has also started working more closely with ISO on standard= s, in particular the date/time work of ISO8601 which was partially dupli= cated into RFC3339.  CalConnect has recently become a standards bod= y in its own right, publishing or co-publishing standards with other bod= ies.

To address the elephant in the room directly - there= is a significant culture clash / divide between IETF and ISO, and CalCo= nnect sits in the middle somewhere. 

My keen goal i= s to act as an ambassador between the two cultures and ensure that calen= daring work which interacts with the internet and with internet standard= s comes to the IETF - at the very least as informational documents which= we can reference, but much better if we can keep the collaborative proc= ess going and either only publish the calendaring standards as IETF docu= ments and just duplicate them into the CalConnect standards namespace to= allow referencing there.
My primary goal for this Zurich= trip is to extract any specifications which have been languishing as un= published drafts but which describe real protocol elements being used by= shipping client/server software and shepherd these through to publicati= on.  I'd also love to re-ignite the collaboration between IETF memb= ers and CalConnect members in the calendaring space, and make sure we ca= pture the work that's being done.

Please let me know if t= here's anything else you'd like my help or involvement in!

Also - if you're going to be at Fosdem this year, I'm speaking about s= ome of the other work I'm doing with my IETF hat as co-chair of the JMAP= and EXTRA working groups on email standards.  I'll be speaking at = 3:40pm in the H.2215 (Ferrer) room on February 2nd.

Cheers,=

Bron.

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


--15c5c17390b44ed6a49877c80336cfce-- From nobody Sat Jan 19 05:28:31 2019 Return-Path: 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 A1C61130DC8 for ; Sat, 19 Jan 2019 05:28:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 5nudjaafmr0S for ; Sat, 19 Jan 2019 05:28:26 -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 76F6A12F1A5 for ; Sat, 19 Jan 2019 05:28:26 -0800 (PST) Authentication-Results: mail.aegee.org/x0JDSMeq020079; auth=pass (PLAIN) smtp.auth=didopalauzov DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1547904502; i=dkim+MSA-tls@aegee.org; r=y; bh=VUH/Q6b7hIXoM+/16acaETHMiRtKTS/ZwgJ73f48Guk=; h=Subject:From:To:Date:In-Reply-To:References; b=MqOZeui0Ig+kEMcn3nS0HfYhXwqwhdT/7cDMqBUDdPEubtc8xN/0BReJI9Hr0UsN1 +Sl21Yaovfl/8m47pPn22gIrgkKkaYdsVP69mW4vT6sGtOCHYxkmNHjfVOTEif2jzK X8wrDYMu7lvMlwQxtqge6TAEH+/hC76MK7lfrP1ecQ0Qn4b6Vh3lvrhQ+Vyup0uXIo njH0Dd+MuS5joK2VFT8oDWPeNoVLSTEdmB/3Ztf6d18Elr2ZLmube3LZzBXgr7/zO0 7tduiE1G3bXlGekuINDzvDESos0cMg5mXDPa1M6oIBC9JC2f731ZNXWRudNXOPv5df BVR3OjQspmOBZOqyQDHgjCam7CdtGjx1A7vhIbTCForElqgsyrFpoBx27DQbIzr+ri yfPu5jp4/WUmj+4WA8qPlt8f9igE65epu5orI+yu7V6Rrlq8uYe0FW5lxaAUutiqTJ WzA66t0RGHwJCX8N2qmzzgCq0pl0FLs/bCv6+Dios14xJ1YIHYqFrCklJB/E09zQfq aWGdiz7+hzPlTJcqmol9cg1K9JrHy/rpLUhKOaAI6FBXl4TUQC4k9ulv6F7iveYJZo 6f9S5uKwTen3pXn+pdwJBLS7J2jkEQGY8Hnq5PxdChq8xz5fnTwHm5QvPqtVmTpb00 FgeHyW36nkwFH1jcuh0nZKpA= Authentication-Results: mail.aegee.org/x0JDSMeq020079; dkim=none Received: from Tylan (adsl-62-167-97-198.adslplus.ch [62.167.97.198]) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id x0JDSMeq020079 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 19 Jan 2019 13:28:22 GMT Message-ID: 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?= To: calsify@ietf.org Date: Sat, 19 Jan 2019 13:28:22 +0000 In-Reply-To: References: <895f00bcf8af786b08011f8d3ee6f3cfd7f2f9f7.camel@aegee.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.31.90 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter 0.101.1 at mail.aegee.org X-Virus-Status: Clean Archived-At: Subject: Re: [calsify] =?utf-8?q?Proposed_Errata_=E2=84=965449_for_RFC_7986?= =?utf-8?q?=3A_COLOR_property_with_arbitrary_RGB_values?= X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 13:28:30 -0000 Hello, do I get weird by sending reminders for erratum 5449? Regards Дилян On Wed, 2018-10-10 at 09:16 +0000, Дилян Палаузов wrote: > Hello, > > what shall happen, so that https://www.rfc-editor.org/errata/eid5449 > makes progress? > > Regards > Дилян > > On Thu, 2018-06-28 at 22:04 +0000, Дилян Палаузов wrote: > > Hello, > > > > I would like to suggest the following Errata and welcome any comments > > within a month. > > > > My reading is that COLOR now cannot have the value RGB(61,211,68) > > > > Please correct me, if I am wrong. > > > > RFC 7986 (new Properties for iCalendar) Section 5.9. COLOR Property > > says: > > https://tools.ietf.org/html/rfc7986#section-5.9 > > > > Type: Technical > > Section: 5.9 COLOR Property > > > > Origianl text: > > > > Description: ...The value is a case-insensitive color name taken from > > the CSS3 set of names, defined in Section 4.3 of [W3C.REC-css3-color- > > 20110607]. > > > > Example: The following is an example of this property: > > COLOR:turquoise > > > > Corrected text: > > > > Description: ...The value is either a case-insensitive color name > > taken from the CSS3 set of names, defined in Section 4.3 of [W3C.REC- > > css3-color-20110607], or an RGB() functional notation with absolute > > values specified in Section 4.2.1 of the same document > > > > Examples: The following are examples of this property: > > COLOR:turquoise > > COLOR:rgb(61\,211\,68) > > > > Notes for the errata: > > > > draft-daboo-icalendar-extensions-07 removed the possibily to have RGB > > colours for COLOR. > > > > CSS3 included color names, that browsers at that time suppored, > > originating from X11's rgb.txt. The color names and values were > > randomly chosen. The minimal distance between the colors isn't > > consistent. One motivation for creating a color name were hardware > > capabilities - an argument which isn't valid for 20 years now. There > > is no reason to limit the number of possible values for COLOR. A user > > interface for choosing a named color has either to offer the user the > > possibility to choose from a pre-filled list of colors, which could > > clutter the interface, or let the user choose any RGB color and narrow > > it later to the closest color with CSS3 name. This narrowing isn't > > trivial and performing it seems like having an RFC running in itself. > > > > Notes for this message, outside the errata: > > > > Gnome Evolution recently added support for the COLOR property and > > uploaded iCalendar files by it now have: > > COLOR:rgb(61\,211\,68) > > > > https://www.w3.org/TR/2011/REC-css3-color-20110607/ lets also other > > forms: > > #f00 > > #ff0000 > > rgb(100%, 0%, 0%) > > > > I have no propbem to let or exclude any of the forms above. The main > > challenge is neither to have the user chose from a final list of > > colours, nor to let her choose any colour but narrow the selected > > colour afterwards to something. Letting more than one form of the > > mentioned above would be overengineering for the mentined challanage. > > > > https://github.com/w3c/csswg-drafts/issues/2813 states the colours are > > chosen randomly, and http://christopher.org/history-web-color-names/ > > proves this thesis. > > > > Randomly choosen colour values (having names coming from rgb.txt) are > > not suitable to achieve any aim. > > > > I haven't worked with colour terms until today, so feel free to > > rephrase the rgb-functional sentence. > > > > Regards > > Дилян > > > > _______________________________________________ > > calsify mailing list > > calsify@ietf.org > > https://www.ietf.org/mailman/listinfo/calsify > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify From nobody Mon Jan 28 15:12:28 2019 Return-Path: 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 1A59B13117A for ; Mon, 28 Jan 2019 15:12:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.982 X-Spam-Level: X-Spam-Status: No, score=-1.982 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, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, 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=fastmailteam.com header.b=roOpPh+K; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=K9s/fGGe 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 yf856UC3byqA for ; Mon, 28 Jan 2019 15:12:24 -0800 (PST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45211131142 for ; Mon, 28 Jan 2019 15:12:24 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 5F2FF1863 for ; Mon, 28 Jan 2019 18:12:23 -0500 (EST) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Mon, 28 Jan 2019 18:12:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=message-id:date:from:to:subject :content-type; s=fm1; bh=bR0bPWKtCEJ6psQtpomWzBAgRRBZ4VU4DA25jRM pQ5Y=; b=roOpPh+KJc/GICeJVI9j+RpOTjHxIbjxAOUDlqQhJzHmBgD9dbRKW5Z BDxOe89Z8tAJEn+pAmNmN3IO6pOBgm7WM/hf103cQJNmFoF0/UDcIYXqn0FC0D1P TGLGf1IJdeY45bg9LoaGg2r6bwwhXEW81NhCehK5sQpQMrGsVX/IYB6S2UcY9Lsl PlvrlKPsbBT5ZTRkZLPdxuZTOc0VmKdU0AD2AlNLQ4clYYqVa81Kpeuu8HZ9vAXj GxL6hai8rsqvseG0UJBhSwCG9oahvkZNMo6ALA0oCswb72/vPQLLO1clgcv5+S1v D4yY7XGQvZrlo1GONVt72M5GF+GdCBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id:subject :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=bR0bPWKtCEJ6psQtpomWzBAgRRBZ4VU4DA25jRMpQ5Y=; b=K9s/fGGe Du9+aufmdDKyA/UDoOiQadxWFNEJhXbrUTODN1EZcyW/VQQkI0BljegTX/YsXqpk u99Ve3TsmCVPPfhZjutPgZU/FzNUyDYHx7EbrnxEblkBn+KQZ5MbzYaxchD/2//k s4eXhXisz1QoKChxksibkSgS2EdnJ0KjMV+tPdPYFAKZMXKqfH+Bjj1dbdRPm6nm YqSH1rqMQhZbB5t5eD5zZd4waNHjBbAwI6s0xFhNKKY4vJuSsE2LArPyT7deSI/A apVqrEAGic9zqHhl0M6W5EiXApP7Uc4D2JyuISwA4wsvOVHSWduX/dTNl0bEE4v5 EETfRIFmuxx8dw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjedugddtjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucenucfjughrpefofgfkfffhvffutgesrgdtreerreertdenucfhrhhomhepfdeurh honhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtgho mheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomh epsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihii vgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0D96420250; Mon, 28 Jan 2019 18:12:22 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.5-816-g6582a22-fmnext-20190123v1 X-Me-Personality: 56629417 Message-Id: <68d00c8a-13df-4c17-ada2-8af2d6777fcf@www.fastmail.com> Date: Mon, 28 Jan 2019 18:12:21 -0500 From: "Bron Gondwana" To: calsify@ietf.org Content-Type: multipart/alternative; boundary=9f5b4748391643dea3e93faed88b110a Archived-At: Subject: [calsify] Shall we meet in Prague? (also: what shall we work on?) X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 23:12:26 -0000 --9f5b4748391643dea3e93faed88b110a Content-Type: text/plain Hi all, It's getting on time to submit meeting requests for the next face-to-face IETF meeting! We have two documents that are waiting for revised drafts: * eventpub-extensions-10 * caldav-attachments-03 As well as the almost ready to go jscalendar: * jscalendar-11 I know there's also interest in bringing other items of work to this group. From memory things that I've seen mentioned include: * caldav-scheduling-controls (author: me, when I write it up!) - a new header "Scheduling-Enabled: F" to disable all scheduling when storing a resource to a server. Good for restoring from backup as well as a way to avoid sending updates more generally while cleaning up spam, rather than the current "Schedule-Reply: F" which is only for resources where you are not the organizer. * caldav-upgrade - a header returned by a server to tell a client that a .ics feed is also available via read-only caldav, allowing clients to use sync-collection for more efficient updates. * caldav-push - a method for delivering push updates when a calendar is changed, allowing clients to avoid polling. * caldav-server-side-subscriptions - a method for federating caldav calendars (potentially with local cached copy) such that the server acts as a client to another server, aggregating calendars from multiple servers into a single homeset. * calendar autodiscovery - I'm not sure if that's coming to this group, or if there's going to be an attempt at renewing the more general service autodiscovery discussion. My notes from last calconnect said it would go to DISPATCH, but I didn't make it to the Monday of Bangkok, so I missed out. .... Does anybody have any other work that they want to bring to this group, or appetite to work on any of the above? I'd love to get this group flowing smoothly and improving calendaring for everybody! I'll be at CalConnect in Zurich next week, and I'll be asking everyone there to get involved over here as well. Submissions for sessions are due Feb 8th at the latest, so do let us know if you'll be present at Prague (or joining remotely) and have something to talk about! Cheers, Bron (on behalf of the calext chairs) -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --9f5b4748391643dea3e93faed88b110a Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Hi all,

It's getting on time to submit meet= ing requests for the next face-to-face IETF meeting!

We h= ave two documents that are waiting for revised drafts:


As well = as the almost ready to go jscalendar:






* caldav-server-side-subscr= iptions - a method for federating caldav calendars (potentially with loc= al cached copy) such that the server acts as a client to another server,= aggregating calendars from multiple servers into a single homeset.
<= /div>

* calendar autodiscovery - I'm not sure if that's coming to t= his group, or if there's going to be an attempt at renewing the more gen= eral service autodiscovery discussion.  My notes from last calconne= ct said it would go to DISPATCH, but I didn't make it to the Monday of B= angkok, so I missed out.

=

....

Does anybody have any other work that th= ey want to bring to this group, or appetite to work on any of the above?=   I'd love to get this group flowing smoothly and improving calenda= ring for everybody!  I'll be at CalConnect in Zurich next week, and= I'll be asking everyone there to get involved over here as well.

Submissions for sessions are due Feb 8th at the latest, so do l= et us know if you'll be present at Prague (or joining remotely) and have= something to talk about!
Cheers,

Bron (on behalf of t= he calext chairs)

<= div style=3D"font-family:Arial;">
<= div style=3D"font-family:Arial;">
--9f5b4748391643dea3e93faed88b110a-- From nobody Thu Jan 31 15:32:44 2019 Return-Path: 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 380621310BF; Thu, 31 Jan 2019 15:32:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=calconnect.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 QE7OsuFBu1TW; Thu, 31 Jan 2019 15:32:33 -0800 (PST) Received: from palegreen.birch.relay.mailchannels.net (palegreen.birch.relay.mailchannels.net [23.83.209.140]) (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 7E895130F86; Thu, 31 Jan 2019 15:32:32 -0800 (PST) X-Sender-Id: dreamhost|x-authsender|dave.thewlis@calconnect.org Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 9CA9E501DA4; Thu, 31 Jan 2019 23:32:26 +0000 (UTC) Received: from pdx1-sub0-mail-a20.g.dreamhost.com (unknown [100.96.30.62]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 22545501C87; Thu, 31 Jan 2019 23:32:26 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|dave.thewlis@calconnect.org Received: from pdx1-sub0-mail-a20.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Thu, 31 Jan 2019 23:32:26 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|dave.thewlis@calconnect.org X-MailChannels-Auth-Id: dreamhost X-Eyes-Left: 6f6830eb024c95e7_1548977546519_690335737 X-MC-Loop-Signature: 1548977546519:1119083809 X-MC-Ingress-Time: 1548977546518 Received: from pdx1-sub0-mail-a20.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a20.g.dreamhost.com (Postfix) with ESMTP id B923480650; Thu, 31 Jan 2019 15:32:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=calconnect.org; h=from :content-type:mime-version:date:subject:message-id:to; s= calconnect.org; bh=ttwcsLmtaHH72gBhX3NEmyWLR4U=; b=Qm94k4QCEc1m5 r/H8+/H8OI16Fji6p2DdNzU4uhxda5i9WBo+SUdclF2l7JouImZszAUg+WQ7Dw+l t1d3UZw7ZxO/8j2cXkAV+1IJfyEyjnGMf0wJjTpw0lge2W83d9T3LFQA8npdjLaA QdVR56cxVO7npeTbiUMHhn+VViJFZs= Received: from [192.168.0.218] (47-208-67-174.erkacmtk02.res.dyn.suddenlink.net [47.208.67.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: dave.thewlis@calconnect.org) by pdx1-sub0-mail-a20.g.dreamhost.com (Postfix) with ESMTPSA id 689CA80642; Thu, 31 Jan 2019 15:32:23 -0800 (PST) X-DH-BACKEND: pdx1-sub0-mail-a20 From: David Thewlis Content-Type: multipart/alternative; boundary="Apple-Mail=_8C2905A8-642C-4851-9EDE-7F7DB174CF1B" Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Date: Thu, 31 Jan 2019 15:32:22 -0800 Message-Id: <7E932036-A5C8-4E18-AF8C-EE0C80E225A8@calconnect.org> To: ietf-tzdist list , tzdist-bis@ietf.org, "calsify@ietf.org" X-Mailer: Apple Mail (2.3445.102.3) X-VR-OUT-STATUS: OK X-VR-OUT-SCORE: -100 X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtledrjeejgdduudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhtgggfffukffvofesrgdtmherhhdtjeenucfhrhhomhepffgrvhhiugcuvfhhvgiflhhishcuoegurghvvgdrthhhvgiflhhishestggrlhgtohhnnhgvtghtrdhorhhgqeenucffohhmrghinhepvghvvghnthgsrhhithgvrdgtohhmpdhgohhoghhlvgdrtghomhdptggrlhgtohhnnhgvtghtrdhorhhgnecukfhppeegjedrvddtkedrieejrddujeegnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopegludelvddrudeikedrtddrvddukegnpdhinhgvthepgeejrddvtdekrdeijedrudejgedprhgvthhurhhnqdhprghthhepffgrvhhiugcuvfhhvgiflhhishcuoegurghvvgdrthhhvgiflhhishestggrlhgtohhnnhgvtghtrdhorhhgqedpmhgrihhlfhhrohhmpegurghvvgdrthhhvgiflhhishestggrlhgtohhnnhgvtghtrdhorhhgpdhnrhgtphhtthhopehmuhhrtghhsehfrghsthhmrghilhdrtghomhenucevlhhushhtvghrufhiiigvpedt Archived-At: Subject: [calsify] Streaming info for CalConnect Public Time Zone Workshop on February 5 in Zurich, Switzerland X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2019 23:32:36 -0000 --Apple-Mail=_8C2905A8-642C-4851-9EDE-7F7DB174CF1B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 The CalConnect Public Time Zone Workshop will be next Tuesday, 5 = February 2019, between 1400 and 1730 Central European Time. We have made arrangements with our host, Google, to stream the = CalConnect Public Time Zone Workshop = = for any interested parties who cannot be present. (The workshop was = announced in November and we did get a few queries as to streaming.)=20 The streaming will be done using Google Hangouts; the URL to join the = stream is https://meet.google.com/qjb-zbip-cpf = . =20 You do have to have a google id of some sort (gmail is fine) to join the = streaming. When you access the stream, your request to join will be = authorized.=20 Please do not attempt to join before 1345 CET. The workshop itself = will take place between 1400-1730 CET. The inbound audio and video stream will be disabled, so this will be a = one-way outbound feed. However, there is a chat function so you can ask = questions via the chat. Our plan is to take periodic pauses so the chat = questions can be brought up and answered. If that proves impractical we = will answer the chat questions after the workshop is over, so you=E2=80=99= ll want to include an e-mail address for a response. =20 Dave Thewlis Here=E2=80=99s the original post: Please note that this is NOT an IETF event. CalConnect will host a Public Time Zone = Workshop on Tuesday afternoon, February 5th, during its conference at = Google in Z=C3=BCrich, Switzerland = . The Time Zone Workshop will be Tuesday February 5th from 13:30 to 17:30 = at the Google facility = . This workshop will be focussed on the potential impact of EU = Summer Time changes and how the changes might be mitigated; please see = our news release = . The workshop is open to the = public but you must register in advance. There is no fee to attend the = workshop. Attendees are invited to stay for a Welcome Reception = following the workshop. More information will be provided as planning = continues. =20 The workshop is intended for anyone who needs to plan and prepare for = this and other TZ/DST changes, in particular representatives from = governments, industries affected by tz changes (travel, financial, = health, device manufacturers, etc.), organizations deploying tz data, = and organizations maintaining and updating tz data.=20 Please register for this event at = https://www.eventbrite.com/e/eu-dst-timezone-change-public-workshop-ticket= s-51513763052 = . We invite anyone who is interested in or concerned by the pending = changes and how time zone change information might better be distributed = and implemented to attend. =20 Dave Thewlis -- Dave Thewlis, Executive Director CalConnect - The Calendaring and Scheduling Consortium +1 707 840 9391 voice | +1 707 498 2238 mobile | +1 415 946 3454 fax http://www.calconnect.org | = Dave.Thewlis@calconnect.org --Apple-Mail=_8C2905A8-642C-4851-9EDE-7F7DB174CF1B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
The CalConnect Public = Time Zone Workshop will be next Tuesday, 5 February 2019, between 1400 = and 1730 Central European Time.

We = have made arrangements with our host, Google, to stream the CalConnect Public Time Zone Workshop for any = interested parties who cannot be present.  (The workshop was = announced in November and we did get a few queries as to = streaming.) 

The streaming will be = done using Google Hangouts; the URL to join the stream is https://meet.google.com/qjb-zbip-cpf.  

You do have to have a google id of some = sort (gmail is fine) to join the streaming.  When you access the = stream, your request to join will be authorized. 

Please do not attempt to join before 1345 = CET.   The workshop itself will take place between 1400-1730 = CET.

The inbound audio and video stream will = be disabled, so this will be a one-way outbound feed.  However, = there is a chat function so you can ask questions via the chat. =  Our plan is to take periodic pauses so the chat questions can be = brought up and answered.  If that proves impractical we will answer = the chat questions after the workshop is over, so you=E2=80=99ll want to = include an e-mail address for a response.  


Dave Thewlis


Here=E2=80=99s the original post:


Please note that this is NOT an IETF event.

CalConnect will = host a Public Time Zone Workshop on Tuesday afternoon, February 5th, = during its conference at Google in Z=C3=BCrich, = Switzerland.

The Time Zone Workshop will be Tuesday = February 5th=20 from 13:30 to 17:30 at the Google facility.  This workshop will be=20= focussed on the potential impact of EU Summer Time changes and how the=20= changes might be mitigated; please see our news = release.  The workshop is open to the public but you must register in advance.  There is no fee to attend the = workshop. =20 Attendees are invited to stay for a Welcome Reception following the=20 workshop.  More information will be provided as planning continues. =  

The = workshop is intended for anyone who needs to plan and prepare for this = and other TZ/DST changes, in particular representatives = from governments, industries affected by tz changes (travel, financial, = health, device manufacturers, etc.), organizations deploying tz data, = and organizations maintaining and updating tz = data. 

Please register for this event at https://www.eventbrite.com/e/eu-dst-timezone-change-public-work= shop-tickets-51513763052.

We invite anyone who is interested in = or concerned by the pending changes and how time zone change information = might better be distributed and implemented to attend.  

Dave Thewlis
--
Dave Thewlis, Executive Director
CalConnect - The Calendaring and Scheduling = Consortium
+1 707 840 9391 voice | +1 707 498 = 2238 mobile | +1 415 946 3454 fax
http://www.calconnect.org | Dave.Thewlis@calconnect.org


= --Apple-Mail=_8C2905A8-642C-4851-9EDE-7F7DB174CF1B--