From: Clive D. W. Feather (clive@on-the-train.demon.co.uk)
Date: Fri Apr 12 2002 - 01:37:58 CDT
-----BEGIN PGP SIGNED MESSAGE-----
In message <200204042005.VAA25723@clw.cs.man.ac.uk>, Charles Lindsey
<chl@clw.cs.man.ac.uk> writes
>3. Our syntax allows parameters in all unstructured headers that our draft
>defines. This causes slight parsing difficulties in headers where a naked
>';' can occur in the main part of the header. In fact, that is just the
>headers with address-list in them.
>4. So we can consider a series of increasingly severe changes we might make:
>
>4a. Leave it as it is.
>
>4b. Disallow parameters in those address-list headers. That would eliminate
> Complaints-To
> Reply-To
> Mail-Copies-To
>(though you might exclude Complaints-To and Mail-Copies-To on the
>grounds that they are "ours", parsing problems or not)
I would prefer 4b, but can live with 4a. If you do 4b, you do it for all
three headers, because it eliminates the parsing ambiguity.
> UTF8-xtra-2-head = %xC2-DF
> UTF8-xtra-3-head = %xE0 %xA0-BF / %xE1-EC %x80-BF /
> %xED %x80-9F / %xEE-EF %x80-BF
> UTF8-xtra-4-head = %xF0 %x90-BF / %xF1-F7 %x80-BF
> UTF8-xtra-5-head = %xF8 %x88-BF / %xF9-FB %x80-BF
> UTF8-xtra-6-head = %xFC %x84-BF / %xFD %x80-BF
> UTF8-xtra-char = UTF8-xtra-2-head 1( UTF8-xtra-tail ) /
> UTF8-xtra-3-head 1( UTF8-xtra-tail ) /
> UTF8-xtra-4-head 2( UTF8-xtra-tail ) /
> UTF8-xtra-5-head 3( UTF8-xtra-tail ) /
> UTF8-xtra-6-head 4( UTF8-xtra-tail )
> UTF8-xtra-tail = %x80-BF
You may or may not recall a discussion on the NNTP list about changing
this, in particular by removing the -5- and -6- cases (Unicode says
these will never happen, as 0x10FFFF characters are enough for anyone).
Do you recall if a consensus was reached? The two ought to be
consistent.
- --
Clive D.W. Feather NOTE | Internet Expert | Work: <clive@demon.net>
Tel: +44 20 8371 1138 change | Demon Internet | Home: <clive@davros.org>
Fax: +44 870 051 9937 to fax | Thus plc | Web: <http://www.davros.org>
Written on my laptop; please observe the Reply-To address
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk 2.0.5
iQEVAwUBPLaAxSNAHP3TFZrhAQHxKQf/cdZuHY3y9LpHz8KCRKgpCLZQJlwNEKQL
Kp8BnAaHJeUtbQL0ZM6oBsvHoGg9B7uAA9PEElrhFdrv22YjNi4gl2+dRZDDyKtY
OEyU9rpc9tDa4Jlk6384j+AkjAXcQafPlBC2RV6YBBsU7elG3VXTO5DBIhTs39yh
B0hCv+bJQGWyn/toZokOkvvm7TnD9TBKypEwxjQ4Imu1MafqzZCUYhXQj7m2uYOU
+cqfnjhw6hqZxxyuwkKBFAEQ0qDSN3c+YFTZxnWxuYtyi2Xc549NNL2Ic/muwDrb
eCgSGSHeIlenBWLBgtTDTtvJapypV2SPf/XIBlhhAdk+i/kNVTpi3w==
=VmUE
-----END PGP SIGNATURE-----