From nobody Fri Mar 2 01:32:57 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 0BE34127275; Fri, 2 Mar 2018 01:32:56 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: calsify@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.73.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151998317599.15743.1302325000617960237@ietfa.amsl.com> Date: Fri, 02 Mar 2018 01:32:56 -0800 Archived-At: Subject: [calsify] I-D Action: draft-ietf-calext-jscalendar-01.txt 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: Fri, 02 Mar 2018 09:32:56 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Calendaring Extensions WG of the IETF. Title : JSCalendar: A JSON representation of calendar data Authors : Neil Jenkins Robert Stepanek Filename : draft-ietf-calext-jscalendar-01.txt Pages : 51 Date : 2018-03-02 Abstract: This specification defines a data model and JSON representation of calendar data that can be used for storage and data exchange in a calendaring and scheduling environment. It aims to be an alternative to the widely deployed iCalendar data format and to be unambiguous, extendable and simple to process. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-calext-jscalendar/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-calext-jscalendar-01 https://datatracker.ietf.org/doc/html/draft-ietf-calext-jscalendar-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-jscalendar-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Mar 2 01:38:48 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 C94511272E1 for ; Fri, 2 Mar 2018 01:38:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 kTJbF61wct-f for ; Fri, 2 Mar 2018 01:38:39 -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 934BE12D941 for ; Fri, 2 Mar 2018 01:38:36 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EFF0720CCF for ; Fri, 2 Mar 2018 04:38:35 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute1.internal (MEProxy); Fri, 02 Mar 2018 04:38:35 -0500 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=fm2; bh=ehBHEWu+gTEipNerSRd2hQyuo96Bv 6IoOeSndUZ03Ww=; b=YaULijO5PCD8grYrelnUUF5Giz6DakoKt0C3YLRgNaqVC Odvbx/q31+69QvHN+fY2u7boz+L8bVC9ooqF3VB1LZbYops1Bolur2cAftD9mf/4 hwYO5yAv2TTP5DGWqRnDNRh3yFUD3AZNzPomyRe02keYcx3oRT6CTEKUyNyfG3At oCW7a9mVL++xf9JSkQqJUP6tlCV/DKf3kSyekFNvjKwesU/eSdSEevRsG4eA7fYR 9viL1hSDVVLoAO46o4h8DNe95E9jKgIAsinwWX7emQ9vb+sucJt1tZC6PMJ0SOYw hrNaxoYi8ZOW31LOsoiUy0HdB9wwCT3yRQwStl6fw== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id C44EC42B4; Fri, 2 Mar 2018 04:38:35 -0500 (EST) Message-Id: <1519983515.3957067.1288884760.36FE6E9B@webmail.messagingengine.com> From: Robert Stepanek To: calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_151998351539570670" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b08ff009 Date: Fri, 02 Mar 2018 10:38:35 +0100 Archived-At: Subject: [calsify] Updated JSCalendar draft calext-01 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: Fri, 02 Mar 2018 09:38:47 -0000 This is a multi-part message in MIME format. --_----------=_151998351539570670 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Hi all, right before the IETF-101 draft submission deadline, I've uploaded version 01[1] of the JSCalendar draft. There has only been one change to the document: * *bySetPosition* *property*: The recurrenceRule type mistakenly did not include the BYSETPOS parameter of the RFC5545 RRULE. It now defines the bySetPosition property (see section 4.3.1[2]). As always, please let me know of any feedback. Cheers, Robert Links: 1. https://tools.ietf.org/html/draft-ietf-calext-jscalendar-01 2. https://tools.ietf.org/html/draft-ietf-calext-jscalendar-01#section-4.3.1 --_----------=_151998351539570670 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
Hi all,

right before the IETF-101 draft submission deadline, I've uploaded version 01 of the JSCalendar draft.

There has only been one change to the document:
  • bySetPosition property: The recurrenceRule type mistakenly did not include the BYSETPOS parameter of the RFC5545 RRULE. It now defines the bySetPosition property (see section 4.3.1).

As always, please let me know of any feedback.

Cheers,
Robert

