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

Bob Harold <> Tue, 26 February 2019 21:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E5A1B130E96 for <>; Tue, 26 Feb 2019 13:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wmXzW_9PxZlu for <>; Tue, 26 Feb 2019 13:15:13 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E114A129A85 for <>; Tue, 26 Feb 2019 13:15:12 -0800 (PST)
Received: by with SMTP id m73so5216720lfa.2 for <>; Tue, 26 Feb 2019 13:15:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=OcFeJ8sbe7K2oT4ssul2n7Vc0+Lrec3nlg0w/eatZYM=; b=Wdbn36hqaKqshOH6mXq7rvewbgS1ubQox6Q1BHcnuZYYEJKSrrpuo+3b4zgEAJ95AX nxCAEzE4ha6p0S3nWZtHWjN9O4boLdGhya6QGqRLhBoG3CSfYOPr8NTcDYomiL/+XavS iFlFUGVmuP5eA27vYVIQaeT3vWLG74Dy6lB/3yvW09aqsr1xLEdjdKkQ0iuxnuf4YqfE MHPXpzs/l0BqtCAhxOj06ROJdMjrm4zJ5sHHiNIBIKORUWS01mWGTLT5kpUBtF8QMP70 QvJca3JoEWbzszv8CeZuK/Kdgcu7gP3jNh+eS9hzTNgrvy1OKFkWhJY2vWST4S3vNYk0 0XSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=OcFeJ8sbe7K2oT4ssul2n7Vc0+Lrec3nlg0w/eatZYM=; b=VL3uef2B/ExRQKodd/l9+oICLG0HG+Rz5Eg/IFDwfdCakXXLnqwdAFahbX4X0wVcI8 FFa2M/3wbM/0X02oDBDzX9jQj4mlJppUPxzIeIuhSKYjY1j5jm8u3/aDvop/wOpwlr5k ORCO2yTn2QCbUoyw0noM9wwS3WpgSc8qW5Xq3U+qCZpNSwfR6OQxv3CBRN5LAezUxNOW iSy+SIyEbPQ+WBPlKnZxGG0ls6MC1H2GTT8CE0p7kYsGrNOno0HQvgVZ7HUu5Ngkt+vH 2fx6IU/gnlqqGQLdia7Ph3A3DuhctSsV56umxahyLUwaMG3QCOFG/MFeJk6PobUxdmY8 2ISg==
X-Gm-Message-State: AHQUAuYQMZckXFiYW0y4T4AUwVU/1CeEt+4aipK938gz94VgnpGnhDiM ERoJ6o0MObwRCDHVWWEvO7VOrL3KJ2cvZpLtGSbDO+fpTP0=
X-Google-Smtp-Source: AHgI3IYbc/vnHHrbTm++n3nu6vasXpDBK2AOp2oN5mX1Frq8SEI0gfORAchhBnP9sjSyAF3iGK+IWoD397CLdmkLin0=
X-Received: by 2002:a19:4d08:: with SMTP id a8mr10851146lfb.14.1551215710090; Tue, 26 Feb 2019 13:15:10 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Bob Harold <>
Date: Tue, 26 Feb 2019 16:14:59 -0500
Message-ID: <>
To: "" <>
Content-Type: multipart/alternative; boundary="0000000000005ecf2d0582d28d8a"
Archived-At: <>
Subject: Re: [dbound] [DNSOP] Related Domains By DNS (RDBD) Draft
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS tree bounds <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 26 Feb 2019 21:15:16 -0000

On Mon, Feb 25, 2019 at 3:38 PM Brotman, Alexander <> wrote:

> Hello,
> Stephen and I have spent a bit of time working on a draft to be able to
> show a relationship between two domains.  We're aware this subject has been
> covered a few times previously, especially in the DBOUND drafts, but we're
> hopeful that a more simple approach might be more acceptable.   The
> secondary domain will create a DNS record that shows a link to a primary
> domain, and the text should be able to be validated using the public key in
> a DNS record the primary domain shares.  This is something akin to DKIM, a
> mechanism that the email world uses to ensure the contents of a message
> have not been tampered with.
> We'll request that replies relating to this be sent to the
> due to the nature of the topic, but it was suggested that we might want to
> notify a few other lists for their awareness.  Thank you for your
> participation and comments.
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
The concept looks reasonable to me.

Both parent and secondary zones should use the "_rdbd" sub-domain for the
TXT records.  Please do not put TXT records directly on the main domain -
too many different things are already doing that.  Please update section
"2.  DNS Record for Secondary Domain" to make that clear.

Also, please keep an eye on
and add a section to your rfc to add "_rdbd" to the registry, once it

Bob Harold