Re: [homenet] RFC 7788-bis (and also draft-cheshire-homenet-dot-home-03)

Ted Lemon <mellon@fugue.com> Sun, 17 July 2016 22:39 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED45612B018 for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 jfNRuNEu_jxO for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:39:06 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::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 1410512B00E for <homenet@ietf.org>; Sun, 17 Jul 2016 15:39:06 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id g62so10057962lfe.3 for <homenet@ietf.org>; Sun, 17 Jul 2016 15:39:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4tmDonKpqWPtcfuDSjuLxlT2js3tvx4vkZ4RQeDkD+0=; b=hPJcTYAQ2eWBU6thrJqdX4HkjWYsKekC5VXGfo9vr036UII1XJPQujRCToWdStcKow b/IeuyGLgdg/0f+W9zles3txyWnM3X6QNvvoTfBEBVdvn4yxTTkQjqkI+ww+HIThrMH0 lZN0T8M4cN1frz+M7aWCbrGmenLXON3VDOtWnfwSu1NTFAk1vekUJRMzr/BcS923ArPW ILaBKhZf4pdV6dgoZUNLTfp/Jdw7ddxa3rbfX9xwLM+h73N35RDyswfAJKgTtzTO2Zey usRkksG1TrxjXJagQ7UXqeJWm8nppKv0HprkCmdPzHhA3HzZy4SevTVl+kLf5wFeKI5t R39g==
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:from:date :message-id:subject:to:cc; bh=4tmDonKpqWPtcfuDSjuLxlT2js3tvx4vkZ4RQeDkD+0=; b=FJT1Tc6752ReV9O2Yp9gXEjbE9KKnb/nSV01hQSMOynesTr9s2F1/Ngs7IJZP8iswY xONknTDIP2Lbl0t8cNIVMu7icmRg8jwtRCTFuuhkEUZrfod4TiNgqgDxI4ywwpSntEQP hnZwIX5nE1AF3/WAJiQ6oMJzXd/RQlo5KJtCTyt5OvU+DHiB3cRhP8XRdQrMOJAgNEYT GKB9V8YLda+PRqBFoISaWQm3OqbuqZgWCs26hWoWzPZT9y7WV+88ASpw/QiycgjzbT5R My+0SIBVDrh3VBb3f5asXh/8aWbkSSXFNquk1YlZeqbDLF+Ns0hXbRHFYa9oIZb3vNqn qLXw==
X-Gm-Message-State: ALyK8tKfrSnYpnHj+LAJyzJl8wd2mAB7yX8uNGRcn/2N9L1FzIB6LVl3mTgWyQIFEEWuND74cmVTYD6t2W2MOQ==
X-Received: by 10.25.159.10 with SMTP id i10mr3043063lfe.131.1468795144181; Sun, 17 Jul 2016 15:39:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Sun, 17 Jul 2016 15:38:24 -0700 (PDT)
In-Reply-To: <20160717223416.GB40669@mx2.yitter.info>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <20160617010044.GA22195@mx2.yitter.info> <4e794ce6-2605-a0d2-c0e7-fe44bb149794@bellis.me.uk> <20160717223416.GB40669@mx2.yitter.info>
From: Ted Lemon <mellon@fugue.com>
Date: Sun, 17 Jul 2016 18:38:24 -0400
Message-ID: <CAPt1N1ngRGChXV_b6z9C_drWNMKccEPt7nKs1DE5_L055GMHHg@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary="001a11411c42d128860537dc843b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ZyCN9-ix4R5-C_r808oPQ2Me7qc>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788-bis (and also draft-cheshire-homenet-dot-home-03)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jul 2016 22:39:09 -0000

Violent agreement here.   Hence, ".homenet".   :)

On Sun, Jul 17, 2016 at 6:34 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> Dear colleagues,
>
> On Fri, Jun 17, 2016 at 09:37:06AM +0100, Ray Bellis wrote:
>
> > Whilst there may be "undermined" ways it's being used, it's clear that
> > most of the ways it's used are just because some vendors and sites
> > decided to use that for their default *site local* domain which makes it
> > completely consistent with what we need.
> >
> > I therefore completely disagree on point #1 - officially allocating
> > .home for this purpose and having it "sunk" by default on internet
> > facing recursive resolvers would IMHO actually *help* with the traffic
> > hitting the root and reduce leakage of it.
>
> The argument above, which is rehearsed to some extent in
> draft-cheshire-homenet-dot-home-03 (although there IMO more subtly),
> is interesting to me, in that it appears to start with the exact same
> premises I do and reach the exact opposite conclusion.  I believe this
> is because of some unstated premises, and so I'm going to attempt to
> lay out the premises as I understand them as completely as I can.
>
> To do this, I'm going to draw some inferences about what Ray was
> arguing and about what is in draft-cheshire-homenet-dot-home-03.  I
> hope the authors indulge me, and I hope you, Gentle Reader, do not
> mistake my inferences as speaking correctly either for Ray or for
> Stuart.  Since they're both here, they can correct what I get wrong;
> but I think trying to lay out this different story might help us.
>
> I think we all agree that the label home, in the top-most position of
> a domain name (but maybe not a name in the DNS), is in use by some
> people.  I think we all agree that at least some uses of that name are
> somehow related to "stuff in my house behind my home-router-like
> thing".  And I think we all agree that, whatever basis for that use
> is, it either is not or ought not to be related to any actual
> delegation of the name in the DNS.
>
> With the above premises, I conclude that home is by definition not
> suitable for our purposes.  I conclude that from these additional
> premises:
>
>     • that, given the detectable pollution of the namespace at and
>       beneath home, there is a significant population already using
>       the name for some purposes, we know not what;
>
>     • that if we want an identifier to be some sort of protocol switch
>       by which we tell software to do something novel, we need an
>       identifier that has at least a modest chance of not running into
>       widely-deployed use for some purpose not defined to be
>       consistent with the protocol switch;
>
>     • that it is at least fantastically difficult to suss out all the
>       strange things people are already doing with "in the wild"
>       undelegated names in the DNS, even if we make the dubious
>       assumption that there is something like a rigorous design behind
>       those doings;
>
>     • that strings that could be used as protocol switches are
>       fundamentally machine-directed rather than human-directed, and
>       therefore have a certain arbitrariness about them.
>
> With the same premises, I think the opposite argument is that home is
> entirely good for our purposes, because of the following additional
> premises:
>
>     • that we have (or we can get, which is what
>       draft-cheshire-homenet-dot-home-03 is asking for) a pretty clear
>       idea that all the uses of home are already more or less what
>       we're trying to do;
>
>     • that picking the same string is very unlikely to break any of
>       the existing behaviour;
>
>     • that a meaningful string to a human user is of high importance
>       here;
>
>     • that a primary (or even important secondary) motivation for the
>       allocation would be to capture traffic that should never have
>       been destined for the root in the first place;
>
>     • that with adequate documentation, a possibly-conflicting use of
>       home would not have negative effects.
>
>
>
>
> I think the effort to document what people are actually doing with
> home is laudable, and I hope it succeeds in producing a more-or-less
> complete account of the use of that name.  But I do not see how we can
> get from "documenting these uses is good" to "having documented it,
> you can then use the name that way."  The kind of exhaustive survey
> that would be needed to show the real uses of home would cost far more
> in time, effort, and money than the convenience of the string
> presents.  Moreover, it's not even clear that this would be the
> "right" string.  For lots of people on Earth don't use Latin writing,
> never mind English words.
>
> I hope this explains why I think proceeding with home is problematic.
>
> Andrew (speaking only for myself).
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>