IETF Logo Mail Archive

Re: [DNSOP] Should we try to work on DNS over HTTP in dnsop?

George Michaelson <ggm@algebras.org> Wed, 23 December 2015 05:13 UTC

Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC841AC3BA for <dnsop@ietfa.amsl.com>; Tue, 22 Dec 2015 21:13:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 itG_kbpxE98d for <dnsop@ietfa.amsl.com>; Tue, 22 Dec 2015 21:13:05 -0800 (PST)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (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 58D7D1A909C for <dnsop@ietf.org>; Tue, 22 Dec 2015 21:13:05 -0800 (PST)
Received: by mail-qg0-x230.google.com with SMTP id o11so70230683qge.2 for <dnsop@ietf.org>; Tue, 22 Dec 2015 21:13:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=x/h8AAivNjPlfVB9Y+J7T753lDGYAwb0zoEZbN/qBBg=; b=HhyNFG47YzmGqy2WxIlNCA/dnSQd+sWQgpj5lDFcUmcvlG0QwUs9WBRcex9er3zSgV WSew1/s0Lk8T8eqD5tXs6TTV2KMHmnIMt5JfKl/V608G8AQClEv1VINsEsQ8lFra77Mj 9BFwEDUEGETM8tym0KmKJqzQeGbwmisR7MDY358xryP4wFuYEpufrvND+bKtx8pwvu+M mydy0Gjue/EN7FGqRhyV+fG1tHEw3XpVd8iGJp8fDlJW0Kj/XPIbHRKsPmSSeg9vN9gB jlQ8sJKyLPMeMuf9DmprFtYbkA+SqvBnmY5fBJTkCAa3POSWZdQFsoCWZNfNEo2q+3y1 gbeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=x/h8AAivNjPlfVB9Y+J7T753lDGYAwb0zoEZbN/qBBg=; b=REuT/dq8lyaHMfImX60nUflNiUSTtk2pCp6Rz8ICdiY9zZ8ay6MgBuOsCFWVvSnFV/ TGrx8Bk+wW6nms22dLCq1sMVwl1C3W2EukLaohR+v9MfNrJB+HwwQgLubKSZ+YbV0OgH S+2mrhc3U30tXEBGk5cnEAu5DgSRRb8gdDUfymkrAv+z4C9bOS2JtqtdvTMWuVhNaSYQ qQVH5+m+PxeE297Y+FoRv6pa17oYB0usD0eoTCjk/yuX5UTusjpHKQwphEQ3H985iBuN DdPUXxUSDvKvfmvLRim4WTn+hDV5J5dtEr+2r6xKIefLOpRKM5ErrORyNC6N/Cf83qhE VN3Q==
X-Gm-Message-State: ALoCoQmsNo5l9VLjpggqhb6TO5GfTP0LIlMHqNYXB6LrufXogMsRm9FUmfuzt97Fi/ZNqiXtvVH5C+yeOgp36Iong3WqxDZZWA==
MIME-Version: 1.0
X-Received: by 10.140.174.68 with SMTP id u65mr40497269qhu.62.1450847584391; Tue, 22 Dec 2015 21:13:04 -0800 (PST)
Received: by 10.55.103.214 with HTTP; Tue, 22 Dec 2015 21:13:04 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:dce6:64b9:baaa:4b48]
In-Reply-To: <4909572.yk9lYxXkhq@linux-85bq.suse>
References: <20151217020754.6915b71c@pallas.home.time-travellers.org> <2858865.LSerpu06UP@linux-85bq.suse> <alpine.LSU.2.00.1512221056460.959@hermes-2.csi.cam.ac.uk> <4909572.yk9lYxXkhq@linux-85bq.suse>
Date: Wed, 23 Dec 2015 15:13:04 +1000
Message-ID: <CAKr6gn2yNB-S7Uk=Sx_=iHUUFQDqRxhrVznRP3GNswkyWvBgxw@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113a5456e435a2052789c6fc"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/aF5Nd40j2XpinkfG9qJU5wV_YI8>
Subject: Re: [DNSOP] Should we try to work on DNS over HTTP in dnsop?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Dec 2015 05:13:07 -0000

I'd be interested in the cache effects. If the TTL is mapped into cache
age, then there is potential for CDN distribution to work more better
gooder.

More for entertainment value, since label compression is totally bogus,
like carrying forward ASCII only standards documents I mean who does that
.. ok sorry But really, if we didn't do label compression, and we did do
UTF-8 instead of punycode, would we still be DNS?

-G

On Wed, Dec 23, 2015 at 1:58 PM, Paul Vixie <paul@redbarn.org> wrote:

> On Tuesday, December 22, 2015 11:00:22 AM Tony Finch wrote:
>
> > Paul Vixie <paul@redbarn.org> wrote:
>
> > > On Monday, December 21, 2015 01:13:10 PM Tony Finch wrote:
>
> > > > The current way to deal with out-of-order responses and head-of-line
>
> > > > blocking in HTTP is HTTP/2.
>
> > >
>
> > > since http/2 is a completely new protocol, i think that's a strange way
>
> > > to say it.
>
> >
>
> > Not completely - it has the same message semantics, they "just" changed
>
> > how the messages are transported.
>
> >
>
> > So another way of phrasing my previous message is that DNS-over-HTTP
> ought
>
> > to be "just" a mapping from DNS messages to HTTP messages.
>
>
>
> i agree. the only specification matter is the transform between message
> formats. there's no reason to talk about transport at all.
>
>
>
> --
>
> P Vixie
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>

v2.23.0 | Report a Bug | By Email