Tuesday, June 10, 2025

There’s Still A Glitch In the Domain Names Implementation!

 

Shouldn’t the cctld be restricted for country specific ‘residents’ only everywhere, like in the cases of .us, .eu, .jp, .fr etc. usually? As many of the other cctld’s are not covered with the same security features & measures! And the reason is -> why would someone else would need another country’s cctld, while operating from somewhere else? Of course, I know the contention is that what about MNCs who’ve global presence, then, their rights in TMs would become obsolete or been jeopardized! NOPE! The said provision is already present as one has to provide the address of service first or the reason before registering them!

Monday, June 9, 2025

What Should Be The Role Of ICANN In Terms Of Paid Privacy Features? And The Dilemma That Recently Met With -> Kaiju Eel!

 

Shouldn’t the paid privacy feature be the prerogative of the ICANN only, and not of the Registrars’? Would it be correct for the Registrars asking the Registrants the Privacy Fees for the Domain Name Privacy Protection Features? In the 90s, the domain names were free, and it was understandable, as Not many had the access of the Internet, and not many were using Custom Domains, and not many Domain names were generated; and as the options on the table were many! And this is also true that the Concept of privacy didn’t come until late, maybe after the DMCA act, for the protection of the online data of the Individuals (which thanks to the likes of AI Companies  today, who butchered Berne & DMCA), and then, the part of the Cybersquatting cases rose, in terms for the protection of the Trademarks it was needed. But herein the dilemmas crossed the paths with Kaiju Eel!

Friday, June 6, 2025

Issue With Any Trademark Accepted With A Disclaimer! And My Dilemma Riding On-> Thomas The Train!

 

Restricting to any Demography is understandable in the Disclaimer Clause! BUT, I never understood, especially, when any trademark is considered as whole, why then restricted disclaimer clause is attributed for certain words in it, especially in the Device Mark itself? This creates an issue later, even at the time of adjudging the opposition or rectification. For the reason, that, now one is allowed to use the Mark with the Disclaimer; YET, one is not allowed to have the exclusive user rights over it, even as a whole! You can’t oppose or rectify it, YET, you can oppose or rectify it!

There’s Still A Glitch In the Domain Names Implementation!

  Shouldn’t the cctld be restricted for country specific ‘residents’ only everywhere, like in the cases of .us, .eu, .jp, .fr etc. usual...