sorry, I want to add a small open item, a change in section 6,
Extensibility:
Extensions MUST state how they interact with constraints defined in
section 2.10, e.g., whether they cancel the implicit keep, and which
actions they are compatible and incompatible with.
+ An extension MUST NOT change the behavior of the "require" control
+ command.
I think this is OK, but do note that require "variables" changes
the semantics of subsequent strings.
yes, except for the arguments to "require", see the last sentence in the
introduction:
1. Introduction
This is an extension to the Sieve language defined by [SIEVE]. It
adds support for storing and referencing named data. The mechanisms
detailed in this document will only apply to Sieve scripts that
include a require clause for the "variables" extension. The require
clauses themselves are not affected by this extension.
I don't want to have text that
forbids this or comparable extensions that modify semantics in some way.
sorry -- do you want to allow an extension which changes "require"
semantics or not?
--
Kjetil T.