IETF Logo Mail Archive

Re: [DNSOP] [Ext] Re: [Doh] Alternate proposal for transport indication in draft-ietf-dnsop-dns-wireformat-http

Ted Lemon <mellon@fugue.com> Wed, 04 April 2018 15:41 UTC

Return-Path: <mellon@fugue.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 EADC712DA0A for <dnsop@ietfa.amsl.com>; Wed, 4 Apr 2018 08:41:32 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 WjwNPX5B5L56 for <dnsop@ietfa.amsl.com>; Wed, 4 Apr 2018 08:41:30 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F0112DA28 for <dnsop@ietf.org>; Wed, 4 Apr 2018 08:41:30 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id d3so20222114qth.8 for <dnsop@ietf.org>; Wed, 04 Apr 2018 08:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=bP3MjKhOu7OyviUKcFjYDmcSPXFJXdhNxWG0JPQaMPc=; b=nxDptREOA/Au0MnCxc7nMmPDTKBw9oX0RzEN1Ff0omw/WNInsjNkQPzNn0+m3dppVy iwXhjSmkhs5HmFvCDeyzupwu5sFTYQ2pUBh+5MfG1pwA4L9wZIiRxpAQ9NuJj4exy96o Rb6NGVAvX3TG9cS4TqfSLrdNAtMGYYtAaL0RGrrC1KMF0dmZCZ+8so3e7jpKMr/7IaHe /3Yv+2StdprdMtTfp62Dpvvelgu2AU8M8vLorAhjBdkGPxcmfI8zcVZHe/F178kLTueK x/D0KAiSoTWCnWdqLvmEbjnfQnLcDLRbv1bWKTRrz93YQE1oa4NkWDEgkTxUDAaOOQE7 j8ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=bP3MjKhOu7OyviUKcFjYDmcSPXFJXdhNxWG0JPQaMPc=; b=fjMioD3QAihtbskxc4+G6OjL74R2TZ6kzguCYRqYBVnI6xX3mUY3Tqih82TVFdTUQV 8jxmB6qWnczwKeZlLjshR0Cmy9c2Hs2prOPgCC+f+fXxqCTtwNpzRKQR1htUNVDiQ9gl p5+JDl3vBnwBxWJZXEnb1fRi2mRXLO68y5jtY/m15/KoPgHcz200SbcQNPpNwd30K8zX nwBOPTAz6OKslRdgFdXI2NMmRt5rM0I1o9SBCujV4Dq4SMm4g/tIn31QY0TQTGFCghh0 tiLI+IiNUHsYGsnEGl1o32sGcGjTamtwRC+43sCvFx/CIYZfB4Zcbk4fiE162kAKEtbB NLJg==
X-Gm-Message-State: ALQs6tCfJO+o7wG6m5BzA+qsx9qwgYUa9/feCcxMe6KQ3+XwyNgQ7JAa WXlJnDy9t1+OfY7Neg3wc5F8bw==
X-Google-Smtp-Source: AIpwx49vl84n8GMmkwCqMjpVSw8ney7ziXE9KiS5MISDCmV10pZfJ8E7KRwu4YmEWzDSJm3g7L+Gyw==
X-Received: by 10.237.41.194 with SMTP id o60mr26623952qtd.197.1522856489565; Wed, 04 Apr 2018 08:41:29 -0700 (PDT)
Received: from cavall.lan (c-24-60-163-103.hsd1.ma.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id g9sm4354378qti.11.2018.04.04.08.41.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Apr 2018 08:41:29 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <602DF02A-3A85-4B3B-9E11-F7A701BD25B5@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4F70FB23-3124-4F61-B905-E5D5A84404E4"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Wed, 04 Apr 2018 11:41:27 -0400
In-Reply-To: <5AC4F11F.3050009@redbarn.org>
Cc: Ray Bellis <ray@bellis.me.uk>, dnsop@ietf.org, doh@ietf.org
To: Paul Vixie <paul@redbarn.org>
References: <152168039295.5550.9572034766968749020.idtracker@ietfa.amsl.com> <23219.33838.166003.614689@gro.dd.org> <CAAObRX+xF5SwVd3x3iXSWd-A0Kpr_ubbOJzn0yTrSk8pc+tm6Q@mail.gmail.com> <23219.56569.2064.711002@gro.dd.org> <CA+nkc8ANQh2wAr6==eNuM82mbD+E2ELzHGizdqF_sGdY-kkOqg@mail.gmail.com> <5AB3E3B7.3080607@redbarn.org> <69AA6C5D-D348-4956-8A31-FE1EC3A2042E@icann.org> <CABkgnnX2jGY_JpVbqJuQdDVUyVzsuM_2CDg4nppfqQHZQm0F+w@mail.gmail.com> <CAAObRXKHhk51DxNt5uiYB0gunJ=DNde2j9FJSU=Ky2m4Q1UkhQ@mail.gmail.com> <CABkgnnVL0XaUDS-WzDGaN9-kLx9p3x1+UVuWhvx=Zyo5oRos+w@mail.gmail.com> <19BED07A-942E-4A46-93A6-09770083EFF9@icann.org> <CABkgnnX-=n-reO9yjA8a2pHAD+JtoS5wX1w-dXMnDFdt4HXu-g@mail.gmail.com> <23236.18671.182273.977633@gro.dd.org> <28199575-e2e2-6966-fe17-f678f9f397f3@bellis.me.uk> <5AC4C2F7.7050906@redbarn.org> <3630b151-9628-235e-a5b1-c838b777d9d2@bellis.me.uk> <5AC4E70C.7020003@redbarn.org> <A0A55AED-0CB2-478C-913A-DCA678FBAC33@fugue.com> <5AC4F11F.3050009@redbarn.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cHEMc5B2WojHIAmZCu5BzWab7yM>
Subject: Re: [DNSOP] [Ext] Re: [Doh] Alternate proposal for transport indication in draft-ietf-dnsop-dns-wireformat-http
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 04 Apr 2018 15:41:33 -0000

On Apr 4, 2018, at 11:37 AM, Paul Vixie <paul@redbarn.org> wrote:
> there's code that implements this. there are people using it. there will be more of both. a standard will mean greater interoperability.

Why was the code written?   Why are they using this?   What is it about this solution that makes it preferable, for their use case, to a smart proxy that is itself a full-service resolver and thus shouldn't tunnel information about the query transport?

Given Bert's talk on camels, I think these are questions that are worth asking, and the answer shouldn't be "because."

v2.23.0 | Report a Bug | By Email