Re: [dbound] Thoughts and comments on draft-levine-orgboundary-04

Casey Deccio <casey@deccio.net> Tue, 19 January 2016 16:11 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 C7D021B315C for <dbound@ietfa.amsl.com>; Tue, 19 Jan 2016 08:11:55 -0800 (PST)
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 ksKpr5oPSVsj for <dbound@ietfa.amsl.com>; Tue, 19 Jan 2016 08:11:49 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 E93441B3159 for <dbound@ietf.org>; Tue, 19 Jan 2016 08:11:47 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id n5so120052389wmn.0 for <dbound@ietf.org>; Tue, 19 Jan 2016 08:11:47 -0800 (PST)
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=A3NnjYPFZAHe+p93jhM/RdTjk3Ih3rpakM6MMzMhfwc=; b=LYWHAVuiEz4w2kW88Z0tWonO8A9OIArsf6QixBQ5y6Z+4nCndbYtCV53zBYKLSpLZ5 vFaSHZNaxlWILrZghWSO5aJHz6OpYl3O0WFpyabIGJP9kX21W3UHXwGAfGSO/ZVWyLyW O76a6Kl86r1VAlgKIogywU40TXacLrrB0NouM=
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=A3NnjYPFZAHe+p93jhM/RdTjk3Ih3rpakM6MMzMhfwc=; b=Pr7llfWqAbgWxS6Tx+IXZx5N2sADf5N1M5LLLfmZ0nEaBKZwda75tXoKQV0YHxneAr 0qaW8+O62r+mGG7heUNcOdt/IttNM5P+L2oj6FmTZs6v+tqlnzvEXh65JN6bVmoiXpLd uVYbpdOgs899RVidrK6cX3c53tJAKVFvWIPbMJBpgAHckd5Dd/GE4UDVH3jjvNSARaBY XfecFfgpl23+bAWVSlXVPVERriAvhtHYm0pfch49FFPCLU24Fn03Zg/o4YD6/WhrckJP 8DFRX6OZvqolIDB8le2IQpKaWqKKuyh0xTiRyaEzcq5RHAS3Zt3Fe1k/n8+SBW7bsXYR IG/w==
X-Gm-Message-State: AG10YOQc+d7MtostaIIrDC1yqzN+W9n9I0bJzso5jrv3DCUDASCKMbYfhWw3NWVAR03rZsmxicbSruo3FMf51Q==
MIME-Version: 1.0
X-Received: by 10.28.90.67 with SMTP id o64mr19109586wmb.38.1453219906405; Tue, 19 Jan 2016 08:11:46 -0800 (PST)
Received: by 10.194.73.137 with HTTP; Tue, 19 Jan 2016 08:11:46 -0800 (PST)
In-Reply-To: <CABuGu1ofY4OCSMRfZcwwB9hOYj6vaEDixVLLj9T4mC_5kzK8cg@mail.gmail.com>
References: <CABuGu1ofY4OCSMRfZcwwB9hOYj6vaEDixVLLj9T4mC_5kzK8cg@mail.gmail.com>
Date: Tue, 19 Jan 2016 11:11:46 -0500
Message-ID: <CAEKtLiSubmqy_CT_oRoJr8R_ZV=SPHT9nUhDsfaWS+eEq6sRMQ@mail.gmail.com>
From: Casey Deccio <casey@deccio.net>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Content-Type: multipart/alternative; boundary="001a114526b84d67120529b22005"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dbound/UQbkh6OS5ZSdhTnHFBocKAMT6eM>
Cc: "dbound@ietf.org" <dbound@ietf.org>
Subject: Re: [dbound] Thoughts and comments on draft-levine-orgboundary-04
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: Tue, 19 Jan 2016 16:11:55 -0000

On Mon, Jan 18, 2016 at 7:42 PM, Kurt Andersen (b) <kboth@drkurt.com> wrote:

> I'm still not sure that I have entirely grasped the nuances and especially
> the potential corner-case holes that reside within the algorithm proposed
> by Casey
>

I'm happy to answer specific questions or better explain concepts that are
poorly presented.


> and I don't see the benefit of supporting an "offline" mode since the
> applicability of the domain boundary lookups is in dealing with online,
> real time queries.
>

Unfortunately, domain boundary lookups are not confined to online,
real-time queries.  For example, for applications with performance
considerations, and/or those which have resource- or network-constrained
environments, online lookups might not be feasible or desirable.  Nor is it
necessarily feasible or desirable for logging or forensic applications.
I'm sure there are other examples.

The context of where we're coming from needs to be understood in designing
solutions in this space: the current solution is an offline file.  While a
solution with an online component is reasonable, closing the door to
offline solutions is not backwards compatible neither in the lookup
process, nor in the behaviors inherent in the process.

Also, this is one of the considerations that was discussed in the Prague
meeting and later mailing list discussion:

http://www.ietf.org/mail-archive/web/dbound/current/msg00502.html

On this topic, I'll be updating my draft (and code implementation) in
coming weeks to flesh out and clarify the offline component, addressing
some of the concerns that have cropped up in that regard.

Regards,
Casey