Re: Reference for UTF8 in SSH UTF8 terminal mode

[Ron Frederick <ronf%timeheart.net@localhost>]

On Dec 12, 2016, at 10:24 PM, Mark Baushke <mdb%juniper.net@localhost> wrote:
>> On Dec 12, 2016, at 11:58 AM, Daniel Migault <daniel.migault%ericsson.com@localhost> wrote:
>> 
>> Hi,
>> 
>> Apology for the confusion. So my understanding of the problem is that using RFC3629 as a reference for the UTF-8 is not convenient as its two normative references need to be updated. The two references in question are: ISO/IEC 10646:2014 and Unicode. However from this thread, I am hearing that the major concern is about providing a updated reference for Unicode, not so much ISO/IEC 10646. As a result,
>> 
>> I propose to have the following references:
>> 
>> RFC3629 as normative
>> [UNICODE]  The Unicode Consortium. The Unicode Standard.
>>              <http://www.unicode.org/versions/latest/> as informational.
>> 
> 
> I like it.
> 
>> A more recent version of ISO/IEC 10646 will be done by refreshing RFC3629.
> 
> Yes.
> 
>> Am I correct ?
> 
> It seems like a good plan to me.


Sounds good here as well. Thanks!
-- 
Ron Frederick
ronf%timeheart.net@localhost