RE: [Gen-art] gen-art review of draft-ietf-sieve-imapflags-04.txt

--> -----Original Message-----
--> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com] 
--> Sent: Monday, May 08, 2006 6:15 AM
--> To: Gray, Eric
--> Cc: Gen-ART@ietf.org; Lisa Dusseault; Cyrus Daboo
--> Subject: Re: [Gen-art] gen-art review of 
--> draft-ietf-sieve-imapflags-04.txt
--> 

--- [SNIP] ---

--> My answers are below, please let me know if you have any 
--> further questions.
--> 
--> >Questions/Comments:
--> >==================
--> >
--> > In section 2.1, you say that spaces are acceptable (MUST 
--> > be always allowed) in flag names.  You also say that a 
--> > string containing a space-separated list of flags (I 
--> > assume flags in this context is the same as flag names) 
--> > is the same as "a string list consisting of the flags."
--> >
--> > I am not sure what this means,
--> >
--> A string list is denoted using ["value1", ..., "valueN"] 
--> notation in Sieve. It is a "list of strings" in usual 
--> programming language sense.
--> 
--> So the text is basically saying that "value1 value 2 ... 
--> valueN" is the same as ["value1", "value2", ..., "valueN"]
--> 
--> > but it seems to say that we MUST allow spaces as valid 
--> > both as part of a flag name and as a separator between 
--> > flag names.
--> >  
--> >
--> IMAP flags/keywords are not allowed to contain spaces 
--> according to RFC 3501.

Although I understand what you mean by string list, now, 
I am still not able to make complete sense of this.

In the third paragraph of section 2.1, you say - 

"The Sieve interpreter SHOULD check the list of flags for validity 
 as described by [IMAP] ABNF. In particular non-ASCII characters 
 are not allowed in flag names. However spaces MUST be always 
 allowed."

However, above you say - 

"IMAP flags/keywords are not allowed to contain spaces 
 according to RFC 3501."

The only way I can reconcile these two statements is by assuming
that "flags" is not the same as "flag names".  This is precisely
the opposite of what I said I was assuming in asking my question
above (I said "I assume flags in this context is the same as flag 
names").

>From your answer above, it seems that by "flags", you may mean
"flag values" as opposed to "flag names" as I had assumed.  Is
it possible for you to be more specific, or is it just assumed 
that anyone reading this specification would already know what 
these terms mean?

-->

--- [SNIP] ---

--> 
--> >Also - are all of the values, in the section 4 examples, 
--> valid flag-names?
--> >  
--> >
--> Yes. IMAP allows for any alpha-numeric value to be used as 
--> a keyword name.

What has me confused here is that the IMAP reference (RFC 3501)
says the following:

'All system flags begin with "\".'

Does that mean that the flag-names here are not "system flags",
or does it mean that the examples list "flag values" and not 
"flag names"?

--> 

--- [SNIP] ---

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art