ICANN74 between lessons of the pandemic and awareness of the richness of the Internet

Between ICANN66 in Montreal, Canada and ICANN74 in The Hague, Netherlands, thirty-two months and seven summits will have passed exclusively online. In 2020, the prospect of a return to face-to-face meetings was already being discussed under the heading of ‘hybrid mode’, a mixture of face-to-face and remote meetings. The question remained as to when this could be implemented. A more favorable health context was needed, with all the questions posed by covid variants and its repeated waves, and sufficient guarantees of security for the participants, who generally come from the four corners of the world. The 74th edition, which was held last month in The Hague, was finally chosen to experiment the ‘hybrid mode’.

The return of face-to-face meetings with the lessons learned from the pandemic

A return to face-to-face sessions in The Hague, but nevertheless extremely constrained, due to health security. Pre-registration was compulsory for all sessions, with a limited number of places per session. This meant that some sessions were already fully booked well before the summit. The compulsory pre-registration led participants to pre-register for sessions they were not sure they would attend in order to reserve a place. Each participant also had to be able to prove that their vaccination status was up to date. Tests were provided on site as well as temperature taking. Finally, masks and distancing measures were mandatory, hence the limited number of places per session. The organization also decided that everyone should go through the video conferencing medium, including those present on site, an idea that aimed to ensure that all participants could interact equally. For those connected remotely, it was also noted that, as promised, the organization planned shorter sessions, generally not exceeding one and a half hour and very often even one hour. The conditions were therefore met to guarantee safe conditions for those present and good conditions for those connected remotely.

Two ODP processes running in parallel

The subject of the next series of new generic extensions has been discussed in sessions of various bodies. The project is now in the Operational Design Phase (ODP), which consists of an assessment of the risks, tasks and resources required, and which is to be concluded with an Operational Design Assessment (ODA). A related subject, that of closed generic extensions, has entered a new sequence. The principle of a so-called “Small Team”, which includes representatives of the GAC, the body representing governments, the ALAC, which represents end-users, and the GNSO, the body in charge of generic policies, has been validated in order to discuss this subject and see if a compromise can be found to envisage next steps. In the 2012 round, it was not possible to create such extension models. The question is therefore whether such extension models will be possible in the next round. Regarding the ODA, the GNSO, which estimates its publication on 31 October, has mentioned a possible postponement of six to eight weeks due to another ODA that is also mobilizing many people on the creation of a Standardized Domain Name Registration Data Access System for legitimate purposes. The SSAD ODA with contrasting conclusions, particularly with regard to its number of potential users and its particularly high cost, was delivered on 25 January. Its findings are still being evaluated. The next step on this second subject is the creation of a sort of prototype called “SSAD Light” which could be based on technologies mastered by ICANN teams to limit delays and costs. The latter would help to validate or not the implementation of an SSAD with, in this case, a prior implementation phase.

Accuracy of registration data, an important issue

Among the many issues currently being examined, the accuracy of domain name registration data is an important one for Europeans. Indeed, it is the Regulation on the Protection of Personal Data, the GDPR, which has prompted ICANN to call for the removal of personal data from registration directories and which, in turn, explains the aforementioned SSAD project and the accuracy of data. How can we ensure that masked data is accurate?  In October 2021, a Scoping Team began a mission to evaluate the obligations related to the accuracy of registration data. It planned to verify the effectiveness of the accuracy of the data. Their findings were expected in June, but the measurement of effectiveness has been hampered by the difficulty of obtaining the necessary data, which is stored at the registrars. Transmitting all registration data to ICANN for research purposes requires a legal basis. The Scoping Team is thus put on hold.

This is particularly important because, as EURALO, the European part of the At-Large body representing end-users, has pointed out, Europe is about to adopt the NIS2 Directive. The directive is due to be voted on in the plenary session of the European Parliament in September before being published in the Official Journal and transposed in the 27 European states. EURALO recalled that NIS2 provides for specific obligations notably on domain name registration data, storage, access and verification and therefore interferes with the role of the regulator ICANN. Moreover, if specific measures apply only to European providers, this creates a disparity of obligations between players, not to mention that the transposition of the text could be unequal in the states. Accuracy at the ICANN level can help harmonize future obligations for all players regardless of their location.

