Minutes IETF125: jmap: Tue 01:00
minutes-125-jmap-202603170100-00
| Meeting Minutes | JSON Mail Access Protocol (jmap) WG | |
|---|---|---|
| Date and time | 2026-03-17 01:00 | |
| Title | Minutes IETF125: jmap: Tue 01:00 | |
| State | Active | |
| Other versions | markdown | |
| Last updated | 2026-04-10 |
JMAP/CALEXT joint session IETF125 Shenzhen
Date: 2026-03-17 09:00-11:00+0800 (China time)
Notewell and Agenda bashing (5 min)
CALEXT
Existing Documents
(Robert Stepanek)
- jscalendar-icalendar: 10 min
- jscalendar-bis
- jscontact-profiles: 5 min
- jscontact-uid: 10 min
- jscontent-cryptographic-key 15 min
- rfc9555-bis
Awaiting adoption, probably ready now
Status report, no controversy
Proposed Work
- vcard4-bis (Ricardo Signes)
RFC 6350 for vcard 4.0 is old, many (33) errata
Role of commas and semicolons, escaping, contexts often at issue
UIDs were a text type in v3, now a URI type in v4. Complicates
migration.
JSContact defined for 4.0, but Google and Apple use 3.0
Minimal restatement of terms clarifiation.
Next step: create a draft and adopt it quickly. Strong support for this
work.
ACTION: Rik to create a vcard4-bis document
Other Discussion Points
- Canonical VCard Location (see email to list recently)
URL to go to in order to "get the latest version of this card"
Next step: remains in ideas too, didn't attrct much interest
JMAP
Existing Documents
-
jmap-calendars: 5 min
-
metadata: 10 min
- refplus: 5 min
- mail-sharing: 5 min
Mauro presenting on above 3 topics, no slides but waiting for feedback
on next steps.
Neil: Will reread latest versions, want to have an implementation or
two. Metadata is the "weirdest" one in terms of many ways to do it.
Bron: Interested in interaction between metadata and filenode.
Mauro will do more implementation if these seem fairly stable.
ACTION: Neil to read and review current metadata/refplus/mail-sharing
documents.
- email-push: 5 min
Neil: Spec is complete, awaiting more implementions.
Mauro: Stalwart has mostly implemented it.
- filenode: 10 min
(Bron): Has started implementing, which is motivation for blobext.
Currently immutable BlobID etc.
Ben: suggests new role for pictures
Immutability: Email typically is immutable, not so much for calendar and
contacts. Relax the restriction?
Micke Nordin: Wonders why immutable. Docs typically evolve over time.
Type might not need to change.
Neil Jenkins: Prefers the Posix model.
Ben Bucksch: Files should be writeable. Uploading large files to change
a node is a burden.
ACTION: Bron to update filenode document based on feedback
Proposed Documents
- blobext: 10 min
(Bron) extension to blob extension. Allows joining blob pieces (range of
bytes), allows write to a small part of a file. Various other goodies.
New draft just uploaded following blackout period
Considering resumable upload feature
Are quotas needed?
Next step: Bron will call for adoption. Would like more implementations.
Ken Murchison: This seems useful. imap convert wasn't much used; is it
needed here?
Ben: Very much like the thumbnail feature as client. For resumable
uploads, use more http semantics?
Ken: working with http working group.
Ken: What will CBOR get us compared with compressed JSON?
Ben: Those are competing ideas, need to benchmark. There are different
CBOR options as well. Guesses that CBOR will end up being faster.
Neil: Tried using CBOR years ago, lack of CBOR support in browser also a
factor. Is the dictionary for a specific compression algorithm?
Ben: It is an algorithm that allows a preshared dictionary (RFC 9842,
compression dictionary transport
)
ACTION: Jim will make a call for adoption for
draft-gondwana-jmap-blobext
Expired Documents: 5 min total
- jmap-tasks
Hans-Joerg is working on it, but hasn't had time since last meeting.
Hopes to get something done for Vienna. Will upload new version to solve
expiration.
Neil: Should put anything needed for jmap-calendar in that draft to
avoid dependency on jmap-tasks.
ACTION: Hans-Joer will upload new jmap-tasks draft
- rest/portability/essential
- smime-sender-extensions
Alexey working on it, has been delayed.
Other Discussion points
- JMAP with CBOR
see above
JMAP Protocol Badge
- coming soon