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

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 07 March 2022 20:29 UTC

Return-Path: <paul.hoffman@vpnc.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 3D8923A0D0D; Mon, 7 Mar 2022 12:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.722
X-Spam-Level:
X-Spam-Status: No, score=-0.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.186, MAY_BE_FORGED=1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 PlM3f3tTDPFf; Mon, 7 Mar 2022 12:29:02 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 1C1863A0D39; Mon, 7 Mar 2022 12:28:46 -0800 (PST)
Received: from [10.32.60.200] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged)) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 227KRQnc006183 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 7 Mar 2022 13:27:27 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged) claimed to be [10.32.60.200]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: "Schanzenbach, Martin" <schanzen@gnunet.org>
Cc: "Independent Submissions Editor (Eliot Lear)" <rfc-ise@rfc-editor.org>, Christian Grothoff <grothoff@gnunet.org>, Jiankang Yao <yaojk@cnnic.cn>, "draft-schanzen-gns.all" <draft-schanzen-gns.all@ietf.org>, i18ndir@ietf.org
Date: Mon, 07 Mar 2022 12:28:34 -0800
X-Mailer: MailMate (1.14r5798)
Message-ID: <C05803EF-505B-49EC-96A8-B3183A9E773B@vpnc.org>
In-Reply-To: <CCBCC361-976C-439C-B718-C0985913DD31@gnunet.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> <d81600c6-f224-d805-7d32-901cbecb3412@gnunet.org> <54d2d315-aa18-1498-4844-f1ae94930425@rfc-editor.org> <CCBCC361-976C-439C-B718-C0985913DD31@gnunet.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/Ruat_peGs9Vv-kPmGNvZWfbi5WM>
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 20:29:03 -0000

On 7 Mar 2022, at 10:45, Schanzenbach, Martin wrote:

> Ah I think this brings us on the right path.
> I am thinking about adding a security/privacy consideration with 
> respect to name leakage:
>
> """
> Name Leakage
>
> GNS names are indistiguishable from DNS names or other special-use 
> domain names [RFC6761].

This statement is not technically true, and making it definitively true 
is difficult in the protocol. To help clarify, I think you mean "GNS 
display names", not on-the-wire names; GNS on-the-wire names are quite 
different than DNS on-the-wire names.

But more significantly, the GNS spec in many places optionally allows 
GNS names and labels (display) to use Unicode characters and label/name 
lengths different from the DNS. Thus many GNS names are distinguishable, 
but many are not, so any security consideration becomes much more 
involved than the wording you proposed.

--Paul Hoffman