Re: [dbound] [art] [DNSOP] Related Domains By DNS (RDBD) Draft

"John Levine" <johnl@taugh.com> Thu, 28 February 2019 02:03 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 B12A8130ED7 for <dbound@ietfa.amsl.com>; Wed, 27 Feb 2019 18:03:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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=B5HqItVX; dkim=pass (1536-bit key) header.d=taugh.com header.b=fzQHZ/YR
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 Bv3LnM60RP7Q for <dbound@ietfa.amsl.com>; Wed, 27 Feb 2019 18:03:35 -0800 (PST)
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 F21A9130ECF for <dbound@ietf.org>; Wed, 27 Feb 2019 18:03:34 -0800 (PST)
Received: (qmail 70194 invoked from network); 28 Feb 2019 02:03:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=11230.5c774175.k1902; bh=2f2OxB/3AD+cX0MyYgUBXX9iSAv7iAVj90ce5T0Qa/4=; b=B5HqItVX98OCOYRAtf1v79QtU1IZ7uMhWC/y1xKBGxVrrjQJvwY6JQk4ms7aMeRSc+t4YSMiL7/J/w5N4D2yPXkZrH4KNofQ0PDvPSneYeB8fxNm4c19muMIFR4Yava/Dbc9hDX4DgXUCZG3WYWmBKi9DWVdrK4L0gkCa0TEofrulpkPvjP4Q9DuJ/CxwiREJOTCaxyG5Q9pB1uIpMk7b6bkUlcBsPOBsq8myJEMWjk/Ty9DHgADZNP1SdQ1aspd
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=11230.5c774175.k1902; bh=2f2OxB/3AD+cX0MyYgUBXX9iSAv7iAVj90ce5T0Qa/4=; b=fzQHZ/YR6kf/ctlixBs1XIGkIrL1N6h2r4NmFjOXu4L8IQkBoY+1RDWAHixdnul7owB4ZOb9eyNl78xhW66pBoe55hgVz9fP0D2Q/NW+GE3O7dnTlsy+3syS4knaNQeze7M3vx1ajL+/v9DgfY1Y1UOlu+QbLJ2fG/aAWGh1rCfNmSh6YI7E1R3L4DCk28mBQwa9geVqYCNyXXgOZlFleb0Cg8HG70aYmEpT49+YIhUUc/adR2lJpJV73+AD4c5P
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 28 Feb 2019 02:03:32 -0000
Received: by ary.local (Postfix, from userid 501) id D2112200F6CEC9; Wed, 27 Feb 2019 21:03:32 -0500 (EST)
Date: 27 Feb 2019 21:03:32 -0500
Message-Id: <20190228020332.D2112200F6CEC9@ary.local>
From: "John Levine" <johnl@taugh.com>
Reply-To: dbound@ietf.org
To: art@ietf.org, dbound@ietf.org, dnsop@ietf.org
Cc: stephen.farrell@cs.tcd.ie
In-Reply-To: <249a56b6-7bf6-d1e3-2639-0f2d8043aa3e@cs.tcd.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/nDoQ8HzJ_-_Ay-4sFlh65QU9jEQ>
Subject: Re: [dbound] [art] [DNSOP] Related Domains By DNS (RDBD) Draft
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, 28 Feb 2019 02:03:37 -0000

In article <249a56b6-7bf6-d1e3-2639-0f2d8043aa3e@cs.tcd.ie>; you write:
>> point back to that key, but not enough just to publish the secondaries'
>> names directly.  I don't get it.
>
>That could work, but'd mean the primary having to store
>all the records and an extra lookup if even if you had the
>public key cached. I believe the former could be an issue
>if there are many secondaries, at least according to one
>chat I had with someone involved with many domains (which
>I'm not).

Well, OK, if that's an issue you spread the names out like we did with
VBR.  If the primary is foo.com and the secondary is bar.org:

bar.org._same.foo.com. SAME .	; yes, we're a primary for whatever name that was

_same.bar.org. SAME foo.com. ; yes, we're secondary for foo.com.

This makes it somewhat more difficult to scrape all the secondaries
for a primary which may be a feature.

R's,
John