Re: [DNSOP] Verifying TLD operator authorisation

Nick Johnson <nick@ethereum.org> Fri, 14 June 2019 02:57 UTC

Return-Path: <nick@ethereum.org>
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 AE3EC120122 for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2019 19:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level:
X-Spam-Status: No, score=-1.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=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=ethereum.org
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 uUAgCzMuHpvY for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2019 19:57:03 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 6755512003E for <dnsop@ietf.org>; Thu, 13 Jun 2019 19:57:03 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id k21so1268262edq.3 for <dnsop@ietf.org>; Thu, 13 Jun 2019 19:57:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ethereum.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2HI9RrgrNaBx6GZEEoynW98saAJY2cvokZHFiveM/9s=; b=IRvy3Dfwo4pHFZn62pRq9BoSc8C48rJv2f7I2jI8jHSIfPcnwot7hnCivI615eZj1w duXCR/U8Xh8gRfjp+UEOq1xyXBqwDqsmun2evC+xBwRjfJsfyVYUS4s37i6LKNNDgXQo RUJL/zvlekDUNkIuY/FjfWLKwMn/TceNbh8dw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2HI9RrgrNaBx6GZEEoynW98saAJY2cvokZHFiveM/9s=; b=uS7vvJRozhWMPWMSPmNaRbOZHmJPL+EyJIHAUhq/jaSRXnjOrCQQ2kDlusI0YQG8y0 AoYIShqcPnPiMsNvI+a+RfZUUb2g6FGkIu3UOOgQqe4Gg6oiTS9jCL9wRIWv+y4fFhgE 9wVLyRA69rWVSrjhP1yQjDf+W39jtaLdGQVlFMbVj73EWojQt6jFxJ+5mLSkY/XbJpDx oLmFplLLIy4JS0QcZlkNFi1kOK5m/+/EBioMd5OBs6QZVie0aBT9FiFLS+DbmDEiDJ8A NseTH6uXMrFb1LAIP+WlSVlQ6bDNJMk/fXbNvLtJirK9H3/5C9xR5zxV5m3BE586Wh3p D5fw==
X-Gm-Message-State: APjAAAXu7ADKGZ2iGoT7xvPPZyu46YO5WYcdFrMYsD61FbmmK/1Ux0kW qu5i0taz9BTANwZK3vDomoNYPFxe/JAvA43sFHgW3A==
X-Google-Smtp-Source: APXvYqxfgSqL0R0KoxOvV95sjImOMNPfh2TiXimBDTfghUPdysv4fmpPPXPIKyQ/ycIbNsqMz7wy0mSmVxU4pEwNghQ=
X-Received: by 2002:a17:906:db:: with SMTP id 27mr22651934eji.153.1560481021940; Thu, 13 Jun 2019 19:57:01 -0700 (PDT)
MIME-Version: 1.0
References: <CAFz7pMvkQUz78Qow03RsFKHof3nrnGu3BUwUP0zstWgVtP3Msw@mail.gmail.com> <945F9411-C904-4CFF-BF67-4808447ED787@nic.br>
In-Reply-To: <945F9411-C904-4CFF-BF67-4808447ED787@nic.br>
From: Nick Johnson <nick@ethereum.org>
Date: Fri, 14 Jun 2019 14:56:49 +1200
Message-ID: <CAFz7pMuc7sZ7Mb=EmQZ-PwsGHmfvNkpFuGU5+dyjiXqtCvUDVQ@mail.gmail.com>
To: Rubens Kuhl <rubensk@nic.br>
Cc: dnsop@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fde852058b3fccbe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bFHS8qiWv-fNCkabuNzgeBJE99s>
Subject: Re: [DNSOP] Verifying TLD operator authorisation
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, 14 Jun 2019 02:57:06 -0000

On Fri, Jun 14, 2019 at 2:51 PM Rubens Kuhl <rubensk@nic.br> wrote:

>
>
> On 13 Jun 2019, at 23:18, Nick Johnson <nick=40ethereum.org@dmarc.ietf.org>
> wrote:
>
> I'm working on a system that needs to authenticate a TLD owner/operator in
> order to take specific actions. We had intended to handle this by requiring
> them to publish a token in a TXT record under a subdomain of nic.tld, but
> it's been brought to our attention that we can't rely on nic.tld being
> owned by the TLD operators - this is only a reserved domain on ICANN
> new-gTLDs, not on ccTLDs or older gTLDs.
>
> An alternative is to require a message signed by the TLD's DNSSEC zone
> signing key, but I'm uncertain whether it's practical for TLD operators to
> sign arbitrary messages using their keys.
>
> Are there domains that are globally reserved for the operator across all
> TLDs? If not, does anyone have any recommendations on an alternative
> authorisation or authentication mechanism?
>
>
> All TLDs have admin and tech contacts published at
> https://www.iana.org/domains/root/db/[TLD].html (or port-43 WHOIS if you
> prefer) ; send e-mail to both of them, both need to be clicked to confirm
> TLD ownership.
> After that, use whatever mutual authentication system you feel like using.
>

That would work, but we'd rather use a mechanism that can be publicly
verified by anyone.

-Nick


>
>
> Rubens
>
>
>