L2/03-251
From: Mark Davis
To: Paul Hoffman / IMC
Sent: Tuesday, June 24, 2003 17:20
Subject: Re: Public Review Issue #10

Paul, I must not be making myself clear. These characters never were
Control Characters (Cc), they were Format Characters (Cf). Many of
could be reasonably restricted in an identifier-like environment. But
that is also true of other characters that are neither Cc nor Cf.

Anyone who is using the spec will work from the tables in the spec,
which just simply lists the characters in a given table. So it doesn't
matter in practice.

So at the next rev, put in a line of documentation above Object
Replacement Character (remember, that is in the table, but is already
not a Cf) and Annotation Characters saying that these chacters,
although neither control characters nor format characters, share some
characteristics and are not suitable for identifier-like contexts.

Mark

__________________________________

----- Original Message -----
From: Paul Hoffman / IMC
To: Mark Davis
Sent: Tuesday, June 24, 2003 16:33
Subject: Re: Public Review Issue #10
>
>
> At 3:46 PM -0700 6/24/03, Mark Davis wrote:
> >Paul, Cf is not a Control character. Moreover, the classification (as
> >being in table 5.6) does not need to change; they are still
> >inappropriate for identifier-like text.
>
> I agree that we don't have to remove them from 5.6; I'm worried about
> section 5.2, as I said in my message.
>
> >  So the RFC does not need to
> > change right now. (At some point it will be appropriate, to add new
> >characters.)
>
> Section 5.2 says:
>
>     Control characters (or characters with control function) cannot be
>     seen and can cause unpredictable results when displayed.  Note that
>     the list below is split into two tables in appendix C: Table C.2.1
>     contains the ASCII code points, while Table C.2.2 contains the non-
>     ASCII code points.  Most profiles of this document that want to
>     prohibit control characters will want to include both tables.
>
> These characters are listed in section 5.2. If they are no longer
> control characters, we have to remove them from section 5.2, change
> the tables, and make sure that every RFC that uses section 5.2 also
> uses section 5.6.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>