|
.xxx approval a positive sign
|
Log in/Create an Account
| Top
| 42 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
Finally someone has articulated a good point about the addition of .xxx. Thanks for posting your well said comment on the front page, rather than after the mindless comments attached to yesterday's post on .xxx.
ICANN taken a good step, and this is a sign that new gTLDs will be provided with the same review. If you meet the technical standards and have the funding to open a registry, you should be allowed in.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
"ICANN's job is to coordinate the top level of the domain name space."
That seems like a very different job description
from the previous research-academic-community claim
that ICANN handles the "IANA Task".
Also, the reality is that ICANN spends much of
their time managing their Registrar Franchisees,
their domain name retailers.
ICANN is also an expensive baby sitter for the
aging, BIND-based, legacy root server operators.
Since those root servers are used less and less,
that part of the job description often fades away.
ICANN's real lock is of course on the 32-bit
address space allocations doled out by ARIN and
their sub-contractor Nominum. Note the recent
ACM award to Jon Postel's crony Paul Mockapetris
with no mention that he is funded from the
address space leasing game.
It is interesting that the average ICANN watcher
and even a so-called "expert" like Mr. "Ruling
the Root" Mueller, would not mention ICANN's
role in address space management in their job
description. A recent poll of ISPs and other
people who claim to be in the "Internet Industry"
shows that they view that ICANN does Names and
ARIN does Numbers. That is the same split that
happened years ago when Verisign walked away
from the numbers game, to make a killing in names.
It turns out that Verisign actually makes their
easy money on numbers, called "certs". Large,
cryptic numbers that they claim to be hard to
deduce [for a fee].
It will be interesting to see what ICANN plans
to do with the new DNS. Their recent hiring of
a crypto software person, seems to indicate
they realize their current "job" has a limited
life. Job security is Job One at ICANN. Keep
watching, ICANN will tax you one way or the
other.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
I think if we had a world where every reasonable proposal got a number and got in the queue, I'd agree with you Milton. And that's the best of all possible worlds. But in this world of needless rationing, I don't see why the insides like Palage should vault to the head of the queue over others. Nor do I see why this proposal is better than many others.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
Good points, all. I'm not sure where or when ICANN gained the impression that they were to make judgements on the market capabilities of any extension.
I appreciate someone making a succinct and well-worded argument otherwise. When ICANN is reduced to misrepresenting an application, as was done with IOD's .WEB application, it is probably safe to assume that particular organization has lost a good bit of its original mandate and direction.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
.XXX Your .ORGy Tax Dollars at Work
The same crowd that runs .ORGy is exxxpading to run .XXX
Check out Dave Farber and Rodney Joffe's NEW.NET .XXX names. Farber and Joffe are both Jon Postel cronies. Vinton Cerf and Steve Crocker went to the
same high-school as Jon Postel.
NEW.NET has Pussy.XXX Reserved.
http://www.Pussy.ORG is the staging site.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
Bill Clinton to be Tapped as .XXX Ombuttsman
With Hillary down-stairs in the whitehouse Oval
Office in '09, Bill Clinton will have a lot of
time on his hands, up-stairs, with the "staff".
Bill Clinton will be able to be the .XXX Ombuttsman
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
Does This Mean There Will Be Hot Babes at ICANN ?
The chicks that go to ICANN meetings are real dogs. .XXX and .PRO should bring a new look to ICANN meetings.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
I am as you know usually quite critical of ICANN but in this case I was relieved to see that they did the right thing. In this case ICANN acted as it should have, as a neutral technical coordinator, unconcerned about content regulation issues. We really do not want governance bodies with technical leverage over the internet exploiting that power to impose their own or some lobbying group's values on Internet users.
Yes, you heard it here first, Mueller praises ICANN!
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
"that strange but deeply-rooted band of old-line techies who believe that their technical experience can be translated into a generalized claim that they know what's best for the Internet"
does that strange and deeply-rooted band of
old-line research-academic amateur regulators
[with way too much time on their hands]
THINK "they know what's best for the Internet" ???
How about the marketplace deciding ?
Do parents have a say ?
How about people and companies that actually
own the equipment (including PCs) that create
the Internet ?
How many ICANN groupies own domain names or
any substantial components that make the Internet
a netWork as opposed to a NotWork ?
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
The New Root from the U.S. Government - NON-.XXX
What people are seeing is a game. In the old days,
the U.S. Government operated some of the key root
servers. Some were portrayed as being in military
bases. That hush-hush government clout, was **used**
by the insiders to build the base of their
multi-level-marketing regime (ISOC, ICANN, ARIN, etc.).
Now that the base is built, and boat loads of
money are flowing into ICANN, the U.S. Government
is no longer needed or desired. ICANN can thumb
their noses at the U.S. Government. Canadian and
British businessmen have rolled into the U.S.
with their .XXX TLD and intend to put it into
the U.S. Government-run root servers. They do
not care if the U.S. Congress pulls support for
those root servers. ICANN has enough money to
put up their own root servers.
ICANN is longing for the day when the U.S.
Government openly says, "We have nothing to do
with that creep show in .LA". ICANN and the
insiders of course were happy to **use** the U.S.
Government as a 900 lb. gorilla to stomp out
any opposition in the early days of building
ICANN. They can now send the gorilla off to
Africa or the Middle East.
What some people are concerned about (right or
wrong) is that an ICANN without the U.S.
Government, is an ICANN without any clout. If
people thought ICANN was a joke in the past, it
will really be a joke without U.S. Government
backing.
Fortunately, time has progressed and it does not
really matter. The new DNS technology does not
rely on ICANN or the the U.S. Government. That
may not stop the U.S. Government from constructing
a new set of root servers, just in case. That
will also not stop State Governments from putting
up their own TLD servers, without ICANN approval.
The Christian Coalition and the Religious Right,
that elected George W., can also not be stopped
from putting up their own root servers. The
ICANN root servers will be just one of many and
WITHOUT U.S. Government endorsement. There is no
way the U.S. Government will openly endorse the .XXX and .PRO "industries", even though they tax
both industries.
The under-world (mafia) can also not be prevented
from putting up their own root-servers to make
sure that THEIR .XXX and .PRO TLDs operate
smoothly. They of course will add .CASINO and
a variety of other TLDs, without needing ICANN.
What some people are reacting to is that .XXX
will expose the corrupt under-belly of the .NET
that most people know is there. They are worried
that, once exposed, *they* may become the targets
of more scrutiny. THEY do not want any scrutiny. .XXX will likely bring scrutiny they do not like.
Too bad. The ICANN corruption is going to bring
scrutiny from so many sectors ICANN will not
know what hit it.
Stay tuned and watch the fireworks.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
"ICANN does not propose TLD applications, the community does. I do agree that we do have a paradox where in order to try to vet the applications, a process is put in place which is expensive and difficult to navigate. This makes it harder for bad applications to get in, but also makes it more difficult for less funded socially positive applications to make it through the process. This is something we need to think about as we work on the RFP process for gTLDs. This is a valid concern.
I haven't been on the ICANN board that long, but I have never seen anything to make me believe that ICANN approves TLDs based on whether they provide more revenue to ICANN or not. It may appear this way because financial viability is one of the criteria. If a TLD operator is not financially viable, it much more likely there will be trouble for the registrants or that the TLD operator will do something unreasonable. Clearly, financial viability also means that it is likely ICANN will receive revenue.
But to put .xxx in context... We are just going through all of the sTLDs that were submitted this round. We had independent evaluators involved in providing a first round of feedback and the board is going through each of the applications. .xxx was not the first one approved and is not the last."
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
ICANN to Require RED Lights in .PRO Porch Lights
ICANN is set to add new regulations to their .PRO ladies.
Red Lights will be required to be installed in
all porch lights, especially after dark. This will
allow law enforcement officers to better provide
protection and to take advantage of services when
off duty.
Whois information will be reviewed by Madam Marilyn to make sure it points to her brothel syndicate.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
The problems will not surface until later, the apparent extra freedom to exist in .xxx, will more than likely be an increasingly regulated existence.
Once .xxx exists overtime governments will be able to mandate that all xxx material should ONLY exist in .xxx
Then once it is contained only in .xxx they can analyze, define and legislate what is appropriate and what, where and when it should not be permitted.
Though America's version of xxx may be very different from Holland or Sweden or China or Iran versions.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
If ICANN had not created an artificial scarcity of Top Level Domain name grants than I would agree that looking into the semantics and intended use of the applicant would be wrong. I said so quite explicitly in my platform when I ran for the ICANN board in year 2000.
However, ICANN has in fact created an artificial scarcity. And ICANN's nod, under the current circumstances, amounts to a highly valuable preference.
As long as ICANN maintains the artificial scarcity then it is indeed appropriate to pick and chose those who will receive the grant based on what they will do. And purvaying porn isn't something that deserves to be placed first - it deserves to come the end of the queue.
The answer, and I know we both agree on this, is to eliminate the artificial scarcity of TLDs. When that day comes, and under ICANN as it now exists I think that day will be a long time coming, then we can be blind to intended use. But as long as ICANN insists of making intended us a criteria, we should insist that those who receive the grant are those who contribute to social and economic progress rather than degrade it.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
.WOW , ICANN has really sucked this guy's brains out.
"The slowness in part is because ICANN is trying to come up with a better way of approving TLDs that allows TLDs to be allocated fairly and easily. The GNSO and other organization are working on a process for generic TLD RFPs. The problem is, the recommendation has not been completed."
What a load of .BS
How many years has it been ? 1998 to 2005 ?
ICANN is **still** working on a "better way" ?
1. ICANN does not care about fairness, Postel never did. The closed private digerati are not
into fairness. Esther Dyson set that pace for ICANN.
2. ICANN does not care about simple or easy, there is no money in that. If ICANN wanted simple or
easy, they would just take the marketing info
from .COM and use that to expand the root zone
as critical mass forms around an extension.
Registry provider companies would line up and
maybe be selected by a lottery for the next TLD
in the queue. ICANN does not want a lot of
Registries, they may band together and realize
that they do not need ICANN. ICANN is like an
airport regulator, 4 rental car companies is
one too many in their view.
The good news is that .XXX will cause a new
root to be formed to protect children and people
who want no part of the ICANN sleeze. It will
be interesting to see how people boycott
Registrars that sign up to sell .XXX names.
Also, it is time for the U.S. Government to
step in and restart from scratch. The FCC will
have a strong voice in all of this going forward
and will be able to help end the Cerfdom.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
Michael Palage, President
Palage consulting has an ongoing long standing contractual relationship Jason Hendeles and two of his companies ATC (ICANN accredited registrars) and ICMRegistry (one of the 47 registry applicants from last year). Palage consulting similarly has a long standing relation with Afilias the registry operator for .INFO, providing registrars accreditation, trademark and policy consulting services. Palage consulting provides part-time consulting services to DomainPro an ICANN accredited registrar, and at this time serves as its voting representative within the constituency. In addition, I have provided pro bono legal and consulting services to a number of registrars on registrars over the years.
(November 28, 2001)
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
If Registrar R217 (who submitted the second shortest list in the .biz2B and got 6 registrations) is ATech / A Technology Company, Inc...
then there is a strong link with Michael Palage of Afilias, and I suspect that this list was closed to the public so that its own owners could benefit...
The practice of some registrars in submitting deliberately short lists to "queue-jump" in Landrush situations was demonstrated very clearly in .biz2B and .info LR2. The shorter your list, the sooner your name came up in the round-robin process. Some registrars like Signature Domains appear to have applied for a tiny number of domains just for themselves, to play the system. I believe Jason Hendeles was involved in the same thing.
Jason Hendeles is Founder/CEO of ATech Registrars
Jason Hendeles is Founder/CEO of ICM Registry Inc
Michael Palage of Afilias is/was linked to ICM as their Chief Policy Officer. He has confirmed this in his "Disclosure" in the Registrars Mailing List in December 2001.
ICM may have been hoping to run a new .XXX registry and gained adult.info in LR2, using their co-company ATech Registrars
This means that ATech submitted a tiny list (to gain advantage) and submitted this application for its own co-company and co-owner
WHOIS details - showing Jason's e-mail:
Domain ID: D2264928-LRMS
Domain Name: ADULT.INFO
Created On: 13-Jul-2002 19:16:49 UTC
Expiration Date: 13-Jul-2004 19:16:49 UTC
Sponsoring Registrar: A Technology Company dba Namesystem.com (R217-LRMS)
Status: HOLD
Status: OK
Registrant ID: C2355539-LRMS
Registrant Name: Cadomain RegistrY Inc
Registrant Organization: Cadomain Registry, Inc
Registrant Street1: 130 Adelaide Street West
Registrant Street2: Suit 2500
Registrant City: Toronto
Registrant State/Province: Ontario
Registrant Postal Code: M4H 2M2
Registrant Country: CA
Registrant Phone: +1.4168681080
Registrant Email: admin@icmregistry.com
Admin ID: C2355554-LRMS
Admin Name: A Technology Company Inc
Admin Organization: A Technology Company Inc
Admin Street1: 3 Hawthorn Gardens
Admin City: Toronto
Admin State/Province: Ontario
Admin Postal Code: M4W 1P
Admin Country: CA
Admin Phone: +1.4169293695
Admin Email: jason@icmregistry.com
Billing ID: C2355554-LRMS
Billing Name: A Technology Company Inc
Billing Organization: A Technology Company Inc
Billing Street1: 3 Hawthorn Gardens
Billing City: Toronto
Billing State/Province: Ontario
Billing Postal Code: M4W 1P
Billing Country: CA
Billing Phone: +1.4169293695
Billing Email: jason@icmregistry.com
Tech ID: C2355554-LRMS
Tech Name: A Technology Company Inc
Tech Organization: A Technology Company Inc
Tech Street1: 3 Hawthorn Gardens
Tech City: Toronto
Tech State/Province: Ontario
Tech Postal Code: M4W 1P
Tech Country: CA
Tech Phone: +1.4169293695
Tech Email: jason@icmregistry.com
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
At the most basic level here, I am concerned that your proposal treats .kids as something of secondary importance, an adjuct to a product (.xxx) aimed at the sex industry. I do not think it is appropriate that the kids domain name sector (or even kid-based content) should be financed by the profits made out of selling .xxx domain names.
The pertinent part of your proposal was:
"To this end, ICM Registry will contribute $6 per domain name for the creation of the .KIDS corporation, support the operation of the .KIDS registry, develop research on children's programming, protect children form exposure to adult-oriented content and provide children with tools to go on-line"
Anyway, I'm interested - what percentage of your .kids advisory board members will be aged under 12? What percentage aged under 18? What consultation have you done with young people? How will they meet? Where? How often? How will they (adults and youth) be selected?
Finally, Michael Palage is both Senior Vice President of your company and a member of an ICANN working group on intellectual property. Is that a conflict of interest? (Maybe not, it just seems that way).
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
>What if a .kids site includes information that you, the censor, >determine not to be appropriate? Can they still be part of the .kids >domain space?
No. You identify a key problem with the .KIDS space. It is difficult to agree on what is and is not acceptable for kids. That is why in our proposal we focus .KIDS on 12 and under. When dealing with teenagers parents have a wide diversity of what is and is not acceptable (i.e. birth control, abortion, etc.)
The Code of Conduct for the .KIDS will eventually be created by consensus building efforts lead by the Policy Advisory Board. This task will not be easy, so ICM Registry believes that the .KIDS TLD should start off with some basic OBJECTIVE standards as to what is not acceptable within the .KIDS TLDS (i.e. nudity, vulgar language, etc.). Although these OBJECTIVE standards may be a little Draconian, it seems the only way to start off.
As ICANN adds additional green-space and red-light TLDs to the root. The Policy Advisory Board for each TLD will be able to get a little more creative as modifications to the Code of Conduct and policy considerations. But I believe one must crawl before they walk, and walk before they run.
I appreciate your comments and suggestions. We have been refining this proposal for eight months and the refinement process will be a never ending process. I apologize if my tone was a little defensive.
Thanks again.
Michael D. Palage
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
ICM Registry Inc., which has proposed to become the registry for two new top level domain names -- .xxx and .kids -- announced today the endorsement by representatives of a leading watchdog group and adult content providers of its concept to shield children from adult Web content by creating virtual red-light and green-light districts on the Internet.
ICM Registry submitted its proposal to the Internet Corporation for Assigned Names and Numbers (ICANN) on Oct. 2 as part of the ICANN process of seeking registries for new domain names to expand the selection of top level domains (TLDs) beyond the current .com, .net and .org. The proposal also outlined the ICM plan to establish .kids as a not-for-profit domain and provide financing to develop research on kid-friendly programming and means of protecting children from exposure to adult-oriented content.
"The new domains are a viable alternative to mandatory filtering of any kind," said Michael Palage, chief policy officer of ICM Registry. "These TLDs would allow parents, schools and libraries to automatically identify and filter access to the Internet's .xxx red-light district, a logical step that is now supported both by organizations seeking to protect children and adult content providers. At the same time, the .kids domain would be the green-light area with safe sites for children under the age of 12 that focus on education, entertainment, community organizations and services."
With community groups and politicians demanding a resolution that balances rights and freedoms, the use of .xxx and .kids is a way of distinguishing child-friendly from adult-oriented material.
"Almost 35 percent of Internet traffic features adult-oriented material and our proposal will preserve the Internet as a key medium for consumer choice and the free exchange of ideas," said Palage, an attorney who has been active in Internet affairs since 1995 and currently serves as co-chairman of the ICANN Working Group B, which is involved with policies on safeguarding trademarks on the Domain Name System.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
.XXX will make it much easier to continue tagging
IP address blocks to be filtered INTO the IPv4
legacy sewer. That will make those blocks available
for other uses by schools, churches, etc.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
ICANN .GAY Director Showcases Male Rectal Photos
That's what ICANN calls a "mature individual" ?
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
What About .XXX Registrations People Don't Make?
Narrow minds such as Joe Sims and Marilyn Cade
and the rest of the ICANN WHOIS police never
seem to consider registrations people do not want.
What happens when someone registers a .XXX name
in the name of their "friend" at work. They then
put up some pics and drop a **hint** to the boss
that their co-worker has a porn site. A quick
check of that all-so-important and valid WHOIS
information shows, that, sure enough, so-and-so
owns a .XXX name. So-and-so is likely never told
and never knows why they were fired. The "friend"
gets the job that is now opened up.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
