Re: [Jmap] I-D Action: draft-ietf-jmap-sieve-02.txt

[Stephan Bosch <[e-mail]>]

On 02/11/2020 12:35, [e-mail] wrote:
> 
> 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-02.txt
> 	Pages           : 25
> 	Date            : 2020-11-02
> 
> Abstract:
>     This document specifies a data model for managing Sieve scripts on a
>     server using JMAP.
> 
> Open Issues
> 
>     o  Should we introduce an "isIncluded" or "isInUse" filter/sort
>        condition for the /query method to locate scripts which are
>        included by others?
> 
>     o  Do we need any (rate) limits for /test?
> 
>     o  Should ":fcc" and associated arguments (e.g., ":flags",
>        ":create":, etc) reported in the /test response be in their own
>        "fcc" sub-object rather than listed inline with the rest of the
>        arguments for the action?
> 
> 
> 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-02
> https://datatracker.ietf.org/doc/html/draft-ietf-jmap-sieve-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-sieve-02
> 

First, I think this now misses a nice way to upload/download raw Sieve 
scripts (i.e. without JSON string escaping). As said earlier in this 
mailing list, using the blob upload/download facility would be better 
and it is more consistent with jmap:mail in my opinion.

Second, I remember RFC 5784 (https://tools.ietf.org/html/rfc5784) That 
is an effort to map the Sieve language grammar to XML. We could 
(optionally of course) do the same in this extension using JSON rather 
than XML and make it easier for clients to evaluate, display, and 
manipulate Sieve scripts without the need to write a Sieve 
parser/generator. This could be a "content:as(json)" field, or something 
like that. Or is that just too complex?

Regards,

Stephan.