Re: [dns-privacy] ADoT signalling

"John Levine" <johnl@taugh.com> Tue, 05 November 2019 18:51 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 DECB7120142 for <dns-privacy@ietfa.amsl.com>; Tue, 5 Nov 2019 10:51:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=f/TF7xzL; dkim=pass (1536-bit key) header.d=taugh.com header.b=d0QHVx60
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 jZF5oDwO88iq for <dns-privacy@ietfa.amsl.com>; Tue, 5 Nov 2019 10:51:47 -0800 (PST)
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 ABD4D12013F for <dns-privacy@ietf.org>; Tue, 5 Nov 2019 10:51:47 -0800 (PST)
Received: (qmail 64373 invoked from network); 5 Nov 2019 18:51:46 -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=fb72.5dc1c4c2.k1911; i=printer-iecc.com@submit.iecc.com; bh=2cFBoWY47/ePORi0sAVu3Q1eh/eR1TvxSKFyPD4uxsk=; b=f/TF7xzLNKcR4zaWz3h4TNQSVN9sQYF/JGYQFRyRY26bQrwpyroUNeQNiRG1uREgbjzO7qmqZkG3gtDZrf5LNtOQ+fTBAql5PNs3sorc7Rb+GVirso6Syv3U8KnRgakihtmYqcLovm9gyHbdpjR4rjZ8Z2eqhhEAOI+gMaddoqgox6fc+G0WCkPvNzmBIueafNaDtqoXu8RFK6ra7icIiBzgeGmhCZX+Qlb/3dfzcKZ5r0iwtABaa9+PgLs7sW7H
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=fb72.5dc1c4c2.k1911; olt=printer-iecc.com@submit.iecc.com; bh=2cFBoWY47/ePORi0sAVu3Q1eh/eR1TvxSKFyPD4uxsk=; b=d0QHVx60mqxN94GyWUzg8J49LhZJmX2Nrdfo88D+k2oJh+P3DDx5iK/SlIh8+VEPbPHXDhXmeQQftEVNwU3zpXeAqZj2LH5h3SHdSvqh80sUP9M5OftgfyTYl1WGoiDS4+fXSqs3/d8cBx9nT3CbZKaEExBNe9cum8C8ZurZ41CVajjE2eACpAV5OoMK7n8SyI8634e/sJWM1D1ZR0tBAqSbzkZMlfPNEYxcKAE4UCMZzqhTBJ/MFVARK6i5tzl/
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 05 Nov 2019 18:51:45 -0000
Received: by ary.local (Postfix, from userid 501) id 3C3E3E6A73C; Tue, 5 Nov 2019 13:51:45 -0500 (EST)
Date: Tue, 05 Nov 2019 13:51:45 -0500
Message-Id: <20191105185145.3C3E3E6A73C@ary.local>
From: John Levine <johnl@taugh.com>
To: dns-privacy@ietf.org
Cc: huitema@huitema.net
In-Reply-To: <711d51d8-8786-6bdd-b95f-d968781b09db@huitema.net>
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/8aHiQZGhTIG4D1IRhKUhDiHmJiE>
Subject: Re: [dns-privacy] ADoT signalling
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, 05 Nov 2019 18:51:49 -0000

In article <711d51d8-8786-6bdd-b95f-d968781b09db@huitema.net> you write:
>Note that port 853 is a convention. Servers could trivially run multiple
>services over port 443, and demux based on the ALPN. I suppose that if
>we see a lot blockage of port 853, servers will just do that -- run on
>port 443, demux based on ALPN="DoT"...

If you're going to do that, it's probably easier to have your client
add https headers and do DoH than to add a DoT switch to the ALPN
code in your web server.

R's,
John