Launching a CLUB on Internet?

AS EASY AS 1-2-3

1. First: you need a .club domain name;
2. Second: you need a CMS;
3. Third: you need a template for a club;
4. What is it that you can't read here?

This is where it gets interesting: many solutions exist to create a website online, but the one with Google Sites allows you to select templates during the creation process of your first website. I like to remind you that many offers allow that too, but Google Sites has an option entitled "Browse the Gallery for more" and guess what: on the seven libraries of templates offered, one is entitled "Clubs and organizations". Some are ugly but... many are quite nice and I have no doubt that you can build your first club online with one of these.
Read the complete article here:
http://ezinearticles.com/?Launching-a-Club-Online?&id=9197762.

The .FEEDBACK Sunrise Period has begun

WHEN:

• SUNRISE PERIOD START: Tuesday, 20 October, 2015 - 16:00
• SUNRISE PERIOD END: Wednesday, 6 January, 2016 - 16:00.

WHERE:

To participate in the .FEEDBACK new gTLD Sunrise Period, contact Nameshield.

Spotted @ the Trademark Clearinghouse:
http://www.trademark-clearinghouse.com/content/feedback

Register your .CLUB domain name with Namebay.

Do you qualify for the .WINE Launch Program?

The .WINE Qualified Launch Program
The .WINE Registry may allocate or register up to one hundred (100) domain names to third parties prior to or during the Sunrise Period in compliance with the Trademark Clearinghouse Rights Protection Mechanism RequirementsQualified Launch Program Addendum.

The .WINE Qualified Launch Program will run from 4 November 2015 – 16 January 2016.

Sunrise Periods
Sunrise Periods for .WINE and .VIN new gTLDs will start on Saturday, 17 November, 2015.

Participate in the .WINE and .VIN Sunrise Periods with the Nameshield Group. Wine clubs can register their .CLUB domain name with Namebay.

Read more on gTLD.club:
http://www.gtld.club/2015/10/the-wine-qualified-launch-program.html

The .WINE Qualified Launch Program

The .WINE Registry may allocate or register up to one hundred (100) domain names to third parties prior to or during the Sunrise Period in compliance with the Trademark Clearinghouse Rights Protection Mechanism Requirements Qualified Launch Program Addendum.

The .WINE Qualified Launch Program will run from 4 November 2015 – 16 January 2016.

Qualified Launch Program Addendum

This addendum (this “Addendum”) to the Trademark Clearinghouse Rights Protection Mechanism Requirements (the “TMCH Requirements”) is hereby approved by ICANN as of 05 June 2015 and, pursuant to the terms of Section 4.5.1 of the TMCH Requirements, automatically incorporated without further action by either ICANN or any Registry Operator into the TMCH Requirements. All capitalized terms used in this Addendum but not defined herein have the meaning given to them in the TMCH Requirements.

