Return-Path: X-Original-To: mailmaint@mail2.ietf.org Delivered-To: mailmaint@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 30A3B81D5958 for ; Mon, 3 Nov 2025 12:05:00 -0800 (PST) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.797 X-Spam-Level: X-Spam-Status: No, score=-2.797 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b="PPzbJ3le"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="YmpHhFh3" Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFMVvDNhK1k8 for ; Mon, 3 Nov 2025 12:04:59 -0800 (PST) Received: from flow-b4-smtp.messagingengine.com (flow-b4-smtp.messagingengine.com [202.12.124.139]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7554D81D593A for ; Mon, 3 Nov 2025 12:04:59 -0800 (PST) Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailflow.stl.internal (Postfix) with ESMTP id 9380713003AD; Mon, 3 Nov 2025 15:04:53 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Mon, 03 Nov 2025 15:04:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1762200293; x=1762207493; bh=O8uxZpSsMf pzswXLABXgqUf7jHnDbloNFxa8f/8g7Yg=; b=PPzbJ3lexXViY4oTWYe6BwSsML keQLm5u1uObLXH/n85bcAmdkEKj+ox2X9BMR+TTdRRSd6ssyVobGZ2iW2c1Y7ccp zX4txAcFE1EI1zIxNDv82VT3a/y4jxTcvkePGXFs0gD9Bp2LIuz+GPNrROzq8EJy qf+MYQetBRJ7d6cHAEFG2npnsiN47vsIP5aEqLFYf1fG1e0t/XQY+0JCMVmddp7r ZI62wcHNGE4YLGr5gtQ3nGuEG0HjRiIi2vpoRdZHHeqaiQ0q5Sgbu8ohaaywQeuk KJkBdg+MFL+wOWriVub3YTZ8S/exdrpvL66uDaCVFnQ1Vynk5Tbbw3eHTH4g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1762200293; x=1762207493; bh=O8uxZpSsMfpzswXLABXgqUf7jHnDbloNFxa 8f/8g7Yg=; b=YmpHhFh3ndMgiWemuPuRuWcghGhi1+6F36gZDCV0wQ8lEQ3QsBC z/qRiykonZERMTXkmmazRM9lkXb+5ru+2C22AIqIKWHWyGXT1c3Uxb6KnbQZ3WgC NNFcBPSlUkPxsuxn9ey9XbuGEPUJAY9lvJfkgdqud20yjarRCKWtxWYNiML5RRc6 grflF8N/nqKW0jouCHqc0Jd2eXwNfgfss+kLGNf09naTm+juNIcJ7BHY/jv1ggAq 91xaFVsfSO/rhwNCd92RnsiueovbELgXAMoS0e42V52fj8BXcnfeuC04S2FfF2Qp 0j9LFvKWgZoxK1vvEeY7VvqB1NwBy/pMFkg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddujeeltdegucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurheptgfkffggfgfuvfhfhfhojgesrgdtreertddvjeenucfhrhhomhepmfgvnhcuofhu rhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrfgrth htvghrnhepudelgfeluddvieevgfefueehleekkeejveegleevffeguedttedthfdufeel ffevnecuffhomhgrihhnpehivghtfhdrohhrghdpshhtrghlfidrrghrthenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmuhhrtghhsehfrghs thhmrghilhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpd hrtghpthhtohepmhgruhhrohepgedtshhtrghlfidrrghrthesughmrghrtgdrihgvthhf rdhorhhgpdhrtghpthhtohepmhgrihhlmhgrihhnthesihgvthhfrdhorhhg X-ME-Proxy: Feedback-ID: ibf914243:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 3 Nov 2025 15:04:51 -0500 (EST) Content-Type: multipart/alternative; boundary="------------0qfx33cpy0r00s6QLxYCsLdd" Message-ID: <890ca353-ee04-46b8-82c0-1f525f67ed83@fastmail.com> Date: Mon, 3 Nov 2025 15:04:51 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Mauro De Gennaro , Mail Maintenance WG References: <36eed3e2-4c42-423a-9070-62f56fa22ee8@fastmail.com> <0E90BDBF-B9C8-42AB-8922-18D1B814F55E@stalw.art> From: Ken Murchison Content-Language: en-US Organization: FastMail US LLC In-Reply-To: <0E90BDBF-B9C8-42AB-8922-18D1B814F55E@stalw.art> Message-ID-Hash: X22BWGSI2P5ISGZPJNDKA5JJVURB5Y6H X-Message-ID-Hash: X22BWGSI2P5ISGZPJNDKA5JJVURB5Y6H X-MailFrom: murch@fastmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Bmailmaint=5D_Re=3A_IMAP_OBJECTID_Account_Identifier_Extension?= List-Id: Mail Maintenance Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This is a multi-part message in MIME format. --------------0qfx33cpy0r00s6QLxYCsLdd Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Already added 10m to the agenda. On 11/3/25 3:03 PM, Mauro De Gennaro wrote: > Hi Ken, > > That would be nice, thanks. I think 5 minutes to present the draft and > 5 minutes to discuss should be enough? > > > Best, > Mauro > >> On 3 Nov 2025, at 8:18 pm, Ken Murchison wrote: >> >>  >> >> Hi Mauro, >> >> Would you like some time during MAILMAINT to introduce this draft as >> a possible work item? >> >> >> On 11/2/25 3:24 AM, Mauro De Gennaro wrote: >>> >>> I’ve just submitted the OBJECTID Account Identifier Internet Draft >>> to Datatracker, which proposes extending the IMAP OBJECTID extension >>> to support account identifiers. >>> >>> As this is my first time submitting an I-D, I’m not entirely sure >>> what the next steps are beyond sharing here for discussion in the >>> WG. I would appreciate any guidance and, of course, any feedback on >>> the draft itself is very welcome. >>> >>> Below are the details: >>> >>> Name:     draft-degennaro-imap-objectid-accountid >>> Revision: 00 >>> Title:    IMAP OBJECTID Account Identifier extension >>> Date:     2025-11-02 >>> URL: >>> https://www.ietf.org/archive/id/draft-degennaro-imap-objectid-accountid-00.txt >>> Status: >>> https://datatracker.ietf.org/doc/draft-degennaro-imap-objectid-accountid/ >>> HTMLized: >>> https://datatracker.ietf.org/doc/html/draft-degennaro-imap-objectid-accountid >>> >>> >>> Abstract: >>> >>>   This document extends the IMAP OBJECTID extension (RFC 8474) to >>>   support account identifiers, enabling IMAP servers to provide >>>   account-level context for mailboxes when multiple accounts are >>>   accessible through a single IMAP connection.  This extension is >>>   particularly relevant for environments where IMAP mailboxes include >>>   shared mailboxes from multiple JMAP accounts, as defined in the JSON >>>   Meta Application Protocol (JMAP).  By introducing the ACCOUNTID >>>   object identifier, this specification ensures that mailboxes can be >>>   uniquely identified across different accounts in both IMAP and JMAP >>>   contexts, thereby facilitating seamless interoperability between the >>>   two protocols in multi-account scenarios. >>> >>> >>> >>> Thanks, >>> Mauro >>> >>> >>>> On 26 Oct 2025, at 11:37, Mauro De Gennaro >>>> wrote: >>>> >>>> Hi all, >>>> >>>> I unfortunately missed the submission deadline for a new draft I’ve >>>> been working on, which defines an extension to IMAP adding >>>> account-level object identifiers to complement the existing >>>> OBJECTID framework. >>>> >>>> I’ll upload the draft as soon as submissions reopen on November >>>> 1st, but in the meantime it’s available online at >>>> https://rfc.stalw.art/imap-objectid-accountid/ >>>> >>>> If there’s time on the Montreal agenda, it would be great to give >>>> it a quick look; otherwise, we can continue the discussion here on >>>> the list. >>>> >>>> >>>> Best, >>>> Mauro >>>> >>>> -- >>>> mailmaint mailing list -- mailmaint@ietf.org >>>> To unsubscribe send an email to mailmaint-leave@ietf.org >>> >>> >> -- >> Kenneth Murchison >> Senior Software Developer >> Fastmail US LLC >> -- >> mailmaint mailing list -- mailmaint@ietf.org >> To unsubscribe send an email to mailmaint-leave@ietf.org > -- Kenneth Murchison Senior Software Developer Fastmail US LLC --------------0qfx33cpy0r00s6QLxYCsLdd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Already added 10m to the agenda.


On 11/3/25 3:03 PM, Mauro De Gennaro wrote:
Hi Ken,

That would be nice, thanks. I think 5 minutes to present the draft and 5 minutes to discuss should be enough?


Best,
Mauro

On 3 Nov 2025, at 8:18 pm, Ken Murchison <murch@fastmail.com> wrote:



Hi Mauro,

Would you like some time during MAILMAINT to introduce this draft as a possible work item?


On 11/2/25 3:24 AM, Mauro De Gennaro wrote:

I’ve just submitted the OBJECTID Account Identifier Internet Draft to Datatracker, which proposes extending the IMAP OBJECTID extension to support account identifiers.

As this is my first time submitting an I-D, I’m not entirely sure what the next steps are beyond sharing here for discussion in the WG. I would appreciate any guidance and, of course, any feedback on the draft itself is very welcome.

Below are the details:

Name:     draft-degennaro-imap-objectid-accountid
Revision: 00
Title:    IMAP OBJECTID Account Identifier extension
Date:     2025-11-02


Abstract:

  This document extends the IMAP OBJECTID extension (RFC 8474) to
  support account identifiers, enabling IMAP servers to provide
  account-level context for mailboxes when multiple accounts are
  accessible through a single IMAP connection.  This extension is
  particularly relevant for environments where IMAP mailboxes include
  shared mailboxes from multiple JMAP accounts, as defined in the JSON
  Meta Application Protocol (JMAP).  By introducing the ACCOUNTID
  object identifier, this specification ensures that mailboxes can be
  uniquely identified across different accounts in both IMAP and JMAP
  contexts, thereby facilitating seamless interoperability between the
  two protocols in multi-account scenarios.



Thanks,
Mauro


On 26 Oct 2025, at 11:37, Mauro De Gennaro <mauro=40stalw.art@dmarc.ietf.org> wrote:

Hi all,

I unfortunately missed the submission deadline for a new draft I’ve been working on, which defines an extension to IMAP adding account-level object identifiers to complement the existing OBJECTID framework.

I’ll upload the draft as soon as submissions reopen on November 1st, but in the meantime it’s available online at https://rfc.stalw.art/imap-objectid-accountid/

If there’s time on the Montreal agenda, it would be great to give it a quick look; otherwise, we can continue the discussion here on the list.


Best,
Mauro

--
mailmaint mailing list -- mailmaint@ietf.org
To unsubscribe send an email to mailmaint-leave@ietf.org


-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC
--
mailmaint mailing list -- mailmaint@ietf.org
To unsubscribe send an email to mailmaint-leave@ietf.org

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC
--------------0qfx33cpy0r00s6QLxYCsLdd--