Re: [DNSOP] [homenet] My assessment of .homenet as described during the WG session yesterday.

Mark Townsley <> Wed, 29 March 2017 22:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 03C121294F9 for <>; Wed, 29 Mar 2017 15:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bkZFf1TLsK_J for <>; Wed, 29 Mar 2017 15:07:24 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1214A126C23 for <>; Wed, 29 Mar 2017 15:07:24 -0700 (PDT)
Received: by with SMTP id 21so19673735pgg.1 for <>; Wed, 29 Mar 2017 15:07:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pecWafBs4689stiQ6yMyIiVt4BBbB0rboHNc/GAxmGA=; b=Wpu4ULlPJoFp1WZTYXtEXqHtx202UkZL+HhUq5hch8q7EB7zy5F3sVGGfXBkAXQLfQ tvTm9ZM7S71ycq+dGqDCMOQ12tOdfRL1CyyEAYRKeBiyfivWl/TUUkYCXzOXtl3FURV9 Po49Ov/A0yWTtEU3F8ANly5XjIz6HoUlXZBwSzbx6Vm5QQr/GjotrDGHio6ho3FG+X5Q R+jNPOjHUqWpeg6a29ModQuA+LPMkKDIaqd0Kdba8CNRpnIvNSDgvjnHuFGg09StE+pc o8oxDDn3/EWf+k1OvHauX+rqbXzkPWd1WSlrjVd0XrsZUS4HeFcYy0Tq1ngnovsDmiPS Xzdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pecWafBs4689stiQ6yMyIiVt4BBbB0rboHNc/GAxmGA=; b=CD5a2WmbywiPprrvAhsPVDhh5KVPhP7o3wo4GOSgtAlTL7XCk1kXb13L/wX7y/IHhe cTRt5eAvOCIXyyr2jqPgFWwwd+VHvoZ3MOYMu1aib51BvUpbzXFjP6BZpkorxP4Ml/kn IJC31CbS1PXY5c3FHsrPxS9lGTvRXxweF+mZ10l15LhgkWq+Rlu81FzA/iry+kaFFvnM NrOcocAFAhb0sfAYaHIXhB32OwkSDxfJ8sUc3G7mA0GSTGApyup6VTHUAPZAP2x7BIrd minxqktyNvUqhqu7xxqoXMXOMbDxTjan7gw4yA7PwnKJwjwVwd3NOn1HY90R2kX/yl2e yACQ==
X-Gm-Message-State: AFeK/H0S1bfrMUMw/0Xc/dfCigwv5yiEUwunIss7GAKVkPBFk7bIJWlIonTxA6PeX8Pg3g==
X-Received: by with SMTP id i8mr2823186pfk.120.1490825243662; Wed, 29 Mar 2017 15:07:23 -0700 (PDT)
Received: from ?IPv6:2001:420:c0cc:1006::cf? ([2001:420:c0cc:1006::cf]) by with ESMTPSA id s11sm172482pgc.61.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 15:07:22 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Mark Townsley <>
In-Reply-To: <>
Date: Wed, 29 Mar 2017 17:07:15 -0500
Cc: Terry Manderson <>, HOMENET <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Michael Richardson <>
X-Mailer: Apple Mail (2.3259)
Archived-At: <>
Subject: Re: [DNSOP] [homenet] My assessment of .homenet as described during the WG session yesterday.
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 29 Mar 2017 22:07:26 -0000

> On Mar 29, 2017, at 10:07 AM, Michael Richardson <> wrote:
> Terry Manderson <> wrote:
>> B) seek a .homenet special use domain WITHOUT the delegation request
>> AND ask the IETF/IESG/IAB to commence the discussion with the ICANN
>> community to achieve an insecure delegation
>> c) seek a <SOMETHING>.arpa insecure special use delegation
>> d) go for "B" and if that doesn't work shift to "C"
> Is there some reason we can not proceed with "C", concurrently with (B).

I think that would require a new consensus call. There was a lot of work done to get to the point of agreeing on a path forward at the last IETF, and this path would be rather different than that.

> This might cause stub resolvers to have to have two cases
> (, and .homenet) eventually, but at least we could deploy
> and attempt interop with NOW, and it would more clearly
> permit "home." to be removed from code.


I don’t think we want to have two defaults in our specs. It’s bad enough that we are already going to end up with .home and .homenet depending on the version of code used or forked from, I really don’t want to do anything that could lead to a third if we can avoid it.

- Mark

>> Again, this situation is fluid and as discussions evolve I will provide
>> more information when it is appropriate. In the mean-time I would very
>> much like everyone to take a calming breath and understand that I am
>> taking a very pragmatic view of this concern.
> Thank you!
> --
> Michael Richardson <>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> _______________________________________________
> homenet mailing list