Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B9F129AB8 for ; Thu, 8 Nov 2018 03:48:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.982 X-Spam-Level: X-Spam-Status: No, score=-1.982 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=P/us1Zv9; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZTn0rrCq 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 pOjazwJw2suU for ; Thu, 8 Nov 2018 03:48:31 -0800 (PST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8461A123FFD for ; Thu, 8 Nov 2018 03:48:31 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 91E7E21FAD for ; Thu, 8 Nov 2018 06:48:30 -0500 (EST) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Thu, 08 Nov 2018 06:48:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=message-id:date:from:to:subject :content-type; s=fm1; bh=wOdgUJYwr1/uVI3Sx6fnHUAc6B7wtT05Si7QCmk lVwg=; b=P/us1Zv98x+pLtvaPcPeCFrKgpHbuFRS+y8t4CpYebvGnjqhFmhgK8p 3q4OSUSOTHncIcqtcJ7gFFEfkykoFULHhA9I2Gr8YQrbkun92A0M556UFs3Z92T+ Q1p1Ij4cqCMi+bwoA2Hx+Yo1Cvb5j6aEkaaH6UOyD4Ecan+L20pM9m8dpJMOZN6W lkA2dGyZOQ6G4lNKRoISQ3WUJyzp4q3BgoiH4fO6feWJmeX9QxIg32XWECAWGnAw I1g5Ni5beiQ9cW8sJfAfW7BnCmlg6Lm40iUqOE5gM8ewluWzRyLsjRAUw12nHQob 6fu3yh8zP8qNe/ll6iwVVjk58CnKTXA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id:subject :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=wOdgUJYwr1/uVI3Sx6fnHUAc6B7wtT05Si7QCmklVwg=; b=ZTn0rrCq vSqw7Qc83IS3cmAOFOJydx3uf72CmdEtVyTddjgaNT+RqnXbqJoAGvLegncVMzz3 kWUef87go3bmzLowFm4wI6Xt9BdKs09X9WRTe1J8Fc5H1omj4DkL5XTVbDGE2VlI x87kAn3JVdifCVBTC4od8HLTbaFoxCwcvvvTI8rXVMQM5VPtyROyYR7lN1Y4iJKF NqsUOWjpXfRLrHlzWgOW16Ps29nv+Gr6n5kJf12srSFi07K0oAWJITuvw5j03I4f VlJHG/u9eKDqLUGlgur83pcn+qv0E95onOa+OedVAX08k4OBks/uo9pD67wEQpq6 TxZDLO2MFWFB/g== X-ME-Sender: X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 495B22030B; Thu, 8 Nov 2018 06:48:30 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface Message-Id: User-Agent: Cyrus-JMAP/3.1.5-610-gd7ceb27-fmstable-20181026v1 X-Me-Personality: 56629417 Date: Thu, 08 Nov 2018 06:48:29 -0500 From: "Bron Gondwana" To: imapext@ietf.org Content-Type: multipart/alternative; boundary=5700c796e0cc4161bd25c77fe738286f Archived-At: Subject: [imapext] =?utf-8?q?IMAP4rev2_questions_and_final_editing_round_?= =?utf-8?q?happening_over_in_EXTRA_working_group?= X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2018 11:48:33 -0000 --5700c796e0cc4161bd25c77fe738286f Content-Type: text/plain Hi IMAPEXT lurkers. If you're not already in the EXTRA working group, there's discussion about the spec: https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/ over on our list: https://mailarchive.ietf.org/arch/browse/extra/ We're interested in feedback on a few topics, and whether or not to include particular standards in our baseline. * RFC6851 MOVE * RFC5182 SEARCHRES * STATUS DELETED * RFC8474 OBJECTID * RFC3516 BINARY * disallow "RENAME INBOX" * draft-ietf-extra-imap-replace We're particularly interested in any feedback from people who will either find it hard to implement one of these in their server, or in the case of removing things, people who use that feature and would be disappointed if the server stopped offering it. We expect to complete this document and submit it for publication in March next year, so feedback in the next couple of months is greatly appreciated. Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --5700c796e0cc4161bd25c77fe738286f Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Hi IMAPEXT lurkers.  If you're not already in th= e EXTRA working group, there's discussion about the spec:

https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/

over on our list:
<= div style=3D"font-family:Arial;">

<= /div>

=
We're interested in feedback on a few = topics, and whether or not to include particular standards in our baseli= ne.

  • RFC6851 MOVE
  • RFC5182 SEARCHRES
  • STATUS DEL= ETED
  • RFC8474 OBJECTID
    • <= li style=3D"font-family:Arial;">RFC3516 BINARY
  • disallow "RENAME INBOX"
  • draft-ietf-extra-imap-replace

We're particul= arly interested in any feedback from people who will either find it hard= to implement one of these in their server, or in the case of removing t= hings, people who use that feature and would be disappointed if the serv= er stopped offering it.

<= /div>
We expect to complete this docume= nt and submit it for publication in March next year, so feedback in the = next couple of months is greatly appreciated.

Cheers,
=

Bron.

<= div class=3D"xtd from-col">
--
  Bro= n Gondwana, CEO, FastMail Pty Ltd
&nbs= p; brong@fastmailteam.com


--5700c796e0cc4161bd25c77fe738286f--