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

[Michael Richardson <[e-mail]>]

The IESG <[e-mail]> wrote:
    > 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
    > [e-mail] mailing lists by 2022-11-23. Exceptionally, comments
    > may be sent to [e-mail] instead. In either case, please retain the
    > beginning of the Subject line to allow automated sorting.

    > Abstract


    >    The document marks as historic any "int" domain names that were
    > designated for infrastructure purposes, and identifies them for removal
    > from the "int" top-level domain.  Any implementation that involves
    > these domains should be considered deprecated.  This document also
    > marks RFC 1528 and RFC 1706 as historic.

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?

At first reading, it seemed like we were removing int entirely, but upon more
careful reading, I see that we are just removing our infrastructure
delegations.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [