[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ga-full] Re: [IPN] ICANN asked to create .union, .sucks and other new TLDs




Dear James:

I strongly support your groups committments to establish the listed top
level domain in your request to ICANN.  However I must advise you that
ICANN is not the TLD permission granting body.  I'm sure you understand
most of us think of ICANN as a glorified farce.

You should take the initiative and go ahead an establish your registries,
publish the information that they are available - and then proceed to
offer icann the opportunity to list them.  If they don't list your tld's
james, some other root server operator will.

The following URL lists some of them:

http://bind1999.pccf.net/resources/whos-who/

I would also like to point out that the namespace was always organization
on a first come first served basis.  I keep track of tlds and the .union
is already listed as a NAMESPACE gTLD.  You might want to work something
out with them concerning that.

Regards
Joe Baptista

On Wed, 1 Mar 2000, James Love wrote:

> http://www.cptech.org/ecom/icann/tlds-march1-2000.html
> 
>                          John Richard
>                          Essential Information
>                          P.O. Box 19405
>                          Washington, DC 20036
>                          http://www.essential.org
> 
>                          James Love
>                          Consumer Project on Technology
>                          P.O. Box 19367
>                          Washington, DC 20036
>                          http://www.essential.org
> 
> March 1, 2000
> 
> Esther Dyson
> Chair
> Internet Corporation for Assigned Names and Numbers (ICANN) 
> 4676 Admiralty Way, Suite 330 
> Marina del Rey, CA 90292  USA                     
> 
> Dear Esther:
> 
> This letter is to propose that Essential Information be permitted
> to establish a registry for new top level domains (TLDs).  It is
> our intention to create several TLDs that would facilitate free
> speech and criticism, and enable consumers, workers and others to
> organize.  Each of these TLDs will be operated under its own
> management charter.   The particular TLDs that we propose
> include:
> 
>      .union
>      .customers
>      .complaints
>      .sucks
>      .ecology
>      .isnotgreen
>      .isnotfair
>      .shareholder
>      .taxpayer
>      .unite
> 
> Our plans for each domain are as follows:
> 
>      .union
> 
> The .union TLD will be a "union label" for cyberspace.  EI is
> working with the international labor union community to develop a
> management system for .union.  Use of the domain would be
> restricted to bona fide labor unions.  Examples of use of this
> TLD would include:
> 
>      nike.union
>      exxon.union
>      microsoft.union
>      
> as well as other uses, such as dcprinters.union, for links to
> union printers in Washington, DC.  EI will be holding meetings
> with members of the labor community to discuss the policies for
> the management of this domain. It is our goal to use the .union
> domain to strengthen union organizing efforts, and to make it
> easier for workers at a firm to communicate with unions that
> represent workers at the firm, or who are seeking to organize
> workers at the firm, and for unions in different countries to
> coordinate efforts with each other.
> 
>      .customers
> 
> EI will create a self governance management organization for
> .customers.  This domain will be used to create democratically
> managed membership organizations of the customers of particular
> companies.  The customer organizations would be able to address
> any number of consumer problems.  For example, ford.customers
> might organize to address safety, service or warranty issues on
> Ford automobiles.  Safeway.customers might organize in favor of
> labeling of genetically modified foods.  Bellatlantic.customers
> might address Bell Altantic service and pricing issues in
> regulatory proceedings.  Bankofamerica.customers could address
> ATM charges and other bank fees.  
> 
> The .customers domain will be a cyberspace version of the
> "Citizens Utilities Boards" that were set up in several US states
> in the 1970s, funded by voluntary contributions from customers of
> public utilities.
> 
>      .complaints
> 
> EI is studying different models for the use of .complaints, to
> give consumers specific information about mechanisms to address
> product or company specific complaints, and to permit customers
> to share information about company practices with each other.
>           
>      .sucks
> 
> This TLD will be used to facilitate criticism of a firm or
> organization, such as aol.sucks, wipo.sucks, or even
> greenpeace.sucks.  We would not permit the organization that
> owned an associated domain to also own .sucks, so it would expand
> the name space in an important way.  The domain would also be
> available for other uses, such as work.sucks, life.sucks or
> television.sucks.  
> 
> Our plan is to create an independent non-profit free speech
> foundation that will be funded by fees from the .sucks
> registration.  The Dot Sucks Foundation (http://dot.sucks) will
> fund Internet related free speech fights. 
> 
> We recognize the .sucks TLD will be offensive to some persons,
> but we do not think that this should exclude .sucks from being
> approved by ICANN.  We believe the .sucks domain will be popular
> in the marketplace, and also generate important funding for the
> free speech rights of individuals and small organizations.
> 
>      .ecology
>      .isnotgreen
> 
> These two TLDs will be managed by environmental groups, to create
> forums to discuss and criticize the environmental policies of
> businesses, governments and other organizations.
> 
>      .isnotfair
> 
> This TLD would be used by civil rights groups to discuss issues
> of discrimination or workers rights.  We will be holding
> discussions with a variety of civil rights organizations to
> determine the management structure for the TLD.  It is our
> intention to create a space where the public can quickly review a
> company's record on employment practices.  For example,
> Texaco.isnotfair or coke.isnotfair might have links to
> information about discrimination suits involving these companies,
> or to organizations working on various discrimination or fairness
> issues. 
> 
>      .shareholder
> 
> This TLD will be used by church groups who organize shareholder
> suits on issues of conscience.
> 
>      .taxpayers
> 
> The .taxpayer TLD would be given to democratically elected
> taxpayer organizations that would monitor budgets and management
> practices of governments.   Examples of this TLD would include
> Arlington.VA.Taxpayers, Anchorage.AK.Taxpayers,
> London.UK.Taxpayers, Sidney.AU.Taxpayers.
> 
>      .unite
> 
> EI is evaluating different models for the use of .unite.    
>                                                        
> These are serious proposals to use the power of a TLD to enable
> citizens to improve civil society.  We believe the creation of
> domains like .union, .customers, .isnotgreen, and .isnotfair will
> create powerful mechanisms to share information and organize.
> 
> We would like to meet with the ICANN staff to discuss these
> proposals further.
> 
> Sincerely,
> 
> 
> John Richard                       James Love
> Director                           Director
> Essential Information              Consumer Project on Technology
> 
> 
> 
> -- 
> =======================================================
> James Love, Director           | http://www.cptech.org
> Consumer Project on Technology | mailto:love@cptech.org 
> P.O. Box 19367                 | voice: 1.202.387.8030
> Washington, DC 20036           | fax:   1.202.234.5176
> =======================================================
> 
> 
> 
> _______________________________________________
> Info-policy-notes mailing list
> Info-policy-notes@lists.essential.org
> http://lists.essential.org/mailman/listinfo/info-policy-notes
> 

--
This message was passed to you via the ga-full@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga-full" in the body of the message).
Archives at http://www.dnso.org/archives.html