Re: [Jmap] [JMAP] CalendarEvent/parse proposition for the JMAP Calendar draft

René CORDIER <rcordier@linagora.com> Fri, 26 May 2023 03:03 UTC

Return-Path: <rcordier@linagora.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D11F4C151B16 for <jmap@ietfa.amsl.com>; Thu, 25 May 2023 20:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.693
X-Spam-Level:
X-Spam-Status: No, score=-1.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=linagora.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17QPab78WyPo for <jmap@ietfa.amsl.com>; Thu, 25 May 2023 20:03:26 -0700 (PDT)
Received: from smtp.linagora.com (smtp.linagora.com [54.36.8.78]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD4D8C151B06 for <jmap@ietf.org>; Thu, 25 May 2023 20:03:25 -0700 (PDT)
Received: from ?Open?PaaS?SMTP?server?for?Linagora? (unknown [51.83.109.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.linagora.com (Postfix) with ESMTPSA id 4707B3EE62 for <jmap@ietf.org>; Fri, 26 May 2023 05:03:24 +0200 (CEST)
DKIM-Signature: a=rsa-sha256; b=WBrxmuWtNC5V8HQfljKlxwydUfFPGHDv4STddLJdT/AV9cuzT+OJdgQeqnUtTaP/dP9mtT4wK5kHsDrkZGqgjm9ciFPgng5Bl9qMWWamSg4flcn+Gr2hRPa4I4DTXcpKn/1yTr9DxaeFOU6G5vqQfe+VKirQErV7yG4gWXTb/EfMzKh0wNqBmoChA51Go7cNJIaXWatLBJz3XcNBoUNOjAy3fQo2CcpJ4+VdluMYsUsaIXQ1On5CisixRbhLaUKIn6HAvIU6/2fNrjLX2dA+Gh2x/FDaXDVwuzvwIEC7qV+2SwHEPgGONI6QBWUb0b13fx2OLWGx9Bd7uH0lDqHjtQ==; s=smtpoutjames; d=linagora.com; v=1; bh=lvMqUQyhb6sKYkAar8eM4kDScmFd0v+sw08Lb3iuZh8=; h=from : reply-to : subject : date : to : cc : resent-date : resent-from : resent-sender : resent-to : resent-cc : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive;
MIME-Version: 1.0
X-LINAGORA-Copy-Delivery-Done: 1
From: René CORDIER <rcordier@linagora.com>
To: jmap@ietf.org
Reply-To: rcordier@linagora.com
Date: Fri, 26 May 2023 03:03:22 +0000
Message-ID: <Mime4j.780.beff1a6f3bb790c6.1885602c60b@linagora.com>
User-Agent: Team-Mail/0.7.9 Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
Content-Type: multipart/alternative; boundary="-=Part.781.891a320f485034b3.1885602c60c.83449ba7e90f9e22=-"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/UNd-wSMX22hTQvti09Rh8daj66w>
Subject: Re: [Jmap] [JMAP] CalendarEvent/parse proposition for the JMAP Calendar draft
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2023 03:03:31 -0000

Hi Neil,

Thanks for the positive feedback! I agree with the additional capability. What should we name it though?

- urn:ietf:params:jmap:icalendars ?

- urn:ietf:params:jmap:calendars:events ?

- urn:ietf:params:jmap:calendars:events:parse ?

- better ideas?

Cheers,

Rene.

On May 25, 2023 1:01 PM, from Neil Jenkins This looks great to me. If we're putting this in the main JMAP Calendars spec, I think it needs its own capability string. Unlike with JMAP Mail (parsing RFC5322 messages), there's no guarantee that the server uses iCalendar underneath (or indeed at all), and a server without this would still be a perfectly capable calendar server.

Cheers,
Neil.

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