IETF Logo Mail Archive

Re: [DNSOP] Last Call: <draft-ietf-dnsop-alt-tld-22.txt> (The ALT Special Use Top Level Domain) to Proposed Standard

Mark Nottingham <mnot@mnot.net> Mon, 13 March 2023 22:45 UTC

Return-Path: <mnot@mnot.net>
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 ABF88C15256E; Mon, 13 Mar 2023 15:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="cuKXTbrN"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="TB8PUA7k"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rssVvvLSj8WZ; Mon, 13 Mar 2023 15:45:35 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16037C13AE26; Mon, 13 Mar 2023 15:45:03 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2AF835C014B; Mon, 13 Mar 2023 18:45:01 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 13 Mar 2023 18:45:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1678747501; x=1678833901; bh=PC9LXaHPLBkFMlQGPiSEEnHWXmgoipEQsWg BsxNw2jE=; b=cuKXTbrNxcCsgMe0hjZgV7DvlfhUpYvZzGPtY34Xl7vAD3QuG1g /AQv3bQndv5RfopfNzhobjlaVk6OAmnhvibTGGA9FVKVoOay4TGcQekWZ/YQrgc4 DwP50Yg2MXfa3rTKKAPfmntZyudUYCUntdYv+2WCerhaaCKwE5ftK5Bn0g1nGHD9 2a7uQatjjKYzbFzeDIJGzqo+xY+y5N6yISEy8NlQkzyO6TBNRGWy7u1xaP7CuCOy RaWIT4NGBCZzjsrz2/1WNd6y6S6AYTvH3ydoIMQ4VQfxNISx2J3Ba4e0sGsonghu EMKnobxVRoRkY/z745BOA2gFlwyhgeLwKYA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1678747501; x=1678833901; bh=PC9LXaHPLBkFMlQGPiSEEnHWXmgoipEQsWg BsxNw2jE=; b=TB8PUA7k/e2tXsIw5F174aT4JDbHpkXUGIvHmfTbVFT4V0kBEuI tqfStqcg3MoVfB2H5lmNCGvtcq+IY1X0HchQiIt6JiIaO9fkK48Ji1zU6rklM0xX PCm5sgjX07/jVIrFmX4Olhx7Zht6dnTGo2byzXExOkli5AdnnQ8s+BHcRx5PiY16 feHwFcCuzMJ6myOxZO4DOcrOCj2AduGntihxcHz6DL7PR0AINP6TsCAiDr3v1wdp VNf2NNPSIP58GdeL3AdDipwk3o0wykHbdFxPYYmRSEOZwYrTzCPyYxXGFq58zQ79 J+vCjouoFPWql8C8yZoWNaklXqoTv7Bqwzg==
X-ME-Sender: <xms:bacPZB5i6ACBoBCQqHILO5aUaRLcL029OEesjJ0AfBRHCtB5oh_75Q> <xme:bacPZO7WturHW-K6PiRxpsheFtITLFu7TJBnm6G12HFBD9RxKEd-nL2QPT5N5SaX3 HKmw0ch4VrRjpi8fQ>
X-ME-Received: <xmr:bacPZIevu7NrAqKIjyHmPHWZ7F5b3fGFu4XPkLXXKvhv7z_l9CD_frLeKsFJTPeEpv3ia0f-b5X7rdK4rtiioebl-j-aSyIkFTYJ0kML4STosKR4NdPF6vLM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvhedgtdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjffevgffkfhfvofesth hqmhdthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothes mhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeejfedufeejvdfhkedvgefhgffgvd fhleffjefgtdekhfetvdfggfeifedvgfeghfenucffohhmrghinhepghhithhhuhgsrdgt ohhmpdhivghtfhdrohhrghdpmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:bacPZKJy9E2lAg5V2UbL73dPJxlNB7rDyFVeM-09tel1SY5CoX0Z9g> <xmx:bacPZFIfrjWYwxZfZVSP1a2WjcG13xO5l4WEu8KxXzCcsWx_Up8-uA> <xmx:bacPZDyexccobCzOpLOtzf0AvkHIE9zTTs4mBQrvwJyE34qWOMp_2g> <xmx:bacPZMUEi0KNHXGsGFrnknj-0DpWLLUB6mYjwTE_-NWeQTTHEIvvlw>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 13 Mar 2023 18:44:59 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <167871730036.24852.13348288925914031793@ietfa.amsl.com>
Date: Tue, 14 Mar 2023 09:44:37 +1100
Cc: dnsop@ietf.org, dnsop-chairs@ietf.org, draft-ietf-dnsop-alt-tld@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D721FC7F-C1EA-4903-9BC9-8EDE85FAD8F0@mnot.net>
References: <167871730036.24852.13348288925914031793@ietfa.amsl.com>
To: last-call@ietf.org
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gQHD14DRUJaxTwFdykypWzucKjc>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-alt-tld-22.txt> (The ALT Special Use Top Level Domain) to Proposed Standard
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 13 Mar 2023 22:45:39 -0000

This seems fine. 

I do wonder whether 'alt' is appropriate -- 'alternative' begs the question of 'alternative to what?' and the answer is a technical detail that most Internet users are blissfully unaware of. It seems to me that it'd be better to choose something meaningful to users.

That said, I struggle to suggest anything specific, and we have plenty of examples of seemingly-relative names still working in practice -- e.g., 'New York.'  

Cheers,


> On 14 Mar 2023, at 1:21 am, The IESG <iesg-secretary@ietf.org> wrote:
> 
> 
> The IESG has received a request from the Domain Name System Operations WG
> (dnsop) to consider the following document: - 'The ALT Special Use Top Level
> Domain'
>  <draft-ietf-dnsop-alt-tld-22.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2023-04-10. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   This document reserves a TLD label, "alt" to be used in non-DNS
>   contexts.  It also provides advice and guidance to developers
>   developing alternative namespaces.
> 
>   [ This document is being collaborated on in Github at
>   <https://github.com/wkumari/draft-wkumari-dnsop-alt-tld>.  The most
>   recent version of the document, open issues, etc should all be
>   available here.  The authors (gratefully) accept pull requests. ]
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

--
Mark Nottingham   https://www.mnot.net/

v2.23.0 | Report a Bug | By Email