Subject: Re: [EAI] Consensus Result on Issue #5 - Keep nested encodings for message/global?

From: Joseph Yee <[email-masked]>
Date: Wed, 16 Feb 2011 01:29:51 -0500

The WG went through rounds to determine name selection for poll then poll to determine the actual name in 2007.  Names in various 'message/rfc2822' extensions had been suggested and the WG consensus preferred name not in the format of extension.

The WG will not reopen the issue regarding name change to 'message/global'.

Regards,
Joseph, co-chair EAI

On 2011-01-28, at 11:41 AM, Dave CROCKER wrote:

> 
> 
> On 1/28/2011 8:27 AM, Joseph Yee wrote:
>> Following responses, this issue reached the consensus of keep the nested encoding for message/global.
>> 
>> 7 people expressed their opinions:
>>     keep it:
> ...
>>     remove it:
>>         Dave Crocker
> 
> 
> Sorry my response was unclear.
> 
> I meant that it should be kept, but should be renamed to message/utf8-rfc822.
> 
> The purpose of renaming is to make it clear that this is a variation of an existing, important message type.  In addition "global" is far too generic, IMO.
> 
> d/
> 
> -- 
> 
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net