<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
This is great, we are getting a great team! Please keep the
volunteers coming for this, we need lots!!<br>
SP<br>
<br>
<div class="moz-cite-prefix">On 2016-01-10 9:55, Zalnieriute, Monika
wrote:<br>
</div>
<blockquote
cite="mid:DB3PR05MB556C510C3C07F15D93FDB79F6C80@DB3PR05MB556.eurprd05.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:10pt;color:#000000;background-color:#FFFFFF;font-family:Helvetica,
Sans-Serif;">
<p><br>
</p>
<p>I am also on!</p>
<p><br>
</p>
<p>Monika</p>
<div id="Signature">
<div id="divtagdefaultwrapper" style="font-size:10pt;
color:#000000; background-color:#FFFFFF;
font-family:Helvetica,Sans-Serif">
<div name="divtagdefaultwrapper"
style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:; margin:0">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div
style="font-family:Calibri,Arial,Helvetica,sans-serif"><span
style="background-color:rgb(255,255,255)"><font face="Helvetica,
sans-serif" color="#808080" size="2">----</font></span></div>
<div
style="font-family:Calibri,Arial,Helvetica,sans-serif"><span
style="background-color:rgb(255,255,255)"><font face="Helvetica,
sans-serif" color="#808080" size="2"><br>
</font></span></div>
<div><span
style="background-color:rgb(255,255,255)"><font
face="Helvetica, sans-serif"
color="#808080" size="2">Dr. Monika
Zalnieriute</font></span></div>
<div><br>
</div>
<div>
<div
style="background-color:rgb(255,255,255)"><font
face="Helvetica, sans-serif"
color="#808080" size="2">C I H R
: Centre for Internet & Human
Rights I</font></div>
<div
style="background-color:rgb(255,255,255)"><font
face="Helvetica, sans-serif"
color="#808080" size="2">a: Mittelweg
50, 12053 Berlin, Germany I </font></div>
<div
style="background-color:rgb(255,255,255)"><font
face="Helvetica, sans-serif"
color="#808080" size="2">e:
<a class="moz-txt-link-abbreviated" href="mailto:monika.zalnieriute@eui.eu">monika.zalnieriute@eui.eu</a> I</font></div>
<div
style="background-color:rgb(255,255,255)"><font
face="Helvetica, sans-serif"
color="#808080" size="2"><span
style="color:rgb(117,123,128);
font-family:Helvetica,sans-serif;
font-size:13px;
background-color:rgb(255,255,255)">p:
+37062852809 |</span><br>
</font></div>
</div>
<div style="font-family:Tahoma;
font-size:13px"><span
style="color:rgb(117,123,128)"><span
style="font-family:Helvetica,sans-serif">w:
cihr.eu</span>
<span style="color:rgb(128,128,128);
font-family:Helvetica,sans-serif;
font-size:small;
background-color:rgb(255,255,255)">
I</span></span><br>
</div>
<div style="font-family:Tahoma;
font-size:13px"><br>
</div>
<div style="font-family:Tahoma;
font-size:13px">
<p style="margin-top:0px;
margin-bottom:0px"><span
style="color:rgb(117,123,128);
font-family:Helvetica,sans-serif"><span
style="font-family:Helvetica,sans-serif">Z E P H I R O : Progressive
Platform for Human Rights I</span></span><br
style="color:rgb(117,123,128);
font-family:Helvetica,sans-serif">
</p>
<div><span
style="font-family:Helvetica,sans-serif;
color:rgb(117,123,128)"><span
style="color:rgb(117,123,128)">a:
Vilnius Str. 14 - 7, LT – 01402,
Vilnius, Lithuania |</span></span></div>
<div><span
style="font-family:Helvetica,sans-serif;
color:rgb(117,123,128)"><span
style="color:rgb(117,123,128)">f:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/zephiroplatform">www.facebook.com/zephiroplatform</a> | </span></span></div>
<div><span
style="font-family:Helvetica,sans-serif;
color:rgb(117,123,128)"><span
style="color:rgb(117,123,128)">w:
zephiroplatform.wix.com/main | </span></span></div>
<div><span
style="font-family:Helvetica,sans-serif;
color:rgb(117,123,128)"><span
style="color:rgb(117,123,128)">e:
<a class="moz-txt-link-abbreviated" href="mailto:zephirplatform@gmail.com">zephirplatform@gmail.com</a> | </span></span></div>
<div><span
style="font-family:Helvetica,sans-serif;
color:rgb(117,123,128)"><span
style="color:rgb(117,123,128)">p:
+37062852809 |</span></span><br>
</div>
<p style="margin-top:0px;
margin-bottom:0px"><span
style="color:rgb(117,123,128)"><br>
</span></p>
<p style="margin-top:0px;
margin-bottom:0px"><br>
</p>
<br>
</div>
<div style="font-family:Tahoma;
font-size:13px"><br>
</div>
<div style="font-family:Tahoma;
font-size:13px"><font face="Helvetica"
size="2"><br>
</font></div>
<div style="font-family:Tahoma;
font-size:13px"><font face="Helvetica"
size="2"><br>
</font></div>
<div style="font-family:Tahoma;
font-size:13.63636302947998px"><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
NCSG-Discuss <a class="moz-txt-link-rfc2396E" href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU"><NCSG-DISCUSS@LISTSERV.SYR.EDU></a> on
behalf of Stephanie Perrin
<a class="moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@MAIL.UTORONTO.CA"><stephanie.perrin@MAIL.UTORONTO.CA></a><br>
<b>Sent:</b> Saturday, January 9, 2016 9:37 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b>Subject:</b> Privacy and WHOIS update</font>
<div> </div>
</div>
<div>This is just a quick note to update list members on what
is going on at ICANN related to privacy and protection of
registration data. The most important development which I
need to bring to your attention is the call for volunteers
for the new pdp to develop a replacement for the WHOIS
directory. I have copied the call at the bottom of this
email. Please consider joining, either as an observer or
full participant. If you have questions, please do not
hesitate to contact me, Tapani Tarvainen, or Kathy Kleiman
(in cc). We really need a great many people to volunteer
for this work, as it is extremely important, and there are
many commercial participants already signed up. It is
important to have balanced representation of interests on
these working groups.<br>
<br>
Registrars and technical experts have expressed concern,
notably at the GNSO level, about the RDAP (registration data
access protocol) work that is proceeding even though the
work of the PDP on WHOIS replacement may make this work
irrelevant. It is likely a call to put the brakes on that
work may develop. For more information on the RDAP
implementation, look here:<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://www.icann.org/public-comments/rdap-profile-2015-12-03-en"
id="LPlnk663046">https://www.icann.org/public-comments/rdap-profile-2015-12-03-en</a>.
We will be putting in comments, due in 22 days.
<div id="LPBorder_GT_14524378053850.4889487395994365"
style="margin-bottom: 20px; overflow: auto; width: 100%;">
<table id="LPContainer_14524378053730.8676186006050557"
style="width: 90%; position: relative; overflow: auto;
padding-top: 20px; padding-bottom: 20px; margin-top:
20px; border-top-width: 1px; border-top-style: dotted;
border-top-color: rgb(200, 200, 200);
border-bottom-width: 1px; border-bottom-style: dotted;
border-bottom-color: rgb(200, 200, 200);
background-color: rgb(255, 255, 255);" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td id="TextCell_14524378053770.27629005652852356"
colspan="2" style="vertical-align: top; position:
relative; padding: 0px; display: table-cell;">
<div id="LPTitle_14524378053770.7127680061385036"
style="top: 0px; color: rgb(95, 188, 162);
font-weight: normal; font-size: 21px;
font-family: wf_segoe-ui_light, 'Segoe UI
Light', 'Segoe WP Light', 'Segoe UI', 'Segoe
WP', Tahoma, Arial, sans-serif; line-height:
21px;">
<a moz-do-not-send="true"
id="LPUrlAnchor_14524378053810.07627998921088874"
href="https://www.icann.org/public-comments/rdap-profile-2015-12-03-en"
target="_blank" style="text-decoration: none;">Registration
Data Access Protocol (RDAP) Operational ...</a></div>
<div
id="LPMetadata_14524378053810.5008193280082196"
style="margin: 10px 0px 16px; color: rgb(102,
102, 102); font-weight: normal; font-family:
wf_segoe-ui_normal, 'Segoe UI', 'Segoe WP',
Tahoma, Arial, sans-serif; font-size: 14px;
line-height: 14px;">
<a class="moz-txt-link-abbreviated" href="http://www.icann.org">www.icann.org</a></div>
<div
id="LPDescription_14524378053810.6021310591604561"
style="display: block; color: rgb(102, 102,
102); font-weight: normal; font-family:
wf_segoe-ui_normal, 'Segoe UI', 'Segoe WP',
Tahoma, Arial, sans-serif; font-size: 14px;
line-height: 20px; max-height: 100px; overflow:
hidden;">
Purpose: This public comment proceeding is being
opened to obtain community input on the
Registration Data Access Protocol (RDAP)
Operational Profile for gTLD ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
<br>
The call for volunteers for the Competition and Consumer
Trust Review Team has resulted in the selection of the team,
listed here:
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://www.icann.org/news/announcement-2-2015-12-23-en">
https://www.icann.org/news/announcement-2-2015-12-23-en</a>.
This is a very important review, and members may be
interested in following the work of this team. Further
information is available here
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://newgtlds.icann.org/en/reviews/cct">
http://newgtlds.icann.org/en/reviews/cct</a> and members
may be interested in looking at the public opinion survey
done by Nielsen in 2015, as it will no doubt be important
for the work of the committee, and be considered in the
context of the the two studies of DNS abuse for which ICANN
is currently tendering.<br>
<br>
The Final report and recommendations of the Privacy Proxy
Working Group has been sent to the GNSO for its endorsement,
and will be discussed at the Marrakech meeting in March. We
expect to see a call for volunteers for the implementation
working group shortly.
<br>
<br>
Finally, we are proposing to have a privacy meeting in
Marrakech, although we have yet to hear whether this
proposal has been approved. Stay tuned, and please join us
for the next monthly discussion on January 19th.<br>
<br>
Stephanie Perrin<br>
<dl>
<dd> </dd>
<dd><a moz-do-not-send="true"
href="https://www.icann.org/news/announcements">https://www.icann.org/news/announcements</a><br>
</dd>
<dd>
<h1><b>Call for Volunteers: New GNSO Policy Development
Process (PDP) Working Group to Establish a Policy
Framework for a Next-Generation gTLD Registration
Directory Service to Replace WHOIS (Next-Gen RDS)</b></h1>
</dd>
<dd>
<h3><b>How to Join</b></h3>
</dd>
<dd>If you are interested in joining the WG as an
individual participant or mailing list observer, please
fill in the
<a moz-do-not-send="true"
href="http://goo.gl/forms/bb65iIznLv">sign up form</a>
or send the <a moz-do-not-send="true"
href="http://gnso.icann.org/en/issues/gnso-pdp-next-gen-rds-wg-sign-up-04jan16-en.docx">Word
document</a> [DOCX, 72 KB] filled in to the <a
moz-do-not-send="true"
href="mailto:gnso-secs@icann.org">
GNSO Secretariat</a><br>
</dd>
<dd>All members and observers will be listed on the PDP
WG's wiki page. <br>
</dd>
<dd>
<h3><b>In Brief</b></h3>
The Generic Names Supporting Organization (GNSO) Council
seeks volunteers to serve on a PDP Working Group to
establish a policy framework for a next-generation gTLD
Registration Directory Service (RDS) to replace WHOIS
(Next-Gen RDS). The GNSO Council
<a moz-do-not-send="true"
href="http://gnso.icann.org/en/council/resolutions#201511">approved
the WG's charter</a> on 19 November 2015, tasking this
PDP to address concerns with WHOIS by creating a new
policy framework capable of balancing diverse interests
to meet today's needs for gTLD registration data.<br>
</dd>
<dd><br>
</dd>
<dd><b>What This Team Will Do</b> </dd>
<dd><br>
The PDP WG will use a 3-phase process defined in the <a
moz-do-not-send="true"
href="http://gnso.icann.org/en/drafts/whois-ng-gtld-rds-charter-07oct15-en.pdf">approved
charter</a>to (1) establish gTLD registration data
requirements to determine if and why a next-generation
RDS is needed, (2) design policies that detail functions
that must be provided by a next-generation RDS to
support those requirements, and (3) provide guidance for
how a next-generation RDS should implement those
policies, coexisting with and eventually replacing
WHOIS.
<br>
</dd>
<dd>This PDP WG will provide the GNSO Council with policy
recommendations regarding the issues identified in the
<a moz-do-not-send="true"
href="https://whois.icann.org/sites/default/files/files/final-issue-report-next-generation-rds-07oct15-en.pdf">Final
Issue Report</a> [PDF, 1.4 MB] and as defined in the <a
moz-do-not-send="true"
href="http://gnso.icann.org/en/drafts/whois-ng-gtld-rds-charter-07oct15-en.pdf">charter
approved by the GNSO Council</a> [PDF, 628 KB].
Specifically, this PDP WG is tasked with analyzing the
purpose of collecting, maintaining and providing access
to gTLD registration data and considering safeguards for
protecting that data, determining if and why a
next-generation RDS is needed to replace WHOIS, and
creating policies and coexistence and implementation
guidance to meet those needs.<br>
</dd>
<dd>During the first phase of this PDP, the PDP WG will,
at a minimum, attempt to reach consensus recommendations
regarding the questions detailed in the PDP WG’s
charter. The PDP WG’s output will then be submitted to
the GNSO Council for approval of its recommendations
regarding IF and WHY a next-generation RDS is needed to
replace WHOIS before moving to the next phase. If the WG
concludes a new policy framework is needed, this output
should include requirements to be addressed by that new
framework and any next-generation RDS. However, if the
WG concludes the existing WHOIS system can adequately
address requirements, the WG’s output should confirm
this and identify any necessary changes to the WHOIS
policy framework.<br>
<br>
</dd>
<dd>After Phase 1, if the GNSO Council confirms that a new
policy framework and next-generation RDS are required,
the PDP WG will then proceed to Phases 2 and 3,
recommending a new consensus policy framework to satisfy
requirements for a next-generation RDS established in
Phase 1, along with any necessary coexistence and
implementation guidance. Further detail regarding this
3-phase process and questions to be considered can be
found in the PDP WG’s charter.<br>
<br>
<b>How This Team Will Work</b> </dd>
<dd><br>
ICANN WGs use transparent, open processes. The meetings
of this PDP WG will be recorded, and the recordings will
be available to the public. The mailing list for the PDP
WG will be archived publicly. The group will collaborate
using a public workspace for draft materials and all
final work products and milestones will be documented on
the <a moz-do-not-send="true"
href="https://community.icann.org/display/gTLDRDS/Next-Generation+gTLD+Registration+Directory+Services+to+Replace+Whois">WG's
wiki</a>. The PDP WG is expected to follow the <a
moz-do-not-send="true"
href="http://gnso.icann.org/en/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf">GNSO
Working Group Guidelines</a> [PDF, 350 KB] as well as
the GNSO PDP Manual.<br>
<br>
<b>How to participate </b></dd>
<dd><br>
There are two ways to volunteer: </dd>
<dd>Individual Members – anyone interested cann volunteer
to join the PDP WG as a WG member, regardless of whether
they are members of the ICANN community. Members are
expected to actively contribute to mailing list
conversations as well as meetings – it is anticipated
tthat the PDP WG will at a minimum meet on a weekly
basis via teleconference. Members are expected to
provide essential input to the process. Members will be
required to provide a Statement of Interest (<a
moz-do-not-send="true"
href="https://community.icann.org/display/gnsosoi/New+SOIs">SOI</a>).
</dd>
<dd>Mailing list observers – for those who are merely
interested in monitoring thhe WG’s conversations,
there is the possibility to sign up as a mailing list
"observer" which offers read-only access to the mailing
list. Mailing list observers will not be permitted to
post, will not receive invitations to the various
meetings or calls of the WG and will not have to
complete a Statement of Interest. At any point in time,
a mailing list observer can join the WG as a member
simply by informing the GNSO Secretariat.
</dd>
<dd>In addition, there will be opportunities to provide
input through public consultations and public comment
processes that the PDP WG is expected to organize.<br>
<br>
<b>How to Join</b> </dd>
<dd><br>
If you are interested in joining the WG as an individual
participant or mailing list observer, please fill in the
<a moz-do-not-send="true"
href="http://goo.gl/forms/bb65iIznLv">sign up form</a>
or send the <a moz-do-not-send="true"
href="http://gnso.icann.org/en/issues/gnso-pdp-next-gen-rds-wg-sign-up-04jan16-en.docx">Word
document</a> [DOCX, 72 KB] filled in to the <a
moz-do-not-send="true"
href="mailto:gnso-secs@icann.org">
GNSO Secretariat</a><br>
</dd>
<dd>All members and observers will be listed on the PDP
WG's wiki page. <br>
<br>
<b>Next steps</b> </dd>
<dd><br>
In its motion, the GNSO Council directed that this call
for volunteers be circulated as widely as possible in
order to ensure broad representation and participation
in the WG. This call will remain open until the WG
convenes for the first time. At this juncture, it is
anticipated that the PDP WG may convene online in late
January 2015. Following that, regular online meetings
will be scheduled in accordance with the PDP WG’s work
plan, which it is expected to develop as one of its
first tasks.<br>
<br>
<b>Further information and preparation</b> </dd>
<dd>For those interested in volunteering for this effort,
you are strongly encouraged to review the following
materials prior to the first meeting of the PDP WG:
</dd>
<dd>The <a moz-do-not-send="true"
href="https://whois.icann.org/sites/default/files/files/final-issue-report-next-generation-rds-07oct15-en.pdf">Final
Issue Report</a> </dd>
<dd>The <a moz-do-not-send="true"
href="http://gnso.icann.org/en/drafts/whois-ng-gtld-rds-charter-07oct15-en.pdf">approved
charter</a> </dd>
<dd>Materials available at the PDP <a
moz-do-not-send="true"
href="https://community.icann.org/display/gTLDRDS/Next-Generation+gTLD+Registration+Directory+Services+to+Replace+Whois">WG's
wiki</a> such as the EWG Final Report and other
relevant information. </dd>
<dd>
<h3><b>Background</b></h3>
<br>
Created in the 1980s, WHOIS began as a service to
identify and contact entities responsible for the
operation of a network resource on the Internet. Over
the years, ICANN's requirements for gTLD domain name
registration data collection, access and accuracy have
undergone some important changes. Yet, after nearly 15
years of task forces, review teams, and studies,
comprehensive WHOIS policy reform remains the source of
long-running discussion and debate.<br>
</dd>
<dd>In 2012, the ICANN Board launched the Expert Working
Group on gTLD Registration Directory Services (EWG) to
help redefine the purpose of gTLD registration data and
consider how to safeguard the data, and to propose a
model for gTLD registration directory services (RDS) to
address accuracy, privacy, and access issues.<br>
</dd>
<dd>Upon publication of the EWG's Final Report in June,
2014, an informal group of GNSO Councilors and ICANN
Board Members collaborated to propose a Process
Framework for structuring a GNSO PDP to successfully
address these challenging issues. This Process Framework
was adopted by the Board in 2015, along with a
reaffirmation of its 2012 request for a PDP to be
convened to define the purpose of collecting,
maintaining and providing access to gTLD registration
data. The Board also asked that the PDP consider
safeguards for protecting data, using the
recommendations in the EWG's Final Report as an input
to, and, if appropriate, as the foundation for a new
gTLD policy.<br>
</dd>
<dd>In preparation for this PDP, a new <a
moz-do-not-send="true"
href="http://whois.icann.org/sites/default/files/files/rds-prelim-issue-13jul15-en.pdf">Preliminary
Issue Report</a> [PDF, 1.4 MB] was published for <a
moz-do-not-send="true"
href="https://www.icann.org/public-comments/rds-prelim-issue-2015-07-13-en">public
comment</a> on 13 July 2015. A <a
moz-do-not-send="true"
href="https://whois.icann.org/sites/default/files/files/final-issue-report-next-generation-rds-07oct15-en.pdf">Final
Issue Report</a> [PDF, 1.2 MB] was subsequently
published on 7 October 2015, including links to all
public comments received, along with a draft charter for
the PDP WG. This draft charter was approved by the GNSO
Council on
<a moz-do-not-send="true"
href="https://community.icann.org/display/gnsocouncilmeetings/Motions+19+November+2015">19
November 2015</a>, enabling the formation of a GNSO
working group of community volunteers to progress this
PDP.<br>
</dd>
<dd>More information can be found on the <a
moz-do-not-send="true"
href="http://gnso.icann.org/en/group-activities/active/rds">
GNSO PDP on Next-Generation gTLD Registration
Directory Service (RDS) page</a> and the
<a moz-do-not-send="true"
href="https://community.icann.org/display/gTLDRDS/Next-Generation+gTLD+Registration+Directory+Services+to+Replace+Whois">WG's
wiki</a>, including the WG's charter, inputs already
provided by all SG/Cs during the public comment period,
and an extensive library of foundational materials to
inform the WG's deliberations. In addition, the WG will
reach out to all SG/Cs for feedback on any items that
they believe should be considered that may not have been
specifically called out in the approved charter.<br>
</dd>
<dd>As this will be a complex multi-phase PDP, all those
interested in helping to shape the policy framework for
a next-generation gTLD RDS are encouraged to volunteer
for this WG. Only with the help of the entire community
can this WG achieve its goal of formally defining an
appropriate purpose of gTLD registration data and
establishing a new policy framework to enable
permissible access to that data with improved privacy
and accuracy.<br>
<br>
<br>
</dd>
<dd>
<h5><br>
</h5>
<br>
</dd>
</dl>
<br>
</div>
</div>
</div>
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 14">
<meta name="Originator" content="Microsoft Word 14">
<link rel="File-List" href="eui%20footer_files/filelist.xml">
<link rel="themeData" href="eui%20footer_files/themedata.thmx">
<link rel="colorSchemeMapping"
href="eui%20footer_files/colorschememapping.xml">
<style> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520092929 1073786111 9 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line
-height:115%;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> </style>
<style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} </style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959">The
information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material. Any review, retransmission,
dissemination, distribution, forwarding, 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 without the express permission of the sender. If
you received this communication in error, please contact the
sender and delete the material from any computer. <o:p>
</o:p></span></p>
</div>
</blockquote>
<br>
</body>
</html>