Re: [Doh] [Ext] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)

Paul Hoffman <paul.hoffman@icann.org> Tue, 12 June 2018 01:51 UTC

Return-Path: <paul.hoffman@icann.org>
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 49093130DD1 for <doh@ietfa.amsl.com>; Mon, 11 Jun 2018 18:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 AfuU6Y5d4G4a for <doh@ietfa.amsl.com>; Mon, 11 Jun 2018 18:51:11 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2D3F130DC3 for <doh@ietf.org>; Mon, 11 Jun 2018 18:51:11 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 11 Jun 2018 18:51:09 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Mon, 11 Jun 2018 18:51:09 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: David C Lawrence <tale@dd.org>
CC: "doh@ietf.org" <doh@ietf.org>
Thread-Topic: [Ext] [Doh] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)
Thread-Index: AQHUAe/VzBhdNBCRWEK8i8XD7rRPGQ==
Date: Tue, 12 Jun 2018 01:51:09 +0000
Message-ID: <1E183D79-5716-47E5-8604-A4F5DC7588C2@icann.org>
References: <20180606093212.GA23880@server.ds9a.nl> <20180608170744.GY11227@mx4.yitter.info> <03DC5A73-4BAD-45FE-AC60-C8BC82FD5690@mnot.net> <23326.43186.501116.977750@gro.dd.org> <20180611202130.GA26355@server.ds9a.nl> <23326.61211.72657.945633@gro.dd.org>
In-Reply-To: <23326.61211.72657.945633@gro.dd.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FCD3F34544B6E7489A9F82A4AFCADC05@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/dlei5xJ5XUaAG_s5Wm597gpse-k>
Subject: Re: [Doh] [Ext] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 12 Jun 2018 01:51:14 -0000

On Jun 11, 2018, at 2:52 PM, Dave Lawrence <tale@dd.org>; wrote:
> If there were even one solid example of how this impacts the rest of
> the DNS, I'd certainly be willing to reconsider my position.

Great! Let me try again.

The DNS message format is defined specifically for two transports. Looking at the format without looking at the transports, one can imagine a message that cannot be carried in either format. However, the original specifications and all the ones since have always treated the message format as being handled in one of the two transports.

When we define a new transport that allows messages different than the ones we have always assumed, gatewaying those different messages will be different than gatewaying between the two current transports and thus have an impact on the rest of the DNS.

The WG charter we are working under clearly says:
  Specification of how DNS-formatted data may be used for use cases beyond
  normal DNS queries is out of scope for the working group.
Creating new queries, to me, seems "beyond normal DNS queries".

--Paul Hoffman