[DNSOP] Moving forward on draft-ietf-dnsop-private-tld

Roy Arends <roy@dnss.ec> Fri, 30 July 2021 18:20 UTC

Return-Path: <roy@dnss.ec>
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 B97E53A095E for <dnsop@ietfa.amsl.com>; Fri, 30 Jul 2021 11:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dnss.ec
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 oAzd5cT9d7AU for <dnsop@ietfa.amsl.com>; Fri, 30 Jul 2021 11:20:50 -0700 (PDT)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 C4FFC3A095D for <dnsop@ietf.org>; Fri, 30 Jul 2021 11:20:50 -0700 (PDT)
Received: by mail-ot1-x331.google.com with SMTP id c2-20020a0568303482b029048bcf4c6bd9so10450170otu.8 for <dnsop@ietf.org>; Fri, 30 Jul 2021 11:20:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dnss.ec; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=lyAEK72V3s1cdaZhp0MzxzPBntvsS8kM9k14jEpyvxk=; b=L4A6BES9l8XyJnLFTVxCBLmn1R0QICNEROdmZ2mLwgoR1xg0Qgp7JvVwPuy42EEoSv KEhT/YNJdl/zN/6NcKS/+smEENNmlOGH/Ofq4oz1xUaqvWS0BZN1zAopG0en4FD339+9 kw1XzdTCbx5HCpvZfSCEDURcfis+A6tNlr2Rg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=lyAEK72V3s1cdaZhp0MzxzPBntvsS8kM9k14jEpyvxk=; b=pUgjs/eTeSdpravg/IpMABX3IZydDojBbMWzlW/543lHATDBo0mJYhu5CwqjKmf8TI XK1Ztw6lEembWcExFDTZLwuGbR6J0d5aTLbAGf0xxXwp/e569JsFRdlR1iNEJayZ0b2g ACSWDV8AmMyt9B9P1Af4z7RhPM5a9qx5Rv+tktGIGJ4I98FYs+RqFpGCvnIpfkzGSMmC n7TcJspSiRzDz3ihy+4MgszQXotuABA3aLFk6uzpnsLalttF/WtT3QGz/1NNu0YB/TA4 bBZAHYcrmlNuoOd3D/uVle3apfny2Ltm7vDfdpq9u3+OPgCR63aoioQYrBqIHfgZ4CBP X+HQ==
X-Gm-Message-State: AOAM530HMGNstpUXI/Sa4d9A1iR9Rlsae/WUqBz5E1DVki/M84l6OARu 6Rwo4nMDfYQ+qTUSKpMcmKLix1VBdA6asA==
X-Google-Smtp-Source: ABdhPJzwJz0i1kR9Cw80cxFERzaHc6Tb99NtyLsQbundgmhaR2ob3UHa9qqF7Ybpgc/6Scab5XOd5Q==
X-Received: by 2002:a05:6830:1b7a:: with SMTP id d26mr3015413ote.218.1627669246757; Fri, 30 Jul 2021 11:20:46 -0700 (PDT)
Received: from [192.168.0.51] (cpc69046-oxfd25-2-0-cust568.4-3.cable.virginm.net. [81.109.86.57]) by smtp.gmail.com with ESMTPSA id f16sm410165oiw.29.2021.07.30.11.20.45 for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jul 2021 11:20:46 -0700 (PDT)
From: Roy Arends <roy@dnss.ec>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Message-Id: <E5E151E6-0BC0-44FE-BF7C-6B2ED207894F@dnss.ec>
Date: Fri, 30 Jul 2021 19:20:43 +0100
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Zczf6jEWmCtgnsKh43Gh3rXyfo4>
Subject: [DNSOP] Moving forward on draft-ietf-dnsop-private-tld
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: Fri, 30 Jul 2021 18:20:56 -0000

Dear WG

About 40 years ago, give or take, when Jon Postel planned to use the ISO3166 two character code elements as top level domains representing country names, ISO's TC46 secretariat was contacted (as was requested to users of the ISO3166 standard at the time) and he was told that the standard should not be used for DNS, as the future was in X.500. (Postel wasn’t swayed by the argument, and did what we now refer to as permission-less innovation).

Recently, the ISO was contacted again, and subsequently the WG was again told that the standard wasn’t to be used in this way. It seems that a handful of folks are swayed by the argument and want to use this as guidance for the future of draft-ietf-dnsop-private-tld.

Early on, Joe Abley proposed a way forward that I held off initially: Recognise that User Assigned 3166 code elements are used in various ways, including private networks, that these elements have not been delegated and are known to be used to anchor private namespaces. Do not recommend, promote or reserve anything, no registries. Document potential future pitfalls for using these codes for private namespaces and empower readers to make their own decisions.

I now see that with the current status quo, this might a way forward that both sides of the argument might come together on. Essentially, instead of making the pond safe, we’ll have a warning sign that using the pond is at their own risk.

I hope the WG can come together on this as a way forward. 

Warmly,

Roy