IETF Logo Mail Archive

Re: [Jmap] Session at IETF116

Jim Fenton <fenton@bluepopcorn.net> Wed, 22 March 2023 23:58 UTC

Return-Path: <fenton@bluepopcorn.net>
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 77AEEC14CE47 for <jmap@ietfa.amsl.com>; Wed, 22 Mar 2023 16:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBtD2rMHsjH0 for <jmap@ietfa.amsl.com>; Wed, 22 Mar 2023 16:58:47 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD72DC14CF1B for <jmap@ietf.org>; Wed, 22 Mar 2023 16:58:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:To:From:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=D5SQRwv14jMiJolLNWE85BYT5C0sH6OP0Eq0RnKY57E=; b=kdcVueEbcyYiWNGtkfht+dKL+3 fs7E+CjIWrk243DF7bY2XxR4PHerT5zxx/jZNyDbnVUGr1UsUX0clpbhK5GdVsNwWenSCjc9hoaRD /OZpNStlhzb76vI/KbV4MR4IrxW2U+aCP+dSSELhXfRTW74hGrs1KjPeLUz4v/BKrAYc=;
Received: from [182.171.77.115] (helo=[10.71.12.50]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <fenton@bluepopcorn.net>) id 1pf8Lv-0005WW-El for jmap@ietf.org; Wed, 22 Mar 2023 16:58:46 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: jmap@ietf.org
Date: Thu, 23 Mar 2023 08:58:43 +0900
X-Mailer: MailMate (1.14r5852)
Message-ID: <C98AB319-AB23-4D96-9266-478C242DA5A7@bluepopcorn.net>
In-Reply-To: <9c8c246d-173c-4862-98dd-f0f3b6309c50@betaapp.fastmail.com>
References: <9c8c246d-173c-4862-98dd-f0f3b6309c50@betaapp.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_25DE6CED-AA83-4CD6-9E77-0EF7833C9D40_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"plain":[834, 1271], "uuid":"3047DC2C-4588-4B1E-B463-681ED1522E2C"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/jh0OvNQPvmeFexNhFS86jaOWuAQ>
Subject: Re: [Jmap] Session at IETF116
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: Wed, 22 Mar 2023 23:58:51 -0000

Greetings from Yokohama (I’m here a little early)!

Following up on Bron’s message here. We still haven’t published an 
agenda for the jmap session at IETF116, and need to do that. I haven’t 
heard any particular requests for session time, so we can publish the 
usual default schedule, which allocates some time for each of our active 
drafts and some time at the end to adjust WG milestones.

So that includes the items below plus perhaps contacts, sieve, and SMIME 
sender extensions.

We also want to allocate time for any future JMAP work anyone has in 
mind. If you have something in mind, please let us know.

We have a 2 hour session planned, and *think* that it’s joint with 
EXTRA but that doesn’t show up on the meeting agenda anywhere. Does 
anyone know for sure?

-Jim

On 24 Jan 2023, at 8:50, Bron Gondwana wrote:

> Hi Meta JSON Enthusiasts,
>
> It's getting on time to plan for Japan!
>
> We have a few things in flight at the moment:
>  * jmap sharing
>  * jmap for tasks
>  * jmap for calendars
>  * jmap for contacts (estimated to be next meeting)
>
> as well as jmap-sieve which is just awaiting one more document 
> revision before submitting to IESG.
>
> and as well as smime-sender-extensions, which is expired but still 
> work that I believe we should do!
>
> Mostly we decided at the last IETF to set milestones of July (in time 
> for San Francisco) - but is there any new work people want to bring, 
> or updates on these documents?
>
> I'm considering either doing a 1h session, or doing 2h combine with 
> EXTRA like we did at last IETF.  There's a bunch of work happening 
> over there.   I'm aware that it may be a bit selfish to combine them 
> for my convenience though, so let me know if you'd rather separate 
> sessions (or if you like it combined too - I enjoy both types of 
> feedback).  Let me (I should say us - hi Jim) know if you have 
> anything you'd like time for on the agenda.
>
> I'll be submitting agenda requests at the end of this week, so don't 
> sit on your responses too long :)
>
> Thanks,
>
> Bron.
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com

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

v2.23.0 | Report a Bug | By Email