Re: Clarifying "implementations MUST NOT allow variable expansion in the script name argument" [WAS Re: I-D Action: draft-ietf-sieve-include-12.txt]

The full sentence is:

187           The script name argument MUST be a constant string as
188           defined in <xref target='RFC5229'>VARIABLES</xref>, Section 3;
189           implementations MUST NOT allow variable expansion in the script
190           name argument.

I believe that this is sufficient, bordering on repeating itself.

On Tue, Sep 27, 2011 at 12:22 PM, Robert Burrell Donkin
<[email protected]> wrote:
> On Sat, Sep 24, 2011 at 7:37 PM, Barry Leiba <[email protected]> wrote:
>> I'm going to hold off on sending this version to Pete until Robert's
>> and Stephan's notes are responded to and we've resolved what we're
>> going to do (or not) about those.
>
> And one more :-)
>
> draft-ietf-sieve-include-12 specifies:
>
> "implementations MUST NOT allow variable expansion in the script name argument"
>
> A clear specification should unambiguously describe the expected
> behaviour. I would therefore prefer something tighter, either [1] or
> [2] (or something else if I've guessed the intended meaning wrong).
>
> Robert
>
> [1] "Implementations supporting VARIABLES [RFC5229] MUST NOT expand
> variables in the script name argument."
> [2] "Implementations supporting VARIABLES [RFC5229] MUST terminate
> execution by raising an error unless the script name argument is a
> constant string as defined in VARIABLES [RFC5229], Section 3."
>
_______________________________________________
sieve mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sieve