For those wondering what's up with the Sieve base spec, it's currently
held up waiting for the comparator draft (draft-newman-i18n-comparator-04)
to get nailed down a bit. In particular, there's some uncertainty
over whether comparators take octets or characters as input and how
i;octet is defined and used in the definition of other comparators.
THe resolution of those issues are likely to require changes to
3028bis, so it would *really* help if more people reviewed the draft
and the discussion thereof.
The comparator draft is discussed on <public-ietf-collation(_at_)w3(_dot_)org>,
which is archived at
http://lists.w3.org/Archives/Public/public-ietf-collation/
This draft is a direct dependency of 3028bis, the IMAP i18n draft
(draft-ietf-imapext-i18n-05), and is also holding up the completion
of the Sieve 'body' extension, so we should all be interested in
finishing it.
Philip Guenther