Re: [DNSOP] [rssac] draft-ietf-dnsop-private-use-tld

Fred Baker <> Mon, 12 October 2020 07:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CAFCF3A12F0; Mon, 12 Oct 2020 00:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id orRKxTMxSu-M; Mon, 12 Oct 2020 00:44:25 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6B0BF3A12EE; Mon, 12 Oct 2020 00:44:22 -0700 (PDT)
Received: by with SMTP id o8so8128580pll.4; Mon, 12 Oct 2020 00:44:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dSpXD/23gDmjb1f52ECQPOfkcTxi0VQAnoklQ+mpSsA=; b=WvB9dCsgEeB+IEjuz5p4dl3ut899VBWM24ZujeV2DVK9TYPFrCAaSCS8Q+WD7CgUrI UssYvt7om+Y4vqlusH29aXIfO16CvZVd2p5YvGVCG5F8QCmN3PjqO/kUcWVUjm0Bf6sX gXYQc++gmKfllwqdm5lhhWaoUSa9gER/rmpGAYmG5fCduUVP28oP4LL2EPA1P2ipOyGA aSbmWfaz/wO6bt1RqP2wr/eqwf5NiOrn1OP+NVhnUo0ZEah+faPe1O/UUY9dXhsdxDJM 4nnS2HVKtjsYJFofnLX+EOpRI0MfdmYhNY+iA8IHmndv7ylPtVq0YBGWCF9zBZsRCx7i GRAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dSpXD/23gDmjb1f52ECQPOfkcTxi0VQAnoklQ+mpSsA=; b=UtrSbd1Kw4ZcZqmjmgdsUDl8mQw6PZz3bC6Q2j0jSK9zaBE053dnh1c8Jr/gAOc8yt 4ZWmuchA3XDkiGLJJN9ww2yUx7aTOMkhmW2QVv04evv+hRktj+QazsuIf/EI6x8yIv7D DD428oVV+cs5G31RMnBts40visoCDtG3IH3qyNOXiOsB6k335tJBjSkg6Ge1Bfmvo9ct +fBhWFW4L/7wTY/QiF5g37goED52TStbFoFV2f3SEU/UEAlvg9zM05KGYPqiL+rp1+pr KmJbJ8+VSSN/lEOWpJe6U7FIWbD4PQ5itnBw5P4FvIvcj5I1kuFGTYqsUAODajezJrH9 Gw0Q==
X-Gm-Message-State: AOAM530RVzjq2PgnrOh4xPVJslLfWjocFjBujE+rUHRpYuBLb0Dc2I86 LWeGCfyJS0qh6OdDUj/2rvE=
X-Google-Smtp-Source: ABdhPJxI+RMmKSPNYrYEo9WT9EkyFKUjDBklgXmUHmjYh44X1Obnm9EApSAmy+ha/Kx759HoonS0LA==
X-Received: by 2002:a17:902:b192:b029:d2:f08:f85a with SMTP id s18-20020a170902b192b02900d20f08f85amr22400585plr.49.1602488661493; Mon, 12 Oct 2020 00:44:21 -0700 (PDT)
Received: from ?IPv6:2600:8802:5800:16d0::1283? ([2600:8802:5800:16d0::1283]) by with ESMTPSA id m13sm20297862pfd.65.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Oct 2020 00:44:21 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
From: Fred Baker <>
In-Reply-To: <>
Date: Mon, 12 Oct 2020 00:44:19 -0700
Cc: dnsop <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Daniel Migault <>,
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [DNSOP] [rssac] draft-ietf-dnsop-private-use-tld
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 12 Oct 2020 07:44:27 -0000

> On Oct 8, 2020, at 7:08 AM, Daniel Migault via RSSAC <> wrote:
> Just to let you know that the draft for the private tld has been adopted as WG document. 
> Yours, 
> Daniel

Thanks, Daniel.

Joe and Roy, I'm trying to figure out how you intend these names to be managed and used. In your draft, you opine that having some form of private tld may be useful, and it may be. You apparently don't intend them to be announced in the root zone (or any other zone), and note that there is nothing that precludes them being formally defined and published from the root in the future, invalidating all extant uses of any such name without warning or review.

That seems a little precarious.

How do you plan to manage them?