Re: [Dbound] Are there any deliverables?

Jeffrey Walton <noloader@gmail.com> Fri, 04 July 2014 00:36 UTC

Return-Path: <noloader@gmail.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 438D41B2B91 for <dbound@ietfa.amsl.com>; Thu, 3 Jul 2014 17:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 mMEIZBztp1YC for <dbound@ietfa.amsl.com>; Thu, 3 Jul 2014 17:36:22 -0700 (PDT)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C60F1B2923 for <dbound@ietf.org>; Thu, 3 Jul 2014 17:36:22 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id jw12so992287veb.39 for <dbound@ietf.org>; Thu, 03 Jul 2014 17:36:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=RHCu9J0iX26lGXP2lgPlaZA5T0PUk3SG5HjkY1GPwEM=; b=VncdW58tr8lQyuotInxmWw4+XXacjuMw5vJg6L/mg27sjNGnks14EtzTL5FHTYP+MC 6jJ5ebPriDXpAnfrETJNgHP+yfJRIZhEdxRohBdHMrF0G+pKEX+o2wn5aG38vs6bOFZL qhdw+8+9FmOkx6vlplxIOkOzclenH+V8wBGYBHm9fL/F2LNAuCkCe+YA6xRQs4Uzysic lVkd257GxyhrJoMQ1V+rhHYsQo4deg3wIm0MRXUZv/es7n9THvTEgig7WYXXOhymC2IC lf1MzEEedFahc77RsfTf7sMiVZOg1LM8RjZ+/e1pUj+AAogjECi7DGHc9w7qGa1qYExU CnBQ==
MIME-Version: 1.0
X-Received: by 10.58.153.4 with SMTP id vc4mr6417079veb.19.1404434180182; Thu, 03 Jul 2014 17:36:20 -0700 (PDT)
Received: by 10.220.227.7 with HTTP; Thu, 3 Jul 2014 17:36:20 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.11.1407031958190.12101@joyce.lan>
References: <20140703222002.GA51076@mx1.yitter.info> <20140703225614.12420.qmail@joyce.lan> <CAH8yC8ko1fR8UvetPqtp5YBN0VJtv5SW42qWDjqZnCnbQ8a9dw@mail.gmail.com> <alpine.BSF.2.11.1407031958190.12101@joyce.lan>
Date: Thu, 03 Jul 2014 20:36:20 -0400
Message-ID: <CAH8yC8=R0Y35boZbNASB90gDz3aRMYRMEFQSC9WjytYxhvR2-Q@mail.gmail.com>
From: Jeffrey Walton <noloader@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dbound/aOphMGcWFnJsvF7R7Roe5Yca47s
Cc: dbound@ietf.org
Subject: Re: [Dbound] Are there any deliverables?
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: noloader@gmail.com
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: Fri, 04 Jul 2014 00:36:23 -0000

>> Ah, OK. I can give you the use cases I am familiar with. But they are
>> not sexy like the WWW folks want or have.
>
> I think we have a pretty good list of problems.  Let me see if I can help
> get a draft out and see if we missed anything.
>
Yes, please.

Also, I'm not sure about this from draft-sullivan-domain-policy-authority-01:

   Historically, policies were sometimes based on the DNS tree.  Early
   policies made a firm distinction between top-level domains and
   everything else; but this was also too naive, and later attempts were
   based on inferences from the domain names themselves.

I think the distinction is going to be one part of the solution.
There's no reason non-browser software should be matching "*.com" and
"*.co.uk" by default (and friends like "www.*.com" and "www.*.co.uk").
If you asked 100 developers if that's what they wanted, I would wager
the majority would not want the feature (and be surprised it was
happening).

Jeff