[DNSOP] private-use in-meeting chat comments

Brian Dickson <brian.peter.dickson@gmail.com> Tue, 17 November 2020 06:56 UTC

Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC7C3A10BF for <dnsop@ietfa.amsl.com>; Mon, 16 Nov 2020 22:56:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 UaHsTGNBxMoM for <dnsop@ietfa.amsl.com>; Mon, 16 Nov 2020 22:56:48 -0800 (PST)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 D84933A10AA for <dnsop@ietf.org>; Mon, 16 Nov 2020 22:56:47 -0800 (PST)
Received: by mail-vs1-xe2a.google.com with SMTP id m16so10513663vsl.8 for <dnsop@ietf.org>; Mon, 16 Nov 2020 22:56:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=BgOLG73rMVU8CE3iotDMxFDD3vg9aPR7ExJb8DKuUpc=; b=ZfLYhkF3JYOwwid7ZQAYvK88C6sllUrj5ocy1O3H9FGn5zE4iP8Pjlhlc4afptaqCj wjzR7Yt5k2C6C4wXbX5g4bFHgp3mwxXDKYkEWhMBpOQtYGwh3B0Rd3alq4YJAJ10ZUC4 o2F7Y2tdjpF96EcIrIVsy8wUhFlmh18VEV5WSl9110UrU7/pdQ1mS3Iqva6FfhpIzW7/ nBdMEf+0Cm3Iwd2uIfKZGQtomCcbG7eWog78vgYzOFcoovQiSpXg4cZmRLekA1gy0tUr s0Qtf5KGU5I8BGmZsbDkK2vinvr3/tQxC4kjSXPncjNcsj/TrX1KaTCEVkbuWinKFrjr KJcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=BgOLG73rMVU8CE3iotDMxFDD3vg9aPR7ExJb8DKuUpc=; b=D8ZvXHq7nrDtkiuejqTTtHm1FYRy0JyngSkw8fwXFkseg8i8F4UU817BO9Xk6XLRWa iyB9hO0vUKCCCkQ7XjQadv20/pdBNvqZyLLvGv+HfOja/h7+ZQo2jTz3swPI7WilDgo9 lTZykqgtQxdWpeY/Bx0rzaxJolNu1krYAtN8EgZCWjjvHuV62HOkCCIy9ka+cHD2jFUj ypBOI1UuQTD5zE8MU5Xhjg3z3EB7lL49XoZlDbWfIrOYmodlMCcO7cltRl4C2k3CWulJ 6AElO01sQb7ZzLB1U+G9nzke8z79jeagOTCGIZCdvqnsDFfmvyMknBuGFtKlxh2pDyXl iYeg==
X-Gm-Message-State: AOAM532jUJu4BFAtHRdhSMpIJBrjlxBoVjGwnrvFTVMpcrYbBIH9LVpN 7BV7JZF1iKfz+2jsitYw2dETzChkAq5CJTb/Yx+Kkjj0Zco=
X-Google-Smtp-Source: ABdhPJwBNf42jQYiwH89vF9pAMlte6dEGg8UssrRbNm7PkQsLnTFl+ROMO2BofjzXlIJ8q+OULfushFDOCMp/qnPOrY=
X-Received: by 2002:a67:fb87:: with SMTP id n7mr10398511vsr.58.1605596206602; Mon, 16 Nov 2020 22:56:46 -0800 (PST)
MIME-Version: 1.0
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Mon, 16 Nov 2020 22:56:35 -0800
Message-ID: <CAH1iCirk5X9xOFmABQU9X9G92eQrePPuOwgXVHd4zza4kK9SwA@mail.gmail.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008c1e3505b447fffc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/T6esi7VXGH2FxxxM_XSD7spEKGw>
Subject: [DNSOP] private-use in-meeting chat comments
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2020 06:56:50 -0000

Comments made in the chat, about the private-use presentation/draft:
Me:
One potential approach is to say (in the RFC) that one of the two-letter
reserved codes should avoid name collision by putting a collision-resistant
second-level label, below .zz and above the private use usage (and use that
particular two-letter code in that manner exclusively).

E.g. whatever-i-want.guid-as-label-to-prevent-collisions.zz rather than
whatever-i-want.zz

Warren:
@Brian: Yes, but as you know (being a registrar), people really want
semantically meaningful names... People have seen using www.corp, not
www.dfads3e4r34324rwefe.corp..

Me:
Correct, and I think possibly providing guidance that this private use
SHOULD be generally limited to "magic" things like automation or
automated/negotiated systems. The UI can/should hide the GUID component and
possibly also the zz TLD

Ben:
That could be $guid.guidspace.arpa, no need for .zz
"guidspace.arpa" is not a thing. I'm just suggesting an adjustment to
Brian's proposal.
Me:
That's a good idea, can be pursued independently of the private-use TLDs
like .zz
(possibly addressing different use cases?)

Brian