Re: [I18ndir] I18ndir early review of draft-schanzen-gns-10

Christian Grothoff <grothoff@gnunet.org> Mon, 07 March 2022 15:24 UTC

Return-Path: <grothoff@gnunet.org>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFCC3A0E8A; Mon, 7 Mar 2022 07:24:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBtqpBnm-jIp; Mon, 7 Mar 2022 07:24:21 -0800 (PST)
Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 725A43A0E95; Mon, 7 Mar 2022 07:24:15 -0800 (PST)
Received: from [2001:470:142:3::e] (port=45270 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <grothoff@gnunet.org>) id 1nRFDX-0001ZW-Rw; Mon, 07 Mar 2022 10:24:11 -0500
Received: from [195.167.221.218] (port=39368 helo=[10.15.167.96]) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from <grothoff@gnunet.org>) id 1nRFDX-0003Ok-EF; Mon, 07 Mar 2022 10:24:11 -0500
Message-ID: <d81600c6-f224-d805-7d32-901cbecb3412@gnunet.org>
Date: Mon, 07 Mar 2022 16:24:09 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: Jiankang Yao <yaojk@cnnic.cn>, "Schanzenbach, Martin" <schanzen@gnunet.org>, rfc-ise <rfc-ise@rfc-editor.org>
Cc: "draft-schanzen-gns.all" <draft-schanzen-gns.all@ietf.org>, "i18ndir@ietf.org" <i18ndir@ietf.org>
References: <164638828309.28413.11846349950083727255@ietfa.amsl.com> <02ce8381-11b8-196a-c0bc-afa21cccec1f@rfc-editor.org> <7A835641-2DF1-4887-A79F-9481C8DB6D6B@gnunet.org> <2022030717083858073951@cnnic.cn>
From: Christian Grothoff <grothoff@gnunet.org>
In-Reply-To: <2022030717083858073951@cnnic.cn>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/Cqons0GxYbTZob6G-wZSsJdQZKY>
Subject: Re: [I18ndir] I18ndir early review of draft-schanzen-gns-10
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2022 15:24:35 -0000

On 3/7/22 10:09, Jiankang Yao wrote:
>> >> 4)ICANN manages the DNS name root space. I suggest to ask some
> experts from
>> >> ICANN to review this document.
>> >> 
>> > This is a name space NOT managed by ICANN.  The issues we are
> concerned about are interactions with the DNS, and of course i18n.
>> 
> 
> Yes, it is NOT managed by ICANN, but "the use of GNS may clash with the
> DNS namespace".
> 
> The DNS name space (common global identfiers) is very important to
> Internet
> success.https://www.internetsociety.org/issues/internet-way-of-networking/
> <https://www.internetsociety.org/issues/internet-way-of-networking/> 
> 
> So before moving this document to the next step, I suggest to get some
> comments from IETFer affiliated with ICANN.
> 

Well, that has been discussed to death, with Warren Kumari even writing
RFC 8244 about the *discussion* that we triggered about it in 2013 (!)
at dnsop and beyond -- including Martin's presentation at ICANN about GNS.

So IMO this is very far outside of the scope of the i18n review, and
simply another topic that the IAB has decided to punt on (my
interpretation). So this is a political issue, which we cannot solve
anymore and will just leave as-is / unresolved / potentially
conflicting.  The expert reviewers (like Bortzmeyer) are also very well
aware of the discussion --- it triggered like 1000 e-mails on dnsop back
in the day...

My 2 cents

Christian