KEP-0014.txt

[Georg Greve]

 KEP-0014.txt |    8 ++++++++
 1 file changed, 8 insertions(+)

New commits:
commit dc5cc5729c75e072245a1f0324b78800add0ffc6
Author: Georg Greve <greve at kolabsys.com>
Date:   Fri Sep 16 18:18:15 2011 +0200

    Final comments by Alec, let's hope that's it.

diff --git a/KEP-0014.txt b/KEP-0014.txt
index 64c6d53..1fc0739 100644
--- a/KEP-0014.txt
+++ b/KEP-0014.txt
@@ -21,6 +21,8 @@ The result is the ability to have different layers of Sieve management per user,
 == Naming Conventions ==
 For the purpose of this KEP, all file names of Sieve<ref name="sieve" /> scripts '''SHALL''' be given in their 'basename' only, so without extension, which is customarily dependent upon the specific IMAP server used. Cyrus IMAP commonly uses '.siv', Dovecot commonly uses '.sieve', other servers or variations of these servers may use different conventions. These extensions '''MAY''' be added as required or customary for the particular installation, but only the basename '''SHALL''' be considered authoritative.
 
+For reading and writing, clients '''SHALL''' consistently use the upper case form for all of [[#MASTER|MASTER]], [[#MANAGEMENT|MANAGEMENT]] and [[#USER|USER]] and '''SHALL''' append extensions in lower case, e.g. '.siv' and '.sieve' as done consistently in this KEP.
+
 == Enabling Non-Conflicting Sieve Editing ==
 In order to enable Non-Conflicting Sieve Editing according to this KEP, a [[#MASTER|MASTER]] alongside an no-op [[#MANAGEMENT|MANAGEMENT]] and [[#USER|USER]] file '''MUST''' be defined during platform integration and adapted during deployment. The [[#MASTER|MASTER]] '''SHALL''' then be considered authoritative for that deployment. 
 
@@ -53,6 +55,8 @@ To be compliant with this KEP, management systems that make use of Sieve for som
 * define a consistent name and version to be used in the provisions outlined in [[#MANAGEMENT|MANAGEMENT]];
 * write out the [[#MANAGEMENT|MANAGEMENT]] script as defined.
 
+The [[#MANAGEMENT|MANAGEMENT]] script '''SHALL NOT''' include any script from the user namespace, it '''MAY''' only include files from the global namespace.
+
 If there is no [[#MASTER|MASTER]] file in the users list of Sieve scripts, management systems '''MAY''' behave as they see fit, but '''MUST''' always ensure its users do not use [[#Protected Names|Protected Names]].
 
 If the management system aims to also control (de-)activation of the functionality defined in this KEP through creation or deletion of the [[#MASTER|MASTER]] script, it '''MUST''' ensure that it writes the [[#MASTER|MASTER]] as defined authoritatively for this platform or group of users, and '''MUST''' always write the [[#MANAGEMENT|MANAGEMENT]] script as defined herein.
@@ -206,6 +210,10 @@ Protected names under this KEP '''SHALL''' be
 * 'MANAGEMENT' for the script written out by management system of the system;
 * 'USER' for the control script of user editable scripts.
 
+All considerations of protected names '''SHALL''' be case-insensitive, e.g. MASTER, master, mAster and Master are '''all''' considered protected names regardless of their extension (if any). 
+
+
+
 == Upgrade Path ==
 
 This KEP introduces new conventions.