<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
There was also a situation with .NAME in which they negotiated a
different Whois policy. I think it may have been upfront, as part of
the contract, but I seem to recall discussions about ICANN's
procedure for handling Whois conflicts with privacy law as part of
the overall discussion.<br>
<br>
(Background: .NAME, which focused on personal email addresses based
on last names, was based in the EU, and I believe in a Scandanavian
country, and they consulted with their data protection commissioner
from the start.)<br>
<br>
Best,<br>
Kathy<br>
<br>
<blockquote
cite="mid:41F6C547EA49EC46B4EE1EB2BC2F34183769D9ACE5@EXVPMBX100-1.exc.icann.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear
Peter and all,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Please
note that there is one occasion where the procedure for
handling WHOIS conflicts with privacy law has been applied
in practice, relating to .TEL, see <a
moz-do-not-send="true"
href="http://www.icann.org/en/announcements/announcement-2-19oct07.htm">http://www.icann.org/en/announcements/announcement-2-19oct07.htm</a>
(announcement of Telnic’s proposed change and opening of a
public comment period) and <a moz-do-not-send="true"
href="http://www.icann.org/en/minutes/minutes-18dec07.htm">http://www.icann.org/en/minutes/minutes-18dec07.htm</a>
(the Board minutes with the decision on the matter). <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In
this case, the procedure is invoked as a “draft Procedure”,
since the .TEL matter was addressed before the procedure was
formally in force , see </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a
moz-do-not-send="true"
href="http://www.icann.org/en/processes/icann-procedure-17jan08.htm">http://www.icann.org/en/processes/icann-procedure-17jan08.htm</a></span>.<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Denise
may have additional information to supply when the sun rises
in California– I just wanted to provide this piece well
before our call today.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Very
best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Olof<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a class="moz-txt-link-abbreviated" href="mailto:rt4-whois-bounces@icann.org">rt4-whois-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:rt4-whois-bounces@icann.org">mailto:rt4-whois-bounces@icann.org</a>] <b>On Behalf Of </b>Nettlefold,
Peter<br>
<b>Sent:</b> Wednesday, August 17, 2011 9:39 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><br>
<b>Cc:</b> Kathy Kleiman<br>
<b>Subject:</b> [Rt4-whois] FW: Applicable laws
[SEC=UNOFFICIAL]<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">Thanks to Lynn and Kathy for continuing our
discussions on these important issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">These were key issues I struggled with in
drafting the accessibility/privacy part of the gaps chapter,
which I circulated yesterday for comment.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">After reading the public submissions to our
discussion paper, it seems clear that some people are
worried about the privacy implications of WHOIS. It was
raised by many respondents to our paper, and acknowledged as
a valid concern by many others.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">However, I don’t see a compelling case for us
to catalogue all potential applicable privacy or data
protection laws as a way to take this forward. In practice,
I think this would be very difficult, and arguably of
limited use. Even if every GAC member provided details of
every potentially applicable law, this would not cover every
country, and would only cover contributing countries at a
set point in time. Further, what would we do with this data?
How would we reconcile the inevitable differences?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">Arguably, any conflict with national law
(whether it relates to ‘sensitive’ information, or other
personal information) is intended to be addressed by ICANN’s
consensus procedure. The consensus procedure was developed
by the ICANN community to deal with specific conflicts with
national law. Whether and how it has been used may therefore
provide us some guidance about any actual conflicts and how
they’ve been handled. I see that Denise has undertaken to
get back to us shortly with an answer to this - thanks
Denise! The answer to this may provide useful insights into
whether that particular procedure is effective or needs
modification to deal with specific legal situations, and it
could also clarify the potential extent of existing legal
conflicts. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">For the procedure to be effective, there is no
need to catalogue applicable laws in advance. Personally, I
can’t see any way to replace this (or a similar)
case-by-case procedure with a more prescriptive universal
mechanism based on a survey of applicable laws, nor any way
to anticipate all potential legal conflicts in advance. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">There is then the additional question of
whether we’re only interested in situations where there is a
conflict with a national law?</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
If so, then </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">we need to consider whether there needs to be
any additional protections beyond the existing procedure. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">On balance, my position is that we should
consider some way to acknowledge the privacy concerns of
individuals, including those that may not be addressed by
ICANN’s existing consensus procedures and policies. The
problem is how to do this without facilitating the
unregulated and widely abused privacy/proxy situation that
we now have. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">This is what I tried to address in the draft
gaps chapter. The proposed recommendations at the end of
that chapter are intended to provide a framework for a
balanced, open and accountable privacy regime, while
acknowledging that much of the detail (such as what data
could be ‘protected’ or ‘limited’, and standardised
processes for release of that data when needed) would
rightly be developed through existing ICANN community (and
cross community) processes.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">I look forward to further discussion on this as
we move forward.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-AU"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a moz-do-not-send="true"
href="mailto:rt4-whois-bounces@icann.org">rt4-whois-bounces@icann.org</a>
<a moz-do-not-send="true"
href="mailto:[mailto:rt4-whois-bounces@icann.org]">[mailto:rt4-whois-bounces@icann.org]</a>
<b>On Behalf Of </b>Kathy Kleiman<br>
<b>Sent:</b> Wednesday, 17 August 2011 2:30 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:lynn@goodsecurityconsulting.com">lynn@goodsecurityconsulting.com</a><br>
<b>Subject:</b> Re: [Rt4-whois] Applicable laws<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU">Dear Lynn and All,<br>
I wanted to say how much I appreciate Lynn posting the key
regional data protection frameworks to the group. I think
they are very important, and she and I have discussed the
need for us to look at them more closely in relation to the
Whois data. I hope we can do this soon! <br>
<br>
Regarding sensitive vs private data, I wanted to add my
views as an attorney who specializes in the area of data
protection and privacy since starting my telecommunications
practice in 1993. While sensitive data may focus on the
areas of financial, birth, religion, health, and let's add
political affiliation and sexual orientation, that's not
where the story ends.<br>
<br>
Data protection and privacy laws certainly consider home
address, home phone number, and now cell phone data as
"private" or "personal data." Certainly telecommunications
laws in the US, as one example, regularly protect the right
of a person to "opt-out" of sharing their home address or
home phone number in a public directory as a matter of
personal privacy. In fact, opt-out in directories was
chosen by a majority of Californians when last I researched
it (and the state protects privacy as part of its state
constitution) because home addresses and home phone numbers
are considered very personal information, and worthy of
protection. <br>
<br>
These are the very elements that have been such an issue of
controversy within the ICANN arena. Over the last decade, as
part of the history of Whois within ICANN, at least four
Data Protection Commissioners and their senior staffs have
warned ICANN about the problems of this data, and its data
protection implications. They are very concerned with the
elements now collected and published in the Whois. I will
gather their letters to ICANN and share them, as well as
notes of the speeches they have given. I would like to
request that we ask ICANN Staff to work with us on this
important matter as well. <br>
<br>
Ultimately, I do not think this is a matter for us to decide
on (which may relieve everyone greatly). As many of you
know, I have been thinking about this issue a great deal. I
will be submitting a recommendation to our Team asking that
GAC provide ICANN with clear information about relevant
applicable laws, including data protection laws, and their
guidance, based on these laws, as to the elements of the
Whois now published. I'll distribute this before our meeting
tomorrow.<br>
<br>
All the best,<br>
Kathy<br>
<br>
Since data privacy is an area of specialization for me, I
would like to offer a couple of <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">comments on the dialogue about privacy laws.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">Although WHOIS data contains personal data,
it does not have any data elements that are<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">considered to be "sensitive" in nature. The
focus and priority of data protection authorities
throughout the world is on protection of sensitive data
such as financial account details, date of birth,
religious affiliations, medical conditions, etc.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">For global, multi-national organizations who
need to develop and maintain policies regarding the
collection and use of personal data, there are
multi-lateral privacy frameworks and principles that have
been accepted and are well established including:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">1) OECD Guidelines on the Protection of
Privacy and Transborder Flows<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">2) UN Guidelines Concerning Computerized
Personal Data Files<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">3) EU Directive 95/46/EC on the Protection of
Individuals with Regard to the Processing of Personsal
Data and on the Free Movement of Such Data<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">4) APEC Privacy Framework<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">Since ICANN is headquartered in the State of
California and the United States, I would note that
California has an Office of Privacy Protection. At the
national level, the U.S. Federal Trade Commission has been
accepted as the equivalent of a Data Protection Authority.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">Hope these brief comments are helpful.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU">Lynn<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""
lang="EN-AU"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
lang="EN-AU"><o:p> </o:p></span></p>
<pre><span lang="EN-AU">_______________________________________________<o:p></o:p></span></pre>
<pre><span lang="EN-AU">Rt4-whois mailing list<o:p></o:p></span></pre>
<pre><span lang="EN-AU"><a moz-do-not-send="true" href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><o:p></o:p></span></pre>
<pre><span lang="EN-AU"><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a><o:p></o:p></span></pre>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
lang="EN-AU"><o:p> </o:p></span></p>
<pre><span lang="EN-AU">-- <o:p></o:p></span></pre>
<pre><span lang="EN-AU"><o:p> </o:p></span></pre>
<pre><span lang="EN-AU"><o:p> </o:p></span></pre>
<p><span lang="EN-AU"><br>
<b>-------------------------------------------------------------------------------</b><o:p></o:p></span></p>
<p><span lang="EN-AU">The information transmitted is for the use
of the intended recipient only and may contain confidential
and/or legally privileged material. Any review,
re-transmission, disclosure, dissemination or other use of,
or taking of any action in reliance upon, this information
by persons or entities other than the intended recipient is
prohibited and may result in severe penalties.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext" lang="EN-AU"><o:p> </o:p></span></p>
<p><span lang="EN-AU">If you have received this e-mail in error
please notify the Security Advisor of the Department of
Broadband, Communications and the Digital Economy, 38 Sydney
Ave, Forrest ACT 2603, telephone (02) 6271-1376 and delete
all copies of this transmission together with any
attachments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext" lang="EN-AU"><o:p> </o:p></span></p>
<p><span lang="EN-AU">Please consider the environment before
printing this email.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext" lang="EN-AU"><br>
<b>-------------------------------------------------------------------------------</b><o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Rt4-whois mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
</pre>
</body>
</html>