1. Pursuant to Section 3.2 of Specification 5 of the Agreement, Registry Operator MAY register to itself up to one hundred (100) domain names (plus their IDN variants, where applicable) cumulatively over the life of the TLD. If Registry Operator complies with the terms and conditions of this Addendum, Registry Operator MAY, through an ICANN-accredited registrar, Allocate or register such one hundred (100) domain names (plus their IDN variants, where applicable) to third parties prior to or during the Sunrise Period (each such domain name, a “QLP Name”) for the purpose of promoting the TLD (a “Qualified Launch Program”). Except as permitted by this Addendum, Registry Operator MUST NOT Allocate or register such one hundred (100) domain names (plus their IDN variants, where applicable) to third parties prior to the Allocation and registration of all Sunrise Registrations.
2. If, at the time Registry Operator seeks to Allocate or register a QLP Name, the QLP Name matches a label contained in the list provided to Registry Operator by the TMCH Sunrise and Claims Provider containing the labels attributable to Sunrise-Eligible Rights Holders (the “Sunrise List”), then such QLP Name MAY be Allocated or registered to a third party registrant as follows:
1. To a registrant who is a Sunrise-Eligible Rights Holder with a valid SMD file for a label that matches the QLP Name; or
2. To a registrant who is an international, national, regional, local or municipal governmental authority (a “Public Authority”) and such QLP Name is either identical to, or translation or a transliteration of, (i) the name or acronym of such Public Authority, (ii) the name of a building, park, monument, airport or other public place operated by such Public Authority, (iii) the name of a region, city, street, district or other geographic area under the governance of such Public Authority, or (iv) the name of a recognized public service provided by such Public Authority. Except as permitted by this Section, if a QLP Name matches a label contained in the Sunrise List, such QLP Name MUST NOT as part of the Qualified Launch Program be Allocated or registered to a registrant who is not a SunriseEligible Rights Holder with a valid SMD file for a label that matches the QLP Name.
3. If, at the time of Allocation or registration of a QLP Name, the QLP Name does not match a label contained in the Sunrise List, then such QLP Name MAY be Allocated or registered to any third party registrant (i.e. does not have to be Allocated or registered to a Sunrise-Eligible Rights Holders), provided that such QLP Name is promptly Allocated or registered to such third party following such review of the Sunrise List.
4. If Registry Operator reviewed a QLP Name against the Sunrise List at the time such QLP Name was Allocated to a third party, then Registry Operator will not be required to review such QLP Name 2 against the Sunrise List again at the time of the registration of such QLP Name to such third party.
5. Prior to Allocating or registering any QLP Name, Registry Operator MUST obtain a Sunrise List from the TMCH Sunrise and Claims Provider. Registry Operator MUST obtain a Sunrise List from the TMCH Sunrise and Claims Provider at least once every 24 hours throughout the duration of the Qualified Launch Program. Registry Operator MUST NOT Allocate or register a QLP Name without obtaining the Sunrise List in accordance with the time requirements of this Section 4 and, as contemplated by this Addendum, reviewing the QLP Name against the most recent Sunrise List obtained by Registry Operator. Registry Operator will obtain the Sunrise List from the TMCH Sunrise and Claims Provider in the same manner as it obtains the Domain Name Label (DNL) List (as defined in the Functional Specification). Notwithstanding any provision of this Addendum, Registry Operator MUST NOT Allocate or register a QLP name prior to the delegation of the TLD to nameservers designated by Registry Operator into the root-zone.
6. Reporting.
1. Upon and following the first registration of a QLP Name, Registry Operator MUST transmit any QLP Name registered pursuant to Section 2 of this Addendum to the TMCH Sunrise and Claims Operator in its List of Registered Domain Names, as specified in the Functional Specification. Registry Operator acknowledges that ICANN may obtain such list of Registered Domain Names from the TMCH Sunrise and Claims Operator in order to assess Registry Operator’s compliance with the provisions of this Addendum and related provisions of the Agreement.
2. Promptly following Registry Operator’s Allocation or registration of all one hundred (100) domain names available for Allocation or registration for the TLD pursuant to Section 3.2 of Specification 5 of the Agreement (accounting for Section 7 of this Addendum) or Registry Operator’s decision to not Allocate or register any further QLP Names beyond what it has already Allocated or registered, and in no event later than the end of the Sunrise Period, Registry Operator MUST deliver to ICANN, via the Global Domains Division Portal (https://myicann.secure.force.com/gdd), a list of all of its Allocated or registered QLP Names (“QLP Names List”). Additionally, upon ICANN’s request at any time, Registry Operator MUST promptly deliver to ICANN its then current QLP Names List. Registry Operator acknowledges and agrees that ICANN MAY post Registry Operator’s QLP Names List to Registry Operator’s TLD Startup Information page.
7. Each Allocation or registration of a QLP Name to a third party as permitted by this Addendum will reduce the cumulative number of domain names that could otherwise be registered by Registry Operator for the operation and promotion of the TLD pursuant to Section 3.2 of Specification 5 of the Agreement (i.e. if Registry Operator registers 20 QLP Names, Registry Operator will only have 80 domain names available to it under Section 3.2 of Specification 5 of the Agreement over the life of the TLD, either for its own use or for use as a QLP Name).
8. Except for QLP Names Allocated or registered pursuant to Section 2.1 of this Addendum, Registry Operator MUST provide the Claims Services for each QLP Name registered to a third party.
9. A registration of a QLP Name is deemed a “Sunrise Registration” for purposes of the TMCH Requirements and the Agreement. 3
10. Notwithstanding any provision of this Addendum, Registry Operator must comply with Section 6 of Specification 6 of the Registry Agreement in connection with the registration of any QLP Name.

For more information, contact the Nameshield Group.

3 Sunrise Periods start today

Sunrise Periods
The TMCH to start 3 new Sunrise Periods
The TLDs concerned are:

1. .FOREX:
   SUNRISE PERIOD START: Thursday, 15 October, 2015 - 16:00;
   SUNRISE PERIOD END: Sunday, 15 November, 2015 - 16:00.
2. .BROKER:
   SUNRISE PERIOD START: Thursday, 15 October, 2015 - 16:00;
   SUNRISE PERIOD END: Sunday, 15 November, 2015 - 16:00.
3. .GOSSIP (IDN):
   (IDN TRANSLATION: xn--45q11c)
   SUNRISE PERIOD START: Thursday, 15 October, 2015 - 16:00;
   SUNRISE PERIOD END: Saturday, 14 November, 2015 - 16:00.

Source:
https://secure.nameshield.net/recherche-dispo/calendar.php?lang=en.

Register your .CLUB domain name with Namebay.

A ".carpooling" coming in French?

Domains ending in ".covoiturage"
According to this article, there will be a new applicant in Round 2 of the ICANN new gTLD program and he will apply for the French version of ".carpooling".

Details of the project are explained and a little surprise is coming at the end of the article so be patient and read it all.

The article is in French.

A lire sur le JournalDuNet:
http://www.journaldunet.com/ebusiness/expert/62466/pourquoi-des-noms-de-domaine-pour-le-covoiturage.shtml

Register your .CLUB domain name with Namebay.

Registrants: what they think about new gTLDs

New gTLDs?
Do you remember the first time you were asked about new generic Top-Level Domains? I remember asking about them and listening to Trademarks' first thought.

What Registrants think about new gTLDs
Extract:

• My Registrar sends me too many emails about new gTLDs, this is annoying;
• Why is there such a difference of price between Registrars?
• I hate don't like domainers;
• .BRAND new gTLDs are a good idea for those who can afford it;
• ...

Read it on gTLD.club:
http://www.gtld.club/2015/10/new-gtlds-according-to-registrants.html.

Register your .CLUB domain name with Namebay.

New gTLDs according to Registrants (updated)

New gTLDs are understood in many different ways: the understanding from end users, and the understanding of domain name professionals is often not the same. As an actor of the ICANN new gTLD program, a true user of these new domains, and a consultant on these questions, find below a mix of things I heard, and things I believe are right about new gTLDs.

A Registrant?
I call a "Registrant", the person to own a domain name and who's had to pay interest in new gTLDs at some point: website owner, law firm, webmaster, IP department...

Feedback received from Registrants:

1. I have a ".com": why would I change my domain name?
2. It is expensive (...)
3. You said a domain name ending in ".consulting": do you mean "consulting.com"?
4. Domain names ending in ".sucks"? Come on: no one would allow that (and certainly not the people who govern the Internet*)!
5. There are too many domain name extensions: I would like to secure my domain in all of them but it is too expensive.
6. I noticed some domain name extensions exist with an "s": this is confusing and irritating.
7. Some extensions are really interesting, some ... I, just don't understand why they exist.
8. My Registrar keeps me informed about new domain names, this is fortunate because I don't have time for this.
9. My Registrar sends me too many emails about new gTLDs, this is annoying.
10. Why is there such a difference of price between Registrars?
11. I hate don't like domainers, they took the domain name I wanted to register and they put an ugly "Sedo" page behind with "buy now" button.
12. .BRAND new gTLDs are a good idea for Trademark owners who can afford it.
13. .BRAND new gTLDs will increase consumers' trust.
14. .BRAND new gTLDs will be confusing...in the beginning.
15. The Trademark Clearing what?
16. It is sad that the Trademark Clearinghouse mechanism did not allow to block domain names from being registered "at the root".
17. Why should I pay more to protect my name? In the past I had a domain name and if was fine: now so many are related to my business, the risk of infringement has increased and I am forced to act.
18. .CITY new gTLDs are a good idea.
19. Community domain name extensions: what ???
20. Now I have a new domain name, should I stop renewing my ".com" or should I keep it?
21. Is there a possibility to register a domain name before the Sunrise Period?

Coming next:

1. "New gTLDs according to Registrars";
2. "New gTLDs according to Registries";
3. Updated: "New gTLDs according to Backend Registries";
4. "New gTLDs according to ICANN" .

* Ok, this one was from me ;-)