<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>that is my understanding too - we are not suggesting that ICANN take on a centralized database.</div>
<div>I like your descripton as "smart web portal"</div>
<div>Lynn </div>
<div> </div>
<BLOCKQUOTE style="BORDER-LEFT: blue 2px solid; PADDING-LEFT: 8px; FONT-FAMILY: verdana; COLOR: black; MARGIN-LEFT: 8px; FONT-SIZE: 10pt" id=replyBlockquote webmail="1">
<DIV id=wmQuoteWrapper>-------- Original Message --------<BR>Subject: Re: [Rt4-whois] Centralized Whois Query system run by ICANN -<BR>Scope and concerns [SEC=UNCLASSIFIED]<BR>From: "Nettlefold, Peter" <<a href="http://Peter.Nettlefold@dbcde.gov.au">Peter.Nettlefold@dbcde.gov.au</a>><BR>Date: Wed, November 30, 2011 4:11 pm<BR>To: "'<a href="mailto:susank@fb.com">susank@fb.com</a>'" <<a href="mailto:susank@fb.com">susank@fb.com</a>>, "'<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>'"<BR><<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, "'<a href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>'"<BR><<a href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>><BR>Cc: "'<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>'" <<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>><BR><BR>
<STYLE>
#wmQuoteWrapper v\:* {behavior:url(#default#VML);}
#wmQuoteWrapper o\:* {behavior:url(#default#VML);}
#wmQuoteWrapper w\:* {behavior:url(#default#VML);}
#wmQuoteWrapper .shape {behavior:url(#default#VML);}
</STYLE>
<STYLE>
#wmQuoteWrapper /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}
#wmQuoteWrapper @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}
#wmQuoteWrapper @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;}
#wmQuoteWrapper @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4;}
#wmQuoteWrapper /* Style Definitions */ p.MsoNormal, #wmQuoteWrapper li.MsoNormal, #wmQuoteWrapper div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";}
#wmQuoteWrapper a:link, #wmQuoteWrapper span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}
#wmQuoteWrapper a:visited, #wmQuoteWrapper span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;}
#wmQuoteWrapper span.EmailStyle17 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;}
#wmQuoteWrapper .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;}
#wmQuoteWrapper @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;}
#wmQuoteWrapper div.WordSection1 {page:WordSection1;}
</STYLE>
<FONT style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Classification: UNCLASSIFIED<BR><BR>Hello all,<BR><BR>I've missed a lot of discussion on this overnight my time, so I apologise if I've missed something that answers my question.<BR><BR>The references to an ICANN database are confusing to me, and may be part of the contention here.<BR><BR>I had understood that we would recommend that ICANN create a smart web portal for consumers that would effectively do a WHOIS search for them. As I understood it, ICANN would not need to make its own database, thereby avoiding some of the data protection issues, and instead purely focus on the user experience.<BR><BR>Is this what others had understood?<BR><BR>If so, does this address the concerns about scope - ie why wouldn't ICANN provide a comprehensive search tool for all gTLDs?<BR><BR>Please let me know if I've got this wrong.<BR><BR>Cheers<BR><BR>Peter<BR></FONT><BR> <BR>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><FONT style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"><B>From</B>: Susan Kawaguchi [<a href="mailto:susank@fb.com">mailto:susank@fb.com</a>] <BR><B>Sent</B>: Thursday, December 01, 2011 03:27 AM<BR><B>To</B>: James M. Bladel <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>; Emily Taylor <<a href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>> <BR><B>Cc</B>: <a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a> <<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>> <BR><B>Subject</B>: Re: [Rt4-whois] Centralized Whois Query system run by ICANN - Scope and concerns <BR></FONT> <BR></DIV>
<DIV class=WordSection1>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I agree that we should not try and answer all the questions but I was under the impression that the centralized WHOIS was only targeting .com and .net to solve the problem of having to search for the correct registrar out of the almost 1000 possible. <o:p></o:p></SPAN></div>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></div>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I do not agree to include all gtlds. <o:p></o:p></SPAN></div>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></div>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<div class=MsoNormal style="font-size:12pt;"><B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> <a href="mailto:rt4-whois-bounces@icann.org">rt4-whois-bounces@icann.org</a> [<a href="mailto:rt4-whois-bounces@icann.org">mailto:rt4-whois-bounces@icann.org</a>] <B>On Behalf Of </B>James M. Bladel<BR><B>Sent:</B> Wednesday, November 30, 2011 8:21 AM<BR><B>To:</B> Emily Taylor<BR><B>Cc:</B> <a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><BR><B>Subject:</B> Re: [Rt4-whois] Centralized Whois Query system run by ICANN - Scope and concerns<o:p></o:p></SPAN></div></DIV></DIV>
<div class=MsoNormal style="font-size:12pt;"><o:p> </o:p></div>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">No, I don't think we should attempt to answer these questions in RT4, nor presume that we have even identified all of the dependent questions.<o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">I believe our recommendation should task the Board, within a reasonable timeframe (90 days?), to request an issues report on a Centralized WHOIS system for all gTLDs, including how it should be operated and what measures would be adopted to protect against abuse / privacy violations / data harvesting. <o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">(This will initiate a PDP which, while slower, will be a more comprehensive approach)<o:p></o:p></SPAN></div></DIV>
<BLOCKQUOTE style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; PADDING-BOTTOM: 0in; MARGIN-TOP: 5pt; PADDING-LEFT: 6pt; PADDING-RIGHT: 0in; MARGIN-BOTTOM: 5pt; MARGIN-LEFT: 6pt; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0in" id=replyBlockquote>
<DIV id=wmQuoteWrapper>
<div style="font-size:12pt;MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt">-------- Original Message --------<BR>Subject: Re: [Rt4-whois] Centralized Whois Query system run by ICANN -<BR>Scope and concerns<BR>From: Emily Taylor <<A href="mailto:emily@emilytaylor.eu" target=_blank>emily@emilytaylor.eu</A>><BR>Date: Wed, November 30, 2011 10:15 am<BR>To: "James M. Bladel" <<A href="mailto:jbladel@godaddy.com" target=_blank>jbladel@godaddy.com</A>><BR>Cc: Kathy Kleiman <<A href="mailto:kathy@kathykleiman.com" target=_blank>kathy@kathykleiman.com</A>>, <A href="mailto:rt4-whois@icann.org" target=_blank>rt4-whois@icann.org</A><BR><BR>Hi James<BR><BR>Thanks for raising these points. Can you suggest some language which you think would work? Also, Kathy raised a good point about whether this is limited to thin registries (.com, .net) or all? I don't think we've ever discussed this. <BR><BR>Kind regards<BR><BR>Emily<o:p></o:p></SPAN></div>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt">On 30 November 2011 16:06, James M. Bladel <<A href="mailto:jbladel@godaddy.com" target=_blank>jbladel@godaddy.com</A>> wrote:<o:p></o:p></SPAN></div>
<DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">I don't oppose this recommendation, but my issue with this is that we are once again being too vague in what we're asking.<o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">ICANN: Who? Staff? The Board? The GNSO? Contracted 3rd party?<o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">Set up: How? By launching a PDP? Sending out an RFP?<o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">Deadline? <o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">Are we confident that this group has considered all of the consequences to privacy, security, access, SLAs, etc.? (Reasons why a PDP can be more helpful for things like this...)<o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">Thanks--<o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR>J.<o:p></o:p></SPAN></div></DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV>
<BLOCKQUOTE style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; PADDING-BOTTOM: 0in; MARGIN-TOP: 5pt; PADDING-LEFT: 6pt; PADDING-RIGHT: 0in; MARGIN-BOTTOM: 5pt; MARGIN-LEFT: 6pt; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt">-------- Original Message --------<BR>Subject: Re: [Rt4-whois] Centralized Whois Query system run by ICANN -<BR>Scope and concerns<BR>From: Kathy Kleiman <<A href="mailto:kathy@kathykleiman.com" target=_blank>kathy@kathykleiman.com</A>><BR>Date: Wed, November 30, 2011 9:56 am<BR>To: <A href="mailto:rt4-whois@icann.org" target=_blank>rt4-whois@icann.org</A><o:p></o:p></SPAN></div>
<DIV>
<DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR><BR>All,<BR>Is this the current version of the Lutz proposal now in circulation? I <BR>thought it applied only to a centralized database of the current "thin <BR>registries," namely .COM and .NET. If so, I can see the advantages and <BR>support sending it out as a recommendation in the draft report.<BR><BR>But if this is a single database of all registries, thick and thin, now <BR>and in the future, I think we creating a database problem. It's an <BR>enormous amount of data and creates a focal point for abuse, for <BR>warehousing, etc. It's the type of policing job that ICANN has never had <BR>to do, and is not operationally set up to do.<BR><BR>So thought summary: If ICANN is helping remedy a bad situation by <BR>operating a single registry for .COM and .NET to fix a historical <BR>problem, I think I am OK for now (pending review of the draft with <BR>registries -- after publication is fine). One database of all Whois <BR>information to Rule the World, not so good.<BR><BR>RECOMMENDATION EDIT:<BR><BR>Detailed recommendation:<BR>ICANN should set up a dedicated, multilingual website to allow<BR>"unrestricted and public access to accurate and complete WHOIS<BR>information" **FOR .COM AND .NET, THE EXISTING "THIN REGISTRIES"** even for those people which have problems with the plain<BR>WHOIS protocol.<BR><BR>The WHOIS information should be collected by following the thin WHOIS<BR>approach starting at <A href="http://whois.iana.org/" target=_blank>whois.iana.org</A>. The service should display the<BR>contractural relationships which are revealed by the WHOIS referals in<BR>a clear and understandable way. The results should be mark clearly the<BR>relevant information "including registrant, technical, ** DELETE BILLING** billing, and<BR>administrative contact" data.<BR><BR>** NOTE: Billing data, which includes credit cards Folks, is simply not <BR>displayed in any other Whois search results. It is only registrant, <BR>technical, and admin contact.**<BR><BR>Best,<BR>Kathy<BR><BR><BR>> Proposal:<BR>><BR>> Summary:<BR>> ICANN should set up and maintain a web interface to access<BR>> all the WHOIS services in order to ease access to the WHOIS data.<BR>><BR>> Presumption:<BR>> The AoC requires that "ICANN implement measures to maintain timely,<BR>> unrestricted and public access to accurate and complete WHOIS information,<BR>> including registrant, technical, billing, and administrative contact<BR>> information."<BR>><BR>> Observation:<BR>> An User Insight Report came up with the following results:<BR>> + Almost nobody is aware of whois<BR>> + Almost nobody is able to query a whois server correctly<BR>> + Whois queries were done on websites which occur first in the search<BR>> engine results. Usually those pages are overloaded with advertisments.<BR>><BR>> Detailed recommendation:<BR>> ICANN should set up a dedicated, multilingual website to allow<BR>> "unrestricted and public access to accurate and complete WHOIS<BR>> information" even for those people which have problems with the plain<BR>> WHOIS protocol.<BR>><BR>> The WHOIS information should be collected by following the thin WHOIS<BR>> approach starting at <A href="http://whois.iana.org/" target=_blank>whois.iana.org</A>. The service should display the<BR>> contractural relationships which are revealed by the WHOIS referals in<BR>> a clear and understandable way. The results should be mark clearly the<BR>> relevant information "including registrant, technical, billing, and<BR>> administrative contact" data.<BR>><BR>> The server needs to be run by ICANN itself, because the "timely,<BR>> unrestricted and public access" is usually rate limited, stripped or even<BR>> blocked by the various WHOIS server administrators for uncontractual<BR>> third party access. ICANN itself is the only party having the power to<BR>> overcome those limits using its contratual compliance.<BR>> _______________________________________________<BR>> Rt4-whois mailing list<BR>> <A href="mailto:Rt4-whois@icann.org" target=_blank>Rt4-whois@icann.org</A><BR>> <A href="https://mm.icann.org/mailman/listinfo/rt4-whois" target=_blank>https://mm.icann.org/mailman/listinfo/rt4-whois</A><BR><BR><BR>-- <BR><BR><BR><BR>_______________________________________________<BR>Rt4-whois mailing list<BR><A href="mailto:Rt4-whois@icann.org" target=_blank>Rt4-whois@icann.org</A><BR><A href="https://mm.icann.org/mailman/listinfo/rt4-whois" target=_blank>https://mm.icann.org/mailman/listinfo/rt4-whois</A><o:p></o:p></SPAN></div></DIV></DIV></DIV></BLOCKQUOTE></DIV>
<div style="font-size:12pt;MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR>_______________________________________________<BR>Rt4-whois mailing list<BR><A href="mailto:Rt4-whois@icann.org" target=_blank>Rt4-whois@icann.org</A><BR><A href="https://mm.icann.org/mailman/listinfo/rt4-whois" target=_blank>https://mm.icann.org/mailman/listinfo/rt4-whois</A><o:p></o:p></SPAN></div></DIV>
<div style="font-size:12pt;MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR><BR clear=all><BR>-- <BR><BR><BR> <img id=_x0000_i1025 border=0 src="http://www.etlaw.co.uk/images/stories/etlaw/etclogo250x60.gif" ><o:p></o:p></SPAN></div>
<DIV style="MARGIN-LEFT: 60pt">
<div class=MsoNormal style="font-size:12pt;"><U><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: #cc33cc; FONT-SIZE: 10pt"> </SPAN></U><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: #993399; FONT-SIZE: 10pt"><BR></SPAN><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR></SPAN><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: #999999; FONT-SIZE: 10pt">76 Temple Road, Oxford OX4 2EZ UK<BR>t: +44 (0)1865 582 811 • m: +44 (0)7540 049 322<BR><A href="mailto:emily@emilytaylor.eu" target=_blank>emily@emilytaylor.eu</A> <BR><BR><B><A href="http://www.etlaw.co.uk/" target=_blank>www.etlaw.co.uk</A></B><BR><BR>Emily Taylor Consultancy Limited is a company registered in England and Wales No. 730471. VAT No. 114487713.</SPAN><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p></o:p></SPAN></div></DIV>
<div class=MsoNormal style="font-size:12pt;"><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></div></DIV></BLOCKQUOTE></DIV>
<div><BR><B>-------------------------------------------------------------------------------</B><BR>NOTICE: This email message is for the sole use of the intended recipient(s) <BR>and may contain confidential and privileged information. Any unauthorized <BR>review, use, disclosure or distribution is prohibited. If you are not the <BR>intended recipient, please contact the sender by reply email and destroy all <BR>copies of the original message. <BR><BR>This message has been content scanned by the Axway MailGate. <BR>MailGate uses policy enforcement to scan for known viruses, spam, undesirable content and malicious code. For more information on Axway products please visit <a href="http://www.axway.com">www.axway.com</a>.<BR><BR><B>-------------------------------------------------------------------------------</B><BR></div>
<HR>
_______________________________________________<BR>Rt4-whois mailing list<BR><a href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><BR><a href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a><BR></DIV></BLOCKQUOTE></span></body></html>