Re: [DNSOP] punctuation follies, I-D Action: draft-ietf-dnsop-alt-tld-15.txt

Paul Wouters <paul@nohats.ca> Tue, 28 June 2022 02:54 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 26452C15A732 for <dnsop@ietfa.amsl.com>; Mon, 27 Jun 2022 19:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 0eHxjNEqMLYg for <dnsop@ietfa.amsl.com>; Mon, 27 Jun 2022 19:54:07 -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 ED753C1595E6 for <dnsop@ietf.org>; Mon, 27 Jun 2022 19:54:06 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4LX8Lf3cbzz2pC for <dnsop@ietf.org>; Tue, 28 Jun 2022 04:54:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1656384842; bh=0WtAJTmrFT1d6qa6Kj+oILHydY9+H3D1KlJqk5HUgaQ=; h=Date:From:To:Subject:In-Reply-To:References; b=tkdXOWHbzcf1SBRicKN5qkDjNYXYZWX7bIjKhV1Y5cBjwNQa2Qa6Neh5Y4sCzrYZN n5GKXCEWcFcihAhtGuC8rBHpCY6olzqCHro6CS5mfIphunfHUFu/kYcySruUh4QqiX 6LIZfJpIw/4bTRRgtD+EoC6nO4IXs0ls02WOExr4=
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 B3mzf5WYykzD for <dnsop@ietf.org>; Tue, 28 Jun 2022 04:54:01 +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>; Tue, 28 Jun 2022 04:54:01 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id C3AA639AC8A; Mon, 27 Jun 2022 22:54:00 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C026939AC89 for <dnsop@ietf.org>; Mon, 27 Jun 2022 22:54:00 -0400 (EDT)
Date: Mon, 27 Jun 2022 22:54:00 -0400
From: Paul Wouters <paul@nohats.ca>
To: dnsop <dnsop@ietf.org>
In-Reply-To: <20220628011909.133AD4496382@ary.qy>
Message-ID: <6f4c53a-2fca-bbfe-601a-5e6ab29038e5@nohats.ca>
References: <20220628011909.133AD4496382@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/g7GlLQ7psrbR-OvfOcVh8pufO1E>
Subject: Re: [DNSOP] punctuation follies, I-D Action: draft-ietf-dnsop-alt-tld-15.txt
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: Tue, 28 Jun 2022 02:54:11 -0000

On Mon, 27 Jun 2022, John Levine wrote:

> spec, it would take a long time for the changes to percolate out into
> the field. There is still plenty of software using TLS 1.1 which was
> published in 2006 and deprecated a year ago.

That does not apply to tor nodes though. These are forced to have some
minimum version of tor or else the nodes are kicked out of the network
for being too insecure. So their long tail is much shorter.

> You'd also need to update web browsers and the SOCKS proxies that are
> usually used to connect the TOR sessions to the browsers. How much
> time are you prepared to spend to persuade them all that they should
> allow _label as the rightmost label?

2-3 years.

Paul
ps. note that I don't think they will change to use _underscore.
ps2. I think we should drop alt, underscore et all proposals
ps3. and formally kill Special Use domains :P