dang and team, perhaps it makes sense to special-case .name domains in the domain hint, like you do for GitHub and Ex-Twitter.
.name Termination
381–390 of 559 posts
Re: .name Termination
#382I can only assume somebody was asleep on the job when this scheme was approved, because the outcome is in direct contradiction to ICANN’s mission statement: > Its enduring mission is to ensure the stable, secure operation of the Internet's unique identifier systems. https://www.icann.org/resources/pages/about-icann Arbitrary termination of service is not stability. Enabling name hijacking is not security. The answer…
It's been through the Ombuds and a reconsideration request [1]. ICANN says: > There will not be any effect on the life cycle of domain names. While the Requestor may disagree with Verisign’s response, the Requestor has not shown that ICANN relied upon false or inaccurate material information. The life cycle of a domain name begins when the domain is registered, then moves through various stages before ultimately comi…
How about the fact that you paid for a service for 10 years and they decided to stop providing it midway? Will you at least get a refund? If not, that's surely illegal right?
Re: .name Termination
#383Earlier quoted context omitted.
There are many examples; k12. .us is another.
Except nobody uses the .us tld, but pretty much every every Japanese company is on a .co.jp
But that was simply the easiest way to market your website as a trusted government entity. And now nobody has ever heard of .us domains in active use.
Re: .name Termination
#384Should I rush to reserve y.name so my email address and personal website can stay online?
Re: .name Termination
#385Earlier quoted context omitted.
I own a .name domain that is an initialism for my wife and I, and Namecheap never gave me any problems adding a record for vpn.mwai.name, for example. In fact I never even realized you could register a 3LD, much less that this was the intended(?) behavior.
The idea is: * .name is open for everybody * a company called "Global Name Registry" scooped up a BUNCH of common last names, including fraser.name * Global Name Registry then sold access to neil.fraser.name for far cheaper than the fraser.name domain would cost on its own; someone else could also buy john.fraser.name or jane.fraser.name, so the single fraser.name domain that they owned could have dozens of customers…
Re: .name Termination
#386I can only assume somebody was asleep on the job when this scheme was approved, because the outcome is in direct contradiction to ICANN’s mission statement: > Its enduring mission is to ensure the stable, secure operation of the Internet's unique identifier systems. https://www.icann.org/resources/pages/about-icann Arbitrary termination of service is not stability. Enabling name hijacking is not security. The answer…
It's been through the Ombuds and a reconsideration request [1]. ICANN says: > There will not be any effect on the life cycle of domain names. While the Requestor may disagree with Verisign’s response, the Requestor has not shown that ICANN relied upon false or inaccurate material information. The life cycle of a domain name begins when the domain is registered, then moves through various stages before ultimately comi…
According to ICANN cutting the life cycle short doesn't have any effect on the life cycle?
ICANN corruption is at the level of FIFA corruption.
Re: .name Termination
#387Earlier quoted context omitted.
I don't store their emails, I use forwardemail.net and they have a pretty reasonable privacy policy: https://forwardemail.net/en/privacy Some people in my family use it as their main address, others don't, it's entirely their call. But yes, ultimately I control the domain and could be nefarious if I wanted to. But there's a certain baseline level of trust as a family, I'm reasonably certain my wife won't poison the m…
How do you manage the bus factor? You die tomorrow and what happens to management of the domain and therefore access to their emails?
Re: .name Termination
#388Re: .name Termination
#389Earlier quoted context omitted.
Having a mix of both 2LD and 3LD registrations under the same TLD is a bit of a nightmare in terms of public-suffix list [0], which is kind of important thing when enrolling your domain for some services, cloudflare among them. [0] https://publicsuffix.org/
Yeah, that’s why RFC 9989 replaced use of PSL with a dns signifier.
The problem DMARC solves is different than the problem the PSL solves, though. DMARC prevents a 3LD from pretending to be a different 3LD on the same 2LD. But the PSL handles things like what it means to make a "cross-site request" or how to handle cookies.
I mean now I'm thinking if DMARC _could_ solve that... but I don't think it could, unless I'm missing some extension or rare use case.
Re: .name Termination
#390Wtf, I have been using my x.y.name domain for everything, haven't been notified of this. Should I rush to reserve y.name so my email address and personal website can stay online?