[EAI] new terms Re: Unicode vs. UTF-8 / Encoding vs. Representation

["Jiankang YAO" <[e-mail]>]

----- Original Message ----- 
From: "Andrew Sullivan" <[e-mail]>
To: <[e-mail]>
Sent: Tuesday, December 28, 2010 8:23 PM
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation


> On Mon, Dec 27, 2010 at 11:17:32PM -0500, John C Klensin wrote:
> 
>> I hope someone in the WG will have a good suggestion.   If not,
>> we may be back to "ASCII" versus "non-ASCII" as the disjoint
>> pair, "Unicode"  to describe the international CCS (inclusive of
>> ASCII), and "UTF-8" to describe the particular encoding that is
>> used for this protocol and recommended by RFC 2277 (a
>> recommendation that is reinforced by draft-iab-idn-encoding and
>> other more recent work).
> 
> It seems to me that one could take a cue from the IDNA work, which
> differentiated A-label, U-label, LDH-label, and so on.
> 

yes, I think that we may borrow the ideas from RFC5890.

 A "U-label" is an IDNA-valid string of Unicode characters, in
      Normalization Form C (NFC) and including at least one non-ASCII
      character, expressed in a standard Unicode Encoding Form (such as
      UTF-8). 


I suggest to define the following terms:

U-character:
 A "U-character" is a non-ASCII Unicode character, in
      Normalization Form C (NFC) and expressed in a standard Unicode Encoding Form of UTF-8. 

 
U-string:
 A "U-string" is a string of Unicode characters, in
      Normalization Form C (NFC) and including at least one non-ASCII
      character, expressed in a standard Unicode Encoding Form of UTF-8. 

A-character:
  An  "A-character" is an ASCII Unicode character, expressed in a standard Unicode Encoding Form of UTF-8. 

A-string:
 An  "A-string" is  a string of Unicode characters,  including ASCII
      characters only, expressed in a standard Unicode Encoding Form of UTF-8. 


are  the definitions above clear?


another question is that we define these new terms in rfc5336bis or in rfc4952bis?


thanks.

Jiankang Yao