From nobody Sat Feb 3 05:50:49 2018 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 730AE127201 for ; Sat, 3 Feb 2018 05:50:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=V7kRJ/4J; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CozVebnu 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 8spKA1TTW8jV for ; Sat, 3 Feb 2018 05:50:42 -0800 (PST) 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 ED3D312D886 for ; Sat, 3 Feb 2018 05:50:41 -0800 (PST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D40F020EE2 for ; Sat, 3 Feb 2018 08:47:49 -0500 (EST) Received: from web2 ([10.202.2.212]) by compute7.internal (MEProxy); Sat, 03 Feb 2018 08:47:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=0ki3mrpWg/Fq0Td96qBWPcN3C5fLRumbiNvVtWsKygs=; b=V7kRJ/4J UJIPrutd5levaiXuTppiAXY1rVesZaNOBAzAi/YbI3doqw40uOHAMiANtbJs+lTx YqdZGh3QZ2p/sqTSr1bV8UltclbQRz8LAsAXRdd0tJJEvAX/kbDL7eUT9PcPpdSe fqCYbjm4Z+twMJ3jUWccXnIILorzaOPX8E0slYlwmbtCF3lcSLxqXRrzaZWUCV5T 4OAHSR5AsMVkCCOw6Qn4ies2EdAFh6b934k/NFI2dqPn/0uNIReka/EqZ3XZPSG9 WG3Y/nnqFOHKn7drnNKkdoA9qBuxwjEI/D/Cz8zVlUEO4JTPLwEpwi9+aM75n4QN UVafOxyn6oC9DA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=0ki3mrpWg/Fq0Td96qBWPcN3C5fLR umbiNvVtWsKygs=; b=CozVebnuKqwufGsOjzNcwGMKTbXkYX5JiRC5vV2JSQZ6s JJ4uQqD1rPMgqn2IdyZyG1hGHyqigxvBnyBW+5hLmlpH4UPcpB6MZJwI0GAyyFAX /dUkJams2Uz+EYy2w4PamFNvLsg8RS3ua+p6mOfpW9cHUq443IBabQoTp8GKfIXW lDo3jcsq6LxiVduy5blknLv1TQUeWnevCDKHyVkGWkLvJcq/XOPbP7cJ8LeTB/J1 B/uzEXYZDKsVidSVoSagbGCo4NIfDWGgkPKWmYFJEbjV+Vu+87YF+EOJkFwxFhqJ ZkuWXBLj7KRC5zEY469zkvOr6y89uCoyv4SHrbfyg== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id A9FAA62B77; Sat, 3 Feb 2018 08:47:49 -0500 (EST) Message-Id: <1517665669.2779809.1258224512.38FF8BCB@webmail.messagingengine.com> From: Alexey Melnikov To: calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-fde26eb3 X-Forwarded-Message-Id: <1517665609.2779778.1258224072.19913E6B@webmail.messagingengine.com> Date: Sat, 03 Feb 2018 13:47:49 +0000 Archived-At: Subject: [calsify] Fwd: Re: [dispatch] Possible revival of the TZDIST WG X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 13:50:43 -0000 FYI. ----- Original message ----- From: Alexey Melnikov To: DISPATCH Cc: Ken Murchison Subject: Re: [dispatch] Possible revival of the TZDIST WG Date: Sat, 03 Feb 2018 13:46:49 +0000 Correction: tzdist@ietf.org mailing list was closed, so please reply to dispatch@ietf.org (or me). On Sat, Feb 3, 2018, at 1:41 PM, Alexey Melnikov wrote: > Hi, > I've been asked by Ken Murchison to help progress 2 of his drafts: > > draft-murchison-tzdist-tzif-00 > The Time Zone Information Format (TZif) > > and > > draft-murchison-tzdist-geolocate-01 > The Time Zone Data Distribution Service (TZDIST) Geolocate Extension > > I am considering reviving of the TZDIST WG to precess these documents, > as well as another possible one that would discuss how to store/retrieve > different versions of tzdata for historical purposes. At this point I > would like to assess how much interest there is in doing this work. If > you are interested in reviewing/participating in discussions of these > topics, please reply to tzdist@ietf.org or directly to me. > > Thank you, > Alexey, as an ART AD From nobody Thu Feb 8 11:57:51 2018 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 851A31267BB for ; Thu, 8 Feb 2018 11:57:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.309 X-Spam-Level: X-Spam-Status: No, score=-1.309 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net 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 SW_CmZ8xOu8j for ; Thu, 8 Feb 2018 11:57:25 -0800 (PST) Received: from resqmta-po-10v.sys.comcast.net (resqmta-po-10v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:169]) (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 7B08F127444 for ; Thu, 8 Feb 2018 11:57:25 -0800 (PST) Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-10v.sys.comcast.net with ESMTP id jsJdeL2cGmQpejsJwe8seq; Thu, 08 Feb 2018 19:57:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1518119844; bh=nA1RklA86Vm+IHI50tVvSxami1YjyWovPXlW+0xoEws=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=WW0wtU9WfivHxG6tFVb3LLvHpWeiPsyiRLRBqn0/FKYtql9VurOCfkM+87Lpyiglo ZjcE0rxRl7SnTARfDQWdBWa9hQ06P1p7Bm0n1ElCnfBCPlM9icdlfvuGF5Cg+0Sinj 9HJI3CMUGCKgh88rpXyhjDaVqBMowwhNSZPH+RQ4S9BOtWoKENJ8GMliyCZKMG8F8G KxVuuYmqr+SlN0MztLdc5V6SCfbjYCb4WQNAPivYP+3ml70ZF4Fo+9nAWehzj3UfWu +FuoY3r2dEe1UoryDwFdqQvHFuXCUrLUBBfrsWKzECqrIrlXnsCOoXQ6sdmYw7hIcS sFPsyebGKrdgg== Received: from THARE ([73.42.14.246]) by resomta-po-03v.sys.comcast.net with SMTP id jsJveHwRpaI8ojsJwetnUz; Thu, 08 Feb 2018 19:57:24 +0000 From: "Tim Hare" To: Date: Thu, 8 Feb 2018 14:57:22 -0500 Message-ID: <008101d3a117$0956f590$1c04e0b0$@comcast.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0082_01D3A0ED.20855A60" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdOhFBxIMnXKxMhpQHS1L0nDtQCQiw== Content-Language: en-us X-CMAE-Envelope: MS4wfDfJMqmGhPo3VKenc+CEXTCrykBtB+lsSSiC+mw7MryGkrh20Inob8inGpAzssNxcwEGfHS+EUbcjjoiZkneJR18iLCLxicFt1GqNGWgqdLXT+bij5uv 5cTlppA+cX7dLF7FOBWFYEdCd1PnnL+l2n0= Archived-At: Subject: [calsify] Question about DESCRIPTION ALTREP X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2018 19:57:27 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0082_01D3A0ED.20855A60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In the RFC section on the ALTREP property for the DESCRIPTION component I see an example of using ALTREP to provide HTML in a description (for our internal application, because we use Outlook for calendaring, we have been using Microsoft's X-ALT-DESC, but I'd like to use the new ALTREP). What's not clear from the example below, is whether the content part beginning with Content-Type: is positioned in the data within the DESCRIPTION component, or should be positioned _after_ the END:VCALENDAR statement (since the BEGIN:VCALENDAR / END:VCALENDAR pair is assumed to be Content-Type: text/calendar. I guess that's really two questions: 1. in an .ics file, where does the ALTREP go if you are using content identifier - in the DESCRIPTION or after the END:VCALENDAR? 2. Can there be a Content-Type: text/Calendar and Content-Id: in the .ics file before the BEGIN:VCALENDAR For myself, the questions specifically relate to the use case where we create an .ics file that others may subscribe to; other use cases such as mailing a calendar might have other answers. Thanks Tim Hare Interested Bystander, Non-Inc. > Example: > > DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": > Project XYZ Review Meeting will include the following agenda > items: (a) Market Overview\, (b) Finances\, (c) Project Man > agement > > The "ALTREP" property parameter value might point to a "text/html" > content portion. > > Content-Type:text/html > Content-Id: > > > > > > >

> Project XYZ Review Meeting will include > the following agenda items: >

    >
  1. Market Overview
    2. >
  2. Finances
    3. >
  3. Project Management
    4. >
>

> > ------=_NextPart_000_0082_01D3A0ED.20855A60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 
In the =
RFC section on the ALTREP property for the DESCRIPTION component I see =
an example of using ALTREP to provide HTML in a description (for our =
internal application, because we use Outlook for calendaring, we have =
been using Microsoft’s X-ALT-DESC, but I’d like to use the =
new ALTREP).  What’s not clear from the example below, is =
whether the content part beginning with Content-Type:  is =
positioned in the data within the DESCRIPTION component,  or should =
be positioned _after_  the END:VCALENDAR statement (since =
the BEGIN:VCALENDAR / END:VCALENDAR pair is assumed to be Content-Type: =
text/calendar.  I guess that’s really two questions:  =

 
1.  in =
an .ics file, where does the ALTREP go if you are using content =
identifier – in the DESCRIPTION or after the =
END:VCALENDAR?
2.  =
Can there be a Content-Type: text/Calendar and =
Content-Id:  in the .ics file before the =
BEGIN:VCALENDAR
 
For =
myself, the questions specifically relate to the use case where we =
create an .ics file that others may subscribe to;  other use cases =
such as mailing a calendar might have other =
answers.

Thanks
Tim Hare
Interested Bystander, =
Non-Inc.

>   Example:

> 

> =       DESCRIPTION;ALTREP=3D"CID:part3.= msg.970415T083000@example.com":

>        Project XYZ Review = Meeting will include the following agenda

>         items: (a) = Market Overview\, (b) Finances\, (c) Project Man

>    =      agement

> 

>      The "ALTREP" property = parameter value might point to a = "text/html"

>      content = portion.

> 

>       = Content-Type:text/html

>       = Content-Id:<part3.msg.970415T083000@example.com><= /p>

> 

>       = <html>

>         = <head>

>          = <title></title>

>         = </head>

>     =     <body>

>           = <p>

>          &nb= sp;  <b>Project XYZ Review Meeting</b> will = include

>          &nb= sp;  the following agenda items:

>          &nb= sp;  <ol>

>          &nb= sp;    <li>Market = Overview</li>

>          &nb= sp;    = <li>Finances</li>

>          &nb= sp;    <li>Project = Management</li>

>          &nb= sp;  </ol>

>           = </p>

>         = </body>

>       = </html>

 

------=_NextPart_000_0082_01D3A0ED.20855A60-- From nobody Tue Feb 20 08:34:29 2018 Return-Path: X-Original-To: calsify@ietf.org Delivered-To: calsify@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E115D12D882 for ; Tue, 20 Feb 2018 08:34:27 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.72.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151914446791.4766.389448112144794196.idtracker@ietfa.amsl.com> Date: Tue, 20 Feb 2018 08:34:27 -0800 From: IETF Secretariat Archived-At: Subject: [calsify] Milestones changed for calext WG X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.22 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Feb 2018 16:34:28 -0000 Changed milestone "Send attachment dratf to IESG", set due date to June 2018 from May 2017. Changed milestone "Send Event Publication draft to IESG", set due date to June 2018 from June 2017. Changed milestone "Send iCal relation draft to IESG", set due date to June 2018 from July 2017. URL: https://datatracker.ietf.org/wg/calext/about/ From nobody Tue Feb 20 08:46:18 2018 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 D957A129C59 for ; Tue, 20 Feb 2018 08:46:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.3 X-Spam-Level: X-Spam-Status: No, score=-4.3 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTN-Y5ubNA1Z for ; Tue, 20 Feb 2018 08:46:16 -0800 (PST) Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 72EBD127871 for ; Tue, 20 Feb 2018 08:46:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1519145174; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=gcEeK6LllWlOBHIqM5Wl2ObHS51B1bHN1/l/G4gefAM=; b=ebbRDQKk/9PFaVma39LyKdqe+B7AGrBx6nW8HTPZEHgj1hbKKmPPR2ZWgobKq8t2 UjgUeI+//0P1BBg7g7UkTARcA1/JSMd2Yz0Ezxql9JigTFPLmUJGRG5/FuwmILtF Ngd1N4DF3rt6gZJ0BnA1S7xc3gepEM1mVVRu2ndBUJQ=; X-AuditID: c6180641-81dff70000007a40-06-5a8c50d615f7 Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 1E.FF.31296.6D05C8A5; Tue, 20 Feb 2018 17:46:14 +0100 (CET) Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0352.000; Tue, 20 Feb 2018 11:46:13 -0500 From: Daniel Migault To: "calsify@ietf.org" Thread-Topic: IETF 101 meeting -- agenda Thread-Index: AdOqafnIveM9JibUSvOlIn3k1IXZZA== Date: Tue, 20 Feb 2018 16:46:12 +0000 Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118D53ABB@eusaamb107.ericsson.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.218] Content-Type: multipart/alternative; boundary="_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53ABBeusaamb107erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyuXRPrO61gJ4og9716habXjSzOjB6LFny kymAMYrLJiU1J7MstUjfLoErY+XuNvaCBSoVW9tvsDQwfpLvYuTgkBAwkZhyIa+LkYtDSOAI o8SL93/YIJzljBJvn+xl7GLk5GATMJJoO9TPDmKLCGhK7L7awwpiCwsoSzQtAWkAiWtILFv/ iBXC1pN4efszE8gCFgFViWUXMkHCvAK+EjvXzwMbySggJvH91BomEJtZQFzi1pP5YLaEgIDE kj3nmSFsUYmXj/+xQtjKEmuO3GGEqM+X+NK0nwlipqDEyZlPWCYwCs5CMmoWkrJZSMog4joS C3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7KkaO0uKCnNx0I8NNjMDwPibB5riDcW+v5yFGAQ5G JR7eDTY9UUKsiWXFlbmHGCU4mJVEeC9/744S4k1JrKxKLcqPLyrNSS0+xCjNwaIkznvOkzdK SCA9sSQ1OzW1ILUIJsvEwSnVwKiw+R3XlNm5L+6uT1p1asnl1im13w/WfXH/ovApVdToVVva 67W+1/a61H843OT/I0Fh1oxmpogHT7vc2rdN25jqrMMXpfk57Edpxx/niuVLZrjffV7hFPQk vCh2ri2LQPrTeM3/MyWqfSJdppv+dlnx8Sbzo9LC588F6mvcrmjcXtLN475gRa0SS3FGoqEW c1FxIgDljAG5awIAAA== Archived-At: Subject: [calsify] IETF 101 meeting -- agenda X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Feb 2018 16:46:18 -0000 --_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53ABBeusaamb107erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Please find the provisional agenda. If there are any topics you are willing= to bring, please let us know. We have asked for remote participation as we= ll. We are also looking for volunteer for jabber scribes as well as minute take= rs ;-) Yours, Calext co-chairs agenda =3D=3D Agenda bashing and status of the drafts * drafts status and milestones (5 minutes) * minute taker, jabber scribes =3D=3D Discusions * draft-ietf-calext-caldav-attachments-03 ( 5 minutes ) * draft-ietf-calext-eventpub-extensions-05 ( 5 minutes ) * draft-ietf-calext-ical-relations-03 ( 5 minutes ) * draft-ietf-calext-jscalendar-00 ( 10 minutes ) Yours, Daniel --_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53ABBeusaamb107erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

Please find the provisional agenda. If there are any= topics you are willing to bring, please let us know. We have asked for rem= ote participation as well.

 

We are also looking for volunteer for jabber scribes= as well as minute takers ;-)

 

Yours,

 

Calext co-chairs

 

 

agenda

 

=3D=3D Agenda bashing and status of the drafts<= /o:p>

 

* drafts status and milestones  (5 minutes)

* minute taker, jabber scribes

 

=3D=3D Discusions

 

* draft-ietf-calext-caldav-attachments-03 ( 5 minute= s )

* draft-ietf-calext-eventpub-extensions-05 ( 5 minut= es )

* draft-ietf-calext-ical-relations-03 ( 5 minutes ) =

* draft-ietf-calext-jscalendar-00 ( 10 minutes )

 

 

 

Yours,

Daniel

--_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53ABBeusaamb107erics_-- From nobody Tue Feb 20 09:58:46 2018 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 9C7FF126D0C for ; Tue, 20 Feb 2018 09:58:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.3 X-Spam-Level: X-Spam-Status: No, score=-4.3 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kf-wckA8BAvy for ; Tue, 20 Feb 2018 09:58:43 -0800 (PST) Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 61DBE124BAC for ; Tue, 20 Feb 2018 09:58:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1519149522; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=x6jCFHWuilu7ZVDLjywgDauVwNNhtHjYfbCprtS2T3Q=; b=VbzxVmfUnhEw8uRaCQsKfdafW0UPm13Hs/yazcKsrrarKJyGJvxDIivRAD6P+oUs y8lGZkyRnWJpRZGB5EDvTLFnuts4GjNRHAbPqlei9MN26QSthrqsSpiMNjNjH/DB b32466PDAcQbQ+9Zu+jvEXDiDibSpQS2LzsSpiOqhb4=; X-AuditID: c6180641-81dff70000007a40-bc-5a8c61d204ad Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id CC.A3.31296.2D16C8A5; Tue, 20 Feb 2018 18:58:42 +0100 (CET) Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0352.000; Tue, 20 Feb 2018 12:58:42 -0500 From: Daniel Migault To: "calsify@ietf.org" CC: "calext-chairs@tools.ietf.org" Thread-Topic: IETF 101 Calext meeting and moving work forward... Thread-Index: AdOqdHCNUCqGRPY+QeW5+rU1nOCjOQ== Date: Tue, 20 Feb 2018 17:58:41 +0000 Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118D53BE4@eusaamb107.ericsson.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.218] Content-Type: multipart/alternative; boundary="_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53BE4eusaamb107erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyuXSPt+6lxJ4ogzNfDC3urfnAZrHpRTOr A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJVxctp21oK1ahVbNvcwNjBOU+xi5OSQEDCR WH7xFEsXIxeHkMARRok7H9azQTjLGSW+vP3CAlLFJmAk0Xaonx3EFhHQlNh9tYcVxGYWcJRY 1XmMDcQWFrCWeHv4OAtEjYPE06aDULaexLprs4BsDg4WAVWJGd+1QMK8Ar4Sa7+8AxvDKCAm 8f3UGiaIkeISt57MZ4I4TkBiyZ7zzBC2qMTLx/9YIWxliTVH7jBC1OdLLFj9mRVipqDEyZlP WCYwCs1CMmoWkrJZSMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7KkaO0uKCnNx0I8NN jMBoOCbB5riDcW+v5yFGAQ5GJR5ek5CeKCHWxLLiytxDjBIczEoivJe/d0cJ8aYkVlalFuXH F5XmpBYfYpTmYFES5z3nyRslJJCeWJKanZpakFoEk2Xi4JRqYPTL5d6uWeWWsfNg9+Z1TrHb 6gIzumoWlTT5yLzxmdf5QWj17kd7Sza7KP7dINBk5eaz9+bJom4WviLD1/opB9Ifdtaa7Vkt b7L3mRHfgc8nfx94uKU7Nmyik/bsIHvriHL7Sffvi639d+zN5Lt58VUbe/XYn81Z8YCNO61f 375/AcPKFSmihUosxRmJhlrMRcWJAFjGLl+CAgAA Archived-At: Subject: [calsify] IETF 101 Calext meeting and moving work forward... X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Feb 2018 17:58:45 -0000 --_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53BE4eusaamb107erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, The current working items are as follows. I propose that we use our time sl= ot in London to discuss their status and progress. * draft-ietf-calext-caldav-attachments-03 (Submitted to IESG) * draft-ietf-calext-eventpub-extensions-05 (WG Last Call) * draft-ietf-calext-ical-relations-03 (WG Document) * draft-ietf-calext-jscalendar-00 ( WG Document) I am encouraging you all to provide reviews and feed backs on these drafts,= so drafts can be moved forward in WG Last Call and then to the IESG. It is necessary that when a WG last call is started we - as chairs have a f= eeling that the draft is supported by the WG. This has to be confirmed duri= ng the WG Last Call before we can pass it to the IESG. If would be even better that we could show progress before the IETF meeting= ;-). We have updated the milestones of these document for June / September= . I would be more than happy to have them achieved earlier! Yours, Your Calext co-chairs --_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53BE4eusaamb107erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

The current working items are as follows. I propose = that we use our time slot in London to discuss their status and progress.

        &nbs= p;      

* draft-ietf-calext-caldav-attachments-03 (Submitted= to IESG)

* draft-ietf-calext-eventpub-extensions-05 (WG Last = Call)

* draft-ietf-calext-ical-relations-03 (WG Document) =

* draft-ietf-calext-jscalendar-00 ( WG Document)

 

I am encouraging you all to provide reviews and feed= backs on these drafts, so drafts can be moved forward in WG Last Call and = then to the IESG.

 

It is necessary that when a WG last call is started = we - as chairs have a feeling that the draft is supported by the WG. This h= as to be confirmed during the WG Last Call before we can pass it to the IES= G.

 

If would be even better that we could show progress = before the IETF meeting ;-). We have updated the milestones of these docume= nt for June / September. I would be more than happy to have them achieved e= arlier!

 

