[Doh] DOH server on non-standard ports

Mateusz Jończyk <mat.jonczyk@o2.pl> Wed, 04 April 2018 10:59 UTC

Return-Path: <mat.jonczyk@o2.pl>
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 462BC127241 for <doh@ietfa.amsl.com>; Wed, 4 Apr 2018 03:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 UnmRIxG-Orr1 for <doh@ietfa.amsl.com>; Wed, 4 Apr 2018 03:59:56 -0700 (PDT)
Received: from mx-out.tlen.pl (mx-out.tlen.pl [193.222.135.142]) (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 3309B1271FD for <doh@ietf.org>; Wed, 4 Apr 2018 03:59:47 -0700 (PDT)
Received: (wp-smtpd smtp.tlen.pl 27167 invoked from network); 4 Apr 2018 12:59:43 +0200
Received: from acjd214.neoplus.adsl.tpnet.pl (HELO [192.168.1.22]) (mat.jonczyk@o2.pl@[83.10.53.214]) (envelope-sender <mat.jonczyk@o2.pl>) by smtp.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP for <doh@ietf.org>; 4 Apr 2018 12:59:43 +0200
From: =?UTF-8?Q?Mateusz_Jo=c5=84czyk?= <mat.jonczyk@o2.pl>
To: doh@ietf.org
Message-ID: <39301825-be3c-5888-ce99-45caf5ab0857@o2.pl>
Date: Wed, 4 Apr 2018 12:58:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TJFpLYX1goUQ9zaBRflvRPvIsLqJ1V0nt"
X-WP-MailID: f31ae8825e3247362703f4e1a23fd078
X-WP-AV: skaner antywirusowy Poczty o2
X-WP-SPAM: NO 000000A [kTN0]
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/T9KRhPilz2c6z9dYb0chbiktsOs>
Subject: [Doh] DOH server on non-standard ports
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
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, 04 Apr 2018 10:59:58 -0000

Hello,
I think that it may be beneficial to specify that a DOH server MAY work on a
port other than 443 and that the DOH client MUST support accessing DOH servers
on ports other than 443.

I have been thinking about the possibility of adding support for DOH to a home
router. In the future, someone may modify dnsmasq so that it would act as a DOH
server - dnsmasq could then run on this router and provide DOH services.
The port 443 would be already used by the router's management interface which
would probably run as a separate process on this router (as it would be an
entirely different codebase). So dnsmasq would have to provide DOH services on
another port.

Greetings,
Mateusz Jończyk