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

james woodyatt <jhw@google.com> Mon, 12 December 2016 21:56 UTC

Return-Path: <jhw@google.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 85C2B129793 for <homenet@ietfa.amsl.com>; Mon, 12 Dec 2016 13:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.896
X-Spam-Level:
X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 Ur8ia_52FsoG for <homenet@ietfa.amsl.com>; Mon, 12 Dec 2016 13:56:48 -0800 (PST)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::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 D273212945C for <homenet@ietf.org>; Mon, 12 Dec 2016 13:56:48 -0800 (PST)
Received: by mail-pg0-x22e.google.com with SMTP id 3so39621708pgd.0 for <homenet@ietf.org>; Mon, 12 Dec 2016 13:56:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:message-id:mime-version:subject:date:references:to:in-reply-to; bh=YritT9UVdm3oysOKSU8AxKcbu30mXw4pLBPG2oyyC1o=; b=EgOW16k2a3ReM/jBbZQzR62Mqa3apMAi1B49q2biW9pdh1AzHiaiIHrVacUysuOlFi 3ok7+7LlVbNgtOLEgvrS2d4IcyHcjKTlizHSCkQuUI30iWahvvdZ3Wpx8iaQVYvCT/KB sM2zMscSiHID8nJeSc+b5LLgKBgnlM4yQNP9R84+a+/GVGemJtDqa2qBE7adQlb7Xkhg /ei0Hr3CxxB1Nqkkc61JiYJWqA2jg6k4h468FG8zyv0BSaS/gae9yxoVZxsvtb3p4H1b gXIE5UsiuVSO0vr1Q7XsdnQjMt4hD3d+zm9kP7zDq8dH/4jbyKJByGEXEKUtI5EHgG0v /rWA==
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 :references:to:in-reply-to; bh=YritT9UVdm3oysOKSU8AxKcbu30mXw4pLBPG2oyyC1o=; b=iqGkJMCVgX/GDZByxOJF+v9vXky8FGQOywkVmCVuQBxjyo5IH4rCUc2+wX1dY6UwOy fa+oQqoMEolnPt1Hp3CF4TDLm84XULcQEsqKtU72+f8SSgOEfw/GDUNKaupMLWDFFcx6 usydp721RUjzgE3gsvEGTmnrqRN05uATaUC5VbXXAcrYpRiRsazIMU0WPyBHj3uympWt QOCV+PU3YTnJ6sy2qDgAsK/weivEgAqvml9k+3qWmlNtE84oCv2kclLlnhHRoXMhTImk FaXp4U+Xpwl+j9nioku4Gklsz2H3LoTMTE+DdvI6osqKtSOq+9rwEBlUjuWB0z8BwoFP KyqA==
X-Gm-Message-State: AKaTC0026/yMOaifpVieAOgKMjrqnFnzAvXTlcHN2OGTgZ/NaqzePOSeabo3YNQ8NK7Cmamj
X-Received: by 10.99.127.72 with SMTP id p8mr170828018pgn.183.1481579807972; Mon, 12 Dec 2016 13:56:47 -0800 (PST)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id 65sm77780094pfn.12.2016.12.12.13.56.47 for <homenet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 12 Dec 2016 13:56:47 -0800 (PST)
From: james woodyatt <jhw@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_87FB80DE-6F9E-43C9-8F0F-178027ABB4C2"
Message-Id: <FF4DCC21-3FD2-4130-A2E4-E8D8E4EBCD72@google.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Date: Mon, 12 Dec 2016 13:56:46 -0800
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> <585D7369-28A8-4B6D-BE77-C94B42CA4432@google.com> <20161212202542.6596A5C871B9@rock.dv.isc.org> <F256B003-68A8-4C42-9A3D-4CBD4412FD90@google.com> <CAPt1N1kzFZzfGxphF9Jm1wDLbGxk7OZvCMhjZHNjXtEt6bJJtQ@mail.gmail.com>
To: HOMENET <homenet@ietf.org>
In-Reply-To: <CAPt1N1kzFZzfGxphF9Jm1wDLbGxk7OZvCMhjZHNjXtEt6bJJtQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/WhEtkzJkk4Ld7dnDdXGeSazbjzU>
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 21:56:50 -0000

On Dec 12, 2016, at 13:32, Ted Lemon <mellon@fugue.com> wrote:
> 
> That is not an option for this working group.   Whether or not it is a good idea is another topic, but that option is definitely not an option for this working group, because it is not in our charter.   If some other working group _had already gotten_ such a TLD, then we could talk about using it, but placing such a process in the critical path doesn't make sense.

The procedural argument for using a special-purpose gTLD (instead of assigning IETF with a new general-purpose gTLD and making a special-purpose subdomain of that) seems to rest on language in the charter that I would think is pretty broad, and maybe broad enough to think it’s really either “both" or “neither" that are really in the charter.

>> The working group will also liason with external
>> standards bodies where it is expected that there are normative
>> dependencies between the specifications of the two bodies.

I say this because I’m really not thrilled by the prospect of *this* (from your original message):

>>> 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.

That “possibly several years” bit is what really stopped me in my tracks.

I would strongly prefer that we avoid the risks above by using a special-purpose subdomain of a gTLD owned by IETF. I don’t really care which gTLD we use, and if “arpa” is really the only reasonable choice, then so be it. However, I can imagine a world where the Working Group decides that “arpa” is unacceptable for whatever reason and decides that it’s better to wait until IETF has another domain with a better name. And I’m not ready to tell them I think that would be a very bad idea.

Actually, I think it’s probably a very bad idea. But, I’m in favor of using a subdomain of “arpa” instead of some new gTLD, so I’m already in a minority, and I’m prepared to lose that argument.


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>