Re: [Dbound] Draft problem statement and IETF "bar BoF"

=JeffH <Jeff.Hodges@KingsMountain.com> Mon, 10 November 2014 00:30 UTC

Return-Path: <Jeff.Hodges@kingsmountain.com>
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 0613A1A87C4 for <dbound@ietfa.amsl.com>; Sun, 9 Nov 2014 16:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.232
X-Spam-Level:
X-Spam-Status: No, score=0.232 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, 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 ciCsrjHRAuib for <dbound@ietfa.amsl.com>; Sun, 9 Nov 2014 16:30:44 -0800 (PST)
Received: from gproxy8-pub.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) by ietfa.amsl.com (Postfix) with SMTP id D8BD21A87C3 for <dbound@ietf.org>; Sun, 9 Nov 2014 16:30:44 -0800 (PST)
Received: (qmail 30714 invoked by uid 0); 10 Nov 2014 00:30:44 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy8.mail.unifiedlayer.com with SMTP; 10 Nov 2014 00:30:44 -0000
Received: from box514.bluehost.com ([74.220.219.114]) by CMOut01 with id DcWg1p00N2UhLwi01cWjJN; Sun, 09 Nov 2014 17:30:43 -0700
X-Authority-Analysis: v=2.1 cv=F5TEKMRN c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=xk8Vn6ZJdw4A:10 a=IkcTkHD0fZMA:10 a=ieNpE_y6AAAA:8 a=XYUc-DgfXtMA:10 a=Fwsyk3WOAnQA:10 a=48vgC7mUAAAA:8 a=v_V_jhFd_orDZri4cwoA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=iyM2aDzDT+dK5n9FZa6RTs96Jcef+utf002FUD0+azw=; b=7VyT3jD+VFi1w1RRxEBppwPwX/p1mdQw8SuLssta+PB1NKIFla9LENWK59FWQvgpw3P+k89fhWH9SLn/ed4vn5Mq0jMndzOvdBfocEtZmD8TIPNdsV61jPYP+fYLrAMp;
Received: from [24.5.2.144] (port=49583 helo=[192.168.11.19]) by box514.bluehost.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1XncsT-0008Kj-IM for dbound@ietf.org; Sun, 09 Nov 2014 17:30:41 -0700
Message-ID: <54600756.1020501@KingsMountain.com>
Date: Sun, 09 Nov 2014 16:31:18 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: dbound@ietf.org
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.5.2.144 authed with jeff.hodges+kingsmountain.com}
Archived-At: http://mailarchive.ietf.org/arch/msg/dbound/TfcR6EK-O_k1GmDnnF89K3LJrD8
Subject: Re: [Dbound] Draft problem statement and IETF "bar BoF"
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: <http://www.ietf.org/mail-archive/web/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: Mon, 10 Nov 2014 00:30:46 -0000

On Wed, 5 Nov 2014 09:36:30 -0500, Andreww Sullivan said:
 > On Wed, Nov 05, 2014 at 02:21:49PM +0000, Edward Lewis wrote:
 >>
 >> I guess what I’m saying is that I’m not so clear on why we are labeling
 >> domains as public or private.
 >
 > Your concern is precisely why, in my previous stabs at this, I have
 > attempted to avoid that.  It's the wrong classification, IMO, even if
 > it's a useful rule of thumb sometimes; and too much confusion has
 > resulted from trying to use it.

+1


 > Instead, we should be looking for a way of grouping identifiers
 > according to other classifications.  The motivating stuff in the
 > earlier I-Ds I wrote or worked on with Jeff is there to explain why
 > the DNS hierarchy is _not_ the right classification, despite the
 > attempts in the past to use it.

agreed.

e.g. please see..

Asserting DNS Administrative Boundaries Within DNS Zones
http://tools.ietf.org/html/draft-sullivan-domain-policy-authority-01

..section 1 "Introduction and Motivation".


 > Unfortunately, to my way of thinking, people who have running code
 > that is already based on the faulty reading of the hierarchy are
 > unlikely to change that enough to work with new arbitrary groupings.
 > Moreover, there's the additional problem that allowing arbitrary links
 > out of hierarchy will potentially explode the data that clients have
 > to pay attention to, and nobody is enthusiastic about that.

..which are considerations to keep in mind as we explore use cases, 
requirements, and potential solutions...

HTH,

=JeffH