Subject: [Fwd: DISCUSS and COMMENT: draft-ietf-sieve-mime-loop]

From: Alexey Melnikov <[email-masked]>
Date: Wed, 12 Aug 2009 22:17:40 +0100

FYI.

Subject: DISCUSS and COMMENT: draft-ietf-sieve-mime-loop
From: Tim Polk <[email-masked]>
To: [email-masked]
Cc: [email-masked], [email-masked], [email-masked]
Date: Wed, 12 Aug 2009 04:40:31 -0700 (PDT)

Discuss:
This is a good document overall, but there are a few issues that need to be addressed to
ensure consistency and interoperability of implementations.

(1) In section 3, the semantics of a "break" command that omits a name in a nested 
"foreverypart" is not clearly specified.  In this case, does the "break" terminate the closest 
enclosing loop, or the outermost?

(2) In section 4.1, the semantics of ":anychild" in the absence of the ":mime" tagged argument 
is not specified, but this construct is permitted by the ABNF and is not forbidden by the text.

Since sections 4.2 and 4.3 reference 4.1 for the behavior of ":anychild" this ambiguity ripples 
forward.

(3) In sections 4.2 and 4.3, the following text is ambiguous:

    "the use of "address" with no ":mime" and ":anychild" tagged arguments ..."

Does the no apply to both arguments or just one? if it applies to both, it might be clearer 
to state: 

    "the use of "address" when both the ":mime" and ":anychild" tagged arguments
     are omitted ..."

Comment:
There is at least one occurrence of "SIEVE" in section 11, but most (all?) other occurrences are "Sieve"

For consistency, suggest the global change
s/SIEVE/Sieve/