On Wed, 22 Oct 2025 at 09:00, Edward Shryane <[email protected]> wrote: > > Dear colleagues, > > As I presented at RIPE 89 and RIPE 90, I'd like to propose to allow UTF-8 > encoded characters in "descr:" and "remarks:" attributes. > > Is there support for adding UTF-8 in the RIPE database? Please let me know > your feedback.
I support adding some support for UTF-8 as the first step on a path towards more UTF-8. [...] > Personal Data > Users must not add personal data in “remarks:” or “descr:” attributes, as > these attributes are not included in the daily limit accounting, are not > validated as they contain free text, and are not filtered by default. This is > already the case in the RIPE database and the introduction of UTF-8 encoding > does not change this. Personal data with UTF-8 encoding is out of scope. What happens if or when someone does include personal data here? Thanks, Leo ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