The impact of regulations and disasters

At ICANN73, which followed the outbreak of the conflict in Ukraine, ICANN had the good idea of creating a session dedicated to geopolitical, regulatory and legislative aspects. This meeting highlighted the risks of fragmentation of the single Internet model advocated by the organization. This meeting was repeated at this summit and allowed to note that the initiatives of the States are increasingly interfering with ICANN’s role as regulator.

EURALO had the good idea of completing this panorama with a session on governance and multipartyism in times of emergency. This session consisted mainly of a round-up of At-Large representatives from different continents. The representative from Ukraine logically started the session. In a moving speech about the tragedy in her country, she reminded us that the Internet infrastructure in her country has been heavily impacted. For the Asia-Pacific region, the representative mentioned the volcanic eruption in Tonga in January 2022, which cut the submarine cables and caused a five-week blackout on the islands. She also mentioned the situation in Myanmar where the Internet has been cut off since a coup in February 2021. The representatives of the two American continents spoke of natural and climatic disasters such as Hurricane Maria in Puerto Rico, which had knocked out telecommunications antennas and the electricity network. For part of the population, electricity and Internet access had been cut off for several months. Finally, the representative of Africa recalled that today at least 60% of Africans do not have access to the Internet.

Our comments

The return to face-to-face meetings was not an easy task for ICANN. While many participants felt that the proposed framework was too restrictive, it seems that the organization worked quite well overall in allowing everyone to attend the sessions fairly. The protection measures also seem to have dissuaded many participants from coming, including the speakers scheduled for the week of exchanges who assumed to participate remotely. Indeed, the figures given by the organization indicate 1817 participants from 101 countries, half of whom attended remotely. A good point for the planet but the limit was the possibility to interact outside the sessions.

On the ongoing policy development and review processes, the sessions during the week of the event reminded us that there are a lot of issues being dealt with in parallel, undoubtedly too many issues. This inevitably makes it difficult to keep track of them and causes delays, such as the two ODPs being conducted simultaneously on SSAD and the next round of new generic extensions. However, the overall feeling is that the topics are moving forward, even if the finish line is often unclear.

The last day provided a break from policy issues as geopolitical and regulatory issues and the impact of disasters reminded us that the governance model and access to the Internet are two particularly fragile critical aspects. While NAMESHIELD offers you solutions to the risks associated with compromised names and malicious registrations, we must also remember that we are not all equal when it comes to accessing the Internet. In addition to stricter legislation, other risks such as armed conflicts or climate change must indeed also be considered.

Image source : ICANN’s website

The .SEXY registry increases drastically its prices

The .SEXY registry increases drastically its prices

The registry that owns .SEXY will drastically increase the price of new registrations under this extension from April, the 30th 2022, 18:00 (Europe/Paris).

All registrations, transfers and renewals of a .SEXY domain name registered after April 30th 2022 will be charged 3850 € HT per year.

This very important price increase, which has not been explained by the registry, will only apply to domain names registered after this deadline.

Domain names registered before April, the 30th can still be renewed at the current price (70 times lower).

To protect your brands without suffering this increase, we invite you to register your .SEXY domain names now.

The Nameshield team is at your disposal for any questions.

Image source :Uni Naming & Registry (UNR) website

Opening of .TZ registrations

Opening of .TZ registrations

Since March 1st 2022, the Tanzanian registry allows the registration of .TZ.

A first phase of 3 months (until 31/05/2022) will allow the registration to the holders of .CO.TZ registered before 01/03/2022.

From 01/06/2022, it will be possible to register .TZ domain names equivalent to domain names recently registered in .CO.TZ (.co.tz registered after 01/03/2022).

A general opening is planned for July 1, 2022.

The Nameshield team is at your disposal for any questions.

Launch of .AU registrations on 24/03/2022 – Reminder

Launch of .AU registrations on 24/03/2022 – Reminder

The opening date for the registration of .AU domain names is announced on 24/03/2022.

