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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux