IETF Logo Mail Archive

Re: [DNSOP] Questions on draft-ietf-dnsop-private-use-tld-01.txt

David Conrad <drc@virtualized.org> Thu, 29 April 2021 00:43 UTC

Return-Path: <drc@virtualized.org>
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 8C3EF3A276B for <dnsop@ietfa.amsl.com>; Wed, 28 Apr 2021 17:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=virtualized-org.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 WLMquu-HaO5D for <dnsop@ietfa.amsl.com>; Wed, 28 Apr 2021 17:42:59 -0700 (PDT)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 4EB363A2740 for <dnsop@ietf.org>; Wed, 28 Apr 2021 17:42:59 -0700 (PDT)
Received: by mail-pg1-x52d.google.com with SMTP id q10so45942369pgj.2 for <dnsop@ietf.org>; Wed, 28 Apr 2021 17:42:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtualized-org.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=LY+/+I3TnLZnIXwcxdV5DPVTa6CFESvNLEZSnF7WvS0=; b=PQBRuZ60QIFdaoe7YU9FE634CR89hOs4PCgelQDFYxEwwfP+DXIw3D0vhA8/E8c/Cl Wl8sSpdugdQ7QuD/UEnpP3mNnXRgbPBcT/K8Xl+cgBIQJAFe6l8XB5PrzyYRxL94LWij 6ByR99wq+gfdFiS8+kwxI0A2ACxZ9FvsdhRx3XgH1gWun8KXvyIQYIa41Katp+8sMARj AcQhTXmJ3uq805gtPJLb7lp0FPt+GlwKxxC7T2qfOQxad8CMzQtyQGQeX3GloXVqMXNk oHtNYat0TlhhEvtP943qPdcwK1irO9vuz1hq4zQp4afAZ4VNI82pD5IRu5jLMltuSeio U8eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=LY+/+I3TnLZnIXwcxdV5DPVTa6CFESvNLEZSnF7WvS0=; b=CKap762qxL4IA/w4cS3LE+YISDnReccnALvhl1A27Z4xi/ZL2I7Av/dhKro4DapEtV kBRGDMlV/ZaeRKgSUaU4wPBw7T2tRqGjdoUzjOI17Jz/aiSFj7lJuKrS7794J2l8BPzk pT5oZyy9LchHKsr86erUkepDSwDVVXeOabw69nkq9VRiUbotn7zoRcK9yxEJNdDVvTsg oa5h5Ix7oWCuFCrIuHmbe7ACZYBEjfSJrnLoMpsbVuKZ+uWrVEuoe8gzMv6pqyvqxAGx KN7db9z80D94QX6m6RNc1Rsy1fAkZAmTR/Tw1TL7AfNE/+peQImTkqPX53jogLbV3bCI dySg==
X-Gm-Message-State: AOAM5307eUiwk2bcfSLZvk5oPOSJFt0DwN4NPunsTqh0wdd1QfbcvRn8 fVwm5o+rOTjmUDWXZSL3AMHZ6u8U0DMkhk57
X-Google-Smtp-Source: ABdhPJz0YlFEC0gjw3kcmSi+nEwj8BCqCoU4y91Fi8e/KxmgorLlF0SsECBOlXBcpRt/QsKINdddgw==
X-Received: by 2002:a62:7d46:0:b029:247:baa2:d95c with SMTP id y67-20020a627d460000b0290247baa2d95cmr30396219pfc.15.1619656977842; Wed, 28 Apr 2021 17:42:57 -0700 (PDT)
Received: from smtpclient.apple (75-12-19-168.lightspeed.irvnca.sbcglobal.net. [75.12.19.168]) by smtp.gmail.com with ESMTPSA id w74sm416888pfc.173.2021.04.28.17.42.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Apr 2021 17:42:57 -0700 (PDT)
From: David Conrad <drc@virtualized.org>
Message-Id: <72F10A33-77AE-408A-85C5-EDB85D2D01A5@virtualized.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_E908301F-3091-48D3-9CC0-98F7693AEAD6"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Date: Wed, 28 Apr 2021 17:42:55 -0700
In-Reply-To: <284547BD-6A60-4B9F-9E71-5F79B2174B4B@rfc1035.com>
Cc: dnsop <dnsop@ietf.org>
To: Jim Reid <jim@rfc1035.com>
References: <161805873252.19178.11471347094062424385@ietfa.amsl.com> <88395F35-AF22-489C-B9D6-2FFE4EB1A767@depht.com> <5F3F8198-23EA-4BA9-A07E-EF7AB035CE72@icann.org> <CAF4+nEFxggFvT-x7L-iqYxT0MTA5ODrR8BLx35VvQdzsmHt89A@mail.gmail.com> <A051DC33-EDF1-459F-B964-11BD05E4C3CB@dnss.ec> <284547BD-6A60-4B9F-9E71-5F79B2174B4B@rfc1035.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ABzxmYLIPhAJMoTS_iIXIC9jAaw>
Subject: Re: [DNSOP] Questions on draft-ietf-dnsop-private-use-tld-01.txt
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: Thu, 29 Apr 2021 00:43:11 -0000

Hi,

On Apr 28, 2021, at 5:38 AM, Jim Reid <jim@rfc1035.com> wrote:
>> On 28 Apr 2021, at 13:24, Roy Arends <roy@dnss.ec> wrote:
>> The working group can (after a potential clarification from the ISO about the future status of code elements) decide if a subset suffices and if so, the composition of the subset.
> 
> I agree with this approach.
> 
> IMO it’s reasonable for the WG to produce an RFC which says “If you need a TLD for private use, pick from the two letter codes that ISO 3166 MA says they’ll never allocate. Bear in mind if they later change their mind, you’ll be on your own and could well be in a world of pain. Have a nice day.”.

I’d agree, with the slight modification of:

“…  if they later change their mind, you and any of the unmeasurable number of folks who happened to listen to ISO-3166/MA regarding the status of the user assigned codes will be on your own and could well be in a world of pain.”

(Only half :) — the reality is that lots of folks use the user assigned codes for all sorts of reasons and if they’re repurposed, it’s probably going to be a mess).

Regards,
-drc
(Speaking for myself)

v2.23.0 | Report a Bug | By Email