IETF Logo Mail Archive

Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draft-ietf-dns-alt-tld

Paul Wouters <paul@nohats.ca> Mon, 08 August 2022 14:03 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9A8C14CF13 for <dnsop@ietfa.amsl.com>; Mon, 8 Aug 2022 07:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D6XjOrqXz-A6 for <dnsop@ietfa.amsl.com>; Mon, 8 Aug 2022 07:03:38 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (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 86523C13CCC2 for <dnsop@ietf.org>; Mon, 8 Aug 2022 07:02:54 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4M1dFT05frzCM6 for <dnsop@ietf.org>; Mon, 8 Aug 2022 16:02:53 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1659967373; bh=V8mt9dK5X3n5c5lG6D2uYL/ScArl6Jv3ypVtDUoo1Tg=; h=Date:From:To:Subject:In-Reply-To:References; b=IOlL+TwRgAMbShUQ05Stvf3u1nX6lfGfAzIar8YP3cxTiKsp4Oxm0WCqtC7gXMpgf NYYEqgJz3dpZia+ByfKNnh0CtvlyDBe62ti1VQhyWtyJxCOQLTqi9sTX+aUcAQr2s6 gtX+96LNgkaMMkjIfgsKJ3uXUTsFiuX8JpcwoqDU=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id ixhpOqcpR4TF for <dnsop@ietf.org>; Mon, 8 Aug 2022 16:02:52 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <dnsop@ietf.org>; Mon, 8 Aug 2022 16:02:52 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 579483B4141; Mon, 8 Aug 2022 10:02:51 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 564293B4140 for <dnsop@ietf.org>; Mon, 8 Aug 2022 10:02:51 -0400 (EDT)
Date: Mon, 08 Aug 2022 10:02:51 -0400
From: Paul Wouters <paul@nohats.ca>
To: dnsop <dnsop@ietf.org>
In-Reply-To: <aa4ac827-a829-2aa8-5ff1-6079700f6fe5@taugh.com>
Message-ID: <c31a6d4b-b222-e061-c71a-6a9d416da36e@nohats.ca>
References: <c9031076-a424-887a-3c1d-b8beb0746f84@rfc-editor.org> <D382DED4-A710-4F03-924A-24E18538E082@nohats.ca> <aa4ac827-a829-2aa8-5ff1-6079700f6fe5@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/eamlm529RCT7xPbge7m9hU7U3yc>
Subject: Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draft-ietf-dns-alt-tld
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2022 14:03:43 -0000

On Mon, 8 Aug 2022, John R Levine wrote:

>
>>  It is not a viable choice outside of a few nerds who are fully capable of
>>  getting a browser plug-in to handle gns:// URIs. Which would still allow
>>  all DNS parsing libraries to be used on the names.
>
> Sufficiently motivated people seem able to install whatever it is you need to 
> browse through Tor.  I wouldn't think a GNS resolver would be much harder.

Yes, they install an "app". GNS can do the same thing already without
IETF or ICANN as well. (if they need a namespace that is truly never
resolved through DNS, they could even use "gns.onion").

Paul

v2.23.0 | Report a Bug | By Email