Yours,

 

Your Calext co-chairs

 

--_000_2DD56D786E600F45AC6BDE7DA4E8A8C118D53BE4eusaamb107erics_-- From nobody Tue Feb 27 15:20:27 2018 Return-Path: X-Original-To: calsify@ietf.org Delivered-To: calsify@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F277E12EA54; Tue, 27 Feb 2018 15:11:24 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: calsify@ietf.org, aamelnikov@fastmail.fm X-Test-IDTracker: no X-IETF-IDTracker: 6.73.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151977308498.5200.11587063921441098627.idtracker@ietfa.amsl.com> Date: Tue, 27 Feb 2018 15:11:24 -0800 Archived-At: Subject: [calsify] calext - Requested session has been scheduled for IETF 101 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.22 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 23:11:27 -0000 Dear Daniel Migault, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. calext Session 1 (0:30:00) Thursday, Morning Session I 0930-1200 Room Name: Palace C size: 50 --------------------------------------------- Special Note: 1100 - 1130 Request Information: --------------------------------------------------------- Working Group Name: Calendaring Extensions Area Name: Applications and Real-Time Area Session Requester: Daniel Migault Number of Sessions: 1 Length of Session(s): 30 Minutes Number of Attendees: 15 Conflicts to Avoid: First Priority: extra jmap nvo3 ipsecme teep saag sfc dinrg tls cdni suit cfrg i2nsf dispatch Second Priority: dnsop People who must be present: Alexey Melnikov Donald E. Eastlake 3rd Daniel Migault Philipp Kewisch Resources Requested: Special Requests: As we regularly do not meet face to face, it woudl be appreciated we have a meetecho support. --------------------------------------------------------- From nobody Wed Feb 28 07:19:05 2018 Return-Path: X-Original-To: calsify@ietf.org Delivered-To: calsify@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B955412EB12 for ; Wed, 28 Feb 2018 07:19:03 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.73.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151983114375.5196.13260141532560681865.idtracker@ietfa.amsl.com> Date: Wed, 28 Feb 2018 07:19:03 -0800 From: IETF Secretariat Archived-At: Subject: [calsify] Milestones changed for calext WG X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.22 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2018 15:19:04 -0000 Changed milestone "Send JSCalendar draft to IESG", set state to active from review, accepting new milestone. URL: https://datatracker.ietf.org/wg/calext/about/