[Last-Call] Re: Secdir last call review of draft-ietf-lisp-name-encoding-08

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Unfortunately, the bad news is that in the era of Unicode, you have to think about the issues. There are a variety of reasons why allowing all Unicode characters in your names is a bad idea. I think you should go read RFC8264 (maybe just the first few sections, it’s a heavy lift) and https://www.ietf.org/archive/id/draft-bray-unichars-09.html (shorter but less thorough) and decide what you think would appropriate for your name field. 

Just saying “UTF-8” would not be helpful. What you need to specify is a character repertoire, not an encoding scheme.

On Jul 10, 2024 at 9:51:44 AM, Dino Farinacci <farinacci@xxxxxxxxx> wrote:
Should we just make a statement with a reference. And what reference is best so you will accept the change?

Dino

On Jul 10, 2024, at 7:02 AM, Salz, Rich <rsalz@xxxxxxxxxx> wrote:

> One of the reasons I wanted to avoid all this and keep it simple.

It is not an ASCII world any more.  This draft should not move forward.


-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux