Re: [homenet] WGLC on "redact" and "homenet-dot"

Ted Lemon <mellon@fugue.com> Mon, 12 December 2016 16:48 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 4E4F21295AD for <homenet@ietfa.amsl.com>; Mon, 12 Dec 2016 08:48:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 nzN9Sp1qksZy for <homenet@ietfa.amsl.com>; Mon, 12 Dec 2016 08:48:39 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 7DC9C129DDB for <homenet@ietf.org>; Mon, 12 Dec 2016 08:44:41 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id w33so81114269qtc.3 for <homenet@ietf.org>; Mon, 12 Dec 2016 08:44:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=WQLXrTe9Df3Io25i4gH3lZszh/FF2p9zcgOjLYBD3AU=; b=nN95vgmczBdAg+EsFOmW8OzF7VXou4p5eykjriVquhFQheLZnfukYLhnhMi0/xVf4q zOyz8r+OGghCb1mdTPZLZtFp4H/gKQk8bFI22IhtFL9MyGOgGJaLPVTykA3knCjrq3fj D/J9HTyqrfLQUzvvHG7QBH7w5Zv0PCqLDq1bsMV9DCeHcL+bKtoktfCNfDmzHxny/JU4 mlLtVVc6ulXIIaXsMOYG+Sib45ZhC6HbqjVDkPy/jgLUSa0wdZPeSCChFi8VqGx9vKcY X8gOIK2Vm72uDwKrqDSFa8rFgBRC0W4COC0o7I366XuRGHfmuIS0Xk34doOnAW2SlEgk t4Yg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=WQLXrTe9Df3Io25i4gH3lZszh/FF2p9zcgOjLYBD3AU=; b=eHl2kPC5TQI86bp/6dudOBmRxwgzacrK6rbwEymUls3iuP6g6WQB61xJtp9ihDz6mg 8USE3Tkej6Y//wa6zjvxBn4oTzurtyuadnIFCd4lXaIKVBLYzjXUwGeX6n9gTSENHaye 5CBjnTQ6RX1z+Kl3NHsGusbPd6Z5MTX/a/06qK2fZaasLepwbujyjuBP/5229AxXQyBk 7+xrnpyV8T8nvv+wNZdrzvpAbzIATD2QmuooBX6E8E/WnlMizS/6ebMXSlybJyoCY2RS IXa7Xtmav9hIOwHapU+Xpn0ipUQk0X7v6QiGtnLfBtnHcBY5Vo+opVY/OkYpMhjZBUYZ S9BA==
X-Gm-Message-State: AKaTC01l8C/JvADm+2mUljdYvT6zat+AYLHL5Wcrifi2uB0Y+BMvbUwcpfhXJV0FsM6bkg==
X-Received: by 10.200.49.247 with SMTP id i52mr79344576qte.108.1481561080694; Mon, 12 Dec 2016 08:44:40 -0800 (PST)
Received: from [192.168.1.229] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id b63sm26757810qka.39.2016.12.12.08.44.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Dec 2016 08:44:39 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <947F5300-67C6-4293-A27E-77295459290A@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F3863A06-C9F2-4B3A-831B-971F8E3912FB"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Date: Mon, 12 Dec 2016 11:44:38 -0500
In-Reply-To: <4C14E0EB-735E-4D21-8DB0-F7944F8AB4D0@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
References: <4ab2a538-603e-4e7a-3be9-ad75ed459006@bellis.me.uk> <B192A1B3-03FF-43D1-AD30-12BBA2D65DF0@gmail.com> <9fe0e34d-51e9-bdf3-a650-d8b3681f1cd8@bellis.me.uk> <CAPt1N1=Z2xERw68-=iFGgYYnEO3eDW-8tvhmTmaf4+vU-24grQ@mail.gmail.com> <4C14E0EB-735E-4D21-8DB0-F7944F8AB4D0@gmail.com>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/34NpjyOxHDKS7ev6gtodQVwjrHU>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] WGLC on "redact" and "homenet-dot"
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: Mon, 12 Dec 2016 16:48:41 -0000

On Dec 12, 2016, at 11:29 AM, Ralph Droms <rdroms.ietf@gmail.com <mailto:rdroms.ietf@gmail.com>> wrote:
>> There are two approaches we can take to this.   One is to proceed--ask ICANN to do the delegation and see what happens.   The other is to take the more expedient, less satisfying approach: use .home.arpa instead of .homenet.   I'm not in love with this as an end solution, but it has the advantage that the IAB controls .arpa, and so we can get an unsecure delegation right away assuming the IAB agrees.   I see no reason to think they would not.   It's a bit more typing, and there is the problem that the fourth google result for arpa is "Advanced Research Projects Agency.   But it would work, and quickly, and would keep the whole process in the family.
>> 
>> The other alternative is to continue with the original plan: do the special-use names registry allocation, and send a liason to ICANN asking them to do the unsecure delegation.   The downside to this approach is that we won't know whether the outcome will be success or failure for a long time, possibly several years.   And the outcome could very well be failure.   The upside is that we get the name we all want; the downside is that we are a long way down the road with no win.
> 
> So, now I’m a little confused by the alternatives; for clarity, does the paragraph that begins “The other alternative” refer back to the “ask ICANN to do the delegation” approach?

Possibly I could have proofread that one more time before I sent it.   The other alternative that I am referring to in the second paragraph is the first alternative I referred to in the first paragraph.   That is, _not_ the expedient version.

>> I should point out that whichever way we go, we already have solved the immediate problem: we have a name that HNCP can use, the potential liability for IETF is dealt with, and our prototypes can be made to work.
> 
> Are you referring to “.home”, “.homenet”, “.home.arpa” or some other name to use as the HNCP default?

What I mean is that whichever alternative we proceed with, we can use that name as the new name to put into the HNCP spec.   So either .homenet or .home.arpa.