Re: [Last-Call] Last Call: <status-change-int-tlds-to-historic-00.txt> (Moving TCP.INT and NSAP.INT infrastructure domains to historic)

S Moonesamy <sm+ietf@elandsys.com> Thu, 31 March 2022 14:20 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78F553A1941 for <last-call@ietfa.amsl.com>; Thu, 31 Mar 2022 07:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.707
X-Spam-Level:
X-Spam-Status: No, score=-6.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 2KYkmV5YLLkP for <last-call@ietfa.amsl.com>; Thu, 31 Mar 2022 07:20:47 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B69D3A19A3 for <last-call@ietf.org>; Thu, 31 Mar 2022 07:20:47 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.1.235]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 22VEK7Cg005516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Mar 2022 07:20:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1648736437; x=1648822837; i=@elandsys.com; bh=LbN6a4AujV17/PoUCtpWCpjYUBdV1yEUxKUN+pS2WmY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0jTxV4gy8aGyD9Zp1aS2d9lV0muLNARDH4jsEn6BuWmoRO3pLA1JWaL6QMX1aQjpe ZhItrL8GLnSJZxFHTmSd2a8o2j+1JD9NRDqp6jcKvxN157JuvQ8kR6O/V87BpW8oU9 TGH79/SYptxQjaJyHmYwlmuFZ7N1fkUn2j77moOU=
Message-Id: <6.2.5.6.2.20220331063526.07f88b38@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 Mar 2022 07:18:53 -0700
To: Joe Abley <jabley@hopcount.ca>, last-call@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <D224B6D3-762A-4254-883E-BAB7C8712048@hopcount.ca>
References: <6.2.5.6.2.20220330004724.07d61520@elandnews.com> <D224B6D3-762A-4254-883E-BAB7C8712048@hopcount.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/ujDzBXaO9eeSE5KazQ-FQOEiQQU>
Subject: Re: [Last-Call] Last Call: <status-change-int-tlds-to-historic-00.txt> (Moving TCP.INT and NSAP.INT infrastructure domains to historic)
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2022 14:20:53 -0000

Hi Joe,

Thanks to Brian for the pointer.

At 02:04 AM 30-03-2022, Joe Abley wrote:
>For some reason I didn't see the original message, and searching 
>datatracker.ietf.org for "status-change-int-tlds-to-historic" 
>reveals no documents. So I am replying to what I have, but perhaps 
>matters have been overtaken by events.

I was able to reproduce the problem described above.

>I suspect the IESG can declare its published documents relating to 
>that domain to be historic which will aid the administrators of the 
>INT domain in making decisions about the remaining delegations. At 
>least some of the names attached to the TPC.INT project are still 
>eminently contactable and it seems entirely plausible to me that a 
>friendly consensus could be reached amongst everybody concerned.

The documents relating to the domain are not IESG-approved 
documents.  They are not covered by the agreement which supplements 
the ICANN-IETF MoU signed between the IETF Administration LLC and the 
Internet Corporation for Assigned Names and Numbers.

>It is not uncommon for there not to be an obvious single point of 
>policy administration when the closer you get to the root of the 
>namespace, especially when you stir in ideas and services conceived 
>in a gentler, more informal era.

Yes.

>I don't think it's necessary for the IESG to claim or try to exert 
>policy control over the INT or TCP.INT domains for a measure such as 
>I imagine this document might be taking to be useful.

The IESG will be asserting policy control by moving forward.

Regards,
S. Moonesamy