Re: [DNSOP] Multiplexing DNS & HTTP over TLS

"John Levine" <johnl@taugh.com> Thu, 14 February 2019 17:22 UTC

Return-Path: <johnl@iecc.com>
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 D909A13104F for <dnsop@ietfa.amsl.com>; Thu, 14 Feb 2019 09:22:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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.001, 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=K7BsFAdZ; dkim=pass (1536-bit key) header.d=taugh.com header.b=Mprn8oYF
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 uoSkwcp9IBzS for <dnsop@ietfa.amsl.com>; Thu, 14 Feb 2019 09:22:41 -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 D9974130E2F for <dnsop@ietf.org>; Thu, 14 Feb 2019 09:22:40 -0800 (PST)
Received: (qmail 39885 invoked from network); 14 Feb 2019 17:22:38 -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=9bca.5c65a3de.k1902; bh=4a78j/4ocw7HV1nVgqdKm76rOEfno4ohU11l0FAyahM=; b=K7BsFAdZa865sFmNQl9A1CGHkrY/VbTqDyhqEWEhEI1v9dsJoc1vJDy2a8LU9DJvd4z7wbPP1GNVOPtbaa5mFpk2bFAO6Wky8jXD+Q6k0s7PnpNt4aAkCxjgSU8XpcTWznt+1vjocO0CWkYkB2oiNcvl0Mk2KcM+Yv2dW0ueFYsDclYt91UCqdkn1Gyr0mz2NSszErJZmYPw8q5eHIhN6DlGf29IT8ftPm00of6UK8+nKmNmeDPR5vEY8YZPlp8o
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=9bca.5c65a3de.k1902; bh=4a78j/4ocw7HV1nVgqdKm76rOEfno4ohU11l0FAyahM=; b=Mprn8oYFGZV98PlyBsVXb418Bd3taVU2Op0lZt0eFkymrF+4HI4hRL4LF1zGK/vTCqbOophx/tlpJEEHjRPNaP0Nn3BoLl3YgvIzbtOIDZ2KFvaZqKjuAaGPOQZysE7Bgm8qdszn5H8EglUnSRYPJODcC6aCZ8YiWTybnFiZL/7L2uyMlv6FkdVIXS500FX8U0oStUI4CnDW/estYCPnWHiM2vmWQ41h3mx17rJO4QJxAm5hCCE1oX77U2QJ5/k9
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; 14 Feb 2019 17:22:38 -0000
Received: by ary.qy (Postfix, from userid 501) id 1DD80200E503FE; Thu, 14 Feb 2019 12:22:37 -0500 (EST)
Date: 14 Feb 2019 12:22:37 -0500
Message-Id: <20190214172238.1DD80200E503FE@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Cc: shane@time-travellers.org
In-Reply-To: <9a7b4bc4-018a-9f8c-d3fd-2428356d6605@time-travellers.org>
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/dnsop/a_UZ9oq6TtET9jL5V23Www0bw9c>
Subject: Re: [DNSOP] Multiplexing DNS & HTTP over TLS
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: Thu, 14 Feb 2019 17:22:43 -0000

In article <9a7b4bc4-018a-9f8c-d3fd-2428356d6605@time-travellers.org>; you write:
>I think that HTTP/2 preserves the initial handshake of HTTP/1.1.

Seems to me you could make it work using SNI, so long as the name you
use for the web and DNS servers are different.  I realize this makes
it more sniffable, but maybe that's less bad than some of the
alternatives.