Michael: IANA are services provided by PTI, an affiliate of ICANN. https://www.iana.org/about See Policy Remit section. Btw: I do remember the discussions back when we introduced IPv6 multicast if/how we could have "commercial"/RIR based allocation of IPv6 multicast group addresses, and i was told none of them would want to bother with crap stuff like that. I can imagine that the answer to why .int would not go commercial beyond IANA would be based on the same commercial argument: being responsible to allocating only to international treaty org ... and getting a busines of 170 names within ca. 20 years - and doing it for free. Thank you, but thank you no. The commercial model only works when you have a combination of easily automated allocation (little/no complex checking) and crazy prices for stupid names. So there is actually a "don't design" area for name spaces requiring registries that we know could not be succesful commercially AND would be too costly for IANA to run. Given the current state of world affairs i'd also wonder if there are going to be any new registration requests for .int any time soon. I digress. Cheers Toerless On Fri, Oct 21, 2022 at 06:20:31PM +0200, Michael Richardson wrote: > > 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 =- > > > > -- > last-call mailing list > last-call@xxxxxxxx > https://www.ietf.org/mailman/listinfo/last-call -- --- tte@xxxxxxxxx -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
