IETF Logo Mail Archive

Re: [dns-privacy] NS names, was re-evaluation of the draft, was Re: [Fwd: New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt]

John Levine <johnl@taugh.com> Tue, 09 June 2020 18:31 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4183A0CD5 for <dns-privacy@ietfa.amsl.com>; Tue, 9 Jun 2020 11:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=eiQiMMAD; dkim=pass (1536-bit key) header.d=taugh.com header.b=U6Napgpa
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 Irh1cXAnaVlX for <dns-privacy@ietfa.amsl.com>; Tue, 9 Jun 2020 11:31:23 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 487D33A0CD4 for <dns-privacy@ietf.org>; Tue, 9 Jun 2020 11:31:23 -0700 (PDT)
Received: (qmail 83603 invoked from network); 9 Jun 2020 18:31:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1468e.5edfd57a.k2006; bh=kFIzvu37S5uu+JMe8CmZnP4w6NLleeK26R5fELLmM08=; b=eiQiMMADUgsACfu/20w/pVBeK6AEDUqVlZm4Roplkj3HPpX2GQ8+QpLIHLr7aI4mbqXuyCpuBO05zkkp+ERGY1iBpJ18QdTaIbuAetTM6Yr1FYWX0VGEQnlxIRzkSv01CiLLwh0PAGZSt65RWYx9/RexPsPh3mPcQLj9HWKyv1HjTU0FToNu+JLk7Mel1LTNrVGhR0gfrX6RBz5Q6DL+96hpYh4XFQBFl6AcCLcPsNepvkZAOfhXBXlLkjAmgly4
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1468e.5edfd57a.k2006; bh=kFIzvu37S5uu+JMe8CmZnP4w6NLleeK26R5fELLmM08=; b=U6Napgpap0zkr6KAWDEv4mzi8omwtjWsQzAN4SFdCTgmTns0e2HYhN2Tkt1f1zB0Qz6jRuqvtW0zyBqLQaQx12YDfoyOoZWJf+/prnRnonnjr08h9FoR4LSMpEZ1SAeyiK8BK2QWbLA4KjXJI84eYyNjOYxPqS6LsP01GpQqhjP/EVR44+U+trm7aLTJt78P6vsuK2aeYqwZzUOVgVHoesbd9zxYjlQ7ChzFKtAwR3Zk6hr9x/YRbdBT8HmjFlg4
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 09 Jun 2020 18:31:21 -0000
Received: by ary.qy (Postfix, from userid 501) id 203851A5666F; Tue, 9 Jun 2020 14:31:22 -0400 (EDT)
Date: Tue, 09 Jun 2020 14:31:22 -0400
Message-Id: <20200609183122.203851A5666F@ary.qy>
From: John Levine <johnl@taugh.com>
To: dns-privacy@ietf.org
Cc: shuque@gmail.com
In-Reply-To: <CAHPuVdUoZVecj5Jfd6NxyJ-cRhTJTS1N8vcC5pC3uWQECLOCnQ@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/v9sIbpmK4o-HKb3oI0BLdaaW1fs>
Subject: Re: [dns-privacy] NS names, was re-evaluation of the draft, was Re: [Fwd: New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt]
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2020 18:31:25 -0000

In article <CAHPuVdUoZVecj5Jfd6NxyJ-cRhTJTS1N8vcC5pC3uWQECLOCnQ@mail.gmail.com> you write:
>Well, the client could just use the zone name as the SNI, no? You can assign
>certificates with the same name but different keys to each of the
>nameservers.

That sounds quite painful for servers that serve hundreds or thousands of zones.

I am assuming these would be self-signed certs. If you want them
signed there's an additional bootstrap problem since the CA everyone
uses, Let's Encrypt, needs working DNS to sign a cert.

v2.23.0 | Report a Bug | By Email