[NNTP] Future-proofing for including capabilities in responses

[Charles Lindsey]

In <20050328090308.GA98698 at finch-staff-1.thus.net> "Clive D.W. Feather" <clive at demon.net> writes:

>Something like this:

>    The server MAY add any text after the
>    response code or last argument as appropriate, and the client MUST
>    NOT make decisions based on this text.  Such text MUST be separated
>    from the numeric status indicator or the last argument by at least
>|   one space. The text MUST NOT begin with the three octets %xE2.81.A3
>+   (the UTF-8 encoding for U+2063 "Invisible Separator"); this code is
>+   reserved for future versions of this specification.

I don't like the idea of a text which, even viewed in a UTF-8 reader with
full capabilities, contains an invisible character which has semantic
meaning.

>or

>|   one space. Future versions of this specification may allow a server
>+   to provide additional data instead of this text; any such data will
>+   begin with the two octets %xC0.9B (this sequence is an invalid UTF-8
>+   encoding of U+001B "Escape" and so cannot appear in a response).

And I like even less the idea of breaking the already-extablished UTF-8
standard.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl at clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5