From nobody Fri Jan 12 03:00: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 0A52B12E052 for ; Fri, 12 Jan 2018 03:00:45 -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 VlYqLTMkh9NI for ; Fri, 12 Jan 2018 03:00:42 -0800 (PST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B641612E04A for ; Fri, 12 Jan 2018 03:00:42 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0D55F20FDE for ; Fri, 12 Jan 2018 06:00:42 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute1.internal (MEProxy); Fri, 12 Jan 2018 06:00:42 -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=fm1; bh=v20/+OkoMnlVWcHr+iHsCXrtpaIOt TbiAyY0xW1XpZo=; b=izrH5rH8ywInjX0pL/lEP3LR7awsku/7ain99gl7zRtrq WDsDAT6h+YmL+lDrEwln4i1eGimsXsbKvHGAvZmJxLq1zg13zNpEl70QnFMndq3O 8b+HIM9hZYo5AtC3/mTsoLrWMDDSL0k+esqASmh5bqRqM/07MGpW+HPWSUZrXtB2 +jHD0q9WKeCU7/CuGDKDRymqBge0m75wDnHVaEiQbJUXXlCYVFeSEfOQR8eQGhuk YFb7rcKyamWZKP0td49nQEvRj4WRCH5NftTsmfxndB83fx1nTWKlgppX7MxtNWul Tj8ATqYt9uUPkySsnlJ5wiXzYpM418J4ok4PECq5w== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id DD7FB4009; Fri, 12 Jan 2018 06:00:41 -0500 (EST) Message-Id: <1515754841.2594266.1232957544.5822EEC0@webmail.messagingengine.com> From: Robert Stepanek To: calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_151575484125942661" X-Mailer: MessagingEngine.com Webmail Interface - ajax-75de3051 Date: Fri, 12 Jan 2018 12:00:41 +0100 Archived-At: Subject: [calsify] JSCalendar draft version 4 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, 12 Jan 2018 11:00:45 -0000 This is a multi-part message in MIME format. --_----------=_151575484125942661 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Hi all, I have just posted version 4 of the JSCalendar RFC draft. This version includes changes to layout and wording as well as to the content of the specification. Notable changes are: * *Re-organise and rephrase sections 1-4*: the layout of these sections has been split into 5 sections. New section 2 introduces JSCalendar objects. The sections have been rephrased for clarity and consistency. * *htmlDescription*: the definition of this property now defines how to handle untrusted domains (section 4.2.3.[1]). * *htmlBody alerts*: the EmailAction alert definition now includes an additional property for HTML email bodies (section 4.5.2.[2]). * *URI Template in replyTo 'web'*: the definition of the replyTo 'web' method changes the property value from URI to a RFC 6570 level 1 URI Template (section 4.4.4.[3]). * *audioLinkId replaced with mediaLinkId*: the DisplayAction alert property 'audioLinkId' is replaced by the multi-valued 'mediaLinkIds' property to allow for rich-media alerts (section 4.5.2.[4]). * *byDate renamed to byMonthDay*: the Recurrence byDate property is renamed to byMonthDay for consistency with the RRULE definition (section 4.3.1.[5]). * *useDefaultAlerts for unknown defaults*: the definition now specifies how to handle alerts if no user-defaults are set or cannot be determined (section 4.5.1.[6]). * *White-list localized properties*: the original list of forbidden properties to localise has been changed to a white-list of properties that can be localised (section 4.6.1.[7]). * *Forbid location.timeZone for rel=start*: the specification forbids now to set the location.timeZone property for location with rel=start (section 4.2.4.[8]). Planned for the next version: * *More examples!* I plan to add a bunch of illustrative examples for the major (and probably some obscure) use-cases. As always, Neil and I very much look forward to your feedback. Cheers, Robert Links: 1. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.2.3 2. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.5.2 3. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.4.4 4. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.5.2 5. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.3.1 6. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.5.1 7. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.6.1 8. https://tools.ietf.org/html/draft-jenkins-jscalendar-04#section-4.2.4 --_----------=_151575484125942661 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Hi all,

I have just posted version 4 of the JSCalendar RFC draft. This version= includes changes to layout and wording as well as to the content of the s= pecification.

Notable changes are:

  • Re-organise and rephrase sections 1-4: the layout of these s= ections has been split into 5 sections. New section 2 introduces JSCalendar= objects. The sections have been rephrased for clarity and consistency.&nbs= p;
  • htmlDescription: the definition of this property now = defines how to handle untrusted domains (section 4.2.3.).
  • htmlBody alerts: the EmailAction alert definition now includes= an additional property for HTML email bodies (section 4.5.2.).<= br>
  • URI Template in replyTo 'web': the definition of the rep= lyTo 'web' method changes the property value from URI to a RFC 6570 level 1= URI Template (section 4.4.4.).
  • audioLinkId repl= aced with mediaLinkId: the DisplayAction alert property 'audioLinkId' i= s replaced by the multi-valued 'mediaLinkIds' property to allow for rich-me= dia alerts (section 4.5.2.).
  • byDate renamed to by= MonthDay: the Recurrence byDate property is renamed to byMonthDay for c= onsistency with the RRULE definition (section 4.3.1.).
  • <= li>useDefaultAlerts for unknown defaults: the definition now specifi= es how to handle alerts if no user-defaults are set or cannot be determined= (section 4.5.1.).
  • White-list localized propertie= s: the original list of forbidden properties to localise has been chang= ed to a white-list of properties that can be localised (section 4.6.= 1.).
  • Forbid location.timeZone for rel=3Dstart: the s= pecification forbids now to set the location.timeZone property for location= with rel=3Dstart (section 4.2.4.).

Planned for the next version:

  • More examples! I plan to add a bunch of illustrative example= s for the major (and probably some obscure) use-cases.
<= br>
As always, Neil and I very much look forward to your feedback.

Cheers,
Robert
--_----------=_151575484125942661-- From nobody Fri Jan 19 02:38:42 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 56EA212D7E9 for ; Fri, 19 Jan 2018 02:38:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.619 X-Spam-Level: X-Spam-Status: No, score=-2.619 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ysP5r8HmY8Ld for ; Fri, 19 Jan 2018 02:38:38 -0800 (PST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85965127AD4 for ; Fri, 19 Jan 2018 02:38:38 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id BDBC620A9E for ; Fri, 19 Jan 2018 05:38:37 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute1.internal (MEProxy); Fri, 19 Jan 2018 05:38:37 -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=fm1; bh=D4W+rPkAp6k8HmCybHandKyT9Wo4Z FGNtMJdPtldxyQ=; b=VAdhr3h3rWlLGbeFG8GG3WRC2PGR+0NqE3uPWRpAMDimq VBc8K2lAm9xBtpQWz6vvMPLJExO99zqgoVbkDablyBHxwAoU5DVr0KSVBU1Xj/Qu Wrmr/qSyf2rygpIDZK1/ae/aZ7jN8WRR9/JoUJKOENebn/SwxjLa71ggNXZo43KF A8LJGDPEtewriKdA9w0TpfWAckBUe+k+k12AeQ0S6UU10IzMGPwc0l9jA4hK6BNH mqn1qHJSjtmIc3fGijdjKDHJ+/WEDyYQ9HAOTGCGThKwW/J9xjY9dYKpTV1V3veo FKZIGd1mnqW3wwZYpJCOLdGutNQDeCTxX0f0/my2A== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9AC9241A8; Fri, 19 Jan 2018 05:38:37 -0500 (EST) Message-Id: <1516358317.3418070.1240857000.2D8A2EC6@webmail.messagingengine.com> From: Robert Stepanek To: calsify@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_151635831734180701" X-Mailer: MessagingEngine.com Webmail Interface - ajax-75de3051 Date: Fri, 19 Jan 2018 11:38:37 +0100 Archived-At: Subject: [calsify] JSCalendar draft version 5 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, 19 Jan 2018 10:38:40 -0000 This is a multi-part message in MIME format. --_----------=_151635831734180701 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Hi all, I have just posted version 5[1] of the JSCalendar RFC draft. This version includes a few property additions and changes, and completely reworked examples. *This version is ready for last call.* Notable changes to the previous version: * *Location time-zone with rel=start*: version 4 forbid using a different time-zone for start locations than the enclosing JSCalendar object time-zone. This is allowed again (see section 4.2.4[2]). * *Alert attachments*: the EmailAction alert definition now includes an additional property for email attachments (see section 4.5.2[3]). * *Optional color*: the color property allows null as value (see section 4.2.9[4]). * *Fractional time for estimated all-day task duration*: the time fields of the estimatedDuration property value are allowed to be non- zero for all-day tasks (see section 5.2.4[5]). * *Examples*: the example section now illustrates main use-cases for JSCalendar objects. Please let me know if you miss anything (see section 7[6]). As I understand, Daniel Migault will soon start a working group call. Thanks, Daniel! Cheers, Robert Links: 1. https://tools.ietf.org/html/draft-jenkins-jscalendar-05 2. https://tools.ietf.org/html/draft-jenkins-jscalendar-05#section-4.2.4 3. https://tools.ietf.org/html/draft-jenkins-jscalendar-05#section-4.5.2 4. https://tools.ietf.org/html/draft-jenkins-jscalendar-05#section-4.2.9 5. https://tools.ietf.org/html/draft-jenkins-jscalendar-05#section-5.2.4 6. https://tools.ietf.org/html/draft-jenkins-jscalendar-05#section-7 --_----------=_151635831734180701 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Hi all,

I have just posted version 5 of the JSCalendar RFC draft. This version in= cludes a few property additions and changes, and  completely reworked = examples.

This version is ready for last call.

Notable changes to the previous version:

  • Location time-zone with rel=3Dstart: version 4 forbid using = a different time-zone for start locations than the enclosing JSCalendar obj= ect time-zone. This is allowed again (see section 4.2.4).
  • Alert attachments: the EmailAction alert definition now includ= es an additional property for email attachments (see section 4.5.2).
  • Optional color: the color property allows null as v= alue (see section 4.2.9).
  • Fractional time for est= imated all-day task duration: the time fields of the estimatedDuration = property value are allowed to be non-zero for all-day tasks (see sec= tion 5.2.4).
  • Examples: the example section now illus= trates main use-cases for JSCalendar objects. Please let me know if you mis= s anything (see section 7).

As I understand, Daniel Migault will soon start a working group call. = Thanks, Daniel!

Cheers,
Robert

--_----------=_151635831734180701-- From nobody Sun Jan 28 08:17:09 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 BEF9712F4CA; Sun, 28 Jan 2018 08:17:07 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: mglt.ietf@gmail.com, calsify@ietf.org, calext-chairs@ietf.org, aamelnikov@fastmail.fm X-Test-IDTracker: no X-IETF-IDTracker: 6.70.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151715622773.21812.13228562490898760686.idtracker@ietfa.amsl.com> Date: Sun, 28 Jan 2018 08:17:07 -0800 Archived-At: Subject: [calsify] calext - New Meeting Session Request 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: Sun, 28 Jan 2018 16:17:08 -0000 A new meeting session request has just been submitted by Daniel Migault, a Chair of the calext working group. --------------------------------------------------------- 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: nvo3 ipsecme teep saag sfc dinrg tls cdni suit cfrg i2nsf 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 Sun Jan 28 08:19:35 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 18E7D12F4D9; Sun, 28 Jan 2018 08:19:35 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 6.70.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151715637509.21839.3684291529972896675.idtracker@ietfa.amsl.com> Date: Sun, 28 Jan 2018 08:19:35 -0800 Archived-At: Subject: [calsify] The CALEXT WG has placed draft-jenkins-jscalendar in state "Adopted by a 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: Sun, 28 Jan 2018 16:19:35 -0000 The CALEXT WG has placed draft-jenkins-jscalendar in state Adopted by a WG (entered by Daniel Migault) The document is available at https://datatracker.ietf.org/doc/draft-jenkins-jscalendar/ From nobody Sun Jan 28 08:28:50 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 E8E4712F4BF for ; Sun, 28 Jan 2018 08:28:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.399 X-Spam-Level: X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=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 Eo584iXocR-f for ; Sun, 28 Jan 2018 08:28:46 -0800 (PST) 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 E622512F4B1 for ; Sun, 28 Jan 2018 08:28:45 -0800 (PST) Received: by mail-lf0-x232.google.com with SMTP id o89so6517184lfg.10 for ; Sun, 28 Jan 2018 08:28:45 -0800 (PST) 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=eBrBuQ9MLLYNEL1MKb/akLydjkL14TGO39Wr8MI+EBM=; b=rRUNc2RX8/4OQ8OoL7vlVqOT4TlydVw37a64YfbiUewZYSgXe/oWnIjXldRJfxeEYN AWoAeNx3TQgE1J6h4kaGLNh5teBZ+9aeQaj5BxfhKhqCg+9ZkYhYJLsAHjNOvrLCRY9R PgTQUJLCTksMMUUpc8S48T6qd4l1Pju/NtcfMnZ0QTm6QCMMPCyMakM3PmF42uV50rTJ DQnExv5AF4go3Wj0ualKziU+bUjuU9QoPQhzh1AcbgbMl4j5L/je1ndHvqILnUlPmtbH rlaeD//JSHP5Da1LlFcw4xzstcAwmg4jBtxrzs7v2+/bCiBU8ANVf2b0zJua6XwPsCxp vagQ== 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=eBrBuQ9MLLYNEL1MKb/akLydjkL14TGO39Wr8MI+EBM=; b=O3gctIC6vIGyjjd3xP1r6YH7wCH7mCVKgEDV0j/vWntQgEbmL4yZJ+qOa891yOi4Jx B29x27TsGSOEXwPvk4qA8G6wlADy/zBhzBmU9uiS1lRaKQZqeuULcK0J4z+8tTy8db35 tdwdwig03M2wIY33KSWbjKrfWbphlSD8QaV+/aZclf0u1xrhia6mxliMq4VyvfeDUk3x H4mNjppzR464bDV1CKnQX8iudUhJxgqiscom+evo2iW3tEEJhhjGg6ukOhG6BoHKO/Ps 5F9Az2XUO2VYJy/s4ySXn5FRtqq2y2lpxVzIuVgoeDAS9eP2IBNYEFCYGc2uawUh8FdQ 7fAw== X-Gm-Message-State: AKwxytfO/TH1vp4AtiEPcRJEcGqcpz383Rp0TSMcZA52L28rNcAKaqXo pGlvU1I/w8PFU8ZtHRc9bl0h5CV3GXRUVGReOTrKTA== X-Google-Smtp-Source: AH8x224lj8DFcr/bgVJFH+xcWljmUepYpmfh2iSGk92LijrlQYDnVsYwyyj9y0gqlWF04BjClysSNapXnPJed4GkMx8= X-Received: by 10.25.67.17 with SMTP id q17mr12219135lfa.114.1517156924228; Sun, 28 Jan 2018 08:28:44 -0800 (PST) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 10.46.32.132 with HTTP; Sun, 28 Jan 2018 08:28:43 -0800 (PST) In-Reply-To: <10A6FF6A-96B1-45EA-9D24-90483997B45E@apthorpia.com> References: <32CDF4A9-9F27-4061-BF9B-815E263CC14A@apthorpia.com> <1513068323.599100.1202156856.66190C40@webmail.messagingengine.com> <1513164195.2678425.1203569672.1CE1CC27@webmail.messagingengine.com> <10A6FF6A-96B1-45EA-9D24-90483997B45E@apthorpia.com> From: Daniel Migault Date: Sun, 28 Jan 2018 11:28:43 -0500 X-Google-Sender-Auth: _LkeI5OtUCHGBA4ut1PKxtMuAYo Message-ID: To: Adrian Apthorp Cc: Robert Stepanek , calsify@ietf.org Content-Type: multipart/alternative; boundary="f403045e975489889c0563d89f7a" Archived-At: Subject: Re: [calsify] Call for adoption for draft-jenkins-jscalendar 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, 28 Jan 2018 16:28:49 -0000 --f403045e975489889c0563d89f7a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, I have just realized that the tread has not been closed. draft-jenkins-jscalendar has been adopted. This mail closes this thread with draft-jenkins-jscalenda= r being adopted by the calext wg. The new status has been updated in the datatracker as well. Next update should be renamed as draft-ietf-calext-jscalendar-00 and replace the current draft. Yours, Philipp, Donald and Daniel On Fri, Dec 15, 2017 at 7:53 AM, Adrian Apthorp wrote: > Adoption supported > > > > On 13 Dec 2017, at 7:23 PM, Robert Stepanek wrote= : > > I've just uploaded draft version 03 [1], which fixes typos and rephrases > descriptions. It does not introduce new or alter existing property > semantics. > > The complete list of changes is available on Github [2] > > Cheers, > Robert > > [1] https://tools.ietf.org/html/draft-jenkins-jscalendar-03 > [2] https://github.com/CalConnect/PUBLIC_DRAFTS/commits/master/jscalendar > > > On Tue, Dec 12, 2017, at 09:45, Robert Stepanek wrote: > > Hi Adrian, > > On Tue, Dec 12, 2017, at 08:00, Adrian Apthorp wrote: > > I=E2=80=99ve just been through the draft and see a few things which I bel= ieve need > correcting before adoption. Also, there are some obvious all be it minor > errors which should be corrected at the same time. > > > Thanks for the review feedback. Expect an updated draft by tomorrow. > > Also, I still notice a bias towards events, even though the draft > discusses both task and event objects: > [...] > Presumably 3.5.1 useDefaultAlerts (plus a few others) apply to tasks as > well as events. > > > Just to be clear: Any properties listed in section 3 (JSCalendar > properties) apply to both tasks and events. Any object-type specific > properties are described in section 4. Looking at your feedback I realize > we still haven't got rid of the event-bias in all descriptions in section= 3 > and I will revisit the section to change that. > > Cheers, > Robert > *_______________________________________________* > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify > > --f403045e975489889c0563d89f7a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I have just realized that= the tread has not been closed. draft-jenkins-jsca= lendar has been adopted. This mail closes this thread with draft-jenkins-jscalendar being ado= pted by the calext wg. The new status has been updated in the datatr= acker as well. Next update should be renamed as draft-ietf-calext-jscalenda= r-00 and replace the current draft.

Yours,

Philipp, Donald = and Daniel
=C2=A0=C2=A0

On Fri, D= ec 15, 2017 at 7:53 AM, Adrian Apthorp <adrian@apthorpia.com> wrote:
Adoption su= pported



On 13 Dec 2017, at 7:23 PM, = Robert Stepanek <rsto@fastmailteam.com> wrote:

I've just uploaded draft version 03 [1], which fixes typos and rep= hrases descriptions. It does not introduce new or alter existing property s= emantics.

The complete list of changes is available on Github [2]

Cheers,
Robert



On Tue, Dec 12, 2017, at 09:45, Robert Stepanek wrote:
Hi Adrian,

On Tue, Dec 12, 2017, at 08:00, Adrian Apthorp wrote:
=
I=E2=80=99ve just been through the= draft and see a few things which I believe need correcting before adoption= . Also, there are some obvious all be it minor errors which should be corre= cted at the same time.

Thanks for the review feedback. Expect an updated draft by tomorrow.

Also, I still notice a bias t= owards events, even though the draft discusses both task and event objects:=
[...]
Presumably 3.5.1 useDefaultAlerts (plus a few others) apply to tasks a= s well as events.

Just to be clear: Any properties listed in section 3 (JSCalendar prope= rties) apply to both tasks and events. Any object-type specific properties = are described in section 4. Looking at your feedback I realize we still hav= en't got rid of the event-bias in all descriptions in section 3 and I w= ill revisit the section to change that.

Cheers,
Robert
_______________________________________________
calsify mailing list

___________________= ____________________________
calsify mailing list
calsify@i= etf.org
https://www.ietf.org/mailman/listinfo/cal= sify

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

--f403045e975489889c0563d89f7a-- From nobody Sun Jan 28 08:37:03 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 37B2712F4E5 for ; Sun, 28 Jan 2018 08:37:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.399 X-Spam-Level: X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=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 gGmb5bcE8BIb for ; Sun, 28 Jan 2018 08:37:00 -0800 (PST) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C376312F4D9 for ; Sun, 28 Jan 2018 08:36:59 -0800 (PST) Received: by mail-lf0-x22c.google.com with SMTP id w27so6557772lfd.6 for ; Sun, 28 Jan 2018 08:36:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=TicP1/jpIY60RsILl9w8K0QekccHfFQnR6Ama8rtcuI=; b=Hd4kswhyIE9gvVmVoUPNglEKQLSFTUwBL6BGrDk+ulhxyevrvMCMK86jBndJVz0FFn YTMGM7xRIGsmrF7N8yr7q29MPF0Jj3N3SMgoF7mjtZmIb04vsODGIAjwND6Q3pABef9X +vS1fqQy6XWbYXIgQaMDn1CpJI3XNZbEAQ/GSWrHcF1LShzVX3MNY/KHeoKidDE2ZuGu w3rAXqH0RGScWmhWNGvn1e76NBRuZk6On2HHKcNpEfgD6fwpAL6FUlRPE7L2QsDvvyzS QWC30UQUIoPwjNQjC+IzjEbtPZ0ikLX/fKVdIXIuGIcmihMG5cpex0uk8j22x7A8yo8A kvNg== 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:from:date:message-id:subject :to; bh=TicP1/jpIY60RsILl9w8K0QekccHfFQnR6Ama8rtcuI=; b=SSBchCkZ3/hP2JNNuO0J52cpITVzJoq0+rQEd76+8kQIesHrx/h2i6ZArtFdq6NzZn becPTr8bbixOlsnGoAwnLsIpTZ93NR8vcP0MNcKBnxm+2X9BlgKn8fALoqq/Np8lAK8K SsDTzXNaS2pPJZQboYcsEjXBtoVldN51IcrCsgT3EyWGNc1fbdBIHUMiTXVUFCc/Zjyd rrHsWUCgq6h/kB7MDyk6MNN15m2mnoKdZXP2zVhxnkkKfViT+LfqtTZtgVkmOJmpmGky rZJd2Y1p0ZcY0tslj03rUmWMTbuDEzUP5AgQPnaQfssX1evQ+63UqdlG+bCN3DNZ9rgh R2uw== X-Gm-Message-State: AKwxyte9fhyMevMOvAJiGJyYAF4zQGRG3qHfNsFMEmMfZIfP/zUpabyy 041ai4Vabfi6u/gcMhX/2CBn9i/EtZMBK8CLsQ4vRQ== X-Google-Smtp-Source: AH8x227MZ+B2RHAjPXW1x+dXRscW5tSMZdQSz+QkvmH5qULDxBwJq3xp8QR07mtNfzxMkqDNHBVnp1Fon7TrBxGs/G8= X-Received: by 10.25.213.19 with SMTP id m19mr11353261lfg.4.1517157417890; Sun, 28 Jan 2018 08:36:57 -0800 (PST) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 10.46.32.132 with HTTP; Sun, 28 Jan 2018 08:36:57 -0800 (PST) From: Daniel Migault Date: Sun, 28 Jan 2018 11:36:57 -0500 X-Google-Sender-Auth: X766kGBypkKl-JIV33Itzi7e_-s Message-ID: To: calsify@ietf.org Content-Type: multipart/alternative; boundary="001a11412bdcf63bb80563d8bc34" Archived-At: Subject: [calsify] Working Group Last Call for draft-jenkins-jscalendar 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, 28 Jan 2018 16:37:02 -0000 --001a11412bdcf63bb80563d8bc34 Content-Type: text/plain; charset="UTF-8" Hi, In order to sync the WG with Calconnect we are starting a WGLC for draft-jenkins-jscalendar. The WGLC period will be a bit extended and please provide your feed backs by February 15. The earlier the better. There is no need to wait the end of the WGLC period to update the draft. If you have or are aware of implementations, please also provide this information on the mailing list. Report of interoperability tests are also much appreciated. We are targeting sending the draft to the IESG before the next IETF in London. Yours, Philipp, Donald and Daniel [1] https://datatracker.ietf.org/doc/draft-jenkins-jscalendar/ --001a11412bdcf63bb80563d8bc34 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

In order to sync the WG with Calconn= ect we are starting a WGLC for draft-jenkins-jscalendar. The WGLC period wi= ll be a bit extended and please provide your feed backs by February 15. The= earlier the better. There is no need to wait the end of the WGLC period to= update the draft.

If you have or are aware of implementation= s, please also provide this information on the mailing list. Report of inte= roperability tests are also much appreciated.

We are targetin= g sending the draft to the IESG before the next IETF in London.
--001a11412bdcf63bb80563d8bc34-- From nobody Mon Jan 29 06:53:50 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 D36DD12EBCA; Mon, 29 Jan 2018 06:53:47 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: mglt.ietf@gmail.com, calsify@ietf.org, calext-chairs@ietf.org, aamelnikov@fastmail.fm X-Test-IDTracker: no X-IETF-IDTracker: 6.70.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151723762781.3048.17895219642061448701.idtracker@ietfa.amsl.com> Date: Mon, 29 Jan 2018 06:53:47 -0800 Archived-At: Subject: [calsify] calext - Update to a Meeting Session Request 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: Mon, 29 Jan 2018 14:53:48 -0000 An update to a meeting session request has just been submitted by Daniel Migault, a Chair of the calext working group. --------------------------------------------------------- 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: nvo3 ipsecme teep saag sfc dinrg tls cdni suit cfrg i2nsf jmap extra 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 Mon Jan 29 06:58:10 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 814C012EBFC; Mon, 29 Jan 2018 06:58:07 -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.70.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151723788747.2990.8797560696092961646@ietfa.amsl.com> Date: Mon, 29 Jan 2018 06:58:07 -0800 Archived-At: Subject: [calsify] I-D Action: draft-ietf-calext-jscalendar-00.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, 29 Jan 2018 14:58:07 -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-00.txt Pages : 51 Date : 2018-01-29 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-00 https://datatracker.ietf.org/doc/html/draft-ietf-calext-jscalendar-00 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 Jan 29 16:08: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 E6B31131473; Mon, 29 Jan 2018 16:08:03 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: mglt.ietf@gmail.com, calsify@ietf.org, calext-chairs@ietf.org, aamelnikov@fastmail.fm X-Test-IDTracker: no X-IETF-IDTracker: 6.70.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151727088388.27524.4976186065633962664.idtracker@ietfa.amsl.com> Date: Mon, 29 Jan 2018 16:08:03 -0800 Archived-At: Subject: [calsify] calext - Update to a Meeting Session Request 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, 30 Jan 2018 00:08:04 -0000 An update to a meeting session request has just been submitted by Daniel Migault, a Chair of the calext working group. --------------------------------------------------------- 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: i2nsf cfrg suit cdni tls dinrg sfc saag teep ipsecme nvo3 jmap extra 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. ---------------------------------------------------------