Re: [dbound] draft-brotman-rdbd

Grant Taylor <gtaylor@tnetconsulting.net> Thu, 09 May 2019 21:23 UTC

Return-Path: <gtaylor@tnetconsulting.net>
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 91D3C1200B7 for <dbound@ietfa.amsl.com>; Thu, 9 May 2019 14:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tnetconsulting.net
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 FJ3gpxAoKpgy for <dbound@ietfa.amsl.com>; Thu, 9 May 2019 14:23:01 -0700 (PDT)
Received: from tncsrv06.tnetconsulting.net (tncsrv06.tnetconsulting.net [IPv6:2600:3c00:e000:1e9::8849]) (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 932F61200FA for <dbound@ietf.org>; Thu, 9 May 2019 14:23:01 -0700 (PDT)
Received: from Contact-TNet-Consulting-Abuse-for-assistance by tncsrv06.tnetconsulting.net (8.15.2/8.15.2/Debian-3) with ESMTPSA id x49LMxsW025873 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dbound@ietf.org>; Thu, 9 May 2019 16:23:00 -0500
ARC-Filter: OpenARC Filter v0.1.0 tncsrv06.tnetconsulting.net x49LMxsW025873
Authentication-Results: tncsrv06.tnetconsulting.net; arc=none header.d=tnetconsulting.net
ARC-Seal: i=1; a=rsa-sha256; d=tnetconsulting.net; s=2015; t=1557436980; cv=none; b=0QmXzfEok9QIdtcJCgWyoK5AdwMqP5yc7BD7hJYPrPSWmmZ7BCmCy/Z9Zt/Z1pOeten1/oSudLNQvCvuyWR1oKkn9m3u973GOA7PufhxtFHGpWeoR4pJ8P7X1mOF4KZTVMPI9kyeKMUHIFgCTn164/KPnVQEXA087vCmnBzGzJ0=
ARC-Message-Signature: i=1; a=rsa-sha256; d=tnetconsulting.net; s=2015; t=1557436980; c=relaxed/simple; bh=GwRjPa34JippFngnf8wxMALDOpg1eFMwWLBjCyBSmM8=; h=DKIM-Signature:Subject:To:From:Message-ID:Date:User-Agent: MIME-Version:Content-Type; b=1roqL5a0uJ0WHy1RhFAg0XzSU+oadcwuYHRx8ttrX499P0oksfndp3XggXO/Xek2EU4rKMRwmQOgccuqlZqEgtn9BtlHpGtfAF9IM+q/NLbKS6YlZFzJ61Eg4I8qEWw6FpY3cnlfaINIU5jejsoR5v8DzKDEBPjasmCC+quIhcU=
ARC-Authentication-Results: i=1; tncsrv06.tnetconsulting.net; none
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tnetconsulting.net; s=2019; t=1557436980; bh=GwRjPa34JippFngnf8wxMALDOpg1eFMwWLBjCyBSmM8=; h=Subject:To:References:From:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Cc:Content-Disposition: Content-Language:Content-Transfer-Encoding:Content-Type:Date:From: In-Reply-To:Message-ID:MIME-Version:References:Reply-To: Resent-Date:Resent-From:Resent-To:Resent-Cc:Sender:Subject:To: User-Agent; b=Qmi89qnZWLsdvPKQocBHy954ht/uKrZHZoKqR4V4RP3oez2r8vN/U7+rIIftAIsF6 f53H6n+hBI/9/Q7dvGxnkzVWVYPjZmXnxa7P0X/2+Ylry7hAU/g+IY4zLBewZnq4fC 8trrvf2wdX0irE/mAE0/hJIl19TwhU2wUYGJit/Y=
To: dbound@ietf.org
References: <20190509164241.354EF2013999BB@ary.qy>
From: Grant Taylor <gtaylor@tnetconsulting.net>
Organization: TNet Consulting
Message-ID: <0b0d9206-2c30-e151-f321-d459bc1e80e8@spamtrap.tnetconsulting.net>
Date: Thu, 9 May 2019 15:22:59 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20190509164241.354EF2013999BB@ary.qy>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040207090409010909000808"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/KjK1hsA8pwuw6VNoBs5NiOQGWpo>
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 21:23:04 -0000

On 5/9/19 10:42 AM, John Levine wrote:
> 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've seen PTRs used outside of in-addr.arpa and ip6.arpa.  Particularly 
with RFC 2317 Classless IN-ADDR.ARPA delegation with CNAMEs pointing to 
names outside of in-addr.arpa / ip6.arpa.  Even RFC 2317 has examples 
reconstructing the in-addr sub-domain structure in other domains in ยง 5.2.

> 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've not suffered through that misfortune myself.

I seem to recall an intriguing use of PTR records for other information. 
  I think it had to do with translating service names to the host 
running said service name without actually altering resolution like a 
CNAME would.

smtp.example.net.   IN   A     192.0.2.34
smtp.example.net.   IN   PTR   host.example.net.
host.example.net.   IN   A     198.51.100.69



-- 
Grant. . . .
unix || die