As a reminder, during the first six months, the implemented priority allocation process will offer you the opportunity:

  • To request an exact match for your existing domain names (.com.au / .net.au / .org.au etc) in .AU ;
  • To register “new” domain names directly in .AU (domain names that would not exist in other extensions such as .com.au, .net.au, .org.au etc.).

Please note: your existing domain names will continue to operate normally and in accordance with the auDA registry policy, regardless of a .AU registration.

The Nameshield team is at your disposal for any questions.

Image source : kitkatty007 via Pixabay

BIMI and VMC: display your logo with emails

BIMI and VMC: display your logo with emails

BIMI (Brand Indicators for Message Identification) allows you to authenticate your emails and reinforce the trust of your customers by displaying your logo in their inbox. VMC (Verified Mark Certificate) is a certificate associated with BIMI, which ensures the authenticity of the logo displayed.

BIMI - Nameshield

What is BIMI?

BIMI is an industry initiative aimed at standardizing the use and display of brand logos in email clients. By placing a brand or company logo next to an email, it is more easily identifiable by customers and users, builds a sense of legitimacy and trust, significantly impacts open rates, and increases consumer protection against fraudulent emails.

Technically speaking, BIMI is an emerging security technology that works alongside DKIM, SPF and DMARC protocols to protect your domain name from being used by malicious actors to send fraudulent emails.

Before BIMI, the steps to get your logo next to an email were specific to each email service your message was sent to. Sometimes the process was entirely manual or relied on other applications to aggregate your brand information and share it across participating platforms.

The AuthIndicators group, which includes email service providers such as Google, Verizon Media, IONOS by 1&1 and Fastmail, is working to implement BIMI in the most common email clients. Many players have already adopted BIMI, others are in the process, Microsoft’s and Apple’s positions are expected to drive final adoption of the standard.

Why is BIMI important?

To complete the arsenal of a brand’s protection on the Internet, more specifically against hijacking attempts through fraudulent spoofing emails whose goal is to deceive the user and lead them to phishing sites.

306 billion emails circulated worldwide in 2020, with an ever-increasing proportion of fraudulent emails hijacking brands.

To increase the desirability of emails, particularly in marketing campaigns. The implementation of BIMI and more widely of security protocols and certificates on the domain name associated with a brand is essential today and has a major impact on online reputation.

Because it is becoming a market standard, easy to implement unlike the number of existing anti-fraud email solutions that are often difficult to test and implement.

How does BIMI work?

BIMI uses a process of several steps to validate emails by ensuring that they are actually associated with the sender’s domain name. Senders must add a TXT DNS record dedicated to BIMI.

For BIMI to work, domain names must also have several other fraud protections, including:

  • SPF (Sender Policy Framework): authenticates emails by identifying mail servers authorized to send from specific domain names ;
  • DKIM (DomainKeys Identified Mail): adds a digital signature to each email to verify that it was sent from an authorized domain name;
  • DMARC (Domain-Based Message Authentication, Reporting, and Conformance): confirms SPF and DKIM records and specifies how non-compliant emails should be handled.

When emails are sent using BIMI, the receiving mail server will first do the standard DMARC/DKIM authentication and SPF validation. If the email passes these checks, the mail server will verify that it has a valid BIMI record and display the brand logo.

How does BIMI interact with DMARC, DKIM and SPF?

The first step towards using BIMI to display a logo is to implement DMARC. This is stored as a DNS record of TXT type on the domain name. For DMARC to work with BIMI, the reject policy in this record must be p=quarantine or p=reject for all emails sent from your domain.

BIMI requires DMARC… and DMARC requires your domain name to have DKIM records to work. While DMARC only requires SPF or DKIM to work, it is best to include SPF records for more security when using BIMI. These 2 security tools are also stored as TXT DNS records in the domain name zone.

VMC, the final link in the chain

A Verified Mark Certificate is a digital certificate that authenticates the ownership of a logo, and completes the use of BIMI in email clients such as Gmail.

The VMC certificate guarantees the authenticity of the logo displayed, which is necessarily owned by the domain name holder sending the email. It is the last link in the chain to guarantee the authenticity of the email received.

