[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MORG] WGLC on draft-ietf-morg-inthread-00

Some additional comments:


3.1. The INTHREAD Search Key

[...]


   The INTHREAD search-key matches a message if its subsidiary search-
   key matches at least one message in the same thread as the message.
Every time I looked at this sentence it makes me 20 seconds in order to understand it. Wouldn't it be better to say that first all messages matching the subsidiary search-key are found. Then all messages belonging to the same threads are returned. 


3.5. The THREAD=* Search Return Option(s)

   The THREAD=* search return options enables the client to select
   which threading algorithm the server uses when processing INTHREAD,
   THREADROOT and THREADLEAF as part of a SEARCH command. If THREAD=*
   isn't specified, then the default for the SEARCH command is
   THREAD=REFS.
I hate to raise this issue, but should we establish an IANA registry for search return options? 


5.  Formal Syntax

   The following syntax specification uses the Augmented Backus-Naur
   Form (ABNF) notation as specified in [RFC5234]. [RFC3501] defines
   the non-terminals "capability" and "search-key", [RFC4466] defines
   "search-return-opt", [RFC5256] defines "thread-alg", and [RFC5322]
   defines "id-left" and "id-right".

   Except as noted otherwise, all alphabetic characters are case-
   insensitive.  The use of upper or lower case characters to define
   token strings is for editorial clarity only.  Implementations MUST
   accept these strings in a case-insensitive fashion.

       capability   =/ "SEARCH=INTHREAD" / "THREAD=REFS"

       search-key   =/ "INTHREAD" SP search-key / "MESSAGEID" SP "<"
                       id-left "@" id-right ">"
I am not entirely convinced (but I haven't yet checked that '"<" id-left "@" id-right ">"' corresponds to atom IMAP syntax. I think quoted strings/literals would be needed to represent some values. 


/ "THREADROOT" /
                       "THREADLEAF"