IETF Logo Mail Archive

Re: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh

"Ralf Weber" <dns@fl1ger.de> Wed, 16 January 2019 19:44 UTC

Return-Path: <dns@fl1ger.de>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 714C21310F7 for <doh@ietfa.amsl.com>; Wed, 16 Jan 2019 11:44:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 T-b-0fG1oPIT for <doh@ietfa.amsl.com>; Wed, 16 Jan 2019 11:44:01 -0800 (PST)
Received: from smtp.guxx.net (nyx.guxx.net [85.10.208.173]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFE31310EF for <doh@ietf.org>; Wed, 16 Jan 2019 11:44:00 -0800 (PST)
Received: by nyx.guxx.net (Postfix, from userid 107) id 695F45F4298D; Wed, 16 Jan 2019 20:43:58 +0100 (CET)
Received: from [172.19.153.181] (p4FF53CB0.dip0.t-ipconnect.de [79.245.60.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id A04EE5F40292; Wed, 16 Jan 2019 20:43:57 +0100 (CET)
From: Ralf Weber <dns@fl1ger.de>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: "A. Schulze" <sca@andreasschulze.de>, DoH WG <doh@ietf.org>
Date: Wed, 16 Jan 2019 20:43:55 +0100
X-Mailer: MailMate (1.12.3r5579)
Message-ID: <88CFA2C4-BBE7-402D-ADFF-DE17339305DB@fl1ger.de>
In-Reply-To: <CAHbrMsAB4GaUJXY1VyQVc0QonY9afGUzWdT5znPw+K4M2V=kNQ@mail.gmail.com>
References: <8999D6F3-600E-4F1A-903C-10F8CAA6E4F3@icann.org> <6f2860bd-2a7f-01b5-2ec9-9667d71e3f38@andreasschulze.de> <CAHbrMsAB4GaUJXY1VyQVc0QonY9afGUzWdT5znPw+K4M2V=kNQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/QLZQQBQHNQk0uZ4j6co0414ZS0k>
Subject: Re: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2019 19:44:03 -0000

Moin!

On 16 Jan 2019, at 19:28, Ben Schwartz wrote:

> DNS over TLS already supports a way for clients to upgrade from 
> unencrypted
> DNS, by probing port 853 on the server's IP address.  I presume that's 
> why
> DNS over TLS discovery was not mentioned in this draft.  Is probing 
> port
> 853 sufficient for your use case?
Well the performance characteristics for DNS over UDP and DNS over TLS 
or HTTP are different, so it would be good to have different platforms 
for these.

Also to answer Jim Reid I thought I was answering on dnsop and not doh 
(wasn’t sufficiently caffeinated ;-) which is why I brought up DoT. I 
really don’t care to much which working group does the work as long as 
it is done and I’ll do my best to contribute.

So long
-Ralf
—--
Ralf Weber

v2.23.0 | Report a Bug | By Email