When you send an email to a contact, the receiving mail server that manages their inbox will take the URL of the tag that indicates where the logo should be displayed. It will then check the VMC certificate to ensure that the correct logo is used. Once the logo is verified by the VMC, BIMI will display it next to the email in the inbox.

To obtain a VMC certificate, the implementation of DMARC on the domain name is a prerequisite. Then follows a reinforced authentication process with a Certification Authority that will validate the identity of the Organization, the registration of the logo with a certified body and will issue the certificate after a one to one meeting with a notary.

Depending on the country, the intellectual property offices for logos registrations may vary as well as the rules of acceptance to issue the certificate. The notions to keep in mind, the authorized trademarks can be:

  • Design trademarks: consist exclusively of a design;
  • Verbal trademarks: contain words, letters and/or numbers, without any particular font, size, color or style;
  • Combination trademarks: include a combination of words with a design, stylized letters or numbers.

While this is not a requirement for implementing BIMI on your domain name at this time, VMC should be part of the standard in the future.

Entrust Datacard and DigiCert are the first 2 companies to issue VMC certificates for the BIMI standard. Nameshield is a partner of both companies and will assist you in obtaining VMC certificates. You can contact directly our certificates department for any question on the subject.

BIMI + VMC = Guarantee of authenticity

BIMI, VMC… and Nameshield

Nameshield now assists its customers in all aspects of the implementation of DMARC, SPF, DKIM, but also BIMI protocols and the obtaining of associated VMC certificates. The domain name is at the core of the implementation of these different protocols. Our historical business as a registrar and DNS zones manager allows us today to assist our customers on these major subjects of the fight against online fraud and the increase of emails desirability.

New document : 5 minutes to understand monitoring solutions

5 minutes to understand - Domain names - Monitoring solutions - Nameshield

A domain name is not static, it evolves. It can be inactive, associated to a website, to a messaging service. The website can be operated, deactivated or its content can change. So many constant modifications that require a particular follow-up in the form of monitoring of domain names that may infringe your brand.

Find in this “5 minutes to understand” document, available for download on the Nameshield’s website, the different monitoring solutions that provide you with information to protect your domain names and brands from possible infringements.

To understand all about Metaverse and alternative domain names

Metaverse and alternative domain names

The word “Metaverse” refers to everything related to virtual worlds (3D, augmented reality, virtual reality), and designates a “future” vision of the Internet, with fictive spaces such as stores, rooms or even games. It’s a bit of a buzzword of the moment, which was put forward by Facebook in October 2021, when it announced the creation of a metaverse (Meta). There is of course a trend effect, however several major brands seem to be working on the subject.

Many projects have used the term “Metaverse” around their services and products. There are projects related to digital assets, such as cryptocurrencies and NFTs, which allow the representation and exchange of value on the Internet. But also alternative domain names, like .eth, .crypto, .metaverse, etc. It’s also related to the concept of “web3”, which is a vision of a more decentralized web.

Regarding the alternative domain names, you have to know that they are extensions that are not regulated by ICANN, so they are not official. This explains why it is not possible to have WHOIS information. Furthermore, most alternative domain names systems do not work with the DNS protocol, but are built on a Blockchain infrastructure.

Here are some examples:

ENS (Ethereum Name Service): .ETH

ENS is one of the most used alternative domain name systems with .ETH. It is built on the Ethereum blockchain, through smart contracts, and allows to register domain names in order to link addresses of crypto wallets, websites or any other type of registration. A domain name can be registered for several years, and there are no domain name recovery procedures for trademark holders, as it is a decentralized project: the holder of an .ETH domain name is the only one who can control it.

The registration procedure is done through the use of an Ethereum wallet, and the payment with the ether cryptocurrency ($ETH).

ENS also allows traditional domain names holders to register their domain names on their system.

Unstoppable Domains: .CRYPTO, .ZIL, .COIN, .WALLET, .BITCOIN, .X, .888, .NFT, .DAO, .BLOCKCHAIN

This is also a domain names system developed on the Ethereum blockchain. It allows, like ENS, to register domain names with different extensions. Unstoppable Domains do not expire and do not need to be renewed. There is, however, a procedure for trademark holders.

