IETF Logo Mail Archive

Re: [Last-Call] [Ext] Re: Last Call: <draft-davies-int-historic-04.txt> (Deprecating infrastructure "int" domains) to Informational RFC

Kim Davies <kim.davies@iana.org> Wed, 19 October 2022 22:12 UTC

Return-Path: <kim.davies@iana.org>
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 C9CE3C14F737; Wed, 19 Oct 2022 15:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 gDduJfnTuqbV; Wed, 19 Oct 2022 15:11:57 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 475A8C14F6EB; Wed, 19 Oct 2022 15:11:57 -0700 (PDT)
Received: from KIDA-9190.local (unknown [10.32.60.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lax.icann.org (Postfix) with ESMTPS id BEDACE3A57; Wed, 19 Oct 2022 22:11:55 +0000 (UTC)
Date: Wed, 19 Oct 2022 15:11:52 -0700
From: Kim Davies <kim.davies@iana.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: last-call@ietf.org, draft-davies-int-historic@ietf.org
Message-ID: <Y1B2KEoXO1fodrqh@KIDA-9190.local>
References: <166621075802.44847.14382611991776479938@ietfa.amsl.com> <371922.1666215280@dyas>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <371922.1666215280@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/3NMeKzv8TQl8tYoVF5v2i0P52AA>
Subject: Re: [Last-Call] [Ext] Re: Last Call: <draft-davies-int-historic-04.txt> (Deprecating infrastructure "int" domains) to Informational RFC
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 19 Oct 2022 22:12:01 -0000

Hi Michael,

Quoting Michael Richardson on Wednesday October 19, 2022:
> 
> So, I understand that none of our infrastructure has been in .int for some
> years (decades even).
> 
> The document says:
>    In conjunction with this change, the eligibility for "int" domains was
>    limited to only intergovernmental treaty organizations.
> 
> I think that, after approval, that this use for int will remain, and the
> management of it will fall to, I guess, ICANN, as yet another TLD?

The .INT domain has been operated as part of the IANA functions and
that will continue as-is. This activity is limited to tidying up some
obsolete second-level domains within .INT.

kim

v2.23.0 | Report a Bug | By Email