The Future of <span id="st" name="st" class="st">WHOIS</span> Policy<br><br>This is a contentious issue, involving tradeoffs between privacy, anonymity, and accountability pitting consumers' right to information with domain owner's privacy rights. <br><br>A public discussion webcast held in New York is available for download here <a href="http://punkcast.com/1064/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://punkcast.com/1064/</a><br><br><div id="mb_0"><a href="http://www.icann.org/announcements/announcement-24nov06.htm" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.icann.org/announceme<wbr>nts/announcement-24nov06.htm</a><br> <br> ICANN launches Public Comments on <span id="st" name="st" class="st">WHOIS</span> Task Force Report<br> <a href="http://gnso.icann.org/issues/whois-privacy/prelim-tf-rpt-22nov06.htm" target="_blank" onclick="return
top.js.OpenExtLink(window,event,this)">http://gnso.icann.org/issues<wbr>/<span id="st" name="st" class="st">whois</span>-privacy/prelim-tf-rpt<wbr>-22nov06.htm</a> <br> <br> The Public Comment Period is from 24 November 2006 to 15 January 2007.<br> <br> Send comments to: <a href="mailto:whois-services-comments%40icann.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"><span id="st" name="st" class="st">whois</span>-services-comments@icann<wbr>.org</a><br> View comments at: <a href="http://forum.icann.org/lists/whois-services-comments" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://forum.icann.org/lists<wbr>/<span id="st" name="st" class="st">whois</span>-services-comments</a><br> <br> ICANN is launching a public comments period on the Preliminary Task<br> Force Report on <span id="st" name="st" class="st">Whois</span> Services. This report forms part of the GNSO<br> policy development process (PDP) on <span id="st"
name="st" class="st">Whois</span> which seeks to build consensus<br> on policy issues in the generic top level domain (gTLD) space. The<br> public comment period will last from 24th November, 2006 to 15 January,<br> 2007.<br> <br> After the public comment period, the <span id="st" name="st" class="st">Whois</span> Task Force will consider the<script><!-- D(["mb","<br>\npublic comments received and prepare a final task force report for<br>\nsubmission to the GNSO Council. The Council is expected to deliberate on<br>\nthe final task force report in early 2007, and work to achieve a<br>\nsuper-majority vote on a recommendation to the ICANN Board. The GNSO<br>\nCouncil will then submit a report to the ICANN Board, and the Board will<br>\nthen carry out its own deliberations and voting.<br>\n<br>\nThis report sets out the key findings that have emerged during the work<br>\nof the Whois Task Force on the following terms of reference:<br>\n<br>\n(3) Determine what data collected
should be available for public access<br>\nin the context of the purpose of Whois. Determine how to access data<br>\nthat is not available for public access. The current elements that must<br>\nbe displayed by a registrar are:<br>\n<br>\n- The name of the Registered Name;<br>\n<br>\n- The names of the primary nameserver and secondary nameserver(s) for<br>\nthe Registered Name;<br>\n<br>\n- The identity of Registrar (which may be provided through Registrar's<br>\nwebsite);<br>\n<br>\n- The original creation date of the registration;<br>\n<br>\n- The expiration date of the registration;<br>\n<br>\n- The name and postal address of the Registered Name Holder;<br>\n<br>\n- The name, postal address, e-mail address, voice telephone number, and<br>\n(where available) fax number of the technical contact for the Registered<br>\nName; and<br>\n<br>\n- The name, postal address, e-mail address, voice telephone number, and<br>\n(where available) fax number of the administrative
contact for the<br>\nRegistered Name.<br>\n<br>\n(4) Determine how to improve the process for notifying a registrar of<br>\ninaccurate Whois data, and the process for investigating and correcting<br>\ninaccurate data. Currently a registrar "shall, upon notification by any<br>\nperson of an inaccuracy in the contact information associated with a<br>\nRegistered Name sponsored by Registrar, take reasonable steps to<br>\ninvestigate that claimed inaccuracy. In the event Registrar learns of",1] ); //--></script><br> public comments received and prepare a final task force report for<br> submission to the GNSO Council. The Council is expected to deliberate on<br> the final task force report in early 2007, and work to achieve a<br> super-majority vote on a recommendation to the ICANN Board. The GNSO<br> Council will then submit a report to the ICANN Board, and the Board will<br> then carry out its own deliberations and voting.<br> <br> This report sets out the key findings
that have emerged during the work<br> of the <span id="st" name="st" class="st">Whois</span> Task Force on the following terms of reference:<br> <br> (3) Determine what data collected should be available for public access<br> in the context of the purpose of <span id="st" name="st" class="st">Whois</span>. Determine how to access data<br> that is not available for public access. The current elements that must<br> be displayed by a registrar are:<br> <br> - The name of the Registered Name;<br> <br> - The names of the primary nameserver and secondary nameserver(s) for<br> the Registered Name;<br> <br> - The identity of Registrar (which may be provided through Registrar's<br> website);<br> <br> - The original creation date of the registration;<br> <br> - The expiration date of the registration;<br> <br> - The name and postal address of the Registered Name Holder;<br> <br> - The name, postal address, e-mail address, voice telephone number, and<br> (where available) fax number
of the technical contact for the Registered<br> Name; and<br> <br> - The name, postal address, e-mail address, voice telephone number, and<br> (where available) fax number of the administrative contact for the<br> Registered Name.<br> <br> (4) Determine how to improve the process for notifying a registrar of<br> inaccurate <span id="st" name="st" class="st">Whois</span> data, and the process for investigating and correcting<br> inaccurate data. Currently a registrar "shall, upon notification by any<br> person of an inaccuracy in the contact information associated with a<br> Registered Name sponsored by Registrar, take reasonable steps to<br> investigate that claimed inaccuracy. In the event Registrar learns of<script><!-- D(["mb","<br>\ninaccurate contact information associated with a Registered Name it<br>\nsponsors, it shall take reasonable steps to correct that inaccuracy."<br>\n<br>\n(The full terms of reference are available here:<br>\n<a
href\u003d\"http://gnso.icann.org/policies/terms-of-reference.html\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\">http://gnso.icann.org/policies<WBR>/terms-of-reference.html</a>)<br>\n<br>\nPublic comments are particularly invited on specific proposals in the<br>\nreport:<br>\n<br>\n* The Operational Point of Contact (OPoC) proposal pages 38 to 42<br>\n * The Special Circumstances proposal pages 43 to 49<br>\n * The five proposals in the discussion on access to data pages 24<br>\nto 27.<br>\n<br>\n-- <br>\nGlen de Saint Géry<br>\nGNSO Secretariat - ICANN<br>\ngnso.secretariat[at]gnso.icann.org<br>\n<a href\u003d\"http://gnso.icann.org/\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\">http://gnso.icann.org</a><br>\n-- <br>Office: +254 20 2732311, 2732312 <br>Mobiles: <WBR> <br>GSM: +254 722 739100 (safaricom)<br>CDMA: +254 20 2013393
(telkom)\n",0] ); D(["ce"]); //--></script><br> inaccurate contact information associated with a Registered Name it<br> sponsors, it shall take reasonable steps to correct that inaccuracy."<br> <br> (The full terms of reference are available here:<br> <a href="http://gnso.icann.org/policies/terms-of-reference.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://gnso.icann.org/policies<wbr>/terms-of-reference.html</a>)<br> <br> Public comments are particularly invited on specific proposals in the<br> report:<br> <br> * The Operational Point of Contact (OPoC) proposal pages 38 to 42<br> * The Special Circumstances proposal pages 43 to 49<br> * The five proposals in the discussion on access to data pages 24<br> to 27.<br> <br> -- <br> Glen de Saint Géry<br> GNSO Secretariat - ICANN<br> gnso.secretariat[at]gnso.icann.org<br> <a href="http://gnso.icann.org/" target="_blank" onclick="return
top.js.OpenExtLink(window,event,this)">http://gnso.icann.org</a><br> ----------- <br><br>rgds,<br><br>/Alex<br><br>Office: +254 20 2732311, 2732312 <br>Mobiles: <wbr> <br>GSM: +254 722 739100 (safaricom)<br>CDMA: +254 20 2013393 (telkom)</div><br><br><b><i>John Walubengo <jwalu@yahoo.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> QED (though I can't seem to remember what that meant...)<br><br>But I think Judy, you have actually solved the riddle! none<br>of the official site were hacked. someone simply<br>registered similar names of the official sites and then put<br>up whatever
they wanted on it....<br><br>But that is technical details. What I must admit is that<br>whoever did it was simultaneously simplistic and brilliant<br>(perfect profile for nasty hackers). I do ofcourse condone<br>the act but cannot fail to acknowledge this type of<br>intelligence...i highly suspect it was Kenyan proving yet<br>again that Kenyans are at the top of their game - both the<br>positive and bad side of things.<br><br>Nway, in the absence of the ICT Bill/Act, I wonder if<br>anyone/someone can hold this chap accountable? ICT<br>Lawyers, here is chance to make another first in Kenya...<br><br>walu.<br><br><br><br>--- Judy Okite <judyokite@gmail.com> wrote:<br><br>> I actually came across a very interesting link....in<br>> regards,with this<br>> matter....<br>> <br>> http://www.mambogani.com/forums/index.php?showtopic=6273<br>> <br>> They key part,being:<br>> <br>> <br>> Folks,<br>> <br>> A few days ago, some sick nuthead, whom
we suspect is a<br>> NARC-K sympathiser,<br>> or perhaps the latest government project, using<br>> mwaikibaki@yahoo. com<br>> address, discreetly sent e-mails to individuals who are<br>> known to support<br>> ODM-K, especially in Washington DC. The e-mails simply<br>> notified them of the<br>> following websites: Kalonzofoundation. org. and<br>> odm-kenya.org. Clicking on<br>> the Kalonzofoundation. org URL re-directs one to the<br>> Raila2007.com website,<br>> with the top browser bar showing a message that reads:<br>> "Kalonzo backs<br>> Raila". Clicking on the odm-kenya.org URL re-directs one<br>> to a Kenya<br>> government website. But a quick check reveals that<br>> neither<br>> kalonzofoundation. org belongs to Hon. Kalonzo Musyoka<br>> Foundation, nor does<br>> odm-kenya.org belong to ODM-K. Needless to say, the<br>> fraudsters are<br>> attempting to hoodwink Kenyans into believing a lie. This<br>>
is only a sick<br>> prank, as none of the genuine websites have been hacked.<br>> <br>> The fact is, the correct website for Hon. Kalonzo Musyoka<br>> is:<br>> www.kalonzomusyokaf oundation. org, while ODM-K's<br>> website, which is not<br>> fully developed is: www.odmk.org. None of these websites<br>> were hacked. The<br>> Standard's headline, unfortunately, is misleading. The<br>> pranksters simply<br>> registered variations of the names of the said<br>> organizations and re-directed<br>> any queries to Raila2007.com, and to the government<br>> website respectively.<br>> This is not the same as hacking. Anyone with a website<br>> can re-direct their<br>> URLs to another website. It doesn't take half-a-brain to<br>> do this.<br>> The pranksters simply juggled the names and registered<br>> them. The jargon for<br>> this kind of registration is "cyber-squatting" . People<br>> register names with<br>> the
hopes of cutting a cash deal with the real owners. In<br>> most cases, all<br>> the squatter needs to cough up is only $10.00 to register<br>> a domain name.<br>> It's as cheap as $2.00 with other companies. These<br>> particular dunderhead(s)<br>> registered these names with the following internet domain<br>> registrar:<br>> <br>> DomainsByProxy. com<br>> 15111 N. Hayden Rd., Ste 160, PMB 353<br>> Scottsdale, Arizona 85260<br>> United States<br>> Phone:+1.4806242599<br>> <br>> Registration details:<br>> Admin Email:KALONZOFOUNDA TION.ORG@ domainsbyproxy. com<br>> Tech ID:GODA-116462376<br>> Tech Email:KALONZOFOUNDA TION.ORG@ domainsbyproxy. com<br>> Name Server:NS3.SECURESE RVER.NET<br>> Name Server:NS4.SECURESE RVER.NET<br>> Admin Email:ODM-KENYA. ORG@domainsbypro xy.com<br>> Tech ID:GODA-122841719<br>> Tech Name:Registration Private<br>> Tech Organization: Domains by Proxy, Inc.<br>>
DomainsByProxy. com<br>> 15111 N. Hayden Rd., Ste 160, PMB 353<br>> City:Scottsdale<br>> State/Province: Arizona<br>> Tech Postal Code:85260<br>> Country:US<br>> Phone:+1.4806242599<br>> FAX:+1.4806242599<br>> Email:ODM-KENYA. ORG@domainsbypro xy.com<br>> Name Server:PARK9. SECURESERVER. NET<br>> Name Server:PARK10. SECURESERVER. NET<br>> All the compainant needs to do is contact the company and<br>> file a complaint.<br>> The culprit will be smoked out and taken to court. The<br>> FBI has been on the<br>> trail of such obscure websites, some of which are used by<br>> terrorist<br>> organizations to convey coded messages. It will only be a<br>> matter of time<br>> before these ones are smoked out.<br>> <br>> The purpose of this infantile prank was of course meant<br>> to have the Kalonzo<br>> and Raila camps go after each other's throats. What's<br>> surprising is the<br>> shallow and very
un-sophisticated manner in which it was<br>> played. It would<br>> have been laughable had it not for the fact that many<br>> gullible Kenyans will<br>> be hoodwinked into believing that this was actually the<br>> work of one ODM camp<br>> against another. It would do us all good if the Standard<br>> corrects this<br>> flawed perception that they have created. I think the<br>> newspaper should have<br>> first done a thorough investigation before splashing such<br>> a misleading<br>> headline.<br>> Whatever the case, the pumbavus will never succeed, and<br>> the sooner they<br>> realize this the better. Fortunately, those who received<br>> the e-mails saw<br>> through the sick jokes and decided to ignore them.<br>> We hope other Kenyans will equally treat them with the<br>> contempt they<br>> deserve.<br>> <br>> Very Best regards<br>> <br>> J Sang.<br>> Washington DC<br>> ============ =<br>>
<br>> <br>> Kind Regards,<br>> <br>> On 2/22/07, Bill Kagai <billkagai@gmail.com> wrote:<br>> ><br>> > Hiya,<br>> ><br>> > I have received a fone call from an ODM supporter<br>> wishing to find out why<br>> > their website www.odm-kenya.org is pointing to a<br>> government website. This<br>> > poses a serious challenge to us in the 'internet<br>> business' with regard to<br>> > whether we have secure systems in place.<br>> ><br>> > However, upon digging a bit deeper, I have realised<br>> that possibly, this is<br>> > a simple blackmail prank since the WHOIS records have<br>> not been altered and<br>> > only the MX record has been changed to point the<br>> website to an innocent Govt<br>> > server. Tracert'ing the address also shows that it is<br>> the admin and<br>> > registrant of the website who have access to the odm<br>> website registry. I am<br>> >
sure many ODM supporters might be pointing a finger at<br>> Govt just because<br>> > someone managed to ping the communications website and<br>> put the server<br>> > address on the opposition website to create a furore<br>> and possibly make money<br>> > Pablo Escobar Way. [Plata o plomo] Spanish for [silver<br>> or lead] literally<br>> > meaning pay up the bribe or face assassination.<br>> ><br>> > How do we contain these Matheri's of the internet???.<br>> Seems the games have<br>> > just begun???<br>> ><br>> > --<br>> > --<br>> > With Kind Regards,<br>> > Bildad Kagai<br></billkagai@gmail.com></judyokite@gmail.com></blockquote><br><p>
<hr size=1>We won't tell. Get more on <a href="http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265
">shows you hate to love</a><br>(and love to hate): <a href="http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265
">Yahoo! TV's Guilty Pleasures list.</a>