Re: [EAI] [eai] #11: Capture the scenario of "SHOULD not use UTF-8 in Message-ID" for future advice draft

[Dave CROCKER <[e-mail]>]

On 9/19/2011 7:58 AM, [e-mail] wrote:
>>   "Implementers of message-id generation algorithms may prefer to restrain
>>   their output to ASCII since that has a few minor advantages, such as when
>>   constructing References fields in mailing-list threads where some senders
>>   use EAI and others not."


I looked over the draft, and this language made me very uncomfortable.

The reason is that -- once again -- it has this draft trying to juggle a hybrid 
(UTF-8/ASCII-only) world, rather than a much simpler UTF-8 only world.  Indeed, 
the language that results looks awkward.

A simple question is why this juggling is appropriate here but not in the rest 
of the core drafts, including this one?

For the situations that need this special treatment, why do they /not/ also need 
it for all other occurrences of UTF-8.  And in answering that question, consider 
whether those are edge conditions or likely to be typical.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net