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

Samuel Weiler <weiler@csail.mit.edu> Thu, 14 March 2019 20:13 UTC

Return-Path: <weiler@csail.mit.edu>
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 1C874128AFB for <dbound@ietfa.amsl.com>; Thu, 14 Mar 2019 13:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 bQELjqnnUnZm for <dbound@ietfa.amsl.com>; Thu, 14 Mar 2019 13:13:24 -0700 (PDT)
Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by ietfa.amsl.com (Postfix) with ESMTP id C6E01126C87 for <dbound@ietf.org>; Thu, 14 Mar 2019 13:13:24 -0700 (PDT)
Received: from 31-33-2.wireless.csail.mit.edu (31-33-2.wireless.csail.mit.edu [128.31.33.2]) by cyrus.watson.org (Postfix) with ESMTPSA id E8FBFC892F; Thu, 14 Mar 2019 20:13:23 +0000 (UTC)
Date: Thu, 14 Mar 2019 16:13:22 -0400 (EDT)
From: Samuel Weiler <weiler@csail.mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: dbound@ietf.org
In-Reply-To: <87a520c1-194a-ffd7-b58f-fea6e549d090@cs.tcd.ie>
Message-ID: <alpine.OSX.2.20.1903141600360.97311@macbook-air-8.local>
References: <20190227172143.10303200F57CE0@ary.local> <1FFA1977E97DE99C390869DA@PSB> <alpine.OSX.2.21.1902272038320.3336@ary.local> <49A2FC767B5A7146F39456B9@PSB> <A4E532F7-484E-4605-8D77-8E0A20A15014@gmail.com> <alpine.OSX.2.20.1903081516350.70761@macbook-air-8.local> <87a520c1-194a-ffd7-b58f-fea6e549d090@cs.tcd.ie>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-164857079-1552594403=:97311"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/HqfE01cZ3Ee3BrwkhOLhv62tWdw>
Subject: Re: [dbound] 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, 14 Mar 2019 20:13:27 -0000

On Fri, 8 Mar 2019, Stephen Farrell wrote:

>>> Accordingly, I’d like to see an example or two of how you’d expect an
>>> application to use the kind of connection between domains established
>>> by the RDBD mechanism.
...
> We added some text on that in -01, in the intro. See the top
> of page 3. Wasn't that clear enough?

No, it is not.  Those are pretty broad use cases.  I want to see them 
more specifically defined.  e.g.  "correlate the ownership of websites 
in different languages" is still pretty broad.  WHO do you want to do 
the correlation?  (Which pieces of code?)  Is this for statistics and 
analysis (only) - e.g. so the Alexa list reflects the aggregate of 
correlated sites?  Or do you want client code doing something?  Do you 
want cookies shared?  Credentials?  I realize that this could touch 
many parts of the stack.

Put another way, if you're right that:

> ... part of the reason DBOUND failed was an
> attempt to be all things to all parties. I think repeating
> such an attempt with RDBD would lead to the same failure.

Then the use case(s) needs to be very clear.

-- Sam