Re: [dbound] on "control"

Casey Deccio <casey@deccio.net> Thu, 08 October 2015 20:27 UTC

Return-Path: <casey@deccio.net>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8788E1ACD52 for <dbound@ietfa.amsl.com>; Thu, 8 Oct 2015 13:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 1B6FWqv7ktah for <dbound@ietfa.amsl.com>; Thu, 8 Oct 2015 13:27:51 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F5871ACD50 for <dbound@ietf.org>; Thu, 8 Oct 2015 13:27:51 -0700 (PDT)
Received: by iofh134 with SMTP id h134so71391606iof.0 for <dbound@ietf.org>; Thu, 08 Oct 2015 13:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=deccio.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=maKaxhjv08COTMKpGF1iAa7VdPFgAIe4VZUpRAKjpKU=; b=GE2dGdLnDN6y3zUaFWz3PqooSN5r6u7TFxAgfmG2Qejnr2PE3NYVfyCI+ueXYZe8hJ MaCVwRVPfmEVOxOaVONiMVqsDeHxgBlsb+iww3U3h2DWU7BLHm/It2fSZXnRT6axDgdb jerbEeVFFlGEmmwS+0RFr8mlMy7uRnHvISpkY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=maKaxhjv08COTMKpGF1iAa7VdPFgAIe4VZUpRAKjpKU=; b=B2+5lxMYe6Teq4x1llyh8zQAGDOGzIvqCeZZLiU6Y8BlmbfgDN3T0lWUfReC6u1xqk DbBs8unxy2xSNVS0yT5fh4cV9kn3/OO5uyQB3NTCoAb7PpOKuEHx9EFbYJqNx4nn77t0 K5TDzOIsMzJAkGtYrST65MykwWMvqQ39IdOIdswYJowbjTCLRFurDxErRHkZzo+uRKzC vJhPo8UlX3XQZuUpRcYfoH51LV66W4/nXjUQr2uewPhHPZO2Fq2x8kr8ymUzzN84rYKp erfNWVGLV+P5AfXXGF0mOICNmcSFY9LbWhc549KgR4UhtnrExGxkIvLFAWOJfqvp7Ke+ usNQ==
X-Gm-Message-State: ALoCoQkIbheVm4M+BWtXaeGhozP5fAPmUAEcV5lnjywlOWpw00hNo1ys32cSBXXU3lmN7LAyF+XA
MIME-Version: 1.0
X-Received: by 10.107.19.234 with SMTP id 103mr12538878iot.41.1444336070207; Thu, 08 Oct 2015 13:27:50 -0700 (PDT)
Received: by 10.50.159.230 with HTTP; Thu, 8 Oct 2015 13:27:50 -0700 (PDT)
In-Reply-To: <20151008192001.GR17602@mx2.yitter.info>
References: <20151008192001.GR17602@mx2.yitter.info>
Date: Thu, 08 Oct 2015 16:27:50 -0400
Message-ID: <CAEKtLiR56fLY=omL5kRghtL=TgY3Hi2KfmK9ji-9p4bn3JAdug@mail.gmail.com>
From: Casey Deccio <casey@deccio.net>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary="001a113f7a9266c9e905219db20e"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dbound/Wvg8hfv-3nFrD4_XQjQKUhsIgBg>
Cc: "dbound@ietf.org" <dbound@ietf.org>
Subject: Re: [dbound] on "control"
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Oct 2015 20:27:52 -0000

Hi Andrew,

On Thu, Oct 8, 2015 at 3:20 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> Control:: (as in "Is domain X under the same control as domain Y")
>
>
While this was one of the "questions" that were posed for discussion prior
to the DBOUND WG meeting in Prague, it seems to me to be fairly high level
and the least grounded in an actual application problem.  I'm not saying
that it's not worth consideration, but if I had to prioritize the
questions, this one comes after others that stem from current application
needs (e.g., HTTP cookies, DMARC, etc.).


> Therefore, it seems to me that we could cover the two different use
> cases by refining the SOPA record Jeff and I have already proposed,
> and then adding a different mechanism for the second style of problem.
> We could call this second case "Parent-Imposed Policy Assertion" (or
> PIPA for a nmemonic.  Yes, this tickles me slightly).  The PIPA RR
> would in effect assert that it has policy rules that bind descendents.
>

In general, think you're right - that there are two broad categories of the
problem: identifying policy relationships between a domain name and its
ancestor or descendant; and identifying policy relationships between two
domain names that are not ancestrally related.  This sentiment was
expressed at the DBOUND WG meeting in Prague.  I also had with the
impression from the WG discussion that the two should be considered
separately and that the former was the more pressing than the latter.

My focus as of late has been the former, and I have a draft that will be
submitted soon on that topic--probably Monday.

Casey