Re: [dbound] draft-brotman-rdbd

"John Levine" <johnl@taugh.com> Thu, 09 May 2019 16: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 3AA611200DF for <dbound@ietfa.amsl.com>; Thu, 9 May 2019 09:42:48 -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=cV1GsGus; dkim=pass (1536-bit key) header.d=taugh.com header.b=u+QG2IQe
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 f66jFH4aotvv for <dbound@ietfa.amsl.com>; Thu, 9 May 2019 09:42:46 -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 3851A12006B for <dbound@ietf.org>; Thu, 9 May 2019 09:42:45 -0700 (PDT)
Received: (qmail 90586 invoked from network); 9 May 2019 16:42:41 -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=161d5.5cd45881.k1905; i=johnl-iecc.com@submit.iecc.com; bh=R+3FANrlShl3D0tA0kMCDJHdC8wVz8+ZrCjTUMwhesE=; b=cV1GsGus+AQEXo7ZA08NXcFnfPY1LB/jJwkWDh9sw6Sxw8L0gNCZDyaiaVhUFHfydCfFt5Gt4i+F9tbZee3WIPZmdiCPCXjHeHVTi0Bk2bf8p+RzEl8B44aWNSF7x/TbSTNHhOF6Ipv1y0Tb6Sm+z/jR1vHBp8/d1uMOZr26KDBWp003TD/+IavNG8jwReiUC1jVq9ByE0VlTl9ppWgwwRNv2Ry9ORjYn7toH664Yb+wS8/ZAOdMjZ65F8McNHCM
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=161d5.5cd45881.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=R+3FANrlShl3D0tA0kMCDJHdC8wVz8+ZrCjTUMwhesE=; b=u+QG2IQetRl7D7a62tKU+CxVxvv8R3xYQT2G5nWVQzo937fIo2wi6egaKXypANze8kNRMYoRlXeKKQhvKJO3CAJS+2QgF5SG4qLTpva7n0YyUafX0oGm/L4psenvrSvFAij2QUh18LW3E4UlS5a9Xlr70oa7ceigPfEzDlLi/bJvFzONQQrukX5BJn4HEMMwSTp15kvsvqzIBEMqSMsoJ/vMT2YyZK8pFeOm0ULDESiAEm/XbGiCsPKLfCA5t6ZG
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 16:42:41 -0000
Received: by ary.qy (Postfix, from userid 501) id 354EF2013999BB; Thu, 9 May 2019 12:42:40 -0400 (EDT)
Date: 9 May 2019 12:42:40 -0400
Message-Id: <20190509164241.354EF2013999BB@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dbound@ietf.org
Cc: Niall.oReilly+IETF@ucd.ie
In-Reply-To: <0899C38C-8802-48ED-ACB6-E6BC3F863C9F@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/Ji_YENlcounNKSZXYf0dClk9j6M>
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 16:42:48 -0000

In article <0899C38C-8802-48ED-ACB6-E6BC3F863C9F@ucd.ie>; you write:
>Hi.
>
>At Stephen Farrell's suggestion, and after an inexcusable delay, I've 
>taken a look at this draft.
>
>My first reaction is that the PTR record (RFC1035, 1987) seems to fit 
>the intended use case.

For over 30 years the only place anyone has used PTR records has been
in the rDNS trees under in-addr.arpa and ip6.arpa.  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.

Note that RFC 1035 says they "are used in special domains".

R's,
John