Namebase

This is a project that allows the creation of all kinds of top-level extensions. It is built on the HNS blockchain.

Namecoin: .BIT

One of the first alternative domain names project on Blockchain.

Touchcast: .METAVERSE

This is a recent project that offers .METAVERSE domain names for sale. There is not much technical information about their system, and their community seems to be quite limited compared to their number of followers on social networks.

Other alternative domain names projects have also emerged. It is important to know that anyone can create an extension not regulated by ICANN.

For users, it is necessary to use another means than a classic DNS resolver to use these extensions (browser extensions, dedicated applications, etc.).

As expected, there is a lot of speculation and cybersquatting related to this type of domain names.

Image source : xresch via Pixabay

Changes in the administration of Turkish extensions

Changes in the administration of Turkish extensions

It is a new change that has been in preparation for a few years in the digital world of Turkey.

Indeed, the administration of extensions in Turkey (.com.tr, .net.tr and .org.tr…) has been entrusted to .TR Network Information Systems (“TRABİS”) which will be incorporated under the Information and Communication Technologies Authority (“BTK”).

With TRABIS, changes will therefore occur in the process of assigning domain names.

The allocation of domain names under the extensions com.tr, net.tr and org.tr, under this new system will be liberalized and will answer to the principle of “first come, first served” (without required supporting documents).

As a reminder, under the management of NIC.TR, it was necessary to justify a trademark or the name of the company with an official document to register a .com.tr (the most used extension).

It will be easier to register a domain name in Turkey in a few weeks.

This change of rules was initially planned for January 2022 but has not happened yet.

BTK will announce soon the official dates and we hope to be able to confirm this liberalization of .com.tr, .net.tr and .org.tr during February 2022.

Do not hesitate to prepare your orders and contact your consultants and account managers to check your .com.tr domain names portfolio.

Image source : RiZeLLi via Pixabay

ICANN72, between prioritisation needs and fragmentation risks

ICANN72, between prioritisation needs and fragmentation risks

At the end of October, the 72nd ICANN summit was held, devoted to the development of policies that impact the domain name system (DNS) and the global Internet community. As already announced during the past summer, this latest annual meeting was to be held by videoconference in the time zone of Seattle in the United States. “Sleepless” were therefore not in Seattle but rather in Europe.

ICANN72, between prioritisation needs and fragmentation risks

The thorn in the side of the next round of new generic extensions

A month before this summit, ICANN announced the schedule for the Operational Design Phase (ODP) for one of the most anticipated topics by the contracting parties: the organisation of a future round of applications for new generic extensions. The ODP is a new mechanism now linked to the policy development process (PDP). It is similar to a project scoping exercise as it aims to identify the steps, risks, costs and resources to be allocated to implement a project, in this case a new round of generic extensions. The PDP was conducted between 2015 and 2020, with the submission of a final recommendations report to the ICANN Board in March of this year. However, it is not until February 2023, almost two years later, that the Board should consider these recommendations, the time to let the ODP conduct. Indeed, ICANN confirmed before the opening of ICANN72 that this scoping phase should last sixteen months in its entirety, including ten months for the conduct of the ODP, three months upstream to initiate the latter and in particular to constitute the teams that will conduct it and three months downstream to conclude the work. This timetable surprised many of the contracting parties and gave rise to much discontent. These discontents were particularly expressed through the Brand Registry Group that represents and promotes the interests of its members, dotBrand owners. For most members, things are not moving fast enough and the ODP would even be partly useless since some aspects overlap with the work already conducted during the previous PDP. Another aspect pointed out was the cost of the ODP estimated to $9 million, which is not a small amount.

The clouds are gathering as are the processes underway

