Lyman, >> It is neither: it is a DNS operational issue. A "large" number of people are >> apparently squatting on CORP/HOME/MAIL. Delegation of those TLDs would thus >> impact that "large" number of people. > > I think it is inaccurate (and unhelpful) to refer to the people who have been > using corp/home/mail as squatters; most of them have simply been following > what textbooks, consultants, and "best practice" guidelines have been > advocating for a long time.
Somewhat irrelevant, but I'll admit I don't see a whole lot of difference between folks using .CORP and folks like those who came up with the Hamachi VPN using 5.0.0.0/8 (before it had been allocated by IANA -- as an aside, I find it sadly ironic that their solution to 5.0.0.0/8 being allocated was to move to 25.0.0.0/8, at least according to http://en.wikipedia.org/wiki/LogMeIn_Hamachi). I recall the Hamachi folks' choice to use 5.0.0.0/8 being described as squatting. I recall a number of people on NANOG have suggested using 7.0.0.0/8 (etc) to deal with the lack of IPv4 address space. And then there is the use of 1.0.0.0/8. What qualitative difference do you see between those uses of numbers and the use of TLDs like CORP? (I'm told that "squatting" does not necessary have negative connotations, particularly outside the US) > The security/stability concerns do not prevent ICANN from selling them. As I understand it, it does prevent them from being delegated, thus resulting in the situation where the applicants have the ability (so I understand) to request a refund. > I'm saying that the IETF's core interest in a stable, operating Internet is > the context in which the issue should be resolved. I agree and as I've said before, I think it would be really nice if the IETF could move CORP/HOME/MAIL to reserved like the TLDs in 2606. However, the question I still have: what criteria do you use to decide that delegating a TLD would negatively impact the stable operation of the Internet? Regards, -drc
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
