On Sat, Oct 22, 2022 at 1:56 AM, Michael Richardson <mcr+ietf@xxxxxxxxxxxx> wrote:
Toerless Eckert <tte@
cs. > wrote:fau. de Michael: IANA are services provided by PTI, an affiliate of ICANN. https:/
/ www. iana. org/ about Yes, I forgot that IANA and ICANN are so close.
Yup.
In the IETF we naturally think of the IANA as "those nice people who hand us the next code point in the Foozle Whatzit registry when we ask, and also keep careful track of which ones are already assigned, etc." - but they actually much more than this, and have more "customers".
For example, the IANA is "operate[s] and maintain[s] a number of key aspects of the DNS, including the root zone, and the .int and .arpa domains."[0], and well as being the "operator of the Key Signing Key"[1] and running the "Key Signing Ceremonies"[2], as well as the arpa servers.
They also "managing Internet number resources is to provide pools of unallocated IP addresses and AS numbers to Regional Internet Registries (RIRs)"[3], and also maintain the "Time Zone Database (often called tz or zoneinfo) contains code and data that represent the history of local time for many representative locations around the globe"[4], etc.
The protocol registries (https://www.iana.org/protocols) that we usually associate with "the IANA" is only a small part of their function.
(I'm sure I've summarized / worded some of the above poorly)
But, I was imagining that it would be passed by ICANN to some like the UN, if not the actual UN. But, as has also been pointed out, it's not our business.
Yup. The way that I was viewing the document, it all basically boils down to:
"We used to put subdomains under .int, but we are no-longer using them. For the last many years, when we need these sorts of infrastructure names, we put them under .arpa."
The color of this particular bikeshed, who should paint it, and who is allowed to store bikes in it, is, thankfully, not really our concern.
Amanda and Kim started this whole document quite a while back, and it's a housecleaning / tidying up / documenting current realities document.
As Brian said: "Personally I'm very grateful to Kim and Amanda for tidying this up for us."
W
I agree with some comments that we should have no text about what .int is for, just deprecate our usage of it.
--
Michael Richardson <mcr+IETF@sandelman. >, Sandelman Software Worksca
-= IPv6 IoT consulting =---
last-call mailing list
last-call@ietf. org
https://www.ietf.org/mailman/listinfo/last-call
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
