La guerre des VGNs est engagée entre l'ICANN et la France.

En fait la question est soulevée de façon plus générale par la défense du droit des marques. Le travail que j'ai engagé sous http://dnsa.org/index.php/TmTLDs parait la seule solution correspondant aux positions initiales de l'ICANN et de l'OMPI.

1. attribuer des variantes alphabetiques pour chaque classe de marque
2. accepter les marques génériques sous le TLD de la classe, ex: champagne.vin
3. accepter les marques selon les règles de propriété industrielles de chaque pays. ex: mmum.fr.vin.

Sinon, nous allons simplement documenter comment supporter la DN CLASS "FR" de l'internet Français en plus de la classe "IN" de l'internet américain. Rappelons-nous que le DNS peut supporter 45.000 fichiers racine (comme celui de l'ICANN) ouverts à tous, et des milliards de fichiers racine privés.

L'histoire du "fichier racine autoritatif unique" n'est qu'un n-ième mensonge d'Etat américain. Comme les armes de destruction massives de Saddam Hussein. Le plus "amusant" est qu'un document politique de référence en vigueur de l'ICANN l'explique et réclame de l'expérimenter (depuis plus de 10 ans), détaillant comment faire pour que cela ne la gène pas (https://www.icann.org/resources/pages/unique-authoritative-root-2012-02-25-en). Mais il faut le lire, le titre du document donnant à croire l'inverse :-)

Je cite pour ceux qui ne s'en souvienne pas : http://sv2b.net/index.php/Appel_%C3%A0_une_exp%C3%A9rimentation_de_l%27%C3%A9volution_du_DNS";

Ci-joint pour l'info et le fun des échanges sur la liste ICANN de la transition NTIA ICANN.

Qui veut monter un Root (FR) avec moi ? On supportera ".beaujolais"

jfc

At 12:50 22/06/2014, michael gurstein wrote:
June 22, 2014 10:38 am
France lashes out at internet naming body Icann

By Hugh Carnegy in Paris

France has launched a strong attack on the US-based international body that
governs internet addresses, calling its decision-making "totally opaque" and
saying a move to assign domain names for wine could threaten talks on a new
transatlantic trade deal.

Paris will demand a big shake-up of Icann - the Internet Corporation for
Assigned Names and Numbers - at a meeting of its government advisory
committee in London on Monday, calling for a bigger say for states in its
governance.

France's anger has been triggered by a decision this year by Icann to go
ahead with the launch of the two domain names .vin and .wine, which critics
say could undermine international agreements on so-called geographical
indicators that restrict the use of labels, such as champagne and other
area-specific wines and foods.

FT paywall
http://www.ft.com/intl/cms/s/0/828ad97c-f94a-11e3-bb9d-00144feab7de.html#axzz35MZvsOdE
France's anger has been triggered by a decision this year by Icann to go ahead with the launch of the two domain names .vin and .wine, which critics say could undermine international agreements on so-called geographical indicators that restrict the use of labels, such as champagne and other area-specific wines and foods.

The European Commission, France, the UK and Spain have all appealed to Icann to halt the procedure on the two domain names unless safeguards for geographical indicators are assured.

But France has linked the issue to the broader question of how Icann is structured and governed.

"The problem is it is totally opaque, there is no transparency at all in the process," Axelle Lemaire, minister for digital affairs, told the Financial Times.

In a letter to Manuel Barroso, European Commission head, this month, Ms Lemaire and two senior ministers argued that the domain names could prejudice EU-US trade talks in which France and other countries are anxious to preserve geographical indicator rights. These stop, for example, American producers calling sparkling wine champagne, or blue cheese Roquefort.

"These decisions could imperil the current talks on the transatlantic [trade] partnership by forcing the imposition of a model by the means of technical discussions on internet naming," they wrote.

Their worry is that a private company which acquired the domain names could market products via, for example, a "champagne.wine" website that were not authentic champagne, without legal recourse.

Ms Lemaire also wrote this month to the Icann board saying the domain name process threatened to "undermine confidence in your organisation".

The US agreed this year to give up its ultimate control of Icann exercised through the commerce department, but Ms Lemaire made clear France wants to go further, seeking to rally support for a global conference on its overhaul.

Paris wants it set up under international law with a redefined mission and overseen by a "general assembly" of stakeholders that would include governmental representation on a "one country, one vote" basis, Ms Lemaire said.

In her letter to the Icann board she wrote: "The lack of adequate redress mechanisms and, above all, the lack of accountability demonstrate the need for significant reform of Icann even before the current debate on the global internet governance system comes to a conclusion."

Icann, founded in 1998, is a non-profit making organisation grouping private sector, public sector and technical interests in what it calls a "bottom-up, consensus-driven, multi-stakeholder model".

Three years ago, Icann decided to lift most restrictions on the naming of top level domains. It has since received applications for almost 2,000 new domains and has already delegated about 300 of them, including .beer,london and .luxury. Among the new domains are ones using non-Latin characters such as Arabic and Chinese.

The process has not been without controversy. Some corporations are worried that they will need to spend large amounts of money buying addresses in the new domains in order to protect their trademarks from cybersquatters or fraudsters.

Others are worried about the potential consequences of generic terms such as .search or .music falling under the control of a single corporation. Google and Amazon are among 13 organisations competing for the domain .app.

Additional reporting by Robert Cookson in London


At 17:59 22/06/2014, Michel S. Gauthier wrote:
it is likely that ICANN and IETF will die from the NTIA retirement after the fragmentation of the technology acknowldged by RFC 6852. This will not happen in one single day with an happy off-the-shelf replacement since no one prepared it. The ".wine" and ".vin" show how uncoordinated ICANN is with WTC, WIPO, GAC, users, etc. (Please consider the DNSA work on the matter http://dnsa.org/index.php/TmTLDs).

We therefore head towards rough times for ICANN until a transition is completed. It is a good thing to have a professionl at the helm, who is able to better explain than Steve Crocker or other BoD Members, and who has good ties with this list.

At 21:24 22/06/2014, Barry Shein wrote:
Not intended as any comment on this particular issue I've long said to
others involved that one of these days "adults" are going to show up
at this party.

It looks like it's finally happening.

So much for the wannabe academics, policy wonks, and trust fund babies
running the show...

(Milton: oh stop it -- you are an actual academic.)

Barry Shein

The World              | [email protected]           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 800-THE-WRLD        | Dial-Up: US, PR, Canada
Software Tool & Die    | Public Access Internet     | SINCE 1989     *oo*

At 21:27 22/06/2014, Barry Shein wrote:
From: Pranesh Prakash <[email protected]>
>When someone says access to <public utility> should be free, they do not
>mean that providing access to <public utility> doesn't cost money (often
>borne by taxpayers or corporations).  They mean that access to <public
>utility> should be free.
>
>I don't necessarily agree with this viewpoint.  But it doesn't help to
>argue whether there are costs associated with <public utility> when no
>one is making an argument that there are no costs associate with <public
>utility>.

Exactly, what I was trying to say but well put. Thank you.

Without such definitions and boundaries the discussion takes on a
sophomoric tone.

Barry Shein

The World              | [email protected]           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 800-THE-WRLD        | Dial-Up: US, PR, Canada
Software Tool & Die    | Public Access Internet     | SINCE 1989     *oo*

At 21:59 22/06/2014, Brian E Carpenter wrote:
I seriously doubt that any court will see a difference between
champagne.com, champagne.fr and champagne.vin when it comes
to protecting the designation of wines from Champagne. This is
just more of the huffing and puffing we've seen for the last 15
years; I don't see it as a sign of real change.

On 22/06/2014 20:11, Patrik Fältström wrote:
each RFC that sets the rules IANA is to follow.

Well, most of them are clear .

But indeed, you are correct to remind us that there is a lot of
detailed work behind the externally smooth running of the IETF-defined
registries, and there's continued technical debate about even the
oldest ones such as the port registry (which is considerably older
than the IETF itself). So we shouldn't be surprised that there is
still debate about the TLD and address registry policies too. It
would be worrying if there was no debate. What is unusual about
the TLD registry is that the debate has become a political football.
Brian

At 18:28 22/06/2014, John Curran wrote:
You don't have to make use of these default parameter coordination arrangements
when doing your own communications, but be advised that many, many folks find
that these arrangements are very convenient; one might even argue that these
IANA registry arrangements have had a foundational role in the success of the
Internet that we all enjoy today.

This is what the US VGN is.

M S G


_______________________________________________
comptoir mailing list
[email protected]
http://cafedu.com/mailman/listinfo/comptoir_cafedu.com

Répondre à