From nobody Tue Sep 20 07:31:08 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MWtWj2V54z4cF2K for ; Tue, 20 Sep 2022 07:31:13 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MWtWj225fz3ltg; Tue, 20 Sep 2022 07:31:13 +0000 (UTC) (envelope-from se@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1663659073; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=D0AN3vP8dnoUSZPo1uuYrjGew4tnaruwG9trU3xzqS0=; b=j2rMsu50gCKLgyiWJ3vbZbjM6N78LaYdr0e4ljpM5O5tIi4kYF8oqZLVaHDxMCbP7o+VPf YpcIVcEGbvHywxvBlqSrkePegZZvSnt2+Dk7zbr05jQw3tfg8lEpIK6xXNFhtvoeKpIwed RfTBngW0UDN5bBUmxnYebcSgegwd6Ni/kYsfwPesKp36f+1sbKQshBHdBvUfd7hVFHcuQ0 yRYaVBOBFUhuoXgV/VLlQ/FKMpl8/87o62H1oTkxO7tBcxZk+l+G7UmZeRE6CHzx4I2cCz 5JAqWmZL4sn2EbF4vejL7XnYwXScoPJ2eURaOS+uq4b6zdt99dq9aK78J27Wqw== Received: from [IPV6:2003:cd:5f24:dc00:8961:6db6:e7ab:e906] (p200300cd5f24dc0089616db6e7abe906.dip0.t-ipconnect.de [IPv6:2003:cd:5f24:dc00:8961:6db6:e7ab:e906]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4MWtWh4jgpz18qr; Tue, 20 Sep 2022 07:31:12 +0000 (UTC) (envelope-from se@FreeBSD.org) Message-ID: Date: Tue, 20 Sep 2022 09:31:08 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: domain names and internationalization? To: Rick Macklem References: From: Stefan Esser Cc: freebsd-current Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1663659073; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=D0AN3vP8dnoUSZPo1uuYrjGew4tnaruwG9trU3xzqS0=; b=bvCayp8HDZ6mREuL42knHYMqDHmpd80NTXwZSFbJuOJMgpMiEuIfjOzuF6nuMITDns6KJh kb9yaP0wdWyVWAIxNAgZEz3xanzISnTmWvbSoqxHfSLEfKDuBhdtblR3c4X6uzGQwOk6Ea 9Bk1EdoVAGAJU4OuyXAWEt+xM4rAYyHmpScTljz7A329YGC2LgN0+iG6SBcYTCYezpMy9f R6LpyDP2ykGuZsol2bVRB1EldTVm5Hz0G55ao36vRIP0SX2AyMz+NQIhYQoCy+xvNwFpg2 AUnprFgVGvAEZl/wy5fK9rrAmkSXP24cHWw5kHQRd7RuY1JdACdGN3NGUEwQoQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1663659073; a=rsa-sha256; cv=none; b=IJ33WRa6nhspzWz39VGvuW9wkrAZCm28R6+25p8yjKCE9nhDVD6AeXspR4s7NTvaGJzSgJ p0xbKRaHjzKv8egUoHAr7GksXWdHkfWrzhkwlEehjzH8E9R2DPdR64nDyXaxPnexPPrz9T sVi82KID8iGEO7Yvo1Fgnb8SYhdClmmif8N8Dxs8UQLEH7lflXZty7cfK1hb4kZKM7jii5 K8Hn2fGFOSv4Nl0oBOr9yfw6Vjehgk+XyW31EfZFj2wmzKJdaw8NaYmn84LaJOvrO/MGTE NSDeiaXzvFX2TJSxzl1itdPDdt0KP+a9rlH+INsPvE3bufpJX0d40H/Yv8DqTA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N Am 19.09.22 um 22:27 schrieb Rick Macklem: > Hi, > > Recently there has been discussion on the NFSv4 IETF working > group email list w.r.t. internationalization for the domain name > it uses for users/groups. Hi Rick, I do assume that you know about RFC 3492 (Punycode): https://datatracker.ietf.org/doc/html/rfc3492 > Right now, I am pretty sure the FreeBSD nfsuserd(8) only works > for ascii domain names, but... You can manually translate domain names into their Punycode representation. The NFS code could work with them and only translate them back to UTF-8 (or whatever) for display purposes. For pure ASCII this is an identity transformation, for names that actually represent UTF-8 strings, the value to send to DNS servers (and to locally store in the daemon) could be the internally stored Punycode representation. > I am hoping someone knows what DNS does in this area (the > working group list uses terms like umlaut, which I have never > even heard of;-). That's the contraction of "ae", "oe", "ue" that has long ago been introduced into the German writing system, with the "e" abbreviated to two dots above the vocal, e.g. "ae" --> "รค". Just a convenience rule to speed up manually copying the bible in monasteries in medieval times ;-) But there are many other accented letters in other languages, that can be used in internationalized domain names, and the whole set of Unicode characters can be represented using Punycode. > I know essentially nothing about internationalization, so any hints > will be appreciated. For a start: https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode There are C implementations of the transformations, e.g. in the dns/libidn2 port. We do not seem to have equivalent library functions in the FreeBSD base system yet, but probably should provide them. Best regards, STefan