Re: [Doh] meta qtypes

Patrick McManus <pmcmanus@mozilla.com> Mon, 19 March 2018 14:20 UTC

Return-Path: <pmcmanus@mozilla.com>
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 B309412778D for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 07:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level:
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 qVCWTyDuHC2L for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 07:20:55 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id 4030D1270A3 for <doh@ietf.org>; Mon, 19 Mar 2018 07:20:48 -0700 (PDT)
Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) by linode64.ducksong.com (Postfix) with ESMTPSA id A7E4D3A058 for <doh@ietf.org>; Mon, 19 Mar 2018 10:20:47 -0400 (EDT)
Received: by mail-oi0-f51.google.com with SMTP id c12so14419011oic.7 for <doh@ietf.org>; Mon, 19 Mar 2018 07:20:47 -0700 (PDT)
X-Gm-Message-State: AElRT7EDUbiaxoC9qpSSbNaNbLY1eaBDmi20u383QU9dLeZnp4/LgTDn GduHvf3H32aPvczCsWmshNvSc4kjp5x4ieG8EuA=
X-Google-Smtp-Source: AG47ELshGj1veJ70FvR7281kFd+ZRH+LvCDEv68wl9tUM1JepfdHXU+zlXH3Se1WkgbVuRgd1wUAHF/GLOEJoqJyEyQ=
X-Received: by 10.202.3.198 with SMTP id 189mr6683485oid.132.1521469247208; Mon, 19 Mar 2018 07:20:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.66.212 with HTTP; Mon, 19 Mar 2018 07:20:46 -0700 (PDT)
In-Reply-To: <16CD849A-55B3-487C-A370-CA96FF619BC3@bangj.com>
References: <20180318143811.bn5kwr7oqo2ux6qm@miek.nl> <CAOdDvNoNN98zOuPAepS0=0Nt06+UAGV1ZCrxs0J2TzQaVnJz8w@mail.gmail.com> <CAN6NTqwA+Ub22Ajr_RGGh2+32aMMUMcKnPdUrUpkk8zF6TBn1Q@mail.gmail.com> <20180319131134.46hjo2eo757jqe7d@miek.nl> <16CD849A-55B3-487C-A370-CA96FF619BC3@bangj.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Mon, 19 Mar 2018 14:20:46 +0000
X-Gmail-Original-Message-ID: <CAOdDvNqaPbQXknz6XpvgagtQvdDZjtc3WScfiPFUTy50i8h=Yg@mail.gmail.com>
Message-ID: <CAOdDvNqaPbQXknz6XpvgagtQvdDZjtc3WScfiPFUTy50i8h=Yg@mail.gmail.com>
To: Tom Pusateri <pusateri@bangj.com>
Cc: Miek Gieben <miek@miek.nl>, =?UTF-8?B?w5NsYWZ1ciBHdcOwbXVuZHNzb24=?= <olafur@cloudflare.com>, DoH WG <doh@ietf.org>, Patrick McManus <pmcmanus@mozilla.com>
Content-Type: multipart/alternative; boundary="001a11c0463c0446580567c4aa68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/qytdHMk1nZw1Dhc7Ph1YnlcRH_o>
Subject: Re: [Doh] meta qtypes
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: Mon, 19 Mar 2018 14:20:58 -0000

I'm happy to learn more, but it appears to me that DoH is not suitable for
use with session signal because:

1] DSO messages communicate operations within persistent stateful sessions

and 2] The Hypertext Transfer Protocol (HTTP) is a stateless
application-level protocol

The HTTP semantics that DoH uses (i.e. it does not require a particular
usage of a particular HTTP wire protocol - it exists at the method and URI
level of things) don't give you basic properties like a stateful session
layer. For instance, your messages could go out of order or even to
different servers.


On Mon, Mar 19, 2018 at 2:01 PM, Tom Pusateri <pusateri@bangj.com>; wrote:

>
> On Mar 19, 2018, at 1:11 PM, Miek Gieben <miek@miek.nl>; wrote:
>
> [ Quoting <olafur@cloudflare.com>; in "Re: [Doh] meta qtypes..." ]
>
> I would prefer if the draft did NOT even consider Meta types, but limited
> itself to pure queries i.e. excluded query type's 128..255
> Additionally doing other things like Updates and Zone transfers should
> involve different meta types (lets learn from experience here not repeat
> mistakes)
>
>
> Yes! So make the draft say?
>
>   MUST support opcode QUERY. MUST NOT support any other opcode.
>   MUST support all RR types excluding the meta range 128..255.
>
>   A non supported query MUST be rejected with a ... ?
>
>
> /Miek
>
>
> No, please don’t prevent DNS Stateful Operations from working which is in
> Last Call and uses a new Opcode.
>
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-session-signal/
>
> Tom
>
>