<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>
<DIV>Milton:</DIV>
<DIV>Great, glad the comments made sense. Mawaki, I think you will be
taking our full range of comments and making them into a final report, is that
right? Thank you!</DIV>
<DIV> </DIV>
<DIV>The reason we send multiple people to ICANN conferences is so that we can
talk and listen to the widest discussions possible. There were people at
the last ICANN conference specifically sent by their companies to pursue single
letter top level domains. The strategy they and the Business Constituency
will be pursuing (I am led to believe) is that only the sponsored and
"super-sponsored domain names" should be allowed, not the general opening up of
general gTLDs. On the one hand, they will want .AOL (just an example, I
have not seen the AOL people at ICANN); on the other hand, they don't want a
.WEB or .OPEN because it will conflict with their trademarks.</DIV>
<DIV> </DIV>
<DIV>So the strategy for us, I think, is to make it very clear to them that we
will block theirs until they let us have ours. Open up the whole gTLD
system (as you, Milton, propose) and all will be well. Open up only little
corners for the biggest companies in the world, and we will oppose.</DIV>
<DIV> </DIV>
<DIV>That's my thought and proposal for NCUC.</DIV>
<DIV> </DIV>
<DIV>As for the preamble, the deletion was inadvertent. It is good. I like
the idea of making it an appendix, or better, a "concluding NCUC note."
Regards, Kathy</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000 size=2>>We
should warn the GNSO Council about [snip] the new push from <BR>>them to
allow only "one-company" top level domains --<BR>> .DISNEY and .O
(Overstock.com) are being discussed. <BR><BR>On .O, I think you are
incorrect, Overstock wants "o.com," not .o as a TLD. I know of no initiative
to add one-letter TLDs.<BR><BR>On .disney, I see nothing wrong with a
company-specific TLD per se. In fact, I think it could be a progressive step
forward, further decentralizing power over DNS, and making it clear to big
companies that if they want domain names to be controlled in a specific way
they can get their own domains and run them that way instead of trying to
regulate the way the rest of us use DNS. Aside from that, why should
policy mandate that a company such as .aol, which has 10 million email
addresses, must be dependent on an external registry (.com) for such a
fundametnal part of their service? Why shouldn't they be allowed to
self-provision?<BR><BR>>(so let's delete the paragraphs about
ccTLDs).<BR><BR>You're absolutely correct about this! <BR><BR>One other point:
you (perhaps correctly) eliminated the preamble about our prior policy votes
on this. While I agree that it reads smoother without that, and that it
appears to conform better to the request for comments, I also think it is very
important to remind everyone, as often as possible, that this debate has been
going on for years, and that almost every time we consider it the majority
view is that there should be some new TLDs. Perhaps we could add an appendix
to that effect</FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV> </DIV></FONT></BODY></HTML>