As the other sessions scheduled during the week-long summit progressed, it was clear that the clouds continued to gather in the weather of ICANN’s policies. For example, the announcement of the launch of an expedited policy development process (ePDP) to review the Uniform Domain-Name Dispute Resolution Policy (UDRP), which allows for the recovery of disputed domain names, caused a great deal of misunderstanding, given that a review of all rights protection mechanisms (RPMs) has already been conducted between 2016 and 2020 and its final recommendations have not yet been examined by the ICANN Board. Now this review to validate the recommendations is scheduled to take place at best in the summer of 2022, by which time the aforementioned ePDP should be finalised. This example illustrated the gap that is being created between the community’s expectations for decisions and ICANN’s decision-making bodies, which seem to be overwhelmed by the policy negotiation processes that are piling up and stretching out over time, risking rendering decisions obsolete if they are made too late. According to some participants, this even affects ICANN’s ability to continue to carry out its mission as set out in its founding documents: To preserve and enhance the operational stability, reliability, security and global interoperability of the Internet.

“Prioritisation”, the word is out

On the first day of the sessions, ICANN CEO Goran Marby defended himself against the idea that the Board was slow to make decisions. He pointed out that the Board had recently examined 228 recommendations from the Competion Consumer Choice & Consumer Trust (CCT), which had just conducted a review to assess the extent to which the expansion of generic TLDs, gTLDs, had promoted competition, consumer confidence and consumer choice. 166 have been approved to date, 44 placed on hold and 18 rejected. Many of these measures are correlated with research and data collection to better understand market trends for new gTLDs.

Goran Marby also justified the delays in decision-making by the large number of ongoing and overlapping issues and by the fact that ICANN sometimes needs additional expertise to make decisions. In response to the criticisms, he also indicated that ICANN is now working on some form of prioritisation, a wish expressed by NAMESHIELD that seems to have been heard. However, Marteen Botterman of the Board nuanced this by specifying that prioritisation is not the Board’s responsibility, as it must ensure that the multi-stakeholder model is respected and must therefore maintain a certain neutrality on the subjects submitted to it.

A risk of fragmentation

From an organisation that has difficulty in making decisions, to its questioning, there is only one step. From the first day of the sessions, Goran Marby, who was particularly involved in the exchanges, spoke of “threats to ICANN”. ICANN is working on a risk management framework for the organisation. He also spoke of the need to talk more closely with governments as the current governance model is being challenged. Indeed, one only has to look at Russia to see that in November 2019, the Russian government introduced new regulations that create a legal framework for centralised state management of the internet within Russia’s borders. Russia has also proposed to hand over the management of the root servers to BRICS (Brazil, Russia, India, China and South Africa) member states. Proof that the States are going on the offensive in terms of their legislation, recent European directives also have an impact on the governance model, such as the General Data Protection Regulation (GDPR) and the forthcoming NIS2 (Network and Information Systems) directive, subjects which were also recalled at the summit. In China, for example, a law strengthening controls on digital services operated in China has just been adopted.

The failure of the ICANN governance model, if confirmed, could lead to a fragmentation of the DNS as we know it today, a fragmentation which takes shape as ICANN becomes bogged down in sterile debates. This summit has highlighted that the community and ICANN leadership have identified this major risk. The challenge for the future is to address it. We will watch the next ICANN summit scheduled in March 2022.

The observation that DNS regulation policies are bogged down, particularly at ICANN72, was widely shared by NAMESHIELD well before this summit. In particular, NAMESHIELD had expressed the need to prioritise topics in agreement with the community during the ICANN72 preparatory sessions. NAMESHIELD, which participates in working groups working on recommendations in the context of the periodic reviews conducted by ICANN, also advocated for re-enchanting voluntary work and helping diversify representatives in these working groups, in particular from small structures. Indeed many volunteers are now overwhelmed by the increasing volume of topics to be considered as the processes accumulate and decisions do not follow. New participants are discouraged from taking an interest in these topics by lengthy and cumbersome processes.

Image source : David Mark via Pixabay

New document : 5 minutes to understand domain names extensions (TLD)

5 minutes to understand - Domain names extensions (TLD) - Nameshield

The “Top Level Domains” also called TLD or extensions, are defined by the IANA (Internet Assigned Numbers Authority) which depends on ICANN since 1998.

ICANN and IANA are in charge of allocating Internet protocol (IP) addresses space, assigning protocol identifiers and managing the top level domain names system, i.e. the “Top Level Domains”.

Find out in this “5 minutes to understand” document, available for download on the Nameshield’s website, the different types of top level domains.