IETF Logo Mail Archive

Re: [dbound] draft-brotman-rdbd

"John Levine" <johnl@taugh.com> Thu, 09 May 2019 19:42 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C9512013C for <dbound@ietfa.amsl.com>; Thu, 9 May 2019 12:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=LmGCw19z; dkim=pass (1536-bit key) header.d=taugh.com header.b=hc7N5cop
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 C8jK-riBohFI for <dbound@ietfa.amsl.com>; Thu, 9 May 2019 12:42:34 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 463341200F4 for <dbound@ietf.org>; Thu, 9 May 2019 12:42:34 -0700 (PDT)
Received: (qmail 51737 invoked from network); 9 May 2019 19:42:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ca17.5cd482a7.k1905; i=johnl-iecc.com@submit.iecc.com; bh=rkredLMRSStmw+WJF23oirJl/seoJhFKgbsrJIRnAxw=; b=LmGCw19zvoZf07rxMexWYU2X/Imho0dv/SckyPflKi9u00BUKDr3J3MdRvPJhxfHIg97OFEE5I+weyDW2/Hkt9fNamwmEVTrv8RvtZqfJJbGFo+uhgPeBsoy+wmmS12i51ZAhFx0Bm2/Yw01HNwTH/rzGmR32I2768ZkfgU+ip0xKC5Im0gwfKvqGQetcuxZMeNkfK5pq1Pwa4qjyrsKp4I1mk33pXNObQ0g3G1k+LvnN11kOdjOyvxzeglgmzSb
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ca17.5cd482a7.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=rkredLMRSStmw+WJF23oirJl/seoJhFKgbsrJIRnAxw=; b=hc7N5copx2ojDoucXwmTJd/J/l0O8RJMpb3OOCB5MK0trjtR5B4Vz6dM3sI8jDC52o3irUfIjlt4fSSUt7D5YsCpQ8/fY66fBPeWOGwVRxxaSQkmlld+fvHeOjQmG7Aa9ReJFxq5A9v2EHOeCIOdUpgBU9aRGB5w62qrQGMAy7OnFnY9MzOG4b2HCgxSVcBJKS/E0nr9f+LWpbqGrfWfJCb9fnua0KxKQjNxPUdEJKQUFNeRWKZYF6q0z5BkJIq+
Received: from ary.qy ([64.246.232.221]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP; 09 May 2019 19:42:31 -0000
Received: by ary.qy (Postfix, from userid 501) id A9AA320139C0F5; Thu, 9 May 2019 15:42:30 -0400 (EDT)
Date: Thu, 09 May 2019 15:42:30 -0400
Message-Id: <20190509194230.A9AA320139C0F5@ary.qy>
From: John Levine <johnl@taugh.com>
To: dbound@ietf.org
Cc: niall.oreilly@ucd.ie
In-Reply-To: <130D3CBF-277E-49FE-B353-6CD8AE15FC61@ucd.ie>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/OQnyIeVV91XhC-ETQc8drNDhfRI>
Subject: Re: [dbound] draft-brotman-rdbd
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 May 2019 19:42:36 -0000

In article <130D3CBF-277E-49FE-B353-6CD8AE15FC61@ucd.ie> you write:
>> I think that if
>> you try to use them anywhere else, you'll find way too much software
>> that has baked in assumptions that they don't belong there.
>
>I'm not sure what kind of software might have such assumptions
>baked in.  The very small sample that my provisioning chain includes
>(Emacs, dnssec-signzone, nsd, unbound, zonemaster) shows no problem
>of this kind.

The usual problem is middleboxes.

>I have a strong suspicion that any provisioning chain needing
>modification to accommodate innovative uses of PTR would also need
>work to add support for the new RRtypes proposed in the draft, and
>that the effort involved in either case might be roughly commensurate.

Commensurate but different.  Adding new rrtypes is a well known misery
with the problem being primarily in the provisioning crudware that
people use to manage their zones.  Finding unhelpful middleboxes is a
more distributed problem.

v2.23.0 | Report a Bug | By Email