On Sat, Feb 27, 2010 at 07:37:34PM +0000, Alexey Melnikov wrote:
Simon Horman wrote:
Hi,
Hi Simon,
I have two minor questions about inconsistencies
in the BNF in draft-ietf-sieve-managesieve-09 and the ACAP RFC 2244.
1. In draft-ietf-sieve-managesieve-09 there is
QUOTED-CHAR = SAFE-UTF8-CHAR / DQUOTE QUOTED-SPECIALS
And in RFC 2244 there is
QUOTED-CHAR = SAFE-UTF8-CHAR / "\" QUOTED-SPECIALS
Or in words, draft-ietf-sieve-managesieve-09 allows DQUOTE
as an escape character whereas RFC 2244 allows "\" as an
escape. RFC 2244 seems to make more sense to me. Is the
change in draft-ietf-sieve-managesieve-09 intentional?
Actually this is a bug I've introduced in
draft-ietf-sieve-managesieve-07 and it will be fixed before
publication of this document as an RFC.
So you should assume that RFC 2244 version is correct.
Thanks, will do.
2. In draft-ietf-sieve-managesieve-09 there is
SAFE-UTF8-CHAR = SAFE-CHAR / UTF8-2 / UTF8-3 / UTF8-4
;; <UTF8-2>, <UTF8-3> and <UTF8-4>
;; are defined in [UTF-8]
And in RFC 2244 there is
SAFE-UTF8-CHAR = SAFE-CHAR / UTF8-2 / UTF8-3 / UTF8-4 /
UTF8-5 / UTF8-6
I am curious to know why this change was made.
The new ABNF matches what is in RFC 3629, which is newer than RFC 2244.
To give you a bit more details: Unicode codepoints are 24bits, so so
far 5 or 6 octet sequences are not possible.
Ok, that makes sense. Thanks for the clarification.
_______________________________________________
sieve mailing list
sieve(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/sieve