Kim Davies <kim.davies@xxxxxxxx> wrote:
> 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.
It seems like it ought to pass out of IANA hands now, since we aren't using
it for infrastructure (Assigned Numbers).
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
