[New-wg-docs] I-D Action: draft-ietf-jmap-sieve-00.txt

internet-drafts@ietf.org Sun, 06 September 2020 12:46 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: new-wg-docs@ietf.org
Delivered-To: new-wg-docs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8763A0DD3 for <new-wg-docs@ietf.org>; Sun, 6 Sep 2020 05:46:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <new-wg-docs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.15.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159939639110.12479.7382820975555945575@ietfa.amsl.com>
Date: Sun, 06 Sep 2020 05:46:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-wg-docs/BoiggNIqPuf-DGzAVyIc6suNamo>
Subject: [New-wg-docs] I-D Action: draft-ietf-jmap-sieve-00.txt
X-BeenThere: new-wg-docs@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <new-wg-docs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/new-wg-docs>, <mailto:new-wg-docs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/new-wg-docs/>
List-Post: <mailto:new-wg-docs@ietf.org>
List-Help: <mailto:new-wg-docs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/new-wg-docs>, <mailto:new-wg-docs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Sep 2020 12:46:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the JSON Mail Access Protocol WG of the IETF.

        Title           : JMAP for Sieve Scripts
        Author          : Kenneth Murchison
	Filename        : draft-ietf-jmap-sieve-00.txt
	Pages           : 15
	Date            : 2020-09-04

Abstract:
   This document specifies a data model for managing Sieve scripts on a
   server using JMAP.

Open Issues

   o  Do we need/want both "content" and "blobId" in the SieveScript
      object?  It may be simpler to have just one way of specifying
      content and "blobId" is more versatile and doesn't require JSON-
      encoding of the content.  Furthermore, use of the forthcoming(?)
      Blob/set method would avoid the extra roundtrip of having to
      upload the blob first.

   o  Should changes made by onSuccessActivateScript be reported in the
      response to the client-initiated request, or via a second implicit
      SIeveScript/set response?

   o  The strawman for SieveScript/test only uses blobIds.  Will this
      have to change once the issue regarding content/blobId in
      SieveScript is resolved?


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-jmap-sieve/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-jmap-sieve-00
https://datatracker.ietf.org/doc/html/draft-ietf-jmap-sieve-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/