- Impact
- 23,153
Deprecating infrastructure .INT domains
I wanted to draw your attention to an Internet Draft we’ve developed, its goal is to formally deprecate a number of historic “.int” domains that were designated for Internet infrastructure purposes decades ago and appear for all intents and purposes obsolete. After some limited consultation on developing the approach so far, it would be useful to get some additional eyes on it so we have greater confidence there is nothing we’ve missed.
You can find the draft at https://www.ietf.org/archive/id/draft-davies-int-historic-01.html
It’s a short document, but at its heart we’ve identified the following domains that are referenced in places but seem to be obsolete:
atma.int, ip4.int, nsap.int, rdi.int, reg.int, tpc.int
Most of these are not delegated in the int zone any longer, but there are lingering references online to them.
https://lists.dns-oarc.net/pipermail/dns-operations/2021-October/021418.html
I wanted to draw your attention to an Internet Draft we’ve developed, its goal is to formally deprecate a number of historic “.int” domains that were designated for Internet infrastructure purposes decades ago and appear for all intents and purposes obsolete. After some limited consultation on developing the approach so far, it would be useful to get some additional eyes on it so we have greater confidence there is nothing we’ve missed.
You can find the draft at https://www.ietf.org/archive/id/draft-davies-int-historic-01.html
It’s a short document, but at its heart we’ve identified the following domains that are referenced in places but seem to be obsolete:
atma.int, ip4.int, nsap.int, rdi.int, reg.int, tpc.int
Most of these are not delegated in the int zone any longer, but there are lingering references online to them.
https://lists.dns-oarc.net/pipermail/dns-operations/2021-October/021418.html
Last edited:
