[DNSOP] Please review and provide feedback -- draft-stw-6761ext

Warren Kumari <warren@kumari.net> Tue, 06 August 2019 19:44 UTC

Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6192212021D for <dnsop@ietfa.amsl.com>; Tue, 6 Aug 2019 12:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id yzwt7Z0HVJjj for <dnsop@ietfa.amsl.com>; Tue, 6 Aug 2019 12:44:22 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 275BE12016E for <dnsop@ietf.org>; Tue, 6 Aug 2019 12:44:22 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id r21so63959494qke.2 for <dnsop@ietf.org>; Tue, 06 Aug 2019 12:44:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=Qv1q29XmXkwQAjuCEr8WwhYZhgGLQ7nygUiB0/ND5bc=; b=DDXu+/2eXPPPpoN6tqCaHfDGAr6+/iP6kg6eZAK18Mb4/tS38agfng3E3qpZT7xqQS fm0JiN/cI6PBjQ3mE9zLfGSKci0xLKBgF1/Nwe0gAlyYxocfBKGACQRuflbPQclEF7A/ +k8b/EIH7B8bd2lm3ITj2NDp1TsUsDv4iGgn2xDQ0jN/Szs4ZV4ysCE9tgsc+NdZSsvn +EILbXIQw22eHUuxwR0qwEHIxOYsd+CeXMMsOq49W1A5qsINhuTBNJPIgrO7FPBlQHTX kh4eSIZPD1yFkyVpHsLhWryc1fXoiMjrlNq+U7mi9AHng/kWCG3c/NNtOhTwIAZPvk2V ZPRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=Qv1q29XmXkwQAjuCEr8WwhYZhgGLQ7nygUiB0/ND5bc=; b=ezrZ9pJ5dYJ68WBJuX9fWKD8j1rBPE/HZyR7H+PAR1gyDQMDvhL+4nVL9nXreJuQh7 gj6+IMQlWFQqvzQhTqJ7+F3ns+cPMZVkiw1Vz+iuAtARZdCROoVrdL+OtW9/jCkWQjtk YYaOJwer2IeLY8aNEofFEKaAa4NokIjIvojhlim8D6lhLrzueq8c17I+A+sNPzGqx+tj 1HA+BUw3xr81TqQnS3fAn3ypBYuf0Y6GMsk1yw1+YjMEMsk7z3MADackS7IkDCHDW1ID a8DX7H+tSOrdW2sWgEqIAXhl29jgYWtAbNDmp5NG5PWsSszu/tuXQ3d1DzQkBEFKE3u3 Zalg==
X-Gm-Message-State: APjAAAWN3dUTvp7TNYIcIUpSiSem9yVSI29aBBXxMrBjR3uTwFFM3VGn P0iuQ+VLZzX0jYI+/IUC/rN7f3GjVMwHmcAPICO7GTIg4949Vg==
X-Google-Smtp-Source: APXvYqx1aiYm3GjbV4Zc1twXOsn5/jFoW0ABhFhFh6hC2NxEr8Lhu1ifoi0Uu6hj4ytUaBUlaQGIN7+esYXiZuGJcj0=
X-Received: by 2002:a05:620a:1661:: with SMTP id d1mr4972044qko.192.1565120660273; Tue, 06 Aug 2019 12:44:20 -0700 (PDT)
MIME-Version: 1.0
From: Warren Kumari <warren@kumari.net>
Date: Tue, 6 Aug 2019 15:43:43 -0400
Message-ID: <CAHw9_iKpTqn+PEYxHnZoYLi=JtyFwYNFw-0=NKVn0i2Gbhvf9Q@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/djDc4Hl_1HfHCKVgOR6-vWy5H4U>
Subject: [DNSOP] Please review and provide feedback -- draft-stw-6761ext
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Aug 2019 19:44:24 -0000

Hi there,

It's time again for everyone's favorite topic -- Special Use Domain Names!

Back in October 2015 the IETF approved RFC7686 - 'The ".onion"
Special-Use Domain Name' -- those who were involved no doubt remember
that it was a really long and frustrating set of discussions, and we
determined that there is much broken in this process.

To job people's memory, Jari penned a nice summary here -
https://www.ietf.org/blog/onion/ :
"Some contention arose during the processing of the document in the
working group. There also was some discussion about needing to clarify
or adjust RFC 6761 before making any additions.
However, subsequent to this action, the IESG believes RFC 6761 needs
action, and substantial community input. It needs to be open for
review and modification because the current process is unscalable.
Several other names had also been submitted for consideration as
special names, and the RFC may not give adequate guidance about how
when names should be identified as special names. Special names should
also be, as the name implies – special and rare. The DNSOP working
group is chartered to address this RFC 6761 review."

The IESG tasked DNSOP with providing better guidance on how to handle
future requests to reserve names under the RFC6761 process[0]. As part
of that we wrote RFC8244 - "Special-Use Domain Names Problem
Statement", which "should be considered required reading for IETF
participants who wish to express an informed opinion on the topic of
Special-Use Domain Names.".  RFC8244 "presents a list, intended to be
comprehensive, of the problems that have since been identified", but
we ran out of steam without actually *solving* the issues.

Later (April 2016) RFC7788 - "Home Networking Control Protocol" was
published which included "A network-wide  zone is appended to all
single labels or unqualified zones in order to qualify them. ".home"
is the default; ..." - this caused much excitement and was updated by
RFC8375 - "Special-Use Domain 'home.arpa.'" which says to use
home.arpa instead of .home.
This was helped by the IAB statement -

This helps, but still doesn't solve many of the issues with RFC6761
style reservations, and wouldn't have really solved the .onion case if
it came along now - the IETF, and the IESG would still be in the
sticky position of how to evaluate if .onion should be placed in the
SUDN registry.

Suzanne has a document which I'd appreciate review and discussion of
-- "Guidelines for Use of the Special Use Names Registry"
As Stephane pointed out, this doesn't solve for issues *outside* the
IETF, but it does (hopefully) "define guidelines for the IESG and the
IETF community on the interpretation of RFC 6761 and the use of the
special use names registry."

I know that people are tired of this whole topic, but I'd really
appreciate some more of your time reviewing and providing feedback on
this topic; this issue isn't going to go away...

As Suzanne is one chairs, she will not be participating in any of the
consensus calls, etc - Benno and Tim can handle that (this is obvious,
but Suzanne asked me to mention it for completeness).

[0]: There is lore that the IESG actually halted reservations under
the 6761 process, but that doesn't seem to be the case, or, if it is,
I cannot find a reference; if there is anything saying so, can someone
please send a link?

I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.