IETF Logo Mail Archive

Re: [DNSOP] Verifying TLD operator authorisation

Rubens Kuhl <rubensk@nic.br> Fri, 14 June 2019 03:02 UTC

Return-Path: <rubensk@nic.br>
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 255111200B8 for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2019 20:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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_MED=-2.3, SPF_PASS=-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=nic.br
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 C3f1HUn57DHf for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2019 20:02:20 -0700 (PDT)
Received: from mail.nic.br (mail.nic.br [200.160.4.5]) (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 7C5E112006D for <dnsop@ietf.org>; Thu, 13 Jun 2019 20:02:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.nic.br (Postfix) with ESMTP id D42DD16B8FE; Fri, 14 Jun 2019 00:02:17 -0300 (-03)
X-Virus-Scanned: Debian amavisd-new at mail.nic.br
Authentication-Results: mail.nic.br (amavisd-new); dkim=pass (1024-bit key) header.d=nic.br
Received: from mail.nic.br ([127.0.0.1]) by localhost (mail.nic.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4FWPvVK9xdTF; Fri, 14 Jun 2019 00:02:15 -0300 (-03)
Received: from [IPv6:2804:431:9701:7e6c:bde8:4e13:d4ac:d139] (unknown [IPv6:2804:431:9701:7e6c:bde8:4e13:d4ac:d139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rubensk@nic.br) by mail.nic.br (Postfix) with ESMTPSA id A94C716B8F5; Fri, 14 Jun 2019 00:02:15 -0300 (-03)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.br; s=dkim; t=1560481335; bh=pxI2IrwEIZ4abKFfje8cq0lSc/32X2LeCTMJzHIgCTA=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=pjkyzXrk8aKr9TLIEP0CZt38+cxkGM55eKC3nFrkWJl2cw0QlABAJHBMM8TtSI6Mp c7KHsPEJgNCeoEGW7kC8MGpE4aibhv0hY8xfVVL5DdgCwBj7Wq4VqEQRqdW6ae6meQ vPiapLyh9ExbTJh5it8MrkTHQRKhHYLdc0FbGVXQ=
From: Rubens Kuhl <rubensk@nic.br>
Message-Id: <67DE7C5B-94BD-45BB-AFDB-D257696F3A82@nic.br>
Content-Type: multipart/signed; boundary="Apple-Mail=_B84EFC45-9694-4DAD-9841-7F15B80746D5"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 14 Jun 2019 00:02:15 -0300
In-Reply-To: <CAFz7pMuc7sZ7Mb=EmQZ-PwsGHmfvNkpFuGU5+dyjiXqtCvUDVQ@mail.gmail.com>
Cc: dnsop@ietf.org
To: Nick Johnson <nick@ethereum.org>
References: <CAFz7pMvkQUz78Qow03RsFKHof3nrnGu3BUwUP0zstWgVtP3Msw@mail.gmail.com> <945F9411-C904-4CFF-BF67-4808447ED787@nic.br> <CAFz7pMuc7sZ7Mb=EmQZ-PwsGHmfvNkpFuGU5+dyjiXqtCvUDVQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
DMARC-Filter: OpenDMARC Filter v1.3.1 mail.nic.br A94C716B8F5
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2X1pLoPFnL6xqXEN4UCFp4ohJzU>
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 03:02:23 -0000


> On 13 Jun 2019, at 23:56, Nick Johnson <nick@ethereum.org> wrote:
> 
> On Fri, Jun 14, 2019 at 2:51 PM Rubens Kuhl <rubensk@nic.br <mailto:rubensk@nic.br>> wrote:
> 
> 
>> On 13 Jun 2019, at 23:18, Nick Johnson <nick=40ethereum.org@dmarc.ietf.org <mailto: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 <https://www.iana.org/domains/root/db/%5BTLD%5D.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.

Like sending an e-mail to a mailman list archive after the process is completed ?


Rubens

v2.23.0 | Report a Bug | By Email