Friday, March 30, 2018

The .BMW new gTLD

While updating the CARS new gTLD report for the month of March 2018, I noticed that the .BMW new gTLD had 53 ".bmw" domain names registered in February to 108 at the end of March.

From the examples that I tested, most are not redirections anymore but real websites such as: http://ratzel.bmw

Monday, March 26, 2018

For .STEPHANE

I just learnt today that Stéphane Van Gelder passed away.

My friend Murielle called me.

Many of us in France have worked with and for Stéphane. I personally worked many years with Stephane to launch new gTLDs at INDOM (which was then acquired by another company). He is the person who taught me everything that I did not know about domain names: he actually taught me that Versign was a thin registry and not a thick one: I did not know the difference...

When I joined INDOM, years ago, he also was the first French guy to have delivered .BRAND new gTLD studies when we did not even know when the first round of the ICANN new gTLD program would start. Actually, we were very good at what we did but he was the guy to think years in advance.

Stéphane was a person of precision. I remember the number of times he asked me to re-write things because I would not have seen a mistake in a word or have missed an accent: I remember going to his office at Indom 10 times a day and getting back to mine ultra pissed because I would have I missed a correction in a study.

...I don't really know what to write in such circumstances...

Today is a sad day.
RIP Stéphane.

More covers here and here.

New gTLDs: homograph attacks on the rise?

The problem with homograph attacks is that the more we talk about them, the mode it gives ideas to frauders.

Note that it is also - and I believe this strongly - a super fantastic way for security providers to scare their clients reminding them to buy their services because if they don't, the world will collapse ;-)

Last May, I wrote (in a very limited english that only non-english speakers can understand) a post about it to explain what an homograph attack is.

This morning, I read a new updated post, written in words that even I understand: it is entitled "Homographs, Attack!": it explains homograph attacks in simple words with cool designs. This is a good read and this is something that operators of large domain name portfolios should read too.

Tuesday, March 6, 2018

New gTLDs: overarching issues

These are recent slides extracted from today's meeting. These topics will be discussed in the next ICANN meeting in Puerto Rico:

Something written about the next new gTLD applicant guidebook's format (the famous AGB):
Exciting, isn't it?
:-)

For action:
  1. Add to the slides for Council planning for PDP WG time at ICANN62 in Panama City.
  2. Take the list of topics in the Initial Report structure and send it to the WG in case we missed any topics.

Notes:
  1. SOI Updates:  No updates.
  2. Work Track updates:
    1. Work Track 1:
      1. Going through all of the topics and trying to make sure we reflected feedback from the calls and the CC2 responses.
      2. Getting that text into the Initial Report.
      3. Call scheduled for 06 March is TBD.
    2. Work Track 3:
      1. Finished meetings and going through topics.
      2. Making sure we've captured all of the input.
      3. Putting the language into the Initial Report.
    3. Work Track 4:
      1. Looked at preparing text for the Initial Report.
      2. Discussed Registry Testing System.
      3. Preparing topics for Puerto Rico.
      4. Name Collisions also will be a topic.
      5. ICANN Board resolution on a longer term study.  See: Draft Project Plan for Name Collision Analysis: https://www.icann.org/public-comments/ncap-project-plan-2018-03-02-en
    4. Work Track 5:
      1. Going through the different categories of Geographic names in the Applicant Guidebook.  Identifying pros and cons.
      2. Looking at how we may want to consider doing the same thing in future or changing the AGB.  Addressing variations between the initial policy work and the final AGB content.
      3. Look at categories that were not in the AGB.
      4. Working Session dedicated to WT5 in San Juan on 14 March 0830.
  3. Review of suggested Initial Report structure/planning for ICANN61
    1. Slide 2: Initial Report
    2. Slide 3:
      1. Complete the Final Report by the end of 2018.
      2. For the Initial Report we are not doing consensus calls. We are putting options out for public comment.  Not the time to take a consensus call on one or more of the recommendations.
      3. Goal is to get out the Draft Initial Report out by the end of March and then have the WG review it in April.
      4. Thinking of changing the meeting schedule to meet every week to help with the review of the Initial Report, starting Monday, 26 March.
      5. In the planning for Panama we need to understand if the PDP WG will need a good chunk of the time at ICANN62.
    3. Slide 4: Work Track 1-4 and overarching issues.
    4. Slide 5:
      1. Overarching Issues and Work Track Topics.
      2. Options and open questions have not gone through a consensus call.
    5. Slide 6:
      1. Status Update Overview.
      2. Overarching Issues.
      3. Recommendations on 4 topics.
      4. Options/questions on 3 topics.
      5. Community Engagement: a lot of overlap with predictability or where we have tried to get feedback on this PDP.
    6. Slide 7:
      1. Status Update Drill-Down.
      2. Overarching Issues.
    7. Slide 8:
      1. Status Update Overview.
      2. Work Track 1.
  4. AOB: ICANN FY19 Budget:
    1. Only a short mention of the Subsequent Procedures PDP, but statement that there are no funds allocated for implementing any GNSO policy on subsequent procedures.
    2. FY19 goes from 01 July 2018 to 30 June 2019.
    3. If the Board waits until FY20 to allocate funds some think this could delay the launch of the next round.
    4. No time for this WG to file formal comments.
    5. PDP WG Co-Chairs may file individual comments.

Structure of the Initial Report (chronological order):
  • Overarching issues
  • Foundational issues
  • Pre-launch activities
  • Application submission
  • Application processing
  • Application evaluation/criteria
  • Dispute proceedings
  • String contention resolution
  • Pre-delegation
  • Contracting
  • Post-delegation