On 10/19/2022 8:35 PM, Scott Bradner wrote:
.int domain is in use - see, for example, itu.int
the IETF can clearly ask that any .int second level domains that were created by IETF action
(e.g. tpc.int) be removed but less clearly can the IETF ask that .int second level domains that the IETF had no
part in creating be removed
.int is run by the IANA because it has always been run by the IANA - Jon at first
then the IANA when the IANA came into existence
*laugh* Not exactly. Jon came to me at DDN (during the IETF meeting at
MITRE - july 1987) and told me that DARPA had asked for its creation -
and I think nato.int was the first registration. I approved the creation
of .INT (I owned the NIC contract at the time and for some reason I
ended up the decider for new non CC TLDs), but required that the
management of it not be at the NIC. ISI ended up running the servers,
and DARPA ended up owning the zone - E.g. - it was a delegated zone
owned by DARPA run by ISI under a DARPA contract, but not part of the
IANA stuff exactly.
I was later hoist by my own petard as I had this white elephant I had to
deal with when I got to DARPA in 92 and took over the ISI contract. I
seem to remember pushing .INT over to the InterNic and NSF as DOD
*really* wanted nothing to do with non-DOD internet. I think that's
where it was when ICANN/IANA stood up.
well prior to ICANN being formed there was talk about handing management of .int over to the ITU -
Jon had proposed that, but told the ITU that he needed some documentation on how .int
would be run before he would do that (I was in at least two meetings between Jon and an ITU person
about the topic) - the two documents were
1/ a clear statement on who could register in .int
RFC1591 had about the simplest statements - international treaty orgs
and international databases were permitted. I do remember the talks,
but I seem to remember that ITU wasn't playing all that nice with the
Internet folk and we mostly gave up.
2/ a document describing how the ITU would actually operate the servers
but the ITU never produced the documents so the transfer never happened
I was not "in the room" when Jon agreed to put tpc in .int - but Marshall Rose was and
also I assume Carl Malamud - one could ask them what their argument was
Steve Wolff would probably be a reasonable source as well as this was
well into the InterNic transition period.
tpc.int fell under the "international" databases prong and that would
have been enough for Jon or whoever to approve the registration without
referral for further approval. https://www.iana.org/domains/int/policy
has more on the current structure (hard to believe its been 20+ years
since databases were deprecated here).
Later, Mike
Scott
On Oct 19, 2022, at 7:23 PM, George Michaelson <ggm@xxxxxxxxxxxx> wrote:
I agree with what I thik Toerless is saying here.
1) the wording in the draft appears to (re)open the door to use of the
domain. This is despite the intent of the draft and I believe the
organisation, to remove dependency and use of the domain. Why is this
wording being used?
2) why does IANA continue to "operate" the domain, if there is no
dependency and no forseen use? The proper way to get shot of a burden,
is to give it to somebody else. Re-delegate to ICANN and make them
responsible for the registrar decisions about what treaty bodies are
allowed to have state in .INT
Toerless? Is that a reasonably good take on what you said? It's what I
think you said.
-G
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
