<html><head></head><body><div class="ydp50e55796yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div> <div dir="ltr" data-setdir="false">Hi Nick</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">"<span style="color: rgb(38, 40, 42);">would it be possible to work towards a day in the future when </span><div><span style="color: rgb(38, 40, 42); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;">the ripedb could formally support utf8 across multiple different field </span><br clear="none" style="color: rgb(38, 40, 42); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;"><span style="color: rgb(38, 40, 42); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;">types, not just email addresses?"</span></div><div><span style="color: rgb(38, 40, 42); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;"><br></span></div><div dir="ltr" data-setdir="false"><div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;">The technical aspect of utilising utf-8 in the RIPE Database has been looked at several times by the RIPE NCC, but it never moves forward because of the social/political/registry/legal issues which cannot be resolved at the technical level:</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;"><br></div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;">-Should we allow all/some/none of the data content to be in non Latin characters?</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;">-Is there some data content that must be in Latin characters (for the correct functioning of the registry?), some that can be duplicated in Latin and local characters, some that can be in any format chosen by the resource holder?</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false">-If some data is duplicated how will the duplicate sets of data be verified as a consistent set (does it need to be the same data)?</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false">-Who needs to be able to interpret which parts of the data content and for what purpose?</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;">-Who can make these decisions (this is the bit that has been missing ever since the subject of utf-8 was first raised many years ago)?</div></div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;"><br></div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false">Probably puny code can be implemented for IDNs in a matter of weeks, full implementation of utf-8 may take years.</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false"><br></div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false">cheers</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false">denis</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false"><br></div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false">co-chair DB-WG</div><div style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;" dir="ltr" data-setdir="false"><br></div></div><div><span style="color: rgb(38, 40, 42); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;"><br></span></div></div><div><br></div> </div><div id="ydpc09e4d26yahoo_quoted_4259662080" class="ydpc09e4d26yahoo_quoted"> <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"> <div> On Tuesday, 7 July 2020, 23:54:13 CEST, Nick Hilliard via db-wg <db-wg@ripe.net> wrote: </div> <div><br></div> <div><br></div> <div><div dir="ltr">Gert Doering via db-wg wrote on 07/07/2020 16:21:<div class="ydpc09e4d26yqt7938808947" id="ydpc09e4d26yqtfd71830"><br clear="none">> On Tue, Jul 07, 2020 at 05:03:01PM +0200, Benedikt Neuffer wrote:<br clear="none">>> I think at the moment it would be easier to update the clients to<br clear="none">>> convert punycode in whatever encoding you prefer.<br clear="none">> <br clear="none">> Cementing this abomination even more...</div><br clear="none"><br clear="none">No-one likes punycode.<br clear="none"><br clear="none">Do you have a better suggestion? Would raw utf8 work here? How much <br clear="none">would it break? If there were broader support in the ripedb codebase <br clear="none">for utf8, would it be possible to work towards a day in the future when <br clear="none">the ripedb could formally support utf8 across multiple different field <br clear="none">types, not just email addresses?<br clear="none"><br clear="none">Nick<div class="ydpc09e4d26yqt7938808947" id="ydpc09e4d26yqtfd96127"><br clear="none"><br clear="none"><br clear="none"></div></div></div> </div> </div></body></html>