Re: [Doh] re original_transport indicator

Martin Thomson <> Sat, 07 April 2018 04:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 401A2126FB3; Fri, 6 Apr 2018 21:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id A6zZhtwbvEP6; Fri, 6 Apr 2018 21:30:06 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4003:c0f::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 68BA1124319; Fri, 6 Apr 2018 21:30:06 -0700 (PDT)
Received: by with SMTP id f47-v6so3343040oth.2; Fri, 06 Apr 2018 21:30:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qkaswSmp4s3rA3XelMuELRMhPj590W3h0YOb7xvlvYw=; b=GBLrQXnZQpYI+9DMhloqVBLDIiwW/Pg2OWDb+91Xmsa7LYRKDna1iiEGa02UAUW18U FVUmx0YnxtKmYsHOcF+8vHYe6CSOyzYVo6yAHoyj7bd/fJAnewvQqyPcdvEbT4wZrWtY CC/G/RBaV3zEiT8PqQbTIcJgexTzlNUuGuRYSI4iXt/q0x2t9aq3yay3S6ihTbdimW4X 4HigxCaHqrQaZdu5XQhnIdOY48ipxisKIxUkoOHeDP4/r87LKDiwY+X7RMZ2Tmn+VuM7 5OznMCgmN66YKC8GzfRPjoZELba+3ItyIHIUrqhAkpNn/TYNYZ65CyyLfuclL35CdnKy JNvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qkaswSmp4s3rA3XelMuELRMhPj590W3h0YOb7xvlvYw=; b=rse/Am/x5ss3VBxyr39XMcQLSS+r0ByijVpSguU5uGHCWNzwJvyFrhrPxL7SKd7IYx DkowzchgQprKRtocHHM1A1F+LroMc2RRMYd3+mLbLA3cikGJHHsV+XGojRczz2594Fg8 6bXhv1L6sOFesmuOUwoZ0Fqvjg7ql9SBZwLXVINpVmXYj9WW/pBwMWn1d91E5advRI/9 HHbkjB7w8UrRWv8Gc6DitqbGlCnpUk1u+tQlWoEWNooEi0oDRfO7Un6zAeMhIeExfBQE xSqXtMawrBi9t2IxoSzfYc06BC/2OmjiFj8dBe9gF5yBOqmTZ1cG9iYCmEkLr1emCTlV w35A==
X-Gm-Message-State: ALQs6tCu65FyDiZ5pU+IWertSAFkUfTK7HjPGzq7ZG7wqZb25gDKYNUP RJLUBBJsPoTuO0g66gccxuFqE0AW4rZ2aFpAAI0=
X-Google-Smtp-Source: AIpwx4+JkG9MMRM9kLSssJtWyZSmTY6JXhQd/GrGW8Tu9lGUf77Fb0qKFs1wIneoCsL7wWvUs7YzqmUZ0xuEAEHMT5Q=
X-Received: by 2002:a9d:1311:: with SMTP id f17-v6mr5616616ote.15.1523075405653; Fri, 06 Apr 2018 21:30:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:ac7:0:0:0:0:0 with HTTP; Fri, 6 Apr 2018 21:30:05 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
From: Martin Thomson <>
Date: Sat, 7 Apr 2018 14:30:05 +1000
Message-ID: <>
To: Paul Vixie <>
Cc: Patrick McManus <>, dnsop <>, DoH WG <>, Ted Lemon <>, Ray Bellis <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Doh] re original_transport indicator
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 07 Apr 2018 04:30:08 -0000

On Sat, Apr 7, 2018 at 9:29 AM, Paul Vixie <>; wrote:
> my original design added an http header, which was seen as even worse.
> someone suggested adding to the content-type, and i went along with it even
> though there is no difference in actual type of actual content.

A header field isn't all bad.  At least from my perspective, anyway.
That said, it is true that adding to the content is a better choice.
I appreciate that this isn't a great fit in this case.

> i am generally supportive of this approach; in fact i wish i'd thought of
> it. the specifics will be different, as in:
> /proxy_dns?proto=tcp
> /proxy_dns?proto=udp

.../request{?dns}{?proto} is the way you would write that.

> i object, as before, to "dns-udpwireformat" as a name. these are dns
> messages, which when carried by udp are raw, and when carried in tcp are
> preceded by a two-octet length indicator for framing of multiple messages
> sharing the same stream. so, the string to be registered should be
> "dns-message".

I agree with this principle, and have expressed similar concerns with
the name.  However, I just checked the media type registry [1] and I
think that a better choice is message/dns.  Just like message/http and