--_----------=_151998351539570670-- From nobody Sat Mar 3 02:56:19 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 7A0B612711A for ; Sat, 3 Mar 2018 02:56:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apthorpia-com.20150623.gappssmtp.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 Q6rpyi64_YBB for ; Sat, 3 Mar 2018 02:56:16 -0800 (PST) Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (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 D06BA1205D3 for ; Sat, 3 Mar 2018 02:56:16 -0800 (PST) Received: by mail-pg0-x230.google.com with SMTP id e9so4830162pgs.10 for ; Sat, 03 Mar 2018 02:56:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apthorpia-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=eBIhe9I6KuCdSgoN7sZ0lHhGsZU+oPsWh+/qgpv7c+s=; b=d1I977DZFo3Z6R8nmQcK5RxlK9d/G7vAoXmbLsptOk0erBN9Znm39cQIKT3h3FK2F5 rAatYnICIUexLi5JqW4JTT5kblH9A2cR2KWA3UAHVSa4UoubpIjOM8uXOMlQ5mfhk2hh yJaPuadLHrehQLF3KzJN6NKdfVNiNriEZmcrUyrNwP6vc16kpwcaTGoTITSLAylsOPfs rscc2lJLc7M3eECpHy/ghHbxmStaK30VFCeNTJ/97Vnp9JqtvSh8oAZvDustdVhmUpQ7 8/kYB8LWoe24KPTa2oJeuiSg0eWh85QvFb5jnhFB9rEwSM4KZ3u0sXI7qoRSQnjCE5lG MeJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=eBIhe9I6KuCdSgoN7sZ0lHhGsZU+oPsWh+/qgpv7c+s=; b=ZyVBf/cSxkyWYU7oJ0yoGxK6b5dFA1kJ6tH/6bogWniEA3wicQ2SsHdH0pePArSehd lbq8M8ClPNEY+KM9iFRsPAtv0sgPkVbxyn9JNLl8IQ4OwOnv+Hiscf7E7wvE2X7iRHEX Dtq3x8LSkF3jCFhOnRgdNp2EYpf7ONlRIeN11MdfNRpHFrSKHDdo/o0URucqqw4y4Tip VCQS5vGKMfm4CiUKDnSVI/QJj+tuOeJtnFxUjLxMs8/rKw1BtRiF7EYPt1B9GFci2vk/ rlc+vEM4DDHz2l25DEZVVPC/EEyhj85cSFt1dpbR2kwfC2KiM91BbCPG57/TvTgF2Sch 838Q== X-Gm-Message-State: APf1xPBnZU9nJgS/fVen2K63ji6ia+eX7GOFHsk2hWNoQ8mpegem3tOG m8OmnqlV/o+6sXwvMvbslsm4L7MA X-Google-Smtp-Source: AG47ELsPUKCS/JiYJkDx3bDMzklceZadGV3WDYIBsgCB3FZ55wQlMKvs0v0rBSCO+1FWOPYhDvEbpg== X-Received: by 10.99.166.10 with SMTP id t10mr6943142pge.198.1520074575715; Sat, 03 Mar 2018 02:56:15 -0800 (PST) Received: from [192.168.2.109] ([138.75.30.234]) by smtp.gmail.com with ESMTPSA id s67sm16885513pfg.104.2018.03.03.02.56.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Mar 2018 02:56:14 -0800 (PST) To: Robert Stepanek , calsify@ietf.org References: <1519983515.3957067.1288884760.36FE6E9B@webmail.messagingengine.com> From: Adrian Apthorp Message-ID: Date: Sat, 3 Mar 2018 18:56:12 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1519983515.3957067.1288884760.36FE6E9B@webmail.messagingengine.com> Content-Type: multipart/alternative; boundary="------------9C5974FCD99885706AD30A6D" Content-Language: en-GB Archived-At: Subject: Re: [calsify] Updated JSCalendar draft calext-01 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 Mar 2018 10:56:18 -0000 This is a multi-part message in MIME format. --------------9C5974FCD99885706AD30A6D Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Robert, I just noticed that the description of 5.2.8 status is incorrect. > The scheduling status (Section 4.4 > ) of a JSTask defaults to "needs- > action" if omitted. Given the possible values it should actually be the overall progress status of a JSTask. Of course the distinction with "5.2.7 progress" needs to be clear as the individual participants progress. With this is there the opportunity to include the two new task status values as per draft-apthorp-ical-tasks-01.txt and also revise "completed" to be a general purpose status change timestamp. Cheers Adrian On 02/03/18 17:38, Robert Stepanek wrote: > Hi all, > > right before the IETF-101 draft submission deadline, I've uploaded > version 01 > of the > JSCalendar draft. > > There has only been one change to the document: > > * *bySetPosition* *property*: The recurrenceRule type mistakenly did > not include the BYSETPOS parameter of the RFC5545 RRULE. It now > defines the bySetPosition property (see section4.3.1 > ). > > > As always, please let me know of any feedback. > > Cheers, > Robert > > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify --------------9C5974FCD99885706AD30A6D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
Robert,

I just noticed that the description of 5.2.8 status is incorrect.

The scheduling status (Section 4.4) of a JSTask defaults to "needs-
   action" if omitted.

Given the possible values it should actually be the overall progress status of a JSTask. Of course the distinction with "5.2.7 progress" needs to be clear as the individual participants progress.

With this is there the opportunity to include the two new task status values as per draft-apthorp-ical-tasks-01.txt and also revise "completed" to be a general purpose status change timestamp.

Cheers

Adrian

On 02/03/18 17:38, Robert Stepanek wrote:
Hi all,

right before the IETF-101 draft submission deadline, I've uploaded version 01 of the JSCalendar draft.

There has only been one change to the document:
  • bySetPosition property: The recurrenceRule type mistakenly did not include the BYSETPOS parameter of the RFC5545 RRULE. It now defines the bySetPosition property (see section 4.3.1).

As always, please let me know of any feedback.

Cheers,
Robert



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


--------------9C5974FCD99885706AD30A6D-- From nobody Mon Mar 5 02:47:25 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 D3DA3127871; Mon, 5 Mar 2018 02:47:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: calsify@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.73.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152024683781.27938.16916406399074991127@ietfa.amsl.com> Date: Mon, 05 Mar 2018 02:47:17 -0800 Archived-At: Subject: [calsify] I-D Action: draft-ietf-calext-jscalendar-02.txt 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: Mon, 05 Mar 2018 10:47:18 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Calendaring Extensions WG of the IETF. Title : JSCalendar: A JSON representation of calendar data Authors : Neil Jenkins Robert Stepanek Filename : draft-ietf-calext-jscalendar-02.txt Pages : 52 Date : 2018-03-05 Abstract: This specification defines a data model and JSON representation of calendar data that can be used for storage and data exchange in a calendaring and scheduling environment. It aims to be an alternative to the widely deployed iCalendar data format and to be unambiguous, extendable and simple to process. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-calext-jscalendar/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-calext-jscalendar-02 https://datatracker.ietf.org/doc/html/draft-ietf-calext-jscalendar-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-jscalendar-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Mar 5 02:50:58 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 025DB12783A for ; Mon, 5 Mar 2018 02:50:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=messagingengine.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 wCnDE4BFd0P4 for ; Mon, 5 Mar 2018 02:50:55 -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 2B452128961 for ; Mon, 5 Mar 2018 02:50:55 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5489020F0E for ; Mon, 5 Mar 2018 05:50:54 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute1.internal (MEProxy); Mon, 05 Mar 2018 05:50:54 -0500 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=fm2; bh=ttTb/8B0tXssI++y1HLIz0ZhP86Oj L8PJPlBEa3DNsI=; b=ljjpjvd91MD37YL4dvmEOYhT9Pyjwq+XQqdgunBzBKu/t afM+KOgj7dqGSzqvzNVSrq7r9LMxhCvnIPOxS7KQQeFngG8nRw3im4gnRKS9FBxL +Di5heDb5gZPeAJmMiKLv3kgH+7eeDrfXA+ydp7AVhEkv4eCAiq3lgZ3EPp1icll opTIu13fTe+UQyqAboOUg2R6UH63ug6kD/Q4YU8ibAtFrgrup85vGqit3o/+FIPg PR7NYtiAL74Y+X3rz6nHQ1okiav4DkAaQNG6FD17vZ9fV+P2xu+I4otXWHW8lOjv 2Kr8SJZl+bwwvAlLiyviPDTnumL7MUJqrzA5NJvog== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 2233F4276; Mon, 5 Mar 2018 05:50:54 -0500 (EST) Message-Id: <1520247054.2917873.1291727904.2D13638A@webmail.messagingengine.com> From: Robert Stepanek To: calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152024705429178736" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b86e6959 Date: Mon, 05 Mar 2018 11:50:54 +0100 Archived-At: Subject: [calsify] Updated JSCalendar draft calext-02 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: Mon, 05 Mar 2018 10:50:57 -0000 This is a multi-part message in MIME format. --_----------=_152024705429178736 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Hi all, I have just uploaded version 02[1] of the JSCalendar draft. This is the final draft before IETF 101. This version includes an update to the JSTask definition: * The *status* and *progress* properties in JSTask are redefined to consider the iCalendar updates defined in draft-apthorp-ical-tasks[2] (see sections 5.2.7[3] and 5.2.8[4]). Cheers, Robert Links: 1. https://tools.ietf.org/html/draft-ietf-calext-jscalendar-02 2. https://tools.ietf.org/html/draft-apthorp-ical-tasks 3. https://tools.ietf.org/html/draft-ietf-calext-jscalendar-02#section-5.2.7 4. https://tools.ietf.org/html/draft-ietf-calext-jscalendar-02#section-5.2.8 --_----------=_152024705429178736 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
Hi all,

I have just uploaded version 02 of the JSCalendar draft. This is the final draft before IETF 101.

This version includes an update to the JSTask definition:

Cheers,
Robert

--_----------=_152024705429178736-- From nobody Mon Mar 5 02:51:20 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 79BAF129C51 for ; Mon, 5 Mar 2018 02:51:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=messagingengine.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 8jiE7BBtJsP2 for ; Mon, 5 Mar 2018 02:51:18 -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 DF87D128896 for ; Mon, 5 Mar 2018 02:51:17 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 524AE20E40; Mon, 5 Mar 2018 05:51:17 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute1.internal (MEProxy); Mon, 05 Mar 2018 05:51:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=12X9hN hMF1Sl0t5VLr3MlLz5VEVqvvDn+USiVl707dA=; b=k7B/9M4s+phoDYDRer7zBd vi7hWot5Cbk27dXRRyyYeoOrv26W+9ygrvtpmxpTxNdrK5qqZyxyY1dgFRSv5ABW k2eyH9zHt4Hp3+XCcto4Jzxn/gsDLjKLgTTm2mGck+CWYopQkQFIp8GG49obgGrk T69VL7ys8niR15x0HTpyl0z0OBdwQjDwFgBWaU9PkbtmTxMisJnxNF0phoO1glNm mMwVTv8hB+qTfqXuf6Mhu9Hy3wa7vqwP/HBuqWZvhlE7NMWW0lY6jYv0wigJ3Des 44XqWXoyX8QqSiK8EIJne2wFPU6WoT9KYpE4LJNwyKJEoljAkijbzbA5pAf9zuNQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 353134136; Mon, 5 Mar 2018 05:51:17 -0500 (EST) Message-Id: <1520247077.2917865.1291733488.59446999@webmail.messagingengine.com> From: Robert Stepanek To: Adrian Apthorp , calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152024707729178650" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b86e6959 References: <1519983515.3957067.1288884760.36FE6E9B@webmail.messagingengine.com> In-Reply-To: Date: Mon, 05 Mar 2018 11:51:17 +0100 Archived-At: Subject: Re: [calsify] Updated JSCalendar draft calext-01 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: Mon, 05 Mar 2018 10:51:19 -0000 This is a multi-part message in MIME format. --_----------=_152024707729178650 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Hi Adrian, I just uploaded a new draft. On Sat, Mar 3, 2018, at 11:56, Adrian Apthorp wrote: > Robert, > > I just noticed that the description of 5.2.8 status is incorrect. It was defined to be backwards-compatible with iCalendar RFC 5545. Considering the RFC updates in draft-apthorp-ical-tasks I agree it makes sense to redefine them also in JSCalendar. >> The scheduling status (Section 4.4[1]) of a JSTask defaults to "needs- >> action" if omitted.> > Given the possible values it should actually be the overall progress > status of a JSTask. Of course the distinction with "5.2.7 progress" > needs to be clear as the individual participants progress. Done. Please note that my changes are more a basis for discussion than a final decision, considering the deadline for IETF 101 today. > With this is there the opportunity to include the two new task status > values as per draft-apthorp-ical-tasks-01.txt and also revise > "completed" to be a general purpose status change timestamp. I'm not sure what change you have in mind for the COMPLETED property? I could imagine it to be confusing to track general update time-stamps given the property name? Cheers, Robert Links: 1. https://tools.ietf.org/html/draft-ietf-calext-jscalendar-01#section-4.4 --_----------=_152024707729178650 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
Hi Adrian,

I just uploaded a new draft.

On Sat, Mar 3, 2018, at 11:56, Adrian Apthorp wrote:
Robert,

I just noticed that the description of 5.2.8 status is incorrect.

It was defined to be backwards-compatible with iCalendar RFC 5545. Considering the RFC updates in draft-apthorp-ical-tasks I agree it makes sense to redefine them also in JSCalendar.

The scheduling status (Section 4.4) of a JSTask defaults to "needs-
   action" if omitted.

Given the possible values it should actually be the overall progress status of a JSTask. Of course the distinction with "5.2.7 progress" needs to be clear as the individual participants progress.

Done. Please note that my changes are more a basis for discussion than a final decision, considering the deadline for IETF 101 today.

With this is there the opportunity to include the two new task status values as per draft-apthorp-ical-tasks-01.txt and also revise "completed" to be a general purpose status change timestamp.

I'm not sure what change you have in mind for the COMPLETED property? I could imagine it to be confusing to track general update time-stamps given the property name?

Cheers,
Robert
--_----------=_152024707729178650-- From nobody Tue Mar 6 05:09:47 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 AAA38127871 for ; Tue, 6 Mar 2018 05:09:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apthorpia-com.20150623.gappssmtp.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 Rh6hzkJGawgz for ; Tue, 6 Mar 2018 05:09:44 -0800 (PST) Received: from mail-pl0-x22e.google.com (mail-pl0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (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 B917B127775 for ; Tue, 6 Mar 2018 05:09:44 -0800 (PST) Received: by mail-pl0-x22e.google.com with SMTP id v9-v6so11788240plp.12 for ; Tue, 06 Mar 2018 05:09:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apthorpia-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vXqmRxgqMbECFLHm3xyM0Ljs57+vlWfrH1Js6ejjueo=; b=WqRDNl2lD2OVnPJPjfd1zJow2HPUBuzhmXAkD7CXqqggH/wVBTZaEl7NhQK/808giL nKG8zulBEQjhKYuGhFIWcQGF1iu4FJvcq+Gs3dSibts+qJa+ExdV1BhNOh4gnp0UKpqX h7cRdfqfNgfkuEWMSmMEBQGfsqn1OEAmrQYXycjvIUwxSBj7EZz43wi0s8Tk3TF0Co3E JYywDrgi7ACDZSMqPX60R+81CPHpuEeoj46ywpMpn1CNqr+wNOHtPq6uAeyKeeoXz657 UJRXdAwttwmfQNCXqhQoOXtkParneg23dayveZTT0D/z90dq0DgiWPEkkHenW+hoOmZx t2Xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vXqmRxgqMbECFLHm3xyM0Ljs57+vlWfrH1Js6ejjueo=; b=PR2NSavm2H3B2AM5xH67pmMULX/I/cJlGZHIp1gAV4lde/oiPJ1qtNy9b9G1kVT1IN 1pAhzz20VynCrk+/fa6OL8VvArTzXuEN51bEuMsbjb8djtiHjezzJmTi3X9oYEaJPmK/ qwuMj9/3s5HDUxj9HKcg+pBshAizSivDilp4elReLF/hs4mydIzfiLQL38Kgh9QTjXFp 42kSWlQlJmiEuuQDrglVGlHhXgVPfIEUJg+Whs9NlDcWR7MnA3F6I1mHwi7fG8eha7Tu lGr9RjllVyYaqzvyitB8lwiWPeYUe5kMl3kZ8iym6kmKvYpQbpb6k5VKHShDFca1zWaF 9LpQ== X-Gm-Message-State: APf1xPBNQQrwkdjAyYyklIk/5B0BFH+6dRTRafrDUysb9aF4kMDs3ODR A1LLJBBRFYIXgMTWM2bGpbhO9bubIGE= X-Google-Smtp-Source: AG47ELtdO9g4e6yRN4i2/l/fHBpULle1l40JiGGYvJnQPc8zjZdfpnQn2C+vLkrn2s4f5uOS3mSk5A== X-Received: by 2002:a17:902:506:: with SMTP id 6-v6mr17065613plf.365.1520341784085; Tue, 06 Mar 2018 05:09:44 -0800 (PST) Received: from [192.168.2.245] ([138.75.30.234]) by smtp.gmail.com with ESMTPSA id q2sm28059352pfh.103.2018.03.06.05.09.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Mar 2018 05:09:43 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-3654AF94-ABB8-4C6C-AA7D-A7C73D1E6D24 Mime-Version: 1.0 (1.0) From: Adrian Apthorp X-Mailer: iPad Mail (15D100) In-Reply-To: <1520247077.2917865.1291733488.59446999@webmail.messagingengine.com> Date: Tue, 6 Mar 2018 21:09:41 +0800 Cc: calsify@ietf.org Content-Transfer-Encoding: 7bit Message-Id: <49A21F80-A14A-4BCC-97E1-B46F6AC47895@apthorpia.com> References: <1519983515.3957067.1288884760.36FE6E9B@webmail.messagingengine.com> <1520247077.2917865.1291733488.59446999@webmail.messagingengine.com> To: Robert Stepanek Archived-At: Subject: Re: [calsify] Updated JSCalendar draft calext-01 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, 06 Mar 2018 13:09:47 -0000 --Apple-Mail-3654AF94-ABB8-4C6C-AA7D-A7C73D1E6D24 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Robert, Thanks - a couple of comments below: > On 5 Mar 2018, at 6:51 PM, Robert Stepanek wrote: >=20 > Hi Adrian, >=20 > I just uploaded a new draft. >=20 >> On Sat, Mar 3, 2018, at 11:56, Adrian Apthorp wrote: >> Robert, >>=20 >> I just noticed that the description of 5.2.8 status is incorrect. >=20 > It was defined to be backwards-compatible with iCalendar RFC 5545. Conside= ring the RFC updates in draft-apthorp-ical-tasks I agree it makes sense to r= edefine them also in JSCalendar. Understood. However, 5545 does not describe the purpose to indicate the sche= duling status of a task. I was suggesting to reword the purpose. >=20 >>> The scheduling status (Section 4.4) of a JSTask defaults to "needs- >>> action" if omitted. >>=20 >> Given the possible values it should actually be the overall progress stat= us of a JSTask. Of course the distinction with "5.2.7 progress" needs to be c= lear as the individual participants progress. >=20 > Done. Please note that my changes are more a basis for discussion than a f= inal decision, considering the deadline for IETF 101 today. I think the only comment I have is not to define the rules for how a partici= pant progress propagates to the task status. These are likely to be business= rules that are determined by the organiser or defined for a specific type o= f task. They can be manually applied or automated. >=20 >> With this is there the opportunity to include the two new task status val= ues as per draft-apthorp-ical-tasks-01.txt and also revise "completed" to be= a general purpose status change timestamp.=20 >=20 > I'm not sure what change you have in mind for the COMPLETED property? I co= uld imagine it to be confusing to track general update time-stamps given the= property name? Yes, I didn=E2=80=99t complete the thought in my original message. What I wa= s thinking was to rename this property (status-changed) and then it becomes a= pplicable to all status changes. Presumably it can still be mapped to 5545 C= OMPLETED when that status is achieved. Cheers Adrian= --Apple-Mail-3654AF94-ABB8-4C6C-AA7D-A7C73D1E6D24 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Robert,

Thanks - a coupl= e of comments below:

On 5 Mar 2018, at 6:51 PM, Robert Stepanek &= lt;rsto@fastmailteam.com> wr= ote:

Hi Adrian,

I just uploaded a new draft.

On Sat, Mar 3, 2018, at 11:56, Adrian Apthorp wrote:
Robert,

I just noticed that the description of 5.2.8 status is incorrect.
<= /div>

It was defined to be backwards-compatible with iCalendar RFC 5545. Cons= idering the RFC updates in draft-apthorp-ical-tasks I agree it makes sense t= o redefine them also in JSCalendar.

Understood. However, 5545 does not describe the purpose to indicate t= he scheduling status of a task. I was suggesting to reword the purpose.

The scheduling stat=
us (Section 4.4) of a JSTask defaults to "needs-
   action" if omitted.

Given the possible values it should actually be the overall progress status of a JSTask. Of course the distinction with "5.2.7 progress" needs to be clear as the individual participants progress.

Done. Please note that my changes are more a basis for discussion than a= final decision, considering the deadline for IETF 101 today.

I think the only comment I have is not to d= efine the rules for how a participant progress propagates to the task status= . These are likely to be business rules that are determined by the organiser= or defined for a specific type of task. They can be manually applied or aut= omated.


With this is there the opportunity to includ= e the two new task status values as per draft-apthorp-ical-tasks-01.txt and also revise "completed" to be a general purpose status change timestamp.

I'm not sure what change you have in mind for the COMPLETED property? I= could imagine it to be confusing to track general update time-stamps given t= he property name?

Yes, I did= n=E2=80=99t complete the thought in my original message. What I was thinking= was to rename this property (status-changed) and then it becomes applicable= to all status changes. Presumably it can still be mapped to 5545 COMPLETED w= hen that status is achieved.

Cheers

=
Adrian
= --Apple-Mail-3654AF94-ABB8-4C6C-AA7D-A7C73D1E6D24-- From nobody Sun Mar 11 15:47:44 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 29FCB1250B8 for ; Sun, 11 Mar 2018 15:47:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 FfLyP8Oyl_p8 for ; Sun, 11 Mar 2018 15:47:41 -0700 (PDT) Received: from maple.morsemedia.net (maple.morsemedia.net [72.51.43.139]) (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 8B1BB1201F8 for ; Sun, 11 Mar 2018 15:47:41 -0700 (PDT) Received: from 47-208-67-174.erkacmtk02.res.dyn.suddenlink.net ([47.208.67.174]:34220 helo=[192.168.0.106]) by maple.morsemedia.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1ev9kf-000LGk-9R; Sun, 11 Mar 2018 15:47:37 -0700 From: Dave.Thewlis@calconnect.org Content-Type: multipart/alternative; boundary="Apple-Mail=_3BCF689D-3804-47AF-B62F-66C82B5586B7" Reply-To: Thewlis Dave Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Message-Id: <0BEBBDAF-68DC-4CE2-B160-3905E30B6B7D@calconnect.org> Date: Sun, 11 Mar 2018 15:47:36 -0700 To: caldeveloper-l mailing list , "calsify@ietf.org" X-Mailer: Apple Mail (2.3445.5.20) X-MorseMedia-MailScanner-Information: Please contact the ISP for more information X-MorseMedia-MailScanner-ID: 1ev9kf-000LGk-9R X-MorseMedia-MailScanner: Found to be clean X-MorseMedia-MailScanner-SpamCheck: X-MorseMedia-MailScanner-From: dave.thewlis@calconnect.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - maple.morsemedia.net X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - calconnect.org X-Get-Message-Sender-Via: maple.morsemedia.net: authenticated_id: dave@dcta.com X-Authenticated-Sender: maple.morsemedia.net: dave@dcta.com Archived-At: Subject: [calsify] Registration is open for CalConnect XLII in Tokyo, Japan, June4-8, 2018, hosted by Jorte 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: Sun, 11 Mar 2018 22:47:43 -0000 --Apple-Mail=_3BCF689D-3804-47AF-B62F-66C82B5586B7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Registration is now open for CalConnect XLII in Tokyo, Japan, June 4-8, = 2018, hosted by Jorte The CalConnect XLII web page is located at = https://www.calconnect.org/events/.calconnect-xlii-june-04-08-2018 = and = contains lodging information, airport and transfer information, meeting = venue, etc. =20 The meeting venue is at Sogetsu Hall = , Akasaka, Tokyo. The venue is = about a five minute walk from the conference hotel, Hotel Monterey = Akasaka . The hotel may be booked immediately, see = https://www.calconnect.org/events/.calconnect-xlii-june-04-08-2018#lodging= = for more information and information. You must book by the end of = April to receive the CalConnect rate, and you must book via the e-mail = address provided on this Lodging page. The Interoperability Test Event and Developers Forum will take place on = our usual schedule beginning Monday morning and going through Wednesday = noon. The Conference will begin Wednesday after lunch and run through = Friday mid-afternoon. There will be some special introductory sessions = on CalConnect and calendaring standards currently planned for Monday, = and some presentations from JEDC (Japan Event Data Consortium) probably = on Wednesday afternoon. =20 We will be posting detailed schedules and agendas on the event web page = once they are available, and expect that they may evolve over time.=20 Registration information is at = https://www.calconnect.org/events/event-registration-payment = and is = also linked from the event web page. =20 As always, please let me know if you have any questions. =20 See you in Tokyo! 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=_3BCF689D-3804-47AF-B62F-66C82B5586B7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Registration is now open  for CalConnect = XLII in Tokyo, Japan, June 4-8, 2018, hosted by Jorte

The CalConnect XLII web = page is located at https://www.calconnect.org/events/.calconnect-xlii-june-04-08-2= 018 and contains lodging information, airport and transfer = information, meeting venue, etc.  

The  meeting venue is at Sogetsu Hall, Akasaka, Tokyo. The venue is about a five = minute walk from the conference hotel, Hotel Monterey Akasaka.

The hotel may be booked immediately, = see https://www.calconnect.org/events/.calconnect-xlii-june-04-08-2= 018#lodging for more information and information. You must book by the end of April = to receive the CalConnect rate, and you must book via = the e-mail address provided on this Lodging page.

The Interoperability = Test Event and Developers Forum will take place on our usual schedule = beginning Monday morning and going through Wednesday noon.  The = Conference will begin Wednesday after lunch and run through Friday = mid-afternoon.  There will be some special introductory sessions on = CalConnect and calendaring standards currently planned for Monday, and = some presentations from JEDC (Japan Event Data Consortium) probably on = Wednesday afternoon.  

We will be posting detailed schedules and agendas on the = event web page once they are available, and expect that they may evolve = over time. 

Registration = information is at https://www.calconnect.org/events/event-registration-payment and is also linked from the event web page.  


As always, please let me know if you have any questions. =  

See you = in Tokyo!

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=_3BCF689D-3804-47AF-B62F-66C82B5586B7-- From nobody Sun Mar 18 07:39:28 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 4917112711A for ; Sun, 18 Mar 2018 07:39:27 -0700 (PDT) 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 2ln2KyTh2ZUJ for ; Sun, 18 Mar 2018 07:39:25 -0700 (PDT) Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 A2BE4126E01 for ; Sun, 18 Mar 2018 07:39:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1521383965; 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=Vqe/uScdH2dbKmuJmlU8SLA5z3hWYHLUo8wXwcH8oAs=; b=ek85HjjQkVBoa53ydDn/FuUHXfGn1LdtM7BtfmKBR0a9sZj3/3MBJhk2rWiNfftV k8qoIuEKudMquQvSvKAOqU4MShe1VUpnuVAuuPsrSvTnWFAnq2MFsh2E1hC3gpul NNeCnBLqRSrna+ssyMGzmxAykm7t+eExhzZ0ULXxb2U=; X-AuditID: c618062d-8d7ff70000004288-39-5aae7a1c6695 Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 40.D0.17032.C1A7EAA5; Sun, 18 Mar 2018 15:39:25 +0100 (CET) Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0382.000; Sun, 18 Mar 2018 10:39:24 -0400 From: Daniel Migault To: "calsify@ietf.org" CC: "calext-chairs@ietf.org" Thread-Topic: Calendaring Extensions Meeting @ IETF101 Thread-Index: AdO+xrLkRtcnTrt1Q0eWpGEr7BRFUw== Date: Sun, 18 Mar 2018 14:39:23 +0000 Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852@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.221] Content-Type: multipart/alternative; boundary="_000_2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852eusaamb107erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBLMWRmVeSWpSXmKPExsUyuXRPuK5s1boogz/FFgsX/me22PSimdWB yWPJkp9MAYxRXDYpqTmZZalF+nYJXBm9/fPZCybKV0y65tnAuEG6i5GTQ0LAROLh0lcsXYxc HEICRxglJvRNY4RwljNKvL84kwmkik3ASKLtUD87iC0ioCmx+2oPaxcjBwezgKnEuvkaIGFh AUOJO6d2M0KUmEk8urSMDcLWk2j6+QPMZhFQlejsuM4KYvMK+Eo0fdvFAmIzCohJfD+1BmwV s4C4xK0n85kgjhOQWLLnPDOELSrx8vE/VghbWeL6qissEPX5ElM+tTNCzBSUODnzCcsERqFZ SEbNQlI2C0kZRFxHYsHuT2wQtrbEsoWvmWHsMwceMyGLL2BkX8XIUVpckJObbmSwiREY/sck 2HR3MN6f7nmIUYCDUYmHVz1jXZQQa2JZcWXuIUYJDmYlEV6DKKAQb0piZVVqUX58UWlOavEh RmkOFiVx3jOevFFCAumJJanZqakFqUUwWSYOTqkGxr7jNtLGjhIFvjq/fBYanbY/s0jmnbiu UKrMihOvtDdln7T9MTOAf9LNta+v/Yv5tPWdNBev4W190ZpZR8o4V712qrTw5d9tNbXF8WGD dJbA/0cey9+q2MXM7pvgvHeF1ZPX29iW7tCzi1G4pRS29EXGRjWTOW1KYWdj7skkzzqqe70m 6/ieaiWW4oxEQy3mouJEAKmtZdB7AgAA Archived-At: Subject: [calsify] Calendaring Extensions Meeting @ IETF101 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: Sun, 18 Mar 2018 14:39:27 -0000 --_000_2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852eusaamb107erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi everyone, This is just to remind you that we are meeting on Thursday, March 22, 2018 = from 11:00 to 11:30 as indicated in the IETF agenda [1]. The current agenda= for the Calendaring Extensions WG meeting can be found here [2]. Please u= pload or send us your presentation by Tuesday March 20. If you want to add an agenda item, feel free to contact us. Calconnect are = more than welcome to join the session of the face-to-face meeting. Yours, Your co-chairs [1] https://datatracker.ietf.org/meeting/agenda.html [2] https://datatracker.ietf.org/meeting/101/materials/agenda-101-calext --_000_2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852eusaamb107erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi everyone,

 

This is just to remind you that we are meeting on Th= ursday, March 22, 2018 from 11:00 to 11:30 as indicated in the IETF agenda = [1]. The current agenda for the  Calendaring Extensions WG meeting can= be found here [2]. Please upload or send us your presentation by Tuesday March 20.

 

If you want to add an agenda item, feel free to cont= act us. Calconnect are more than welcome to join the session of the face-to= -face meeting.

 

Yours,

Your co-chairs

 

 

[1] https://datatracker.ietf.org/meeting/agenda.html

[2] https://datatracker.ietf.org/meeting/101/materials/agenda-101-calext

 

--_000_2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852eusaamb107erics_-- From nobody Wed Mar 21 08:27:55 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 93C1212D95C; Wed, 21 Mar 2018 08:27:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=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=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D0GTfy7DgBlM; Wed, 21 Mar 2018 08:27:52 -0700 (PDT) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 295331275F4; Wed, 21 Mar 2018 08:27:52 -0700 (PDT) Received: by mail-lf0-x232.google.com with SMTP id x205-v6so8484249lfa.0; Wed, 21 Mar 2018 08:27:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AV2aelJqt0wHbRAybweyGIyEXFjhwlhqLuieu/8cOWs=; b=keu5jPGhBU0XSd2eyWl5fFmVNOC0DGqD4uM3b2z6Ppig/TuQh4CPhynCiZPdmU0c7s jSPw5YQUqlejcSaUtM/9ijAt2cqPCU0WW8UuPQ5bRzWp7fGcl1b5bmr8DtBC7O8f51ld 1pD/ePbFir2wJfQGMrNSbQtjA5uFTa/WudqGKO8glqhXrU/IwLe8at6pivZyRCHq/XGR m7UG2OfzSdz0kX9huP9tgskrX3EN05rWJ9EHpbzF+XlnOhoPRrEoIpUXlGnE+FrWSUAf i/csY0gsPrQpfpXHCsAvah2QOHuJRzjs3HWywg00c6kvl+z1O2rmIrnaln/LGsXgjkak 5suQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AV2aelJqt0wHbRAybweyGIyEXFjhwlhqLuieu/8cOWs=; b=JQdJObQz8mXjEWvJXiCf4m+N8sesEWMp1+cCQFB9vIwAhyDEnazH+/WZeuV8SggnwO OSSqmpZ7/lJ5I5bBLWIliG4D8q4E6lsH5Pn6ut8wF9Q5XLvR7vXoVSKtLHSYXrA4udvj 316WfIkUPfUOAlYS85WCDICBb7h5fBNgx5JPfU7CMqwlYk7a+V4sDYGFmXgTctcwOm9D RoaQRmnPl9Butz/cbCpZLyAWuq8RZqhHVcLeVyDhkz1zcD/IoUrAebLtU7lohBEnu8XK 6STp99Rpu6D8sfogtHvdn61L47frfpLINMXF495mgTgAll58kvBUQgR8/fD77hKnl7xI 0IRw== X-Gm-Message-State: AElRT7GlAVSiWSe8GUO/YFsvDUzOYJPUOeCduYbjJizpblV5mLgTS2lZ U3p8kuRIeH2nn7542zsoFGeDLFO1z+wXgfdDg/U= X-Google-Smtp-Source: AG47ELu8jtju5ssEbSuNTpX19f1Qc/7g9hQfd26GxG6JOK40la00aG2+83ZNWX672sPk8OnW6gvhzIwEZbgo6KdIxGA= X-Received: by 2002:a19:7103:: with SMTP id m3-v6mr13786019lfc.29.1521646070237; Wed, 21 Mar 2018 08:27:50 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 10.46.129.5 with HTTP; Wed, 21 Mar 2018 08:27:49 -0700 (PDT) In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852@eusaamb107.ericsson.se> References: <2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852@eusaamb107.ericsson.se> From: Daniel Migault Date: Wed, 21 Mar 2018 11:27:49 -0400 X-Google-Sender-Auth: Sj9APeG3dUwZew3xNl0G5WPuLRA Message-ID: To: "calsify@ietf.org" Cc: "calext-chairs@ietf.org" Content-Type: multipart/alternative; boundary="0000000000007d8e040567edd5c5" Archived-At: Subject: Re: [calsify] Calendaring Extensions Meeting @ IETF101 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: Wed, 21 Mar 2018 15:27:55 -0000 --0000000000007d8e040567edd5c5 Content-Type: text/plain; charset="UTF-8" Hi everyone, We are looking for volunteers for minutes and Jabber scribes. Feel free to volunteer! Yours, Daniel On Sun, Mar 18, 2018 at 10:39 AM, Daniel Migault < daniel.migault@ericsson.com> wrote: > Hi everyone, > > > > This is just to remind you that we are meeting on Thursday, March 22, 2018 > from 11:00 to 11:30 as indicated in the IETF agenda [1]. The current agenda > for the Calendaring Extensions WG meeting can be found here [2]. Please > upload or send us your presentation by Tuesday March 20. > > > > If you want to add an agenda item, feel free to contact us. Calconnect are > more than welcome to join the session of the face-to-face meeting. > > > > Yours, > > Your co-chairs > > > > > > [1] https://datatracker.ietf.org/meeting/agenda.html > > [2] https://datatracker.ietf.org/meeting/101/materials/agenda-101-calext > > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify > > --0000000000007d8e040567edd5c5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi everyone,

We are looking for voluntee= rs for minutes and Jabber scribes. Feel free to volunteer!

You= rs,
Daniel

On Sun, Mar 18, 2018 at 10:39 AM, Daniel Migault <d= aniel.migault@ericsson.com> wrote:

Hi everyone,

=C2=A0

This is just to remind you that we are meeting on Th= ursday, March 22, 2018 from 11:00 to 11:30 as indicated in the IETF agenda = [1]. The current agenda for the =C2=A0Calendaring Extensions WG meeting can= be found here [2]. Please upload or send us your presentation by Tuesday March 20.

=C2=A0

If you want to add an agenda item, feel free to cont= act us. Calconnect are more than welcome to join the session of the face-to= -face meeting.

=C2=A0

Yours,

Your co-chairs

=C2=A0

=C2=A0

[1] https://datatracker.ietf.org/meeting/agenda.html

[2] https://datatracker.ietf.org/meeting/101/materials/agenda-101-cal= ext

=C2=A0


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

--0000000000007d8e040567edd5c5-- From nobody Wed Mar 21 09:25:23 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 35DF512E043; Wed, 21 Mar 2018 09:25:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=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=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3jBkIxS0KZsX; Wed, 21 Mar 2018 09:25:19 -0700 (PDT) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 C11E312E035; Wed, 21 Mar 2018 09:25:18 -0700 (PDT) Received: by mail-lf0-x22f.google.com with SMTP id m16-v6so5020675lfc.4; Wed, 21 Mar 2018 09:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=q34SOv2wp1orZa6v0J7/a+cBgNdjTaSukeyyMfvg5Ig=; b=daX3/U9Q09DBWGzyFR1IqFFTf4naFq8xFxWGPHmKRp1SMlawmpy9RW1UmqqEQLROmf 1amD9oNw/9FPT65E6m04NnGKpj2BpM2lXxLLXLz5e+th4wROZv/UwSRuKQEIJJy/cykf ixdBOXB5sKLY25aVquOd0jgpgkUHt3ITIhDa8+p/1U4KOxd752Jc7H0l4PPRA6WEjc/9 tZ8HH3lcQkhdwirctTijEsXqTVP93c0rJCrLlhpnZ5ypDZjKcFW74zctesuJLFMQkYmP v8HUb8LDCKY0J4DsPpFHBRFe6xRQ6+3TfH/NK/AcbmP6fZ8s3TA5xUoXXoOD0K5rZleu xOlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=q34SOv2wp1orZa6v0J7/a+cBgNdjTaSukeyyMfvg5Ig=; b=GHTcq+TCwmlGyJiaP5F3MPmzZhjQ8ZcuMd70/QbPizuQ+855QtuLnzkLntooDFx2QG b+s+T1Byhdw4wTItCJVJ6eRHsRubydeL23Te2x01RdcT56EKdXlcgaVz96Pxe+2pnZn4 pKSLiwnGYrO72gHzzZCc2iJYbCIV+50kcMeBZ2l2UnVO9Ns1utbxPJRJOPjl5r4cb9gT CKBTG0jDhvAnBvfOg/parzklWOejy5RQBJz+rszxIxzur2636nPg2EcmAtKmqfHkS8yt nC8L1Wf36dMPb8ntGfmGwTIvjiw1+2d/+9aOwU8hmgA5OoUx2CdTZRcsi8FBNbETrZ10 NxKw== X-Gm-Message-State: AElRT7Eeloq/4TEzE2AfbFTf/B2twxiv3ztaPe6Izx2+sTBjnoTNxVa8 L2y8znXNDuJ0Rs/pteWY6hF9NbhWe2DTUYPqpXW/vA== X-Google-Smtp-Source: AG47ELvdqS5py+dFtUpNajTubzz2k8NrmhkHH5O7CEQnp4lexbvJS0i45EVT6hlcYwqhCO6aR67NRPo3985PO0aJ5So= X-Received: by 2002:a19:5c4b:: with SMTP id q72-v6mr15053229lfb.126.1521649516897; Wed, 21 Mar 2018 09:25:16 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 10.46.129.5 with HTTP; Wed, 21 Mar 2018 09:25:16 -0700 (PDT) In-Reply-To: References: <2DD56D786E600F45AC6BDE7DA4E8A8C118DF3852@eusaamb107.ericsson.se> From: Daniel Migault Date: Wed, 21 Mar 2018 12:25:16 -0400 X-Google-Sender-Auth: _EohYtz6hmeSKxQw4URjt4bFBqQ Message-ID: To: "calsify@ietf.org" Cc: "calext-chairs@ietf.org" Content-Type: multipart/alternative; boundary="000000000000ed70ff0567eea274" Archived-At: Subject: Re: [calsify] Calendaring Extensions Meeting @ IETF101 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: Wed, 21 Mar 2018 16:25:21 -0000 --000000000000ed70ff0567eea274 Content-Type: text/plain; charset="UTF-8" Philipp, It woudl be good to sum up the problem / status of draft-ietf-calext-caldav-attachments-03 If you are not attending teh meeting, feel free to send me a note on it. Yours, Daniel On Wed, Mar 21, 2018 at 11:27 AM, Daniel Migault < daniel.migault@ericsson.com> wrote: > Hi everyone, > > We are looking for volunteers for minutes and Jabber scribes. Feel free to > volunteer! > > Yours, > Daniel > > On Sun, Mar 18, 2018 at 10:39 AM, Daniel Migault < > daniel.migault@ericsson.com> wrote: > >> Hi everyone, >> >> >> >> This is just to remind you that we are meeting on Thursday, March 22, >> 2018 from 11:00 to 11:30 as indicated in the IETF agenda [1]. The current >> agenda for the Calendaring Extensions WG meeting can be found here [2]. >> Please upload or send us your presentation by Tuesday March 20. >> >> >> >> If you want to add an agenda item, feel free to contact us. Calconnect >> are more than welcome to join the session of the face-to-face meeting. >> >> >> >> Yours, >> >> Your co-chairs >> >> >> >> >> >> [1] https://datatracker.ietf.org/meeting/agenda.html >> >> [2] https://datatracker.ietf.org/meeting/101/materials/agenda-101-calext >> >> >> >> _______________________________________________ >> calsify mailing list >> calsify@ietf.org >> https://www.ietf.org/mailman/listinfo/calsify >> >> > --000000000000ed70ff0567eea274 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Philipp,

It woudl be goo= d to sum up the problem / status of
=20 =20

If you are not attending teh meeting, feel free to = send me a note on it.

Yours,
Daniel

On Wed, Mar 21, 2018 at= 11:27 AM, Daniel Migault <daniel.migault@ericsson.com> wrote:
H= i everyone,

We are looking for volunteers for minutes and Jabber sc= ribes. Feel free to volunteer!

Yours,
Daniel

On Sun, Mar 18, 2018 at 10:39 AM, Daniel Migault = <daniel= .migault@ericsson.com> wrote:

Hi everyone,

=C2=A0

This is just to remind you that we are meeting on Th= ursday, March 22, 2018 from 11:00 to 11:30 as indicated in the IETF agenda = [1]. The current agenda for the =C2=A0Calendaring Extensions WG meeting can= be found here [2]. Please upload or send us your presentation by Tuesday March 20.

=C2=A0

If you want to add an agenda item, feel free to cont= act us. Calconnect are more than welcome to join the session of the face-to= -face meeting.

=C2=A0

Yours,

Your co-chairs

=C2=A0

=C2=A0

[1] https://datatracker.ietf.org/meeting/agenda.html

[2] https://datatracker.ietf.org/meeting/101/materials/agenda-101-cal= ext

=C2=A0


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


--000000000000ed70ff0567eea274-- From nobody Thu Mar 22 04:42:59 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 DA14A127873 for ; Thu, 22 Mar 2018 04:42:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.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 DAmOoenb-cgD for ; Thu, 22 Mar 2018 04:42:55 -0700 (PDT) Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 C467D124235 for ; Thu, 22 Mar 2018 04:42:55 -0700 (PDT) Received: from dhcp-8056.meeting.ietf.org (dhcp-8056.meeting.ietf.org [31.133.128.86]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w2MBgqob006092 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 22 Mar 2018 04:42:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1521718975; bh=tgwuW06Yqww4ZEdOzENYTCV3jBNevl0yS/IdT9dy/Io=; h=To:From:Subject:Date; b=aACz5ynkuKWlCNOI3v0O+vdzabmPIYM+vm9gEENVZxFcQSIqyBcQrqH2TzVomfld8 MLog0L1qvbhVryfSq9RsAPxOAW9496MRXq9RORakrxsqQy5OrOexMjGDzT4ib8iaLE xYK2E4rqPQEEtmHo8Evhm7oClo+7iJ4WHKKuxgGY= To: calsify@ietf.org From: Jim Fenton Message-ID: <859af752-3dca-b709-d723-031bc6420dfb@bluepopcorn.net> Date: Thu, 22 Mar 2018 04:42:50 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [calsify] Minutes from calext meeting at IETF 101 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, 22 Mar 2018 11:42:57 -0000 calext minutes 22 March 2018 Started 11:03 am Note Well reviewed ----- draft-ietf-calext-caldav-attachments-03 Alexey and Ken Murchison: Julian raised issues so it has gone Informational. content disposition header issue should be brought to httpbis working group as a question. Document has been in limbo quite a while so will probably return it to the working group for another Last Call. Action: Ken to provide new revision, then move back to WG. ----- draft-ietf-calext-eventpub-extensions-05 draft-ietf-calext-ical-relations-03 Mike Douglass feels documents are pretty much ready to go. Need information on implementations, experience with protocols. Mike will revise by mid-April, at least 3 reviews expected. Plan to do this by end April ----- draft-ietf-calext-jscalendar: Robert Stepanek - FastMail Calendating data model and exchange format using I-JSON. New semantics and representation for calendaring data. 2-3 years feedback and revision from IETF and CalConnect. Planning to issue minor update, go to WGLC before IETF 102. Chair requests feedback on implementations on-list. ----- AOB Alexey asks Ken Murchison about CalConnect. Ken says they are looking to speed up the process of IETF review of CalConnect products. Discussion of liaison relationship with CalConnect. This is a minor liaison relationship that shouldn't require an RFC. Trying to get Last Call comments from CalConnect members, but some of them are concerned with leaking proprietary info. CalConnect needs to understand that if they want IETF publication, they need to provide reviews. Adjourned 11:39 am From nobody Thu Mar 22 04:59:02 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 4DCE412D88A for ; Thu, 22 Mar 2018 04:58:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.301 X-Spam-Level: X-Spam-Status: No, score=-4.301 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_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 BncLNWxWwGw7 for ; Thu, 22 Mar 2018 04:58:51 -0700 (PDT) Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 3CE3E12D86E for ; Thu, 22 Mar 2018 04:58:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1521719930; 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=gDA9NkhEXPkP6FXEc2an2bi07JFe+YW7uAUxb720zsI=; b=dLCSo8kiFqnV0AqC22d9MZZ0ACu8Qu5GA2lzjAUzayTj9TlxMJomdy7/9U+Gz3Oi D0ftUu22OtQjxOt2noQjsK5Tpn95TlVqVoUV5L+5HmEFxb/0CZpnKqW95wM5pzXd m89Fvtji6HOrazCh4a7hmDuhAdah8sVzqQupJyu16do=; X-AuditID: c618062d-8efff70000004288-60-5ab39a797c71 Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 1C.67.17032.97A93BA5; Thu, 22 Mar 2018 12:58:50 +0100 (CET) Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0382.000; Thu, 22 Mar 2018 07:58:49 -0400 From: Daniel Migault To: Jim Fenton , "calsify@ietf.org" Thread-Topic: [calsify] Minutes from calext meeting at IETF 101 Thread-Index: AQHTwdLwt2HcEQHpL0+BHK1gn0rOjqPcJdUg Date: Thu, 22 Mar 2018 11:58:49 +0000 Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118DF5C6C@eusaamb107.ericsson.se> References: <859af752-3dca-b709-d723-031bc6420dfb@bluepopcorn.net> In-Reply-To: <859af752-3dca-b709-d723-031bc6420dfb@bluepopcorn.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.216] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyuXRPoG7VrM1RBjeeCVtsetHMavGtcxaz A5PH01WvmDyWLPnJFMAUxWWTkpqTWZZapG+XwJVx6fV2toKTQhUnbr5kbGCcxd/FyMkhIWAi 0bb/C1MXIxeHkMARRonm0zegnOWMEns+z2ABqWITMJJoO9TPDmKLCPhJtD08wQZiCwvYSTRt eMEMEbeX2P7yNSuEbSRx4vYfxi5GDg4WAVWJr612IGFeAV+Jg7uPM4LYQgJOEguX72ACKeEU cJY41mkNEmYUEJP4fmoNE4jNLCAucevJfCaIOwUkluw5zwxhi0q8fPyPFcJWlpj47BsjRL2O xILdn9ggbG2JZQtfM0OsFZQ4OfMJywRGkVlIxs5C0jILScssJC0LGFlWMXKUFhfk5KYbGWxi BIb8MQk23R2M96d7HmIU4GBU4uFV6dkcJcSaWFZcmXuIUYKDWUmE95AmUIg3JbGyKrUoP76o NCe1+BCjNAeLkjjvGU/eKCGB9MSS1OzU1ILUIpgsEwenVANjzIYDfELrUifsaEq+x5xhphn7 dlV8yJ++OyZvI1aypWh7Ojro2R4PTf5wTpQ5raT39M+WkOtNNxIOPXaPXtT3aL+KEct2Zxme L186WQ0vyzE1bDxyJjxqTnzho+275FNsVv1oiuadcERT4+g/1iMBOVcbLu+qXFXbvGvOVeGM bUbqMttK9VWVWIozEg21mIuKEwFk1fbNdQIAAA== Archived-At: Subject: Re: [calsify] Minutes from calext meeting at IETF 101 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, 22 Mar 2018 11:58:53 -0000 Thank you very much Jim for providing the minutes. I am inviting the member= to let me know if there is anything that needs to be corrected. The curren= t text has been posted on the datatracker.=20 We also thank you all for the participation, and this meeting was from my p= oint of view useful.=20 Yours,=20 Daniel -----Original Message----- From: calsify [mailto:calsify-bounces@ietf.org] On Behalf Of Jim Fenton Sent: Thursday, March 22, 2018 11:43 AM To: calsify@ietf.org Subject: [calsify] Minutes from calext meeting at IETF 101 calext minutes 22 March 2018 Started 11:03 am Note Well reviewed ----- draft-ietf-calext-caldav-attachments-03 Alexey and Ken Murchison: Julian raised issues so it has gone Informational= . content disposition header issue should be brought to httpbis working gro= up as a question. Document has been in limbo quite a while so will probably= return it to the working group for another Last Call. Action: Ken to provi= de new revision, then move back to WG. ----- draft-ietf-calext-eventpub-extensions-05 draft-ietf-calext-ical-relations-03 Mike Douglass feels documents are pretty much ready to go. Need information= on implementations, experience with protocols. Mike will revise by mid-Apr= il, at least 3 reviews expected. Plan to do this by end April ----- draft-ietf-calext-jscalendar: Robert Stepanek - FastMail Calendating data model and exchange format using I-JSON. New semantics and = representation for calendaring data. 2-3 years feedback and revision from I= ETF and CalConnect. Planning to issue minor update, go to WGLC before IETF = 102. Chair requests feedback on implementations on-list. ----- AOB Alexey asks Ken Murchison about CalConnect. Ken says they are looking to sp= eed up the process of IETF review of CalConnect products. Discussion of liaison relationship with CalConnect. This is a minor liaison= relationship that shouldn't require an RFC. Trying to get Last Call commen= ts from CalConnect members, but some of them are concerned with leaking pro= prietary info. CalConnect needs to understand that if they want IETF public= ation, they need to provide reviews. Adjourned 11:39 am _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify